ICD code V01.92XD – Skateboarder hit by a bicycle, follow-up

Key takeaways

V01.92XD codes a skateboarder hit by a pedal cycle at a follow-up visit, when the record doesn’t say traffic or nontraffic.

It is an external cause code, so the injury code always goes first on the claim.

A named location changes the code: V01.02XD for a nontraffic accident, V01.12XD for a traffic accident.

The X in position 6 is a placeholder, and the code is invalid without it.

D fits routine care while the injury heals, and active treatment still takes A, even at a later visit.

ICD-10 code V01.92XD means a skateboarder was hit by a bike

ICD-10 code V01.92XD describes a pedestrian on a skateboard who was injured in a collision with a pedal cycle. The record doesn’t say whether it was a traffic or nontraffic accident. The final D marks a subsequent encounter, so you use it at follow-up visits while the injury heals.

In ICD-10-CM, a person on a skateboard counts as a pedestrian. That is why this code lives in category V01, with walkers and roller skaters, and not in the cyclist codes.

The code explains how the injury happened. It never explains what the injury is. You still need an injury code from Chapter 19, such as a contusion or a fracture, and that code goes first.

Where the code sits in the hierarchy

Each character in V01.92XD tells the payer something

Read the code one character at a time and the logic gets easy. Change one character and you describe a different accident.

Why the X can’t be skipped

V01.92 has only five characters, but the category needs a 7th character. The placeholder X fills the empty sixth position. If you send V01.92D, the code is invalid, because the D lands in the wrong position.

Encoders usually add the X for you. Problems tend to start with hand-typed codes and copied templates, so check the full seven characters.

Traffic status picks the right V01 sibling code

Category V01 splits three ways on location. V01.0 covers nontraffic accidents, and V01.1 covers traffic accidents. V01.9 is for records that don’t say which.

Within each split, the fifth character names how the pedestrian was moving. Here are the subsequent-encounter codes side by side.

So V01.91XD is not the traffic version of this code. It means a person on roller-skates, with traffic status unknown. That mix-up is easy to make when you scan the list fast.

Check the notes before you settle on “unspecified”

The ICD-10-CM transport notes define a traffic accident as one on a public highway. They also say a vehicle accident is assumed to be on the public highway unless another place is specified.

So look hard for a location first. A note like “hit by a cyclist on Main Street” points to V01.12XD. “Clipped by a bike at the skate park” points to V01.02XD.

Strictly, the tabular assumption points to a traffic code (V01.1-) when no place is given. V01.9- is for records where traffic status can’t be determined. Check your payer and facility policy.

A, D or S? Let the care decide, not the calendar

The 7th character follows the type of care at this visit. It doesn’t count visits. The rules sit in the ICD-10-CM Official Guidelines, Section I.C.19.a.

A patient can have many D visits. A skateboarder seen for a cast check in week two and again in week six gets D both times.

The external cause code carries the same idea. Under Section I.C.20, you report it at each encounter where the injury is treated, with the matching 7th character.

A worked example: coding the skateboarder’s follow-up

Here is how the code plays out across two visits. The patient is a 15-year-old who was hit by a bike while skateboarding. The notes leave the traffic status undetermined.

Visit one, the emergency department

The provider diagnoses a contusion of the right knee and treats it. The coder reports S80.01XA first, then V01.92XA. Any place of occurrence and activity codes also go on this first visit.

Visit two, the follow-up two weeks later

The knee is healing, and the provider checks progress. The coder reports S80.01XD first, then V01.92XD.

The place and activity codes don’t come back. Under Sections I.C.20.b and I.C.20.c, each one is reported once, at the initial encounter for treatment.

When V01.92XD is the wrong code for the visit

This code fits a narrow scene. Four questions about the record decide whether a visit lands on it.

Switch codes if the record shows any of the following.

• The patient was the cyclist. Pedal cycle riders are coded in V10-V19.
• The skateboarder fell alone. A fall from a skateboard is V00.131-, and hitting a stationary object is V00.132-.
• The patient was on foot. Use V01.90XD, or V01.00XD and V01.10XD when the location is known.
• The location is documented. Use V01.02XD for nontraffic or V01.12XD for traffic.
• A motor vehicle hit the skateboarder. Look in V02-V09 for the vehicle type. A bus or heavy transport vehicle, for example, takes V04.92XD.
• Active treatment is still going. Use V01.92XA.
• The visit treats a late effect. Use V01.92XS, after the sequela condition code.

Before you submit, run this five-point check

A minute with the chart saves a resubmission later. Work through these points in order.

1. Role. The patient was the skateboarder, not the cyclist.
2. Vehicle. The notes say “bicycle”, “bike” or “pedal cycle”.
3. Place. You searched the notes, and traffic status still can’t be determined.
4. Phase. The plan shows routine healing care, not active treatment.
5. Order and format. The injury code is first, and the code reads V01.92XD, seven characters with the X.

This kind of review is the core of medical billing compliance for injury coding.

Common mistakes that send this claim back

These errors show up again and again on V01 claims. Each one is easy to catch once you know to look.

• Listing V01.92XD first. External cause codes are never the first-listed diagnosis. Put the injury code ahead of it.
• Reading V01.91XD as the traffic version. It means roller-skates. The skateboard traffic code is V01.12XD.
• Dropping the X. V01.92D is not a valid code.
• Using D during active treatment. A second visit can still be an initial encounter.
• Repeating place and activity codes. They belong on the initial encounter only.
• Sending the cause code alone. V01.92XD explains a mechanism, so it needs an injury code to explain the visit.

If one of these slips through, the remittance names the problem with a standard denial code. A clear denial management routine then helps you fix and resend the claim fast.

How the claim moves from the chart to the payer

It helps to see where each check happens. A typical follow-up claim moves like this.

1. The provider documents the injury, the cause and the plan.
2. The coder assigns the injury code, then V01.92XD.
3. The biller adds the procedure codes and checks the order.
4. The claim goes out electronically through a clearinghouse.
5. The payer processes it and sends back a remittance.

Most coding errors start at steps one and two. A clean claim depends on a clear note and a careful coder more than on any software.

How Pabau helps you send injury follow-up claims

Follow-up visits for injuries create a lot of small billing tasks. Each one needs the right codes, an invoice and often the next appointment.

Pabau, the billing and scheduling software we make for practices, keeps those steps in one place. Your team records the visit and adds the diagnosis codes to the claim. Then claims management sends it out.

In the US, claims go out electronically through our Claim.MD integration. So your billers spend less time re-keying claims and more time on the checks above.

Send injury follow-up claims with less re-keying

See how Pabau records the visit, adds the diagnosis codes and sends the claim electronically through Claim.MD.

Book a demo

Conclusion

V01.92XD is a fallback for one narrow case. Use it when a skateboarder hit by a bike comes back for routine healing care, and the record can’t settle traffic status.

Most of the time, a closer read of the notes gives you a location. That moves you to V01.02XD or V01.12XD and makes the claim more precise. The trade-off is a few extra minutes per chart, and on injury follow-ups that time pays off.

Book a demo to see how Pabau helps your team code, bill and send injury follow-up claims in one workflow.

Continue your research

Need a process for denied injury claims? Denial management in healthcare walks through tracking, appealing and resolving denials.

Curious how a clearinghouse handles your claims? Pabau’s Claim.MD clearinghouse guide explains how claims travel from your system to the payer.

Want fewer front-end rejections? Clean claim submission covers the details that get a claim paid the first time.

Looking at the bigger billing picture? What is revenue cycle management shows how coding fits into getting paid.

Frequently asked questions