ICDcodes.org
FY2027

S62.606GFracture of unspecified phalanx of right little finger, subsequent encounter for fracture with delayed healing

BillableUnspecified

Is S62.606G billable?

Yes, but S62.606G is an unspecified code. S62.606G is a valid, billable ICD-10-CM code for encounters from October 1, 2026 through September 30, 2027. However, S62.606G 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 S62.606G — the more specific alternatives are listed below.

S62.606G at a glance

CodeS62.606G
DescriptionFracture of unspecified phalanx of right little finger, subsequent encounter for fracture with delayed healing
BillableYes
Code setICD-10-CM FY2027
Valid for encountersOctober 1, 2026 – September 30, 2027
7th character "G"subsequent encounter for fracture with delayed healing

What does the 7th character "G" mean in S62.606G?

In S62.606G, the 7th character G means subsequent encounter for fracture with delayed healing. The 7th character is required for S62.606G to be a valid, complete code.

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

Which MS-DRGs does S62.606G group to?

S62.606G 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 S62.606G listed in the Alphabetic Index?

The Alphabetic Index lists these routes under S62.60, the nearest indexed parent of S62.606G. Use them to find the family, then select the specific code.

  • Fracture, traumaticfinger (abduction) (adduction) (separation)
  • Fracture, traumaticfingerindex (abduction) (adduction) (separation)
  • Fracture, traumaticfingerlittle (abduction) (adduction) (separation)
  • Fracture, traumaticfingermiddle (abduction) (adduction) (separation)
  • Fracture, traumaticfingerring (abduction) (adduction) (separation)

Excludes1 — never code together — inherited from S62

The conditions below can never be reported together with S62.606G 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 wrist and hand (S68.-)

Use additional code — inherited from Chapter 19

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

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

Excludes2 — not included here — inherited from S60-S69

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

  • burns and corrosions (T20-T32)
  • frostbite (T33-T34)
  • insect bite or sting, venomous (T63.4)

Excludes2 — not included here — inherited from S62

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

  • fracture of distal parts of ulna and radius (S52.-)

Excludes2 — not included here — inherited from S62.6

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

How long has S62.606G existed?

S62.606G 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.