Hospital Incident Command System (HICS)

The Hospital Incident Command System (HICS) is the hospital-specific adaptation of the Incident Command System — the standardised, scalable command structure used across US emergency response. It gives a hospital a pre-agreed way to convert its normal management hierarchy into an incident organisation: one person in command, a defined span of control, named roles with written responsibilities, and a documented planning cycle that produces an Incident Action Plan.

The reason HICS exists as a separate thing from generic ICS is that hospitals do not respond the way fire and law enforcement agencies do. A hospital cannot stage, it cannot decline the incident, it is usually both a responding agency and a piece of critical infrastructure that is itself at risk, and its “operations” are continuing clinical care rather than a discrete tactical objective. HICS keeps the ICS command architecture and rewrites the roles and job aids around that reality.

Sourcing note, and why this topic is hard to research. HICS has no single authoritative national publisher. Its materials originate with California’s Emergency Medical Services Authority, which developed HICS from the earlier Hospital Emergency Incident Command System (HEICS), and they are redistributed by state hospital associations and regional healthcare coalitions across the country. During the preparation of this page, the California EMSA HICS pages returned an authentication gate rather than content, and the guidebook PDF was not retrievable; the Internet Archive was offline. We have therefore not verified the current HICS guidebook edition or revision date, and do not state one here. Confirm the current edition and download the current forms from your own state hospital association or healthcare coalition before building them into a plan. The material set and structure described below are drawn from the HICS resources published by the California Hospital Association, which distributes the forms, Incident Planning Guides and Incident Response Guides, and from the current text of 42 CFR 482.15 as published by the eCFR.

The regulatory hook: HICS is not required, but its function is

No federal regulation names HICS. What the CMS emergency preparedness Condition of Participation for hospitals — 42 CFR 482.15 — requires is a set of capabilities that an incident command structure is the practical means of delivering. Two provisions do most of the work.

First, the emergency plan at 482.15(a)(3) must “address patient population, including, but not limited to, persons at-risk; the type of services the hospital has the ability to provide in an emergency; and continuity of operations, including delegations of authority and succession plans.” Delegations of authority and succession are, in effect, a requirement to have decided in advance who is in command and who takes over.

Second, and more directly, the communication plan at 482.15(c)(7) requires “a means of providing information about the hospital’s occupancy, needs, and its ability to provide assistance, to the authority having jurisdiction, the Incident Command Center, or designee.” The regulation assumes the existence of an incident command structure the hospital can report into and be reached through.

Beyond that, 482.15(a)(4) requires a process for cooperation and collaboration with local, tribal, regional, state and federal emergency preparedness officials “to maintain an integrated response.” Those officials run on ICS. A hospital using an idiosyncratic internal command structure has to translate at the boundary during the worst hour of the incident, which is the failure mode HICS exists to prevent. For the full CMS requirement — plan, policies and procedures, communication plan, training and testing, and emergency power — see the companion guide on hazard vulnerability analysis and the CMS emergency preparedness rule.

The command structure

HICS uses the standard ICS organisation. Understanding it as a set of functions that always exist — and that default to the Incident Commander until delegated — rather than a set of boxes that must always be filled is the single most useful conceptual move for a hospital adopting it.

Incident Commander

One person, always. The Incident Commander holds every function not explicitly delegated, sets incident objectives, approves the Incident Action Plan, and owns the decision to expand or contract the organisation. In a hospital this is frequently not the chief executive — it is whoever is qualified and present, which at 03:00 on a Sunday is often the administrator on call or the nursing supervisor. Pre-designating a single named individual is a common planning error; the role is filled by position qualification and availability, and formally transferred when a more qualified person arrives.

Command Staff

Public Information Officer — the single point for information released externally, including to media and, in a hospital, to families and to the wider workforce.
Safety Officer — monitors conditions and has the authority to stop unsafe operations. This authority is real and is not subject to the Operations Section Chief’s agreement.
Liaison Officer — the point of contact for assisting and cooperating agencies: EMS, public health, the healthcare coalition, other hospitals, law enforcement.
Medical/Technical Specialists — the distinctively hospital element. Subject-matter advisers attached to Command (or to a Section) for the specific incident: infectious disease, hazardous materials, legal affairs, risk management, clinic administration, pediatric care, medical ethicist, and others depending on the event. This is how HICS injects clinical expertise into a command structure that would otherwise have no place for it.

General Staff — the four Sections

Operations — everything that directly addresses the incident. In a hospital this is the clinical response: patient care, triage, surge, casualty management, infrastructure and hazmat response, business continuity of clinical services. Operations is usually the largest section and the first to need subdivision into branches, divisions and groups.
Planning — situational awareness, resource status tracking, documentation, demobilisation planning, and running the planning cycle that produces the Incident Action Plan. Planning is the section hospitals most often under-staff and most often regret under-staffing.
Logistics — everything the response consumes: staffing, supplies, equipment, food, transport, communications, IT, facilities support. In prolonged incidents Logistics becomes the critical section.
Finance/Administration — cost tracking, time recording, procurement, compensation and claims. Its importance is disproportionate to its visibility: incident cost documentation is what makes later reimbursement or federal cost recovery possible, and it cannot be reconstructed after the fact.

