NFIRS 5.0 Element: ‘Transaction Type (Add, Update, Delete)’
Delete: Check or mark this box when you have previously submitted data on this incident and now want to have the data on this incident deleted from the database. If this box is marked, complete Section A and leave the rest of the report blank. This will delete all data regarding the incident. Forward the report according to your normally established procedures.
Change: Check or mark this box only if you previously submitted this fire incident to your State reporting authority and now want to update or change the information in the State database. Complete Section A and any other sections or blocks that need to be updated or corrected. If you need to blank a field that contains data, you must resubmit the original module containing the newly blanked field along with all the other original information in the module for that incident. This action is required only when sending an updated module to your State reporting authority. Forward the report according to your normally established procedures.
No Activity: If the fire department has had no incidents during the month, a no activity report should be submitted. Unless otherwise specified by the State, this report should be submitted monthly according to your normally established procedures.
|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|
Transaction Type (Add, Update, Delete) CODES
Here are the NFIRS codes for the ‘Transaction Type (Add, Update, Delete)’ element,
|Transaction Type (Add, Update, Delete)||Code|
|Change / Update||1|
Relational Edit Rules for ‘Transaction Type (Add, Update, Delete)’
NFIRS defines relational edit rules to ensure data consistency and accuracy in its database. These are the rules for ‘Transaction Type (Add, Update, Delete)’.
|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.|
Transactions containing ‘Transaction Type (Add, Update, Delete)’
The value of this element is captured by the following transaction :
- Incident Header
- Basic Incident
- Incident Address
- Aid Given Received
- Officer In Charge
- Member Making Report
- Incident Remarks
- Structure Fire
- Wildland Fire
- Fire Mobile Property Involved
- Fire – File attached
- Fire – Equipment Involved
- EMS Patient
- Arson Agency Referral
- Arson Juvenile Subject
- 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
Need more NFIRS help?
Here are some other useful ressources to learn more about NFIRS.
NFIRS Codes Cheat Sheet – NFIRS Coding – NFIRS Examples – FDIDs – POCs – NFIRS Transactions – NFIRS Modules – NFIRS Elements – NFIRS Rules – NFIRS Reference – NFIRS Compliant ?
You can also read this NFIRS 5.0 Complete Reference Guide, and NFIRS 5.0 Design Documentation in order to have a deeper understanding of NFIRS 5.0. Here are also NFIRS 5.0 Forms ready for you to download and use.
We are here to help, Feel free to contact us if you need any additionnal informations.
Last Updated on May 9, 2023