WO2018069383A1

WO2018069383A1 - Emergency responder routing system for cardiac emergencies

Info

Publication number: WO2018069383A1
Application number: PCT/EP2017/075911
Authority: WO
Inventors: Dawn Blilie JORGENSON; Dennis E. Ochs; Gregory James LANCASTER
Original assignee: Koninklijke Philips N.V.
Priority date: 2016-10-13
Filing date: 2017-10-11
Publication date: 2018-04-19

Abstract

A method and system for locating a nearest available responder to an emergency event. The method comprises determining a location of an emergency event by a central dispatch server. At least one responder is then identified based on an at least one responder data, which includes location proximity data, traffic congestion data, and time availability data. Then, an emergency request and routing data is sent from the central dispatch server to the at least one identified responder. After receiving the emergency request and routing data, the acceptance signal of the at least one identified responder is transmitted to the central dispatch server. When the at least one identified responder arrives at the determined location of the emergency event, a confirmation alert from the at least one identified responder's portable device is received, and a cancellation alert is sent to one or more other responders.

Description

EMERGENCY RESPONDER ROUTING SYSTEM FOR CARDIAC EMERGENCIES

BACKGROUND OF THE INVENTION

[0001] Numerous cardiac emergencies involving sudden cardiac arrest (SCA) occur outside hospitals causing injuries and killing thousands of people every year. It is well established that if an SCA patient is not given immediate medical attention, the likelihood of survival is low. Specifically, every minute the patient moves without defibrillation, the chance of survival drops by ten percent.

[0002] Emergency Medical Services (EMS) systems have been developed that provide rapid response methods to dispatch EMS personnel from their stations to the SCA victim. However, these methods can still suffer from delays from traffic, confusion regarding patient location, and limited number of on-duty EMS personnel.

[0003] U.S. Pat. App. No. 2007/0218869 discloses an emergency response system for summoning an emergency responder and for routing said responder to a patient. A central station transmits a trigger signal to activate an emergency response device upon receiving a distress call from a patient's location. The emergency response device then sends signals and navigation means to as many potential emergency responders as possible and provides routing to the patient's location, which is fed-back to a responder via a user interface.

BRIEF SUMMARY OF THE INVENTION

[0004] The present invention relates to a method for locating a nearest available responder to an emergency event. The method of the present invention comprises determining a location of an emergency event by a central dispatch server. At least one responder is then identified based on an at least one responder data, which includes location proximity data, traffic congestion data, and time availability data. Then, an emergency request and routing data is sent from the central dispatch server to the at least one identified responder. After receiving the emergency request and routing data, the acceptance signal of the at least one identified responder is transmitted to the central dispatch server. The location of the at least one identified responder on board a vehicle that is en route to the determined location of the emergency event is then tracked by the central dispatch server, wherein an Automated External Defibrillator (AED) is integrated into the vehicle with a navigation system. When the at least one identified responder arrives at the determined location of the emergency event, a confirmation alert from the at least one identified responder' s portable device is received, and a cancellation alert is sent to one or more other responders.

[0005] The present invention also relates to a system for locating a nearest available responder to an emergency event. The system comprises a patient device for transmitting an emergency signal, a central dispatch server comprising a communications module for receiving and transmitting emergency signals and alerts, and a tracker for determining the location of the emergency event, identifying the at least one responder based on location proximity data, traffic congestion data, and time availability data, and locating the at least one responder on board a vehicle with an AED while en route to the determined location of the emergency event. The system further comprises a responder device comprising a communications module for receiving emergency request and transmitting acceptance, confirmation and cancellation alerts.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The accompanying drawings, which are included to provide a further understanding of the invention, are incorporated herein to illustrate embodiments of the invention. Along with the description, they also serve to explain the principle of the invention. In the drawings: [0007] FIG. 1 is a flowchart illustrating a method for locating a nearest available responder to an emergency event according to a preferred embodiment of the present invention.

[0008] FIG. 2 illustrates a system for locating a nearest available responder to an emergency event according to a preferred embodiment of the present invention.

[0009] FIG. 3 shows a screenshot of a responder device graphical user interface (GUI) according to a preferred embodiment of the present invention.

[0010] FIG. 4 shows a screenshot of a responder device GUI in accordance with the present invention that is displayed when responders are en route to the cardiac patient's location.

