How to build a telehealth platform, Part 3: e-prescribing and pharmacy routing

The signature is the beginning

In a clinic, prescribing ends at the printer. In telehealth it starts a pipeline: the prescription must reach a pharmacy that can lawfully fill it for a patient in that state, the pharmacy must fill and ship it, the package must arrive intact, and your product must know where it is at each step. Each stage has its own rules, its own failure modes, and its own source of truth.

Stage 1 · The electronic prescription

The clinician signs in e-prescribing software certified on the national network, and the prescription leaves as a standardized message — the NCPDP SCRIPT standard — addressed to a specific pharmacy. The pharmacy acknowledges receipt. Refill requests, cancellations, and changes travel the same way in the other direction. For controlled substances, DEA rules add identity proofing of the prescriber and two-factor authentication at the moment of signing, and the prescription must satisfy the federal telemedicine rules covered in our DEA telemedicine guide.

Two facts shape the architecture. You do not integrate with the network directly; certified software does, and infrastructure carries that certification so a brand never has to. And the network’s job ends at acknowledgement: it does not know whether the pharmacy filled or shipped anything. Status after this point comes from somewhere else.

Stage 2 · Choosing the pharmacy

The most common misconception in telehealth architecture is that pharmacy is a partnership you sign once. It is a routing decision made per order.

A program selling compounded semaglutide in thirty states, finasteride in fifty, and a Schedule IV medication in a handful will use several pharmacies, and any single order should go to the right one automatically. That logic — plus the contracts, the onboarding, and the per-pharmacy integrations behind it — is what a brand is buying when it buys infrastructure.

Stage 3 · The fill

The pharmacy verifies the prescription, checks it against the patient’s profile (drug utilization review, interactions, duplicates), compounds or picks the product, labels it, and packages it. Compounded products carry a beyond-use date, which makes fill timing matter: a product compounded on Monday for a patient who receives it Friday has lost four days of a short window. Good routing accounts for it; good status reporting tells your product when the fill happened.

Stage 4 · Shipping and cold chain

Room-temperature tablets ship like any parcel. Injectables and many peptides ship cold chain: insulated packaging with refrigerant sized for the transit time, carrier service levels chosen so packages do not sit over a weekend, and exception handling when a delivery is delayed or a package arrives warm. The pharmacy owns packaging; the program owns the patient’s expectations, which means your product needs the carrier events — label created, in transit, out for delivery, delivered, exception — not just “shipped.” The cold-chain glossary entry covers what to ask a pharmacy.

The status model your product needs

Patients experience this pipeline as a single question asked repeatedly: where is it? Answering it well means modeling the stages explicitly and receiving each as an event rather than polling.

On Lithos the clinical side of this arrives as encounter.approved (with the signed prescriptions — medication, sig, quantity, days_supply, the prescribing physician’s NPI — on the encounter) and the fulfillment side as order.created, order.processing, and order.completed, with the fulfilling pharmacy on the order; carrier-level tracking is outside the API today, so model those stages from your pharmacy’s notifications; the next post in the integration series, event-driven telehealth, covers building around them.

Refills flow backward

Pharmacies also originate messages: when a patient’s fills run out, the pharmacy can send a renewal request to the prescriber over the same network. In subscription telehealth the program usually drives renewals instead — a check-in on your schedule, a refill encounter, a clinician’s authorization — so the design question is which system is the source of truth for “due.” Pick the program, and make the pharmacy’s requests informational. Our refill guide covers the program-driven loop.

Build or buy

Nobody should build this layer for one brand. E-prescribing certification, EPCS, pharmacy contracting in multiple states, per-pharmacy integrations, carrier integrations, and cold-chain operations are the same for every program and take quarters to assemble. What a brand should own is the patient-facing status experience and the decisions about which treatments to offer where. Everything between the signature and the doorstep is infrastructure.

Frequently asked questions