Provider Guide to Launching a Telehealth Practice

Launching a telehealth practice involves more moving parts than most providers expect — licensure, technology, billing infrastructure, and informed consent protocols all have to click into place before the first patient encounter. This page maps the structural requirements for establishing a compliant, functional telehealth operation, covering everything from state-by-state licensing obligations to HIPAA-compliant platform selection to reimbursement mechanics. The goal is a reference-grade overview that works equally well for a solo psychiatrist setting up a virtual panel and a multi-specialty group building a formal telehealth program.

Definition and Scope

A telehealth practice is a clinical operation — whether solo, group, or institutional — that delivers health services through electronic communications, including synchronous video visits, asynchronous store-and-forward consultations, and remote patient monitoring. The definition is not cosmetic. How a practice is classified under this framework determines which federal and state statutes apply, what billing codes are available, and how malpractice exposure is structured.

The scope of launching such a practice spans at least four distinct domains: regulatory compliance (licensure, prescribing, consent), technical infrastructure (platforms, connectivity, device integration), financial operations (credentialing, coding, payer contracts), and clinical workflow design. Missing any one of these doesn't produce a partial telehealth practice — it produces a legally or operationally broken one.

The National Telehealth Authority home page provides orientation across these domains for providers new to the field.

Core Mechanics or Structure

Licensure as the load-bearing wall. Telehealth law in the United States is built around a principle with significant teeth: a provider must be licensed in the state where the patient is physically located at the time of service — not where the provider sits. This means a physician licensed only in Massachusetts cannot legally treat a patient who happens to be visiting family in Florida, even over a routine video call. The Interstate Medical Licensure Compact (IMLC), as of 2024, includes 39 states plus the District of Columbia and Guam, offering an expedited pathway for allopathic and osteopathic physicians. The Nurse Licensure Compact (NLC) covers a comparable multi-state structure for registered nurses. Providers without compact participation must obtain individual state licenses for each jurisdiction served — a process that can take 60 to 120 days per state.

Platform selection and HIPAA. The technical backbone of a telehealth practice must satisfy HIPAA's Security Rule (45 CFR Part 164), which requires encryption in transit and at rest, access controls, and audit logging. During the COVID-19 public health emergency, the HHS Office for Civil Rights issued enforcement discretion allowing providers to use consumer-grade video tools; that discretion has since been withdrawn, meaning platforms must execute a Business Associate Agreement (BAA) with the covered entity. Dedicated telehealth platforms — not general-purpose video conferencing — are the compliant default. The telehealth technology platforms reference covers platform categories in detail.

Credentialing and privileging. Even after licensure is established, hospital-affiliated providers must complete telehealth-specific credentialing with each facility where telehealth services will be recognized. The Centers for Medicare & Medicaid Services (CMS) allows a mechanism called "credentialing by proxy," under which a distant-site hospital can rely on the originating site's credentialing decision — a provision governed by 42 CFR § 482.12(a)(8). Independent practices without hospital affiliation face a simpler but still non-trivial credentialing process with each payer. See telehealth credentialing and privileging for the full mechanics.

Causal Relationships or Drivers

The expansion of telehealth practice launches after 2020 was not accidental. CMS issued 1,135 pages of regulatory guidance between March 2020 and December 2021 relaxing originating site requirements, expanding the list of covered telehealth services, and permitting audio-only visits for certain Medicare beneficiaries. Those temporary flexibilities rewired provider expectations. When providers discovered that a large share of their patient population preferred video visits — or had no practical alternative — the business case for a permanent telehealth infrastructure became self-sustaining.

State legislatures followed. By 2023, 43 states had enacted audio-only reimbursement protections of some form (Center for Connected Health Policy, 2023 State Telehealth Laws Report), and 37 states had passed payment parity laws requiring private insurers to reimburse telehealth services at the same rate as in-person equivalents. These legislative shifts mean that the financial model for telehealth is no longer provisional — it is embedded in state insurance codes in a majority of jurisdictions.

Broadband access remains a structural bottleneck. The FCC's 2022 Broadband Data Collection found that approximately 14.5 million Americans lack access to fixed broadband at speeds of 25 Mbps download / 3 Mbps upload — the FCC's baseline threshold — with rural and tribal communities disproportionately affected. This shapes patient panel composition in ways a new telehealth practice must account for. Telehealth broadband and connectivity maps these gaps by region.

Classification Boundaries

Not all remote clinical activity is telehealth in the regulatory sense. The distinction matters for billing and liability.

Synchronous telehealth involves real-time, two-way audio-visual interaction between provider and patient. This is the archetype most payers reimburse and most regulations address.

Asynchronous (store-and-forward) involves the transmission of recorded health information — imaging, video clips, clinical notes — for review at a different time. Dermatology and radiology are primary use cases. Store-and-forward telehealth covers the technical and billing specifics.

Remote patient monitoring (RPM) involves the collection and transmission of physiologic data from a patient's location to a provider, using devices. RPM has its own CPT code family (99453–99458) and its own consent and billing logic. See remote patient monitoring for the full framework.

Telephone-only (audio-only) encounters occupy a contested regulatory space. Medicare covers audio-only visits for behavioral health under conditions established by the Consolidated Appropriations Act, 2023, but coverage parameters vary significantly by payer and state.

