ICD code V43.54XD – Car driver injured in van collision

Key takeaways

V43.54XD codes a car driver hurt in a collision with a van in traffic, at a follow-up visit after active treatment.

The X placeholder in the 6th position is mandatory, so V43.54D without it is an invalid code.

V43.54XD is always a secondary code, listed after the injury code that describes what was hurt.

The other vehicle sets the 5th character: 1 for an SUV, 2 for another car, 3 for a pick-up truck and 4 for a van.

Place of occurrence, activity and status codes belong on the initial encounter, so they stay off V43.54XD follow-ups.

What ICD-10 code V43.54XD means

ICD-10 code V43.54XD describes a car driver injured in a collision with a van in traffic, at a subsequent encounter.

The official CMS descriptor reads “Car driver injured in collision with van in traffic accident, subsequent encounter.” It is a billable ICD-10-CM code from Chapter 20. It records how the injury happened, not what the injury is.

Because the code records a cause, it never stands alone on a claim. The guidelines in the CMS ICD-10-CM coding resources place external cause codes after the injury diagnosis. Payers, auto insurers and injury researchers read V43.54XD as context on the crash.

For the wider code set around it, see our ICD-10-CM code guide.

Where V43.54XD sits in the V43 tree

The hierarchy narrows from the chapter down to the visit type. Each level adds one fact about the crash.

• Chapter 20: External causes of morbidity (V00-Y99)
• Block V40-V49: Car occupant injured in transport accident
• Category V43: Car occupant injured in collision with car, pick-up truck or van
• Subcategory V43.5: Car driver injured in collision with car, pick-up truck or van in traffic accident
• Code V43.54: Car driver injured in collision with van in traffic accident
• V43.54XD: Same, subsequent encounter (placeholder X, 7th character D)

Two characters do most of the work. The 4th character sets the occupant’s position and whether the crash was in traffic. That is why V43.4 means a person boarding or alighting, not a vehicle type.

The 5th character then names the other vehicle. Under V43.5-, V43.51 is an SUV, V43.52 another car, V43.53 a pick-up truck and V43.54 a van. The breakdown below shows each character and what replaces it.

Before you code, check the full V43 tabular list in the CDC/NCHS ICD-10-CM web tool.

A, D or S: Picking the 7th character

The 7th character tells the payer which phase of care the visit belongs to. It is a frequent audit finding on crash-related claims.

V43.54XA vs V43.54XD vs V43.54XS

The choice turns on the phase of care, not the number of visits. A driver still in active treatment gets V43.54XA, even on a third ED visit. Once care shifts to routine healing checks, each visit takes V43.54XD.

Sequela works differently. When a healed injury leaves a late effect, such as post-traumatic arthritis, the visit takes V43.54XS. A quick test helps here. Is the clinician still managing an unresolved injury, or a consequence of a healed one?

One more rule keeps claims consistent. The guidelines say the external cause code’s 7th character should match the injury code’s 7th character for that encounter.

What V43.54XD covers, and what it doesn’t

Inclusion and exclusion notes sit at several levels of the V43 hierarchy. These are the scenarios that send coders to the wrong code.

Included scenarios

• The driver of a car injured in a collision with a van
• Collisions on a public road, which the “traffic accident” wording requires
• Follow-up visits in any setting, from outpatient clinics to inpatient rehabilitation

Excluded scenarios (use a different code)

• Passenger in the same car: V43.64XD (car passenger, van collision, subsequent encounter)
• Person on the outside of the car: V43.74XD (subsequent encounter)
• Unspecified car occupant: V43.94XD (van collision), when the record doesn’t confirm driver or passenger
• Non-traffic accidents, such as a private parking lot: a different 4th character, in the V43.0-V43.3 range
• Other vehicle is an SUV, another car or a pick-up truck: V43.51XD, V43.52XD or V43.53XD
• Motorcycle rider hit by a car, pick-up truck or van: category V23, not V43

Codes people confuse with V43.54XD

Most mix-ups happen in three places. Coders confuse the occupant’s seat, the other vehicle or the phase of care.

When the record is unclear on any of these points, query the provider before you settle on an unspecified code.

What the chart must show for a van collision follow-up

Four details must appear in the record before V43.54XD fits. If one is missing, the coder drops to a less specific code, or the claim is exposed at audit.

1. The patient was the driver. “Patient was driving at the time of the collision” meets the standard. “Patient was in the car” does not.
2. The other vehicle was a van. The police report, patient history or provider note should name it. An SUV documents to V43.51-, and a pick-up truck to V43.53-.
3. The crash happened in traffic. A collision on a public road qualifies. Non-traffic events take a different 4th character.
4. The visit is follow-up care. Phrases such as “post-MVA follow-up” or “cast removal after a crash fracture” support the subsequent-encounter character. Notes that read like active treatment are a compliance risk.

Pairing V43.54XD with the injury code

V43.54XD never leads a claim. The injury code that describes what was hurt comes first, and V43.54XD follows it. Good medical billing documentation keeps that order on every claim line.

