NEMT SOFTWARE
Complete NEMT Software for Medical Transportation Operations
NEMT Platform connects payers, plans, Members and coverage to eligibility, authorizations, reservations, recurring transportation, dispatch, trip verification, billing and claims, so one enterprise platform runs the whole non-emergency medical transportation lifecycle.
Features
Manage the Complete NEMT Lifecycle
Payer → Plan → Member Coverage → Eligibility → Authorization → Reservation → Dispatch → Driver Execution → Trip Verification → Billing → Claims → Reconciliation → Reporting. Each stage hands its data to the next instead of living in a separate tool.
1. Payer
The organization responsible for the transportation benefit.
2. Plan
Payer plans with their own rules, pricing and context.
3. Member Coverage
Which Member is covered by which plan, and for what dates.
4. Eligibility
Service-date eligibility checks with a stored history.
5. Authorization
Authorization numbers, approved trips and effective dates.
6. Reservation
One-way, round-trip, Will Call and multi-leg trips.
7. Dispatch
Readiness-aware assignment and reassignment.
8. Driver Execution
Pickup, progression, drop-off and completion in the field.
9. Trip Verification
Operational proof of what happened on each trip.
10. Billing
Pricing rules, charges and the receivables queue.
11. Claims
Claims preparation, validation and submission through configured integrations.
12. Reconciliation
Remittance processing and payment application.
13. Reporting
Operational, eligibility, authorization and finance reporting.
Modules
Payers, Plans, Members & Coverage
NEMT starts with who is covered and under which plan. NEMT Platform models that relationship explicitly. A generic passenger account is not automatically a NEMT Member; a Member is created and linked deliberately.
Payer Profiles & Plans
Keep payers and their plans as first-class records.
- •Payer profiles with payer-specific context
- •Payer plans and payer-plan relationships
- •Rules and pricing that can differ by plan
Member Records
A Member is an explicit NEMT record, separate from a passenger login.
- •Explicit Member linkage to a passenger account where one exists
- •Mobility and service needs held on the Member
- •Member data kept within tenant and ownership boundaries
Member Coverage
Know which plan covers a Member on a given date.
- •Coverage with effective dates
- •Coverage history over time
- •Coverage tied to payer and plan
Modules
Eligibility & Authorization
Check coverage for the date of service and keep authorization context attached to the trip. Eligibility results are normalized into clear states, and raw provider responses remain server-side.
Service-Date Eligibility
Eligibility is evaluated for the date the trip is needed.
- •Normalized eligibility states
- •Eligibility history per Member
- •Raw provider responses kept server-side
- •Eligibility checks run through configured integrations
Authorizations
Capture the approvals that sit behind a reservation.
- •Authorization number and approved or pending status
- •Approved trip quantities and remaining-trip context
- •Effective dates
- •Authorization association with reservations
Modules
Reservations & Scheduling
Reservations capture the trip a Member needs, with the appointment, service level and mobility context dispatch will rely on.
Trip Types
Model the trips medical transportation actually involves.
- •One-way reservations
- •Scheduled round trips
- •Will Call returns: a return leg can exist without inventing a fixed pickup time
- •Multi-leg journeys
Appointment & Facility Context
Keep the reason and place of the trip on the reservation.
- •Facility endpoints
- •Appointment context and trip purpose
- •Service level and mobility requirements
Submission Safeguards
Reduce accidental double bookings.
- •Duplicate-submission protection on reservation creation
Modules
Standing Orders for Recurring Transportation
Recurring treatment, such as dialysis, is managed with Standing Orders. A Standing Order is a template; each generated occurrence becomes a normal Reservation that dispatch handles like any other.
Recurrence Rules
Describe how often transportation repeats.
- •Daily and weekly patterns
- •Weekday selection
- •Start and end dates
Exceptions & Control
Adjust a series without rewriting it.
- •Skip dates and exception dates
- •Preview of upcoming occurrences
- •Pause and resume
Generated Reservations
Occurrences stay traceable to the order that created them.
- •Generated Reservations link back to the Standing Order
Modules
Service Levels & Mobility Needs
Different Members need different vehicles and drivers. Service level and mobility requirements travel with the reservation so assignment can respect them.
Ambulatory, Wheelchair & Stretcher
Service levels that reflect how a Member travels.
- •Ambulatory, wheelchair and stretcher workflows
- •Assistance level
- •Escort or attendant context
Matching to Vehicles & Drivers
Requirements are compared with what vehicles and drivers can provide.
- •Vehicle capability matching
- •Driver qualification matching
Modules
Driver & Vehicle Readiness
Missing qualifications, compliance records or GPS stay visible as dispatch blockers instead of being discovered after a trip is assigned.
Driver Qualifications
Track what each driver is qualified to do.
- •Qualification tracking
- •Credential expiry
- •Verification status
Vehicle Compliance & Capability
Know what each vehicle can carry and whether its records are current.
- •Seating, ramp, lift and securement capability
- •Inspection, insurance and registration expiry
Dispatch Blockers
Readiness gaps are surfaced, not hidden.
- •Visible blockers for missing qualifications, compliance or GPS
Modules
Dispatch & Driver Execution
Dispatch works from ready, unassigned trips and respects Member needs, service level, driver qualifications and vehicle capability. Drivers then run the trip step by step.
Assignment & Reassignment
Put the right trip with the right driver and vehicle.
- •Ready and unassigned trip views
- •Assignment and reassignment
- •Driver readiness and vehicle capability considered
Driver Trip Execution
The driver moves the trip through its stages.
- •Pickup
- •Progression
- •Drop-off
- •Completion
Exceptions & Verification
Handle what goes wrong and keep a record of what happened.
- •Exception and recovery workflows
- •Trip verification and operational proof workflows
Who it's for
Member, Facility & Payer Portals
Each audience sees only what it should, scoped to the Members, facilities or payers it belongs to.
A Member web portal for managing their own transportation.
- ✓Upcoming trips, booking and trip details
- ✓Tracking
- ✓Coverage, eligibility and authorization context
- ✓Recurring transportation
- ✓Communication preferences
Modules
Pricing, Billing & Accounts Receivable
Pricing resolves from the most specific rule that applies: payer plan, then payer, then facility, then the tenant default. Receivables are worked from queues and aging views.
Pricing Rules
Configure how a trip is charged.
- •Base charge, minimum charge and mileage
- •Wait time, after-hours and weekend charges
- •Cancellation and no-show charges
- •Service-level and payer-specific pricing
Accounts Receivable
Follow what is owed and by whom.
- •AR queue and AR aging
- •Payer AR and facility AR
- •Reconciliation of recorded payments in the platform
Modules
Claims, EDI, ERA & Remittance
NEMT Platform supports claims preparation, validation, submission, acknowledgement, rejection, remittance and resubmission workflows through configured integrations. Outcomes depend on payer rules and the data submitted; the platform does not promise acceptance or reimbursement.
Claims Work Queue
Prepare and send claims from one place.
- •Claims work queue
- •Validation
- •Submission
- •Acknowledgement and rejection signals
Denials & Resubmission
Work what comes back.
- •Denial and remittance queue
- •Resubmission candidates
ERA & Remittance
Process remittance information and apply payments.
- •ERA retrieval
- •Remittance processing
- •Payment application and reconciliation context
Modules
Configurable Stedi & Integration Center
Eligibility and claims connectivity is provided through a configurable Stedi integration. Availability depends on how your deployment is configured; it is not assumed to be enabled everywhere.
Configurable Stedi Integration
Connect eligibility and claims workflows to an external clearinghouse where configured.
- •Eligibility checks
- •Claims validation, submission and sync
- •Configured per deployment
Integration Center
Operate integrations without leaving the platform.
- •Event destinations
- •Retry and dead-letter workflows
- •Machine identities with scoped permissions
- •Create, rotate and revoke credentials
Partner Reservation API
Let approved external systems submit and track reservations.
- •Partner and machine API access
- •Tenant boundaries enforced on every call
Features
Reporting Across Operations and Finance
See how trips, eligibility, authorizations, drivers, vehicles, facilities and money are performing, and export what you need.
Trip Performance
Completed, cancelled and exception trips.
Eligibility & Authorization
Eligibility results and authorization usage.
Driver Performance
How drivers are performing across trips.
Vehicle Utilization
How vehicles are being used.
Facility Activity
Reservations and trips by facility.
Billing, Finance & Claims
Receivables, claims status and finance views.
CSV & Export
Take reporting data into your own tools.
Security
Security & Multi-Tenancy
Built with role-based access, tenant isolation, auditability and privacy-conscious workflows for organizations operating in regulated healthcare transportation environments.
Role-Based Access
NEMT-specific permissions for who can see and do what.
Tenant Isolation
Each organization’s data is kept separate in a multi-tenant platform.
Ownership & Scoping
Customer ownership checks and payer and facility scoping.
Machine API Scopes
Scoped permissions for partner and machine identities.
Auditability
Activity is recorded so changes can be reviewed.
Cross-Passenger Isolation
One Member or passenger cannot see another’s records.
Use cases
Learn More About NEMT Operations
Practical guides on requirements, scheduling, dispatch, eligibility, recurring transportation and billing for non-emergency medical transportation.
A practical checklist for defining and comparing NEMT software across coverage, eligibility, dispatch, portals, billing and security.
Learn more →See how a trip moves from Member and coverage through eligibility, authorization, reservation and dispatch readiness.
Learn more →Understand readiness, mobility matching, driver qualifications, Will Call returns and exceptions in NEMT dispatch.
Learn more →Learn how service-date eligibility, coverage, authorization and provider responses fit into NEMT booking.
Learn more →See how recurring transportation templates generate normal Reservations, with skips, exceptions and pause and resume.
Learn more →Follow a completed trip through pricing, receivables, claim preparation, remittance and reconciliation.
Learn more →Understand what medical transportation adds to ride booking: Members, payers, authorizations, readiness and claims.
Learn more →Use cases
Need a Custom NEMT Implementation or Integration?
Every transportation network has its own payers, facilities and systems. RuteAppz can scope the implementation with you.
Need a custom NEMT implementation or integration? RuteAppz can configure, extend and integrate the platform around your operation.
Learn more →For taxi, shuttle, corporate transport and wider mobility operations that sit alongside NEMT.
Learn more →Looking for general on-demand taxi operations instead? Rute Taxi Platform covers ride booking, dispatch and driver apps for taxi and ride-hailing businesses.
Explore Taxi Platform →FAQ
NEMT Software FAQs
READY TO GET STARTED
See How NEMT Platform Fits Your Operation
Tell us about your payers, facilities, Members, fleet and trip volume. We will walk through the lifecycle against how you run transportation today.