ICD-10 Coding for Carotid Artery Disease(I63.5, I63.511U, I63.512U)

Explore detailed ICD-10 coding guidelines for carotid artery disease, including specific codes for stenosis and occlusion, documentation requirements, and common pitfalls.

Also known as:
Carotid StenosisCarotid OcclusionCarotid Atherosclerosis
Related ICD-10 Code Ranges

Complete code families applicable to Carotid Artery Disease

Code Comparison: When to Use Each Code

Compare key differences between these codes to ensure accurate selection

CodeDescription
I65.21Occlusion and stenosis of right carotid artery
I65.22Occlusion and stenosis of left carotid artery

Clinical Decision Support

Always review the patient's clinical documentation thoroughly. When in doubt, choose the more specific code and ensure documentation supports it.

Key Information

Essential facts and insights aboutCarotid Artery Disease

Differential Codes

Alternative codes to consider when ruling out similar conditions

Cerebral infarction due to embolism of right carotid arteryI63.511

Use when infarction is directly linked to carotid embolism.

Cerebral infarction due to embolism of left carotid arteryI63.512

Use when infarction is directly linked to carotid embolism.

Documentation & Coding Risks

Avoid these common issues when documenting Carotid Artery Disease.

Omitting laterality in documentation

Impact

Clinical: Potential for incorrect treatment planning., Regulatory: Non-compliance with coding standards., Financial: Loss of reimbursement due to unspecified coding.

Mitigation

Always document laterality in clinical notes., Verify imaging reports include laterality.

Using I77.9 for specific carotid stenosis

Impact

Reimbursement: Potential underpayment due to lack of specificity., Compliance: Non-compliance with coding guidelines., Data Quality: Inaccurate data representation of patient condition.

Mitigation

Use I65.2- codes with specific laterality and stenosis details.

Unspecified coding

Impact

Using unspecified codes like I77.9 when specific codes apply.

Mitigation

Implement regular training on documentation specificity.

Frequently Asked Questions