• Cervical strain: S13.4XXD (sprain of ligaments of cervical spine, subsequent encounter) first, then V43.54XD
• Rib fracture: S22.39XD (fracture of one rib, subsequent encounter) first, then V43.54XD
• Concussion or TBI: S06.0X1D or the S06 code that fits first, then V43.54XD
• Lumbar sprain: S33.5XXD (sprain of ligaments of lumbar spine, subsequent encounter) first, then V43.54XD

How a V43.54XD claim moves, step by step

Take a typical follow-up as an example. A driver returns three weeks after a van hit her car, for physical therapy on a neck sprain.

1. The therapist documents the visit as routine follow-up for a post-crash cervical sprain.
2. The coder lists S13.4XXD first, because the sprain is the reason for the visit.
3. V43.54XD goes second, with a 7th character that matches the injury code.
4. Place of occurrence (Y92), activity (Y93) and status (Y99) codes stay off, because they belong to the initial encounter.
5. The claim passes a required-field check, then goes to the payer through a clearinghouse.
6. If an auto insurer pays, the biller confirms whether it wants the external cause code reported.

Steps 2 and 3 are where sequencing errors start. When a claim comes back, check those two first.

POA status and payer rules

Many external cause codes appear on the POA (present on admission) exempt list. That list sits in Appendix I of the ICD-10-CM Official Guidelines. Check the current year’s list before you leave the POA field blank for V43.54XD.

External cause reporting rules vary by payer too. There is no national requirement to report external cause codes, and many payers accept claims without them.

Still, some state Medicaid programs and auto-liability carriers do require them. Check each payer’s policy before you leave V43.54XD off a claim. Then record the rule where your billing team can find it.

Why V43.54XD claims get denied

Most denials tied to ICD-10 code V43.54XD trace back to five errors. Each one can be caught before the claim leaves the practice.

1. Wrong 7th character. V43.54XA on a follow-up, or V43.54XD on a first ED visit, conflicts with the injury code. Confirm the care phase at the time of service.
2. Missing placeholder X. V43.54 has only five characters, so the X holds the 6th place. V43.54D is invalid and fails front-end edits. Look the full code up rather than typing it from memory.
3. V43.54XD in first position. Chapter 20 guidelines bar external cause codes from the principal or first-listed slot. Sequence the injury code first.
4. No injury code at all. A claim with only V43.54XD has no diagnosis that explains the visit. Ask the clinician to name the specific injury in the note.
5. Payer policy on external cause codes. A few payers reject claims that carry them. Drop V43.54XD only where the payer’s policy requires it, never across the board.

Review the clean claim requirements before you send crash-related claims. A denial management workflow that tags V-code denials by reason also shows repeat errors early.

Before you submit: a quick checklist

• Injury code listed first, with V43.54XD after it
• X in the 6th position and D in the 7th
• 7th character matches the injury code for this visit
• Patient documented as the driver, and the other vehicle as a van
• No Y92, Y93 or Y99 codes on the follow-up claim
• Payer’s external cause policy checked

How Pabau keeps follow-up injury claims moving

Follow-up crash claims often stall on small errors, like a dropped placeholder or a missing membership number. Teams that check claims by hand tend to find these late, after a rejection.

Pabau, the practice management platform we build, pre-fills each claim from the patient record. Its faster claims management tools include ICD-10-CM and CPT lookup libraries, so coders search V43.54XD instead of typing it. Required fields are checked before the claim can be sent.

In the US, claims go out through the Claim.MD clearinghouse. Real-time eligibility checks confirm coverage before the follow-up visit is billed.

Send cleaner follow-up injury claims

Pabau pre-fills claims from the patient record, adds ICD-10 and CPT code lookup, and checks required fields. Claims then go out through Claim.MD with eligibility checks.

Book a demo

Conclusion

V43.54XD pays when three facts line up in the note: the driver, the van and a follow-up visit. Get those into the record, and the code almost assigns itself.

The trade-off is a minute at the point of care against a resubmission later. Build the checklist above into your follow-up workflow, and audit first-position errors every month.

For practices that bill crash follow-ups often, revenue cycle management works best when coding checks happen before the claim is sent. Book a demo to see how Pabau helps your team send cleaner injury claims from the first follow-up.

Continue your research

Need a process for claims that come back denied? Denial management in healthcare covers how to identify, appeal and prevent payer denials on injury claims.

Submitting crash follow-up claims electronically? How the Claim.MD clearinghouse works explains 837P submission, real-time eligibility checks and remittance handling.

Want to see where diagnosis codes sit in a claim file? 837 file format guide breaks down the transaction set and how ICD-10 codes map to claim segments.

Not sure what a clearinghouse checks before the payer? Medical claims clearinghouse explained walks through the scrubbing and routing steps between your practice and the payer.

Checking coverage before a follow-up visit? Insurance eligibility verification shows what to confirm before the visit so the claim is payable.

Frequently asked questions