ICD code W56.32XD – Struck by other marine mammals

Key takeaways

W56.32XD is a billable ICD-10-CM external cause code for follow-up visits after a seal, porpoise, manatee, walrus, or similar marine mammal strikes a patient.

Dolphin, sea lion, and orca strikes have their own codes (W56.02-, W56.12-, and W56.22-), so W56.32 never covers them.

The 7th character D marks the healing phase after active treatment ends. Use XA for the initial active-treatment visit and XS for sequela.

W56.32XD never stands alone. Pair it with the S-chapter injury code, such as a contusion or laceration, which goes first on the claim.

Practice management software like Pabau checks each claim for missing details before it’s sent, so fewer external cause claims come back rejected.

ICD-10 code W56.32XD: Definition and billable status

ICD-10 code W56.32XD is the billable ICD-10-CM code for a patient struck by other marine mammals, presenting for a subsequent (follow-up) encounter.

It sits in Chapter 20, External causes of morbidity (V00-Y99), under section W50-W64, Exposure to animate mechanical forces. Its parent category is W56, Contact with nonvenomous marine animal.

According to the CDC/NCHS ICD-10-CM web tool, W56.32XD is valid for FY2025 and FY2026, with FY2026 effective October 1, 2025. No deletions or revisions are scheduled. The parent code W56.32 isn’t billable on its own, because every code in this category needs a 7th character.

What does the 7th character ‘D’ mean?

The 7th character D means the patient is presenting for a subsequent encounter. The ICD-10-CM Official Guidelines define that as a visit during the healing or recovery phase, after active treatment for the injury has ended. It doesn’t mean a second injury event. It tells the payer this visit is routine follow-up care.

Three 7th characters are valid for W56.32. Each maps to a distinct phase of care, and mixing them up is a common cause of denials on external cause claims.

A subsequent encounter doesn’t require a set number of days to pass. What decides it is whether active treatment has ended. Say a patient leaves the ED and sees their primary care provider five days later for a wound check. That visit is a subsequent encounter, even if the wound hasn’t fully healed.

Which marine mammals are covered under W56.32?

W56.32 covers marine mammals that don’t have a subcategory of their own. Dolphins (W56.0-), sea lions (W56.1-), and orcas (W56.2-) each have separate codes, which is why the ICD-10-CM Tabular List calls this group “other marine mammals.” W56.32 applies to nonvenomous marine mammals including:

• Porpoises
• Seals
• Manatees
• Walruses

So a dolphin strike codes to W56.02- and a sea lion strike to W56.12-, never to W56.32. The chart below walks through the three choices that lead to W56.32XD.

W56.32 covers being “struck by” these animals only. A bite codes to W56.31 (Bitten by other marine mammals). Contact without a strike or bite codes to W56.39 (Other contact with other marine mammals). The distinction matters because some payers audit external cause code specificity during utilization review.

Every animal in category W56 is classified as nonvenomous, per the category header, so no species under W56.32 counts as venomous.

W56.32XD vs neighboring codes: How to choose correctly

Coders most often confuse W56.32XD with two kinds of codes. One is the wrong 7th character, such as XA coded when the patient is in follow-up. The other is the wrong subcode, such as W56.39 for contact instead of W56.32 for a strike, or W56.32 used for a dolphin. The table below maps the key decisions, based on the AAPC ICD-10-CM code lookup.

Always add a companion S-chapter injury code to identify the nature of the injury. A patient returning for a wound check after a seal strike that caused a skin laceration carries both codes. The S-chapter laceration code is the primary diagnosis, and W56.32XD follows it.

When to use W56.32XD: Clinical scenarios

Each scenario below involves a patient who has already received initial treatment and is now in the follow-up phase of recovery.

• Wound check after a seal strike: A patient struck by a seal during an open-water swim was treated in the ED. Five days later, they return to a primary care practice for a suture check. This visit codes W56.32XD alongside the S-chapter laceration code as the principal diagnosis.
• Physical therapy for bruising: A patient struck by a manatee while snorkeling has significant soft-tissue bruising and is referred to physical therapy. The PT visit falls in the healing phase, so W56.32XD applies with the appropriate contusion code.
• Outpatient follow-up for rib injury: A marine researcher struck by a harbor seal returns for follow-up imaging at an outpatient radiology center. The scan confirms healing of a previously identified rib injury. W56.32XD accompanies the rib fracture follow-up code.
• Occupational medicine visit: An aquarium trainer sees occupational medicine two weeks after a work-related strike by a walrus. Active treatment is complete and this is routine follow-up, so W56.32XD is correct.

In each scenario, the external cause code describes the mechanism. The injury itself, whether a laceration, contusion, or fracture, carries the S-chapter principal diagnosis code. W56.32XD never stands alone.

Documentation requirements for W56.32XD

External cause codes need specific clinical documentation to survive payer audit. Assigning W56.32XD without it can trigger a retroactive denial during compliance reviews. The medical record should contain these elements before the code is assigned:

