Category A — Standard ride
- Patient
- The patient boards and leaves the vehicle unaided and needs no medical supervision.
- Permitted carrier
- Licensed taxi or locally authorised ride-hailing service.
NEMT City
NEMT City: patient ride coordination for one city or region
A package for launching non-emergency patient ride coordination in one city or region, together with a local partner and licensed local carriers.
Network model
Coordination between the organisation and the road
NEMT.cz does not own vehicles and is not an ambulance service. We sit between the organisation that needs the ride and the carriers licensed to drive it.
Healthcare provider / municipality
NEMT.cz coordination
Licensed local carriers
Who NEMT City is for
For local partners who want to offer coordinated patient rides to clinics, hospitals, dialysis centres, municipalities and care organisations in their area — without building the workflow and software from scratch.
How it works
Five steps from request to report
1
Request
The provider, municipality or patient sends a ride request by phone or e-mail.
2
Classify
We establish the ride category and what the patient needs on the way.
3
Dispatch
We book a licensed carrier that can serve that category and confirm the time.
4
Monitor
We watch pick-up, arrival and the return leg, and a person handles exceptions.
5
Report
The ordering organisation receives a ride record and the basis for invoicing.
Ride categories
What kind of ride does the patient need?
The patient's condition decides which carrier is allowed to drive the ride. We classify every request with the ordering organisation.
Category B — Assisted ride
- Patient
- The patient needs light help getting in and out, or travels with a folding wheelchair or walker.
- Permitted carrier
- A vetted carrier with an assistance service and a trained driver. The scope of help is agreed in advance — the driver is not a medical professional and does not lift or carry the patient.
Category C — Wheelchair-accessible ride
Confirmed case by case- Patient
- The patient stays in the wheelchair or needs a ramp, a lift and safe wheelchair restraint in the vehicle.
- Permitted carrier
- A vetted wheelchair-accessible (WAV/TPMR) operator. Availability is confirmed individually for the specific location and date.
Category D — Medical transport
Confirmed case by case- Patient
- The patient needs medical supervision, positioning, oxygen or an accompanying medical professional.
- Permitted carrier
- Only a locally licensed medical transport service. This is not an ordinary taxi service and availability is confirmed individually.
Categories C and D are not available everywhere — we always confirm them for the specific location and date. In an emergency call 112, not us.
Platform
What the platform does today
Live means the feature runs today as it is. Set up individually means we deliver it as part of the deployment — the scope and the interfaces are agreed with each partner, so it is not a self-service feature yet.
Multilingual intake
Requests are accepted and handled in Czech and English; German and Polish are handled with translation support.
Human escalation
Anything the automation cannot resolve is handed to a coordinator.
Ride monitoring
Pick-up, arrival and return legs are tracked and confirmed to the ordering organisation.
Invoicing export
Ride records are exported as the basis for invoicing.
Recurring rides
Series of repeating appointments booked as one standing order.
Partner API
REST endpoints and webhooks for carriers and ordering systems.
Audit log
Tamper-evident record of who ordered, changed or cancelled a ride.
Partner reporting
Self-service SLA and volume reports for partners and payers.
Scheduling integration
Booking a ride directly from an appointment in the provider's system.
Data minimisation is part of the design: a ride request carries pick-up, destination, time, ride category and agreed assistance. We do not ask for diagnoses and do not pass them to carriers. The service is designed for GDPR-conscious operation in the EU.
Roles
Who does what
A launch works when every party knows its part.
NEMT provides
- Coordination workflow and operating know-how
- Software for intake, dispatch, ride monitoring and ride records
- An operating standard for ride categories A–D and exceptions
- Automation and reporting within the agreed deployment scope
Local partner provides
- Legal and contractual set-up for the local market
- Licensed local carriers, including backup capacity
- Relationships with local healthcare providers and municipalities
- Day-to-day operations and the customer network
Healthcare organisation provides
- The need for rides and the appointment times
- Ordering rules: who may book rides, and for whom
- The information a ride needs — never diagnoses
- Feedback on punctuality and quality
Features marked as set up individually on the NEMT City page are agreed and configured during deployment; they are not activated automatically.
What a launched city needs
- A primary scheduled transport partner
- A backup local carrier
- Ride-hailing capacity where it is appropriate and legal
- A licensed medical transport provider for category D
Launch process
Pilot, evaluation and scale decision
A typical sequence, not a fixed timeline. Each step ends with a joint decision.
- Discovery — Country, city, the partner's role and the local demand for rides.
- Feasibility — Local regulation, available carriers, ride categories and who is responsible for what.
- Pilot set-up — Terms, processes, communication and onboarding of the first organisations and carriers.
- Measured pilot — Quality, volume, reliability and unit economics, measured on real rides.
- Scale decision — Both sides decide whether to continue, adjust or expand to further areas.
- The scope is agreed up front: area, ride categories, ordering organisations and duration.
- The pilot is evaluated on punctuality, completed rides, exceptions and unit economics.
- Pilot duration and pricing are agreed individually, based on the scope.
- After the pilot, both sides decide whether to continue and expand.
Frequently asked questions
Does NEMT own vehicles?
No. Rides are driven by licensed local carriers under their own authorisations. NEMT coordinates; the local partner builds the carrier network.
Which rides are covered?
Planned, non-emergency rides in categories A to D. Categories A–D are our internal coordination categories, not a harmonised European legal classification. Categories C and D are available only after individual confirmation for the location; category D only with a licensed medical transport provider. Emergencies are not covered.
What does AI do?
An AI assistant may answer the first contact and help with intake; it always identifies itself. It does not assess anyone's medical condition, and unusual or risky situations are always handed to a person.
Who pays for the rides?
That depends on the local market and the contracts in place. We do not assume reimbursement by health insurance in any country. Commercial terms are agreed individually.
Is there an API?
REST API and webhooks for partners are set up individually as part of a deployment. They are not a self-service feature today.
How long does a pilot take?
There is no fixed duration. Length and scope are agreed with each partner so that the pilot produces enough real rides to evaluate.
How is personal data protected?
A ride request carries only what the ride needs: pick-up, destination, time, ride category and agreed assistance. We do not ask for diagnoses and do not pass them to carriers. Personal data is processed under the GDPR.
What NEMT.cz is not
- We coordinate non-emergency rides that can be planned in advance.
- We are not an ambulance or emergency medical service and we do not provide medical care.
- We do not assess the patient's medical condition and give no medical advice.
- Transport is carried out by licensed carriers under their own authorisations.
- A driver is not a medical professional. The scope of assistance is agreed in advance with the ride category.
In an emergency call 112.
Start with one city
Tell us where you want to launch and what you already have in place. We will come back with the next steps.