ICD code V73.1XXS – Nontraffic bus passenger collision sequela

Key takeaways

V73.1XXS applies only when the acute phase of a nontraffic bus-accident injury has resolved and the patient presents with a documented residual condition.

V73.1 is four characters without the decimal, so two placeholder Xs fill positions 5 and 6 and S lands in position 7. Submitting V73.1S or V73.1XS fails format edits.

V73.1XXS is an external cause code from ICD-10-CM Chapter 20, so it never serves as the principal or first-listed diagnosis. The residual condition is coded first.

A collision on a public road, or one whose location the chart never states, takes traffic codes such as V73.6XXS instead.

Pabau’s claims management software pre-fills claim forms from the patient record, offers an ICD-10-CM lookup library, and checks required claim fields before you submit.

ICD-10 code V73.1XXS covers the late effects of a nontraffic bus crash

ICD-10 code V73.1XXS describes a bus passenger injured when the bus collides with a car, pick-up truck or van in a nontraffic accident. The current visit treats a sequela of that crash, not the acute injury itself.

The code sits in ICD-10-CM Chapter 20 (External causes of morbidity, V00-Y99), in block V70-V79 for bus occupants. Its parent category is V73, bus occupant injured in collision with car, pick-up truck or van.

Four facts must all hold for this code to apply:

• The injured person was a passenger, not the driver.
• The bus hit a car, pick-up truck or van, not another bus, a heavy vehicle, a fixed object or a pedestrian.
• The accident was nontraffic, such as in a parking lot, a depot or on private property, not on a public road.
• The visit treats a condition that persists after the injury’s acute phase has ended.

When one of them fails, a different V73 code or a different category applies. The sections below show which one, starting with the code’s key facts.

The key facts about V73.1XXS fit in one table

The 7th character S means the injury itself has healed

The 7th character S marks a sequela, a late effect of the bus-accident injury after its acute phase has ended. Under the ICD-10-CM Official Guidelines, the residual condition is sequenced first and the sequela code second. V73.1XXS is never the principal diagnosis.

Coders often confuse S with D, and the line between them is clinical. Use D while the patient still receives active treatment for the injury itself, even if that runs for months. Switch to S only once the provider documents that the injury has resolved and a residual condition remains.

The guidelines set no time limit on a sequela, so S can apply years after the crash. The table shows how each 7th character maps to the encounter.

Why V73.1XXS needs two placeholder Xs

ICD-10-CM requires the 7th character to sit in the 7th position. V73.1 is four characters long, because the decimal point is not counted. Without placeholders, S would land in position 5 and the code would be invalid. Two X characters fill positions 5 and 6, so S lands in position 7.

The breakdown below shows what each position carries:

S is the 7th character; the decimal point is not counted. The decimal is written between positions 3 and 4 but takes no position of its own. Submitting V73.1S or V73.1XS produces an invalid-format error at the clearinghouse, so the claim is rejected before the payer reviews it.

Location, role and encounter decide which V73 code fits

V73.1XXS covers one combination of facts, and changing any of them hands the claim to a neighboring code. The chart below walks the three questions in the order a coder should ask them.

Location comes first because the ICD-10-CM Tabular List assumes a vehicle accident happened on a public road unless the record names another place. A chart that never says where the bus was hit points to traffic codes, not V73.1XXS.

Check these exclusions before you settle on the code:

• Driver of the bus in the same nontraffic collision: Use V73.0XXS, not V73.1XXS.
• Occupant whose role is not documented, nontraffic: Use V73.3XXS.
• Passenger hurt in a collision on a public road: Use V73.6XXS. V73.9XXS is the unspecified-occupant code for a traffic accident.
• Noncollision bus accident (rollover, fire, fall from the bus): A different V70-V79 category applies.
• Pedestrian struck by a bus: Falls outside the V73 category entirely.
• Bus collision with another bus, a heavy transport vehicle or a fixed object: Different V70-V79 codes govern these scenarios.
• Visit for the acute injury: Use V73.1XXA (initial encounter) or V73.1XXD (subsequent encounter) until the acute phase resolves.

