BOOK DEMO
BOOK DEMO
faqs

NEMT, Paratransit & School Transportation FAQ

Common questions about the non-emergency medical transportation, paratransit, and school transportation industries. Industry terminology, regulatory basics, and operational fundamentals — answered clearly for operators, dispatchers, and people researching the field.

Table of Contents

NEMT industry basics

What is non-emergency medical transportation?

What's the difference between NEMT and emergency medical transportation?

Who pays for NEMT services?

What does an NEMT broker do?

What is a Medicaid managed care organization (MCO)?

Starting and Operating an NEMT Business

What licenses are required to start an NEMT business?

What insurance do NEMT operators need?

Do NEMT drivers need a commercial driver's license (CDL)?

What vehicles are typically used for NEMT?

How do NEMT operators get contracts with brokers?

Paratransit fundamentals

What is paratransit?

What's the difference between paratransit and NEMT?

What does ADA paratransit eligibility mean?

What is demand-response transit?

What is the National Transit Database (NTD)?

School Transportation Operations

What software do school districts use for bus routing?

What is special needs transportation in schools?

How does FERPA apply to school transportation software?

What are bell-time-aware school routes?

What's the difference between district-operated and contracted school transportation?

Billing, Compliance, and Regulations

What is 837P billing in NEMT?

What is a CMS 1500 form?

How does HIPAA apply to NEMT operations?

What is a Business Associate Agreement (BAA)?

What are common reasons NEMT claims get denied?

faqs

NEMT Industry Basics

Non-emergency medical transportation, commonly abbreviated as NEMT, is transportation provided to people who need to get to medical appointments but do not require an ambulance. The classic NEMT trip is a dialysis patient going to a thrice-weekly treatment, a behavioral health patient going to a weekly counseling session, or a senior going to a primary care visit. NEMT is a federally protected benefit under Medicaid, which means state Medicaid programs are required to provide transportation to medical appointments for beneficiaries who lack other means of getting there. NEMT is delivered by transportation providers — sometimes large multi-state operators, sometimes solo drivers operating a single van — who contract with brokers, managed care organizations, or directly with health systems.

Emergency medical transportation is ambulance service — typically dispatched through 911, staffed by paramedics or EMTs, and intended for medical emergencies where the patient’s condition requires immediate care during transport. NEMT is the opposite: scheduled, non-urgent, for patients who are medically stable. NEMT vehicles are vans or sedans — not ambulances. Drivers are not medical personnel; they are trained transportation operators with first aid certification but not paramedic credentials. The two service types are funded separately, regulated separately, and dispatched separately. A patient going home from a hospital after a planned surgery uses NEMT; a patient going to a hospital because of chest pain uses emergency medical services.

The largest funding source for NEMT in the United States is Medicaid, which covers transportation as a federally required benefit for eligible beneficiaries. State Medicaid programs typically contract with NEMT brokers (Modivcare, MTM, and others) who then contract with transportation providers. Medicare Advantage plans increasingly cover NEMT as a supplemental benefit. Private insurance, workers’ compensation, veterans’ benefits, and some employer health plans also fund NEMT. Self-pay (the patient or family paying directly) accounts for a smaller share. Different funding sources have different rules for eligibility, billing format, and documentation requirements — which is why NEMT operations need software that handles multiple billing formats and payer rules.

An NEMT broker is an intermediary between the funding source (typically a state Medicaid program or a managed care organization) and the transportation providers who actually deliver the rides. The broker handles eligibility verification, trip authorization, scheduling coordination, provider network management, claims processing, and quality oversight. The broker doesn’t own vehicles or employ drivers — those belong to the contracted providers. The largest NEMT brokers in the U.S. include Modivcare (formerly LogistiCare), MTM Inc., Access2Care, VectorCare, Alivi, and HBSS Connect Corp. Brokers typically charge the funding source a per-trip or per-member-per-month fee and pay providers based on contracted rates per trip type.

A Medicaid managed care organization is a health insurance company that contracts with state Medicaid programs to administer benefits for enrolled members. Instead of the state Medicaid agency directly paying for each service, the MCO receives a fixed per-member-per-month payment and is responsible for managing the member’s care. Most state Medicaid programs now operate primarily through managed care — around 70% of Medicaid beneficiaries nationwide are enrolled in MCOs. For NEMT, this matters because transportation benefits are typically administered by the MCO rather than the state directly, and each MCO may contract with different brokers. An NEMT operator working in a state with multiple MCOs may end up running trips for several different broker-MCO combinations.

FAQS

Starting and Operating an NEMT Business

