What is the best tech stack for a non-emergency medical transport company in 2027?

Direct Answer

The best tech stack for a non-emergency medical transport (NEMT) company in 2027 is built around a purpose-built NEMT dispatch, scheduling, and routing platform — Tobi (NEMT Cloud Dispatch) or RouteGenie for small fleets, MediRoutes or NovusMED (NovusEdge) at mid-size, Routematch at the enterprise tier — wired directly into Medicaid broker EDI feeds (Modivcare, MTM, Veyo), a Medicaid/insurance claims-and-billing engine, and a driver app that captures GPS, proof-of-pickup, signature, and odometer for reimbursement.

Layer on Samsara telematics, QuickBooks for accounting, and Power BI for reporting. The whole point is to turn broker-assigned trips into clean, paid claims while keeping ambulatory, wheelchair, and stretcher vehicles inside tight appointment windows.

Why the Non-Emergency Medical Transport Tech Stack Works Differently

NEMT is not a limo company with a medical paint job, and it is not a courier moving boxes. It is broker-assigned, Medicaid-billed medical transportation governed by appointment windows, vehicle-type requirements, and claim-level documentation. Four mechanics force a distinct tech stack.

1. Many short trips with strict on-time windows across mixed vehicle types. A single NEMT operator may run 60 to 300 legs a day — dialysis runs three mornings a week, one-off specialist visits, standing wheelchair pickups — each with a hard "appointment time" and a separate "return" leg that may fire hours later. Dispatch software has to batch shared rides, respect ambulatory vs. Wheelchair vs. Stretcher capacity per vehicle, and re-optimize in real time when a driver runs late. Generic field-service or rideshare tools do not model the will-call return leg or the wheelchair-securement time, so NEMT-native dispatch is the load-bearing layer.

1. Broker integration is mandatory because most trips arrive ASSIGNED. The majority of NEMT volume comes through state Medicaid transportation brokers — Modivcare (formerly LogistiCare), MTM, Veyo, Access2Care, Verida — who push trip assignments by EDI or portal and expect status updates back. If your platform cannot ingest a broker trip feed and return confirmations, willcalls, and no-shows automatically, dispatchers re-key everything by hand and you lose trips to faster providers. Broker connectivity is a procurement requirement, not a nice-to-have.

1. Reimbursement depends on claim-level proof, and the margins are thin. Medicaid and managed-care payers reimburse per trip only when the documentation is airtight: pickup and drop-off timestamps, GPS breadcrumb, member signature, odometer/mileage, and the correct procedure and modifier codes (A0130, wheelchair vs. Ambulatory). A missing signature or a mileage mismatch becomes a denied claim, and on $25–$60 trips a 10% denial rate erases the profit. The stack must capture proof at the curb and turn it into a clean EDI 837 claim with minimal human touch.

1. Compliance and HIPAA ride on every trip. Drivers carry credentials (defensive driving, CPR, PASS or wheelchair-securement certs), vehicles need inspection logs, and member health information is protected. The platform has to track credential expirations, vehicle inspection due dates, and Electronic Visit Verification (EVV) where states require it — all while keeping member data inside a HIPAA-aware system. This compliance burden does not exist for a courier and is heavier than a limo operator's.

The Core Stack, Layer by Layer

Dispatch, Scheduling & Routing Platform — Tobi (NEMT Cloud Dispatch) (alternates: RouteGenie, MediRoutes). This is the system of record for trips, vehicles, drivers, and the day's manifest. Tobi wins for small-to-mid fleets that want broker import, route building, a driver app, and billing in one subscription; RouteGenie is the close competitor with strong auto-scheduling and broker import.

MediRoutes is the stronger pick once you cross roughly 25 vehicles and need multi-location dispatch boards. Expect roughly $20–$40 per vehicle per month for Tobi/RouteGenie, with MediRoutes landing higher per seat. Newer Bambi uses AI to auto-assign trips to drivers and suits operators who want hands-off dispatch.

Broker Integration & Trip Assignment — native broker EDI built into the platform (alternates: WellRyde, NEMT Platform). Trips flow in from Modivcare, MTM, Veyo, Access2Care, and Verida; the platform must auto-ingest assignments and return pickup/drop confirmations, willcalls, and no-shows over the broker's EDI or API.

