Skip to main content

S72.24 vs S72.25

S72.24 (Nondisplaced subtrochanteric fracture of right femur) compared with S72.25 (Nondisplaced subtrochanteric fracture of left femur), from the official CMS tabular data. S72.24 and S72.25 code the same condition on opposite sides. MedCoder-derived

Relationship

Review

Laterality relationship

S72.24
Right
Nondisplaced subtrochanteric fracture of right femur
S72.25
Left
Nondisplaced subtrochanteric fracture of left femur

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. S72.24 and S72.25 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

S72.24Nondisplaced subtrochanteric fracture of right femurS72.25Nondisplaced subtrochanteric fracture of left femur
Billing statusNon-billable header

Report instead: S72.24XA, S72.24XB, S72.24XC, S72.24XD, S72.24XE

Non-billable header

Report instead: S72.25XA, S72.25XB, S72.25XC, S72.25XD, S72.25XE

ClassificationS00-T88 — Injury, poisoning and certain other consequences of external causesS00-T88 — Injury, poisoning and certain other consequences of external causes
DefinitionNondisplaced subtrochanteric fracture of right femur is a non-billable ICD-10-CM category code (S72.24).Nondisplaced subtrochanteric fracture of left femur is a non-billable ICD-10-CM category code (S72.25).
7th characterThe appropriate 7th character is to be added to all codes from category S72The appropriate 7th character is to be added to all codes from category S72

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