ISO 7101:2023 Emergency Preparedness and Response Procedure Template and Guide

ISO 7101:2023 Emergency Preparedness and Response Procedure Template and Guide

$149
A complete, worked ISO 7101:2023 contingency and emergency response procedure for a healthcare organization. Discharges all eight obligations of Clause 8.2.2 plus the information system contingency requirement at Clause 7.5.4 f) that sits in no procedure at most hospitals. Covers fire detection and containment, power and water backup stated in hours of service, medical gas pipeline integrity and verification before return to clinical use, nutrition and water for survival, evacuation of service users who cannot leave unaided, and outbreak, civil unrest and conflict measures. 36 pages, editable Word format, with a plain-language Start Here sheet, a process interaction map, an event record, six logs including an offline ward dependency list, a ward card, two worked examples and an eight-element maturity ladder.

Clause 8.2.2 is not an emergency plan. It is a continuity plan.

ISO 7101:2023 opens Clause 8.2.2 with its purpose: in order to ensure continuation of its services. That phrase governs the eight obligations beneath it. They are not eight ways to respond to an emergency. They are eight ways a healthcare organization keeps delivering care when something it depends on has failed.

This is what separates a hospital contingency procedure from an industrial emergency plan. An industrial site can stop production and evacuate. A hospital has ventilated patients, operating rooms in use, and a dialysis unit mid-treatment. Stopping is itself a clinical risk, and most of the people in the building cannot leave unaided.

This is a complete Clause 8.2.2 procedure discharging all eight obligations, plus the information system continuity requirement at Clause 7.5.4 f). Thirty-six pages, editable Word format, with a worked fictional hospital throughout.

Three things in this that are in almost nothing else

1. The obligation that sits in no procedure at all

Clause 7.5.4 f) requires the information management system to have contingency plans so that services are not disrupted. It is a named requirement, and in most organizations it lives nowhere. It is not in the emergency plan, because that plan is about the building. It is not in the IT policy, because that policy is about backups and recovery time rather than about how a nurse gives the right medication to the right patient with no record system.

Section 6.13 closes it with ten questions, including which clinical services stop entirely without the record, how allergies and current medication are known on paper, who declares downtime and recovery, and how a cyber incident differs from a technical outage — because the restore may reintroduce the problem and the outage may run days rather than hours.

The intersection nobody models. The ward list of who cannot move unaided normally lives in the electronic record — which is exactly what is unavailable in a fire, a flood, or a ransomware incident. Appendix B.4 makes it an offline ward-level record with a refresh interval. It is the single most valuable page in this procedure.

2. Medical gases, written to the detail the clause actually demands

Clause 8.2.2 e) is the most prescriptive obligation in the standard’s contingency requirements. It names color coding of pipelines, pipeline material, connectors, leak detection systems and alarms, and requires adequate backup. This procedure covers each, with reserve capacity stated in hours at expected and at surge demand, zone valve locations known to clinical staff rather than only to facilities, and — the control that matters most — verification and certification before any pipeline is returned to clinical use after maintenance or building work.

3. Backup capacity stated in hours, not described as adequate

Clause 8.2.2 d) requires backup arrangements for continuous and uninterrupted power supply, and Clause 8.2.1 h) requires the same for potable water. This procedure asks for the figures: generator run time at full load on the fuel held, the refueling trigger and supplier, what covers the gap between mains loss and generator start, water reserve in hours of service, and which clinical services fail first without water. It also asks the question most plans omit — what happens if the generator does not start.

