EMS incident

An EMS incident is an event involving emergency medical services. It can generate one or more unit responses and patient-care records, and it does not necessarily result in transport. The source's incident definition and identifier determine what is counted, so an incident total should remain distinct from responses, patients, or ambulance trips.

Several records can describe one event

A dispatch event can involve multiple resources, patients, and care teams. A data system may keep separate identifiers for the event and each unit's response. Patient-care documentation adds another level of detail.

NEMSIS version 3.5.1 distinguishes the dispatch-assigned incident number from an EMS unit-response number and a patient care report number. Its disposition fields separately describe patient contact and transport. These are useful distinctions when reading an EMS dataset, rather than a guarantee that every public release exposes all of those fields. NEMSIS dictionary.

Example

Hypothetical example: One roadway event produces a dispatch incident involving an engine and two ambulances. Two patients are assessed, and one is transported. Under the stated incident rule, the event counts once.

A unit-response report can count three responses, while a patient-focused report counts two assessed patients and a transport report counts one transported patient. The figures can all be correct. They should not be added together or described as competing estimates of the same unit.

Common confusion

An EMS incident is not automatically a confirmed diagnosis or a hospital admission. The request, field assessment, and eventual hospital findings concern different stages of the episode. An initial medical call label cannot establish the final clinical outcome.

An incident can also end without patient contact, for example when a unit is canceled or no patient is found. Whether such events appear in a particular incident total depends on its inclusion rules. Their presence should not be interpreted as completed treatment.

Reading a public EMS release

Identify whether each row represents an incident, unit, encounter, or another record. Check how multiple patients, mutual aid, repeated assignments, and duplicate dispatch identifiers are handled. San Diego's public fire-and-EMS release, for example, describes dispatched calls and uses generalized problem descriptions to protect patient information. That local release is not the same as a full patient-care record. San Diego dataset documentation.

Keep the same scope and date basis across comparisons. A transport-only dataset and an all-dispatched-events dataset describe different portions of EMS activity, even if their charts both use the label “incidents.”

Related terms

• Response count
• Patient care report
• EMS transport
• No patient found

Sources

• NEMSIS v3.5.1 Data Dictionary, October 2025 — eResponse.03/.04, eRecord.01, and disposition fields establish different reporting units.
• City of San Diego: Calls for Fire and Emergency Medical Services — Local dispatched-call release with generalized problem descriptions for patient privacy.