ICD-10 Code V00.892D: Pedestrian conveyance colliding with stationary object, subsequent encounter

Key takeaways

V00.892D describes a pedestrian on another type of pedestrian conveyance colliding with a stationary object — a wall, post, tree, curb, or parked vehicle — not a collision with another rider, at a subsequent encounter.

The code sits inside the V00.89 residual subcategory, where the sixth digit signals the accident type: V00.891 is a fall, V00.892 is colliding with a stationary object, and V00.898 is any other accident.

V00.892D is a billable, specific ICD-10-CM external cause code valid for FY2026, always reported alongside a principal injury diagnosis and never as a standalone primary code.

The 7th character D means subsequent encounter: active treatment for the injury is complete and the patient is receiving routine follow-up care; use V00.892A for the initial encounter and V00.892S for a sequela.

Hoverboards, electric kick scooters, and Segways fall under the separate V00.84 standing micro-mobility subcategory rather than V00.89 — practice management software like Pabau that captures the exact conveyance and encounter phase in the visit note helps coders avoid this kind of misclassification.

Coders working external cause codes often reach for the busier collision-with-another-person codes, but a meaningful share of pedestrian conveyance claims describe something simpler: a single rider losing control and striking something that does not move. ICD-10 Code V00.892D is the billable, FY2026-valid code for exactly that scenario at the follow-up stage — a pedestrian on another type of pedestrian conveyance colliding with a stationary object, at a subsequent encounter. This reference covers the code’s clinical meaning, 7th character rules, related code variants, hierarchy, synonyms, documentation requirements, and answers to the most common coder questions.

ICD-10 Code V00.892D: Definition and Billable Status

ICD-10 Code V00.892D is a billable, specific ICD-10-CM diagnosis code valid for HIPAA-covered transactions in FY2026. Per the CDC/NCHS ICD-10-CM web tool, the code became effective October 1, 2025. It carries a full clinical description: “Pedestrian on other pedestrian conveyance colliding with stationary object, subsequent encounter.” The code sits within the V00-Y99 range of external causes of morbidity, meaning it always functions as a supplementary code alongside a principal injury diagnosis. External cause codes describe the circumstances that caused an injury, not the injury itself, so submitting V00.892D as a standalone primary diagnosis code is incorrect and will trigger a claim edit.

Clinical meaning: what “colliding with a stationary object” covers

The phrase “other pedestrian conveyance” is ICD-10-CM’s residual, not-elsewhere-classified label for personal, non-motorized mobility devices that do not have their own dedicated V00 subcategory. Roller skates, skateboards, non-motorized push scooters, and wheeled shoes (Heelys) are classified under the separate rolling-type subcategory (V00.1x); ice skates and sleds sit under the gliding-type subcategory (V00.2x); snow skis and snowboards sit under the flat-bottomed subcategory (V00.3x); and powered wheelchairs, baby strollers, motorized mobility scooters, and standing micro-mobility devices — electric scooters, hoverboards, and Segways — each have their own dedicated subcategory under V00.81 through V00.84. V00.89 is what is left over: a pedestrian conveyance accident where the specific device is not named elsewhere in the Tabular List, or is not documented precisely enough for a coder to select one of those more specific codes.

Within V00.89, the sixth digit tells coders which type of accident occurred: V00.891 is a fall from the conveyance, V00.892 is the conveyance rider colliding with a stationary object, and V00.898 is any other accident type. A stationary object includes a wall, fence post, tree, parked or stopped vehicle, curb, or similar fixed obstacle — the clinical distinction that matters for V00.892D is that the object the patient struck was not moving.

Coders should confirm the device type against the Tabular List before assigning V00.89, since several common pedestrian conveyances already have their own dedicated code elsewhere in the V00 category:

• Hoverboards, electric kick scooters, and Segways — V00.84 (standing micro-mobility pedestrian conveyance), not V00.89.
• Skateboards and non-motorized push scooters — V00.1x (rolling-type pedestrian conveyance), not V00.89.
• Roller skates and wheeled shoes (Heelys) — V00.1x (rolling-type pedestrian conveyance), not V00.89.
• Powered wheelchairs, baby strollers, and motorized mobility scooters — V00.81 through V00.83, not V00.89.

V00.89 applies when the conveyance genuinely does not fit any of the categories above, or when the documentation does not identify the specific device.

V00.892D codes the scenario where a single rider on such a conveyance strikes something that is not moving — for example, a rider losing control and hitting a parked car, a fence, or a lamp post. It does not describe a collision between two riders. Document the mechanism precisely: the device type if known, the object struck, and which party the patient was.

