Hospital Tabletop Exercise: Clinical Systems Downtime
A generic, reusable tabletop exercise template for hospitals and health systems. Run it on paper in about 90 minutes. Replace bracketed details to fit your organization. No real organization names are used.
This exercise is aligned to HIPAA Security Rule contingency-planning expectations and designed to support CMS Emergency Preparedness and Joint Commission emergency-management requirements. It does not by itself satisfy any regulation or ensure compliance.
Scenario summary
A routine overnight update to the electronic health record (EHR) fails, and the attempted rollback corrupts the system. Clinicians across the hospital lose access to records, orders, results, and medication administration records, and the outage is expected to last hours, not minutes. Care continues on paper while the organization manages patient safety, coordinates a single incident response, communicates with staff and families, and prepares to reconcile a day's worth of paper documentation back into the record once systems return.
Exercise objectives
- Activate clinical downtime procedures across every affected unit and confirm, unit by unit, that each has switched to paper workflows within the target time.
- Maintain safe medication ordering, results management, and patient identification during the outage, with a working process to surface and log near-misses.
- Stand up a single incident command structure and a defined decision cadence for "continue on downtime" versus "wait for restoration."
- Deliver accurate, consistent communication to staff, patients, and families, and manage external/media inquiries through one channel.
- Reconcile paper documentation into the EHR on recovery using a documented error-catching process, and identify any care gaps.
- Exercise the decision path for disclosing and reporting a potential patient-safety event linked to the outage.
Participants and roles
- Incident commander — senior operations or nursing executive who runs the response.
- IT / EHR incident lead — owns the technical picture and vendor coordination.
- Clinical informatics — bridges clinical workflow and the systems team.
- Nursing leadership / charge nurses — downtime procedures on the units.
- Pharmacy — medication ordering and verification on paper.
- Patient safety / risk management — near-miss capture, event review.
- Health information management — downtime documentation and later reconciliation.
- Communications / PR — staff, patient, family, and media messaging.
- Legal / compliance — disclosure, reporting, and regulatory questions.
- Facilitator — delivers injects, keeps time, captures decisions (not a participant).
Injects
T+0 — The EHR goes dark. Delivered to: IT on-call / help desk → incident lead. An overnight EHR update fails and the rollback corrupts the system. Clinicians can no longer open records, enter orders, or view results. Restoration time is unknown.
- Who do you notify first, and how do you reach clinicians who rely on the system right now?
- What is the trigger, and who has the authority, to declare a downtime event and stand up incident command?
- How do staff on the units learn that this is a real outage and not a local glitch?
T+20m — The units respond unevenly. Delivered to: nursing leadership / charge nurses. Some units have opened their downtime boxes and switched to paper; others are waiting for the system to "come right back." Two units cannot find current downtime forms.
- How do you confirm every unit has actually switched to paper, not just been told to?
- What do you do about units without usable downtime materials at hand?
- Who owns the running picture of which units are and are not operating safely?
T+45m — Medications and results pile up. Delivered to: pharmacy + patient safety officer. Medication orders and results are moving on paper and by phone. Pharmacy reports a verbal-order near-miss, and the emergency department is slowing as staff hand-carry information.
- How are medication orders being verified without the system's safety checks?
- How are near-misses being captured in real time so they are not lost once systems return?
- What gets prioritized if staff cannot keep up with the paper load?
T+1h30 — "Hours, not minutes." Delivered to: incident commander / IT lead. The vendor now says restoration is several hours away. Some units are running low on printed downtime forms, and staff fatigue is setting in.
- Does the response posture change now that this is a long outage rather than a brief one?
- What do you do about dwindling downtime supplies and tiring staff?
- When and how do you set expectations with the whole organization about duration?
T+3h — A safety event and an outside question. Delivered to: risk management + communications. A possible patient-safety event tied to the downtime is reported and is under review. Separately, a patient's family and a local reporter have begun asking what is going on.
- Who reviews the potential safety event, and on what timeline, while the outage continues?
- What can the organization say publicly and to families while facts are still unconfirmed?
- How do you keep one consistent message across the units, the front desk, and any spokesperson?
T+6h — Recovery is messy. Delivered to: health information management + clinical informatics. Systems begin to come back. Reconciling hundreds of paper orders and notes into the record surfaces transcription errors, and it is not yet clear everything will line up.
- How do you reconcile paper documentation into the EHR without introducing new errors?
- How do you know which patients were affected and whether any care was missed?
- Who signs off that the record is trustworthy again?
T+12h — A possible missed dose. Delivered to: patient safety + compliance + legal. Reconciliation suggests a medication dose was likely missed during the outage. The patient is stable. Leadership has to decide on clinical follow-up, disclosure to the patient, and any reporting.
- What is the clinical follow-up, and who owns telling the patient and family honestly?
- What internal and external reporting obligations apply, and who decides?
- What would make this outage a reportable or recurring risk, and how is that captured?
Contingency — The second outage. Delivered to: incident commander. Shortly after recovery is declared, a related component fails again and a subset of units drops back to paper, just as everyone had stood down.
- How do you re-mobilize staff who were just released?
- What does a second failure change about trust in the restoration and the vendor?
After-action checklist
- Time to declare a downtime event and stand up incident command, measured against target.
- Confirmation that every affected unit switched to paper workflows, and where that lagged.
- Downtime materials (forms, boxes, printed references) present, current, and sufficient on every unit.
- Medication and results safety: near-misses captured, verification steps held or broken.
- Single source of truth for outage status and a working decision cadence.
- Communication consistency across staff, patients, families, and external inquiries.
- Reconciliation process on recovery, including how care gaps were found and closed.
- Disclosure and reporting decisions documented, with owners and timelines.
Frequently asked questions
How long does this hospital tabletop exercise take?
About 90 minutes: seven timed injects across a multi-hour EHR outage, plus a contingency inject and a short debrief.
Who should take part?
The incident commander, the IT/EHR lead, clinical informatics, nursing leadership, pharmacy, patient safety, health information management, communications and legal. A facilitator runs the exercise and doesn't take part.
Does this exercise meet CMS or Joint Commission requirements?
It's designed to support CMS Emergency Preparedness and Joint Commission emergency management requirements, and aligned to HIPAA contingency-planning expectations. It doesn't by itself satisfy any regulation, so record it in your program alongside your other exercises.
Can we run it live instead of on paper?
Yes. Build it in Crewcible from this template, or start from a related library scenario such as White Screens. The facilitator releases each inject to participants' screens and captures every decision for the after-action report.