• Prior initial encounter documented: The record must show that active treatment happened at an earlier visit. A reference to the ED visit, urgent care note, or initial treating provider’s record satisfies this.
• Encounter type confirmed as follow-up: The clinical note should state that this is a follow-up, wound check, PT visit, or similar post-treatment encounter. It shouldn’t describe the visit as the presenting injury event.
• Mechanism of injury recorded: Note the marine mammal species and the activity, such as a recreational swim, occupational exposure, or marine research. The species decides the subcode, because a dolphin or sea lion strike codes elsewhere. Per CMS ICD-10-CM guidance, external cause code specificity is encouraged where documentation permits.
• Body part and injury nature: A documented injury description must support the primary S-chapter code. An external cause code with no matching injury diagnosis gives the payer grounds to deny the claim.
• Place of occurrence and activity codes: Some commercial, liability, and workers’ compensation payers require Y93 (activity) and Y92 (place of occurrence) codes alongside W56.32XD. Check payer contracts or EDI companion guides for their requirements.

Payer rules and reimbursement considerations

W56.32XD is an external cause code, so it describes how an injury happened. The injury itself is coded separately, and that split has direct reimbursement implications. Under the WHO ICD-10 framework and CMS implementation guidance, external cause codes don’t drive payment directly. Payment rests on the companion S-chapter injury code.

Payer requirements differ by line of business:

• Medicare and Medicaid: Traditional Medicare accepts external cause codes but generally doesn’t require them for claim processing. Medicare Advantage plans and state Medicaid programs may add their own requirements, so check the plan’s EDI companion guide.
• Commercial payers: Most accept external cause codes as supplementary information. Some require Y92 place-of-occurrence and Y93 activity codes alongside them, so check payer-specific policies before submission.
• Liability and workers’ compensation: These payers typically require external cause codes to determine cause of injury. A workers’ compensation claim carrying W56.32XD, such as an aquarium or marine research workplace injury, should include the matching place-of-occurrence code.

Common claim denial reasons for W56.32XD

External cause codes draw denials when billing teams treat them as administrative add-ons instead of coded fields that need checking. The denial patterns for W56.32XD are predictable, and they cluster around six failure points.

• Wrong 7th character submitted: Using W56.32XA (initial) instead of W56.32XD (subsequent) is a common coding error. A coder who defaults to XA for a follow-up visit risks a denial or a flag. Check the encounter type in the note before assigning the code.
• External cause code submitted as sole diagnosis: W56.32XD without a companion S-chapter injury code will be rejected. Payers expect the primary injury diagnosis, such as a laceration, contusion, or fracture, to drive payment. Without it, the claim has no clinical justification for the visit.
• Outdated or incomplete code: A code from a prior fiscal year’s code set, or W56.32 without its 7th character, generates an invalid code rejection. Confirm the code comes from the current FY2026 code set, effective October 1, 2025.
• Wrong species subcode: A note describing a dolphin or sea lion strike doesn’t support W56.32XD. Those strikes code to W56.02- and W56.12-, so the claim and the note disagree.
• Missing place-of-occurrence code: Some payer contracts require a Y92 place-of-occurrence code with external cause codes on certain claim types, especially liability and workers’ comp. Leaving it off triggers a denial, and the remittance gives the reason with one of the standard medical billing denial codes.
• Documentation inconsistency: A clinical note that reads “first visit for this injury” paired with W56.32XD triggers an audit flag. The encounter type in the note must match the 7th character on the claim.

Teams seeing repeat denials on external cause codes can work through a clean claim submission checklist before batching these claims. Each failure point above can be caught at the pre-submission scrub stage.

How claims management software prevents W56.32XD denials

Without automated checks, external cause codes get reviewed by hand, if at all. A coder who picks the unbillable parent W56.32 instead of W56.32XD often finds out only when the rejection comes back.

Practice management software like Pabau runs validation checks every time a claim is sent. Its claims management software confirms the details insurers need are in place. If something is missing or doesn’t match, the Send button stays disabled until the claim is complete.

In the US, Pabau connects to the Claim.MD clearinghouse. Your team can run real-time eligibility checks, submit claims electronically to thousands of payers, and track each claim’s status from one dashboard. Denied claims are flagged for rework, so a claim missing its Y92 code gets fixed and resubmitted quickly.

Catch external cause code errors before submission

Pabau checks every claim for missing details before it’s sent. Denied claims get flagged for rework, so W56.32XD errors don’t cost you a payment cycle.

Book a demo

Conclusion

W56.32XD is simple to assign once three choices are settled: the animal, the mechanism, and the visit type. Confirm the species first, because a dolphin or sea lion strike never belongs here. Then check that active treatment has ended before choosing D over A.

External cause codes rarely pay on their own, but they can still sink a claim. Pair W56.32XD with its S-chapter injury code every time, and add Y92 and Y93 codes wherever the payer asks for them.

Book a demo to see how Pabau checks claims for missing details before they reach the payer.

Continue your research

Need help with external cause code denials? Denial management in healthcare covers how to build a systematic process for identifying and appealing common external cause code rejections.

Want to understand the full clearinghouse submission process? Pabau’s Claim.MD clearinghouse guide explains how electronic claims are checked and routed to thousands of US payers.

Looking for broader coding context? Medical billing fundamentals covers how diagnosis codes, external cause codes, and companion codes work together in a compliant claim.

Preparing for a payer audit? Medical billing compliance explains the documentation and coding checks that keep external cause claims defensible.

Want the bigger picture? What is revenue cycle management shows where coding accuracy fits between patient intake and final payment.

Frequently asked questions

Billing and payer questions