Online booking for NEMT: letting facilities and families request rides

Which rides belong in online booking

Online booking fits the rides you are paid for directly: facility accounts, private-pay riders, and families arranging rides for a parent. A form takes requests after the office closes, and a typed address cannot be misheard over a bad phone line.

Medicaid rides that run through a broker are a separate channel. The broker takes the request from the member or the facility, authorizes it, and assigns the trip to one of its contracted providers. Delaware is a typical example. Modivcare’s Delaware facility page lets facility staff book standing orders in Modivcare’s own online system, and it asks for three business days of notice on routine and recurring trips such as dialysis. A request on your website does not replace that step. If a family books privately and the rider has Medicaid, see private pay NEMT for how to handle it.

Three ways to take requests online

Most companies end up running all three, each for a different kind of customer.

Start with the channel that matches your busiest source of rides. A company with two hospital contracts gets more from a facility portal than from a polished public form. Our guide to facility contracts explains how those accounts are won in the first place.

What every request should collect

Build the form from the questions your dispatchers already ask on the phone. The trip intake guide has the full call script. Broker forms show how much detail a facility request needs. Modivcare’s Delaware individual trip request form asks for the rider’s weight and height on wheelchair and stretcher trips, stairs, whether the rider can transfer to an ambulatory vehicle, a manual or electric chair, oxygen in liters, isolation, the room or apartment number, the suite at the destination, and whether the destination allows stretcher drop-offs.

Three design choices cut most of the follow-up calls:

• Menus for mobility, not a text box. A dropdown of service levels removes abbreviations and guesses.
• Required fields for the essentials. The form will not send without an address, a time, a mobility level, and a return plan.
• One notes field for everything else. Door codes, a dog in the yard, the rider who needs extra time on the stairs.

Ask for what the ride needs and stop there. The trip type (dialysis, discharge, a regular appointment) helps you plan wait times and repeating rides. A diagnosis does not. Limiting requests to what a task needs is also the habit HIPAA’s minimum necessary standard builds (45 CFR 164.502(b)).

Request first, booking second

An online request should arrive as a request, not as a confirmed ride. A dispatcher accepts it after five checks:

1. Area and hours. Both addresses sit inside your service area, at a time you run.
2. Vehicle and crew. A wheelchair van or stretcher vehicle, and the crew that trip needs, are free at that hour.
3. Timing. The pickup leaves enough drive and loading time to arrive by the appointment.
4. Price and payer. The facility rate applies, or the private rider gets a quote and any deposit terms.
5. Return. The ride home has a time or is marked as will-call.

Then answer: accept, offer another time, or decline with a reason. Once accepted, the request should become the trip on your board, with nothing retyped from an email. State your reply time on the form and meet it, for example within two business hours. Set a cutoff for next-day requests as well, such as 2 PM the day before, so tomorrow’s plan is built on a known list.

Same-day and discharge requests need a person on the phone. MTM’s Virginia Medicaid handbook gives the provider three hours, counted from the call saying a discharged rider is ready, to get a van there. A form sitting unread for an hour spends a third of that window. Put the phone number at the top of the form and say plainly that same-day rides are booked by phone. Discharge work has its own guide: hospital discharge transportation.

Automatic confirmation has a place, within limits. A known facility booking an ambulatory ride two or more days out is low risk. A first-time family asking for a stretcher ride tomorrow is not.

Confirmations, reminders, and tracking links

The confirmation is where errors surface, so repeat the request back in full:

• A trip or confirmation number
• The pickup date and time, or the pickup window
• Both addresses as you understood them
• The vehicle type
• The return plan
• How to change or cancel, and the deadline for doing it without a fee
• Your phone number

After that, the rider should hear from you twice more: a reminder the evening before, and a text as the van heads out, carrying a tracking link with the van’s position and an arrival estimate. Facilities should get the same updates for their residents. A front desk that can watch the van come in stops calling dispatch to ask where it is.

Automated texts generally need the rider’s consent first, so put a separate, unticked consent box on the form. Under 47 CFR 64.1200, a rider can take that consent back by replying stop, quit, end, revoke, opt out, cancel, or unsubscribe, and you have no more than ten business days to honor it. The full rules and message wording are in ride reminders and tracking links.

