When an EHR goes offline, two problems emerge simultaneously. The first is operational: clinical and administrative workflows need to shift to backup procedures. The second is informational: every person in the organization who depends on the EHR needs to know what is happening, what to do, and when to expect resolution. The operational problem gets most of the attention in downtime preparedness planning. The informational problem gets far less, and the gap shows up painfully during actual events.
Poor communication during a downtime event does not just cause inconvenience. It causes operational failures that compound the disruption. Departments that do not know downtime procedures have been activated improvise instead of following protocol. Clinical staff who do not know the expected duration of the outage make poor decisions about deferring care versus proceeding without the EHR. Leadership that is not informed cannot make decisions about escalation, patient diversion, or external communication. Patients who are not told anything become anxious and difficult to manage.
A downtime communication plan is a distinct component of the broader downtime preparedness program. It specifies who communicates what to whom, through which channel, at which trigger points during the outage lifecycle. Getting this right is as important as getting the technology right.
The Four Communication Audiences During a Downtime Event
A downtime communication plan needs to address four distinct audiences, each with different information needs and different communication channel requirements:
- Clinical and administrative staff, who need to know that downtime procedures are activated, where the downtime workstations are, what their specific role is during the event, and what updates they can expect on recovery timeline
- Leadership and decision-makers, including the CIO, CMO, CNO, and department directors, who need timely information about the nature and scope of the outage, the expected recovery timeline, any patient safety concerns that have arisen, and any decisions that require executive input such as patient diversion or external notifications
- IT and the EHR vendor’s support team, who need a clear internal communication channel for sharing technical status updates and coordinating the recovery effort without creating noise across the rest of the organization
- Patients and families, who may be waiting for appointments, procedures, or test results that are affected by the outage and who deserve timely, honest communication about what is happening and what it means for their care
Each of these audiences requires a different message, a different tone, and potentially a different channel. A single all-staff email satisfies none of them well.
Building the Communication Trigger Framework
A downtime communication plan should specify what communication goes out at each stage of the outage lifecycle, not just at the beginning. The trigger points that should generate defined communications include:
- Initial detection and activation: The moment the IT team confirms an outage and downtime procedures are activated, a notification goes to department leads and leadership with the basic facts: what is down, what is known about the cause, what downtime procedures are being activated, and who the point of contact is for updates
- 30-minute update: If the outage is not resolved within 30 minutes, a follow-up communication updates the original audience with what is known about the expected recovery timeline and any operational decisions that have been made, such as holding elective procedures or diverting ambulance traffic
- Hourly updates for extended outages: For outages lasting more than an hour, hourly updates to staff and leadership maintain situational awareness and prevent the information vacuum that leads to improvisation and rumor
- Patient communication trigger: A defined threshold, for example an outage affecting scheduled appointments or patient-facing services that extends beyond a specified duration, should automatically trigger patient-facing communication through whatever channels the organization uses: text, phone, patient portal message
- Recovery notification: When the EHR is restored, a clear communication to all staff confirms that normal operations can resume and specifies any transition steps required, including how downtime workstations should be closed out and what the reconciliation process looks like
Channel Selection for Downtime Communication
One of the most common failures in downtime communication planning is the assumption that normal communication channels will work during an outage. If staff communication runs primarily through the EHR’s internal messaging system, that channel may be unavailable during a downtime event. If leadership communication relies on email and the email system is hosted on infrastructure that is also affected by the outage, that channel may be degraded.
A downtime communication plan should specify backup channels for each audience that are independent of the EHR and the organization’s primary IT infrastructure. Practical options include:
- A dedicated overhead paging protocol for facility-wide downtime notifications that does not depend on any digital system
- A phone tree or group text chain for department leads that uses personal mobile devices rather than organization-issued devices that may be connected to affected infrastructure
- A pre-designated physical command location where the downtime coordinator and key stakeholders gather for in-person communication during extended events
- Pre-written communication templates for each trigger point that can be deployed immediately without requiring someone to draft new communications under pressure
dbtech’s Downtime Solution supports communication continuity by keeping the operational infrastructure, patient data, forms, and registration tools available during an outage, which reduces the volume and urgency of operational questions that the communication plan has to manage. When staff have clear backup procedures and functional tools, the communication burden shifts from explaining what to do to providing status updates on recovery, which is a significantly more manageable task.
Patient Communication During a Downtime Event
Patient communication is the dimension of downtime communication planning that organizations most often skip entirely. The assumption is that patients do not need to know about IT problems. In reality, patients who are waiting for appointments, test results, or procedure scheduling are directly affected by an outage, and leaving them uninformed creates anxiety, erodes trust, and generates volume in the phone system that the organization’s staff cannot manage while simultaneously managing the downtime procedures.
Effective patient communication during a downtime event is brief, honest, and action-oriented:
- Patients with scheduled appointments should be notified promptly if their appointment will be delayed or rescheduled, with a specific alternative offered rather than a generic apology
- Patients waiting in the facility should be given a realistic update on the situation and the expected timeline, delivered in person by a staff member or registration representative rather than by an overhead announcement
- Patients who have pending results or referrals should be reassured that their records are intact and that normal service will resume as soon as the system is restored
None of these communications requires detailed technical information about the outage. Patients do not need to know that the EHR’s HL7 feed experienced a connectivity failure. They need to know what it means for them and what happens next. Keeping the patient communication simple and specific is both more effective and more appropriate.
To learn how dbtech supports the full downtime response lifecycle, including the operational infrastructure that makes communication management easier, visit our Downtime Solutions page or request a demo.