ICDcodes.org
FY2027

S32.311DDisplaced avulsion fracture of right ilium, subsequent encounter for fracture with routine healing

Billable

Is S32.311D billable?

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

S32.311D at a glance

CodeS32.311D
DescriptionDisplaced avulsion fracture of right ilium, subsequent encounter for fracture with routine healing
BillableYes
Code setICD-10-CM FY2027
Valid for encountersOctober 1, 2026 – September 30, 2027
7th character "D"subsequent encounter for fracture with routine healing

What does the 7th character "D" mean in S32.311D?

In S32.311D, the 7th character D means subsequent encounter for fracture with routine healing. The 7th character is required for S32.311D to be a valid, complete code.

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

Which MS-DRGs does S32.311D group to?

S32.311D 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.

  • 559Aftercare, Musculoskeletal System and Connective Tissue with MCCmedical
  • 560Aftercare, Musculoskeletal System and Connective Tissue with CCmedical
  • 561Aftercare, Musculoskeletal System and Connective Tissue without CC/MCCmedical

How is S32.311D listed in the Alphabetic Index?

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

  • Fracture, traumaticiliumavulsion (abduction) (adduction) (separation)
  • Fracture, traumaticiliumavulsionnondisplaced (abduction) (adduction) (separation)

Excludes1 — never code together — inherited from S32

The conditions below can never be reported together with S32.311D 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)

Excludes1 — never code together — inherited from S32.3

The conditions below can never be reported together with S32.311D on the same claim. An Excludes1 note means the two conditions cannot occur in the same patient, so reporting both is a coding error.

  • fracture of ilium with associated disruption of pelvic ring (S32.8-)

Code first — inherited from S32

The underlying condition below must be sequenced before S32.311D. S32.311D 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.311D to fully describe the condition. S32.311D 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.311D, but a patient may have both at the same time. When documentation supports it, S32.311D 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.311D, but a patient may have both at the same time. When documentation supports it, S32.311D 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.311D, but a patient may have both at the same time. When documentation supports it, S32.311D and the excluded code may both be reported.

How long has S32.311D existed?

S32.311D 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.