Skip to main content

G97.0 vs T83.62XA

G97.0 (Cerebrospinal fluid leak from spinal puncture) compared with T83.62XA (Infection and inflammatory reaction due to implanted testicular prosthesis, initial encounter), from the official CMS tabular data. Both may be reported when both conditions are documented (Excludes2).

Relationship

Informational

Excludes2 relationship

T83.62XA
Infection and inflammatory reaction due to implanted testicular prosthesis, initial encounter
G97.0
Cerebrospinal fluid leak from spinal puncture

Distinct conditions — both may be reported.

“cerebrospinal fluid leak from spinal puncture (G97.0)”

An Excludes2 note means the excluded condition is not part of the code above it, but a patient can have both. Report both when both are documented.

Source: CMS ICD-10-CM tabular instructional notes

Can these codes be reported together?

Yes, when both are documented. T83.62XA carries an Excludes2 note covering G97.0: “cerebrospinal fluid leak from spinal puncture (G97.0)”

Excludes2 marks distinct conditions — both may be reported when both are documented.

Side by side

G97.0Cerebrospinal fluid leak from spinal punctureT83.62XAInfection and inflammatory reaction due to implanted testicular prosthesis, initial encounter
Billing statusBillableBillable
ClassificationG00-G99 — Diseases of the Nervous System (G00-G99)S00-T88 — Injury, Poisoning and Certain Other Consequences of External Causes (S00-T88)
DefinitionCerebrospinal fluid leak from spinal puncture is a billable ICD-10-CM diagnosis code (G97.0).Infection and inflammatory reaction due to implanted testicular prosthesis, initial encounter is a billable ICD-10-CM diagnosis code (T83.62A).
7th characterThe appropriate 7th character is to be added to each code from category T83
Use additional code
code to identify infection
code for adverse effect, if applicable, to identify drug (T36-T50 with fifth or sixth character 5)
code(s) to identify the specified condition resulting from the complication

Derived from the official CMS ICD-10-CM tabular data (FY2026). Not billing advice; verify sequencing rules for the encounter. All data sources