Back to HomeBeta

ICD-10 Coding for Food Poisoning(A05.9, T62.9)

Complete ICD-10-CM coding and documentation guide for Food Poisoning. Includes clinical validation requirements, documentation requirements, and coding pitfalls.

Also known as:

Foodborne IllnessGastroenteritis due to Food Poisoning

Related ICD-10 Code Ranges

Complete code families applicable to Food Poisoning

A05Primary Range

Other bacterial foodborne intoxications, not elsewhere classified

This range includes bacterial foodborne intoxications, which are primary for food poisoning when bacterial etiology is confirmed.

Toxic effect of other noxious substances eaten as food

This range is used for toxic effects from food when bacterial etiology is not confirmed.

Code Comparison: When to Use Each Code

Compare key differences between these codes to ensure accurate selection

CodeDescriptionWhen to UseKey Documentation
A05.9Bacterial foodborne intoxication, unspecifiedUse when gastroenteritis is documented with food poisoning and bacterial etiology is suspected or confirmed.
  • Provider documentation of gastroenteritis due to food poisoning
  • Stool culture confirming bacterial presence
T62.9Toxic effect of unspecified substance eaten as foodUse when food poisoning is documented without bacterial confirmation.
  • Provider documentation of food poisoning without bacterial confirmation
  • Symptoms consistent with toxic ingestion

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: ICD-10 code for food poisoning

Essential facts and insights about Food Poisoning

The ICD-10 code for unspecified bacterial foodborne intoxication is A05.9, while T62.9 is used for toxic effects of substances eaten as food without bacterial confirmation.

Primary ICD-10-CM Codes for food poison

Bacterial foodborne intoxication, unspecified
Billable Code

Decision Criteria

clinical Criteria

  • Documented gastroenteritis with suspected bacterial cause

coding Criteria

  • Avoid using K52.9 with A05.9 as it is included

Applicable To

  • Gastroenteritis due to food poisoning

Excludes

Clinical Validation Requirements

  • Provider documentation of gastroenteritis due to food poisoning
  • Stool culture confirming bacterial presence

Code-Specific Risks

  • Misclassification if bacterial etiology is not confirmed

Coding Notes

  • Ensure bacterial etiology is documented to avoid misclassification.

Ancillary Codes

Additional codes that should be used in conjunction with the main diagnosis codes when applicable.

Nausea and vomiting

R11.2
Use to document severe nausea and vomiting requiring treatment.

Differential Codes

Alternative codes to consider when ruling out similar conditions to the primary diagnosis.

Toxic effect of unspecified substance eaten as food

T62.9
Use when food poisoning is documented without bacterial confirmation.

Bacterial foodborne intoxication, unspecified

A05.9
Use when bacterial etiology is confirmed or suspected.

Documentation & Coding Risks

Avoid these common documentation and coding issues when documenting Food Poisoning to ensure proper reimbursement, maintain compliance, and reduce audit risk. These guidelines are particularly important when using ICD-10 code A05.9.

Impact

Clinical: Inadequate information for treatment decisions., Regulatory: Non-compliance with coding standards., Financial: Potential for claim denials.

Mitigation Strategy

Educate providers on documentation specificity, Implement documentation templates

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 Strategy

Omit K52.9 as A05.9 includes gastroenteritis manifestation.

Impact

Reimbursement: Potential for incorrect DRG assignment., Compliance: Risk of audit findings for incorrect coding., Data Quality: Misleading data on food poisoning cases.

Mitigation Strategy

Query for clarification on bacterial vs toxic etiology.

Impact

Lack of specific etiology documentation can lead to audit findings.

Mitigation Strategy

Ensure provider documentation includes specific bacterial or toxic cause.

Documentation errors, coding pitfalls, and audit risks are interconnected aspects of medical coding and billing. Addressing all three areas helps ensure accurate coding, optimal reimbursement, and regulatory compliance.

Frequently Asked Questions

Common questions about ICD-10 coding for Food Poisoning, with expert answers to help guide accurate code selection and documentation.

Documentation Templates for Food Poisoning

Use these documentation templates to ensure complete and accurate documentation for Food Poisoning. These templates include all required elements for proper coding and billing.

Emergency Department Visit for Food Poisoning

Specialty: Emergency Medicine

Required Elements

  • Chief complaint
  • History of present illness
  • Exposure details
  • Diagnostic tests
  • Treatment plan

Example Documentation

Chief Complaint: 'Vomiting and diarrhea after eating at [venue]' HPI: - Onset: 4hrs post-ingestion of raw oysters - Symptoms: 6 episodes watery diarrhea, 3x emesis - Associated: Fever 38.5°C, abdominal cramping - Exposure: Group meal with 3 others symptomatic Assessment: Acute bacterial gastroenteritis (A05.9) secondary to suspected Vibrio infection from raw shellfish exposure Plan: - Stool for culture/PCR - IV fluids - Ciprofloxacin 500mg BID

Examples: Poor vs. Good Documentation

Poor Documentation Example
Patient has food poisoning.
Good Documentation Example
Patient presents with acute gastroenteritis secondary to bacterial food poisoning from undercooked poultry.
Explanation
The good example specifies the cause and symptoms, providing a clear basis for coding.

Need help with ICD-10 coding for Food Poisoning? Ask your questions below.

Ask about any ICD-10 CM code, or paste a medical note

We build tools for
clinician happiness.

Learn More at Freed.ai
Back to HomeBeta

Built by Freed

Try Freed for free for 7 days.

Learn more