U.S. patent application number 15/085492 was filed with the patent office on 2016-07-21 for method and apparatus for emergency response notification.
The applicant listed for this patent is Emergency University, Inc.. Invention is credited to Odelia BRAUN.
Application Number | 20160210581 15/085492 |
Document ID | / |
Family ID | 52006314 |
Filed Date | 2016-07-21 |
United States Patent
Application |
20160210581 |
Kind Code |
A1 |
BRAUN; Odelia |
July 21, 2016 |
METHOD AND APPARATUS FOR EMERGENCY RESPONSE NOTIFICATION
Abstract
Embodiments of the invention leverage mobile proliferation to
enable laypersons to initiate a timely and effective emergency
response in case of an emergency, such as a medical emergency, e.g.
cardiac event. Mobile apps are made available as part of an
organization's overall response plan and program, allowing
bystanders of emergency events to easily initiate notification of
trained responders, for example in their facility, in a timely
manner commensurate with the type of emergency specific to their
facility. More particularly, embodiments of the invention use
mobile applications to alert certified first trainees to respond to
the scene of the emergency.
Inventors: |
BRAUN; Odelia; (Redwood
City, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Emergency University, Inc. |
Emerald Hills |
CA |
US |
|
|
Family ID: |
52006314 |
Appl. No.: |
15/085492 |
Filed: |
March 30, 2016 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
14269030 |
May 2, 2014 |
9324120 |
|
|
15085492 |
|
|
|
|
61832691 |
Jun 7, 2013 |
|
|
|
61892836 |
Oct 18, 2013 |
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
H04W 4/60 20180201; G06Q
50/265 20130101; H04W 4/021 20130101; H04W 4/90 20180201; G16H
40/20 20180101; G06Q 10/063112 20130101; G06Q 10/00 20130101; G06Q
10/10 20130101; H04L 65/608 20130101; G16H 40/67 20180101; H04W
4/023 20130101; G06Q 50/22 20130101; H04M 2250/10 20130101 |
International
Class: |
G06Q 10/06 20060101
G06Q010/06; H04W 4/02 20060101 H04W004/02; G06Q 50/26 20060101
G06Q050/26 |
Claims
1. A computer implemented method for routing communications signals
in response to an emergency, comprising: providing a processor for
receiving an input signal comprising an initial notification
transmitted by a bystander within a facility and indicating that
there is an emergency within said facility; independently of a
central emergency medical services (EMS) notification system, said
processor extracting content from said signal comprising
identification of a specific location of said emergency and
identification of said emergency type; said processor using said
extracted content to identify laypersons within said facility who
are trained responders for said emergency and who are most
qualified to respond to said emergency based upon the type of said
emergency; said processor prioritizing said identified most
qualified trained responders based upon their training and
qualification; and independently of said central notification
system, said processor transmitting a prioritized alert signal
directly to said identified most qualified trained responders
comprising said emergency type and said emergency location.
2. The method of claim 1, further comprising: said processor
identifying location and operational status of emergency equipment
based on parameters that include any of most recent successful
maintenance inspection, expiration dates that are relevant to
critical equipment, components, supplies, and medication that
require routine replacement due to their age and/or expiration
date; and said processor providing notifications to trained
responders who have indicated that they are responding, said
notifications identifying nearest appropriate emergency
equipment.
3. The method of claim 1, further comprising: when GPS is
available, said processor using emergency event GPS location and
dynamically comparing said emergency event GPS location with a
closest facility as determined by GPS to identify appropriate
trained responders; and when GPS is not available said processor
using pre-configured location data.
4. The method of claim 1, further comprising: said processor
identifying location and operational status of emergency equipment
based on parameters that include most recent confirmation of GPS
location.
5. The method of claim 1, further comprising: said processor
receiving a confirming response from trained responders who respond
to said alert; and said processor providing a notification to said
bystander indicating receipt of said notification from said trained
responders who respond to said alert.
6. The method of claim 1, further comprising: said processor using
multiple real-time notification channels to immediately communicate
between said bystander and said responder
7. The method of claim 1, further comprising: responsive to any of
said initial notification and said content, said processor
providing said bystander with any of specific text-based, graphic,
video, and voice instructions on actions to perform in response to
said emergency.
8. The method of claim 1, further comprising: said processor
providing communication and activity tracking of all communications
and times at which actions are taken.
9. The method of claim 1, further comprising: said processor
providing direct notification to 911 of said emergency.
10. The method of claim 1, further comprising: said processor
receiving GPS location information for emergency equipment and
confirmation that said emergency equipment is operational.
11. The method of claim 1, further comprising: said emergency
comprising a sudden cardiac arrest (SCA); and any of said processor
using geo-location to identify said trained responders based on
their location when providing said confirming response; said
processor providing identification of AEDs based upon proximity and
operational readiness; said processor providing notifications to
said trained responders identifying a nearest AEDs prioritized by
proximity; and said processor providing communication and activity
tracking of any of time a responder arrived, if and when an AED is
attached, and when an EMS arrived.
12. The method of claim 1, further comprising: said processor
communicating instructions to individuals based on any of a type of
emergency, organizational structure, pre-defined roles, equipment
availability, training and experience, and an organization's
emergency policies, procedures, protocols, and emergency response
plans.
13. The method of claim 1, further comprising: said processor
exchanging information with individual workforce members comprising
any of notification to evacuate, where to evacuate to, confirmation
of receipt of notification by workforce, evacuation from building
confirmation, arrival at assembly point confirmation, and
notification of individual workforce members who have issued a
distress notification.
14. The method of claim 13, further comprising: said processor
providing an incident commander with aggregate, continually updated
reports of individuals who have successfully evacuated by points of
evacuation; receipt of notification, including GPS location;
evacuation from building, with new GPS location; and arrival at an
assembly point by GPS location.
15. The method of claim 13, further comprising: said processor
providing an incident commander with distress notifications from
individual workforce members; and said processor triaging said
distress notifications to security and emergency response team
members.
16. The method of claim 13, further comprising: said processor
providing an incident commander with aggregate, continually updated
reports of distress notification by degree of triage assigned.
17. The method of claim 13, further comprising: said processor
identifying evacuation exits with a transmitted signal to direct
workforce members to a nearest evacuation exit, said signal
comprising any of Wi-Fi-based IP addresses, Bluetooth, radio,
satellite, pre-placed transmission equipment proximate to said
exits, Wi-Fi-based signals transmitted from exit doors at said
exits. Wi-Fi signals from a nearest router.
18. The method of claim 13, further comprising: said processor
locating non-evacuating personnel with a transmitted signal, said
signal comprising any of Wi-Fi-based IP addresses, Bluetooth,
radio, satellite, pre-placed transmission equipment proximate to
said exits, Wi-Fi-based signals transmitted from exit doors at said
exits, Wi-Fi signals from a nearest router, said signal further
comprising instructions in any of text and graphic format to said
non-evacuating personnel directing them to a nearest exit.
19. The method of claim 1, further comprising: said processor
providing any of coded or time-limited coded drills for designated
responders, or classes and non-coded, facility wide drills to
simulate actual emergencies
20. The method of claim 1, further comprising: said processor
incorporating time-based prompts to ensure necessary individuals
are notified, and necessary actions are timely performed.
21. The method of claim 1, further comprising: said processor
ascertaining whether a workforce member whose cell phone is turned
on is still in a facility if said workforce member has not
confirmed receipt of a notification.
22. The method of claim 1, further comprising: said processor
informing said bystander how many responders have been
notified.
23. The method of claim 13, further comprising: said processor
identifying an individual having known disabilities, as specified
during said individual's registration; and said processor issuing a
pre-configured distress signal during an evacuation with specific
instructions for said trained responder, and location of nearest
appropriate equipment based upon the disability, to assist said
individual with equipment necessary to ensure they are able to
evacuate said individual.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of U.S. patent
application Ser. No. 14/269,030, filed May 2, 2014, which claims
priority to U.S. provisional patent application Ser. No.
61/832,691, filed Jun. 7, 2013, and to U.S. provisional patent
application Ser. No. 61/892,836, filed Oct. 18, 2013, each of which
application is incorporated herein in its entirety by this
reference thereto.
TECHNICAL FIELD
[0002] The invention relates to responding to emergencies. More
particularly, the invention relates to providing alerts to
proximate, trained personnel in the event of an emergency, such as
a medical emergency.
BACKGROUND
[0003] Emergency response is a serious problem. Under such systems
as 911, when seconds count, a responder is at least several minutes
away. Consider, for example, cardiac arrest. Each Year 330,000
Americans experience sudden cardiac death, yet less than 5% of
Americans receive CPR training annually. The majority of these
trainees are health care professionals who work in controlled
medical environments such as hospitals, ambulances, and clinics.
However, the majority of cardiac arrests take place at work or in
the home. While EMS systems have evolved to bring trained medical
professionals to the scene of a medical emergency more rapidly, the
optimal window for medical intervention in a cardiac arrest is
often too narrow to allow for the timely transport of equipment and
skills to the location of the victim.
[0004] The probability of surviving an out-of-hospital cardiac
arrest is at least doubled for victims who receive bystander CPR.
In addition, cardiac arrest victims who receive bystander CPR and
the benefit of an automated external defibrillator (AED) that can
deliver a shock to the heart within four minutes quadruple their
survival with reports of survival between 34-70%.
[0005] However, victims receive the benefit of bystander CPR only
7-28% of the time, and receive the combined benefit of bystander
CPR and AED application only 2-3.4% of the time. While researchers
and clinicians understand what elements are necessary to improve
survival from cardiac arrest, it is as yet not possible to deliver
these components to the cardiac arrest victim in a timely
fashion.
[0006] A major problem in this regard lies in the fact that there
is statistically a very small likelihood that a trained responder
is present when a cardiac arrest occurs. The bystander, unfamiliar
with the emergency medical response, most often does nothing, or
merely calls emergency medical services (EMS), i.e. 911.
[0007] A sudden cardiac arrest (SCA) is an emotionally daunting
event. As such, most laypersons are unwilling to perform unfamiliar
tasks, such as AED and CPR, in public under these emotionally
charged circumstances. The best EMS response times nationwide are
greater than four minutes, and the average response time is between
8-12 minutes. Thus, trained personnel, and the appropriate
equipment (AEDs), arrive at the victim's side too late to impact
survival. This is best understood when one considers that EMS
requires a minimum of an additional 2-4 minutes to process the a
call. EMS obtains information regarding responders and equipment
voluntarily and is therefore an incomplete network of both trained
responders and equipment. EMS has no way to ascertain the continued
validity of the information initially provided, which
experientially has been demonstrated to change by 20%/year.
Further, EMS has no way to ascertain the operational status of the
equipment because it does not maintain this information itself.
[0008] Additionally, EMS has no way to customize the information
based on organizational structure, nor does it have the operational
plans and protocols of different organizations in the
community.
[0009] To address this issue, many workplaces have instituted
internal emergency response plans and trained workplace personnel
in CPR and AED. They have purchased AEDs to be placed at convenient
locations throughout the workplace. However, the average number of
trained personnel in the workforce averages 2-10% Therefore,
victims still do not collapse near their trained responders.
[0010] The foregoing discussion considers a single type of medical
emergency. Yet, there are many types of medical and non-medical
emergencies that require prompt and skilled response. It would be
advantageous to provide an approach that enables prompt
notification to elicit early response to such emergencies.
SUMMARY
[0011] Embodiments of the invention leverage mobile proliferation
to enable laypersons to initiate a timely and effective emergency
response in case of an emergency, such as a medical emergency, e.g.
cardiac event. Mobile applications (APPs) are made available as
part of an organization's overall response plan and program,
allowing bystanders of emergency events to easily initiate
notification of trained responders, specific to their facility.
More particularly, embodiments of the invention use mobile
applications to alert certified first responders to respond to the
scene of the emergency. Such mobile applications also inform
certified first responders of the nearest operational emergency
equipment and can provide specific instructions to the certified
first responders regarding the emergency and how best to
respond.
BRIEF DESCRIPTION OF THE DRAWINGS
[0012] FIG. 1 is an organization diagram showing the participants
in a tiered response system according to the invention;
[0013] FIG. 2 is a flow diagram a medical emergency response model
according to the invention;
[0014] FIG. 3 is a block schematic diagram showing the main
components of an emergency response notification system according
to the invention;
[0015] FIG. 4 is a flow diagram that shows a sequence of
activities/communications in a medical emergency (ME) according to
the invention;
[0016] FIG. 5 is a flow diagram showing the sequence of operations
during an emergency event according to the invention;
[0017] FIG. 6 is a flow diagram showing the sequence of operations
during an SCA emergency event according to the invention;
[0018] FIG. 7 is a flow diagram showing a non-medical emergency
response model according to the invention;
[0019] FIGS. 8A-8C are a flow diagrams showing the sequence of
operations during a non-medical emergency event according to the
invention;
[0020] FIGS. 9A-9D are a series of screenshots showing a workforce
evacuation notification sequence according to the invention;
[0021] FIG. 10 is a flow diagram showing an example of how the
role-based details are lifted out of the emergency response
protocol and transmitted to the appropriate role based individual
in an emergency, where an electronic site survey generates
organization specific emergency response protocols that detail
role-based tasks according to the invention;
[0022] FIG. 11 is a flow diagram showing the cancellation of an
alert according to the invention;
[0023] FIGS. 12-17 are screen shots showing various user screens
provided by the APP during an emergency; and
[0024] FIG. 18 is a block schematic diagram showing a machine in
the example form of a computer system within which a set of
instructions for causing the machine to perform one or more of the
methodologies discussed herein may be executed.
DETAILED DESCRIPTION
[0025] Embodiments of the invention facilitate the arrival of
trained personnel with the appropriate equipment to aid in an
emergency, for example to assist a cardiac arrest victim or other
emergency. With the invention, individuals having no training can
now alert trained co-workers in their workplace to respond
immediately in an emergency, e.g. to the victim of cardiac arrest,
via a mobile application that notifies all trained responders in
the facility via text and email. This allows the untrained
bystander to contribute in a meaningful way in an emergency while
not requiring the bystander to perform an unfamiliar task in public
under pressure. Importantly, while 911 can be included as part of
the initial notification, the use of the 911 service is not
required to obtain or send the initial notifications, thus saving
important minutes.
[0026] Embodiments of the invention include a database that tracks
the training and certification of all workplace personnel, as well
as the date of their certification, and whether they have received
special responder classes or other applicable training classes or
certifications. Trained personnel are notified by the bystander in
order, prioritized, for example, by the quality of their training
and preparation, as defined by the most recent certification dates,
and whether they have received a special responder class or other
applicable training classes or certifications.
[0027] In the case of a cardiac arrest response, the trainees are
tracked by the completion of CPR, AED, and AED Responder online
training modules, and their dates of completion. They are also
tracked by the date they demonstrate skills competence in these
classes, as verified by an instructor. Certification is awarded
when both the online training modules and skills competence have
been successfully completed. Re-certification is required every two
years and each re-certification date is maintained in the system.
Trainees are also tracked by the completion of the AED responder
class, and they are awarded certification upon completion of this
class.
[0028] The rules engine first looks to the closest facility, then
prioritizes by the trainees who have current certification in AED
Responder and CPR/AED. Next, it looks to trainees who have current
certification in CPR/AED, but not AED Responder. Next, it looks to
trainees who have previously been certified, but are not currently
certified in CPR/AED. Then, it looks to trainees who have
previously completed either CPR/AED skills or the online training
programs. Those skilled in the art will appreciate that the order
of prioritization may be changed and that some steps may be left
out, while other steps may be added, all as appropriate and
desired. Further, while this embodiment of the invention concerns
medical emergencies and, in particular an SCA, those skilled in the
art will appreciate that such rules and prioritization can be
applied as appropriate to any emergency event in which the
invention is used.
[0029] FIG. 1 is an organization diagram showing the participants
in a tiered response system according to the invention. In
embodiments of the invention, a four tier emergency response system
is established for organizations. Each tier of the emergency
response system has its own roles and responsibilities. Training
specific to the each tier's responsibilities is provided, as are
the equipment and tools necessary for each tier to fulfill their
respective roles.
[0030] Organization-wide emergency policies and procedures are
developed with the leaders of the organization 11, the first tier.
The second tier of the system, each facility's program coordinator
12, develops a facility specific emergency response plan. The
trained responders 13 form the third tier of the emergency response
system, and the fourth tier is the general workforce 14 who is not
trained and is targeted by a mobile application. An
emergency/disaster physician 10 typically oversees the emergency
response system in the case of medical emergencies.
[0031] Those skilled in the art will appreciate that the invention
is not limited to medical emergencies and applies as well to other
emergencies, such as might occur in the case of a fire, flood,
storm, earthquake, terror attack, etc. A key feature of the
invention is the bystander initiated notification of an emergency
for which a response by trained personnel is required and the
automatic identification and notification of such responders on the
basis of event-related rules, as well as prioritization of such
notifications. This creates and ad hoc network for emergency
response that is independent of public services, such as the 911
service. As such, there is no need to operate through an
intermediary, such as a central dispatcher. In this way, precious
time is saved. This is especially important in a cardiac arrest
because the likelihood of survival decreases by 10% with each
passing minute from the moment of collapse. It is estimated that on
average, use of an internal notification system decreases the time
to defibrillation from 10-12 minutes to 1-3 minutes. If the
emergency is a wide ranging event, where a central response system
would be overburdened and, as such, subject to limited resources
and degraded response times. Embodiments of the invention avoid
such bottleneck. Nonetheless, embodiments of the invention are able
to create an impromptu, tiered command structure through the
application of rules and prioritization with regard to the
communication of notifications. These rules define roles and assess
abilities, locate equipment, and the like without the need for a
central dispatch facility.
[0032] For example, with regard to non-medical emergencies, each
company should have an emergency response plan. Such plans include
the concept of who does what, in what instances, and when.
[0033] For example, at Tier one, incident command, one to three
people are designated as the incident command, where two of the
people are backups. The organization's Emergency Response Plan
includes a list of initial tasks that should be immediately
completed in case of specific emergencies, for example in a fire.
The incident commander's initial responsibilities include for
example, turning off elevators, escalators, shutting down secure
areas, calling the Fire Marshall, calling the security team,
etc.
[0034] Practically speaking, in a private sector emergency,
incident commanders typically, have very little experience with
managing emergencies and do not know what their initial tasks are.
They somehow need to find their long neglected, dusty emergency
response plan notebook, written by someone else, at some previous
time, in a drawer somewhere.
[0035] In contrast thereto, with the herein disclosed alert APP, a
bystander can click on, e.g. fire and the incident commander
receives a text that lists all the initial tasks that he is charged
with, and a link to his protocol or plan.
[0036] Tier 2 and, sometimes Tier 3, includes the emergency
response team or floor wardens, which consists of a predetermined
number of people per floor; and/or security, which is variable by
company, i.e. different names are often used in the middle tier for
similar function. At this level in the hierarchy, participants
receive texts and/or emails that tell them exactly what equipment
they should retrieve, where it is located, and directions to where
they should station themselves to assist in the evacuation. Such
notifications list the proper steps in evacuating personnel, e.g.
links to additional immediately necessary information. Their
responsibilities, tasks, and the equipment they need to retrieve
information are described in their organization's emergency
response policies and procedures, again in a notebook an unknown
dusty drawer, and which no one reads, but for which they are
responsible. In embodiments of the invention, the APP extracts the
relevant task related information from the emergency response plan,
which is pre-loaded into the database, and which is accessible by
defined fields, and transmits this critical information to specific
individuals who need it at the time they need it.
[0037] In appropriate emergencies, the general workforce receives
instructions to evacuate, and directions to the nearest evacuation
exist, as well as the location and directions to the assembly point
located at a safe distance from their building or facility.
[0038] The individuals are pre-configured in the database as to
their role, i.e. incident commander, emergency response team,
security, general workforce, etc. The individuals receive
instructions from their pre-existing emergency response plans
(ERPs), and policies, procedures, and protocols according to their
role. These instructions are taken directly from the company's
emergency response policies, procedures, protocols and plans, all
of which are documents that are stored in the database by templates
and fields of unique texts, and which can be lifted into the
notification text. This information comes directly from the
database, is collected initially by management applications, and is
selected for the particular user using the rules engine.
[0039] An important aspect of the invention concerns that fact that
each participant in the emergency response system is enabled to
communicate with each other person, and such communications are
organized in tiers to implement a command structure spontaneously
and in real time. Thus, roles are filled from a pool of candidates
based upon their availability and also, for example, their
proximity, skills, certification, etc. Information within the
network of participants is routed, based upon the rules and
prioritization, to the right person when it is needed. Thus, in
addition to defining a tiered organizational structure in real
time, the system provides instructions as well. In this way, each
individual's role is reinforced and each individual's skills are
augmented. For example, the location of each participant in the
emergency response system is known from the individual's profile
information and/or from real time tracking information; each
individual's skills and availability is known; and all emergency
equipment in inventory is known as to its location, capabilities,
and operational state.
[0040] In embodiments of the invention, a database and rules engine
provide an information storage and routing facility, although in
other embodiments of the invention such structure and knowledge
need not be stored in a central server or cleared through a central
dispatch facility. Rather, the initiation of an alert by a
bystander propagates a series of notifications through a network of
participants, for example, by use of an APP on their personal
wireless device, where all rules and information is distributed,
with pertinent rules for each individual on their device, as well
as all profile information that is necessary to involve the
individual appropriately in the tiered emergency response
structure. In all embodiments of the invention, the mobile device
can comprise, for example, a smartphone, such as an iPhone, tablet,
watch, automotive device, aviation or nautical device, wearable
device, such as Google Glass, or any other device that is capable
of receiving transmissions.
[0041] Thus, in embodiments of the invention, the APP is used
independently of a server, such as the rules engine and database.
In such cases, the APP is subject to periodic synching with the
database to ensure that the cached information stored in the APP
remains current. Further, the database and rule engine can be
periodically distributed to or cached on one or more of the
handheld devices as a backup if the central system is not reachable
during an emergency. Notifications are then sent directly, to the
extent possible, from the bystander's phone.
[0042] In some embodiments of the invention, a more comprehensive
user profile is collected at time of registration, and the user can
inform the system of any skills, professional license, training, or
equipment that they have and are willing to share, i.e. there may
be people who were not trained by a specific organization; who are
not known to be trained but are, in fact, trained; and/or have
capabilities that would enable them to assist in an emergency.
[0043] In other embodiments of the invention, the APP is downloaded
by workforce members, or even ordinary people who may or may not be
part of an organization and who, as part of their user profile,
potentially wish to share their medical information, i.e. potential
patients and/or victims, so that they can personally initiate an
alert, and indicate consent by a separate button "Share my medical
information" with the trained responders to facilitate care. For
example, a workforce member may be diabetic, and initiate the
internal response system by selecting "share my information," in
which case the responders would be notified that he is diabetic and
they could bring orange juice or sugar for a more rapid recovery.
Other examples of the aspect of the invention include individuals
who are allergic to certain foods, e.g. peanuts, or medications and
who, upon feeling symptoms of an allergic reaction, could initiate
a call for assistance that can also indicate, for example, the fact
that the individual carries an EpiPen, which the responder could
then find in the individual's purse, etc. Once found, this would
allow the individual to be injected. Another example concerns
someone who has a pacemaker or an internal defibrillator that they
can tell is malfunctioning. In such case, they can send out a
notification and receive immediate assistance. In the foregoing
embodiments, rules are applied to identify an individual having
known disabilities, as specified during the individual's
registration, and a pre-configured distress signal is issued
during, for example, an evacuation, with specific instructions for
the trained responder, and directions to the nearest appropriate
equipment based upon the disability, to assist the individual with
equipment necessary to ensure that they are able to evacuate the
individual.
[0044] In an embodiment of the invention, the general workforce is
provided an overview of the organization's emergency response
program. The overview provides the workforce with the knowledge
that the organization has emergency response resources in its
facilities, that there are trained responders, that there is an
internal emergency response system, and that they play an important
role in the system, i.e. to activate the system to bring trained
responders to the scene of the emergency.
[0045] The emergency response program can pertain to a building, a
campus, a town, or any other facility or organization. The program
can include, for example, predetermined assembly areas at which
individuals are to gather in the event of an emergency. Embodiments
of the invention allow individuals to be tracked and located, or to
send out distress messages. In this way, those individuals who did
not successfully escape can be assisted.
[0046] For example, upon notification of the need to evacuate and
instructions and/or directions on where their closest evacuation
point and assembly area is located, a member of the general
workforce, is provided with three successive buttons that appear on
their APP:
[0047] First, a button is provided that instructs the member:
"Press to confirm that you have received the evacuation
notification;"
[0048] Next, a button is provided that instructs the member: "Press
to confirm that you have evacuated out of the building;" and
[0049] Next, a button is provided that instructs the member: "Press
to confirm that you have reached the assembly area."
[0050] A button stays on the screen that instructs the member:
"Press to indicate that you are having difficulties evacuating,"
and a text field is provided to allow the participant to tell
Incident Command (IC) what problems they are having and where they
are located.
[0051] A report is constantly updated based on individuals
confirming their evacuation, or lack thereof. The report is
available to the IC and distributable by regions to the responsible
ERT or security teams. Ideally, in companies that have security
upon entering the building, the initial list of individuals inside
in the structure is updated with those that have successfully
evacuated, and special alerts are sent to ICs and ERT/security for
individuals who are having difficulty evacuating and need
assistance.
[0052] The mobile application ("APP") 16 empowers lay bystanders to
play a critical yet simple role in the organization's emergency
response system and provides them the tool with which to
participate. The mobile application allows the bystander to
initiate the facility's emergency response plan more rapidly by
yelling out for help in the manner described in the emergency
response plan, such as yelling out for help or using the nearest
squawk box. Next, the APP instructs the lay bystander to notify
trained workplace personnel via the mobile APP. Next, the APP
instructs the lay bystander to initiate a call to 911, or the APP
directly calls 911 by presenting the user with a button that says
"Press to call 911." Once the button is pressed, the APP opens the
phone function and places the call. The mobile APP continues to
follow the originally prescribed emergency response plan, but
facilitates the more rapid arrival of trained responders. The
mobile APP also provides a mechanism with which to simulate, for
example, an SCA, with its drill function.
[0053] Medical Emergencies--Emergency Response Notification
System
[0054] FIG. 2 is a flow diagram a medical emergency response model
according to the invention, in which the relationship between the
general workforce, emergency response team and emergency medical
services is shown. The flow in this model is discussed in detail
below.
[0055] FIG. 3 is a block schematic diagram showing the main
components of an emergency response notification system according
to the invention. These components include a database 20 that
stores data acquired through management applications; a rules
engine 22, including a learning management system ("LMS") that
acquires and hierarchically stores raw data and that analyzes the
data based on rules; a multi-mode, multi-dimensional
communications, and two-way messaging and communication system 24,
including emails, an SMS gateway 25, telephone and intelligent
communications to provide progressive levels of intelligence,
analyzed information, and compiled information that is dynamically
driven by the rules engine, and including a mechanism for sending
and receiving both human-to-human and technology generated
intelligence, e.g. two-way communications and content between
system participants, such as an alert initiator 27 and an alert
responder 23; Web services 26 which communicate via the Internet
21, including business logic that performs functions directly on
the database, initiates communications, provides analysis, and
compiles reports; a mobile application 16 that provides an access
point to the system and/or user interface; and geo-location
capabilities 29.
[0056] Data stored in the database includes, for example: [0057] 1.
Name of all individuals who have downloaded the APP, including
their organization, their specific facility (location), their email
address; and a cell phone number; [0058] 2. Name of all trained
responders, including their organization, their specific facility
(location), their email address; a cell phone number, and the date
of their most recent certifications, e.g. CPR/AED certification,
AED responder certification, first aid certification, and the date
of their most recent training, if they are not certified. Such
information can also include the responder's role within a tiered
emergency response organization and the specific emergency type for
which they are to receive notification. [0059] 3. Location of
emergency equipment, such as AEDs by organization, facility,
address, location in facility, e.g. floor, and specific description
of location, such as 9.sup.th floor elevator South, and GPS
coordinates; date of last successful maintenance; and date of
expiration for critical equipment, components, supplies, and
medication that require routine replacement due to their age and/or
expiration date. [0060] 4. Location of first aid, medical kits,
oxygen, blood borne pathogen (BBP) kits by organization, facility,
address, location in facility, e.g. floor, and specific description
of location, such as 9.sup.th floor elevator South, and GPS
coordinates; date of last successful maintenance; and date of
expiration for supplies, equipment, and critical equipment,
components, supplies, and medication that require routine
replacement due to their age and/or expiration date. [0061] 5.
Location of event initiated by APP by address, specific descriptive
location, and, GPS. [0062] 6. Name(s) of designated Incident
Control Commander(s) (IC), including their organization; their
specific facility, address, GPS (location); email address; cell
phone; and competence level, e.g. they can they make secondary
decisions to initiate variable protocols and/or rely on
preconfigured content, based on experience, training, using rules.
[0063] 7. Name of designated Team Leaders, Security (Modified
structures/designations) (TL), including their organization; their
specific facility, address GPS (location); email address; cell
phone; date of most recent CPR/AED certification; date of most
recent AED Responder certification; date of most recent First Aid
certification; date of most recent Evacuation Leadership training,
or other pre-configured training requirements; date of most recent
Incident Command (or other relevant) training; duration of service;
and previous experience. [0064] 8. Name of all workforce personnel
(WF), including their organization; their specific facility,
address, GPS (location); email address; and cell phone. [0065] 9.
Location of other Medical Emergency Equipment First Aid, Medical
Kits, Oxygen, BBP kits, and other relevant supplies and/or
equipment, including by organization; by facility; by address; by
location in facility, e.g. floor, and specific description of
location, such as 9.sup.th floor elevator South; by GPS
coordinates; date of last successful maintenance; and date of pad
and battery, medication expiration, AED's or other medical
equipment or expirable supplies. [0066] 10. Location of
non-emergency equipment and emergency equipment, such as fire
extinguishers, evacuation equipment for personnel with
disabilities, radios, walkie talkies, megaphones, vests, flags,
etc., including by organization; by facility; by address; by
location in facility, e.g. floor, and specific description of
location, such as 9.sup.th floor elevator South; by GPS
coordinates; and date of last successful maintenance. [0067] 11.
Geo-location of boundaries of facility. [0068] 12. Geo-location of
assembly area. [0069] 13. Dynamically generated geo-mapping and/or
other technology for location of cell phones of workforce during
emergency. [0070] 14. Comparison of security data of personnel
location vs. confirmed evacuees and/or location of cell phones of
workforce during emergency.
[0071] Rules
[0072] Rules can be implemented based on a pre-configured
designation or they can be implemented dynamically.
[0073] Pre-configured rules are, for example, where an individual
registers for the APP in the Boston Facility, an emergency
notification is initiated in the Boston Facility and the database
sends notifications to trained responders in the Boston facility,
along with instructions about the location and operational status
of AEDs in the Boston facility.
[0074] Dynamic rules are, for example, where the individual who is
registered in Boston initiates an alert while in Maryland, as
determined by GPS and address location applications, and the rules
engine modifies its search dynamically for equipment and responders
based on the individual's actual location. In this case, location
can be accomplished by a coordinate mapping of the facility
interpreted into addresses using GPS and address location
applications, where the rules engine modifies its search for
equipment and responders based on the individual's actual
location.
[0075] Further, such rules can include the individual's role within
a tiered organizational structure. In such case, the rules
establish appropriate routing and chain-of-command to establish an
ad hoc emergency response organization in real time.
[0076] For example, if the primary Incident Commander does not
respond to the initial notification because, for example, he is out
of town at a conference or sick, the rules engine notifies the
first back-up incident commander and, if no response is received,
then contacts the next back-up incident commander. The individual
who first confirms IC notification receives a follow up text and/or
email with an initial task list to perform and links to additional
information that may be needed.
[0077] Organizations designate certain individuals as their ERT
members or floor wardens and provide training to them. It is not
known which of these workers are available on the day and time they
are needed. The rules engine continues to search for appropriate
responders, prioritized by training, experience, and location based
on pre-configured data. As each potential responder confirms
receipt, the responder is provided with the next series of tasks
that needs to be performed on a per floor or per facility basis.
For example, if the assignment to assist in the evacuation of the
general workforce, then the first responder to confirm is sent to
the primary exit door on the floor to shuttle the workforce out the
appropriate exit door; the next responder is sent to the
appropriate evacuation door from the building to continue exiting
the workforce from the building; the third responder is located at
the ground level to shuttle the workforce out of the building; and
a fourth responder leads the evacuated workforce to the assembly
area, etc. Security can be sent to assist distress calls that are
routed through incident command (IC).
[0078] Process Flow
[0079] FIG. 4 is a flow diagram that shows a sequence of
activities/communications in a medical emergency (ME) according to
the invention. Those skilled in the art will appreciate that the
invention is readily applicable to other types of emergency.
[0080] As shown in FIG. 4, a bystander of an ME (100), in this case
an SCA, initiates the emergency response notification system via a
mobile application (102) by accessing and using the APP on a phone,
tablet, etc. The bystander communicates with the APP and can enter
the specific location of the ME within the facility, e.g. 3.sup.rd
floor bathroom, by any form of information entry, such as typing,
voice, etc.
[0081] As discussed above, the APP exchanges information via a
communication system and Web service to access and interact with a
rules engine and database. Information that is input by the
bystander, e.g. via a cellular service, WIFI, and/or other system,
is transmitted via the Web service to the rules engine and
database.
[0082] In embodiments of the invention, a secondary screen
displays, for example, a drop down or other menu that allows the
bystander to select, for example the type of medical emergency,
e.g. SCA. The selection of pre-configured types of medical
emergencies shown on the display provides the bystander with a text
description of each medical emergency, and thus facilitates an
early assessment of the situation.
[0083] In embodiments of the invention, the bystander can also
place a call to a service, such as 911, by calling 911 directly
from the APP. As discussed above, the APP exchanges information via
a communication system to access and, to the extent possible,
interact with the 911 service. Where supported by the 911 service,
information that is input by the bystander, e.g. via a cellular
service, WIFI, and/or other system, is transmitted to the 911
service.
[0084] Responsive to the notification, the bystander of the ME
receives an optional instruction to initiate first aid or
resuscitation or other assistance as specified on the APP
(104).
[0085] The APP receives a message that asks the bystander if there
is an emergency (106). In this case there is an emergency, an SCA,
as noted above. If the bystander is seeking information, but not
providing notification of an emergency, the bystander can select
the "No" button on the APP, in which case the bystander is provided
with training links, (108) and can choose, as well, to receive
further information in connection with such training (110).
[0086] In the bystander selects the "Yes" button on the APP,
indicating that there is an emergency, the bystander may be alerted
to yell out than an ME has occurred (109), e.g. "Medical emergency,
we need an AED responder!" Embodiments of the invention contemplate
using the system for preparedness training. Thus, the APP provides
a drill options switch (111) for executing practice sessions. The
scope of the drills can be established as desired (112), e.g.
facility-wide or classroom drills. Drills can be coded to include
only designated individuals, i.e. those in a specific class; or
they can be non-coded, in which case all of the responders in the
facility are notified of the drill.
[0087] In this example above, the ME is not a drill and the APP
provides a simple dialog to the bystander to provide location
information to the system such that trained responders can be
located (114). Responsive thereto, the Web service runs a
rule-driven query of rules engine and database that compares the
location of event to that of a nearest facility having trained
responders. The system locates nearest trained responders in the
facility and prioritizes notification of the trained responders by
applying rules that determine the level and type of training and
competence required of the trained responder, as well as the
proximity of the trained responder to the event. The system also
locates the nearest appropriate equipment for the ME, such as AEDs
and other medical equipment in the case of an SCA. The location of
such equipment is prioritized by rules that evaluate the proximity
of the equipment to the event, as well as the operational status of
the equipment, e.g. if it has been recently serviced and is
operable.
[0088] The bystander is also asked if the 911 service has been
called (116). If the bystander responds with "Yes," then the
bystander is asked if the 911 service is being called by a person
other than the bystander (118), e.g. if "Yes," press the purple
button. If the bystander responds with "No," the 911 service has
not been called then the bystander is instructed to call the 911
service (120), e.g. press the green button to call the 911 service
and proceed to the next screen.
[0089] Responsive thereto, a message containing specific
information is sent to selected trained responders. In such case,
the rules engine and database generate the message and the specific
location of event within the facility is communicated to the
selected trained responders with instructions to respond,
prioritized by the trained responder's training, competency, and
proximity rules. Embodiments of the invention also send the cell
phone number of the bystander to the trained responder.
[0090] One or more messages are sent to the bystander indicating
how many trained responders have been notified, e.g. to provide the
bystander with peace of mind. In this case, the rules engine and
database generate the message and the communications system sends
the message to the bystander.
[0091] If no responders are available, a message sent to the
bystander identifying the location of the nearest appropriate
equipment, e.g. AEDs, prioritized by functionality rules. In this
case, the rules engine and database generate the message and the
communications system sends the message to the bystander.
[0092] The trained responders respond to the alert text with a
confirmation message that communicates to the database via Web
service indicating that they are responding. The message generates
the geo-location of the trained responder.
[0093] One or more additional messages are sent to the bystander.
Thus, as each trained responder responds to the alert, indicating
whether the trained responder is coming or not coming to assist,
the bystander receives such messages, e.g. for the bystander's
peace of mind and to indicate that help is on the way. In such
case, the rules engine and database generate the message and the
communications system sends the message to the bystander.
[0094] One or more additional messages are sent to the trained
responders. After the trained responders respond to the alert
indicating they are coming to assist, the en route trained
responders receive a message containing the location of the nearest
operational emergency equipment, such as AEDs. In such case, the
rules engine and database generate a message indicating the
location of nearest functioning emergency equipment and the
communications system sends the message indicating the location of
nearest operational emergency equipment to trained responders who
are en route.
[0095] In embodiments of the invention, the bystander records the
time of arrival of the first trained responder via the APP, which
then uses the Web service to record such data in the database. The
bystander also records the time that emergency equipment and
supplies are provided via the APP, which again uses the Web service
to record such data in the database. Further, the bystander also
records such other events as EMS arrival via the APP, which again
uses the Web service to record such data in the database.
[0096] Embodiments of the invention provide emergency response data
tracking, which documents the elapsed time from collapse to arrival
of a first responder.
[0097] Embodiments of the invention allow the bystander to cancel
the alert (as discussed above).
[0098] Embodiments of the invention allow a trained responder to
communicate to bystander that they are on the way to provide
assistance. As well, responders can communicate with each other,
for example, where an impromptu, tiered emergency response is
established to manage the response effort.
[0099] Database
[0100] All communications are logged in the database, and there is
a report for each incident. Aggregate reports can be generated
across multiple incidents. Information captured in the database
includes, for example: [0101] 1. Date, time, and GPS location of
the alert; [0102] 2. Who initiated the alert, by cell phone and GPS
location; [0103] 3. Who is notified of the alert, by cell phone
number; [0104] 4. Date and time of the notification; [0105] 5. Who
responds to the notification, by cell phone number and GPS
location; [0106] 6. Date and time that emergency equipment location
information is sent to each responder via the communication system;
[0107] 7. Date and time of notification of responding trained
responder and geo-location of the trained responder at the time the
confirming notification is sent; [0108] 8. Date and time of arrival
of the first trained responder; [0109] 9. Date and time that the
emergency equipment is placed in use, e.g. when an AED is attached;
[0110] 10. Date and time of EMS arrival; [0111] 11. Date and time
of alert and type of emergency; [0112] 12. Who initiated alert by
cell phone; [0113] 13. Date and time that each IC was notified and
confirmed notification; [0114] 14. Date and time that each TL
notified and confirmed notification; [0115] 15. Date and time that
each WF notified; [0116] 16. Date and time each IC, TL, and/or WF
responded that they received initial notification; [0117] 17. Date
and time that each WF confirmed notification received, successful
evacuation, and successfully reached assembly area is confirmed;
[0118] 18. Date and time and GPS of all "failure to evacuate" or
"distress" messages; [0119] 19. Date and time and content of each
ongoing communication by text between IC, TL, and/or WF and content
of text and/or email communication; and [0120] 20. Date and time of
EMS, fire, and/or police arrival by IC.
[0121] Sequence of Operations
[0122] The foregoing is illustrated in FIG. 5, which is a flow
diagram showing the sequence of operations during an emergency
event according to the invention. In FIG. 5:
[0123] Step 1. Bystander of emergency, such as a medical emergency
(ME), initiates emergency response notification system via mobile
application ("APP"): [0124] 1A: Bystander to APP--bystander of ME
emergency initiates emergency response notification system via APP
by accessing and using App on phone, tablet, etc.; bystander
communicates (type/vocal input) to APP the specific location within
the facility, e.g. 3.sup.rd floor bathroom); and [0125] 1B: APP to
communication system; [0126] 1C: Communication system to Web
service; and [0127] 1D: Web service to rules engine/database--Data
inputted by bystander, via cellular service, WIFI, etc.,
transmitted via Web service to rules engine/database.
[0128] Step 2. Bystander to 911--bystander of ME calls 911 directly
from APP: [0129] 2A: Bystander to APP; [0130] 2B: APP to
communication system; and [0131] 2C: Communication system to
911;
[0132] Step 3. App to bystander--bystander of ME receives optional
instruction to initiate first aid or resuscitation or other
assistance as specified on the APP.
[0133] Step 4. Web service to rules engine/database--Web service
runs rule-driven query of rules engine/database. This query
includes: [0134] a. Comparing location of event to nearest facility
having trained responders; [0135] b. Locating nearest trained
responders in facility; [0136] c. Prioritizing notification of the
trained responders by rules that determine the level and type of
training, competence, proximity; [0137] d. Locating nearest
emergency equipment, e.g. AEDs/medical equipment; and [0138] e.
Prioritizing by rules that evaluate proximity to the event, and
emergency equipment functionality.
[0139] Step 5. Message containing specific information sent to
select trained responders: [0140] 5A: Rules engine/database to
communications system--Rules engine/database generates message; and
[0141] 5B Communications system to trained
responders--Communications system communicates the following
information to selected trained responders: The specific location
of event within the facility with instructions to respond
prioritized by trained responder training, competency and proximity
rules.
[0142] Step 6. Message sent to bystander informing them how many
trained responders have been notified): [0143] 6A: Rules
engine/database to communications system--Rules engine/database
generates message; and [0144] 6B: Communications system to
bystander--Communications system sends message to bystander.
[0145] If no responders are available, a message is sent to
bystander informing the bystander of the location of the nearest
emergency equipment prioritized by functionality rules: [0146] 6C:
Rules engine/database to communications system--Rules
engine/database generates message; and [0147] 6D: Communications
system to bystander--Communications system sends message to
bystander.
[0148] Step 7. Trained responder responds--Trained responders
respond to the alert text with a confirmation message that
communicates to database via the Web service indicating that they
are responding. Message generates geo-location of the trained
responder: [0149] 7A: Trained responder to communication system;
[0150] 7B: Communication system to Web service; and [0151] 7C: Web
service to rules engine/database.
[0152] Step 8. Messages sent to bystander--As each trained
responder responds to the alert, indicating that the trained
responder is coming or not coming to assist, the bystander receives
messages: [0153] 8A: Rules engine/database to communications
system--Rules engine/database generates message; and [0154] 8B:
Communications system to bystander--Communications system sends
message to bystander.
[0155] Step 9. Messages sent to trained responders--After a trained
responder responds to the alert indicating they are coming, the en
route trained responders receive a message containing location of
nearest operational emergency equipment: [0156] 9A: Rules
engine/database to communications system--Rules engine/database
generates message indicating location of nearest functioning
emergency equipment; and [0157] 9B: Communications system to
trained responders--Communications system sends a message
indicating the location of nearest operational emergency equipment
trained responders who are en route.
[0158] Step 10. Bystander to APP--bystander records time of arrival
of first trained responder via the APP which uses the Web service
to record data in database: [0159] 10A: Bystander to APP; [0160]
10B: APP to Web service; and [0161] 10C: Web service to
database.
[0162] Step 11. Bystander to APP--bystander records time that
emergency equipment and supplies re provided via the APP which uses
Web service to record data in the database: [0163] 11A: Bystander
to APP; [0164] 11 B: APP to Web service; and [0165] 11C: Web
service to database.
[0166] Step 12. Bystander to APP--bystander records EMS arrival via
APP which uses the Web service to record data in the database:
[0167] 12A: Bystander to APP; [0168] 12B: APP to Web service; and
[0169] 12C: Web service to database.
[0170] Content
[0171] In embodiments of the invention, content that is
communicated amongst the participants can include, for example,
specific written instructions on actions to perform; graphic
representations, i.e. of actions to perform, video, voice, and
graphics; use of voice commands/technology, such as SIM to provide
instructions and/or content; and multi-lingual capabilities. For
example, this invention can be used with any language including,
for example, Chinese, Japanese, etc. with which the database is
compatible.
[0172] In embodiments of the invention, participants receive
content, based upon their role, that includes:
[0173] ICs: Based on company-established level of responsibility,
company-based emergency response policies and procedures, and other
instructive company established documents and protocols: [0174]
Initial procedures, e.g. turn off elevators and escalators, lock
certain doors, contact specific authorities inside and outside of
company; [0175] Option to initiate variable protocols based by type
of emergency, including primary and secondary emergencies, medical
emergencies, non-medical, emergencies, etc.; and [0176] Ongoing
communications.
[0177] TLs or other designees, such as security: Based on
company[established level of responsibility, company-based
emergency response policies and procedures of company, and other
instructive company established documents and protocols: [0178]
Initial procedures, e.g. get radio, vest, megaphone, and/or flag,
and go to pre-assigned location to assist evacuation; and [0179]
Ongoing communications.
[0180] WF: Based on emergency response policies and procedures of
company and level of complexity (described below): [0181] Simple
notification text instruction to evacuate and location of assembly
area; [0182] Text indicating location of nearest exit based on
their pre-configured location and assembly area; [0183] Graphic of
evacuation route for their pre-configured location and assembly
area; [0184] GPS or other technology driven instructions to nearest
exit and to assembly point based on their dynamic location; and
[0185] Bluetooth or wireless or other frequency transmitter driven
instructions to nearest exit and to assembly point.
[0186] Drill Functions
[0187] As discussed above, drill functions can be performed to
prepare participants for an emergency. Drill codes allow selection
of an ad hoc group of participants, independent of organization or
geographic boundaries. At the start of a drill, all participants
are given a shared code, which each person enters at about the same
time into his handheld device. This code therefore defines the
group of participants. Drill codes automatically expire after a
fixed time, e.g. the duration of a drill, so that they can re-used
in the future. When a drill incident is initiated, only the
participants in the pool with valid, unexpired drill codes are
alerted. Using drill codes during responder classes allows the
emergency response system to be used across organizational barriers
or geography.
[0188] A drill simulates an emergency and helps assess the adequacy
of emergency response in the facility and/or organization and to
allow repetitive practice, which enhances the quality and reduces
the time to carry out the response with increased familiarity. The
instructor for the drill enters drill code as initiator of the
drill. Students, responders, and personnel attending the class
enter drill code as responders. Only those individuals who have
entered the drill code receive the communications during the drill.
All messaging begins with a notification that is received via the
APP, such as MEDICAL DRILL/EMERGENCY DRILL.
[0189] Spontaneous drills, i.e. drills that do not have drill
codes, may also be held to test the system and response abilities
of a facility and to empower the workforce by practicing for an
emergency. In such cases, all responders receive all communications
and all messaging begins with a notification that is received via
the APP, such as MEDICAL DRILL/EMERGENCY DRILL. The instructor or
other authorized person can cancel the alert at any time via the
APP.
[0190] Sudden Cardiac Arrest ("SCA") Emergency Response
Notification System
[0191] FIG. 6 is a flow diagram showing the sequence of operations
during an SCA emergency event according to the invention. The
system for such application is architecturally similar to the
discussed above for a generic emergency event, for example as
discussed in connection with FIGS. 1 and 2. Those skilled in the
art will appreciate that some variations, all within their skill,
may be made as appropriate to implement this embodiment of the
invention.
[0192] Database
[0193] In addition to that data stored in connection with a generic
emergency response system, as described above, data stored in
database for this embodiment of the invention also includes the
location of AEDs by organization, facility, address, and location
in facility, such as floor, and a specific description of location,
e.g. 9.sup.th floor elevator South; GPS coordinates; date of last
successful maintenance; and date of pad and battery expiration.
[0194] All communications are logged in the database and there is a
report for each incident. Aggregate reports are generated across
multiple incidents and include, for example: [0195] 1. Date, time,
and GPS location of the alert; [0196] 2. Who initiated the alert,
by cell phone and GPS location; [0197] 3. Who is notified of the
alert, by cell phone number; [0198] 4. Date and time of
notification; [0199] 5. Who responds to the alert, by cell phone
number and GPS location; [0200] 6. Date and time that information
regarding AED locations is sent to each responder via the
communication system; [0201] 7. Date and time of notification of
responding, using GPS if responder had APP; [0202] 8. Date and time
of arrival of first trained responder; [0203] 9. Date and time that
an AED is attached; and [0204] 10. Date and time of EMS
arrival.
[0205] Sequence of Activities/Communications in an SCA
Emergency
[0206] In FIG. 6:
[0207] Step 1. bystander of SCA emergency initiates emergency
response notification system via mobile application ("APP"): [0208]
1A: bystander to APP--bystander of SCA emergency initiates
emergency response notification system via APP by accessing and
using the App on a phone, tablet, etc.; the bystander communicates
to APP, for example by typing or voice input, the specific location
within the facility, e.g. 3.sup.rd floor bathroom; [0209] 1B: APP
to communication system; [0210] 1C: Communication system to Web
service; and [0211] 1 D: Web service to rules engine/database--Data
input by the bystander, e.g. via a cellular service, WIFI, etc. is
transmitted via the Web service to the rules engine/database.
[0212] Step 2. bystander to 911--bystander of SCA calls 911
directly from the APP: [0213] 2A: bystander to APP; [0214] 2B: APP
to communication system; and [0215] 2C: Communication system to
911.
[0216] Step 3. App to bystander--bystander of SCA receives optional
instructions to initiate resuscitation on the victim via APP.
[0217] Step 4. Web service to rules engine/database--The Web
service runs a rule-driven query of rules engine/database. This
query includes, for example: [0218] a. Comparing location of event
to nearest facility having trained responders; [0219] b. Locating
nearest trained responders in facility; [0220] c. Prioritizing
notification of the trained responders by rules that determine the
level and type of training, competence, proximity; [0221] d.
Locating nearest AEDs; and [0222] e. Prioritizing by rules that
evaluate proximity to the event, and AED functionality.
[0223] Step 5. A message containing specific information is sent to
selected trained responders: [0224] 5A: Rules engine/database to
communications system--Rules engine/database generates message; and
[0225] 5B Communications system to trained
responders--Communications system communicates the following
information to selected trained responders: The specific location
of event within the facility with instructions to respond
prioritized by trained responder training, competency and proximity
rules.
[0226] Step 6. Messages sent to the bystander informing the
bystander how many trained responders have been notified: [0227]
6A: Rules engine/database to communications system--Rules
engine/database generates message; and [0228] 6B: Communications
system to bystander--Communications system sends a message to the
bystander.
[0229] If no responders are available, a message sent to the
bystander informing the bystander of the location of the nearest
AEDs, prioritized by functionality rules: [0230] 6C: Rules
engine/database to communications system--Rules engine/database
generates message; and [0231] 6D: Communications system to
bystander--Communications system sends the message to
bystander.
[0232] Step 7. Trained responder responds--Trained responders
respond to the alert text with a confirmation message that
communicates to the database via the Web service indicating that
they are responding. The message generates a geo-location of the
trained responder: [0233] 7A: Trained responder to communication
system; [0234] 7B: Communication system to Web service; and [0235]
7C: Web service to rules engine/database.
[0236] Step 8. Messages sent to the bystander--As each trained
responder responds to the alert, indicating whether the bystander
is coming or not coming to assist, the bystander receives messages:
[0237] 8A: Rules engine/database to communications system--Rules
engine/database generates the message; and [0238] 8B:
Communications system to bystander--Communications system sends the
message to bystander.
[0239] Step 9. Messages sent to trained responders--After a trained
responder responds to the alert indicating that the trained
responder is coming to assist, the en route trained responders
receive a message containing the location of nearest functional
AEDs: [0240] 9A: Rules engine/database to communications
system--Rules engine/database generates message indicating location
of nearest functioning AEDs; and [0241] [9B: Communications system
to trained responders--Communications system sends a message
indicating the location of the nearest functioning AEDs to the
trained responders who are en route.
[0242] Step 10. bystander to APP--bystander records time of arrival
of first trained responder via the APP, which uses the Web service
to record data in the database: [0243] 10A: bystander to APP;
[0244] 10B: APP to Web service; and [0245] 10C: Web service to
database.
[0246] Step 11. bystander to APP--bystander records time that the
AED is attached via the APP, which uses the Web service to record
data in the database: [0247] 11A: bystander to APP; [0248] 11 B:
APP to Web service; and [0249] 11C: Web service to database.
[0250] Step 12. bystander to APP--bystander records EMS arrival via
the APP, which uses the Web service to record data in the database:
[0251] 12A: bystander to APP; [0252] 12B: APP to Web service; and
[0253] 12C: Web service to database.
[0254] Sequence of Activities/Communications in a Non-Medical
Emergency (NME)
[0255] FIG. 7 is a flow diagram showing a non-medical emergency
response model according to the invention, in which the
relationship between the general workforce, floor wardens and/or
emergency response team, security staff, and incident coordinator
is shown. This model is discussed in detail below.
[0256] FIGS. 8A-8C are a flow diagrams showing the sequence of
operations during a non-medical emergency event according to the
invention.
[0257] In FIGS. 8A-8C:
[0258] Step 1. Bystander of NME initiates emergency response
notification system via mobile application (APP): [0259] 1A:
Bystander to APP--bystander of NME emergency initiates emergency
response notification system via APP by accessing and using APP on
phone, tablet, etc.; Bystander communicates (type/vocal input) to
APP the specific location within the facility, e.g. 3.sup.rd floor
bathroom; [0260] 1 B: APP to communication system; [0261] 1C:
Communication system to Web-service; [0262] 1 D: Web-service to
rules engine/database--Data inputted by bystander via cellular
service, WIFI, and/or other is transmitted via the Web-service to
the rules engine/database: [0263] a. Secondary screen allows
selection between medical and non-medical emergencies; or [0264] b.
Secondary screen uses drop down screen to select type of medical or
non-medical emergency; and/or [0265] c. Permits text description of
emergency.
[0266] Step 2. Bystander to 911--Bystander of NME calls 911
directly from APP: [0267] 2A: Bystander to APP; [0268] 2B: APP to
communication system; and [0269] 2C: Communication system to
911.
[0270] Step 3. App to Bystander--Bystander of NME receives optional
instruction to assist in emergency based on type of emergency and
competence level, i.e. nearest fire extinguisher with instructions
on how to use it if there is a small fire.
[0271] Step 4. Web-service to Rules Engine/Database--Web-service
runs a rule-driven query of the rules engine/database. This query
includes: [0272] Comparing location of event; [0273] Identifying
IC, TL, and/or WF for facility; [0274] Selecting communications and
content based on defined roles, i.e. IC, TL, WF; [0275] Identifying
nearest facility with trained responders; [0276] Prioritizing
notification of personnel by roles; [0277] Locating nearest
required equipment based on designated roles, type of emergency,
and availability of equipment by designated geographic area;
locating nearest AEDs/medical equipment; [0278] Prioritizing by
rules that evaluate proximity to event and AED/medical; and [0279]
Prioritizing by rules that evaluate type of emergency, proximity to
event, and equipment functionality.
[0280] Step 5. Message containing specific information sent to IC:
[0281] 5A: Rules Engine/Database to Communications System--Rules
Engine/database to communications system generates message; and
[0282] 5B: Communications System to IC--Communications system to IC
communicates the following information: notification of emergency,
location, and type of emergency with instructions for completing
initial pre-configured series of actions and to confirm receipt of
notification.
[0283] Step 6. Message containing specific information sent to TL:
[0284] 6A: Rules Engine/Database to Communications System--Rules
engine/database to communications system generates message; and
[0285] 6B: Communications System to TL--Communications system to TL
communicates the following information: notification of emergency,
location, and type of emergency with instructions for completing
initial pre-configured series of actions and to confirm receipt of
notification, including to retrieve equipment, supplies, assume
proper location, assist with evacuation, and confirm receipt of
notification. In addition, report initial and ongoing problems to
IC. Variable content for initial instructions includes ongoing
communications, e.g. Doug is unable to evacuate, because he is
trapped under bookshelf that fell; Mary needs a disability stair
chair to exit; there is a secondary fire in the hallway near the
3.sup.rd floor bathroom; etc.
[0286] Step 7. Message containing specific information sent to WF:
[0287] 7A: Rules Engine/Database to Communications System--Rules
engine/database to communications system generates message; and
[0288] 7B: Communications System to WF--Communications system to WF
communicates the need to initiate evacuation procedures including
location and/or directions to nearest evacuation exit from their
location, and assembly point address, and to confirm receipt of
notification. This can include variable quantity and quality of
content; and use of variable technologies to assist with locating
exits, such as Bluetooth or wireless transmitter technology to
assist WF to reach evacuation exit rapidly. The message includes
instructions to respond to alert text with notification that they
have evacuated and reached assembly point.
[0289] Step 8. IC to APP to Communication System to Web-Service to
Rules Engine/Database, where IC responds to the alert text, with
communication to database via the Web-service indicating that they
are assuming command, and if IC does not respond, an alternate
pre-designated authority is notified: [0290] 8A: IC to APP--IC
responds to the alert text, with communication to database via
web-service indicating that they are assuming command; [0291] 8B:
APP to Communication System; [0292] 8C: Communication System to
Web-Service; and [0293] 8D: Web-Service to Rules
Engine/Database--Data inputted by IC via cellular service, WIFI,
and/or other is transmitted via the Web-service to the rules
engine/database.
[0294] Step 9. TL to APP to Communication System to Web-Service to
Rules Engine/Database. TLs respond to the alert text with
communication to database via the Web-service, indicating that they
are responding and assuming their responsibilities. If no response,
the IC assesses the need for additional personnel notification:
[0295] 9A: TL to APP--TLs respond to the alert text with
communication to database via the Web-service, indicating that they
are responding and assuming their responsibilities; [0296] 9B: APP
to Communication System; [0297] 9C: Communication System to
Web-Service; and [0298] 9D: Web-Service to Rules
Engine/Database--Data inputted by IC via cellular service, WIFI,
and/or other) is transmitted via the Web-service to the rules
engine/database.
[0299] Step 10. WF to APP to Communication System to Web-Service to
Rules Engine/Database. WF responds to the alert text with
communication to the database via Web-service, indicating that they
have received notification: [0300] 10A(1): WF to APP--WF responds
to the alert text with communication to database via the
Web-service, indicating that they have received notification;
[0301] 10B(1): APP to Communication System; [0302] 10C(1):
Communication System to Web-Service; and [0303] 10D(1): Web-Service
to Rules Engine/Database--Data inputted by IC via cellular service,
WIFI, and/or other is transmitted via the Web-service to the rules
engine/database. WF clicks notification on evacuation screen that
they have successfully evacuated. [0304] 10A(2): WF to APP--WF
clicks notification on evacuation screen that they have
successfully evacuated; [0305] 10B(2): APP to Communication System;
[0306] 10C(2): Communication System to Web-Service; and [0307]
10D(2): Web-Service to Rules Engine/Database--Data inputted by IC
via cellular service, WIFI, and/or other is transmitted via the
Web-service to the rules engine/database. WF clicks notification on
assembly screen that they have successfully arrived at assembly
point. [0308] 10A(3): WF to APP--WF clicks notification on assembly
screen that they have successfully arrived at assembly point;
[0309] 10B(3): APP to Communication System; [0310] 10C(3):
Communication System to Web-Service; and [0311] 10D(3): Web-Service
to Rules Engine/Database--Data inputted by IC via cellular service,
WIFI, and/or other is transmitted via the Web-service to the rules
engine/database.
[0312] Step 11. RE to IC: Database/rules engine generates
communication to IC providing continuously updated and/or compiled
report of personnel who have successfully evacuated and reached
assembly point, including a continuously updated report of all
personnel who have confirmed receipt of notified of emergency and
their GPS location, a continuously updated report of all personnel
who have provided notification of evacuation and their GPS
location, and a continuously updated report of all personnel who
have provided notification of arriving at the assembly area and
their GPS location.
[0313] Step 12. IC to APP to Communication System to Web Service to
Rules Engine/Database: IC indicating time of arrival of each
EMS/Fire/Police arrival.
[0314] Step 13. IC to APP to Communication System to Web Service to
Rules Engine/Database: IC requests APP geo-locate location of all
personnel.
[0315] Step 14. Database/Rules engine to Communication System:
Dynamically generated map of cellphones locating personnel who have
not evacuated as per GPS coordinates within the facility and
require assistance.
[0316] Step 15. Ongoing communication between ICs, TLs, and WF:
Ongoing communication between ICs, TLs, and WF including requests
for assistance; identification of injuries, e.g. Joe broke leg from
falling debris, Doug had a heart attack, Sam sustains major bleed
from falling glass; identification of secondary emergencies, e.g.
fire following earthquake, do something on the chart that indicates
all the way across the IC, WF, TL, and people ongoing
communications.
[0317] Workforce Evacuation Notification
[0318] FIGS. 9A-9D area series of screenshots showing a workforce
evacuation notification sequence according to the invention, which
an individual uses the APP to send a notification that they have
received the evacuation notification (FIG. 9A), that they have
exited the building (FIG. 9B), and that they have arrived at their
pre-designated assembly point (FIG. 9C); or that they are in
distress (FIG. 9D).
[0319] Embodiments of the invention identify evacuation exits with
a transmitted signal to direct workforce members to a nearest
evacuation exit. The signal can comprise any one or more of a
Wi-Fi-based IP addresses, Bluetooth, radio, satellite, pre-placed
transmission equipment proximate to said exits, Wi-Fi-based signals
transmitted from exit doors at said exits. Wi-Fi signals from a
nearest router.
[0320] Embodiments of the invention locate non-evacuating personnel
with a transmitted signal. The signal can comprise any one or more
of Wi-Fi-based IP addresses, Bluetooth, radio, satellite,
pre-placed transmission equipment proximate to said exits,
Wi-Fi-based signals transmitted from exit doors at said exits,
Wi-Fi signals from a nearest router. In embodiments of the
invention, the signal includes instructions in any of text and
graphic format to said non-evacuating personnel directing them to a
nearest exit. Notifications can include any one or more of text,
graphics, voice, and visual dynamic directions, such as GPS
directions (WAZE).
[0321] In embodiments of the invention, location information can be
determined from, for example, the elevation component of GPS, where
the height of each floor is pre-calculated to locate the individual
by floor. Location information can also be determined from the APP
using the proximity of the phone signal to the IP of the routers in
the facility; using the proximity of the phone signal to the
wireless signal of a transmitter located in the evacuation door;
using the proximity of the phone signal to the Bluetooth signal of
a transmitter located on the evacuation door; or with any device
that can transmit and receive signals. Embodiments of the invention
use any of the foregoing techniques to create a dynamic map of the
location of workforce personnel, trained responders, emergency
equipment, exit doors, etc.
[0322] Role-Based Task Generation
[0323] FIG. 10 is a flow diagram showing an example of how the
role-based details are lifted out of the emergency response
protocol and transmitted to the appropriate role based individual
in an emergency, where an electronic site survey generates
organization specific emergency response protocols that detail
role-based tasks according to the invention.
[0324] In FIG. 10, the top screen is a sample frame of an
electronic site survey that is completed by an organization.
Authorized personnel complete text screens in answer to questions
that reflect the customized information that is included in their
emergency response policies, procedures, plans, and protocols. For
example, in #51, the organization states that the phone number that
must be dialed to reach an outside line and call 911 is actually
9-911. This phone number is incorporated into their Emergency
Response Protocol (bottom screen on the right in FIG. 10). This
field is transmitted to the mobile application to individuals who
are attempting to initiate a call to 911 from a company
landline.
[0325] In example #53, the initial tasks of the Incident Commander
are determined and typed into the electronic site survey (top of
FIG. 10) by the incident commander or his designee who is
authorized to develop the organization's policies and procedures.
Once it is confirmed that these are the organizational IC's initial
responsibilities in an emergency, they are incorporated into the
organization's emergency response plan (top frame in lower half of
page on the right In FIG. 10). At the time of an emergency, these
tasks are transmitted to the IC on his mobile application, upon
confirmation of receipt of notification of an emergency from a
bystander and/or witness for an emergency that requires initiation
of a command structure.
[0326] Alert Cancellation
[0327] FIG. 11 is a flow diagram showing the cancellation of an
alert according to the invention. In FIG. 11 if an alert is to be
cancelled 60, the APP provides a message the bystander 62 advising
the bystander that the alert can be cancelled. A button 64 can then
be selected by the bystander to cancel the alert.
[0328] If the bystander did not intend to cancel the alert, the
cancellation can be rescinded by pressing a button, e.g. press
green to re-alert the emergency responders. The alert is then
reinstituted. For example, during an alert the system alerts the
bystander to take an action (200), such as applying CPR if trained
or willing to do so. The systems records that time at which the
first responder is on the scene (202). The APP provides a button
for the bystander to press indicating the arrival of the first
responder. The system also records such activities as the attaching
of an AED to the victim (204). Again, a button can be pressed by
the bystander to indicate this action has taken place. The system
also records when an EMS arrives (206). Again, a button can be
pressed by the bystander to indicate this event has taken place.
Thereafter, the alert is completed (208).
[0329] The APP
[0330] The APP is a mobile application that alerts all trained
first responders to the scene of an emergency, such as a sudden
cardiac arrest (SCA) or medical emergency. Users may be certified
trained responders or laypersons. For example, consider the
following participants in a sudden cardiac arrest (SCA) or medical
emergency: [0331] 1. The victim of the medical emergency; [0332] 2.
Bystanders to the event, whether laypersons or trained responders;
and [0333] 3. Certified first responders who are not at the
event.
[0334] Embodiments of the invention include:
[0335] Real Life Event
[0336] As part of an organization's emergency response plan, the
general workforce downloads and initially registers the mobile
application. Bystanders to the event activate the APP and verify
the event location. If the event occurs at the location for which
the bystander originally registered, then the bystander types in
the specific location of the event into provided field. If the
bystander is at a different location, then a drop down menu is
provided for an alternative facility where the bystander is now
located. (In embodiments of the invention, GPS is used as first
determinant of location and, if it is not available, then the
system falls back on a pre-configured location, and the user must
change location by a drop down menu.
[0337] The APP communicates the location of the emergency to the
database and rules engine system via a Web service. The rules
engine uses an algorithm and searches the specified company and
facility for a prioritized call-to-action list of certified first
responders. In embodiments of the invention, the order of priority
of called responders is the most recently trained responders,
certified responders, certified trainees, and trainees requiring
re-certification. The Web service compiles a list of the certified
first responders in order of most recent skills dates, i.e.
certification dates, to least recent skills dates.
[0338] The system sends both an email and a text message to these
certified first responders at the facility. To send the email or a
text message, the APP sends a request to the Web service. The Web
service sends out the emails through, for example, SMTP. The SMS
gateway captures the original call-to-action ID and establishes
communication between the bystander and the facility alerted
responders. Each responder receives multiple alerts via SMS and
emails to ensure that this notification is unique from typical
SMS/email reception. Upon receiving an alert, the responder replies
via SMS/email if they are on the way. The bystander receives a
notification on their smartphone, tablet, etc. of the number of
responders that have been alerted and the number of responders that
are on the way. The APP performs tracking of the event's vital
clinical performance milestones, such as time to first responder
arrival; time to AED Pad attachment; and time to EMS arrival.
[0339] Facility Wide Drill
[0340] This function allows trained responders to practice their
facility's emergency response plan and has the same functionality
as a real life event, except that the actual content of the email
and text alerts says "THIS IS A DRILL." Text messages and email are
only sent one time.
[0341] Drill Code Option
[0342] This embodiment of the invention provides the same
functionality as the facility wide drill, except this embodiment is
class specific and is used during a training class. This means that
the APP is activated and messages are sent to a specific subset of
people. Rather than the algorithm pulling certification dates and
sorting responders to receive alerts, the participants all enter a
specific drill code. Those entering the drill code receive the
email and text. The email and text are sent as many times as the
APP button is pushed. This drill code can be used regardless of
company or facility. Thus, trainees from different sites can train
together and get alerts.
[0343] Operation
[0344] Critical to the viability of the APP is the availability of
the database and rules engine system that stores the physical
facilities and the certified responders who are located at each
facility. Responders must complete regular training and drills
which are tracked in the database and rules engine system.
[0345] Responders receive certifications in areas such as CPR,
First Aid, and AED response. Response planning is structured to
ensure adequate response time from one or more trained responders
within the physical location.
[0346] As part of a program rollout at a facility, employees of an
organization are encouraged to download and install the mobile APP
on their phones. Registration and downloading the App requires that
the user enter, for example, a code specific to a certain company.
Based on this code, a menu of locations is provided, allowing the
user to select the appropriate facility. The list of locations is
retrieved from a central Web service over the public Internet. The
Web service uses the database and rules engine system to retrieve
the list of facilities using the company code.
[0347] Once the location is selected, the user also provides his
name, email address, and phone number to register the APP. The
registration information is passed to the database and rules engine
system via another Web service. The information is also stored on
the user's phone or tablet. More information about the responders
and other members of the emergency response team is stored in the
database, but it is not necessarily related to registration for the
APP. For example, such information is retrieved based on the
individual's role as defined in the database. In fact, in
embodiments of the invention responders do not need to have the APP
to be contacted. They are automatically contacted once an alert is
sent to the database, based on the rules engine determining who is
required for the emergency, which is pre-configured by role in the
database. Responders are identified in the database, for example,
by their email address, cell phone number, name, company, and
facility. All of the above information is stored based on
identifying the individual in this way, i.e. their training status,
their role, and, therefore, the information that they are to
receive.
[0348] Although responders do not have to be registered to be
notified in case of an emergency they must be registered to send an
alert themselves.
[0349] In embodiments of the invention, users of the APP are either
any of untrained general workforce members who serve as the witness
or bystander of the emergency and initiated the notification
process and/or initiate the emergency response plan, and trained
responders who may also witness an emergency.
[0350] Subsequent launching of the APP bypasses the registration
process and the user is immediately prompted, "Do you have an
Emergency?", to which the user can answer "Yes," "No," or "Drill."
If the user answers "Yes," a screen with a large button is
presented, that initiates the medical response protocol. Prior to
pressing the button, the user can verify their location or enter
specific location information, e.g. via touch or dictation.
Answering "No" allows users to obtain non-emergency information or
change their registration information. Answering "Drill" is
discussed below.
[0351] When the button is pressed, the notification process begins.
The APP invokes another network Web service, including the
location, phone number, and name of the initiator. The Web service
logs an incident in the database and rules engine system and then
retrieves a list of potential responders using the certification
data for the facility. The responder list is sorted so that most
recently certified responders are at the top of the list and added
to a messaging system queue. The service then returns the number of
notifications that are queued and the initiator is told how many
messages were sent.
[0352] The messaging system sends medical alert text messages to
responder phones and also sends email messages as a back-up. The
responders do not need an APP to receive these messages. The
messaging system interacts with a third-party SMS gateway using its
public API to transmit the actual messages. The gateway is
configured with a pool of phone numbers and the messaging system
transmits the text messages by rotating through the phone numbers
pool. This allows transmission of hundreds of emergency
notifications within seconds, without drops from phone system
carriers, seconds that are critical for a cardiac event. The text
message notification includes a prompt to "reply Yes if you will
respond" and the SMS gateway is configured to invoke a Web service
when it receives such a response. This Web service tracks the
responses and sends additional text messages back to the initiator,
letting the initiator know that a responder is en route.
[0353] After initiating the event notification, the mobile APP user
is taken to progressive screens where further progress is tracked.
The user is prompted to call the 911 service, then asked to push
buttons progressively, e.g. when the responder arrives, when a
defibrillator (AED) is attached, and when EMS arrives. Each of
these actions interacts with the Web services to record these
events along with associated timestamps in the database and rules
engine system. Over time, this allows data about such events to be
collected, which can be analyzed and summarized to produce response
rate studies. The user may also cancel an incident if the
notification system was initiated in error. As with the initial
notification, a Web service is invoked which determines the list of
responders and, in the same manner as before, cancellation messages
are sent to the responders.
[0354] It is important to practice emergency response events
regularly using drills. After registration has been completed, the
user also has the option to select "Drill" when launching the
mobile APP. As discussed above, there are two types of drills, a
facility-wide drill and a classroom drill using a drill code. After
pressing "Drill" the user is prompted to enter a drill code for a
classroom drill, or leave it blank for a facility-wide drill. The
facility wide drill is identical to the actual incident
notification process described above, except that the notifications
clearly include "THIS IS A DRILL" in the text.
[0355] The classroom drill requires the instructor or drill
coordinator to provide a drill code to all of the participants. The
mobile APP users can then enter the drill code and join the drill
either as an event initiator or responder. The APP transmits the
phone numbers to a Web service which tracks drill codes and
participants in the database and rules engine system. Initiators
are then taken to through the same screens described above, with
the button to begin the notifications. However, the drill code is
included in the incident notification Web service and, instead of
retrieving all responders at a particular facility, it retrieves
only those responders associated with the drill code. In this mode,
only the drill code is used for selecting responders.
[0356] The drill responders can be selected from across multiple
facilities. Drill codes have a limited validity period, e.g. 30
minutes, depending on the class timeframe. Responders are not
notified if they joined the drill during a period that has
lapsed.
[0357] User Interface
[0358] FIG. 12-17 are screen shots showing various user screens
provided by the APP during an emergency.
[0359] Do you have an emergency? See FIG. 12.
[0360] This screen asks the user if they have an emergency and
presents them with two options, yes or no. By clicking on the "yes"
button the user starts the emergency response sequence. If the user
chooses the "no" option they are taken to to menu that provides
three choices to learn more about the APP, the AED program, or
CPR/AED training.
[0361] EU-Alert Information Menu
[0362] By clicking on the "no" option in the "do you have an
emergency screen" the user taken to this screen which has three
informative options which are identical to the "thank you for
registering screen."
[0363] Emergency Alert Initiated. See FIG. 13.
[0364] Initiate the emergency response plan by yelling out Medical
Emergency!! We need a responder!! To proceed to the next step press
the "next button."
[0365] Notify Your Trained Emergency Responders. See FIG. 14.
[0366] Ensure that correct site is highlighted in the drop down
menu. Provide a specific location in the second data field and
press the green button to send out the alert to nearby
responders.
[0367] Emergency Alert Confirmation. See FIG. 15.
[0368] Press the green button to automatically call 911 and alert
the local EMS about the event. If someone else is calling 911, or
the local EMS have already been notified, press the purple button.
If the user wishes to cancel the alert, press the blue button in
the top right corner of the screen.
[0369] Start CPR. See FIG. 16.
[0370] If you are qualified to perform CPR please begin to do so
immediately. Once the responders arrive with the AED please press
the green button in the middle to move on to the next screen. The
user also has the option to cancel the alert for any reason by
pressing the blue "cancel alert" button in the top right corner of
the screen.
[0371] Attach AED. See FIG. 17.
[0372] When the responders arrive with the AED in hand, make sure
to properly attach the device to the victim as quickly as possible.
Once this has been completed press the green button in the middle
of the screen to move on to the next step. If the user needs to
cancel the alert, press the blue button in the top right
corner.
[0373] Confirm EMS
[0374] Once EMS arrives at the scene press the green button in the
middle to complete the alert.
[0375] Computer Implementation
[0376] FIG. 18 is a block diagram of a computer system that may be
used to implement certain features of some of the embodiments of
the invention. The computer system may be a server computer, a
client computer, a personal computer (PC), a user device, a tablet
PC, a laptop computer, a personal digital assistant (PDA), a
cellular telephone, an iPhone, an iPad, a Blackberry, a processor,
a telephone, a Web appliance, a network router, switch or bridge, a
console, a hand-held console, a (hand-held) gaming device, a music
player, any portable, mobile, hand-held device, wearable device, or
any machine capable of executing a set of instructions, sequential
or otherwise, that specify actions to be taken by that machine.
[0377] The computing system 40 may include one or more central
processing units ("processors") 45, memory 41, input/output devices
44, e.g. keyboard and pointing devices, touch devices, display
devices, storage devices 42, e.g. disk drives, and network adapters
43, e.g. network interfaces, that are connected to an interconnect
46.
[0378] In FIG. 18, the interconnect is illustrated as an
abstraction that represents any one or more separate physical
buses, point-to-point connections, or both connected by appropriate
bridges, adapters, or controllers. The interconnect, therefore, may
include, for example a system bus, a peripheral component
interconnect (PCI) bus or PCI-Express bus, a Hyper Transport or
industry standard architecture (ISA) bus, a small computer system
interface (SCSI) bus, a universal serial bus (USB), IIC (12C) bus,
or an Institute of Electrical and Electronics Engineers (IEEE)
standard 1394 bus, also referred to as Firewire.
[0379] The memory 41 and storage devices 42 are computer-readable
storage media that may store instructions that implement at least
portions of the various embodiments of the invention. In addition,
the data structures and message structures may be stored or
transmitted via a data transmission medium, e.g. a signal on a
communications link. Various communications links may be used, e.g.
the Internet, a local area network, a wide area network, or a
point-to-point dial-up connection. Thus, computer readable media
can include computer-readable storage media, e.g. non-transitory
media, and computer-readable transmission media.
[0380] The instructions stored in memory 41 can be implemented as
software and/or firmware to program one or more processors to carry
out the actions described above. In some embodiments of the
invention, such software or firmware may be initially provided to
the processing system 40 by downloading it from a remote system
through the computing system, e.g. via the network adapter 43.
[0381] The various embodiments of the invention introduced herein
can be implemented by, for example, programmable circuitry, e.g.
one or more microprocessors, programmed with software and/or
firmware, entirely in special-purpose hardwired, i.e.
non-programmable, circuitry, or in a combination of such forms.
Special-purpose hardwired circuitry may be in the form of, for
example, one or more ASICs, PLDs, FPGAs, etc.
[0382] Although the invention is described herein with reference to
the preferred embodiment, one skilled in the art will readily
appreciate that other applications may be substituted for those set
forth herein without departing from the spirit and scope of the
present invention.
[0383] For example, embodiments of the invention apply rules to
identify the operational status of emergency equipment based on
identifying parameters, including most recent successful
maintenance inspection, most recent confirmation of GPS location,
expiration date of AED pads, expiration date of AED batteries,
other expiration dates checked in case of other equipment. See U.S.
provisional patent application Ser. No. 61/892,836, filed Oct. 18,
2013, which application is incorporated herein in its entirety by
this reference thereto.
[0384] Accordingly, the invention should only be limited by the
Claims included below.
* * * * *