
When a flight is delayed, passengers are told immediately. When a restaurant is closed unexpectedly, a sign goes on the door. When a bank’s online system goes down, customers receive a notification within minutes. In each of these cases, the organization affected treats the people who depend on it as stakeholders who deserve timely, honest communication about disruptions that affect them.
Healthcare is different. When an EHR goes offline, the disruption is typically communicated within the organization and managed internally. The patients who are scheduled for appointments, waiting for test results, or currently in the facility receiving care are rarely told anything formal. They observe that something seems different. Staff are doing things in unusual ways. Wait times are longer. The person at the registration desk is using paper forms. Something is happening, and no one is explaining what.
This silence is not malicious. It reflects the healthcare industry’s default orientation toward managing operational problems internally rather than communicating them to patients. It also reflects a genuine concern about causing unnecessary alarm. But the absence of communication does not protect patients from the anxiety of noticing something is wrong. It simply leaves them to form their own conclusions, which are frequently more alarming than the reality.
Patients deserve to know more about how their hospital handles EHR downtime than most organizations currently communicate. Not because regulatory requirements demand it, though some increasingly do, but because the people whose health depends on an organization’s ability to function continuously during system failures have a legitimate stake in knowing that the organization takes that responsibility seriously.
What Patients Are Actually Experiencing During a Downtime Event
Understanding what patients deserve to know starts with understanding what they are actually experiencing during a downtime event, most of which happens without any explanation from the organization.
A patient who arrives for a scheduled appointment during an EHR outage notices that the registration process is slower than usual, that the staff member at the desk seems stressed, and that information the patient provided at previous visits is being requested again. They may wait longer than expected to be called back. The care they receive may feel different in subtle ways: the nurse asking more questions from memory rather than reviewing the chart on a screen, the physician not having the most recent test results immediately available.
A patient who is already in the facility when an outage begins experiences a more abrupt transition. The care they are receiving continues, but the environment changes in ways they may not understand. The tablet or screen that was displaying their care information may go dark. Staff interactions may shift from screen-focused to more direct but less informed. The patient may hear staff discussing something called downtime without context for what that means for their care.
A patient who is waiting for results or follow-up care during an outage may simply not hear anything for longer than expected, with no explanation of why.
In each of these scenarios, the patient’s experience of the downtime event is shaped almost entirely by what staff say or do not say. Most patients receive no explanation unless they directly ask, and many are reluctant to ask because they do not want to appear difficult or because they are genuinely uncertain whether something is actually wrong.
What Well-Prepared Organizations Communicate and When
Organizations that handle patient communication during downtime events well share a set of practices that the less prepared do not consistently apply.
They brief front-facing staff before or immediately at the start of a downtime event on what to say to patients who ask or who visibly notice that something has changed. The briefing script is simple, honest, and reassuring: the hospital is experiencing a temporary system issue, care is continuing with electronic backup systems in place, and the patient’s information and record are secure and will be fully updated when the system is restored. Staff who have this script are confident. Staff who do not improvise in ways that sometimes produce accurate information and sometimes produce well-intentioned misinformation that creates more anxiety than the honest version would have.
They proactively notify patients whose scheduled appointments may be affected, rather than leaving those patients to arrive and discover the situation. A brief outbound call or message that acknowledges the system issue, confirms that the appointment is proceeding as scheduled, and assures the patient that their care will not be affected treats the patient as a stakeholder rather than a problem to be managed.
They display visible evidence of their preparedness. The registration desk that transitions seamlessly to electronic downtime registration using dbtech’s downtime workstations, prints a properly barcoded wristband, and completes the consent form electronically is communicating organizational competence without a single word. The patient’s direct experience of the intake process communicates more about the organization’s preparedness than any announcement.
What Patients Have a Right to Expect
Healthcare organizations have legal and ethical obligations to patients that extend into the downtime context, even where no specific regulatory requirement mandates downtime-specific patient communication. These include:
The right to care that is not compromised by preventable system failures. Patients who are harmed during a downtime event because the organization had no functional backup procedures for medication safety or patient identification are patients whose safety was put at risk by organizational negligence, not by the technology failure itself. Adequate downtime preparedness is a component of the safe care obligation.
The right to honest communication when care is affected. A patient who is told that everything is fine when a system failure is affecting the quality of information available to their care team has not received accurate communication. Transparency about what is happening and reassurance that backup systems are in place is both more honest and more effective at managing patient anxiety than vague reassurance.
The right to a complete record. A patient whose care during a downtime event is documented on paper that is partially or incorrectly reconciled into their EHR after restoration has an incomplete medical record. The documentation quality during downtime events is a patient rights issue as much as an operational one. Patients should be able to trust that the record of their care is complete and accurate regardless of what system was available when the care was delivered.
Why Transparency About Preparedness Builds Trust
The healthcare organizations that communicate most transparently about how they handle downtime events are not the ones that experience fewer downtime events. They are the ones that have invested in genuine preparedness and are not afraid to explain what that investment means for their patients.
A hospital that can tell a patient we have electronic backup systems that keep your care continuous during any system outage, and your record will be fully complete when everything is restored is communicating something true and reassuring. That communication is only possible because the organization has dbtech’s Downtime Solution in place, has practiced using it, and knows from experience that the claim is accurate.
The organizations that say nothing during downtime events are often the ones that have nothing confident to say, because their backup procedures are inadequate and the honest explanation would acknowledge that patient care was compromised during the event rather than reassure patients that it was protected.
Building the genuine preparedness that makes transparent patient communication possible is the investment that produces trust. The trust is the outcome. The downtime solution is the prerequisite. To learn how dbtech supports organizations in building the preparedness that makes this kind of transparency possible, request a demo or contact our team.