Hazard and Disaster Planning

Committee

Meeting
Oct 3, 2011
Agenda of Meeting
Review status of current Strategic Emergency
Management Plans (SEMP)
Review all-hazards analysis results; develop
list of strategic priorities for EMPs
Slides to review Incident Command System
approach to emergency management
Designate 2 groups to address Mass Casualty
SEMP and Incident Command Plan
Review of Current Emergency
Management Plans
What plan do you have if a newborn is
stolen from the nursery? Who is called?
What do they do?
What do you do if a you receive a bomb
threat in your hospital? What if a bomb
exploded in the lobby? Who is called?
What if they are not able to be reached?
Results of All-Hazards Risk
Analysis for Siloam
1) Internal Fire 0.60 (0.13-1.00)
2)Electric Failure 0.56 (0.30-0.72)
3)Bomb Threat 0.49 (0.20-0.72)
4)Earthquake 0.47 (0.26-0.67)
5)Terrorism, biological 0.38 (0.00-0.72)
6)Wild Fire 0.37 (0.00-0.72)
7)Generator Failure 0.35 (0.13-0.52)
8)Fire Alarm Failure 0.29 (0.06-0.37)
Results of All-Hazards Risk
Analysis For Siloam
9)Communication Failure 0.28 (0.17-0.37)
10)Hostage Situation 0.26 (0.19-0.44)
11)Large Internal Spill 0.25 (0.00-0.22)
12)Small-medium sized internal spill 0.24
(0.00-0.22)
13)Infant abduction 0.23 (0.00-0.44)
14)Labor action 0.22 (0.11-0.39)
15)Structural Damage 0.21 (0.00-0.28)

Results of All-Hazards Risk
Analysis for Siloam
16)Information systems failure 0.21
(0.06-0.52)
17)Transportation failure 0.20 (0.11-0.41)
18)Radiological exposure , internal 0.19
(0.07-0.22)
19)VIP situation 0.18 (0.09-0.44)
20)Supply shortage 0.17 (0.11-0.48)
21)Mass Casualty Incident( trauma) 0.16
(0.02-0.22)

Results of All-Hazards Risk
Analysis for Siloam
22)Medical Gas failure 0.15 (0.11-0.26)
23)Mass Casualty Incident (medical/
infectious) 0.15 (0.04-0.22)
24)Civil disturbance 0.14 (0.13-0.44)
25)Epidemic 0.14 (0.02-0.44)
26)Hurricane 0.13(0.00-0.31)
27)HVAC failure 0.12 (0.00-0.37)
28)Drought 0.11 (0.00-0.19)
Results of All-Hazards Risk
Analysis for Siloam
29)Flood , internal 0.10 (0.09-0.24)
30)Water failure 0.10 (0.00-0.22)
31)Tornado 0.09 (0.00-0.22)
32)Radiological exposure , external 0.08
(0.00-0.22)
33)Severe thunderstorm 0.07 (0.00-0.24)

Brief Overview of Incident
Command System
Incident Command System (ICS)
Based on the National Incident
Management System (NIMS)
It allows a coordinated response from
various departments and groups within
Siloam, as well as outside the organization
Establishes common processes for planning
and management of resources
ICS
An all-hazards approach to handling of
threats and disasters
Flexible for any type of hazard or disaster,
and can expand or contract as needed
The information presented is based on the
FEMA IS100HC course
ICS History
Started in the 1970s when fires in
California caused much damage and killed
many people
Found to be in large part preventable and
due to lack of coordination, and using
resources where they were needed
NIMS Components
NIMS is made up of these key components:
Preparedness
Communications and Information Management
Resource Management
Command and Management
Ongoing Management and Maintenance

NIMS Command and
Management Component
Weaknesses of the old System
Lack of accountability
Poor communication systems and common
terminology
Lack of a systemic planning process
No common, flexible, management structure that
delegates and manages efficiently
No predefined interagency methods of coordination

