ICD code S40.261D – Nonvenomous insect bite, right shoulder

Key takeaways

S40.261D is the billable ICD-10-CM code for a nonvenomous insect bite of the right shoulder at a follow-up visit.

Use S40.262D for the left shoulder, and S40.269D only when the record never names a side.

The 7th character ‘D’ belongs on every visit after the first one where active treatment was given.

The note must state right shoulder laterality, the nonvenomous nature of the bite, and the prior encounter.

Pabau, the practice management platform we build, validates each claim before submission and shows the payer’s rejection reason.

ICD-10 Code S40.261D: Code details at a glance

ICD-10 Code S40.261D is the billable diagnosis code for a nonvenomous insect bite of the right shoulder at a follow-up visit. It sits in the S40-S49 block, injuries to the shoulder and upper arm, within Chapter 19 of ICD-10-CM. The table below is the quick-reference data for the code.

ICD-10 Code S40.261D breaks down character by character:

• S40 – superficial injury of shoulder and upper arm
• .26 – insect bite, nonvenomous, of shoulder
• 1 – right shoulder
• D – subsequent encounter

Confirm the breakdown against the CDC/NCHS ICD-10-CM web tool for the current fiscal year before submitting claims.

What S40.261D covers: Clinical description

S40.261D covers a nonvenomous insect bite on the right shoulder or deltoid region. It applies at a visit where the patient is receiving routine care during healing or recovery. The key clinical criteria are:

• Bite location: right shoulder, including the deltoid region and right upper arm proximal to the elbow
• Bite nature: nonvenomous – no toxic effect, no envenomation. The insect caused a skin surface wound without venom injection
• Encounter type: subsequent – the patient is not presenting for the first time with this injury; active treatment began at an earlier visit
• Injury depth: superficial – the S40 block covers superficial injuries. A bite that penetrates deeper structures requires a different code family

The superficial classification is important. S40.261D is a non-penetrating wound code. If the bite resulted in an open wound requiring debridement or suture, the S41 block (open wound of shoulder) would apply instead. If the patient reports systemic symptoms consistent with envenomation, the T63 venom codes apply instead.

Understanding the 7th character ‘D’: Subsequent encounter rules

The 7th character in ICD-10-CM injury codes signals the episode of care. Getting it wrong is a frequent reason S40.261D claims are denied. Per the ICD-10-CM Official Guidelines for Coding and Reporting, the three options for S40.261x are:

The critical distinction for “D”: the patient does not have to be completely healed. “D” applies whenever the patient is beyond the first active treatment visit, even if healing is ongoing. The question to ask before assigning the suffix is: Has this patient already received active treatment for this specific injury at a prior encounter? If yes, use D. If this is the first time active treatment is being provided, use A.

S40.261A vs S40.261D vs S40.261S: Choosing the right 7th character

A and D get confused often in this code family. Work through this sequence at the point of coding, and the diagram underneath shows the same routing at a glance.

1. Is this the first visit where active treatment for the bite is being provided? Yes = S40.261A. No = proceed to step 2.
2. Is the injury still in the healing phase (not yet fully resolved)? Yes = S40.261D. No (fully healed, patient presenting with a late complication) = proceed to step 3.
3. Is the patient presenting with a late effect, a new condition arising as a consequence of the healed bite? Yes = S40.261S. No = reassess whether the encounter relates to the original injury.

One common misconception: “subsequent encounter” does not mean the patient’s second visit to your practice. It means the second or later visit where treatment for this injury is provided. The practice does not have to be the same one. Say a patient was treated in the ER for the bite, which was coded as the initial encounter. They present to your urgent care five days later for a wound check. That visit takes the D suffix.

Inclusion and exclusion notes for S40.261D

The S40.26x subcategory carries important boundary conditions that define what ICD-10 Code S40.261D can and cannot cover.

• Included: Nonvenomous insect bites of the right shoulder and deltoid region, including mosquito bites, flea bites, and bites from non-toxic insects where no envenomation occurred
• Excluded (code elsewhere): Venomous stings or bites with a toxic effect. Use the T63.4- subcode for the insect, such as T63.441D for a bee or T63.461D for a wasp. Those codes cover the toxic effect of venom from bees, wasps, hornets and other arthropods, subsequent encounter.
• Excluded: Left shoulder bites – use S40.262D
• Excluded: Unspecified shoulder bites – use S40.269D (only when laterality genuinely cannot be determined from the record)
• Excluded: Open wounds of the shoulder – if the bite created a penetrating wound requiring suture or debridement, use S41.x codes
• Excluded: Insect bite of the upper arm below the shoulder. Use the S40.86- codes, such as S40.861D for the right upper arm, subsequent encounter

