ICD-10 code S62.032S: Displaced scaphoid fracture left wrist sequela

Key takeaways

ICD-10 code S62.032S is a billable code for a displaced fracture of the proximal third of the scaphoid bone in the left wrist, sequela.

It took effect on October 1, 2025, as part of the 2026 ICD-10-CM edition, and it is valid on HIPAA-covered claims.

The 7th character S means the patient has a late effect of the old fracture, not a fracture that is still healing.

Mixing up sequela (S) with subsequent encounter (D) is the most common error in this code family, and it triggers denials.

Practice management software like Pabau helps orthopedic teams record laterality, displacement, and encounter type before the claim goes out.

ICD-10 code S62.032S covers a displaced fracture of the proximal third of the navicular (scaphoid) bone of the left wrist, sequela. It is a billable, specific ICD-10-CM code, and it entered the 2026 edition on October 1, 2025. Coders can report it on HIPAA-covered claim transactions.

Coders in sports medicine practices and orthopedic offices reach for this code when a patient returns months or years after a scaphoid fracture. The complaint has to be a direct consequence of that original injury. The code does not fit an encounter where the fracture itself is still being managed.

Understanding the 7th character: Sequela (S)

The 7th character is the most consequential element of this code. It tells the payer whether the patient is at an initial encounter, a subsequent encounter, or a sequela encounter. Getting it wrong is the top reason S62-family claims get flagged in an audit.

Per the CMS ICD-10-CM guidelines, Section I.C.19, the sequela character applies only once the fracture has finished its active healing phase. When you report a sequela code, add a second code that names the condition itself. Post-traumatic arthritis of the wrist and avascular necrosis of the scaphoid are the two you will see most.

The healing-phase characters follow the same logic across the whole S62 chapter. A code such as S62.606K marks a fracture that has failed to unite. That is still active management, so it is not a sequela.

S62.032S in the ICD-10-CM code hierarchy

Knowing where S62.032S sits in the ICD-10-CM structure helps you verify specificity and avoid dropping to a parent code. The CDC ICD-10-CM tool lets you browse the hierarchy by fiscal year.

• S00-T88: Injury, poisoning and certain other consequences of external causes
• S60-S69: Injuries to the wrist, hand, and fingers
• S62: Fracture at wrist and hand level
• S62.0: Fracture of navicular [scaphoid] bone of wrist
• S62.03: Fracture of proximal third of navicular [scaphoid] bone of wrist
• S62.032: Displaced fracture of proximal third of navicular [scaphoid] bone of left wrist
• S62.032S: Displaced fracture of proximal third of navicular [scaphoid] bone of left wrist, sequela

Never stop at S62.0 or S62.03 for a final claim. Those are parent codes, not billable codes. Only the fully specified 7th-character code is valid for submission. Non-specific parent codes are a common rejection trigger in physical therapy practices and orthopedic offices alike.

Anatomy: Displaced fracture of the proximal third of the scaphoid

The scaphoid, also called the navicular bone, is the most commonly fractured carpal bone in the wrist. The anatomy behind the code matters at documentation time. Unless the clinical record names the sub-site, nothing on the chart justifies S62.032S over a sibling or parent code.

The three anatomical thirds of the scaphoid

ICD-10-CM splits scaphoid fractures across three sub-sites: the distal third, the middle third (waist), and the proximal third. The proximal third sits closest to the radius, and it carries the heaviest consequences for healing.

Blood reaches the proximal pole by a retrograde route, entering at the distal end and travelling back up the bone. A fracture through the proximal third can cut that supply off. The American Society for Surgery of the Hand ties this pattern to a raised risk of avascular necrosis.

The phrase “proximal third” has to be explicit in the documentation. An operative report or imaging read that says “proximal pole” or “proximal segment” maps to the same sub-site. “Waist” or “middle third” routes instead to S62.022, the displaced middle-third code for the left wrist. Fractures at the far end of the bone sit in the S62.01 group, where a code like S62.011A lands.

What “displaced” means for coding

A displaced fracture is one where the fragments have shifted out of normal anatomical alignment. That shift is a required element of S62.032S. If the fragments are still aligned, the correct family is S62.035x, the nondisplaced proximal third code for the left wrist.

Never infer displacement from an imaging report that avoids the word. Query the ordering clinician instead. Coding guidelines require you to code what is documented, and a default assumption is not permitted. Nondisplaced codes carry identical 7th-character rules, as S62.360G shows.

Related ICD-10-CM codes for scaphoid fractures

