T36.91XS — Poisoning by unspecified systemic antibiotic, accidental (unintentional), sequela
Is T36.91XS billable?
Yes, but T36.91XS is an unspecified code. T36.91XS is a valid, billable ICD-10-CM code for encounters from October 1, 2026 through September 30, 2027. However, T36.91XS is an unspecified or catch-all code. Payers apply additional scrutiny to unspecified codes and many deny them when the medical record supports a more specific option, so check the documentation before selecting T36.91XS — the more specific alternatives are listed below.
More specific alternatives
- T36.0X1SPoisoning by penicillins, accidental (unintentional), sequela
- T36.1X1SPoisoning by cephalosporins and other beta-lactam antibiotics, accidental (unintentional), sequela
- T36.2X1SPoisoning by chloramphenicol group, accidental (unintentional), sequela
- T36.3X1SPoisoning by macrolides, accidental (unintentional), sequela
- T36.4X1SPoisoning by tetracyclines, accidental (unintentional), sequela
- T36.5X1SPoisoning by aminoglycosides, accidental (unintentional), sequela
- T36.6X1SPoisoning by rifampicins, accidental (unintentional), sequela
- T36.7X1SPoisoning by antifungal antibiotics, systemically used, accidental (unintentional), sequela
- T36.8X1SPoisoning by other systemic antibiotics, accidental (unintentional), sequela
- T36.AX1SPoisoning by fluoroquinolone antibiotics, accidental (unintentional), sequela
T36.91XS at a glance
| Code | T36.91XS |
|---|---|
| Description | Poisoning by unspecified systemic antibiotic, accidental (unintentional), sequela |
| Billable | Yes |
| Code set | ICD-10-CM FY2027 |
| Valid for encounters | October 1, 2026 – September 30, 2027 |
| 7th character "S" | sequela |
What does the 7th character "S" mean in T36.91XS?
In T36.91XS, the 7th character S means sequela. The 7th character is required for T36.91XS to be a valid, complete code.
Same condition, different episode of care — switch the 7th character:
Which MS-DRGs does T36.91XS group to?
T36.91XS sits in MDC 21 and helps define the logic of 2 MS-DRGs (version 44, FY2027). Which one a stay actually groups to also depends on procedures and secondary diagnoses.
- 922Other Injury, Poisoning and Toxic Effect Diagnoses with MCCmedical
- 923Other Injury, Poisoning and Toxic Effect Diagnoses without MCCmedical
Inclusion terms
Alternative wording in documentation that is classified to T36.91XS.
- Poisoning by systemic antibiotic NOS
Excludes1 — never code together — inherited from T36-T50
The conditions below can never be reported together with T36.91XS on the same claim. An Excludes1 note means the two conditions cannot occur in the same patient, so reporting both is a coding error.
- toxic reaction to local anesthesia in pregnancy (O29.3-)
Excludes1 — never code together — inherited from T36
The conditions below can never be reported together with T36.91XS on the same claim. An Excludes1 note means the two conditions cannot occur in the same patient, so reporting both is a coding error.
Code first — inherited from T36-T50
The underlying condition below must be sequenced before T36.91XS. T36.91XS describes a manifestation and cannot be the principal or first-listed diagnosis.
Use additional code — inherited from Chapter 19
Report an additional code alongside T36.91XS to fully describe the condition. T36.91XS is sequenced first.
- code to identify any retained foreign body, if applicable (Z18.-)
Use additional code — inherited from T36-T50
Report an additional code alongside T36.91XS to fully describe the condition. T36.91XS is sequenced first.
Excludes2 — not included here — inherited from Chapter 19
The conditions below are not part of T36.91XS, but a patient may have both at the same time. When documentation supports it, T36.91XS and the excluded code may both be reported.
Excludes2 — not included here — inherited from T36-T50
The conditions below are not part of T36.91XS, but a patient may have both at the same time. When documentation supports it, T36.91XS and the excluded code may both be reported.
How long has T36.91XS existed?
T36.91XS has been in ICD-10-CM since at least FY2016, the earliest fiscal year on record here.
Derived from the official order files for FY2016–FY2026. FY2017 and FY2020 publish no order file, so those years are not covered.