This is engineering guidance, not legal advice. Confirm specifics with qualified counsel.

Why this matters

If you are a founder, product manager, or hospital IT lead scoping a healthcare video product, the first trap is vocabulary. Investors say "digital health," regulators write "telehealth," clinicians say "telemedicine," and vendors say "virtual care" — often about the same product. Each word maps to a different scope, a different regulator, and a different payment rule, so a mislabeled product gets mis-scoped budgets and mis-scoped compliance. This article gives you the working definitions from the agencies that own them, and shows how each term changes what you build. It is the vocabulary the rest of this course assumes.

The short version: three nested circles

Picture three circles, one inside the other.

The innermost circle is telemedicine: a doctor (or nurse, or therapist) providing clinical care — diagnosis, treatment, prescribing, monitoring of a specific patient — across a distance, using telecommunications. The World Health Organization defines it as "the delivery of health care services, where distance is a critical factor, by all health care professionals using information and communication technologies" for diagnosis, treatment, and prevention [7]. If a clinician is making decisions about a particular patient remotely, that is telemedicine.

The middle circle is telehealth. The Health Resources and Services Administration (HRSA), the agency inside the US Department of Health and Human Services (HHS) that owns the federal definition, describes telehealth as "the use of electronic information and telecommunications technologies to support long-distance clinical health care, patient and professional health-related education, health administration, and public health" [1]. Notice what got added: education, administration, public health. The Office of the National Coordinator for Health IT (ONC) draws the line explicitly: telemedicine refers specifically to remote clinical services, while telehealth also covers remote non-clinical services such as provider training, administrative meetings, and continuing medical education [2].

The outermost circle is digital health. The US Food and Drug Administration (FDA) uses it as the umbrella for everything: mobile health (mHealth), health information technology, wearable devices, telehealth and telemedicine, and personalized medicine [3]. A meditation app with no clinician anywhere near it is digital health. So is an AI model reading chest X-rays. Digital health does not imply a doctor, a patient relationship, or a billable visit — it implies only that technology touches health.

Nested diagram: telemedicine inside telehealth inside digital health, with sibling terms in each ring Figure 1. The three terms nest. Everything in an inner circle belongs to the outer ones, but not the reverse.

A useful test: a video consult with a dermatologist is telemedicine, telehealth, and digital health at once. A webinar training rural nurses is telehealth and digital health, but not telemedicine. A step-counting watch with no clinical loop is only digital health.

Telemedicine: the clinical core

Telemedicine is the word with the strongest claim to precision, because it is anchored to the clinical act. Medicaid's program guidance frames it as care that "seeks to improve a patient's health by permitting two-way, real-time interactive communication between the patient and the physician or practitioner at the distant site" [4]. Two things in that sentence carry weight for a product team.

First, the patient and the practitioner are identified people in a care relationship. That relationship is what triggers healthcare law. The federal privacy law for health data, the Health Insurance Portability and Accountability Act (HIPAA), protects "protected health information" (PHI) — individually identifiable health information held or transmitted by a covered entity or its business associate, in any form (45 CFR §160.103) [5]. The moment your video call carries an identifiable patient's health information for a provider, PHI is on the wire, and the HIPAA Privacy and Security Rules apply to how you transmit, store, and log it.

Second, "real-time" is one mode, not the definition. Telemedicine spans three delivery modes with very different architectures, which we cover next.

One more anchor worth knowing: the word "telemedicine" also appears in federal prescribing law. The Ryan Haight Act of 2008 (21 U.S.C. §829(e)) generally requires an in-person medical evaluation before a practitioner may prescribe controlled substances, and defines the telemedicine exceptions to that requirement [6]. So in prescribing law, "practice of telemedicine" is a defined legal term with its own conditions — another reason precision pays.

Telehealth: the word the money uses

Telehealth is the term US statute and reimbursement policy actually operate on. Medicare — the federal insurance program for Americans 65 and older, and the de facto standard-setter for US payment rules — pays for a defined list of "telehealth services" under §1834(m) of the Social Security Act, with rules about where the patient is (the "originating site"), what technology counts ("interactive telecommunications system"), and which practitioners may bill [4][8].

