Trip Imports
Import trips from any broker file format
With Trip Imports ,
The Dispatcher can
import any broker file format
so they can
onboard new brokers instantly
— resulting in zero manual re-entry.
The Problem
The Core Problem
Operators miss out on broker contracts or waste hours on manual entry because the broker does not have a standard integration format.
The Scenario
A new regional broker sends a daily CSV with 30 to 50 trip assignments in their own column format.
Why It's Urgent
Their column called "RideID" is what MediRoutes calls "Authorization Number." Their "PickupTime" is what MediRoutes calls "Scheduled Pickup." Every field name is different.
Without MediRoutes
The dispatcher either re-keys every trip or spends time reformatting the file before importing. Both take 45 to 90 minutes per day.
With MediRoutes
A Custom Trip Import mapping is created once. After that, the dispatcher drops the broker's file into the import tool and all 50 trips load in under a minute, every day.
Who This Helps
The Dispatcher
works with regional brokers and local facilities that have no standard MediRoutes integration. Currently re-keys every trip from a spreadsheet or emailed list. Frustrated by the time and the errors.
The Fleet Owner
wants to take on new broker contracts but the broker uses a custom file format. Without Custom Trip Import, the only option is to key every trip manually.
How It Works
Each step shows what happens when things go right — and what MediRoutes does when they don't.
Start / End
Process Step
Decision Point
Common Questions
Modivcare, Verida, MTM, and Access2Care have standard formats coded directly into MediRoutes Desktop. All other brokers need a Custom Trip Import mapping.
One saved mapping per broker source. Operators with multiple non-standard brokers create a separate mapping for each.
CSV (comma-delimited) only. Excel files and UTF-8 CSV variants will not work. Most brokers can export to standard CSV from Excel or their own system.
New columns are ignored by default if they are not in the saved mapping. Update the mapping to capture the new data if it is relevant.
Standard imports handle single-pickup, single-dropoff trips. Complex multi-stop scenarios may require manual review after import.
Any CSV file with patient and trip data in the right structure can be imported. Facilities that send daily trip lists are a common use case.