ICD-10 Coding for Stye Left Eye(H00.0, H00.015, H00.015B)
Learn about ICD-10 coding for styes on the left eye, including specific codes for external and internal hordeolum. Ensure accurate documentation and coding compliance.
Complete code families applicable to Stye Left Eye
Compare key differences between these codes to ensure accurate selection
| Code | Description | When to Use | Key Documentation |
|---|---|---|---|
| H00.015 | Hordeolum externum left lower eyelid | Use when documentation specifies an external stye on the left lower eyelid. |
|
| H00.016 | Hordeolum externum left eye, unspecified eyelid | Use when documentation mentions a stye on the left eye but does not specify the eyelid. |
|
| H00.025 | Hordeolum internum left lower eyelid | Use when documentation specifies an internal stye on the left lower eyelid. |
|
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 aboutStye Left Eye
Alternative codes to consider when ruling out similar conditions
Documentation & Coding Risks
Avoid these common issues when documenting Stye Left Eye.
Documenting 'stye left eye' without specifying eyelid.
Impact
Clinical: May lead to incorrect treatment if the type of stye is not clear., Regulatory: Increases risk of coding audits., Financial: Potential for reduced reimbursement due to unspecified coding.
Mitigation
Ensure documentation includes specific eyelid location., Educate clinicians on the importance of detailed documentation.
Using unspecified codes when specific eyelid information is available.
Impact
Reimbursement: May lead to lower reimbursement due to lack of specificity., Compliance: Increases risk of audits for overuse of unspecified codes., Data Quality: Reduces accuracy of clinical data and reporting.
Mitigation
Ensure documentation specifies the eyelid location to use the most specific code.
Use of unspecified codes
Impact
Frequent use of unspecified codes can trigger audits.
Mitigation
Ensure documentation is detailed and specific to support the most accurate code.