EIDO & IDX FAQ (Frequently Asked Questions): Difference between revisions

Added links to NENA/APCO-INF-005.1 EIDD Information Document
m ("an" to "a")
(Added links to NENA/APCO-INF-005.1 EIDD Information Document)
Line 1:
NENA-REF-011.X (DRAFT)
 
NOTE: "EIDO" refers to a JSON - formatted Emergency Incident Data Object. The EIDO specification in development is based on the [https://www.nena.org/page/EIDD_INF NENA/APCO-INF-005.1 EIDD informationInformation documentDocument] and other NENA documents that refer to "EIDDs" which describe XML - formatted documents.
 
The answers shown here are based on the point in time when they were provided, based on the then current applicable specifications. All answers are subject to change if the applicable specifications change. NENA will endeavor to keep this document in sync with any changes made in the applicable specifications that would cause these answers to be outdated. Those applicable specifications (Standards) are the normative source, and this document is informative.
 
== EIDO Questions & Answers ==
<br />
 
=== What is an EIDO? ===
"'''EIDO'''" is an abbreviation for '''<big>E</big>'''mergency '''<big>I</big>'''ncident '''<big>D</big>'''ata '''<big>O</big>'''bject.
Line 22:
 
=== Where are the EIDO specifications? ===
There are several documents where the specifications and requirements relating to EIDOs are published or being developed:
*'''The EIDO specifications are being developed''' from the [https://www.nena.org/page/EIDD_INF NENA/APCO-INF-005.1 EIDD Information Document]
*'''The requirements for PSAP functional elements for sending and receiving EIDOs''' are included in the [https://www.nena.org/?NG911_PSAP_REQ NENA/APCO NG9-1-1 PSAP Requirements Document] where they were described as "EIDDs".
* '''EIDOs used for transferred calls and other aspects of EIDOs''' are published in [https://www.nena.org/?page=i3_Stage3 NENA-STA-010 Detailed Functional and Interface Standards for the NENA  i3 Solution]
Line 33 ⟶ 34:
 
=== What kind of information is in an EIDO? ===
An EIDO contains information about a single incident including: the calls related to that incident, the responders assigned to the incident, the participants and vehicles involved in the incident, etc. EIDOs will often include the caller's information like name, number, and location. EIDOs can also include agents' notes, information about responder equipment, agencies involved in the incident, and lots of other incident information. You can find details on all of the kinds of information that can be transferred in an EIDO in the [https://www.nena.org/page/EIDD_INF NENA/APCO-INF-005.1 EIDD Information Document].
 
=== Is there a standard JSON schema for the EIDO? ===
Line 88 ⟶ 89:
The current proposed transport draft uses Subscribe/Notify to send updated EIDOs. The mechanism includes filters that allow the recipient to control the rate of transmission. The sender can decide how often to send updates, which could be as often as every character, or as little as complete notes. The recipient can limit how often it receives EIDOs using the rate filters.
 
=== The APCO-NENA EIDOEIDD INF document says that an EIDOEIDD does not provide historical data. What does that mean? ===
ItThe meansEIDO specification that youis being developed from the [https://www.nena.org/page/EIDD_INF NENA/APCO-INF-005.1 EIDD Information Document] indicates that the EIDO only getincludes the entire (not delta) CURRENT ‘state’ of the incident, as known by the sender. Historical data is stored in, and retrieved from the logging service.
 
=== How do I determine that something has changed during the course of an incident? ===
Line 227 ⟶ 228:
=== NENA-STA-010 ===
[https://www.nena.org/page/i3_Stage3 NENA Detailed Functional and Interface Standards for the NENA i3 Solution]
 
=== NENA/APCO-INF-005.1 ===
[https://www.nena.org/page/EIDD_INF EIDD Information Document]
 
[[Category:Proposed Draft]]