Access boundaries, audit history, and plain claims.
This page separates three things: what the software itself enforces, what stays the responsibility of your prescribers and the pharmacy, and what we set up with you during onboarding.
- Enforced by the database. Not by what a screen chooses to show.
- Added to, never rewritten. Orders, payments and status history.
- Claims said exactly. And the ones we do not make, said too.
Serious about the parts that matter.
The boundaries that protect your patients and your licence are enforced by the system itself, not left to a setting someone can forget.
Your patients stay yours
A clinic sees only its own patients, prescribers and orders, and the database enforces it.
Licences checked on every order
The prescriber’s licence in the patient’s state is checked before an order can be signed.
What you sign is what is sent
The signed prescription is stored exactly as signed. The pharmacy receives that, and so would an auditor.
A record nobody rewrites
Orders, payments and status history are added to, never edited, with every charge itemized.
Who can see what.
The boundaries between clinics, and between a clinic and the money behind its orders, are enforced below the screen.
One clinic cannot read another’s
A clinic session reads its own clinic’s patients, prescribers and orders, and that boundary is enforced by the database rather than by the screen. An organization running several clinics decides which pharmacies each one can see; access is opt-in, and a missing row means no.
Fees are documented
Fee and clinic-price configuration is fully versioned: who changed it, when, from what, to what, and why.
A charge you can account for
Behind every charge, the medication, fees, fulfillment and shipping are each recorded as their own line that cannot be edited, and the card is charged exactly their sum.
Frozen at signature, checked again before it leaves.
A prescription is a legal artifact. TrueRoute keeps the one that was signed, and re-checks it before it moves.
An immutable snapshot
Everything on the review panel is frozen into an immutable snapshot at signature. That snapshot, not a later join, is what the pharmacy receives and what an auditor reads.
Nine gates, twice
The server re-runs the nine gates at signature and again at send. An ineligible order is refused with a reason, never silently re-routed.
Non-controlled only
No DEA workflow and no EPCS. Gate 0 refuses a controlled substance before any pharmacy is considered.
The minimum a patient needs, and nothing a lock screen should show.
Shipment messages are logistics, not medicine. How shipment messages work
No medication detail
Shipment texts and email subject lines carry no medication name, dose, strength or SKU: the template has no parameter for one.
Consent, re-checked
A text is sent only if prior express consent is recorded, checked on every send. Replying STOP updates the consent record in our own system, not just the carrier’s.
A signed, expiring status link
Logistics only: no medication, price, patient record or login. An expired link and an order that does not exist render the same page, so the link cannot be used to probe for one.
Said precisely.
Whose license is on a prescription?
Prescriptions are written under the clinic’s own NPI and state licensure, and no TrueEval provider is ever enrolled at a pharmacy on a clinic’s behalf: the database refuses it.
How does TrueRoute check a prescriber?
What we claim about a prescriber is exactly what we do: NPI-validated and clinic-attested. We do not offer live license verification, and we do not describe it as something it is not.
How is one clinic’s data kept from another’s?
A clinic session reads its own clinic’s patients, prescribers and orders, and that boundary is enforced by the database rather than by the screen.
What record does TrueRoute keep?
Every order keeps its status history, signed prescription, payment state and tracking on one record. Order, payment and ledger records are append-only, configuration is versioned, and an activity feed shows who did what.
Does TrueRoute handle controlled substances?
No. TrueRoute is for non-controlled products and prescriptions only, and refuses a controlled substance before anything else runs. There is no DEA workflow and no EPCS.
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.
Software checks are not clinical decisions.
Who is responsible for what, from the software to the pharmacy.
The software
Refuses what it can check: an unenabled program, a missing enrollment, a prescriber not licensed in the ship-to state as attested, an unpriced product, a controlled substance. It records every decision.
Your prescribers and the pharmacy
The prescriber owns the prescription and its clinical judgment. The pharmacy holds its own licensure and makes its own dispensing decisions.
Onboarding
Accounts, roles, prescriber enrollments, ordering programs and delivery locations are set up and confirmed with you before orders flow.
Questions about security?
Ask us anything about how TrueRoute handles access, records and patient messages.