Tobi, RouteGenie, and MediRoutes all ship broker connectors. WellRyde (a Modivcare product) is the natural choice when Modivcare is your dominant broker, and NEMT Platform is a budget option for single-broker shops. Broker integration is usually bundled into the dispatch subscription, but premium multi-broker connectors can add a few hundred dollars a month.

Medicaid & Insurance Claims + Billing — platform-native billing with EDI 837 (alternates: Office Ally, Waystar). Once a trip is completed and documented, it becomes a claim. MediRoutes and NovusMED generate compliant EDI 837 claim files and reconcile broker remittances; Tobi and RouteGenie handle broker invoicing and private-pay billing natively.

For complex multi-payer Medicaid managed-care billing, route claims through a clearinghouse — Office Ally (low cost) or Waystar (enterprise scrubbing and denial management). Clearinghouse fees run roughly $35–$100 per provider per month or per-claim. Getting billing right is the single highest-leverage investment in the stack.

Driver App, GPS & Proof-of-Pickup — platform driver app + EVV (alternates: Samsara Driver, in-app signature/odometer). Drivers run the platform's mobile app to accept trips, navigate, log arrival/pickup/drop timestamps, capture member signature, snap odometer, and mark no-shows.

This is the evidence trail that gets claims paid and satisfies EVV mandates. Tobi, RouteGenie, MediRoutes, and NovusMED all include driver apps with GPS breadcrumb and signature capture. The app is bundled with the dispatch subscription, so there is no separate line item beyond device cost.

Vehicle Telematics — Samsara (alternates: Azuga, Geotab). Real fleet visibility — engine health, harsh-braking events, live location, dashcam, and driver coaching — sits on top of the dispatch GPS. Samsara is the default for NEMT fleets that want dashcams and maintenance alerts; Azuga and Geotab are lower-cost telematics-only alternatives.

Budget roughly $25–$45 per vehicle per month including hardware amortization. Telematics is optional below ~15 vehicles but pays for itself in insurance and accident defense as you scale.

Vehicle & Driver Compliance — platform compliance module (alternates: spreadsheet at startup, dedicated fleet-maintenance software). Track driver credential expirations (CPR, defensive driving, PASS/wheelchair securement), vehicle inspection and registration due dates, and insurance certs.

MediRoutes, NovusMED, and Routematch include compliance dashboards; a 1–5 van startup can survive on a disciplined spreadsheet but should graduate fast. Compliance lapses ground vehicles and trigger broker audits, so this layer earns its keep.

Payments — broker reimbursement + private-pay (alternates: Stripe, Square). Most revenue arrives as broker remittance against submitted claims; private-pay and facility-contract trips need card or invoice billing. Stripe or Square handle private-pay card capture and recurring facility billing.

Card processing runs the standard ~2.9% + $0.30. Keep broker AR and private-pay AR clearly separated in your billing system.

Accounting — QuickBooks Online (alternate: Xero). The general ledger, payroll feeds, fuel and maintenance expense tracking, and tax prep live in QuickBooks Online; Xero is the alternate for operators who prefer it. Expect roughly $35–$100/month depending on plan. Sync billing-system revenue and AR into QuickBooks rather than re-keying.

Business Intelligence — Power BI (alternates: Looker Studio, platform-native dashboards). On-time performance, denial rate, revenue per trip, cost per mile, and broker mix are the numbers that decide whether you keep your contracts. Power BI connects to your billing and dispatch exports for true operational reporting; Looker Studio is the free starter.

Most platforms include canned dashboards that suffice until you need cross-source analysis. Budget roughly $10–$20 per user per month for Power BI.

Real Operators & What They Run

ModivCare network providers (large multi-state) — high-volume providers serving Modivcare's broker network typically run an enterprise dispatch platform such as Routematch or NovusMED, ingest trips by EDI from Modivcare and a second broker, push completed trips to EDI 837 claims through Waystar, and feed everything into a data warehouse with Power BI on top.

Compliance and EVV are platform-managed across hundreds of vehicles.

