ICD code V79.60XS – Bus occupant collision sequela

Key takeaways

V79.60XS is valid and billable for fiscal year 2026 as an external cause code for bus occupant collision sequela

Use the 7th character S only when treating a residual condition caused by the earlier bus accident, never for a fracture still healing

V79.60XS is always an additional code, so it can never be the principal or primary diagnosis

A sequela encounter requires two codes: the residual condition code first, then V79.60XS as the external cause

ICD-10 Code V79.60XS: Official descriptor and code facts

ICD-10 Code V79.60XS has one official descriptor in the CMS ICD-10-CM tabular list. It reads: Unspecified bus occupant injured in collision with unspecified motor vehicles in traffic accident, sequela.

The code is billable and valid for the 2026 fiscal year. Report it as a secondary external cause code whenever the condition being treated traces back to a qualifying bus accident.

What the sequela 7th character (S) means for V79.60XS

The 7th character S in ICD-10 Code V79.60XS designates a sequela encounter. The visit treats a condition that the earlier bus collision caused directly, and the active injury phase is over.

Under the ICD-10-CM Official Guidelines for Coding and Reporting, Section I.B.10, sequela coding applies once the original injury has resolved but a residual condition remains.

Typical examples include post-traumatic cervical radiculopathy developing months after a bus rear-end collision, or chronic knee instability persisting after ligament damage from the original crash.

A sequela is the residual condition left behind, so ongoing treatment of an unhealed fracture never qualifies. That distinction sits at the core of the A/D/S decision, and coders get it wrong more often than any other part of this code family.

The three 7th characters for V79.60

V79.60XS vs V79.60XA vs V79.60XD: Choosing the right encounter type

The difference between V79.60XS and its siblings V79.60XA and V79.60XD comes down to whether the original injury is still being actively treated. A patient returning six months after a bus crash with persistent neck pain and radiculopathy uses S.

A patient returning three weeks post-crash for a follow-up X-ray on an unhealed rib fracture uses D instead. The word “subsequent” describes the status of the injury rather than the calendar. It applies for as long as the crash injury itself is the condition being managed.

One practical test settles most cases. Ask whether the physician documented a new residual diagnosis, such as cervical spondylosis or nerve damage, alongside the external cause code.

If yes, that is a sequela encounter (S). If the physician is still treating the fractured rib or soft-tissue injury from the crash, the encounter is subsequent (D), however many months have passed.

Who counts as an unspecified bus occupant

An unspecified bus occupant is any person aboard the bus whose specific role cannot be determined from the medical record. ICD-10-CM offers more specific V79 subcodes for drivers and passengers. V79.60XS applies only when the documentation does not clearly identify the occupant type.

• Use V79.60XS when the record says “bus occupant” or “patient was on the bus” without specifying driver or passenger
• Use a driver-specific V79 subcode when the record confirms the patient was operating the bus
• Use a passenger-specific V79 subcode when the record confirms the patient was a fare-paying or non-driving occupant
• Do not assume “unspecified” when the record supports a more specific code. The ICD-10-CM specificity principle requires the most precise code the documentation supports

Emergency department notes, police reports referenced in the record, and patient-reported history can all support a more specific occupant designation. Query the treating provider before defaulting to the unspecified code when that information is available in the chart.

Where V79.60XS sits in the ICD-10-CM hierarchy

V79.60XS is classified within the external causes of morbidity chapter of ICD-10-CM, confirmed by the CDC/NCHS ICD-10-CM web tool. Understanding the hierarchy helps coders navigate the tabular list and select the correct level of specificity.

The same breakdown appears on every page in our library of ICD-10-CM codes, which helps when comparing V79.60XS against a neighboring subcategory.

Neighboring codes that coders confuse with V79.60XS

Several sibling codes within the V79 category are frequently selected in error. The most common confusion points involve the occupant-type distinctions and the encounter-type suffix.

Required sequencing and additional codes for V79.60XS

V79.60XS is an external cause code and must never be sequenced as the principal or primary diagnosis. This is an absolute rule in the ICD-10-CM Official Guidelines, Section I.C.20. Claims that list V79.60XS as the first-listed diagnosis will be rejected by payers, however strong the documentation.

A sequela encounter always requires two codes in sequence:

1. The residual condition code (principal/primary), naming what the patient is treated for today: cervical radiculopathy M54.12, post-traumatic headache G44.309, or chronic pain G89.29
2. V79.60XS (additional/secondary), which identifies the original bus collision as the external cause of the residual condition

