Most downtime planning assumes the problem is the system. The software fails, the server goes down, or an attacker locks the network, and everything else in the building keeps working. Severe weather and natural disasters break that assumption. A hurricane, ice storm, flood, wildfire, tornado, or earthquake can take down the EHR, and it can also take down power, phone service, internet, supply deliveries, and the staff who normally run the facility, all at once.
That combination changes what a downtime solution has to do. It also changes how healthcare organizations should plan, test, and communicate. The CMS Emergency Preparedness Rule already expects facilities to plan using an all-hazards approach. Downtime preparedness belongs inside that planning, not beside it.
How Disaster-Driven Downtime Differs
- Multiple failures at once. Power, network, and the EHR may be unavailable together, so any plan that assumes one working system to lean on is fragile
- Longer duration. Restoration depends on utility crews, road access, and vendor logistics, not only on your IT team
- Reduced and unpredictable staffing. Employees may be dealing with damage at home, blocked roads, or evacuation orders
- Patient surge or evacuation. Weather and disasters can drive volume up quickly, or require moving patients out
- Communication limits. Cell and landline service may be degraded or overloaded
- Physical risk to equipment. Flooding, wind, and heat can damage workstations and printers directly
Power Comes First
Electronic downtime tools are useless without electricity.
- Confirm which circuits in each clinical area are on emergency power, and that downtime workstations and wristband printers are plugged into them. Our post on what happens to downtime workstation data after a full facility power outage covers the details
- Include downtime equipment in generator and UPS testing, not just in IT inventory
- Know how long generators can run on available fuel and what the refueling plan is
- Plan for battery life on any laptops or tablets used as supplementary devices
- Keep spare label and wristband stock and consumables in protected storage
Connectivity and Data Location
Disasters often damage connectivity first. Ask specific questions about your downtime solution’s design.
- Does it function without internet access?
- Where is patient data stored, and does it remain available if the wider network is down?
- What is the plan if the local network is partially damaged?
dbtech’s on-premise design stores synchronized patient data locally, so the workstations do not depend on a cloud connection to display what was current before the event. For events that physically damage a facility, also ask how you would recover data and operations if equipment is lost, and discuss options with your dbtech team. For the broader risk of simultaneous failures, see our FAQ on what happens when both the EHR and the backup system have problems.
Last-Resort Resources
A printed fallback matters more in a disaster than in any other scenario.
- A printed census and key safety information for each unit, refreshed at the start of every shift
- Printed procedure cards and downtime forms for the highest-priority workflows
- Paper wristbands and labels that can be used if all printers are down
- Clear rules for who updates the binders and when
Staffing and Roles
- Define how essential downtime roles are covered if the usual people cannot reach the facility
- Make sure someone who has used the system is on hand each shift. Cross-train more than one person per department
- Include agency and traveler orientation in your disaster plan, because surge staffing often means unfamiliar faces
- Use the roles and structure in our post on building a downtime command center, and extend the roster to include emergency management and facilities leaders
Surge, Evacuation, and Transfers
- Pre-size the downtime encounter number bank for surge volume, not just normal volume. Our FAQ on downtime during surge capacity operations discusses this
- Prepare a short triage and registration form built for speed during mass arrivals
- For evacuation, decide in advance what information travels with each patient: identity, medications, allergies, diagnoses, code status, and contact details
- Keep a log of where each patient went, so records and billing can be reconciled later
- Coordinate with receiving facilities on how documents will be exchanged
Our post on accurate patient identification during downtime explains why identification deserves special care when patients arrive in volume or are moved.
Communication During the Event
- Use channels that do not depend on the EHR or the building network, and have more than one
- Pre-write patient and family messages for common scenarios
- Define when external parties, such as payers, regulators, and emergency management agencies, are notified
- Follow the structure in our guide to creating a downtime communication plan
Recovery and Reconciliation
- Expect a larger backlog than a typical outage, and a longer duration
- Begin reconciliation planning during the event. Our post on reconciling downtime data back into the EHR provides the sequence
- Capture documentation that may be needed for insurance claims, regulatory reviews, and any emergency-related reimbursement
- Hold a structured after-action review, using the format in our post on writing a downtime after-action report that improves your program
Planning and Testing
- Start from your facility’s hazard vulnerability assessment. Which hazards are most likely where you are located: hurricanes, floods, wildfires, winter storms, earthquakes, tornadoes?
- Walk the downtime plan through the top two or three hazards, step by step
- Use planned maintenance windows for part of the practice, and tabletop exercises for the rest. A realistic scenario with power loss and reduced staffing reveals gaps routine drills miss. See our tabletop exercise guide
- Coordinate with local emergency managers and health coalitions. Resources such as FEMA’s national preparedness guidance and ASPR TRACIE offer planning tools for healthcare facilities
- Monitor forecasts through the National Weather Service so that preparation, such as printing updated binders and verifying generators, begins before a storm arrives
A Short Pre-Season Checklist
- Workstations and printers on emergency power and tested
- Consumables stocked
- Printed binders current and in place
- Encounter number bank sized for surge
- Staff roles and backups confirmed
- Communication channels tested
- Evacuation and transfer forms ready
- Contacts for vendors, utilities, and emergency management verified
To review how your downtime solution fits an all-hazards plan, schedule a Downtime Audit Assessment or contact our team.