10.5 Incident Command and Resource Coordination

Command Turns Chaos Into Tasks

Incident command is an operations topic because emergencies can outgrow one responder fast. A single crash can involve traffic, fire risk, multiple patients, and limited access. The Incident Command System (ICS), part of the National Incident Management System (NIMS), provides the structure that prevents freelancing and keeps everyone accountable.

Core ICS principles the EMR must recognize:

• Unified, single command — one Incident Commander is accountable for the scene; you report to command, you do not invent your own parallel operation.
• Manageable span of control — one supervisor manages roughly 3 to 7 people (about 5 is ideal); beyond that, the structure expands.
• Common terminology — plain language, not radio codes that other agencies may not share.
• Chain of command and accountability — orders and resource requests flow through defined positions.

If you are first on a chaotic, multi-patient scene, the right move is usually to establish command (or assume the EMR role under it), size up, communicate the situation, and request additional resources rather than rushing to one patient and ignoring the bigger picture. If command already exists, you report in and take an assignment instead of acting independently. When a scene is unsafe — fire, traffic, violence, hazardous materials — you stage at a safe location and wait for the resources that can make it safe.

Consent, Refusal, and Advance Directives

Every contact begins with the authority to treat:

A competent adult has the right to refuse care, even care you believe is lifesaving. A valid refusal means the patient is alert, oriented, and not impaired by injury, drugs, or alcohol; you explain the risks of refusal in understandable terms, you try to persuade and arrange follow-up, and you document the refusal and the warnings given, ideally with a witness. A patient who is confused, intoxicated, or has an altered mental status cannot give a valid refusal, and implied consent for emergency care applies.

A Do Not Resuscitate (DNR) order and other advance directives are legal instructions about the care a patient wants if they cannot speak for themselves. When you encounter one, verify it is valid per local protocol, then honor it — but remember a DNR usually limits resuscitation, not comfort care or treatment of other problems. When the document's validity is unclear in a true arrest, most systems direct you to begin resuscitation and let medical direction sort out the document, because you cannot undo a withheld resuscitation.

Negligence, Abandonment, Confidentiality, and Scope

Abandonment is terminating care without ensuring the patient is handed off to a provider of equal or higher training. Once you start care, you cannot simply walk away; you transfer to EMS/the hospital and document who took over. Negligence requires all four elements — miss one and there is no negligence:

1. Duty to act — you had a responsibility to provide care (e.g., you were dispatched or assumed care).
2. Breach of duty — you failed to meet the standard of care expected of an EMR.
3. Causation — the breach directly caused harm (the "but for" link).
4. Damages — the patient suffered actual harm.

Work within your scope of practice (what an EMR is legally allowed to do under the National EMS Scope of Practice Model and your state) and to the standard of care (what a reasonable, similarly trained EMR would do in the same situation). Good Samaritan laws protect good-faith volunteer care but do not shield gross negligence, willful misconduct, or acting outside your training.

Confidentiality is a legal duty: patient information is protected under HIPAA, and you share the minimum necessary only with those involved in the patient's care. The exceptions are mandatory reporting situations defined by law — child or elder abuse, gunshot and stab wounds, certain assaults and communicable diseases — where reporting is required and overrides ordinary confidentiality. Talking about a patient on social media or to uninvolved people is a breach.

Staging, Resource Requests, and ICS Roles

Knowing when not to enter is as important as knowing when to act. Staging means holding at a safe location near the scene until it is secured or until you are assigned. The clearest staging scenarios are violence or crime in progress (stage until law enforcement secures it), active fire or unstable structure (stage until the fire service controls it), and hazardous materials (stage uphill/upwind until hazmat clears a safe zone). Entering an unsecured scene to reach a patient is the trap answer; an injured EMR helps no one and consumes resources.

When you request resources, be specific and early. "Send more help" is weak; command needs to know what and how much — additional ambulances, fire suppression, law enforcement, a hazmat team, air medical, heavy rescue/extrication, or utility shutoff. The EMR role in extrication is usually patient-focused: protect the patient with blankets and shielding, maintain manual spinal stabilization and the airway, and let trained rescuers run the tools. Recognize air medical as an option for serious trauma or remote/access-limited scenes per local criteria.

Under ICS, large incidents expand into functional sections — Operations, Planning, Logistics, and Finance/Administration — but an EMR rarely staffs these; the key is to understand the structure, report to command, take an assignment, and communicate clearly. Using common terminology, maintaining accountability (command always knows where you are and what you are doing), and avoiding freelancing are the behaviors the exam scores as correct. The recurring theme across consent, command, and resource coordination is the same: act within your authority and inside the system, escalate to the right people, and document what you did.