NEMTIO.
Planning thousands of patient transports. In a world that doesn’t stick to the plan.
Nemtio automates non-emergency medical transport planning. Built in collaboration with one of Austria’s largest organizations in the field, it keeps vehicle assignments and routes responsive to a schedule that changes throughout the day.
DESIGN TARGETS
NOT DEPLOYED PERFORMANCE RESULTS
One changing plan. Two ways for dispatchers to stay in control.
A plan that keeps moving.
The planning timeline brings vehicles, assignments and new proposals into a single operational view. As transport requests and conditions change, dispatchers can see what is committed, what is suggested and what still needs attention.
The fleet at a glance.
Vehicle schedules, proposed transports and committed jobs share one timeline.
Make problems visible.
Unassigned transports and decisions awaiting release stand out alongside the plan.
Protect what is next.
A configurable near-term planning freeze helps avoid unnecessary changes to imminent assignments.
Every journey, in context.
Alongside the timeline, dispatchers have a detailed view of individual transports: their time windows, vehicle assignments, current status and outstanding actions. Proposed assignments remain reviewable rather than disappearing inside an algorithm.
IDENTIFYING DETAILS REDACTED · INTERFACE VIEWS, NOT PILOT RESULTS
THE
DETAILS.
The challenge
Patient transport schedules rarely stay fixed. Some journeys are booked well in advance; others arise with little or no notice — for example, when someone is ready to go home after a hospital discharge and needs transport now. At the same time, planners must account for pickup and arrival windows, mobility requirements, vehicle capacity, crew shifts, mandatory breaks, delays and cancellations.
The approach
Instead of calculating a plan once and leaving dispatchers to adjust it manually, Nemtio continuously revisits the schedule as new requests and disruptions arise. It balances operational constraints with the need to keep near-term assignments stable, so dispatchers can supervise the changing plan rather than rebuild it themselves.
The platform
At its core, an API-first orchestration kernel connects the planning engine to operational data, routing, audit trails and external systems. The interface exposes proposals, assignments and exceptions so dispatchers can review decisions or supervise automated commitments, according to configurable policy.
My contribution
I founded Nemtio and took responsibility for the platform's end-to-end architecture and build, bringing the optimization, backend services, integrations and operational interface together.
Current status
The platform is built and approaching its pilot stage. Its target planning scale is 4,000 transports per day across 1,000–1,500 vehicles; pilot outcomes and production performance are not yet available.