Skip to main content

V05 ICD-10-CM Code: Pedestrian injured in collision with railway train or railway vehicle

Compare with another codeCheck this code on a claim

Billing Status: NO. This is a non-billable ICD-10-CM code: report a more specific billable code beneath it.

Coding at a Glance

7th character
Required — characters A · D · S
Tabular directives
2 inclusion terms · 3 Excludes1

Category · FY2027A non-billable heading in the tabular list: report a more specific code beneath it.

What you need to know

Source: CMS/NCHS Official ICD-10-CM tabular notes, quoted. From the CMS/NCHS tabular list for the release in force. A note the category or block publishes applies to this code too; the Instructions section marks which is which.

Excludes1Never report with this code
  • fall due to non-transport collision with other person (W03)
  • pedestrian on foot falling (slipping) on ice and snow (W00.-)
  • struck or bumped by another person (W51)
IncludesWhat this code covers
  • person changing tire on transport vehicle
  • person examining engine of vehicle broken down in (on side of) road

Most relevant related codes MedCoder-derived

Read off the official notes above and this code’s own position in the tabular list. Which to report is a documentation question; Compare shows the two side by side.

CompareCheck ClaimView Related Codes

Coding instructions

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

Source: CMS/CDC — ICD-10-CM Tabular ListRelease: FY2027Effective: October 1, 2026

Trace:FY2027 changesChange historyRelease, file and checksum

Notes without a marker are published on V05 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.

  • person changing tire on transport vehicle
  • person examining engine of vehicle broken down in (on side of) road

Source: inherited from V00-V09

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 V00-V09

7th Character Guide

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

  • A — initial encounter
  • D — subsequent encounter
  • 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

V05.00XA, V05.00XD, V05.00XS, V05.01XA, V05.01XD, V05.01XS, V05.02XA, V05.02XD

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 V05

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

Before you code V05

  1. V05 is not reportable as written. Select the more specific code beneath it that the documentation supports. Codes are reported to the highest level of specificity the classification provides (Guidelines I.B.2).

    ReviewV05.0, V05.1, V05.9

    See the relationships section · Guide: How to choose an ICD-10-CM code →

  2. A 7th character is required in this family. Confirm the documented encounter: initial (active treatment), subsequent (healing or recovery phase), or sequela. V05 is not valid without one. “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. V05’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 V05. 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 documentation support one of the more specific codes beneath V05?
    Yes → Select that code and continue the checks below on its own page.
    No → V05 cannot be reported as written; query for the specificity its subcategory needs.

    ReviewV05.0, V05.1, V05.9

  2. Does the documentation support a condition named in V05’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.

    ReviewW03, W00, W51

  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 V05. 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).

Official instructions as workflow

  • Excludes1 — check before selecting V05(3 notes)

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

    CompareW03, W00, W51

    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: Both the condition V05 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).

ReviewW03, W00, W51

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).

Documentation: Only one of the components this code’s title joins is documented.

Coding question: Is V05 supported?

Path: Review the code for the documented component on its own.

Reason: A combination code is assigned only when it fully identifies the documented conditions; otherwise the documented component takes its own code (Guidelines I.B.9).

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.

Don’t confuse V05 with…

MedCoder analysis — pairs from this code’s official notes, distinctions written by MedCoder

The codes most likely to be picked instead of V05 — named in its own official notes, or sharing its laterality or encounter family — with what separates them and which documentation moves the case. Each links to the full comparison.

  • W03— Excludes1 conflict (Excludes1 — generally not reported together)

    Not coded here — the tabular list excludes this pair for the same encounter.

    Not reported together with this code, except where the two conditions are documented as unrelated.

    What moves you there: Documentation of fall due to non-transport collision with other person moves the case to W03; the two are not reported together unless documented as unrelated.

    Full comparison: V05 vs W03 →

  • W00— Excludes1 conflict (Excludes1 — generally not reported together)

    Not coded here — the tabular list excludes this pair for the same encounter.

    Not reported together with this code, except where the two conditions are documented as unrelated.

    What moves you there: Documentation of pedestrian on foot falling (slipping) on ice and snow moves the case to W00; the two are not reported together unless documented as unrelated.

    Full comparison: V05 vs W00 →

  • W51— Excludes1 conflict (Excludes1 — generally not reported together)

    Not coded here — the tabular list excludes this pair for the same encounter.

    Not reported together with this code, except where the two conditions are documented as unrelated.

    What moves you there: Documentation of struck or bumped by another person moves the case to W51; the two are not reported together unless documented as unrelated.

    Full comparison: V05 vs W51 →

  • V05.00XA— Encounter relationship (Review)

    Same underlying diagnosis, different encounter phase.

    The same diagnosis at a different phase of care; one encounter takes one 7th character.

    What moves you there: Documentation of a initial encounter moves the case to V05.00XA.

    Full comparison: V05 vs V05.00XA →

  • V05.00XD— Encounter relationship (Review)

    Same underlying diagnosis, different encounter phase.

    The same diagnosis at a different phase of care; one encounter takes one 7th character.

    What moves you there: Documentation of a subsequent encounter moves the case to V05.00XD.

    Full comparison: V05 vs V05.00XD →

