Don’t replace your EHR. Integrate once and get all of it.
One signed, versioned, server-to-server API for prescriptions, office-use supply, labs, specimen collection and device data. Your clinicians stay in the software they already use, and every order lands on one TrueRoute record.
At a glance.
Telehealth, EHR and practice software.
- Integrate once and offer every service to the clinics you serve
- A signed, versioned API with a sandbox to build against
- Clinics without your software use the TrueRoute console
One integration. Every service.
Most platforms integrate a pharmacy, then a lab, then a collection service, then a device aggregator, each with its own credentials, webhooks and failure modes. With TrueRoute it is one contract, one set of credentials and one stream of signed events.
Prescriptions and office use
Your clinic's catalog and prices, a quote before you order, the same nine checks as the console, and the order itself.
GET /v1/integrations/catalog POST /v1/integrations/quotes POST /v1/integrations/prescription-checks POST /v1/integrations/orders POST /v1/integrations/prescribers
Labs
A quote with your account's price, the order, every result with its revisions, and critical values with their acknowledgements.
POST /diagnostics/quotes POST /diagnostics/orders GET /diagnostics/results/:id GET /diagnostics/results/:id/revisions/:n POST /diagnostics/critical-facts/:id/acknowledgements
Collection
Draw sites near the patient, open slots, a booked visit, a phlebotomist at home or an at-home kit, each with its own status.
GET /collection/sites GET /collection/slots POST /collection/appointments GET /collection/kits/:id
Device data and platform
Patient-permissioned device connections, the patient record keyed to your own id, what each clinic has switched on, and invoices.
GET /collection/devices POST /patients GET /patients/by-external-id/:id GET /availability GET /invoices
Paths shortened for reading. The full reference is shared with approved partners.
Integrate at the parent. Reach every clinic.
An EHR that serves a group connects once. Each clinic under it is granted, one by one or all at once, with exactly the services it should have. A clinic added later gets nothing until it is granted, so access is never inherited by accident.
Preview, then apply
See every clinic a bulk grant will touch before it is recorded, then apply it in one step.
Never narrows by surprise
A bulk grant only widens or leaves a clinic as it was. Taking access away is its own deliberate act.
Every grant on the record
Who granted what, to which clinic, when and why.
- Clinic APrescriptions, labs
- Clinic BLabs, collection
- Clinic CEvery service
- New clinicNothing until granted
What each call carries.
The details your engineering team will ask about first.
A credential scoped to its clinics
The clinic an order belongs to comes from the credential and its grants, never from the request body.
A signature over the raw bytes
An HMAC over exactly what was sent, so a request altered in transit is refused.
A five-minute window
A captured request cannot be replayed later.
An idempotency key
Claimed in the same transaction as the work, so a retried request never creates a second order.
POST /diagnostics/orders Authorization: Bearer <your partner credential> Idempotency-Key: lab-order-10023 X-TrueRoute-Signature: t=1791331200,v1=<HMAC-SHA256> Content-Type: application/json { the clinic, the patient, the tests, the collection }
diagnostics.lab_order.accepted collection.appointment.booked collection.appointment.collected diagnostics.specimen.received diagnostics.result.version_available diagnostics.result.critical order.shipped
Events you can build on.
One webhook stream for every service, signed, in order, and safe to retry.
Signed, with rotation
Rotate a signing secret without downtime: for seven days every event is signed under both, so you switch over on your own schedule.
In order, per subject
A later event for an order waits while an earlier one is still being retried, so you never see a result before its collection.
Only where access stands
An event for a clinic whose grant has ended is withheld, never sent.
Build against real scenarios before anything is live.
A sandbox plays the full journey onto the same records production uses: a result, a correction, a critical value, a rejected specimen. Your team sees every event it will ever have to handle before a real patient is involved.
- 1
A conversation
What you are building, and which clinics and services it serves.
- 2
Sandbox credentials
Issued per partner and scoped to your clinics, in a non-production environment.
- 3
Certification
You run the scenarios end to end and we review the results with you.
- 4
Live
Live credentials are issued and each clinic is granted the services it should have.
The portal is the same product.
Clinics without an EHR use the TrueRoute console: the same catalog, the same checks, the same record and the same bill. A group can run some clinics on its EHR and others in the console, side by side.
Already on an EHR or platform? Keep it.
After your clinic is onboarded, the EHR or practice platform you already use can connect to TrueRoute through the same signed API, once that platform is an approved integration partner. Your clinicians keep working where they are; orders and their status come back into the software they know.
- Your clinic is onboarded first, with its own catalog, prices and programs
- Your platform connects with its own partner credentials, granted to your clinic
- Not connected yet? The TrueRoute console works the whole time
Questions platforms ask.
How do software partners connect?
Partner access is switched on per approved partner, after onboarding. Every request carries a credential scoped to that partner’s clinics, a signature, a short-lived timestamp and an idempotency key.
Can we connect our EHR or platform?
Approved software partners connect through a signed, versioned, server-to-server API after onboarding, with a sandbox to build against first. Partner access is set up with each partner; it is not self-serve.
You do not need an integration to use TrueRoute: clinics can order in the TrueRoute portal in a web browser on its own.
Is there a sandbox to build against?
Yes. Sandbox credentials are issued per partner and scoped to your clinics, in a non-production environment. You run the scenarios end to end and we review them with you before live credentials are issued.
Can we get API credentials online?
No. Credentials are issued per approved partner after onboarding, never self-serve, and each is scoped to that partner’s clinics.
Does the API send events?
Yes. One webhook stream, signed, in order and built to be retried, carries each order’s events as it moves.
Can a platform that serves a group connect once?
Yes. It connects once at the parent, and each clinic under it is granted, one by one or all at once, with exactly the services it should have. A clinic added later gets nothing until it is granted.
Tell us what you are building.
Tell us about your platform and the clinics on it, and someone on our team will reply to talk through fit and onboarding.
Integration inquiry
Fields marked optional can be left blank.
No patient information, please. These forms are for business enquiries only — do not include patient names, dates of birth or prescription details.