NEMT Dispatch Software: What Medical Transport Fleets Need
Non-emergency medical transportation runs on a promise that has nothing to do with street work: a patient has to be in a dialysis chair at a fixed hour, three times a week, and get home afterwards. Dispatch software built for on-demand taxi trips can technically move those rides, but the parts that decide whether you keep a facility account are appointment times, standing orders, return legs and documentation, and those are exactly what a generic setup handles worst. Here is what to look for, and what to get in writing before you sign.
What is NEMT dispatch software?
NEMT dispatch software is the system a medical transport company uses to schedule appointment-based trips, assign them to the right vehicle and driver, follow them while they run, and leave a record of what happened. The difference from ordinary taxi dispatch is that the trip is anchored to an appointment time rather than to a pickup request, most of the work is booked days or weeks ahead, and a large share of it repeats on a fixed schedule. The dispatch screen has to show tomorrow and next week as clearly as it shows right now.
How is NEMT dispatch different from taxi dispatch?
The trips look similar on a map and behave completely differently in practice. In taxi work the rider decides when to travel and forgives a few minutes. In medical transport the clinic decides, the window is narrow, and one late arrival can cost the patient the appointment and cost you the account. The differences that matter operationally:
- Trips are anchored to an appointment time, not to a pickup request
- Standing orders repeat weekly, or several times a week, for months
- Return legs are often will-calls: the patient calls when treatment ends and the wait is unpredictable
- Vehicle type matters, and sending an ambulatory car to a wheelchair passenger is a failed trip
- Drivers may need to assist door to door instead of curb to curb
- Somebody other than the passenger usually books the trip and pays for it
- Every trip needs a record that still answers a question asked three months later
What features does a medical transport fleet actually need?
Start with scheduling and records; everything else is secondary. A NEMT operation lives or dies on whether tomorrow's schedule is complete, correct and assigned before the day starts, and on whether last month's trips can be proven when an account asks. In order of how much they hurt when they are missing:
- Recurring trip templates, so a standing order is entered once instead of every week
- Appointment time, pickup window and drop-off visible on the same view
- Mobility requirements attached to the passenger record, not typed into a free-text note
- Will-call handling for return legs, with a visible queue of patients waiting for pickup
- Driver app steps that confirm pickup and drop-off with time stamps
- Trip history searchable by passenger, by account and by date
- Reporting by facility or account, because that is the unit contracts get renewed in
What about HIPAA and compliance?
Do not take a compliance claim from a web page, including this one. WayCab Plus does not publish certification claims here. If your operation needs specific safeguards, ask for them in writing and get them reflected in the contract before you sign, and hold every other vendor you evaluate to the same standard. A badge on a landing page is marketing; a clause in an agreement is a commitment.
The questions worth asking are concrete: what passenger data is stored, who inside the vendor can see it, where it is hosted, what happens to it if the contract ends, and what the vendor will put in writing. A vendor that answers those clearly in a document is worth more than one that answers enthusiastically on a call.
Broker trips, facility accounts and private pay
Most NEMT fleets serve more than one kind of payer, and each one arrives through a different door. Broker work usually shows up in the broker's own portal or as a file. Facility accounts call, email or send a weekly list. Private-pay customers book for themselves or for a relative. Before you assume trips will flow automatically from any outside system into your dispatch screen, ask the vendor directly whether that connection exists today and get the answer in writing, because we can look into that is not the same as it works now. What you can plan on regardless is having one place where every trip ends up, whichever door it came through, so your dispatcher is not reading three inboxes at seven in the morning.
Which numbers decide whether you keep an account?
On-time performance and completion, both measured against the appointment time rather than against the pickup time. Facilities and brokers almost never ask about your app; they ask why a patient arrived late twice last month and what you changed. Track these and you can answer:
- Arrival time versus appointment time, trip by trip
- Trips completed, cancelled and no-showed, and who cancelled them
- How long return-leg passengers waited after calling for pickup
- Trips reassigned at the last minute, and the reason
- Volume by facility and by account, month over month
If those numbers only exist inside a chat group, you cannot defend an account when it gets questioned, and questioning usually happens right before renewal.
How do you move off spreadsheets without dropping a trip?
One direction at a time, with the phone still working. Load the standing orders first: they are the backbone of the schedule, the easiest to verify, and the most expensive to lose. Run one full week with both systems in parallel and compare the two schedules every evening until they match. Bring one facility account across at a time rather than all of them at once, and keep the old list until a full billing cycle has closed cleanly. Migration failures in this business are rarely technical; they are a trip that existed in the notebook and never made it into the system.
WayCab Plus for medical transport fleets
WayCab Plus develops, configures and maintains the passenger app, driver app and dispatch panel that a transportation company runs under its own brand, on a monthly fee with no commission per ride, unlimited drivers and technical support included 24/7. For a medical transport operation the configuration is the part that decides everything: how trips get entered, how vehicles and mobility requirements are categorized, and what the dispatcher sees first when the day starts. Those rules are defined during setup, which is the moment to bring the specific requirements your accounts impose on you.
How do recurring treatment trips change your schedule?
Recurring trips are the backbone of a NEMT operation and the main reason generic taxi software struggles with this work. A dialysis patient may travel three times a week for months, at the same hour, to the same clinic, with a return leg that depends on when treatment ends. If every one of those has to be typed in by hand, your dispatcher spends the morning re-entering trips instead of solving problems. What you want is the ability to create the series once, change a single day without breaking the pattern, and see next week's committed trips beside today's live work.
Will-calls, no-shows and wait time
The return leg is where a NEMT day falls apart. A will-call ride has no fixed hour: the passenger calls when treatment finishes, and the clock starts then. Treat it as a queue rather than an appointment. Keep open return trips visible all day, record who is waiting and since when, and set a clear rule for how long a driver waits before the trip is marked as a no-show. Those numbers are also the ones whoever pays for the ride will ask about, so they have to be recorded at the moment they happen and not reconstructed at the end of the month.
Matching the vehicle to the passenger
A medical transport trip fails before it starts if the wrong vehicle arrives. Ambulatory, wheelchair, bariatric and stretcher trips need different vehicles, different equipment and sometimes a second attendant, so the level of service has to be captured at booking and honoured at assignment. Set the vehicle types in the platform, mark which drivers are trained and equipped for each, and make sure the dispatch screen never hides that detail behind a menu.
- Level of service on every trip: ambulatory, wheelchair, stretcher, bariatric
- Whether an attendant or a family member is riding along
- Equipment the driver must carry, and any lift or ramp requirement
- Building access details: which entrance, which floor, who to ask for
- The authorisation or trip reference from whoever is paying for the ride
What belongs on the trip record
Whoever pays for the ride decides what a valid trip record looks like: a broker, a health plan, a facility or the family. Ask them in writing which fields they require and when they expect them, then check that your platform can capture each one at the moment of the trip rather than afterwards. Pickup and drop-off times, mileage, signatures, wait time and cancellation reasons are the ones that come up most often. Requirements vary by state, by payer and over time, so confirm them with your own payer and your own advisor instead of assuming any software has already settled the question for you.
Frequently asked questions
Is WayCab Plus HIPAA compliant?
We do not make compliance claims on a web page. If your operation requires specific safeguards, ask us for the details in writing and have them reflected in your agreement, and apply exactly the same standard to every other vendor you evaluate.
Can trips that repeat every week be entered only once?
That is what recurring trip configuration is for, and it should be the first thing you test in any demo. Ask the vendor to show you a standing order being created, edited for one single date, and cancelled for one week without destroying the rest of the series. With WayCab Plus that behavior is defined during configuration, so raise your accounts' rules before go-live.
Do I need a different platform for NEMT than for taxi work?
Not necessarily, as long as the same platform can be configured around appointment times, mobility requirements and recurring trips. Plenty of operators run medical transport alongside airport and corporate work. The risk is not mixing the two, it is running medical work on a configuration that only understands on-demand pickups.
How does a driver prove that a pickup happened?
Through time-stamped status changes in the driver app, plus whatever additional confirmation your accounts require. Agree with each facility or payer in advance on what counts as proof, and make sure that evidence is searchable months later, not just visible on the day of the trip.
Can the same platform handle NEMT trips and regular taxi work?
Yes, provided it supports levels of service, driver qualifications, recurring trips and both scheduled and on-demand work in the same dispatch view. Many local operators run a mixed fleet, with ambulatory medical trips alongside cab or shuttle service, because the same vehicles fill gaps in the middle of the day.
What should be recorded when a passenger is not there?
The time the driver arrived, how long they waited, who was contacted and what the outcome was, recorded at that moment and not from memory later. Then confirm with whoever pays for the ride what they specifically require for a no-show to be recognised, because that varies by payer.
How far ahead should recurring trips be created?
As far ahead as the authorisation or the treatment schedule runs, and then reviewed weekly. Creating the series far out gives dispatch a real picture of committed capacity, while the weekly review catches the changes that always happen: a treatment moved, a patient discharged, a new address.