Non-medical transportation software for waiver and senior ride programs

What non-medical transportation covers

Non-medical transportation, or NMT, is any ride whose purpose is not a medical appointment. Riders go to the grocery store, the bank, a senior center, a day program, a job, church, or a family visit. For people who no longer drive, these rides are how they reach the services and activities that keep them living in the community.

Most NMT money comes from three places:

CMS’s core waiver definition frames NMT as the way participants get to the waiver services, community activities, and resources their service plan lists. It sits on top of the medical transportation a state already owes and never replaces it. CMS also expects programs to lean first on unpaid help from relatives, neighbors, friends, or community groups whenever it is available. For the full definition, see waiver transportation.

One rider, several payers

The trip’s purpose decides who pays for it, and one rider can easily touch three programs in a week. Take an example rider on a waiver who also pays privately for extras:

• Tuesday dialysis is a medical trip. It belongs to the state’s Medicaid transportation benefit, often booked through a broker, and CMS says it cannot be billed to the waiver.
• Thursday grocery run is in the service plan, so it bills to the waiver.
• Saturday visit to a daughter across town is outside the plan, so the family pays.

Two more rules make the split matter. When another waiver service already includes transport in its rate, such as an adult day health program that brings people in, CMS requires safeguards so the same ride is not billed twice. And waiver dollars are limited to trips that serve the plan. Software that records a purpose and a payer on every trip keeps those lines straight. Software that assumes one payer per rider does not.

The trip record programs pay against

NMT programs pay only for trips they can check, and each program writes its own list of what a trip record must contain. Ohio publishes three separate rules, which makes it a useful example of how much the lists differ.

A paper sheet can hold all of this, but paper fails in predictable ways: a missing time, an unreadable signature, a trip logged on the wrong rider. A driver app that stamps times and places at each tap, takes the rider’s signature on the phone, and records the route from GPS produces the record as the ride happens. See the trip log entry for what a complete log looks like.

Units and rates change by program

The same ride can count as a different number of units depending on who pays, so pricing has to follow the payer.

• Ohio Older Americans Act rides: each one-way trip is one unit, and the unit rate must reflect everything the ride costs the provider, overhead and training included.
• Ohio PASSPORT waiver: one trip is one job, whether it is one-way or round trip, with a maximum rate set in state rule.
• Ohio developmental disabilities waivers: per-trip rates are set per person no matter how many ride together, while per-mile rates change with the number of people on board and on whether the van is a modified vehicle.

Private pay follows your own rate sheet. A system that prices each trip from the payer’s own rates, and invoices each payer separately, avoids re-pricing trips by hand at month end. For saved cards and chasing unpaid balances, see the private pay guide.

Scheduling errands and community rides

NMT days look different from medical days. Trips repeat on a weekly rhythm, stops take longer, and the rules reach into the van.

• Many rides repeat. The same riders go to the same senior center, day program, or store on the same days. Set each series once and change single days without rebuilding the week.
• Assistance takes time. Ohio’s PASSPORT rule has drivers assist on every trip, from the pickup spot to the van, getting in and out, and on to the destination. Build that time into each stop.
• Wheelchair vans get a daily check. Both Ohio aging rules require an inspection before the first trip of the day of any vehicle carrying a rider in a wheelchair, checking tie-downs, seat belts or harnesses, and the ramp or lift, and the provider keeps a record of each check.
• Drivers need two-way communication. Ohio’s aging rules require every driver to have a two-way radio or a cell phone while carrying riders.
• A backup plan is required. Ohio’s aging rules expect providers to say how riders still get moved, or at least told, if a driver calls out or a van is down.

What to look for in non-medical transportation software

1. Recurring trips with one-day changes. Weekly errands and program days set once.
2. A payer on every trip. Waiver, aging program, family, or rider, chosen per trip rather than per person.
3. Per-payer rates and invoices. Units and prices that follow each program’s rules.
4. Trip records captured in the app. Times, places, rider and driver confirmation, and GPS-recorded miles.
5. Vehicle checks before each shift. A record of the daily inspection for every van.
6. Easy booking for families. Private-pay riders and relatives who can book and pay without calling.
7. Exports for program reviews. A trip log that downloads as a spreadsheet or PDF when a reviewer asks.

Running NMT rides in HealthRide

Weekly errands and program days go into HealthRide once as recurring trips, and finished rides are gathered into invoices priced at each payer’s own rates. Families can book a ride on the web, watch the driver’s progress from a link sent by text, and pay with a saved card or a pay link. Each shift starts with a van check in the driver app, and rides record GPS miles and the rider’s signature on the phone.