Skip to main content

V43.94XD ICD-10-CM Code: Unspecified car occupant injured in collision with van in traffic accident, subsequent encounter

Billing Status: YES. This is a valid, specific, and billable ICD-10-CM reference.

Coding at a Glance

7th character
Required — see the character table on this page
Tabular directives
2 inclusion terms · 6 Excludes1

Coding instructions

Official Tabular Instructional Notes: the inclusion, exclusion and sequencing notes published for V43.94XD in the official ICD-10-CM tabular list, quoted as published.

Notes without a marker are published on V43.94XD itself; “inherited from” names the category or block whose note applies here.

Includes

Conditions the official ICD-10-CM tabular list includes under this code.

  • a four-wheeled motor vehicle designed primarily for carrying passengers
  • automobile (pulling a trailer or camper)

Source: inherited from V40-V49

Excludes1 — Not Coded Here

Conditions generally not reported together with this code (Excludes1) -- an error unless the two conditions are documented as unrelated to each other (ICD-10-CM Official Guidelines, Section I.A.12.a).

Source: inherited from V40-V49

7th Character Guide

"The appropriate 7th character is to be added to each code from category V43"

  • A — initial encounter
  • D — subsequent encounter (this page’s code)
  • S — sequela

How the encounter character is assigned. “Initial encounter” means the patient is receiving active treatment for the condition — it is not limited to the first visit, and a different or new provider giving active treatment still assigns it. “Subsequent encounter” covers care during the healing or recovery phase after active treatment. “Sequela” is for complications or conditions that arise as a direct result of the original condition.

ICD-10-CM Official Guidelines for Coding and Reporting, Section I.C.19.a (paraphrased by MedCoder).

Variant codes in this family

V43.94XA, V43.94XD, V43.94XS

Character meanings are CMS's official 7th-character extensions for this family, as carried in each variant code's official description; variant codes are registry rows. The explanation of how the encounter character is assigned is MedCoder editorial, distinct from the official content above it.

Coder workflow for V43.94XD

MedCoder structured workflow — derived from this code’s own official record

Before you code V43.94XD

  1. Unspecified does not mean incorrect. When the record gives no greater specificity, V43.94XD may be the appropriate code. Check the record for detail that supports a more specific sibling — in this subcategory the siblings differ by the presence or absence of the associated condition. An unspecified code is for records that do not provide the detail a more specific code needs; a query, not an assumption, is the route to specificity (Guidelines I.A.9.b, I.B.18).

    See the hierarchy · Guide: Other vs unspecified (NEC vs NOS) →

  2. A 7th character is required in this family. Confirm the documented encounter: initial (active treatment), subsequent (healing or recovery phase), or sequela. This page’s code carries “D”. “Initial” means active treatment, not the first visit (Guidelines I.C.19.a).

    See the 7th Character Guide · Guide: 7th characters: initial, subsequent, sequela →

  3. V43.94XD’s title joins a condition with an associated condition or complication. Confirm each component is documented. Where the classification presumes the link through the “with” convention, only a provider statement that the conditions are unrelated defeats it. A combination code is assigned only when it fully identifies the documented conditions; a required second code for the stage, type or manifestation is still reported when the notes ask for it (Guidelines I.B.9, I.A.15).

    Guide: Combination codes →

  4. An external cause code is reported in addition to the code for the injury or condition, never as the principal or first-listed diagnosis. Confirm the cause, intent, place of occurrence, activity and status where the record documents them, and assign the 7th character that matches the injury code. External cause coding guidelines (Guidelines I.C.20.a).

  5. Check the Excludes1 note: if the documentation supports a condition named there, do not simply proceed with V43.94XD. Excludes1 conditions are not reported together with this code unless the record shows they are unrelated (Guidelines I.A.12.a).

    See the official tabular notes

Choose the right path

  1. Does the record document the detail a more specific sibling code needs?
    Yes → Review the specific siblings in this subcategory.
    No → Continue — V43.94XD is appropriate when the documentation goes no further.
  2. Does the documentation support a condition named in V43.94XD’s Excludes1 note?
    Yes → Do not simply proceed: review the excluded code. Both are reported only when the record shows the two conditions are unrelated.
    No → Continue.
  3. Is the encounter phase documented — active treatment, healing or recovery, or a sequela?
    Yes → Assign the matching 7th character; the variant codes are in the 7th Character Guide.
    No → The code is invalid without its 7th character — query for the missing element.

Consider V43.94XD. Then confirm the code is valid for the date of service in the Verify section.

Documentation check

The provider’s diagnostic statement
Codes are assigned from the provider’s documented diagnosis, not from clinical criteria, test values or a medication list (Guidelines I.A.19).
Encounter type
Active treatment, healing or recovery phase, or sequela — the basis of the 7th character (Guidelines I.C.19.a).
The associated condition or complication
Whether the associated condition the title names is documented; the “with” convention presumes some links, and a provider statement that the conditions are unrelated defeats it (Guidelines I.A.15).
Any detail beyond this code’s title
What the record states that a more specific sibling code would capture — or its absence, which itself supports the unspecified code.

