ICD-10 Code S56.411D: Extensor tendon strain, right index finger

Key takeaways

S56.411D is the billable ICD-10-CM code for a right index finger extensor strain at forearm level, subsequent encounter.

The code is not a recent addition. It has been in ICD-10-CM since October 1, 2015, and FY2026 leaves it unchanged.

The 7th character D means active treatment has finished and the patient is now in follow-up care.

The treatment phase decides between A and D, not how many days have passed since the injury.

Its closest siblings are S56.412D for the left index finger and S56.413D for the right middle finger.

ICD-10 code S56.411D: definition and billable status

S56.411D is a billable ICD-10-CM code for a strain of the extensor muscle, fascia, and tendon of the right index finger. The injury sits at forearm level, and the code covers a subsequent encounter. Use it for follow-up visits rather than the parent-level or non-specific codes in the S56 category.

The code is not a recent addition. It has been in ICD-10-CM since the code set took effect on October 1, 2015, and the FY2026 edition leaves it unchanged. It remains valid for HIPAA-covered electronic transactions.

The S56.4 subcategory covers injury of the extensor muscle, fascia, and tendon of other and unspecified finger at forearm level. Its parent category, S56, covers injury of muscle, fascia, and tendon at forearm level. The CDC/NCHS ICD-10-CM web tool confirms the billable status and carries the FY2026 tabular list.

Clinical description: extensor strain of the right index finger

The extensor muscles of the hand originate at the lateral epicondyle of the humerus and the posterior forearm. They run along the dorsal surface, pass through fibrous sheaths, and attach at the dorsal aspect of each finger. At forearm level, the extensor digitorum communis and extensor indicis proprius are the primary structures serving index finger extension.

• Extensor digitorum communis: the primary extensor of digits 2-5, running along the dorsal forearm
• Extensor indicis proprius: a deeper muscle providing independent extension of the index finger
• Fascia: the connective tissue investing the extensor compartment, also captured within the S56.411D descriptor
• Strain vs. rupture: S56.411D covers strain, meaning overstretching or partial disruption; complete rupture takes a different code

A strain at this level means those structures have been overstretched or partially torn. Three findings usually appear together in the note:

• Localized pain along the dorsal forearm
• Weakness extending the right index finger against resistance
• Swelling or bruising over the extensor compartment

The injury typically follows forceful gripping, repetitive extension loading, or direct trauma. Coders should read “at forearm level” literally. The pathology sits in the muscle-tendon unit proximal to the finger, not at the tendon insertion on the digit.

Accurate use of this code requires the note to confirm the structure, the digit, the anatomical level, and the encounter type. Missing any of those elements pushes the coder to a nonspecific code, which may affect reimbursement.

The 7th character: when D applies instead of A or S

The 7th character decides which S56.411 code goes on the claim, and one question settles it. Is the provider still delivering active treatment for the injury?

Per the CMS ICD-10-CM coding guidance, the distinction turns on whether the provider is still actively treating the injury. A patient may return two days after initial splinting for a cast check. That visit is D, because care has moved from active intervention to recovery management.

The reverse also holds. A patient who presents weeks after an undiagnosed injury and receives first treatment still takes A, whatever the elapsed time.

Payers apply claim edits against these encounter characters, so a D where A was warranted can trigger a denial or an audit flag. Physical therapists and occupational therapists treating extensor strains after the acute phase will almost always reach for the D character. Practices that review common denial codes line by line tend to catch this mismatch early.

ICD-10-CM code hierarchy for S56.411D

Knowing where S56.411D sits in the tabular hierarchy helps coders navigate parent codes, excludes notes, and related categories. The AAPC Codify ICD-10-CM lookup displays this hierarchy in full.

Neither S56.4 nor S56.41 is billable on its own, and S56.411 still needs a 7th character. Submitting any of the three returns a code-validity rejection. Check that the full seven-character string is on the claim before it leaves the practice.

The hierarchy also shows where wrong sibling codes come from, one character at a time.

Related codes and sibling codes

S56.411D belongs to a family of closely related codes in the S56.4 subcategory. Picking the wrong sibling is one of the most common accuracy errors on musculoskeletal injury claims. The differences come down to laterality, digit, injury type, and encounter type.

When a patient strains both index fingers, report S56.411D and S56.412D together. Watch the 5th character as closely as the 6th, because S56.42- covers laceration rather than strain of the same structures.

Approximate synonyms and documentation language

Clinical documentation often uses descriptive language rather than ICD-10-CM code terminology. These synonyms map to S56.411D in the alphabetical index and should prompt the coder to confirm the selection.

