L
Operations

Leg

Definition
A single, continuous segment of transportation from a specific pick-up location (origin) to a specific drop-off location (destination). A "trip" may consist of one or more legs.

Overview

Why it Matters

Billing and scheduling occur at the leg level. If a driver takes a member to an appointment and waits to take them home, that is often two billable legs (Outbound and Return), not one "trip" event.

How it Works

When a member requests a ride, the dispatch software generates a "Leg" for the outbound journey. If they need a return, a second "Leg" is generated. Each leg has its own unique status (e.g., "Picked Up," "Dropped Off," "Cancelled").

Code Comparison

Comparison: Leg vs. Trip

A Trip is the overarching request or order (e.g., "I need to go to the doctor and back"). A Leg is the individual execution of movement (e.g., "Leg 1: Home to Doctor"). A Round Trip consists of two legs.

Common Questions

  • Merging data: Assuming "1 Trip" equals "1 Claim." (One trip often equals two claims/lines).
  • Status errors: Marking a whole trip as "Complete" when only the first leg was finished.
  • Assign unique IDs to every leg, not just every trip.
  • Capture timestamps (arrive, pick-up, drop-off) for each leg independently.

Sources

Texas Health and Human Services NEMT Handbook (Section 16.4)