Fire and EMS records reporting: NFIRS, NERIS, and NEMSIS

Reference article · 5 min read

Every fire department and EMS agency produces two streams of records that outlive the call. One is the incident report: what the call was, what crews found, what they did, and what was damaged. The other is the patient care report: assessment, vital signs, medications, procedures, and disposition for each patient. Both serve the agency first, and both feed state and national data programs.

For staff replacing a records management system, the question is whether one product can do three jobs well: documentation a crew can finish at the end of a long shift, the submissions the state requires, and the analysis a chief and a governing body will ask for later.

Fire incident reporting: NFIRS and the move to NERIS

The National Fire Incident Reporting System, run by the U.S. Fire Administration within FEMA, has long been the national collection point for fire department activity. It is modular: a basic module covers every incident, with others for fire, structure fire, casualty, hazardous materials, wildland, apparatus, personnel, and arson. Incident types use a numeric code set, and coding discipline matters because the code drives everything downstream. Departments report through a state program manager. Federal participation has been voluntary, but many states require reporting by rule or statute, and federal fire grant programs have conditioned awards on it. Confirm your obligation with the state fire marshal or program manager.

The U.S. Fire Administration has been developing the National Emergency Response Information System, or NERIS, with the Fire Safety Research Institute, as the replacement. NERIS is cloud hosted, submits through an interface rather than flat file uploads, and covers all-hazards response rather than fire alone. Timelines have shifted more than once, so confirm current dates with the agency and your state program office rather than a vendor roadmap, and ask how historical records stay searchable locally.

EMS reporting: NEMSIS and the patient care record

The National EMS Information System is the national data standard for EMS, supported through the NHTSA Office of EMS. It defines an XML structure with sections for dispatch, response, scene, patient, history, vital signs, medications, procedures, narrative, disposition, times, and outcome, and it marks each element as national and as mandatory, required, recommended, or optional.

Agencies submit to a state repository, which submits onward to the national database, so the version and validation rules your state accepts govern, and state adoption usually trails the national release.

In the field, look for genuine offline capture with reliable sync, narrative templates that do not produce identical charts, controlled substance tracking, signature capture, and amendments that preserve the original entry with an audit trail.

Times, CAD integration, and the clock

Response times should come from computer aided dispatch, not be typed in later. A useful interface carries incident number, location, call type, units, and the time stamps:

• Call handling. Call received at the PSAP, call answered, dispatch.
• Turnout and travel. Unit notified, en route, arrived on scene.
• Patient and transport. Arrived at patient, left scene, arrived at destination, transfer of care.
• Release. Back in service, or cancelled.

Clock synchronization across CAD, station alerting, mobile devices, and the records system is a recurring failure point: unsynchronized clocks produce negative intervals and arrivals that precede dispatch, corrupting every percentile calculated later. Report performance as fractile measures rather than averages, which is how NFPA deployment standards and accreditation frame it.

Hospital outcomes and closing the loop

Without outcome data, an agency knows what it did and not whether it helped. Exchange usually takes one of three forms: a direct interface with a receiving hospital, participation in a regional or state health information exchange, or a vendor operated network that matches patient care records to hospital encounters. Matching is typically probabilistic, using identifiers and arrival time rather than a shared record number. Trauma, stroke, STEMI, and cardiac arrest registries do similar work. All of it depends on permitted uses and disclosures and usually a written agreement, so have counsel review the arrangement before data moves.

Quality assurance, privacy, and public records

A workable quality program reviews every record in high-risk categories such as cardiac arrest, advanced airway management, pediatric patients, refusals, and controlled substance administration, plus a random sample of routine calls. Reviews score records against stated clinical indicators and return findings to providers under the medical director's authority. The system should track review status and feedback, not simply store the chart.

Patient care reports are protected health information; fire incident reports are more often disclosable public records subject to exemptions. The two collide when clinical detail lands in a fire narrative, so train crews to keep patient information in the patient record. Many states also shield peer review materials from disclosure, with limits; confirm the scope in your state before promising reviewers confidentiality.

What to ask vendors and require in the contract

• Standards conformance. Which NEMSIS version the product produces, whether it validates before submission, and its path for national fire reporting.
• Data ownership and export. Full export in native standard format, including narratives, attachments, and audit logs, during the term and at termination, at no charge.
• CAD interface. Which interface, who maintains it, and what a change costs when the CAD system is replaced.
• Offline behavior. What happens in a basement or a rural coverage gap, and how conflicts resolve on sync.
• Analytics access. Read access to a database replica or warehouse, not only the canned reports.
• Security terms. A business associate agreement, hosting location, access controls, logging, and breach notification timelines.

HQT works with state and local agencies on public safety records systems, CAD and hospital integrations, and the data quality work behind them.

Frequently asked questions