Telehealth Platform Types and Technologies

The infrastructure underneath a telehealth visit is more varied — and more consequential — than most patients realize. Different platform types handle different clinical tasks, operate under different technical standards, and carry different implications for privacy, reimbursement, and care quality. Mapping those distinctions helps clinicians choose appropriate tools and helps patients understand what they're actually engaging with when a provider says "just log in to our portal."

Definition and scope

A telehealth platform is the technical system that mediates a clinical encounter or health management activity conducted at a distance. That definition covers more ground than a simple video call. According to the Health Resources and Services Administration (HRSA), telehealth encompasses synchronous live interactions, asynchronous data exchange, and remote monitoring — each of which relies on a distinct class of technology.

The full landscape of telehealth types and modalities breaks down into three primary delivery modes:

1. Synchronous platforms — real-time, two-way audio-video communication between patient and provider
2. Asynchronous platforms — store-and-forward systems that transmit clinical information (images, video clips, patient histories) for review outside of real time
3. Remote patient monitoring (RPM) platforms — continuous or periodic data collection from devices the patient uses between clinical encounters

A fourth category, mobile health (mHealth) applications, overlaps with all three. Some mHealth tools are clinical-grade and regulated by the FDA; others are consumer wellness products that fall outside FDA oversight entirely. The FDA's Digital Health Center of Excellence maintains the distinction between software as a medical device (SaMD) and general wellness apps — a line that matters enormously for liability and HIPAA compliance.

How it works

Synchronous video platforms operate much like a secured video conferencing system, but with additional requirements layered on top. To qualify as HIPAA-compliant, a platform must support end-to-end encryption, maintain audit logs, and execute a Business Associate Agreement (BAA) with covered entities — requirements outlined in 45 CFR Part 164. Commercial platforms like Zoom, Teams, and FaceTime do not satisfy these requirements in their standard consumer configurations, though enterprise versions with BAA agreements can be configured for clinical use.

Store-and-forward telehealth works on a fundamentally different timeline. A dermatologist reviewing photographs submitted 18 hours earlier, or a radiologist interpreting images from a clinic in a different time zone, is practicing asynchronous care. The platform captures, encrypts, and routes structured clinical data — often with metadata tagging for specialty-specific workflow queues. This approach is particularly well-established in dermatology, ophthalmology, and radiology.

Remote patient monitoring platforms sit at the intersection of hardware and software. A patient with heart failure might wear a device that transmits daily weight, blood pressure readings, and heart rhythm data to a cloud dashboard monitored by a care team. CMS recognizes RPM under CPT codes 99453, 99454, 99457, and 99458, with coverage contingent on a minimum of 16 days of device data per 30-day period (CMS Medicare Physician Fee Schedule). The clinical workflows around these platforms are meaningfully different from video visit workflows — a distinction explored in telehealth clinical workflows.

Wearable health devices often feed into RPM platforms but don't always. Consumer wearables — smartwatches, fitness trackers — generate data that may or may not be integrated into a clinical system, depending on the provider's infrastructure and the device's regulatory classification.

Common scenarios

The platform type tends to follow the clinical use case with reasonable predictability:

• Primary care follow-ups and behavioral health visits almost exclusively use synchronous video platforms, since the encounter depends on real-time observation and dialogue. Mental health telehealth has particularly high synchronous utilization — audio-only visits are also common and reimbursable under Medicare for many behavioral health services.
• Dermatology consults lean heavily on store-and-forward, where a referring provider photographs a skin lesion and routes it to a dermatologist for review. Telehealth for dermatology often combines this with a subsequent synchronous visit only when findings warrant it.
• Chronic disease management — diabetes, hypertension, COPD — increasingly layers RPM data collection over periodic video check-ins. Chronic disease telehealth programs using this hybrid approach have shown measurable reductions in hospitalization rates in peer-reviewed literature published in journals including JAMA and Annals of Internal Medicine.
• Rural and underserved settings often rely on hub-and-spoke models where a rural clinic (the "spoke") connects patients to specialists at a larger hospital (the "hub") via dedicated synchronous infrastructure — a model central to telehealth for rural communities.

Decision boundaries

Choosing among platform types isn't purely a technology question. Reimbursement rules, state licensure requirements, and clinical appropriateness all constrain the decision space.

Reimbursement varies significantly by modality. Medicare's coverage rules for synchronous video differ from RPM rules and from audio-only rules. Medicare telehealth coverage and telehealth billing and coding are the operational touchstones here — a platform that doesn't generate the right documentation outputs will create billing failures downstream regardless of clinical quality.

Connectivity is a real constraint, not a theoretical one. Synchronous high-definition video requires stable broadband — the FCC defines broadband as a minimum of 25 Mbps download / 3 Mbps upload — and a meaningful portion of rural households fall below that threshold. Telehealth broadband and connectivity examines this gap in structural terms. When bandwidth is unreliable, asynchronous platforms or audio-only synchronous options may be the clinically responsible choice.

Clinical suitability sets hard limits. No synchronous video platform substitutes for an in-person physical examination when hands-on assessment is required. Telehealth vs in-person care maps those limits carefully. The platform is the medium; the clinical judgment about when that medium is appropriate remains the provider's responsibility — and, increasingly, a matter addressed in telehealth malpractice and liability case law.