T36.92XA — Poisoning by unspecified systemic antibiotic, intentional self-harm, initial encounter
Is T36.92XA billable?
Yes, but T36.92XA is an unspecified code. T36.92XA is a valid, billable ICD-10-CM code for encounters from October 1, 2026 through September 30, 2027. However, T36.92XA 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.92XA — the more specific alternatives are listed below.
More specific alternatives
- T36.0X1APoisoning by penicillins, accidental (unintentional), initial encounter
- T36.1X1APoisoning by cephalosporins and other beta-lactam antibiotics, accidental (unintentional), initial encounter
- T36.2X1APoisoning by chloramphenicol group, accidental (unintentional), initial encounter
- T36.3X1APoisoning by macrolides, accidental (unintentional), initial encounter
- T36.4X1APoisoning by tetracyclines, accidental (unintentional), initial encounter
- T36.5X1APoisoning by aminoglycosides, accidental (unintentional), initial encounter
- T36.6X1APoisoning by rifampicins, accidental (unintentional), initial encounter
- T36.7X1APoisoning by antifungal antibiotics, systemically used, accidental (unintentional), initial encounter
- T36.8X1APoisoning by other systemic antibiotics, accidental (unintentional), initial encounter
- T36.AX1APoisoning by fluoroquinolone antibiotics, accidental (unintentional), initial encounter
T36.92XA at a glance
| Code | T36.92XA |
|---|---|
| Description | Poisoning by unspecified systemic antibiotic, intentional self-harm, initial encounter |
| Billable | Yes |
| Code set | ICD-10-CM FY2027 |
| Valid for encounters | October 1, 2026 – September 30, 2027 |
| 7th character "A" | initial encounter |
What does the 7th character "A" mean in T36.92XA?
In T36.92XA, the 7th character A means initial encounter. The 7th character is required for T36.92XA to be a valid, complete code.
Same condition, different episode of care — switch the 7th character:
Which MS-DRGs does T36.92XA group to?
T36.92XA 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.
- 917Poisoning and Toxic Effects of Drugs with MCCmedical
- 918Poisoning and Toxic Effects of Drugs without MCCmedical
Excludes1 — never code together — inherited from T36-T50
The conditions below can never be reported together with T36.92XA 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.92XA 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.92XA. T36.92XA 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.92XA to fully describe the condition. T36.92XA 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.92XA to fully describe the condition. T36.92XA is sequenced first.
Excludes2 — not included here — inherited from Chapter 19
The conditions below are not part of T36.92XA, but a patient may have both at the same time. When documentation supports it, T36.92XA and the excluded code may both be reported.
Excludes2 — not included here — inherited from T36-T50
The conditions below are not part of T36.92XA, but a patient may have both at the same time. When documentation supports it, T36.92XA and the excluded code may both be reported.
How long has T36.92XA existed?
T36.92XA 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.