Telehealth Platform Types and Technologies

Telehealth encompasses a broad and technically diverse set of platform categories, each distinguished by delivery mode, data handling method, and regulatory classification. Understanding these distinctions matters because platform type directly determines applicable HIPAA compliance requirements, reimbursement eligibility under Medicare and Medicaid, and the clinical scenarios each technology can legally and safely support. This page maps the major platform types, their underlying mechanisms, representative use cases, and the structural boundaries that separate one category from another.

Definition and scope

The Health Resources and Services Administration (HRSA) 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). Within that broad definition, the Centers for Medicare & Medicaid Services (CMS) distinguishes four operational modalities in its billing and coverage guidance: synchronous interactive audio-video, asynchronous store-and-forward, remote patient monitoring (RPM), and audio-only communication.

Platform classifications are not purely technical — they carry regulatory weight. The Office for Civil Rights (OCR) within HHS enforces HIPAA against covered entities that transmit individually identifiable health information through any telehealth platform, regardless of modality. The Federal Communications Commission (FCC) further defines broadband connectivity thresholds — a minimum of 25 Mbps download / 3 Mbps upload — relevant to platform viability in underserved areas (FCC Broadband Speed Benchmark, 2015).

Platform type also shapes telehealth prescribing laws and limits and determines which provider-patient interactions qualify for specific CPT billing codes under CMS guidance.

How it works

Telehealth platforms operate through four structurally distinct delivery mechanisms:

1. Synchronous video (live audio-video): A real-time, two-way audiovisual connection between a provider and patient. Platforms must meet HIPAA's Technical Safeguard requirements under 45 CFR §164.312, including end-to-end encryption and access controls. Video conferencing software used for this purpose must operate under a Business Associate Agreement (BAA) with the covered entity.

2. Asynchronous store-and-forward: Clinical data — images, video clips, diagnostic files, or completed questionnaires — are captured at one point in time and transmitted to a reviewing clinician at a later time. No real-time interaction occurs. This model is dominant in telehealth dermatology services and teleradiology services, where high-resolution image review is the primary clinical task. CMS recognizes store-and-forward under specific FQHC and RHC billing exceptions (see store-and-forward telehealth).

3. Remote patient monitoring (RPM): Connected devices — blood pressure cuffs, glucometers, pulse oximeters, cardiac monitors — collect physiological data from patients outside clinical settings and transmit it to provider systems. CMS reimburses RPM under CPT codes 99453, 99454, 99457, and 99458, subject to minimum daily measurement requirements (CPT 99454 requires at least 16 days of data per 30-day period). See remote patient monitoring overview for full billing structure.

4. Audio-only (telephone): A voice-only interaction without video. CMS permitted expanded audio-only coverage under COVID-19 emergency waivers; the status of permanent coverage for audio-only telehealth is governed by ongoing rulemaking. Audio-only is the lowest-bandwidth modality and is critical for patients facing connectivity barriers discussed in telehealth broadband and connectivity requirements.

Synchronous vs. asynchronous — key distinction: Synchronous platforms require both parties to be present simultaneously and generate real-time protected health information (PHI) data streams. Asynchronous platforms generate stored PHI that is transmitted and accessed on a time-delayed basis, creating a different risk profile under HIPAA's Security Rule and a different evidentiary record for malpractice purposes. Full comparison is covered in synchronous vs asynchronous telehealth.

Common scenarios

Platform type maps predictably onto clinical specialty and care setting:

• Synchronous video supports primary care follow-ups, behavioral health therapy sessions, and urgent care triage. CMS covers synchronous telehealth visits at originating sites defined under 42 CFR §410.78.
• Store-and-forward is used in teledermatology (image review for lesion assessment), teleophthalmology (retinal image grading), and teleradiology. In each case, a specialist reviews transmitted imaging without a live encounter.
• RPM is most prevalent in telehealth chronic disease management, particularly telehealth diabetes management and telehealth cardiology and remote monitoring. RPM requires patient enrollment, device provisioning, and ongoing clinical review workflows.
• Mobile health (mHealth) applications — distinct from RPM — are software-based tools on consumer devices. The FDA classifies certain mHealth apps as Software as a Medical Device (SaMD) under 21 CFR Part 880, requiring 510(k) clearance or De Novo classification when the app performs diagnostic functions (FDA Digital Health Center of Excellence).
• Audio-only is used when patients lack video-capable devices or reliable broadband, common in rural and low-income populations served by federally qualified health center telehealth programs.

Decision boundaries

Several structural criteria determine which platform type applies to a given clinical situation:

• Real-time requirement: If the clinical decision requires immediate bidirectional communication, synchronous video or audio-only applies. If the decision can wait for expert review, store-and-forward is appropriate.
• Physiological data collection: If the purpose is ongoing monitoring of biometric parameters, RPM applies, and the platform must comply with CPT billing rules requiring a minimum number of monitoring days and documented clinical review.
• FDA jurisdiction: If the platform performs clinical decision support that is not purely administrative, the FDA's 2019 Clinical Decision Support guidance and the 21st Century Cures Act framework (Public Law 114-255) determine whether regulatory oversight applies.
• HIPAA covered entity status: All platform types transmit PHI if they involve identified patient data, but the security controls required differ by transmission method. Asynchronous platforms storing data at rest must implement 45 CFR §164.312(a)(2)(iv) encryption for stored PHI in addition to transmission encryption.
• Prescribing eligibility: Not all platform types support prescribing. DEA telehealth prescribing rules, particularly for controlled substances, impose encounter-type requirements that audio-only interactions may not satisfy. See DEA telemedicine prescribing regulations.
• State law variability: State telehealth laws and policies impose independent requirements on platform standards, informed consent mechanisms, and permissible modalities for specific service types that operate in parallel with federal rules.

References

• HRSA Telehealth Programs — Definition and Program Overview
• CMS Telehealth Services — Medicare Benefit Policy Manual, Chapter 15
• HHS Office for Civil Rights — HIPAA and Telehealth
• FDA Digital Health Center of Excellence — Software as a Medical Device
• FCC Broadband Speed Benchmark
• 45 CFR §164.312 — HIPAA Security Rule Technical Safeguards (eCFR)
• 21st Century Cures Act, Public Law 114-255 (Congress.gov)
• American Telemedicine Association — Telehealth Policy and Standards Resources