ICD code S61.340D – Puncture wound with foreign body of right index finger with damage to nail

Key takeaways

ICD-10 Code S61.340D describes a puncture wound with foreign body of the right index finger, with damage to the nail, at a follow-up encounter

Nail status sits in the 4th character, so S61.240D is the sibling to rule out first. S61.3- codes mean the nail was damaged, and S61.2- codes cover the same wound with the nail intact

This is a billable, specific ICD-10-CM code valid for FY2026 HIPAA-covered transactions, effective October 1, 2025

The 7th character D is required for a subsequent encounter. Using A or S at a follow-up visit is a common and costly miscoding error

Pabau’s built-in ICD-10 code library helps clinicians select the correct encounter-specific code at the point of documentation

ICD-10 Code S61.340D: definition and billable status

ICD-10 Code S61.340D is the billable code for a follow-up visit after a puncture wound of the right index finger. The wound involved a foreign body, and the injury also damaged the nail. Using S61.340A at that follow-up visit is the coding error that generates the rejection.

This reference covers the official description, billable status, 7th character rules, code hierarchy, sibling codes, and documentation requirements. It also covers the nail-damage distinction that separates the S61.34- codes from their nail-intact S61.24- counterparts. All information reflects the CMS ICD-10-CM FY2026 update, effective October 1, 2025.

S61.340D at a glance

The table below covers every field a coder or biller needs before submitting a claim with ICD-10 Code S61.340D.

Understanding the 7th character D: subsequent encounter

The CDC/NCHS ICD-10-CM Official Guidelines define three encounter types for injury codes, each controlled by the 7th character. Choosing the wrong one at the wrong visit is the most common reason finger wound claims are rejected.

• A – Initial encounter: the patient is receiving active treatment for the injury. This is typically the emergency department or urgent care visit where the wound is first assessed. The foreign body is usually addressed at that visit too.
• D – Subsequent encounter: the patient returns for routine follow-up while the wound is still healing. Wound checks, suture removal, and aftercare visits all fall under the D suffix. The treating provider does not have to be the one who managed the initial encounter.
• S – Sequela: a late effect or complication that arises after the healing phase is complete. Examples include scarring or reduced range of motion in the finger.

“Subsequent encounter” does not mean a second visit to the same clinician. It means the injury has passed the initial acute-treatment phase. A patient seen at urgent care on Monday takes A. The same patient seen for a wound check on Wednesday takes D.

When to use S61.340D vs S61.340A vs S61.340S

Puncture wound with foreign body: documentation requirements for S61.340D

Every element of the ICD-10 Code S61.340D description must be supported by the clinical record. Missing any one element gives a payer grounds for a query or a denial.

• Wound type: the record must confirm a puncture wound, not a laceration or abrasion. Puncture wounds have a small entry point relative to their depth. Lacerations have torn or cut edges. The distinction changes the code entirely.
• Foreign body: the provider must document that a foreign body was present. It does not matter whether it was removed at a prior encounter or is still being monitored. A note recording only “injury” will not support S61.340D.
• Laterality: right hand, right index finger. Left index finger maps to a different code family (S61.341x). Unspecified laterality codes exist but should be avoided when documentation allows specificity.
• Nail status: the record must confirm damage to the nail – splitting, avulsion, subungual hematoma, or nail bed injury. If the nail is intact, the S61.24x series applies instead, and the right index finger code becomes S61.240D.
• Encounter type: the note must reflect follow-up or aftercare context (wound check, progress assessment, dressing change) rather than an initial acute evaluation.

With damage to nail: why this distinction matters

The nail-damage distinction is carried by the 4th character, so it decides whether the claim sits in the S61.2 or the S61.3 subcategory. Payers also check that choice against the wound care procedure codes on the same claim.

If the initial encounter note documents subungual hematoma, nail avulsion, or splitting, the S61.34x codes apply across the whole episode of care. If the nail was never involved, S61.240D is the correct subsequent-encounter code and S61.340D will not be supported by the record. S61.350D is not the alternative here. That code covers an open bite of the right index finger with damage to nail, a different wound mechanism.

S61.340D code hierarchy and classification

Understanding the full code tree helps coders navigate sibling codes quickly. It also prevents assignment of a non-specific parent code when a billable child code exists.

The parent code S61.340 is not billable on its own. A 7th character is always required. Submitting S61.340 without the encounter suffix will be rejected by payers and clearinghouses as an invalid code.

Related and sibling codes for open wound of right index finger

The S61.340 family covers puncture wounds with foreign body of the right index finger with damage to the nail. Each sibling code differs from S61.340D at exactly one character position, and the map below shows which position carries which clinical fact.

Coders working across a patient episode, across lateralities, or across nail status need the sibling codes below. Our ICD-10-CM code library indexes the wider S61 range, and the AAPC Codify ICD-10-CM lookup carries the official descriptions.

Approximate synonyms and index references for S61.340D

The following clinical terms and index references map to ICD-10 Code S61.340D in the ICD-10-CM Alphabetic Index. Documenting any of these in the clinical note supports code selection:

