US-12628245-B2 - Emergency data exchange

US12628245B2US 12628245 B2US12628245 B2US 12628245B2US-12628245-B2

Abstract

Disclosed herein is an emergency response data platform (ERDP) that facilitates data exchange between various data sources and various data recipients. The ERDP may establish communication links with each of the various data sources and recipients and leverage these communication links to function as emergency data exchange between the data sources and/or recipients, for example, between different Public Safety Answering Points.

Inventors

Lucas Richard Eager Leavitt
David Paul SEHNERT
Jordi CABANAS
Benjamin Taylor HARVILL, III
Lauren Javaly

Assignees

RAPIDSOS, INC.

Dates

Publication Date: 20260512
Application Date: 20220927

Claims (20)

1 . A method of operating an emergency data exchange module of a cloud-based emergency response data platform, the method comprising: establishing, with the emergency data exchange module, a first communication link with a first software application executed on a first computing device at a first emergency response entity and a second communication link with a second software application executed on a second computing device at a second emergency response entity; determining, by the emergency data exchange module via a first policy store associated with the first emergency response entity, and via a second policy store associated with the second emergency response entity, a first set of emergency data sharing criteria regarding the second emergency response entity and a second set of emergency data sharing criteria regarding the first emergency response entity, both the first policy store and the second policy store operatively coupled to the emergency data exchange module; receiving, by the emergency data exchange module, emergency data from the first software application at the first emergency response entity via the first communication link; determining, by the emergency data exchange module, that the emergency data satisfies both the first and second sets of emergency data sharing criteria; and transmitting the emergency data to the second software application at the second emergency response entity, from the emergency data exchange module via the second communication link, in response to determining that the emergency data satisfies both the first set of emergency data sharing criteria from the first policy store, and the second set of emergency data sharing criteria from the second policy store.
2 . The method of claim 1 , wherein receiving, by the emergency data exchange module, emergency data from the first software application at the first emergency response entity via the first communication link, comprises: receiving the emergency data in the form of a single data object.
3 . The method of claim 1 , further comprising: storing the emergency data in the form of a single data object.
4 . The method of claim 3 , further comprising: storing the single data object as an emergency incident data object (EIDO).
5 . The method of claim 3 , further comprising: receiving updated emergency data from the second software application via the second communication link; updating the single data object using the updated emergency data; and transmitting the updated emergency data to the first software application via the first communication link.
6 . The method of claim 5 , further comprising: digitally verifying that the single data object stored is up to date and is a most recent version; and transmitting the updated emergency data to the first software application to update the single data object in response to digitally verifying that the single data object is the most recent version.
7 . The method of claim 3 , further comprising: enforcing, by the emergency data exchange module, the first set or emergency data sharing criteria regarding the second emergency response entity, by permitting the second emergency response entity to read from the single data object, and preventing the second emergency response entity to write to the single data object.
8 . The method of claim 3 , further comprising: enforcing, by the emergency data exchange module, the first set of emergency data sharing criteria regarding the second emergency response entity, by permitting the second emergency response entity to read from the single data object and write to the single data object.
9 . The method of claim 1 , wherein determining the first set of emergency data sharing criteria regarding the second emergency response entity comprises: determining that the second emergency response entity is permitted to write to a data object.
10 . The method of claim 1 , further comprising: determining at least a portion of the first set of emergency data sharing criteria and at least a portion of the second set of emergency data sharing criteria, through an emergency response entity relationship management portal accessed by the first emergency response entity and the second emergency response entity.
11 . The method of claim 10 , further comprising: receiving at least a portion of the first set of emergency data sharing criteria regarding the second emergency response entity from the first emergency response entity through the emergency response entity relationship management portal; and receiving at least a portion of the second set of emergency data sharing criteria regarding the first emergency response entity from the second emergency response entity through the emergency response entity relationship management portal.
12 . The method of claim 10 , further comprising: establishing an emergency response entity link between the first emergency response entity and the second emergency response entity through the emergency response entity relationship management portal, wherein the first set of emergency data sharing criteria and the second set of emergency data sharing criteria are associated with the emergency response entity link between the first emergency response entity and the second emergency response entity.
13 . The method of claim 12 , further comprising: determining at least a portion of the first set of emergency data sharing criteria and at least a portion of the second set of emergency data sharing criteria in response to establishment of the emergency response entity link between the first emergency response entity and the second emergency response entity.
14 . The method of claim 12 , wherein establishing the emergency response entity link between the first emergency response entity and the second emergency response entity-through the emergency response entity relationship management portal comprises: receiving, through a first instance of the emergency response entity relationship management portal, a request to establish an emergency response entity link with the second emergency response entity from the first emergency response entity; transmitting, through a second instance of the emergency response entity relationship management portal, the request to establish the emergency response entity link to the second emergency response entity; and receiving, through the second instance of the emergency response entity relationship management portal, confirmation of the request to establish the emergency response entity link from the second emergency response entity.
15 . The method of claim 10 , wherein the emergency response entity relationship management portal is accessible via a web browser.
16 . The method of claim 1 , wherein the first software application and the second software application are computer aided dispatch (CAD) software applications.
17 . The method of claim 1 , wherein the first emergency response entity and the second emergency response entity are public safety answering points (PSAPs).
18 . An emergency data exchange system configured to facilitate an exchange of emergency data between various emergency response entities, the emergency data exchange system comprising: a plurality of policy store databases, each policy store database corresponding to, and storing emergency data sharing criteria for, a specific emergency response entity that is operatively coupled to the emergency data exchange system; a network component; and at least one processor, operatively coupled to the plurality of policy store databases, and to the network component, and operative to: establish a first communication link between the emergency data exchange system and a first software application executed on a first computing device at a first emergency response entity and establish a second communication link between the emergency data exchange system and a second software application executed on a second computing device at a second emergency response entity; determine via a first policy store associated with the first emergency response entity, and via a second policy store associated with the second emergency response entity, the first policy store and the second policy store contained within the plurality of policy store databases, a first set of emergency data sharing criteria regarding the second emergency response entity and a second set of emergency data sharing criteria regarding the first emergency response entity; receive, by the emergency data exchange system, emergency data from the first software application via the first communication link; determine, by the emergency data exchange system via the first policy store and via the second policy store, that the emergency data satisfies both the first set of emergency data sharing criteria from the first policy store, and the second set of emergency data sharing criteria from the second policy store; and transmit the emergency data to the second software application at the second emergency response entity via the second communication link, in response to determining that the emergency data satisfies both the first set of emergency data sharing criteria from the first policy store, and the second set of emergency data sharing criteria from the second policy store.
19 . The system of claim 18 , further comprising: a message bus; a first emergency response entity account module associated with the first emergency response entity and configured to receive the emergency data from the first software application via the first communication link and publish the emergency data to the message bus; and a second emergency response entity account module associated with the second emergency response entity and configured to receive the emergency data from the message bus and transmit the emergency data to the second software application via the second communication link.
20 . The system of claim 19 , wherein the first set of emergency data sharing criteria is stored within the first emergency response entity account module and wherein the second set of emergency data sharing criteria is stored within the second emergency response entity account module, each emergency response entity account module comprising a policy store database of the plurality of policy store databases.

