S32.464K — Nondisplaced associated transverse-posterior fracture of right acetabulum, subsequent encounter for fracture with nonunion
Is S32.464K billable?
Yes — S32.464K is billable for FY2027. S32.464K is a valid, billable ICD-10-CM code at the highest level of specificity in its branch. S32.464K may be submitted for encounters from October 1, 2026 through September 30, 2027.
S32.464K at a glance
| Code | S32.464K |
|---|---|
| Description | Nondisplaced associated transverse-posterior fracture of right acetabulum, subsequent encounter for fracture with nonunion |
| Billable | Yes |
| Code set | ICD-10-CM FY2027 |
| Valid for encounters | October 1, 2026 – September 30, 2027 |
| 7th character "K" | subsequent encounter for fracture with nonunion |
What does the 7th character "K" mean in S32.464K?
In S32.464K, the 7th character K means subsequent encounter for fracture with nonunion. The 7th character is required for S32.464K to be a valid, complete code.
Same condition, different episode of care — switch the 7th character:
Which MS-DRGs does S32.464K group to?
S32.464K sits in MDC 08 and helps define the logic of 2 MS-DRGs (version 44, FY2027). Which one a stay actually groups to also depends on procedures and secondary diagnoses.
- 521Hip Replacement with Principal Diagnosis of Hip Fracture with MCCsurgical
- 522Hip Replacement with Principal Diagnosis of Hip Fracture without MCCsurgical
As a secondary diagnosis, S32.464K is a complication or comorbidity (CC), which can move a stay into a higher-paying DRG.
How is S32.464K listed in the Alphabetic Index?
The Alphabetic Index lists these routes under S32.46, the nearest indexed parent of S32.464K. Use them to find the family, then select the specific code.
- Fracture, traumatic › acetabulum › transverse › with associated posterior wall fracture (abduction) (adduction) (separation)
- Fracture, traumatic › acetabulum › transverse › with associated posterior wall fracture › nondisplaced (abduction) (adduction) (separation)
- Fracture, traumatic › acetabulum › wall › posterior › with associated transverse fracture (abduction) (adduction) (separation)
- Fracture, traumatic › acetabulum › wall › posterior › with associated transverse fracture › nondisplaced (abduction) (adduction) (separation)
Excludes1 — never code together — inherited from S32
The conditions below can never be reported together with S32.464K 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.464K. S32.464K 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.464K to fully describe the condition. S32.464K 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.464K, but a patient may have both at the same time. When documentation supports it, S32.464K and the excluded code may both be reported.
Excludes2 — not included here — inherited from S30-S39
The conditions below are not part of S32.464K, but a patient may have both at the same time. When documentation supports it, S32.464K and the excluded code may both be reported.
Excludes2 — not included here — inherited from S32
The conditions below are not part of S32.464K, but a patient may have both at the same time. When documentation supports it, S32.464K and the excluded code may both be reported.
- fracture of hip NOS (S72.0-)
Code also — inherited from S32.4
Two codes may be needed to describe the condition fully. Whether S32.464K is sequenced first depends on the reason for the encounter.
- any associated fracture of pelvic ring (S32.8-)
How long has S32.464K existed?
S32.464K 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.