Study guide
10.1 Legal Elements in Emergency Dispatch: Duty, Breach, Causation & Damages
IAED Emergency Medical Dispatcher EMD
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: MPDS Foundations & Call Processing Architecture
1.1 IAED, MPDS History & The Role of the EMD 1.2 Case Entry Sequence & Structured Interrogation 1.3 The Four Priority Symptoms & Four Commandments of EMD 1.4 Call Processing Architecture: Parallel Dispatch, Fast Track & Shunts
2 Chapter 2: Chief Complaint Protocols: Cardiorespiratory Emergencies
2.1 Protocol 9: Cardiac or Respiratory Arrest / Death 2.2 Protocol 6: Breathing Problems & Respiratory Distress 2.3 Protocol 10: Chest Pain & Protocol 19: Heart Problems / AICD
3 Chapter 3: Chief Complaint Protocols: Acute Medical Emergencies
3.1 Protocol 11: Choking (Foreign Body Airway Obstruction) 3.2 Protocol 12: Convulsions / Seizures 3.3 Protocol 13: Diabetic Problems & Protocol 23: Overdose / Poisoning 3.4 Protocol 1: Abdominal Pain, Protocol 2: Allergies & Protocol 18: Headache
4 Chapter 4: Chief Complaint Protocols: Environmental & Trauma Emergencies
4.1 Protocol 17: Falls & Protocol 30: Traumatic Injuries 4.2 Protocol 21: Hemorrhage / Lacerations 4.3 Protocol 14: Drowning, Protocol 15: Electrocution & Protocol 20: Heat / Cold Exposure 4.4 Protocol 7: Burns, Protocol 8: Carbon Monoxide / Hazchem & Protocol 22: Industrial Accidents
5 Chapter 5: Chief Complaint Protocols: Neurological, Obstetric & Specialized Incidents
5.1 Protocol 28: Stroke / CVA & Prehospital Stroke Screening 5.2 Protocol 24: Pregnancy / Childbirth / Miscarriage 5.3 Protocol 31: Unconscious / Fainting & Protocol 32: Unknown Problem (Man Down) 5.4 Protocols 25, 27, 29 & 39: Behavioral, Penetrating Trauma & High-Threat Scenes
6 Chapter 6: MPDS Determinant Codes & Response Configuration
6.1 The Determinant Hierarchy: OMEGA to ECHO Severity Ladder 6.2 Determinant Code Architecture: Syntax & Descriptors 6.3 Suffix Modifiers & Clinical Acuity Qualifiers 6.4 Response Configuration, Travel Modes (HOT vs COLD) & ProQA Integration
7 Chapter 7: Dispatch Life Support: Telephone CPR & Airway Management
7.1 Adult Telephone CPR (T-CPR): Compressions-First Protocol & Cadence 7.2 Pediatric and Infant T-CPR: Technique Variations & Rescue Breathing 7.3 Agonal Breathing Identification vs Normal Breathing & The Agonal Breathing Detector Tool 7.4 Choking Dispatch Life Support: Severity, Age & Loss of Responsiveness
8 Chapter 8: Dispatch Life Support: Time-Critical Medical, Obstetric & Trauma Care
8.1 Childbirth Pre-Arrival Instructions: Normal Cephalic Delivery Coaching & Neonatal Care 8.2 Obstetric Emergencies PAIs: Breech Presentation, Prolapsed Umbilical Cord & Postpartum Bleeding 8.3 Opioid Overdose & Naloxone (Narcan) Pre-Arrival Coaching 8.4 Bleeding Control, Tourniquets, Eye Irrigation & Hazmat Evacuation PAIs
9 Chapter 9: Quality Assurance, AQUA & ACE Accreditation
9.1 Continuous Quality Improvement & The IAED Certified EMD-Q 9.2 AQUA Software & Case Review Methodology 9.3 Deviation Classification: Critical, Major, Moderate & Minor Deviations 9.4 The 20 Points of Accreditation & ACE Certification
10 Chapter 10: Legal Liability, Dispatch Ethics & Telecommunicator Wellness
10.1 Legal Elements in Emergency Dispatch: Duty, Breach, Causation & Damages 10.2 Standard of Care, Medical Direction & Protocol Compliance 10.3 Caller Interrogation Dynamics: Repetitive Persistence & The Hysterical Threshold 10.4 Telecommunicator Wellness: Secondary Traumatic Stress & CISM
10.1 Legal Elements in Emergency Dispatch: Duty, Breach, Causation & Damages
Key Takeaways Explain This Topic AI
Negligence generally requires duty, breach, causation, and legally recognized harm; defenses and immunity require a separate jurisdiction-specific analysis.
Answering a 9-1-1 call does not automatically establish an individualized legal duty in every jurisdiction. Public-duty and special-duty rules may apply.
Nonfeasance describes an omitted required act; misfeasance describes improper performance; malfeasance describes wrongful conduct. Labels alone do not establish liability.
A caller's reasonable reliance on an assurance can matter to a special-duty or causation analysis, but reliance does not automatically make an agency liable.
Maintain care, monitoring, and handoff as the applicable protocol requires. Whether ending a call constitutes legally actionable abandonment depends on the facts and law.
Last updated: September 2026
Legal Elements in Emergency Dispatch
Scope: This is a general educational framework for U.S. dispatch practice, not a statement that every jurisdiction applies the same duty, immunity, or damages rules. An operational protocol is important evidence of expected conduct; it does not decide a lawsuit by itself.
Four questions in a negligence analysis
Element Question to examine
Duty Did the defendant owe this claimant a legally recognized duty?
Breach Did the conduct fall below the applicable standard?
Causation Did the breach cause the harm in fact, and is the harm within the legally recognized scope of responsibility?
Damages Did the claimant suffer legally compensable harm?
Even when these elements are alleged, a court must consider applicable defenses and immunity. A poor outcome does not itself prove negligent dispatch, and protocol compliance does not automatically defeat every claim.
Duty and reliance
An EMD has operational responsibilities to process the call, dispatch resources, provide authorized instructions, and document the event. Whether those responsibilities create an individual civil duty to a particular caller is a separate legal question. Some jurisdictions distinguish duties owed to the public generally from a special duty owed to an individual. Merely answering a call is not a universal rule for establishing the latter.
For example, New York's Court of Appeals discusses special-duty requirements and governmental immunity separately in Valdez v. City of New York (2011) and Howell v. City of New York (2022) . These are examples of New York law, not national EMD rules.
A caller's reasonable reliance on a specific assurance may be relevant. Avoid promising arrival times, responder presence, or outcomes that have not been confirmed. Fictional discussion example: Assume a caller forgoes an otherwise viable action because of an inaccurate assurance that responders are already present. That reliance is a fact to investigate; it is not, by itself, a verdict against the agency.
Breach: describe the conduct precisely
Nonfeasance: failing to perform an act that was required, such as omitting an indicated dispatch step.
Misfeasance: performing an authorized task improperly, such as giving an incorrect instruction.
Malfeasance: wrongful conduct, such as intentionally falsifying a record.
These terms organize a discussion. They do not establish an automatic level of culpability, remove immunity, or replace proof of the other elements. Record what happened rather than assigning a legal conclusion during routine quality review.
Causation is more than sequence in time
A delay followed by an injury does not alone prove causation. Cause in fact and proximate or legal cause are related but distinct questions; a simple but-for inquiry does not resolve every jurisdiction's legal-causation test. The clinical evidence, timing, alternative causes, and applicable law matter.
Continuing care and handoff
Follow the current protocol for monitoring, caller safety, disconnection, callbacks, and transfer of care. Do not end indicated assistance merely because units have been dispatched. Equally, do not teach that every ended call is legally abandonment or that flawless scripting guarantees immunity. Preserve the audio, CAD timestamps, protocol version, and handoff details so the actual conduct can be reviewed.