The job it replaces
Ride2MD trips usually start as a list in the broker's system. Without a matched import, someone retypes each one into dispatch and hopes the phone numbers and dates come out right. With Bambi, you export the Ride2MD trip file and upload it. Bambi maps every column for you.
How the matched import works
- Export the trip file from Ride2MD.
- In Bambi, go to Trips, click Upload, pick the payer and the template that matches the Ride2MD format, and choose your file.
- Bambi flags formatting problems, like phone numbers and dates, before import and can fix them in one click. Trips that look like ones already on your schedule get a duplicate warning.
- Addresses Bambi can't match exactly get a Review Pickup Address or Review Dropoff Address tag, with the broker's original text in Dispatcher Notes.
What comes through
- Trips (Ride2MD file to Bambi): Broker-matched import. Every field in the Ride2MD file maps to the right place in Bambi.
- Formatting fixes and duplicate warnings: Live. Caught before the trips hit your board.
- Completed trips (Bambi to file): CSV export. Export completed trips as a CSV to take back to the broker portal.
- Automatic sync: No. This is a file-based integration, not a live API. Someone on your team still exports the Ride2MD file. We'd rather you hear that here than after you sign.
What still happens with Ride2MD
Pulling the trip file, credentialing, contracting and rates stay with Ride2MD.
Turning it on
Tell your Bambi onboarding team you run Ride2MD trips and Bambi Support turns on the matching import for your account. There's no extra cost.
Ride2MD facts for providers
Ride2MD arranges pre-scheduled and on-demand non-emergency medical rides for health plans.
Related: Broker Trip Import · Dispatch · Get Paid billing · MTM integration · NEMT broker guide · All Bambi integrations
