When the internet drops mid-session: redundancy for one room

What backup connectivity a telehealth practice actually needs

A one-room telehealth practice needs redundancy at three points, not one: a second connection to the internet that doesn't share a failure point with the first, backup power for the equipment that connection runs through, and a rehearsed fallback for finishing the session anyway when both fail. Skipping any one of the three still leaves a real gap — a backup hotspot with a dead phone battery is not a backup.

• A second internet path — a cellular hotspot on a different carrier than the primary ISP, kept charged and ready
• Battery or UPS backup — enough to keep the router and modem running through a short outage, not just the laptop
• A phone fallback plan — a rehearsed script for switching to a voice call without losing the rest of the session
• A documented contingency plan — written down once, not improvised the first time it's actually needed

Why this is a Security Rule question, not just an inconvenience

The Security Rule's administrative safeguards call for a documented contingency plan — how the practice keeps operating, and how it protects access to ePHI, when normal systems go down — which makes connectivity redundancy a compliance question with a paper trail, not just good sense 1Ref 1HHS Office for Civil Rights (2026).Summary of the HIPAA Security Rule.That the Security Rule's administrative safeguards call for a documented contingency plan, supporting connectivity redundancy as a compliance question rather than only an operational one.. A practice that has never written down what happens when the internet drops mid-session has a gap in that contingency planning, whether or not it has ever actually lost a connection yet.

The free risk-assessment tool built for small practices walks through contingency and availability questions in the same pass as the rest of the Security Rule review, and connectivity redundancy is a natural line item to answer honestly while completing it, rather than assuming a home internet connection is resilient enough on its own 2Ref 2Office of the National Coordinator / ASTP (2026).Security Risk Assessment Tool.That the free risk-assessment tool for small practices covers contingency and availability questions, supporting connectivity redundancy as a natural item within that existing process..

The phone fallback: what to do when video drops mid-session

When a video connection fails outright, finishing the session by phone is both clinically reasonable and billable — CMS's own list of telehealth-payable codes includes audio-only eligibility for a defined set of services, so a dropped call doesn't automatically turn the visit into unbillable time 3Ref 3Centers for Medicare & Medicaid Services (2026).List of Telehealth Services.That CMS's telehealth list includes audio-only eligibility for defined services, supporting that a phone fallback after a dropped video call can remain billable.. Confirming which specific codes in the practice's regular billing carry audio-only eligibility, rather than assuming all of them do, avoids a surprise at claims time.

The platform used for that phone fallback still has to meet the same HIPAA bar as the video platform it's replacing — a personal cell line is fine for the call itself, but any note taken about what happened during the outage belongs in the same secured record as the rest of the visit 4Ref 4HHS Office for Civil Rights (2026).HIPAA and Telehealth.That telehealth arrangements, including audio-only, must meet HIPAA-compliant standards, supporting that a phone fallback still needs compliant documentation of the encounter.. Building the dropped call into a written protocol in advance — who calls whom, what gets said about the interruption, how the remaining time gets billed — turns a stressful moment into a rehearsed one instead of an improvised one.

The second connection itself: what redundancy actually looks like

A cellular hotspot on a carrier different from the practice's primary internet provider is the most common form of real redundancy for a single-room practice, because it fails independently of a wired connection going down — a hotspot on the same carrier that provides the office's fiber or cable line doesn't offer much protection if that carrier has a wider outage. Keeping the hotspot charged, tested monthly, and loaded with enough data to actually carry a video session is what turns it from a drawer item into a working backup.

A small UPS battery for the router and modem covers the more common failure — a brief power blip, not a full outage — and buys enough time to either finish the session on battery power or switch to the cellular hotspot cleanly instead of losing the call outright.

For a practice in an area prone to multi-hour or multi-day outages — storm season, an aging local grid — a small generator or a larger battery bank is worth the extra cost beyond a basic UPS, since a UPS sized for a router and modem typically only bridges a short blip, not an extended outage. Matching the backup's actual runtime to the practice's own outage history, rather than buying the cheapest UPS available, is what keeps this a real plan instead of a token gesture.

What else goes down when the internet does

A connectivity outage doesn't only take down the telehealth session — the practice line, if it runs over VoIP rather than a traditional landline, can go with it, along with practice email and the practice website if either depends on the same office connection for anything live. Mapping out which of those actually depend on the office's own internet, versus which run entirely in the cloud regardless of what happens at the office, is worth doing once rather than discovering the dependency during an actual outage.

A cellular hotspot that restores the video session usually restores the phone and email dependency at the same time, which is one more reason a tested, charged hotspot is the single highest-value piece of this whole setup.

A cloud-hosted EHR is the exception worth understanding separately: it generally keeps running through a local outage since it lives on the vendor's own infrastructure, not the practice's — the outage only blocks the practice's own access to it, which is one more reason a working internet connection of some kind is the actual bottleneck, not the EHR itself. Confirming that the EHR vendor's own uptime and support commitments are documented somewhere the practice can reference gives a second data point beyond the practice's own redundancy plan.

Deciding how much redundancy is worth building

How much redundancy makes sense depends on the practice's format: the officeless practice running entirely on telehealth has more riding on a single connection than a practice splitting time between in-person and video, where the hybrid decision already builds in a fallback of sorts — an in-person day covers for whatever a bad connectivity day would have cost. Either way, the redundancy plan is worth writing into the same operational section of the practice's business plan where other continuity questions already live, rather than treating it as a one-off purchase decision 5Ref 5U.S. Small Business Administration (2026).Write your business plan.SBA's business-plan structures, supporting the framing of a connectivity contingency plan as part of the operations section of a standard business plan..

HHS's own cybersecurity practices guidance for small health care practices frames this kind of contingency planning as one baseline expectation among several, sized specifically for an operation with no IT department behind it 6Ref 6HHS 405(d) Program (2026).HHS 405(d) — Aligning Health Care Industry Security Approaches.That HHS's 405(d) program publishes a cybersecurity practices baseline sized for small practices, supporting a proportionate, not data-center-scale, approach to redundancy. — which is the right frame for a solo practice deciding how much to spend on redundancy: enough to keep operating through an ordinary outage, not a data-center-grade buildout no single-room practice needs.