Skip to main content

T78.111D ICD-10-CM Code: Other adverse food reaction due to milk and dairy products with reactivity to baked milk, subsequent encounter

Billing Status: YES. This is a valid, specific, and billable ICD-10-CM reference.

Coding at a Glance

Inpatient Payment Groups (MS-DRG)

Potential MS-DRG participation — not a DRG assignment.

MS-DRGs this diagnosis helps define, as principal or secondary, per the CMS ICD-10-CM/PCS MS-DRG Definitions Manual v43, Appendix B.

A diagnosis appearing in a group's logic does not by itself determine the DRG assigned to a stay; the grouper uses the full claim.

Coding instructions

Official Tabular Instructional Notes: the inclusion, exclusion and sequencing notes published for T78.111D in the official ICD-10-CM tabular list, quoted as published.

Notes without a marker are published on T78.111D itself; “inherited from” names the category or block whose note applies here.

Excludes1 — Not Coded Here

Conditions generally not reported together with this code (Excludes1) -- an error unless the two conditions are documented as unrelated to each other (ICD-10-CM Official Guidelines, Section I.A.12.a).

Excludes2 — Not Included Here

Conditions not covered by this code, but which may be reported alongside it when both are present.

Code Also

Additional codes that may be required to fully describe the encounter.

  • Code also, if applicable, place of occurrence, such as:
  • highway rest stop (Y92.523)
  • school (private) (public) (state) as the place of occurrence of the external cause (Y92.21-)
  • service areas as the place of occurrence of the external cause (Y92.52-)
  • single-family non-institutional (private) house as the place of occurrence of the external cause (Y92.01-)
  • transport vehicle as the place of occurrence of the external cause (Y92.81-)

Source: inherited from T66-T78

Use Additional Code

Supplementary codes the tabular list directs you to add.

  • Use additional code to identify the type of reaction, if applicable

Source: inherited from T78.1

7th Character Guide

"The appropriate 7th character is to be added to each code from category T78"

  • A — initial encounter
  • D — subsequent encounter (this page’s code)
  • S — sequela

How the encounter character is assigned. “Initial encounter” means the patient is receiving active treatment for the condition — it is not limited to the first visit, and a different or new provider giving active treatment still assigns it. “Subsequent encounter” covers care during the healing or recovery phase after active treatment. “Sequela” is for complications or conditions that arise as a direct result of the original condition.

ICD-10-CM Official Guidelines for Coding and Reporting, Section I.C.19.a (paraphrased by MedCoder).

Variant codes in this family

T78.111A, T78.111D, T78.111S

Character meanings are CMS's official 7th-character extensions for this family, as carried in each variant code's official description; variant codes are registry rows. The explanation of how the encounter character is assigned is MedCoder editorial, distinct from the official content above it.

Coder workflow for T78.111D

MedCoder structured workflow — derived from this code’s own official record

Before you code T78.111D

  1. “Other” (NEC) means the condition is specified in the record but no dedicated code captures it. Confirm the documented form is not one a sibling code names before settling on T78.111D; if the record states no specifics at all, the unspecified sibling applies instead. “Other” codes are for documented conditions the classification gives no specific code; “unspecified” codes are for records lacking the detail (Guidelines I.A.9.a, I.A.9.b).

    See the relationships section · Guide: Other vs unspecified (NEC vs NOS) →

  2. A 7th character is required in this family. Confirm the documented encounter: initial (active treatment), subsequent (healing or recovery phase), or sequela. This page’s code carries “D”. “Initial” means active treatment, not the first visit (Guidelines I.C.19.a).

    See the 7th Character Guide · Guide: 7th characters: initial, subsequent, sequela →

  3. T78.111D’s title joins a condition with an associated condition or complication. Confirm each component is documented. Where the classification presumes the link through the “with” convention, only a provider statement that the conditions are unrelated defeats it. A combination code is assigned only when it fully identifies the documented conditions; a required second code for the stage, type or manifestation is still reported when the notes ask for it (Guidelines I.B.9, I.A.15).

    Guide: Combination codes →

  4. Check the Excludes1 note: if the documentation supports a condition named there, do not simply proceed with T78.111D. Excludes1 conditions are not reported together with this code unless the record shows they are unrelated (Guidelines I.A.12.a).

    See the official tabular notes

