ICD-10 Code V10.5XXS: Pedal cycle passenger injury, sequela

Key Takeaways

ICD-10 Code V10.5XXS describes a pedal cycle passenger injured in a collision with a pedestrian or animal in a traffic accident, with the 7th character S indicating sequela (a late effect of the original injury).

V10.5XXS is an external cause code and must always be paired with a primary diagnosis code reflecting the current sequela condition; it cannot be used as a principal diagnosis.

The three 7th character variants (A = initial encounter, D = subsequent encounter, S = sequela) are not interchangeable; selecting the wrong character is a common coding error that triggers claim denials.

Pabau’s claims management software helps coding teams apply external cause codes consistently and track encounter-type sequencing across the care episode.

Sequela coding trips up even experienced coders. When a cyclist treated months ago for injuries from a collision returns with chronic knee pain or a healed-but-symptomatic shoulder, the external cause code has to shift from D (subsequent encounter) to S (sequela), and the primary diagnosis has to reflect the late effect, not the original trauma. Get either wrong, and the claim fails. ICD-10 Code V10.5XXS covers exactly this scenario: a pedal cycle passenger whose injuries from a traffic collision with a pedestrian or animal have progressed to the sequela stage. This reference covers the full code hierarchy, 7th character logic, documentation requirements, and correct pairing rules for clinical billing workflows.

ICD-10 Code V10.5XXS: Full description and code hierarchy

V10.5XXS carries the official descriptor: Pedal cycle passenger injured in collision with pedestrian or animal in traffic accident, sequela. The code is valid for the 2026 ICD-10-CM code year, effective October 1, 2025, per CMS ICD-10 coding resources.

Understanding where V10.5XXS sits in the classification hierarchy is essential before applying it. The code lives in the V00-Y99 chapter (External Causes of Morbidity), within the V10-V19 block (Pedal cycle rider injured in transport accident). See the full hierarchy below.

The two placeholder X characters in the code are required dummy characters, present because the ICD-10-CM tabular format reserves positions 6 and 7 for specificity extensions. For V10.5, no additional sixth-position specificity is defined, so both placeholder positions are filled with X before the 7th character encounter type. Coders familiar with ICD-10 code documentation across different chapters will recognise this placeholder convention from other injury and external cause sections.

7th character extensions: A, D, and S explained

The 7th character is the most clinically significant element of V10.5XXS. It determines the encounter type and directly affects which diagnosis codes can be paired alongside it. Using the wrong character is one of the most common external cause code errors in injury billing.

The critical clinical distinction: S is not simply “a later visit.” Sequela means the original injury has resolved or stabilised, and the current condition being treated is a direct late effect. A patient completing physical therapy for a fracture from the accident still uses V10.5XXD. Only when the provider is treating a condition that resulted from the injury, rather than the injury itself, does the 7th character shift to S. For related guidance on encounter-type distinctions across injury codes, the CDC/NCHS ICD-10-CM web tool provides the authoritative code-level notes and guidelines.

How to pair V10.5XXS with a primary diagnosis code

External cause codes are never sequenced first. Per CMS ICD Code Lists guidance and the ICD-10-CM Official Guidelines for Coding and Reporting (Section I.C.20), V10.5XXS is a supplementary code that identifies the cause and circumstances of an injury. The principal diagnosis must be the condition currently being treated.

For sequela encounters, this means the primary code must reflect the specific late-effect condition, not the original injury. Maintaining accurate client record management across the care episode helps coding teams trace the chain from original injury to current late-effect presentation.

• Chronic pain as sequela: Use a pain code (such as G89.28, chronic post-traumatic pain) as the principal diagnosis, followed by V10.5XXS as the external cause.
• Scarring or contracture: Code the specific scar or contracture condition (e.g. L90.5, scar conditions) as the primary code, then V10.5XXS.
• Neurological late effect: Assign the relevant neurological condition code first (e.g. nerve damage from injury), then V10.5XXS to establish the cause.
• Musculoskeletal sequela: Pair a current musculoskeletal condition code (e.g. M79.3, panniculitis) or relevant residual condition with V10.5XXS as secondary.

CMS guidance confirms that V codes (external cause codes) may be used in Section 111 claim reports in specific circumstances, including to identify the alleged cause of injury. This means V10.5XXS can appear on Medicare coordination-of-benefits claims when properly documented and sequenced. Practices using claims management software can configure code pairing rules to flag instances where an external cause code appears without a valid primary diagnosis.

Keep external cause codes accurate across every encounter

Pabau's claims management tools help coding teams sequence external cause codes correctly, flag missing primary diagnoses, and reduce claim errors across injury and sequela encounters.

