Skip to main content

S02.642K vs T16

S02.642K (Fracture of ramus of left mandible, subsequent encounter for fracture with nonunion) compared with T16 (Foreign body in ear), from the official CMS tabular data. Both may be reported when both conditions are documented (Excludes2).

Relationship

Informational

Excludes2 relationship

S02.642K
Fracture of ramus of left mandible, subsequent encounter for fracture with nonunion
T16
Foreign body in ear

Distinct conditions — both may be reported.

“effects of foreign body in ear (T16)”

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. S02.642K carries an Excludes2 note covering T16: “effects of foreign body in ear (T16)”

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

Side by side

S02.642KFracture of ramus of left mandible, subsequent encounter for fracture with nonunionT16Foreign body in ear
Billing statusBillableNon-billable header

Report instead: T16.1XXA, T16.1XXD, T16.1XXS, T16.2XXA, T16.2XXD

ClassificationS00-T88 — Injury, Poisoning and Certain Other Consequences of External Causes (S00-T88)S00-T88 — Injury, Poisoning and Certain Other Consequences of External Causes (S00-T88)
DefinitionFracture of ramus of left mandible, subsequent encounter for fracture with nonunion is a billable ICD-10-CM diagnosis code (S02.642K).Foreign body in ear is a non-billable ICD-10-CM category code (T16).
7th characterThe appropriate 7th character is to be added to each code from category S02The appropriate 7th character is to be added to each code from category T16
Includes
injuries of ear
injuries of eye
injuries of face [any part]
injuries of gum
foreign body in auditory canal
Use additional code
code, if known, for foreign body entering into or through a natural orifice (W44.-)

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