NERIS FAQ | NERIS Specification | NERIS Fire Department Specification | NERIS Incident Specification

 

NERIS Draft Specification

Note: NERIS is currently a draft specification (where this is based upon version: V0.1 - December 2023) and is subject to change.

NERIS - is a DRAFT SPECIFICATION, presented here to aid in review
WORK IN PROGRESS: This information is draft and subject to change. We have presented this information in order to promote review and feedback on the specification. Please provide your feedback to the NERIS team.

CAD Core Specification

CAD Core Specification

The NERIS CAD core specification is information gathered by the Computer Aided Dispatch (CAD) system, or perhaps a Fire Records Management System (Fire RMS.) Gathering information here allows for less redundant data entry but the end firefighter.

 
 

Data Framework

The data framework provides fields and definitions for the data.

General

  • fd_neris_id - This 10 digit integer is a unique identifer for each fire department. Entity type plus state and county FIPS plus with random trailing characters.
  • dispatch_center_id - This 4 digit integer is a unique identifier for each PSAP dispatch center.
  • dispatch_comments - Free text and canned remarks comments from distpatcher throughout duration of call.  
     

Incident Details

  • incident_number - Unique numeric identifier for the event that requires dispatch of department resources.
  • incident_address_1 - House number and street name of incident; can also be cross streets
  • incident_address_2 - Additional address information
  • incident_city - City in which incident occurs
  • incident_state - State or Territory in which incident occurs
  • incident_zip - Zip Code in which incident occurs
  • incident_county - County in which incident occurs
  • incident_census - Census Tract in which incident occurs
  • incident_latitude - WGS84 latitude of incident
  • incident_longitude - WGS84 longitude of incident
  • incident_battalion_name - The battalion in which the incident occurs
  • incident_battalion_geometry - The geometry of the battalion in which the incident occurs
  • incident_first_due_name - The first due area where the incident occurs; often a subset of battalion
  • incident_first_due_geometry - The geometry of the first due area where the incident occurs
  • incident_area_name - The department-specific area where the incident occurs; often a subset of first due area
  • incident_area_geometry - The geometry of the incident area where the incident occurs  
     

Dispatch Values

  • dispatch_incident_type - The specific incident type that details the nature of the incident; levels up into incident_category
  • dispatch_ems_category - IF EMS Category: the level of care required
  • dispatch_determinate_code - The output code from dispatch protocol based on the call specifics
  • dispatch_incident_code - The department-specific incident code pulled from CAD; levels up into incident_type
  • dispatch_coordinate_latitude - WGS84 latitute of unit
  • dispatch_coordinate_longitude - WGS84 longitude of unit
  • dispatch_lights_and_sirens - Whether or not lights and sirens are used en route
  • dispatch_final_disposition - Closing disposition of call set by dispatcher  
     

GIS Values

  • station_id - Name of the station responding to the incident
  • mutual_aid - Identifies whether or not mutual aid was provided on the incident and whether this record is associated with it being provided to another agency or received
  • mutual_aid_name - The name(s) of the Fire Department(s) where aid was received/given  
     

Data Framework Details

General

Attribute Definition Comment Mandatory
fd_neris_id This 10 digit integer is a unique identifer for each fire department. Entity type plus state and county FIPS plus with random trailing characters. Yes
dispatch_center_id This 4 digit integer is a unique identifier for each PSAP dispatch center. If not valid in PSAP registry, create NERIS dispatch ID Yes
dispatch_comments Free text and canned remarks comments from distpatcher throughout duration of call. Yes IF captured
 
 

Incident Details

Attribute Definition Comment Mandatory
incident_number Unique numeric identifier for the event that requires dispatch of department resources. Yes
incident_address_1 House number and street name of incident; can also be cross streets Yes
incident_address_2 Additional address information No
incident_city City in which incident occurs Yes
incident_state State or Territory in which incident occurs Yes
incident_zip Zip Code in which incident occurs Yes
incident_county County in which incident occurs Computed
incident_census Census Tract in which incident occurs Computed
incident_latitude WGS84 latitude of incident Yes
incident_longitude WGS84 longitude of incident Yes
incident_battalion_name The battalion in which the incident occurs Links to Core Department Spec Computed
incident_battalion_geometry The geometry of the battalion in which the incident occurs Links to Core Department Spec Computed
incident_first_due_name The first due area where the incident occurs; often a subset of battalion Links to Core Department Spec Computed
incident_first_due_geometry The geometry of the first due area where the incident occurs Links to Core Department Spec Computed
incident_area_name The department-specific area where the incident occurs; often a subset of first due area No
incident_area_geometry The geometry of the incident area where the incident occurs No
 
 

Dispatch Values

Attribute Definition Comment Mandatory
dispatch_incident_type The specific incident type that details the nature of the incident; levels up into incident_category See inc_types sheet Yes
dispatch_ems_category IF EMS Category: the level of care required Yes
dispatch_determinate_code The output code from dispatch protocol based on the call specifics Yes IF EMD used
dispatch_incident_code The department-specific incident code pulled from CAD; levels up into incident_type Yes
dispatch_coordinate_latitude WGS84 latitute of unit No
dispatch_coordinate_longitude WGS84 longitude of unit No
dispatch_lights_and_sirens Whether or not lights and sirens are used en route Yes
dispatch_final_disposition Closing disposition of call set by dispatcher Yes
 
 

GIS Values

Attribute Definition Comment Mandatory
station_id Name of the station responding to the incident Links to Core Department Spec Yes
mutual_aid Identifies whether or not mutual aid was provided on the incident and whether this record is associated with it being provided to another agency or received Yes
mutual_aid_name The name(s) of the Fire Department(s) where aid was received/given Comes from FD Specifications - Mutual Aid Agencies (for Selection Purposes) No
 
 

Data Framework Examples

General

Attribute Example
fd_neris_id FD06067001
dispatch_center_id 8747
dispatch_comments
 
 

Incident Details

Attribute Example
incident_number FDID_20230814000001, FDID_20230814000002
incident_address_1 1234 Market St
incident_address_2 Apt. Number
incident_city Baltimore
incident_state Maryland
incident_zip 21230
incident_county Baltimore County
incident_census 6059.02
incident_latitude 39.299236
incident_longitude -76.609383
incident_battalion_name 1
incident_battalion_geometry polygon()
incident_first_due_name 7
incident_first_due_geometry polygon()
incident_area_name 703
incident_area_geometry polygon()
 
 

Dispatch Values

Attribute Example
dispatch_incident_type Structure Fire, Cardiac Arrest, etc.
dispatch_ems_category ALS OR BLS
dispatch_determinate_code 17-D-5
dispatch_incident_code STRF1, ALS2, etc.
dispatch_coordinate_latitude 39.299236
dispatch_coordinate_longitude -76.609383
dispatch_lights_and_sirens Yes or No
dispatch_final_disposition No Patient Found, Building Secure
 
 

GIS Values

Attribute Example
station_id 703
mutual_aid Received, Given, None
mutual_aid_name DCFD, PGFD, etc.
 
 

 
 
Was this helpful? Please share...

Need more NFIRS help?

Need more help with NFIRS, or not yet found what you are looking for? Please see if these help …  

 
 

For more information see the NFIRS Cheat Sheet, NFIRS Coding and contact Responserack to learn about our fire department software.