What’s included

  • Complete Clause 8.2.2 procedure — 36 pages, editable Word format
  • Start Here front sheet — one page in plain language covering what the document is, what you must decide, what to do first, and what to do with the finished file
  • All eight lettered obligations mapped to the section that delivers each, plus Clause 7.5.4 f), with a full cross-reference including 8.2.1 f) h) k) l), 8.2.3, 8.1 and 6.1.3
  • Process interaction map at Section 9.0 with an interface detail table
  • Event list covering natural, human-caused, infrastructure, supply and workforce categories, with an applicability column to complete for every row including the ones you rule out
  • Life safety priority order for when several systems fail at once
  • Fire detection, abatement and containment including the two failures that defeat compartmentation invisibly — wedged fire doors and unsealed service penetrations after contractor work
  • Power and water sections built around figures rather than assurances
  • Medical gas section with verification before return to clinical use
  • Nutrition and water for survival covering service users and workforce, including enteral feed and infant formula, which have longer resupply lead times than ordinary food
  • Evacuation section covering defend in place, horizontal, vertical and transfer, with the order of movement decided on clinical grounds in advance
  • Outbreak, civil unrest, armed conflict and extreme weather measures
  • Drill program including generator load test, medical gas alarm exercise, information system downtime drill and an out-of-hours scenario
  • Exception paths for when the backup also fails, and when moving a patient is more dangerous than staying
  • Records table with no blanks, retention set against your regulatory requirement rather than the standard
  • Maturity ladder — eight healthcare-specific elements, four levels each
  • Appendix A — event record with an eleven-question closing gate
  • Appendix B — six logs including contingency capability figures, the offline ward dependency list, and an information system downtime log
  • Appendix C — ward card for the nurses’ station plus two worked examples

Written to be read by the people who would use it. The front matter and the notes in this template are written at a plain reading level and checked against it. Clause language is kept where it is needed and nowhere else. A procedure that only the quality manager can read is a procedure that only the quality manager follows.

Who it’s for

Quality directors, facilities leads and emergency preparedness coordinators at hospitals, clinics and other healthcare organizations certified to ISO 7101:2023 or working toward it. Particularly useful where emergency planning sits with facilities and clinical continuity sits with nursing and nobody owns the space between them, and where the information system contingency requirement has not yet been placed in any procedure.

What you get out of it

  • Stop rewriting from a blank page. Backup thresholds, escalation, evacuation sequence, review triggers — already decided and explained.
  • Place the IT continuity obligation somewhere. Clause 7.5.4 f) is a named requirement and it is routinely unassigned. Section 6.13 assigns it.
  • Replace “adequate” with hours. Backup capacity written as a figure is auditable, actionable, and tells a charge nurse when to escalate.
  • Make the dependency list survive the outage. An evacuation without it is an evacuation done from memory.
  • Set retention against the right clock. Healthcare record retention periods almost always exceed anything ISO 7101 implies.

New to ISO 7101? Our ISO 7101 overview course covers the structure of the standard and what it asks of a healthcare organization.

Buying more than one procedure?

This template is also included in the full documentation packages, which bundle the procedure set for a standard at a lower cost per document:

Prefer to be invoiced? If your organization purchases by purchase order or requires an invoice, contact us at 760-434-9141 or toll-free 888-914-9141, or through msi-international.com, and we will raise one. Templates are delivered on receipt of payment.

Questions

Is this a template or a completed procedure?

A completed procedure. The decisions are already made and explained, with bracketed placeholders only where a value is genuinely yours to set — your test frequencies, your named roles, your retention periods. Every placeholder is a decision you must make, and the document says so. There are no blank records tables and no "TBD" entries.

Can I edit it and issue it under my own document number?

Yes. It is supplied in editable Word format and licensed for internal use at any number of your own sites. Replace the fictional organization with your own, insert your own document number, and issue it as a controlled procedure. Resale, redistribution, or use in consulting deliverables for third parties requires a separate consultant license — contact us if that is what you need.

Will this make us conformant on its own?

No, and no document can. A procedure is conformant when it reflects what your organization actually does and when the records it calls for exist. What this gives you is a structurally complete starting point, so the work is adapting decisions rather than inventing them from a blank page.

How is this different from a free template?

Most templates restate the clause. The standard says test the planned response; the template says "the planned response shall be tested." Nothing has been added. This one names the test types, states what each proves, requires findings to be recorded including what did not work, and explains why a test record with no findings is worth less than no record at all.

What format is it delivered in?

Microsoft Word (.docx), fully editable, with the header and footer document control blocks already built. Download is immediate on purchase.

About MSI

Management Systems International, LLC is a veteran-owned and female-owned ISO consulting firm, co-founded in 1998. Across 28 years we have supported 80+ certifications, attended 200+ audits, and trained 600+ professionals. These templates encode what recurs across those audits — not one organization's approach generalized, but the structural patterns that show up again and again.

msi-international.com · 760-434-9141

© 2026 Management Systems International, LLC · All rights reserved. ISO standards are the copyright of the International Organization for Standardization. Clause numbers and titles are cited for reference; this template does not reproduce the text of any standard and is not a substitute for your own licensed copy.