EIDO & IDX FAQ (Frequently Asked Questions)

Test Page Note. The same content is shown in a table format here: EIDD Frequently Asked Questions (test page for table format). Before deciding a preference for either the table or non-table format, please view the pages on as many devices as possible, including desktop, tablet, and smart phone.

If you have questions about EIDDs that are not answered here, put them in the Discussion page. You can also use the Discussion page to submit comments, suggestions, or improvements on the answers you see here.

EIDD Basics

What is an EIDD?

"EIDD" is an abbreviation for Emergency Incident Data Document.

Here's the official NENA Master Glosssary definition: A National Information Exchange Model (NIEM) conformant, object that is used to share emergency incident information between and among authorized entities and systems.

Here are some other ways to describe an EIDD:

An EIDD is an XML document conforming to a standard schema that contains current information about a call, the associated emergency incident, or responder assets.

An EIDD is a way to label current information about an incident using a standard format so you can send the information from one system to another.

Where are the EIDD specifications?

There are several documents where the specifications and requirements relating to EIDDs are published:

• The format and XML schema for EIDDs is specified in an APCO/NENA standard that can be downloaded: NENA/APCO Emergency Incident Data Document (EIDD)
• The requirements for PSAP functional elements for sending and receiving EIDDs are included in the NENA/APCO NG9-1-1 PSAP Requirements Document
• EIDDs used for transferred calls and other aspects of EIDDs are published in NENA-STA-010 Detailed Functional and Interface Standards for the NENA  i3 Solution

NENA Working Groups are currently developing additional documentation for EIDDs and their use:

• EIDD Conveyance: Conveyance of Emergency Incident Data Document (EIDD) Working Group
• EIDD Management: Management of Emergency Incident Data Documents (EIDD)
• IDX Functional Element: i3 Architecture
• EIDD Specifications for NG9-1-1 PSAP Functional Elements: NG9-1-1 PSAP SYSTEMS

Is there a standard XML schema for the EIDD?

Yes. The NIEM-Conformant IEPD (Information Exchange Package Document) is available here: NIEM IEPD (Schemas & other documents)

Why do we need EIDDs?

We need a way for one system that has information about an incident to send that information to another system using a standard format. That way, both systems can understand the information, even if the systems are from different vendors or operated by different agencies. In NENA documentation, these systems are often also called functional elements (FE).

Sending EIDDs

What functional elements can send or receive EIDDs?

The functional elements in NG9-1-1 that can send or receive EIDDs are shown here: FE (Functional Element)

When does a functional element send an EIDD?

A functional element sends an EIDD when it detects a change in the status of an incident. Want some examples? They're next.

What are some examples of when an EIDD would be sent?

• A call-handling FE would send an EIDD to the incident-handling FE when a call arrives. The EIDD would include the caller information that came with the call's signalling data.
• The same call-handling FE would send another EIDD to the incident-handling FE when the call is answered. That EIDD would add the identity of the agent that answered the call and other information.
• If the call-taker types notes, an EIDD with the notes, agent's identification, etc. would be sent from the incident-handling FE to the dispatch FE.
• If a dos[atcher dispatches a firetruck, an EIDD with the details would be sent to incident handling, and maybe call-handling so the call-taker would know.

EIDD Contents

What information does a functional element put in an EIDD when it sends one?

An FE puts information about the current state of the incident that it "knows". Depending on which FE generates an EIDD, it might include the caller's information like name, number, and location. EIDDs can also include agents' notes, information about responder equipment and lots of other incident information.

You can find details on all of the kinds of information that can be transferred in an EIDD in the NENA/APCO Emergency Incident Data Document (EIDD).

There is also a handy Excel spreadsheet guide to all of the kinds of XML elements that can be in an EIDD in the EIDD Mapping Spreadsheet.

Does an EIDD include voice or other media?

No, but it may contain links where various forms of media can be accessed.

EIDD Transport

What protocol is used to send EIDDs from one element to another?

There is a SIP-based transport specification in development and an HTTP-based specification suggested.

IDX (Incident Data eXchange)

What is the IDX?

The IDX (Incident Data eXchange) is a functional element that receives EIDDs from other elements in a PSAP and aggregates the information in order to send a consolidated view of an incident upon to subscribers.

Who subscribes to an IDX

Subscribers can be elements both within and outside of the PSAP. They may be regional or state agencies inside an ESInet and they may be outside agencies or services.

What are examples of outside agencies or services.

Outside recipients of EIDDs might include power and gas utilities, ambulance services, hospitals, U.S. government agencies like the DHS (Department of Homeland Security), towing services, etc.