ICD code T78.09XA – Anaphylactic reaction due to other food products

Key takeaways

T78.09XA is valid on HIPAA-covered claims as a principal or secondary diagnosis under ICD-10-CM FY2026.

The 7th character A means active treatment. Use D for follow-up visits and S for sequela.

T78.09XA applies only when the food has no dedicated code. Peanuts, shellfish, other fish, fruits and vegetables, tree nuts and seeds, food additives, milk, and eggs take T78.01-T78.08.

A food reaction without documented anaphylaxis takes T78.1XXA, not T78.09XA.

Pabau, the practice management platform we build, scrubs T78.09XA claims for errors and submits them to US payers through Claim.MD.

ICD-10 code T78.09XA: Definition and clinical placement

ICD-10 code T78.09XA is the billable code for anaphylactic reaction due to other food products, initial encounter. Use it when the clinician documents anaphylaxis caused by a food without its own code, such as soy, wheat, or corn.

The patient must still be in active treatment. The code sits in category T78 within Chapter 19 of the CDC/NCHS ICD-10-CM tabular list, which covers codes S00-T88.

Category T78 is residual. It collects adverse effects and anaphylactic reactions that have no more precise home elsewhere in the classification. Under T78.0, anaphylactic reaction due to food, eight common triggers get their own codes, T78.01 through T78.08. T78.09 covers every other named food.

Understanding the 7th character: A, D, and S

The ICD-10-CM Chapter 19 instructions require a 7th character on all T78.09 codes to define the encounter type. T78.09XA uses the mandatory placeholder “X” at the 6th position (no 6th-character subdivision exists) followed by the 7th character. A wrong encounter character is enough for a payer to reject the claim.

Per the ICD-10-CM Official Guidelines (Section I.C.19.a), “initial encounter” means the patient is still receiving active treatment for this event. It doesn’t mean the first time the patient has ever had anaphylaxis.

A second ED visit two days later for the same reaction still uses character “A” if treatment is ongoing. Switching to “D” is appropriate only when the condition is being managed as a healed or healing issue rather than an acute one.

What “other food products” includes and excludes

T78.09XA is the catch-all for named foods. The ICD-10-CM tabular list gives eight common food triggers their own codes under T78.0. T78.09XA is valid only when the documented food is none of them.

Two neighbors sit outside this table. When the record names no food at all, T78.00XA (anaphylactic reaction due to unspecified food) applies instead.

T78.1 (other adverse food reactions, not elsewhere classified) covers food reactions that don’t meet anaphylaxis criteria, such as gastrointestinal upset. If the clinician’s note confirms anaphylaxis, T78.1 is wrong whichever food is involved.

T78.09XA vs similar codes: How to choose the right one

T78.09XA is often confused with two other codes: T78.40XA (allergy unspecified, initial encounter) and T78.1XXA (other adverse food reaction, non-anaphylactic). Three questions settle the choice, and the order matters.

T78.09XA and T78.40XA are easy to mix up. T78.40XA is for allergy, not anaphylaxis, and it does not specify food as the trigger. Using T78.40XA when the documentation clearly states “anaphylactic reaction to soy” is an under-coding error that payers may flag during claims review.

Clinical documentation required for an anaphylactic reaction claim

T78.09XA claims are only defensible when the medical record contains specific elements. A vague notation of “food allergy reaction” is not sufficient. Auditors and payers look for four documentation anchors before accepting the code.

• Anaphylaxis confirmed in writing: The treating clinician must use the word “anaphylaxis” or “anaphylactic reaction” in the assessment. Phrases like “severe allergic response” or “possible anaphylaxis” leave the coder without clear direction and expose the claim to denial or query.
• Food identified as the causative agent: The specific food must be documented. If the food is named and it falls within T78.01-T78.08, that code takes precedence over T78.09XA. Only proceed with T78.09XA when the named food has no dedicated subcategory.
• Food NOT in the T78.01-T78.08 list: This is the coder’s responsibility to verify, not something clinicians typically state explicitly. Check the documented food against the T78.01-T78.08 exclusion list before assigning T78.09XA.
• Encounter type consistent with the 7th character: The note must show whether the visit is active treatment (“A”) or follow-up of a resolved event (“D”). Conflicting signals, such as “post-anaphylaxis follow-up” alongside “epinephrine administered today,” should prompt a physician query before billing.