Choose the right path

  1. Does the documentation support a condition named in T78.111D’s Excludes1 note?
    Yes → Do not simply proceed: review the excluded code. Both are reported only when the record shows the two conditions are unrelated.
    No → Continue.

    ReviewT78.110, T78.0, A05

  2. Is the encounter phase documented — active treatment, healing or recovery, or a sequela?
    Yes → Assign the matching 7th character; the variant codes are in the 7th Character Guide.
    No → The code is invalid without its 7th character — query for the missing element.

Consider T78.111D. Then work the Use Additional Code note and review the Code Also note, and confirm the code is valid for the date of service in the Verify section.

Documentation check

The provider’s diagnostic statement
Codes are assigned from the provider’s documented diagnosis, not from clinical criteria, test values or a medication list (Guidelines I.A.19).
Encounter type
Active treatment, healing or recovery phase, or sequela — the basis of the 7th character (Guidelines I.C.19.a).
The associated condition or complication
Whether the associated condition the title names is documented; the “with” convention presumes some links, and a provider statement that the conditions are unrelated defeats it (Guidelines I.A.15).
The conditions the Use Additional Code note names
Reported with this code when documented; a conditional instruction (“if applicable”, “if known”) applies only when the record supports it.
Any detail beyond this code’s title
What the record states that a more specific sibling code would capture — or its absence, which itself supports the unspecified code.

Official instructions as workflow

  • Excludes1 — check before selecting T78.111D(4 notes)

    Coding workflow: If the documentation supports a condition named in this note, do not simply proceed with T78.111D: the two are not reported together. The one exception is when the record shows the two conditions are unrelated to each other.

    CompareT78.110, T78.0, A05

    See the official tabular notes · Guidelines I.A.12.a

  • Excludes2 — not part of T78.111D(7 notes)

    Coding workflow: The conditions named in this note are not included in T78.111D. When the record documents both, both may be reported; the note is a boundary, not a prohibition.

    CompareK52.29, J30.5, L23.6, L24.6, L25.4, L27.2

    See the official tabular notes · Guidelines I.A.12.b

  • Use Additional Code — after identifying T78.111D(1 note)

    Coding workflow: Check whether the documentation supports the additional code(s) the note names, and report them with T78.111D when it does. Where the instruction is conditional (“if applicable”, “if known”), it applies only when the record documents the condition.

    See the official tabular notes · Guidelines I.A.13

  • Code Also — related condition(6 notes)

    Coding workflow: Review the related condition when both are documented and the instruction applies. A Code Also note does not fix sequencing; the order follows the circumstances of the encounter.

    ReviewY92.523, Y92.21, Y92.52, Y92.01, Y92.81

    See the official tabular notes · Guidelines I.A.17

Coding decision scenarios

Pattern scenarios for this code’s structure — decision rules, not clinical cases

Documentation: Both the condition T78.111D describes and a condition named in its Excludes1 note are documented for the same encounter.

Coding question: Can both codes be reported?

Path: Review the Excludes1 note and the excluded code, and look for a provider statement on whether the two conditions are related.

Reason: Excludes1 means the two are not coded together; the exception is when the record shows the conditions are unrelated to each other (Guidelines I.A.12.a).

ReviewT78.110, T78.0, A05

Documentation: The patient returns during the healing or recovery phase after active treatment of the same condition.

Coding question: Which 7th character applies?

Path: Review the official 7th-character definitions for this family in the 7th Character Guide.

Reason: “Initial encounter” means active treatment, not the first visit; care during recovery takes “subsequent encounter”, and a complication arising from the original condition takes “sequela” (Guidelines I.C.19.a).

Documentation: Only one of the components this code’s title joins is documented.

Coding question: Is T78.111D supported?

Path: Review the code for the documented component on its own.

Reason: A combination code is assigned only when it fully identifies the documented conditions; otherwise the documented component takes its own code (Guidelines I.B.9).

Every row is derived from this code’s own record — its title, tabular notes, 7th-character family and same-category siblings — with fixed MedCoder wording; nothing is inferred about a patient. The official notes and guideline text are in the sections each row links to, and they control.

Code Overview

Other adverse food reaction due to milk and dairy products with reactivity to baked milk, subsequent encounter is a billable ICD-10-CM diagnosis code (T78.111D).

