ICD-10 Code S60.159D: Contusion of unspecified little finger with damage to nail

Key Takeaways

S60.159D is a billable ICD-10-CM code for contusion of the unspecified little finger with damage to nail, subsequent encounter – valid for FY2026 claims from October 1, 2025.

The 7th character D signals a follow-up visit: active treatment is ongoing but the patient is no longer presenting for the initial acute encounter.

Documentation must confirm the little finger, nail involvement, and that the encounter is a subsequent (not initial or sequela) visit – missing any element risks a claim denial.

Pabau’s claims management software supports accurate ICD-10-CM code submission on both UB-04 and CMS-1500 claim forms.

ICD-10 Code S60.159D describes a contusion of the unspecified little finger with damage to the nail, coded at a subsequent encounter. It is a billable, specific ICD-10-CM code valid for reimbursement under the 2026 edition, which became effective on October 1, 2025. Coders and billing staff use this code when a patient returns for follow-up care after an initial little-finger contusion with nail involvement has already been documented and treatment has begun.

The code is accepted on both UB-04 (institutional) and CMS-1500 (professional) claim forms, making it valid across hospital outpatient and physician office settings. Because ICD-10-CM codes are updated each October 1, confirm the code’s active status against the CDC/NCHS ICD-10-CM web tool before submitting claims for any fiscal year beyond FY2026. Note that billable status does not guarantee payer reimbursement – coverage depends on the individual plan and medical necessity documentation.

What does S60.159D mean? Breaking down the code

Each segment of ICD-10 Code S60.159D carries a distinct clinical meaning. Understanding the structure helps coders select the right code and avoid the common mistake of using the initial-encounter suffix when the patient is returning for ongoing care.

The “unspecified” in S60.159D reflects that the clinical record does not document whether the left or right little finger was injured. Where laterality is documented, coders should use S60.151 (right) or S60.152 (left) instead. Using the “unspecified” variant without checking the record first is a common audit risk; accurate clinical record documentation reduces that exposure.

Understanding the 7th character: Initial vs. subsequent vs. sequela

The 7th character is the most frequently misapplied element in the S60 code family. According to the CMS ICD-10-CM coding guidelines, the suffix chosen must reflect the actual status of the encounter, not the stage of healing.

A key point that confuses many coders: a patient can still be in a subsequent encounter (D) even if their condition has not fully healed. The D suffix applies any time the patient is returning for routine follow-up care, physical therapy check-ins, or wound monitoring, as long as active treatment is being provided. Only after the injury is considered resolved and a late-effect complication presents separately does the sequela suffix (S) become appropriate. Billing teams handling HIPAA-covered transactions should build this distinction into their coder training to avoid suffix errors at claim submission.

Clinical description: contusion of the little finger with nail damage

A contusion is a bruise caused by blunt force trauma without breaking the skin. In the context of ICD-10 Code S60.159D, the injury affects the fifth (little) finger and involves damage to the nail – typically subungual hematoma (blood collecting beneath the nail plate), nail-bed laceration, partial nail avulsion, or pressure injury to the nail matrix.

Common mechanisms include crush injuries (doors, machinery, heavy objects), sports impacts, and workplace accidents. Clinicians treating these presentations in urgent care, occupational health, or sports medicine settings will encounter this code regularly during follow-up visits.

• Subungual hematoma: blood pooling under the nail, often requiring trephination for drainage
• Nail-bed injury: disruption to the tissue beneath the nail plate requiring monitoring for deformity
• Nail avulsion (partial): portion of the nail plate detached from the nail bed
• Contusion without disruption: bruising and soft-tissue swelling at the fingertip with visible nail discolouration

For subsequent visits, the provider note should confirm that the nail injury is still being actively managed (for example, a wound check after nail trephination or a suture removal visit). Practices using digital intake forms for returning patients can prompt clinicians to re-document the injury site, laterality, and current treatment stage at every follow-up, making it easier to support the D suffix at coding time.

Code hierarchy and parent codes for S60.159D

S60.159D sits within a well-defined hierarchy under the S00-T88 block covering injuries. Understanding this structure helps coders verify they have the most specific code available before submitting a claim. The AAPC ICD-10-CM code lookup presents this hierarchy visually for quick navigation.

S60.159 itself is not billable – only the 7th-character variants (A, D, S) can be submitted on a claim. Coders should never submit S60.159 without its suffix, as payers will reject it as a non-specific code.

Related and sibling codes

Several sibling codes sit alongside ICD-10 Code S60.159D within the S60.15 subcategory. These cover laterality variants and the three encounter types. Selecting the wrong sibling, particularly confusing “right” and “left” or using the initial-encounter code at a follow-up visit, is a top denial trigger for this code family. Practices that track claim patterns through claims management software can identify which sibling codes generate the most rework and target coder education accordingly.