Official instructions as workflow

  • Excludes1 — check before selecting V43.94XD(6 notes)

    Coding workflow: If the documentation supports a condition named in this note, do not simply proceed with V43.94XD: the two are not reported together. The one exception is when the record shows the two conditions are unrelated to each other.

    See the official tabular notes · Guidelines I.A.12.a

Coding decision scenarios

Pattern scenarios for this code’s structure — decision rules, not clinical cases

Documentation: The provider documents the condition in the terms of this code’s title and records no further detail.

Coding question: Is a more specific sibling code supportable?

Path: Review the subcategory for a sibling that names the missing detail.

Reason: A more specific code needs documentation of the distinguishing element; without it the unspecified code is appropriate, and a provider query is the route to specificity (Guidelines I.A.9.b, I.B.18).

Documentation: Both the condition V43.94XD describes and a condition named in its Excludes1 note are documented for the same encounter.

Coding question: Can both codes be reported?

Path: Review the Excludes1 note and the excluded code, and look for a provider statement on whether the two conditions are related.

Reason: Excludes1 means the two are not coded together; the exception is when the record shows the conditions are unrelated to each other (Guidelines I.A.12.a).

Documentation: The patient returns during the healing or recovery phase after active treatment of the same condition.

Coding question: Which 7th character applies?

Path: Review the official 7th-character definitions for this family in the 7th Character Guide.

Reason: “Initial encounter” means active treatment, not the first visit; care during recovery takes “subsequent encounter”, and a complication arising from the original condition takes “sequela” (Guidelines I.C.19.a).

Every row is derived from this code’s own record — its title, tabular notes, 7th-character family and same-category siblings — with fixed MedCoder wording; nothing is inferred about a patient. The official notes and guideline text are in the sections each row links to, and they control.

Code Overview

Unspecified car occupant injured in collision with van in traffic accident, subsequent encounter is a billable ICD-10-CM diagnosis code (V43.94XD).

MedCoder summary Summary composed by MedCoder from this code's official ICD-10-CM record. The tabular instructional notes themselves appear verbatim below.

Verify Before Coding

  • Principal-diagnosis restriction. External cause of morbidity codes (V, W, X and Y) describe the circumstance that caused an injury, not the condition treated. The Medicare Code Editor rejects them as a principal diagnosis; sequence the injury or condition first and report this code as secondary.

From the code registry, the Medicare Code Editor, and the MS-DRG Definitions Manual. Check it against a full claim in Claim Check.

Relationships & Classification

Clinical classification (AHRQ CCSR):EXT029 — External cause codes: subsequent encounter.

Clinical Classifications Software Refined (CCSR) for ICD-10-CM Diagnoses. Healthcare Cost and Utilization Project (HCUP), Agency for Healthcare Research and Quality.

Related Codes

Same clinical category (CCSR)

AHRQ's Clinical Classifications Software groups these diagnoses under the same clinical category (External cause codes: subsequent encounter).

+2321 more

Contextual Map

Every relationship of V43.94XD in one view: hierarchy, official tabular instructions in both directions, clinical classification, risk adjustment, MS-DRG participation, index terms and change history — each edge carrying the CMS source it derives from.

Hierarchy

Clinical classification (CCSR)

Nearest codes (40)

Change history

  • FY2016 — In the code set at ICD-10-CM adoption [Change history]— CMS release files (code change ledger) · icd10cm-fy2016

Common coding questions

Does V43.94XD require a 7th character?

Yes. The appropriate 7th character is to be added to each code from category V43.

Sources for this page

Codes, titles, notes, index terms and mappings on this page are transcribed from the datasets below. Relationships MedCoder computed and text MedCoder wrote are labelled where they appear.

Code, title, tabular notes and index terms Official source data
CMS/CDC ICD-10-CM FY2026 tabular list, index and tables, effective October 1, 2025 Release, file and checksum · Publisher’s page
Claim edits Official source data
CMS Definitions of Medicare Code Edits — v43.1 (April 2026) Release, file and checksum · Publisher’s page
Change history and date-of-service validity Official source data
CMS ICD-10-CM release addenda, ingested release by release into the change ledger Release, file and checksum · Publisher’s page
Comparisons, relationships and the contextual map MedCoder structured relationship
Computed by MedCoder from the tabular notes and tables above; every derived relationship is marked as derived where it appears
Summary and FAQ answers MedCoder explanation
Written by MedCoder to explain the sources above: drafted with AI assistance, checked by a person against the release files, and labelled as MedCoder text where it appears. Not official text.

Labels on this page: Official source data · MedCoder structured relationship · MedCoder explanation. How to read the labels · All data sources and release dates

Change history

  • FY2016 — October 1, 2015
    In the code set at ICD-10-CM adoption
    Unspecified car occupant injured in collision with van in traffic accident, subsequent encounter

No changes since FY2016 — additions, deletions, description changes and billable-status changes are tracked through FY2027 (effective October 1, 2026), and none are recorded for this code. Note changes are tracked from FY2027 only.

Nearest Codes in This Family

Official ICD-10-CM classifications closest to V43.94XD in its code family, with their registry titles.

View all codes in the V43 family