Sibling V73 codes change with role and setting

Each V73 code differs by occupant role, by traffic or nontraffic setting, and by encounter type. Picking the wrong sibling is a common error in this category, so compare the options side by side.

Two mix-ups cause many V73.1XXS coding errors

Two confusion pairs come up again and again with this code.

V73.1XXD vs. V73.1XXS: The dividing line is whether the original injury is still being treated. A healing fracture, or physical therapy for acute whiplash, stays on the D code. Once the provider documents that the injury has resolved and chronic pain remains, switch to the S code. Billing D out of habit invites audits asking why subsequent-encounter claims run years past the accident.

V73.0XXS vs. V73.1XXS: Driver versus passenger is a documentation question, not a clinical judgment. If the record does not state the patient’s role, query the provider or report V73.3XXS for an unspecified occupant. Assuming passenger status without support is a compliance risk. The AAPC’s ICD-10-CM code reference shows the occupant’s role built into every code in this block.

A third error is reporting V73.1XXS on its own. External cause codes never stand alone, so the residual condition must be coded first.

What the chart must show before you assign V73.1XXS

Payers and auditors apply the sequela guidelines strictly on accident claims, especially in workers’ compensation and auto liability cases.

Solid medical billing compliance depends on the record holding five elements before you assign V73.1XXS:

• A causal link to the original accident: The provider ties the condition to the bus collision, not to a later injury or an unrelated cause.
• Confirmation the acute phase has resolved: The record shows, directly or by clear implication, that the original injuries have healed.
• Patient role confirmation: Documentation identifies the patient as a passenger on the bus in a nontraffic accident, not the driver and not a pedestrian.
• Accident location: The record names where the collision happened, such as a parking lot, a depot or private property. Without it, the coding defaults to a traffic accident.
• Vehicle specificity: The record confirms the bus collided with a car, pick-up truck or van. Police reports, intake notes or earlier accident records support this when the current note references them.

When the record leaves the patient’s role thin or ambiguous, V73.3XXS (unspecified occupant) is more defensible than V73.1XXS. A specific code with weak support carries more audit risk than a less specific code the record backs.

How to code a V73.1XXS sequela visit, step by step

Code reference pages tend to stop at the descriptor, yet errors usually creep in during the workflow. Follow these five steps for each sequela encounter:

1. Confirm sequela status. Read the provider’s note. Is the acute injury resolved? Is the patient now treated for a residual condition, such as chronic pain, a cognitive deficit, post-traumatic anxiety or limited motion? If yes, sequela coding applies. If you’re unsure, query the provider before coding.
2. Code the residual condition first. Assign the ICD-10-CM code for the sequela condition as the principal or first-listed diagnosis. Examples include G89.21 (chronic pain due to trauma), M54.50 (low back pain, unspecified), or a post-traumatic cognitive or psychiatric code. V73.1XXS explains why the condition exists, not what it is.
3. Add the injury code, then V73.1XXS. Report the original injury code with 7th character S after the residual condition. Then add V73.1XXS and confirm the string reads V73.1XXS, not V73.1S or V73.1XS.
4. Check payer requirements. No national rule requires external cause codes. Report them where a state mandate or the payer requires it, and confirm with each payer. Auto liability and workers’ comp payers often request them, so check the payer’s manual.
5. Verify clearinghouse acceptance. A clean claim needs both a valid code format and correct sequencing. Clearinghouse edits catch a malformed code string before the payer sees it, but sequencing still needs a coder’s eye. Effective revenue cycle management fixes these errors at submission rather than after a denial.

Worked example: A car hit a shuttle bus in a hospital parking lot, injuring a seated passenger. Eight months later the fracture has healed, but the provider now treats chronic post-traumatic pain. The claim lists G89.21 first, then the fracture code with 7th character S, then V73.1XXS.

Why V73.1XXS claims get denied, and how to fix them

