ICD-10 Coding for High Serum Digoxin Level(E87.5U, I49.9U, R79.89)
Learn how to accurately code and document high serum digoxin levels using ICD-10. Understand the clinical criteria, documentation requirements, and coding pitfalls.
Complete code families applicable to High Serum Digoxin Level
Compare key differences between these codes to ensure accurate selection
| Code | Description | When to Use | Key Documentation |
|---|---|---|---|
| T46.0X | Poisoning by cardiac-stimulant glycosides | Use when there is confirmed digoxin toxicity with specified intent. |
|
| R79.89 | Other specified abnormal findings of blood chemistry | Use for elevated digoxin levels without clinical symptoms of toxicity. |
|
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 aboutHigh Serum Digoxin Level
Alternative codes to consider when ruling out similar conditions
Use when digoxin toxicity is documented without specific details on intent or symptoms.
Documentation & Coding Risks
Avoid these common issues when documenting High Serum Digoxin Level.
Omitting serum level documentation
Impact
Clinical: May lead to inappropriate treatment decisions., Regulatory: Non-compliance with documentation standards., Financial: Potential for claim denial or reduced reimbursement.
Mitigation
Always include serum levels in documentation., Use templates to ensure completeness.
Using T88.7 for confirmed digoxin toxicity
Impact
Reimbursement: Potential underpayment due to lack of specificity., Compliance: Non-compliance with coding guidelines requiring specificity., Data Quality: Decreased accuracy in clinical data reporting.
Mitigation
Use T46.0X with appropriate 7th character for specificity.
Specificity of coding
Impact
Risk of audits due to lack of specificity in coding digoxin toxicity.
Mitigation
Ensure documentation supports the use of specific codes with appropriate 7th characters.