S62.618S — Displaced fracture of proximal phalanx of other finger, sequela
Is S62.618S billable?
Yes — S62.618S is billable for FY2027. S62.618S is a valid, billable ICD-10-CM code at the highest level of specificity in its branch. S62.618S may be submitted for encounters from October 1, 2026 through September 30, 2027.
S62.618S at a glance
| Code | S62.618S |
|---|---|
| Description | Displaced fracture of proximal phalanx of other finger, sequela |
| Billable | Yes |
| Code set | ICD-10-CM FY2027 |
| Valid for encounters | October 1, 2026 – September 30, 2027 |
| 7th character "S" | sequela |
What does the 7th character "S" mean in S62.618S?
In S62.618S, the 7th character S means sequela. The 7th character is required for S62.618S to be a valid, complete code.
Same condition, different episode of care — switch the 7th character:
- Ainitial encounter for closed fractureS62.618A
- Binitial encounter for open fractureS62.618B
- Dsubsequent encounter for fracture with routine healingS62.618D
- Gsubsequent encounter for fracture with delayed healingS62.618G
- Ksubsequent encounter for fracture with nonunionS62.618K
- Psubsequent encounter for fracture with malunionS62.618P
- SsequelaS62.618S
Which MS-DRGs does S62.618S group to?
S62.618S 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.618S listed in the Alphabetic Index?
The Alphabetic Index lists these routes under S62.61, the nearest indexed parent of S62.618S. Use them to find the family, then select the specific code.
- Fracture, traumatic › finger › proximal phalanx (abduction) (adduction) (separation)
- Fracture, traumatic › finger › index › proximal phalanx (abduction) (adduction) (separation)
- Fracture, traumatic › finger › little › proximal phalanx (abduction) (adduction) (separation)
- Fracture, traumatic › finger › middle › proximal phalanx (abduction) (adduction) (separation)
- Fracture, traumatic › finger › ring › proximal phalanx (abduction) (adduction) (separation)
Inclusion terms
Alternative wording in documentation that is classified to S62.618S.
- Displaced fracture of proximal phalanx of specified finger with unspecified laterality
Excludes1 — never code together — inherited from S62
The conditions below can never be reported together with S62.618S 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.618S to fully describe the condition. S62.618S 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.618S, but a patient may have both at the same time. When documentation supports it, S62.618S and the excluded code may both be reported.
Excludes2 — not included here — inherited from S60-S69
The conditions below are not part of S62.618S, but a patient may have both at the same time. When documentation supports it, S62.618S and the excluded code may both be reported.
Excludes2 — not included here — inherited from S62
The conditions below are not part of S62.618S, but a patient may have both at the same time. When documentation supports it, S62.618S 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.618S, but a patient may have both at the same time. When documentation supports it, S62.618S and the excluded code may both be reported.
- fracture of thumb (S62.5-)
How long has S62.618S existed?
S62.618S 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.