ICD code V73.9XXA – Unspecified bus occupant injured in traffic accident

Key takeaways

V73.9XXA is a billable ICD-10-CM external cause code for an unspecified bus occupant hurt when a car, pick-up or van hits the bus in traffic.

It’s always a secondary code, so the patient’s injury code goes first on the claim.

If the record names a role, use V73.5 for the driver, V73.6 for a passenger or V73.7 for someone on the outside of the bus.

The 7th character A marks active treatment, D marks subsequent care and S marks sequela.

Pabau, the practice software we build, submits claims through Claim.MD and tracks claim status and remittances.

ICD-10 code V73.9XXA records how a bus crash injury happened

ICD-10 code V73.9XXA describes one scenario. A car, pick-up truck or van hits a bus in traffic and injures someone on board. The record doesn’t say whether that person drove or rode. The A on the end marks the first phase of care, when the patient is in active treatment.

The code sits in Chapter 20, External causes of morbidity (V00-Y99), inside the bus occupant block V70-V79. Like every external cause code in our ICD-10-CM library for coders, it explains the cause rather than the injury.

In medical billing, that difference decides the order on the claim. Say a passenger breaks a wrist when a van hits the bus. The fracture code comes first, and V73.9XXA follows it as the secondary code.

The official descriptor and code details at a glance

Here is the reference data for V73.9XXA, as published by CDC/NCHS in the official ICD-10-CM tabular list.

Five conditions must all be true before you use V73.9XXA

V73.9XXA applies only when all five conditions are met. If one of them fails, a different code is correct.

• Bus type: the patient was in a bus, meaning a motor vehicle designed or adapted primarily to carry more than 10 persons.
• Other vehicle: the bus collided with a car, pick-up truck or van. A motorcycle, a heavy transport vehicle or another bus points to a different category.
• Setting: it was a traffic accident on a public road or highway. A crash off public roads uses the non-traffic codes.
• Occupant position: the record does not state whether the patient was the driver or a passenger.
• Encounter phase: the patient is in active treatment, so the 7th character is A.

The 7th character changes with each phase of care

The 7th character tells the payer which phase of care you’re billing. A wrong one is a common reason external cause claims are rejected. All three versions describe the same collision, and only the encounter type changes.

The “XX” fills the 5th and 6th character positions, which this category doesn’t subdivide. Keep both placeholders. Coders who drop them create an invalid code string.

Where V73.9XXA sits in the V73 hierarchy

V73.9XXA is the most specific level of its branch. Knowing the levels above it helps you switch codes when the documentation says more than “unspecified.”

If the patient’s role is documented, move to a specific traffic code instead. Use V73.5 for the driver, V73.6 for a passenger and V73.7 for a person on the outside of the bus. Each one still needs XX and its own 7th character.

Sibling codes are easy to confuse, so check role and setting

The V73 category describes the same bus-versus-car collision for different people and settings. Picking the wrong sibling when the record is clear is a coding accuracy error.

The table below draws on the AAPC ICD-10-CM code reference and covers the codes coders mix up most.

Two questions settle the choice: who was the patient, and was the bus on a public road? The grid maps every answer to its V73 code.

Every sibling also comes in A, D and S versions. A passenger’s late effects from a non-traffic collision, for example, are coded V73.1XXS.

Exclusions: When a neighboring code fits better

Several scenarios look like V73.9XXA but belong to other codes. Using V73.9XXA for them gets the claim rejected at the payer’s edit stage.

• Non-traffic accidents: a non-traffic collision where the occupant role is unspecified uses V73.3XXA, not V73.9XXA. A crash inside a bus depot is one example.
• Known occupant role: a driver in a traffic accident is V73.5XXA. A passenger is V73.6XXA.
• Other vehicle types: a bus hitting a motorcycle uses V72.9XXA. A bus versus a heavy transport vehicle uses V74.9XXA.
• Principal diagnosis: V73.9XXA can never be the first-listed or principal diagnosis. ICD-10-CM guidelines Section I.C.20 state this directly.
• Missing “XX” placeholders: V73.9A without the XX is an invalid code, and payers reject it at the front end.

Documentation requirements: Three facts the clinician must record

The code you can assign depends on what the provider writes down. Three details matter most.

1. Occupant role. Was the patient driving, riding as a passenger, or on the outside of the bus? The clinician’s note decides whether V73.5, V73.6, V73.7 or V73.9 applies.
2. Traffic or non-traffic setting. The note should say whether the crash happened on a public road. That choice separates V73.5-V73.9 from V73.0-V73.3.
3. Encounter phase. The record should show whether this visit is active treatment, follow-up care or a late effect. That sets the 7th character.

Coders can’t infer a role from context. If the note is silent, V73.9XXA is correct, and a query to the provider is the way to get something more specific.

Companion codes complete the story on the claim

V73.9XXA never appears alone. ICD-10-CM guidelines and some payer policies call for related codes that explain the injury and its circumstances.

