Long-distance medical transportation software for trips across counties and state lines

One long trip changes the whole day

A trip that runs for hours takes one van and one driver out of the day, so the schedule has to show the whole block of time, not only the pickup. Pricing these trips is covered in the long-distance pricing guide, and rider care on the road is in the long-distance rider care guide. This page covers what the software has to keep.

Here is an example. A wheelchair rider has a 10:30 appointment at a clinic 230 miles from the base. At 50 miles an hour that is 4.6 hours each way, or 9.2 hours of driving. Add the first pickup, loading, a three-hour appointment, a short break and unloading, and the driver is on duty for about 14 hours. No other trip can use that van, and a one-hour delay would use up the slack and push the driving past 10 hours.

Three things follow for the software. The board should show the van as committed from the first pickup to the return to base. The return should hold as an open trip, because nobody knows when the appointment will end, and a will-call trip does that. And the office should be able to see where the van is on the way, not only at each end.

Driver time: what the record has to show

A trip like the example sits close to the federal driving-time limits for passenger vans, so the record has to show each driver’s time. Those limits are 10 hours of driving after 8 consecutive hours off duty and no driving after 15 hours on duty (49 CFR 395.5). In the example, 9.2 hours of driving leaves 0.8 hours under the first limit, and about 14 hours on duty leaves about one hour under the second. Who the limits cover, the short-haul exemption and the exception for sick and injured persons are in the driving-time guide.

The software’s part is the evidence. For drivers who must log duty status, 49 CFR 395.11 has the carrier keep supporting documents, including each dispatch record or trip record. Each one must show the driver, or a vehicle number tied to the driver, the date, the nearest city, town or village, and a time that converts to the local time where it was recorded. A trip record with those four items for every leg supports any later review of the trip.

Time zones and daylight saving time on the way

Every time on a long trip has to convert to local time, because the appointment is on the clinic’s clock and the trip can cross a zone line. 49 CFR Part 71 sets the boundaries. The line between the eastern and central zones follows county lines inside Kentucky and Tennessee, and the line between the central and mountain zones does the same in South Dakota and Kansas. A driver who leaves at 6:00 a.m. for a 10:30 appointment one zone to the west has 5.5 hours, not 4.5.

Daylight saving time adds a second trap. It starts at 2 a.m. on the second Sunday of March and ends at 2 a.m. on the first Sunday of November (15 U.S.C. 260a), but a state can exempt itself. NIST lists Arizona as not observing it, with the Navajo Nation as the exception, so a summer route across Arizona and the Navajo Nation can change the clock by an hour without leaving the state. Ask any vendor to show a trip that starts in one zone and ends in another, and one booked near a changeover date.

When the signal drops on a long road

A long trip will cross stretches with no signal, so the office needs to see when a van last reported, not only where it was. The FCC’s 2026 Section 706 Report says that as of June 2025, 59.5 percent of rural road miles had 5G service at 35/3 Mbps from at least one provider, against 99.0 percent of urban road miles. Treat that as the direction of the gap and test your own routes against the FCC’s coverage map.

A family waiting at a clinic reads a ten-minute-old position as the van’s position now. The tracking link and the dispatch screen should show how fresh the position is, and the driver app should keep recording pickups, drop-offs and signatures until the phone reconnects. Planning around dead zones on rural corridors is in the rural NEMT software guide.

Out-of-state trips: the approval travels with the trip

For a Medicaid rider, the approval has to be on the trip itself. A state pays for care in another state only in the situations listed in 42 CFR 431.52, so a payer can approve one out-of-state ride and refuse another. The trip should carry the authorization number, the approved destination, the dates and the approved miles from the day it is booked. What each approval means is in the guide to out-of-state trips, and the trip authorization number entry explains the number.

What to see demonstrated before you buy

Give the vendor one real long trip and watch what happens.

1. A trip that fills a day. Book a 230-mile trip with a long appointment, and check that the board shows the van committed for the whole block and the return stays open.
2. Times in two zones. The pickup and the appointment are in different zones, and each person sees the right local time.
3. A tracking link for the family and the clinic. It opens from a text message with no account, follows the van for hours and shows when the position last updated.
4. A record for the driver-time rules. Each leg shows the driver, the date, the nearest town and a time that converts to local time.
5. Payment before the trip. A private-pay rider can pay through a secure link or save a card before the van leaves.
6. The approval on the trip. The authorization number, destination and approved miles sit on the trip record.

Long trips in HealthRide

Families and facilities can follow the driver live from a text link, and the office watches every van on the live map. The driver app keeps working without cell service, and every trip keeps its GPS-recorded miles and timestamps. A flexible return trip holds its place on the board and activates the moment the rider is ready. Riders can pay by card through a secure payment link or a saved card (see payments), and the reports show each driver’s hours.