As we deploy NG9-1-1 across the country, the focus has a tendency to be on receiving and transporting the “call”. What about all of the data (information pertaining to that call) that also needs to be transported along with it? NG9-1-1 has accounted for that data, it’s called the Emergency Incident Data Document (EIDD) which is the container for moving that data from the PSAP receipt of the call and initiation of the incident, all the way through to its end. The movement of that information is managed by the Incident Data Exchange (IDX) functional element. These items can be part of the transport of a call/incident from one PSAP to another and/or could be a request for services by CAD or other means. One of the questions concerning NG9-1-1 is; if another PSAP answers my call, how do I get the information back so that I can send the first responders? EIDD will likely be the answer to that question.
The “FAQ” gives a summary of both the EIDD and the IDX. It is by no means the detailed explanation of these entities but rather is designed to provide a working knowledge of what these items are and, equally important, what they are not.
Please help us help you by reading through this document and let us know if you find it helpful. If this system was in place today in your PSAP, do you think it would help your telecommunicators, or will it make their job more difficult? We would love your feedback and don’t hesitate to let us know if you have questions by sending an email to email@example.com.
Pete Eggimann, ENP and Jim Shepard, ENP
NENA Development Steering Council Co-Chairs
Additional Information may be found in the following documents:
NG9-1-1 Emergency Incident Data Document (EIDD)
Detailed Functional and Interface Specification for the NENA i3 Solution
If you would like to learn more and get involved, NENA currently has 2 WGs related to EIDD you may join.
Management of EIDD