A clinic internet outage backup plan should do more than switch to another connection. It should help staff keep essential patient communications and clinical work moving, while making clear what to do if the EHR itself is unavailable.
The right setup depends on how your practice uses phones, cloud systems, local equipment, and backup power. Start by identifying what depends on the internet, what must remain available during an outage, and which backup options do not share the same points of failure.
Map the services and dependencies
List the systems staff rely on during a normal clinic day. Include the EHR, phones, appointment and patient communication tools, access to essential patient information, and the network equipment that connects them. Note which services are cloud-based and which depend on equipment at the clinic.
Then trace the dependencies. A cloud EHR may need a working internet connection, a powered router, and a functioning device. VoIP phones may rely on that same connection, local network equipment, and electrical power. If both services share one internet path or one power source, a single failure could affect them together.
Ask your internet provider, phone provider, and EHR vendor what each service depends on, how an outage is reported, and what alternatives are available. Keep the answers in a place staff can reach without relying on the affected systems.
Choose a backup connection by independence, not just availability
A second connection is useful only if it can still work when the primary path fails. Possible options include a second wired provider, cellular internet failover, or satellite service. Their usefulness depends on local availability, expected capacity, power, equipment, and the cause of the outage.
- Second wired provider: Ask whether it uses a different route and infrastructure from the primary provider. Two plans may still share a vulnerable path.
- Cellular failover: A cellular router or hotspot can provide another route, but check signal strength inside the clinic, provider coverage, data capacity, and whether the equipment can switch over as intended.
- Satellite service: Consider whether it is available and suitable for the clinic’s needs, and what equipment, power, and operating conditions it requires.
A cellular hotspot may let staff reach a cloud-based EHR if the EHR vendor is available, the cellular connection has enough capacity, and the clinic’s device and security setup permit access. It is not a substitute for the clinic’s EHR downtime procedure, and a hotspot does not resolve an outage at the EHR vendor.
For background on telecommunications disruptions in healthcare, see the HHS telecommunications utility-failure tip sheet. The SAFER Guide to Contingency Planning is also a useful resource when reviewing how clinical systems should be handled during downtime.
Prioritize backup capacity around clinical risk
There is no universal traffic order that fits every clinic. Decide priorities by considering the clinical purpose of each service, how staff will use it during an outage, and what other work depends on it. Include clinical staff and the people responsible for IT and operations in the discussion.
For many practices, the assessment should first consider access to essential patient information and clinical communications. Next, consider how patients can reach the practice and how staff can coordinate. Administrative applications, guest Wi-Fi, and other work that can safely wait may be lower priorities on a constrained backup connection.
Write down which services should be available on the backup link and who can change those priorities. If network equipment supports traffic prioritization, have the configuration reviewed and tested. Do not assume that a backup connection has enough capacity for every service at once.
Keep patient calls reachable
Find out how your phone system behaves when the clinic’s internet or power fails. VoIP phones may stop working if they depend on the same internet connection or powered network equipment that went down. Some phone services may support call forwarding or alternate devices, but the details depend on the provider and configuration.
Agree on a fallback with your phone provider before an outage. Document how calls can reach designated staff, which approved devices they should use, and how the team will communicate if the usual phones are unavailable. Keep the instructions accessible outside the systems they are meant to replace, and make sure staff know who is responsible for activating them.
Prepare for an EHR outage separately
When the internet is down, a working alternate connection may restore access to a cloud EHR. When the EHR vendor is down, changing internet providers may not help. Your response should distinguish between these situations so staff do not spend time troubleshooting the wrong problem.
Document how staff will confirm whether the issue appears to affect the clinic’s connection, the EHR, or both. Use the providers’ established support and status channels, and identify who will communicate updates to the team. If the EHR is unavailable, staff should follow the practice’s approved downtime workflow for essential patient information and documentation. Define how records created during downtime will be entered or reconciled after service returns.
For additional EHR downtime considerations, see what to do when an EHR goes down. A review of your healthcare network setup can also help identify shared dependencies that may affect both primary and backup access.
Test the plan and make it usable
A plan on paper may not match how the clinic’s equipment and services behave. Schedule practice tests that fit your operations, and repeat them after meaningful changes to the internet connection, phones, network, or EHR setup. Coordinate tests with providers when needed so they do not create avoidable disruption.
- Confirm whether failover occurs automatically or requires a staff action.
- Check whether essential EHR access and phone arrangements work on the backup connection.
- Verify that routers, phones, and other needed equipment have a power plan.
- Practice staff communications and the EHR downtime workflow.
- Record problems, assign follow-up, and update the instructions after changes.
Keep the plan concise and available in a location staff can reach during an outage. Include contacts, activation steps, decision-makers, and recovery steps. A clear process can help the team move from uncertainty to an agreed response.
Frequently asked questions
Will VoIP phones work if the internet or power goes out?
They may not if they depend on the failed connection or local power. Confirm the phone provider’s options for forwarding calls or using alternate devices, and test the arrangement.
How can we tell whether the outage is with our internet provider or EHR vendor?
Check the clinic connection and the vendor’s approved status or support channels. Have a designated person gather updates and share them with staff. A second internet link can help with a clinic-side connection failure, but it may not help if the EHR vendor is unavailable.
How often should we test failover and downtime steps?
Set a schedule that fits the practice, and test again after relevant system or provider changes. Include both the technical connection and staff workflows, not just whether a device can get online.
Keep the response practical
A dependable clinic internet outage backup plan accounts for connection failures, phone continuity, power, and EHR downtime as related but distinct problems. Zevonix supports healthcare IT infrastructure, including network management, backup, and disaster recovery, with 24/7 network monitoring and proactive maintenance. Contact Zevonix to discuss how your practice can review its outage and failover plan.