Chat with GenHealth to automate any coding or chart task.
Name of the Condition
- Pedestrian on other standing micro-mobility pedestrian conveyance injured in collision with two- or three-wheeled motor vehicle, unspecified whether traffic or nontraffic accident, subsequent encounter
Summary
This condition refers to injuries sustained by a pedestrian using an "other standing micro-mobility pedestrian conveyance" (e.g., non-electric scooter, self-balancing device) as a result of a collision with a two- or three-wheeled motor vehicle (e.g., motorcycle, moped). The incident may occur in either traffic or nontraffic settings, and injury severity depends on factors like vehicle speed, pedestrian position, and protective measures. The "subsequent encounter" modifier indicates this is for encounters after the acute phase of treatment.
Causes
The primary cause is physical trauma from a collision between a pedestrian on an other standing micro-mobility conveyance and a two- or three-wheeled motor vehicle. Accidents can result from factors such as inattentiveness, poor visibility, failure to observe safety measures, or environmental hazards like road conditions or weather.
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 or micro-mobility users.
- 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 to extremities.
- Head injuries (e.g., concussions) if protective gear is absent.
- Soft tissue damage or internal injuries from impact.
- Pain, swelling, or reduced mobility at the injury site.
Diagnosis
Diagnosis involves a clinical evaluation of the injury, including a physical examination and patient history of the collision. Imaging (e.g., X-rays, CT scans) may be used to assess fractures or internal damage. Documentation should specify the type of micro-mobility conveyance, the motor vehicle involved, and the accident context (traffic/nontraffic) if known.
Treatment Options
Treatment depends on injury severity and may include wound care, immobilization for fractures, pain management, and rehabilitation. Severe cases may require surgery or ongoing physical therapy. Follow-up care focuses on monitoring recovery and addressing any complications.
Prognosis and Follow-Up
Prognosis varies based on injury type and severity. Minor injuries may resolve with conservative care, while severe trauma could lead to long-term disability. Follow-up ensures proper healing, manages chronic pain, and addresses any functional limitations. Rehabilitation may be necessary for mobility or strength restoration.
Complications
- Chronic pain or reduced mobility from unresolved injuries.
- Infection at wound sites.
- Long-term disability from severe fractures or head trauma.
- Psychological effects (e.g., anxiety) related to the accident.
Lifestyle & Prevention
- Use protective gear (e.g., helmets, pads) when operating micro-mobility devices.
- Follow traffic rules and stay alert in shared spaces.
- Maintain devices to avoid mechanical failures.
- Improve visibility with lights or reflective clothing.
- Choose safe, well-maintained surfaces for use.
When to Seek Professional Help
Seek immediate care for severe pain, visible deformities, head injuries, or difficulty breathing. Follow up with a healthcare provider for persistent symptoms, worsening pain, or signs of infection (e.g., redness, swelling, fever).
Tips for Medical Coders
Use this code for subsequent encounters (after active treatment) for injuries from the specified collision. Document the type of micro-mobility conveyance, motor vehicle, and accident context (traffic/nontraffic) if available. Ensure the "subsequent encounter" modifier aligns with the patient’s treatment phase.
V02.938D policy automation walkthrough
Walk through the policies, prior authorization requirements, and workflow automation opportunities connected to this code.