For finger contusions without nail involvement, see the S60.0 subcategory (contusion of finger without damage to nail). If the provider notes crush injury to the nail with a concurrent open wound, a separate wound code may be required in addition to the contusion code. Practices managing physical therapy follow-up visits for hand injuries will frequently rotate between the A, D, and S variants of this code family across a single episode of care.

Approximate synonyms and index terms

Medical coders searching by clinical description rather than code number use these approximate synonyms. Each maps to ICD-10 Code S60.159D and its parent S60.159. Recognising these terms in provider notes accelerates lookup and reduces the risk of selecting an incorrect code. The ICD List lookup tool indexes many of these synonym terms for quick retrieval.

• Bruised little finger with nail damage, follow-up visit
• Contusion of pinky finger with nail injury, subsequent encounter
• Contusion of fifth finger with damage to nail, subsequent encounter
• Little finger nail contusion, subsequent encounter
• Bruised fingernail, little finger, follow-up
• Subungual hematoma, little finger, subsequent encounter
• Pinky finger blunt trauma with nail involvement, follow-up

Documentation requirements for accurate coding

Claim denials for this code almost always trace back to missing or ambiguous documentation. The clinical note must support all four elements the code communicates: the injury type (contusion), the specific finger (little/fifth), the nail involvement, and the encounter stage (subsequent). Getting healthcare documentation practices right at the point of care prevents downstream rework.

• Injury type: the note must confirm blunt force/crush mechanism without an open wound (or, if a wound is present, the open wound code must be added separately)
• Finger specificity: “little finger,” “fifth digit,” or “pinky” – all acceptable; the coder resolves to S60.15x. If the provider names the finger plus a side (left or right), use S60.151 or S60.152 rather than the unspecified S60.159.
• Nail involvement: explicit mention of nail damage, subungual hematoma, nail discolouration, or nail-bed trauma is required to justify S60.1 (with damage to nail) vs. S60.0 (without)
• Encounter stage: language such as “return visit,” “wound check,” “follow-up,” or “suture removal” supports the D suffix. Absence of this language may prompt payer review.

Practices using structured ICD-10-CM coding workflows for injury follow-ups reduce the rate of unspecified coding by prompting providers to document laterality and encounter context at every visit.

Coding guidelines and compliance tips for S60.159D

These practical reminders address the most common compliance issues coders encounter when working the S60.15x code family. Official guidance is published annually by CMS and the NCHS in the ICD-10-CM Official Guidelines for Coding and Reporting.

• Do not default to A at follow-up: the initial-encounter suffix (A) is appropriate only for the first time the provider actively treats the injury. If the patient has been seen previously for the same injury, D is correct even if a different provider is seeing them this visit.
• Check for laterality before selecting “unspecified”: S60.159D should only be used when the provider genuinely does not document which hand was injured. If the note says “right pinky” or “left fifth finger,” do not use the unspecified code.
• Sequela requires a separate code: when coding S60.159S (sequela), a secondary code for the nature of the late effect (for example, scar contracture, nail deformity) must also be reported.
• Billable does not mean covered: verify payer-specific policies for injury follow-up visits. Medicare, Medicaid, and commercial payers may have different medical necessity thresholds for subsequent encounter visits.
• Annual update check: ICD-10-CM codes are revised every October 1. Confirm S60.159D remains active in the fiscal year of service using the official CDC/NCHS code lookup.

Clinics that manage high volumes of occupational or sports injury follow-ups benefit from configuring structured ICD-10 reference workflows into their billing systems. Pabau’s claims management software helps practices submit ICD-10-CM codes accurately on both UB-04 and CMS-1500 forms, reducing the manual error rate at claim generation.

Reduce claim errors on injury follow-up codes

Pabau's claims management software supports accurate ICD-10-CM code submission, helping billing teams get subsequent encounter codes right the first time.

Book a demo

Conclusion

Most claim issues with S60.159D come down to three documentation gaps: missing laterality, the wrong encounter suffix, and absent nail-involvement language. Solving all three requires a short note – and a short note is only possible if the provider has a clear prompt at the point of care.

Pabau’s digital forms let you build injury follow-up templates that prompt for laterality, encounter stage, and nail status every time – cutting unspecified-code submissions before they reach the billing team. To see how this works in practice, book a demo.

Continue your research

Managing injury billing across multiple visit types? Intraparenchymal hemorrhage ICD-10 codes covers another high-complexity injury code family with similar 7th-character considerations.

Need to understand HIPAA compliance for your billing workflows? HIPAA compliance checklist for primary care outlines the requirements every billing team must meet before submitting HIPAA-covered transactions.

Running a sports medicine or occupational health practice? Sports medicine software shows how Pabau supports high-volume injury follow-up workflows from scheduling through claim submission.

Frequently Asked Questions