Launch operations
From idea to first patient: a telehealth launch checklist
A published site is only one piece of a launch. Before the first patient arrives, prove that a person can enter your offer, reach a clinical decision, and receive the right charge, fulfillment update, or refund.
10 min read
U.S. telehealth launch operations
Start with one patient path you can actually run
A new site may accept a patient's form before anyone has agreed which clinician reviews it, whether the patient's state is supported, or what happens if care is declined. Define a first offer narrow enough that each of those questions has an owner. HHS advises direct-to-consumer programs to decide their clinical focus, patient population, services, staffing, and workflow before offering care.[1]
Write a one-page brief that a clinical partner, operations lead, and website team can all use. A brand with several future programs can still launch one carefully scoped service first. The brief should answer these five questions:
Who is the first patient?
One defined audience, not a list of every condition you may treat later.
What are they buying?
The visit or program, its price, what is included, and what can cost more.
Where can they be served?
An initial state list matched to clinician coverage and program rules.
What happens after intake?
A named clinical review path, including decline and follow-up.
Who supplies each step?
The contracting party for care, pharmacy, payments, support, and marketing.
Put exclusions in the same brief. If the initial program cannot serve a state, requires an in-person visit for some patients, or does not include medication, the site and support team need to say so before a patient pays. The launch-cost guide helps separate your platform budget from care, pharmacy, payments, and acquisition costs.
Set the care boundaries before designing the checkout
Ask the clinical lead to approve the patient criteria, review method, escalation rules, and states served. HHS notes that cross-state care depends on the patient's location and the clinician's authority under that state's rules. Its guidance also recommends verifying patient location and consent before an appointment. Consent rules vary by state, so have the clinical and legal teams review the actual intake and consent language.[3][4]
The clinical partner should decide which cases can be reviewed asynchronously, which require a live visit, and which should leave the program for in-person or urgent care. The brand should not promise an approval or prescription before that independent decision. Record who contacts the patient if the clinician needs more information or declines care.
Confirm who owns the medical record and how staff reach it. For HIPAA-covered providers and plans, HHS says telehealth technology vendors must meet applicable HIPAA requirements and enter business associate agreements for services involving protected health information. A vendor's general security claim is not a substitute for reviewing your actual data path and contracts.[5]
Map every handoff, including the one that ends without an order
Draw the path from the first offer page to the first follow-up. Write the person or system responsible beside each transition. HHS's workflow guidance covers scheduling, check-in, triage, consent, documentation, technical support, and follow-up; it recommends a practice run before patients use the service.[2]
The first-patient path has a fork
The care decision determines the next payment, fulfillment, and patient-message action.
Offer and eligibility
Patient sees the right service and state availability.
Intake and consent
The correct history and consent reach the care team.
Clinical decision
Approval, decline, or more information is recorded.
Collect and fulfill
Capture the agreed amount when the workflow permits, send the approved order, and tell the patient what comes next.
Close without an order
Do not send a prescription. Apply the stated payment policy and give the patient a clear, private next step.
The hard part is the fork after review. If care is approved, someone must send the right order to the right fulfillment partner and tell the patient when to expect the next update. If care is declined, the system must prevent an order and apply the published payment policy. If more information is needed, the case needs a visible pending state and an owner. Our guide to card holds, capture, voids, and refunds explains why the timing of a charge has to match the care path.
For each handoff, ask for a test record or screenshot showing that the next party actually received the right information. A diagram in a sales deck is useful for scoping; a rehearsal tells you whether the team can operate the path.
Clear the data, payment, and marketing paths separately
List the information collected before and after intake, where it is stored, and which vendors receive it. Review analytics and advertising tags before they touch patient or authenticated pages. HHS's tracking guidance addresses disclosures of protected health information through online tools; it also notes that a court vacated one part of the guidance about unauthenticated public-page visits. The right decision depends on the data actually shared and the organization's role, not a blanket assumption about every page.[6]
Get payment approval for the real offer before turning on checkout. Stripe lists telemedicine and prescription-related commerce among categories that require additional due diligence. Confirm the merchant's approved scope, who is charged, when a hold becomes a completed payment, and who handles a void or refund.[8]
Marketing has its own gate. The FTC says objective health claims, including claims implied by imagery or testimonials, need support before publication. If the offer facilitates prescribing and you plan to use Google Ads in the U.S., review its telemedicine certification requirements before budgeting a campaign. A payment processor's approval does not approve an advertisement.[7][9]
Rehearse six outcomes before the first real patient
Use synthetic people and test accounts. Run the full path with the clinical, operations, payment, and support teams present. A successful approved order is only one test; the launch can still fail when a clinician declines care or a payment result is uncertain.
| Test case | What the team should prove |
|---|---|
| Eligible patient, approved care | Intake and consent reach the clinician; the approved charge and order reach the right partners; the patient sees an accurate next step. |
| Patient in an unsupported state | The path stops before care is offered. The patient sees a useful explanation, and no clinical or fulfillment request is sent. |
| Clinician declines treatment | No prescription or pharmacy order is created. The patient receives the approved message and the correct payment outcome. |
| More information is needed | The case stays pending with a visible owner; the patient knows what to provide and where to get help. |
| Payment action fails or times out | The team can determine whether money moved before retrying, and the patient is not charged twice. |
| Fulfillment cannot proceed | Operations sees the exception, the clinical/pharmacy partner decides the next safe action, and the patient receives an appropriate update. |
Write down the result, the person who checked it, and what remains broken. For a failed payment or pharmacy handoff, record whether the patient needs an immediate message, whether money moved, and which partner will resolve the case. Do not turn the unresolved exception into a silent support ticket.
Decide who can say “go live”
One launch owner should collect sign-offs from the teams that bear the risk. A developer can confirm that the form submits; only the clinical lead can approve the care protocol, and the payment provider must approve the offer it will process. Give each team a concrete result to demonstrate, then record the decision in one place.
Four sign-offs before real traffic
Ask each owner for a demonstrated result, not a status label.
Care
Clinical leadState coverage, intake, consent, and escalation path signed off.
Money
Commerce leadMerchant approval and charge, void, and refund cases tested.
Data
Privacy leadPatient data flows, vendor agreements, and tracking reviewed.
Follow-through
Operations leadEvery pending, declined, failed, and fulfilled case has an owner.
If a gate fails, narrow the release. A program with coverage in two states does not need to advertise in ten. A site can explain a future service while checkout stays closed. Make the live offer match the part of the operating model that has actually passed review.
Watch the first week for stuck patients, not just sales
The first live orders show where the rehearsal was incomplete. Check new intakes, cases waiting for clinical review, declined cases, payment exceptions, orders waiting on fulfillment, and unanswered patient messages every day. Track how long each case waits and who owns the next action. HHS recommends evaluating direct-to-consumer programs against their objectives and patient experience, not simply launching the technology and moving on.[1]
ScalerMD's published platform scope includes branded website and ecommerce setup with implementation support; partner services and managed marketing are scoped separately. Bring the first-patient path to that conversation so the technology work, clinical decisions, and operating responsibilities are clear before launch.[10]
Frequently asked questions
What must be ready before the first telehealth patient?
Your first offer and target states need defined clinical coverage, a reviewed intake and consent path, a patient-facing price and refund policy, an approved payment setup, and an owner for every follow-up. Rehearse an approved case and several declined or failed cases before sending real traffic.
Do I need clinicians in every state before launch?
You need an approved care model and appropriately authorized clinicians for the states where you actually serve patients. State rules vary. Begin with the states your clinical partner can cover, verify patient location before care, and expand only after checking the additional states.
Is a HIPAA-capable video tool enough?
No single tool resolves the full privacy workflow. A covered provider must assess where protected health information travels, which vendors receive it, what agreements and safeguards apply, and how staff access and marketing tracking are configured.
Behind the research
Sources & methodology
Sources reviewed
We reviewed primary HHS telehealth, HHS privacy, FTC health-marketing, Stripe merchant, and Google Ads policy pages on October 8, 2026. We also read public competitor launch guides to identify gaps, without adopting their market projections or linking to them. This checklist is an operating framework for a U.S. cash-pay direct-to-consumer program. It does not establish state eligibility, clinical protocols, merchant approval, advertising certification, or a guaranteed launch timeline. ScalerMD publishes the article and sells related platform and implementation services.
- HHS Telehealth: Developing a direct-to-consumer strategy
Clinical focus, patient needs, staffing, technology, legal considerations, roles, simulations, and evaluation.
- HHS Telehealth: Planning your telehealth workflow
Scheduling, check-in, triage, consent, documentation, technical support, and practice runs.
Back to:Telehealth workflow planning - HHS Telehealth: Licensing across state lines
State-dependent clinician licensure pathways and verification of patient location.
Back to:Location and consent - HHS Telehealth: Obtaining informed consent
State variation in consent requirements, documentation, and review of intake forms.
Back to:Location and consent - HHS Telehealth: HIPAA rules for telehealth technology
Technology-vendor responsibilities and business associate agreements for covered providers and plans.
Back to:Telehealth privacy and vendors - HHS OCR: Use of online tracking technologies
PHI and tracking technology on regulated sites and apps; the bulletin notes a 2024 court order vacating one public-page interpretation.
Back to:Online tracking and PHI - FTC: Health Products Compliance Guidance
Truthful, non-misleading, substantiated express and implied health claims in digital marketing.
Back to:Health-marketing claims - Stripe: Prohibited and restricted businesses
Additional due diligence for telemedicine and prescription-related payment activity.
Back to:Merchant review - Google Ads: Healthcare and medicines policy
Conditional certification rules for U.S. telemedicine advertisers facilitating prescribing.
Back to:Telemedicine ad policy - ScalerMD: Platform pricing and scope
Published platform and standard implementation scope; partner services and managed marketing are scoped separately.
Back to:ScalerMD platform scope
Published . Updated .
Prepared October 8, 2026 from current HHS, FTC, Stripe, and Google guidance. The launch gates and test cases are editorial recommendations, not a certification or a substitute for program-specific clinical and legal review.
Suggest a correctionWho’s behind this article
Jonathan Saeidian is the founder of Brenton Way, Bridge, and Growth Virality. At Brenton Way, he leads growth strategy spanning paid media, SEO, content, conversion optimization, and analytics for brands in health, beauty, and e-commerce. His ScalerMD Research articles examine telehealth platforms through a business and growth lens: how technology choices, launch responsibilities, and acquisition workflows fit together for founders and operators.