Codes commonly confused with S40.261D

These neighboring codes sit in the same block or cover overlapping clinical scenarios. Knowing when each applies prevents misassignment.

Documentation requirements to support S40.261D

Payers – including CMS for Medicare and Medicaid – evaluate ICD-10 Code S40.261D claims against the clinical note. The note must substantiate three points: the right site, the nonvenomous nature of the bite, and the follow-up encounter status. A medical billing workflow that catches missing fields before claim submission is far cheaper than chasing denials after the fact.

Required documentation elements:

• Laterality (right shoulder): The physical exam, wound description, or subjective complaint must explicitly state “right shoulder.” “Shoulder” alone does not support S40.261D – it supports only S40.269D (unspecified).
• Nonvenomous bite confirmation: The note should reflect that no envenomation signs were observed (no systemic reaction, no venom-specific treatment administered). If the provider documented a suspected bee sting with local reaction only, clarify that no toxic effect was present.
• Encounter type (subsequent): The record must show or reference a prior encounter where active treatment was initiated. That reference can be direct, such as “patient returns for wound check following initial evaluation on [date]”. A prior visit note in the same record works, and so does a referral letter documenting the initial encounter.
• Treatment provided at this visit: Document what was done, such as wound inspection, dressing change, topical antibiotic application, or patient education on wound care. An undocumented encounter raises a medical necessity question.
• Wound status: Note the current state – healing, open, signs of infection, discharge, surrounding erythema. This supports medical necessity for the follow-up.

A clinical record that templates these fields lowers the documentation burden on providers. It also makes laterality and encounter type routine entries rather than afterthoughts.

Payer requirements and coverage considerations

Medicare and most commercial payers accept ICD-10 Code S40.261D for wound care follow-up visits when medical necessity is established. Coverage expectations vary by payer, but the consistent requirements are:

• Medical necessity for the follow-up: A minor bite that fully resolved at the first visit may not justify a second billable encounter. The clinical note must show why the follow-up was warranted. Active healing, infection risk, complex wound care instruction, or a developing complication all qualify.
• CPT code pairing: S40.261D is a diagnosis code, not a procedure code. It must be paired with a valid CPT or HCPCS procedure code. Wound care follow-ups typically pair with evaluation and management codes (e.g., 99213) or wound care codes. The CPT/ICD pairing must be clinically coherent – an E&M code paired with a minor insect bite diagnosis requires documentation of a clinically meaningful encounter.
• Prior encounter documentation: Some payers may query the prior encounter when none appears on file. A chain break, where the initial encounter was billed under a different payer, provider or system, can complicate subsequent encounter billing. Keep a reference to the original encounter in the record.

Understanding clean claim submission standards before filing reduces rejections on technical grounds (missing fields, invalid code pairs) separately from clinical-necessity denials.

Why S40.261D claims get denied

Revenue cycle teams working on denial management workflows for wound care codes meet these rejection patterns on S40.261D:

• Wrong 7th character (A used instead of D): A frequent error. If the coder selects S40.261A on a follow-up visit because “the patient is still sick,” the claim is coded incorrectly. The A suffix is for the first active treatment visit only – not the first visit where the patient feels unwell.
• Laterality not in the note: The diagnosis is specific to the right shoulder. If the clinical note says only “shoulder” or “upper extremity,” the coder cannot assign S40.261D without physician addendum. Claims submitted with a specific code but a non-specific note create an audit liability.
• Venomous vs nonvenomous not clarified: The provider may have written “bee sting” or “wasp sting” without noting the absence of a toxic effect. The payer can then query whether a T63.4- venom code such as T63.441D (bee) or T63.461D (wasp) applies. The note must reflect that the bite caused only local skin disruption with no systemic reaction.
• No documented prior initial encounter: A payer may deny a subsequent-encounter claim when no initial encounter sits on file. Reference the original visit in the follow-up note.
• CPT/ICD mismatch: Pairing a wound debridement CPT code with S40.261D (a superficial bite that does not require debridement by definition) raises an edit. Match the procedure to what the superficial bite warranted.

