How to Launch a Telehealth Service Line

Launch in this order: define the clinical scope, pick the states, settle who may prescribe what, sign the vendors, write the policies, then enroll with payers. Each step constrains the next one. A practice that picks a platform before it knows whether it will prescribe controlled substances, or files payer enrollments before it knows which states it will serve, usually redoes the work.

What follows is that sequence, with the federal and state facts that shape each step as of October 2026. None of it is legal advice; the state-by-state conclusions belong in front of your counsel.

Step 1: What exactly will the service line treat?

Write the scope as a list of conditions, the visit types for each (synchronous video, audio-only, asynchronous), and the prescriptions likely to follow. Be specific. "Weight management" is not a scope. "Adults with a BMI that meets our protocol, synchronous video intake, labs before any prescription, follow-up every four weeks" is a scope.

The scope decides almost everything downstream:

• Controlled substances. If any Schedule II through V drug is on the list, the DEA question is in play. The fourth temporary extension (90 FR 61301, published December 31, 2025) lets DEA-registered practitioners prescribe by telemedicine without a prior in-person evaluation only through December 31, 2026. The Special Registration for Telemedicine was proposed in January 2025 and its final version went to OIRA for review on August 25, 2026; it is not published. Plan for both outcomes. Our DEA telemedicine rules hub tracks the status.
• Modality. Whether an asynchronous or audio-only visit can establish the patient relationship is a state-by-state question. See asynchronous telehealth by state and establishing a patient relationship by telehealth.
• Labs, devices and pharmacy. A scope that needs labs before prescribing needs a lab partner in every launch state. A scope that ships devices needs a device vendor and, if Medicare will pay, the remote monitoring rules.

Step 2: Which states first?

Choose launch states on four filters: where your clinicians already hold licenses, where the scope is clearly allowed by telehealth, where the payer mix works, and where demand is. Then check each state for the things that block a launch outright.

• Licensure. The clinician needs a license where the patient sits, a compact privilege, or a telehealth-specific registration. The Center for Connected Health Policy's Fall 2025 summary counts 18 states plus Puerto Rico and the US Virgin Islands with a telehealth-specific registration or license. Florida's (Fla. Stat. § 456.47(4)) is the best known, and it comes with limits: a registrant may not open an office in Florida or see Florida patients in person.
• Prescribing limits. Florida's same statute bars prescribing Schedule II drugs by telehealth except for psychiatric disorders and a few inpatient, hospice and nursing home settings. Other states have their own lists. Our state telehealth law pages summarize each state.
• Consent. CCHP counts 45 states plus DC and Puerto Rico with a telehealth consent requirement. The form and the wording differ.
• Corporate practice of medicine. If a non-physician company will own the brand, the structure question has to be answered state by state before you sign leases or hire. See corporate practice of medicine and telehealth.

Starting with three to five states and adding more in waves is a common pattern. Which states to expand into first explains how we sequence the waves.

Step 3: Who prescribes, and under what registration?

Map every clinician to every state on one sheet: license or privilege, DEA registration status in that state, state controlled-substance registration where the state requires one, PDMP account, and collaboration or supervision agreements for NPs and PAs where required. A DEA registration is tied to a state; a registration in Texas does not cover a patient in Ohio. The filings themselves are handled by our sister sites for physicians, nurse practitioners and physician assistants; licenses for a whole team start at White Glove Medical.

Step 4: Which vendors, and what do the contracts say?

Choose the platform, the pharmacy, the lab and any device vendor after steps 1 to 3, because each contract should name the states, the drug classes and the data flows you settled there. Every vendor that creates, receives, maintains or transmits protected health information for you needs a business associate agreement under 45 CFR 164.504(e). Starting January 1, 2027, the Consolidated Appropriations Act, 2026 (§6209(g)) also requires Medicare telehealth claims to carry a new modifier when the practitioner contracts with, or pays, the company that owns the virtual platform; CMS named them BB and BC in the CY2027 fee schedule proposal. Your platform contract is now a billing fact. Details are in choosing a telehealth platform, choosing a pharmacy partner and lab partners for telehealth.

