INDUSTRY ARTICLE (UPDATED FROM FEB 20, 2024)

NERIS Simplified:
The Data Field Changes
In Focus

Back in February 2024, we provided an early look at the NFIRS-to-NERIS transition, outlining anticipated changes in data fields and addressing key implementation hurdles, such as system integration and training.

Now that Phase 1 onboarding concluded in November 2024, and with Phase 2 scheduled to begin in February 2025, we have a sharper and more complete understanding of the reporting transformations ahead. Fire departments can now gain clarity on what to expect, from new data requirements to enhanced reporting capabilities.

Three Areas Transforming Fire Department Data

Fire department data is entering a transformative era, driven by a focus on three pivotal areas: Department Information, Dispatch/CAD Information, and Incident Information. These categories are at the core of the NERIS transition, shaping how data is collected, analyzed, and utilized to enhance reporting accuracy and operational insights.

Here’s a breakdown of each:

1. Department Information:

Streamlined Transition: NERIS introduces new ID numbers, including fields for legacy FDIDs, ensuring smooth transitions and precise data tracking throughout the changeover.
Enhanced Multi-Agency Support: Designed for flexibility, NERIS accommodates single-system, multi-agency setups with advanced features like sub-department management and parent-child indicators.
Hierarchical Organization: Information is structured logically—Department → Station(s) → Unit(s)—while offering flexibility to adjust existing data structures for compatibility.
Expanded Data Precision: NERIS adds critical new fields, including neris_id and GIS polygon coordinates, enabling more granular and accurate response area mapping.

2. Dispatch/CAD Schema:

Expanded Data Fields: While NERIS builds on existing data, it introduces additional fields that may require careful consideration for system compatibility and tailored customization.
Call Type Alignment: Standardized NERIS call types might need to be matched with client-specific call codes to ensure seamless data submission and consistency across systems.

3. Incident Schema:

Expanded Incident Categories: NERIS builds on NFIRS with additional fields, offering greater detail, particularly for critical incident categories like FIRE and EMS.
Integration with NEMSIS: Many NERIS fields align with NEMSIS specifications, allowing departments to leverage existing tables for efficient data lookup and integration.
Flexible Data Fields: Some fields, like Actions Taken, require adjustments due to their variable data inputs, ensuring precise tracking and reporting.
Enhanced GIS Integration: The inclusion of GIS data—such as incident scene outlines and coordinates—adds complexity to data collection but significantly improves the accuracy and depth of incident analysis.

By refining these data fields, fire departments will gain a deeper understanding of their operations, streamline emergency responses, and improve decision-making capabilities. This shift represents a critical step toward modernizing fire service reporting and meeting the growing demands of data-driven community safety initiatives

RedNMX NERIS hierarchical data structure of emergency services departments transitioning to NERIS

RedNMX NERIS NFIRS firefighter at a modern fire department command and dispatch center adapting to the NERIS system

NERIS Unveils Secondary Data Schemas for Improved Analysis

NERIS has introduced secondary data schemas designed to enhance incident analysis and provide fire departments with a more detailed understanding of their operations.

Here’s a brief overview of what these entail.

Incident Analysis: The incident analysis schemas were created to capture more nuanced information about both incident causes and response outcomes. Some of the most notable fields include a core analysis of:

Incident Types
Damage Assessment
Human Factors
Casualties
Consumer Products Involved

There are also modules for different incident types, including outdoor and transportation fires.

Community Risk Reduction: Community risk reduction is focused on compiling information on the surrounding community’s baseline risk. This includes new fields for building inspection information, like:

The Number of Units
Vacancy Status
Construction Details
Fire Protection Measures
Hydrant Flow Tests

New details can be included for different inspection types, including commercial, outdoor, and hydrant inspections.

Health and Safety: Health and safety schemas are designed to collect information on first responder health and safety. They include fields for:

Potential Exposures
Personnel Injuries
Demographic Information
Service and Lifestyle Information

With new fields, it will be easy to access information about shift schedules, equipment conditions, sleep hours, and injury details (including cause, location, and severity).

Implementation Challenges of the New NERIS Requirements

While the transition promises enhanced reporting capabilities, several challenges must be addressed:

1. Data Transfer Requirements:

Clarification is needed regarding the method of data submission, whether through REST endpoints, SOAP, or other protocols.

2. Approval and Submission Process:

Procedures for approval, submission statuses, and vendor verification processes require definition to ensure smooth operations.

3. System Integration:

Integrating NERIS-compliant data fields into existing systems, such as RedNMX, may necessitate updates and customization.

4. Training and Familiarization:

Fire department personnel will require training to familiarize themselves with the new reporting protocols and systems.

5. Technical Considerations:

Ensuring compatibility with existing CAD systems and addressing any discrepancies in data formatting are essential for seamless transition.

RedNMX NERIS NFIRS the expanded incident schema for FIRE and EMS categories under NERIS, illustrating the broader range of data fields, actions taken, and the inclusion of GIS data

Training for NERIS: What to Expect and How to Adapt

NERIS is poised to improve data collection, making it easier for departments like yours to track performance and make data-driven decisions. And, as your department prepares for the transition to NERIS, effective training will be a key factor in ensuring a smooth shift.

What to Expect:

In-depth Overview of NERIS Changes: A comprehensive breakdown of new data fields and reporting structures to ensure your team understands the updates.
Hands-On Training for New Features: Practical sessions on how to navigate and utilize the expanded NERIS schemas and data fields.
Customizable Training Sessions: Tailored content depending on your agency’s existing RMS and how it integrates with NERIS.
System Integration Training: Focus on how NERIS works within your current infrastructure and addressing any compatibility issues.
Ongoing Support and Resources: Access to continued learning materials and a support system to guide your department through the transition.

Understanding what to expect and how to adapt will help streamline the process, but it’s important to note that the scope and depth of training will depend largely on your agency’s existing Records Management System (RMS), as well as whether or not they’re making the NERIS transition available to their customers.

Making the NERIS Transition Easy, Together!

NERIS is designed for operational efficiency. Your RMS should do the same. Fortunately, Alpine’s RedNMX™ helps you achieve this goal by offering a complete customized reporting solution for first responders – and our software will interact seamlessly with NERIS once launched. This will facilitate an easy transition for your department.

Schedule a demo with our team today and see how we can support your transition to a new era of fire safety reporting.

NERIS Simplified:
The Data Field Changes
In Focus