ICD-10 Coding for Lacunar Infarction and Costovertebral Angle Tenderness(I63.4, I63.81, I63.81B)
Explore ICD-10 coding for lacunar infarction (I63.81) and CVA tenderness (R10.819), including documentation requirements and common pitfalls.
Complete code families applicable to Lacunar Infarction and Costovertebral Angle Tenderness
Compare key differences between these codes to ensure accurate selection
| Code | Description | When to Use | Key Documentation |
|---|---|---|---|
| I63.81 | Other cerebral infarction due to occlusion or stenosis of small artery | Use when imaging confirms a lacunar infarct and risk factors for small vessel disease are documented. |
|
| R10.819 | Abdominal tenderness, unspecified site | Use when CVA tenderness is noted without a definitive diagnosis. |
|
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 aboutLacunar Infarction and Costovertebral Angle Tenderness
Alternative codes to consider when ruling out similar conditions
Documentation & Coding Risks
Avoid these common issues when documenting Lacunar Infarction and Costovertebral Angle Tenderness.
Using R10.819 for unspecified abdominal pain
Impact
Clinical: May lead to inappropriate treatment focus., Regulatory: Non-compliance with coding specificity requirements., Financial: Potential for claim denials due to lack of specificity.
Mitigation
Ensure documentation specifies CVA tenderness, Link symptoms to potential renal causes
Confusing CVA (stroke) with CVA tenderness
Impact
Reimbursement: Incorrect coding can lead to denied claims., Compliance: Misinterpretation of clinical context violates coding guidelines., Data Quality: Inaccurate data on patient conditions and treatments.
Mitigation
Clarify context in documentation to distinguish between cerebrovascular accident and costovertebral angle tenderness.
Stroke coding
Impact
Misclassification of stroke types due to vague documentation.
Mitigation
Educate providers on the importance of specifying stroke types in documentation.