NFIRS Codes Cheat Sheet - NFIRS Coding - NFIRS Examples - FDIDs - POCs
Definition: The incident number is a unique sequence number (unique within a given day.)
Entry: This is NOT necessarily the incident identification number, however in case with CAD (Computer Aided Dispatch) generates an identifier as an incrementing sequence number throughout the year, this can work.
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 Number (Identifier)’.
Rule | Group | Overview |
---|---|---|
Relational Edit Rule 1 | Transaction | Key must be Unique. |
‘Incident Number (Identifier)’ is a key element, so it is in pretty much all transactions.
Specification | Value |
---|---|
Requirement | Mandatory |
Maximum Length | 7 |
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. - Maximum length 7 characters |
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.