For clean claim submission, build a prompt covering all four elements into your anaphylaxis encounter template. A medical billing workflow that checks the note before the claim goes out saves a round of rework and resubmission.

Payer requirements and claim submission guidance

T78.09XA is recognized by Medicare, Medicaid, and most commercial payers as a valid primary or secondary diagnosis code. Payer-specific Local Coverage Determinations (LCDs) vary by Medicare Administrative Contractor (MAC) region, so verify with your specific MAC before submitting. The guidance below reflects general CMS ICD-10-CM coding principles rather than any single payer’s LCD.

When T78.09XA is the reason for an emergency department visit, it typically serves as the principal diagnosis. An allergy workup or desensitization consult after the event may list it as a secondary diagnosis.

The primary reason for that visit goes first. Per CMS ICD-10 coding guidance, sequencing follows the circumstances of the admission. The condition most responsible for the visit becomes the principal code.

Prior authorization is generally not required for emergency anaphylaxis treatment coded under T78.09XA. Follow-up allergy testing, desensitization protocols, or specialty referrals may need prior authorization. That depends on the payer and the CPT codes involved. Check payer portals before scheduling non-emergency services.

Common claim denial reasons and how to fix them

T78.09XA denials usually trace back to one of four causes. Each has a clear fix, and front-end documentation checks prevent most of them.

A structured denial management workflow that categorizes T78 denials by denial reason code speeds up the corrective process. Practices handling many anaphylaxis claims should also keep the medical billing denial codes reference handy. It lists the CARC/RARC codes payers use when rejecting T78.09XA claims.

Codes commonly reported alongside T78.09XA

T78.09XA rarely appears alone on a claim. The following codes are frequently submitted alongside it, depending on the clinical encounter and treatment delivered.

When T78.09XA is the main reason for the encounter, it is coded as principal. Companion codes for treatment (J0171, CPT E/M) follow as additional codes. On a later visit for allergy testing, the reason for that visit becomes principal and T78.09XD becomes secondary.

Our electronic remittance advice processing guide shows how payers signal sequencing errors on 835 ERA files. For the wider picture, the revenue cycle management guide covers how these code pairings fit into the full claim lifecycle.

Before submission, check T78 placement against the CDC tabular list or the AAPC ICD-10-CM code lookup. The WHO ICD-10 browser shows the international version. It stops at T78.0, with no T78.09 subcategory and no 7th characters.

How Pabau catches T78.09XA coding errors before submission

Without a claims tool, a biller checks the food in the note against T78.01-T78.08 by hand, then rekeys the code into a clearinghouse portal. A wrong food code or 7th character only shows up when the denial comes back.

Pabau keeps the encounter note, the diagnosis code, and the claim in one patient record. Its medical billing software scrubs every claim for missing or invalid details before it leaves Pabau. A claim that still comes back rejected is flagged Needs action, with a link to the field to correct.

US practices submit CMS-1500 claims through Claim.MD and settle payments straight from ERA files. Our Claim.MD clearinghouse overview explains how submission, tracking, and reconciliation work.

Send T78.09XA claims out clean

Pabau scrubs each claim for missing or invalid details and submits it to US payers through Claim.MD. Rejections come back flagged with the field to fix.

Book a demo

Conclusion

T78.09XA rewards one habit at the point of care. Name the food, use the word anaphylaxis, and state whether treatment is still active. With those three facts in the note, the code choice takes seconds and holds up on audit.

Without them, coders fall back on T78.40XA or guess the 7th character, and the claim comes back for rework. Check the food against T78.01-T78.08 before you reach for the catch-all, and query the clinician when the note is vague.

Book a demo to see how Pabau checks T78.09XA claims for errors before they leave your practice.

Continue your research

Need to understand how denials are categorized and resolved? Denial management in healthcare covers the full workflow for identifying, appealing, and preventing claim rejections.

Frequently asked questions