ICS is built on over 30 years of
Experience
Helps to ensure:
Safety of members, visitors, patients
Achievement of objectives
Efficient resource utilization
ICS is Used for All-Hazards
Used in all hazards
Natural Hazards
Fires, floods, earthquakes, tsunamis, epidemics
Technological Hazards
Radiological or chemical spills, power failures, medical device
failures
Human-caused Hazards
Bomb threats or other terrorist acts, civil disturbances
Used for every incident, even small ones
ICS Principles
Requires common terminology
Clarity of command: Incident Commander
Chain of command is clear, with only 1 ICS
commander
Management by objectives
Incident Action Plan (IAP)
Specifies incident objectives
States objectives to be completed
Timeframe called operational period

ICS Principles
Span of control
Depending on the incident, the ICS can contract or
expand
The supervisor should oversee 3 to 7 people, with a
ratio of 1 supervisor to 5 divisions recommended
When more resources require supervision, they should
be grouped and headed by another supervisor

ICS Principles
Incident Resources
It is critical to know what resources you have, where
they are, when they are available

ICS Principles
Incident Locations
The Incident Commander identifies where operational
locations and support facilities are to be located.
The Incident Command Post is best kept away from
day-to-day work setting to avoid distractions

ICS Principles
Integrated Communications
Response partners should be able to communicate and
operate together
It may be as simple as having the same vocabulary, or
having a current list of phone numbers to key players

Review of ICS Accountability
All responders must check in to receive their
assignments
Incident Action Plan (IAP): response must be
coordinated based on the IAP
Unity of command: Each individual is assigned to
only 1 supervisor
Span of control: Supervisors oversee their
subordinates (2-7 with average of 5)
Resource Tracking: Supervisors must track and
record resource status

Incident Management Functions
Five major functions:
Command
Sets the incident objectives, strategies, and priorities and has overall
responsibility for the incident
Operations
Conducts operations to reach the incident objectives. Establishes tactics
and directs all operational resources
Planning
Supports the incident action planning process by tracking resources,
collecting/analyzing information, and maintaining documentation
Logistics
Arranges for resources and needed services to support achievement of the
incident objectives
Finance and Administrations
Incident Commander
The Incident Commander is responsible for all
operations until he/she delegates the functions and
are as follows
Command
Operations
Planning
Logistics
Finance and Administration
Modular ICS Organization
ICS can create and delegate sections as needed based
on the incident
Incident Commander (IC)
Needs to be qualifies in Incident Command
operations
Deputy Incident Commanders need to be trained
and available if the Incident Commander needs to
assume the IC position. Transfer of operations
needs to be done verbally or in writing
General Staff
The Incident Commander can establish any of the
following 4 sections:
Operations Section
Develops and implements strategy and tactics to
carry out the incident objectives.
Organizes, assigns, and supervises the tactical
response resources.
Planning Section
The major activities of the Planning Section may
include:
Collecting, evaluating, and displaying incident intelligence
and information.
Preparing and documenting Incident Action Plans.
Tracking resources assigned to the incident.
Maintaining incident documentation.
Developing plans for demobilization.
Logistics Section
The Logistic Section Chief helps make sure that
there are adequate resources (personnel, supplies,
and equipment) for meeting the incident objectives.
Ordering, obtaining, maintaining, and accounting
for essential personnel, equipment, and supplies.
Providing communication planning and resources.
Setting up food services for responders.
Setting up and maintaining incident facilities.
Providing support transportation.
Providing medical services to incident personnel.
Finance/Administration Section
The Finance/Administration Section is responsible
for:
Contract negotiation and monitoring.
Timekeeping.
Cost analysis.
Compensation for injury or damage to property.
Documentation for reimbursement (e.g., under mutual aid
agreements and assistance agreements).
Brief Review Of ICS
We now need to develop the Siloam ICS,
with standard operating procedures, and
training for ICs and other members
Different Emergency
Management Plans (EMP)
Based on the All-Hazard Risk Analysis for
Siloam, we now have a list of hazards we
need to address
We will start with Mass Casualty
Emergency Plan for Siloam
A Working Group will be formed to create
and train for Mass Casualties
Agenda for next meetings
ICS Group Meeting
Review more ICS information and discuss
current threats and opportunities
Develop a list of possible Incident
Commanders for initial training
Discuss framework of ICS
Mass Casualty Workgroup
Review current mass casualty SOPs
Discuss and review other mass casualty
plans
Outline further plans for development of
Siloam mass casualty SOP
Thank you for your participation
and input