Pabau GO app

The new Pabau GO is heredownload on the App Store

Download on the App Store
Book a demo Book a demo
Diagnostic Codes

ICD-10 code S63.289D: PIP joint dislocation coding guide

Key takeaways

Key takeaways

S63.289D is a billable ICD-10-CM code for a PIP joint dislocation of an unspecified finger at a subsequent encounter

The 7th character D means the patient is back for routine care during the healing phase

When the note names the finger, swap in a specific sibling code from S63.280D to S63.288D

Claims fail most often when the coder keeps the initial-encounter A after the first active-treatment visit

Practice management software like Pabau carries the code from the clinical note to the claim without re-entry

ICD-10 code S63.289D reports a dislocated proximal interphalangeal (PIP) joint when the record never names which finger. It is billable for fiscal year 2026, and it belongs on follow-up visits only. The last character carries the weight here. D means active treatment is finished and the patient is now in the healing phase.

Keep the initial-encounter A on that second visit and the payer has an easy reason to deny. Lean on the unspecified sixth character too often, and your documentation starts to look thin in an audit.

This guide walks through the code’s structure, its specific siblings, the CPT pairings, and the checks to run before you submit.

Found our content helpful?

What S63.289D covers, at a glance

Two questions bring most coders to this page. Is the code still billable, and does the D character fit today’s visit? The table answers both, and the sections after it explain why.

Field Detail
Code S63.289D
Full description Dislocation of proximal interphalangeal joint of unspecified finger, subsequent encounter
Billable / specific Yes – billable ICD-10-CM code
Valid for HIPAA submission Yes – valid for reimbursement claims
ICD-10-CM edition 2026 (effective October 1, 2025)
7th character D = Subsequent encounter
Code category S63.2 – Subluxation and dislocation of other finger(s)
Maintaining body National Center for Health Statistics (NCHS) / Centers for Medicare and Medicaid Services (CMS)

Each character in S63.289D tells you something different

Read the code left to right and it describes the injury in six steps. Misread one position and the claim can bounce as invalid before a human ever sees it.

Position Character(s) Meaning
1st S Injury chapter (S00-T88)
2nd-3rd 63 Wrist and hand – dislocation and sprain of joints/ligaments
4th .2 Subluxation and dislocation of other finger(s), not thumb
5th 8 Dislocation of proximal interphalangeal joint
6th 9 Unspecified finger (no laterality or specific digit identified)
7th D Subsequent encounter – routine care during the healing phase

The sixth character 9 is what makes this the unspecified version, rather than a digit from 0 to 8. When the clinical note identifies the injured finger, a code in the S63.280 to S63.288 range is always preferred.

The 7th character D covers the healing phase, not the first visit

The 7th character is where follow-up claims go wrong most often. According to the CMS ICD-10 coding guidance, S63.289 accepts three of them. Each one marks a different point in the life of the injury.

7th character Code When to use
A – Initial encounter S63.289A First time the patient receives active treatment for the dislocation, such as an ED visit or the first ortho appointment
D – Subsequent encounter S63.289D Routine care during the healing phase: follow-up visits, splint checks, range-of-motion assessments, wound healing reviews
S – Sequela S63.289S Late effects that persist after the injury is considered healed, such as chronic joint instability or stiffness

How to tell an initial encounter from a subsequent one

The encounter type follows the purpose of the visit, not the specialty of the provider. Once the dislocation has been reduced and the patient returns for healing-phase care, switch to S63.289D. A physiatrist seeing that patient three weeks after reduction still uses D, even on their own first visit with them.

  • Use A when the dislocation is treated actively for the first time, including reduction, casting, or surgical repair.
  • Use D when the patient returns for healing-phase care, such as splint checks, therapy referrals, or imaging review.
  • Use S when the injury has healed but a complication remains, such as late instability or post-traumatic stiffness.

The ICD-10-CM Official Guidelines for Coding and Reporting are maintained jointly by the NCHS and CMS. They keep the D character in place for the whole healing phase, whichever provider delivers the care.

