The telehealth patient journey has eight stages: discovery and the storefront, adaptive intake with identity verification, provider matching and state routing, the encounter (asynchronous review or video), the clinical decision (prescription, labs, or decline), pharmacy fulfillment and shipping, follow-up messaging, and refills that turn one order into a program. A patient experiences it as one branded flow; operationally it is a hand-off chain in which each link has an owner and a characteristic way to fail. The brands that keep patients are the ones that know, for every stage, what good looks like, where the protected health information boundary sits, and who is on the hook when the stage stalls. This post walks the chain in order and maps where Orbit Intake, the Provider Network, OrbitRx, Orbit Labs and the white-label patient portal and app sit in it.
This is general information, not medical advice.
Key takeaways
- A telehealth patient journey runs discovery, intake, routing, encounter, decision, fulfillment, follow-up and refill, and each stage has a distinct owner and a distinct failure mode.
- Protected health information begins at the first intake question, so the marketing site and the clinical flow need different tooling, different tracking rules and a business associate agreement behind everything on the clinical side.
- Routing must match the patient's physical location at the time of the visit to a provider licensed in that state; a coverage gap at this stage is the most common reason a paid-for patient never gets care.
- Asynchronous review fits protocol-driven, non-controlled programs and video fits observation, nuance and controlled-substance prescribing; most programs run async-first with a video escalation path.
- Retention is decided after delivery, in follow-up messaging, refill review and lab monitoring, not in the first order.
Who this is for
- Operators designing or auditing a telehealth funnel and deciding where to put effort to reduce drop-off.
- Clinical and compliance leads mapping PHI boundaries, routing rules and escalation paths across a program.
- Product and engineering teams embedding care into an existing app and needing to know which stage each API call and webhook belongs to.
What are the stages of a telehealth patient journey?
| Stage | What happens | Owner | Typical failure mode |
|---|---|---|---|
| 1. Discovery and storefront | Patient finds the brand, reads the program, pays or starts intake | Brand (marketing, offer, pricing) | Vague eligibility; price revealed late; checkout on a page that also collects health data |
| 2. Adaptive intake and identity | Structured medical history, severity scoring, red flags, ID verification, consent | Clinical team sets questions; platform runs the engine | Too long, non-adaptive, or missing a field the provider needs, causing re-contact |
| 3. Matching and state routing | Patient's location mapped to a licensed, available provider | Platform and provider network | No licensed provider in the patient's state, or one provider holding the whole queue |
| 4. Encounter | Async chart review or live video | Licensed provider | Nights and weekends with no coverage; video forced where async is appropriate |
| 5. Clinical decision | Prescribe, order labs, request more information, or decline | Licensed provider | Manual pharmacy hand-offs; no EPCS when a controlled substance is indicated |
| 6. Fulfillment and shipping | Pharmacy fills, ships (cold chain where needed), tracking flows back | Pharmacy network and platform | Pharmacy not licensed for the state; markup inflating price; broken tracking |
| 7. Follow-up | Check-ins, side-effect questions, dose titration, lab results read | Provider plus brand support split | Clinical questions landing with non-clinical support; messages unanswered |
| 8. Refills and retention | Check-in before each refill, provider review, subscription renewal | Provider, platform, brand | Auto-ship without review; failed payments shipping product; churn with no exit survey |
The rest of this post takes each stage in turn.
Stage 1: How does the storefront start the journey?
The storefront is where the patient decides whether to trust you with their health history. What good looks like: the program page says who it is for and who it is not for, what the medication or service is, what is included each month, how fast the first decision usually comes, and what the price is, before the patient enters any health information. Payment-first and intake-first flows both work; what does not work is a page that silently mixes marketing and clinical data collection.
Common drop-off points here are qualitative but consistent: price surprises at checkout, a required account creation before the patient has seen value, and eligibility criteria revealed only after intake. On MyOrbitHealth the branded storefront, checkout and subscriptions are included in the platform, and the storefront can also present a patient self-order lab catalog where every order is signed by a provider.
PHI boundary. The storefront is pre-clinical. The moment a patient answers a medical question, you are collecting health information, which is why the intake step runs on separate, BAA-covered infrastructure and why ad pixels stop at this border.
Stage 2: What does good adaptive intake look like?
Intake is the clinical front door and the first safety control. A good intake is adaptive: it asks follow-ups based on earlier answers rather than presenting every patient with the same long form. It scores severity, so that a red-flag answer (a history that contraindicates the medication, a symptom that needs urgent care) routes the patient to escalation or decline rather than into the ordinary queue. It captures exactly what the protocol needs (relevant history, current medications, allergies, required photos or documents) and nothing the provider will not use. It embeds consent (telehealth consent, privacy acknowledgment, terms) with timestamps. And it verifies identity before a provider spends time on the chart, with a fallback path when automated verification fails.
What good looks like: the patient finishes on a phone in one sitting, the provider opens a chart that already contains what they need, and red flags never reach the ordinary queue. The failure modes are the mirror image: abandonment at an intrusive or redundant question, incomplete charts that force re-contact, and red flags discovered by the provider rather than by the engine.
Orbit Intake is MyOrbitHealth's AI-driven adaptive intake with severity scoring and red-flag escalation, white-labeled per brand; the clinical team sets the questions and thresholds per program during onboarding, which is why the telehealth launch checklist has intake design as its own phase.
PHI boundary. Everything from the first question onward is PHI. Intake runs under a BAA, access is role-based, and every view is audit-logged.
Stage 3: How does provider matching and state routing work?
A provider must be licensed in the state where the patient is physically located at the time of the visit. Routing therefore starts with location (declared at intake and checked against identity and billing signals), then filters the provider pool to those licensed in that state, credentialed for the program, and currently available, and then balances load so one clinician does not hold the entire queue while others sit idle.
What good looks like: every state in your ad targeting has active, available prescribers; the queue is visible in real time; time from intake completion to a provider opening the chart is short during business hours and bounded overnight. The failure mode that costs the most is simple: a patient in a state with no licensed provider pays, completes intake and waits, then churns. The second is a thin bench, where coverage exists on paper but one provider's day off becomes a backlog.
MyOrbitHealth's Provider Network covers this stage with 2,400+ board-certified MD, DO, NP and PA providers across all 50 states and 38+ specialties, live availability with intelligent load balancing, average response under six minutes during business hours, and 24-hour visit availability. Credentialing is to NCQA standards with monthly OIG/SAM exclusion screening, and brands can bring their own providers into the same routing table. Our staffing comparison explains why routing depth, not headcount, is the number to ask about.
Stage 4: Async review or video, and when does each fit?
An asynchronous encounter means the provider reviews the completed intake, any photos or labs, and the patient's messages, then documents a decision and plan without a live session, with the option to ask follow-up questions through the portal. A synchronous encounter is a scheduled or on-demand video (or, where permitted, audio) visit.
Async fits protocol-driven, non-controlled programs where the intake captures what the provider needs: hair loss, many dermatology complaints, sexual health, GLP-1 weight management with appropriate screening, routine refills. Video fits conditions that need observation or conversation, first encounters where a state requires a real-time component, and controlled-substance prescribing, which under DEA's current telemedicine flexibilities generally requires an audio-video encounter. Some states restrict asynchronous prescribing for particular drug classes, so modality is set per program and per state, not per brand.
What good looks like: async decisions arrive quickly during business hours and within a bounded window overnight; video is offered where it adds clinical value and required where the rule says so; the patient can see the status of their case in the portal at every moment. The failure modes are forcing video on a population that chose the brand for convenience, and nights and weekends with no coverage at all. The async vs sync telehealth guide covers the clinical, regulatory and economic tradeoffs.
Stage 5: What happens at the clinical decision?
The provider has four options: prescribe, order labs first, request more information, or decline with guidance. Each needs a clean path.
Prescribe. The prescription goes electronically to a pharmacy licensed for the patient's state, over Surescripts for retail and to a 503A compounding pharmacy for patient-specific compounded medications. If the medication is a controlled substance, the prescription must go through EPCS: the prescriber has completed identity proofing and uses a two-factor credential under 21 CFR Part 1311, and holds a DEA registration for the state. OrbitRx is EPCS-ready with two-factor identity proofing, routed via Surescripts, with DEA-registered partner pharmacies where applicable.
Order labs. Many programs (hormone therapy, weight management, longevity) need baseline or monitoring labs before or alongside the first prescription. The provider orders, the patient chooses how to be drawn, results return to the chart, and the provider reads them into the plan. Orbit Labs supports a Quest Diagnostics or Labcorp walk-in order slip, a Tasso at-home kit returned via FedEx, or mobile phlebotomy; the labs page describes the three methods, and lab pricing is quoted per program.
Request more information. The portal message should be specific, and the case should stay visibly open to the patient.
Decline. A patient who is not a candidate deserves a clear, respectful message and a next step, written by the brand and approved by the clinical team.
What good looks like: the decision is documented in the record with the reasoning, the prescription reaches the pharmacy electronically with no manual re-keying, and the patient receives a plain-language summary. The failure modes are paper or fax hand-offs, a controlled substance indicated with no EPCS path, and decisions that live in a provider's inbox instead of the chart. OrbitOS, the multi-tenant clinical console, holds patients, encounters, prescriptions and providers with a full HIPAA audit trail; the telehealth EHR guide explains what that record needs that a traditional EHR lacks.
Stage 6: How do pharmacy fulfillment and shipping work?
The pharmacy receives the electronic prescription, verifies it, fills it, and ships it, with cold-chain packaging for temperature-sensitive products such as many injectables. Tracking should flow back to the platform so the patient sees it in the portal and the brand's support team sees it in the same place.
What good looks like: the pharmacy is licensed for the patient's state before the prescription is routed, the medication cost passes through without a markup, compounded products ship from a certified pharmacy, cold-chain shipments carry tracking and temperature assurance, and the patient receives a shipping notification under your brand with realistic timing. Failure modes: a pharmacy licensed in most but not all of your states, a per-prescription markup that quietly compounds against your margin, a cold-chain failure with no replacement playbook, and tracking that lives only in the pharmacy's system.
OrbitRx routes to a LegitScript-certified pharmacy network, 503A compounding plus retail, with cold-chain shipping to all 50 states and 0% medication markup. The prescription.dispensed webhook event lets an integrated brand trigger its own shipping notification.
PHI boundary. Shipping data (name, address, tracking) tied to a prescription is PHI. Shipping notifications should not name the medication on the outside of the package or in a message that could be seen on a lock screen unless the patient has opted in.
Stage 7: What does good follow-up look like?
Follow-up is where clinical safety and retention meet. The patient has questions about side effects, dosing, timing and what to expect; some of those questions are clinical and some are logistical, and the two must route differently. Clinical questions go to a licensed provider through the portal; order, billing and shipping questions go to the brand's support team. An adverse-event message must reach a provider under a documented escalation path regardless of which channel it arrived on.
What good looks like: automated, branded check-ins at the moments that matter (first dose, first week, before each refill), a provider reply to clinical questions within a stated window, lab results read into the plan and explained to the patient, and dose adjustments documented as encounters. Failure modes: clinical questions answered by non-clinical staff, side-effect reports sitting unread, and check-ins that are marketing emails rather than clinical touchpoints.
The white-label patient portal and the native white-label iOS/Android app carry messaging, refills, orders and results under your brand, so the patient never meets the vendor.
Stage 8: How do refills and retention work?
A refill is not an auto-ship. Before each renewal, the patient completes a short check-in (weight, symptoms, side effects, adherence, for example), the provider reviews it, and the next prescription issues only if the review supports it. Subscriptions handle the billing side: renewal, pause, upgrade, cancel, and failed-payment recovery that holds the refill until payment clears.
What good looks like: the check-in is short and clinically relevant, the review is fast, the refill ships on time, and the patient understands why the check-in exists. Retention improves when the program feels like care and worsens when it feels like a subscription box. Failure modes: shipping product on a failed payment, shipping without review, and losing patients at the first renewal with no exit survey to learn why.
OrbitOS provides operational and revenue and retention reporting per brand; the telehealth subscription pricing guide covers plan design and dunning. We do not publish retention or conversion benchmarks because they vary too much by vertical and acquisition channel to be useful; measure your own cohort by stage instead.
Where exactly do the PHI boundaries sit?
Three lines matter.
- Marketing site to intake. Everything before the first medical question is marketing data under ordinary privacy law and the FTC's Health Breach Notification Rule (16 CFR Part 318) if you are a health app or site outside HIPAA. Everything from the first medical question onward is PHI under HIPAA when a covered entity or business associate handles it. Ad pixels stop at this line.
- Brand support to clinical staff. Your support team sees orders, shipping and billing and the minimum necessary to resolve them; licensed providers see the chart. Role-based access in the console enforces the split, and the audit trail proves it.
- Platform to pharmacy and lab. Prescriptions, lab orders and results move to and from pharmacies and labs under BAAs, over certified channels (Surescripts for prescriptions), with the minimum necessary data.
MyOrbitHealth includes a BAA in every contract, is SOC 2 Type II, runs a HITRUST-aligned architecture, and keeps PHI encrypted in US regions. The HIPAA for founders guide covers what the brand must do on its own side of each line.
How do MyOrbitHealth products map to each stage?
| Stage | MyOrbitHealth component | What it does at this stage |
|---|---|---|
| Storefront | Branded storefront, checkout, subscriptions | Presents programs and prices; starts intake; self-order lab catalog signed by a provider |
| Intake and identity | Orbit Intake | Adaptive questions, severity scoring, red-flag escalation, white-labeled per brand |
| Routing | Provider Network | 2,400+ providers, all 50 states, 38+ specialties, live availability, load balancing |
| Encounter | Provider Network via OrbitOS | Async review or video, 24-hour availability, average response under six minutes during business hours |
| Decision | OrbitOS, OrbitRx, Orbit Labs | Encounter record and audit trail; EPCS-ready e-prescribing via Surescripts; provider-ordered labs three ways |
| Fulfillment | OrbitRx pharmacy network | LegitScript-certified 503A and retail pharmacies, cold chain to 50 states, 0% markup |
| Follow-up | Patient portal and native app | Branded messaging, results, orders, with clinical escalation to providers |
| Refills and retention | OrbitOS reporting, subscriptions | Check-in before refill, provider review, revenue and retention reporting |
For API-integrated brands, the same stages map to the documented patients, appointments and prescriptions endpoints and the signed webhook events such as appointment.completed and prescription.dispensed. For the operational functions behind each stage, and how vendors divide them, read turnkey telehealth clinical operations.
Frequently asked questions
What is the telehealth patient journey?
It is the sequence a patient moves through from finding a brand to receiving ongoing treatment: storefront, adaptive intake with identity verification, matching to a provider licensed in the patient's state, an asynchronous or video encounter, a clinical decision (prescription, labs or decline), pharmacy fulfillment and shipping, follow-up messaging, and provider-reviewed refills. Each stage has an owner and a characteristic failure mode.
How long does it take to get a prescription through telehealth?
It depends on modality, coverage and the pharmacy. With asynchronous review and a provider available in the patient's state, the clinical decision can come within the hour during business hours; shipping then depends on the pharmacy and whether the product is cold-chain. On MyOrbitHealth, average provider response is under six minutes during business hours with 24-hour availability, and pharmacies ship to all 50 states.
Where does protected health information start in a telehealth funnel?
At the first medical question. Marketing pages before intake are governed by ordinary privacy law and, for health sites outside HIPAA, the FTC Health Breach Notification Rule; everything from intake onward is PHI handled under HIPAA and business associate agreements. Advertising pixels belong only on the marketing side of that line.
What is the difference between asynchronous and synchronous telehealth?
Asynchronous means the provider reviews the patient's completed intake, photos, labs and messages and responds without a live session; synchronous means a real-time video or audio visit. Async suits protocol-driven, non-controlled programs; video suits observation, nuance, and controlled-substance prescribing, which under DEA's current telemedicine flexibilities generally requires an audio-video encounter.
Why do telehealth patients drop off after paying?
The most common operational reasons are no licensed provider available in the patient's state, intake that is too long or asks for things the protocol does not need, slow or invisible case status, and shipping that arrives later than the checkout page implied. Each is fixable at the stage where it occurs.
How are refills handled in a telehealth program?
A short check-in before each renewal, a provider review of that check-in, and a new prescription only if the review supports it. Subscriptions handle billing, pause, cancel and failed-payment recovery, and the refill holds until payment clears. Auto-shipping without review is a safety and compliance problem, not a convenience.
Who answers a patient's side-effect question?
A licensed provider, through the patient portal or app, under a documented escalation path. The brand's support team handles orders, shipping and billing and routes anything clinical to the provider side; the role split is enforced by access controls in the clinical console.
Sources
- 45 CFR 164.504(e), Business associate contracts
- HHS Office for Civil Rights, Business Associates guidance
- FTC Health Breach Notification Rule, 16 CFR Part 318
- 21 CFR Part 1311, Electronic prescriptions for controlled substances
- DEA and HHS, Fourth Temporary Extension of COVID-19 Telemedicine Flexibilities, 90 FR 61301 (December 31, 2025)
- MyOrbitHealth Provider Network
Run the whole journey under your brand
MyOrbitHealth powers every stage behind 50+ digital clinics: Orbit Intake, a 2,400+ provider network in all 50 states, OrbitOS, OrbitRx at 0% medication markup, Orbit Labs, and a branded portal and native app, with a BAA in every contract. You control the brand; we power the medicine. Book a demo to walk your program through all eight stages, or see the white-label patient portal.