• Injury diagnosis code (required, sequenced first): the condition treated, such as S72.001A for a right femoral neck fracture or S09.90XA for an unspecified head injury.
• Place of occurrence (Y92): a Y92.4- code reports a street or highway, for example Y92.410 for an unspecified street and highway.
• Activity (Y93): a Y93 code describes what the patient was doing, where the record documents it.
• External cause status (Y99): Y99.8 covers other status, such as leisure travel. Y99.0 covers paid work, such as a bus driver on shift.

Place, activity and status codes go on the initial encounter only. The status code also signals when workers’ compensation may be the payer.

The order never changes: the injury code leads, and V73.9XXA follows. Reversing it is a common reason external cause claims come back unpaid.

How a V73.9XXA claim moves from encounter to payment

No national rule requires external cause codes. CMS doesn’t require them on Medicare Part B claims, though ICD-10-CM guidelines encourage reporting them. Some state Medicaid programs require them, and commercial payers set their own rules in provider agreements.

Here’s the path a typical bus accident claim takes:

1. The clinician documents the injury, how it happened, the patient’s role and the setting.
2. The coder lists the injury code first, then V73.9XXA, then any Y92, Y93 and Y99 codes.
3. Billing confirms who pays: the health plan, an auto insurer or a workers’ compensation carrier.
4. The claim goes out electronically through a clearinghouse and passes the payer’s edits.
5. The remittance comes back, and any denial gets corrected and resubmitted.

Step three trips teams up most often. A work-related bus accident sent to a commercial plan can take weeks to unwind. That’s why getting a clean claim out on the first pass matters so much here.

Before you submit: A quick V73.9XXA checklist

Run through these checks before the claim leaves your system. They catch the errors that cause most rework on bus accident claims.

• The injury code is in first position, and V73.9XXA follows it.
• The record names no role. If it does, switch to V73.5, V73.6 or V73.7.
• The crash happened in traffic. If not, use V73.3XXA.
• Both XX placeholders are present.
• The 7th character matches the encounter, and it matches the injury code’s phase.
• Y92, Y93 and Y99 codes are added on the initial encounter where the payer wants them.
• The responsible payer is confirmed, including any workers’ compensation or auto carrier.

Common denial reasons and how to fix them

Transportation accident codes tend to fail in the same few ways. Spotting the pattern early keeps your denial management workflows from turning into a backlog.

• V73.9XXA listed as the principal diagnosis: payer claim editors reject external cause codes in first position. Move the injury code to the top.
• Wrong 7th character: billing A on a follow-up visit, or D on a first ED visit, can trigger a denial. Match the character to the encounter.
• Missing placeholders: V73.9A instead of V73.9XXA returns straight away with a format error.
• No injury code: some payers won’t process a claim that carries an external cause code without the injury diagnosis.
• Payer ignores external cause codes: some commercial payers don’t use them on professional claims. Check the provider agreement before you submit.
• Mismatched encounter phase: an injury code ending in D next to V73.9XXA can prompt a review. Keep both on the same phase.

For medical billing compliance, track denial reasons by code group. A pattern across V-codes shows up much faster than it does claim by claim.

The ICD-9-CM crosswalk points to E813.9

Before October 2015, transportation injuries were coded with ICD-9-CM E-codes. The approximate equivalent for V73.9XXA is E813.9, a motor vehicle traffic accident involving collision with another vehicle, unspecified person.

Treat that mapping as approximate. The CMS General Equivalence Mappings (GEMs) file is the authoritative translation table. Check it before using the crosswalk in a legacy system, a research dataset or payer correspondence.

How Pabau keeps transportation injury claims moving

Urgent care centers, emergency departments, orthopedic practices and physical therapy practices see motor vehicle injuries every week. Each claim needs the injury code first, the right V73 code second and a matching 7th character. Chasing those claims across payers by hand eats into the billing team’s day.

Pabau’s claims software for practices builds the CMS-1500 from the visit and submits it electronically. Claims go through the Claim.MD clearinghouse, which reaches thousands of US payers.

Eligibility checks run in real time, so you know who pays before the patient leaves. Pabau also tracks claim status and electronic remittance advice (ERA), so your team can see which claims were paid and which need work.

Send transportation injury claims electronically

Pabau’s claims management software submits claims through Claim.MD, checks eligibility in real time and tracks claim status and ERA remittances. Your team spends less time chasing payers.

Book a demo

Conclusion

V73.9XXA is a fallback, not a first choice. It fits only when the crash happened in traffic and nobody recorded who the patient was on the bus.

So the best fix starts upstream. When clinicians note the role and the setting, coders can reach for V73.5, V73.6 or V73.7 instead, and payers ask fewer questions. When the note stays silent, V73.9XXA is the honest code, as long as it sits behind the injury code.

Book a demo to see how Pabau tracks your accident claims from submission to remittance.

Continue your research

Need to understand how external cause codes interact with the revenue cycle? Revenue cycle management in healthcare explains the end-to-end billing workflow from encounter to payment posting.

Want guidance on reducing claim rejections from coding errors? How to submit a clean claim covers the pre-submission checks that prevent the most common ICD-10-CM errors from reaching the payer.

Looking for the clearinghouse that handles US transportation accident claims? Medical claims clearinghouse guide explains how electronic claim routing works across commercial and government payers.

Frequently asked questions