• Subsequent encounter for strain of extensor tendon of right index finger
• Right index finger extensor muscle strain, follow-up visit
• Strain of extensor digitorum at forearm level, right index finger, subsequent care
• Right index finger dorsal forearm tendon strain, subsequent encounter
• Follow-up care for right index finger extensor muscle injury
• Overuse strain of extensor indicis, right side, subsequent encounter

Documentation that reads only “hand injury” or “finger tendon pain” will not support S56.411D. The note has to name extensor rather than flexor structures, the specific digit, and the anatomical level. Coders should query the treating provider when any of the three is ambiguous.

Excludes notes and dual coding

The S56 category carries notes that govern code selection and sequencing. Both of them apply directly to S56.411D.

Excludes notes (S56 category level)

• Injury of muscle, fascia and tendon at or below wrist (S66.-): an Excludes2 note, so the two may be reported together
• Sprain of joints and ligaments of elbow (S53.4-): also Excludes2, so these codes may appear on the same claim

Practical excludes guidance

Excludes1 notes prohibit reporting two codes together for the same condition. Excludes2 notes allow it when two distinct conditions coexist. Category S56 carries no Excludes1 note, so nothing at that level is mutually exclusive with S56.411D.

The anatomical level still matters. An extensor tendon injury at the digit itself falls under a different code, and it should not be reported as S56.411D for the same site. The tabular hierarchy governs here, not the code descriptor alone.

How to reach the code through the alphabetical index

The index pathway to S56.411D follows a branching structure. Coders should trace the lead term first, then move to the tabular list for final verification.

• Lead term: Strain
• Subterm 1: muscle (tendon)
• Subterm 2: finger (s) extensor
• Subterm 3: forearm level, NEC
• Index entry: S56.41- (digit and 7th character still to be added)

After locating S56.41- in the index, the coder moves to the tabular list. There the digit is confirmed and the 7th character is added, which gives S56.411D. This two-step process, index then tabular, is required under the ICD-10-CM official coding guidelines.

Documentation that supports the code

Accurate coding of S56.411D depends on what appears in the clinical note, not on what the coder infers. Four documentation elements must be present to support this specific code.

Two mistakes account for most errors on this code. First, coders use A for every visit because the note records the injury without the treatment phase. Second, they submit S56.411 with no 7th character, which is not a billable string.

What happens after the claim goes out

Once S56.411D reaches the payer, it is adjudicated against medical necessity policy. The payer then returns an electronic remittance advice showing payment, adjustment, or denial. For subsequent encounter codes, payers usually want documentation that links the initial encounter to the current follow-up.

Denials on subsequent encounter codes commonly cite insufficient evidence of continued medical necessity. The note should record the current state of healing rather than repeat the original injury description. Partial resolution of pain, an ongoing therapy protocol, or a strength re-evaluation all serve that purpose.

Practices that audit S56 category codes periodically should treat 7th-character accuracy as its own audit dimension. It is the element most likely to be wrong and least likely to be noticed.

How Pabau keeps follow-up injury claims clean

A 7th-character error usually surfaces only after the payer sends the claim back. The correction cycle then costs a resubmission and several weeks of delay on a low-value claim.

Practice management software like Pabau keeps the documentation and the claim in one system. The encounter note, the injury history, and the assigned diagnosis code sit on the same client record. A coder can then see whether the visit was active treatment or follow-up before the claim goes out.

For US practices, Pabau integrates with the Claim.MD clearinghouse for electronic claim submission and real-time eligibility checks. Its cleaner claims management tracks each claim after submission, so denials surface in days. That matters most on low-value injury codes, where a month-end discovery leaves the claim already aging.

Catch coding errors before the claim leaves

Pabau puts the encounter note and the diagnosis code on one client record, then submits through the Claim.MD clearinghouse and tracks the result. Follow-up injury claims stop coming back for rework.

Book a demo

Conclusion

S56.411D turns on four documentation anchors. The note has to show extensor structures, the right index finger, forearm-level anatomy, and subsequent encounter status.

Two errors are worth guarding against. One is the parent code submitted without a 7th character. The other is A used where D belonged. Both start in the clinical note rather than at the coding desk, so that is where the fix belongs.

Fix the note template once and the code looks after itself on every follow-up visit. Book a demo to see how Pabau keeps injury follow-up documentation and claim submission in one workflow.

Continue your research

Need a guide on medical billing fundamentals? What is medical billing walks through the end-to-end claims process from code assignment to payment posting.

Want to understand how ERA workflows reduce rework? Electronic remittance advice explains how 835 files connect payer adjudication back to your practice management system.

Seeing repeat denials on injury codes? Denial management in healthcare sets out how to triage, appeal, and prevent the denials that follow coding errors.

Want the claim accepted first time? Clean claim explains which fields payers check before adjudication, and what makes a claim fail on submission.

Frequently asked questions