Broadband and Connectivity Requirements for Telehealth

Reliable broadband access is a foundational infrastructure requirement for telehealth delivery, determining whether real-time video consultations, remote patient monitoring transmissions, and asynchronous data exchanges can occur without clinically meaningful disruption. This page covers the technical thresholds, regulatory frameworks, and connectivity classifications that govern telehealth broadband adequacy across the United States. Understanding these requirements matters because connectivity gaps directly affect care continuity, particularly in rural and underserved settings where broadband infrastructure is least developed.

Definition and scope

Broadband, as defined by the Federal Communications Commission (FCC), refers to high-speed internet service capable of supporting advanced telecommunications applications. The FCC's longstanding benchmark, established in 2015 and reaffirmed through subsequent proceedings, sets the minimum threshold at 25 Mbps download and 3 Mbps upload (FCC Broadband Speed Benchmark, 2015). However, the FCC proposed in 2023 to raise that standard to 100 Mbps download and 20 Mbps upload to reflect evolving use patterns, including telehealth video.

Within telehealth specifically, connectivity requirements are not uniform. The scope encompasses three distinct technical contexts:

1. Synchronous video encounters — live, two-way audio-video sessions between patient and provider
2. Remote patient monitoring — continuous or episodic transmission of physiological data from wearable or in-home devices to clinical systems
3. Store-and-forward telehealth — asynchronous upload of images, recordings, or diagnostic files for later clinical review

Each context carries different bandwidth, latency, and packet-loss tolerances. The Health Resources and Services Administration (HRSA) and the Office for the Advancement of Telehealth (OAT) publish guidance documents that reference these distinctions in the context of federally funded telehealth programs.

The FCC's E-Rate and Rural Health Care (RHC) programs, authorized under the Telecommunications Act of 1996, provide the primary federal subsidy structure for extending broadband infrastructure to health care facilities in rural areas. Facilities operating under the RHC program may receive discounts of up to 65 percent on eligible telecommunications services (FCC Rural Health Care Program).

How it works

Telehealth connectivity performance depends on four measurable network parameters: bandwidth, latency, jitter, and packet loss. Each parameter maps to specific clinical failure modes.

Bandwidth governs the volume of data transferable per second. For standard definition video consultations, the American Telemedicine Association (ATA) has referenced minimum thresholds of approximately 1 Mbps symmetric (upload and download matched) as the floor for functional video, with high-definition encounters requiring 3–5 Mbps symmetric. Diagnostic-quality video, such as dermatology or ophthalmology image review, may require 10 Mbps or higher.

Latency measures the round-trip delay between endpoints, expressed in milliseconds (ms). The ITU-T G.114 recommendation (ITU-T G.114) sets the upper acceptable one-way delay for real-time voice applications at 150 ms; latency above this threshold introduces perceptible conversational lag that affects clinical communication accuracy.

Jitter is the variance in packet arrival timing. In synchronous video encounters, jitter exceeding 30 ms causes video artifacts and audio breakup. Packet loss above 1 percent in a telehealth video stream produces visible blocking, frozen frames, or dropped audio segments — all conditions that can obscure clinical observations such as patient affect, gait, or wound appearance.

HIPAA's Security Rule, administered by the Office for Civil Rights (OCR) within the Department of Health and Human Services (HHS), does not mandate specific bandwidth thresholds but requires covered entities to implement technical safeguards that protect the confidentiality and integrity of electronic protected health information (ePHI) during transmission (45 CFR §164.312). Unstable connections that cause session interruptions can trigger ePHI exposure risk if applications do not properly terminate sessions or clear cached data. For a broader treatment of HIPAA obligations in telehealth, see Telehealth HIPAA Compliance Requirements.

Common scenarios

Connectivity requirements vary substantially across care settings and encounter types. Four representative scenarios illustrate the range:

Primary care video visit (patient home to provider office): A standard synchronous encounter for telehealth primary care requires sufficient upstream bandwidth at the patient's location — typically 1.5–3 Mbps — and matching downstream capacity at the provider end. Consumer broadband connections in suburban and urban areas generally exceed this threshold, but rural fixed wireless or satellite connections may not meet latency requirements even when nominal bandwidth appears adequate.

Telestroke consultation (hospital spoke to hub): Stroke neurology assessments via telehealth require high-definition video at frame rates sufficient to evaluate facial droop and limb coordination. Hospital-to-hospital links for telestroke and neurology telehealth typically run over dedicated leased lines or managed healthcare networks rather than public internet connections, targeting latency below 100 ms and packet loss below 0.5 percent.

Remote patient monitoring (home wearable to EHR): Cardiac monitoring devices transmitting continuous ECG data require stable upload capacity. Devices in the wearable devices and telehealth category typically generate between 10 kilobits and 1 Mbps of upstream data depending on sampling rate and compression, but the critical requirement is connection reliability rather than peak throughput.

Federally Qualified Health Center (FQHC) deployment: FQHCs operating telehealth programs under HRSA funding face both technical and regulatory connectivity standards. The FCC's RHC Healthcare Connect Fund targets multi-site health care broadband networks and permits FQHCs to receive subsidized high-capacity connections. More on FQHC telehealth infrastructure appears at Federally Qualified Health Center Telehealth.

Decision boundaries

Determining whether a given broadband connection is adequate for telehealth requires applying classification criteria across three dimensions: connection type, measured performance, and clinical use case.

Connection type classification:

Geostationary satellite connections present a structural barrier to synchronous telehealth because orbital altitude — approximately 35,786 kilometers — produces round-trip signal latency of 600–700 ms, well above the ITU-T G.114 threshold and the ATA's functional video requirements. Low-earth orbit (LEO) systems operating at altitudes of 340–1,200 kilometers reduce this latency to ranges compatible with live video.

Regulatory decision boundaries also apply at the program level. The Centers for Medicare and Medicaid Services (CMS) does not specify a minimum Mbps requirement in Medicare telehealth coverage rules (42 CFR §410.78), but does require that the telecommunications system used for interactive telecommunications be capable of real-time, two-way interactive audio and video. A connection that produces video failure rates high enough to preclude clinical assessment fails this functional standard regardless of nominal speed.

State-level variation also applies. As detailed in State Telehealth Laws and Policies, individual states may impose technology requirements within their Medicaid programs that specify connection quality or platform certification standards separate from federal CMS rules.

Practitioners and health system administrators evaluating connectivity adequacy typically apply a three-step assessment:

1. Measure actual performance — not advertised speed — using tools such as the FCC's Measuring Broadband America program or network diagnostic instruments that report latency and packet loss alongside throughput
2. Match use case to thresholds — synchronous video, asynchronous store-and-forward, and RPM each carry distinct minimum requirements; a connection adequate for store-and-forward may be inadequate for live video
3. Assess redundancy — clinical-grade telehealth deployments in hospital and health system contexts typically require a secondary connection path, documented in business continuity plans under HIPAA's contingency planning standard at [45 CFR §164.308(a)(7)](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart