ICDcodes.org
FY2027

S32.612ADisplaced avulsion fracture of left ischium, initial encounter for closed fracture

BillableCC

Is S32.612A billable?

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

S32.612A at a glance

CodeS32.612A
DescriptionDisplaced avulsion fracture of left ischium, initial encounter for closed fracture
BillableYes
Code setICD-10-CM FY2027
Valid for encountersOctober 1, 2026 – September 30, 2027
7th character "A"initial encounter for closed fracture

What does the 7th character "A" mean in S32.612A?

In S32.612A, the 7th character A means initial encounter for closed fracture. The 7th character is required for S32.612A to be a valid, complete code.

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

Which MS-DRGs does S32.612A group to?

S32.612A 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.

  • 535Fractures of Hip and Pelvis with MCCmedical
  • 536Fractures of Hip and Pelvis without MCCmedical

As a secondary diagnosis, S32.612A is a complication or comorbidity (CC), which can move a stay into a higher-paying DRG. It also carries Hospital-Acquired Condition category 05.

How is S32.612A listed in the Alphabetic Index?

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

  • Fracture, traumaticischiumavulsion (abduction) (adduction) (separation)
  • Fracture, traumaticischiumavulsionnondisplaced (abduction) (adduction) (separation)

Excludes1 — never code together — inherited from S32

The conditions below can never be reported together with S32.612A 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.6

The conditions below can never be reported together with S32.612A 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 ischium with associated disruption of pelvic ring (S32.8-)

Code first — inherited from S32

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

How long has S32.612A existed?

S32.612A 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.