S63.639D — Sprain of interphalangeal joint of unspecified finger, subsequent encounter
Is S63.639D billable?
Yes, but S63.639D is an unspecified code. S63.639D is a valid, billable ICD-10-CM code for encounters from October 1, 2026 through September 30, 2027. However, S63.639D 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 S63.639D — the more specific alternatives are listed below.
More specific alternatives
- S63.001DUnspecified subluxation of right wrist and hand, subsequent encounter
- S63.101DUnspecified subluxation of right thumb, subsequent encounter
- S63.200DUnspecified subluxation of right index finger, subsequent encounter
- S63.301DTraumatic rupture of unspecified ligament of right wrist, subsequent encounter
- S63.400DTraumatic rupture of unspecified ligament of right index finger at metacarpophalangeal and interphalangeal joint, subsequent encounter
- S63.8X1DSprain of other part of right wrist and hand, subsequent encounter
S63.639D at a glance
| Code | S63.639D |
|---|---|
| Description | Sprain of interphalangeal joint of unspecified finger, subsequent encounter |
| Billable | Yes |
| Code set | ICD-10-CM FY2027 |
| Valid for encounters | October 1, 2026 – September 30, 2027 |
| 7th character "D" | subsequent encounter |
What does the 7th character "D" mean in S63.639D?
In S63.639D, the 7th character D means subsequent encounter. The 7th character is required for S63.639D to be a valid, complete code.
Same condition, different episode of care — switch the 7th character:
Which MS-DRGs does S63.639D group to?
S63.639D sits in MDC 23 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.
- 949Aftercare with CC/MCCmedical
- 950Aftercare without CC/MCCmedical
How is S63.639D listed in the Alphabetic Index?
The Alphabetic Index lists these routes under S63.63, the nearest indexed parent of S63.639D. Use them to find the family, then select the specific code.
- Sprain › finger › interphalangeal (joint) (ligament)
- Sprain › finger › interphalangeal › index (joint) (ligament)
- Sprain › finger › interphalangeal › little (joint) (ligament)
- Sprain › finger › interphalangeal › middle (joint) (ligament)
- Sprain › finger › interphalangeal › ring (joint) (ligament)
Excludes1 — never code together — inherited from S63.6
The conditions below can never be reported together with S63.639D 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 rupture of ligament of finger at metacarpophalangeal and interphalangeal joint(s) (S63.4-)
Use additional code — inherited from Chapter 19
Report an additional code alongside S63.639D to fully describe the condition. S63.639D 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 S63.639D, but a patient may have both at the same time. When documentation supports it, S63.639D and the excluded code may both be reported.
Excludes2 — not included here — inherited from S60-S69
The conditions below are not part of S63.639D, but a patient may have both at the same time. When documentation supports it, S63.639D and the excluded code may both be reported.
Excludes2 — not included here — inherited from S63
The conditions below are not part of S63.639D, but a patient may have both at the same time. When documentation supports it, S63.639D and the excluded code may both be reported.
- strain of muscle, fascia and tendon of wrist and hand (S66.-)
Code also — inherited from S63
Two codes may be needed to describe the condition fully. Whether S63.639D is sequenced first depends on the reason for the encounter.
- any associated open wound
How long has S63.639D existed?
S63.639D 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.