ICD-10 Code S66.399S: Extensor tendon injury, finger sequela

Key takeaways

ICD-10 Code S66.399S describes other injury of extensor muscle, fascia and tendon of unspecified finger at wrist and hand level, sequela.

S66.399S is a billable, specific ICD-10-CM code valid for fiscal year 2026 (October 1, 2025 through September 30, 2026) and accepted for HIPAA-covered transactions.

The seventh character ‘S’ means the patient presents with a sequela. That is a lasting consequence of a prior extensor tendon injury, not an active or healing one. Confusing it with ‘D’ (subsequent encounter) is the most common coding error.

Practice management software like Pabau attaches the correct ICD-10 code at the point of care. Its claims tools then submit HIPAA-compliant claims without switching systems.

ICD-10 Code S66.399S is a billable diagnosis code for other injury of the extensor muscle, fascia, and tendon of an unspecified finger. The full descriptor places that injury at wrist and hand level and marks it as a sequela. The seventh character ‘S’ marks a lasting consequence of a prior injury rather than the injury itself.

That one character is where S66.399S claims usually come apart. This guide covers the code definition, the seventh character conventions, the full hierarchy, the documentation each claim needs, and the errors that draw denials.

Physical therapists, occupational therapists, hand surgeons, and sports medicine practitioners see extensor tendon sequelae throughout follow-up care. Knowing where S66.399S applies, and when a sibling code fits better, keeps claims moving and audits clean.

Practices with structured physical therapy documentation catch seventh character errors before submission instead of after denial.

ICD-10 Code S66.399S: Definition and billable status

S66.399S is a billable, specific ICD-10-CM diagnosis code. Its full official description in the CDC coding tool reads as follows. Other injury of extensor muscle, fascia and tendon of unspecified finger at wrist and hand level, sequela.

The code is valid for fiscal year 2026, effective October 1, 2025 through September 30, 2026. It is accepted for HIPAA-covered transaction submission.

The code is maintained under the joint authority of the NCHS (National Center for Health Statistics) and CMS (Centers for Medicare and Medicaid Services).

Validity is confirmed annually, so check the current CMS ICD-10-CM code release at the start of each fiscal year.

Code description and clinical meaning

Breaking down the full descriptor clarifies exactly what S66.399S captures and what it excludes.

• Extensor muscle, fascia and tendon: The code covers the extensor mechanism at the dorsal (back) surface of the hand, including the extensor digitorum tendons. These structures allow fingers to straighten. Damage here typically follows laceration, blunt force, or avulsion injuries.
• Unspecified finger: The “unspecified finger” qualifier applies when the clinical note does not identify which finger is involved. If the note names the finger, use the matching laterality-specific sibling code instead. Where the digit is identified but has no dedicated code, S66.398 covers “other finger.” Specificity is always preferred when documentation supports it.
• At wrist and hand level: This anatomical qualifier distinguishes S66 injuries from injuries coded at the forearm level (S56 series) or the finger level specifically. The injury site is the wrist and hand, not the digit alone.
• Sequela: The patient is presenting with a condition that is the lasting consequence of a prior extensor tendon injury. The original injury has resolved or moved beyond the active treatment phase. Examples include chronic weakness, contracture, or restricted range of motion following an earlier tendon laceration or crush injury.

Occupational therapists and hand rehabilitation specialists working with patients post-tendon repair frequently encounter these sequelae.

Practices using occupational therapy software with structured clinical note templates can prompt clinicians to capture the prior injury history. That record is what justifies the ‘S’ seventh character at every relevant encounter.

What the seventh character ‘S’ means

The ICD-10-CM seventh character convention is one of the most frequently misapplied rules in injury coding. According to the CMS coding guidelines, three episode-of-care indicators apply to most injury codes in the S and T ranges. Choosing the wrong character is enough on its own to trigger a denial.

The distinction turns on healing status. A patient attending hand rehabilitation six weeks after an extensor tendon repair is coded with ‘D’ while the tendon still heals.

