ICD-10 code S62.163P: Displaced pisiform fracture, malunion

Key takeaways

ICD-10 code S62.163P describes a displaced pisiform fracture at a follow-up encounter, where imaging confirms the bone healed out of alignment.

The code is billable and valid for FY2026, which runs from October 1, 2025 through September 30, 2026.

The ‘P’ 7th character means malunion. It separates this code from ‘D’ for routine healing, ‘G’ for delayed healing, and ‘K’ for nonunion.

Subsequent encounter codes such as S62.163P are exempt from Present on Admission reporting.

Practice management software like Pabau keeps the chart and the claim code aligned at every follow-up visit.

ICD-10 code S62.163P is a billable diagnosis code for a displaced fracture of the pisiform, unspecified wrist. It applies at a subsequent encounter where imaging confirms the fracture healed with malunion. Practices running claims management software that tracks encounter-specific codes can catch a wrong 7th character before submission.

The code sits in ICD-10-CM category S62, which covers fractures at wrist and hand level. S62.163P took effect October 1, 2025 and stays valid through September 30, 2026. Those dates come from the FY2026 guidelines published by the Centers for Medicare and Medicaid Services (CMS). The code is valid for submission in all HIPAA-covered transactions.

Code details and validity for FY2026

Before submitting a claim with S62.163P, billing staff should confirm the attributes in the table below. Each one affects whether the claim passes payer edits cleanly. Staff at HIPAA-compliant medical offices should recheck fiscal year validity every fall, since CMS updates the ICD-10-CM tabular list each October.

What is the pisiform and why does it fracture?

The pisiform is the smallest of the eight carpal bones. It sits on the medial side of the wrist, inside the flexor carpi ulnaris tendon.

Because the bone sits superficially at the hypothenar eminence, direct trauma reaches it easily. A fall onto an outstretched hand or a blow to the ulnar wrist is the usual cause. Clinicians in sports medicine practices see these fractures most often in contact sport athletes and manual laborers.

Displaced fractures happen when the fragments shift out of anatomical alignment. That distinction drives the coding, because the S62.163x family captures displaced fractures only. Non-displaced pisiform fractures carry their own codes.

• Common injury mechanisms: A fall onto an outstretched hand, direct impact to the ulnar palm, or repetitive microtrauma.
• Presenting symptoms: Tenderness over the pisiform, pain on resisted wrist flexion, and grip weakness.
• Imaging confirmation: A standard wrist X-ray often misses the fracture, so a carpal tunnel view or CT is usually needed.

Carpal fractures are easy to mistake for one another on a plain film. A scaphoid fracture test at the bedside helps rule out the neighboring bone before further imaging is ordered.

When the patient returns and imaging shows the bone healed out of position, the picture shifts from acute management to malunion. The code shifts with it, from an initial or routine healing suffix to S62.163P.

How the 7th character ‘P’ differs from D, G, and K

The 7th character is the most important differentiator within the S62.163x family. Picking the wrong suffix is one of the most common reasons fracture claims are denied or flagged for audit. Coders handling post-fracture rehabilitation visits need to know what each suffix represents before they assign one.

P vs K: Malunion means the bone healed, but in a poor position. Nonunion means the bone never healed at all. The two findings are distinct, clinically and radiologically. Coding K when imaging shows malunion puts the wrong story in the record and invites payer queries.

The same suffix logic runs across the forearm codes. S52.356R covers an open radius shaft fracture that healed malunited. S52.266R applies to a nondisplaced ulna fracture with the same complication.

P vs S: The S suffix covers the late effects of a fracture that has fully resolved. Chronic wrist pain after complete healing is the typical example. Sequela coding also needs a second code for the nature of that late effect.

P denotes an active complication of the healing process itself. S52.591S shows how the sequela suffix works on the distal radius, where the same distinction applies.

Where the code sits in the ICD-10-CM hierarchy

Knowing where S62.163P sits in the ICD-10-CM tree makes related codes easier to find. The parent chain runs from the broadest injury range down to the specific encounter variant. The CDC ICD-10-CM web tool lets coders browse that tree by chapter and confirm validity for the current fiscal year.