The general rule of thumb ICS uses for span of control is that one supervisor manages roughly three to seven subordinates, with five as the usual target. That number is what drives the organisation to expand — you add a layer when a supervisor’s span exceeds it, not because a chart says the box exists.

The HICS material set

HICS is distributed as a package of job aids rather than a single document. The components you should expect to find from your state hospital association or coalition are:

Job Action Sheets

One per position. Each sheet states the position’s mission, who it reports to, and a checklist of actions organised by time phase — immediate, intermediate, extended, and demobilisation/system recovery. The Job Action Sheet is what makes HICS workable for staff who fill an incident role a handful of times in a career: the person taking the position reads the sheet and starts working, rather than trying to recall training from two years ago.

Incident Planning Guides (IPGs)

Pre-incident planning documents, one per hazard type. An IPG poses the questions a hospital should have answered before that hazard occurs — mitigation, preparedness, response and recovery considerations for that specific scenario. IPGs are the natural bridge from your hazard vulnerability analysis: the HVA tells you which hazards rank highest, and the corresponding IPGs tell you what planning those hazards demand.

Incident Response Guides (IRGs)

The response-time counterpart, again one per hazard type. An IRG sets out the immediate, intermediate and extended actions for that scenario, mapped to the positions responsible, plus documentation and demobilisation considerations. The California Hospital Association’s current HICS distribution also includes NETEC special-pathogen IPG and IRG documents alongside the general set — a useful indicator that the hazard list is maintained rather than frozen.

HICS forms

HICS uses the standard ICS form numbering, so a hospital form is intelligible to an external incident management team without translation. The core set distributed for hospital use is:

Form	Purpose
201 — Incident Briefing	The first document of any incident. Captures the initial situation, objectives, actions taken and the organisation as it stands. Doubles as the transfer-of-command briefing document.
202 — Incident Objectives	The objectives for the operational period, approved by the Incident Commander. The first page of the Incident Action Plan.
203 — Organization Assignment List	Who is filling which position this operational period.
204 — Assignment List	Tactical assignments for a specific division, group or branch.
213 — General Message	Written message form; creates a record of a communication that would otherwise be verbal and unrecoverable.
214 — Activity Log	Individual position log of significant events and decisions. The most under-used and most consequential form — 214s are the raw material for the after-action review and for any subsequent legal or regulatory inquiry.
215A — Incident Action Plan Safety Analysis	Safety Officer’s hazard analysis of the planned assignments, with mitigations.

The distribution also includes an Incident Action Plan Cover Sheet and an IAP Quickstart form — the latter being a condensed IAP for short incidents that do not justify the full planning cycle, which describes the majority of real hospital activations.

The planning cycle and the Incident Action Plan

The discipline HICS actually imposes is not the org chart — it is the operational period. Command sets a defined block of time, states objectives for it, plans against those objectives, executes, then evaluates and re-plans. The Incident Action Plan is the written product of one turn of that cycle.

Initial response and assessment — activate, establish command, complete the ICS 201.
Set objectives — the Incident Commander states what must be achieved this operational period (ICS 202). Objectives should be specific and measurable; “manage the surge” is not an objective, “decompress the ED to under 20 boarding patients by 18:00” is.
Plan — Sections develop assignments against the objectives; Planning assembles the IAP; the Safety Officer completes the 215A.
Approve and brief — the Incident Commander approves the IAP; the operational period briefing distributes it.
Execute and assess — Operations works the plan; Planning tracks status and resources.
Re-plan — the cycle repeats for the next operational period.

Operational period length is a judgement call and one of the more consequential ones. Twelve hours is the common default because it aligns with hospital shift changes, but a fast-moving incident may need shorter periods and a prolonged one may extend them. Aligning the operational period to shift change is deliberate: it makes the operational period briefing and the shift handover the same event, which is the only way the cycle survives contact with a 24-hour clinical operation.

Activation, expansion and demobilisation

Activation criteria

Write down what triggers activation and who may declare it, and make the threshold low enough that it actually gets used. Hospitals that reserve HICS for catastrophes never practise it, and then attempt to stand it up for the first time under the worst conditions. The more useful model is a graduated activation — a partial activation for a moderate event (Command plus Operations plus Logistics, one operational period, IAP Quickstart) that exercises the same machinery.

Expansion and contraction

Fill only the positions the incident requires. Every unfilled position’s responsibilities sit with the position above it, ultimately with the Incident Commander. A small event may be Incident Commander plus one Section Chief. Over-filling the chart is not caution — it pulls clinical staff out of clinical roles to sit in a command post with nothing to do, which is a real cost during a surge.

Demobilisation and recovery