If that patient returns months later with chronic stiffness or grip weakness from the same injury, ‘S’ applies. The same rule governs every sequela code in the S66 category, including S66.527S.

S66.399A vs S66.399D vs S66.399S: Choosing the correct code

All three codes share the same base descriptor. The seventh character alone changes their meaning and their eligibility for reimbursement. Choosing the wrong one can trigger a denial even when the underlying diagnosis is correct.

Cross-check the seventh character against the clinical picture in the note, never against the injury date alone. Codes outside the S66 family follow the same logic, so S63.631D covers a finger sprain still in its healing phase. When the note is ambiguous, query the clinician before the claim goes out.

ICD-10 code hierarchy: Where S66.399S sits

Understanding the hierarchy helps coders navigate to the correct level of specificity. It also identifies the parent codes that apply when documentation will not support a specific code.

The WHO ICD-10 classification framework organizes all injury codes in a nested structure from broad to specific.

Sports medicine and hand surgery practices see a high volume of these injuries. Many patients progress from active treatment through the healing phase and on to sequela care.

Coding each stage correctly means reading the current note. The parent code never changes, but the seventh character moves from ‘A’ to ‘D’ to ‘S’.

Related and sibling codes

The S66.399 base yields three episode-of-care variants. Sibling codes within the S66.39 group cover the same injury type on a finger that the record identifies by name and side.

Reviewing these helps confirm S66.399S is the correct choice rather than a finger-specific alternative. The AAPC Codify ICD-10-CM lookup is useful for cross-referencing sibling codes in the S66 family.

Verify the exact descriptions of the finger-specific siblings against the current CMS tabular list before coding. The sixth character carries both the digit and its side, so one transposed number changes the finger and the laterality.

Every code in this group still needs a seventh character before it can be submitted. Surgery on the same structures is billed separately, with procedure codes such as CPT code 25118.

Documentation requirements for S66.399S

A claim submitted with S66.399S must be supported by documentation that establishes both the prior injury and the current sequela. Missing either element gives payers grounds to deny. The following elements must appear in the clinical record to support this code.

• Reference to the original injury: The note must explicitly mention the prior extensor tendon injury at the wrist and hand level. It also needs the mechanism (laceration, crush, avulsion) and the date the injury occurred. A vague “history of hand injury” is not sufficient.
• Sequela relationship: The documentation must establish a direct causal link between the prior injury and the current presenting condition. The clinician should state that the patient’s current symptoms (stiffness, contracture, weakness) are a consequence of the prior injury, not a new acute event.
• Affected structure: The note must identify the extensor muscle, fascia, or tendon as the structure involved. “Hand pain” alone does not support this code.
• Laterality or unspecified rationale: If the specific finger is known and documented, a more specific sibling code should be used. If the finger is genuinely unknown or not documented, the note should record that the information is unavailable rather than simply omit it.
• Episode of care justification: The documentation must make clear that the patient is not presenting for initial treatment or during an active healing phase. That is what confirms ‘S’ (sequela) over ‘A’ or ‘D’.

Most rehabilitation practices already run structured note templates that capture injury history and episode of care. Adding a sequela prompt to those templates makes the coding justification auditable without extra clinician effort. Purpose-built clinical documentation software can make that field mandatory before the note closes.

Practice management software like Pabau attaches the diagnosis code inside the note itself. Its claims management software then carries that code through to submission, so nobody re-keys it into a billing screen.

Common coding errors and how to avoid them

Most denials involving ICD-10 Code S66.399S trace back to a small number of systematic errors. Reviewing these patterns helps coders build a pre-submission checklist.