The PIP joint is the middle knuckle, and it dislocates most

The proximal interphalangeal joint sits between the proximal and middle phalanges of fingers two through five. Viewed from the side, it is the middle knuckle. It is also the finger joint that dislocates most often, in sport and at work alike.

Dorsal dislocations account for the large majority of these injuries, with the middle phalanx displacing backward, away from the palm. Volar and lateral dislocations show up less often, and they leave more complex instability behind.

S63.289D stays valid whether or not the note records the direction. Even so, the mechanism and the joint should both appear in the record.

Pro Tip

Name the mechanism in every note that supports S63.289D. Hyperextension from ball contact, a crush injury, and a fall on an outstretched hand are all worth writing down. A note that reads only ‘finger dislocation, follow-up’ gives an auditor nothing to work with, and it weakens the clinical record.

Where S63.289D sits in the ICD-10-CM hierarchy

Every level above S63.289D narrows the anatomy by one step. Reading the ladder is what tells you whether a more specific code exists for this patient. The whole S00-T88 chapter is built this way, so the habit carries over to the other ICD-10 diagnostic codes you bill.

Level Code Description
Chapter S00-T88 Injury, poisoning and certain other consequences of external causes
Block S60-S69 Injuries to the wrist, hand and fingers
Category S63 Dislocation and sprain of joints and ligaments of wrist and hand
Subcategory S63.2 Subluxation and dislocation of other finger(s)
Group S63.28 Dislocation of proximal interphalangeal joint of finger
Code (no encounter) S63.289 Dislocation of proximal interphalangeal joint of unspecified finger
Billable code S63.289D …subsequent encounter

Eight sibling codes beat S63.289D on specificity

The S63.28 series carries one code per finger, per side. Read the sixth character as a map of the hand and the swap becomes mechanical. Confirm your choice in the CDC/NCHS ICD-10-CM web tool before the claim goes out.

Grid mapping the sixth character of ICD-10 code S63.28 to finger and side
The sixth character runs right to left across each pair, so odd digits always sit on the left hand. Mapped from the ICD-10-CM 2026 tabular list.
Code Description Note
S63.280D Dislocation of PIP joint, right index finger, subsequent encounter Prefer over S63.289D when finger documented
S63.281D Dislocation of PIP joint, left index finger, subsequent encounter Prefer over S63.289D when finger documented
S63.282D Dislocation of PIP joint, right middle finger, subsequent encounter Prefer over S63.289D when finger documented
S63.283D Dislocation of PIP joint, left middle finger, subsequent encounter Prefer over S63.289D when finger documented
S63.284D Dislocation of PIP joint, right ring finger, subsequent encounter Prefer over S63.289D when finger documented
S63.285D Dislocation of PIP joint, left ring finger, subsequent encounter Prefer over S63.289D when finger documented
S63.286D Dislocation of PIP joint, right little finger, subsequent encounter Prefer over S63.289D when finger documented
S63.287D Dislocation of PIP joint, left little finger, subsequent encounter Prefer over S63.289D when finger documented
S63.288D Dislocation of PIP joint, other finger, subsequent encounter Finger is named but falls outside the four digits above
S63.289D Dislocation of PIP joint, unspecified finger, subsequent encounter Use only when specific finger is not documented
S63.289A Same as above – initial encounter First active-treatment visit
S63.299D Dislocation of distal interphalangeal joint of unspecified finger, subsequent encounter DIP joint (end knuckle), distinct from the PIP joint

Provider wording that still maps to S63.289D

Few providers write “proximal interphalangeal joint dislocation, subsequent encounter” word for word.

The phrases below all land on S63.289D when the finger is unspecified and the visit is a follow-up. Recognizing them saves a query the record does not need.

  • Dislocation of middle knuckle, unspecified finger, follow-up
  • PIP joint dislocation, unspecified digit, subsequent encounter
  • Proximal interphalangeal joint dislocation, follow-up visit
  • Finger PIP dislocation, ongoing care
  • Dislocated finger (PIP), routine healing care
  • Subluxation of proximal interphalangeal joint, unspecified finger, subsequent encounter

