ICD code V90.32XD – Drowning from crushed fishing boat, subsequent encounter

Key takeaways

V90.32XD is a billable external cause code for drowning or submersion after falling or jumping from a crushed fishing boat, subsequent encounter.

It is always sequenced after the principal diagnosis and is never the first-listed code on a claim.

The 7th character D marks a subsequent encounter, for routine care after active treatment ends. A marks the initial encounter, and S marks a sequela.

The placeholder X in the 6th position is mandatory, and a code string without it is rejected as an invalid format.

Pabau’s claims management software keeps notes, codes and invoices together and sends electronic CMS-1500 claims to US payers through Claim.MD.

ICD-10 Code V90.32XD: Definition, billable status, and code structure

ICD-10 Code V90.32XD is the valid, billable ICD-10-CM code for “Drowning and submersion due to falling or jumping from crushed fishing boat, subsequent encounter.” It is a Chapter 20 external cause code.

It records how the injury happened, while a separate code carries the condition being treated. The code is valid in the current tabular list, per the CDC/NCHS ICD-10-CM web tool.

Check the Excludes1 notes at category V90 before you assign it. They send other scenarios to V92.-, V94.81- and W16.-, and military watercraft accidents to Y36 and Y37.

The code hierarchy starts at Chapter 20 (V00-Y99) and Block V90-V94 (water transport accidents). It then runs Category V90 → Subcategory V90.3 (crushed watercraft) → Code V90.32 (fishing boat) → V90.32XD (subsequent encounter).

That specificity ladder is why vessel documentation matters. Without “fishing boat” in the note, a coder cannot use V90.32 over V90.39 (crushed unspecified watercraft). You can check the neighboring codes on that ladder in our ICD-10-CM code index.

What each part of the V90.32XD descriptor means

Each segment of the descriptor needs its own support in the provider note. Matching the note to each segment prevents the specificity errors behind downcoded or denied claims.

• Drowning and submersion: The mechanism. The patient entered the water and submersion occurred. Near-drowning outcomes, such as pulmonary injury or hypoxic encephalopathy, are coded as the principal diagnosis.
• Due to falling or jumping from: Describes the activity that caused the submersion. The patient left the vessel, either involuntarily (fell) or voluntarily (jumped), and entered the water. A fall on the vessel’s deck is a V93 event instead.
• Crushed fishing boat: Two specifics in one phrase. “Crushed” describes damage to the vessel itself, such as a hull crushed by a collision or by ice. A person caught between a boat and another object is coded to V91.1- instead. “Fishing boat” is the vessel class: a commercial or recreational fishing vessel, as opposed to a merchant ship, sailboat or inflatable craft.
• Subsequent encounter: The episode-of-care designation. Active treatment for the drowning event has concluded; this visit is for routine care, rehabilitation, or ongoing management of sequelae during the healing phase.

The “crushed” qualifier is where coding most often outruns the documentation. The provider note must state that the vessel was crushed, beyond the fact that the patient fell overboard from a fishing boat.

A fire on board points to V90.22- instead, and a simple fall overboard with no damage to the boat points to V92.02-. Coding from assumed circumstances rather than documented ones is a claim risk under CMS ICD-10-CM coding guidance.

The 7th character: When XD applies instead of XA or XS

V90.32 has only five base characters, so ICD-10-CM requires a placeholder X in the 6th position before the episode-of-care character can occupy the 7th. The three valid extensions for this code are XA, XD and XS. Picking the wrong one is a frequent error on watercraft external cause codes.

Decision rule: Is active treatment still ongoing? Use XA. Has care shifted to routine management, rehabilitation, or monitoring? Use XD. Is the patient presenting only because of a long-term consequence of the drowning, with no acute management of the original injury? Use XS. XD fits most follow-up visits after a drowning event.

The placeholder X is mandatory. V90.32D, without the X, is an invalid code. A payer rejects that string as a format error before any clinical review takes place.

Codes commonly confused with V90.32XD

The watercraft injury codes in Chapter 20 trip up coders who search by keyword instead of reading the full descriptor. V90, V91, V92 and V93 share terms like drowning, watercraft and fishing boat, yet they describe different circumstances. Within V90 itself, the fourth character names the accident to the vessel: overturning, sinking, burning, crushing, or another accident.

The V90 vs V92 vs V93 split is the highest-risk confusion point. All three categories reference fishing boats, use the same episode-of-care characters and sit in the same block.

The split follows the circumstances. V90 codes describe drowning after an accident to the watercraft: it overturns, sinks, burns or is crushed. V92 codes describe drowning with no accident to the boat, such as a fall overboard.

V93 codes describe injuries on board when the patient never entered the water. The four questions below settle the choice from the provider note.

Which additional codes are reported with V90.32XD?

V90.32XD always follows a principal diagnosis code, and at the initial encounter it travels with place, activity and status codes. Per ICD-10-CM Official Guidelines Section I.C.20, external cause codes are always secondary. They supplement the injury or condition code that drove the encounter. A claim with V90.32XD as the first-listed code will be rejected.

The full coding picture for this event typically covers four code categories:

