ICD-10 code S62.211D: Bennett’s fracture, subsequent encounter

Key takeaways

S62.211D is a billable ICD-10-CM code for Bennett’s fracture of the right hand at a follow-up visit with routine healing.

The 7th character is mandatory for billing, so S62.211 submitted on its own comes back as an invalid code.

S62.211 accepts seven 7th characters: A, B, D, G, K, P and S. Each one names an encounter type or a healing outcome.

Routine healing (D) is only correct when the note says healing is progressing normally, so healing status has to be documented at every visit.

Practice management software like Pabau links diagnosis codes to CPT codes inside the billing workflow, so fewer coding errors reach the payer.

S62.211D is a billable and valid ICD-10-CM diagnosis code. Its full official description is: Bennett’s fracture, right hand, subsequent encounter for fracture with routine healing. Every element of that description carries coding significance.

A key point for billing staff: S62.211 on its own is not a billable code. Payers need the 7th character to identify the encounter type before they will process a claim. Submitting S62.211 without a suffix returns a code-invalid error on the remittance.

Practices using integrated claims management software can flag incomplete codes before submission. That catches a missing 7th character at the scrubbing stage instead of after a rejection.

What is Bennett’s fracture?

Bennett’s fracture is an intra-articular fracture-dislocation at the base of the first metacarpal, the thumb metacarpal. Because the fracture line runs into the carpometacarpal (CMC) joint surface, it is more complex than a simple metacarpal shaft fracture. The usual mechanism is axial loading on a partially flexed thumb.

That happens most often in falls, contact sports, and motor vehicle incidents. The anterior oblique ligament holds the proximal fragment in place, while the abductor pollicis longus pulls the shaft radially and proximally. This displacement is why most Bennett’s fractures need reduction, and often surgical fixation.

For sports medicine practices managing post-surgical rehabilitation, accurate coding of every follow-up encounter is what keeps reimbursement clean. Three clinical features drive code selection here:

• The fracture sits at the first metacarpal base, not in the shaft
• It is intra-articular, extending into the CMC joint
• Laterality is specified as right or left hand

For subsequent encounter coding, the clinician has to document one more thing: The healing status at that visit.

What the 7th character ‘D’ means

The 7th character is the most consequential part of this code for billing. Section I.C.19 of the ICD-10-CM Official Guidelines for Coding and Reporting sets the 7th character extensions for traumatic fractures. Each one names the encounter type and, for follow-up visits, the healing outcome.

Seven characters are billable under S62.211, not four. A and B split the initial encounter by closed and open fracture. D, G, K and P then describe what happened to the bone afterwards.

The choice between D and G is a clinical determination, not a coder’s call. The treating provider assesses and documents healing status at each visit. A coder who picks G from the length of treatment alone, with no note documenting delayed healing, risks an audit flag. When the note says healing is proceeding normally, use D. The same rule governs S62.360G and every other delayed-healing code in this category.

K and P describe outcomes rather than timing. Use K once imaging confirms the fracture has not united, however long the patient has been in follow-up. Use P when it united in a poor position, which at the thumb base often shows up as stiffness or a weak pinch grip. Nonunion coding works the same way across the S62 category, as it does for S62.606K.

The CDC ICD-10-CM web tool publishes the official tabular list and index for each fiscal year. It carries the complete 7th character table for the S62 category. Verify code validity and effective dates there before you submit a claim.

S62.211D vs. S62.211A vs. S62.211S: Choosing the right encounter type

Misapplying the encounter suffix is one of the most common fracture coding errors. Here is a side-by-side view of the three suffixes coders reach for most often, with the scenario that fits each one.

A practical rule: The 7th character switches from A to D once the provider’s note moves from managing the acute fracture to monitoring healing progress. For a surgically treated Bennett’s fracture, that is usually the first post-operative visit. Initial-encounter coding on a neighboring wrist injury follows the same logic, as it does for S62.011A.

Coding teams at occupational therapy practices see S62.211D often, because patients arrive for hand therapy during the routine healing phase. The referring diagnosis on the therapy order supports the same D suffix on those visits.

Laterality variants: Right hand, left hand, and unspecified

ICD-10-CM requires laterality for fractures of the hand and wrist. Bennett’s fracture has three laterality options under S62.21. A code that leaves laterality out, when the note names the right or left hand, may be flagged as insufficiently specific.

Use S62.213D only when the documentation genuinely fails to name the hand. If the operative report, imaging order, or exam note identifies right or left, the laterality-specific code is required. For most Bennett’s fracture cases, the surgical record makes that clear.

Bilateral injuries need a separate claim for each hand, each with its own laterality code. A single unspecified code for a documented bilateral injury misstates the encounter. Good client record management settles this at the source. When the record captures laterality during documentation, the coder never has to guess.

Where S62.211D sits in the code hierarchy

Knowing where S62.211D sits in the ICD-10-CM taxonomy helps you confirm that no more specific code applies. The hierarchy runs from broad to specific:

• Chapter 19: Injury, poisoning, and certain other consequences of external causes (S00-T88)
• Block S60-S69: Injuries to the wrist, hand, and fingers
• Category S62: Fracture at wrist and hand level
• Subcategory S62.2: Fracture of first metacarpal bone
• S62.21: Bennett’s fracture
• S62.211: Bennett’s fracture, right hand, not billable without a 7th character
• S62.211D: Bennett’s fracture, right hand, subsequent encounter for fracture with routine healing

