S32.810 — Multiple fractures of pelvis with stable disruption of pelvic ring
Is S32.810 billable?
No — S32.810 is a non-billable header code. S32.810 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.810.
Billable codes under this header
- S32.810AMultiple fractures of pelvis with stable disruption of pelvic ring, initial encounter for closed fracture
- S32.810BMultiple fractures of pelvis with stable disruption of pelvic ring, initial encounter for open fracture
- S32.810DMultiple fractures of pelvis with stable disruption of pelvic ring, subsequent encounter for fracture with routine healing
- S32.810GMultiple fractures of pelvis with stable disruption of pelvic ring, subsequent encounter for fracture with delayed healing
- S32.810KMultiple fractures of pelvis with stable disruption of pelvic ring, subsequent encounter for fracture with nonunion
- S32.810SMultiple fractures of pelvis with stable disruption of pelvic ring, sequela
S32.810 at a glance
| Code | S32.810 |
|---|---|
| Description | Multiple fractures of pelvis with stable disruption of pelvic ring |
| Billable | No — header code |
| Code set | ICD-10-CM FY2027 |
| Valid for encounters | October 1, 2026 – September 30, 2027 |
How is S32.810 listed in the Alphabetic Index?
These are the routes through the Alphabetic Index that lead to S32.810. They show the wording a clinician may have documented, which often differs from the Tabular description.
- Disruption › pelvic ring (of)
Excludes1 — never code together — inherited from S32
The conditions below can never be reported together with S32.810 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.810. S32.810 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.810 to fully describe the condition. S32.810 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.810, but a patient may have both at the same time. When documentation supports it, S32.810 and the excluded code may both be reported.
Excludes2 — not included here — inherited from S30-S39
The conditions below are not part of S32.810, but a patient may have both at the same time. When documentation supports it, S32.810 and the excluded code may both be reported.
Excludes2 — not included here — inherited from S32
The conditions below are not part of S32.810, but a patient may have both at the same time. When documentation supports it, S32.810 and the excluded code may both be reported.
- fracture of hip NOS (S72.0-)
Code also — inherited from S32.8
Two codes may be needed to describe the condition fully. Whether S32.810 is sequenced first depends on the reason for the encounter.
What codes fall under S32.810? (6)
- S32.810AMultiple fractures of pelvis with stable disruption of pelvic ring, initial encounter for closed fracture
- S32.810BMultiple fractures of pelvis with stable disruption of pelvic ring, initial encounter for open fracture
- S32.810DMultiple fractures of pelvis with stable disruption of pelvic ring, subsequent encounter for fracture with routine healing
- S32.810GMultiple fractures of pelvis with stable disruption of pelvic ring, subsequent encounter for fracture with delayed healing
- S32.810KMultiple fractures of pelvis with stable disruption of pelvic ring, subsequent encounter for fracture with nonunion
- S32.810SMultiple fractures of pelvis with stable disruption of pelvic ring, sequela
How long has S32.810 existed?
S32.810 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.