NFIRS Codes Cheat Sheet - NFIRS Coding - NFIRS Examples - FDIDs - POCs
Definition: The date the initial incident occurs, which is only different from the incident date/time if this is an exposure on the initial fire, and the exposure occurs on a subsequent day.
Purpose: In conjunction with other required Section A fields, this element uniquely identifies each incident.
Entry: The Incident Date is the same as the Alarm date (Block E1), except if the incident is an exposure and the exposure occurs on a subsequent day.
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 ‘Incident (Alarm) Date’.
|Relational Edit Rule 22||Arrival after Alarmed.|
|Relational Edit Rule 23||Controlled after Alarmed.|
|Relational Edit Rule 24||Alarmed before Cleared.|
‘Incident (Alarm) Date’ is a key element, so it is in pretty much all transactions.
|Element Type||Numeric - Integer numbers (no decimal points). If the user has not provided information, an empty field should be transmitted. All integer values are assumed to be positive. Any fields which allow a negative integer value have been denoted with ‘+ or –’ in the comment field. Negative numbers should be transmitted with the minus sign preceding the digits. - - Date only|
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.