ICDcodes.org
FY2027

S52.009EUnspecified fracture of upper end of unspecified ulna, subsequent encounter for open fracture type I or II with routine healing

BillableUnspecified

Is S52.009E billable?

Yes, but S52.009E is an unspecified code. S52.009E is a valid, billable ICD-10-CM code for encounters from October 1, 2026 through September 30, 2027. However, S52.009E is an unspecified or catch-all code. Payers apply additional scrutiny to unspecified codes and many deny them when the medical record supports a more specific option, so check the documentation before selecting S52.009E — the more specific alternatives are listed below.

S52.009E at a glance

CodeS52.009E
DescriptionUnspecified fracture of upper end of unspecified ulna, subsequent encounter for open fracture type I or II with routine healing
BillableYes
Code setICD-10-CM FY2027
Valid for encountersOctober 1, 2026 – September 30, 2027
7th character "E"subsequent encounter for open fracture type I or II with routine healing

What does the 7th character "E" mean in S52.009E?

In S52.009E, the 7th character E means subsequent encounter for open fracture type I or II with routine healing. The 7th character is required for S52.009E to be a valid, complete code.

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

Which MS-DRGs does S52.009E group to?

S52.009E 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 S52.009E listed in the Alphabetic Index?

The Alphabetic Index lists these routes under S52.00, the nearest indexed parent of S52.009E. Use them to find the family, then select the specific code.

  • Fracture, traumaticulnaupper end (abduction) (adduction) (separation)

Excludes1 — never code together — inherited from S52

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

  • traumatic amputation of forearm (S58.-)

Use additional code — inherited from Chapter 19

Report an additional code alongside S52.009E to fully describe the condition. S52.009E 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 S52.009E, but a patient may have both at the same time. When documentation supports it, S52.009E and the excluded code may both be reported.

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

Excludes2 — not included here — inherited from S50-S59

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

  • burns and corrosions (T20-T32)
  • frostbite (T33-T34)
  • injuries of wrist and hand (S60-S69)
  • insect bite or sting, venomous (T63.4)

Excludes2 — not included here — inherited from S52

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

  • fracture at wrist and hand level (S62.-)
  • periprosthetic fracture around internal prosthetic elbow joint (M97.4)

Excludes2 — not included here — inherited from S52.0

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

  • fracture of elbow NOS (S42.40-)
  • fractures of shaft of ulna (S52.2-)

How long has S52.009E existed?

S52.009E 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.