ICD-10 Coding for Avascular Necrosis of Hip(M16.9, M16.9U, M87.85)
Comprehensive guide on ICD-10 coding for avascular necrosis of the hip, including documentation requirements, coding pitfalls, and billing considerations.
Complete code families applicable to Avascular Necrosis of Hip
Compare key differences between these codes to ensure accurate selection
| Code | Description | When to Use | Key Documentation |
|---|---|---|---|
| M87.851 | Osteonecrosis of right femur | Use when avascular necrosis is confirmed in the right femoral head with documented laterality. |
|
| M87.852 | Osteonecrosis of left femur | Use when avascular necrosis is confirmed in the left femoral head with documented laterality. |
|
| M87.859 | Osteonecrosis of unspecified femur | Use when avascular necrosis is confirmed but laterality cannot be determined. |
|
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 aboutAvascular Necrosis of Hip
Alternative codes to consider when ruling out similar conditions
Use only if osteoarthritis is secondary to AVN and both conditions are documented.
Documentation & Coding Risks
Avoid these common issues when documenting Avascular Necrosis of Hip.
Failure to document etiology of AVN
Impact
Clinical: May affect treatment decisions., Regulatory: Non-compliance with documentation standards., Financial: Potential for denied claims.
Mitigation
Always include etiology in patient history., Use templates to ensure comprehensive documentation.
Coding AVN without specifying laterality
Impact
Reimbursement: May lead to reduced reimbursement due to unspecified coding., Compliance: Non-compliance with coding standards., Data Quality: Decreases accuracy of clinical data.
Mitigation
Always document and code the specific side affected by AVN.
Laterality Documentation
Impact
Failure to document laterality can lead to audit findings.
Mitigation
Implement mandatory fields in EHR for laterality.