This is where dates start to matter. The pandemic-era expansions of Medicare telehealth — the patient's home as an eligible originating site for non-behavioral care, no geographic restriction, audio-only options, the expanded practitioner list — are not all permanent. As of this writing, recent legislation extends most of these flexibilities through December 31, 2027 [8]. A narrower set is permanent: behavioral and mental telehealth in the patient's home, with no geographic restriction, including audio-only delivery [8]. The lesson for a product team is not the specific dates — it is that "can we bill this visit?" is a question about the word telehealth as defined in statute, re-answered every year. Article 1.8 on reimbursement walks through how these rules shape product architecture.

Telehealth is also the broader operational word inside health systems: a hospital's "telehealth program" typically includes scheduling, triage, e-consults between clinicians, patient education, and remote monitoring — the full platform anatomy, not just the video visit.

Digital health: the investor's word, the FDA's category

Digital health is the broadest and loosest term — and the one with the most money attached. Analyst estimates put the global telehealth market alone around $190–220 billion in 2026, with the US telehealth services industry near $36 billion [9]; "digital health" as a funding category is larger still. When you read a market report or a pitch deck, you are almost always reading the digital-health framing.

The FDA's interest is narrower and sharper: somewhere inside digital health sits the line where software becomes a medical device. Software intended to diagnose, treat, or prevent disease can be regulated as Software as a Medical Device (SaMD), with premarket obligations; software that merely supports a clinician's decision may fall under the Clinical Decision Support exemptions [3]. A telemedicine video platform by itself is generally not a medical device — but bolt an AI feature onto it that diagnoses, and you may have crossed the FDA line. We treat that boundary in detail in the AI block of this course.

The sibling words you will meet all live in this outer circle:

mHealth (mobile health) is health practice supported by mobile devices — apps, SMS reminders, phone-based sensors. Health IT is the records-and-plumbing layer: electronic health records (EHRs), interoperability, e-prescribing. Virtual care is a marketing-friendly synonym for telehealth, common in hospital branding; it has no distinct regulatory meaning. Connected care usually means devices plus care coordination. Digital therapeutics are software products that themselves deliver a clinical intervention — and those generally are regulated products. None of these words changes your legal duties; the data and the clinical relationship do.

Three delivery modes: synchronous, asynchronous, RPM

Whatever the label on the box, telemedicine ships in three modes, and the mode — not the word — sets your latency budget, data flow, and cost.

Synchronous means live, two-way interaction: a video consult, an audio-only visit. The patient and clinician are present at the same time. Technically this is the realm of real-time video (WebRTC), where one-way latency above roughly 300–500 ms makes conversation awkward — milliseconds matter.

Asynchronous, also called store-and-forward, means data is captured now and reviewed later: a dermatology photo uploaded today, read by a specialist tomorrow [2]. No live session, so latency is measured in hours — but integrity, audit trails, and queue management dominate the design.

Remote patient monitoring (RPM) is a stream of device readings — weight, blood pressure, glucose — transmitted to a care team that watches trends and intervenes on anomalies [2]. It is asynchronous in rhythm but continuous in volume, with its own Medicare billing codes and device-integration burden.

Three columns comparing synchronous, asynchronous, and RPM telemedicine by timing, example, and design driver Figure 2. Three delivery modes, three architectures. The compliance umbrella is shared; the engineering is not.

These three modes recur through the whole course; article 1.4 dedicates itself to them.

Why the words matter: each one summons a different rulebook

Here is the practical payoff. The terms are not interchangeable because each is load-bearing in a different body of rules.

Term Owned by What it covers What it triggers for your product
Telemedicine WHO, state medical boards, DEA (prescribing) Remote clinical care of a patient Licensure, standard-of-care, prescribing rules (Ryan Haight Act)
Telehealth HRSA/HHS, CMS, state Medicaid Clinical + non-clinical remote health services Medicare/Medicaid billing eligibility, originating-site and modality rules
Digital health FDA, investors All health-touching technology Possible device (SaMD) obligations if you diagnose/treat
mHealth WHO, FDA (subset) Mobile-supported health practice App-store health policies; HIPAA only if PHI + covered relationship
Virtual care Marketing Synonym of telehealth Nothing by itself — check the underlying service
RPM CMS (billing codes), FDA (devices) Device data streamed to a care team Device classification, RPM billing rules, data-retention design

