Telehealth: What It Is and Why It Matters

Telehealth is the delivery of health care services, education, and health information through telecommunications technology — covering everything from a video visit with a primary care physician to a dermatologist reviewing a photograph submitted hours earlier. The term is broad by design, and that breadth is precisely what makes it contested in policy, billing, and clinical practice. This reference covers the core definition, how the system is structured, where confusion reliably arises, and what the regulatory architecture actually requires.

• What qualifies and what does not
• Primary applications and contexts
• How this connects to the broader framework
• Scope and definition
• Why this matters operationally
• What the system includes
• Core moving parts
• Where the public gets confused

What qualifies and what does not

Not every app with a health-related function is telehealth, and not every telehealth encounter is reimbursable under the same rules. The federal government draws a functional distinction between telehealth services (clinical encounters conducted via technology) and health information technology (software that stores or transmits health data without a direct clinical interaction).

A synchronous video visit between a patient and a licensed clinician qualifies. An automated symptom checker that routes patients to general information does not — at least not under the clinical definitions used by the Centers for Medicare & Medicaid Services (CMS) and the Health Resources & Services Administration (HRSA). The types and modalities of telehealth that actually count for reimbursement purposes fall into three broad categories: live video (synchronous), store-and-forward (asynchronous transmission of clinical data), and remote patient monitoring (RPM), which involves continuous or periodic collection of physiological data outside a clinical setting.

What definitively does not qualify: phone calls conducted without video in most Medicare contexts (with exceptions carved out during the COVID-19 public health emergency), consumer wellness apps without a supervising clinician, and general health education content — no matter how medically accurate.

Primary applications and contexts

The clinical applications of telehealth are not evenly distributed. Mental health services represent the single largest category of telehealth utilization in the United States by volume, a pattern that became entrenched after 2020 and has remained stable as clinicians and patients both identified behavioral health as particularly well-suited to video delivery. The American Psychological Association has reported that the majority of psychologists shifted at least a portion of their practice to telehealth after the public health emergency began.

Beyond behavioral health, the highest-volume applications include dermatology (where store-and-forward has been standard practice for decades), chronic disease management for conditions like hypertension and diabetes, post-surgical follow-up, primary care triage, and specialty consultations in neurology and cardiology. Rural communities represent a distinct and structurally important use case — patients living in Health Professional Shortage Areas (HPSAs), as designated by HRSA, often face drive times exceeding 60 miles to the nearest specialist.

Telehealth also operates in institutional contexts that consumers rarely see: hospital-to-hospital specialist consultations (tele-ICU is one well-documented application), school-based health programs, correctional health care, and occupational health services delivered to remote worksites.

How this connects to the broader framework

Telehealth does not exist as a self-contained system. It operates inside — and is shaped by — a layered regulatory framework involving federal statute, state medical practice acts, payer contracts, and technology standards. The interplay between these layers is where most operational complexity lives.

This site is part of the Authority Network America reference ecosystem (authoritynetworkamerica.com), which maintains reference-grade properties across health, legal, and financial topics. Within that network, this property focuses specifically on the telehealth domain — spanning over 116 published reference pages covering everything from HIPAA compliance requirements and state licensure compacts to reimbursement rates and clinical workflow design. Readers looking for a structured entry point into the regulatory side of the field will find federal telehealth policy and regulation a natural next step after this overview.

The governing statute for most federal telehealth coverage questions is Title XVIII of the Social Security Act, which defines Medicare coverage, and the telehealth-specific provisions at 42 U.S.C. § 1395m(m). The DEA's rules on prescribing via telemedicine — particularly for controlled substances — operate under the Controlled Substances Act and the Ryan Haight Online Pharmacy Consumer Protection Act of 2008, a separate and often misunderstood layer of the framework.

Scope and definition

The Health Resources & Services Administration defines telehealth as "the use of electronic information and telecommunications technologies to support long-distance clinical health care, patient and professional health-related education, public health and health administration" (HRSA Telehealth Programs). The World Health Organization's framing is broader still, encompassing health system strengthening and cross-border information exchange.

CMS, for reimbursement purposes, uses a narrower operational definition anchored to eligible practitioners, covered services, and originating site requirements — the location where the patient physically sits at the time of the encounter. These definitions are not interchangeable. An interaction that qualifies as telehealth under HRSA's public health framing may not qualify for a Medicare telehealth billing code under CMS rules.

The frequently asked questions resource on this site maps the most common definitional confusions, including the distinction between telehealth and telemedicine — a difference that is largely semantic in clinical use but occasionally carries regulatory weight depending on the state.

