Telehealth vs. Telemedicine: Definitions and Distinctions

The terms telehealth and telemedicine appear interchangeably in policy documents, insurance contracts, and clinical literature, yet federal agencies and standards bodies assign them distinct meanings with meaningful operational consequences. Understanding the boundary between the two concepts affects how providers bill for services, how regulators classify programs, and how patients access care across state lines. This page maps the official definitions, structural differences, and practical decision points that separate telehealth from telemedicine in the United States regulatory landscape.

Definition and scope

The Health Resources and Services Administration (HRSA), a division of the U.S. Department of Health and Human Services, defines telemedicine as the use of electronic information and telecommunications technologies to provide clinical health care services at a distance (HRSA Telehealth Programs). Telemedicine is narrower in scope: it refers specifically to remote clinical services — diagnosis, treatment, prescription, and patient monitoring — delivered by a licensed clinician to a patient.

Telehealth, by contrast, is the broader category. HRSA and the Centers for Medicare and Medicaid Services (CMS) use telehealth to encompass both clinical and non-clinical services, including health education, administrative functions, provider training, and public health activities (CMS Telehealth). The World Health Organization (WHO) similarly frames telehealth as the umbrella term, with telemedicine representing one subset of health services delivered through technology (WHO Global Observatory for eHealth).

A useful structural summary:

1. Telemedicine — remote clinical care delivered by a licensed clinician (e.g., physician, nurse practitioner, physician assistant)
2. Telehealth — all technology-mediated health-related activities, clinical and non-clinical
3. mHealth — a further subset involving mobile device applications and consumer-facing wellness tools
4. Remote Patient Monitoring (RPM) — a clinical subspecialty within telehealth focused on continuous physiologic data collection outside a clinical setting

The Telehealth Glossary of Terms on this resource provides expanded definitions for mHealth, RPM, store-and-forward, and synchronous/asynchronous modalities.

How it works

Both telehealth and telemedicine rely on the same underlying technology stack — video conferencing, secure messaging platforms, electronic health records, and broadband infrastructure — but differ in the regulatory obligations triggered by each use case.

Telemedicine encounters require that the delivering clinician hold a valid license in the state where the patient is physically located at the time of the visit (Federation of State Medical Boards, FSMB). This licensure requirement applies regardless of where the clinician is physically located. The Telehealth Licensure and Interstate Practice framework, including the Interstate Medical Licensure Compact, was developed specifically to address multistate clinical practice barriers.

Non-clinical telehealth activities — continuing medical education delivered via webinar, population health dashboards, or administrative coordination between health system sites — do not trigger the same licensure requirements because no direct patient care relationship is formed.

HIPAA applicability follows the clinical/non-clinical divide. The HIPAA Privacy Rule and Security Rule (45 CFR Parts 160 and 164) apply to covered entities and business associates handling protected health information (PHI). Telemedicine encounters generate PHI by definition; non-clinical telehealth activities may or may not, depending on whether individually identifiable health data is processed. The Telehealth HIPAA Compliance Requirements page covers the specific technical safeguards required under the Security Rule.

Delivery modalities within telemedicine include:

1. Synchronous — real-time audio/video interaction between clinician and patient
2. Asynchronous (store-and-forward) — transmission of clinical data (images, lab results, patient history) reviewed by a clinician at a later time
3. Remote Patient Monitoring — collection of physiologic data through wearable or home-based devices, transmitted to the treating clinician

The Synchronous vs. Asynchronous Telehealth page documents how payer coverage differs across these modalities, and Store-and-Forward Telehealth covers specialty-specific applications such as teleradiology and teledermatology.

Common scenarios

The practical distinction between telehealth and telemedicine becomes clearest through specific clinical and operational scenarios.

Scenario 1 — Telemedicine: A patient in rural Kansas connects via video to a board-certified internist licensed in Kansas. The physician reviews symptoms, orders laboratory tests, and prescribes a non-controlled medication. This is a telemedicine encounter: a licensed clinician delivers clinical services to a patient. CMS reimburses this under Medicare Part B using specific Current Procedural Terminology (CPT) codes (CMS Medicare Telemedicine Services).

Scenario 2 — Non-clinical telehealth: A hospital system broadcasts a live webinar on diabetes self-management to patients across 12 states. No physician–patient relationship is created; no diagnosis or prescription is issued. This is a telehealth activity, not a telemedicine encounter, and does not trigger licensure requirements in each broadcast state.

Scenario 3 — RPM within telemedicine: A cardiologist implants a cardiac monitor and the device transmits electrocardiographic data nightly to the cardiologist's office. The cardiologist reviews flagged readings and adjusts medication. Because clinical judgment is applied and a treatment decision is made, this falls within telemedicine despite the asynchronous data pathway.

Scenario 4 — mHealth with no clinical component: A consumer downloads a meditation application and logs daily mood scores. No clinician reviews the data; no clinical decision is made. This is a mHealth/telehealth activity with no telemedicine dimension and limited HIPAA exposure unless the app is sponsored by a covered entity.

Decision boundaries

Determining whether a specific program constitutes telemedicine (and therefore triggers licensing, prescribing, malpractice, and reimbursement requirements) involves four discrete classification questions:

1. Is a licensed clinician involved in a direct patient care relationship? If yes, the activity is telemedicine regardless of modality.
2. Is protected health information generated, stored, or transmitted? If yes, HIPAA obligations attach under 45 CFR Parts 160 and 164.
3. Does the interaction result in a diagnosis, treatment plan, or prescription? If yes, state medical practice acts and, where applicable, DEA prescribing regulations under 21 U.S.C. § 829 apply. See DEA Telemedicine Prescribing Regulations for current scheduling requirements.
4. Does the activity cross state lines? If yes, the clinician's licensure must be valid in the patient's state, or the encounter must qualify under a recognized interstate mechanism such as the Interstate Medical Licensure Compact.

Activities that fail to meet criterion 1 — such as health coaching by non-licensed personnel, patient education content, or administrative scheduling — remain within the broader telehealth category and do not carry the same regulatory burden.

Payer classification follows similar logic. CMS distinguishes between Medicare-covered telehealth services (which require a qualifying originating site and a covered service type) and separately reimbursed RPM codes (CPT 99453, 99454, 99457, 99458), which have distinct enrollment and documentation requirements (CMS Telehealth Coverage and Billing).

State-level definitions introduce additional variation. The Telehealth Regulatory Framework United States page documents how state medical boards, insurance commissioners, and Medicaid agencies apply their own definitions — some of which diverge from the HRSA and CMS frameworks. As of 2023, all 50 states and the District of Columbia had enacted at least some form of telehealth coverage policy, though the scope and modality requirements differ materially across jurisdictions (National Conference of State Legislatures, Telehealth Policy).

References

• Health Resources and Services Administration (HRSA) — Telehealth Programs
• Centers for Medicare and Medicaid Services (CMS) — Telehealth
• CMS Medicare Telehealth Codes
• Federation of State Medical Boards (FSMB) — Telemedicine Policy
• World Health Organization — Global Observatory for eHealth
• National Conference of State Legislatures — Telehealth Policy
• U.S. Department of Health and Human Services — HIPAA for Professionals, 45 CFR Parts 160 and 164
• Drug Enforcement Administration — Telemedicine Regulations, 21 U.S.C. § 829