ICD-10 Code S66.292A: Extensor muscle injury of the left thumb

ICD-10 Code S66.292A covers other specified injury of the extensor muscle, fascia and tendon of the left thumb at wrist and hand level, initial encounter. It is a billable code, effective October 1, 2025 and valid throughout FY2026. The parent code S66.292 carries no 7th character, so payers reject it on sight.

This page covers the official description, the code hierarchy, the 7th character rules, documentation requirements, related codes, and billing guidance. Coders in hand surgery, orthopedics, emergency medicine, and rehabilitation meet this code family often, and laterality plus encounter type drive most of its denials.

Found our content helpful?

Key takeaways

ICD-10 Code S66.292A describes other specified injury of the extensor muscle, fascia and tendon of the left thumb, initial encounter. It is billable and valid for claim submission.

The 7th character A means the patient is in active treatment, while D covers follow-up and S covers sequela. Picking the wrong one is a common denial trigger.

S66.292 without a 7th character is not billable. Only S66.292A, S66.292D, and S66.292S can be submitted to payers.

Practice management software like Pabau captures the diagnosis code at the point of billing, which keeps laterality and encounter type consistent.

ICD-10 Code S66.292A: official description and billable status

S66.292A is a billable, specific ICD-10-CM code. According to the CDC/NCHS ICD-10-CM web tool, it became effective on October 1, 2025, and is valid throughout FY2026. The full official description is: Other specified injury of extensor muscle, fascia and tendon of left thumb at wrist and hand level, initial encounter.

The code targets a precise anatomical site: the extensor muscle, fascia, and tendon complex of the left thumb at wrist and hand level. This is distinct from flexor tendon injuries, which fall under different S66 subcategories. Clinicians must specify the structure (extensor, not flexor) and the laterality (left, not right) in their documentation for this code to be supportable on audit.

Code hierarchy: where S66.292A fits in ICD-10-CM

S66.292A descends from the broader injury chapter. Knowing where it sits helps coders pick the right subcategory when documentation is ambiguous. It also keeps claims off the overly broad parent code.

S66.292 (without the 7th character) is a non-specific, non-billable code. Payers will reject claims submitted with S66.292 alone. Always append the appropriate 7th character before billing.

Read the code from left to right and each segment answers a separate documentation question. The breakdown below shows which fact sits in which position.

How the 7th character works in ICD-10-CM

ICD-10-CM requires a 7th character on all injury codes in the S00-T88 chapter. This character tells the payer what phase of treatment the encounter represents. Getting it wrong is one of the most preventable causes of claim denial on musculoskeletal injury codes. The CMS ICD-10 coding guidelines are clear on this. The character reports the clinical situation at that encounter, not the date of injury.

“Initial encounter” does not mean the patient’s first-ever visit to any provider. It means the patient is still in active treatment for this injury at this encounter.

Take a patient who saw an emergency physician three days ago. She now sees an orthopedic surgeon for the first time, so active treatment continues and the A character still applies. Healing starts later, and a routine wound check six weeks after surgery takes D instead.

The same rule runs through the injury chapters of the wider ICD-10-CM code set. The character reports clinical status at the encounter, not the order in which providers saw the patient.

S66.292A vs S66.292D vs S66.292S: choosing the right variant

All three codes describe the same anatomical injury (extensor muscle, fascia, and tendon of the left thumb at wrist and hand level). The 7th character is the only differentiator. Use the decision framework below to make the selection at the point of care, before the claim is built.

What an extensor injury of the left thumb involves

The extensor pollicis longus (EPL) and extensor pollicis brevis (EPB) tendons run along the dorsal surface of the thumb. Together they extend and abduct it. Injuries at the wrist and hand level, the zone covered by S66.292A, come from lacerations, crush injuries, sports trauma, or degenerative rupture.

The extensor mechanism sits close to the skin, so even a minor laceration can partly or fully transect the tendon. Naming the structure and the mechanism in the note also supports the rehabilitation coding that follows later in the episode.

• Common causes: Glass laceration, sharp tool injury, avulsion fracture, degenerative rupture over Lister’s tubercle
• Structures involved: Extensor muscle belly, musculotendinous fascia, tendon proper – all three may be documented as injured under this code
• Anatomical zone: At the wrist and hand level (not forearm – injuries proximal to the wrist fall under a different S66 section)
• Laterality requirement: S66.292A is left thumb only; right thumb injuries use S66.291A; unspecified thumb injuries use S66.299A
• Clinical findings that support this code: inability to extend the thumb IP joint, dorsal thumb tenderness, a visible tendon gap, extensor lag on examination

“Other specified” captures injury presentations that do not fit the strain or laceration categories within S66.2. If documentation describes a complete tendon rupture or a specific laceration, other more precise codes may apply. Coders should review the full S66.2 category before defaulting to S66.292A.

Documentation the code requires

Coding accuracy for ICD-10 Code S66.292A depends on four documentation elements. Miss any one of them and the coder either drops to a lower-specificity code or holds the claim pending clarification.