Why this matters operationally

The stakes of definition and classification are not academic. A clinical encounter miscategorized for billing purposes creates compliance exposure under the False Claims Act — a federal statute that imposes penalties of up to $27,894 per false claim (as adjusted for inflation; see DOJ Civil Division FCA information). A provider practicing across state lines without complying with the applicable state medical practice act may face licensure board action, malpractice liability exposure, or both.

Telehealth prescribing rules carry their own distinct risk profile. The Ryan Haight Act requires, with narrow exceptions, an in-person medical evaluation before a controlled substance can be prescribed via telemedicine. DEA special registrations for telemedicine prescribing of controlled substances — proposed in 2023 and subject to extended comment and revision — represent one of the most actively evolving areas of telehealth compliance as of 2024.

For patients, the operational stakes look different but are equally real. Whether a telehealth visit is covered by insurance, whether a prescription written by a remote clinician is valid in the patient's state, and whether the platform being used meets HIPAA security requirements — these are not fine-print concerns. They are the difference between a functioning clinical encounter and an expensive, legally murky transaction.

What the system includes

Telehealth as a functional system comprises five distinct layers:

1. Clinical interaction layer — The actual encounter between patient and provider, conducted via video, audio, asynchronous message, or data transmission.

2. Technology platform layer — The software and hardware infrastructure enabling the interaction. Telehealth technology platforms range from large enterprise systems integrated with electronic health records (Epic, Cerner) to direct-to-consumer platforms (Teladoc, MDLive, Amazon Clinic). HIPAA requires that any platform handling protected health information operate under a Business Associate Agreement with the covered entity.

3. Regulatory and licensure layer — State medical practice acts, interstate licensure compacts (including the Interstate Medical Licensure Compact covering 39 jurisdictions as of 2024), DEA registration, and CMS conditions of participation.

4. Reimbursement layer — Medicare Part B telehealth billing, Medicaid coverage (which varies by all 50 states and the District of Columbia), and private payer policies, which are governed by state parity laws in 43 states as of 2023 (CCHP Telehealth Policy Finder).

5. Patient access layer — Broadband connectivity, device availability, digital literacy, and language access — the non-clinical factors that determine whether the first four layers actually reach the patient.

Core moving parts

The mechanism of a telehealth encounter — from scheduling to clinical documentation — involves a checklist of requirements that varies by payer, modality, and state:

• Verification that the provider holds an active license in the state where the patient is physically located at the time of the visit
• Informed consent documented in the patient record, as required by most state boards and payer contracts (telehealth informed consent requirements)
• Confirmation that the selected modality (video vs. audio-only) is eligible for reimbursement under the applicable payer's coverage rules
• Documentation of the originating site if Medicare billing is involved
• Completion of any mandatory prescribing safeguards if controlled substances are involved
• Transmission of clinical notes to the patient's primary care record, as required under information blocking provisions of the 21st Century Cures Act

The comparison of telehealth vs. in-person care on this site addresses the clinical and logistical thresholds that determine which setting is appropriate — a question that turns out to be more nuanced than the binary framing suggests.

Where the public gets confused

Three misconceptions appear with enough regularity that they deserve direct correction.

Misconception 1: Telehealth means video only. Store-and-forward consultations — a dermatologist reviewing photographs submitted by a referring physician — have been standard clinical practice for decades and involve no real-time interaction at all. Remote patient monitoring involves no video component whatsoever.

Misconception 2: A prescription written via telehealth is automatically valid anywhere. Prescribing authority is determined by the practitioner's license in the patient's state at the time of the encounter, the drug schedule, and — for Schedule II–V controlled substances — compliance with Ryan Haight Act requirements. A prescription written by an out-of-state, unlicensed provider is not a valid prescription regardless of the platform used to generate it.

Misconception 3: Telehealth eliminates geography as a variable. Broadband access remains uneven. The Federal Communications Commission's 2024 Broadband Data Collection identified over 14 million American locations lacking access to broadband at the FCC's minimum threshold of 25 Mbps download / 3 Mbps upload (FCC Broadband Map). For patients in those areas, the promise of telehealth is real but contingent on infrastructure that has not yet arrived. The telehealth and broadband connectivity reference on this site covers that gap in detail.

The system works when all five layers — clinical, technology, regulatory, reimbursement, and access — are functional simultaneously. When any one layer fails, the encounter either does not happen or happens in a way that creates downstream legal, clinical, or financial problems. That is the fundamental operational tension telehealth continues to navigate.