1. Principal diagnosis code: The condition being managed at this visit. Examples include effects of drowning (T75.1XXD, unspecified effects of drowning and nonfatal submersion), hypoxic encephalopathy, aspiration pneumonitis, or a respiratory condition caused by the submersion. The principal code drives payment; V90.32XD adds mechanism context.
2. Place of occurrence (Y92 series): Identifies where the original accident happened. Use Y92.814 (boat) or Y92.89 (other specified places), depending on documentation. It is reported only at the initial encounter, per ICD-10-CM guidelines.
3. Activity code (Y93 series): Identifies what the patient was doing at the time. Y93.19 (activity, other involving water and watercraft) is the appropriate activity code for fishing boat incidents. Like the place code, it is reported at the initial encounter.
4. External cause status (Y99 series): Indicates whether the event happened during paid work or not. Y99.0 applies to commercial fishing done for income, while Y99.8 covers leisure or other non-work status. Like the place and activity codes, it is reported at the initial encounter only.

Place of occurrence, activity and status codes are not reported again at subsequent encounters, because they went on the initial claim. For a follow-up visit coded V90.32XD, the coder’s focus is on the principal diagnosis and confirming the correct episode-of-care character.

Documentation that supports V90.32XD

Four documentation elements must be present to support V90.32XD specifically. Missing any one of them means the coder must default to a less-specific code or query the provider before coding.

• Vessel type confirmed as a fishing boat: The provider note must identify the vessel as a fishing boat (or fishing vessel), not generic watercraft. “Patient fell from a crushed boat” supports V90.39XD (unspecified watercraft) at best. “Patient fell from the fishing vessel he operates commercially” supports V90.32XD.
• Vessel was crushed: Explicit documentation that the boat was crushed, for example by a collision with another vessel or by ice. This is often absent when the provider focuses on the drowning injury and omits the circumstances. The coder cannot infer a crushed hull from a drowning diagnosis alone.
• This is a subsequent encounter: Documentation that active treatment of the original drowning event has ended. The visit must be for follow-up, rehabilitation or ongoing management. The discharge summary from the initial hospitalization, or a note stating “continuing rehabilitation from prior drowning incident,” supports XD.
• Connection between the original event and this visit: The provider must link this encounter back to the drowning event. The note should show that the visit manages a condition caused by the submersion. A generic follow-up note with no reference to the original event is insufficient to code the external cause.

When documentation is ambiguous on any of these points, the ICD-10-CM guidelines require the coder to query the provider rather than assume. Structured medical billing compliance workflows prompt providers to record mechanism, vessel type and episode of care at each visit. That cuts the number of pre-submission queries.

Payer requirements and reimbursement for V90.32XD

V90.32XD is billable but drives no direct reimbursement on its own, because payment attaches to the principal diagnosis code. The external cause code gives the payer mechanism context for subrogation and injury reporting. It does not generate a separate line-item payment.

Payer requirements for external cause codes vary. CMS does not mandate them for Medicare Part B claims, though many state Medicaid programs do. Commercial payers increasingly require them on injury claims to support subrogation and coordination of benefits.

Because requirements shift from year to year, confirm each payer’s expectations before you submit. Reporting V90.32XD to a payer that does not require it causes no harm. Leaving it off for a payer that does may trigger an edit that delays payment.

In inpatient settings, the principal diagnosis and secondary conditions drive MS-DRG grouping. V90.32XD carries no CC or MCC status, so it does not change the DRG. Its role there is the same as on an outpatient claim: mechanism context for subrogation and injury reporting.

Common denial reasons for V90.32XD claims

External cause codes for watercraft drowning events produce a predictable set of denial patterns. Each one maps to a specific documentation or coding mistake, and each has a fix.

Repeated denials on injury claims call for structured denial management workflows that track reason codes (CARCs) and route each correction to the right person. A clean claim checklist confirms the principal diagnosis, code format and sequencing before the first submission. That check alone catches three of the six patterns above.

How Pabau keeps V90.32XD claims accurate from note to remittance

Without a structured note, the coder hunts through free text for the vessel type, the crushed-hull detail and the episode of care. Each missing detail becomes a query or a denial.

Pabau, the practice management and billing platform we build, keeps the clinical note, the diagnosis codes and the invoice in one patient record. Its claims management without rework lets the coder read the note and set the codes in the same place.

For US payers, Pabau connects to the Claim.MD clearinghouse. Claim.MD turns Pabau invoices into electronic CMS-1500 claims and tracks each claim’s status. It then returns the ERA to Pabau, so payments and denials post against the original visit.

Simplify ICD-10-CM coding and claims submission

Pabau keeps clinical notes, ICD-10-CM codes and invoices in one record. It then sends electronic CMS-1500 claims to US payers through Claim.MD and tracks their status.

Book a demo

Conclusion

Code V90.32XD only when the note says three things: the vessel was a fishing boat, the boat was crushed, and active treatment has ended. If one is missing, query the provider before the claim goes out.

The trade-off is specificity against speed. V90.39XD is always available when the vessel type is unclear, and it is safer than a fishing-boat code the note cannot support.

To see how Pabau carries the note, the code and the CMS-1500 claim through one record, book a demo.

Continue your research

Need to understand how claim denials are tracked and resolved? Denial management in healthcare covers workflows for routing, appealing, and preventing recurring denial patterns.

Want a checklist for submitting clean claims the first time? Clean claim best practices outlines the pre-submission checks that prevent the most common external cause code errors.

Looking for guidance on electronic remittance and ERA reconciliation? Electronic remittance advice (ERA) explains how 835 files map denial reason codes back to specific claim lines.

Frequently asked questions