Book a demo

Related codes in the V10 category and adjacent blocks

Accurate coding often depends on distinguishing V10.5XXS from closely related codes in the same category. The most common confusion involves the driver vs. passenger distinction and the traffic vs. nontraffic modifier.

The passenger vs. driver distinction matters because the clinical circumstances differ: a passenger on a tandem bike or in a cargo attachment has no steering control, which can affect injury patterns documented in the record. Coders should verify the patient’s role in the incident from the provider’s note, not assume. For additional context on how ICD-10 classification handles injury hierarchies, see ICD-10 codes for traumatic brain conditions, which illustrates how injury chapter codes interact with external cause codes.

Documentation requirements for sequela encounters

Sequela coding places specific demands on the clinical record. The documentation must support three elements: the original injury and its cause, the causal link between the original injury and the current condition, and the current condition being treated at this encounter.

Practices using digital intake forms can build injury history capture into the patient questionnaire, creating a structured record that coders can reference without hunting through free-text notes. For broader guidance on maintaining compliant records, ICD-10 diagnostic coding reference articles illustrate how documentation requirements vary by code category.

• Original injury: The provider note should reference the prior accident date and describe the injury that occurred. This establishes the temporal and causal foundation for sequela coding.
• Causal link: The clinician must explicitly connect the current condition to the original injury. Phrasing such as “chronic knee pain resulting from the 2024 bicycle collision” is more defensible than a general reference to knee pain without context.
• Current condition: The active sequela condition being treated at this visit must be clearly identified and coded as the primary diagnosis. The visit cannot be coded using the original injury codes when the injury has resolved.
• Encounter type justification: The note must support the use of 7th character S. If the provider is still treating the acute injury, D is more appropriate. Documentation should make the distinction unambiguous.

Maintaining this level of documentation discipline also supports HIPAA-compliant clinical documentation standards, where the integrity of the clinical record is central to audit readiness. The WHO ICD-10 browser provides the international classification context for these external cause codes, useful when treating patients with records from international healthcare systems.

Common coding errors and audit risks with V10.5XXS

External cause codes in the V10-V19 range generate specific audit risks when misapplied. Knowing where errors concentrate helps coding teams build internal checks before claims leave the practice.

• Using S when D applies: The most frequent error. A patient still in active rehabilitation is a subsequent encounter (D), not a sequela encounter (S). Auditors look for alignment between the 7th character and the primary diagnosis; a rehabilitation-phase primary code paired with a sequela external cause code raises flags.
• Sequencing V10.5XXS first: External cause codes are never principal diagnoses. Placing V10.5XXS in the first code position will cause the claim to reject. The current sequela condition always leads.
• Omitting the primary diagnosis entirely: Some billers submit V10.5XXS without a companion sequela condition code, treating it as a standalone code. It is not billable in isolation.
• Using an initial encounter code at a follow-up: Reporting V10.5XXA for a visit that is clearly a follow-up or late-effect encounter misrepresents the care episode and can constitute a billing integrity issue.
• Misidentifying driver vs. passenger: Using V10.4XXS (driver) when the patient was a passenger, or vice versa, introduces a specificity error that affects accuracy reporting and can complicate liability claim processing.

Structured patient data security in clinical records practices also reduce audit exposure by ensuring that documentation supporting external cause codes is preserved, accessible, and attributable to the treating clinician. Practices managing high volumes of injury-related claims benefit from practice management workflows that surface coding inconsistencies before submission.

Conclusion

External cause codes like ICD-10 Code V10.5XXS do real work in the claim: they tell payers the mechanism and circumstances of the injury, support coordination-of-benefits processing, and protect the practice in audit situations. Getting the 7th character right, sequencing V10.5XXS behind a valid sequela primary diagnosis, and documenting the causal link between the original accident and the current condition are the three elements that determine whether the claim processes cleanly or triggers a review.

Pabau’s compliance management tools support coding teams in building structured workflows around injury episode tracking, external cause code application, and documentation review. To see how Pabau handles injury billing workflows in practice, book a demo with the team.

Continue your research

Need guidance on ICD-10 documentation for neurological injury codes? ICD-10 codes for traumatic brain conditions covers how injury chapter codes interact with external cause supplementary codes.

Looking for HIPAA-compliant ways to capture injury history at intake? Medical office compliance requirements outlines documentation and intake practices that support audit-ready clinical records.

Want to reduce claim rejections from coding sequence errors? Claims management software helps practices configure code pairing rules and flag sequencing issues before submission.

Frequently Asked Questions