A major hurricane makes landfall near a metropolitan hospital. The emergency department fills with injured residents, power fluctuates across the region, and ambulances begin arriving from facilities that have lost critical services.
Then the hospital’s electronic health record (EHR) goes dark. Without a redundant environment, clinicians lose immediate access to medication histories, allergies, laboratory results, diagnostic images, and active orders.
For example, a nurse preparing a dose must rely on paper records that may already be outdated. An emergency physician treating an unconscious patient cannot review prior cardiac diagnoses or recent imaging. Teams moving patients to create capacity must hand off care without a complete record. In the middle of a community crisis, the hospital is forced to manage a second emergency inside its own walls.
This scenario illustrates why continuous EHR availability belongs in the same conversation as infection prevention, medication safety, and emergency preparedness. Hospitals operate around the clock, and the clinical record must remain available whenever care is being delivered. Planned maintenance that routinely removes access may be predictable, but predictability does not remove the risk.
Real physician voices, twice a week
Free, and one click to unsubscribe.
Downtime changes the conditions of care
Recent research in the American Economic Journal: Economic Policy shows how quickly technology disruption can affect patients. A study of ransomware attacks found that hospital volume fell between 17 percent and 24 percent during the initial week of an attack.
Among patients who were already admitted when an attack began, in-hospital mortality rose between 34 percent and 38 percent. The findings apply to ransomware-related disruption, but they reinforce a broader point. When digital systems fail, the conditions under which clinicians deliver care change immediately.
Separately, a 2025 JAMA Network Open analysis examined network disruptions associated with a faulty cybersecurity software update at 759 U.S. hospitals. Of nearly 1,100 internet-based services evaluated, 21.8 percent supported direct patient care. The disruption affected services involving EHRs, imaging, patient portals, monitoring, transfers, and other operational functions.
The operational consequences of downtime are also substantial. In a 2025 Ponemon Institute survey of U.S. health care IT and security professionals, an average of 72 percent of organizations affected by the cyberattack categories studied reported disruption to patient care. Among respondents whose organizations experienced ransomware, 67 percent reported longer lengths of stay, and 56 percent reported delays in procedures or tests. Respondents estimated that downtime or system-performance delays tied to their most costly recent attack caused approximately $859,000 in lost productivity on average.
Some of the most consequential costs of downtime are harder to calculate. They may include delayed medication, an incomplete clinical decision, pressure on neighboring emergency departments receiving diverted patients, and the emotional burden on clinicians delivering care without familiar information and workflows.
Design continuous availability into the service model
Zero planned downtime depends on an operating model that treats reliability as a continuous responsibility. Under a system-as-a-service approach, the technology provider assumes accountability for the software, hardware, implementation, maintenance, upgrades, and ongoing support required to keep the EHR operating. Bringing these elements together under one service model can reduce gaps in ownership and give health care organizations clearer expectations for system performance over the life of the agreement.
The architecture supporting that model should use redundancy to eliminate single points of failure. If a server, data center, network component, or local utility fails, another component should sustain access to the patient record without requiring clinicians to shift to paper workflows.
Upgrades and routine maintenance should also occur without interrupting clinical operations. Hospitals should evaluate whether a proposed solution has demonstrated this level of reliability in high-acuity, high-security environments and during real-world events, including natural disasters and infrastructure failures.
This approach also changes how reliability is evaluated. Rather than accepting recurring maintenance windows as an unavoidable part of EHR ownership, leaders can require continuous availability as a contractual and operational expectation. Clear accountability, resilient architecture, bundled support, and evidence of performance give hospitals a stronger foundation for protecting clinical workflows, care quality, and patient safety around the clock.
A safer standard for digital care
Hospitals cannot prevent every storm, cyberattack, software defect, or infrastructure failure. However, they can build an environment in which those events are far less likely to separate clinicians from the information required for safe decisions. An approach that combines resilient architecture, clear accountability, bundled support, and demonstrated reliability can make zero downtime an achievable standard for health care operations.
As health care leaders make continuous availability a patient safety standard, the industry can move toward a future in which technology remains dependable through routine maintenance and the most demanding moments of care.
Sandra Johnson is a health care executive.
Your KevinMD author page is one of the top results for your name. Turn it into a premium profile, publish in 1 to 3 days, and get a guaranteed podcast slot.
