ICD-10 code S66.599A: Intrinsic finger muscle injury

Key takeaways

ICD-10 code S66.599A covers other injury of intrinsic muscle, fascia and tendon of an unspecified finger, initial encounter.

The code is billable and valid for HIPAA-covered electronic transactions in FY 2026.

Sixth-character digits 0 through 8 name the finger and the side. Use one of those whenever the record identifies the finger.

Thumb codes under S66.4- carry an Excludes2 note, not an Excludes1. Both can appear on one claim when both injuries are documented.

The seventh character A covers the whole active treatment phase, not just the first visit. It becomes D once active care ends.

ICD-10 code S66.599A covers other injury of the intrinsic muscle, fascia and tendon of an unspecified finger at wrist and hand level, initial encounter. It is billable, so a claim carrying it can be paid.

The trouble sits in the sixth character. That 9 says nobody named the finger, and payers look hard at unspecified injury codes. When the record does name the finger, a sibling code moves through the payer with far less friction.

The rest of this page works through the sibling codes, the seventh character, and the documentation that keeps the claim moving.

Every field a payer checks before S66.599A gets paid

S66.599A is a billable, HIPAA-valid ICD-10-CM code for FY 2026, and it is complete as written. Nothing else needs to be appended to it. The table below is the field-by-field reference.

Per CMS ICD-10-CM guidance, every billable ICD-10-CM code is valid on HIPAA-covered electronic transactions. Codes are reviewed each year, so check the current tabular list before you submit.

What each character in S66.599A tells the payer

Read S66.599A from left to right and it answers five separate questions. Every answer has to be earned by a line in the note, or the code is wrong.

The intrinsic group is where coders slip most often. Lumbricals, interossei and hypothenar muscles begin and end inside the hand.

Extrinsic flexors and extensors begin in the forearm, so their injuries belong to other S66 subcategories. Mislabeling an extensor tendon injury as an intrinsic one changes the diagnosis, and payer edits usually catch it.

The full ladder from chapter down to billable code runs like this:

• S00-T88: Injury, poisoning and certain other consequences of external causes
• S60-S69: Injuries to the wrist, hand and fingers
• S66: Injury of muscle, fascia and tendon at wrist and hand level
• S66.5: Injury of intrinsic muscle, fascia and tendon of other and unspecified finger at wrist and hand level
• S66.59: Other injury of intrinsic muscle, fascia and tendon of other and unspecified finger at wrist and hand level
• S66.599: Other injury of intrinsic muscle, fascia and tendon of unspecified finger at wrist and hand level
• S66.599A: Initial encounter, the billable code

Step down that ladder as far as the documentation allows. Where the note names the finger, S66.599A is not the bottom rung.

The seventh character decides whether this is still initial care

The seventh character is required, and A means active treatment rather than first visit. Codes in the injury chapters are incomplete without it, so a claim missing that character comes straight back.

Choosing the wrong one is a common reason hand injury claims get returned for correction.

According to the CDC/NCHS ICD-10-CM tool, initial encounter describes the phase of care and not the visit count. A patient can have four visits and still sit in the A phase. The code moves to D once the clinician documents that active management has ended.

Code the finger before you settle for unspecified

When the note names the finger, one of nine sibling codes replaces S66.599A. The sixth character carries the finger and the side together, which is why the list below is worth reading digit by digit.

The sixth character is also where a keystroke does the most damage, because S66.594A and S66.595A differ only by the side. Pull the descriptor from our ICD-10-CM code library rather than from memory, then read it back against the note.

Thumb codes are an Excludes2, so both can ride on one claim

Thumb injuries sit under S66.4- as an Excludes2, not an Excludes1. That distinction decides whether you can report both codes together, and the FY 2026 tabular list is clear on it.

• Excludes2 for the thumb (S66.4-): intrinsic thumb injuries have their own subcategory. Report one alongside S66.599A when the record documents an injury to both the thumb and another finger.
• No code-level note for extrinsic muscles: extrinsic flexors and extensors classify to other S66 subcategories on their own. There is no official note at S66.599A separating them, so both can be reported when both are documented.
• Code also any associated open wound: S66 instructs coders to add the matching open wound code from S61-. A laceration over the injured muscle needs both codes, not one.
• External cause codes: ICD-10-CM guidelines expect a code from V00 to Y99 naming the mechanism. Not every payer demands one, and some make it a condition of coverage.

When S66.599A actually fits the encounter in front of you

Use S66.599A when the intrinsic structures of a non-thumb finger are injured at wrist and hand level. It applies where neither the injury type nor the finger is pinned down. These four presentations come up most:

• Blunt trauma or contusion to the intrinsic hand muscles, with no finger named in the emergency note
• A grip or impact sporting injury where the first note records a hand injury but not a digit
• Post-procedural injury to intrinsic finger musculature that meets no strain or laceration criteria
• An initial workup where imaging is pending and no finger-level code can be confirmed yet

