ICD-10 code V00.382D: Pedestrian flat-bottomed conveyance, subsequent encounter

Key Takeaways

ICD-10 code V00.382D describes a pedestrian on a flat-bottomed conveyance involved in an accident, coded at a subsequent encounter

V00.382D is a billable ICD-10-CM code valid for HIPAA-covered transactions, effective October 1, 2025 (2026 edition)

The 7th character D means subsequent encounter: the patient is receiving active follow-up care for a healing or recovering injury

Pabau’s claims management software and Claim.MD clearinghouse integration help practices submit these external cause codes accurately

ICD-10 code V00.382D is a billable, specific diagnosis code for a pedestrian on another flat-bottomed conveyance involved in an accident, at a subsequent encounter. This reference page covers the code’s full description, 7th character rules, hierarchy, sibling codes, documentation requirements, and coding guidelines for the 2026 edition of ICD-10-CM.

ICD-10 code V00.382D: Quick reference code details

ICD-10 code V00.382D became part of the 2026 ICD-10-CM edition on October 1, 2025. The table below captures the key billing and classification details at a glance.

What V00.382D means: Code description explained

Each segment of the code carries a specific clinical meaning. Breaking it down removes the ambiguity coders run into when choosing between sibling codes.

• V00 – Pedestrian conveyance accident. The patient is a pedestrian using a conveyance (not a motor vehicle) who was involved in an accident.
• V00.38 – Pedestrian on other flat-bottomed conveyance. This covers wheeled conveyances with a flat base that don’t fall under the specific sub-categories for skateboards, scooters, or similar named devices.
• V00.382 – The sixth character adds specificity; this code family covers accidents (as opposed to falls from the conveyance or other event types).
• D (7th character) – Subsequent encounter. The patient has already received initial active treatment and is now returning for follow-up, healing monitoring, or ongoing care of the injury.

Approximate synonyms and alternate descriptions that coders and documentation systems may use include: “pedestrian on flat-bottomed wheeled device, subsequent encounter,” “non-motorized conveyance accident, follow-up,” and “wheeled conveyance injury, subsequent visit.”

Understanding the 7th character D for subsequent encounter ICD-10 coding

The 7th character is where most V00-series coding errors originate. ICD-10-CM requires coders to select from three options for external cause injury codes, and each has a precise clinical meaning.

A common misconception: “subsequent encounter” refers to the type of care, not the number of visits. A patient can have multiple initial-encounter (A) claims if they are still receiving active treatment. The shift to D happens when the care transitions to routine follow-up of a healing injury, regardless of how many visits have occurred.

Code hierarchy: Where V00.382D sits in ICD-10 transport accident codes

Understanding the hierarchical path from the parent chapter down to V00.382D helps coders verify they’ve selected the most specific code and understand sequencing rules. This code sits within a chapter dedicated entirely to external cause code categories in ICD-10-CM, which are always supplementary to a principal diagnosis.

Sibling and related pedestrian conveyance accident ICD-10 codes

V00.382D belongs to a tight family of codes that share the V00.382 base. Choosing the wrong sibling is one of the most common validation errors on claims involving flat-bottomed conveyance accidents. These codes cover injury and trauma diagnosis codes for pedestrian-type incidents across all encounter types.

The parent code V00.38 (pedestrian on other flat-bottomed conveyance) is a non-billable category header. V00.382D is the correct billable code when the event is classified as a general accident at the subsequent-encounter stage. Verify the accident type (collision with stationary object vs. other accident) in the clinical notes before assigning the code.

Clinical documentation requirements for ICD-10 injury subsequent encounter coding

Payers auditing V00.382D claims look for specific documentation elements. Missing any one of them can flip a claim from paid to denied. Revenue cycle management teams should build these fields into their follow-up visit note templates to reduce manual coder review time.

• Nature of the conveyance: The note must describe the conveyance as a flat-bottomed, non-motorized wheeled device. Descriptions like “balance board,” “flat-bed cart,” or “flat wheeled scooter” all support V00.38x coding. Absent a description, a coder cannot confirm the code over a more general pedestrian code.
• Encounter type: The clinician’s note must clearly indicate this is a routine follow-up visit for a healing injury, not an active treatment session. Phrases like “presenting for wound check,” “follow-up on healing fracture,” or “monitoring recovery” establish the subsequent-encounter 7th character.
• Injury details: The specific injury being followed (fracture, laceration, contusion) should be documented alongside V00.382D in the principal diagnosis field. External cause codes never stand alone.
• Original accident context: Where possible, a brief reference to the original accident in the history section strengthens the medical record. This is especially useful if the initial encounter was coded at a different facility.
• Place of occurrence and activity codes: Per submitting a clean claim guidelines, place-of-occurrence (Y93-Y99) and activity codes should accompany V00.382D when the information is documented and available.

