ESRI EMS Solutions should seek to be NEMSIS V3 Complaint

504
2
07-20-2023 04:23 PM
Status: Open
Jen_Zumbado-Hannibal
Occasional Contributor

The National Emergency Medical Services Information System (NEMSIS) is part of the National Highway Traffic Safety Administration Office of Emergency Medical Services (EMS). This national system is used to collect, store and share EMS data from all fifty states and territories. The system's primary goal is to improve prehospital patient care by using standardization, aggregation, and point-of-care EMS data at all levels of government. 

Hence, although ESRI developed Fire and EMS solutions, I'm not seeing them in the list of companies seeking V3 compliance. Why is this not a goal for ESRI? 

ESRI has been pretty good at being very proactive in adopting standards for every industry. However, I wonder why it's lagging behind in this very important area, especially after the pandemic. 

I can't endorse any ESRI solution to my current Fire Department because it is not NEMSIS V3 compliant. 

So, please start either developing solutions with NEMSIS V3 standard in mind or, start partnerships with major vendors to integrate GIS Fire and EMS solutions into their software. You've done with everyone else. Why not with EMS? 

Thanks. 

2 Comments
mcox_fire

Jen, 

Thank you for your comment. 

Our many RMS, CAD, and performance analytics Partners deal with NEMSIS data regularly.

And while we are identifiying EMS focused solutions, our current solution workflows do work for EMS response data just like NFIRS or crime data.

Partners like ESO and First Due for RMS, and Bradshaw (BCS) and Deccan for analysis, regularly use NEMSIS data.

If you have any ideas for EMS focused solutions I would love to hear about them. Feel free to email me: mike_cox@esri.com

Thank you, 

Mike

Jen_Zumbado-Hannibal

An EMS jurisdictional solution would be nice. There are many situations in which calls get routed to the nearest EMS or Fire station, yet, they belong to different jurisdictions. Thus, the rates for services are calculated differently. So, having a map/dashboard depicting where the calls came from and the overall cost for calls outside jurisdictional areas would be nice.