Your EHR will go offline eventually — here’s how to make sure your team is ready
An EHR downtime is the kind of event that reveals, quickly and concretely, whether a team has practiced for it or only planned for it. While planning establishes procedures on paper, practice builds the competence needed to carry them out under pressure. This guide covers six clinical and operational priorities for EHR downtime drills and explains how to build an exercise around each one.
Why drills expose what plans miss
When the EHR is unavailable, clinicians face specific, concrete problems: How do you confirm a patient’s identity without a pull-up? Where are the paper order forms? Who decides when to escalate a medication question that normally gets answered by checking the chart? These are procedural muscle-memory questions, and they are only answered reliably by practice rather than by reading a checklist.
The Academic Medical Center Patient Safety Organization’s downtime task force guidelines specifically recommend running drills as part of a complete downtime preparedness program, alongside staff training and a communication triage procedure. The US Department of Health and Human Services’ Administration for Strategic Preparedness and Response (ASPR) also provides a collection of EHR downtime resources to help healthcare organizations prepare for outages and maintain patient safety.
Patient identification: The highest-risk workflow
Analysis of patient safety events during EHR downtime consistently highlights patient identification and clinical information communication as the two areas of greatest risk. When the EHR system is unavailable, clinicians cannot verify patient identity through the standard electronic process, and the manual alternatives need to be established and practiced before they are needed.
The drill should walk through how staff confirm patient identity using two manual identifiers, where paper wristbands are stored and how they are applied, and what process is used to flag patients whose records may have been updated during the outage and need to be reconciled once the system returns. This is one of the areas where badge buddy cards, which are laminated reference sheets that attach to staff ID badges, have been shown in published implementation studies to improve nurse readiness.
Medication safety during downtime
Medication errors are among the most documented harms associated with EHR downtime. When the system is offline, pharmacy, nursing, and prescribing teams may lose access to current medication lists, allergy records, and order histories simultaneously. The drill should therefore test how each group handles this gap.
Specific scenarios to rehearse include:
Verifying an existing medication order without EHR access
Managing a new prescription when clinical decision support is unavailable
Communicating a critical allergy flag from nursing to pharmacy by paper
Handling a controlled substance order when the usual electronic verification cannot be completed
The Institute for Safe Medication Practices recommends assigning a dedicated downtime response team, with designated leaders on call to oversee medication safety during extended outages.
Documentation and order management
All orders, assessments, and clinical notes generated during downtime need to be documented on paper, tracked, and then entered into the EHR system during the recovery phase. The drill should confirm that paper forms are stocked, accessible, and understood by staff in each unit; that there is a defined process for numbering and collecting downtime documents; and that staff know which actions require immediate documentation versus which can be logged during recovery.
A standardized naming convention for patients seen during downtime is important for laboratory and radiology workflows, in particular, where specimens and images may need to be matched to a patient record that was created or updated while the EHR was unavailable.
Internal communications and escalation
When the EHR is offline, the communication infrastructure that coordinates care across departments also degrades. Automated alerts, results notifications, and order confirmations stop flowing. The drill should establish and test an alternative communication protocol: who notifies each clinical area when downtime begins, what the expected update frequency is, and what channel (telephone tree, whiteboard, radio) carries clinical communications during the event.
Escalation criteria should also be established in advance, since not every situation that triggers an EHR alert during normal operations warrants the same response during downtime. The drill should clarify which conditions require immediate escalation to a physician or charge nurse, regardless of system availability.
Recovery and reconciliation
Returning to full EHR functionality is not a passive event. Paper records created during downtime need to be scanned and entered, orders verified and reconciled, and any discrepancies between downtime documentation and the pre-downtime record resolved. The drill should cover who is responsible for each component of this reconciliation, how long it is expected to take, and what the priority order is for entering data generated during the outage.
A safe return to normal operations depends on how well these steps are coordinated. Research examining a major EHR downtime event in Australia highlighted the importance of effective communication during the transition back to electronic records. This recovery phase, sometimes called the uptime procedure, requires as much planning and coordination as the downtime response itself.
Our team helps healthcare practices and facilities develop and update EHR downtime procedures and clinical IT continuity plans, including practical drill programs tailored to their needs. Get in touch to discuss how we can help your organization prepare for EHR outages.
Most healthcare organizations have an EHR downtime policy. Fewer have a practiced downtime procedure that clinical staff can execute under pressure. The two are different, and the gap between them is where patient safety risk lives. This article focuses on building a drill that trains the actual workflows your team will need when the system goes offline.
EHR downtime can disrupt essential clinical workflows, delay access to patient information, and complicate medication management. Without clear procedures and adequate preparation, these disruptions can put patient safety and continuity of care at risk. A written contingency plan is a starting point, but regular drills help staff practice the workflows they need to maintain care when the system goes offline.
Browser extensions are treated as convenient add-ons rather than what they actually are: software installed on a business computer with significant access to network traffic, browsing data, and, in some cases, stored credentials. The Cybersecurity and Infrastructure Security Agency (CISA) has explicitly noted that browser extensions can carry high privilege levels and introduce substantial security concerns. For businesses that haven’t reviewed their extension landscape recently, this checklist covers the areas that are often overlooked.
A browser extension with permission to read and change all your data on every website has roughly the same access to your activity as the browser itself. For individual users, that might be an acceptable tradeoff for a useful tool. For a business PC, it is an access level that deserves the same scrutiny as any other privileged software. This guide covers browser security best practices recommended by the Cybersecurity and Infrastructure Security Agency (CISA), including how to audit installed extensions, evaluate their permissions, and keep them under control.
Most businesses carefully manage which software gets installed on company computers. Fewer apply the same discipline to browser extensions, even though extensions often carry permissions that rival those of traditional installed applications. The Cybersecurity and Infrastructure Security Agency’s (CISA) guidance on web browser security calls out extensions specifically as a source of elevated risk. This checklist translates that concern into practical steps.
An uninterruptible power supply (UPS) is the kind of equipment that gets purchased, installed, and then forgotten about until something goes wrong. The problem with that approach is that UPS batteries degrade, their runtimes shrink, and the workloads connected to them grow over time, often without anyone updating the protection strategy to match. A regular UPS audit closes those gaps before an actual power event turns them into downtime.
An uninterruptible power supply (UPS) is one of those IT investments that looks fine on paper until a real power event tests it. However, over time, UPS batteries age and lose capacity. Workloads grow and exceed original runtime estimates. Units get supplemented with additional equipment but never re-evaluated for load. A periodic UPS audit catches these issues while there is still time to correct them.
Most small and mid-size businesses have at least one UPS (uninterruptible power supply) protecting their servers and network gear. Fewer have a clear picture of whether those units are still adequately sized, whether the batteries are still functional, or whether the equipment they’re protecting has grown beyond the unit’s rated capacity. This guide covers the key areas to check and what to do about what you find.
For businesses reconsidering their phone infrastructure, the VoIP vs. VoLTE question comes up regularly. Both technologies deliver digital voice calls at lower cost than legacy systems. Where they differ is in the network they rely on, how they perform in different environments, and what kind of mobility they support. Working through those three criteria narrows the field considerably.