Step 5: Which policies must exist before the first visit?

At minimum: patient location verification, identity verification, consent, emergency protocols, prescribing protocols per drug class, PDMP checks, record-keeping, and a privacy and security program that covers your website as well as your EHR. The policies a telehealth practice needs on day one lists each with what it must say.

Step 6: Payers, and what happens to Medicare in 2028?

Enroll last, once the states and the entity are settled. CMS notes in the CY2026 fee schedule final rule that a separate Medicare enrollment is required for each state in which a practitioner furnishes and intends to bill for covered services. Medicare's telehealth flexibilities (home as the originating site, no geographic limits, the expanded practitioner list) run through December 31, 2027 under the Consolidated Appropriations Act, 2026, and the in-person requirement for tele-mental health is deferred to January 1, 2028. If Medicare revenue matters to the service line, build the 2028 plan now: see the Medicare telehealth hub. Commercial enrollment is handled by White Glove Credentialing.

Who needs to be on the launch team?

Small launches fail when one person holds every thread. Name an owner for each of these, even if some are the same person:

• Medical director. Signs the scope and protocols, sets visit standards, and oversees prescribers. See what a telehealth medical director is responsible for.
• Licensing and credentialing lead. Runs the clinician-by-state matrix and the renewal calendar.
• Compliance lead. Owns policies, the privacy and security program, website tracking review and advertising claims review.
• Operations lead. Owns scheduling, intake, vendor management and the patient experience.
• Revenue lead. Owns payer enrollment and the billing setup, with outside help where needed.
• Outside counsel. Reviews the structure, the state-by-state conclusions and the vendor contracts.

Where do launches usually stall?

• Licensing started late. Board processing and fingerprinting set the critical path; nothing else can fix a license that has not issued.
• A DEA registration missing in one state. Controlled-substance patients in that state wait, and the schedule fills with patients who cannot be treated.
• A vendor that does not cover a launch state. Pharmacies and labs each have their own state lists, and New York's lab permit catches many practices.
• Structure questions found after hiring. A corporate practice problem discovered after clinicians are employed by the wrong entity is expensive to unwind.
• Marketing ahead of operations. Ads that run before every state is open create patients you cannot see, and claims written before the protocols exist rarely match them.

Is the practice ready on go-live day?

• Scheduling only offers each state's slots to clinicians authorized there.
• The platform captures patient location, identity and the state's consent language at every visit.
• A test patient has gone through intake, visit, prescription, pharmacy fill, lab order and result routing in each launch state.
• Every clinician has completed training on the policies and signed off.
• The emergency protocol has been drilled with a mock call.
• The website has passed a tracking review and the ads have passed a claims review.

The launch checklist

• Written scope: conditions, visit types, drug classes, labs, devices.
• Launch-state list with the blocking issues for each state resolved or flagged for counsel.
• Clinician-by-state matrix: license, DEA, state CSR, PDMP, collaboration agreements.
• Entity and structure memo reviewed by counsel in every state where ownership is an issue.
• Signed BAAs with platform, pharmacy, lab, device vendor, answering service and any analytics vendor that touches PHI.
• Policies adopted and staff trained, with sign-off dates.
• Website and intake reviewed for advertising claims and tracking technology.
• Payer enrollment submitted, with effective dates tracked.
• A compliance calendar with every renewal, registration and rule date. See building a telehealth compliance calendar.
• A DEA contingency for January 1, 2027, if controlled substances are in scope.

How long does a launch take?

The work in steps 1, 4 and 5 can be done in a few weeks. Licensure and payer enrollment set the real timeline, and they depend on the state, the board and the payer. Start those first, in parallel, as soon as the state list is fixed.

Our Telehealth Launch Blueprint runs steps 1 through 6 for one service line in up to five states for $4,950, and the deliverable is written for your counsel to review. See pricing.