
Trust takes years to build and can be tested in a few hours. An EHR outage is one of those tests. Patients may never know the technical cause, but they notice how the organization behaves: whether staff seem prepared, whether someone explains what is happening, whether the same questions are asked three times, and whether their care feels safe.
Most downtime plans are written for staff and systems. Very few are written with the patient’s experience in mind. That is a missed opportunity, because the choices an organization makes in the first hours of an outage often determine whether patients walk away feeling reassured or uneasy. Our posts on protecting the patient experience during downtime and what patients deserve to know lay the groundwork. This post focuses on trust specifically.
What Patients Notice
- Staff using paper or handwriting when they expect screens
- Asking for information the patient already provided
- Longer waits with no explanation
- Visible stress, raised voices, or hallway huddles
- Printed wristbands that look different or are missing
- Medication questions that seem to rely on memory rather than a chart
- A phone line that rings and rings
- A patient portal that will not load
Five Things That Protect Trust
- Competence they can see
- Candor in what they are told
- Safety that does not slip
- Privacy that holds
- Follow-through afterward
Competence They Can See
- Registration that continues electronically, with information pre-populated from the existing record where possible
- A proper identification wristband, printed promptly
- Staff who move calmly to a known procedure
- Signs and scripts ready to use rather than improvised
The preparation behind this is described in our posts on first 30 minutes of an outage and the first 24 hours of an extended outage.
Candor in What They Are Told
Honest communication is brief, specific, and consistent. It acknowledges the problem, explains the effect on the patient, and says what the organization is doing.
- At the front desk: a short statement that the system is temporarily unavailable, that registration is continuing with backup systems, and what the patient can expect for wait times
- At the bedside: a plain explanation that staff are using backup systems and are double checking identification and medications, and an invitation to ask questions
- By phone: a recorded message or script that gives the same information and a direct number for urgent needs
- Outbound: for scheduled appointments, proactive calls or texts that confirm whether the visit is proceeding or needs rescheduling
- Online: a short notice on the website and, if it is available, the portal, with updates as the situation changes
Avoid promises you cannot keep. Saying nothing is affected, when an appointment may run late, damages trust more than saying some delays are possible. Patients with limited English proficiency need the same information in their language. See HHS guidance on Section 1557 and plan interpreter access for downtime. Our post on the communication plan shows how to structure messages by audience.
Safety That Does Not Slip
Patients trust that their identity is correct, their medications are right, and their allergies are known. Outages put pressure on all three.
- Maintain two-identifier verification, supported by barcoded wristbands when possible. The Joint Commission National Patient Safety Goals emphasize correct patient identification
- Keep allergy and medication information accessible to clinicians through the downtime workstation or printed fallback
- Use handoff forms so information survives staff changes
- Review the ONC SAFER Guides for contingency planning practices
- Our post on why patient safety and downtime preparedness are the same conversation explains the connection
Privacy That Holds
Patients also worry about their information. If an outage may involve a security incident, the stakes rise.
- Make sure downtime workstations use authenticated access and logging, as described in our post on HIPAA and EHR data access during an outage
- Work with your privacy officer and counsel early if there is any chance of a breach
- Under the HIPAA Breach Notification Rule, notification to affected individuals must occur without unreasonable delay and no later than 60 days after discovery. The 60 days is an outer limit, not a target
- Communicate what you know and what you are still investigating, and avoid speculation
- Our post on ransomware versus routine downtime explains why the two require different responses
When Harm Occurs
If an outage contributes to a patient safety event, the quality of the response matters as much as the event itself.
- Disclose promptly, clearly, and with empathy, in line with your policies and legal guidance
- Follow a structured approach such as the AHRQ CANDOR toolkit, which focuses on early, honest communication and fair resolution
- Investigate with a systems lens, and share what changed as a result
- Support the clinicians involved
- Coordinate with risk management and legal teams on required steps and state law
Follow-Through After the Outage
- Confirm that the record is complete. Our guide to reconciling downtime data back into the EHR describes how to ensure that downtime registrations, forms, and documents are in the final record
- Review accounts for downtime-period encounters before statements go out, so patients are not billed for errors the outage created
- Follow up with patients whose visits were disrupted, with a thank you, an apology for inconvenience, and a way to ask questions
- Route complaints through your grievance process and track themes
- Share a short, honest summary of what happened and what you learned on your website or in a community update when the outage was significant
- Thank staff, because patients notice how staff treat each other during stress
How to Tell Whether Trust Held
- Complaints and grievances that mention the outage
- Comments in patient experience surveys that reference waiting, repeated questions, or system problems
- Walk-aways, reschedules, and no-shows during and after the event
- Portal messages and call volume related to the outage
- Referring physician feedback
Compare these to normal periods and keep the results with your after-action report.
What Preparedness Makes Possible
None of the above works without a functioning backup. Electronic registration with pre-populated information, properly printed wristbands, consistent consent capture, and a complete record after recovery are the visible proof that the organization was ready. dbtech’s downtime solution, together with eForms, is designed to support those elements. The communication and follow-through are organizational decisions that cost very little and can be written into your plan today.
To discuss how dbtech supports a patient-centered downtime program, contact our team or request a demo.