Skip to main content

S72.135S vs S72.136S

S72.135S (Nondisplaced apophyseal fracture of left femur, sequela) compared with S72.136S (Nondisplaced apophyseal fracture of unspecified femur, sequela), from the official CMS tabular data. S72.135S and S72.136S code the same condition on opposite sides. MedCoder-derived

Relationship

Review

Laterality relationship

S72.135S
Left
Nondisplaced apophyseal fracture of left femur, sequela
S72.136S
Unspecified
Nondisplaced apophyseal fracture of unspecified femur, 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. S72.135S and S72.136S 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.135SNondisplaced apophyseal fracture of left femur, sequelaS72.136SNondisplaced apophyseal fracture of unspecified femur, 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)
DefinitionNondisplaced apophyseal fracture of left femur, sequela is a billable ICD-10-CM diagnosis code (S72.135S).Nondisplaced apophyseal fracture of unspecified femur, sequela is a billable ICD-10-CM diagnosis code (S72.136S).
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