Emergency Calltaking and Protocol Systems
Emergency Calltaking and Protocol Systems
This domain tests how a telecommunicator converts an unstructured 9-1-1 conversation into a structured, protocol-driven call. The exam expects you to know the architecture of the Academy's protocol system and to apply Case Entry, Key Questions, and Dispatch Life Support in the correct order.
The protocol architecture
- Case Entry (CE) captures the minimum data set: address, callback number, and the chief complaint, elicited with "Tell me exactly what happened."
- Chief complaint is the caller's presenting problem, mapped to a numbered protocol: Protocol 6 Breathing Problems, Protocol 10 Chest Pain, Protocol 9 Cardiac Arrest.
- Key Questions (KQs) are scripted and asked in order. They are not optional prompts; each answer branches the call toward a determinant.
- Dispatch Life Support (DLS) includes pre-arrival instructions (PDIs) and post-dispatch instructions.
Core rules
- Read the protocol text as written; do not improvise medical advice.
- Confirm address and callback before ending the call.
- Ask about consciousness and breathing early; they drive nearly every high-acuity determinant.
- Document answers, not interpretations.
Worked example
A caller says, "My husband has pressure in his chest and he's sweating." CE is complete. The chief complaint is chest pain, so you open Protocol 10. You ask the Key Questions: Is he completely awake? Is he breathing normally? Has he had heart problems before? His answers (awake, breathing but clammy, cardiac history) keep the call at a high determinant and trigger DLS. You do not code "heart attack," because the caller's diagnosis is not a protocol complaint.
Traps that cost marks
- Skipping or reordering Key Questions "because you already know."
- Coding from the caller's diagnosis instead of the chief complaint.
- Paraphrasing protocol instructions into your own words.
- Failing to confirm the address while the caller is upset.