Three rule-mapping facts deserve emphasis, because teams get them wrong expensively.

HIPAA follows the data, not the label. HIPAA applies when PHI is created, received, or transmitted by a covered entity (a provider, plan, or clearinghouse) or its business associate — your platform, if it serves providers (45 CFR §160.103) [5]. Calling your product "a wellness app" does not exempt you if a clinician uses it for patient care. The reverse is also true: a direct-to-consumer wellness app with no covered entity in the loop may sit outside HIPAA — but it is not in a law-free zone. The Federal Trade Commission's Health Breach Notification Rule (16 CFR Part 318, strengthened in 2024) covers exactly those apps [10]. HIPAA in plain English unpacks this, including why "encrypted" and "compliant" are different claims and why every vendor in your stack needs a signed Business Associate Agreement.

Reimbursement reads the statute, not your marketing. Medicare pays for "telehealth services" as defined in §1834(m); whether you call the product virtual care or connected care changes nothing about the claim form. The current flexibility window runs to December 31, 2027 for most services [8] — and your roadmap should carry that date.

Prescribing has its own clock. Remote prescribing of controlled substances runs on Drug Enforcement Administration (DEA) rules. The current temporary flexibilities — which let DEA-registered practitioners prescribe Schedule II–V medications via audio-video telemedicine without a prior in-person exam — were extended by the DEA's Fourth Temporary Extension rule through December 31, 2026 [6]. More than 7 million controlled-substance prescriptions were issued via telemedicine without a prior in-person visit in 2024 alone [6], so this single date governs a large product category.

Map of triggers to rulebooks: PHI to HIPAA, billing to CMS, prescribing to DEA, diagnosis to FDA SaMD Figure 3. Four rulebooks, four triggers. None of them is triggered by your product's name — each is triggered by what the product does.

A worked example: the date math a prescribing feature lives on

The arithmetic every roadmap in this space should run at least once. Suppose today is June 10, 2026, and you are scoping a telepsychiatry product whose business model depends on remote prescribing under the current DEA flexibilities.

Days until the flexibility expires: June 10 → December 31, 2026 = 20 days (June) + 31 + 31 + 30 + 31 + 30 + 31 = 204 days.

A typical compliant MVP build: ~5 months ≈ 150 days. A pilot with a partner clinic: ~2 months ≈ 60 days. Total: 150 + 60 = 210 days — which is 6 days past the expiry of the rule your business model assumes.

The point is not panic; DEA has extended four times and is finalizing permanent rules. The point is that the schedule of a regulation is a first-class input to your product plan, on the same row as engineering estimates. Teams that treat the label "telemedicine" as decoration discover this in month five. The cost model article shows how compliance scope feeds the budget the same way.

Common mistake: choosing the word by vibe, then inheriting the wrong scope. A team brands its product "digital wellness," skips HIPAA scoping, and later signs its first clinic customer — instantly becoming a business associate with none of the required safeguards, agreements, or audit logging in place. Retrofitting compliance onto a shipped architecture costs multiples of designing it in. Decide what the product does (clinical or not, PHI or not, prescribing or not) on day one, and let the words follow.

What this means when you start building

When you scope a telemedicine app, the vocabulary translates directly into build decisions. "Telemedicine" scope means identity-verified users, consent capture, audit logging, and a HIPAA-eligible infrastructure with BAAs from every vendor that can touch PHI. "Telehealth" scope adds the non-clinical surfaces — education content, scheduling, admin workflows — which carry lighter rules but share the platform. "Digital health" ambitions (an AI triage bot, a diagnostic feature) add the FDA question to your roadmap. And the delivery mode — synchronous, store-and-forward, RPM — decides whether your hard engineering problem is real-time video reliability, queue-and-review workflow, or device-data ingestion at scale. Why telemedicine video is harder than a normal video call takes the synchronous path apart; who is in the room covers the identity and consent layer.

Decision tree of four questions on clinical care, PHI, prescribing, and diagnosis leading to category and rulebook Figure 4. Four questions that classify your product better than any label. Answer them before choosing a name.

