ICD code V09.01XS – Pedestrian injured in nontraffic accident involving military vehicle

Key takeaways

V09.01XS identifies a pedestrian injured in a nontraffic accident involving a military vehicle, reported at the sequela encounter stage.

The seventh character S (sequela) means the active injury phase has resolved and the visit treats a late complication of the original incident.

The sequela condition is coded first as the principal diagnosis, and V09.01XS follows it as the external cause code.

Pabau, the practice management platform we build, checks each claim for missing or invalid details before it goes to Claim.MD for submission.

ICD-10 Code V09.01XS: Code description and clinical meaning

ICD-10 code V09.01XS carries the official descriptor “Pedestrian injured in nontraffic accident involving military vehicle, sequela.”

It is a secondary external cause code, reported when a visit treats a late effect of that injury. Each segment of the code answers a specific question about the original incident.

The placeholder X is not optional. Without it, the code truncates to six characters and fails the ICD-10-CM structural requirement for seventh character assignment. Coders sometimes omit it when transcribing the code manually, which produces an invalid string and triggers an automatic edit.

Per the ICD-10-CM tabular list, V09.01 covers a military vehicle involved in a nontraffic accident with a pedestrian. Code only the vehicle the record documents, and don’t stretch the subcategory to cover other vehicle types.

Code hierarchy: Where V09.01XS sits in ICD-10-CM

V09.01XS belongs to the external cause chapter of ICD-10-CM. Understanding its parent-to-child path helps coders navigate to adjacent codes when the clinical facts require a different selection. You can browse the full hierarchy using the CDC/NCHS ICD-10-CM web tool, which mirrors the current fiscal year tabular list.

• Chapter 20: External causes of morbidity (V00-Y99)
• Block V00-V09: Pedestrian injured in transport accident
• Category V09: Pedestrian injured in other and unspecified transport accidents
• Subcategory V09.0: Pedestrian injured in nontraffic accident involving other and unspecified motor vehicles
• V09.01: Pedestrian injured in nontraffic accident involving military vehicle
• V09.01XS: Sequela encounter (this code)

The V09 category captures pedestrian incidents that do not fit neatly into the more specific V01-V08 blocks. Before settling on V09.01XS, check the ICD-10-CM code library for a more specific code elsewhere in the chapter.

Seventh character S: Understanding the sequela extension

Sequela, in ICD-10-CM terms, is a late effect or residual condition that persists after the acute phase of the original injury has ended. The seventh character S signals this condition to payers and reviewers. It is governed by ICD-10-CM Official Guidelines Section I.C.19.a.

Three seventh characters are valid for V09.01. Their meanings are mutually exclusive and cannot appear on the same claim for the same injury episode.

The clearest test for S versus D is the state of healing. If the original wound or fracture is still actively healing, D applies. If healing is complete and a complication of the original injury brings the patient in, S applies.

Adjacent and easily confused codes

The V09.0 subcategory contains several codes that describe nontraffic pedestrian accidents but differ in the vehicle type involved. Selecting the wrong sibling code is a common specificity error that payers may flag during audits.

Traffic versus nontraffic is the single most consequential distinction in the V09 block. A nontraffic accident occurs on private property, a military base, an industrial site, or any location not classified as a public highway. If the documentation is ambiguous, query the provider before defaulting to “unspecified.” The decision path below runs those checks in order, from setting to vehicle to seventh character.

Documentation requirements to support V09.01XS

Code specificity obligations under medical billing compliance guidelines require the medical record to justify every granular element of a code. For V09.01XS, four documentation elements must be present.

1. Nontraffic setting confirmed: The record must state or clearly imply that the incident did not occur on a public road. Acceptable language includes references to a military installation, a private base, a restricted compound, or a comparable nonpublic location.
2. Vehicle identified as military: The provider’s note, operative report, or ER documentation must name the vehicle or describe it as a military vehicle. “Truck” alone does not suffice.
3. Sequela linkage established: The treating clinician must document that the condition being treated is a direct, late consequence of the original pedestrian injury. A statement tying the current diagnosis to the prior incident, with its date and the nature of the injury, puts that link in writing.
4. Original injury code referenced or implicit: The sequela condition is coded first, and V09.01XS follows as the external cause code. The record should allow a coder to identify the original injury type so the principal diagnosis code can be selected correctly.

When documentation is incomplete, the correct action is a physician query before coding, not an assumption. Assumptions that produce a more specific code without record support expose the practice to audit liability.

How to code sequela claims: Step-by-step