[0011] FIG. 5 shows a screenshot of a responder device GUI in accordance with the present invention that is displayed when a responder is boarding a vehicle with an AED.

DETAILED DESCRIPTION OF THE VARIOUS EMBODIMENTS OF THE

INVENTION

[0012] The following are definitions of terms as used in the various embodiments of the present invention.

[0013] The term "patient device" as used herein refers to a portable device such as a cellphone, smartphone, tablet, and laptop, among others, that is used by the patient or a bystander to report an emergency event.

[0014] The term "responder device" as used herein refers to a portable device such as a smartphone, tablet, and laptop, among others, that is used by the responder to communicate with the central dispatch server.

[0015] The term "pin icon" as used herein refers to a location marker on the map indicating the position of patients and responders to an emergency. [0016] The term "database" as used herein refers to a collection of data and information or data organized in such a way as to allow the data and information or data to be stored, retrieved, updated, and manipulated and to allow them to be presented into one or more formats such as in table form or to be grouped into text, numbers, images, and audio data. The term "database" as used herein may also refer to a portion of a larger database, which in this case forms a type of database within a database. "Database" as used herein also refers to conventional databases that may reside locally or that may be accessed from a remote location, e.g., remote network servers. The database typically resides in computer memory that includes various types of volatile and nonvolatile computer memory. Memory wherein the database resides may include high-speed random access memory or non- volatile memory such as magnetic disk storage devices, optical storage devices, and flash memory. Memory where the database resides may also comprise one or more software for processing and organizing data received by and stored into the database.

[0017] The present invention relates to a method for locating a nearest available responder to an emergency event. The method of the present invention comprises: determining a location of an emergency event by a central dispatch server; identifying an at least one responder based on an at least one responder data, wherein the at least one responder data comprises location proximity data, traffic congestion data, and time availability data of the at least one responder; sending an emergency request and routing data from the central dispatch server to the at least one identified responder; transmitting the at least one identified responder's acceptance signal to the central dispatch server; tracking by the central dispatch server a location of the at least one identified responder on board a vehicle that is en route to the determined location of the emergency event, wherein an AED is integrated into the vehicle with a navigation system; receiving a confirmation alert from the at least one identified responder's device when the at least one identified responder has arrived at the determined location of the emergency event; and sending a cancellation alert to one or more other responders when the at least one identified responder has sent the confirmation alert.

[0018] The present invention also relates to a system for locating a nearest available responder to an emergency event comprising: a patient device for transmitting an emergency signal; a central dispatch server comprising a communications module for receiving and transmitting emergency signals and alerts, and a tracker for determining the location of the emergency event, identifying the at least one responder based on location proximity data, traffic congestion data, and time availability data, and locating the at least one responder on board a vehicle with an AED while en route to the determined location of the emergency event; and a responder device comprising a communications module for receiving emergency request and transmitting acceptance, confirmation and cancellation alerts.

[0019] FIG. 1 is a flowchart illustrating a method for locating a nearest available responder to an emergency event according to a preferred method of the present invention. A central dispatch server receives a notification regarding an emergency event involving one or more patients, such as an SCA (step 100). The transmission of the emergency event involving one or more patients is identified by a central dispatch server. Here, notification of the emergency event to the central dispatch server is preferably accomplished via a portable device such as a cellphone by a nearby bystander. The bystander may report the emergency by dialing 91 1 and providing information regarding the person or persons involved in the emergency and the nature and location of the emergency event. Alternatively, the emergency alert may originate from a smartphone application or a patient wearable device. When the emergency alert is received, the central dispatch server identifies possible responders (step 102) who are preferably trained in handling the emergency event and collects relevant responder information (step 104) that preferably includes responder' s status (e.g., if responder is on or off-duty), proximity to a resuscitating device (such as an AED), proximity to the emergency event, proximity to a vehicle, responder' s current mode of transportation, possible routes from the responder to the emergency event, and traffic information. The central dispatch server then chooses which responder or responders are available based on the collected responder information (step 106). If the central dispatch server determines that a responder is not the best responder for the current emergency based on all the collected information, the central dispatch server selects another possible responder. If one or more responder information satisfies the emergency criteria, emergency information is then sent to the at least one selected responder via a responder device (step 108), preferably one that is Wi-Fi or GPS-capable such as a smartphone or tablet. The available responder then chooses to accept or decline the emergency request (step 110). If the available selected responder declines the emergency request, the central dispatch server searches for another responder. If the next available responder accepts the emergency request, an acceptance notification is sent to the central dispatch server (step 112) preferably via the responder's device. The confirmed responder is then automatically routed to the emergency event location, and tracked by the central dispatch server (step 114). When the responder arrives at the emergency location, the attending responder sends a notification alert to the central dispatch server that the responder has arrived (step 116). The central dispatch server then sends a cancellation alert to other responders who have not reached the emergency location (step 118) and prompts the other responders not to proceed to the emergency location.