Where Fora Soft fits in

Fora Soft has built video software since 2005 — video conferencing, streaming, OTT, surveillance, e-learning, and telemedicine among them — with 239+ shipped projects. In telemedicine work, the requirement comes first: we scope whether a product is clinical telemedicine, broader telehealth, or non-clinical digital health before an architecture line is drawn, because that classification decides the PHI boundary, the BAA list, and the audit surface. Then we build the real-time video layer to clinical reliability standards. That order — compliance scope, then capability — is the discipline this whole section teaches.

What to read next

Call to action

References

  1. HRSA — What is Telehealth? (Office for the Advancement of Telehealth), https://www.hrsa.gov/telehealth/what-is-telehealth — accessed 2026-06-10. Tier 1. Federal definition of telehealth.
  2. ONC / HealthIT.gov — What is telehealth? How is telehealth different from telemedicine? (FAQ), https://www.healthit.gov/faq/what-telehealth-how-telehealth-different-telemedicine — accessed 2026-06-10. Tier 1. Telemedicine = remote clinical services; telehealth includes non-clinical; store-and-forward and RPM definitions.
  3. FDA — What is Digital Health? (Digital Health Center of Excellence), https://www.fda.gov/medical-devices/digital-health-center-excellence/what-digital-health — accessed 2026-06-10. Tier 1. Digital health scope: mHealth, health IT, wearables, telehealth/telemedicine, personalized medicine; SaMD boundary.
  4. Medicaid.gov — Telehealth, https://www.medicaid.gov/medicaid/benefits/telemedicine/index.html — accessed 2026-06-10. Tier 1. Two-way real-time interactive communication framing; state-level definition variance.
  5. 45 CFR §160.103 — definitions of protected health information, covered entity, business associate (HIPAA Administrative Simplification), https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-160/subpart-A/section-160.103 — accessed 2026-06-10. Tier 1.
  6. DEA & HHS — Fourth Temporary Extension of COVID-19 Telemedicine Flexibilities for Prescription of Controlled Medications, Federal Register, 2025-12-31, https://www.federalregister.gov/documents/2025/12/31/2025-24123/fourth-temporary-extension-of-covid-19-telemedicine-flexibilities-for-prescription-of-controlled — flexibilities effective Jan 1 – Dec 31, 2026; 7M+ telemedicine controlled-substance prescriptions in 2024; Ryan Haight Act (21 U.S.C. §829(e)) baseline. Tier 1.
  7. WHO — Telemedicine: Opportunities and Developments in Member States (Global Observatory for eHealth, 2010) — WHO definition of telemedicine. Tier 1.
  8. HHS — Telehealth policy updates, Telehealth.HHS.gov, last updated 2026-02-05, https://telehealth.hhs.gov/providers/telehealth-policy/telehealth-policy-updates — Medicare flexibilities extended through 2027-12-31; permanent behavioral-health provisions; CY 2026 Physician Fee Schedule links. Tier 1.
  9. Fortune Business Insights — Telehealth Market Size Report (2026 estimate ~$219B global), https://www.fortunebusinessinsights.com/industry-reports/telehealth-market-101065; IBISWorld — Telehealth Services in the US (~$36.1B, 2026), https://www.ibisworld.com/united-states/industry/telehealth-services/5775/ — accessed 2026-06-10. Tier 5 (analyst estimates; methodologies differ).
  10. FTC — Health Breach Notification Rule, 16 CFR Part 318 (final rule amendments 2024), https://www.ftc.gov/legal-library/browse/rules/health-breach-notification-rule — accessed 2026-06-10. Tier 1. Covers consumer health apps outside HIPAA.
  11. AHA Market Scan — 5 Key Telehealth Insights (2026-03-10), https://www.aha.org/aha-center-health-innovation-market-scan/2026-03-10-5-key-telehealth-insights — telehealth utilization by specialty (mental health ~28.2%, Dec 2025; primary care 6–7%). Tier 5.

Where lower-tier sources disagreed with rule text — e.g., vendor explainers that treat "telemedicine" and "telehealth" as interchangeable, or imply pandemic-era billing rules are permanent — this article follows the HRSA/ONC definitions and the dated CMS/DEA expiry schedule above.