Per the CDC/NCHS ICD-10-CM Tabular List, the V00 category carries a Type 1 Excludes note. It does not include: collision with another person without a fall (W51); a fall due to a person on foot colliding with another person on foot (W03); a fall from a non-moving wheelchair, non-motorized scooter, or motorized mobility scooter without collision (W05.-); a pedestrian conveyance collision with another land transport vehicle (V01-V09); or a pedestrian on foot falling on ice and snow (W00.-). If the patient collided with a car, bicycle, or other land transport vehicle rather than a stationary object, the correct code range is V01-V09, not V00.

Understanding the 7th character D and subsequent encounter coding

The 7th character is the element coders most commonly get wrong on V00.892 claims. ICD-10 Code V00.892D carries “D” as its 7th character, which the ICD-10-CM Official Guidelines define as “subsequent encounter.” This means the patient is receiving care after the active treatment phase has ended. The CMS ICD-10 coding resources page and the Official Guidelines Section I.C.20 govern when each character applies.

A critical distinction: the 7th character reflects the encounter type from the provider’s perspective, not the patient’s overall care timeline. A patient can have multiple “initial encounter” visits if they are still in the active treatment phase across different providers. Once that phase ends, all follow-up visits use D.

V00.892D vs. V00.892A and V00.892S: choosing the right variant

Coders frequently ask how to distinguish between the A, D, and S variants when a patient presents weeks after a conveyance accident. The answer depends on the treatment status, not the calendar date. Understanding the ICD-10-CM external cause coding for traumatic injuries (as covered in ICD-10-CM coding for traumatic injuries) helps clarify the sequencing principles that apply across injury categories.

One practical rule: if the visit note documents “follow-up for laceration sustained when the patient’s pedestrian conveyance struck a parked car” and the wound is healing without complication, use V00.892D. If the note documents “chronic pain in right wrist, history of pedestrian conveyance collision with a stationary object 18 months ago, now presenting with functional limitation,” use V00.892S. Sequela requires that the original injury has resolved and the current problem is a consequence of the past event.

External cause codes and ICD-10-CM coding guidelines

V00.892D belongs to the V00-Y99 range, the ICD-10-CM chapter dedicated to external causes of morbidity. Per the Official Guidelines Section I.C.20, external cause codes are always supplementary. They provide mechanism-of-injury detail but cannot stand alone as a principal or first-listed diagnosis.

Key guidelines governing the use of V00.892D include the following. Reviewing HIPAA-covered transaction requirements for claim submission also applies when external cause codes are attached to a claim, since payer edits can reject claims where mandatory injury codes are missing.

• External cause codes are sequenced after the principal diagnosis (the injury itself, such as a fracture or laceration code)
• Multiple external cause codes may be assigned if more than one mechanism contributed to the injury
• Some states mandate external cause coding on all inpatient and outpatient claims; others treat it as optional. Check your state’s payer policies before assuming the code is elective.
• A place-of-occurrence code (Y93) and activity code may be assigned alongside V00.892D when documented
• The external cause code should match the 7th character of the principal injury code (if the injury is coded at a subsequent encounter, the external cause code must also carry D)

The AHA Coding Clinic and the ICD-10-CM Official Guidelines for Coding and Reporting (maintained jointly by CMS and NCHS) are the authoritative sources for any sequencing dispute. When a payer questions the placement of V00.892D, cite Section I.C.20 of the current guidelines.

Code hierarchy: where ICD-10 Code V00.892D sits in ICD-10-CM

Understanding the parent-child hierarchy helps coders select the correct subcategory when documentation is ambiguous. V00.892D resolves to a very specific leaf node within a multi-level classification tree. This hierarchy follows the same logical structure used across ICD-10-CM for injury and external cause codes.

The parent code V00.892 is not billable on its own; it requires the 7th character to become a valid, reportable code. Submitting V00.892 without the D, A, or S extension will trigger a claim edit. Always select the fully extended code.

The sixth digit within V00.89 is what distinguishes the three sibling codes from one another:

Approximate synonyms and ICD-10-CM index terms for V00.892D

The ICD-10-CM Alphabetic Index and Tabular List recognize several alternate descriptions that map to V00.892D. When documentation uses informal or variant phrasing, coders can use these synonyms to confirm code selection. Note that procedure codes for rehabilitation-related services referenced in procedure codes for rehabilitation-related services are a separate billing step, but they often accompany these external cause codes when the patient is in the follow-up phase.

• Pedestrian on other pedestrian conveyance colliding with stationary object, subsequent encounter
• Pedestrian conveyance rider striking a fixed object, follow-up encounter
• Non-motorized pedestrian conveyance collision with wall, post, or parked vehicle, subsequent encounter
• Other pedestrian conveyance accident, collision with stationary object, follow-up visit
• Follow-up visit for injury sustained when a pedestrian conveyance struck a stationary obstacle

These synonyms are useful during clinical documentation review. If the chart uses any of these phrasings and the encounter is a follow-up visit, V00.892D is the correct code assignment. Cross-reference unusual conveyance descriptions against the official Tabular List and Alphabetic Index before finalizing the code.