The AAPC Codify ICD-10-CM lookup lets you walk this hierarchy by keyword or code range. That is useful when an operative note describes the anatomy instead of naming a code.

Approximate synonyms and lay terms

Operative reports, referral letters, and client records often use clinical or lay terminology rather than the ICD-10-CM description. These synonyms all map to the S62.211 code family, so each one should send you to the S62.2 subcategory.

• Bennett fracture (without possessive apostrophe)
• Bennett’s fracture-dislocation
• Intra-articular fracture, base of first metacarpal
• Articular fracture, thumb metacarpal base
• Fracture-dislocation, carpometacarpal joint of thumb
• Fracture, base of thumb metacarpal
• CMC fracture-dislocation, first ray
• First metacarpal base fracture, right hand

When an operative report describes a fracture at the base of the thumb without naming Bennett’s, check whether it is intra-articular. Intra-articular involvement at the first metacarpal base is the defining feature, and it maps to S62.21. An extra-articular fracture maps to a different subcategory under S62.2. If the note does not say either way, query the provider before assigning a code.

For practices with a high volume of hand surgery cases, a standardized documentation approach for operative and office notes removes most of that ambiguity. Fewer provider queries also means fewer claims parked in a work queue.

Associated CPT codes for Bennett’s fracture treatment

S62.211D is a diagnosis code, so it has to be paired with a CPT procedure code on the claim. Which CPT applies depends on what was performed at that encounter. For HIPAA-covered healthcare practices, accurate CPT-to-ICD pairing is the basis of a clean claim.

CPT selection has to reflect what was documented and performed at the encounter. Do not bill a surgical CPT code at a routine follow-up simply because surgery happened earlier. Each claim covers the services rendered on that date of service.

For current CPT descriptors and payment values, the CMS Physician Fee Schedule gives rates by code, region, and payer type. Check those amounts again each January, when the new schedule takes effect.

Coding guidelines and documentation requirements

The ICD-10-CM Official Guidelines govern how subsequent encounter codes work for traumatic fractures. Five rules matter most for S62.211D:

• Active care is not required for the D suffix: Subsequent encounter codes cover visits that are part of ongoing fracture management. The provider may only be monitoring healing. Cast checks, imaging review, and suture removal all qualify while healing is routine.
• Routine healing must be documented: The note has to show that healing is progressing normally. An absent or ambiguous healing assessment weakens audit support for S62.211D over S62.211G.
• The D suffix does not mean the patient is discharged: One patient can have several visits coded S62.211D across the healing period. The code holds until healing is complete or the clinical picture changes.
• Sequela coding needs a healed fracture: S62.211S applies when the patient presents with a late effect, such as arthritis or stiffness. The fracture itself must no longer be the active condition, which is the same test used for S62.032S.
• External cause codes are optional but useful: A Chapter 20 code explains how the fracture happened. It supports population health reporting, and some payers ask for it.

For Medicare patients, CMS requires ICD-10-CM codes on all Part A and Part B claims. A missing or invalid diagnosis code causes a rejection. The official CMS guidelines remain the primary reference for code-specific questions.

Practices processing a high volume of orthopedic follow-up claims benefit from structured documentation prompts in the note template. When the template carries a healing status field, coders get what they need without a provider query.

For hand surgery practices reviewing their practice management workflows, a tighter coding pipeline cuts admin work for clinical staff. First-pass claim rates tend to rise at the same time.

How Pabau keeps 7th character coding accurate

In most practices, the healing assessment sits in the provider’s free-text note, and the coder reads it after the visit. When the wording is vague, the claim either waits for a query or goes out with the wrong 7th character. Both outcomes cost the practice time.

Practice management software like Pabau puts the diagnosis and the procedure code on the same billing screen. The pairing is made once, then checked before submission. Note templates can prompt for healing status at every follow-up visit. Digital forms capture the hand treated at the point of documentation, and that detail carries through to the claim.

The result is a shorter path from visit to payment. Coders stop chasing providers for a healing status, and fewer claims come back with an invalid code. Every Pabau subscription includes the full records and billing toolset, so none of this sits behind a higher tier.

Simplify your billing workflow

Pabau connects ICD-10 diagnosis codes directly to CPT procedure codes within your billing module, helping catch coding errors before claims are submitted. See how it works for your practice.

Book a demo

Conclusion

The hard part of S62.211D is rarely the code itself. It is the wording of the follow-up note that has to support it. A provider who writes one clear line about healing status removes most of the denial risk across the whole episode of care.

So build that prompt into the note template rather than auditing for it later. The alternative is a coder choosing between D, G, K and P from context, and that is where a preventable rejection starts.

Keeping diagnosis and procedure codes in one workflow shortens that loop for good. Book a demo to see how Pabau handles fracture follow-up coding and claims at your practice.

Continue your research

Coding an open fracture rather than a closed one? S52.356C shows how the open-fracture 7th characters work on a forearm injury.

Billing a follow-up visit for a hand wound? S61.441D covers subsequent encounter coding when a foreign body is involved.

Not sure when suture removal is separately billable? CPT 15851 sets out the rules for suture removal at a post-operative visit.

Need an outcome measure for hand therapy notes? QuickDASH outcome measure scores upper limb function across a course of rehabilitation.

Coding a late effect of a finger injury? S61.311S walks through sequela coding once the original wound has healed.

Frequently asked questions