ICDcodes.org
FY2027

S32.89XKFracture of other parts of pelvis, subsequent encounter for fracture with nonunion

BillableCC

Is S32.89XK billable?

Yes — S32.89XK is billable for FY2027. S32.89XK is a valid, billable ICD-10-CM code at the highest level of specificity in its branch. S32.89XK may be submitted for encounters from October 1, 2026 through September 30, 2027.

S32.89XK at a glance

CodeS32.89XK
DescriptionFracture of other parts of pelvis, subsequent encounter for fracture with nonunion
BillableYes
Code setICD-10-CM FY2027
Valid for encountersOctober 1, 2026 – September 30, 2027
7th character "K"subsequent encounter for fracture with nonunion

What does the 7th character "K" mean in S32.89XK?

In S32.89XK, the 7th character K means subsequent encounter for fracture with nonunion. The 7th character is required for S32.89XK to be a valid, complete code.

Same condition, different episode of care — switch the 7th character:

Which MS-DRGs does S32.89XK group to?

S32.89XK sits in MDC 08 and helps define the logic of 3 MS-DRGs (version 44, FY2027). Which one a stay actually groups to also depends on procedures and secondary diagnoses.

  • 564Other Musculoskeletal System and Connective Tissue Diagnoses with MCCmedical
  • 565Other Musculoskeletal System and Connective Tissue Diagnoses with CCmedical
  • 566Other Musculoskeletal System and Connective Tissue Diagnoses without CC/MCCmedical

As a secondary diagnosis, S32.89XK is a complication or comorbidity (CC), which can move a stay into a higher-paying DRG.

How is S32.89XK listed in the Alphabetic Index?

The Alphabetic Index lists these routes under S32.89, the nearest indexed parent of S32.89XK. Use them to find the family, then select the specific code.

  • Fracture, traumaticpelvis, pelvicspecified site NEC (abduction) (adduction) (separation)

Excludes1 — never code together — inherited from S32

The conditions below can never be reported together with S32.89XK 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.89XK. S32.89XK 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.89XK to fully describe the condition. S32.89XK 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.89XK, but a patient may have both at the same time. When documentation supports it, S32.89XK and the excluded code may both be reported.

  • birth trauma (P10-P15)
  • obstetric trauma (O70-O71)

Excludes2 — not included here — inherited from S30-S39

The conditions below are not part of S32.89XK, but a patient may have both at the same time. When documentation supports it, S32.89XK and the excluded code may both be reported.

  • burns and corrosions (T20-T32)
  • effects of foreign body in anus and rectum (T18.5)
  • effects of foreign body in genitourinary tract (T19.-)
  • effects of foreign body in stomach, small intestine and colon (T18.2-T18.4)
  • frostbite (T33-T34)
  • insect bite or sting, venomous (T63.4)

Excludes2 — not included here — inherited from S32

The conditions below are not part of S32.89XK, but a patient may have both at the same time. When documentation supports it, S32.89XK and the excluded code may both be reported.

Code also — inherited from S32.8

Two codes may be needed to describe the condition fully. Whether S32.89XK is sequenced first depends on the reason for the encounter.

  • any associated:
  • fracture of acetabulum (S32.4-)
  • sacral fracture (S32.1-)

How long has S32.89XK existed?

S32.89XK 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.