• 1. Laterality confirmed: The note must state “left thumb” or “left hand” explicitly. “Thumb” alone is ambiguous and forces an unspecified code (S66.299A).
• 2. Structure identified: The record should specify extensor muscle, fascia, or tendon (or all three) rather than just “thumb injury.” Flexor injuries map to different codes.
• 3. Encounter type documented: The note should indicate whether this is an initial presentation for active treatment, a follow-up during healing, or a late-effect visit. The 7th character cannot be assigned without this.
• 4. Injury specificity: The description should confirm an “other specified” injury. It is not a simple strain (S66.211-) or a laceration coded under open wound categories. If documentation says laceration, review the open wound codes before using S66.292A.

A brief clinical note that reads “Left thumb extensor tendon injury, initial assessment and treatment” provides all four elements. A note that reads “hand pain, follow-up” provides none and cannot support S66.292A.

Related ICD-10-CM codes

Coders working with S66.292A will frequently need to compare it against sibling and parent codes. The table below covers the key related codes within the S66.2 family and the broader S66 category. Linking the correct diagnosis code to the CPT code performed, such as 26418 for extensor tendon repair, is what keeps the claim clean.

The AAPC Codify ICD-10-CM lookup lists every S66.2x code with its 7th character extensions. Check it when you pair a diagnosis code with a CPT code before submission.

ICD-9-CM crosswalk for S66.292A

ICD-10-CM replaced ICD-9-CM in the US on October 1, 2015. Anyone migrating legacy records or reviewing older claims may still need the approximate ICD-9-CM equivalent. Crosswalks are approximate, not exact, and one ICD-9 code often maps to several ICD-10 codes.

The closest ICD-9-CM equivalent for S66.292A is 842.12 (Sprain of thumb – metacarpophalangeal (joint)). It does not capture the extensor tendon specificity of the ICD-10-CM code. Check any legacy mapping against the ICD List crosswalk tools before you rely on it for a billing review.

Billing and reimbursement guidance

S66.292A is a fully billable ICD-10-CM code, valid for submission to Medicare, Medicaid, and commercial payers. A valid diagnosis code is only half of the claim, because musculoskeletal injury claims pair it with one or more CPT procedure codes.

Two CPT codes come up often for extensor tendon work in the hand. CPT 26418 is “Repair, extensor tendon, finger, primary or secondary; without free graft, each tendon.” CPT 26415 covers excision of an extensor tendon with implantation of a synthetic rod. The code you bill depends on the procedure the surgeon documented.

• Payer-specific notes: Some payers apply Medical Necessity policies requiring the diagnosis to substantiate the procedure. An S66.292A diagnosis supports extensor tendon repair CPT codes but must align with operative documentation.
• Modifier considerations: For bilateral procedures (rare with a laterality-specific code), modifier 50 would not apply to S66.292A – the code is already left-specific. Use S66.291A for any concurrent right thumb procedure.
• Denial risk: Two preventable denials dominate this code family. One is S66.292 submitted without a 7th character. The other is S66.299A submitted when the chart clearly documents the left thumb. Good claim denial management starts with a pre-bill audit of both.
• Sequencing: When S66.292A is submitted alongside other injury codes, sequence the most severe injury first unless payer or UHDDS guidelines direct otherwise.

Clearinghouse edit engines flag 7th character errors automatically, so a claim built on the bare parent code rarely reaches the payer at all. Checking laterality and encounter type before submission costs far less than reworking a rejected claim two weeks later.

How Pabau keeps laterality and encounter type on the claim

The four facts this code needs usually get captured twice. The clinician writes them into the note, and a coder reads the note back days later to rebuild them. A vague note turns into a coder’s query, and the claim waits.

Practice management software like Pabau moves that capture to the point of care. Structured clinical notes and digital forms record the side, the structure, and the phase of treatment as the clinician documents the visit. The diagnosis code is then attached to the encounter itself rather than reconstructed afterwards.

Billing staff see the same record the clinician wrote, so a left thumb stays a left thumb from note to claim. Pabau’s claims management software then carries that detail into submission and tracks what each payer does with it.

Reduce coding errors at the source

Pabau helps clinics document encounters with structured clinical notes and digital forms, so the right code details are captured at the point of care. Less rework, fewer denials, and cleaner claims from day one.

Book a demo

Conclusion

S66.292A rewards documentation, not memory. Once the note states the side, the structure, and the phase of treatment, the code writes itself and the 7th character stops being a guess.

So the work worth doing sits upstream of the claim. Build the pre-bill check into the coder’s routine, and query the clinician while the encounter is still recent rather than after a rejection. Book a demo to see how Pabau captures those details in the note, so your coders are not chasing them later.

Continue your research

Want to stop denials before the claim leaves the practice? Claim denial management in healthcare covers the denial reasons that recur across injury coding and how to work them systematically.

Not sure what separates a clean claim from a reworked one? What is a clean claim explains the payer edits a diagnosis code has to survive on first submission.

Need to see where diagnosis coding sits in the wider billing cycle? Revenue cycle management walks through the steps from encounter to posted payment.

Frequently asked questions