ICD-10 Code S63.252D: Unspecified dislocation of right middle finger

Key takeaways

ICD-10 code S63.252D covers an unspecified dislocation of the right middle finger at a follow-up encounter, not the first visit.

The code is billable and valid for FY2026, effective October 1, 2025, so it can be submitted on its own.

Use A at the first encounter, D during healing and recovery, and S only for a documented late effect.

A supportable claim needs laterality, the digit named, the encounter type, and the dislocation as the reason for the visit.

Practice management software like Pabau carries the code from the clinical note into the claim, so nobody re-keys it.

ICD-10 code S63.252D is a billable ICD-10-CM diagnosis code for an unspecified dislocation of the right middle finger, subsequent encounter. It applies once the dislocation has already been treated and the patient returns for follow-up care. Reaching for it at the first encounter, or using S63.252A at a follow-up visit, triggers payer edits.

This reference covers the billable status, code structure, documentation requirements, and sequencing rules for ICD-10 code S63.252D. According to CMS ICD-10-CM guidance, the FY2026 edition took effect October 1, 2025. This page reflects that edition.

What ICD-10 code S63.252D covers

S63.252D is a billable ICD-10-CM diagnosis code. Its official long description is: Unspecified dislocation of right middle finger, subsequent encounter.

Use it when a patient returns for ongoing care of a right middle finger dislocation. The word “unspecified” refers to the joint, not to laterality. Nobody named the proximal interphalangeal, distal interphalangeal, or metacarpophalangeal joint in the original record.

Coders working with sports medicine practice software meet this code often. Athletes come back for physical therapy or a follow-up x-ray after an emergency or urgent care visit.

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

Knowing where S63.252D sits in the ICD-10-CM classification confirms you have picked the most specific code available. That check also reduces audit exposure. Neighboring codes in the same subcategory, such as S63.295D, follow the same five-level structure.

How the seventh character changes the code

The seventh character is where most S63.252 coding errors happen. ICD-10-CM assigns three seventh-character values to injury codes in the S00-T88 chapter. Each one marks a distinct phase of care, and picking the wrong one is the most common reason these claims are denied.

Match the seventh character to the patient’s clinical status, not to the number of visits they have had. The same rule governs finger fracture codes such as S62.630K.

• A (Initial encounter): The patient is receiving active treatment for the dislocation for the first time. This covers the emergency department visit, urgent care, or a first orthopedic appointment. Use S63.252A.
• D (Subsequent encounter): The patient has already had active treatment and is now healing. Follow-up x-rays, physical therapy check-ins, casting management, and post-reduction visits all sit here. Use S63.252D.
• S (Sequela): A late effect of the original dislocation, such as chronic joint instability or persistent ligament laxity. It is documented months after the acute injury has resolved. Use S63.252S.

S63.252A, S63.252D, and S63.252S: Choosing the right encounter type

The clinical question is simple. Has the patient already received active treatment for this dislocation? If they have, and they are back for follow-up care, S63.252D applies. The table below sets out the decision logic and a typical scenario for each variant.

Documentation requirements for a subsequent encounter claim

A claim using S63.252D is only supportable when the medical record carries four specific elements. Miss any one of them and payers have grounds to request records or downcode the claim. Practices using digital intake forms can pre-populate these fields.

• Laterality confirmed as right: The documentation must state “right” explicitly. “Right middle finger dislocation” satisfies this, but “middle finger dislocation” alone does not.
• The middle finger named: The third digit has to be identified. A generic reference to “finger dislocation” fails the specificity requirement.
• Encounter type as subsequent: The record must make clear this is follow-up care. Phrases such as “returns for post-reduction check” or “follow-up from prior treatment” meet the requirement.
• Dislocation as the primary condition: The note must establish the dislocation as the reason for the encounter. A note focused on a different complaint, with a passing mention of the finger, will not support S63.252D as the principal code.

Clinical documentation tools inside an EHR can structure progress notes so laterality and encounter type are captured at every visit. Practices treating hand injuries should build note templates that force a coder to confirm digit and encounter phase before the record is finalized.

Adjacent and related finger dislocation codes

Coders working with S63.252D often cross-reference nearby hand injury codes to confirm they have the most precise option. Ligament injuries carry their own entries, such as S63.491A. The table below shows the sibling codes inside S63.25 for subsequent encounters, plus related codes in the wider S63.2 block.

Check the AAPC ICD-10-CM code list when the documented digit is not the middle finger.

Coding guidelines and sequencing rules

The ICD-10-CM Official Guidelines for Coding and Reporting set the authoritative rules for S63.252D. CDC/NCHS and CMS maintain them jointly. Any billing platform an orthopedic or rehab practice runs should enforce the sequencing logic below.

• Principal diagnosis selection: Code S63.252D first when the dislocation is the primary reason for the encounter. If the visit also addresses a separate rotator cuff problem, sequence by whichever condition consumed the most resources.
• External cause coding: The guidelines recommend, though do not always require, an external cause code from Chapter 20 to describe how the injury happened. For a sports-related finger dislocation, look at W50-W64 for exposure to animate mechanical forces, or Y93 for activity codes.
• No Excludes1 conflicts: Check the S63 category-level notes. S63 carries no Excludes1 restriction that would block S63.252D from being reported alongside most upper-extremity codes.
• Seventh-character consistency: Once active treatment ends, every code for that injury episode should use the D suffix. Do not revert to A at a later visit, even when a new clinician is seeing the patient for the first time.

How Pabau supports coding for hand and finger injuries

For practices treating hand and finger injuries, revenue leaks between code selection and clean claim submission. Practice management software like Pabau closes that distance. Its claims management software connects code entry straight to the billing queue, so S63.252D reaches the claim without re-entry.

Pabau Scribe, our AI scribe, structures progress notes so the four elements a S63.252D claim needs are captured at the point of care. Those elements are laterality, digit specificity, encounter type, and the dislocation as the primary complaint.

The system flags an incomplete note before it reaches billing. That cuts the back-and-forth between clinical and billing teams, which is common in busy orthopedic and physical therapy EHR software settings.

For groups running several providers and locations, Pabau’s practice management software centralizes coding rules and payer requirements. Billing staff then apply the same seventh-character logic across every provider’s notes, without relying on memory.

Streamline ICD-10 coding and claim submission

Pabau’s claims tools help practices document musculoskeletal injuries, assign ICD-10 codes accurately, and submit clean claims. That means fewer denials and less rework for your billing team.

Book a demo

Conclusion

S63.252D is an easy code to assign and an easy one to lose on appeal. What decides the outcome is the note behind it, written weeks earlier by a clinician who was not thinking about billing.

Fix the note template once and the coding looks after itself. If laterality, the digit, and the encounter phase are required fields, a coder never has to guess which seventh character the visit earned.

Book a demo to see how Pabau ties clinical notes to clean claims for hand and finger injuries.

Continue your research

Documenting a sprain that never fully settled? S63.615S explains how the sequela suffix works for a finger sprain.

Need cleaner clinical notes across the team? Safer clinical notes covers the documentation habits that cut coding errors and support audit readiness.

Managing billing for rehab patients? Physiotherapy clinic management software looks at how integrated tools handle ICD-10 workflows in rehab settings.

Frequently asked questions