Subluxation and full dislocation share the same S63.28 range in ICD-10-CM. The classification does not separate partial displacement from complete displacement at this level of specificity.

The CPT codes that usually ride with S63.289D

A healing-phase visit for a PIP dislocation usually bills an office visit, sometimes with a splint or therapy on the same day.

Most of these encounters land on CPT code 99213, with the heavier visits moving up to 99214. Pairings shift by payer and by scenario, so check the AAPC CPT-to-ICD-10 crosswalk before you submit.

CPT code Description Typical use at follow-up
99213 Office or other outpatient visit, established patient, low complexity Standard follow-up visit for a healing progress check
99214 Office or other outpatient visit, established patient, moderate complexity Follow-up with a complication or extended decision-making
29130 Application of finger splint, static Splint application or replacement during the healing phase
97110 Therapeutic procedure – therapeutic exercises Range-of-motion and strengthening for PIP joint recovery
73140 Radiologic examination, finger(s), minimum 2 views Post-reduction imaging to confirm alignment during healing

Splint application and therapy on the same day as an office visit are a frequent source of edits. Many payers want modifier 25 on the visit code before they pay both lines, so read your contract first.

How an S63.289D claim moves from note to payment

Picking the code is the first step of a longer trip. Below is the route a follow-up claim takes in a US practice, and the point where it usually stalls.

  1. The provider documents the visit, naming the PIP joint, the side if it is known, and the healing status.
  2. The coder assigns S63.289D or a specific sibling code, plus the office visit and any procedure performed that day.
  3. The diagnosis code goes in box 21 of the CMS-1500, and box 24E points each service line back at it.
  4. The claim leaves as an 837P file through a clearinghouse, which scrubs it for invalid codes and missing 7th characters.
  5. The payer adjudicates and returns an 835 remittance advice, carrying either the payment or an adjustment reason code.

Step four is the cheap place to fail. A clearinghouse rejection never reaches the payer, so you can correct the 7th character and resend the same day. A denial at step five costs a rework cycle and, on older claims, a fight with the timely filing limit.

Run this check before you submit

  • Encounter type. Is this the first active treatment, or healing-phase care that calls for D?
  • Finger and side. Does the note name a digit that would support a specific sibling code instead?
  • 7th character present. S63.289 submitted without one is an invalid code and rejects on arrival.
  • Joint named. The note should say proximal interphalangeal, not just “finger joint” or “knuckle”.
  • Same-day services. Check whether a splint or therapy line needs a modifier on the office visit.
  • Code validity. Confirm the code is current for fiscal year 2026 before the claim leaves the practice.

Four mistakes that get these claims denied

  • Leaving the initial-encounter A on every visit in the healing phase.
  • Dropping the 7th character, which turns a valid code into a rejected one.
  • Coding S63.289D when the note actually names the injured finger.
  • Reaching for S63.299D, the DIP joint code, for a middle-knuckle injury.

Documentation that keeps an S63.289D claim paid

Documentation decides whether this claim survives a review. The habits below hold whether the note comes from an orthopedic surgeon, a primary care provider, or a hand therapist.

  • Name the joint: Write “proximal interphalangeal joint” or “PIP joint”, not “finger joint” or “knuckle”. Vague anatomy forces the coder to guess and creates audit risk.
  • State the encounter purpose: A line such as “follow-up for PIP joint dislocation, healing well, splint intact” supports the D character outright. “Finger pain” does not.
  • Document healing status: Record range of motion, swelling, and neurovascular status. That evidence supports both the subsequent encounter and the medical necessity of the visit.
  • Flag if the finger becomes identifiable: When a later note names the finger, move to the correct sibling code from S63.280D through S63.288D. Do not amend earlier claims without payer-specific guidance.
  • Confirm the code is current: Verify validity for fiscal year 2026 before the claim leaves the practice. A retired code rejects on arrival, whatever the note says.