Licensing requirements vary significantly by state and sometimes by county or municipality. Common requirements include a state business registration (LLC or corporation), a transportation provider license or motor carrier authority (often regulated by the state Department of Transportation or Public Utilities Commission), a state Medicaid provider enrollment if you plan to bill Medicaid directly, and broker credentialing if you plan to work with NEMT brokers. Some states require a separate medical transportation permit. Vehicles need commercial registration and the appropriate insurance. Drivers need clean driving records, drug screens, and (in some states) specific NEMT driver certifications. Before starting, contact your state Medicaid agency, state DOT, and the brokers you intend to work with to get the complete requirement list — missing one license can delay your start by months.

Standard NEMT insurance coverage includes commercial auto liability (typically $1 million minimum per accident, often higher for broker contracts), general liability, workers’ compensation if you have employees, and professional liability. Many broker contracts require named-insured certificates listing the broker as an additional insured. Some states or brokers require specific coverage for non-medical wheelchair transport at higher liability limits. Insurance for NEMT is generally more expensive than for non-passenger commercial vehicles because you’re transporting passengers — some of whom have medical conditions — and the liability exposure is higher. Plan for $5,000-15,000 per vehicle per year for commercial auto liability alone, depending on your state, drivers’ records, and coverage limits.

Most NEMT drivers do not need a CDL. CDL requirements are based on vehicle weight class and passenger capacity — typically vehicles over 26,000 pounds gross vehicle weight or designed to transport 16 or more passengers (including the driver). Standard NEMT vans transporting 1-8 passengers fall well below this threshold. However, NEMT drivers typically need a clean driving record, a valid state driver’s license, drug screening, criminal background check, and often state-specific NEMT driver certifications or first aid/CPR training. Some brokers require additional driver credentials specific to their network. If you operate larger vehicles — specifically larger than a 15-passenger van — CDL requirements may apply. Always verify with your state DOT and the brokers you contract with.

NEMT vehicles fall into a few common categories. Sedan or crossover vehicles handle ambulatory transportation — patients who can walk and don’t require special equipment. Standard passenger vans handle ambulatory and small-group trips. Wheelchair-accessible vans (typically with a side or rear lift, securement equipment, and 1-2 wheelchair positions) handle riders who use mobility aids. Bariatric-equipped vehicles handle riders requiring higher weight capacity equipment. Stretcher vans handle non-ambulatory transports where the rider needs to remain horizontal but doesn’t require an ambulance. Most NEMT operations run a mixed fleet to handle different rider needs. Vehicles must comply with state inspection requirements, and accessibility equipment requires periodic certification (wheelchair lifts in particular).

Each major NEMT broker has its own provider enrollment process, which typically involves an application, vehicle and driver documentation, insurance verification, on-site or virtual review, and contract execution. Modivcare, MTM, Kaiser Permanente, Access2Care, VectorCare, Alivi, and HBSS Connect Corp all run their own provider networks with their own enrollment requirements. The process can take 30-90 days from application to first dispatched trip. Brokers prioritize providers in their service areas with capacity for the trip volumes they need to fulfill. New providers typically start with smaller trip volumes and earn additional capacity over time as they demonstrate reliability and on-time performance. Building broker relationships is often easier when you can integrate technically — brokers prefer providers whose dispatch systems can receive trips electronically rather than via portal-only manual workflows.

faqs

Paratransit Fundamentals

Paratransit is shared-ride, demand-response transportation for people who can’t use fixed-route public transit because of disability. The term “paratransit” specifically refers to the service required under the Americans with Disabilities Act (ADA) to be provided alongside fixed-route public transit. When a city or transit agency runs bus and rail service, it must also provide paratransit service for people whose disability prevents them from using the fixed-route system. Paratransit is typically operated by transit agencies directly or by private contractors under contract to the agency. Service is demand-response — riders book trips in advance or same-day — with strict pickup window requirements set by ADA regulations. Paratransit overlaps with NEMT in that both serve people with mobility limitations, but the funding source, regulatory framework, and operating model differ substantially.

Paratransit and NEMT are often confused because both serve riders with mobility limitations or medical conditions. The differences come down to funding, regulation, and service model. Paratransit is funded primarily by transit agency budgets and Federal Transit Administration grants; NEMT is funded primarily by Medicaid and other healthcare payers. Paratransit is regulated by the Americans with Disabilities Act with specific rules about service area, eligibility, and pickup windows; NEMT is regulated by Medicaid program rules and state transportation regulations. Paratransit serves any qualifying disability, regardless of trip purpose — a paratransit rider can go to work, the grocery store, a friend’s house, or anywhere else within the service area. NEMT serves only medical-purpose trips. In practice, many transportation operators run both paratransit and NEMT with the same fleet, which is why software that handles both verticals is operationally valuable.