Practices using Pabau can build structured follow-up note templates that prompt clinicians for each of these fields, reducing documentation gaps before the claim is generated.

Coding guidelines and usage notes for ICD-10 external cause codes

The CMS ICD-10-CM guidelines establish several non-negotiable rules for external cause codes like V00.382D. Violating them at the claim level almost always results in denial. The ICD-10-CM coding guidelines for behavioral diagnoses follow the same sequencing logic, so coders familiar with one code family will recognize the patterns here.

• Never sequence as the principal diagnosis. V00.382D is an external cause code. It always follows a principal diagnosis that describes the actual injury (e.g., S62.001D – fracture of unspecified bone of wrist, subsequent encounter). Payers will reject a claim if V00.382D appears in the primary diagnosis position.
• Use with the injury code at the same encounter level. The 7th character on the injury code and the external cause code should align. If the injury code uses D, the external cause code should also use D.
• Multiple external cause codes are allowed. ICD-10-CM guidelines permit additional external cause codes to describe the place of occurrence, the patient’s activity, and the patient’s status (e.g., civilian activity, leisure activity). Use all that apply when the documentation supports them.
• Payers may not require external cause codes, but they improve data quality. While not universally mandatory for reimbursement, the CDC/NCHS ICD-10-CM tool and NCHS guidelines strongly recommend external cause code reporting for injury surveillance and public health data purposes. Some state Medicaid programs do require them.

Effective denial management in medical billing for external cause code rejections typically traces back to sequencing errors or 7th character mismatches. Auditing a sample of V00-series claims monthly catches most patterns before they compound.

Submit external cause codes accurately, every time

Pabau integrates with Claim.MD to validate ICD-10-CM codes before submission, reducing denials from sequencing errors and 7th character mismatches. See how the workflow fits your practice.

Book a demo

Billing and reimbursement: Submitting V00.382D claims

Billing teams submitting claims with ICD-10 code V00.382D need a clearinghouse that validates external cause code sequencing before the claim reaches the payer. Pabau’s Claim.MD clearinghouse integration supports CMS-1500 and 837P claim formats, checks ICD-10-CM code validity against a built-in catalogue, and processes electronic remittance advice (ERAs) so practices can see exactly why a claim was accepted or denied.

For practices working through a medical claims clearinghouse, the key submission rules for V00.382D are straightforward. The external cause code goes in a secondary diagnosis field, paired with the principal injury diagnosis at the matching encounter stage. Pabau’s claims management software flags sequencing conflicts before submission, reducing the manual review cycle.

Using a superbill documentation workflow that pre-populates the principal injury code alongside the external cause code eliminates the most common submission error on follow-up visits: submitting V00.382D without a paired injury code in position one.

Code history and effective dates for ICD-10-CM V00 codes

Knowing when a code was introduced or revised matters for appeals and retrospective audits. Submitting V00.382D on a claim for a date of service before the code’s effective date will result in an invalid-code rejection.

The AAPC Codify ICD-10-CM lookup and the ICD List reference tool both confirm V00.382D as a current, valid, billable code for fiscal year 2026. Neither site shows revision or retirement notices for this code in the 2026 edition.

Conclusion

External cause coding errors are largely preventable. Most V00.382D denials trace back to 7th character confusion or sequencing mistakes, both of which structured documentation templates and pre-submission validation can catch before a claim leaves the practice.

Pabau’s built-in claims management tools and Claim.MD integration give practices a direct line to pre-submission ICD-10 validation, matched to the correct encounter type. If your team spends time correcting external cause code rejections on follow-up visits, see how a cleaner revenue cycle management workflow can reduce that rework.

Ready to see it in action? Book a demo to walk through the billing workflow with your team.

Continue your research

Need guidance on ICD-10-CM billing submission workflows? Claim.MD clearinghouse overview explains how electronic claim submission and remittance processing works end to end.

Want to reduce external cause code claim denials? Denial codes in medical billing covers the most common rejection reasons and how to address them before resubmission.

Looking for a structured approach to ICD-10 billing compliance? Medical billing compliance outlines documentation standards and audit preparation steps for external cause codes and injury claims.

Frequently asked questions