A comprehensive reference for NERIS incident types with NFIRS code mappings. Learn how the National Emergency Response Information System (NERIS) uses hierarchical string codes instead of numeric NFIRS codes.
NFIRS vs NERIS: Understanding the Difference
The transition from NFIRS (National Fire Incident Reporting System) to NERIS (National Emergency Response Information System) brings a more descriptive and structured approach to incident typing.
NFIRS (Legacy):
Uses 3-digit numeric codes (e.g., 111, 321, 551)
Less descriptive and requires memorization
Requires code lookup tables
Example: 321 = Medical
NERIS (Modern):
Uses hierarchical string codes with || separators
Self-documenting and descriptive
Easier to understand at a glance
Example: MEDICAL||ILLNESS||CARDIAC_ARREST
Why Move Away from Numeric Codes?
NERIS's move to hierarchical string codes represents a significant improvement in data clarity and maintainability:
Self-Documenting — String codes like MEDICAL||ILLNESS||CARDIAC_ARREST are immediately understandable without reference materials. You don't need to remember that "321" means medical.
Easier Updates — When new incident types are needed, NERIS can add them without worrying about numeric code conflicts or running out of numbers in a series.
Better Data Quality — Descriptive codes reduce errors from misremembering numeric codes. When reviewing reports, the incident type is clear without cross-referencing lookup tables.
Future-Proof — The string-based system can evolve with changing needs. New categories and subcategories can be added without restructuring the entire code system.
NERIS Code Management & Deprecation
NERIS handles code updates and deprecations differently than NFIRS:
Versioned API — NERIS uses API versioning (currently v1) to manage changes. When incident types are added, modified, or deprecated, these changes are documented in the API specification and release notes.
Backward Compatibility — When NERIS deprecates an incident type, it typically remains valid for a transition period. Both the old and new codes may be accepted.
Clear Migration Paths — Deprecated codes are usually replaced with more specific or accurate alternatives. The NERIS API documentation provides migration guidance.
Stable Core, Flexible Extensions — Core incident categories (FIRE, MEDICAL, RESCUE, etc.) remain stable, while specific types can be refined.
Best Practices for NFIRS Users
If you're familiar with NFIRS and transitioning to NERIS, here are some key strategies:
Think Hierarchically — Instead of memorizing that "111" is a structure fire, think in terms of categories: FIRE → STRUCTURE_FIRE → STRUCTURAL_INVOLVEMENT_FIRE.
Use the Descriptive Names — Take advantage of the self-documenting nature. New staff can understand incident types from the code itself.
Leverage Search and Autocomplete — Modern systems can search NERIS codes by typing keywords. Typing "cardiac" will quickly find MEDICAL||ILLNESS||CARDIAC_ARREST.
Keep NFIRS Mappings for Reference — While transitioning, maintain NFIRS code mappings for historical data analysis and cross-referencing.
Embrace More Specific Codes — NERIS often provides more granular options. Use the most specific code that accurately describes the incident.
Stay Updated with API Changes — Subscribe to NERIS API release notes and documentation updates.
NERIS Incident Type Structure
NERIS incident types follow a hierarchical format: CATEGORY||SUBCATEGORY||TYPE
For example, a structure fire with structural involvement is coded as: FIRE||STRUCTURE_FIRE||STRUCTURAL_INVOLVEMENT_FIRE, which maps to NFIRS code 111.
Complete Incident Type Reference
Below is a complete enumeration of all NERIS incident types organized by category, with their corresponding NFIRS codes where applicable. This data is based on the NERIS API documentation.