ADA paratransit eligibility is the formal determination that someone qualifies for paratransit service under the Americans with Disabilities Act. Eligibility is granted by the local transit agency through an application process that typically includes documentation of the person’s disability and how it prevents fixed-route transit use. There are three eligibility categories: full eligibility (the person cannot use fixed-route transit at all), conditional eligibility (the person can use fixed-route transit in some conditions but not others — for example, can use it in good weather but not in winter), and trip-by-trip eligibility (each trip is evaluated individually). Eligibility is typically time-limited and must be renewed periodically. The eligibility determination affects which trips a rider can book, how the trip is priced, and what reporting the operation must capture.

Demand-response transit is transportation service that operates based on rider requests rather than fixed routes and schedules. A bus running route 12 every 30 minutes is fixed-route service; a paratransit van that picks up wherever the rider is and takes them wherever they’re going (within a defined service area) is demand-response. Demand-response is the operational model behind paratransit, microtransit pilots, rural transit programs, senior transportation services, and many NEMT operations. The challenge with demand-response is operational efficiency — fitting many individual trip requests into a limited fleet without long wait times, excessive ride times, or empty miles. Demand-response scheduling is mathematically complex and benefits significantly from software automation.
The National Transit Database is the federal data repository that public transit agencies report into annually. NTD reporting is required for any transit agency receiving Federal Transit Administration funding. The data covers ridership, revenue hours, revenue miles, fleet inventory, financial information, and safety incidents. For paratransit operations, NTD reporting includes total trips, eligibility data, on-time performance, and operating costs. The data feeds federal funding allocations, transit performance benchmarking, and Congressional oversight. Paratransit operators — whether transit agencies running service in-house or contractors operating under contract — need software that captures the data fields NTD reports require and produces reports in the format the FTA accepts. Missing or incorrect NTD data can affect federal funding.
FAQS

School Transportation Operations

School districts typically use one of three categories of software for bus routing. Legacy desktop routing software (the longest-established category, dominant for decades) handles route construction and bell-time scheduling but often lacks modern features like parent-facing apps and real-time GPS tracking. Cloud-based modern routing platforms combine route optimization with real-time dispatch, parent communication, and integrated mobile applications. All-in-one transportation software handles routing alongside dispatch, fleet management, and parent apps from a single platform. The choice depends on district size, budget, and integration requirements with student information systems. Smaller districts often use simpler tools or even spreadsheets; larger districts and those with special needs transportation requirements increasingly move to integrated platforms.

Special needs transportation in K-12 schools refers to bus service for students whose individualized education programs (IEPs) or 504 plans specify transportation accommodations. Common accommodations include wheelchair-accessible buses, harness or safety vest requirements, aide or attendant accompaniment, specific seating requirements, travel restrictions (certain students should not travel together for behavioral reasons), and modified pickup or dropoff locations (often door-to-door rather than corner pickup). Special needs transportation typically operates separately from general education routes, with smaller buses, dedicated drivers and aides, and longer route times to accommodate individual student needs. Districts are legally required to provide IEP-mandated transportation as part of free appropriate public education — it’s not optional, and missing or mishandling these requirements can trigger compliance issues.
The Family Educational Rights and Privacy Act (FERPA) protects student educational records, and bus route data — including student names, addresses, IEP accommodations, and transportation needs — falls within FERPA protection. School transportation software handling student data must implement appropriate access controls so that only authorized personnel see student information. Parents have the right to access their own child’s records but not other students’ records. Transportation contractors operating for the district typically sign agreements that bind them to FERPA compliance. Parent-facing apps must scope each parent’s account to only their own child’s information. Audit logs and data retention policies must support compliance reviews. Districts evaluating transportation software often include FERPA compliance verification as part of vendor selection.

Bell times are the start and end times of the school day. A bell-time-aware school route is one that’s built around delivering students before the morning bell and picking them up after the afternoon bell. The constraint matters operationally because routes have to be timed precisely — students arriving 5 minutes after the bell are tardy, and a route that consistently delivers students late triggers parent complaints, principal frustration, and sometimes formal compliance issues. Modern routing software treats bell times as hard constraints during route construction — routes that can’t deliver on time aren’t proposed, and routes that come close to the bell time edge are flagged. Multi-bell-time districts (where elementary, middle, and high schools have different start times) can use the staggered bell schedule to share buses across schools, which significantly reduces fleet size requirements.

