Contact

GlossaryFire and EMS reporting

NERIS ID

A NERIS ID identifies an entity in the national fire-service reporting system. It is distinct from a legacy FDID, local incident number, or service-area code.

A NERIS ID is an identifier assigned within the National Emergency Response Information System. In an agency profile or department reference file, it commonly means the entity ID identifying that organization. The field's full name matters: an entity identifier should not be confused with an incident number, unit identifier, or legacy fire-department code.

Identifying the organization consistently

Departments can have similar names, use abbreviations, or change their public-facing names. An assigned identifier helps connect records to the correct organization without relying solely on text matching.

USFA's NERIS data FAQ describes an entity ID as a ten-character alphanumeric identifier, with an initial letter pair indicating an entity type. Its examples include FD for fire departments and FM for fire marshals. The FAQ also describes entity verification and state fire-marshal involvement for fire-department IDs. USFA entity-ID explanation.

Oregon State Fire Marshal's agency-information guidance separately explains that an agency's assigned NERIS ID identifies it uniquely across the nation. This corroborates the organizational role without making the ID a description of the agency's geography or capabilities. Oregon NERIS guidance.

Example

Hypothetical example: Two departments in different states both use the public name “Riverview Fire.” A national reference file gives each its own NERIS entity ID. A monthly incident export includes the relevant entity ID, allowing the records to be matched to the correct department.

Joining on the name alone could combine the two departments' activity. Joining on an exact, documented entity identifier avoids that particular ambiguity, provided the reference file is appropriate for the period.

Now suppose one department operated under a legacy NFIRS FDID in older data. The analyst uses an official correspondence table or verified department reference to connect the old and new identifiers. They do not assume that the numbers match or create a new ID by adding a prefix.

Common confusion

Entity ID versus incident ID: The entity identifies the organization; the incident identifies an event record. One department identifier can legitimately appear on thousands of incidents.

NERIS ID versus FDID: The NERIS entity system and legacy NFIRS department identification are different frameworks. A crosswalk, meaning a documented correspondence between identifiers, is needed for reliable historical matching.

Identifier versus geography: An entity ID does not define a service-area boundary. A department may serve multiple communities, share responsibilities, or assist outside its usual area. The service map requires separate evidence.

Identifier versus endorsement or coverage: Having an identifier does not prove complete reporting, public access to every record, or participation in any unrelated product or partnership.

Using the field accurately

Preserve the complete value as text, including letters and zeros. Keep the original identifier alongside a readable agency name. If a file uses several NERIS-related ID fields, consult its dictionary to determine which identifies the reporting organization and which identifies another entity or resource.

For mergers, name changes, or historical comparisons, verify the period covered by the agency reference. A stable-looking name can conceal an organizational change; a different name can still refer to the same entity.

If the public record does not supply a verified correspondence to an older identifier, describe the match as unresolved. An uncertain join can misattribute an entire department's activity, so a precise identification boundary is more useful than a guessed connection.

Sources