Picking the most specific code means knowing the rest of the scaphoid family. The table below covers the siblings, parents, and neighbors that coders most often confuse with S62.032S. Solid medical documentation practices turn that choice into a lookup rather than a judgment call.

A scaphoid fracture often arrives alongside a distal radius injury. That second injury is coded from the S52 family rather than S62, and it needs its own line on the claim. S52.356C is one of those radius codes.

When to use S62.032S instead of another encounter type

Most coding errors in this family happen right here. Sequela and subsequent encounter describe different clinical situations, and the ICD-10-CM guidelines draw a firm line between them. Of all the 7th-character choices, this is the one coders find least intuitive.

Subsequent encounter (D, G, K, P) vs. sequela (S)

• Subsequent encounter: The fracture is still healing. The patient comes back for cast changes, imaging, physical therapy, or treatment of delayed healing, nonunion, or malunion. The provider is still managing the fracture itself, as in S62.211D.
• Sequela encounter: The fracture has finished healing. The patient now has a condition caused by that old injury. After a proximal scaphoid fracture, that usually means post-traumatic wrist arthritis, avascular necrosis of the proximal pole, chronic pain, or lost grip strength.

The provider’s note usually settles it. If the note describes managing the fracture, the nonunion, or the malunion, you are in a subsequent encounter. If it names a separate condition and traces that condition back to an old fracture, you are in a sequela encounter.

The AAPC code reference applies the same D-versus-S logic across every injury chapter. The test you use on a scaphoid claim carries over to the rest of the fracture families.

Documentation requirements for S62.032S

Four documentation elements have to appear in the clinical record to support S62.032S. Miss one and a payer can downcode or deny the claim on specificity. Practices working from structured clinical records software can build all four into the standard encounter template.

• Laterality: The record has to say “left wrist.” A note that says only “wrist fracture” routes to S62.033, the unspecified-laterality code.
• Displacement status: The record has to say “displaced,” or describe the fragment shift in radiologic terms. Without that, the claim defaults to an unspecified displacement code.
• Anatomical sub-site: The record has to place the fracture in the proximal third, proximal pole, or proximal segment. “Scaphoid fracture” on its own does not support S62.032S.
• Encounter type as sequela: The record has to show the complaint is a late effect of an old fracture. A note reading “chronic wrist pain secondary to remote left scaphoid fracture” supports it. A note about ongoing fracture management does not.

When the record is incomplete at coding time, send a query to the treating clinician rather than drop to a less-specific code. A standard history and physical form captures laterality and mechanism at the first visit. High-volume fracture teams also lean on HIPAA-compliant documentation workflows that gather all four elements before the claim is built.

How Pabau supports accurate scaphoid fracture documentation

Orthopedic billing teams write off reimbursement every year to coding errors that started life as an incomplete note. When the record skips laterality, displacement, sub-site, or encounter type, the coder either guesses or sends a query. Both options slow the revenue cycle down.

Pabau’s claims management software works from the same structured clinical record your clinicians write in. The fields that support a code like S62.032S are captured before anyone opens the claim. A clinician documenting a wrist injury works through a template that prompts for laterality, displacement, sub-site, and encounter type.

Multi-provider orthopedic and sports medicine teams also use Pabau’s digital intake forms to standardize how fracture presentations get recorded. When every provider documents a wrist injury the same way, far fewer claims stall on missing specificity.

Catch coding errors before the claim is submitted

Pabau’s claims management tools capture laterality, displacement status, and encounter type inside the structured clinical record. The right code reaches the payer the first time.

Book a demo

Conclusion

S62.032S is a narrow code. It earns its place only when the wrist is left, the fracture was displaced, and the sub-site was the proximal third. The fourth condition is the one that trips people up. The encounter has to be about a late effect, not a fracture still under treatment.

So the practical move sits upstream of the coder. Fix the note template and the code selects itself, because all four elements are already in the record when the coder opens it. Leave it to the claim stage and you are querying clinicians weeks after the visit.

That trade-off is worth remembering the next time an S62 denial lands on your desk. Book a demo to see how Pabau captures laterality, displacement, and encounter type at the point of care.

Continue your research

Coding a radius fracture alongside the wrist injury? S52.356C walks through the open fracture characters and the documentation each one needs.

Need a note format that captures all four specificity elements? Clinical progress notes template gives your coders a structured record to work from.

Handling a shoulder injury on the same patient? S43.111A covers laterality and encounter type for acromioclavicular joint subluxation.

Documenting a hand wound at a follow-up visit? S61.441D shows how the subsequent-encounter character works outside the fracture chapters.

Frequently asked questions