Each rejection arrives with a denial reason code, and reading it tells you which of the five you hit.

Three coding scenarios, worked through

These vignettes show correct and incorrect code selection in common clinical situations, which a static lookup table cannot give you.

Scenario 1: correct use of S40.261D

A patient was seen four days ago for a mosquito bite on the right shoulder. At that visit (coded S40.261A), the wound was cleaned and a topical antibiotic was applied. Today the patient returns. The wound shows early healing with mild erythema but no signs of infection. The provider performs a wound check, changes the dressing, and instructs the patient on further home care.

Correct code: S40.261D. This is a follow-up to a documented initial encounter. The site is the right shoulder. The bite is nonvenomous. The note documents the wound status and the treatment provided. The diagnosis supports medical necessity for the follow-up visit.

Scenario 2: Incorrect use of S40.261D

A patient presents for the first time after a flea bite on the right shoulder two days ago. The site is itchy and inflamed, with no sign of infection. The provider prescribes a steroid cream and goes through wound care.

Wrong code: S40.261D. This is the first visit where active treatment is provided, so the 7th character must be A. The correct code is S40.261A. The bite itself fits the S40.261x family, because a flea bite is nonvenomous. Only the encounter character is wrong.

Scenario 3: When S40.261D is not the right code at all

A patient presents for follow-up after a prior shoulder bite. The provider notes the skin is fully healed but the patient has developed a raised scar at the bite site causing discomfort.

Correct code: S40.261S (sequela). The original injury has healed; the current complaint is a late effect of the bite. The scar itself would be coded as a secondary diagnosis using the appropriate scar or keloid code, per ICD-10-CM sequela coding rules.

ICD-10-CM to ICD-9-CM crosswalk

Practices managing legacy records or older payer systems occasionally need an ICD-9-CM equivalent. The approximate crosswalk for ICD-10 Code S40.261D is ICD-9-CM 912.4 (insect bite, nonvenomous, of shoulder and upper arm, without mention of infection).

This mapping is approximate. ICD-9-CM did carry a shoulder and upper arm bite code, but it had no laterality. One code covered both shoulders, so 912.4 cannot tell a payer which side was bitten. The AAPC’s ICD-10-CM crosswalk tool and the CMS General Equivalence Mapping (GEM) files are the sources for verifying crosswalk accuracy before submission. Treat the 912.4 mapping as a starting point, not a confirmed equivalent.

How Pabau keeps S40.261D claims clean before they go out

In most practices the coder assigns S40.261D, the biller raises the claim, and the two only meet again when a rejection lands weeks later. By then the note is cold, and nobody remembers whether the laterality line was in it.

Pabau’s claim validation scrubs each claim for missing or invalid details before it leaves the system. When a payer still rejects one, the claims dashboard flags it as Needs action. It shows the payer’s reason, with a link straight to the field that needs correcting.

US practices submit CMS-1500 claims through Claim.MD, our clearinghouse partner, and can check a patient’s coverage before the visit. Pabau’s claims software for practices then tracks every claim from Pending to Paid on one dashboard. So a run of S40.261D rejections reads as a pattern you can act on, not a stack of separate letters.

Catch a wrong 7th character before submission

Pabau validates every claim for missing or invalid details before it leaves the system. When a payer rejects one, the dashboard shows the reason so you can correct it and resubmit.

Book a demo

Conclusion

S40.261D is not a hard code to assign. It is an easy one to get wrong. A single character and one word in the exam note separate a paid claim from a denied one.

So the fix belongs upstream of the coder. If the note template asks for the side and the encounter history every time, the coder never has to guess. The biller never has to chase an addendum either.

Reviewing your denial history by code is what turns a one-off fix into a habit. Our guide to medical billing compliance is a good place to start. Book a demo to see how Pabau checks claims before they reach the payer.

Continue your research

Need a clearinghouse that validates ICD/CPT pairs before submission? Pabau’s Claim.MD clearinghouse integration covers eligibility checks and CMS-1500 claim submission for US practices.

Want to understand denial codes when S40.261D comes back rejected? Denial codes in medical billing explains CARC reason codes and how to respond to each rejection category.

Looking for guidance on the full claims lifecycle from code to payment? Revenue cycle management covers the end-to-end workflow from eligibility verification through remittance posting.

Frequently asked questions