T26.71 (Corrosion with resulting rupture and destruction of right eyeball) compared with T26.72 (Corrosion with resulting rupture and destruction of left eyeball), from the official CMS tabular data. T26.71 and T26.72 code the same condition on opposite sides. MedCoder-derived
Same condition; these differ only in which side is documented.
These codes share a category and title and differ only in the side affected. The documentation decides which applies, and a bilateral code is reported only where the code set provides one.
Source: ICD-10-CM tabular list (laterality variant derived from the code title)
Same condition, opposite side. T26.71 and T26.72 name the same condition on opposite sides of the body.
Same category and title, differing only in which side is affected — the documentation decides which one applies, and a bilateral code is reported only where the code set provides one.
| T26.71Corrosion with resulting rupture and destruction of right eyeball | T26.72Corrosion with resulting rupture and destruction of left eyeball | |
|---|---|---|
| Billing status | Non-billable header | Non-billable header |
| Classification | S00-T88 — Injury, poisoning and certain other consequences of external causes | S00-T88 — Injury, poisoning and certain other consequences of external causes |
| Definition | Corrosion with resulting rupture and destruction of right eyeball is a non-billable ICD-10-CM category code (T26.71). | Corrosion with resulting rupture and destruction of left eyeball is a non-billable ICD-10-CM category code (T26.72). |
| 7th character | The appropriate 7th character is to be added to each code from category T26 | The appropriate 7th character is to be added to each code from category T26 |
| Use additional code | external cause code to identify place (Y92) | external cause code to identify place (Y92) |
| Code first | (T51-T65) to identify chemical and intent | (T51-T65) to identify chemical and intent |
Derived from the official CMS ICD-10-CM tabular data (FY2026). Not billing advice; verify sequencing rules for the encounter. All data sources