Skip to content
English
Go to angeltrack.com
  • There are no suggestions because the search field is empty.

Fire Database Uploads / NERIS Reporting

Learn how AngelTrack automatically performs your fire database reporting.

Data Validation

NERIS reports are subject to national validation rules. AngelTrack has these rules onboard and enforces them when crew members attempt to submit their reports QA, and again when QA passes a report onward.

The FSRI national database also applies the rules on every upload, and rejects the upload if necessary, in which case AngelTrack captures the rejection message(s) and sends the dispatch to the Outflow Queue where it will await correction.

For a more detailed explanation of these validation steps, refer to the Outflows Guide, which explains it in terms of EMS uploads that are treated similarly.

"Jumping" a call over QA review

If a supervisor "jumps" a dispatch over QA review, skipping the checks to send it straight to "Billing office" or "Finished", then AngelTrack is required to upload it even though the crew and the QA reviewer did not have a chance to check and correct any data validation errors.

AngelTrack will perform a final data validation right before upload, and this might fail for a "jumped" call. Such failing calls will appear in the Outflow Queue Queue as validation failures. From there you can open the reports to make corrections, or open the run tickets to send them back to the crews to be fixed, or tell AngelTrack to try the validation again.

NERIS Uploader

AngelTrack's NERIS uploader is a RESTful client conforming to the F.S.R.I. webservice.

It can upload directly to F.S.R.I. on your behalf, or it can upload to any other webservice that emulates the F.S.R.I. webservice's API.

It has automatic linear backoff/retry capability, and is gentle to the receiving server by uploading no more than two reports per minute. If it encounters any error, it will report it to you by raising a warning flag on the Settings icon on the AngelTrack home page.

To configure the uploader, find the Outflows item under the Settings page. To add a new credential, click the Add.large-4 plus sign.

F.S.R.I. Onboarding / Account Provisioning

AngelTrack already has a built-in username (aka Client ID) and password (aka Client Secret) for use when uploading data on your behalf to FSRI. Therefore, when you configure an outflow credential for the FSRI, you don't need a URL, or a username, or a password, because all of that is built-in.

However, you must perform the following steps before AngelTrack is permitted to upload to FSRI on your behalf:

  1. Obtain your NERIS ID, also known as your entity ID. AngelTrack cannot obtain or issue it for you. A proper NERIS ID looks like one of these:

    • FDxxxxxxxx (for a fire department), for example FD12345678

    • VNxxxxxxxx (for a vendor)

    • FMxxxxxxxx (for a fire marshal)

    • FAxxxxxxxx (for a federal agency)

  1. In your FSRI dashboard, select the Enrollments item from the left-hand menu, and add AngelTrack. If you cannot find the AngelTrack integration by name, then you can find it by its Vendor ID, which is VN00664628, or its Client ID, which is: 6e77d5e4-4799-4172-b98d-742b7efeca5b

  2. Back in AngelTrack, input your NERIS ID into the "Fire Ops" section of the Agency Information page, which is available under Settings. While you are there, fill out the other datafields that describe your department.

  3. Still in AngelTrack, go to the Outflows page (also under Settings) and create a new outflow credential. Set the payload type to "NERIS v1", give the credential a name like "FSRI National Fire Database", leave everything else set to defaults, and save.

AngelTrack will begin automatic uploads of your data. After a while, check back on the Outflows page to verify that data is flowing.

Multiple Authorities / Multiple Credentials

AngelTrack's outflows system can upload to multiple authorities, in a cascade:

  1. Incident city
  2. Incident county
  3. Statewide

That is, each credential in the uploader can have a jurisdiction city, or a jurisdiction county, or be a statewide credential. To decide where each report should be uploaded, AngelTrack checks for a city match, and if not found then a county match, and if not found then a statewide credential.

For example, suppose you have a credential for the city of Dallas and another for the city of Fort Worth, plus a credential for Tarrant County, and finally a statewide credential. AngelTrack will then decide jurisdiction like this:

  1. Check to see if the incident occurred within Dallas or Forth Worth, and if so, upload it using those credentials.
  2. If no match found by city, then check to see if the incident occurred within Tarrant County, and if so, upload it using that credential.
  3. If no match found by city or by county, then upload it using the statewide credential.

In this manner, you can create a cascade of credentials for the different authorities to which you must submit reports. To learn more, please visit the Outflows Guide.

Note that this does not apply to ET3 uploads, to CAD pushes to ESO, or to progress-report pushes to HealthEMS, to Movi, and to VectorCare. All of those have their own separate uploaders and so run independently of the outflows system.

'Entity' Payload / Demographic Upload

FSRI requires AngelTrack to upload your agency information, the list of your stations, and each station's list of vehicles. This is called an 'Entity' payload, and is equivalent to the 'Demographic' payload of the EMS world.

This information will appear in your FSRI console. If you need to make changes to it, make the changes in AngelTrack, not in FSRI, otherwise AngelTrack will overwrite your changes during the next Entity upload.

You can configure any outflow credential to NOT perform an 'entity' payload, if you are sending data to some other fire registry that doesn't want it, but it is mandatory for FSRI uploads.

Inactivity Reports

If you respond to zero incidents during a calendar month, NERIS requires you to submit an inactivity report. AngelTrack does this for you, automatically, to every active credential.

NERIS-Assigned Trip IDs

When AngelTrack first uploads a dispatch to the FSRI national database, NERIS will assign a unique incident identifier. The identifier looks like this:

FDxxxxxxxx|yyyyyy|zzzzzzzz

...where:

  • FDxxxxxxxx is your department's NERIS entity ID;

  • yyyyyy is the AngelTrack dispatch ID; and

  • zzzzzzzz is a NERIS-assigned unique number.

If you upload to the FSRI national database and also to a state fire database, then each database will assign its own unique ID to the trip. IDs assigned by state fire databases might not look like a NERIS incident identifier. In any event, AngelTrack keeps track of all of them for you, because they are needed for any reupload if the underlying data later changes.

You can review all NERIS-assigned trip IDs from the "Outflows" tab of the relevant dispatches.