Non-emergency medical transportation (NEMT) has long run on phone calls, faxed trip sheets and spreadsheets. That is changing, partly because of federal rules on drivers and no-shows, partly because health systems and plans want transportation tied to the care it supports, and partly because riders now expect the same tracking and notifications they get from any ride app.
This guide covers the NEMT technology trends that matter for brokers, transportation providers, health plans and health systems: automated driver compliance, new expectations around no-shows, trips booked from clinical systems, network and rideshare dispatch, trip verification, rider communication, where AI fits, and how buyers should weigh these trends when choosing software.
What are the main NEMT technology trends?
Choosing or building NEMT software?
Our NEMT software buyer's guide covers the features, integrations and questions that matter for brokers and providers.
The main NEMT technology trends are automated driver and vehicle compliance, software support for federal no-show policy, trips booked directly from clinical scheduling, dispatch across mixed networks including rideshare, stronger trip verification, real-time rider communication and targeted use of AI for scheduling and fraud review. Most are driven by regulation and by buyers.
These trends affect each party differently. Brokers manage networks and answer to Medicaid agencies and plans; transportation providers run vehicles and drivers; health systems and clinics want patients to arrive on time. Software that serves one party well often creates work for another, so the strongest products are those that exchange data cleanly between them.
How are driver requirements changing NEMT software?
Driver requirements are changing NEMT software because they are now federal law for Medicaid. Medicaid.gov explains that section 209 of the Consolidated Appropriations Act, 2021 added minimum requirements for NEMT providers and drivers to the Social Security Act and codified the assurance of transportation found in 42 CFR 431.53.
Under those requirements, providers and individual drivers must not be excluded from federal health programs, drivers must hold a valid license, states need a process to address violations of state drug laws, and drivers must disclose their driving history to the state or broker. Each is a recurring check rather than a one-time step.
- Exclusion screening: Regular checks of drivers and companies against federal and state exclusion lists, with results stored.
- License tracking: Expiry dates with alerts, and automatic removal from dispatch when a license lapses.
- Driving history: Disclosure records and reviews kept with the driver profile.
- Audit trail: Evidence that every trip used a driver who was eligible on that date.
Software that blocks an ineligible driver from being assigned a trip is far safer than a spreadsheet reviewed monthly. Brokers increasingly require providers to share compliance data through portals or APIs rather than emailed documents.
Vehicle compliance follows the same pattern, although the specifics come from state contracts rather than federal law. Inspections, insurance certificates, wheelchair securement checks and driver training records all have expiry dates, and a system that holds them next to the dispatch board can stop a noncompliant vehicle from being assigned before it ever leaves the lot.
How are no-shows handled now?
No-shows are handled under clearer federal guidance. In State Medicaid Director letter 23-006, CMS explains that states may not deny transportation to beneficiaries because of previous no-shows or charge them for missed trips, and that federal matching funds are not available for trips where the provider fails to show.
The letter also encourages states to monitor provider no-shows and to allow short-notice replacement trips. For software, that means recording who caused each missed trip, tracking provider no-show rates, and making it fast to reassign a trip when a provider cancels late.
- Cause codes: Rider no-show, provider no-show, late cancellation and facility cancellation recorded separately.
- Evidence: GPS arrival data and attempted contact logs attached to each no-show claim.
- Reassignment: One-step rebooking with another provider, with the rider notified.
- Provider scorecards: No-show and lateness rates used in network management.
Rider no-shows still matter operationally even if they cannot be penalized. Reminders the day before and an hour before pickup, with an easy way to cancel, reduce wasted trips without restricting access.
Data on rider no-shows is still useful for planning. Patterns by facility, time of day or appointment type often point to fixable causes, such as clinics that cancel appointments without telling the broker, or early morning pickups that riders cannot make. Sharing those reports with facilities turns no-shows into a joint problem rather than a dispute.
Why are trips being booked from clinical systems?
Trips are being booked from clinical systems because missed appointments cost health systems and plans money and harm patients. When a clinic schedules a dialysis session, a discharge or a follow-up visit, it is the natural place to request the ride.
In practice this means a request from the EHR or scheduling system to the broker or provider, carrying the appointment time, location, mobility needs and eligibility details, and a confirmation coming back. Hospital discharge teams benefit most, since a delayed ride can hold a bed for hours.
Standards help but do not cover everything. Appointment data can be read through FHIR APIs in many EHRs, while trip requests and status updates often still use broker-specific APIs. Building a clean adapter layer between the two is now a common project for both health systems and brokers.
The adapter also has to handle change. Appointments move, discharges slip and clinics run late, so trip times must update when the appointment does, and return trips need a will-call option that the facility can trigger when the patient is ready. Without these updates, booking from the EHR simply moves the phone calls to a different desk.
How are network and rideshare models changing dispatch?
Network and rideshare models are changing dispatch because brokers now combine dedicated NEMT fleets, wheelchair and stretcher vans, public transit and rideshare companies in one network. Dispatch software has to choose the right mode for each rider, not just the nearest vehicle.
- Level of service: Ambulatory, wheelchair, stretcher or attendant needs matched to vehicles and drivers.
- Mode selection: Rules for when rideshare or transit is suitable and when a specialized vehicle is required.
- Multi-loading: Grouping riders with compatible times and destinations, such as dialysis schedules.
- Provider capacity: Real-time availability from multiple providers rather than fixed daily allocations.
Medicaid.gov notes that public transit authorities are exempt from the driver requirements, which affects how transit trips are recorded. Rideshare drivers present a separate question: brokers need contracts and data feeds that show those drivers meet the applicable requirements.
What does trip verification look like now?
Trip verification now relies on device data rather than paper. Trip logs with GPS pickup and drop-off points, timestamps and electronic rider signatures or confirmations support billing and make fraud harder.
Verification also supports payment integrity. Brokers can compare billed mileage with the route actually driven, flag trips without matching appointments, and detect patterns such as the same rider picked up by different providers on the same day. These checks work only when trip data is captured consistently by drivers' apps, so driver app design matters.
Paper trip sheets still exist in smaller providers, and brokers that accept them face slower billing and weaker audit evidence. Offering providers a free or low-cost driver app is one way brokers raise data quality across a network.
How is rider communication changing?
Rider communication is moving to automated texts, calls and app notifications at each step: booking confirmation, a reminder the day before, a driver en route alert with a live map, and an arrival notice. Many NEMT riders are older or have disabilities, so voice calls and plain text messages remain essential alongside apps.
Facilities need visibility too. Dialysis centers and clinics want a view of which patients are on the way and which rides are late, so they can adjust schedules. A facility portal or feed reduces the phone calls that otherwise flood broker call centers.
Language access and accessibility are part of this trend. Messages should be available in the languages riders speak, readable with screen readers, and short enough to understand at a glance. Riders should also be able to reply to a text to confirm, cancel or ask for help, rather than having to call a number and wait in a queue.
Where does AI fit in NEMT?
AI fits in NEMT mainly as optimization and review support: predicting no-show risk to target reminders, improving route and multi-load planning, flagging suspicious billing patterns and assisting call center staff with trip intake. It works on top of clean trip and compliance data, not in place of it.
Decisions about eligibility and level of service should stay with people and clear rules, with AI suggesting rather than deciding. Our article on AI in NEMT for providers covers these uses in more depth.
How should buyers weigh these trends?
Buyers should weigh these trends by asking which ones their contracts and regulators already require and which ones their customers are asking for. Driver compliance and no-show tracking are requirements; clinical booking integration and facility portals are increasingly what win broker and plan contracts.
Check that any system can export trip, compliance and no-show data in formats brokers and states accept, offers APIs rather than only screens, and handles mixed fleets. A product that only works for one broker or one vehicle type will limit growth.
Ask vendors for evidence, not roadmaps. A short pilot with real trips, real drivers and one facility partner will show whether driver apps are reliable in low-signal areas, whether reassignment is really one step, and whether reports match what the broker or state expects to receive.
How Agnotic can help
Agnotic Technologies builds NEMT software for brokers and transportation providers: dispatch and multi-load scheduling, driver apps with GPS verification and electronic signatures, driver compliance tracking, rider notifications, and integrations with EHR scheduling and broker APIs.
We also extend existing NEMT platforms with the integrations and reports that new contracts require, so teams can meet broker and state expectations without replacing their whole system.
Plan your NEMT software
Read our NEMT software buyer's guide, or browse more guides and playbooks.
Related reading on Agnotic
See AI in NEMT for providers, why NEMT matters, the Epic scheduling API and hospital at home technology.