[0020] FIG. 2 illustrates a system for locating a nearest available responder to an emergency event according to one embodiment of the present invention. The patient device 200 comprises a communications module 202, processor 204, and a memory 206. The patient device preferably includes a health sensor 208. Also, the patient device 200 may be a laptop, a tablet, a smartphone, a wearable heart monitoring device or any other devices that comprise at least one or more processors, one or more types of memory, and at least one computer program or operating system. The responder device 210 comprises a communications module 212, processor 214, memory 216, and a GUI 218. The responder device 210 may be a laptop, a tablet or a smartphone. The vehicle with an AED 220 can be directly sent to the responder B22 from a medical facility by the responder device 210 or by the central dispatch server 224. The responder B22 can be any experienced medical personnel trained to use an AED. Also, the vehicle with an AED 220 preferably includes a navigation and communication system that can pair with the responder B22 and the central dispatch server 224.

[0021] As shown in FIG. 2, the central dispatch server 224 comprises a communication module 226, processor 228, patient, responder and vehicle tracker 230, and a memory 232. The memory 232 further comprises responder database 234, vehicle with an AED database 236, and map database 238. The responder database 234 includes data relating to the responders' name, contact details, location, and time availability. The vehicle with an AED database 236 includes data relating to location and contact information of all vehicles with an AED 220. The map database 238 includes maps, as well as data needed to create navigational routes on maps. The map database 238 preferably includes the estimated time of arrival (ETA) of a vehicle with an AED 220 based on real-time traffic information. The patient device 200, responder device 210, vehicle with an AED 220, and central dispatch server 224 are all connected via a network 242.

[0022] FIG. 3 shows a screenshot of a responder device GUI 218 in accordance with the present invention. The GUI 218 shows a patient information window 300 and a map 302 showing a patient's location. The map 302 comprises a patient pin icon 304 indicating the patient's location, the responder pin icon 306 indicating the responder's current location, and routing information indicating the determined quickest route from the responder's current location to the patient's location. The patient's information window 300 includes a request for an AED 308, patient's details 310 specifying the patient's complaint, current location and ETA at the patient's location relative to the responder's current location, and an accept button 312, which the responder presses to transmit the responder's acceptance central dispatch server 224.