Description

CROSS-REFERENCE This application claims the benefit of U.S. Provisional Application No. 63/248,829, filed Sep. 27, 2018, the contents of which is hereby incorporated herein by reference. BACKGROUND OF THE INVENTION A person in an emergency situation may request help using a mobile communication device such as a cell phone to dial a designated emergency number like 9-1-1 or a direct access phone number for the local emergency service provider (e.g. an emergency dispatch center). Traditionally, this call is assigned to one or more first responders by the emergency service provider, and the caller's estimated location (generally either the location of a nearby cell tower or a triangulation from the location of three or more nearby cell towers) is provided to the emergency service provider by the caller's wireless carrier (e.g., AT&T). Alternatively, the caller may provide their location to the emergency service provider by verbally speaking their location over the phone. Unfortunately, many emergency callers are unaware of their precise location or otherwise unable to verbalize it. However, modern technologies have enabled the development and implementation of previously unimaginable or unachievable emergency services. For example, modern communication devices are capable of generating highly accurate, real-time locations (e.g., device-based hybrid locations) during emergency situations (e.g., in response to an emergency number being dialed) and transmitting the locations to emergency management systems and emergency service providers. Emergency service providers can then use these accurate locations to more quickly locate and dispatch emergency assistance to emergency callers. In another example, devices such as surveillance cameras can capture images, videos, or audio that can be shared in real-time with emergency management systems and emergency service providers to provide emergency service providers with situational awareness that they did not have access to in the past. SUMMARY Disclosed herein, in some aspects, is a method for exchanging emergency data between two or more emergency response entities (EREs), the method comprising: (a) providing an ERE relationship management portal to a first ERE and a second ERE; (b) receiving, through the ERE relationship management portal, a first set of emergency data sharing criteria regarding the second ERE from the first ERE and a second set of emergency data sharing criteria regarding the first ERE from the second ERE; (c) receiving emergency data associated with an emergency incident; (d) transmitting the emergency data associated with the emergency incident to the first ERE; (e) determining that a first portion of the emergency data associated with the emergency incident satisfies both the first and second sets of emergency data sharing criteria; and (f) in response to determining that the first portion of the emergency data associated with the emergency incident satisfies both the first and second sets of emergency data sharing criteria, autonomously transmitting the first portion of the emergency data associated with the emergency incident to the second ERE. In some embodiments, both the first and second sets of emergency data sharing criteria comprise two or more of emergency location, geofence, emergency type, emergency data type, time, and link status. In some embodiments, the first and second sets of emergency data sharing criteria comprise emergency type and link status. In some embodiments, the first ERE is a public safety answering point (PSAP) and the second ERE is one of a fire department, a police department, and an emergency medical service. In some embodiments, the emergency data associated with the emergency incident comprises an emergency location In some embodiments, further comprising identifying the first ERE as appropriate to receive the emergency data associated with the emergency incident based on the emergency location. In some embodiments, identifying the first ERE as appropriate to receive the emergency data associated with the emergency incident based on the emergency location comprises determining that the emergency location is within a geofence associated with the first ERE. In some embodiments, further comprising: (a) providing the ERE relationship management portal to a third ERE; (b) receiving, through the ERE relationship management portal, a third set of emergency data sharing criteria regarding the third ERE from the second ERE and a fourth set of emergency data sharing criteria regarding the second ERE from the third ERE; (c) determining that a second portion of the emergency data associated with the emergency incident satisfies both the third and fourth sets of emergency data sharing criteria; and (d) in response to determining that the second portion of the emergency data associated with the emergency incident satisfies both the third and fourth sets of emergency data sharing criteria, autonomously transmitting the second po