Skip to main content

S82.432 vs S82.433

S82.432 (Displaced oblique fracture of shaft of left fibula) compared with S82.433 (Displaced oblique fracture of shaft of unspecified fibula), from the official CMS tabular data. S82.432 and S82.433 code the same condition on opposite sides.

Relationship

Review

Laterality relationship

S82.432
Left
Displaced oblique fracture of shaft of left fibula
S82.433
Unspecified
Displaced oblique fracture of shaft of unspecified fibula

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)

Can these codes be reported together?

Same condition, opposite side. S82.432 and S82.433 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.

Side by side

S82.432Displaced oblique fracture of shaft of left fibulaS82.433Displaced oblique fracture of shaft of unspecified fibula
Billing statusNon-billable headerNon-billable header
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)
DefinitionDisplaced oblique fracture of shaft of left fibula is a non-billable ICD-10-CM category code (S82.432).Displaced oblique fracture of shaft of unspecified fibula is a non-billable ICD-10-CM category code (S82.433).
7th characterThe appropriate 7th character is to be added to all codes from category S82The appropriate 7th character is to be added to all codes from category S82
Includes
fracture of malleolus
fracture of malleolus

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