Codes / ICD10CM / V02.90XD

V02.90XD Pedestrian on foot injured in collision with two- or three-wheeled motor vehicle, unspecified whether traffic or nontraffic accident, subsequent encounter

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Pedestrian on foot injured in collision with two- or three-wheeled motor vehicle, unspecified whether traffic or nontraffic accident, subsequent encounter

Summary

This condition describes injuries sustained by a pedestrian as a result of a collision with a two- or three-wheeled motor vehicle (e.g., motorcycle, scooter, moped) in an unspecified setting (traffic or nontraffic). The "subsequent encounter" modifier indicates this is for encounters after the acute phase of treatment for the injury. Severity varies based on factors like vehicle speed, pedestrian position, and protective measures.

Causes

The primary cause is physical trauma from a collision between a pedestrian and a two- or three-wheeled motor vehicle. Accidents may result from inattentiveness, poor visibility, failure to observe safety measures, or environmental hazards (e.g., road conditions, weather). The unspecified setting means the incident could occur on public roadways or private property.

Risk Factors

  • High foot and motor vehicle traffic in urban or suburban areas.
  • Shared roadways without clear separation (e.g., lack of sidewalks or bike lanes).
  • Lack of protective gear (e.g., helmets) for vehicle operators.
  • Distractions (e.g., mobile device use) during movement by either party.
  • Uneven or poorly maintained surfaces that increase collision risk.

Symptoms

  • Bruises, abrasions, or lacerations.
  • Fractures or dislocations, particularly in limbs.
  • Head injuries, including concussions, if protective gear is absent.
  • Pain, swelling, or reduced mobility in the affected area.

Diagnosis

Physical examination to assess visible injuries and vital signs. Imaging tests (e.g., X-rays, CT scans) may be used to evaluate fractures or internal trauma. Neurological assessments are recommended if head injuries are suspected. Documentation should confirm the collision with a two- or three-wheeled vehicle and the subsequent encounter status.

Treatment Options

Treatment depends on injury severity and may include wound care, immobilization for fractures, pain management, or surgical intervention. Rehabilitation (e.g., physical therapy) may be necessary for recovery. Follow-up care focuses on monitoring healing and addressing any long-term effects.

Prognosis and Follow-Up

Prognosis varies based on injury severity and promptness of care. Most minor injuries heal with conservative treatment, while severe trauma may require extended recovery. Follow-up ensures proper healing, manages complications, and adjusts treatment as needed.

Complications

  • Infection at injury sites.
  • Chronic pain or mobility issues.
  • Neurological deficits from head injuries.
  • Psychological effects (e.g., anxiety, PTSD) related to the accident.

Lifestyle & Prevention

  • Use crosswalks and follow traffic signals when walking.
  • Increase visibility with reflective clothing or lights in low-light conditions.
  • Encourage vehicle operators to wear helmets and follow safety protocols.
  • Maintain awareness of surroundings and avoid distractions (e.g., mobile devices) while walking or riding.

When to Seek Professional Help

Seek immediate care for severe pain, visible fractures, head injuries, or signs of internal bleeding. Follow up with a healthcare provider for worsening symptoms, delayed healing, or new complications during recovery.

Tips for Medical Coders

Document the collision with a two- or three-wheeled motor vehicle and confirm the encounter is subsequent (not initial or acute). Specify if the accident occurred in a traffic or nontraffic setting if known, but use "unspecified" if details are unavailable. Ensure the pedestrian was on foot at the time of injury.

Book a walkthrough

V02.90XD policy automation walkthrough

Walk through the policies, prior authorization requirements, and workflow automation opportunities connected to this code.