Denials on this code follow predictable patterns, and knowing them in advance prevents rework. A structured denial management workflow helps you track and resolve each one:

Compare your rejections against medical billing denial codes to see whether V73.1XXS problems share a CARC/RARC combination. Clearinghouses that parse CARCs automatically make that pattern faster to spot.

Payers decide whether V73.1XXS belongs on the claim

External cause codes from Chapter 20 are not universally required. The Official Guidelines state there is no national requirement for mandatory external cause reporting.

Knowing how medical billing works across payer types helps before you submit V73.1XXS, because requirements vary by setting and plan.

• Medicare inpatient (CMS/UHDDS): No national rule requires external cause codes, and the UHDDS does not mandate them. Report them where a state mandate or the payer requires it, and confirm with each payer.
• Commercial payers (outpatient/professional): Requirements vary by state and by plan. Some accept external cause codes as additional information, while others treat them as erroneous additions that trigger edits. Check the payer’s provider manual or call provider relations before submitting.
• Workers’ compensation: Workers’ comp payers often request external cause codes to establish the accident context, so check the payer’s manual. V73.1XXS supports the record when the injury happened during work-related transport.
• Auto liability: Auto liability carriers often request them to confirm the injury arose from the documented accident, so check the payer’s manual. V73.1XXS matters most on sequela claims filed months or years after the crash.
• Medicaid: Requirements vary by state. Check the state’s fee-for-service billing guide or the managed care organization’s rules.

The CDC/NCHS ICD-10-CM web tool confirms V73.1XXS as a valid, billable code for the current fiscal year. Before routing external cause codes through any claims workflow, confirm each payer’s submission rules. Sending a clean claim means knowing whether the payer will accept the external cause code before it arrives.

Run this five-point check before you submit

A quick pass over the claim catches the errors covered above while they are still cheap to fix:

• The note documents a resolved injury and a residual condition linked to the crash.
• The record places the collision off a public road.
• The patient’s role as a passenger is documented.
• The residual condition comes first, the injury code with S follows, and V73.1XXS comes last.
• The code string carries both placeholder Xs, and this payer accepts external cause codes.

How claims management software keeps V73.1XXS claims complete

In many practices, sequela claims are still assembled by hand. A biller retypes codes from the provider’s note, checks payer rules in a separate portal, and finds missing fields only when the claim bounces.

Pabau, the practice management platform we build, moves that work into the patient record. Its streamlined claims management pre-fills claim forms from the chart and offers an ICD-10-CM lookup library. Required-field checks run before you submit, and US claims go out through Claim.MD with eligibility and remittance tracking.

The coder still owns sequencing and the S-versus-D call. What changes is the retyping and the missing fields, so sequela claims leave complete and come back less often.

Submit V73.1XXS claims with fewer rework loops

Pabau’s claims management tools pre-fill ICD-10 codes from the patient record and check required claim fields, so sequela claims go out complete.

Book a demo

Conclusion

V73.1XXS rewards the coder who reads the chart before reaching for the code. Location, role and the state of the injury each change the answer. Ask them in that order, and the right V73 code is rarely in doubt.

The trade-off worth remembering is specificity against support. A precise code on a thin record is a bigger audit risk than V73.3XXS on a solid one. When the note is silent, query the provider, and keep V73.1XXS behind the residual condition.

If retyping codes and chasing claim fields eat into your week, book a demo and see Pabau build sequela claims from the patient record.

Continue your research

Need to understand how clearinghouse validation works? How a medical claims clearinghouse works explains the validation steps a claim passes through before it reaches the payer.

Want to read ERA and remittance data for sequela denials? Electronic remittance advice explained covers how to read 835 ERA files and spot denial reason codes at scale.

Coding another nontraffic transport sequela? ICD-10 code V26.29XS applies the same nontraffic and sequela logic to a motorcycle crash.

Comparing clearinghouse options for your practice? Claim.MD vs Office Ally compares two US clearinghouses on format validation, payer reach and denial reporting.

Frequently asked questions