U.S. patent application number 14/809378 was filed with the patent office on 2016-01-28 for automated external defibrillator configuration.
This patent application is currently assigned to ZOLL MEDICAL CORPORATION. The applicant listed for this patent is Ziad F. Elghazzawi. Invention is credited to Ziad F. Elghazzawi.
Application Number | 20160023009 14/809378 |
Document ID | / |
Family ID | 49995584 |
Filed Date | 2016-01-28 |
United States Patent
Application |
20160023009 |
Kind Code |
A1 |
Elghazzawi; Ziad F. |
January 28, 2016 |
AUTOMATED EXTERNAL DEFIBRILLATOR CONFIGURATION
Abstract
Systems and techniques for configuring an Automated External
Defibrillators are described herein.
Inventors: |
Elghazzawi; Ziad F.;
(Newton, MA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Elghazzawi; Ziad F. |
Newton |
MA |
US |
|
|
Assignee: |
ZOLL MEDICAL CORPORATION
Chelmsford
MA
|
Family ID: |
49995584 |
Appl. No.: |
14/809378 |
Filed: |
July 27, 2015 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
13558697 |
Jul 26, 2012 |
9119971 |
|
|
14809378 |
|
|
|
|
Current U.S.
Class: |
607/5 |
Current CPC
Class: |
A61N 1/3925 20130101;
A61N 1/3993 20130101; A61N 1/3904 20170801 |
International
Class: |
A61N 1/39 20060101
A61N001/39 |
Claims
1. A system comprising: a protocol database that includes at least
one protocol; and a computer configured to: receive from a
requestor a request to configure an external defibrillator;
identify, based on the request, one or more protocols from the
protocol database to which the requestor is permitted access;
receive from the requestor an identification of a selected protocol
from among the one or more protocols; and automatically configure
the external defibrillator according to the selected protocol.
2. The system of claim 1, wherein the computer is further
configured to: receive an update to the selected protocol; and
automatically reconfigure the external defibrillator according to
the selected protocol as updated.
3. The system of claim 1, wherein the computer is further
configured to automatically configure the external defibrillator
according to the selected protocol without manual reprogramming of
the external defibrillator.
4. The system of claim 2, wherein the computer is further
configured to update the selected protocol in the protocol
database.
5. The system of claim 2, wherein the requestor is a first
requestor, and wherein the computer is further configured to
receive the update from a second requestor.
6. The system of claim 1, the computer further configured to:
receive from a requestor, with one or more processors, a new
protocol for configuring the external defibrillator; and add the
new protocol to the protocol database.
7. The system of claim 6, wherein the new protocol indicates one or
more privacy settings.
8. The system of claim 7, wherein the requestor is a first
requestor and the request is a first request and the external
defibrillator is a first external defibrillator, the computer
further configured to: receive from a second requestor, with the
one or more processors, a second request to configure a second
external defibrillator; determine whether the second requestor has
access to the new protocol based on the one or more privacy
settings; and based on a determination that the second requestor
has access to the new protocol, include the new protocol in one or
more protocols from the protocol database to which the second
requestor is permitted access.
9. The system of claim 8, the computer further configured to
automatically configure, with the one or more processors, the
second external defibrillator according to the new protocol.
10. The system of claim 1, wherein the external defibrillator is an
automatic external defibrillator.
11. The system of claim 1, wherein the one or more protocols
include settings that affect operation of the external
defibrillator.
12. The system of claim 11, wherein the one or more protocols
include settings that affect clinical operation of the external
defibrillator.
13. The system of claim 12, wherein the one or more protocols
include settings that affect one or a combination of language, CPR
rate, CPR depth, shock voltage, shock waveform, and ECG analysis
protocol of the external defibrillator.
14. A method for configuring an external defibrillator, the method
comprising: receiving from a requestor, with one or more
processors, a request to configure an external defibrillator;
identifying, based on the request, one or more protocols from a
protocol database to which the requestor is permitted access, the
protocol database having at least one protocol; receiving from the
requestor an identification of a selected protocol from among the
one or more protocols; and automatically configuring the external
defibrillator according to the selected protocol.
15. The method of claim 14, further comprising: receiving, with the
one or more processors, an update to the selected protocol; and
automatically reconfiguring, with the one or more processors, the
external defibrillator according to the selected protocol as
updated.
16. The method of claim 14, further comprising: receiving from a
requestor, with one or more processors, a new protocol for
configuring the external defibrillator; and adding the new protocol
to the protocol database.
17. The method of claim 14, wherein automatically configuring the
external defibrillator according to the selected protocol does not
require manual reprogramming of the external defibrillator.
18. A computer program product comprising instructions to cause a
processor to: receive from a requestor a request to configure an
external defibrillator; identify, based on the request, one or more
protocols from a protocol database to which the requestor is
permitted access; receive from the requestor an identification of a
selected protocol from among the one or more protocols; and
automatically configure the external defibrillator according to the
selected protocol.
19. The computer program product of claim 18, further comprising
instructions to cause the processor to: receive an update to the
selected protocol; and automatically reconfigure the external
defibrillator according to the selected protocol as updated.
20. The computer program product of claim 18, further comprising
instructions to cause the processor to automatically configure the
external defibrillator according to the selected protocol without
manual reprogramming of the external defibrillator.
Description
CLAIM OF PRIORITY
[0001] This application is a continuation of and claims priority
under 35 USC 120 to U.S. Ser. No. 13/558,697, filed Jul. 26, 2012,
the entire contents of which are hereby incorporated by
reference.
TECHNICAL FIELD
[0002] This document relates to systems and techniques for
configuring an Automated External Defibrillator (AED).
BACKGROUND
[0003] Sudden cardiac arrest (colloquially "heart attack") is a
regular killer. The best treatment for cardiac arrest is quick and
competent chest compressions to keep blood flowing through a
subject's heart. Generally, every minute of delay in treating a
cardiac arrest subject lowers the chance of survival by about ten
percent. As a result, the ability to provide CPR in a competent
manner can be a very important personal skill, and is particularly
important for professional healthcare workers such as emergency
medical technicians (EMTs).
[0004] Various CPR feedback devices are available that indicate to
a rescuer whether they are performing CPR chest compressions at an
appropriate rate and an appropriate depth of compression, such as
dictated by American Heart Association (AHA) guidelines.
SUMMARY
[0005] In an embodiment, a method for configuring an automated
external defibrillator includes sending, to a remote database that
includes records associated with automated external defibrillator
protocols used to configure automated external defibrillators, a
request for available protocols for configuring the automated
external defibrillator. The method also includes receiving
information about one or more available protocols and sending, to
the remote database, a request to download a particular one of the
available protocols. The method also includes receiving, from the
remote database, configuration io information to automatically
configure the automated external defibrillator based on the
selected protocol.
[0006] In an embodiment, a method includes receiving configuration
information associated with an automated external defibrillator
protocol from a first automated external defibrillator and storing
the protocol and the associated configuration information in an
automated external defibrillator protocol database. The method also
includes downloading the protocol and configuration information to
a second automated external defibrillator that is different from
the first automated external defibrillator.
[0007] In an embodiment, a system includes a protocol database
stored in a memory, the protocol database including multiple
protocol records each of which includes multiple configurations for
an automated external defibrillator. The system also includes a
computing device configured to receive configuration information
associated with an automated external defibrillator protocol from a
first automated external defibrillator, store the protocol and the
associated configuration information in the protocol database, and
download the protocol to a second automated external defibrillator
that is different from the first automated external
defibrillator.
[0008] In an embodiment, a defibrillator includes a memory
configured to store a protocol comprising multiple configurations.
The defibrillator also includes a computing device configured to
send, to a remote database that includes records associated with
automated external defibrillator protocols, a request for available
protocols for configuring the automated external defibrillator,
receive information about one or more available protocols, send, to
the remote database, a request to io download a particular one of
the available protocols, receive from the remote database,
configuration information to automatically configure the automated
external defibrillator based on the selected protocol, store the
received protocol in the memory, and configure the automated
external defibrillator to operate according to the protocol stored
in the memory.
[0009] The details of one or more embodiments are set forth in the
accompanying drawings and the description below. Other features and
advantages will be apparent from the description and drawings, and
from the claims.
DESCRIPTION OF DRAWINGS
[0010] FIG. 1 shows a system for responding to an emergency medical
condition according to an example embodiment of the invention.
[0011] FIG. 2A shows a system for configuring an AED according to
an example embodiment of the invention.
[0012] FIGS. 2B and 2C show exemplary database records and
configuration entries, respectively.
[0013] FIG. 3A shows an AED including a display screen according to
an example embodiment of the invention.
[0014] FIGS. 3B and 3C are screen shots of AED configuration
screens according to an example embodiment of the invention.
[0015] FIG. 4A is a multi-entity flow diagram of a process for
uploading and storing AED protocols according to an example
embodiment of the invention.
[0016] FIG. 4B is a multi-entity flow diagram of a process for
downloading AED io protocols according to an example embodiment of
the invention.
DETAILED DESCRIPTION
[0017] This document describes systems and techniques that may be
used to configure an AED. The AED is configured according to a
protocol that outlines various configurations for the AED and
causes the AED to function in a desired manner. As used herein a
protocol provides guidelines on how the AED should operate and can
include protocol information that provides configurations/settings
for the AED such that the AED will perform and operate in a manner
that conforms to the set of guidelines on how to operate the AED.
For example, one portion of a protocol used by the AED can include
a CPR protocol which could include protocol information and
configurations to set a desired compression depth, compression
rate, ventilation rate and volume, and other parameters which
outline how the CPR is optimally performed. These configurations
will be used to analyze CPR performance and provide feedback to the
user. A protocol for the AED could additionally include guidelines
regarding when and how to administer a defibrillation shock. For
example, the protocol could include algorithms used in analyzing
data collected from a subject such as ECG waveforms or other
monitored physical parameters, shock voltages, waveforms for the
defibrillation energy, timing for defibrillation, and the like.
Many of the features of the protocol are stored as configurations
on an AED. For example, a protocol could outline a shock voltage
and this shock voltage could be stored as a configuration on the
AED. Other configurations which are associated with a protocol can
include configurations for the AED which do not directly relate to
treatment guidelines on which the protocol is based. For example,
the language in which prompts are provided to the user is not
treatment guideline specific but is still a configuration stored on
the AED. Protocol information, including stored AED configurations,
is provided in a centrally accessible database. AED owners or
administrators can store protocols in the database (e.g., by
uploading the configurations from a manually configured AED and/or
uploading a file with the configurations), and other AED owners or
administrators can download the protocols to configure different
AEDs. Thus, AED owners can share protocols and their associated
configurations with one another.
[0018] In certain implementations, the systems and techniques
discussed here may provide one or more advantages. For example, by
providing an AED owner with a set of available protocols (which
include the configurations for operation of the AED), the AED owner
is able to select appropriate settings without requiring the owner
to manually program the AED. Additionally, once an AED owner
selects a particular protocol and downloads the protocol to the
AED, updates to the configurations of the AED based on changes to
the treatment guidelines on which the protocol is based can be
pushed (e.g., automatically sent) to the AED. For example, when the
selected protocol is modified, the modifications can be pushed to
the AED. As such, the AED owner does not have to keep track of
advances in treatment but rather any changes to the treatment
guidelines on which the protocol is based can be automatically sent
to the AED to update the AED's configurations.
[0019] This detailed description discusses examples of configuring
an AED, according to at least one protocol. Protocol information,
including stored AED configurations, is provided in a centrally
accessible database. AED owners can io store protocols in the
database (e.g., by uploading the configurations from a manually
configured AED and/or uploading a file with the configurations),
and other AED owners can download the protocols to configure
different AEDs. Thus, AED owners can share protocols and their
associated configurations with one another.
[0020] For example, if a company owns five AEDs and want each of
the AEDs to function in the same manner, and owner of the five AEDs
can configure a first one of the AEDs manually to form a protocol
for operation of the AED. The owner can then upload the newly
formed protocol, including the manual configurations, as a new
protocol which is stored in the central database. Because the
protocol is then centrally accessible, the owner can download the
protocol on to the remaining AEDs, such that the AEDs all operate
using the same protocol.
[0021] FIG. 1 shows a system 100 for responding to an emergency
medical condition of a subject 102. In general, system 100 includes
various portable devices for monitoring on-site care given to a
subject 102 of an emergency situation. The rescuer 114 in this
example is interacting with a computing device in the form of a
laptop computer 116 that includes a graphical display by which to
report information to the rescuer 114, and may have an input
mechanism such as a keyboard or a touchscreen by which the rescuer
114 may enter data into the system 100. The laptop computer116 may
also include a wireless transceiver for communicating with a
wireless network, such as a 3G or 4G chipset that permits long
distance communication over cellular data networks, and further
through the internet.
[0022] Separately, a portable defibrillator 112 is shown in a
deployed state and io is connected to the subject 102. In addition
to providing defibrillation, the defibrillator 112 may serve as a
subject monitor via a variety of sensors or sensor packages. For
example, as shown here, electrodes 108 connected to the
defibrillator 112 have been applied to the subject 102 so that
electrical shocking pulses may be provided to the electrodes in an
effort to defibrillate the subject 102, and electrocardiogram (ECG)
signals may be read from the subject 102. Further examples of use
of the portable defibrillator are described, for example, in U.S.
Ser. No. 13/398,280 filed on Feb. 16, 2012 and entitled
"Coordinated Resuscitation Perfusion Support", the contents of
which are hereby incorporated by reference. The defibrillator
operates according to a protocol that includes set of
configurations stored on the defibrillator.
[0023] The defibrillator 112 may include an accelerometer assembly
110 configured to identify a vertical displacement caused by CPR
compressions (e.g., to compute the displacement of the subject's
breastbone for comparison to American Heart Association (AHA)
guidelines). In response to receiving such information from the
accelerometer assembly 112, the defibrillator 112 can provide
feedback to a rescuer, for example, the defibrillator 112 may
generate a metronome to pace such a user in providing chest
compressions. In addition, or alternatively, the defibrillator 112
may provide verbal instructions to the rescuer, such as by telling
the rescuer that they are providing compressions too quickly or too
slowly, or are pushing too hard or too soft, so as to encourage the
rescuer to change their technique to bring it more in line with
proper treatment guidelines--where the proper treatment guidelines
may be any protocol stored on the AED and need not be a protocol
based on standard, published treatment guidelines. In addition,
similar feedback may be provided visually on a screen of the
defibrillator, such as by showing a bar graph or number that
indicates depth and another that indicates rate, with appropriate
mechanisms to indicate whether the depth and rate or adequate, too
low, or too high. Examples of such feedback are described, for
example, in U.S. Ser. No. 13/025,348, filed on Feb. 11, 2011 and
entitled "Defibrillator Display", the contents of which are hereby
incorporated by reference.
[0024] The defibrillator can additionally be provided with a
ventilation bag 104 that includes an airflow sensor 106. The
airflow sensor 106 may be configured to monitor the flow of air
into and out of the subject's mouth, so as to identify a rate at
which ventilation is occurring with the victim. In addition, in
certain implementations, the airflow sensor 106 may be configured
to monitor a volume of airflow into and out of the subject 102.
This information can be used to provide feedback to the rescuer
about ventilation, for example, as described in U.S. Ser. No.
13/081,217 filed on Apr. 6, 2011 and entitled "Wireless Ventilation
Reporting", the contents of which are hereby incorporated by
reference. The feedback provided to the rescuer is based on the
protocol stored on the defibrillator.
[0025] The defibrillator 112 may communicate through a short range
wireless data connection with the laptop computer 116 to provide to
the laptop computer 116 status information, such as information
received through the electrode assembly 108, including ECG
information for the subject 102. Also, the defibrillator 112 can
send information about the performance of chest compressions, such
as depth and rate information for the chest compressions.
[0026] Where described herein, the processing and display of data
may occur on the defibrillator 112, the laptop computer 116, or on
both. For example, the defibrillator 112 may include a display that
matches that of the laptop computer 116, and the two may thus show
matching data. In contrast, the defibrillator 112 may have a more
limited display than does the laptop computer 116, and might show
only basic information about the technician's performance, while
the laptop computer 116 may show more complete information such as
secondary historic information. Also, the processing of primary
information to obtain secondary information may be performed by the
defibrillator 112, the laptop computer 116, or a combination of the
two, and the two devices may communicate back and forth in various
manners to provide to each other information they have received or
processed, or to relay commands provided to them by the rescuer
114.
[0027] A central server system 120 may communicate with the laptop
computer 116, the defibrillator 112, or other devices at the rescue
scene over a wireless network and a network 118, which may include
portions of the Internet (where data may be appropriately encrypted
to protect privacy).
[0028] The defibrillator 112 and associated devices can function
based on a protocol stored on the system. The configurations
included in the protocol can be based on treatment guidelines, for
example, based on the American Heart Association Guidelines for
Cardiopulmonary Resuscitation (AHA CPR). The defibrillator can
initially be installed to operate based on a standard protocol such
as the AHA protocol, however, a user or owner of the defibrillator
could override the initial configurations to have the device
operate using a different protocol or to io update the device as
the protocols change. In some examples, the new or updated protocol
could be downloaded from a central computer server to the
defibrillation device. Such an approach may have the benefit of
being able to easily update and modify settings/configurations of
the AED to implement the desired protocol.
[0029] The computing device may then receive information about the
performance by the rescuers, such as from wired or wireless
transmitters on a defibrillator, an assisted ventilation unit, or
other medical device (e.g., blood pressure reader). The computing
device may provide feedback or coaching when the performance falls
out of line with a defined protocol stored on the AED, or may
provide feedback to maintain the performance in line with the
protocol. In providing the feedback, the computing device or the
defibrillator may generate a number of derived parameters from
measured parameters of the subject, and both the measured
parameters and the more comprehensive derived parameters may be
reported visually or audibly by the computing device, the
defibrillator/monitor, or both.
[0030] FIG. 2A is a diagram of multiple defibrillation devices
200a, 200b, and 200c connected to a central server 206 that
includes a protocol database 208. The protocol database can include
information about the protocol such as the AED configurations used
to operate the defibrillation devices 200a, 200b, and 200c. The
database 208 provides centralized access to the multiple, different
protocols (including the configuration information used to set the
defibrillator configurations) by various AEDs communicatively
connected to the database by a wired or wireless connection. For
example, a particular one of the defibrillation devices can modify
the protocol stored on the AED by requesting to download an updated
or a different protocol from the protocol database 208 (e.g., the
AED can download a protocol with different configuration settings
that is based on the same or a different set of treatment
guidelines). Additionally, protocols can be uploaded to the
protocol database 208 so that the protocols will be accessible for
download onto other AEDs. For example, an owner or user of the
defibrillation device can manually update the protocol used to
operate the AED (e.g., manually change one or more of the device
configurations) and then store the configurations associated with
the updated protocol in the protocol database 208. By storing the
protocol including the configuration information in the protocol
database 208, this set of configurations will be available to be
downloaded onto another, different defibrillation device such that
the same protocol (e.g., the updated protocol) can be used to
operate the other defibrillation device without having to manually
configure the device.
[0031] The communication between the defibrillation devices 200a,
200b, and 200c and the central server 206 can occur over a wireless
network such as a cellular network. For example, the defibrillation
devices 200a, 200b, and 200c can include a wireless transceiver for
communicating with a wireless network, such as a 3G or 4G chipset
that permits long distance communication over cellular data
networks, and further through the internet. In additional examples,
a tablet, laptop computer, or other computing device associated
with the defibrillation device can include the wireless transceiver
for communicating with the wireless network and the defibrillation
device can include a short range communication chip to communicate
with the tablet, laptop computer, or other computing device. In
such an arrangement, the tablet, laptop computer, or other
computing device communicates with both the central server 206 and
with the defibrillation device.
[0032] As shown in FIG. 2B, the protocol database 208 stored in the
memory associated with the central server 206 includes multiple
records 210a-d each of which is associated with a particular stored
protocol. Each of these records includes multiple configurations
212. These configurations are used to configure a defibrillation
device. For example, as shown in FIG. 2C, each stored protocol can
include settings for items such as language 214a, CPR rate 214b,
CPR depth 214c, shock voltage 214d, shock wave form 214e, and ECG
analysis protocol 214f.
[0033] FIG. 3A shows an exemplary defibrillation device 300 that
includes a display 302 showing the current settings for the
defibrillation device. During use, or during an initial setup, a
user may desire to change the configurations for the defibrillation
device. In order to modify the configurations, the user can
manually update the configurations by selecting button 310, or
automatically update the settings by downloading a set of
configurations (e.g., a different protocol) from the central
database by selecting button 312. When the user is satisfied with
the configuration, the user can accept the configurations by
selecting button 308.
[0034] If the user selects to manually update the configurations
(e.g., by selecting the manual update option by pressing button
310), the defibrillation device displays the current configurations
and options for amending those configurations. For example, FIG.
3B, shows an exemplary user interface for manually modifying the
configurations of the defibrillation device. By selecting a
drop-down menu associated with a particular configuration, the user
can modify the configuration. In the exemplary display of FIG. 3B,
the user has selected to modify the language used on the display
and for the audio prompts. In order to change the language from the
currently selected language of English, the user selects the
drop-down menu 316 and then clicks on a particular one of the
available languages 318a-d. Thus, the user can modify the
configurations used by the defibrillator by manually changing one
or more of the configurations. The amended configurations can form
a new or updated protocol that includes any changes to the
configurations of the original protocol. The new or updated
protocol can be stored on the defibrillation device and optionally
uploaded to the central database 208.
[0035] If the user selects to automatically update the
configurations (e.g., by selecting the automatic update option by
pressing button 312), the defibrillation device displays a listing
of available protocols as shown in the user interface 320 shown in
FIG. 3C. The user interface 320 displays a list of available
protocols (e.g., protocols 322a-c). A user can select to see
additional details about a particular protocol by selecting the
associated view details button (e.g., buttons 324a-c). For example,
to view the details (e.g., the particular configuration settings)
of the AHA guideline protocol 322a the user would select view
details button 324a.
[0036] The list of protocols that are available can be filtered to
assist a user in identifying a particular protocol. In some
examples, the set of protocols is automatically filtered based on
the model of the AED. And some additional examples, a user can
filter the list of available protocols to narrow the number of
protocols to select from based on one or more features of interest
to the user. For example, key features of protocols (such as key
configurations) can be displayed and the user can select from
drop-down menus to filter the available protocols based on the
setting for a particular configuration. For example, as shown in
FIG. 3C, the user can select to filter the results based on the
language (e.g., using the drop down menu in filter box 325) such
that only protocols in the selected language will be displayed.
Other key features, such as whether the CPR protocol relies on
hands only CPR, the CPR rate, the analysis protocols, or the shock
voltage could be used to filter the results. In some examples, the
results could be filtered based on multiple, different
features.
[0037] In some examples, protocols stored in the protocol database
can have associated skill level indicators and the list of
available protocols can be filtered based on an anticipated skill
level of the rescuer. In some additional examples, a combination of
language and skill level can be used to filter the list of
available protocols.
[0038] FIG. 4A shows a multi-entity flow diagram of a process for
storing AED protocols in a centralized database. The process begins
with a user setting the configurations of an AED manually (402).
For example, the user can progress through a set of predefined
screens to select different configurations. Values for these
configurations can be based on existing protocols or can be set to
a desired set of configurations that is different from the
configurations of an existing protocol. After manual configuration
of the AED is complete, the user uploads the protocol, including
all of the associated configurations to a remote configuration
database (404). For example, the user can select an `upload
configuration` or `export io configuration` option and the
configurations for the new protocol can be wirelessly uploaded to
the remote database using a cellular connection.
[0039] The remote server receives the protocol information,
including the configurations from the AED and stores the protocol
information in the protocol database as a new entry (406). The user
can select a name or identifier to associate with the uploaded
protocol. Associating a user-selected name can enable the user or
another user to later locate the protocol and download the protocol
to additional AEDs.
[0040] After storing the configurations for the uploaded protocol,
the central server sends a request for verification of the
configurations for the protocol and a request for information about
privacy settings to associate with the protocol (408). The AED
receives the request (410), and provides any user-input updates
and/or verification of the configurations and the requested privacy
settings to the central server (412). The central server receives
the user input response and, if needed, updates the stored
configurations for the protocol (414). The central server also sets
the privacy settings for the protocol (including any downloading
restrictions) based on the privacy settings from the AED owner
(416). For example, and AED owner may restrict download of their
protocols to others within the same Corporation, others having the
same hospital affiliation, other AEDs maintained by the same AED
servicing group, etc.
[0041] FIG. 4B is a multi-entity flow diagram of a process for
downloading a protocol to an AED and configuring the AED based on
the configurations stored in the protocol. The process begins with
an AED sending a request to update/change io the protocol for the
AED (430). The central server that includes a protocol database
receives the request (432) and determines protocols that are
available for the user to download based on ownership and/or a
model of the AED (434). The central server provides a list of the
available protocols to the AED and the list of available protocols
is displayed on the AED, or an associated device (436). The AED
receives a user selection of one of the protocols from the list of
protocols (438). This selection is sent to the central database and
the central database receives an indication of the selected
protocol (440). The central database then sends configurations
associated with the protocol to the AED which will automatically
configure the AED according to the selected protocol (442). The AED
downloads the protocol, including the configurations, and stores
the received configurations as the current settings for the AED
(444). Thus, a user is able to select a protocol from a list of
protocols and have the settings for the AED automatically
configured according to the configurations in the protocol by
downloading the desired protocol.
[0042] In some embodiments, updates to a protocol (e.g., changes to
one or more configurations of the protocol) can be automatically
pushed to AEDs operating based on the protocol. For example, if an
owner of an AED downloads the AHA protocol and the AHA protocol is
later updated (e.g., one or more of the configurations is changed)
then the updates to the configurations can be automatically sent to
the AED. As such, the initial protocol is downloaded by the user
(e.g., pulled from the database at the central server) and the
updates are automatically sent (e.g., pushed to the AED from the
central server) to the AED.
[0043] A number of embodiments have been described. Nevertheless,
it will be understood that various modifications may be made
without departing from the spirit and scope of the invention. For
example, much of this document has been described with respect to
ICU monitoring with attending physicians, but other forms of
patient monitoring and reporting may also be addressed.
[0044] In addition, the logic flows depicted in the figures do not
require the particular order shown, or sequential order, to achieve
desirable results. In addition, other steps may be provided, or
steps may be eliminated, from the described flows, and other
components may be added to, or removed from, the described systems.
Accordingly, other embodiments are within the scope of the
following claims.
* * * * *