Skip to main content

S89.291S vs S89.292S

S89.291S (Other physeal fracture of upper end of right fibula, sequela) compared with S89.292S (Other physeal fracture of upper end of left fibula, sequela), from the official CMS tabular data. S89.291S and S89.292S code the same condition on opposite sides.

Relationship

Review

Laterality relationship

S89.291S
Right
Other physeal fracture of upper end of right fibula, sequela
S89.292S
Left
Other physeal fracture of upper end of left fibula, sequela

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. S89.291S and S89.292S 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

S89.291SOther physeal fracture of upper end of right fibula, sequelaS89.292SOther physeal fracture of upper end of left fibula, sequela
Billing statusBillableBillable
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)
DefinitionOther physeal fracture of upper end of right fibula, sequela is a billable ICD-10-CM diagnosis code (S89.291S).Other physeal fracture of upper end of left fibula, sequela is a billable ICD-10-CM diagnosis code (S89.292S).
7th characterThe appropriate 7th character is to be added to each code from subcategories S89.0, S89.1, S89.2, and S89.3The appropriate 7th character is to be added to each code from subcategories S89.0, S89.1, S89.2, and S89.3

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