Study guide
7.2 Emergency Preparedness & NIMS
FACHE Board of Governors Exam in Healthcare Management Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 About the FACHE Credential 1.2 Current Exam Facts 1.3 Eligibility, Application & Recertification
2 Healthcare Systems & Trends
2.1 Healthcare and Medical Terminology 2.2 Healthcare Trends 2.3 Continuum of Care Levels
3 Healthcare Organizations & Services
3.1 Levels of Service from a Business Perspective 3.2 Types of Healthcare Organizations 3.3 Ancillary and Support Services
4 Integration, Clinicians & Staff Perspectives
4.1 Integration, Competition & Partnerships 4.2 Clinician Roles and Qualifying Criteria 4.3 Staff Perspectives & Evidence-Based Management
5 Patient Perspective & Care Delivery
5.1 Patient vs Provider Perspective 5.2 Access, Quality, Cost & Community 5.3 Care Delivery Models and Access Points
6 Digital Health, Population Health & Prevention
6.1 Digital Health 6.2 Population Health Concepts 6.3 Social Determinants & Preventative Medicine
7 Management Planning & Organizational Systems
7.1 Implementation Planning 7.2 Emergency Preparedness & NIMS 7.3 Organizational Systems & Management Functions
8 Leadership, Teams & Change
8.1 Leadership and Communication Styles 8.2 Team-Building Techniques 8.3 Change Management & Organizational Development
9 Collaboration, DEIJ & Networks
9.1 Stakeholder Collaboration 9.2 DEIJ & Resource Allocation 9.3 Network Structures & Collective Bargaining
10 Financial Accounting & Budgeting
10.1 Financial Accounting and Ratios 10.2 Operating Budgets 10.3 Capital Budgeting
11 Reimbursement, Productivity & Controls
11.1 Reimbursement Methodologies 11.2 Productivity Measures 11.3 Financial Controls
12 Revenue, Business Cases & Capital Finance
12.1 Revenue Generation and Payer Mix 12.2 Business Cases & Financial Decision Impacts 12.3 Asset Management & Financing
13 Philanthropy, Supply Chain & Revenue Cycle
13.1 Philanthropy and Foundations 13.2 Supply Chain Management 13.3 Revenue Cycle
14 HR Laws, Recruitment & Staffing
14.1 HR Laws and Regulations 14.2 Recruitment and Retention 14.3 Staffing Methodologies
15 Performance, Engagement & Compensation
15.1 Performance Management Systems 15.2 Motivation, Development & Engagement 15.3 Compensation and Benefits
16 Workplace Safety, Conflict & Labor Relations
16.1 Employee Safety, Security & Health 16.2 Conflict, Grievances & Selection 16.3 Labor Relations & HR Decision Impacts
17 Job Design, Succession & Coaching
17.1 Job Design 17.2 Succession Planning, Mentorship & Coaching
18 Confidentiality, Compliance & Payment Rules
18.1 Confidentiality and Privacy Laws 18.2 Healthcare Compliance Laws 18.3 Medicare, Medicaid & Third-Party Payment Regulations
19 Accreditation, Patient Rights & Ownership Rules
19.1 Accreditation & Inspection Standards 19.2 Patients' Rights Laws 19.3 Nonprofit vs For-Profit Requirements
20 Regulatory Impacts, Labor Law & M&A
20.1 Regulatory Impact on Executive Decisions 20.2 Collective Bargaining Laws 20.3 Legal Implications of Mergers & Acquisitions
21 Benchmarking, Peer Review & Risk
21.1 Benchmarking & Best Practices 21.2 Medical Staff Peer Review 21.3 Risk Management Programs
22 Improvement Methods & Measurement
22.1 PDSA, Lean & Six Sigma 22.2 Clinical Performance Improvement & Pathways 22.3 Quality Measurement & HCAHPS
23 Utilization, Patient Safety & Quality Impacts
23.1 Utilization Review & Case Management 23.2 Patient Safety Tools 23.3 How Quality Impacts Operations
24 Strategic Planning, Business Planning & Contracts
24.1 Strategic Planning Process 24.2 Business Planning for Services 24.3 Business Contracts
25 Socioeconomic Context, Marketing & Media
25.1 Socioeconomic Environment 25.2 Marketing Principles 25.3 Media, Social Media & Community Relations
26 Negotiation & Business Decision Impacts
26.1 Contract Negotiation 26.2 Business Decision Impacts
27 Health IT Operations, Trends & Regulation
27.1 IT in Business Operations 27.2 Technology Trends & Clinical Applications 27.3 HIPAA Security, HITECH & Interoperability
28 Informatics, IT Impacts & Continuity
28.1 Health Informatics for Operational Decisions 28.2 IT Decision Impacts 28.3 Information Systems Continuity
29 IT Acquisition & Analytics
29.1 IT Selection, Acquisition & Maintenance 29.2 Healthcare Analytics & Clinical Informatics
30 ACHE Ethics, Patient Rights & Ethics Committees
30.1 ACHE Code of Ethics 30.2 Patients' Rights & Responsibilities 30.3 Ethics Committees
31 Diversity, Conflicts of Interest & Research Ethics
31.1 Cultural & Spiritual Diversity 31.2 Conflict of Interest 31.3 Unethical Actions & Human-Subject Research
32 Professional Norms, Ethical Culture & Diversity Statement
32.1 Professional Norms & Standards 32.2 Creating an Ethical Culture 32.3 ACHE Statement on Diversity
33 Governance Theory, Structure & Medical Staff
33.1 Governance Theory 33.2 Governance Structure & Operations 33.3 Medical Staff Structure
34 Board Accountability & Public Policy
34.1 Board Role, Accountability & Fiduciary Duty 34.2 Public Policy & Advocacy
7.2 Emergency Preparedness & NIMS
Key Takeaways Explain This Topic AI
Contingency and emergency planning prepare the organization for disruptions—natural disasters, mass casualty, cyber events, infectious disease, utility failure, and supply shocks
NIMS (National Incident Management System) provides a standardized U.S. framework for incident command, common terminology, modular organization, and multi-agency coordination
Hospital Incident Command System (HICS) adapts ICS concepts to healthcare facilities with defined roles, job action sheets, and scalable response structure
Preparedness includes hazard vulnerability analysis (HVA), emergency operations plans, training/exercises, continuity of operations, and after-action improvement
Executives own resource readiness, command authority clarity, communications, surge capacity, and recovery—not only a written binder for surveyors
Last updated: August 2026
Emergency Preparedness & NIMS
Quick Answer: Contingency planning prepares the organization for credible disruptions; emergency preparedness and response mobilize people, command structures, and resources when events occur. In the United States, the National Incident Management System (NIMS) defines standardized incident management concepts that healthcare organizations use—often through Hospital Incident Command System (HICS) —to coordinate internally and with external agencies. FACHE ML2 tests executive fluency with this framework, not firefighter tactics.
Healthcare executives are accountable for keeping care available under stress: hurricanes, wildfires, floods, mass casualty incidents, active threat events, pandemics, ransomware, prolonged power or water failure, and critical supply shortages. Accreditation (e.g., CMS Emergency Preparedness Rule requirements for participating providers, Joint Commission emergency management standards) and community expectation make preparedness a governance and leadership duty.
Contingency Planning vs. Routine Operations
Contingency planning anticipates events that would force the organization off its normal operating plan. It defines triggers, alternative procedures, resource reallocations, communication pathways, and decision authority when standard processes cannot meet demand or safety requirements.
Related concepts executives should separate cleanly:
- Concept Focus
- Emergency operations plan (EOP) All-hazards framework for response and recovery
- Continuity of operations (COOP) Maintain mission-essential functions during disruption
- Business continuity / disaster recovery (IT) Systems, data, and applications recovery
- Surge plan Expand capacity for patients, space, staff, supplies
- Crisis standards of care Ethical, legal, and clinical framework if resources are overwhelmed
Trap: Equating “we have a binder” with preparedness. Plans that are untrained, unexercised, or unknown to leaders fail under stress. Preparedness is a capability , not a document.
Hazard Vulnerability Analysis (HVA)
Most healthcare emergency management programs begin with a hazard vulnerability analysis : ranking hazards by probability, magnitude, and preparedness/mitigation gap. HVAs are typically multidisciplinary (clinical, facilities, security, IT, supply chain, emergency management, community partners) and updated periodically and after major events.
HVA outputs drive:
- Mitigation investments (generators, redundant utilities, cybersecurity controls, stockpiles)
- Training and exercise priorities
- Community partnership focus (public health, EMS, regional hospitals, emergency management agencies)
- Capital and operating budget requests tied to residual risk
Executives should ensure HVA results influence real resource allocation , not only survey documentation.
NIMS: Why Standardization Matters
The National Incident Management System (NIMS) , managed under FEMA/DHS policy frameworks, is the national approach for enabling government, private sector, and nongovernmental partners to work together to prevent, protect against, mitigate, respond to, and recover from incidents. Healthcare organizations adopt NIMS concepts so they can plug into multi-agency responses with shared language and structure.
Core NIMS ideas high-yield for executives:
Common Terminology
Standard terms reduce confusion across agencies. Using idiosyncratic local titles for command roles during a regional mass casualty event creates dangerous ambiguity.
Modular, Scalable Organization
Incident organization expands and contracts with incident complexity. A small internal utility outage may need a limited command structure; a multi-day regional disaster activates full sections and external liaison.
Chain of Command and Unity of Command
Personnel report to one designated supervisor within the incident structure to avoid conflicting orders. This principle becomes critical when clinical leaders, executives, and external agencies all feel urgency to direct staff.
Unified Command
When multiple agencies or jurisdictions share management responsibility, unified command allows joint objectives without collapsing into chaos. Hospitals may participate with public health, EMS, fire, law enforcement, and emergency management.
Incident Action Planning
Responses run on operational periods with objectives, strategies, resource assignments, and communications—documented in incident action plans as complexity warrants.
Integrated Communications and Information Management
Common communications plans, interoperable systems where possible, and disciplined information flow (what is known, what is rumor, what is decision-relevant) are NIMS expectations. Executives own rumor control and public information coordination.
Resource Management
Typing, inventory, ordering, and demobilization of resources (staff, equipment, teams) follow structured processes—especially important for mutual aid and regional sharing.
Incident Command System (ICS) and HICS
The Incident Command System (ICS) is the on-scene management structure within NIMS. Healthcare facilities commonly use Hospital Incident Command System (HICS) (or analogous healthcare ICS models) that map ICS roles to hospital functions.
Typical command and general staff concepts:
Incident Commander (IC) — overall responsibility for incident management at the facility/response level; may be an administrator on call or designated emergency manager depending on plan design and incident type
Public Information Officer (PIO) — external/internal messaging; media and often family information coordination
- Safety Officer — safety of responders and operations
- Liaison Officer — agency coordination
- Operations Section — tactical medical/care delivery and related operations
- Planning Section — situation status, documentation, resource tracking, action planning
- Logistics Section — support (supplies, food, transportation, staff support)
- Finance/Administration Section — cost tracking, claims, emergency purchasing authorities
Job action sheets define role duties so responders can assume positions under stress. Command centers (Hospital Command Center / Emergency Operations Center) provide physical or virtual hubs for coordination.
Executive nuance: The CEO may or may not be the Incident Commander for every event. What matters is pre-designated authority , 24/7 activation pathways, and clarity that clinical care continuity and organizational authority are aligned. Executives still remain accountable for policy, resource commitment, external representation, and recovery decisions.
Preparedness Cycle: Plan, Train, Exercise, Improve
A durable program follows a continuous cycle:
- Organize and equip — roles, supplies, communications tools, MOUs/mutual aid
- Plan — EOP, annexes (evacuation, pandemic, cyber, active threat), continuity plans
- Train — role-specific and general staff awareness; NIMS/ICS familiarity for key personnel
- Exercise — tabletop, functional, and full-scale exercises; include community partners when feasible
- Evaluate and improve — after-action reports (AARs) and improvement plans with owners and due dates
CMS and accreditation expectations generally require emergency plans, policies for communication, resources/assets, safety/security, staffing, utilities, and patient/clinical support activities—plus training and testing. Executives should know their organization’s compliance obligations and the evidence surveyors will seek (plans, drills, AARs, training records).
Surge Capacity, Capability, and Medical Surge
Surge capacity is the ability to expand care for a volume increase; surge capability addresses specialized care needs (e.g., burn, pediatric, behavioral health, highly infectious disease). Strategies include:
- Canceling electives and converting space
- Altered staffing models and credentialing of volunteers/disaster privileges when lawful
- Cache and just-in-time supply strategies
- Load-balancing transfers across a region
Crisis standards of care only when conventional and contingency strategies are insufficient—and under ethical/legal frameworks with appropriate authority
Executives must pre-think legal, ethical, and communication dimensions of triage and resource allocation; improvising ethics under media glare is a leadership failure mode.
Continuity: People, Plant, Technology, Supply Chain
Modern healthcare emergencies are often non-meteorological :
Cybersecurity incidents can halt EHRs, labs, imaging, and revenue cycle; downtime procedures and offline clinical workflows are emergency management
Supply chain shocks (drugs, PPE, devices) require substitution protocols and conservation strategies
Utility failures need generator testing, fuel contracts, water contingency, and HVAC strategies for infection control
Workforce shocks (illness, transportation failure, childcare collapse in community disasters) require labor pools and dependency planning
Business continuity for IT and revenue cycle should be integrated with the EOP—not owned in a disconnected silo the command center cannot see.
Communication and Stakeholder Coordination
During incidents, leaders manage multiple audiences: patients and families, staff, medical staff, board, regulators, media, and partner agencies. Principles:
- Single coordinated message via PIO/command structure
- Frequent updates even when facts are incomplete (“what we know / don’t know / next update time”)
- Staff communication to reduce rumor and absenteeism
- Documentation for later regulatory, legal, and improvement review
Community integration—healthcare coalitions, public health, EMS—determines whether a hospital is an island or a node in a resilient system.
Recovery and Organizational Learning
Response ends; recovery begins: demobilization, staff psychological support, facility restoration, financial recovery (including eligible cost tracking), restoration of elective services, and reputational repair. After-action review with honest findings and funded improvements is the bridge from one incident to better readiness for the next.
Exam-ready summary: Contingency/emergency planning is an executive system: HVA-driven priorities, NIMS-aligned command and multi-agency coordination, HICS role clarity, surge and continuity capabilities, trained and exercised plans, disciplined communications, and AAR-driven improvement. Documents support capability; they do not replace it.