HICS

# HICS- Hospital Incident Command System

# Background
HICS is a comprehensive incident management system intended for use in both emergent and non-emergent situations. It provides hospitals of all sizes with tools needed to advance their emergency preparedness and response capabilityboth individually and as a member of the broader response community.

# Introduction to the Hospital Incident Command System
HICS is based upon the Hospital Emergency Incident Command System (HEICS), which was created in the late 1980s as an important foundation for the more than 6,000 hospitals in the United States in their efforts to prepare for and respond to various types of disasters. In developing the fourth edition of HEICS, the value and importance of using an incident management system to assist as well with daily operations, preplanned events, and non-emergent situations became apparent. Thus, the HICS was created as a system for use in both emergent and non-emergent situations, such as moving the facility, dispensing medications to hospital staff, or planning for a large hospital or community event.
HICS was developed by a National Work Group of twenty hospital subject-matter experts from across the United States. In addition to the contributions of the National Work Group, ex officio members were included to ensure consistency with governmental, industrial, and hospital accreditation planning efforts and requirements.

# Overview of the Principles of the Incident Command System
ICS is designed to:
- Be usable for managing all routine or planned events, of any size or type, by establishing a clear chain of command
- Allow personnel from different agencies or departments to be integrated into a common structure that can effectively address issues and delegate responsibilities
- Provide needed logistical and administrative support to operational personnel
- Ensure key functions are covered and eliminate duplication
The incident planning process takes place regardless of the incident size or complexity. This planning involves six (6) essential steps:
- Understanding the hospitals policy and direction
- Assessing the situation
- Establishing incident objectives
- Determining appropriate strategies to achieve the objectives
- Giving tactical direction and ensuring that it is followed (e.g., correct resources assigned to complete a task and their performance monitored)
- Providing necessary back-up (assigning more or fewer resources, changing tactics, et al.)

# National Incident Management System Compliance for Hospitals
The Homeland Security Presidential Directive-5 (HSPD-5), issued by President George W. Bush in February 2003, created the National Incident Management System (NIMS). Until NIMS, there had been no standard for domestic incident response that united all levels of government and all emergency response agencies. The NIMS is designed to provide a framework for interoperability and compatibility among the various members of the response community. The end result is a flexible framework that facilitates governmental and nongovernmental agencies working together at all levels during all phases of an incident, regardless of its size, complexity, or location.

# The Hospital Emergency Management Program
The Emergency Operations Plan (EOP) outlines the hospitals strategy for responding to and recovering from a realized threat or hazard or other incident. The document is intended to provide overall direction and coordination of the response structure and processes to be used by the hospital. An effective EOP lays the groundwork for implementation of the Incident Command System and the needed communication and coordination between operating groups. The essence of the process includes the following steps:
- Designating an Emergency Program Manager Program
- Establishing the Emergency Management Committee
- Developing the all hazards  Emergency Operations Plan
- Conducting a Hazard Vulnerability Analysis
- Developing incident-specific guidance (Incident Planning Guides)
- Coordinating with external entities
- Training key staff
- Exercising the EOP and incident-specific guidance through an exercise program
- Conducting program review and evaluation
- Learning from the lessons that are identified (organizational learning)

# The Hospital Incident Command System
HICS incident management team charts depict the hospital command functions that have been identified and represent how authority and responsibility are distributed within the incident management team.
The activities at the Hospital Command Center (HCC) are directed by the Incident Commander, who has overall responsibility for all activities within the Hospital Command Center (HCC). The Incident Commander may appoint other Command Staff personnel to assist.
Many incidents that likely will occur involve injured or ill patients. The Operations Section will be responsible for managing the tactical objectives outlined by the Incident Commander. Branches of this section include: Department Level, Patient Care, Infrastructure, Business Continuity, Security, and HazMat.
The Planning Section will collect, evaluate, and disseminate incident situation information and intelligence to Incident Command and includes a Resources Unit, Situation Unit, Documentation Unit, and Demobilization Unit. Support requirements will be coordinated by the Logistics Section, and the Finance/Administration account for the costs associated with the response.
Also, several additional incident command principles and practices are covered in this section, including incident command staff identification, building incident command staff depth, job action sheets, and incident response guides.

# Life Cycle of an Incident
The life cycle of an incident includes the following steps:
- Alert and notification
- Situation assessment and monitoring
- EOP Implementation
- Establishing the HCC
- Building the ICS structure
- Incident action planning
- Communications and coordination
- Staff health and safety
- Operational considerations
- Legal and ethical considerations
- Demobilization
- System recovery
- Response evaluation and organizational learning

# Implementation