Thank you for your interest in developing software for the U.S. Fire Administration's (USFA) National Fire Incident Reporting System (NFIRS).
There are no NFIRS specification changes for the January 2022 cycle. The January 2015.1 specification remains in place.
Specification enforcement began with the October 2020 release of the U.S. Fire Administration's eNFIRS applications. Learn how to comply
NFIRS 5.0 software development procedures
To get started, follow these 4 steps:
- Register your company/organization and software with the NFIRS Support Center to receive a vendor ID and a software ID. All transaction files processed at the national level are required to have these two IDs embedded in the transaction file as specified in the design documentation.
- Develop software using the NFIRS 5.0 design documentation and then test your output transaction files using the vendor validation tool.
- Notify us when your product development is completed and tested to be compatible with the national NFIRS 5.0 database standard. Send your contact information, vendor ID and software ID to FEMA-NFIRSHELP@fema.dhs.gov
- After you notify us, we will add your company/organization to the Active Vendor list. Fire departments and states use this list as a resource when shopping for a software product.
Monitoring and ensuring data quality
Because we don’t certify vendor transaction files, it is important for state agencies, fire departments and vendors to continue monitoring data quality issues. Issues with NFIRS vendor files are addressed by the fire department, the state involved and your company/organization.
- Fire departments are responsible for using the current version of your software and ensuring data files remain compatible with the national system.
- State agencies are the authority for state reporting compliance and are also responsible for ensuring data files are compatible.
- USFA acts as a resource for states to identify data problems at the national level.
Vendors should retest software after revisions or version changes. If testing files using the vendor validation tool, please review the files listed below for validation errors and/or rejected transaction information.
- Output file
- Log file of exported records
- Validation error file
- Rejected transactions file