Transportation providers
Fleet operators running wheelchair vans, ambulatory cars and stretcher vehicles who need dispatch, driver apps and billing.
Healthcare / NEMT Software
NEMT software buyer's guide
Choosing non-emergency medical transportation software means matching dispatch, driver apps and Medicaid broker workflows to how your operation really runs. This guide from Agnotic Technologies sets out what to evaluate, when a packaged product fits, and when a custom build is the better choice.
Dispatch
Scheduling and routing
X12 270/271
Eligibility checks
X12 837
Claims for completed trips
Trusted by global innovators
Industry Overview
What should NEMT software buyers look for?
NEMT software buyers should check six areas: trip intake and scheduling, dispatch and routing, a driver app with proof of service, broker and Medicaid workflows, eligibility checks, and billing. Agnotic Technologies builds custom NEMT software and helps buyers test packaged products against their own trips before they commit.
Who buys NEMT software
Which NEMT buyers is this guide for?
Different buyers need different parts of an NEMT system. Knowing which one you are narrows the shortlist.
Brokers
Organizations that manage trips for a state Medicaid program or a health plan and assign them to a provider network.
Health systems and clinics
Hospitals, dialysis centers and therapy clinics that book rides for discharges and recurring appointments.
Health plans
Plans that offer a transportation benefit and need trip, cost and complaint reporting.
Industry Challenges
Where do NEMT software purchases go wrong?
Buyers usually find these gaps after go-live, when trips are already running on the new system.
The demo showed a clean booking flow, but standing orders for dialysis and therapy rides need manual work every week.
The driver app needs a constant signal, so proof of pickup fails on rural roads.
The broker's trip file format is not supported, so dispatchers re-key trips each morning.
Eligibility is checked once at booking and not again before the ride, so denied claims arrive weeks later.
Billing exports cover one payer, and every other payer needs spreadsheets.
Trip records reveal medical destinations, but access controls and audit logs were never scoped.
Decision table
Should you buy, extend or build NEMT software?
The answer depends on how standard your workflows are. Most buyers fit one column clearly.
| Criteria | Buy a packaged product | Buy and extend | Custom build |
|---|---|---|---|
| Workflow fit | Standard provider or broker workflows | Mostly standard, with a few gaps | A distinct model, such as a broker with its own network rules |
| Integrations | Those the vendor already supports | Vendor API plus custom connectors | Built for your brokers, payers and EHRs |
| Data ownership | Held in the vendor's platform | Shared between the vendor and your systems | Yours, in your own cloud account |
| Change speed | The vendor's roadmap | The vendor's roadmap plus your extensions | Your own backlog |
| Choose it when | Common workflows and a need to start soon | One or two gaps block you | Software is part of how you compete |
Our Approach
How do we help NEMT buyers decide?
Agnotic is a software development services company, not an NEMT product vendor, so our advice is about fit rather than selling a licence.
Map the trip lifecycle
We follow one trip from request to paid claim with your dispatchers, drivers and billing team, and note every manual step.
Score the shortlist
Each product on your shortlist is scored against the checklist below, using your own trip data in the demo.
Build only the gaps
If a product fits, we build connectors and extensions around it. If none fits, we scope a custom build with a fixed first release.
Capabilities
What does NEMT software need to do?
The core modules every buyer should check, whether bought or built.
Trip intake and scheduling
Requests by phone, portal or facility, with standing orders for recurring dialysis and therapy rides.
Dispatch and routing
Assignment by vehicle type, mobility needs, driver hours and location, with re-routing when a trip changes.
Driver app
Manifest, navigation, pickup and drop-off timestamps, signatures and offline capture where coverage is weak.
Broker and Medicaid workflows
Trip import from brokers, acceptance and rejection, status updates and the trip records each program asks for.
Eligibility checks
Member eligibility confirmed through X12 270/271 inquiries at booking and again before the ride.
Billing and claims
Completed trips turned into X12 837 claims or broker invoices, with remittance matched back to each trip.
Engineering Stack
Standards and systems NEMT software touches
What a buyer should expect any NEMT product or custom build to support.
Transactions
X12 270/271 eligibilityX12 837 claimsX12 835 remittanceBroker APIs and trip files
Apps
iOS and Android driver appsWeb dispatch consoleRider and facility booking portalsSMS and voice reminders
Location
GPS and telematicsRouting and mapping servicesGeofenced arrival detection
Security
SSO and role-based accessEncryption in transit and at restAudit loggingMobile device management
Measured Impact
Which numbers should an NEMT system report?
Measures buyers should ask every product to show, using real trip data.
On time
Pickups within the window
Share of pickups inside the window your program or contract sets.
Completion
Completed trips
Completed trips against no-shows and cancellations, with a reason for each.
Clean claims
First-pass acceptance
Trip claims accepted on first submission, with denial reasons traced.
Complaints
Rider and facility issues
Logged, assigned and closed with a recorded outcome.
My Lauren Maternal Health Platform | Built by Agnotic
A HIPAA-ready maternal health platform enabling remote patient monitoring, care coordination, and personalized engagement from pre-pregnancy through postpartum.
Case Study
LERA Health: Compliant Women’s Health App Platform
A women’s health product experience focused on guided care journeys, education, and compliance-aware workflows to support long-term engagement.
Case Study
Use Cases
Which NEMT projects do buyers bring to us?
Most NEMT work we scope is one of these, either around a packaged product or as a custom platform.
01
Broker integration layer
Connectors that import broker trips and return status, added to an existing dispatch product.
02
Driver app rebuild
An offline-first driver app with proof of service, replacing an unreliable one.
03
Facility booking portal
A portal for hospitals and dialysis centers to book and track rides.
04
Eligibility and billing automation
Eligibility checked before every ride and claims generated from completed trips.
05
Custom dispatch platform
A full platform for a broker or provider whose model packaged products do not fit.
06
Health plan reporting
Trip, cost and complaint reports built from the dispatch data.
Integrations
Which systems should NEMT software connect to?
Check each one against the products on your shortlist.
Trip source
Medicaid brokers
Eligibility
Payer eligibility (X12 270/271)
Claims
Clearinghouses
Facility bookings
EHRs and discharge systems
Vehicles
Telematics and GPS
Back office
Accounting and payroll
Self-assessment
NEMT software buyer's evaluation checklist
Tick what each product on your shortlist can show you with your own trips. The gaps are what you negotiate, extend or build.
Compliance-First Development Services Backed by Global Standards
We build secure, scalable products designed for privacy, interoperability, and regulatory readiness from day one across every sector we serve.
Health Insurance Portability and Accountability Act
Protect PHI with privacy-first architecture, encrypted storage and transmission, and strict access controls.
Our Edge
Why Global Leaders Choose Us
We combine deep technical expertise with industry-specific knowledge to deliver solutions that aren't just functional, but transformational.
Enterprise-Grade Security
We implement rigorous security protocols and compliance standards (HIPAA, GDPR, SOC2) across all industrial solutions to protect sensitive data.
High-Performance Scaling
Our architectures are built to handle massive data loads and user bases, keeping performance steady whether you're serving ten or ten million.
Accelerated Time-to-Market
Using our suite of internal tools and proven frameworks, we reduce development cycles and get your product to market 40% faster.
Embedded AI Integration
Beyond simple wrappers, we build deep-learning integrations and predictive analytics directly into the core of your industry-specific workflows.
Engagement Model
How does an NEMT engagement work?
Timing depends on scope; we agree a fixed first release on the scoping call.
01
Scoping call
We agree whether you need help choosing, extending or building, and what the first release covers.
02
Trip lifecycle mapping
One trip followed from request to paid claim with your team, noting every manual step.
03
Evaluation or design
Shortlisted products scored with the checklist, or a custom design for the gaps.
04
Fixed-scope first release
A connector, driver app or platform module running with real trips and monitoring.
05
Support
Broker format changes, payer rule changes and app releases under agreed change control.
Facts and sources
Rules that shape NEMT software
Short facts NEMT software has to support, each linked to its primary source.
A state Medicaid plan must specify that the Medicaid agency will ensure necessary transportation for beneficiaries to and from providers, and describe the methods it will use.
Source: 42 CFR 431.53 (eCFR)Federal Medicaid rules let a state run a non-emergency medical transportation brokerage program, covering services such as wheelchair vans, taxis, stretcher cars and bus passes for beneficiaries with no other means of transportation.
Source: 42 CFR 440.170(a)(4) (eCFR)HIPAA adopts ASC X12 standards for electronic transactions, including health care claims (837), payment and remittance advice (835), eligibility inquiries (270/271) and prior authorization requests (278).
Source: 45 CFR Part 162 (eCFR)The HIPAA Security Rule requires administrative, physical and technical safeguards for electronic protected health information.
Source: 45 CFR Part 164 Subpart C (eCFR)WCAG 2.2 is the W3C Recommendation commonly used as the technical benchmark for accessible web and mobile interfaces.
Source: W3C
Voice of success
We don't just build products; we forge lasting partnerships. See how we've helped industry leaders transform their vision into technical reality.
“I can clearly see how Agnotic has a unique way of handling end-to-end development. They are always active on quick chat and provide support quickly.”
Aaron Phelan
Founder, Benchmark
“Agnotic combines deep technical expertise with strong domain knowledge. They understand the business context, anticipate challenges, and make collaboration smooth and effective.”
John Pasmore
Founder, Latimer
“Agnotic is the best technical team we evaluated. Their engineering excellence made our work dramatically easier and allowed us to stay focused on what matters most for maternal care outcomes. They took full ownership of the technical execution, and we are always happy to continue working together.”
Kim Smith
Founder, My Lauren
Related pages
Related services for NEMT buyers
Pages that cover the systems around NEMT dispatch.
Custom software development for healthcare teams
Custom software for rehab, NEMT and specialty care teams, connected to EHR and billing systems.
Fleet management software
GPS tracking, vehicle maintenance and driver management for transport fleets.
Revenue cycle management software
Claims, remittance and denial workflows that NEMT billing feeds into.
HIPAA requirements for software teams
The safeguards every system that holds trip records needs.
More in Healthcare
More Healthcare Solutions
Explore other production-grade engineering platforms we deliver across healthcare.
Cross-Industry Reach
The Same Engineering Patterns, Across Other Industries
The technical patterns behind this platform translate naturally into adjacent verticals.
Frequently Asked Questions
Packaged products set their own licence terms, so compare total cost over the contract, including any connectors you would still need. A custom build depends on scope: the modules, the brokers and payers to connect, and the apps needed. We describe these drivers on the scoping call rather than quoting a price.
It depends on scope; we agree a fixed first release on the scoping call, such as a broker connector or a driver app, and give you its timeline before work starts.
Often yes, if the product has an API or file exports. We build connectors for broker trips, eligibility checks and billing around it, so you keep the product your dispatchers already know.
Role-based access so drivers see only their own manifest, encryption in transit and at rest, audit logs of who viewed which trip, and a business associate agreement with every vendor that handles trip data. These follow the HIPAA Security Rule safeguards.
Yes. Trip records link riders to medical destinations, so they are protected health information when handled for a covered entity. Agnotic signs a business associate agreement before any PHI is shared with our team.
Yes, if it is designed offline-first. The app stores the manifest, timestamps and signatures on the device, encrypted, and syncs when the signal returns, so proof of service is not lost on rural roads.
Industries