• S00-T88: Injury, poisoning and certain other consequences of external causes
• S60-S69: Injuries to the wrist and hand
• S62: Fracture at wrist and hand level
• S62.1: Fracture of carpal bone(s) other than the scaphoid
• S62.16: Fracture of pisiform
• S62.163: Displaced fracture of pisiform, unspecified wrist
• S62.163P: Displaced fracture of pisiform, unspecified wrist, subsequent encounter for fracture with malunion

Laterality specificity sits one level up. S62.161x covers the right wrist and S62.162x covers the left. The same principle holds across musculoskeletal coding. Use the most specific code the documentation supports, and move off “unspecified” as soon as laterality is recorded.

Documentation requirements for S62.163P

Missing one documentation element can turn into a denial or a request for records. Practices using structured clinical documentation can build encounter-specific note templates that prompt for each element before the note closes.

To support S62.163P, the clinical record has to confirm all of the following:

1. Displaced fracture confirmed: The record describes the fracture as displaced. If the notes or the imaging report describe non-displaced alignment, S62.163P does not apply.
2. Pisiform bone identified: The fracture has to be at the pisiform specifically. A chart that says only “carpal fracture” does not support this code.
3. Malunion confirmed on imaging: The ‘P’ suffix needs imaging evidence, usually a follow-up X-ray or CT showing the bone healed out of alignment. A clinical note on its own is not enough, so reference the imaging report.
4. Subsequent encounter status: The patient is in the follow-up phase, not under active treatment for the acute fracture. Active surgical treatment at this visit usually reverts the encounter to an ‘A’ suffix.
5. Unspecified wrist documented: If the notes name the right or left wrist, use S62.161P or S62.162P instead. “Unspecified” applies only when the documentation genuinely does not record laterality.

Coders in occupational therapy practices and hand clinics should flag encounters where laterality is missing and query the physician before submission. Defaulting to the unspecified code is the wrong reflex. Specificity is a core principle of ICD-10-CM, as AAPC code references set out.

ICD-9-CM crosswalk for legacy claims

Legacy billing systems, audit reviews, and research datasets often need a map between ICD-10-CM codes and their ICD-9-CM predecessors. The mapping below is approximate rather than exact. ResDAC guidance treats ICD-9 crosswalks as non-exact equivalents for research and audit work.

S62.163P has no exact ICD-9-CM counterpart. ICD-9 could not express displacement, the specific carpal bone, laterality, encounter type, and healing complication in one code. Auditors reviewing historical claims should carry that limitation into their findings.

How Pabau supports fracture coding accuracy

Encounter-type errors and thin documentation cost practices money on fracture codes, where the 7th character decides whether a claim clears. Accurate coding for S62.163P depends on the record capturing displacement status, the carpal bone involved, imaging-confirmed malunion, and the encounter type.

Without a structured template, the coder ends up chasing the physician afterwards for laterality or an imaging reference. Pabau lets orthopedic and musculoskeletal practices build laterality prompts, encounter-type checkboxes, and imaging reference fields into the note itself.

Digital intake and encounter forms collect the same detail from the patient before the visit starts. The result is a chart that already says what the 7th character claims. The claim goes out first time and holds up under audit.

Code every fracture follow-up with confidence

Pabau's clinical records and claims tools keep laterality, imaging, and encounter type on the same chart. Your coders stop chasing physicians for the detail a 7th character needs.

Book a demo

Conclusion

The judgment that matters with S62.163P is timing. The suffix has to change the moment follow-up imaging shows the bone healed out of alignment. Coders who wait for the physician to write the word “malunion” will keep submitting D.

That makes it a documentation problem before it is a coding problem. Fix the note template and the code follows. Leave the template alone and no amount of coder diligence will keep the S62.163x family accurate.

Book a demo to see how Pabau keeps imaging, laterality, and encounter type on the chart before your coder needs them.

Continue your research

Working out sequela versus subsequent encounter? S63.004S shows how the sequela suffix applies after a wrist dislocation has resolved.

Coding a forearm fracture at first presentation? S52.271A covers the initial encounter rules for a Monteggia fracture of the right ulna.

Billing the surgical side of fracture care? 20693 explains external fixation adjustment billing and the modifiers that go with it.

Assessing nerve involvement after a wrist injury? Two-point discrimination test covers the procedure, normal values, and how to read the result.

Coding a flexor tendon injury? S56.114S handles the sequela of a flexor tendon strain in the index finger.

Frequently asked questions