S32.112 — Severely displaced Zone I fracture of sacrum
Is S32.112 billable?
No — S32.112 is a non-billable header code. S32.112 groups more specific codes and cannot be submitted on a claim. A valid ICD-10-CM code must be reported at the highest level of specificity available in its branch. Select one of the 6 billable codes beneath S32.112.
Billable codes under this header
- S32.112ASeverely displaced Zone I fracture of sacrum, initial encounter for closed fracture
- S32.112BSeverely displaced Zone I fracture of sacrum, initial encounter for open fracture
- S32.112DSeverely displaced Zone I fracture of sacrum, subsequent encounter for fracture with routine healing
- S32.112GSeverely displaced Zone I fracture of sacrum, subsequent encounter for fracture with delayed healing
- S32.112KSeverely displaced Zone I fracture of sacrum, subsequent encounter for fracture with nonunion
- S32.112SSeverely displaced Zone I fracture of sacrum, sequela
S32.112 at a glance
| Code | S32.112 |
|---|---|
| Description | Severely displaced Zone I fracture of sacrum |
| Billable | No — header code |
| Code set | ICD-10-CM FY2027 |
| Valid for encounters | October 1, 2026 – September 30, 2027 |
How is S32.112 listed in the Alphabetic Index?
These are the routes through the Alphabetic Index that lead to S32.112. They show the wording a clinician may have documented, which often differs from the Tabular description.
- Fracture, traumatic › sacrum › Zone › I › displaced › severely (abduction) (adduction) (separation)
- Fracture, traumatic › vertebra, vertebral › sacrum › Zone › I › displaced › severely (abduction) (adduction) (separation)
Excludes1 — never code together — inherited from S32
The conditions below can never be reported together with S32.112 on the same claim. An Excludes1 note means the two conditions cannot occur in the same patient, so reporting both is a coding error.
- transection of abdomen (S38.3)
Code first — inherited from S32
The underlying condition below must be sequenced before S32.112. S32.112 describes a manifestation and cannot be the principal or first-listed diagnosis.
- any associated spinal cord and spinal nerve injury (S34.-)
Use additional code — inherited from Chapter 19
Report an additional code alongside S32.112 to fully describe the condition. S32.112 is sequenced first.
- code to identify any retained foreign body, if applicable (Z18.-)
Excludes2 — not included here — inherited from Chapter 19
The conditions below are not part of S32.112, but a patient may have both at the same time. When documentation supports it, S32.112 and the excluded code may both be reported.
Excludes2 — not included here — inherited from S30-S39
The conditions below are not part of S32.112, but a patient may have both at the same time. When documentation supports it, S32.112 and the excluded code may both be reported.
Excludes2 — not included here — inherited from S32
The conditions below are not part of S32.112, but a patient may have both at the same time. When documentation supports it, S32.112 and the excluded code may both be reported.
- fracture of hip NOS (S72.0-)
Code also — inherited from S32.1
Two codes may be needed to describe the condition fully. Whether S32.112 is sequenced first depends on the reason for the encounter.
- any associated fracture of pelvic ring (S32.8-)
What codes fall under S32.112? (6)
- S32.112ASeverely displaced Zone I fracture of sacrum, initial encounter for closed fracture
- S32.112BSeverely displaced Zone I fracture of sacrum, initial encounter for open fracture
- S32.112DSeverely displaced Zone I fracture of sacrum, subsequent encounter for fracture with routine healing
- S32.112GSeverely displaced Zone I fracture of sacrum, subsequent encounter for fracture with delayed healing
- S32.112KSeverely displaced Zone I fracture of sacrum, subsequent encounter for fracture with nonunion
- S32.112SSeverely displaced Zone I fracture of sacrum, sequela
How long has S32.112 existed?
S32.112 has been in ICD-10-CM since at least FY2016, the earliest fiscal year on record here.
Derived from the official order files for FY2016–FY2026. FY2017 and FY2020 publish no order file, so those years are not covered.