• Puncture wound of right index finger with retained foreign body and nail damage, subsequent encounter
• Foreign body wound, right index finger, nail bed involved, follow-up visit
• Penetrating wound with foreign object, right index finger, damaged nail, subsequent
• Right index finger injury with foreign body and subungual hematoma, aftercare

Coding tips and common errors with ICD-10 Code S61.340D

Wrong-encounter-type errors account for a disproportionate share of injury code denials. A documentation checklist built into the pre-claim workflow catches them before the claim goes out.

• Wrong laterality: right vs left index finger is not interchangeable. S61.340D is right-side only. Always confirm laterality from the clinical note before coding.
• Wrong encounter type: using S61.340A at a wound check or suture removal visit is the most common error. The patient has already passed the initial encounter stage.
• Missing foreign body specificity: the record must mention a foreign body, even one removed at the initial visit. Without it, use S61.330D instead, which covers a puncture wound without foreign body.
• Nail-status mismatch: review the initial encounter note. If the nail was never damaged, the episode belongs to S61.240D, not S61.340D. S61.350D is an open bite code and is never the nail-damage version of a puncture wound.
• Non-billable parent code submitted: S61.340 without the 7th character is not a valid submission code. Every claim must carry the full 7-character code.

Practices managing a high volume of hand injury follow-ups benefit from coding templates that enforce 7th character selection before the claim leaves the system. Catching the pattern at documentation is faster and cheaper than working the denial afterwards.

Billing S61.340D: submission and reimbursement context

S61.340D is a diagnosis code, not a procedure code. It supplies the medical necessity for the service billed at the follow-up visit. It carries no RVU or payment amount of its own.

Key billing considerations for S61.340D claims:

• The service is usually an E/M or wound care visit: subsequent encounters are normally billed as an office or outpatient E/M service. A wound check or dressing change works the same way, with S61.340D attached as the supporting diagnosis.
• Foreign body removal belongs to the encounter where it happened: subcutaneous removal is reported with CPT code 10120 or 10121. Those codes go on the visit where the removal is performed, normally the initial encounter carrying S61.340A.
• Nail damage can bring a second service into scope: drainage of a subungual hematoma and nail bed repair are separate procedures. Each carries its own CPT code. Document the nail work explicitly so the diagnosis and the procedure agree.
• Payer policy still applies: CMS and commercial plans pay these services under standard outpatient rules. Individual payers may still require prior authorization or specific documentation. Verify coverage before the visit wherever possible.

Claims carrying S61.340D go out on the standard 837P professional transaction. Running real-time eligibility checks before the follow-up visit reduces post-service billing disputes. That matters most on injury episodes that span several encounters.

ICD-9-CM crosswalk for S61.340D

ICD-9-CM was retired in the US on October 1, 2015. Crosswalk lookups still matter for legacy data analysis, audits of pre-2015 claims, and reporting that spans the transition.

ICD-9-CM had no axis for laterality, for the digit injured, or for nail involvement. Every mapping between S61.340D and an ICD-9 code is therefore an approximation. The reverse direction does not return S61.340D either, since 883.1 maps back to a far less specific S61 code. Treat these rows as analysis aids rather than billing equivalents.

How Pabau supports accurate ICD-10 documentation

Most ICD-10 reference pages stop at the descriptor. Coders using a static lookup still cross-check the encounter type, laterality, and nail status by hand. That check happens against a separate clinical note, before the claim is built.

Practice management software like Pabau keeps the ICD-10 code library inside the clinical documentation workflow. When a clinician documents the follow-up visit, the code search returns encounter-specific options with the 7th character visible. That reduces the chance of picking S61.340A for a visit that should carry S61.340D. The claims management software then checks the claim for required fields before submission.

For US practices billing through insurance, Pabau’s Claim.MD clearinghouse integration connects to thousands of US payers. Claims carrying S61.340D run through real-time eligibility checks before they reach the payer. Electronic remittance advice returns with CARC denial reason codes, so a denial that traces to the wrong encounter suffix is easy to spot.

The audit trail Pabau creates links the clinical note, the selected ICD-10 code, and the submitted claim. That record supports both internal review and external audits. A billing workflow that runs through one system is harder to misconfigure. The alternative spreads the same job across a clinical note, a manual lookup, and a separate billing platform.

Tired of encounter-type denials?

Pabau’s built-in ICD-10 code library surfaces 7th character options at the point of documentation. Your team picks the right encounter suffix before the claim is built.

Book a demo

Conclusion

Two fields decide whether an S61.340D claim survives. One is the 7th character, and the other is the nail finding recorded at the initial encounter. Confirm both before the claim leaves the practice.

A nail-intact record belongs to S61.240D, and a follow-up visit never takes S61.340A. Get those two calls right and the rest of the S61.34x family follows from the note you already have.

Pabau keeps the encounter suffix visible while the note is being written. Book a demo to see how that fits your practice’s follow-up workflow.

Continue your research

Need to understand the full claims submission process? Medical billing workflows explained covers the end-to-end process from documentation to payment posting.

Dealing with rejected claims after the fact? Denial management in healthcare outlines how to track, appeal, and prevent denials by root cause.

Want to understand how clearinghouses validate your claims? How a medical claims clearinghouse works explains the role Claim.MD plays in claim routing to payers.

Frequently asked questions