The Hospital Incident Command System (HICS): An Overview for Hospital Leaders

Vital Signs - Green Background

The Hospital Incident Command System (HICS) is an incident management system any hospital can use to manage threats, planned events, and emergencies. It gives the hospital a predictable command structure when normal operations stop working, and it is built on the same principles as the Incident Command System (ICS) that fire, EMS, and emergency management agencies use. That shared language is the point. When the hospital, the county, and the ambulance services all organize the same way, they can work together without stopping to translate.

We’ve worked with nearly a dozen hospital and health systems since we founded Bryghtpath in 2014. This overview covers what HICS is, what the current guidebook contains, how the team works, and where we see hospitals get it wrong.

What the Hospital Incident Command System Is

HICS dates to the late 1980s, when hospitals recognized they would benefit from an incident management system based on ICS principles. It was revised three times before 2014. The current version is HICS 2014, the Fifth Edition of the HICS Guidebook, published in May 2014 by the California Emergency Medical Services Authority (EMSA). The previous version was HICS IV in 2006. As of October 2026, 2014 is still the current edition.

The HICS 2014 Guidebook is available as a download, and the US Department of Health and Human Services’ ASPR TRACIE resource center also lists it. The guidebook is explicit about two things it is not. It is not a definitive text on hospital preparedness, and it is not your Emergency Operations Plan (EOP). Every hospital still needs its own all-hazards EOP. EMSA calls the guidebook and tools “living documents” that will change as hospitals report lessons learned.

HICS isn’t only for disasters. The guidebook encourages hospitals to use it for planned events and non-emergencies too, such as moving patients within the facility or running a mass flu vaccination clinic for staff. Every time you use it, your team gets a rep.

The Seven Fundamental Elements of HICS

The guidebook builds HICS on seven elements:

  1. A predictable chain of command with a suggested span of control.
  2. Accountability for each position and team function, including prioritized action checklists.
  3. A common language that makes communication with outside agencies easier.
  4. Scalability, so the same system works for any size hospital.
  5. A modular design that adapts to non-emergency incidents and events.
  6. Alignment with guidance from the National Incident Management System (NIMS) and accreditation agencies on hospital use of incident command principles.
  7. Management by objectives: evaluate the problem, build and carry out a plan to fix it, and assign the resources to do it.

One design choice surprises people. The HICS structure deliberately does not match the hospital’s daily org chart; the guidebook says this reduces confusion over roles and titles. It also fits what I tell every crisis team: the leader of the response should be the person best positioned to bring it to a successful conclusion, not automatically the one with the biggest title.

Old View New View
HICS is the binder we pull out for a disaster HICS is how we run every incident and planned event, so it’s familiar when the disaster comes
Fill every box on the chart Activate only the positions the incident needs
The most senior executive takes command The best-prepared leader takes command, and command transfers cleanly
HICS covers our emergency program HICS is one piece, alongside the EOP, business continuity, and IT disaster recovery
Customize the system to fit our culture Customize the details, keep the structure partners recognize

The Hospital Incident Management Team

HICS organizes the response through the Hospital Incident Management Team (HIMT).

The Incident Commander is the only position that is always activated. The Incident Commander manages the incident inside the hospital, runs the Hospital Command Center, sets the operational periods, and sets the strategies and priorities in the Incident Action Plan.

The Incident Commander can appoint Command Staff:

  • Public Information Officer, who coordinates information inside and outside the hospital, including the media.
  • Liaison Officer, the hospital’s main contact for outside agencies.
  • Safety Officer, who watches response operations and corrects unsafe practices.
  • Medical-Technical Specialists, with expertise such as infectious disease, legal affairs, risk management, or medical ethics.

Depending on the incident, the Incident Commander can also activate General Staff section chiefs for Operations, Planning, Logistics, and Finance/Administration. Operations manages the tactical work and carries out the Incident Action Plan, and it is usually the largest section.

The guidebook lists hospital roles that commonly fill each position. For Incident Commander, candidates include the administrator on call, the nursing supervisor, the chief operating officer, the chief medical officer, the chief nursing officer, the emergency program manager, and the CEO. The right answer depends on your hospital, the incident, and the time of day.

Transfer of command

The first person in the Incident Commander’s chair is rarely the last. As more experienced people arrive, and at every shift change, command transfers. HICS calls for a transition meeting where the outgoing commander briefs the incoming one on the situation, the response actions, the available resources, and the role of outside agencies. Then document the transfer and tell your staff who is in charge. Rehearse it. A sloppy handoff at hour six is where many responses lose the thread.

Getting HICS in Place

HICS sits inside a broader hospital emergency management program. The guidebook lays out a nine-step process for that program:

  1. Designate an Emergency Program Manager.
  2. Establish the Emergency Management Committee.
  3. Develop the all-hazards Emergency Operations Plan.
  4. Conduct the Hazard Vulnerability Analysis (HVA).
  5. Develop incident-specific guidance.
  6. Coordinate with external entities.
  7. Train key staff.
  8. Exercise the Emergency Operations Plan.
  9. Review and evaluate the program, then plan and carry out improvements.

None of it works without your executives. The CEO and senior administrators have to back the program, fund the training, and show up for the exercises. If your executives see HICS as the emergency manager’s project, they will improvise when the real incident comes, and the structure you built will be ignored.

