NERIS Reporting Announcement

Modified on Thu, Aug 7 at 7:19 AM

EMERGENT NERIS REPORTING
Emergent is championing the transition to NERIS, bringing next-generation enhancements to how fire and EMS agencies create, manage, and report incident records. Behind the scenes, our team has been focused on building intuitive, NERIS-approved tools that simplify records creation while unlocking deeper insights -- so agencies can stay compliant and ahead of the curve.

UPDATE
On Wednesday afternoon August 6th (web portal) and Thursday afternoon August 7th (iPad), Emergent will be deploying the first generation of their NERIS ready RMS solution for customers to begin to play with.  This release allows customers to record the data that NERIS accepts in the NERIS approved formats.  We are however, by no means, at the finish line.  We have just begun.  Over the coming weeks and months, we will be continuing to improve the tools, with improved data integration with CAD as well as the Tactical Board, improving workflows to make the data collection better and more streamlined than NERIS requires and ultimately generating the end report to submit to NERIS.  

 

PORTAL KEY DIFFERENCES
Previously, in the web portal, you would see the incidents that came from PulsePoint or were created manually on the iPad, and you could view the Tactical Board Timeline as an attachment:

A screenshot of a computer

AI-generated content may be incorrect.

 

With the updates rolling out on Wednesday, the portal will have a new interface.   The left side of the incident contains all of the call details on the old interface, and the right side has new information…

Status of Active will reflect PulsePoint calls that have an active iPad session going.  Manually created incidents will not show on the portal until the user hits End Incident and Upload Report on the iPad

Tactical Board Used will update that Tactical Board state after the user has hit End Incident and Upload Report on the iPad

Incident Report Started will reflect the state of the Incident Report from the iPad after the user has hit End Incident and Upload Report, or if the Incident Report has been worked in the Portal.

A screenshot of a computer

AI-generated content may be incorrect.

 

You can click on an incident to being to explore the NERIS Incident Reporting. 

Remember: To get an incident to show on the list without the PulsePoint CAD integration, you will need to manually create the incident on the iPad and then hit End Incident and Upload Report.  Once you have done that, refresh your browser and the new incident should show on your list.

 

iPad KEY DIFFERENCES
Previously, on the iPad after you started an incident the app took you to the Incident Map with navigation like this.

 

With the updates rolling to the iPad on Thursday afternoon, the Fire module will have a new look and feel.  

A map of a city

AI-generated content may be incorrect.

 

Once you enter the incident, you can navigate to the Situation tab to access the NERIS Reporting interface.  You will be prompted to specify the incident type (or types, up to 3) and then you will access the report.  NOTE:   The screen map looks different because of 2 different locations used – there were no changes made to the map at this time.

The types of incidents you select will drive what data is collected.  In the screenshot below, I specified  Fire, Hazardous Situation and Medical incident types, so there are 3 extra fields of data collection.

A screenshot of a computer

AI-generated content may be incorrect.

The iPad is designed to streamline data collection.  A such, no fields are required on the iPad.  Users can populate as much as desired or needed while mobile and complete the report on the Portal once they hit END CALL and UPLOAD REPORT.

 

Our development team is continuing to work on both the iPad and the Portal side, as well as the logic in between.  If you experience connectivity issues with the iPad data syncing to the Portal, do know that is an area of focus they are working on, and it may be up and down as they work to improve that data flow.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article