Demobilisation is a planned phase, not the incident stopping. It covers releasing staff and resources in an orderly sequence, restoring normal operations, collecting documentation — the 214 logs above all — and formally terminating command. The after-action review and improvement plan follow, and this is where the loop closes back to CMS: 482.15(d)(2)(iii) requires the hospital to “analyze the hospital’s response to and maintain documentation of all drills, tabletop exercises, and emergency events, and revise the hospital’s emergency plan, as needed.”

Training and exercising HICS

The CMS testing requirement at 482.15(d)(2) is the practical driver of how often HICS gets exercised. The hospital must conduct exercises to test the emergency plan at least twice per year: an annual full-scale community-based exercise (or, where a community-based exercise is not accessible, an annual individual facility-based functional exercise), plus one additional annual exercise which may be a second full-scale or functional exercise, a mock disaster drill, or a facilitated tabletop exercise or workshop.

Notably, if the hospital experiences an actual natural or man-made emergency requiring activation of the emergency plan, it is exempt from its next required full-scale or facility-based functional exercise. A real activation counts — which is an additional reason to formally activate HICS for moderate events rather than managing them informally.

For individual training, the ICS course sequence (IS-100, IS-200, IS-700 for NIMS familiarity, and ICS-300/400 for those filling Command and General Staff positions in complex incidents) is the standard baseline that makes hospital staff intelligible to external partners. Match the training level to the position, not to the person’s seniority.

Why HICS guidance is so scattered — and what to do about it

Anyone researching HICS quickly notices that authoritative-looking material comes from a dozen unrelated places: a state EMS authority, several state hospital associations, regional healthcare coalitions, federal technical assistance centres and commercial training vendors, often with different form versions and different hazard lists. This is not an accident of search results. HICS originated as a state programme, was adopted nationally by practice rather than by mandate, and has never had a single federal owner in the way NIMS has FEMA.

The practical consequences for a hospital:

Check provenance and date on every HICS artefact you adopt. Superseded forms and guidebook editions remain in wide circulation on institutional and vendor websites.
Prefer your own state hospital association or healthcare coalition as the source, because that is also the body whose regional plans your hospital has to interoperate with.
Do not treat a vendor’s HICS training package as the standard. Vendors package HICS; they do not define it.
Expect local variation and plan for it. Neighbouring hospitals may be running different form versions. What has to match at the boundary is the ICS structure and terminology, which is stable, rather than the paperwork.

Frequently asked questions

What is the Hospital Incident Command System?

A hospital-specific incident management system built on the Incident Command System, giving hospitals a standard command structure (Incident Commander, Command Staff, and Operations, Planning, Logistics and Finance/Administration Sections), position-specific Job Action Sheets, hazard-specific Incident Planning and Incident Response Guides, and the standard ICS forms.

Is HICS required by CMS?

No. 42 CFR 482.15 does not name HICS. It requires an all-hazards emergency preparedness programme including delegations of authority and succession plans, integration with local and regional emergency officials, and a means of reporting occupancy, needs and capability to the authority having jurisdiction or the Incident Command Center. HICS is the most widely used way of meeting those requirements, not a mandated one.

What is the difference between HICS and ICS?

ICS is the general incident command framework used across US emergency response. HICS applies that framework to hospitals: it keeps the command structure, span of control and forms, and replaces the roles and job aids with hospital-specific ones — including Medical/Technical Specialists, a category with no equivalent in field ICS.

Who is the Incident Commander in a hospital?

Whoever is qualified for the role and available when the incident begins — commonly the administrator on call or nursing supervisor outside business hours. Command is formally transferred, with a briefing, when a more qualified individual arrives. Pre-assigning the role permanently to a single executive is a planning error.

What are HICS Job Action Sheets?

Position-specific checklists that state the role’s mission, reporting relationship, and actions organised by time phase (immediate, intermediate, extended, and demobilisation/recovery). They allow a staff member who rarely fills an incident role to begin working immediately.

What is the difference between an IPG and an IRG?

An Incident Planning Guide is a pre-incident document: what a hospital should plan for a given hazard before it happens. An Incident Response Guide is the response-time counterpart: the actions to take, by position and time phase, once that hazard occurs.

How long should an operational period be?

There is no fixed rule. Twelve hours is the common hospital default because it aligns the operational period briefing with shift handover. Fast-moving incidents may need shorter periods; prolonged, stable incidents may extend them. The Incident Commander sets it.

How often must a hospital exercise its emergency plan?

Under 42 CFR 482.15(d)(2), at least twice per year: an annual full-scale community-based exercise (or a facility-based functional exercise where a community exercise is not accessible), plus one additional annual exercise which may be a second full-scale or functional exercise, a mock disaster drill, or a facilitated tabletop. An actual emergency requiring plan activation exempts the hospital from its next required full-scale or functional exercise.

Which HICS edition is current?

We were unable to verify the current edition from a primary source while preparing this page, and deliberately do not state one. Obtain the current guidebook and forms from your state hospital association or healthcare coalition, and check the revision date on each artefact before adopting it — superseded versions circulate widely.

Hospital Incident Command System (HICS): Structure, Forms, and How It Is Actually Run