Does dbtech Work If the Internet Is Also Down?
Yes. This is one of the most important architectural distinctions between dbtech and cloud-based downtime solutions, and it is a question every healthcare organization should ask before purchasing any downtime product.
The scenario where both the EHR and the internet go down simultaneously is more common than most IT teams expect. A ransomware attack that encrypts your network will take down your EHR and may sever your internet connection as containment measures are applied. A severe weather event that damages local infrastructure can take out both simultaneously. A major ISP outage in your region can affect your EHR connectivity and your internet access at the same time.
If your downtime solution depends on reaching a cloud server to access patient data, it will not work in any of these scenarios. You will have a downtime solution that goes down with everything else.
Why dbtech Is Built On-Premise
dbtech’s solution is an on-premise system. Patient data is stored locally, either on dedicated downtime workstations or on a local server within your facility, depending on your configuration. The HL7 interface that continuously feeds data from your EHR into dbtech runs on your local network. When the internet goes down, that local data remains accessible because it does not depend on reaching an external server.
Specifically, here is what remains functional when the internet is unavailable:
- Clinical staff can access the current patient census and patient history from downtime workstations
- The medication administration record is available for nursing staff to reference
- New patients can be registered electronically using downtime encounter numbers
- Barcoded wristbands and labels can be printed from local printers connected to the downtime workstations
- eForms can be completed, signed, and saved locally without internet connectivity
- Patient documents can be scanned and saved within the system
What Requires Connectivity and What Does Not
To be precise about the architecture, the HL7 data feed between your EHR and dbtech requires your local network to be running. It does not require internet access. The downtime workstations themselves require power and local network connectivity to function fully. In a scenario where the local network is completely down, the data that was already synchronized to individual workstation storage remains accessible on those specific machines.
This distinction matters most in ransomware scenarios, where IT teams may intentionally isolate parts of the network to contain the spread. In those situations, your downtime preparedness plan should specify which workstations are designated for isolated operation and how staff access them when network segments are being shut down.
What This Means for Your Preparedness Planning
Understanding the on-premise architecture of dbtech’s solution should directly inform how you structure your downtime procedures. Organizations that know their downtime system works without internet can be confident deploying it in any outage scenario, including the most severe ones. To learn more about how dbtech’s architecture fits your environment, request a demo or contact our team.