Transaction Type (Add, Update, Delete) - NFIRS
NFIRS Codes Cheat Sheet - NFIRS Coding - NFIRS Examples - FDIDs - POCs
National Fire Incident Reporting System. Reporting by Responserack Fire Department NFIRS RMS.
NFIRS 5.0 Element: ‘Transaction Type (Add, Update, Delete)’
Definition: Defines the intent of this transaction upon the NFIRS system. Should NFIRS read this as an ‘add’ or ‘change’ or ‘delete’? ‘No Activity’ is a special use case, for when no incidents have occurred in this reporting period.
Entry: ‘Blank’ = Add, 1 = Change, 2 = Delete, 3 = No Activity
Need something else? Here is the complete list of all NFIRS modules and subsequent NFIRS transactions, plus a list of all NFIRS elements.
Relational Edit Rules for ‘Transaction Type (Add, Update, Delete)’
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 ‘Transaction Type (Add, Update, Delete)’.
| Rule | Group | Overview |
|---|---|---|
| Relational Edit Rule 1 | Transaction | Key must be Unique. |
| Relational Edit Rule 3 | Transaction | No Duplicates except to Lookup Edits. |
| Relational Edit Rule 4 | Transaction | Delete and No Activity require minimal fields. |
Need to replace your Fire RMS?
Responserack provides innovative middle-of-the-night firefighter-simple volunteer fire department software and NFIRS incident reporting software. Learn how Responserack helps your volunteer fire department.NFIRS Coding
Here are the NFIRS codes for the ‘Transaction Type (Add, Update, Delete)’ element, including any “other” values in case none of the preselected choices match:
All values for Transaction Type (Add, Update, Delete)
| Transaction Type (Add, Update, Delete) | Code |
|---|---|
| Add | Leave Blank |
| Change / Update | 1 |
| Delete | 2 |
| No Activity | 3 |
Transactions containing ‘Transaction Type (Add, Update, Delete)’
‘Transaction Type (Add, Update, Delete)’ is a key element, so it is in pretty much all transactions.
- Incident Header
- Basic Incident
- Incident Address
- Aid Given Received
- Officer In Charge
- Member Making Report
- Incident Remarks
- Fire
- Structure Fire
- Wildland Fire
- Fire Mobile Property Involved
- Fire - File attached
- Fire - Equipment Involved
- EMS Patient
- Arson
- Arson Agency Referral
- Arson Juvenile Suspect
- Apparatus
- Personnel
- Fire Department Header - for Fire Department records
- Fire Department Personnel - for Fire Department records
- Fire Department Apparatus - for Fire Department records
- Civilian Fire Casualty
- Fire Service Casualty
- Fire Service Casualty - Equipment Failure
- Special Study
Element Specification
| Specification | Value |
|---|---|
| Requirement | Mandatory |
| Maximum Length | 1 |
| 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. - Maximum length 1 characters- Blank is a valid value |
Need more NFIRS help?
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.