When “unspecified finger” holds up, and when to query

S63.289D is clinically valid when the provider genuinely cannot identify the finger. That happens in multi-trauma cases, when the earlier treating records are unavailable, or when a patient arrives for follow-up without them. Using the unspecified code there is appropriate and compliant.

Reaching for “unspecified” because nobody asked is a different matter. AHIMA’s query guidance points coders back to the provider when the record supports specificity but stops short of stating it.

One clarification, right index or left ring, turns S63.289D into the code the payer prefers. Payers also read repeated unspecified codes as a documentation quality signal during audits.

Pro Tip

Run a monthly audit on your unspecified finger dislocation claims. If S63.289D appears more than twice in one patient record, the finger was probably identifiable in at least one note. Flag those charts for a provider query before they close.

How Pabau keeps the code attached to the claim

In most practices the diagnosis gets recorded twice. The provider writes the injury into the note. Someone then re-enters a code in the billing system days later, without that note in front of them. That second entry is where the encounter type quietly slips back to A.

Pabau, our practice management software, keeps the code with the record it came from. Whoever codes the visit picks S63.289D inside the clinical note, and the same code moves onto the claim without re-entry.

Claims then leave for the clearinghouse from the same screen through our Claim.MD integration, which supports CMS-1500 and 837P claims across thousands of US payers.

You get fewer transcription errors and a shorter path from visit to submission. The chart also still reads consistently if a payer asks for it a year later.

Our claims management software also flags codes that are no longer valid, so a retired 7th character does not travel out with the claim.

Stop copying codes between systems

Pabau embeds ICD-10 diagnosis code selection directly into your clinical notes and billing workflow. Select S63.289D at the point of care and push it straight to the claim, with no manual re-entry and no transcription errors.

Pabau clinical documentation and billing workflow

Conclusion

S63.289D is an easy code to bill correctly and an easy one to leave stale. Two decisions carry it: the encounter type and the sixth character. Settle both at the first follow-up visit and the rest of the healing phase largely codes itself.

Where the finger is documented, the sibling code is always the stronger claim. Where it genuinely is not, S63.289D holds up, as long as the note explains why.

Book a demo to see how Pabau keeps that code and the note behind it moving together, from the follow-up visit to the remittance.

Continue your research

Continue your research

The note names the finger after all? S63.252D covers an unspecified dislocation of the right middle finger at a subsequent encounter.

Still at the first active-treatment visit? S63.209A sets out the initial-encounter code for an unspecified finger subluxation.

Want this claim to pay on the first pass? Clean claim explains the fields payers reject most and how to fix them before submission.

Curious how the 837P file reaches the payer? Claim.MD clearinghouse guide walks through submission, eligibility checks, and ERA remittance handling.

Frequently asked questions

Do I need an external cause code with S63.289D?

No national ICD-10-CM rule makes external cause codes mandatory, though some payers and state programs ask for them. If you report one, give the cause code the same 7th character D for the subsequent encounter. Place of occurrence, activity and patient status codes belong on the initial encounter only, so leave them off the follow-up claim.

Should I use an aftercare Z code instead of S63.289D?

No. The ICD-10-CM guidelines tell you not to use aftercare Z codes for the aftercare of injuries. Report the injury code with the 7th character for a subsequent encounter instead, which is S63.289D here. Aftercare Z codes fit planned care such as joint replacement follow-up, not a healing dislocation.

How long can I keep billing the D character?

For as long as the patient receives routine care while the injury heals. ICD-10-CM sets no day limit and no visit cap on the 7th character. Once healing is complete and only a residual problem remains, such as chronic stiffness, switch to the sequela character S.

Does S63.289D cover a dislocated thumb?

No. Thumb dislocations sit in S63.1, a separate subcategory, because the thumb has one interphalangeal joint rather than two. S63.2 covers the other fingers. Coding a thumb injury to S63.289D misstates the anatomy and can contradict the rest of the note.

Found our content helpful?
×