A Greater Houston medical-courier platform built around PHI-minimizing package QR codes, documented handling requirements, and a server-authoritative chain of custody from booking through receiver attestation.
Built for hospitals, labs & pharmacies
across the Texas Medical Center corridor
LP-2048
STAT DELIVERY
Pickup verified
10:41 AM
En route to
Houston Methodist
ETA
08 min
Cold-chain
2–8°C
Industry surveys of hundreds of lab professionals show 99% are impacted by medical couriers in a typical week — and facilities quietly absorb the cost in overtime, duplicate STAT fees, and repeat patient draws. We built LabPath Logistics to end exactly that.
hit a courier delay or error last month that compromised patient results
of lab leaders lost an irreplaceable specimen to a courier error in one year
had to re-collect specimens — forcing patients back for repeat draws
of lab staff stayed late waiting on a courier that didn't show on time
Source: CAP Today surveys of lab professionals (2023, n=269 · 2025, n=318), commissioned by MedSpeed. Figures measure at-least-once incidence in the stated period.
Four planned service lanes — STAT, scheduled routes, dedicated capacity, and pharmacy & home-health delivery — on one compliant network built for clinical transport.
Immediate
Dispatch workflow
Local tests prove the workflow. Contracts, integrations, operational drills, and live evidence turn that workflow into a service commitment.
Pickup windows, communication timing, and any service-credit remedies become commitments only when written into an executed facility agreement.
The STAT workflow is designed for immediate dispatch eligibility. A real ETA requires a live courier assignment and production location integration; traffic physics still applies.
Typed incident records exist in the product. Staffing, notification timing, escalation paths, and response evidence remain production-readiness gates.
The backend produces the booking quote and preserves the accepted amount. The website estimator is nonbinding and its published rate card still needs reconciliation before launch.
Opaque package-QR scans, timestamped custody events, receiver attestation, and signature are locally verified. Production photos, device telemetry, and PDF export remain release-gated.
The current business plan is month-to-month with no planned volume minimum. The executed agreement is authoritative once live contracting begins.
Published performance, from month one. Incumbents self-report their on-time rates. We’ll publish ours — monthly, unedited, on this site — starting with our first month of operations. If we want your specimens, you deserve our scoreboard.
Accountability by design
Target operating workflow
Checklist · Cold chain · Chain of custody
Driver standard
Training evidence required
The launch standard requires vetted, role-trained couriers, approved vehicles, package segregation, and material-appropriate containers. Those controls need current evidence before a live contract.
There are no patient fields, package QRs are opaque, and notifications carry only an order reference and status. An executed BAA and operational safeguards remain facility-by-facility launch gates.
The product is designed around an accountable dispatch relationship and offer-based courier assignment. Service levels and remedies become commitments only in an executed agreement.
The product, address bounds, and route concepts are designed for the Texas Medical Center and Greater Houston. Live staging and response performance still require operational proof.
From the Texas Medical Center to suburban clinics and independent labs, the workflow supports STAT direct routing without a fixed-minute pickup promise. Production routing and driver-location integrations remain in rollout.
Click through the interactive steps below to see how the system coordinates pickups and builds the chain-of-custody record step by step.
Interactive product preview · simulated data
Houston Lab
ACTIVE COURIER
Quote Accepted
Net-15 billing remains outside the app. An eligible courier can now receive the dispatch offer.
Current local verification evidence
Locally Verified E2E Layers
Required Package Scans
Patient Data Fields In Our Software
The cloud BAA and local enforcement tests are in place. Live adapters, deployment, and operational compliance evidence remain production release gates.
Emulator tests enforce tenant and assignment boundaries. Production deployment remains a release gate.
Tests keep alert copy to an order reference and status. SMS, email, and push providers are not integrated yet.
Cloud Data Access logging and an archive path are configured; staging and production workflow evidence remain cutover gates.
What Houston facilities should verify before trusting a dedicated medical-courier platform.
HIPAA compliance is an operating and contractual posture, not a federal courier certification. A facility should verify the executed BAA, workforce training, access controls, incident process, and evidence for the specific service. LabPath's technical design has no patient fields, uses opaque package QRs, and keeps PHI out of notifications; production legal and operating controls remain launch gates.
Preview the facility onboarding flow today. Public web submission and production portal access are not enabled yet.