NFIRS Codes Cheat Sheet - NFIRS Coding - NFIRS Examples - FDIDs - POCs
Definition: The reason why the detector failed to operate or did not operate properly.
Need something else? Here is the complete list of all NFIRS modules and subsequent NFIRS transactions, plus a list of all NFIRS elements.
NFIRS 5.0 relational edit validation rules are provided to ensure NFIRS data is consistent and correct for the fire/reporting concepts that are being modeled. Relational edits determine relationships between multiple fields / elements. These are the rules for ‘Detector Failure Reason’.
|Relational Edit Rule 76||If the detector failed, how did it fail?.|
Here are the NFIRS codes for the ‘Detector Failure Reason’ element, including any “other” values in case none of the preselected choices match:
|Detector Failure Reason||Code|
|Power Failure, Hardwired Detector Shut Off, Disconnect||1|
|Improper Installation or Placement Of Detector||2|
|Lack Of Maintenance, Includes Not Cleaning||4|
|Battery Missing or Disconnected||5|
|Battery Discharged or Dead||6|
|Detector Failure Reason - Other||0|
A few NFIRS elements are reused accross a number of transactions, but typically the value is captured by one transaction only.
|Element Type||Coded Field - The coded field relating to an entry in the code table. Most coded fields allow for Plus+ One codes. For these fields the expected length of the coded entry is depicted as (National length OR Plus+ One length). Only fields with this notation in the expected length column allow for Plus+ One definitions. If the user has not provided information, an empty field should be transmitted.|
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.