Editing Computer-aided dispatch (section)

==Data exchange (EDI)==

In public safety systems, standards are under discussion to allow disparate systems to exchange call information. For example, a call taker at the county [[fire department]] receives a call for an auto accident inside a city limit. Evolving standards will allow CAD systems to send messages to one another for calls originating outside local jurisdiction. Some entities have arrangements that already support data exchange between systems, but standards aim to make these interconnections more common. Because of auditing trail and fail-safe needs, the problem is more complex than it sounds.<ref>[http://www.apcointl.org/about/datatransfer/index.html#Focus_Group_Three_DTC_FG3 Associated Public-Safety Communications Officers web site, Data Transfer Committee, Focus Group III.] {{Webarchive|url=https://web.archive.org/web/20061010050853/http://apcointl.org/about/datatransfer/index.html#Focus_Group_Three_DTC_FG3 |date=2006-10-10 }} The A.P.C.O. refers to this as Project 36.</ref>

The usage of EDI applied to CAD is specific to the law enforcement community and should not be confused with Electronic Document Interchange (EDI) standards for eCommerce. Within law enforcement EDI is used as a buzzword to represent all electronic automated messaging. 

More mature efforts to interconnect CAD can be found in the standards developed for the Intelligent Transportation Initiatives program of Department of Transportation.<ref>[http://www.its.dot.gov/ Intelligent Transportation Systems]</ref> This initiative sponsored the IEEE 1512 series of protocols for emergency management<ref>{{Cite web |url=http://grouper.ieee.org/groups/scc32/imwg/index.html |title=IEEE Incident Management Working Group |access-date=2009-02-28 |archive-url=https://web.archive.org/web/20090419201437/http://grouper.ieee.org/groups/scc32/imwg/index.html |archive-date=2009-04-19 |url-status=dead }}</ref> which provides sophisticated means to coordinate incidents across operations centers using CAD software.

Additional work is occurring under the [[National Information Exchange Model]]<ref>[http://www.niem.gov NIEM.gov]</ref> to link homeland security with CAD.  Also the [[OASIS (organization)|OASIS]] international standards body has produced standards<ref>[http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency OASIS EM TC and EDXL Emergency Data Exchange Language]</ref> funded in part by the [[United States Department of Homeland Security|DHS]] and the disaster management e-gov initiative<ref>{{Cite web |url=http://www.egov.gov/ |title=Egov.gov |access-date=2019-07-08 |archive-url=https://web.archive.org/web/20080908004634/http://egov.gov./ |archive-date=2008-09-08 |url-status=dead }}</ref> to communicate in emergencies.

Other interoperability technologies can bridge disparities between the data-format, software, and hardware that constitute various computer-aided dispatch systems in various jurisdictions. ''Middleware'', software and servers (data brokers), can translate and integrate various systems into a seamless automated dispatch system. One example of such middleware (provided by Utah-based FATPOT Technologies/CII)<ref>{{Cite web |url=http://www.fatpot.com/ |title=Fatpot.com |access-date=2019-11-13 |archive-url=https://web.archive.org/web/20180710230842/https://www.fatpot.com/ |archive-date=2018-07-10 |url-status=dead }}</ref> exists in Orange County, Calif., where the Fire Authority has integrated different emergency service answering points into a seamless dispatching network. A similar project was completed for the Silicon Valley Regional Interoperability Project (SVRIP), and is part of the Dept. of Homeland Security's CADIP report.

[[Australia]] and [[New Zealand]] use the [[ICEMS]] protocol for messaging between different CAD systems operated by various emergency services organisations.