[0023] FIG. 4 shows another screenshot of the responder device GUI 218. The responder device GUI 218 shows a map 400 comprising pin icon 402 for Patient A, icon 404 for Patient B, icon 406 for Responder A, and icon 408 for Responder B, which indicates the positions of patients and responders on the map 400. Responder A information window 410 includes the Responder A's image 412, responder work profile 414, which includes name, healthcare work type, and duty status, Responder A's routing details 416, which includes the ETA at the location of Patient A 402, and arrival confirmation alert 418. Responder B information window 420 comprises an arrival confirmation alert 422 (which indicates that responder A has arrived at the Patient A's location), Responder B's image 424, responder work profile 426 comprising name, healthcare work type, and duty status, and Responder B's routing details 428, which includes the ETAs at both patients' locations, Responder B's cancel button 430 for declining Patient A's emergency request, and Responder B's button 432 for accepting Patient B's emergency request.

[0024] FIG. 5 shows yet another screenshot of a responder device GUI 218 when a responder 222 is not on board a vehicle with an AED 220. In this example, Responder 222 is still getting ready to report for work when Responder 222 receives an emergency notification from the central dispatch server after the central dispatch server has determined that Responder 222 is the one nearest the patient's location. As shown in FIG. 5, the responder device GUI 218 shows a map 500 to a patient's location and a patient's information window 502. The map 500 comprises a patient pin icon 504, responder pin icon 506, pin icon 508 for the vehicle with an AED, and routing information indicating the determined quickest route from the current location of the vehicle with an AED to Responder 222 's current location and also to the patient's location. The patient's information window 502 includes a request for an AED, patient details 512 indicating the patient's complaint, current location and ETA at the patient's location relative to Responder 222 's current location, an accept button 514, which the responder presses to relay Responder 222 's acceptance of the emergency request, and an on board button 516, which the responder presses to notify the central dispatch server 224 that the vehicle with an AED 220 has arrived at Responder 222 's current location and that the responder has boarded on to the vehicle. Once the responder aboard the vehicle arrives at the patient's location, another notification is sent by Responder 222 's device to the central dispatch server 224 to inform the server that the vehicle has arrived at the emergency location.

[0025] In one embodiment of the present invention, a runner participating in a marathon suffers from sudden cardiac arrest. An event official sends a cardiac emergency request and the event location to a central dispatch server using a smartphone. The central dispatch server then identifies two available responders who are in close proximity to the patient's location. The central dispatch server sends to the two identified responders the emergency request and the routing data to the patient's location. The two identified responders send acceptance signals to the central dispatch server when they receive the emergency request and routing data. The central dispatch server tracks the two responders on board each vehicle with an AED. One responder arrives ahead of the other, sends an arrival notification to the central dispatch server and attends to the patient. The central dispatch server then sends a cancellation alert to the other responder informing the other responder that another responder is already attending to the patient.

[0026] In another embodiment of the present invention, a cardiac patient wearing a heart monitoring device experiences a sudden cardiac arrest. The wearable heart monitoring device, which is connected to the central dispatch server via a cloud network, sends an emergency alert to the central dispatch server. The central dispatch server tracks the location of the wearable device, and identifies the nearest available responder based on proximity and traffic data. The central dispatch server then sends an emergency request and the patient's location to the responder. The selected responder receives the emergency request and routing data and then sends an acceptance signal. The responder's acceptance signal is then transmitted to the central dispatch server. The central dispatch server tracks the responder on board the vehicle with an AED. When the responder arrives at the emergency location, the responder transmits an arrival notification to the central dispatch server and attends to the patient. The central dispatch server then sends a cancellation alert to the other nearby responders to inform them that the patient is now being attended to.

[0027] In yet another embodiment of the present invention, a person walking in a park suffers from a sudden cardiac arrest. A bystander sends a cardiac emergency request to the central dispatch server using a smartphone, including the person's location data. The central dispatch server then identifies two available responders who are in close proximity to the patient's location. The central dispatch server sends the patient's emergency request and the routing data to the patient's location to the two identified responders. The two identified responders receive the emergency request and routing data, and send acceptance signals. The responders' acceptance signals are then transmitted to the central dispatch server. The central dispatch server tracks the two responders on board each vehicle with an AED. The first responder who is in closer proximity to the patient's location is expected to arrive within a few minutes. The second responder, while en route to the patient's location, receives a second emergency request from the central dispatch server. The second patient happens to be located in closer proximity to the second responder than the first patient. The second responder thus sends a cancellation alert to the central dispatch server regarding the second responder's earlier acceptance for the first emergency. Then, the second responder sends a corresponding acceptance signal to attend to the second patient who is in closer proximity to the second responder. The two responders arrive at the location of the two respective patients, send corresponding arrival notifications, and attend to the respective patients.

[0028] In a further embodiment of the present invention, an identified responder is unable to reach the patient's location due to an unexpected traffic congestion. The identified responder sends a cancellation alert, which is transmitted to the central dispatch server. The central dispatch server sends a cancellation notification of the identified responder to the other responders and the central dispatch server again sends out emergency requests to other nearby responders. The same or similar process occurs when the disruption to the responder's route arises from other events such as road accidents involving the emergency vehicle, road blockade, and sudden severe weather disruptions.

[0029] In one embodiment of the present invention, a patient suffers from sudden cardiac arrest. A bystander sends a cardiac emergency request to a central dispatch server using a smartphone, including the patient's location data. The central dispatch server then identifies two available responders who are in close proximity to the patient's location. The central dispatch server sends the patient's emergency request and the routing data to the patient's location to the two identified responders. The two identified responders receive the emergency request and routing data, and send acceptance signals. The responders' acceptance signals are then transmitted to the central dispatch server. The central dispatch server tracks the two responders on board a vehicle with an AED. One responder arrives ahead of the other, sends a confirmation alert to the central dispatch server and attends to the patient. The attending responder uses the AED, but the AED is malfunctioning. The attending responder thus sends another emergency alert to the central dispatch system. In response, the central dispatch server then does not deactivate the other responder. The other responder, not having received a cancellation alert, continues towards the emergency location. Once the responder arrives at the patient's location the responder attends to the patient with a fully- functioning AED.

[0030] In another embodiment of the present invention, a patient suffers from sudden cardiac arrest at the patient's house. One of the patient's family members sends a cardiac emergency request to a central dispatch server using a smartphone, including the patient's location and insurance company information. The central dispatch server then identifies one available responder who is in close proximity to the patient's location. The central dispatch server also sends a request for the patient's hospitalization history to the insurance company. The insurance company sends the requested patient medical history to the central dispatch server, including the name of the hospital where the patient was last admitted. The central dispatch server then sends a request for the patient information to the hospital where the patient was last admitted. The hospital sends the patient's information including the patient's name, gender, age and medical history to the central dispatch server. The central dispatch server sends the emergency request, patient information, patient's location, and routing data to the identified responder. After the identified responder receives the emergency request, patient information, and routing data, and sends an acceptance signal to the central dispatch server. The responder' s acceptance signal is then transmitted to the central dispatch server. The central dispatch server tracks the responder on board a vehicle with an AED. When the responder arrives, the responder sends a confirmation alert to the central dispatch server and attends to the patient.

[0031] The present invention is not intended to be restricted to the several exemplary embodiments of the invention described above. Other variations that may be envisioned by those skilled in the art are intended to fall within the disclosure.

Claims

CLAIMS What is claimed is:

1. A method for locating a nearest available responder to an emergency event comprising the steps of:

determining (100) a location of an emergency event by a central dispatch server;

identifying (102) an at least one responder based on an at least one responder data, wherein the at least one responder data comprises location proximity data, traffic congestion data, and time availability data of the at least one responder;

sending (108) an emergency request and routing data from the central dispatch server to the at least one identified responder;

transmitting (112) the at least one identified responder's acceptance signal to the central dispatch server;

tracking (114) by the central dispatch server a location of the at least one identified responder on board a vehicle that is en route to the determined location of the emergency event, wherein an Automated External Defibrillator (AED) is integrated into the vehicle with a navigation system; and

receiving (116) a confirmation alert from the at least one identified responder's portable device when the at least one identified responder has arrived at the determined location of the emergency event

2. The method of Claim 1, further comprising the step of sending a cancellation alert (118) to one or more other responders when the at least one identified responder has sent the confirmation alert.

3. The method of Claim 1, further comprising a step of reporting the emergency event, wherein the determining step is based upon the reporting step.

4. The method of Claim 3, wherein the step of reporting originates from one of a smartphone application and a patient wearable device.

5. The method of Claim 1, further comprising a step of automatically choosing the at least one responder with the central dispatch server based upon whether information satisfies emergency criteria.

6. The method of Claim 5, wherein the emergency criteria is selected from one or more of criteria including a responder' s status of on-duty or off-duty, a proximity to an AED, a proximity to the emergency event, a proximity to a vehicle, a responder's current mode of transportation, possible routes from the responder to the emergency event, and traffic information.

7. A system for locating a nearest available responder to an emergency event comprising:

a patient device (200) for transmitting an emergency signal;

a central dispatch server (224) comprising

a communications module (226) for receiving and transmitting emergency signals and alerts,

a tracker for determining the location of the emergency event, identifying the at least one responder based on location proximity data, traffic congestion data, and time availability data, and locating the at least one responder on board a vehicle with an AED while en route to the determined location of the emergency event, and a responder device (210) comprising a communications module for receiving emergency request and transmitting acceptance, confirmation and cancellation alerts.

8. The system of Claim 7, wherein the responder device includes a display having a graphical user interface (GUI) displaying a map showing a patient location.

9. The system of Claim 8, wherein the GUI further includes a patient information window.

10. The system of Claim 7, wherein the responder device GUI includes an accept button and a cancel button.

11. The system of Claim 7, wherein the patient device comprises a health sensor.

12. The system of Claim 11, wherein the health sensor comprises a wearable heart monitoring device.

13. The system of Claim 7, wherein the AED is configured to be in direct communication with the central dispatch server.

14. The system of Claim 7, wherein the vehicle with an AED includes a navigation and communication system configured to be in communication with the responder device and the central dispatch server.