ICD-10 Code S60.312D: Abrasion of left thumb, subsequent encounter

Key takeaways

S60.312D is a billable ICD-10-CM code for abrasion of left thumb, subsequent encounter, effective October 1, 2025 through September 30, 2026.

The 7th character D means the patient is receiving active care after the initial treatment phase, distinct from A (initial) and S (sequela).

Using S60.319D (unspecified thumb) when the affected side is documented is a common and avoidable coding error.

The abrasion level sits at S60.31, so the digit 1 in S60.312D encodes the injury type rather than the site.

Pabau’s claims management software and Claim.MD clearinghouse integration support ICD-10-CM code submission on CMS-1500 and UB-04 claim forms.

S60.312D code details at a glance

S60.312D is a billable ICD-10-CM code for abrasion of left thumb, subsequent encounter.

It applies to follow-up visits during the active healing phase, after the first treatment contact. The 7th character D is what separates it from S60.312A and S60.312S.

According to the CDC/NCHS ICD-10-CM web tool, S60.312D is confirmed billable and specific under the FY2026 code set. The code is valid for submission on standard CMS claim forms, provided the encounter type and laterality are clearly documented in the clinical record.

What does S60.312D mean? A component-by-component breakdown

Every character in S60.312D carries a specific meaning. Get one of them wrong and the claim points at the wrong code or trips a laterality edit.

• S60 – Category: Superficial injury of wrist, hand and fingers (Chapter 19, injury block S60-S69)
• .3 – Subcategory: Other superficial injuries of thumb (this level names the site)
• 1 – Injury type: Abrasion, which gives the S60.31 level, abrasion of thumb
• 2 – Laterality: Left (1 = right, 9 = unspecified)
• D – 7th character: Subsequent encounter (active follow-up care after the initial treatment phase)

The full parent code is S60.312, which cannot be used on its own for billing. A 7th character is mandatory. Each position narrows the one before it, and the abrasion level sits at S60.31 rather than at S60.3.

How the 7th character works: A, D and S compared

The 7th character is where superficial injury coding most often goes wrong. Many coders default to A (initial encounter) regardless of visit context, which creates a mismatch between the claim and the clinical note.

Per ICD-10-CM Official Guidelines Section I.C.19, the subsequent encounter designation applies for as long as the patient is receiving active care for the injury. That holds even if the original treating provider no longer sees them. The coding guidance from the CMS ICD-10 codes page confirms this reading for Chapter 19 injury codes.

S60.312D code hierarchy within ICD-10-CM

Knowing where S60.312D sits in the code hierarchy helps coders navigate related codes quickly and catch parent-level exclusion notes that might apply.

Other superficial injury codes in the S00-T88 block follow the same hierarchical logic. The ICD-10-CM code index is where to check a neighboring wrist or finger site before the claim goes out.

Related ICD-10 codes: Laterality and encounter variants

S60.312D is one of nine billable codes in the S60.31 abrasion of thumb subcategory. Payers check laterality carefully, and using the unspecified code when the affected side is documented creates an avoidable query.

Use the AAPC ICD-10-CM code lookup to verify the laterality family for any superficial injury code. It also covers the adjacent finger codes, S60.4- through S60.9-, if they appear on the same claim.

Approximate synonyms and clinical documentation terms

Clinical notes rarely use the exact ICD-10-CM descriptor phrase. These are the documentation terms that map to S60.312D and support accurate code assignment from chart text.

• Abrasion of left thumb, follow-up visit
• Left thumb skin abrasion (subsequent care)
• Scrape of left thumb (follow-up)
• Left thumb surface wound, subsequent encounter
• Left thumb grazing injury (follow-up)
• Superficial wound left thumb, subsequent care
• Left thumb friction injury (subsequent encounter)

When abstracting from clinical notes, coders should confirm both laterality (“left”) and encounter context (“follow-up,” “wound check,” “subsequent”) before assigning S60.312D. Documentation that is ambiguous about laterality requires a provider query rather than defaulting to S60.319D (unspecified). Digital clinical forms that prompt for laterality at the point of care reduce abstraction errors downstream.

Clinical information and coding notes for S60.312D

Three areas generate the most coding questions on superficial thumb injuries: the Excludes2 note, laterality selection, and the encounter-type transition from A to D.

Excludes2 note: Abrasion of wrist and hand (S60.81-)

An Excludes2 note means the excluded condition is not part of the coded condition, but both can be reported together when documented. A patient may present for follow-up care with both a left thumb abrasion and a separate hand abrasion. Report S60.312D and the appropriate S60.81- code together. This is different from an Excludes1 note, which prohibits dual reporting.

Laterality selection rules

ICD-10-CM instructs coders to assign the most specific code when laterality is documented. If the note clearly states “left thumb,” S60.312D is the correct code.

S60.319D (unspecified) is only appropriate when the provider has not documented which thumb is affected and a query is not feasible. Recording laterality in every encounter note removes the need for that query.

When the encounter type transitions from A to D

The transition from S60.312A (initial encounter) to S60.312D occurs when the patient returns for follow-up care after the first active treatment visit. There is no fixed number of days.

The clinical context sets the encounter type. A wound check three days after the initial injury is S60.312D. A review step that checks the 7th character against the visit date and the note context catches the error before submission.

When to use S60.312D vs S60.312A vs S60.312S

This decision table covers the three most common clinical scenarios coders encounter when coding left thumb abrasions across a care episode.

Consistent encounter-type selection across the care episode prevents claim mismatches between the first visit and the follow-ups. All of them carry the same injury code, so only the 7th character tells them apart.

How Pabau supports accurate ICD-10-CM coding and claim submission

Selecting the right 7th character is a documentation problem before it is a coding one. When the encounter type is captured in a structured note at the point of care, the coding decision is already made.

Pabau is an all-in-one practice management system with claims and billing built in. Its claims management software supports ICD-10-CM code entry and generates CMS-1500 claims from the encounter record. Through the Claim.MD clearinghouse integration, practices submit claims electronically to thousands of US payers. Real-time eligibility checks and electronic remittance advice (835) close the billing loop.

A clean claim submission for S60.312D needs the encounter type, the laterality and the Excludes2 context to match the note. Any mismatch between the note and the claim form is what the payer queries. Connecting the note, the code and the submission in one system removes the handoff where 7th character errors appear.

Streamline ICD-10 claim submission with Pabau

Pabau integrates with the Claim.MD clearinghouse, supporting CMS-1500 and UB-04 submission for ICD-10-CM codes including S60.312D. Book a demo to see how accurate code documentation and automated claim workflows reduce denials.

Book a demo

Conclusion

Two errors account for most S60.312D queries. The first is using A for a follow-up visit. The second is defaulting to S60.319D when the note already documents the left thumb.

Both are caught by the same habit. Read the note for laterality and encounter context before you pick the 7th character. Query the provider when either one is missing.

Practices that build that check into the claim workflow stop submitting superficial injury claims twice. Book a demo to see how Pabau keeps the encounter note, the code and the CMS-1500 claim in step.

Continue your research

Need the fundamentals of the billing cycle? What is revenue cycle management covers the path from encounter to payment.

Want fewer denials on injury claims? Denial management in healthcare lists the common denial reasons and how to resolve them.

Coding to a documentation standard? Medical billing compliance sets out the record-keeping that survives a payer audit.

Filing a follow-up claim late? Timely filing limits explains each payer’s submission window and how to protect it.

Frequently asked questions