ICD-10 code S66.192D: Right middle finger flexor injury

Key takeaways

S66.192D is a billable ICD-10-CM code for other injury of the flexor muscle, fascia and tendon of the right middle finger.

The 7th character D marks a subsequent encounter, meaning routine care during healing after active treatment has already been given.

The code has been in ICD-10-CM since the original FY2016 release, so it is not a new FY2026 addition.

Even sixth digits sit on the right hand and odd digits on the left, which is where most sibling mix-ups start.

Practice management software like Pabau keeps the note, the code and the claim in one record, so follow-up claims go out complete.

ICD-10 code S66.192D covers other injury of the flexor muscle, fascia and tendon of the right middle finger. The site is wrist and hand level, and the encounter is a subsequent one. In plain terms, you bill it when active treatment is finished and the patient comes back for routine healing-phase care.

Below you will find the full description, the hierarchy, and the sibling codes by digit and side. The last sections cover the documentation a payer expects and the errors that stall payment.

What S66.192D describes, word by word

The code is valid, billable and accepted on HIPAA-covered transactions, so it can go on a claim as it stands. It has been part of ICD-10-CM since the original FY2016 release on October 1, 2015, and the FY2026 edition simply carries it forward. CMS publishes the current edition in its ICD-10 code files.

The official description reads: Other injury of flexor muscle, fascia and tendon of right middle finger at wrist and hand level, subsequent encounter. Every phrase in it does a job.

• Other injury separates this from the strain codes and the laceration codes in the same category.
• Flexor keeps it on the palm side, so an extensor injury never belongs here.
• Right middle finger fixes both the side and the digit.
• At wrist and hand level sets the anatomical zone, which rules out the forearm-level codes.
• Subsequent encounter is the 7th character, and the next section covers how to confirm it.

The 7th character D decides how the claim reads

D tells the payer that active treatment is over and that the patient is now in the healing phase. According to the CDC/NCHS ICD-10-CM official guidelines, that phase begins once the provider has delivered active treatment for the injury.

Active treatment covers surgical repair, casting, medication management and supervised physical therapy aimed at the injury itself.

A worked example makes the boundary clear. A patient has flexor tendon repair on the right middle finger, then returns two weeks later for a wound check and suture removal. That visit is S66.192D.

If the same patient comes back a year on with tendon adhesion and reduced grip, the visit takes S66.192S instead. The injury code stays on the record throughout. Only the 7th character moves, and the chart below turns that choice into one question you can ask of any note.

Where the code sits in the ICD-10 hierarchy

S66.192D is the seven-character billable form of base code S66.192, which sits three levels under category S66. Reading the hierarchy downward is the fastest way to confirm that no more specific code exists for what the note describes.

S66.192 on its own is not billable. Every claim carries the full seven characters, and a stripped six-character code will bounce at the front door.

Practices that submit high volumes of injury claims usually handle this inside their claims management software. The code, the note and the claim line then live in one place.

The sibling codes that get picked by mistake

Only the sixth digit changes across the S66.19 siblings, and it carries both the finger and the side. Even digits are the right hand and odd digits the left, running outward from the index finger.

Learn that pattern once and the whole subcategory becomes readable without a lookup.

Laterality and digit variants

Each code below carries the same wording as S66.192D, with only the finger and the side changing. The full ICD-10-CM code index covers the neighboring subcategories if the note points somewhere else in S66.

• S66.190D – right index finger
• S66.191D – left index finger
• S66.192D – right middle finger (this code)
• S66.193D – left middle finger
• S66.194D – right ring finger
• S66.195D – left ring finger
• S66.196D – right little finger
• S66.197D – left little finger
• S66.198D – other or unspecified finger

Encounter variants for S66.192

• S66.192A – initial encounter, during the active treatment phase
• S66.192D – subsequent encounter, during healing or recovery
• S66.192S – sequela, for a late effect of the original injury

S66 codes stop at wrist and hand level. A flexor injury documented above the wrist belongs in the S56 family instead, and the forearm-level equivalent for an unspecified finger is S56.109A. Checking the level before the digit saves a rework cycle.

What the note must document at a follow-up visit

Four elements have to be in the record before this code is defensible. They are the side, the digit, the structure, and evidence of earlier active treatment.

• Laterality confirmed: the note states “right”, not “dominant hand” or “affected side”. Payers want the side written out in words.
• Digit specified: “middle finger” appears in the note. If it says “third digit” or “D3”, the coder needs written crosswalk guidance to read that as the middle finger.
• Structure identified: the note names the flexor musculature, tendon sheath or fascia. A note reading “hand injury” does not support this level of specificity.
• Encounter phase documented: the record shows that active treatment already happened. An operative note, a prior visit record, or a clear statement that the patient is here for follow-up all count.

