What Is NEMSIS? EMS Data Standards Explained
NEMSIS is the National EMS Information System, the national standard for collecting and sharing EMS patient-care data. This guide explains how NEMSIS is structured, what its elements mean inside an ePCR, and where CaseSync fits without replacing the agency’s ePCR or submission process.
NEMSIS in one sentence
NEMSIS — the National EMS Information System — is the national standard, funded by the NHTSA Office of EMS, for collecting and sharing EMS patient-care data. It defines a common vocabulary so that a cardiac-arrest call documented in one state can be aggregated and compared with calls from every other state.
The current release is version 3.5.1 (published October 2025). Version 3 was a major rewrite of the 2005 version 2 standard, built to improve data quality, measure EMS performance, and move the standard toward formal HL7 / ANSI recognition.
The three NEMSIS datasets
NEMSIS v3 is not one list — it is three coordinated datasets:
| Dataset | What it describes | Who submits it |
|---|---|---|
| EMSDataSet | The patient care report (ePCR) for a single EMS activation | The local EMS agency, per call |
| DEMDataSet | Demographic snapshot of the agency itself | The EMS agency |
| StateDataSet | State reporting requirements and resources | The state EMS office |
Every element number tells you where it lives: an element beginning with e (like eVitals.06) belongs to the EMS patient-care report, while one beginning with d (like dAgency.01) belongs to the agency demographic set.
What’s inside an ePCR: the EMSDataSet
The EMSDataSet organizes a call into clinical and operational sections. Each section groups related elements:
- Response & timing:
eResponse,eDispatch,eTimes - Patient & scene:
ePatient,eScene,eSituation,eInjury,eHistory - Clinical care:
eVitals,eExam,eMedications,eProcedures,eAirway,eDevice,eArrest,eLabs,eProtocols - Outcome & handoff:
eDisposition,eOutcome,eNarrative - Administrative:
eRecord,ePayment,eCrew,eOther
In version 3.5.1 the EMSDataSet defines 449 elements in total, of which 144 are “national” elements that must be submitted to the national repository.
Mandatory, Required, Recommended, Optional
Not every element carries the same weight. NEMSIS assigns each one a usage level that tells software and crews when it must be completed:
| Usage level | Meaning | EMSDataSet count (v3.5.1) |
|---|---|---|
| Mandatory | Must be completed; cannot use a “NOT” value | 21 |
| Required | Must be completed, but may use a “NOT” value | 130 |
| Recommended | Optional to complete; allows “NOT” values | 61 |
| Optional | Not required; no “NOT” values | 237 |
This is why “fill out the whole record” is misleading. A compliant ePCR is not about typing every field — it is about completing the mandatory and required elements correctly, with valid coded values.
“NOT Values” and pertinent negatives
NEMSIS is strict about the difference between blank and intentionally not recorded. For elements that allow them, three NOT Values document why a real value is missing:
- Not Applicable — the element does not pertain to this call
- Not Recorded — the element applied but was left blank
- Not Reporting — the agency or state does not collect it
Separately, pertinent negatives (for example, “No Known Drug Allergy” or “None Reported”) let a crew affirmatively document the absence of a finding — which is clinically very different from leaving a field empty.
Why NEMSIS data quality matters
NEMSIS data does more than satisfy a state mandate. It feeds quality improvement, protocol development, billing, research, and public-health surveillance. When fields are incomplete or inaccurate, every one of those downstream uses degrades — and inadequate prehospital documentation has been associated with worse in-hospital outcomes.
That is the catch: NEMSIS standardizes the structure of the record, but it cannot guarantee the accuracy of what a crew types from memory at the end of a long shift.
How CaseSync connects NEMSIS fields to an existing ePCR
VeriMedic makes CaseSync, an EMS-specific body-camera and software platform. CaseSync synchronizes body-camera video, cardiac monitor data, and CAD onto one timeline, drafts supported NEMSIS fields, and pushes them into your existing ePCR for paramedic confirmation. CaseSync does not replace your ePCR or your NEMSIS submission.
Review the EMS body-camera documentation workflow, the CaseSync workflow from capture through protocol review, and how CaseSync differs from a traditional ePCR. For the downstream quality process, use the EMS QA, QI, and record-accuracy guide.
Frequently asked questions
What does NEMSIS stand for? The National EMS Information System — the NHTSA-funded national standard for EMS patient-care data.
What is the NEMSIS EMSDataSet? The dataset that defines the elements in an ePCR — 449 elements in v3.5.1, each with a usage level and validation rules.
What does NEMSIS-compliant documentation mean? A patient care report structured and coded to the NEMSIS standard so it passes schema validation and can be submitted to state and national repositories.
Sources
- NEMSIS Data Dictionary, v3.5.1 (EMSDataSet) — element counts, usage levels, datasets, NOT Values
- NEMSIS v3 EMSDataSet Guide — sections, national vs. state elements
- NEMSIS.org — program overview and NHTSA funding