NFIRS - NFIRS Codes - NFIRS Examples
NFIRS 5.0 coding is “how turned out” not “how toned out”. An incident may be toned as smoke report, or (seemingly inarguably & precisely) motor vehicle accident with rollover, or medical, but if it ends as unable to locate (UTL) it should be coded as 622 - No Incident Found. How it is toned does not matter for NFIRS coding, it is how it turns out.
Admittedly a call to MVA with precise details (so detailed they have to be witnessing it) that ends up as UTL appears to be in the malicious, mischievous false alarm group, however if it cannot be proven as such, then it should be coded as 622 - No Incident Found.
Even if there is no precise “dispatch address”, e.g. a smoke report in a general area with no reporting party (RP) address not callback, this UTL should be coded as 622 - No Incident Found.
All UTLs are coded as 622 - No Incident Found.
These are some of the values in the wrong location / no incident found group:
Unable to locate is when nothing can be found at or in the area of the incident report. However if something is found, but not an incident (e.g. phone line down not powerline down, legal campfire not illegal or unattended campfire) then report a Good Intent incident type.
Unable to locate is when nothing can be found at or in the area of the incident report. However if something is found, but UTL incident Good Intent
See more NFIRS coding examples for quick “how to” coding snippets:
For more information see the NFIRS / eNFIRS training and contact Responserack if you would like more help with NFIRS or eNFIRS.