ICD-10 Coding for Food Poisoning(A05.9, A05.9B, A05.9M)
Explore ICD-10 coding for food poisoning, including A05.9 and T62.9 codes, documentation requirements, and common pitfalls.
Complete code families applicable to Food Poisoning
Compare key differences between these codes to ensure accurate selection
| Code | Description | When to Use | Key Documentation |
|---|---|---|---|
| A05.9 | Bacterial foodborne intoxication, unspecified | Use when gastroenteritis is documented with food poisoning and bacterial etiology is suspected or confirmed. |
|
| T62.9 | Toxic effect of unspecified substance eaten as food | Use when food poisoning is documented without bacterial confirmation. |
|
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 aboutFood Poisoning
Alternative codes to consider when ruling out similar conditions
Documentation & Coding Risks
Avoid these common issues when documenting Food Poisoning.
Vague documentation of 'food poisoning'
Impact
Clinical: Inadequate information for treatment decisions., Regulatory: Non-compliance with coding standards., Financial: Potential for claim denials.
Mitigation
Educate providers on documentation specificity, Implement documentation templates
Using K52.9 with A05.9
Impact
Reimbursement: May lead to claim denials or reduced reimbursement., Compliance: Non-compliance with ICD-10 guidelines., Data Quality: Inaccurate data reporting and analysis.
Mitigation
Omit K52.9 as A05.9 includes gastroenteritis manifestation.
Coding T62.9 when provider documents 'food poisoning' without qualifiers
Impact
Reimbursement: Potential for incorrect DRG assignment., Compliance: Risk of audit findings for incorrect coding., Data Quality: Misleading data on food poisoning cases.
Mitigation
Query for clarification on bacterial vs toxic etiology.
Etiology Documentation
Impact
Lack of specific etiology documentation can lead to audit findings.
Mitigation
Ensure provider documentation includes specific bacterial or toxic cause.