MedCoder summary Summary composed by MedCoder from this code's official ICD-10-CM record. The tabular instructional notes themselves appear verbatim below.

Indexed Clinical Terms (2)

Official source data — entries quoted as published, in the Index’s own lookup phrasing

Clinical term phrases from the official ICD-10-CM Index to Diseases and Injuries that map to this code. These are alphabetic-index entries shown as the Index writes them — lookup phrasing, not necessarily the wording of a final diagnosis.

Decision Points

The directives on this code's own record, as a pre-claim checklist.

  1. A 7th character applies in this family. Confirm the documented encounter matches the character assigned. See the official 7th-character definitions and this code’s variants
  2. 1 Use Additional Code instruction — report the named additional code(s) when the documentation supports them. See the Use Additional Code notes
  3. 6 Code Also notes — a second code may apply; the guidelines leave its sequencing to the circumstances of the encounter. See the Code Also notes
  4. 4 Excludes1 entries — codes named there are generally not reported together with this code (Guidelines I.A.12.a). See the Excludes1 notes
  5. 7 Excludes2 entries — those conditions are not part of this code and may be reported additionally when documented. See the Excludes2 notes

Checklist rows are derived from this code's own official directives; the wording of each check is MedCoder editorial. The official notes themselves are in the sections each row links to.

Verify Before Coding

  • Principal-diagnosis restriction. The Medicare Code Editor lists this code as unacceptable as a principal diagnosis: it describes a circumstance influencing health status rather than a current illness or injury being treated. It is valid as a secondary diagnosis.

From the code registry, the Medicare Code Editor, and the MS-DRG Definitions Manual. Check it against a full claim in Claim Check.

Relationships & Classification

MedCoder structured relationships — computed from published CMS and AHRQ datasets

Other codes that name T78.111D or its code family, from the CMS ICD-10-CM tabular instructional notes. Tabular-note edges are stored at the code family level that carries each note.

Referenced by 1 Excludes1 note: T75 — Other and unspecified effects of other external causes (via T78.-).

These codes’ tabular lists mark this diagnosis as mutually exclusive — not reported together unless the conditions are documented as unrelated.

Referenced by 1 Excludes2 note: L27 — Dermatitis due to substances taken internally (via T78.-).

These codes’ tabular lists name this diagnosis as distinct — both may be reported when both are documented.

MS-DRG Grouper Relationships (FY2026)

Potential MS-DRG participation — not a DRG assignment.

Not on the CMS CC/MCC list — as a secondary diagnosis this code does not change MS-DRG severity.

Named in the grouper logic of 2 MS-DRGs: DRG 949 (MDC 23), DRG 950 (MDC 23).

From the CMS MS-DRG Definitions Manual (Appendices B and C). Actual DRG assignment depends on the complete claim.

Clinical classification (AHRQ CCSR):INJ067 — Allergic reactions, subsequent encounter (default).

Clinical Classifications Software Refined (CCSR) for ICD-10-CM Diagnoses. Healthcare Cost and Utilization Project (HCUP), Agency for Healthcare Research and Quality.

Related Codes

Principal diagnosis restriction (Medicare Code Editor)

Not acceptable as a principal diagnosis on an inpatient claim.

Same injury, other encounter phase

Same injury, coded at a different phase of treatment via the 7th character.

T78.111A — Other adverse food reaction due to milk and dairy products with reactivity to baked milk, initial encounterCompare T78.111D vs T78.111A →, T78.111S — Other adverse food reaction due to milk and dairy products with reactivity to baked milk, sequela

Same clinical category (CCSR)

AHRQ's Clinical Classifications Software groups these diagnoses under the same clinical category (Allergic reactions, subsequent encounter).