Taking payment when a family books

Private-pay requests go smoother when the price and the rules are clear before anyone submits.

• Quote before you confirm. Show how fares are figured, or send the quote with the acceptance.
• Take cards through your processor’s hosted checkout or pay link. The PCI Data Security Standard applies to any business that stores, processes, or transmits cardholder data. A card number typed into a notes field or an email pulls your systems into that group.
• Ask for a deposit on long trips. A four-hour round trip to a specialist takes one van and one driver out of service for half a shift.
• Put your late-cancellation and no-show rules on the form and have the rider agree before sending. You can adapt our no-show policy template.

Our guide to charging riders by card covers saved cards, holds, and chargebacks.

Privacy and security on booking pages

A ride request carries a name, a home address, where the person gets care, and what help they need. Treat the form and the portal as part of the rider record.

45 CFR 160.103 makes a health care provider a HIPAA covered entity when it sends health information electronically as part of a standard transaction, an electronic claim being the usual example. Broker agreements can add duties of their own. Modivcare has every transportation company certify that its owners and drivers finished Modivcare training, and that training covers HIPAA privacy and security. Five safeguards matter most on booking pages:

1. A signed agreement with whoever hosts the form or portal. HHS guidance on cloud services treats any company that stores, receives, or sends rider health data for your company as your business associate. Sign the agreement before the first request arrives.
2. No ad or analytics tags on request pages without an agreement. HHS guidance on online tracking describes someone making an appointment on a covered clinic’s website: tracking code on the page can send the appointment details and the person’s IP address to the tracking vendor, which makes that vendor a business associate that needs an agreement. The same guidance says tracking on pages behind a login generally has access to health information. In June 2024 a federal court (American Hospital Association v. Becerra) struck a narrower part of that guidance: the part about public pages on health conditions or providers, where the only link is an IP address and a page visit.
3. One login per facility staff member. Each facility sees only its own riders. Ask facilities to tell you when staff leave, and review the user list on a set schedule.
4. Lean emails. A confirmation email needs the time and the place. Keep mobility details and notes behind a sign-in.
5. Secure pages throughout. The form, the confirmation page, and the portal all load over an encrypted connection.

The vendor side of this is covered in HIPAA-compliant NEMT software, and your own policies in HIPAA for NEMT providers.

A form every rider can use

The people booking include older adults and riders with disabilities, so the form has to work for them. The Justice Department’s guidance on web accessibility and the ADA (March 18, 2022) lists inaccessible online forms among its examples of website barriers: fields without labels a screen reader can announce, missing instructions, and no alert when a field is empty or wrong. Its other examples include red text as the only sign that a field is required, and pages that cannot be used without a mouse. For technical detail, it points to the Web Content Accessibility Guidelines (WCAG) and the federal Section 508 Standards.

In practice:

• A visible label on every field, written in plain words
• Large buttons that are easy to tap on a phone
• Required fields marked with text, not only with red
• Error messages that say what to fix
• A form that works with a keyboard alone
• Your phone number at the top for anyone who would rather call

Rolling it out to facilities

A slow, steady rollout keeps facilities on your side:

1. Start with one or two facilities that already send you rides every week.
2. Set up a login for each staff member and hand over a one-page how-to.
3. Keep taking calls and faxes during the switch. Enter those requests yourself so every ride lives in one place.
4. Review requests weekly for missing fields, late requests, and slow replies.
5. Fix the form as you learn. A field people keep leaving blank needs a clearer label or a menu.

Four numbers show whether it is working: the share of requests that arrive online, the median time from request to confirmation, how many requests need a call back for missing details, and how many changes and cancellations facilities make on their own.

Taking ride requests online with HealthRide

Each facility you serve gets a HealthRide login where its staff request rides, follow them live on a map, and see and pay what they owe. Families and riders can book online as well, then open a text link to see the driver’s live location, with a reminder text before the ride and another once the driver sets off. Card payments run through a secure processor, by pay link or saved card, for riders and facilities alike. See the live map and payments pages for the details.