• Using ‘D’ when ‘S’ applies: Coding a sequela encounter as a subsequent encounter (S66.399D) is the most common error. If the original injury has resolved and the patient presents with a lasting consequence, ‘S’ applies. If healing is still underway, ‘D’ applies. The documentation must support whichever character is chosen.
• Failing to document the prior injury: Using S66.399S without a record of the original extensor tendon injury leaves no clinical basis for the code. Payers can deny on the grounds that the sequela relationship is unsubstantiated.
• Using ‘unspecified finger’ when the finger is known: ICD-10-CM requires coding to the highest level of specificity the documentation supports. If the clinical note identifies the affected finger specifically (for example, the ring or middle finger), a more specific sibling code must be used. S66.399S should only appear when the specific finger is genuinely unidentifiable or undocumented.
• Missing the anatomical site qualifier: The S66 category covers injuries at the wrist and hand level. If the injury sits at the forearm level, the correct family is S56. A forearm-level tendon sequela such as S56.114S belongs there instead. Documentation must confirm the anatomical site matches the code family.
• Applying ‘S’ prematurely: Switching to a sequela code before the healing phase has concluded creates a mismatch. The episode of care in the record no longer matches the code submitted. Sequela codes are appropriate only after the condition producing them has resolved. Fracture cases carry their own healing-status characters, such as nonunion in S42.302K.

A one-line prompt in the encounter note is the cheapest control available here. Ask the clinician to confirm episode of care at every visit. The seventh character then stops being a guess made weeks later by someone who never saw the patient.

Each denial sends the claim back through the medical billing cycle, which costs staff time no practice has budgeted for.

How Pabau supports accurate diagnostic coding

Coding accuracy depends on the documentation captured during the encounter. A coder working weeks later can only use what the note already says. Pabau builds ICD-10 code attachment into the clinical documentation workflow, so a code like S66.399S is applied while the patient is still with you.

• Structured clinical notes: Pabau’s digital clinical forms can prompt clinicians to record prior injury history, episode of care status, and affected anatomical structure. These prompts surface the documentation elements required to support sequela codes before the encounter is closed.
• Integrated claims workflow: Once the diagnosis code is attached in the clinical record, Pabau’s claims tools carry it through to submission without re-keying. This reduces transcription errors that can flip a seventh character.
• Full encounter history: Pabau’s structured patient records keep every past encounter on file. The original injury date and treatment timeline stay visible when you code a sequela encounter months or years later.
• HIPAA-compliant submission: S66.399S is valid for HIPAA-covered transactions. Pabau’s end-to-end claim workflow supports compliant transmission of billable ICD-10-CM codes, helping practices meet submission standards without manual workarounds. See Pabau’s HIPAA compliance page for details.

Practices that treat documentation and claim submission as one workflow see fewer sequela denials. The prior injury, the episode of care, and the diagnosis code all come out of the same record.

Reduce coding errors at the point of care

Pabau’s clinical documentation tools capture the injury history, episode of care, and anatomical detail each ICD-10 code needs. Everything is in place before the claim leaves your practice. See how it works.

Book a demo

Conclusion

The decision that settles an S66.399S claim is made in the treatment room, long before a coder opens the chart. Whoever writes the note decides whether the record shows a healed injury with a lasting consequence.

So put the prompt in the note template rather than on the coder’s checklist. The sequela question then gets answered while the patient is still in the room. Denials that used to arrive weeks later never get filed.

One trade-off is worth keeping in mind. ‘Unspecified finger’ costs you nothing on this claim, but it thins the record if the same patient comes back for surgery. Book a demo to see how Pabau keeps injury history and diagnosis codes together at the point of care.

Continue your research

Coding a finger sprain that has already healed? S63.615S works through a left ring finger sprain with the sequela seventh character.

Documenting a thumb laceration with nail damage? S61.119S sets out the descriptor and the record a sequela claim needs.

Billing a wrist fracture months after it healed? S62.032S covers scaphoid fracture sequela coding and the notes that support it.

Billing the surgery behind these hand injuries? CPT code 25110 explains how to bill excision of a tendon sheath lesion at the wrist.

Planning rehabilitation for nerve-related arm pain? Brachial neuritis exercises breaks the program down phase by phase.

Frequently asked questions