Once imaging or a specialist note identifies the finger, move to the sibling code at the next encounter. Staying inside the initial encounter phase does not stop you from adding specificity, and S66.590A through S66.598A remain available for the rest of the episode.

Words in the chart that point away from S66.599A

Sprain, strain and laceration each send the claim somewhere other than S66.599A. Three of those detours account for most of the miscoding in this range.

• A documented sprain of a finger is a ligament injury, so it classifies to S63.6- rather than anywhere in S66
• A strain of the intrinsic muscle group belongs at S66.51-, and a laceration of the same structures at S66.52-
• An injury with no type documented at all is S66.50-, unspecified injury, which is a different claim from other injury

Other phrasing does map here. Operative notes, referral letters and therapy assessments describe this code in several ways:

• Finger musculotendinous injury, unspecified finger
• Intrinsic hand muscle injury
• Musculotendinous injury at wrist and hand level, finger
• Injury of lumbrical or interosseous muscle, unspecified finger
• Finger intrinsic mechanism injury, acute phase

Where the note gives a structure and a mechanism but no injury type, S66.599A is the honest choice. Do not reach for it to paper over an injury the surgeon already described precisely.

How an S66.599A claim moves, and where it stalls

Picking the code takes seconds. Payment is decided by what happens either side of it, so it helps to see the whole path.

1. The clinician documents the structure, the level, the injury type and the finger, where it is known
2. The coder reads the sixth character off the note, then adds the seventh for the phase of care
3. The biller attaches the external cause code and links the diagnosis to each procedure line
4. The clearinghouse runs payer edits and returns rejections before the claim reaches the payer
5. The payer adjudicates, and the remittance reports payment or a denial reason code

Most S66.599A problems surface at step four, which is the cheapest place to find them. A rejection there costs a correction. A denial after adjudication costs an appeal, and the clock on timely filing keeps running while you write it.

Run this check before you submit S66.599A

Five things account for most returns on this code. Work down them before the claim leaves your system.

• The note names the injured structure and places it at wrist or hand level
• The finger is either named, in which case a sibling code applies, or genuinely absent from the record
• The injury type reads as something other than a strain or a laceration
• The seventh character matches the phase of care described at this visit
• An external cause code names the mechanism, with place and activity codes where the payer asks for them

Those five checks are most of the distance between a coded encounter and a clean claim that pays on the first pass. Run them while the note is still open, because chasing the clinician a week later rarely works.

How Pabau keeps ICD-10 coding and claim submission on one record

Plenty of practices code in one system and submit from another. The diagnosis gets entered twice, and the second copy is where the transposed sixth character lands. Nobody sees it until the rejection arrives.

Practice management software like Pabau keeps that entry in one place.

The ICD-10 code sits on the encounter inside the patient record. Pabau’s medical claims management then links it to the procedure lines that go out on the claim. Coders search for S66.599A in the built-in ICD-10 and CPT catalogues instead of switching to a separate lookup tool.

Pabau also integrates with Claim.MD, our US clearinghouse partner, which reaches thousands of US insurance payers. Claims leave as CMS-1500 forms generated from the invoice, and claim status plus electronic remittance advice comes back into the Pabau claims dashboard.

Billing staff see a rejected diagnosis code in the same place they submitted it.

Keep ICD-10 entry and claim submission on one record

Pabau holds the ICD-10 code on the encounter, generates the CMS-1500 from the invoice, and brings claim status and remittance back into one dashboard. Your coders and billers stop retyping the same diagnosis.

Book a demo

Conclusion

S66.599A is a clean code to report and an easy one to over-use. The sixth character is where the money sits, because an unspecified finger invites the review that a named finger avoids.

So push for the finger in the documentation before the encounter closes. That single habit moves most of these claims onto a sibling code, shortens the payment cycle, and gives an auditor less to ask about later.

If your coders and your billers work in separate systems, that diagnosis is being retyped somewhere. Book a demo to see how Pabau keeps ICD-10 entry, claim submission and remittance on a single patient record.

Continue your research

Need the whole claim lifecycle in view? What is revenue cycle management covers how accurate diagnosis coding connects to every later step in the claim.

Chasing a denial on a musculoskeletal claim? Denial codes in medical billing explains the common denial reasons and how to answer them before you resubmit.

Wondering where payer edits catch a bad code? Medical claims clearinghouse shows what a clearinghouse checks before your claim reaches the payer.

Building a superbill for a hand injury visit? Superbill walks through the fields that have to be right before it becomes a claim.

New to the billing side of diagnosis coding? What is medical billing sets out each step between the encounter and the payment.

Frequently asked questions