ICD-10 Coding for Macular Pucker(H35.34, H35.37, H35.371)
Comprehensive guide to ICD-10 coding for macular pucker, including documentation requirements and clinical validation.
Complete code families applicable to Macular Pucker
Compare key differences between these codes to ensure accurate selection
| Code | Description | When to Use | Key Documentation |
|---|---|---|---|
| H35.371 | Macular pucker, right eye | Use when macular pucker is confirmed in the right eye. |
|
| H35.372 | Macular pucker, left eye | Use when macular pucker is confirmed in the left eye. |
|
| H35.373 | Macular pucker, bilateral | Use when macular pucker is confirmed in both eyes. |
|
| H35.379 | Macular pucker, unspecified eye | Use only when 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 aboutMacular Pucker
Alternative codes to consider when ruling out similar conditions
Documentation & Coding Risks
Avoid these common issues when documenting Macular Pucker.
Failing to document laterality.
Impact
Clinical: Inaccurate treatment planning., Regulatory: Non-compliance with coding standards., Financial: Potential claim denials.
Mitigation
Always verify and document laterality., Use standardized templates.
Using unspecified laterality codes when laterality is documented.
Impact
Reimbursement: May lead to claim denials or reduced reimbursement., Compliance: Non-compliance with coding guidelines., Data Quality: Decreases accuracy of clinical data.
Mitigation
Always document and code the specific eye affected.
Confusing macular pucker with macular hole.
Impact
Reimbursement: Incorrect coding can lead to improper billing., Compliance: Violates coding standards., Data Quality: Affects clinical data integrity.
Mitigation
Differentiate based on OCT findings and clinical presentation.
Unspecified laterality
Impact
Using unspecified codes when laterality is documented.
Mitigation
Implement mandatory laterality documentation checks.