Synchronous vs. Asynchronous Telehealth: Key Differences

Telehealth delivery falls into two structurally distinct modes — synchronous and asynchronous — each with separate technical requirements, clinical applications, reimbursement rules, and regulatory treatment. Understanding the boundary between these modes is essential for clinicians, health systems, payers, and policymakers operating within the US regulatory landscape. This page defines both delivery types, explains how each functions mechanically, identifies the clinical scenarios where each applies, and establishes the decision boundaries that determine when one mode is appropriate versus the other.


Definition and scope

Synchronous telehealth refers to real-time, two-way communication between a patient and a clinician occurring simultaneously over an audio or audio-video connection. Asynchronous telehealth — also called store-and-forward telehealth — refers to the transmission of recorded health information (images, video clips, data, patient history) from one party to another for review and response at a different point in time.

The Centers for Medicare & Medicaid Services (CMS) maintains formal distinctions between these delivery types in its telehealth coverage framework. Under 42 CFR Part 410, Subpart B, CMS defines telehealth services eligible for Medicare reimbursement, and those definitions treat synchronous visits differently from store-and-forward transmissions. The Health Resources and Services Administration (HRSA) similarly separates these modalities in its Telehealth Programs documentation, noting that store-and-forward is distinct from live, interactive services.

A third recognized mode — remote patient monitoring — occupies its own regulatory category under CMS billing codes (CPT codes 99453, 99454, 99457, and 99458), though it shares asynchronous characteristics in that data collected by devices is transmitted and reviewed outside of a live encounter. For classification purposes, RPM is treated separately from both core synchronous and store-and-forward categories.

The telehealth regulatory framework in the United States governs all three modalities through overlapping federal and state authority, with state telehealth laws and policies adding jurisdiction-specific requirements on top of federal baselines.


How it works

Synchronous delivery requires simultaneous presence of both clinician and patient on a shared communication channel. The technical infrastructure typically includes:

  1. A HIPAA-compliant video conferencing or audio platform (45 CFR Part 164 governs security and privacy requirements under HIPAA)
  2. Sufficient broadband connectivity at both endpoints — the Federal Communications Commission (FCC) defines minimum broadband thresholds relevant to telehealth in its Connect America Fund programs
  3. Real-time clinical decision-making during the session
  4. Documentation generated contemporaneously with or immediately following the encounter

The encounter proceeds in a single defined session window. Clinical assessment, history-taking, examination (where feasible), and care planning all occur within that window.

Asynchronous delivery separates the data-capture event from the clinical review event. The functional sequence is:

  1. Patient or referring provider submits structured health data — photographs, recorded video, lab results, or intake questionnaires — through a secure transmission system
  2. Data is stored on a compliant platform pending specialist review
  3. A reviewing clinician evaluates the submission at a later time, which may be hours or days after submission
  4. The reviewing clinician generates a report, diagnosis, or recommendation that is transmitted back to the originating party

Telehealth platform types and technologies vary significantly between these two workflows. Synchronous platforms prioritize low-latency streaming and real-time session management; asynchronous platforms prioritize structured data capture, secure storage, and workflow routing.

HIPAA's Security Rule (45 CFR § 164.312) applies to both modalities, but the specific technical safeguards differ — asynchronous systems must address data-at-rest encryption and access controls over stored clinical media, while synchronous systems must address data-in-transit encryption and session integrity.


Common scenarios

Clinical use cases cluster around each modality based on acuity, specialty workflow, and the necessity of real-time interaction.

Synchronous telehealth is the dominant modality for:

Asynchronous (store-and-forward) telehealth is the primary modality for:

CMS covers store-and-forward telehealth under Medicare for Federal Telemedicine Demonstration Programs in Alaska and Hawaii specifically (per 42 CFR § 410.78). Broader asynchronous coverage under Medicaid varies by state — 26 states and the District of Columbia had explicit Medicaid coverage policies for store-and-forward as of the most recent Center for Connected Health Policy (CCHP) State Telehealth Laws and Reimbursement Policies report.


Decision boundaries

Selecting between synchronous and asynchronous delivery is not solely a clinical decision — it is shaped by regulatory coverage rules, licensure requirements, platform capabilities, and patient circumstances.

Regulatory coverage boundaries

Medicare's primary telehealth benefit under Section 1834(m) of the Social Security Act applies to synchronous audio-video services. Asynchronous services receive narrower and more conditional coverage. Clinicians operating under telehealth Medicare coverage and billing rules must identify the correct HCPCS or CPT billing code for the modality used, as miscoding between synchronous and asynchronous encounters is an auditable compliance risk.

Clinical decision boundaries

The following structured breakdown identifies the primary factors that determine modality appropriateness:

  1. Acuity: High-acuity, time-sensitive conditions (stroke, acute psychiatric crisis, pediatric respiratory distress) require synchronous evaluation. Stable, non-urgent conditions with documentable clinical history may be appropriate for asynchronous review.
  2. Specialty workflow: Specialties relying on interpreted media (radiology, dermatology, pathology) have established asynchronous workflows. Specialties requiring therapeutic interaction (psychiatry, primary care, behavioral health) are structurally synchronous.
  3. Patient access: Patients in areas with limited broadband infrastructure — a documented barrier in rural and underserved communities per FCC Broadband Deployment Reports — may lack the connectivity for reliable synchronous video, making asynchronous or audio-only modalities the accessible alternative.
  4. Licensure jurisdiction: Telehealth licensure and interstate practice rules apply to both modalities. A clinician conducting asynchronous review of a patient's records is typically subject to the licensure requirements of the state where the patient is located, not where the clinician is physically present, under the majority interpretation applied by state medical boards.
  5. Informed consent requirements: Telehealth informed consent standards differ by state and modality. Several states require separate informed consent documentation for store-and-forward services.
  6. Prescribing constraints: Synchronous audio-video encounters are required under DEA telemedicine prescribing regulations for most controlled substance prescriptions issued via telehealth. Asynchronous-only encounters do not satisfy this requirement under the Ryan Haight Online Pharmacy Consumer Protection Act of 2008 (21 U.S.C. § 829).

Hybrid workflows

Health systems increasingly deploy hybrid models in which an asynchronous intake (patient-submitted images, symptom questionnaires, or remote monitoring data) precedes a scheduled

📜 3 regulatory citations referenced  ·  ✅ Citations verified Feb 25, 2026  ·  View update log

Explore This Site