Never submit V79.60XS alone. Without the residual condition code in first position, the claim has no billable diagnosis and will be denied. The residual condition code must use its own sequela or appropriate encounter-type 7th character where applicable.

Documentation requirements for V79.60XS claims

Every V79.60XS claim requires documentation that supports both the sequela 7th character and the unspecified occupant designation. A missing element turns the submission into rework. The wider clean claim submission checklist covers the rest of what a payer looks for.

• Confirmed history of bus collision: the record documents that a bus collision occurred. An approximate date is acceptable, such as “bus accident roughly 18 months ago”
• Residual condition with causal linkage: the treating physician names the current residual condition and states that it results from the crash. For example, “cervical radiculopathy secondary to bus MVA in 2024”
• Occupant type: the record notes the patient’s role on the bus, or records that this detail is unknown, which justifies the unspecified designation
• Active injury resolved: documentation shows the original crash injury is no longer the active condition. The visit is for a downstream sequela
• Date of original injury and current encounter: both dates are derivable from the record, and some payers require the accident date on the claim form

Coders cannot add a causal linkage the provider did not document. If the chart shows a post-crash condition but the physician has not connected it to the original accident, query the provider before assigning V79.60XS. Submitting the sequela external cause code without a documented causal link is a compliance risk.

Why V79.60XS claims get denied and how to fix them

V79.60XS denial patterns cluster around four errors, and a pre-submission check catches all four. The table below pairs each denial with its root cause and the correction that clears it.

Payer and compliance considerations for V79.60XS

External cause codes including V79.60XS are accepted by Medicare, Medicaid, and most commercial payers as secondary codes, though acceptance policies vary. Bus collision cases frequently involve auto liability insurance or workers’ compensation as the primary payer, ahead of health insurance. That coverage order decides which payer receives the claim first.

• Medicare: accepts external cause codes as informational secondary codes. It does not require them on every claim, though they support medical necessity for sequela care. The AAPC ICD-10-CM code reference notes that MACs may issue Local Coverage Determinations affecting the residual condition diagnoses paired with these codes
• Medicaid: state-specific policies apply. Some state programs require external cause codes on injury-related claims, so verify with the relevant program before assuming acceptance
• Commercial payers: most commercial plans follow the ICD-10-CM Official Guidelines for external cause codes. Check the payer’s claim-editing rules for NCCI edits affecting the pair of V79.60XS and the residual condition code
• Auto liability and workers’ comp: a work-related bus accident, or one involving a third-party vehicle, often puts auto liability or workers’ comp first. Those payers set their own injury code requirements and may not use ICD-10-CM at all. Health insurance billing with V79.60XS usually follows once primary coverage is exhausted or denied

How Pabau keeps external cause codes in the right claim position

Sequencing errors on external cause codes usually surface after the denial arrives. A biller enters the residual condition code and V79.60XS, the clearinghouse passes the claim through, and the rejection lands weeks later. The encounter is closed by then, so the fix becomes rework.

Practice management software like Pabau checks the claim while the encounter is still open. Pabau’s claims management software validates diagnosis order before submission, so an external cause code in first position gets flagged at the point of coding.

That changes what the billing team spends its week on. Denials that used to arrive in a monthly batch get resolved at the desk instead. The documentation query reaches the provider while the visit is still fresh.

Stop sequencing errors before they reach the payer

Pabau’s claims management tools validate code sequencing and flag external cause code placement before submission, so these denials get prevented rather than reworked.

Book a demo

Conclusion

V79.60XS rarely fails on the code selection. It fails on the encounter-type judgment behind it, and that judgment depends on documentation the coder cannot write alone. Building the provider query into the coding step, rather than into the appeal, is what keeps these claims out of the denial queue.

Treat the sequela decision as a documentation question first and a coding question second. Practices that do rarely see V79.60XS come back from the payer. Book a demo to see how Pabau validates external cause code sequencing before a claim is submitted.

Continue your research

Need a reference for denial code meanings? Denial codes in medical billing covers the CARC and RARC codes most frequently paired with external cause code rejections.

Working denials after they land? Denial management in healthcare sets out the workflow for tracking, appealing and preventing repeat rejections.

Want to understand the billing compliance framework? Medical billing compliance covers the documentation and sequencing standards that underpin external cause code acceptance across payers.

Frequently asked questions