A regional NEMT company (40–80 vehicles) — a mid-size operator covering several counties usually standardizes on MediRoutes or NovusMED (NovusEdge) for multi-board dispatch and routing, integrates two or three brokers (Modivcare, MTM, Veyo), runs platform-native EDI 837 billing reconciled against broker remittances, and adds Samsara for telematics and dashcams.

QuickBooks holds the ledger.

A small NEMT startup (1–5 vans) — a new entrant typically runs Tobi (NEMT Cloud Dispatch) or RouteGenie, imports trips from a single broker's EDI feed, uses the platform driver app for proof-of-pickup and signature, bills brokers natively, and keeps books in QuickBooks.

Telematics is deferred; a compliance spreadsheet covers credentials until volume justifies a module.

A wheelchair-van specialist — an operator focused on wheelchair and stretcher transport leans on dispatch software that models securement time and lift-equipped vehicle types accurately (MediRoutes or RouteGenie), captures securement-confirmation in the driver app for claim defense, and tracks PASS-certified driver credentials tightly.

Vehicle-type matching is the make-or-break configuration.

An NEMT + private-pay senior transport provider — a hybrid that mixes Medicaid broker trips with private-pay senior and facility contracts runs Tobi or MediRoutes for dispatch, splits broker EDI billing from Stripe-based private-pay card billing, and uses Bambi AI auto-dispatch to keep a small office staff productive across two revenue streams.

Power BI reports broker vs. Private-pay margin.

The pattern across all five: an NEMT-native dispatch and routing platform, broker EDI as the trip source, a claims/billing engine that produces clean EDI 837s, and curbside proof-of-pickup capture — with telematics, BI, and a data warehouse added as fleet size grows.

Integration Architecture

The dispatch platform is the operational hub, but the billing engine is where money is made or lost. Trips originate at the brokers, flow through dispatch to drivers, and return as documented claims.

The second view is the trip lifecycle — how one assigned ride moves from broker offer to paid claim, including the will-call return leg and the no-show branch that protects revenue.

Failure Modes

1. Claim denials from incomplete proof-of-pickup. Drivers skip the signature or odometer, or arrival timestamps do not match the GPS breadcrumb, and the payer denies the trip weeks later when cash is already spent. On thin per-trip margins a 10% denial rate wipes out profit. Make the driver app block trip completion until signature, odometer, and timestamps are captured, and run a daily denial-review queue.

1. Manual broker re-keying and missed trip assignments. Without live broker EDI, dispatchers copy trips from a portal by hand, miss late assignments, and return status updates slowly — so brokers route volume to faster providers. Insist on automated broker import and confirmation as a platform requirement, and monitor the broker scorecard weekly.

1. On-time performance collapse from poor routing. Treating NEMT like rideshare ignores wheelchair-securement time and will-call return legs, so drivers run late, members miss dialysis, and brokers penalize OTP. Use NEMT-native route optimization that models vehicle type and securement, and staff a dispatcher to handle real-time exceptions.

1. Compliance lapses that ground the fleet. An expired driver credential or a missed vehicle inspection surfaces during a broker audit and pulls vehicles off the road, killing revenue overnight. Track every credential and inspection due date in a compliance module with automated alerts, never a forgotten spreadsheet tab.

Budget & Sizing

Startup NEMT (1–5 vans, single broker). Tobi or RouteGenie or Bambi for dispatch and the driver app, single-broker EDI import, platform-native broker billing, QuickBooks for the ledger, and a compliance spreadsheet. Skip telematics initially. Roughly $300–$900/month in software plus per-vehicle dispatch fees.

Small-to-mid NEMT (6–25 vehicles, two brokers). RouteGenie or MediRoutes for multi-board dispatch, two-broker EDI integration, platform EDI 837 claims billing, Samsara telematics on every vehicle, QuickBooks, and platform compliance tracking. Roughly $1,500–$4,000/month all-in.

Mid-size NEMT provider (40–80 vehicles, multi-broker). MediRoutes or NovusMED (NovusEdge) for dispatch and routing, multi-broker EDI, native EDI 837 billing reconciled against remittances, Samsara fleet-wide, a clearinghouse (Office Ally or Waystar), QuickBooks, and Power BI reporting. Roughly $5,000–$12,000/month.