Four mistakes that stall an S66.192D claim

Denials on this code cluster around four repeatable mistakes. Each one is visible in the chart before the claim leaves the practice, which is the cheapest place to catch it.

Mistake 1: An A on a follow-up claim

Submitting the initial-encounter code at a follow-up appointment is the most common error on this family. Payers expect a logical progression from A to D across the encounter history. A repeated A reads as active treatment that never ended, which invites a medical necessity review and slows payment.

Mistake 2: An extensor injury coded as flexor

S66.192D covers the flexor surface only. Extensor tendon injuries at the same level sit in a separate subcategory, S66.3-. A coder who reaches for S66.192D without checking which surface the clinician named is introducing an error that may only show up at audit.

Mistake 3: The digit carried forward from the last visit

S66.192D is the right side and the middle finger. Choosing S66.193D or S66.190D instead misstates the injury, and both are one keystroke away. This error usually comes from a note copied forward from an earlier visit. The side and digit fields deserve a second read at every follow-up.

Mistake 4: Reaching for the sequela character too early

Sequela applies when the visit treats a late effect of the injury, such as tendon adhesion or lasting grip weakness. Time since the injury is not the test. Switching to S66.192S while the patient is still in routine healing care puts the code and the note in contradiction.

Clinical wording that maps to this code

These phrases in a note, a referral letter or an operative report should send you to S66.192D. None of them is the official wording, which is why the mapping has to be deliberate.

• Follow-up visit for right middle finger flexor tendon injury
• Subsequent encounter, right middle finger flexor tendon damage
• Injury to flexor muscle of right third digit, healing phase
• Right middle finger flexor mechanism injury, routine recovery visit
• Flexor tendon injury right hand, middle finger, subsequent encounter
• Other injury flexor fascia right middle finger at wrist and hand level, follow-up

For a second check on the descriptor or the hierarchy, the AAPC Codify ICD-10-CM lookup supports synonym search across the chapter. Whatever tool you use, read it against the note in front of you.

Run this check before you submit

Run these five checks before the claim leaves the practice. Each one maps to a mistake above, so the list is short by design.

1. The 7th character matches the phase of care in today’s note, not the phase at the last visit.
2. The note spells out “right” and “middle finger” in words, with no reliance on “D3” or “dominant”.
3. The documented structure is flexor rather than extensor, so the claim stays out of S66.3-.
4. The record holds proof that active treatment already happened, whether an operative note or a prior visit entry.
5. The claim itself is complete, with the member ID, plan details and any authorization number the payer requires.

How Pabau keeps follow-up injury claims complete

In most practices the encounter note lives in one system and the claim gets rekeyed into another. Staff then pick the 7th character away from the note that justifies it. That is how an A survives onto a follow-up claim.

Practice management software like Pabau keeps both in one record. The clinical note, the diagnosis code and the claim line all sit against the same appointment. A coder can read the prior operative note while picking the character, and code lookup libraries put the descriptor a search away.

On the claim itself, Pabau checks that the payer’s required fields are filled in, including membership numbers and authorization codes. US practices submit through the Claim.MD integration, which handles the CMS-1500 and 837P formats.

Coding judgment stays with your coder, which is why having the note and the code side by side matters. Pabau tracks submission status and remittances after that, so a queried follow-up surfaces while it is still easy to fix.

Keep follow-up injury claims complete

Pabau keeps the clinical note, the diagnosis code and the claim line on one record. It also checks that a payer’s required fields are filled before submission. Status and remittance tracking then show which claims need a second look.

Book a demo

Conclusion

The judgment on this code is small and it is made in one keystroke. Read the phase of care off today’s note, confirm the side and digit in words, then append the character that matches. Skip either check and the denial queue grows on a code that was never in doubt.

Practices that build those two checks into the follow-up template stop paying for them later in reworked claims. Book a demo to see how Pabau keeps the note, the code and the claim on one record.

Continue your research

Need help understanding your clearinghouse options? Medical claims clearinghouse guide covers how electronic claim submission works and what to look for in a clearinghouse partner.

Want to reduce claim denials systematically? Denial codes in medical billing breaks down the most common denial reason codes and how to address each one.

Chasing a claim that came back short-paid? Denial management in healthcare sets out a process for working denials by reason code instead of case by case.

Want fewer claims returned on the first pass? Clean claim explains what a payer accepts without a query and how to hit that standard consistently.

Building out your billing compliance process? How to get credentialed with insurance companies covers the credentialing steps that support accurate ICD-10 claim submission across payer networks.

Frequently asked questions