The regulatory driver is the CMS Emergency Preparedness Rule, which hospitals have had to meet since November 2017. It requires four core elements: an emergency plan based on an all-hazards risk assessment, policies and procedures, a communication plan, and a training and testing program. For hospitals accredited by The Joint Commission, the Emergency Management chapter was reorganized in 2022, with more weight on continuity of operations, recovery, and evaluating exercises. HICS is not a regulation. It is a ready-made way to build the incident command piece of what CMS and your accreditor expect. Our healthcare practice page covers how we work with hospitals and health systems on all of it.

The HICS Toolkit

The 2014 guidebook comes with tools you customize for your hospital:

  • Incident Planning Guides (IPGs) set out actions to consider when writing your plans, grouped into mitigation, preparedness, response, and recovery.
  • Incident Response Guides (IRGs) give suggested response actions for specific hazards.
  • HIMT Activation Charts show which positions to activate for each response period.
  • Job Action Sheets give each position its checklist.
  • HICS Forms, revised in 2014 to be more consistent with FEMA’s ICS forms, including the new IAP Quick Start, the HICS 200 IAP Cover Sheet, and the HICS 221 Demobilization Check-Out.

The 2014 edition also consolidated the 2006 scenario lists. Instead of separate guides for every variety of chemical attack or utility loss, the IPGs and IRGs now organize around effects: chemical incident, infectious disease, utility failure, evacuation and shelter-in-place, staff shortage and mass casualty incident, and others. That matches how I think about all crisis planning. The causes of emergencies vary. The effects mostly don’t. Plan for the effects.

One example shows the age of the toolkit. The 2006 “Cyber Attack” scenario became “Information Technology (IT) Failure” in 2014. The February 2024 ransomware attack on Change Healthcare disrupted claims processing, pharmacy transactions, and provider payments across the country for weeks. If your IT failure guide still assumes a short outage at your own hospital, update it for a long one that starts at a vendor. I covered the wider problem in Managing Uncertainty, Episode 298: Technology Resilience in Healthcare.

How an Incident Starts

Some incidents come with warning. Law enforcement, EMS, the local health department, or the local emergency management agency may notify the hospital in one of three levels:

  • Advisory: no response is needed yet, but one may be.
  • Alert: a response is likely or imminent. Raise your readiness.
  • Activation: a response is required.

Many incidents come with no warning at all. The first sign is an EMS radio report, a breaking news story, or patients arriving at the emergency department. Early information is often incomplete or wrong. Your team has to act on it anyway and correct course as the picture fills in.

Incident Action Plans

The Incident Action Plan (IAP) puts management by objectives into practice. It records the objectives, strategies, and tactics for each operational period. The guidebook lists the benefits: fewer omissions and less duplicated effort, lower cost, better information sharing and communication, and a historical record of the incident.

The IAP scales. When time or people are short, or the incident is small, start with the IAP Quick Start, a shorter documentation tool, and expand to the full IAP forms as the incident grows.

Customizing HICS

Customize the details and keep the structure. The guidebook says minor changes to fit your hospital’s mission and resources are fine, but significant variations should be approached with caution. A system that departs far from ICS principles may not be recognized by your response partners, and that hurts coordination in exactly the large-scale incidents where you need it most.

Good customization looks like this: hospital-specific information in your Job Action Sheets, IPGs, and IRGs; key forms pre-populated so they can be completed faster; and forms stored where your team can reach them electronically during an incident.

HICS at Small Hospitals and Off Hours

Small and rural hospitals can use HICS, but they have to adapt it. The guidebook added a chapter on this in 2014. The same problem applies to every hospital at 2 AM on a holiday weekend.

The fix is to activate only the positions you need and blend roles into combined Job Action Sheets. Staff at Critical Access Hospitals already do several jobs on a normal day. In an emergency, the same people will hold more than one HIMT position, at least at first. Some positions combine more easily than others. The Incident Commander often takes on the Public Information Officer and Liaison Officer roles. The guidebook says the Safety Officer and Medical-Technical Specialists should not be combined with other roles unless absolutely necessary.

Where HICS Stops

HICS manages the incident inside a hospital. It does not, by itself, coordinate a health system with a dozen hospitals, clinics, and corporate functions. It doesn’t keep billing, the supply chain, or the electronic health record running. That takes business continuity and IT disaster recovery, and in a system, a coordination layer above the hospitals.

That’s the gap we closed for a major healthcare system in the southwestern United States. It already had hospital-level emergency management in place. We built a System Emergency Management Program aligned with ISO 22361 and Joint Commission requirements, with governance that brought business continuity, system emergency management, and hospital emergency management under one framework and a resilience steering committee to hold it together.

Then exercise it at the system level. For one of the largest healthcare systems in the United States, we designed a systemwide mass casualty tabletop exercise based on the 2015 terrorist attacks in and around Paris, updated for modern tactics. It ran three hours with more than forty injects and over fifty participants, including the CEO, COO, and General Counsel.

HICS gives your hospital a common structure. Practice is what makes it work.
WAYlTTcSWclkeF68_kk1yRqwLwHjcCH2N7Zryifeshn-r77UHUUE0moHk-UehUjkC-V3KQGy-qU6edOZdD0xZzY=s0 The Hospital Incident Command System (HICS): An Overview for Hospital Leaders

Keep Going

A few ways to go deeper if this was useful.

Bryan Strawser Avatar

About the author

Let’s build your Resilience Roadmap

Our team has spent two decades helping the world’s leading organizations prepare for and navigate disruption. We’ll bring that experience to yours.