Large NEMT operator (150+ vehicles, multi-state). Routematch or NovusMED enterprise dispatch, broker EDI across all contracts, Waystar for claim scrubbing and denial management, Samsara, a data warehouse feeding Power BI, and full platform compliance/EVV. Spend scales into the tens of thousands per month but cost-per-trip drops with automation.

30/60/90 Day Implementation Plan

The goal is a working broker-to-claim pipeline by day 30, clean billing and proof capture by day 60, and optimization by day 90.

Days 0–30 — Stand up dispatch and go live with the broker. Select the NEMT platform (Tobi or RouteGenie for a small shop), connect the primary broker's EDI feed so trips import automatically, onboard drivers onto the mobile app, and run the first live manifests. Validate that confirmations and no-shows return to the broker without manual work.

Days 31–60 — Lock down billing and proof. Configure EDI 837 claim generation, enforce mandatory signature/odometer/timestamp capture in the driver app, reconcile the first broker remittance against submitted claims, and sync revenue into QuickBooks. Stand up a daily denial-review queue.

Days 61–90 — Optimize and report. Add Samsara telematics, move compliance tracking into the platform module with expiration alerts, build Power BI dashboards for on-time performance, denial rate, and cost per mile, and tune route optimization. Add a second broker once the pipeline is clean.

FAQ

Do I really need broker EDI integration, or can dispatchers just use the broker portal? Below a handful of trips a day a portal works, but it does not scale. Manual re-keying causes missed assignments, slow confirmations, and lost trips to faster providers. Automated broker EDI is the difference between holding a contract and losing it as volume grows.

What causes most claim denials in NEMT, and how does the tech stack prevent them? The top causes are missing member signatures, odometer/mileage mismatches, and timestamps that do not align with the GPS breadcrumb. A driver app that blocks trip completion until proof is captured, plus a daily denial-review queue, drives the denial rate down toward the low single digits.

Can I run a small NEMT operation on a single platform without separate billing software? Yes. Tobi, RouteGenie, and MediRoutes bundle dispatch, routing, the driver app, and broker billing in one subscription. You only add a separate clearinghouse like Office Ally or Waystar when multi-payer managed-care billing gets complex.

How is an NEMT stack different from a limo or courier stack? NEMT trips arrive assigned from Medicaid brokers, must be billed as claims with proof-of-pickup, and require ambulatory/wheelchair/stretcher vehicle matching and HIPAA compliance. Limo software optimizes for reservations and chauffeur experience; courier software optimizes for package routing.

Neither models broker EDI or EDI 837 claims.

When should I add telematics like Samsara? Telematics is optional below roughly 15 vehicles. Add it when accident-defense, insurance savings, dashcam footage, and maintenance alerts justify the per-vehicle cost — usually as you scale past a single dispatch board.

Do I need EVV (Electronic Visit Verification) for NEMT? It depends on your state and payer. Where EVV is mandated, the driver app's GPS, timestamp, and verification capture satisfy the requirement. Confirm with each broker and state Medicaid program, and choose a platform that supports EVV natively so you are not bolting it on later.

Sources

• Modivcare — transportation provider EDI and trip-assignment requirements for the broker network (2026).
• MTM — NEMT provider onboarding, trip confirmation, and reimbursement documentation guidance (2026).
• Veyo — broker provider portal and trip-status integration overview (2025).
• MediRoutes — NEMT dispatch, routing, and EDI 837 billing feature and pricing documentation (2027).
• RouteGenie — NEMT scheduling, broker import, and driver-app capability guide (2026).
• Tobi (NEMT Cloud Dispatch) — small-fleet dispatch, billing, and broker-integration pricing (2026).
• NovusMED (NovusEdge) — enterprise NEMT dispatch and claims platform overview (2026).
• Samsara — fleet telematics, dashcam, and per-vehicle pricing for transportation operators (2026).
• CMS / state Medicaid — NEMT reimbursement codes, EVV requirements, and managed-care billing rules (2025).