Dispatcher Test 21
5 min40 WPM required285 words
Click on the passage and start typing to begin.
A mass casualty incident inverts the normal logic of dispatch: instead of many resources for one patient, there are many patients for limited resources, and the communications center becomes the regulator of scarcity. The first calls from a bus crash, a building collapse, or a multiple shooting produce a founding incident whose most important early field is the estimated number of patients, a number the dispatcher updates relentlessly as reports firm up. The medical branch is built by protocol: a first alarm of ambulances, a supervisor to establish triage, and notifications to every receiving hospital so emergency departments can clear beds before the first transport leaves the scene. Hospital capacity becomes live data at the console, with the dispatcher polling each facility for the number of critical and stable patients it can accept and typing the answers into a distribution plan that keeps any single hospital from being overwhelmed. On scene, patients receive triage tags, and transport officers call the dispatcher with each departure: unit, patient count, triage categories, and destination. The dispatcher logs every transport with times, building the master patient tracking record that families, hospitals, and investigators will depend on for days. Mutual aid ambulances flow in from neighboring counties, and the dispatcher tracks their assignments while backfilling the rest of the system, because routine emergencies do not pause out of respect for a disaster. Radio discipline is enforced by designating separate talkgroups for command, medical, and staging. Amid it all, the keyboard remains the bottleneck and the safeguard: a transport logged incorrectly is a patient lost to the tracking system. Centers that excel at mass casualty work share one trait, ruthless commitment to structured, time stamped entry while chaos argues for shortcuts.