Project TRIPLINK

The Real Problem: Medical Transportation Is Operationally Fragmented

The biggest weakness in the current NEMT model is not a lack of vehicles. It is a lack of synchronized operational intelligence.

Today’s transportation workflows are often divided across too many disconnected layers:

• brokers approve trips,
• facilities request pickups,
• dispatchers manually juggle schedules,
• drivers operate with incomplete information,
• and billing teams clean up what operations could not document properly.

The result is predictable:

• patients wait too long after discharge,
• dialysis and recurring patients get delayed,
• wheelchair and stretcher assets are used inefficiently,
• dispatchers spend the day manually fixing preventable problems,
• providers lose money through deadhead miles, poor routing, and billing errors,
• and facilities become frustrated by the lack of visibility and reliability.

Project TRIPLINK is built to solve those operational failures at the system level. It acts as a live medical logistics infrastructure that continuously aligns trip demand, fleet resources, patient readiness, and billing events in one coordinated workflow.

The Actual Problems We Are Solving

1. Static scheduling breaks the moment clinical reality changes

Most NEMT schedules are built in advance and then adjusted manually throughout the day. That works poorly in healthcare, where discharge timing changes constantly, appointments run late, treatments are extended, and patient readiness is often uncertain until the last minute.

A dialysis treatment overrun, a delayed discharge order, a late facility handoff, or an unexpected need for wheelchair transport can immediately disrupt multiple downstream trips. In many companies, dispatchers must resolve this manually, call by call.

TRIPLINK solves this with Broker-to-Bedside Synchronization (BBS), a real-time orchestration layer that absorbs updates from facilities, brokers, and field operations as they happen. Instead of leaving the dispatcher to rebuild the day manually, the platform dynamically reorders priorities, shifts pickup windows, and reassigns trips based on the latest operational reality.

This reduces avoidable waiting, missed pickups, and schedule collapse.

2. Dispatch decisions are often made without enough clinical or operational context

In many NEMT workflows, dispatch decisions are based on partial information:

• trip time,
• pickup address,
• destination,
• and basic transport type.

But safe and efficient transportation requires much more context:

• whether the patient is ambulatory, wheelchair, or stretcher,
• whether oxygen is required,
• whether the patient is bariatric,
• whether the facility is actually ready,
• whether the trip is routine or clinically time-sensitive,
• and whether the closest available vehicle can truly perform the transport.

TRIPLINK addresses this through a Predictive Patient-Readiness Engine (PPRE) and a live dispatch intelligence layer. The system evaluates facility throughput patterns, current delays, patient transport requirements, and vehicle status to determine not just who is closest—but who is operationally appropriate.

This prevents the common failure of assigning the wrong unit, sending drivers too early, or allowing high-priority trips to be delayed by lower-acuity transports.

3. Specialized vehicles are scarce and often misused

A major cost and efficiency problem in NEMT is improper asset allocation. Wheelchair vans, stretcher vehicles, and bariatric-capable units are limited resources, but many systems still schedule them inefficiently because they lack a strong logic layer for matching vehicle capability to actual patient need.

That creates downstream problems:

• specialized vehicles get tied up on trips that could have been handled by standard units,
• high-acuity patients wait longer for the correct transport,
• dispatchers must constantly rebalance the day,
• and utilization becomes reactive instead of strategic.

TRIPLINK solves this through Multimodal Asset Allocation (MAA). Every trip request is evaluated against vehicle capability, geographic position, service urgency, and local resource scarcity. The system protects high-value specialized assets from being wasted on low-acuity trips and helps ensure that patients with true mobility or transport constraints are matched to the right unit at the right time.

This improves both service reliability and fleet economics.

4. Drivers often operate with outdated or incomplete information

In traditional NEMT operations, the driver’s manifest can become obsolete within minutes. A patient may no longer be ready, a transport level may change, the pickup entrance may shift, or the facility may delay release. If these changes are not communicated immediately and clearly, the driver loses time, the patient waits, and dispatch gets flooded with calls.

TRIPLINK solves this with a HIPAA-compliant Smart Manifest, a live operational view for the field that updates in real time. Instead of relying on static lists or fragmented text communication, drivers receive current trip details, updated status changes, revised priorities, and patient mobility requirements through a structured mobile workflow.

This improves field execution, reduces miscommunication, and gives drivers the situational clarity they need to operate effectively.

5. Too much dispatch work is still manual