T78.05XD — Anaphylactic reaction due to tree nuts and seeds, subsequent encounter, T78.06XD — Anaphylactic reaction due to food additives, subsequent encounter, T78.070D — Anaphylactic reaction due to milk and dairy products with tolerance to baked milk, subsequent encounter, T78.071D — Anaphylactic reaction due to milk and dairy products with reactivity to baked milk, subsequent encounter, T78.079D — Anaphylactic reaction due to milk and dairy products, unspecified, subsequent encounter, T78.080D — Anaphylactic reaction due to egg with tolerance to baked egg, subsequent encounter, T78.081D — Anaphylactic reaction due to egg with reactivity to baked egg, subsequent encounter, T78.089D — Anaphylactic reaction due to eggs, unspecified, subsequent encounter, T78.09XD — Anaphylactic reaction due to other food products, subsequent encounter, T78.110D — Other adverse food reactions due to milk and dairy products with tolerance to baked milk, subsequent encounter, T78.119D — Other adverse food reaction due to milk and dairy products with baked milk tolerance/reactivity, unspecified, subsequent encounter, T78.120D — Other adverse food reaction due to egg with tolerance to baked egg, subsequent encounter, T78.121D — Other adverse food reaction due to egg with reactivity to baked egg, subsequent encounter, T78.129D — Other adverse food reaction due to egg with baked egg tolerance/reactivity, unspecified, subsequent encounter, T78.19XD — Other adverse food reactions, not elsewhere classified, subsequent encounter, T78.2XXD — Anaphylactic shock, unspecified, subsequent encounter, T78.3XXD — Angioneurotic edema, subsequent encounter, T78.40XD — Allergy, unspecified, subsequent encounter, T78.41XD — Arthus phenomenon, subsequent encounter, T78.49XD — Other allergy, subsequent encounter, +6 more

Contextual Map

Every relationship of T78.111D in one view: hierarchy, official tabular instructions in both directions, clinical classification, risk adjustment, MS-DRG participation, index terms and change history — each edge carrying the CMS source it derives from.

Run T78.111D with these 2 related codes in Claim Check

Hierarchy

Referenced by Excludes1 notes

Referenced by Excludes2 notes

Clinical classification (CCSR)

MS-DRG Grouper

MDC crossing

  • MDC 23 — Factors Influencing Health Status and Other Contacts with Health Services[MDC crossing]: “Factors Influencing Health Status and Other Contacts with Health Services — the grouper's crossing between diagnoses and procedures: a principal diagnosis sets the MDC, and same-MDC procedures move the stay to its surgical DRGs. 1,235 same-MDC procedures group here; browse them on the MDC page.”— CMS MS-DRG Definitions Manual · FY2026

Index entries

  • Allergy, allergic (reaction) (to), dairy products, with, reactivity to baked milk[Index term]— CMS ICD-10-CM Index to Diseases and Injuries · icd10cm-fy2026
  • Allergy, allergic (reaction) (to), milk protein, adverse reaction NEC, with, reactivity to baked milk[Index term]— CMS ICD-10-CM Index to Diseases and Injuries · icd10cm-fy2026

Nearest codes (40)

Change history

Common coding questions

Does T78.111D require a 7th character?

Yes. The appropriate 7th character is to be added to each code from category T78.

Sources for this page

Codes, titles, notes, index terms and mappings on this page are transcribed from the datasets below. Relationships MedCoder computed and text MedCoder wrote are labelled where they appear.

Code, title, tabular notes and index terms Official source data
CMS/CDC ICD-10-CM FY2026 tabular list, index and tables, effective October 1, 2025 Release, file and checksum · Publisher’s page
Claim edits Official source data
CMS Definitions of Medicare Code Edits — v43.1 (April 2026) Release, file and checksum · Publisher’s page
Inpatient payment groups Official source data
CMS MS-DRG Definitions Manual (incl. Appendix B diagnosis index, Appendix C CC/MCC list, Appendix E procedure index) and IPPS Final Rule tables — v43 Release, file and checksum · Publisher’s page
Change history and date-of-service validity Official source data
CMS ICD-10-CM release addenda, ingested release by release into the change ledger Release, file and checksum · Publisher’s page
Comparisons, relationships and the contextual map MedCoder structured relationship
Computed by MedCoder from the tabular notes and tables above; every derived relationship is marked as derived where it appears
Summary and FAQ answers MedCoder explanation
Written by MedCoder to explain the sources above: drafted with AI assistance, checked by a person against the release files, and labelled as MedCoder text where it appears. Not official text.

Labels on this page: Official source data · MedCoder structured relationship · MedCoder explanation. How to read the labels · All data sources and release dates

Change history

  • FY2026 — October 1, 2025
    Added to the code set
    Other adverse food reaction due to milk and dairy products with reactivity to baked milk, subsequent encounter
    FY2026 changes

Nearest Codes in This Family

Official ICD-10-CM classifications closest to T78.111D in its code family, with their registry titles.

View all codes in the T78 family