Documentation requirements and common coding errors for V00.892D

Incomplete documentation is the leading cause of external cause code denials. For V00.892D, the clinical record must support three things: the mechanism of injury, the conveyance type, and the encounter phase. This is a genuine content gap compared to most reference pages that list only code definitions without addressing what the chart must actually say. Good clinical documentation captures all three elements at every follow-up visit, not just at the initial encounter.

Required documentation elements for a valid V00.892D claim include the following:

• Mechanism statement: the note must confirm that, while riding a pedestrian conveyance, the patient struck a stationary object such as a wall, post, tree, curb, or parked vehicle. “Patient’s scooter struck a parked car” is sufficient; “patient had a scooter accident” is not.
• Conveyance device: identify the specific device when it is known. Do not use generic terms like “vehicle.” If the device is genuinely unspecified or does not match a named V00 subcategory, document that explicitly so the “other pedestrian conveyance” code is clearly justified.
• Encounter phase confirmation: the note should indicate active treatment for this injury is complete and the visit is for follow-up, wound check, suture removal, or rehabilitation. This is what justifies the D character.
• Principal diagnosis code: a specific injury code (fracture, laceration, contusion) must be listed first. V00.892D cannot appear without a principal diagnosis.

Common coding errors on V00.892D claims are concentrated in two areas. First, coders continue using V00.892A at follow-up visits simply because it was used at the initial encounter, without reassessing the 7th character. Second, practitioners confuse V00.892D with V00.892S when a patient returns months later with residual symptoms, using D when S is clinically appropriate. Using digital intake forms at each follow-up visit helps capture the treatment phase status explicitly, giving coders the documentation clarity they need. Practices managing ongoing injury cases can also benefit from medical intake and injury documentation forms that prompt clinicians to record encounter type at every visit.

For coders managing injury episodes across multiple providers, consistent clinical documentation is what keeps the record accurate at every touchpoint. Practice management software like Pabau centralizes each visit note in one patient record, so the person coding the claim can see whether the injury is still in active treatment or has moved into the follow-up phase, rather than relying on what was documented weeks earlier. ICD-10-CM coding for injury-related conditions such as those covered in ICD-10-CM coding for injury-related conditions follows the same encounter-tracking logic: consistent documentation at every touchpoint protects against audit exposure.

How Pabau supports documentation for external cause follow-up encounters

Many practices track injury follow-up visits the same way they track routine care: a note in the chart, a diagnosis code pulled from memory, and no consistent record of whether the encounter is still “active treatment” or has moved into the follow-up phase. That gap is exactly where V00.892D claims get miscoded — a coder defaults to the initial-encounter character because that is what was used last time, without anything in the record flagging that the treatment status has changed.

Practice management software like Pabau gives clinicians a structured visit note at every follow-up appointment, with fields that prompt for the mechanism of injury, the object involved, and whether active treatment has concluded. Because every visit note lives in one patient record, the person assigning the diagnosis code afterward can see the full sequence of encounters rather than relying on what was documented weeks earlier.

The result is a chart that already answers the question a coder would otherwise have to chase down: is this patient still in active treatment, or is this the follow-up visit that calls for the subsequent-encounter character? For practices handling a steady volume of injury follow-up visits, that consistency reduces the back-and-forth between clinical and billing staff that slows down claim preparation.

Keep injury follow-up documentation complete and consistent

Pabau's customizable visit notes prompt clinicians to record the mechanism of injury, the object involved, and the treatment phase at every follow-up encounter, so coders have the detail they need to select the correct 7th character.

Book a demo

Conclusion

V00.892D is a narrower code than its title suggests: a single rider on a pedestrian conveyance striking something that was not moving, at the follow-up stage of care. Once that scenario is clear, most of the coding difficulty disappears — the work shifts from puzzling over which V00 subcategory applies to making sure the chart actually says what happened.

That is the part worth fixing first. A note that names the conveyance, the object struck, and the treatment phase at every visit gives a coder everything needed to choose between A, D, and S without guessing. Skip that step, and the same 7th character gets carried forward out of habit, which is where most of these claims run into trouble.

Book a demo to see how Pabau’s visit notes and clinical documentation tools help your practice capture that detail consistently, visit after visit.

Continue your research

Need a reference for coding other injury-related ICD-10-CM diagnoses? ICD-10-CM codes for intraparenchymal hemorrhage covers external cause sequencing rules for traumatic injury cases.

Want to reduce documentation gaps at follow-up visits? Digital intake forms capture encounter phase, mechanism of injury, and treatment status at every visit.

Need one record for every follow-up visit on an injury case? Medical records management keeps mechanism-of-injury notes and encounter phase together across every visit.

Frequently asked questions