Source: https://patents.google.com/patent/US9990829B2/en
Timestamp: 2019-05-23 13:48:34
Document Index: 211071825

Matched Legal Cases: ['§ 120', '§ 120', '§ 120', '§ 119', '§ 119', 'art 2', 'art 2']

US9990829B2 - System and method for adapting alarms in a wearable medical device - Google Patents
System and method for adapting alarms in a wearable medical device Download PDF
US9990829B2
US9990829B2 US15/483,203 US201715483203A US9990829B2 US 9990829 B2 US9990829 B2 US 9990829B2 US 201715483203 A US201715483203 A US 201715483203A US 9990829 B2 US9990829 B2 US 9990829B2
ambulatory medical
US15/483,203
US20170278370A1 (en
John G. Clark
2011-03-25 Priority to US201161467663P priority Critical
2011-10-03 Priority to US201161542749P priority
2012-03-23 Priority to US13/428,703 priority patent/US9135398B2/en
2015-05-05 Priority to US14/704,033 priority patent/US9378637B2/en
2016-05-19 Priority to US15/159,557 priority patent/US9659475B2/en
2017-04-10 Priority to US15/483,203 priority patent/US9990829B2/en
2017-04-10 Application filed by ZOLL Medical Corp filed Critical ZOLL Medical Corp
2017-09-21 Assigned to ZOLL MEDICAL CORPORATION reassignment ZOLL MEDICAL CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CLARK, JOHN G., KAIB, THOMAS E., VOLPE, SHANE S.
2017-09-28 Publication of US20170278370A1 publication Critical patent/US20170278370A1/en
2018-04-27 Priority claimed from US15/965,287 external-priority patent/US10269227B2/en
2018-06-05 Publication of US9990829B2 publication Critical patent/US9990829B2/en
2032-03-23 Anticipated expiration legal-status Critical
According to another example, a wearable medical device controller is provided. The device controller includes a memory and a processor coupled to the memory. The processor is configured to determine a correlation between a phenomenon identifiable by the wearable medical device controller and at least one response pattern associated with a patient and store, responsive to detecting the correlation, an adaptation path to address the at least one response pattern, the adaptation path specifying an adaptation of at least one characteristic of an alarm. The at least one response pattern may include a plurality of response patterns and the adaptation path may reflect adaptations made to address at least some of the plurality of response patterns.
This application claims benefit under 35 U.S.C. § 120 as a continuation of U.S. patent application Ser. No. 15/159,557, titled “SYSTEM AND METHOD FOR ADAPTING ALARMS IN A WEARABLE MEDICAL DEVICE”, filed on May 19, 2016. U.S. patent application Ser. No. 15/159,557 claims benefit under 35 U.S.C. § 120 as a continuation of U.S. patent application Ser. No. 14/704,033, titled “SYSTEM AND METHOD FOR ADAPTING ALARMS IN A WEARABLE MEDICAL DEVICE,” filed on May 5, 2015. U.S. patent application Ser. No. 14/704,033 claims benefit under 35 U.S.C. § 120 as a continuation of U.S. patent application Ser. No. 13/428,703, titled “SYSTEM AND METHOD FOR ADAPTING ALARMS IN A WEARABLE MEDICAL DEVICE,” filed on Mar. 23, 2012. U.S. patent application Ser. No. 13/428,703 claims benefit under 35 U.S.C. § 119(e) to U.S. Provisional Application Ser. No. 61/467,663, titled “SYSTEM AND METHOD FOR ADAPTING ALARMS IN A WEARABLE MEDICAL DEVICE,” filed on Mar. 25, 2011. U.S. patent application Ser. No. 13/428,703 also claims benefit under 35 U.S.C. § 119(e) to U.S. Provisional Application Ser. No. 61/542,749, titled “SYSTEM AND METHOD FOR ADAPTING ALARMS IN A WEARABLE MEDICAL DEVICE,” filed on Oct. 3, 2011. Each of these related applications is hereby incorporated herein by reference in its entirety.
Aspects of the present invention relate to medical devices, and more particularly to apparatus and methods for adapting alarms in medical devices.
Some wearable medical devices notify patients wearing the medical device of events of interest to the patient. In certain situations, wearable medical devices receive responses to these notifications from the patient. For instance, a wearable defibrillator worn by an ambulatory patient generates an alarm if the patient's electrocardiogram (ECG) signal indicates a cardiac abnormality. Where the ECG signal indicates that the cardiac abnormality is treatable via a therapeutic shock, the wearable defibrillator must receive a response to this notification if the patient wishes to avoid the administration of an unnecessary therapeutic shock.
In situations where the cause of a notification is not as pressing, a wearable medical device may repeatedly notify a patient of the event of interest. For example, if a battery installed in the wearable medical device is running low on power, the wearable medical device may notify the patient. After a period of time, if the wearable medical device continues to detect that the battery has a low power state, the wearable medical device may reissue the previous notification. However, in the case of a critical care medical device, such as the LifeVest® Wearable Cardioverter Defibrillator available from Zoll Medical Corporation of Chelmsford, Mass., lack of a responsive action by the patient may result in the wearable defibrillator becoming inoperative due to lack of battery power.
Examples disclosed herein adapt the characteristics of an alarm issued by a wearable medical device to increase the efficacy of a wearable medical device while maintaining or enhancing the usage experience of patients wearing the medical device. For instance, some adaptations presented herein increase the probability that patients will respond to the alarm in a suitable manner. Other adaptations tailor alarms to fit the traits and preferences of particular patients. Thus, various examples address situations in which a patient does not hear an alarm, does not recognize the significance of an alarm or does not respond according to established timetables.
In one example, a method for adapting alarms issued by a wearable medical device is provided. The method includes acts of issuing a first instance of an alarm; determining that no predetermined response to the first instance of the alarm was received within a target response time; adapting, responsive to determining that no predetermined response was received within the target response time, at least one characteristic of the alarm according to an adaptation path associated with the alarm and issuing a second instance of the alarm, the second instance of the alarm having the at least one adapted characteristic.
In the method, the act of determining that the first instance of the alarm was not effective may include receiving no response within a target response time. In addition, the act of adapting the at least one characteristic of the alarm may include increasing the intensity of the alarm. Further, the act of adapting the at least one characteristic of the alarm may include changing the conduit of the alarm. The act of changing the conduit of the alarm may include transmitting the alarm to a personal electronic device. Moreover, the method may further operate using an alarm profile that indicates an alarm that is triggered upon occurrence of an event. Additionally, the method may further include acts of storing within the alarm profile, responsive to adapting the at least one characteristic of the alarm, an association between the alarm and the adaptation path; detecting an occurrence of the event; identifying, responsive to detecting the occurrence of the event, the association between the alarm and the adaptation path; adapting, responsive to identifying the association, at least one characteristic of the alarm according to the adaptation path and issuing a third instance of the alarm, the third instance of the alarm having the at least one adapted characteristic.
According to another example, a method for adapting alarms issued by a wearable medical device is provided. The method includes acts of receiving an alarm profile via an interface, the alarm profile indicating an alarm to be triggered upon occurrence of an event and including an association between an adaptation path and the alarm; detecting an occurrence of the event; identifying, responsive to detecting the occurrence of the event, the association between the adaptation path and the alarm; adapting, responsive to identifying the association, at least one characteristic of the alarm according to the adaptation path; and issuing an instance of the alarm having the at least one adapted characteristic.
According to another example, a wearable medical device controller is provided. The wearable medical device controller includes a memory storing alarm profile information and a processor coupled to the memory. The processor being configured to issue a first instance of an alarm, determine that no predetermined response to the first instance of the alarm was received within a target response time, adapt, responsive to determining that no predetermined response was received within the target response time, at least one characteristic of the alarm according to an adaptation path associated with the alarm and issue a second instance of the alarm, the second instance of the alarm having the at least one adapted characteristic. In addition, the processor may be configured to determine that the first instance of the alarm was not effective where the processor receives no response within a target response time.
According to another example, a method for adapting alarms issued by a wearable medical device is provided. The method includes acts of detecting an inhibiting factor associated with an alarm and adapting, responsive to detecting the inhibiting factor, at least one characteristic of the alarm according to an adaptation path.
According to another example, a method for adapting alarms issued by a wearable medical device is provided. The method includes acts of detecting a correlation between a value of an independent variable and an alarm response pattern associated with a patient, determining, after detecting the correlation, that the independent variable has the value and adapting, responsive to determining that the independent variable has the value, an alarm based on the alarm response pattern.
In the device controller, the processor may be further configured to detect the phenomenon and adapt, responsive to detecting the phenomenon, the at least one characteristic of the alarm according to the adaptation path. The processor may be configured to determine the correlation by determining a correlation between a value of an independent variable indicative of the phenomenon and the at least one response pattern. Adapting the at least one characteristic of the alarm may include increasing the intensity of the alarm. Adapting the at least one characteristic of the alarm may include changing the conduit of the alarm. Changing the conduit of the alarm may include transmitting the alarm to a personal electronic device. In some examples, the phenomenon may be an inhibiting factor.
In the device controller, the memory may store an alarm profile indicating that the alarm be triggered upon occurrence of an event. The alarm profile may include an association between the adaptation path and the alarm. The processor may be further configured to detect an occurrence of the event and issue a first instance of the alarm, the first instance having the at least one adapted characteristic. The adaptation path may specify a plurality of adaptations and the processor is further configured to determine that no predetermined response to the first instance of the alarm was received within a target response time; adapt, responsive to determining that no predetermined response was received within the target response time, a characteristic of the alarm according to an adaptation from the plurality of adaptations and issue a second instance of the alarm, the second instance of the alarm having the adapted characteristic.
The device controller may further comprise an interface in data communication with the processor. The processor may be further configured to receive the alarm profile via the interface and store the alarm profile in the memory. The processor may be further configured to receive a new adaptation path via the interface and store the new adaptation path in the alarm profile.
According to another example, a wearable medical device controller is provided. The device controller includes a memory and a processor coupled to the memory. The memory stores an alarm profile indicating that an alarm be triggered upon occurrence of an event and includes an association between an adaptation path and the alarm. The processor is configured to detect an occurrence of the event; issue a first instance of the alarm; determine that no predetermined response to the first instance of the alarm was received within a target response time; adapt, responsive to determining that no predetermined response was received within the target response time, at least one characteristic of the alarm according to the adaptation path; and issue a second instance of the alarm, the second instance of the alarm having the at least one adapted characteristic.
According to another example, a method for adapting alarms issued by a wearable medical device is provided. The method includes acts of determining, by the wearable medical device, a correlation between a phenomenon identifiable by the wearable medical device and at least one response pattern associated with a patient and storing, responsive to detecting the correlation, an adaptation path to address the at least one response pattern, the adaptation path specifying an adaptation of at least one characteristic of an alarm. The act of determining the correlation includes determining the correlation between the phenomenon and a plurality of response patterns and storing the adaptation path includes storing an adaptation path that reflects adjustments made to address at least some of the plurality of response patterns.
The method may further comprise acts of detecting the phenomenon and adapting, responsive to detecting the phenomenon, the at least one characteristic of the alarm according to the adaptation path. In the method, the act of determining the correlation may include an act of determining a correlation between a value of an independent variable indicative of the phenomenon and the at least one response pattern. The act of adapting the at least one characteristic of the alarm may include ac act of increasing the intensity of the alarm. The act of adapting the at least one characteristic of the alarm may include changing the conduit of the alarm. The act of changing the conduit of the alarm may include an act of transmitting the alarm to a personal electronic device.
The method may further comprise act of detecting an occurrence of an event and issuing a first instance of the alarm, the first instance having the adaptation of the at least one characteristic of the alarm. The adaptation path may specify a plurality of adaptations and the method further comprises acts of determining that no predetermined response to the first instance of the alarm was received within a target response time; adapting, responsive to determining that no predetermined response was received within the target response time, a characteristic of the alarm according to an adaptation from the plurality of adaptations and issuing a second instance of the alarm, the second instance of the alarm having the adapted characteristic.
Still other aspects, examples, and advantages of these exemplary aspects and examples, are discussed in detail below. Moreover, it is to be understood that both the foregoing information and the following detailed description are merely illustrative examples of various aspects, and are intended to provide an overview or framework for understanding the nature and character of the claimed subject matter. References to “an example,” “some examples,” “an alternate example,” “various examples,” “one example,” “at least one example,” “this and other examples” or the like are not necessarily mutually exclusive and are intended to indicate that a particular feature, structure, or characteristic described in connection with the example may be included in that example and other examples. The appearances of such terms herein are not necessarily all referring to the same example.
Furthermore, in the event of inconsistent usages of terms between this document and documents incorporated herein by reference, the term usage in the incorporated references is supplementary to that of this document; for irreconcilable inconsistencies, the term usage in this document controls. In addition, the accompanying drawings are included to provide illustration and a further understanding of the various aspects and examples, and are incorporated in and constitute a part of this specification. The drawings, together with the remainder of the specification, serve to explain principles and operations of the described and claimed aspects and examples.
The accompanying drawings are not intended to be drawn to scale. In the drawings, components that are identical or nearly identical may be represented by a like numeral. For purposes of clarity, not every component is labeled in every drawing. In the drawings:
FIG. 1 is a functional schematic of one example of a wearable medical device controller;
FIG. 2 is a flow diagram of one example of a process for adapting alarms issued by a medical device;
FIG. 3 is a flow diagram of one example of a process for configuring information within an alarm profile;
FIG. 4 is a flow diagram of one example of a process for monitoring events associated with a medical device; and
FIG. 5 is a flow diagram of one example of a process for producing alarms associated with a medical device.
Aspects and examples disclosed herein relate to apparatus and processes for adapting alarms issued by a wearable medical device. The examples disclosed herein are potentially applicable to a wide variety of wearable medical devices. In some examples, the wearable medical devices are configured in accord with the wearable medical devices described in co-pending application Ser. No. 13/109,382, entitled WEARABLE AMBULATORY MEDICAL DEVICE WITH MULTIPLE SENSING ELECTRODES, filed May 17, 2011, which is incorporated by reference herein in its entirety. In other examples, the wearable medical device is a monitoring device that does not conduct a therapy delivery method or include a therapy delivery apparatus. In each of these examples, a control unit of the wearable medical device includes a set of components configured to perform the adaptation processes described herein. This set of components may include hardware components or a combination of hardware and software components.
The examples of the methods and apparatuses discussed herein are not limited in application to the details of construction and the arrangement of components set forth in the following description or illustrated in the accompanying drawings. The methods and apparatuses are capable of implementation in other examples and of being practiced or of being carried out in various ways. Examples of specific implementations are provided herein for illustrative purposes only and are not intended to be limiting. In particular, acts, elements and features discussed in connection with any one or more examples are not intended to be excluded from a similar role in any other examples.
Also, the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. Any references to examples or elements or acts of the systems and methods herein referred to in the singular may also embrace examples including a plurality of these elements, and any references in plural to any example or element or act herein may also embrace examples including only a single element. References in the singular or plural form are not intended to limit the presently disclosed systems or methods, their components, acts, or elements. The use herein of “including,” “comprising,” “having,” “containing,” “involving,” and variations thereof is meant to encompass the items listed thereafter and equivalents thereof as well as additional items. References to “or” may be construed as inclusive so that any terms described using “or” may indicate any of a single, more than one, and all of the described terms.
Wearable Medical Device Controller
FIG. 1 illustrates a wearable medical device controller 100 that is configured to monitor a patient and the patient's environment for events of interest and to adapt notifications reporting these events. As shown in FIG. 1, the wearable medical device controller 100 includes a processor 118, a sensor interface 112, an alarm manager 114, a therapy delivery interface 102, data storage 104, a communication network interface 106, a user interface 108 and a battery 110. The data storage 104 includes alarm profile information 116. Further, in this illustrated example, the battery 110 is a rechargeable 3 cell 2200 mAh lithium ion battery pack that provides electrical power to the other device components with a minimum 24 hour runtime between charges.
According to the example illustrated in FIG. 1, the processor 118 is coupled to the sensor interface 112, the therapy delivery interface 102, the data storage 104, the network interface 106 and the user interface 108. The processor 118 performs a series of instructions that result in manipulated data which is stored in and retrieved from the data storage 104. According to a variety of examples, the processor 118 is a commercially available processor such as a processor manufactured by Texas Instruments, Intel, AMD, Sun, IBM, Motorola, Freescale and ARM Holdings. However, the processor 118 may be any type of processor, multiprocessor or controller, whether commercially available or specially manufactured. For instance, according to one example, the processor 118 may include a power conserving processor arrangement such as described in co-pending application Ser. No. 12/833,096, entitled SYSTEM AND METHOD FOR CONSERVING POWER IN A MEDICAL DEVICE, filed Jul. 9, 2010 (hereinafter the “'096 application”), which is incorporated by reference herein in its entirety. In another example, the processor 118 is an Intel® PXA270.
In addition, in several examples the processor 118 is configured to execute a conventional RTOS, such as RTLinux. In these examples, the RTOS may provide platform services to application software, such as some examples of the alarm manager 114 which is discussed further below. These platform services may include inter-process and network communication, file system management and standard database manipulation. However, one of many operating systems may be used, and examples are not limited to any particular operating system or operating system characteristic. For instance, in some examples, the general purpose processor 118 may be configured to execute a non-real time operating system, such as BSD or GNU/Linux.
The alarm manager 114 is configured to manage alarm profiles, such as the alarm profile information 116, and notify one or more intended recipients of events specified within the alarm profiles as being of interest to the intended recipients. These intended recipients may include external entities such as users (patients, physicians, and monitoring personnel) as well as computer systems (monitoring systems or emergency response systems). The alarm manager 114 is also configured to adapt notifications according to an adaptation path specified within the alarm profile information 116. Adaptation paths are discussed further below with reference to the alarm profile information 116.
The alarm manager 114 may be implemented using hardware or a combination of hardware and software. For instance, in one example, the alarm manager 114 is implemented as a software component that is stored within the data storage 112 and executed by the processor 118. In this example, the instructions included in the alarm manager 114 program the processor 118 to configure alarm profiles and notify intended recipients using the alarm profiles. In other examples, alarm manager 114 may be an application-specific integrated circuit (ASIC) that is coupled to the processor 118 and tailored to manage alarm profiles and notify intended recipients using alarms specified within the alarm profiles. Thus, examples of alarm manager 114 are not limited to a particular hardware or software implementation. Particular examples of the processes performed by the alarm manager 114 are discussed further below with reference to FIGS. 2-5 and the Example Alarm Adaptations section below.
In some examples, the components disclosed herein, such as the alarm manager 114, may read parameters that affect the functions performed by the components. These parameters may be physically stored in any form of suitable memory including volatile memory, such as RAM, or nonvolatile memory, such as a magnetic hard drive. In addition, the parameters may be logically stored in a proprietary data structure, such as a database or file defined by a user mode application, or in a commonly shared data structure, such as an application registry that is defined by an operating system. In addition, some examples provide for both system and user interfaces, as may be implemented using the user interface 108, that allow external entities to modify the parameters and thereby configure the behavior of the components.
For example, the alarm manager 114 includes an alarm mode parameter. The alarm mode parameter indicates a generalized set of preferences that the alarm manager 114 applies to triggered alarms. The alarm manager 114 may adjust any characteristics of an alarm depending on the particular alarm mode currently in effect. Example alarm modes include, but are not limited to, normal (no modification to alarm characteristics), silent (do not produce sensory output to one or more senses when reporting the alarm), loud (increase sensory output to one or more senses when reporting the alarm), vehicle (decrease sensory output and target response times, delay alarms with adaptation paths indicating to delay the alarm if the alarm mode parameter indicates vehicle mode, issue triggered alarms through an in-vehicle communications and entertainment system if available), walking (issue triggered alarms via an output embedded within an article of clothing, such as a foot buzzer), and personal electronic device (issue triggered alarms via a personal electronic device such as an earpiece, phone, tablet computing device, pen, personal entertainment device, sport equipment, personal digital assistant, etc. . . . ).
The data storage 104 includes a computer readable and writeable nonvolatile data storage medium configured to store non-transitory instructions and other data. In addition, the data storage 104 includes a processor memory that stores data during operation of the processor 118. In some examples, the processor memory includes a relatively high performance, volatile, random access memory such as dynamic random access memory (DRAM), static memory (SRAM) or synchronous DRAM. However, the processor memory may include any device for storing data, such as a non-volatile memory, with sufficient throughput and storage capacity to support the functions described herein. According to several examples, the processor 118 causes data to be read from the nonvolatile data storage medium into the processor memory prior to processing the data. In these examples, the processor 118 copies the data from the processor memory to the non-volatile storage medium after processing is complete. A variety of components may manage data movement between the non-volatile storage medium and the processor memory and examples are not limited to particular data management components. Further, examples are not limited to a particular memory, memory system or data storage system.
The instructions stored on the data storage 104 may include executable programs or other code that can be executed by the processor 118. The data storage 104 also may include information that is recorded, on or in, the medium, and this information may be processed by the processor 118 during execution of instructions. More specifically, the information may be stored in one or more data structures specifically configured to conserve storage space or increase data exchange performance. The instructions may be persistently stored as encoded signals, and the instructions may cause the processor 118 to perform the functions described herein. The medium may, for example, be optical disk, magnetic disk or flash memory, among others, and may be permanently affixed to, or removable from, the wearable medical device controller 100.
The alarm profile information 116 includes data used by the alarm manager 114 to notify intended recipients of events of interest. More particularly, according to the illustrated example, the alarm profile information 116 includes information that identifies events of interest, characteristics of one or more alarms used to report the identified events and one or more adaptation paths for each of the one or more alarms. Events of interest may include any event detectable by the wearable medical device controller 100. However, in broad terms, events of interest may be categorized as concerning the patient wearing the wearable medical device, such as an indication of a physiological abnormality in the patient, or concerning the wearable medical device itself, such as a component in need of service (for example, a low battery).
Common alarm characteristics include an alarm identifier, an intended recipient of the alarm, one or more potential responses, a conduit through which the alarm is provided, content for the alarm, an intensity with which the content is communicated, an issuance rate at which the content is communicated and a target response time. The conduits through which alarms may be issued include, among others, the user interface 108, the network interface 106 and the therapy delivery interface 102. Adaptation paths may specify initial characteristics of alarms and how the characteristics of the alarms are altered based on the currently selected alarm mode, the number of times the alarms have issued, the circumstances surrounding the intended recipients of any alarms and any responsive actions taken, or not taken, by the external entities. In general, the adaptations specified by adaptation paths involve actions such as increasing the intensity with which an alarm is communicated, altering the content or conduit of an alarm and increasing the issuance rate with which an alarm is communicated. Specific examples of adaptation paths that are specified with the alarm profile information 116 and that the alarm manager 114 is configured to conduct are discussed further below within the Example Alarm Adaptations section.
As illustrated in FIG. 1, the alarm manager 114 and the alarm profile information 116 are separate components. However, in other examples, the alarm manager 114 and the alarm profile information 116 may be combined into a single component or re-organized so that a portion of the data included in the alarm manager 114, such as executable code that causes the processor 118 to adapt a triggered alarm, resides in the alarm profile information 118, or vice versa. Such variations in these and the other components illustrated in FIG. 1 are intended to be within the scope of the examples disclosed herein.
The alarm profile information 116 may be stored in any logical construction capable of storing information on a computer readable medium including, among other structures, flat files, indexed files, hierarchical databases, relational databases or object oriented databases. In addition, various examples organize the alarm profile information 116 into particularized and, in some cases, unique structures to perform the functions disclosed herein. In these examples, the data structures are sized and arranged to store values for particular types of data.
As shown in FIG. 1, the wearable medical device controller 100 includes several system interface components 102, 106 and 112. Each of these system interface components is configured to exchange, i.e. send or receive, data with one or more specialized devices that may be located within the wearable medical device controller 100 or elsewhere. The components used by the interfaces 102, 106 and 112 may include hardware components, software components or a combination of both. In the instance of each interface, these components physically and logically couple the wearable medical device controller 100 to the specialized devices. This physical and logical coupling enables the wearable medical device controller 100 to both communicate with and, in some instances, control the operation of the specialized devices. These specialized devices may include physiological sensors, therapy delivery devices and computer networking devices.
According to various examples, the hardware and software components of the interfaces 102, 106 and 112 employ a variety of coupling and communication techniques. In some examples, the interfaces 102, 106 and 112 use leads, cables or other wired connectors as conduits to exchange data between the wearable medical device controller 100 and specialized devices. In other examples, the interfaces 102, 106 and 112 communicate with specialized devices using wireless technologies such as radio frequency or infrared technology. The software components included in the interfaces 102, 106 and 112 enable the processor 118 to communicate with specialized devices. These software components may include elements such as objects, executable code and populated data structures. Together, these software components provide software interfaces through which the processor 118 can exchange information with specialized devices. Moreover, in at least some examples where one or more specialized devices communicate using analog signals, the interfaces 102, 106 and 112 further include components configured to convert analog information into digital information, and vice versa, to enable the processor 118 to communicate with specialized devices.
As discussed above, the system interface components 102, 106 and 112 shown in the example of FIG. 1 support different types of specialized devices. For instance, the components of the sensor interface 112 couple the processor 118 to one or more physiological sensors such as a body temperature sensors, respiration monitors, and dry capacitive ECG electrodes, one or more environmental sensors such as atmospheric thermometers, airflow sensors, video sensors, audio sensors, accelerometers, GPS locators, and hygrometers. In these examples, the sensors may include sensors with a relatively low sampling rate, such as wireless sensors.
The components of the therapy delivery interface 102 couple one or more therapy delivery devices, such as capacitors and defibrillator electrodes, to the processor 118. In addition, the components of the network interface 106 couple the processor 118 to a computer network via a networking device, such as a bridge, router or hub. According to a variety of examples, the network interface 106 supports a variety of standards and protocols, examples of which include USB (via, for example, a dongle to a computer), TCP/IP, Ethernet, Wireless Ethernet, Bluetooth, ZigBee, M-Bus, CAN-bus, IP, IPV6, UDP, DTN, HTTP, FTP, SNMP, CDMA, NMEA and GSM. To ensure data transfer is secure, in some examples, the wearable medical device controller 100 can transmit data via the network interface 106 using a variety of security measures including, for example, TLS, SSL or VPN. In other examples, the network interface 106 includes both a physical interface configured for wireless communication and a physical interface configured for wired communication. According to various embodiments, the network interface 106 enables communication between the wearable medical device controller 100 and a variety of personal electronic devices including computer enabled glasses and earpieces.
Thus, the various system interfaces incorporated in the wearable medical device controller 100 allow the device to interoperate with a wide variety of devices in various contexts. For instance, some examples of the wearable medical device controller 100 are configured to perform a process of sending critical events and data to a centralized server via the network interface 106. An illustration of a process in accord with these examples is disclosed in U.S. Pat. No. 6,681,003, entitled “DATA COLLECTION AND SYSTEM MANAGEMENT FOR PATIENT-WORN MEDICAL DEVICES” and issued on Jan. 20, 2004 which is hereby incorporated by reference in its entirety.
As illustrated in FIG. 1, the therapy delivery interface 102 and the network interface 106 are optional and may not be included in every example. For instance, a heart rate monitor may employ the wearable medical device controller 100 to issue adaptive alarms but may not include a therapy delivery interface 102 to treat cardiac abnormalities. Similarly, a wearable defibrillator may include the wearable medical device controller 100 to provide adaptive alarm functionality but may not include a network interface 106 where, for example, the wearable defibrillator is designed to rely on the user interface 108 to announce alarms.
The user interface 108 shown in FIG. 1 includes a combination of hardware and software components that allow the wearable medical device controller 100 to communicate with an external entity, such as a user. These components are configured to receive information from actions such as physical movement, verbal intonation or thought processes. In addition, the components of the user interface 108 can provide information to external entities. Examples of the components that may be employed within the user interface 108 include keyboards, mouse devices, trackballs, microphones, electrodes, touch screens, printing devices, display screens and speakers. In some examples, the electrodes include an illuminating element, such as an LED. In other examples, the printing devices include printers capable of rendering visual or tactile (Braille) output.
The wearable medical device controller 100 has a variety of potential applications and is well suited to devices that notify external entities of a variety of events, some of which require a predetermined response from the external entity. Predetermined responses may include any response that is appropriate given the event being reported. Predetermined responses may include acknowledgment of the alarm, entry of information indicating that the alarm is being addressed and rectification of the event or condition that triggered the alarm. Examples of devices to which the wearable medical device controller 100 is well suited include critical care medical devices, such as a wearable external defibrillator. An example of one such defibrillator is described in the '096 application with reference to FIG. 3. In at least one example, the wearable defibrillator 300 illustrated in FIG. 3 of the '096 application employs the wearable medical device controller 100, as disclosed in the present application, as a substitute for the portable treatment controller 200 described in the '096 application. In this example, the ECG Electrodes and Therapy Pads illustrated in FIG. 3 of the '096 application are logically and physically coupled to the wearable medical device controller 100 via the sensor interface 112 and the therapy delivery interface 102, respectively.
Alarm Adaptation Processes
Various examples provide processes through which a medical device adapts alarms that report events of interest to one or more intended recipients. In these examples, the medical device is arranged to include the wearable medical device controller 100 and performs the acts disclosed herein, including the acts described in the Example Alarm Adaptations section below. FIG. 2 illustrates one such process 200 that includes acts of configuring alarm profiles, monitoring events and producing alarms. Process 200 begins at 202.
In act 204, the medical device configures alarm profile information. According to some examples, an alarm manager, such as the alarm manager 114, implements a configuration interface through which the alarm manager receives alarm profile information from a user, such as a patient, physician or equipment technician. Acts in accord with these examples are discussed below with reference to FIG. 3.
In act 206, the medical device monitors events. According to a variety of examples, the alarm manager monitors the various inputs of the medical device for events of interest as specified in alarm profile information, such as the alarm profile information 116. Acts in accord with these examples are discussed below with reference to FIG. 4.
In act 208, the medical device produces an alarm. According to various examples, the alarm manager adapts and issues the alarm in accord with the alarm profile information. Acts in accord with these examples are discussed below with reference to FIG. 5.
In act 210, the medical device determines if an interruption in monitoring is about to commence, such as an interruption caused by shutdown of the wearable medical device controller. If so, the medical device proceeds to 212. Otherwise the medical device returns to act 206.
Process 200 ends at 212. Examples in accord with process 200 allow a medical device to notify intended recipients, such as the patient, a physician or monitoring personnel, of important events in a manner that decreases the likelihood that the alarm will be ignored. Thus, such examples increase the efficacy of the medical device.
As discussed above with regard to act 204 shown in FIG. 2, various examples provide processes for configuring alarm profiles by a medical device. FIG. 3 illustrates one such process 310 that implements act 204 and that includes acts of providing a configuration interface, receiving alarm profile information and storing the alarm profile information. A medical device implementing process 310 begins at 312.
In act 314, an alarm manager, such as the alarm manager 114, provides a configuration interface through which the alarm manager receives alarm profile information, such as the alarm profile information 116. The characteristics of the configuration interface vary from example to example. For instance, in one example, the configuration interface presents, via the user interface 108, one or more screens arranged to receive information identifying an alarm, an intended recipient of the alarm, one or more potential responses, a conduit through which the alarm is provided, content for the alarm, an intensity with which the content is communicated, an issuance rate with which the content is communicated, a target response time and an adaptation path for the alarm. According to another example, the configuration interface includes a system interface implemented via a network interface, such as the network interface 106, and through which the alarm manager receives alarm profile information from an external system. In one example, the external system is a web site through which external entities, such as patients or monitoring personnel, may configure alarm profile information for download to the wearable medical device controller. Other examples detailing characteristics of the configuration interface provided are discussed below in the Example Alarm Adaptations section.
In act 316, the alarm manager receives alarm profile information via the configuration interface. For instance, in one example, the configuration interface receives an intended recipient of the alarm, one or more potential responses, a conduit through which the alarm is provided, content for the alarm, an intensity with which the content is communicated, an issuance rate with which the content is communicated, a target response time and an adaptation path for the alarm via the screens described above. In another example, the alarm profile information is received from the external system described above. In act 318, the alarm manager stores the alarm profile information in data storage, such as the data storage 104. A medical device implementing process 310 terminates the process at 320. Examples in accord with process 310 enable medical devices to gather alarm profile information for later use in reporting and adapting alarms.
As discussed above with regard to act 206 shown in FIG. 2, various examples provide processes for monitoring events encountered in a medical device. FIG. 4 illustrates one such process 400 that may be used to implement act 206 and that includes acts of receiving event information, determining if the event triggers an alarm, and triggering an alarm. A medical device implementing process 400 begins at 402.
In act 404, an alarm manager, such as the alarm manager 114, receives an event from the processor 118. In act 406, the alarm manager determines if the event triggers an alarm by referencing alarm profile information, such as the alarm profile information 116. If so, the alarm manager triggers the alarm in act 408. Otherwise the alarm manager proceeds to 410. A medical device implementing process 400 terminates the process at 410. Examples in accord with process 400 enable medical devices to determine if an event encountered by the device triggers an alarm.
As discussed above with regard to act 208 shown in FIG. 2, various examples provide processes for producing alarms by medical devices. FIG. 5 illustrates one such process 500 that may be used to implement act 208 and that includes acts of retrieving alarm profiles, determining alarm characteristics and issuing an alarm. A medical device implementing process 500 begins at 502.
In act 504, an alarm manager, such as the alarm manager 114, retrieves alarm profile information, such as the alarm profile information 116, from a data storage, such as the data storage 104. In act 506, the alarm manager determines the alarm characteristics based on the alarm profile information and the alarm mode parameter. In one example, the alarm manager determines if the alarm has previously been issued but no predetermined response has been received. If this is the situation, the alarm manager adapts the alarm according to the adaptation path associated with the alarm. Further, in some examples, the alarm manager may record this adaptation so that future instances of the alarm are adapted automatically, i.e. without requiring the issuance of an ineffective alarm. In another example, the alarm manager determines, prior to issuing any alarm instances, that an alarm profile indicates instances of the alarm should be adapted according to the adaptation path and the alarm manager adapts the alarm accordingly. In another example, the alarm manager determines if the environment of the intended recipient of the alarm is such that the alarm should be adapted and, if so, adapts the alarm according to the adaptation path associated with the alarm. Other examples detailing characteristics and adaptations of alarms are discussed below in the Example Alarm Adaptations section.
In act 508, the alarm manager issues the alarm with the characteristics as determined in act 506. A medical device implementing process 500 terminates the process at 510. Examples in accord with process 500 enable medical devices to issue alarms that are adapted to effectively notify the intended recipient of the alarm. This, in turn, increases the likelihood that the intended recipient will perform any actions required to suitably respond to the alarm, thereby benefiting the wearer of the medical device.
Each of the processes disclosed herein depicts one particular sequence of acts in a particular example. The acts included in each of these processes may be performed by, or using, a medical device specially configured as discussed herein. Some acts are optional and, as such, may be omitted in accord with one or more examples. Additionally, the order of acts can be altered, or other acts can be added, without departing from the scope of the systems and methods discussed herein. In addition, as discussed above, in at least one example, the acts are performed on a particular, specially configured machine, namely a medical device configured according to the examples disclosed herein.
Example Alarm Adaptations
According to various examples, an alarm manager, such as the alarm manager 114, performs a wide variety of actions with reference to adaptation paths specified in alarm profile information, such as the alarm profile information 116. For instance, in some examples, the alarm manager receives, via a configuration interface as discussed above, an adaptation path specifying that the alarm manager should initially issue an alarm via one or more conduits and later, if necessary, adapt the alarm to different or multiple conduits. These conduits may communicate, or cause other devices to communicate, with the intended recipient via different sensory outputs such as optical (a display, LED, illuminated electrode, etc. . . . ), auditory (a speaker), and tactile (vibrating output) outputs. In at least one example, the adaptation path specifies that the alarm be initially issued as a vibration alarm and subsequently be adapted to a voice instruction using a voice selected by a user via the configuration interface. According to these examples, the alarm manager issues the alarm according to the adaptation path when the alarm is triggered by an event.
In other examples, the alarm manager receives, via the configuration interface, an adaptation path specifying a duration threshold for the amount of time an alarm may be silenced by an external entity. In these examples, the adaptation path further specifies that the alarm manager should, if the alarm is silenced beyond the threshold and no responsive action has been taken, adapt the alarm by increasing the intensity or issuance rate of the alarm or by changing the conduit through which the alarm is communicated. According to these examples, the alarm manager issues the alarm according to the adaptation path when the alarm is triggered by an event. Further, according to one example, the alarm manager adapts, in accord with information specified in the adaptation path, the alarms silenced beyond the threshold by changing the alarm from a tone to a voice command requesting that the intended recipient take a particular action.
In other examples, the alarm manager receives, via the configuration interface, an adaptation path specifying that if no response is received from an external entity within a specified response time, the alarm manager should increase the intensity of an alarm, for example increase the volume in the case of an auditory alarm. According to these examples, the alarm manager issues the alarm according to the adaptation path when the alarm is triggered by an event.
In other examples, the alarm manager receives, via the configuration interface, an adaptation path specifying that if no response is received from an external entity within a specified response time, the alarm manager should change the content of an alarm, for example change from a tone to a voice command in the case of an auditory alarm. According to these examples, the alarm manager issues the alarm according to the adaptation path when the alarm is triggered by an event.
In other examples, the alarm manager receives, via the configuration interface, an adaptation path specifying that if no response is received from an external entity within a specified response time, the alarm manager should modify the issuance rate with which an alarm is being reported, for example decrease the duration between re-issuances of the alarm. According to these examples, the alarm manager issues the alarm according to the adaptation path when the alarm is triggered by an event.
In other examples, the alarm manager receives, via the configuration interface, an adaptation path specifying that if no response is received from an external entity within a specified response time, the alarm manager should modify the sensory output through which an alarm is being reported, for example change from auditory to visual indicia or vice versa. According to these examples, the alarm manager issues the alarm according to the adaptation path when the alarm is triggered by an event.
In other examples, the alarm manager receives, via the configuration interface, an adaptation path specifying that if no response is received from an external entity within a specified response time, the alarm manager should modify the content of an alarm, for example change from a gentle gong to an ear-piercing siren in the case of an auditory alarm. According to these examples, the alarm manager issues the alarm according to the adaptation path when the alarm is triggered by an event.
In other examples, the alarm manager receives, via the configuration interface, an adaptation path specifying that if no response is received from an external entity within a specified response time, the alarm manager should modify the conduit through which an alarm is reported, for example change the reporting device from the wearable medical device controller to another device associated with the intended recipient. These other devices may include personal electronic devices (such as smart phones, PDAs, wired and wireless headphones or headsets, and tablet computing devices), computer systems (through which alarms may be reported via, for example, on-screen pop-ups), home base stations, bedside radios, televisions (through which alarms may be reported, for example, via on-screen pop-ups or widgets), cars or any other addressable device with an output. According to these examples, the alarm manager issues the alarm according to the adaptation path when the alarm is triggered by an event.
In other examples, the alarm manager receives, via the configuration interface, an adaptation path specifying that the alarm manager issue an alarm to a device other than the wearable medical device prior to issuing the alarm to the wearable medical device. For instance, in one example, the adaptation path specifies that the alarm manager issue an alarm via a call to an intended recipient's phone. In another example, the adaptation path specifies that the alarm manager issue an alarm through a Bluetooth headset paired with the wearable medical device. In still another example, the adaptation path specifies that the alarm manager issue an alarm via a text message sent to the intended recipient's phone. In all of these examples, if a response is not received by the wearable medical device within a target response time, the alarm manager issues the alarm via the wearable medical device.
As with other adaptation paths, this adaptation path may be configured to apply to one or more specific events of interest. For example, where the event of interest is detection of a misplaced or improperly attached electrode, the adaptation path may specify that the alarm manager first issue an alarm specifying the color of the misplaced or improperly attached electrode. Alternatively, this adaptation path may specify that the alarm manager first issue an alarm by illuminating an LED included within the misplaced or improperly attached electrode. In another example, the adaptation path may specify that the alarm manager also issue an alarm via the user interface that specifies the color of the electrode. In another example where the event of interest is passage of a threshold amount of time since a battery included within the wearable medical device has been replaced, the adaptation path may specify that the alarm manager first issue an alarm by sending a text to the phone of an intended recipient.
In other examples, the alarm manager receives, via the configuration interface, an adaptation path specifying that if no response is received from an external entity within a specified response time, the alarm manager should modify the intended recipient to a list of intended recipients including, for example, family members of a patient or local emergency response personnel. According to these examples, the alarm manager issues the alarm according to the adaptation path when the alarm is triggered by an event.
In other examples, the alarm manager receives, via the configuration interface, an adaptation path specifying that if no response is received from an external entity within a specified response time, the alarm manager should, prior to each issuance of an alarm, iterate one or more characteristics of the alarm through a set of values, thereby altering the characteristics of the alarm each time it is issued. This iteration may cycle through the values and may modify any of the characteristics of the alarm including the intensity, issuance rate, content and conduit of the alarm. According to these examples, the alarm manager issues the alarm according to the adaptation path when the alarm is triggered by an event.
In other examples, the alarm manager adjusts the target response time for one or more alarms based on the average patient response time to the alarms. For instance, if the alarm manager detects that the average response time plus a predefined acceptable margin is less than the target response time, the alarm manager may modify the target response time to be equal to the average response time plus the predefined margin.
In other examples, the alarm manager determines, prior to issuance of an alarm, if factors exist that may inhibit the intended recipient's (or bystander's) ability to recognize the alarm. Exemplary inhibiting factors include environmental characteristics, such as excessive sensory stimulation, patient characteristics, such as the physical, mental or emotional state of the patient, and characteristics affecting the wearable medical device. Where an inhibiting factor is present, the alarm manager adapts the alarm to increase the likelihood that the alarm will be recognized despite the presence of the inhibiting factor. Such adaptations may include extending the target response time by some predetermined amount, adjusting the intensity of the alarm or both. In the case of an audio alarm, adjusting the intensity may include adjusting the amplitude or the frequency of the alarm. In other examples, the alarm manager detects the amount of motion or the ambient noise level of the environment of the intended recipient to determine if these factors may be inhibiting recognition of the alarm. According to these examples, the alarm manager extends the target response time or adjusts the intensity of the alarm upon determining that the motion or the ambient noise level is above a predetermined threshold.
In other examples, the alarm manager determines, via a hygrometer such as the hygrometer described above, the relative humidity of the current environment of the wearable medical device and alters the audio alarm characteristics to be more tolerant of the environmental conditions. For instance, in these examples, the alarm manager may increase the target response time or increase the volume of an audio alarm to compensate for the relatively high sound absorption present in a high humidity environment.
In other examples, the alarm manager determines whether the wearable medical device is properly fitted to the patient. In these examples, if the alarm manager determines that the wearable medical device is not properly fitted, the alarm manager adapts alarms to overcome this inhibiting factor. For instance, the alarm manager may increase the intensity of a tactile alarm to increase the likelihood that a patient wearing a loose-fitting medical device feels the tactile alarm. Alternatively, the alarm manager may change the tactile alarm to an auditory alarm.
In another example, the alarm manager uses audio input or physiological data to determine if the mood or stress level of the patient may be an inhibiting factor or may affect the patient's response to an alarm. In this example, where the intended recipient appears to be undergoing stress, the alarm manager decreases the intensity or the duration of the alarm to prevent panic or some other negative or volatile reaction to the alarm. In another instance, where the patient appears to be lying in response to an alarm, the alarm manager repeats the alarm or alters the alarm to verify the veracity of the response. Other adaptations may be performed in response to alarm inhibiting factors and examples are not limited to particular adaptation paths or inhibiting factors.
Some wearable medical devices are continuously or nearly continuously worn by patients for extended periods of time. In fact, in certain situations, these periods of time can extend to two months or more. Over these extended time periods, some patients repeatedly display particularized alarm response patterns. For instance, a patient who commutes to work in the morning, takes lunch at midday, commutes home in the evening and sleeps at night may display a repeatedly delayed response pattern at particular points during the day, such as during the morning and evening commutes, or when the patient is asleep.
According to various examples, the alarm manager analyzes alarm response data for repeating patterns and adapts alarms issued according to an adaptation path that addresses the repeating pattern. More particularly, in some of these examples, the alarm manager identifies the number of false alarms (e.g. alarms responded to by canceling treatment) that occur over a period of time. In these examples, the alarm manager compares the number of false alarms to a threshold value. If the number of false alarms exceeds the threshold value, the alarm manager reports this event to the patient and provides the patient with a set of corrective actions specific to the type of false alarm encountered.
In other examples, the alarm manager determines correlations between values of independent variables that represent a phenomenon and a tendency for a patient to respond to alarms in a particular way (i.e., follow a particular alarm response pattern). This phenomenon may be any phenomenon quantifiable and identifiable by the wearable medical device via sensors or other facilities disclosed herein. Examples of identifiable phenomenon include one or more events as described herein, a predetermined series of events occurring over a predefined span of time, a physical circumstance, such as the time of day, and physiological measurements. According to some examples, the alarm manager may determine correlations by analyzing information describing alarms and responses to alarms as this information is processed by the wearable medical device. The alarm manager may periodically scan a history of this alarm response data that is compiled by the alarm manager during its normal operation. In one example, the alarm manager scans the history of alarm response patterns daily, while in another example, the alarm manager performs this analysis on a weekly or monthly basis. It is to be appreciated that, in some of these examples, the alarm manager determines correlations from population samples that vary in size and whose values are recorded over an extended period of time. Thus, in these examples, the correlations reflect multiple, discrete alarms and response episodes.
In some examples, the alarm manager identifies one or more correlations of interest between independent variables and patient response patterns. In one example, the alarm manager identifies interesting correlations by determining that a value of a correlation exceeds a predetermined threshold. In other examples, the alarm manager automatically creates one or more alarm profiles for each interesting correlation. In these examples, the alarm manager stores one or more adaptation paths within the automatically created alarm profiles. These adaptation paths specify adaptations that address the correlated patient response pattern (i.e., adaptations to alarm characteristics that improve the efficacy of the alarm). Some specific examples of the adaptations performed by the alarm manager when implementing these adaptation paths are described further below. It is to be appreciated that, in some examples, the alarm manager iteratively adjusts the adaptation path correlated with the patient response pattern over an extended period of time. In these examples, the adaptation path gradually improves as the alarm manager analyzes an increasing number of discrete alarms and response episodes.
The alarm manager may adapt alarms to accommodate a repeating pattern in a variety of ways. For instance, to accommodate a period of time in which the patient is normally slow to respond, the alarm manager may simply extend the target response time for any alarms issued. Alternatively, if the alarm is of sufficient importance, the alarm manager may increase the intensity of the alarm or change the conduit used to communicate the alarm. In another example, to accommodate a physiological indication that is correlated with delayed response times by a patient (such as an indication exhibited by the patient during sleep), the alarm manager may delay issuance of the alarm until the physiological indication changes. Examples of the alarm manager may determine correlations between independent variables, other than time of day or physiological data, and alarm response patterns, examples of which are not limited to a particular set of independent variables or alarm response patterns.
In other examples, the alarm manager determines if acuity (or lack of acuity) of the patient's senses may be an inhibiting factor and, if so, adapts alarms to overcome these obstacles. For instance, in one example, the alarm manager administers, within the configuration interface, a hearing test. In this example, the results of the hearing test are stored in the alarm profile information and used by the alarm manager to tailor the audio alarms to a specified frequency, amplitude and tonal qualities. Further, according to this example, the alarm manager issues the audio alarms according to the frequency, amplitude and tonal settings when the audio alarms are triggered by an event. The adaptations in this example enable the alarms to be perceived by the intended recipients with partial hearing loss. In another example designed to address hearing loss, the alarm manager alters the conduit through which audio alarms are presented, instead presenting the alarms as visual alarms through a display.
In other examples, the alarm manager receives, via the configuration interface, an indication that the patient possesses impaired sight. In these examples, the alarm manager alters the conduit through which visual alarms are presented to a non-visual conduit. Non-visual conduits include an auditory conduit (e.g., a speaker) or a tactile conduit (vibration or Braille printout). Alarms issued through a vibrating tactile conduit may simply vibrate once, vibrate repeatedly or vibrate according to a signature pattern, such as Morse code.
In other examples, the alarm manager receives, via the configuration interface, an adaptation path specifying that if no response is received from an external entity within a specified response time, the alarm manager should determine if any bystanders are near the intended recipient. In these examples, the adaptation path may further specify that where bystanders are detected, the alarm manager should adjust the content of the alarm to direct it to the bystanders. In one example, the alarm manager detects the presence of bystanders by determining a difference between a detected voice pattern and a sample voice pattern of the intended recipient that is stored in the alarm profile information. According to these examples, the alarm manager issues the alarm according to the adaptation path when the alarm is triggered by an event.
In other examples, the alarm manager determines that the patient may be asleep and, in response, increases alarm intensities and target response times. In these examples, the alarm manager determines that the patient may be asleep by analyzing any combination of a variety of factors including: physiological data (such as heart rate and respiration), the current time of day, and the presence (or lack) of patient motion, the body position of the patient and the proximity of the patient to a home base station near the patient's bed. In one example, the home base station is configured in accord with the base unit described in co-pending application Ser. No. 13/286,533, entitled REMOTE DEVICE ALARM, filed Nov. 1, 2011, which is incorporated by reference herein in its entirety. Further the alarm manager may receive, via the configuration interface, an adaptation path that specifies a multi-stage alarm in which an intense, initial “wake-up” alarm is followed by a separate alarm reporting the event of interest with different intensity and content. Alternatively, the adaptation path may specify that alarms should be routed to a home base station so that the triggered alarms are communicated with greater intensity. According to these examples, the alarm manager issues the alarm according to the adaptation path when the alarm is triggered by an event.
In other examples, the alarm manager determines that the patient may be mentally or physically impaired and, in response, directs the alarm to another intended recipient, such as a doctor, relative or other caregiver. In these examples, the alarm manager determines that the patient may be mentally impaired by analyzing any combination of a variety of factors including: physiological data (such as heart rate and respiration), the presence (or lack) of patient motion, and audio input (to determine if the patient's speech is impaired).
In other examples, the alarm manager receives, via the configuration interface, an adaptation path that specifies that when the patient fails to take medication according to a prescribed schedule, the alarm manager issues an alarm reminding the patient to do so. In these examples, the alarm manager determines that the patient failed to take medication by analyzing physiological data (such as heart rate and respiration) or by questioning the patient via the user interface. In some of these examples, particular patterns in the physiological data may be linked to particular medications and these links may be used to provide specific alarms to the patient. For instance, if the physiological data exhibits a pattern indicative of congestive heart failure and that pattern is linked to lisinopril, the alarm manager may issue an alarm to remind the patient to take a prescribed dose of lisinopril.
In other examples, the alarm manager receives, via the configuration interface, an adaptation path that specifies adjustments of the intensity, issuance rate or duration of an alarm based on the severity of the event of interest. For instance, in some examples in which the wearable medical device controller is incorporated into a wearable defibrillator, the adaptation path may define particular alarm characteristics to indicate the number and type of electrodes that are not properly positioned on the patient's body. In one example, the adaptation path may specify different tones to indicate incorrect positioning for ECG electrodes and therapy pads. Similarly, in this example, the adaptation path may specify increasing alarm intensities to indicate increasing numbers of electrodes being out of position. According to these examples, the alarm manager issues the alarm according to the adaptation path when the alarm is triggered by an event.
In other examples, the alarm manager is trained by the patient, via the configuration interface, to detect one or more locations, such as a car, office or home, frequently visited by the patient. In one of these examples, the alarm manager receives a location identifier from a user via the configuration interface, records and stores information representative of the ambient noise within the location and creates and stores an association between the location and the stored ambient noise information. In another of these examples, the alarm manager receives a location identifier from a user via the configuration interface, records and stores information representative of the current GPS position of the wearable medical device controller and creates and stores an association between the location and the current GPS position. According to these examples, the alarm manager automatically detects the location of the wearable medical device controller, sets the alarm mode parameter to a value associated with the location and adjusts the triggered alarms accordingly (both according to the alarm mode parameter in general and as defined by the adaptation paths associated with the alarms).
In a particular example, where the alarm mode parameter indicates the patient is occupying a vehicle, the alarm manager issues, via the network interface 106, alarms to the patient through an in-vehicle communications and entertainment system, such as OnStar, SYNC, MyFord Touch, BMW Assist and Lexus Link, that allows users to make hands-free telephone calls and control music and other functions using voice commands. In this example, the alarm manager provides an interface to the patient via the in-vehicle communications and entertainment system. In addition, according to this example, the alarm manager may employ the facilities of the in-vehicle communications system to issue notifications to intended recipients other than the patient, for example sending a request for help to monitoring or emergency personnel.
According to another example, where the alarm mode parameter indicates the patient is at home, the alarm manager issues, via the network interface 106, alarms to the patient through a home security system that allows users to make hands-free telephone calls and control functions using voice command or through a television or computer located within the home of the patient. In this example, the alarm manager provides an interface to the patient via the home security system, television or computer. In addition, according to this example, the alarm manager may employ the facilities of the home security system to issue notifications to intended recipients other than the patient, for example sending a request for help to monitoring or emergency personnel.
According to another example, where the alarm mode parameter indicates the patient is using a personal electronic device, the alarm manager issues, via the network interface 106, alarms to the patient through the personal electronic device. In this example, the alarm manager provides an interface to the patient via the personal electronic device. In addition, according to this example, the alarm manager may employ the facilities of the personal electronic device to issue notifications to intended recipients other than the patient, for example sending a request for help to monitoring or emergency personnel. Moreover, the alarm manager may preempt the normal functioning of the personal electronic device when issuing alarms. For instance, where the personal electronic device is being used to make a phone call, the alarm manager may send alarms and messages into the phone so they can be heard from an external entity. In another example, the personal electronic device may include a light, buzzer or some other sensory output that is activated by the alarm manager when the alarm manager issues an alarm.
In yet another example, a sensory output, such as a light, is positioned within the field of vision of a patient by being integrated into a pair of glasses that are worn by the patient. According to this example, the alarm manager activates the light when issuing an alarm, thereby notifying the patient of the alarm.
In other examples, the alarm manager provides a user interface, via the user interface 108, that receives and responds to voice commands. According to this example, the alarm manager validates the identity of the speaker by verifying that the voice pattern matches a voice pattern stored in data storage, such as the data storage 104. Further, according to this example, the configuration interface receives and responds to voice commands and allows external entities, such as the patient or monitoring personnel to configure alarm information using voice commands.
1. An ambulatory medical device comprising:
one or more physiological sensors configured to acquire cardiopulmonary data from a patient, the cardiopulmonary data comprising one or more of electrocardiogram (ECG) data, heart rate data, and respiration data;
one or more environmental sensors configured to monitor one or more environmental parameters of an environment of the ambulatory medical device; and
at least one processor operatively coupled to the one or more physiological sensors and the one or more environmental sensors and configured to
detect a physiological condition of the patient based on the cardiopulmonary data,
identify a notification associated with the detected physiological condition of the patient to be issued to an intended recipient, the notification having one or more characteristics,
detect an environmental condition of the ambulatory medical device based on the one or more environmental parameters,
determine, based on the detected environmental condition of the ambulatory medical device, whether one or more factors exist that may inhibit the intended recipient's ability to recognize the notification associated with the physiological condition of the patient,
on determining existence of the one or more factors that may inhibit the intended recipient's ability to recognize the notification associated with the physiological condition of the patient, adapt the one or more characteristics of the notification to provide an adapted notification associated with the physiological condition of the patient, and
issue the adapted notification associated with the physiological condition of the patient to the intended recipient.
2. The ambulatory medical device of claim 1, wherein the one or more environmental sensors comprises at least one or more of an atmospheric sensor, a thermometer, an airflow sensor, a video sensor, an audio sensor, an accelerometer, a global positioning system sensor, and a hygrometer.
3. The ambulatory medical device of claim 1, wherein the one or more factors comprises excessive motion.
4. The ambulatory medical device of claim 1, wherein the one or more factors comprises high humidity.
5. The ambulatory medical device of claim 1, wherein the one or more factors comprises an environmental condition correlated with false alarms.
6. The ambulatory medical device of claim 1, wherein the one or more factors comprises excessive sensory stimulation.
7. The ambulatory medical device of claim 6, wherein the excessive sensory stimulation comprises excessive ambient noise.
8. The ambulatory medical device of claim 1, wherein the one or more factors comprises a geographic location of the ambulatory medical device.
9. The ambulatory medical device of claim 1, further comprising at least one defibrillator electrode operably coupled to the at least one processor and configured to treat the patient.
10. The ambulatory medical device of claim 9, wherein the ambulatory medical device is a wearable defibrillator.
11. The ambulatory medical device of claim 10, wherein the ambulatory medical device requires a response to the notification to avoid administration of an unnecessary therapeutic shock.
12. The ambulatory medical device of claim 1, wherein the at least one processor is configured to adapt the one or more characteristics of the notification to one or more of an extended response time and an adjusted intensity.
13. The ambulatory medical device of claim 1, wherein the intended recipient is a person other than the patient.
14. The ambulatory medical device of claim 1, wherein the one or more factors comprises an ambient noise level in the environment.
15. An ambulatory medical device comprising:
detect a physiological condition of the patient based at on the cardiopulmonary data,
determine, based on the detected environmental condition of the ambulatory medical device, whether one or more factors exist that may inhibit the intended recipient's ability to recognize the notification associated with the physiological condition of the patient, the one or more factors comprising at least one of excessive ambient noise and excessive motion of the ambulatory medical device,
16. The ambulatory medical device of claim 15, wherein the one or more factors further comprise high humidity.
17. A method of adapting notifications issued from an ambulatory medical device comprising one or more environmental sensors, one or more physiological sensors, a memory, and at least one processor coupled to the memory, the one or more environmental sensors, and the one or more physiological sensors, the method comprising:
monitoring one or more environmental parameters of an environment of the ambulatory medical device;
acquiring cardiopulmonary data from a patient, the cardiopulmonary data comprising one or more of electrocardiogram (ECG) data, heart rate data, and respiration data;
detecting a physiological condition of the patient based on the cardiopulmonary data;
identifying a notification associated with the detected physiological condition of the patient to be issued to an intended recipient, the notification having one or more characteristics;
detecting an environmental condition of the ambulatory medical device based on the one or more environmental parameters;
determining, based on the detected environmental condition of the ambulatory medical device, whether one or more factors exist that may inhibit the intended recipient's ability to recognize the notification associated with the physiological condition of the patient;
on determining existence of the one or more factors that may inhibit the intended recipient's ability to recognize the notification associated with the physiological condition of the patient, adapting the one or more characteristics of the notification to provide an adapted notification associated with the physiological condition of the patient; and
issuing the adapted notification associated with the physiological condition of the patient to the intended recipient.
18. The method of claim 17, wherein determining whether one or more factors exist comprises determining existence of one or more of excessive motion, high humidity, and improper fitting of the ambulatory medical device to the patient.
US15/483,203 2011-03-25 2017-04-10 System and method for adapting alarms in a wearable medical device Active US9990829B2 (en)
US201161467663P true 2011-03-25 2011-03-25
US201161542749P true 2011-10-03 2011-10-03
US13/428,703 US9135398B2 (en) 2011-03-25 2012-03-23 System and method for adapting alarms in a wearable medical device
US14/704,033 US9378637B2 (en) 2011-03-25 2015-05-05 System and method for adapting alarms in a wearable medical device
US15/159,557 US9659475B2 (en) 2011-03-25 2016-05-19 System and method for adapting alarms in a wearable medical device
US15/483,203 US9990829B2 (en) 2011-03-25 2017-04-10 System and method for adapting alarms in a wearable medical device
US15/965,287 US10269227B2 (en) 2018-04-27 System and method for adapting alarms in a wearable medical device
US15/159,557 Continuation US9659475B2 (en) 2011-03-25 2016-05-19 System and method for adapting alarms in a wearable medical device
US15/965,287 Continuation US10269227B2 (en) 2011-03-25 2018-04-27 System and method for adapting alarms in a wearable medical device
US20170278370A1 US20170278370A1 (en) 2017-09-28
US9990829B2 true US9990829B2 (en) 2018-06-05
ID=46025894
US13/428,703 Active 2032-10-13 US9135398B2 (en) 2011-03-25 2012-03-23 System and method for adapting alarms in a wearable medical device
US14/704,033 Active US9378637B2 (en) 2011-03-25 2015-05-05 System and method for adapting alarms in a wearable medical device
US15/159,557 Active US9659475B2 (en) 2011-03-25 2016-05-19 System and method for adapting alarms in a wearable medical device
US15/483,203 Active US9990829B2 (en) 2011-03-25 2017-04-10 System and method for adapting alarms in a wearable medical device
US (4) US9135398B2 (en)
EP (1) EP2689363A2 (en)
JP (1) JP6166253B2 (en)
WO (1) WO2012135059A2 (en)
WO2012135059A2 (en) 2011-03-25 2012-10-04 Zoll Medical Corporation System and method for adapting alarms in a wearable medical device
US20120313746A1 (en) * 2011-06-10 2012-12-13 Aliphcom Device control using sensory input
US8645132B2 (en) * 2011-08-24 2014-02-04 Sensory, Inc. Truly handsfree speech recognition in high noise environments
TWI483212B (en) * 2012-11-29 2015-05-01
US9757579B2 (en) * 2013-02-25 2017-09-12 West Affum Holdings Corp. Wearable cardioverter defibrillator (WCD) system informing patient that it is validating just-detected cardiac arrhythmia
US20140273917A1 (en) * 2013-03-14 2014-09-18 Ekahau Oy Positioning tag with alert function
US9710678B2 (en) * 2013-04-02 2017-07-18 Dropbox, Inc. Techniques for recovering missing devices
EP3027274A4 (en) 2013-08-01 2017-04-26 Zoll Medical Corporation Systems and methods for utilizing identification devices in a wearable medical therapy device
US10251382B2 (en) * 2013-08-21 2019-04-09 Navico Holding As Wearable device for fishing
EP3058434A2 (en) * 2013-10-14 2016-08-24 NIKE Innovate C.V. Adaptive timing configuration for athletic devices
US9597523B2 (en) * 2014-02-12 2017-03-21 Zoll Medical Corporation System and method for adapting alarms in a wearable medical device
EP3151731A1 (en) * 2014-06-06 2017-04-12 Koninklijke Philips N.V. Unobtrusive advisors for patient monitor
CN105303782B (en) * 2014-06-25 2018-11-23 南京中兴新软件有限责任公司 Warning method and apparatus
US20160055740A1 (en) * 2014-08-25 2016-02-25 Mindray Ds Usa, Inc. Systems and methods for medical device location discovery
KR20160025850A (en) * 2014-08-28 2016-03-09 삼성전자주식회사 Wearable Electronic Device
US20160071392A1 (en) * 2014-09-09 2016-03-10 Apple Inc. Care event detection and alerts
US9737212B2 (en) 2014-12-26 2017-08-22 Intel Corporation Electronic device system to display biometric feedback
EP3268881A1 (en) 2015-03-09 2018-01-17 Koninklijke Philips N.V. Wearable device obtaining audio data for diagnosis
US9987489B2 (en) * 2015-03-27 2018-06-05 Elwha Llc Controlling ear stimulation in response to electrical contact sensing
US10252070B2 (en) 2015-09-08 2019-04-09 Zoll Medical Corporation Secure limited components for use with medical devices
KR20170066034A (en) * 2015-12-04 2017-06-14 삼성전자주식회사 Method for Outputting Alarm and Electronic Device supporting the same
US20170164832A1 (en) * 2015-12-09 2017-06-15 Zoll Medical Corporation Device Administered Tests and Adaptive Interactions
US10121355B1 (en) * 2018-06-26 2018-11-06 Capital One Services, Llc Condition-responsive wearable device for sensing and indicating proximity of an article with a specific characteristic
US3922665A (en) 1974-10-04 1975-11-25 Whittaker Corp Apparatus and method for maintaining operator alertness
DE2644236C3 (en) 1976-09-30 1981-04-02 Siemens Ag, 1000 Berlin Und 8000 Muenchen, De
WO1983004171A1 (en) 1982-05-28 1983-12-08 Mirowski, Mieczyslaw Heart rate detector
US4576170A (en) 1980-07-09 1986-03-18 Micro-Circuits Company Heart monitor and defibrillator device
US4580572A (en) 1983-06-01 1986-04-08 Bio-Stimu Trend Corp. Garment apparatus for delivering or receiving electric impulses
US4583547A (en) 1983-06-01 1986-04-22 Bio-Stimu Trend Corp. Garment apparatus for delivering or receiving electric impulses
US4729377A (en) 1983-06-01 1988-03-08 Bio-Stimu Trend Corporation Garment apparatus for delivering or receiving electric impulses
US4926879A (en) 1988-06-13 1990-05-22 Sevrain-Tech, Inc. Electro-tactile stimulator
US4991217A (en) 1984-11-30 1991-02-05 Ibm Corporation Dual processor speech recognition system with dedicated data acquisition bus
JPH05115450A (en) 1991-10-30 1993-05-14 Nec Corp Auto drift cancel circuit of electrocardiogram analyzing system
EP0295497B1 (en) 1987-06-18 1993-09-08 SGS-THOMSON MICROELECTRONICS S.r.l. High-dynamics amplifier stage with distortion detection
EP0335356B1 (en) 1988-03-30 1996-03-20 Nellcor Incorporated Method and apparatus for compensating for distortion in a pulse oximetry device
EP0761255A1 (en) 1995-08-02 1997-03-12 Pacesetter, Inc. A system and method for storing and displaying historical medical data measured by an implantable medical device
JPH10505515A (en) 1994-07-13 1998-06-02 ジーダブリュ サイエンティフィック インコーポレイテッド Induction of detection and normal heart rate variability abnormal
US5758443A (en) 1993-08-03 1998-06-02 Healtech S.A. Patient Identification Device
US5792190A (en) 1995-08-01 1998-08-11 Survivalink Corporation Automated external defibrillator operator interface
US5827196A (en) 1997-07-15 1998-10-27 Hewlett-Packard Company Method and system for providing characterizations of waveform representations of heart function
WO2000002484A1 (en) 1998-07-10 2000-01-20 Physiometrix, Inc. Self adjusting headgear appliance using reservoir electrodes
US20010031991A1 (en) 1999-12-14 2001-10-18 Joseph Russial Circuit for producing an arbitrary defibrillation waveform
US6405082B1 (en) 2000-01-24 2002-06-11 Koninklijke Philips Electronics N.V. Method and apparatus for distinguishing between therapy modes in a defibrillator
US20020181680A1 (en) 1999-10-05 2002-12-05 Marshal Linder Data collection and system management for patient-worn medical devices
US20030054866A1 (en) * 2001-09-20 2003-03-20 Byers Charles Calvin Method for automatically selecting the alert type for a mobile electronic device
US20030149462A1 (en) 2002-02-04 2003-08-07 White Sheldon S. Medical electrodes
US20030195567A1 (en) 2002-04-10 2003-10-16 Medtronic Physio-Control Corp. Automated external defibrillator with user interface for adult and pediatric applications
US20030212311A1 (en) 2002-05-07 2003-11-13 Medtronic Physio-Control Manufacturing Corp. Therapy-delivering portable medical device capable of triggering and communicating with an alarm system
US6690969B2 (en) 1999-03-05 2004-02-10 Revivant Corporation Public access CPR and AED device
US20040049233A1 (en) 2002-09-11 2004-03-11 Edwards D. Craig Medical device status information system
WO2004054656A1 (en) 2002-12-13 2004-07-01 Koninklijke Philips Electronics N.V. External defibrillator with shock activated by cessation of precordial compressions
WO2004078259A1 (en) 2003-02-28 2004-09-16 Medtronic Emergency Response Systems, Inc. Recording information for emergency call by defibrillator apparatus
WO2005082454A1 (en) 2004-02-19 2005-09-09 Koninklijke Philips Electronics, N.V. Method and apparatus for broadcasting audible information prompts from an external defibrillator
US20050246199A1 (en) 2004-05-03 2005-11-03 Tom Futch Health and wellness station
US20060036292A1 (en) 2004-08-16 2006-02-16 Mitchell Smith Risk of death indicator
US20060059976A1 (en) 2004-09-23 2006-03-23 Innalabs Technologies, Inc. Accelerometer with real-time calibration
US20060085049A1 (en) 2004-10-20 2006-04-20 Nervonix, Inc. Active electrode, bio-impedance based, tissue discrimination system and methods of use
WO2006050325A2 (en) 2004-10-29 2006-05-11 Worcester Polytechnic Institute System and method for multi-channel electrophysiologic signal data acquisition
US20060178706A1 (en) 2005-02-10 2006-08-10 Lisogurski Daniel M Monitoring physiological signals during external electrical stimulation
US20060211934A1 (en) 2005-03-16 2006-09-21 Textronics, Inc. Textile-based electrode
US20060259080A1 (en) 2005-03-21 2006-11-16 Defibtech, Llc System and method for presenting defibrillator status information while in standby mode
US20060270952A1 (en) 2005-03-25 2006-11-30 Freeman Gary A Integrated resuscitation
WO2007019325A2 (en) 2005-08-04 2007-02-15 Access Cardiosystems, Inc. Automatic external defibrillator (aed) with wireless communications
US20070118056A1 (en) 2005-11-18 2007-05-24 Hua Wang Posture detector calibration and use
US20070161913A1 (en) 2004-03-31 2007-07-12 Michael Farrell Methods and apparatus for monitoring the cardiovascular condition of patients with sleep disordered breathing
US20070169364A1 (en) 2001-02-23 2007-07-26 Microstrain, Inc. Posture and body movement measuring system
US20070232946A1 (en) * 2006-03-31 2007-10-04 Koninklijke Philips Electronics N.V. Ecg lead misplacement detection and correction
US20070239220A1 (en) 2006-03-29 2007-10-11 Greenhut Saul E Implantable medical device system and method with signal quality monitoring and response
US20080004536A1 (en) 2006-06-30 2008-01-03 Baxi Amit S Method and apparatus for amplifying multiple signals using a single multiplexed amplifier channel with software controlled AC response
EP1455640B1 (en) 2001-10-26 2008-01-16 Philips Electronics N.V. Garment comprising medical sensors
US20080021532A1 (en) 2006-07-21 2008-01-24 Kveen Graig L Delivery of cardiac stimulation devices
US20080033495A1 (en) 2006-08-01 2008-02-07 Kumar Uday N External Defibrillator
US20080030309A1 (en) 2006-07-31 2008-02-07 Texas Instruments Incorporated System and method for providing information about a medication to a medicine user
US20080058884A1 (en) 2006-08-29 2008-03-06 Matos Jeffrey A Control of a defibrillator and/or pacemaker
US7427921B2 (en) 2003-05-21 2008-09-23 Koninklijke Philips Electronics N.V. Monitoring system capable of generating audible messages
US20080266118A1 (en) 2007-03-09 2008-10-30 Pierson Nicholas J Personal emergency condition detection and safety systems and methods
US20080306560A1 (en) 2007-06-06 2008-12-11 Macho John D Wearable defibrillator with audio input/output
US20080306562A1 (en) 2007-06-07 2008-12-11 Donnelly Edward J Medical device configured to test for user responsiveness
US20080312709A1 (en) 2007-06-13 2008-12-18 Volpe Shane S Wearable medical treatment device with motion/position detection
US20090018428A1 (en) 2003-05-19 2009-01-15 Umist Ventures Limited Knitted transducer devices
US7488293B2 (en) 2003-04-23 2009-02-10 Zoll Medical Corporation Processing pulse signal in conjunction with accelerometer signal in cardiac resuscitation
JP2009510631A (en) 2005-09-30 2009-03-12 ネルコー ピューリタン ベネット エルエルシー Patient monitoring alarm escalation system and method
US20090076340A1 (en) 2007-09-14 2009-03-19 Corventis, Inc. Adherent Cardiac Monitor with Advanced Sensing Capabilities
US20090076344A1 (en) 2007-09-14 2009-03-19 Corventis, Inc. Multi-Sensor Patient Monitor to Detect Impending Cardiac Decompensation
WO2009034506A1 (en) 2007-09-12 2009-03-19 Koninklijke Philips Electronics, N.V. Remote status indicator for a defibrillator
US20090076363A1 (en) 2007-09-14 2009-03-19 Corventis, Inc. Adherent Device with Multiple Physiological Sensors
US20090076405A1 (en) 2007-09-14 2009-03-19 Corventis, Inc. Adherent Device for Respiratory Monitoring
US20090076348A1 (en) 2007-09-14 2009-03-19 Corventis, Inc. Injectable Device for Physiological Monitoring
US20090138059A1 (en) 2004-12-08 2009-05-28 Koninklijke Philips Electronics N.V. Heart Defibrillator With Contactless ECG Sensor For Diagnostics/Effectivity Feedback
JP2009521865A (en) 2005-12-22 2009-06-04 マクロビジョン・コーポレーション Content distribution and monitoring technology
US20090146822A1 (en) 2007-11-13 2009-06-11 Elevate Technologies Pty Ltd. Telemedicine Application for Remote Monitoring, Viewing and Updating of Patient Records
US20090234410A1 (en) 2008-03-12 2009-09-17 Corventis, Inc. Heart Failure Decompensation Prediction Based on Cardiac Rhythm
US20090232286A1 (en) 2008-03-14 2009-09-17 Gigle Semiconductor, Ltd. Coupling signal processing circuitry with a wireline communications medium
WO2009122277A2 (en) 2008-04-04 2009-10-08 Gambro Lundia Ab A medical apparatus
JP2009536068A (en) 2006-05-10 2009-10-08 コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ Automated external defibrillator with a voice prompt that clarity is enhanced
US20090264792A1 (en) 2008-04-18 2009-10-22 Corventis, Inc. Method and Apparatus to Measure Bioelectric Impedance of Patient Tissue
US20090281394A1 (en) 2006-09-25 2009-11-12 Brian Keith Russell Bio-mechanical sensor system
US20090312650A1 (en) 2008-06-12 2009-12-17 Cardiac Pacemakers, Inc. Implantable pressure sensor with automatic measurement and storage capabilities
WO2010025432A1 (en) 2008-08-31 2010-03-04 Abbott Diabetes Care Inc. Closed loop control with improved alarm functions
US20100052892A1 (en) 2008-08-27 2010-03-04 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Health-related signaling via wearable items
US20100069735A1 (en) 2006-07-29 2010-03-18 Lior Berkner Device for mobile electrocardiogram recording
US20100076513A1 (en) 2001-11-21 2010-03-25 Cameron Health, Inc. Multiple Electrode Vectors for Implantable Cardiac Treatment Devices
US20100076533A1 (en) 2007-08-23 2010-03-25 Amit Dar System for transmitting electrical current to a bodily tissue
US7712373B2 (en) 2006-03-03 2010-05-11 Nagle H Troy Sensor device for real-time monitoring or relative movement using capacitive fabric sensors
WO2010077997A2 (en) 2008-12-16 2010-07-08 Bodymedia, Inc. Method and apparatus for determining heart rate variability using wavelet transformation
US20100295674A1 (en) 2009-05-21 2010-11-25 Silverplus, Inc. Integrated health management console
US20100298899A1 (en) 2007-06-13 2010-11-25 Donnelly Edward J Wearable medical treatment device
US20110172550A1 (en) 2009-07-21 2011-07-14 Michael Scott Martin Uspa: systems and methods for ems device communication interface
US20110170692A1 (en) 2009-11-06 2011-07-14 Roche Diagnostics International Ltd. Method And System For Establishing Cryptographic Communications Between A Remote Device And A Medical Device
US7991460B2 (en) 2002-09-20 2011-08-02 Angel Medical Systems, Inc. Methods and apparatus for detecting cardiac events based on heart rate sensitive parameters
US20110288605A1 (en) 2010-05-18 2011-11-24 Zoll Medical Corporation Wearable ambulatory medical device with multiple sensing electrodes
US20120011382A1 (en) 2010-07-09 2012-01-12 Shane Volpe System and method for conserving power in a medical device
US8121683B2 (en) 2005-11-15 2012-02-21 Metrax Gmbh External automatic defibrillator
US20120112903A1 (en) 2010-11-08 2012-05-10 Zoll Medical Corporation Remote medical device alarm
US20120126975A1 (en) * 2010-11-23 2012-05-24 Gonzales Eric V Dynamic Alarm Sensitivity Adjustment and Auto-Calibrating Smoke Detection for Reduced Resource Microprocessors
US20120150008A1 (en) 2010-12-09 2012-06-14 Kaib Thomas E Electrode with redundant impedance reduction
US20120146797A1 (en) 2010-12-10 2012-06-14 Emil Oskin Wearable therapeutic device
US20120158075A1 (en) 2010-12-16 2012-06-21 Kaib Thomas E Water resistant wearable medical device
US20120191476A1 (en) 2011-01-20 2012-07-26 Reid C Shane Systems and methods for collection, organization and display of ems information
US20120259377A1 (en) 2011-04-08 2012-10-11 Zoll Medical Corporation Coordinated resuscitation perfusion support
US8290574B2 (en) 2008-03-10 2012-10-16 Koninklijke Philips Electronics N.V. ECG monitoring system with configurable alarm limits
US20120283794A1 (en) 2011-05-02 2012-11-08 Kaib Thomas E Patient-worn energy delivery apparatus and techniques for sizing same
US20120289809A1 (en) 2011-03-25 2012-11-15 Zoll Medical Corporation Method of detecting signal clipping in a wearable ambulatory medical device
US8319632B1 (en) 2008-08-25 2012-11-27 Vaisnys Gintaras A System and method for monitoring external portable medical devices
US20120302860A1 (en) 2011-03-25 2012-11-29 Zoll Medical Corporation Selection of optimal channel for rate determination
US20130085538A1 (en) 2011-09-01 2013-04-04 Zoll Medical Corporation Wearable monitoring and treatment device
US20130231711A1 (en) 2012-03-02 2013-09-05 Thomas E. Kaib Systems and methods for configuring a wearable medical monitoring and/or treatment device
US20130324868A1 (en) 2012-05-31 2013-12-05 Zoll Medical Corporation Systems and methods for detecting health disorders
US20130325078A1 (en) 2012-05-31 2013-12-05 Zoll Medical Corporation Medical monitoring and treatment device with external pacing
US20130325096A1 (en) 2012-05-31 2013-12-05 Zoll Medical Corporation Long term wear multifunction biomedical electrode
US20140004814A1 (en) 2012-06-29 2014-01-02 Zoll Medical Corporation Rescue services activation
US20140031885A1 (en) 2012-07-27 2014-01-30 Zoll Medical Corporation Medical equipment messaging
WO2014097035A1 (en) 2012-12-17 2014-06-26 Koninklijke Philips N.V. Adaptive self-testing and stress analysis of medical devices
US20140277243A1 (en) 2013-03-12 2014-09-18 Cardiac Pacemakers, Inc. Heart sounds template comparison to identify true pacing mode
US20150039053A1 (en) 2013-06-28 2015-02-05 Zoll Medical Corporation Systems and methods of delivering therapy using an ambulatory medical device
US20150039042A1 (en) 2013-08-01 2015-02-05 Zoll Medical Corporation Indicators on a Wearable Medical Therapy Device
US20150035654A1 (en) 2013-08-01 2015-02-05 Zoll Medical Corporation Systems and Methods for Utilizing Identification Devices in a Wearable Medical Therapy Device
US20150224330A1 (en) 2014-02-12 2015-08-13 Zoll Medical Corporation System and method for adapting alarms in a wearable medical device
2012-03-23 WO PCT/US2012/030428 patent/WO2012135059A2/en active Application Filing
2012-03-23 EP EP12718463.8A patent/EP2689363A2/en active Pending
2012-03-23 US US13/428,703 patent/US9135398B2/en active Active
2012-03-23 JP JP2014501285A patent/JP6166253B2/en active Active
2015-05-05 US US14/704,033 patent/US9378637B2/en active Active
2016-05-19 US US15/159,557 patent/US9659475B2/en active Active
2017-04-10 US US15/483,203 patent/US9990829B2/en active Active
US6097982A (en) 1996-05-23 2000-08-01 Lifecor, Inc. Patient-worn energy delivery apparatus
JP2002514107A (en) 1997-03-07 2002-05-14 カーディアック・サイエンス・インコーポレイテッド Wearable defibrillator system
US20110022105A9 (en) 1997-03-07 2011-01-27 Owen James M Defibrillation system
JP2002509472A (en) 1998-04-15 2002-03-26 カーディアック・ペースメイカーズ・インコーポレーテッド Atrial defibrillation system including a portable audible voice communication device
US7476206B2 (en) 2002-10-25 2009-01-13 Zoll Circulation, Inc. System for estimating the actual ECG of a patient during CPR
JP2007522859A (en) 2004-02-19 2007-08-16 コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ Method for transmitting audible information prompts from an external defibrillator and apparatus
US20070162075A1 (en) 2004-02-19 2007-07-12 Koninklijke Philips Electronics N.V. Method and apparatus for broadcasting audible information prompts from an external defibrillator
JP2006091013A (en) 2004-09-23 2006-04-06 Innalabs Technologies Inc Accelerometer with real time calibration
US20080046015A1 (en) 2004-09-30 2008-02-21 Zoll Medical Corporation Integrated Resuscitation
US20090221887A1 (en) 2005-09-30 2009-09-03 Nellcor Puritan Bennett Incorporated Patient monitoring alarm escalation system and method
US8331574B2 (en) 2006-05-10 2012-12-11 Koninklijke Philips Electronics N.V. Automatic external defibrillator with enhanced clarity of audible prompts
US20140324112A1 (en) 2007-06-06 2014-10-30 Zoll Medical Corporation Wearable defibrillator with audio input/output
US8774917B2 (en) 2007-06-06 2014-07-08 Zoll Medical Corporation Wearable defibrillator with audio input/output
JP2008302225A (en) 2007-06-06 2008-12-18 Zoll Medical Corp Wearable defibrillator furnished with voice input/output
US20130144355A1 (en) 2007-06-06 2013-06-06 Zoll Medical Corporation Wearable defibrillator with audio input/output
JP2008302228A (en) 2007-06-07 2008-12-18 Zoll Medical Corp Medical device configured to test for user responsiveness
US20130013014A1 (en) 2007-06-07 2013-01-10 Zoll Medical Corporation Medical device configured to test for user responsiveness
US20100312297A1 (en) 2007-06-13 2010-12-09 Zoll Medical Corporation Wearable medical treatment device with motion/position detection
US20140303680A1 (en) 2007-06-13 2014-10-09 Zoll Medical Corporation Wearable medical treatment device
US8649861B2 (en) 2007-06-13 2014-02-11 Zoll Medical Corporation Wearable medical treatment device
US8676313B2 (en) 2007-06-13 2014-03-18 Zoll Medical Corporation Wearable medical treatment device with motion/position detection
US20140163334A1 (en) 2007-06-13 2014-06-12 Zoll Medical Corporation Wearable medical treatment device with motion/position detection
US9283399B2 (en) 2007-06-13 2016-03-15 Zoll Medical Corporation Wearable medical treatment device
US20090076410A1 (en) 2007-09-14 2009-03-19 Corventis, Inc. System and Methods for Wireless Body Fluid Monitoring
US20090076364A1 (en) 2007-09-14 2009-03-19 Corventis, Inc. Adherent Device for Sleep Disordered Breathing
US8706215B2 (en) 2010-05-18 2014-04-22 Zoll Medical Corporation Wearable ambulatory medical device with multiple sensing electrodes
WO2012006524A1 (en) 2010-07-09 2012-01-12 Zoll Medical Corporation Wearable medical treatment device
US8406842B2 (en) 2010-12-09 2013-03-26 Zoll Medical Corporation Electrode with redundant impedance reduction
US20130218252A1 (en) 2010-12-09 2013-08-22 Zoll Medical Corporation Electrode with redundant impedance reduction
WO2012100219A1 (en) 2011-01-20 2012-07-26 Zoll Medical Corporation Systems and methods for collection, organization and display of ems information
US20150080699A1 (en) 2011-03-25 2015-03-19 Zoll Medical Corporation Method of detecting signal clipping in a wearable ambulatory medical device
US8897860B2 (en) 2011-03-25 2014-11-25 Zoll Medical Corporation Selection of optimal channel for rate determination
US8644925B2 (en) 2011-09-01 2014-02-04 Zoll Medical Corporation Wearable monitoring and treatment device
US20140206974A1 (en) 2011-09-01 2014-07-24 Zoll Medical Corporation Wearable monitoring and treatment device
WO2013130957A2 (en) 2012-03-02 2013-09-06 Zoll Medical Corporation Systems and methods for configuring a wearable medical monitoring and/or treatment device
WO2014018160A1 (en) 2012-07-27 2014-01-30 Zoll Medical Corporation Medical equipment messaging
American Journal of Respiratory and Critical Care Medicine, vol. 166, pp. 111-117 (2002), American Thoracic Society, ATS Statement: Guidelines for the Six-Minute Walk Test, available at http://ajrccm.atsjournals.org/cgi/content/ull/166/1/111.
Association for the Advancement of Medical Instrumentation, ANSI/AAMI DF80:2003 Medical Electrical Equipment-Part 2-4: Particular Requirements for the Safety of Cardiac Defibrillators (including Automated External Defibrillators) 2004, ISBN 1-57020-210-9; abstract; p. vi; p. 50, section 107.1.2.
Association for the Advancement of Medical Instrumentation, ANSI/AAMI DF80:2003 Medical Electrical Equipment—Part 2-4: Particular Requirements for the Safety of Cardiac Defibrillators (including Automated External Defibrillators) 2004, ISBN 1-57020-210-9; abstract; p. vi; p. 50, section 107.1.2.
DeBock, et al., "Captopril treatment of chronic heart failure in the very old," J. Gerontol. (1994) 49: M148-M152.
http://web.archive.org/web/20030427001846/http:/www.lifecor.comiimagelib/imageproduct.asp. Published by LifeCor, Inc., 2002, on a webpage owned by LifeCor, Inc.
International Search Report and Written Opinion from corresponding PCT Application No. PCT/US2012/030428, dated Nov. 7, 2012.
O'Keeffe et al., "Reproducability and responsiveness of quality of life assessment and six minute walk test in elderly heart failure patients," Heart (1998) 80: 377-382.
ZOLL Medical Corporation, LifeVest Model WCD 3000 Operator's Manual, Pittsburgh, PA.
US9378637B2 (en) 2016-06-28
US20120293323A1 (en) 2012-11-22
US20160267765A1 (en) 2016-09-15
US20170278370A1 (en) 2017-09-28
JP2014517716A (en) 2014-07-24
US20150235541A1 (en) 2015-08-20
WO2012135059A3 (en) 2013-01-17
US9659475B2 (en) 2017-05-23
EP2689363A2 (en) 2014-01-29
US20180315286A1 (en) 2018-11-01
US9135398B2 (en) 2015-09-15
JP6166253B2 (en) 2017-07-19
WO2012135059A2 (en) 2012-10-04
US8781847B2 (en) 2014-07-15 System and method for managing alert notifications in an automated patient management system
US8027632B2 (en) 2011-09-27 Systems, devices, and methods for selectively preventing data transfer from a medical device
US8727978B2 (en) 2014-05-20 Health monitoring appliance
Lee et al. 2007 A mobile care system with alert mechanism
JP5254339B2 (en) 2013-08-07 Medical information transmission method through the life-critical networks, medical information transmission system, and the patient portable communication device
US20100286490A1 (en) 2010-11-11 Interactive patient monitoring system using speech recognition
US20170010664A1 (en) 2017-01-12 Smart wearable devices and methods for automatically configuring capabilities with biology and environment capture sensors
US8655441B2 (en) 2014-02-18 Methods and apparatus for monitoring patients and delivering therapeutic stimuli
US20170140170A1 (en) 2017-05-18 Wearable device multi-mode system
JP5937091B2 (en) 2016-06-22 Detecting device of convulsions
US7512889B2 (en) 2009-03-31 Method and system for controlling presentation of information to a user based on the user&#39;s condition
US20140195166A1 (en) 2014-07-10 Device control using sensory input
JP6478461B2 (en) 2019-03-06 Mobile device with an intuitive alert
US8766789B2 (en) 2014-07-01 First emergency response device
US20110267196A1 (en) 2011-11-03 System and method for providing sleep quality feedback
US20180301209A1 (en) 2018-10-18 User terminal device and system for performing user customized health management, and methods thereof
JP5005819B2 (en) 2012-08-22 Environment related with respiratory disease self-monitoring method and system
EP1578338A2 (en) 2005-09-28 Repeater device for communications with an implantable medical device
JP2017200587A (en) 2017-11-09 Medical monitoring system
Massé et al. 2013 Miniaturized wireless ECG monitor for real-time detection of epileptic seizures
Trapanotto et al. 2004 Behavioural and physiological reactivity to noise in the newborn
Baig et al. 2015 Mobile healthcare applications: system design review, critical issues and challenges
US7649449B2 (en) 2010-01-19 System and method for providing synergistic alert condition processing in an automated patient management system
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KAIB, THOMAS E.;VOLPE, SHANE S.;CLARK, JOHN G.;REEL/FRAME:043655/0325