Relationships are read from this code's own official notes, its laterality siblings and its encounter family; the wording of each distinction is MedCoder editorial, and the documentation named in each “what moves you there” line is the official note phrase or sibling title itself. Source: CMS ICD-10-CM tabular instructional notes; ICD-10-CM Official Guidelines, Section I.A.12.a.

Coding context

Guidelines, coding notes, decision aids, relationships (with MS-DRG and CCSR classification), hierarchy, HCC, coverage and the context map: what a coder reaches for after the core. Each section names whether it is official source data, a MedCoder-derived relationship or MedCoder editorial.

Code Overview

Pedestrian injured in collision with railway train or railway vehicle is a non-billable ICD-10-CM category code (V05). A more specific billable subcode must be selected for claims submission.

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

  • Not billable as written — a more specific code is required: V05.00XA, V05.00XD, V05.00XS, V05.01XA, V05.01XD.
  • Requires a 7th character. "The appropriate 7th character is to be added to each code from category V05" Options: V05.00XA, V05.00XD, V05.00XS, V05.01XA, V05.01XD, V05.01XS
  • 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

MedCoder-derived relationships — computed from published CMS and AHRQ datasets

Other codes that name V05 or its code family, from the CMS ICD-10-CM tabular instructional notes. Tabular-note edges are stored at the code family level that carries each note.

Referenced by 14 Excludes1 notes: V00 — Pedestrian conveyance accident, V00.118 — Other in-line roller-skate accident, V00.128 — Other non-in-line roller-skating accident, V00.138 — Other skateboard accident, V00.148 — Other scooter (nonmotorized) accident, V00.218 — Other ice-skates accident, V00.228 — Other sled accident, V00.288 — Other accident on other gliding-type pedestrian conveyance, V00.318 — Other snowboard accident, V00.328 — Other snow-ski accident, V00.898 — Other accident on other pedestrian conveyance, V87 — Traffic accident of specified type but victim's mode of transport unknown, V88 — Nontraffic accident of specified type but victim's mode of transport unknown, W03 — Other fall on same level due to collision with another person.

These codes’ tabular lists mark this diagnosis as mutually exclusive — not reported together unless the conditions are documented as unrelated.

Contextual Map

Every relationship of V05 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.

Run V05 with these 11 related codes in Claim Check

Hierarchy

Excludes1

Referenced by Excludes1 notes (14)

Nearest codes (78)

Change history

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

Reference

Index terms and tables, published questions and FAQ, every source behind this page with its release and checksum, the date-of-service check and the complete change history.

Common coding questions

MedCoder editorial

Can V05 be billed directly?

No. V05 (Pedestrian injured in collision with railway train or railway vehicle) is a non-billable ICD-10-CM category code. A more specific billable subcode must be selected based on clinical documentation.

Does V05 require a 7th character?

Yes. The appropriate 7th character is to be added to each code from category V05; A: initial encounter; D: subsequent encounter; S: sequela.

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 FY2027 tabular list, index and tables, effective October 1, 2026 Release, file and checksum · Publisher’s page
Claim edits Official source data
CMS Definitions of Medicare Code Edits — v44.0 (October 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-derived 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 editorial 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.

Current data releases:ICD-10-CM FY2027 · ICD-10-PCS FY2027 · HCPCS October 2026 · MS-DRG v44 · Medicare Code Editor v44.0 · NCCI PTP Q4 2026 · MUE Q4 2026 · NCD code lists 2026-01 · LCD export September 28, 2026 · All releases and sources

Labels on this page: Official source data · MedCoder-derived relationship · MedCoder editorial explanation. How to read the labels · All data sources and release dates · CMS coding rules

Cite this page

Reference this page in a research guide, syllabus or article. The release is included because code content changes each year.

MedCoder.ai. "V05 — Pedestrian injured in collision with railway train or railway vehicle." ICD-10-CM FY2027. https://medcoder.ai/icd10/code/v05-pedestrian-injured-in-collision-with-railway-train-or-railway-vehicle

Change history

  • FY2016 — October 1, 2015
    In the code set at ICD-10-CM adoption
    Pedestrian injured in collision with railway train or railway vehicle

No changes since FY2016 — additions, deletions, description changes and billable-status changes are tracked through FY2027, 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 V05 in its code family, with their registry titles.