District-operated transportation means the school district owns the buses, employs the drivers, and runs the transportation operation in-house. Contracted transportation means the district contracts with a private transportation company that handles some or all of the operation — the contractor provides buses, drivers, dispatch, and management, with the district setting service requirements and paying per-route or per-student fees. Roughly 40% of U.S. school transportation is contracted; the rest is district-operated. The choice affects software needs significantly. District-operated transportation needs software that integrates with payroll, district HR systems, and student information systems. Contracted transportation needs software that handles multi-district reporting, contract-specific billing, and clear separation between districts. Some software platforms serve both models from one system, with role-based access controls keeping each operation’s data separated.
FAQs

Billing, Compliance, and Regulations

837P is an electronic claims format used in healthcare billing, including NEMT. The 837P is the electronic equivalent of the CMS 1500 paper claim form — it’s the standard format for submitting professional services claims to Medicaid, Medicare, and most commercial insurance payers. For NEMT, 837P claims include trip details (origin, destination, date, time), service codes (typically HCPCS codes for the type of transportation), modifiers indicating service specifics (wheelchair, ambulatory, escort), provider identifiers, and rate information. Payers process the 837P file and respond with electronic remittance advice (ERA, formally 835) showing what was paid and what was denied. Modern NEMT software generates 837P files automatically from completed trip data, reducing the manual work that previously bogged down NEMT back offices.

The CMS 1500 is the standard paper claim form for professional healthcare services submitted to Medicare, Medicaid, and most commercial insurance payers. The form was developed by the Centers for Medicare & Medicaid Services (CMS) and is used across the U.S. healthcare system. For NEMT, CMS 1500 forms capture the same information as 837P electronic claims — patient details, trip information, service codes, modifiers, and rates — in paper format. Most modern NEMT billing has shifted to 837P electronic submission, but some payers, smaller programs, and certain claim types still require CMS 1500 paper submissions. NEMT software typically supports both formats so operators can handle whichever each payer accepts.

The Health Insurance Portability and Accountability Act (HIPAA) protects patient health information, and NEMT operations handle HIPAA-protected data on every trip. Patient names, addresses, medical conditions necessitating transport, appointment locations (which reveal medical conditions), and trip purpose are all protected. NEMT operators are typically classified as business associates under HIPAA — they handle protected health information on behalf of covered entities (the broker, the health plan, or the originating healthcare provider). HIPAA compliance for NEMT operations includes role-based access to patient data (drivers see what they need for the trip; dispatchers see operational details; billing sees what’s needed for claims), encryption in transit and at rest, audit logs of who accesses what, and Business Associate Agreements with each healthcare partner. Software that NEMT operators use to manage trips, communicate with drivers, and bill payers must support these compliance requirements.

A Business Associate Agreement is a contract between a HIPAA-covered entity (a healthcare provider, health plan, or healthcare clearinghouse) and a business associate (an organization that handles protected health information on behalf of the covered entity). For NEMT, the broker is typically the covered entity, and the transportation provider is the business associate. The BAA specifies how protected health information may be used, requires the business associate to implement appropriate safeguards, mandates breach notification, and limits the business associate’s use of the information to the purposes of the contract. NEMT operators sign BAAs with each broker they work with. Software vendors handling NEMT data also sign BAAs with their NEMT operator customers — the BAA cascades down through the chain of organizations handling the data.

NEMT claim denials typically come from a small set of common causes. Member eligibility issues — the patient wasn’t actually enrolled with the plan or broker on the trip date — are the most common, often caused by month-to-month enrollment changes that hadn’t propagated to the operator’s system. Service code mismatches happen when the wrong HCPCS code or modifier is submitted for the trip type. Missing prior authorization affects trips that require pre-approval. Documentation gaps — missing pickup/dropoff times, missing signatures, missing trip notes — cause technical denials. Duplicate billing happens when the same trip gets submitted twice. Address mismatches between the authorized origin/destination and the actual trip details cause review denials. Strong NEMT software reduces denials through pre-submission validation — the system checks claims against payer requirements before they’re submitted, flagging issues that would cause denial so operators can fix them upfront rather than appeal afterward.

Looking for software to run your transportation operation?

NEMT Cloud Dispatch is the cloud-based platform for non-emergency medical transportation, paratransit, and school transportation operations. Direct integrations with major NEMT brokers, transparent pricing from $49.99/month, and a single platform that handles all three transportation verticals.

Book A Demo
See Pricing

Have a specific question that wasn’t covered above? Call (623) 226-8966 or [email protected]