Sequela coding follows a defined sequence under ICD-10-CM guideline I.C.19.a. Getting the order wrong is one of the most reliable ways to generate a denial on a V09.01XS claim. The first rule of medical billing basics applies here too: an external cause code never leads the claim.

1. Code the sequela condition first: The residual condition (for example, chronic neuropathic pain, post-traumatic gait disorder, or scar contracture) becomes the principal diagnosis. This is the code that appears in the primary diagnosis position on the claim form.
2. Sequence V09.01XS as the external cause: The code goes in a secondary diagnosis position. It explains the origin of the condition, not the condition itself. It cannot occupy the principal diagnosis slot for a sequela encounter.
3. Never mix seventh characters for one injury: A claim carrying both V09.01XA and V09.01XS for the same injury and encounter fails edit checks. The encounter is either in the active treatment phase (A), healing phase (D), or sequela phase (S). One applies.
4. Check the S extension on the principal diagnosis too: Chapter 19 injury codes that take a seventh character also use S when coded as sequela. Confirm in the tabular list before submitting.

Payer requirements and claim submission

External cause codes including V09.01XS are not universally required across all payers. Requirements vary by payer type and, for state Medicaid programs, by jurisdiction. Confirm requirements against current Local Coverage Determinations (LCDs) and payer-specific billing manuals before assuming any rule applies universally.

Common claim denials and how to avoid them

V09.01XS claims fail for predictable reasons. A structured denial management workflow reduces rework by catching these errors at the pre-submission stage rather than after a rejection.

• Wrong seventh character used: Using A or D on a sequela encounter is the most common coding error. Active treatment has ended, and the patient is now being seen for a chronic complication. The encounter type must match. Verify the clinical phase before assigning the seventh character.
• External cause code in the principal diagnosis position: V09.01XS is an external cause code. It cannot occupy the principal diagnosis slot under any circumstance. The sequela condition goes first, and V09.01XS follows as a secondary code. Reversed sequencing triggers an automatic edit on most clearinghouses.
• Missing specificity in the record: If the record doesn’t separate nontraffic from traffic or name the vehicle as military, V09.01XS can’t be justified. The claim may be downcoded to V09.00XS (unspecified motor vehicle) or V09.1XXS (unspecified nontraffic accident), both of which may affect coverage determinations.
• Incompatible principal diagnosis: The sequela condition coded first must be clinically linkable to a pedestrian injury. Pairing V09.01XS with an unrelated principal diagnosis raises a medical necessity flag. An acute infection with no injury context is a typical example.
• Placeholder X omitted: Submitting V09.01S rather than V09.01XS produces an invalid code string. Clearinghouse edits will reject it before the claim reaches the payer. A thorough pre-submission scrub using clean claim standards catches this before it becomes a denial.

How Pabau catches V09.01XS errors before a claim goes out

Without a claims tool, a coder keys V09.01XS by hand and checks its sequencing and seventh character by eye. One dropped placeholder X or a reversed code order sends the claim back.

Pabau’s claims management software scrubs each claim for missing or invalid details before it leaves Pabau, so a fix takes seconds. US claims then go out as electronic CMS-1500 submissions through Claim.MD, Pabau’s clearinghouse partner for thousands of payers.

Real-time eligibility checks run before the visit, so you know whether the patient’s plan covers the sequela treatment. Remittances flow back into Pabau, so a denied V09.01XS claim surfaces in one place for follow-up.

Stop claim denials before they start

Pabau’s claim validation flags missing or invalid details on claims like V09.01XS before submission. Clean claims then go to thousands of US payers through Claim.MD.

Book a demo

Conclusion

V09.01XS rewards the coder who reads the record before reaching for the code. It applies only when three facts line up: a sequela encounter, a nontraffic accident, and a vehicle documented as military. If one is missing, query the provider or move to the matching sibling code in category V09.

The payoff is a claim that survives an audit and gets paid on the first pass. The cost is a few minutes of record review and a pre-submission scrub on every sequela claim. Book a demo to see how Pabau’s claim validation catches sequencing and seventh-character errors before your V09 claims reach the payer.

Continue your research

Need a clearinghouse that handles V09 external cause codes? Pabau’s Claim.MD clearinghouse guide explains how electronic claim submission handles ICD-10 external cause coding validation across thousands of US payers.

Want to understand denial patterns for external cause codes? Denial codes in medical billing covers the CARC denial codes most commonly returned on sequela and external cause submissions.

Looking for guidance on claim submission workflows? Revenue cycle management explained walks through the full claim lifecycle from coding through payment posting.

Frequently asked questions