Many transportation providers still depend heavily on dispatcher memory, phone calls, spreadsheets, and manual status tracking to keep daily operations moving. This creates fragility:

• one overloaded dispatcher can bottleneck the entire operation,
• one missed call can delay care,
• one undocumented change can lead to a billing issue,
• and one poor handoff can create a service failure.

TRIPLINK is designed to reduce that operational burden by turning real-time events into automated workflow actions. Facility updates, driver status, location data, trip progression, and schedule conflicts are all processed as structured events rather than informal interruptions.

That means dispatchers can spend less time patching basic workflow failures and more time managing true exceptions.

6. Billing often happens too late and with avoidable errors

Revenue loss in NEMT does not come only from low rates. It also comes from weak documentation, delayed trip closure, missing verification, incorrect modifiers, and disconnected operational-to-billing workflows.

When operations and billing are separated, reimbursement slows down and claim errors increase.

TRIPLINK addresses this with an automated Trip-to-Claim pipeline. Once trip milestones are validated through route status, GPS-backed event confirmation, and structured trip completion logic, the platform prepares billing-ready transport data for downstream claim workflows. The goal is to reduce manual rework, improve documentation quality, and shorten the gap between completed service and reimbursement.

This turns operations into a cleaner revenue engine instead of a source of financial leakage.

How the Technology Solves These Problems

Project TRIPLINK is designed as a real-time logistics and medical transportation platform using technologies chosen for concurrency, reliability, geospatial intelligence, and event-driven operations.

Core Backend and Concurrency Layer

• Go (Golang) powers high-performance backend services responsible for dispatch logic, trip orchestration, status handling, and API operations where speed and concurrency matter.
• Erlang/OTP supports highly resilient, fault-tolerant real-time systems, making it ideal for event-heavy dispatch environments where uptime and process reliability are critical.

Operational Data and Geospatial Intelligence

• PostgreSQL with PostGIS stores trip, vehicle, facility, and geographic data while enabling advanced spatial queries for route logic, proximity matching, zone planning, and service coverage analysis.
• Redis supports fast in-memory state management, queueing, caching, and low-latency coordination for live operational updates.

Mobile Field Execution

• React Native powers the driver and patient-facing mobile applications, enabling real-time manifests, trip updates, location-aware workflows, and communication between field staff and central operations.

Mapping and Route Awareness

• Mapbox API provides route visualization, travel-time awareness, navigation context, and geospatial interaction that supports dispatch decisions and mobile execution in the field.

API and System Communication Layer

• GraphQL helps unify the platform’s operational data access so mobile apps, dispatch systems, and administrative panels can retrieve exactly the data they need efficiently.
• gRPC supports fast, structured service-to-service communication across internal platform components, especially where low-latency event handling is required.

Real-Time Event Processing

• Apache Flink enables stream processing of live operational events such as driver location updates, facility delays, dispatch changes, and trip progression signals. This is a critical part of turning raw operational activity into immediate workflow decisions.

Cloud and Infrastructure

• AWS Lambda supports event-driven backend actions and lightweight asynchronous processing for specific operational triggers.
• Docker standardizes application packaging and deployment.
• Kubernetes orchestrates services at scale and supports reliable production deployment across distributed workloads.
• Terraform manages infrastructure as code to ensure repeatable, controlled, and secure environment setup.

Security and Sensitive Data Protection

• HashiCorp Vault is used to secure secrets, credentials, tokens, and sensitive system configuration, supporting a stronger security posture for environments that handle protected operational and patient-related data.

Operational Impact

TRIPLINK is built to improve the core realities of NEMT operations:

• fewer manual dispatch corrections,
• stronger matching between trip needs and vehicle capabilities,
• faster adaptation to delays and clinical changes,
• better driver awareness in the field,
• cleaner trip documentation,
• improved facility coordination,
• and more reliable operational-to-billing continuity.

The platform is designed not just to move patients, but to coordinate transportation as part of the broader care delivery chain.

Why This Matters

Transportation failures in healthcare are not minor inconveniences. They interrupt treatment, delay discharge, increase operational stress on facilities, and reduce trust in providers. In high-volume NEMT environments, every inefficiency compounds across the day.

TRIPLINK is built to solve that by replacing fragmented transportation workflows with a synchronized logistics intelligence system—one that understands that in medical transportation, timing, readiness, clinical appropriateness, and execution all matter at once.

This is the shift from simple dispatch software to enterprise medical logistics infrastructure.