A practice that conflates these modalities will misapply codes, misbill payers, and expose itself to audit risk — a category of problem that is entirely avoidable with a clear operational taxonomy from the outset.

Tradeoffs and Tensions

The central operational tension in telehealth practice design is between patient access and clinical appropriateness. Expanding geographic reach means serving patients the provider has never met in person, across variable bandwidth environments, without the physical examination data that informs in-person clinical judgment. Some specialties — dermatology, psychiatry, primary care — tolerate this limitation well. Others — cardiology with complex presentations, orthopedics requiring range-of-motion assessment — tolerate it less. The telehealth vs. in-person care comparison examines where the evidence supports substitution versus supplementation.

A second tension exists between prescribing flexibility and regulatory constraint. The DEA's proposed special registration framework for telemedicine prescribing of Schedule II–V controlled substances — a rule under rulemaking as of 2023 — would establish new requirements for providers who prescribe controlled substances without an in-person evaluation. This directly affects behavioral health and pain management telehealth practices. The telehealth prescribing rules page tracks this rulemaking in detail.

A third tension is financial: telehealth visit reimbursement rates from Medicare are, for most codes, set at the same rate as in-person visits. But the overhead structure differs — no facility fee for home-based providers, but technology and platform costs that in-person practices don't bear. Whether this arithmetic favors telehealth depends heavily on visit volume and payer mix.

Common Misconceptions

Misconception: A single national telehealth license exists. It does not. No federal statute creates a unified national telehealth practice license. The IMLC and NLC are multi-state compacts, not federal licenses, and they cover specific provider types only.

Misconception: HIPAA compliance is the platform's responsibility. The covered entity — the provider or practice — bears compliance responsibility. A BAA with a platform vendor shifts some contractual liability but does not transfer the provider's underlying obligations under 45 CFR Part 164.

Misconception: Audio-only visits are universally covered by Medicare. Coverage is conditional. CMS's audio-only telehealth coverage applies to behavioral health services under specific statutory conditions established by the Consolidated Appropriations Act, 2023 (CMS Telehealth Services fact sheet), not to all visit types or specialties.

Misconception: Informed consent for telehealth is the same as for in-person care. Telehealth-specific informed consent is required by statute in at least 32 states, covering disclosures specific to the telehealth modality — technology limitations, privacy considerations, provider location. The telehealth informed consent reference covers state-by-state requirements.

Checklist or Steps

The following sequence represents the structural stages of telehealth practice launch, not a sequence of professional recommendations:

  1. Determine patient geography — Identify target patient states; this determines the complete licensure map required before any services begin.
  2. Assess compact eligibility — Determine whether IMLC, NLC, or other applicable compact membership is available for the provider type and states identified.
  3. Apply for required state licenses — Initiate applications in all non-compact states. Build 90-day minimum lead time into the launch timeline.
  4. Select a HIPAA-compliant platform — Confirm BAA availability; evaluate platform capabilities against the modality mix (synchronous, asynchronous, RPM) the practice will offer.
  5. Execute BAA with platform vendor — This step must precede any patient encounter on the platform.
  6. Complete payer credentialing — File credentialing applications with all payers the practice will bill; allow 90 to 120 days for completion.
  7. Develop telehealth-specific informed consent documentation — Draft consent language that satisfies the requirements of each state served, with legal review against the telehealth informed consent state matrix.
  8. Design billing and coding workflows — Map visit types to applicable CPT codes and modifier requirements; configure the practice management system accordingly. See telehealth billing and coding for code-level detail.
  9. Establish prescribing protocols — Determine which services will involve controlled substances; apply applicable federal and state prescribing requirements.
  10. Implement clinical workflow documentation — Ensure that telehealth visit notes capture patient location, technology used, and consent confirmation — all elements that differentiate telehealth from in-person documentation.

Reference Table or Matrix

Telehealth Practice Launch: Domain Requirements by Provider Scenario

Domain Solo Provider, Single State Solo Provider, Multi-State Group Practice
Licensure 1 state license IMLC/NLC or individual state licenses per jurisdiction All providers must independently satisfy per-state requirements
Platform BAA Required Required Required; single BAA typically covers all providers under entity
Credentialing Payer-level only (no hospital affiliation) Payer-level per state served Hospital credentialing by proxy may apply; payer credentialing per plan
Informed consent Per patient-state statute Per patient-state statute for each state served Centralized consent template differentiated by state
Billing/coding Provider NPI Provider NPI; confirm payer contracts per state Group NPI + individual NPIs; taxonomy codes critical
Prescribing compliance DEA registration at provider address DEA registration required in each state of practice Each prescribing provider holds individual DEA registration
Malpractice coverage Confirm telehealth endorsement with carrier Confirm coverage extends to all states of practice Group policy must enumerate telehealth and all covered states

For the malpractice dimension in detail, telehealth malpractice and liability covers the carrier, policy, and case-law landscape.

Providers building mental health-specific programs will find additional clinical and regulatory context at mental health telehealth. Those designing services for rural populations should consult telehealth for rural communities for the specific access, broadband, and reimbursement dynamics that apply.

References