HCPCS code P2029: Congo red, blood billing guide
The official description for HCPCS code P2029 is Congo red, blood. It sits in th...
Last Updated: August 12, 2026
Key takeaways
ICD-10 code V79.49XS covers a bus driver injured in a collision with other motor vehicles, billed for the late effects of that crash.
The code is billable and specific, valid on FY2026 claims since October 1, 2025.
Sequence the residual condition first and V79.49XS second, because an external cause code never leads a claim.
The 7th character S applies only after the original injury has healed, so a nonunion still counts as subsequent care.
Leave place of occurrence and activity codes off a sequela claim, since those belong to the initial encounter.
ICD-10 code V79.49XS is the external cause code for a bus driver injured in a collision with other motor vehicles in traffic. You report it when the visit treats a late effect of that crash, not the crash itself.
That distinction is where claims come unstuck. The 7th character S fits only once the original injury has healed, and the code never travels alone on a claim form. Miss either detail and the claim comes back.
What ICD-10 code V79.49XS covers and when it’s billable
V79.49XS is a billable, specific ICD-10-CM code and it is valid on FY2026 claims. The 2026 edition took effect on October 1, 2025, per the CMS ICD-10 codes page. It can be reported on inpatient, outpatient, and physician claims.
The official description reads: Driver of bus injured in collision with other motor vehicles in traffic accident, sequela.
Two facts are baked into that wording. The patient was driving, and the crash happened in traffic, which in ICD-10-CM means on a public highway.
The code lives in the external causes of morbidity chapter, V00-Y99, inside the bus occupant block V70-V79. Everything else about it follows from those two facts and one letter at the end.
What the 7th character S tells the payer
It tells the payer the crash is history and the visit is about what the crash left behind. V79.49 is incomplete on its own, so the code stays invalid and unbillable until a 7th character is added.
The X in the sixth position is a placeholder, not a code choice. V79.49 has no fifth or sixth character of its own, so the X holds the space and keeps S in the seventh slot.
The record has to show which phase of care the patient is in, which is a job for clinical documentation rather than the coder’s judgment. Mixing up D and S is the error to watch, because both look identical in a note that never mentions injury status.
Sequela, subsequent, or initial? Let the healing decide
Healing status picks the 7th character, not the calendar. If the crash injury has healed and a residual problem remains, S is the right letter. If the injury is still healing, it is not.
Take a bus driver who comes in six months after a multi-vehicle collision. Her fractured ribs healed months ago, but she now has lumbar pain and post-traumatic headaches that started with the crash. Those residuals are sequelae, so the external cause code is V79.49XS.
- V79.49XA covers active treatment of the crash injury, from the emergency visit through the first round of fracture care.
- V79.49XD covers routine care while that injury heals, such as a cast change, a wound check, or a medication review.
- V79.49XS covers a residual problem being treated after the original injury has healed.
No guideline sets a waiting period, so elapsed time alone never turns a condition into a sequela. A fracture that has not knitted makes the point. Nonunion is still subsequent care, coded like S52.262K, and the external cause code stays on D.
Practices that see a lot of collision follow-up, chiropractic practices in particular, face this call every week. A patient care management routine that records injury status at each visit turns it into a five-second decision.
Pro Tip
Record injury status in the chart at every visit. A crash injury that is still healing points to the D character. One that healed with a residual problem points to the S character. That single habit prevents most 7th character errors on external cause claims.
How the code is built, from chapter to 7th character
V79.49XS sits at the bottom of a six-level structure, and the levels above it set the rules it inherits. Excludes notes and instructions cascade down from the block and the category, so reading upward is part of coding it correctly.
One row deserves a second look. V79.4 covers collisions with other and unspecified motor vehicles, and the fifth character splits those two ideas.
Use V79.49 when the record names the other vehicle. Use V79.40 when the note simply says another vehicle was involved.
The index terms that lead to this code
Coders arrive at V79.49XS from plain-language phrases, because charts rarely echo the code descriptor.
Knowing which phrases land here saves a trip through the tabular list. The CDC coding tool searches the same index if the wording in the note is unusual.
- Bus operator injured in a motor vehicle collision in traffic, late effect
- Motorcoach driver injured in a collision with another motor vehicle in traffic, sequela
- Driver of bus in a traffic accident with another motor vehicle, sequela
- Late effect of a bus driver’s injury from a multi-vehicle traffic collision
- Residual condition following a bus driver’s traffic collision
Watch what the other vehicle was, because that detail moves the code out of V79 entirely. If the note names a car, a pick-up truck, or a van, the bus occupant codes sit in the V73 family instead. A sport utility vehicle counts there too. V79.4 is for other and unspecified motor vehicles.
One more piece of vocabulary. “Late effect” in older documentation means the same thing as “sequela” in ICD-10-CM.
Both point to a residual condition left behind after the acute phase resolved. Rehabilitation notes in a physical therapy practice still use the older phrase regularly.
Which excludes notes apply, and which don’t
Only one Excludes1 note above this code changes what you may report.
The V70-V79 block excludes a minibus, which is classified with pick-up trucks and vans in V50-V59. Everything else you may have heard about excludes notes here needs checking.
- Includes (V70-V79): motorcoach. A motorcoach injury belongs in this block, so the wording in the chart does not have to say “bus”.
- Excludes1 (V70-V79): minibus, classified to V50-V59. Excludes1 means the two are never reported together for the same event.
- Traffic and nontraffic: separate subcategories, not an excludes rule. V79.0 to V79.3 cover nontraffic events and V79.4 to V79.9 cover traffic events.
So the traffic decision is a selection choice rather than a restriction. A crash either happened on a public highway or it did not, and the subcategory follows.
Other vehicle families work the same way, which is how a nontraffic sequela such as V86.54XS ends up in a different block.
Nothing stops V79.49XS from sitting next to the code for the residual condition. The guidelines actually require that pairing, which is where most of the claim trouble starts.
The claim needs two codes, in this order
The residual condition goes first and V79.49XS goes second. An external cause code explains how an injury happened, so it never carries the medical necessity for the visit. On its own it tells a payer nothing about what was treated.
That order comes from Section I.C.20.i of the ICD-10-CM Official Guidelines, the sequela guidance inside the external cause chapter.
- First: the code for the residual condition being treated today. Cervicalgia, M54.2, and post-traumatic headache, G44.309, are common choices, and cervical spondylosis with radiculopathy would be M47.22.
- Second: V79.49XS, which records the crash that caused the residual condition.
When the residual is itself an injury code, it carries its own 7th character. A residual after a lumbar sprain is reported as S33.8XXS first, then V79.49XS. A healed wrist fracture that still causes trouble works the same way, coded as S62.032S. A residual coded as a condition, such as cervicalgia, has no 7th character at all.
Two code groups stay off a sequela claim. Place of occurrence codes (Y92), activity codes (Y93), and the external cause status code (Y99) are reported once, at the initial encounter. They are not used for sequelae.
On the claim itself, V79.49XS is an additional diagnosis rather than a billed target. Service lines point at the residual condition, since that is the diagnosis a payer reads for medical necessity. V79.49XS supplies the backstory that supports it.
Pro Tip
Never send V79.49XS on its own. It always follows the code for the residual condition being treated. A claim carrying only the external cause code comes back as a rejection or a medical necessity denial. Reworking it costs more than coding it right the first time.
Before you submit: A quick check
Seven checks catch nearly every problem this code creates. Run them before the claim leaves the practice.
- The note says the original crash injury has healed, and names the residual being treated today.
- The residual condition is the first-listed diagnosis, with V79.49XS sitting after it.
- The 7th character is S, and the placeholder X fills the sixth position.
- The other vehicle was not a car, a pick-up truck, or a van. Those collisions belong in V73.
- The crash happened on a public highway, which is what makes it a traffic accident.
- No place of occurrence, activity, or external cause status code rides along.
- Your state or your payer actually wants external cause codes, because no national mandate requires them.
Two mistakes show up more than the rest. The first is reporting V79.49XS beside a current injury code. The guidelines rule that out, because one visit cannot be both acute care and sequela care for the same injury.
The second is carrying S forward out of habit. A fracture that fails to knit is still subsequent care. So is a routine follow-up visit with no documented residual. Both sit in the healing phase rather than the late-effect phase.
Sibling codes in V79 worth knowing
The rest of the V79 family turns on two questions: who the patient was in the vehicle, and whether the crash was in traffic. Use the table as a cross-reference when the note answers those questions differently.
Driver against passenger matters beyond the code set. Workers’ compensation and liability cases turn on the role in the record, so pick the code that matches where the patient was sitting. V79.3XXS covers either role, but only for a nontraffic event.
How Pabau keeps the code, the note, and the claim together
Most sequencing errors start life as a documentation problem. The coder cannot tell from the note whether the crash injury healed. So the 7th character becomes a guess, and payers send guesses back.
Practice management software like Pabau keeps the treatment note, the injury history, and the invoice on one client record. Nothing gets re-keyed between a clinical system and a billing system. So the detail that decides D or S is on screen at the moment the code is picked.
Digital intake forms capture how the accident happened in the patient’s own words. That is the same detail that separates a traffic code from a nontraffic one.
Claims management then bills from the record the clinician wrote in. The crash story travels with the claim rather than being rebuilt from memory months later.
Keep diagnosis codes with the note that earns them
Pabau holds client records, treatment notes, and invoicing in one system, so the injury detail behind a 7th character never has to be reconstructed. See how documentation and claims work together in a live demo.
Conclusion
The 7th character is a documentation decision before it is a coding decision. Once a note states plainly that the crash injury healed and names what it left behind, S is easy to defend and easy to audit.
Two habits keep V79.49XS out of the denial pile. Sequence the residual condition first, and record injury status at every visit. Book a demo to see how Pabau keeps treatment notes, diagnosis codes, and claims on the same record.
Continue your research
Coding a nontraffic sequela instead? V86.54XS shows how the nontraffic side of external cause coding is handled.
Need the sequencing rules for a residual sprain? S33.8XXS covers billing, sequencing, and the denials that follow a late effect.
Not sure whether a fracture counts as healed? S52.262K explains why nonunion stays in the subsequent encounter phase.
Looking for a nature-of-sequela example to sequence first? S62.032S walks through a healed wrist fracture with a residual problem.
Want the same 7th character outside road traffic? V90.21XS applies sequela rules to a water transport accident.
Frequently asked questions
Is reporting V79.49XS mandatory?
No. There is no national requirement to report external cause codes. Report V79.49XS when your state has a reporting mandate, or when the payer asks for it. Auto and workers’ compensation carriers usually do.
Can V79.49XS be the first-listed diagnosis?
No. An external cause code is never first-listed or principal. The residual condition being treated takes that slot, and V79.49XS follows it as an additional diagnosis.
Do place of occurrence and activity codes go with it?
No. Y92, Y93, and Y99 codes are assigned at the initial encounter only. A sequela claim carries the residual condition and the external cause code, and nothing else from Chapter 20.
How long can V79.49XS stay on claims?
For as long as the residual condition is treated, since no guideline sets an end date. The record has to keep tying that condition back to the crash, so causation stays documented at each visit.
Does the claim need the accident date?
Usually yes for auto and workers’ compensation claims. Those payers want the date of the original accident on the claim, since V79.49XS alone does not prove causation.
Does a follow-up visit with no residual use V79.49XS?
No. Routine follow-up on a healing injury takes the subsequent encounter character. Use S only when a late effect is documented and treated at that visit.
