Block 1. Telemedicine Foundations

1

What Is Telemedicine, Telehealth, and Digital Health — The Words That Get Confused

Telemedicine, telehealth, and digital health are not synonyms. What each term means for HIPAA, reimbursement, and scope in telemedicine app development.

2

Why Telemedicine Video Is Harder Than a Normal Video Call

A dropped Zoom call is annoying; a dropped telehealth visit is a clinical event. The telemedicine video requirements ordinary calls never meet.

3

The Telemedicine Product Landscape: DTC, B2B2C, Hospital, Specialty

The four telemedicine product types — DTC, B2B2C, hospital, specialty — and how each changes your architecture, compliance burden, and integrations.

4

Synchronous, Asynchronous, and Remote Patient Monitoring — Three Products, Three Architectures

Synchronous video, store-and-forward, and remote patient monitoring are three different products. The architectures, billing rules, and costs of each.

5

The Anatomy of a Telemedicine Platform, End to End

The ten subsystems of a telemedicine platform architecture — typical technology, failure modes, and where PHI lives at every hop, app to analytics.

6

Who Is in the Room: Roles, Identity, and Consent

Telemedicine identity verification explained: who may join a visit, patient and provider proofing (NIST IAL/AAL), and the consent layers states require.

7

The Telemedicine Cost Model: What a Platform Actually Costs to Build and Run

What a telemedicine app really costs in 2026: build-team math, CPaaS vs self-host video, compliance line items, and a 5,000-visit worked example.

8

Reimbursement and the Rules That Shape the Product

Telehealth reimbursement rules decide product architecture: Medicare 2026 policy, parity laws, state licensing, and the billing record to capture.