T36 vs Y63.9

Summary

What is different?

The conditions named, billing status and chapter.T36 is “Poisoning by, adverse effect of and underdosing of systemic antibiotics”; Y63.9 is “Failure in dosage during unspecified surgical and medical care”. T36 is a non-billable header; Y63.9 is billable. T36 sits in S00-T88 — Injury, Poisoning and Certain Other Consequences of External Causes (S00-T88); Y63.9 in V00-Y99 — External Causes of Morbidity (V00-Y99).

Registry fact

Can these codes be reported together?

Yes, when both are documented.Y63.9 lists T36 under Excludes2: “accidental overdose of drug or wrong drug given in error (T36-T50)”. Excludes2 marks distinct conditions that may both be reported when both are documented.

Official ruleGuide: Excludes1 vs Excludes2

Is there an Excludes1 relationship?

None.Neither entry carries an Excludes1 note that names the other code. T36 carries 5 Excludes1 notes and Y63.9 carries 1 Excludes1 note covering other codes; the side-by-side table quotes them.

Official rule

Is there an Excludes2 relationship?

Yes.Y63.9’s tabular entry: “accidental overdose of drug or wrong drug given in error (T36-T50)”. The note covers T36.

Official ruleGuide: Excludes1 vs Excludes2

Is one more specific?

Not comparable.The codes sit in different categories; specificity is only comparable within one category.

Is one a parent or header code?

One is a header.T36 is a non-billable header, but Y63.9 is not one of its subdivisions.

Registry fact

Are there sequencing instructions?

Yes.T36 first, Y63.9 as an additional code: T36 carries a Use Additional Code instruction covering Y63.9 (“underdosing or failure in dosage during medical and surgical care (Y63.6, Y63.8-Y63.9)”).

Official ruleGuide: Code First vs Use Additional Code vs Code Also

Are there other coding relationships?

None found.No laterality, encounter-phase, Table of Neoplasms, Table of Drugs and Chemicals, or history-versus-active-disease relationship links these codes.

MedCoder-derived

Official rule: a tabular instructional note or a section of the ICD-10-CM Official Guidelines, quoted as published. Registry fact: the codes’ own published attributes (titles, billable status, position in the hierarchy, code set). MedCoder-derived: a reading MedCoder computes from those facts; it is not itself a rule. How to read the labels

Can these codes be reported together?

Sequencing on the claim

Official guidance behind these answers

• Section I.A.12.b — Excludes2 · applies to: Excludes2

  A type 2 Excludes note represents “Not included here.” An excludes2 note indicates that the condition excluded is not part of the condition represented by the code, but a patient may have both conditions at the same time. When an Excludes2 note appears under a code, it is acceptable to use both the code and the excluded code together, when appropriate.

  ICD-10-CM Official Guidelines FY2026

• Section I.B.7 — Multiple coding for a single condition · applies to: Code first / Use additional code

  In addition to the etiology/manifestation convention that requires two codes to fully describe a single condition that affects multiple body systems, there are other single conditions that also require more than one code. “Use additional code” notes are found in the Tabular List at codes that are not part of an etiology/manifestation pair where a secondary code is useful to fully describe a condition. The sequencing rule is the same as the etiology/manifestation pair, “use additional code” indicates that a secondary code should be added, if known. For example, for bacterial infections that are not included in chapter 1, a secondary code from category B95, Streptococcus, Staphylococcus, and Enterococcus, as the cause of diseases classified elsewhere, or B96, Other bacterial agents as the cause of diseases classified elsewhere, may be required to identify the bacterial organism causing the infection. A “use additional code” note will normally be found at the infectious disease code, indicating a need for the organism code to be added as a secondary code. “Code first” notes are also under certain codes that are not specifically manifestation codes but may be due to an underlying cause. When there is a “code first” note and an underlying condition is present, the underlying condition should be sequenced first, if known. […]

  ICD-10-CM Official Guidelines FY2026

• Section I.A.13 — Etiology/manifestation convention (“code first”, “use additional code” and “in diseases classified elsewhere” notes) · applies to: Etiology/manifestation convention

  Certain conditions have both an underlying etiology and multiple body system manifestations due to the underlying etiology. For such conditions, the ICD-10-CM has a coding convention that requires the underlying condition be sequenced first, if applicable, followed by the manifestation. Wherever such a combination exists, there is a “use additional code” note at the etiology code, and a “code first” note at the manifestation code. These instructional notes indicate the proper sequencing order of the codes, etiology followed by manifestation. In most cases the manifestation codes will have in the code title, “in diseases classified elsewhere.” Codes with this title are a component of the etiology/ manifestation convention. The code title indicates that it is a manifestation code. “In diseases classified elsewhere” codes are never permitted to be used as first listed or principal diagnosis codes. They must be used in conjunction with an underlying condition code and they must be listed following the underlying condition. See category F02, Dementia in other diseases classified elsewhere, for an example of this convention. There are manifestation codes that do not have “in diseases classified elsewhere” in the title. For such codes, there is a “use additional code” note at the etiology code and a “code first” note at the manifestation code, and the rules for sequencing apply. […]

  ICD-10-CM Official Guidelines FY2026

Quoted from the ICD-10-CM Official Guidelines for Coding and Reporting in effect for the release shown. The tabular notes above are the code-level instruction; these sections are the convention that says how such a note is applied. Source document (CMS PDF) · Release and checksum

Side by side

Notes are the code’s own tabular entry, quoted as published. A note that names the other code is the one the verdict above rests on.