Proximity based processing systems and methods

Description

BACKGROUND

This disclosure relates generally to external medical devices, and more specifically, to apparatus and processes of ambulatory medical devices that provide proximity based notifications and location determination services.

There are a wide variety of electronic and mechanical medical devices for monitoring and treating patients' medical conditions. The one or more particular medical devices used to monitor and/or treat a patient depend on the underlying medical condition with which the patient is afflicted. For example, where a patient has a medical condition that affects the patient's cardiac function (e.g., a cardiac arrhythmia), medical devices such as cardiac pacemakers or defibrillators may be used to treat the patient. In some cases, these medical devices may be surgically implanted or externally connected to the patient. Such medical devices may be used alone, or in combination with drug therapies, to treat medical conditions such as cardiac arrhythmias.

One of the most deadly cardiac arrhythmias is ventricular fibrillation, which occurs when normal, regular electrical impulses are replaced by irregular and rapid impulses, causing the heart muscle to stop normal contractions and to begin to quiver. Normal blood flow ceases, and organ damage or death can result in minutes if normal heart contractions are not restored. Because the victim has no perceptible warning of the impending fibrillation, death often occurs before the necessary medical assistance can be administered. Other cardiac arrhythmias include excessively slow heart rates known as bradycardia.

Implantable or external pacemakers and defibrillators (such as automated external defibrillators or AEDs) have significantly improved the ability to treat these otherwise life-threatening conditions. Such devices operate by applying corrective electrical pulses directly to the patient's heart. For example, bradycardia can be corrected through the use of an implanted or external pacemaker device. Ventricular fibrillation can be treated by an implanted or external defibrillator.

Some medical devices operate by continuously or substantially continuously monitoring the patient's heart for treatable arrhythmias via one or more sensing electrodes and, when such is detected, applying corrective electrical pulses directly to the heart through one or more therapy electrodes. Patients use these devices while ambulatory and visiting various locations, such as their home or place of work.

SUMMARY

An ambulatory medical device is capable of and designed for moving with a patient as the patient goes about his or her daily routine. The mobility enabled by an ambulatory medical device provides for a greater quality of life for a patient undergoing treatment and also presents opportunities for improved patient care. However, this same mobility creates challenges for patients and ambulatory medical device providers. Various aspects and examples described herein leverage the mobile nature of an ambulatory medical device to beneficial effect while addressing challenges created thereby.

For example, a patient wearing an ambulatory medical device may visit various locations where medical assistance is not readily available. Thus it may be important for the health of the patient that the ambulatory medical device be in proper operating condition when the patient visits these locations. The tasks required to maintain an ambulatory medical device in proper operating condition vary between devices. For example, where the ambulatory medical device includes electrodes, the tasks required to maintain the device in proper working condition may include replacing and/or adjusting the electrodes periodically and swapping or recharging a battery that powers the device. Some tasks (e.g., replacing an electrode or swapping a battery) require a replacement component be readily available, but these replacement components may be of limited availability in some locations. In some examples, the tasks required to maintain an ambulatory medical device in proper operating condition further include maintaining software components of the medical device, as may be achieved by updating the software components to keep their versions current.

Aspects and examples disclosed herein manifest an appreciation for these and other problems facing patients and medical device providers. For instance, some examples execute automated tasks that prompt the patient and/or other persons to take the actions necessary to maintain an ambulatory medical device in proper working condition, while the patient and/or other persons are in a position to do so. In other examples, the medical device automatically executes tasks that directly maintain the ambulatory medical device in proper working condition, while the device is in position to do so.

One example is directed to an ambulatory medical device. The ambulatory medical device includes at least one sensor configured to acquire data descriptive of a patient; a memory; a user interface; and at least one processor coupled with the memory, the at least one sensor, and the user interface. The at least one processor is configured to determine whether the ambulatory medical device is within a predefined range of a reference location and to initiate location-specific processing in response to determining that the ambulatory medical device is within the predefined range, the location-specific processing comprising at least one of issuing a notification and adapting the user interface.

In the ambulatory medical device, the reference location may refer to at least one of a fixed geographic location, a location of a fixed device, and a location of a mobile device. The at least one processor may be configured to determine whether the ambulatory medical device is within the predefined range using at least one of a location of a cellular tower, dead reckoning, a global positioning system, indoor positioning system, triangulation, an indoor beacon, and signal strength. The reference location may refer to a physical location including a location of a battery charger and the location-specific processing may include issuing a notification to charge a battery. The medical device may further include the battery.

The ambulatory medical device may further include at least one capacitor coupled to the battery and at least one therapy electrode coupled to the at least one capacitor. The location-specific processing may include at least one of downloading of one or more software updates, downloading device configuration information, downloading new or updated patient parameters, downloading threshold changes to underlying monitoring parameters, and downloading threshold changes to underlying treatment parameters. The location-specific processing may include calculating at least one metric based on a physiological signal.

The location-specific processing may include transmitting a notification to the patient to perform a six minute walk test. The location-specific processing may include transmitting a notification to the patient to review a patient training module.

In the ambulatory medical device, the memory may include a template schedule listing scheduled visitations to reference locations. The location-specific processing may include identifying, in the template schedule, a next scheduled visitation to a reference location equipped to complete a task and determining that the task is due prior to the next scheduled visitation, and the notification includes a request to complete the task within the predefined range. The at least one processor may be further configured to adjust the template schedule based on sampled movement observations of the patient. The task may include taking medication. The task may include servicing a serviceable component of the ambulatory medical device. The serviceable component may include a battery. In the ambulatory medical device, determining that the task is due may include determining that the battery has a remaining runtime of less than a period of time based on the next scheduled visitation. The serviceable component may include a garment. In the ambulatory medical device, determining that the task is due may include determining that the garment has not been laundered for a period of time based on the next scheduled visitation.

In the ambulatory medical device, the reference location may refer to a caregiver facility and the location-specific processing may include adapting the user interface to interact with a caregiver. In the ambulatory medical device, the at least one processor may be further configured to determine whether the ambulatory medical device is within at least one other predefined range of at least one other reference location and to initiate the location-specific processing in response to determining that the ambulatory medical device is within the at least one other predefined range. In the ambulatory medical device, the at least one processor may be further configured to determine whether the ambulatory medical device is within at least one other predefined range of at least one other reference location and to execute a conflict resolution process that favors the reference location.

The ambulatory medical device may further comprise a network interface coupled with the at least one processor. The network interface may be configured to detect an identifier of a network, the memory stores a predefined network identifier, and the at least one processor may be configured to determine that the ambulatory medical device is within the predefined range at least in part by comparing the identifier of the network to the predefined network identifier. The identifier of the network may indicate that the network is at least one of a wired local area network, a Wi-Fi network, a BLUETOOTH network, BLE beacon identifier, and a near field communication network. The memory may store an association between the predefined network identifier and an identifier of at least one of a home of the patient, an office of the patient, and a health care facility for the patient.

In the ambulatory medical device, the at least one processor may be configured to determine whether the ambulatory medical device is within the predefined range of the reference location in response to at least one of expiration of a periodic timer, expiration of an aperiodic timer, and receipt of a request to determine the distance. The ambulatory medical device may further include a network interface coupled with the at least one processor. The at least one processor may be further configured to operate the network interface in a power conservation mode when not determining whether the ambulatory medical device is within the predefined range of the reference location. The ambulatory medical device may further include a battery. The at least one processor may be further configured to limit determining whether the ambulatory medical device is within the predefined range of the reference location when the battery has a remaining runtime of less than a predetermined period of time.

Another example is directed to a method of executing location-specific processing within an ambulatory medical device. The method includes acts of determining whether the ambulatory medical device is within a predefined range of a reference location; and initiating location-specific processing in response to determining that the ambulatory medical device is within the predefined range, the location-specific processing comprising at least one of issuing a notification and adapting the user interface.

Still other aspects, examples and advantages of these 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 features, and are intended to provide an overview or framework for understanding the nature and character of the claimed aspects and examples. Any example or feature disclosed herein may be combined with any other example or feature. References to different examples 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 at least one example. The appearances of such terms herein are not necessarily all referring to the same example.

DESCRIPTION OF DRAWINGS

Various aspects of at least one example are discussed below with reference to the accompanying figures, which are not intended to be drawn to scale. The figures are included to provide an illustration and a further understanding of the various aspects and examples, and are incorporated in and constitute a part of this specification, but are not intended as a definition of the limits of any particular example. The drawings, together with the remainder of the specification, serve to explain principles and operations of the described and claimed aspects and examples. In the figures, each identical or nearly identical component that is illustrated in various figures is represented by a like numeral. For purposes of clarity, not every component may be labeled in every figure.

FIG. 1 is a schematic diagram of one example of a medical device in accordance with an example of the present disclosure.

FIGS. 2A and 2B are schematic diagrams of a first side and a second side of one example of a medical device controller in accordance with an example of the present disclosure.

FIG. 3 is a schematic diagram of an example system including a medical device controller and a base station in accordance with an example of the present disclosure.

FIG. 4 is a block diagram of an example of a medical device controller in accordance with an example of the present disclosure.

FIG. 5 is a flow diagram illustrating one example of a proximity monitoring process in accordance with an example of the present disclosure.

FIG. 6 is a flow diagram illustrating one example of a proximity detection process in accordance with an example of the present disclosure.

FIG. 7 is a flow diagram illustrating another example of a proximity detection process in accordance with an example of the present disclosure.

FIG. 8 is a flow diagram illustrating one example of a location-specific process in accordance with an example of the present disclosure.

FIG. 9 is a flow diagram illustrating one example of a template schedule adaptation process in accordance with an example of the present disclosure.

FIG. 10 is a block diagram of screens illustrating an adaptation by one or more location aware components in accordance with examples of the present disclosure.

FIG. 11 is a flow diagram illustrating another example of a proximity monitoring process in accordance with an example of the present disclosure.

FIG. 12 is a diagram of a location aware processing system in accordance with examples of the present disclosure.

DETAILED DESCRIPTION

Some aspects and examples are directed to apparatus and processes that monitor the location of a medical device and execute location-specific processing upon detecting that the medical device is within a predetermined range of a reference location. In various examples, this location-specific processing includes executing automated tasks that issue localized notifications to the patient or other recipients and/or adapting the user interface of the medical device to increase its relevance to the patient while the patient is within range of the reference location, and/or adapting the user interface of the medical device to increase its relevance to persons associated with the reference location. For example, the localized notifications may include reminders to maintain serviceable components of the medical device, while any materials needed to do so are readily at hand, download and/or apply software upgrades, upload certain medical device data or patient data to a base station, smartphone, or remote computer system, download and/or apply device configuration parameters, treatment data, monitoring and/or treatment thresholds and parameters, and new or updated instructions to the patient.

In some examples, the location-specific processing includes execution of one or more tasks, other than notification tasks, based on the location of the device. For example, these other tasks may include downloading and/or applying software upgrades, uploading medical device and/or patient data to a base station, mobile device, smartphone, or a remote computer system, changing device configuration parameters, updating or downloading new treatment data, changing or adding new monitoring and/or treatment thresholds and parameters, or instructions to the patient. In some cases, the information to be downloaded to and applied on the medical device may be available on a base station or another device, such as a mobile phone, within a reference location. As such, on detecting proximity to such base station or other device, the medical device can perform preconfigured tasks in response to the detected proximity. Further, one or more adaptations of the user interface as described above may include removing some elements of the user interface, changing existing elements, and exposing new elements to, for example, the patient or professional medical personnel when the medical device is in a location associated with the personnel.

Examples of the methods and systems 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 systems 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, components, 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, components, elements or acts of the systems and methods herein referred to in the singular may also embrace examples including a plurality, and any references in plural to any example, component, element or act herein may also embrace examples including only a singularity. 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. In addition, 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.

Example Medical Devices

A medical device as described herein is configured to monitor a patient and, in some implementations, provides treatment to the patient based on the monitoring. For instance, in some examples, the medical device monitors one or more physiological parameters of the patient. More particularly, the medical device can be configured to monitor data digitized from one or more physiological signals acquired from a patient (e.g., electrocardiograph (ECG) data), heart beats, respiration, breath sounds, tissue fluids, lung fluids, lung sounds, chest movements, and/or cardiopulmonary anomalies, detect anomalies present in the digitized data, and determine whether the detected anomalies impair cardiac or pulmonary function. In various implementations, the medical device can be configured to monitor other patient parameters including but not limited to blood pressure, glucose levels, weight, blood oxygen, etc.

External medical devices as described herein may be in contrasted with internal devices, such as implantable medical devices. For example, the external medical devices as described herein may be capable of continuous, substantially continuous, long-term and/or extended monitoring and/or treatment of a patient or wear by, or attachment or connection to the patient for a period of time. For instance, external medical devices as described herein may be capable of being used or worn by, or attached or connected to a patient, without substantial interruption for a predetermined period of time. In some examples, such external medical devices may be capable of being used or worn by, or attached or connected to a patient for example, up to hours or beyond (e.g., weeks, months, or even years). In some examples, the period of time may be at least 24 hours. In some examples, the period of time may be at least one week. In some examples, the period of time may be at least two weeks. In some examples, the period of time may be at least one month. A medical professional may determine an appropriate period of time based on a number of factors including the patient's underlying condition, the data being monitored, and availability of alternative therapy and/or monitoring methods among others.

Some medical devices as disclosed herein can be used as cardiac monitors in certain cardiac monitoring applications, such as holter monitoring, mobile cardiac telemetry (MCT) and/or continuous event monitoring (CEM) applications. In some instances, the medical devices may carry out monitoring in periodic or aperiodic time intervals or times. For example, the monitoring during intervals or times can be triggered by a user action or another event. The one or more durations between the periodic or aperiodic intervals or times can be user-configurable.

Example Wearable Medical Device

In some implementations, an external ambulatory medical device can be configured as a wearable defibrillator, such as the LifeVest® wearable defibrillator available from ZOLL® Medical Corporation of Chelmsford, MA FIG. 1 illustrates an example medical device 100 that is external, ambulatory, and wearable by the patient 102. As shown, the medical device 100 includes a garment 110, a plurality of sensing electrodes 112, a plurality of therapy electrodes 114, a medical device controller 120, a connection pod 130, a patient interface pod 140, and a belt 150. The plurality of sensing electrodes 112 can be disposed at various positions about the patient's body. As shown, the sensing electrodes 112 are electrically coupled to the medical device controller 120 through the connection pod 130. In some implementations, some of the components of the wearable medical device 100 are affixed to the garment 110 that can be worn on the patient's torso. For example, as shown in FIG. 1, the controller 120, at least some of the sensing electrodes 112, and, optionally, one or more therapy electrodes 114 can be mounted on a belt 150 worn by the patient. The sensing electrodes 112 and the connection pod 130 can be assembled or integrated into the garment 110 as shown. The sensing electrodes 112 are configured to monitor the cardiac function of the patient (e.g., by monitoring one or more cardiac signals of the patient). The plurality of therapy electrodes 114 can be electrically coupled to the controller 120 through the connection pod 130. The therapy electrodes 114 are configured to deliver one or more therapeutic defibrillating shocks to the body of the patient if the medical device 100 determines that such treatment is warranted. The connection pod 130 may include electronic circuitry and one or more sensors (e.g., a motion sensor, an accelerometer, etc.) that are configured to monitor patient activity.

The wearable medical device 100 may include the optional patient interface pod 140 that is coupled to the patient interface of the medical device controller 120. For example, the patient interface pod 140 may include patient interface elements such as a speaker, a microphone responsive to patient input, a display, an interactive touch screen responsive to patient input, and/or physical buttons for input. In certain implementations, the patient interface pod 140 may include some or all of the location aware components described herein (see, e.g., FIG. 4). In some of these implementations, these location aware components may utilize information descriptive of the location of the medical device 100. This location information may be derived from components included in the patient interface pod 140, such as global positioning system (GPS) devices, inertial measurement units (e.g., accelerometers, gyroscopes, etc.), and other data acquisition devices.

In some implementations, in addition to or instead of display 220, the patient may interact with the medical device 100 (e.g., receive patient input or provide information to the patient as described herein) via the patient interface pod 140. In an example, the controller 120 may be configured to detect that if the patient interface pod 140 is operatively coupled to the controller 120, the controller 120 may then disable the patient interface elements of the controller 120 (e.g., display 220) and instead communicate via the patient interface pod 140. In certain examples, the patient interface pod 140 and the user elements of controller 120 may serve as redundant input via which the patient may interact with the device 120. The patient interface pod 140 may be wirelessly coupled with the controller 120. The patient interface pod 140 may take other forms and include additional functionality. For instance, the patient interface pod 140 may be implemented on a smartphone, tablet, or other mobile device carried by the patient. In another example, the patient interface pod 140 may be worn as a watch about the wrist of the patient, or as a band about an upper arm of the patient. In some implementations, the controller 120 may communicate certain alerts and information and/or be responsive to patient input via both the patient interface elements included in the controller 120 and the patient interface pod 140. The patient and/or caregiver can interact with the touch display 220 or the patient interface pod 140 to control the medical device 100.

Example Medical Device Controller

FIGS. 2A and 2B illustrate an example of the controller 120. The controller 120 includes a port 202, a speaker 204, response buttons 210, a battery 212, a display 220, and a housing 206 in which one or more location aware components are disposed. These location aware components are configured to execute location-specific processing and are described further below with reference to FIG. 4. The display 220 can be implemented as a touch screen interactive user interface. Accordingly, the patient and/or a caregiver can interact with the display 220 to control the medical device 100. In some examples, the controller 120 is configured to communicate audio information to the patient, the caregiver, and/or a bystander via the speaker 124 including audible alarms to alert the patient and bystanders to the patient's medical condition. The controller 120 can include the response buttons 210 for the patient to press to indicate that the patient is conscious, thereby instructing the controller 120 to withhold the delivery of therapeutic defibrillating shocks. If the patient does not respond to an instruction, the medical device 100 may determine that the patient is unconscious and proceed with a treatment sequence, culminating in the delivery of one or more defibrillating shocks to the body of the patient. The port 202 is configured to removably connect sensing devices (e.g., sensing electrodes 112) and/or therapeutic devices (e.g., therapy electrodes 114) to the controller 120. In some examples, the sensing electrodes 112 include ECG sensing electrodes. The controller 120 may be powered by the rechargeable battery 212.

In some examples, the controller 120 may be in communication with a base station 300 as shown in FIG. 3. The base station 300 includes an antenna 302, a battery charging bay 304, one or more buttons 306, a speaker 308, a display 310, and one or more communication interfaces 312, 314, and 316. The base station 300 communicates with the controller 120 via, for example, a wireless communication connection 318 (e.g., BLUETOOTH, Wireless USB, ZigBee, and Wireless Ethernet). The information received by the base station 300 may be communicated over a wired or wireless communication network shortly after it is received by the base station 300, or alternatively, may be stored in a memory of the base station 300 and communicated over the network at a later time. For example, information relating to the patient's medical condition and/or device status information over a period of time may be communicated by the base station 300 to a remote server through which a caregiver, such as a physician, may remotely monitor the patient's medical condition.

FIG. 4 shows a schematic of an example of the controller 120 of FIGS. 1, 2A, 2B and 3. The controller 120 includes at least one processor 418, location adaptation component 410, a proximity monitoring component 414, a location-specific processing component 416, a sensor interface 412, an optional therapy delivery interface 402, data storage 404 (which may include location data store 430), an optional network interface 406, a user interface 408, and the battery 212. The sensor interface 412 may be coupled to any one or combination of sensors to receive information indicative of patient parameters. For example, the sensor interface 412 may be coupled to one or more sensing devices including, for example, sensing electrodes 428. The therapy delivery interface 402 (if included) may be coupled to one or more electrodes that provide therapy to the patient including, for example, one or more defibrillation electrodes 420, pacing electrodes 422, and/or TENS electrodes 424. In some examples, the sensing electrodes 428 are included in the sensing electrode 112 and the defibrillation electrode 420, the pacing electrode 422, and/or the TENS electrode 424 are included in the therapy electrodes 114. The sensor interface 412 and the therapy delivery interface 402 may implement a variety of coupling and communication techniques for facilitating the exchange of data between the sensors and/or therapy delivery devices and the controller 120. In some examples, the network interface 406 is configured to operate in a power conservation mode.

In some examples, the network interface 406 can facilitate the communication of information between the controller 120 and one or more other devices or entities over a communications network. For example, the network interface 406 may be configured to communicate with a server (e.g., a remote server) where a caregiver can access information related to the patient or with a base station (e.g., the base station 300) that is associated (e.g., paired) with the controller 120.

In some examples, the controller 120 includes a cardiac event detector 426 to monitor the cardiac activity of the patient and identify cardiac events experienced by the patient based on received cardiac signals.

In some examples, the user interface 408 includes one or more physical interface devices such as input devices, output devices, and combination input/output devices and a software stack configured to drive operation of the devices. These user interface elements may render visual, audio, and/or tactile content, including content relating to location-specific processing. For instance, in some examples, the user interface 408 includes a microphone, the speaker 204, the display 220, and the response buttons 210. Thus the user interface 408 may receive input or provide output, thereby enabling a user to interact with the controller 120.

In some implementations, the processor 418 includes one or more processors that each can perform a series of instructions that result in manipulated data and/or control the operation of the other components of the controller 120. In some implementations, when executing a specific software process as provided herein (e.g., FIGS. 5-8), the processor 418 is configured to make specific logic-based determinations based on input data received, and further capable of providing one or more outputs that can be used to control or otherwise inform subsequent processing to be carried out by the processor 418 and/or other processors or circuitry with which processor 418 is communicatively coupled. Thus, the processor 418 reacts to specific input stimulus in a specific way and generates a corresponding output based on that input stimulus. In this sense, the structure of processor 418 according to one example is defined by the flow charts shown in FIGS. 5-8. In some example cases, the processor 418 proceeds through a sequence of logical transitions in which various internal register states and/or other bit cell states internal or external to the processor 418 may be set to logic high or logic low. This specific sequence of logic transitions is determined by the state of electrical input signals to the processor 418 and a special-purpose structure is effectively assumed by the processor 418 when executing each software instruction of the software process shown in FIGS. 5-8. Specifically, those instructions anticipate the various stimuli to be received and change the implicated memory states accordingly. In this way, the processor 418 may generate and store or otherwise provide useful output signals. It is appreciated that the processor 418, during execution of a software process is capable of processing specific input signals and rendering specific output signals based on the one or more logic operations performed during execution of each software instruction. As referred to herein, the processor 418 is configured to execute a function where software is stored in a data store coupled to the processor 418 that is configured to cause the processor 418 to proceed through a sequence of various logic decisions that result in the function being executed.

In various implementations, the controller 120 implements an embedded operating system that supplies file system and networking support. In one example, the controller 120 includes software features that provide relational database functionality, touch screen display drivers, audio generation, BLUETOOTH wireless networking, BLUETOOTH Low Energy (BLE) Beacon technology, networking security and firewalling, a lightweight web server and data encryption services.

Example Location Aware Components

The proximity monitoring component 414 illustrated in FIG. 4 is configured to monitor for and detect occurrences of the controller 120 being within one or more predefined ranges of one or more reference locations. When executing according to any of various configurations, the proximity monitoring component 414 detects such occurrences by executing any of a variety of proximity detection processes. These processes may, for example, detect proximity with reference to a coordinate system (e.g., a geographic coordinate system) and/or detect proximity with reference to one or more range identifiers (e.g., identifiers that indicate the controller 120 is within one or more predefined ranges of a reference location). For example, the reference location may be based on one or more predetermined geographic coordinates (e.g., GPS coordinates of a certain physical location) or a location of a base station device (e.g., base station 300). In implementations involving base station locations, typically base stations may be associated with a physical location (e.g., a patient's home, place of work, or other location). In yet some examples, the reference location may be based on a mobile device such as a patient, caregiver or other predetermined person's smartphone or tablet. As such, one or more proximity detection processes may include detecting proximity to one or more such devices.

For instance, when executing according to its configuration in some examples, the proximity monitoring component 414 detects proximity by determining a geographic location of the controller 120, calculating a distance from the geographic location to a reference location, and comparing the distance to one or more ranges defining various proximities. The proximity monitoring component 414 may utilize a variety of technologies and techniques to determine the geographic location of the controller 120. Examples of these technologies and techniques include GPS devices, dead reckoning processes, signal strength calculations, cellular network services, WiFi network services, BLUETOOTH network services, BLE beacon technologies, radio frequency identification (RFID) devices, indoor beacons, triangulation techniques, and indoor positioning systems. In some examples, the proximity monitoring component 414 is configured to limit execution of proximity monitoring processes when the battery 212 has a remaining runtime that is less than a configurable threshold value. For example, such a threshold may be set by default to 20% of remaining battery charge capacity. Additionally, in some examples, the proximity monitoring component 414 may switch the network interface 406 into its power conservation mode when the proximity monitoring component is not actively executing a proximity monitoring process. Particular example applications of these technologies and techniques are described further below with reference to FIGS. 5, 6, 11, and 12.

In some examples, the proximity monitoring component 414 is configured to detect proximity by detecting one or more range identifiers without reference to a coordinate system. These range identifiers may include identifiers of networks available to the controller 120, identifiers of other devices available to the controller 120 via a network, identifiers of other devices detectable by the proximity monitoring component 414 (e.g., RFID tags), signal strength information, express range identifiers (e.g., as defined by the IBEACON standard as published by APPLE Inc. BLE beacon technologies, among others), visual fiduciaries, audio signals, motion patterns (e.g., as generated by a commute via car, bus or train, or ocean waves on a boat), etc. Thus, when executing according to its configuration, the proximity monitoring component 414 may interoperate with other components of the controller 120 to detect range identifiers. Examples of these other components include the network interface 406 (e.g., to detect network and device identifiers), the user interface 406 (e.g., to detect visual or audio identifiers), and the sensor interface 412 (e.g., to detect speed or motion identifiers). Particular examples of processes that the proximity monitoring component 414 is configured to execute to detect range identifiers are described further below with reference to FIGS. 5, 7, 11, and 12.

The location adaptation component 410 illustrated in FIG. 4 is configured to, in some examples, adapt operation of a medical device including the controller 120 in response to the controller being within a predefined range of a reference location. When executing according to its configuration, the location adaptation component 410 adapts the operation of the medical device by altering the information and/or options displayed via the user interface 408. For instance, the location adaptation component 410 may omit, add, and/or move user interface elements (e.g., menu selections, text boxes, graphs, etc.) in various screens presented via the user interface 408 based on the range of the controller 120 from one or more reference locations. Particular examples of processes that the location adaptation component 410 is configured to execute to adapt operations of a medical device are described further below with reference to FIGS. 5, 10, 11, and 12. One example screen adapted by the location adaptation component 410 is described further below with reference to FIG. 10.

The location-specific processing component 416 illustrated in FIG. 4 is configured to execute location-specific tasks such as issuing specialized, location-oriented notifications in response to the controller being within a predefined range of a reference location. The location-specific processing component 416 may be configured to issue these notifications to a patient, a caregiver near the patient, such as a family member, a designated person, or a loved one, and/or another such caregiver located at a remote location. For example, proximity-based notifications may be issued to both the patient and another designated person other than the patient. In some implementations, such notifications may be issued to the patient and a designated person other than the patient at substantially the same time. In some cases, the notifications may be issued with a preconfigured, programmable time delay, such that first the patient is notified, and if the patient does not respond to the notification (e.g., by acknowledging the notification), a designated person other than the patient is notified after expiration of the time delay. Communication channels for these notifications may include the user interface 408, the patient interface pod 140, a user interface of another medical device, a user interface of a programmable device (e.g., a smart phone, tablet computer, personal computer, etc.), and the like.

The content of the notifications may vary broadly between examples. For instance, in some examples, the content includes a prompt for the patient to download and apply one or more of the software patches, updates, device configuration information, new or updated patient parameters, and/or threshold changes to underlying monitoring or treatment parameters. Alternatively or additionally, the content may include a notification to the patient of a device task to be performed automatically. The content of the notifications may include a reminder for a patient to service a component of a medical device (while the patient is at a location where such servicing is available), a reminder for a patient to take medication, a reminder for a patient to review training materials, a request for a patient to perform a diagnostic or remedial physical activity, etc. In some examples, the content may include a reminder to the patient the charge a rechargeable battery when the device detects proximity to a base station equipped with a battery charger. For example, if the battery charge level is below a threshold and the patient is proximate a base station with a battery charger, the device may alert the patient that the battery needs to be charged.

As noted below, the device may adaptively learn about the patient's movements with respect to proximity to the base station over time. In adaptively providing notifications based on proximity, the device may also take into account the time of the day, the priority of the notification, the device status and, patient condition in determining when and whether to provide proximity-based notifications. As such, the device may adapt its notifications to make them more relevant to the patient in accordance with the patient's current activity. For example, if the patient is sleeping, or taking a nap, the device may suppress some or all such notifications until the patient is awake and still proximate to the base station.

In some examples, the location-specific processing component 416 is configured to execute other location-specific tasks automatically in response to detecting that the medical device controller 120 is within a predefined proximity of one or more reference locations. For instance, the location-specific processing component 416 may be configured to, when within range of a reference location, automatically calculate certain trends, metrics, and/or statistics based on the sensed physiological and/or device data, perform a data fetch operation to download one or more software updates (e.g., upgrades or patches), device configuration information, new or updated patient parameters, and/or download and apply threshold and/or other changes to underlying monitoring or treatment parameters.

For instance, within a cardiac monitor or an ambulatory external defibrillator (e.g., a wearable defibrillator), the location-specific processing component 416 can be configured to perform calculations of arrhythmia burdens and immediately transmit such information to a remote server. When executing according to this configuration, the location-specific processing component 416 monitors the signal quality and if the signal quality deteriorates or a disconnection of an electrode occurs, the location-specific processing component 416 instead records an onset and an exit event corresponding to the portion of the recording of interest and transmits the information at a later time. Other types of trends, metrics, and/or statistics may be calculated and transmitted to a remote server. For example, the location-specific processing component 416 may calculate a patient's heart rate during a predetermined period and supplement such heart rate information with additional information regarding a range of the patient's heart rate during the period, the maximum rate detected, the lowest rate detected, and an average rate. The location-specific processing component 416 may be configured to calculate atrial fibrillation (AF) metrics, including total AF burden, a number of AF episodes, and a range of the AF, including maximum, minimum, and average information. The location-specific processing component 416 may be configured to calculate a sinus rhythm metrics, including a range for sinus rhythm rate, including maximum, minimum, and average information, bradycardia burden and/or duration, bradycardia episode count, and extreme values corresponding to bradycardia episodes (e.g., longest and slowest episodes). The location-specific processing component 416 may be configured to calculate metrics relating to pauses and/or blocks, including a corresponding total burden and/or duration, missed beats (e.g., a count of such missed beats), asystole, etc. The location-specific processing component 416 may be configured to calculate supraventricular tachycardia metrics, including total burden and/or duration, premature atrial contraction (PAC) counts.

In one example, a physiological patient monitor (e.g., a cardiac monitor) or an external ambulatory treatment device (e.g., a wearable defibrillator or pacing device) including the location-specific processing component 416 may exchange information relating to cardiac monitoring and/or treatment thresholds with a remote server based on proximity to a reference location. In general, such information can include patient information, device status information, and other operational data. A cardiac monitor or a defibrillator including the location-specific processing component 416 may exchange patient information such as ECG information, such as atrial fibrillation (AF) threshold values, changes in QRS (e.g.: width, height, or other such parameter), change in (s-t) t-wave, ventricular tachycardia (VT) thresholds, ventricular fibrillation (VF) thresholds, tachycardia (e.g., above a specified threshold), bradycardia (e.g., heart rate falling below a specified threshold, significant pauses (e.g., triggered by a predetermined threshold), and pre-ventricular contractions (PVCs), e.g., when a count threshold is exceeded. Patient information may include patient reported symptom information, e.g., when the patient reports (e.g., by activation of a user interface element) dizziness, palpitations, chest pain, etc. Other patient information may include change in patient fluid levels (e.g., based on an radio-frequency wave sensor), respiration information, accelerometer-detected patient falls, walk test activation, thresholds, parameters and associated data, cardiac sounds or measures such as an S3, S4, or prolonged electromechanical activation times (EMAT). The data may be configured to be exchanged on a continuous, periodic, or aperiodic basis.

In some examples, a defibrillator including the location-specific processing component 416 may exchange information relating to treatment thresholds, such as shock energy levels, number of pulses, duration of pulses, etc. with a remote server. For example, the server receiving such information may be configured to perform analysis on the returned data, including study data trends, and provide one or more reporting functions to predetermined end-users and/or devices. For example, reports can be generated in specified intervals (e.g., weekly, daily, or hourly). Reports may also be generated based on onset of certain events (e.g., cardiac events described above).

In some examples, the location-specific processing component 416 may execute tasks that configure components of the medical device controller 120. For example, when a medical device including the location-specific processing component 416 comes within range of a predetermined reference location, the location-specific processing component 416 may download an updated configuration file. This download may involve an HTTP GET operation to get settings and action files from a specified location on the remote server (e.g., /settings/downloads/configuration/). In some examples, one or more redirection rules can be implemented at the remote server to properly direct the query to an appropriate location within the server.

The updated configuration file may include configuration information such as, a unique device record identifier, a patient identifier, configuration file path name, initial device settings and configurations, and monitoring and/or treatment threshold values. In cardiac monitoring devices, the configuration file can include event reporting settings, such as, creation of event report files, frequency of event recording and reporting, thresholds for triggering certain recordings, and recording of one or more specified parameters.

Additional examples of processes that the location-specific processing component 416 is configured to execute are described further below with reference to FIGS. 5, 8, 9, 11, and 12.

Example Location Aware Processes

As described above, some examples execute one or more location aware processes. FIG. 5 illustrates one of these processes, a proximity monitoring process 500. As shown, the proximity monitoring process 500 is executed by a proximity monitoring component (e.g., the proximity monitoring component 414) of a controller (e.g., the controller 120) of a medical device (e.g., the medical device 100).

At a high level, proximity monitoring process 500 involves stepping through a predetermined plurality of reference locations stored in a data structure in, for example, location data store 430. In some examples, the plurality of reference locations may be stored at a remote location (e.g., a server accessible via the network interface 406) and made available to the proximity monitoring process 500. For example, the plurality of reference locations may be preprogrammed into the controller 120 or a remote server database. In some implementations, the controller 120 may be configured to allow a patient or other non-patient user (e.g., a patient service representative) to add one or more new reference locations to the location data store 430 for processing in accordance with the examples below.

For each reference location of the plurality of reference locations, the process 500 checks to see if the location of the controller 120 is within range of the reference location. For example, the process 500 may make use of a distance calculation of the current location of the controller 120 from the reference location (see FIG. 6) to determine whether the controller 120 is in range of a reference location. In addition or alternatively, the process 500 may detect one or more wireless network identifiers, for example, in order to determine whether the controller 120 is in range of a reference location.

The proximity monitoring process 500 starts in act 502, where the proximity monitoring component identifies data descriptive of a reference location of a plurality of reference locations stored in the location data store 430 (e.g., in a first pass of process 500, the process 500 may begin with the first reference location in a list of reference locations stored in the store 430). In one implementation, the monitoring process 500 may automatically detect a reference location that the controller 120 has not previously encountered and initiate a process whereby the controller 120 can prompt the patient or other non-patient user to store the reference location and associate it with a proximity detection process for future use. The controller 120 may determine a previously unencountered location based on analyzing a patient's movements and location history over a period of time. For instance, if the controller 120 detects that a patient is often at a particular location (e.g., a relative's home) that is not in the location data store 430, the controller 120 may prompt the patient or other non-patient user to store the reference location.

As noted, the data descriptive of the plurality of reference locations may reside in one or more records in a data structure stored in a location data store (e.g., the location data store 430). In some examples, each record of this data structure includes a field storing a unique identifier of a reference location. In some of these examples, the data structure includes a plurality of such records, each record being associated with a distinct reference location. In the data structure, the unique identifier for the reference location may be associated with a user-configurable name for the reference location (e.g., a street address, name of the location, etc.) and GPS coordinates for the location.

In act 504, the proximity monitoring component executes a proximity detection process associated with a reference location of the plurality of reference locations in the data store 430. In some examples, each of the records of the data structure described in act 502 includes an identifier of a proximity detection process to be executed when attempting to determine whether the controller is within a predefined range of the reference location associated with the record. In these examples, within the act 504, the proximity monitoring component accesses this identifier within the record associated with the current reference location and executes a proximity detection process identified thereby.

In some implementations, a plurality of reference locations may be associated with a proximity detection process. For instance, a single proximity detection process may execute by periodically or aperiodically stepping through each reference location in the plurality of reference locations and checking to see if the reference location is in range of the current location of the controller 120. For example, the time period or the times at which the process is executed may be controlled through a user interface panel on the controller 120.

As described above, the proximity monitoring component may execute any of a variety of proximity detection processes to determine whether the controller is within a predefined range of (e.g., is proximal to) a reference location. In some examples, an identifier of a proximity detection process to be executed for the reference location may be stored in a field of the record of the data structure associated with the reference location. In these examples, the proximity monitoring component may identify the proximity detection process to be executed by accessing this field.

FIG. 6 illustrates one example of a proximity detection process 600 that may be executed by the proximity monitoring component in the act 504. As shown in FIG. 6, the proximity detection process 600 begins with act 602 where the proximity monitoring component determines the location of the controller within a coordinate system, such as a geographic coordinate system.

In the act 602, the proximity monitoring component determines the location of the controller within the coordinate system using any of a variety of technologies and techniques. For instance, according to one example, the proximity monitoring component includes a GPS receiver that provides a fix for the location of the controller. In another example, the proximity monitoring component includes an accelerometer and combines a previously recorded location (e.g. a GPS fix) with movement information generated from the accelerometer to determine the location. In another example, the proximity monitoring component interoperates with a network interface (e.g., the network interface 406) to calculate one or more strengths of one or more signals received from one or more network sources (e.g., cellular towers, network access points, BLUETOOTH transmitters, BLE beacons, WiFi access points, RFID tags, other medical devices, etc.) that are associated with one or more recorded locations and determines the location of the controller based on the one or more recorded locations and the one or more calculated signal strengths. In another example, the proximity monitoring component interoperates with a microphone included in the user interface 408 to scan for one or more audio signals that are associated with one or more recorded locations and determines the location of the controller based on the one or more recorded locations and the amplitude of the one or more audio signals. In another example, the proximity monitoring component interoperates with a 2D and/or 3D camera included in the user interface 408 to scan for one or more visual fiduciaries that are associated with one or more recorded locations and determines the location of the controller based on the one or more recorded locations and a distance to the visual fiduciaries. The proximity monitoring component may determine the location of the controller within the coordinate system other of technologies and techniques and the examples disclosed herein are not limited to a particular technology or technique.

In act 604, the proximity monitoring component calculates a distance between the current reference location and the location of the controller. In act 606, the proximity monitoring component determines whether the calculated distance is within a predefined range of distance values. If so, the proximity monitoring component executes act 608. If the proximity monitoring component determines that the calculated distance is not within the predefined range, the proximity monitoring component executes act 610.

In the act 608, the proximity monitoring component stores an indication that the controller is within the predefined range of the current reference location. In the act 610, the proximity monitoring component stores an indication that the controller is not within the predefined range of the current reference location. After executing either the act 608 or the act 610, the proximity monitoring component terminates the proximity detection process 600 and returns to the proximity monitoring process 500.

Processes in accord with the proximity detection process 600 enable a medical device to determine whether the medical device is within a predefined range (e.g., 100 feet) to a reference location, thereby enabling the medical device to execute (or not execute) subsequent processes that are relevant to the reference location and predefined range.

FIG. 7 illustrates another example of a proximity detection process 700 that may be executed by the proximity monitoring component in the act 504. As shown in FIG. 7, the proximity detection process 700 begins with act 702 where the proximity monitoring component scans for one or more range identifiers associated with a reference location of a plurality of reference locations. These one or more range identifiers may take a variety of forms and may be stored in one or more fields of the record of the data structure associated with the reference location. In some examples, the proximity monitoring component may identify the one or more range identifiers by accessing the one or more fields. In one example, the proximity monitoring component interoperates with the network interface 406 to scan for one or more network identifiers (e.g. service set identifiers (SSIDs), etc.) identified as one or more range identifiers for the reference location. In another example, the proximity monitoring component interoperates with the network interface 406 to scan for one or more network device identifiers (e.g. transport control protocol/internet protocol addresses, etc.) identified as one or more range identifiers for the reference location. In another example, the proximity monitoring component includes an RFID reader and scans for one or more RFID tags identified as one or more range identifiers for the reference location. In another example, the proximity monitoring component interfaces with a 2D/3D camera included in the user interface 408 to scan for one or more visual fiduciaries identified as one or more range identifiers for the reference location. In another example, the proximity monitoring component interfaces with a microphone included in the user interface 408 to scan for one or more audio signals identified as one or more range identifiers for the reference location. In another example, the proximity monitoring component includes an accelerometer and scans for one or more motion patterns identified as one or more range identifiers for the reference location. This motion pattern may be generated by (and thus follow) a commute or trip via car, bus, train, airplane, or boat. The proximity monitoring component may scan for other range identifiers and the examples disclosed herein are not limited to a particular range identifier or set of range identifiers.

In act 704, the proximity monitoring component determines whether any range identifier scanned for in the act 702 was detected. If so, the proximity monitoring component executes act 608. If the proximity monitoring component determines that no range identifier scanned for in the act 702 was detected, the proximity monitoring component executes act 610.

After executing either the act 608 or the act 610, the proximity monitoring component terminates the proximity detection process 700 and returns to the proximity monitoring process 500.

Processes in accord with the proximity detection processes 600 and 700 enable a medical device to determine whether the medical device is within a predefined range (e.g., 100 feet) of a reference location, thereby enabling the medical device to execute (or not execute) subsequent processes that are relevant to the reference location and predefined range.

Returning to FIG. 5, in act 506, the proximity monitoring component determines whether the medical device is within a predefined range of a reference location of a plurality of reference locations. In at least one example, the proximity monitoring component makes this determination by accessing an indicator stored by the proximity monitoring component during execution of either the act 608 or the act 610. Where the proximity monitoring component determines that the medical device is within the predefined range of a reference location, the proximity monitoring component executes act 510. Where the proximity monitoring component determines that the medical device is not within the predefined range of a reference location, the proximity monitoring component executes act 508.

In the act 510, the proximity monitoring component executes one or more location-specific processes that are associated with the predefined range identified in the act 506. In some examples, one or more identifiers of the one or more location-specific processes executed for the current reference location and/or predefined range are stored in one or more fields of the record of the data structure associated with each of the plurality of reference locations. In these examples, the proximity monitoring component may identify the one or more location-specific processes to be executed by accessing the one or more fields.

In some examples of the act 510, the proximity monitoring component interoperates with a location adaption component (e.g., the location adaptation component 410) and/or a location-specific processing component (e.g., the location-specific processing component 416) to execute the one or more location-specific processes. As such, the location-specific processing executed may include tasks that issue localized notifications to the patient and/or other recipients and/or other tasks. The location-specific processing may also adapt the user interface of the medical device to increase its relevance to persons associated with the predefined range.

For instance, in some examples of the act 510, the proximity monitoring component initiates execution of the location-specific processing component. In these examples, the location-specific processing component executes tasks that generate and issue one or more notifications associated with a particular reference location of a plurality of reference locations. These notifications may include, among other such notifications, reminders to service the medical device (e.g., change a battery, replace an electrode, etc.) when the patient is within range of a battery charger or area having additional/alternative electrodes, or reminders for the patient to take medication, instructions for the patient to perform a test (e.g., a six minute walk test), reminders to download or install an available software update, reminders to download or apply available changes to one or more operating parameters (e.g., monitoring, treatment or other patient parameters), reminders to download or apply available changes to one or more device configuration parameters, and/or instructions for the patient to complete a training program (e.g., when the patient is at home). In certain implementations, the device may first determine that the next opportunity for such task(s) may not be for a period of time (e.g., the patient is about to leave home for work) and issue the reminders while the patient is still at home. For example, the device may base its decision-making process on one or more template schedules as described in further detail below. Alternatively or in addition, the device may take into account a criticality indication associated with the one or more reminders (e.g., an indication that the proposed task(s) is important or critical and needs to be performed as soon as possible) in determining whether to issue the reminder while the device is within range of a reference location. In some instances, a next reference location that the patient is expected to be within range may not be equipped with the necessary features for performing certain task(s). As described below, the device may take this into account in determining whether and when to issue notifications to perform the task(s). The location-specific processing component may issue these notifications to a variety of recipients including, for example, programmable devices associated with the patient, bystanders, caregivers near the patient, and caregivers remote from the patient. As such, the location-specific processing component may issue notifications using a variety of channels including the user interface and the network interface.

In another example of act 510, location-specific processing may include one or more automatically initiated tasks performed by the device upon detecting proximity to a reference location. For example, such tasks may include automatic download/upload or updates of data or software on determining proximity to a base station or other reference location. In certain implementations, the device may first determine that the next opportunity for such task(s) may not be for a period of time (e.g., the patient is about to leave home for work) and enable the task(s) while the patient is still at home. For example, the device may base its decision making process on one or more template schedules as described in further detail below. Alternatively or in addition, the device take into account a criticality indication associated with the one or more task(s) (e.g., an indication that the proposed task(s) is important or critical and needs to be performed as soon as possible) in determining whether to perform the task which the device is within range of a reference location. In some instances, a next reference location that the patient is expected to be within range may not be equipped with the necessary features for performing certain task(s). As described below, the device may take this into account in determining whether and when to perform the task(s). Other automated tasks may include automatically initiating instructions for the patient to perform a test (e.g., a six minute walk test), downloading or installing available software updates (e.g., upgrades or patches), downloading or applying available changes to one or more operating parameters (e.g., monitoring, treatment or other patient parameters), downloading or applying available changes to one or more device configuration parameters, and/or automatically initiating a training program for the patient to complete, e.g., when the patient is at home.

FIG. 8 illustrates a location-specific process 800 executed by the location-specific processing component in accordance with some examples. Once the controller 120 has determined that the patient is within range of a particular reference location, the controller 120 may then assess whether there are any manual or automated tasks that need to be completed prior to the next time the patient returns to the same reference location or is at a different reference location that is equipped to allow for the manual or automated task to be performed at that location. For example, a manual task may be charging a battery pack of the device. If the controller 120 determines that the battery will need to be charged prior to the patient returning to within range of a battery charger, then the location-specific processing component may prompt the patient to charge the battery before leaving the reference location. As described above, automated tasks may include providing notifications or reminders with respect to manual tasks, or automatically initiating automated tasks, such as, providing instructions for the patient to perform a test (e.g., a six minute walk test), downloading or installing available software updates, upgrades, or patches, downloading or applying available changes to one or more operating parameters (e.g., monitoring, treatment or other patient parameters), downloading or applying available changes to one or more device configuration parameters, and/or automatically initiating a training program for the patient to complete, e.g., when the patient is at home.

In this regard, as shown, the location-specific process 800 begins with act 802 where the location-specific processing component identifies a task of a plurality of tasks associated with a reference location of a plurality of reference locations. Examples of tasks that may be identified include tasks to service the medical device (e.g., change or charge a battery, replace an electrode, etc.), to take medication, to perform a diagnostic test (e.g., a six minute walk test) or remedial physical activity, to complete a training program, etc. For instance, in one example, the task is to service a serviceable component of the medical device. This serviceable component may be, for example, a battery (e.g. the battery 212), a garment (e.g., the garment 110), or any other component of the medical device.

In act 804, the location-specific processing component identifies a time when the task is scheduled for completion. For example, where the task is to service a serviceable component, the location-specific processing component determines when service is next due for the serviceable component. In some examples, the location-specific processing component makes this determination by accessing a service schedule for the serviceable component. This service schedule may be stored in the location data store and may include information descriptive of one or more historical dates and times when the serviceable component was serviced. For example, where the unprocessed serviceable component is the garment, the service schedule may include a date and time that the garment was last laundered. Where the unprocessed serviceable component is the battery, the service schedule may include a date and time that the battery was last replaced. The service schedule may also include information descriptive of the next date and time that the serviceable component is due for service. For example, where the serviceable component is the garment, the service schedule may include a date and time that the garment is due to be laundered. Where the serviceable component is the battery, the service schedule may include a date and time that the battery's remaining runtime will expire and/or a date and time when the battery's remaining service life will expire.

In some examples, the location-specific processing component determines when service is next due by assessing the current state of the serviceable component. For example, where the serviceable component is the battery, the location-specific processing component may run a diagnostic of the battery to estimate a date and time that the battery's remaining runtime will expire and/or a date and time when the battery's remaining service life will expire.

In act 806, the location-specific processing component determines whether the task is due prior to the controller's arrival at a next reference location associated with facilities capable of completing the task. Where the task is to service a serviceable component, the location-specific processing component determines whether service is due for the serviceable component prior to the controller's arrival at a next service location (e.g., a reference location associated with equipment useful in servicing the serviceable component). In some examples, the location-specific processing component makes this determination by accessing a template schedule stored in the location data store. The template schedule may include a chronology of reference locations routinely visited by the patient. In some examples, the chronology specifies both arrival and departure dates and times for each visitation of reference location. The template schedule may be configured during an initial fitting of the medical device to the patient and periodically adjusted by artificial intelligence processes (e.g., the machine learning process described below with reference to FIG. 9).

In some examples of the act 806, the location-specific processing component determines whether service is due by projecting the date and time when service is next due for the serviceable component (as determined in the act 804) onto the template schedule and identifying any service locations beyond the current service location that are scheduled to be visited prior to the date and time when service is due. For example, where the serviceable component is the garment, the location-specific processing component may identify service locations (e.g., that are associated with laundering facilities) that the controller is projected to visit before laundering is next due. Where the unprocessed service component is the battery, the location-specific processing component may identify service locations (e.g., that are associated with battery chargers and replacement batteries) that the controller is projected to visit before battery charging and/or replacement is next due. If the location-specific processing component does not to identify at least one service location scheduled to be visited prior to the date and time service is due, the location-specific processing component executes act 810. If the location-specific processing component identifies one or more service locations to be visited prior to the date and time service is due, the location-specific processing component executes act 808.

In the act 810, the location-specific processing component executes the task by issuing a notification to a recipient requesting that the task be completed prior to departure from the current reference location and/or automatically executing the task. For example, where the task is to service a serviceable component, the location-specific processing component issues a notification to a recipient requesting that the serviceable component be serviced prior to departure from the current service location. The recipient of this notification may be a programmable device (e.g., the medical device or a smart phone) associated with the patient, a programmable device associated with a caregiver with the patient, or a programmable device associated a caregiver not with the patient. Where the task is to update configuration information of the medical device, the location-specific processing component updates the configuration information by downloading and applying updated configuration information.

In act 812, the location-specific processing component determines whether the task has been completed. In some examples, the location-specific processing component makes this determination in response to a reply to the notification issued in the act 810. This reply may be submitted by the recipient. For example, where the task is to service a serviceable component, the location-specific processing component determines whether the serviceable component has been serviced. In at least one example, the location-specific processing component makes this determination (or verifies a determination based on the reply) by assessing the status of the serviceable component. For example, where the serviceable component is the garment, the location-specific processing component determines the garment has been laundered by analyzing input indicating the same received via the user interface. Where the serviceable component is the battery, the location-specific processing component determines the battery has been recharged and/or replaced by running a diagnostic on the battery. If the location-specific processing component does not verify, within a configurable timeout period, that the serviceable component was serviced, the location-specific processing component executes act 810. If the location-specific processing component verifies, within the configurable timeout period, that the serviceable component was serviced, the location-specific processing component updates the historical dates and times and/or the next date and time stored in the service schedule for the serviceable component and executes act 808.

In the act 808, the location-specific processing component determines whether additional tasks associated with the reference location and/or a predefined range of the reference location exist. If so, the location-specific processing component executes the act 802. If no additional unprocessed tasks exist, the location-specific processing component terminates the location-specific process 800.

Processes in accord with the location-specific process 800 enable a medical device to remind users (e.g., patient, caregivers, etc.) of tasks to complete when the users are in a convenient location to do so.

As described above with reference to the act 806, some examples implement machine learning processes that adjust the template schedule based on the recorded movement of the controller and/or the patient. FIG. 9 illustrates a machine learning process 900 in accordance with these examples. As shown, the machine learning process 900 starts with act 902 where the location-specific processing component constructs feature vectors descriptive of sampled movement observations of the controller. These feature vectors may include elements descriptive of a location visited, a duration of the visitation, a start time of the visitation, an end time of the visitation, the day of the week of the visitation, etc.

In act 904, the location-specific processing component identifies clusters of feature vectors. Within the act 904, the location-specific processing component may execute any of a variety of clustering processes (e.g., k-means process) to identify clusters and centroids within the feature vectors generated in the act 902.

In act 906, the location-specific processing component calculates a distance (e.g., a cosine distance) between each of the centroids identified in the act 904 and visitation feature vectors descriptive of each visitation scheduled in the chronology of template schedule. Next, the location-specific processing component associates a centroid with each visitation feature vector (e.g., the centroid closest to the visitation feature vector). In this way, the location-specific processing component identifies centroids that are closest to the existing template schedule. Next, within the act 906, the location-specific processing component compares the distance between each centroid and its associated visitation feature vector and, where the distance transgresses a threshold, adjusts the visitation schedule in the chronology such that the visitation feature vector is brought within the threshold distance of its associated centroid. After executing the act 906, the location-specific processing component terminates the machine learning process 900.

Processes in accord with the machine learning process 900 enable a medical device to adaptively adjust a template schedule based on empirical data, thereby increasing the likelihood of the schedule being followed and the relevance of notifications based on thereon.

In another example of the act 510, the proximity monitoring component initiates execution of the location adaptation component. The location adaptation component, in turn, adapts the operation of the medical device. For instance, in one example, the location adaptation component alters the information and/or options displayed via the user interface. FIG. 10 illustrates the effect of an adaptation process executed by the location adaptation component.

As shown, FIG. 10 illustrates the location adaptation component 410, device home screen 1000, and device home screen 1002. The device home screen 1000 includes patient information 1004, which is descriptive of the patient being treated by the medical device, and a main menu button 1006. The device home screen 1002 includes the patient information 1004, the main menu button 1006, and a caregiver menu button 1008.

In some examples, the adaptation process executed by the location adaptation component 410 identifies one or more adaptations associated with the predefined range of the current reference location and adapt the user interface in accordance with the one or more identified adaptations. For example, with reference to FIG. 10, the adaptation process identifies the caregiver menu button 1008 as being associated with the predefined range of the current reference location in the location data store and adds the caregiver menu button to the device home screen 1000 to render the device home screen 1002. In response to a selection of the caregiver menu button, the controller may provide, for example, access to historical patient information, additional configuration options, and the like.

Processes in accord with the adaptation process illustrated in FIG. 10 enable a medical device to adapt operation of a user interface for one or more predefined ranges of one or more reference locations, thereby increasing the relevance of information presented by the user interface to persons located within the one or more predefined ranges.

Returning to FIG. 5, in the act 508, the proximity monitoring component records the reference location as having been processed and determines whether additional reference locations of a plurality of reference locations exist for processing. If so, the proximity monitoring component executes the act 502. If no additional reference locations exist, the proximity monitoring component terminates the proximity monitoring process 500.

Processes in accord with the proximity monitoring process 500 enable a medical device to monitor for changes of location and execute beneficial location-specific processing based on these location changes. The proximity monitoring process 500 may be executed periodically, aperiodically, or in response to events (e.g., startup of the controller, change in available WiFi network, etc.).

FIG. 11 illustrates another proximity monitoring process 1100. The proximity monitoring process 1100 may be executed by the proximity monitoring component. At a high level, the proximity monitoring process 1100 mimics the operation of the proximity monitoring process 500 and includes the acts 502, 504, 506, and 508. However, the proximity monitoring process 1100 is enhanced to provide conflict resolution between reference locations where the controller is within two or more predefined ranges of two or more reference locations.

In act 1102, the proximity monitoring component maintains a list of reference locations that are currently proximal to the medical device by adding the reference location identified in the act 506 to a list of reference locations maintained in the location data store. In act 1104, the proximity monitoring component determines whether two or more reference locations are stored in this list. If so, the proximity monitoring component executes a conflict resolution process to determine the location-specific processing to execute in act 1106. The particular conflict resolution process executed varies between examples and may include first come, first served, priority, mediation, etc. The first come, first served process resolves conflicts in favor of the reference location first detected by proximity monitoring component. The priority process requires that each reference location be associated with a priority and resolves conflicts in favor of the reference location associated with the highest priority. The mediation process resolves conflicts by allowing processing for some or all reference locations in the list. Other conflict resolution processes may be executed in the act 1104 and the examples disclosed herein are not limited to a particular conflict resolution process.

In the act 1106, the proximity monitoring component executes location-specific processing associated with one or more applicable predefined ranges of one or more reference locations favored by the conflict resolution process. In examples where a single reference location is favored over others, the act 1106 executes the tasks of the act 510. In examples where a two or more reference locations are favored, the act 1106 may execute location-specific processing associated with the two or more reference locations. For example, the location-specific processing component may issue notifications associated with two or more predefined ranges of two or more reference locations and/or the location adaptation component may execute adaptations associated with the two or more predefined ranges of the two or more reference locations.

Example Location Aware Processing System

In some examples, a medical device including location aware components (e.g., the proximity monitoring component 414, the location-specific processing component 416, and the location adaptation component 410) is incorporated into a location aware processing system. FIG. 12 illustrates a location aware processing system 1200 in accordance with these examples. As shown, the location aware processing system 1200 includes the medical device 100, the base station 300, predefined ranges 1202, 1204, 1206, 1208, and 1210, a remote server 1212, a programmable device 1214, a communication network 1216, and a local communication network 1220. In this example, the medical device 100 is associated with the patient 102 and the programmable device 1214 is associated with the user 1218 (e.g., a support technician, a caregiver, etc.). The programmable device 1214 may be, for example, a computer or a handheld device such as a tablet, smartphone, or mobile device, with access to the network 1216 and associated with the user 1218. Also, as shown, the predefined range 1202 is associated with a reference location of the network 1220, the predefined ranges 1204, 1206, and 1208 are associated with a reference location of the base station 300, and the predefined range 1210 is associated with a reference location of a geographic point 1222.

As shown in FIG. 12, the medical device 100 exchanges (e.g., transmits or receives) information with the programmable device 1214 and the remote server 1212 via the network 1216. This information may include localized notifications such as those described herein to enable the user 1218 or another user with access to the remote server 1212 to monitor the status and activities of the patient 102. The network 1216 may include any communication network through which programmable devices may exchange information. In some examples, the network 1216 supports wireless network and/or wired connections. For instance, the network 1216 may support any of various networking standards such as GSM, CMDA, USB, BLUETOOTH, CAN, ZigBee, Wireless Ethernet, and TCP/IP, among other networking standards.

In various examples, the programmable device 1214 is implemented using any of a variety of programmable devices (e.g., a device with data storage and at least one processor in data communication with the data storage). In some examples, the programmable device 1214 includes a plurality of interfaces, one or more processors, and a data storage device coupled to one another via a communication mechanism, such as a bus. In these examples, the programmable device 1214 also includes a battery to power the device and may include one or more antennas. The plurality of interfaces in the programmable device 1214 include a user interface and a network interface configured to communicate with the network 1216.

FIG. 12 also illustrates the patient 102, as the patient 102 goes about her daily routine. In one example, the patient 102 begins her day at home. Her home includes the base station 300, which is in wireless communication with the medical device 100 via the network connection 318. In this example, the network connection 318 supports the IBEACON standard and the predefined ranges 1204, 1206, and 1208 respectively correspond to IBEACON range identifiers of immediate (e.g., where the medical device 100 is within centimeters of the base station 300), near (e.g., where the medical device 100 is approximately between 10 centimeters and 10 meters away from the base station 300), and far (e.g., where the medical device 100 is approximately between 10 meters and 100 meters away from the base station 300). As such, the proximity monitoring component 414 of the medical device 100 discriminates between each of the predefined ranges 1204, 1206, 1208 using these range identifiers and determines within which predefined range the medical device 100 resides as the patient 102 moves about her home.

In this example, the proximity monitoring component 414 also interoperates with the location-specific processing component 416 to issue various notifications to the patient 102 that are relevant to the patient's current location with her home. For instance, where the proximity monitoring component 414 detects that the medical device has entered either of the predefined ranges 1204 or 1206, the proximity monitoring component 414 may notify the location-specific processing component 416. The location-specific processing component 416, in turn, may check the status of the battery 212 and issue a notification to the patient 102 to change the battery 212 if the runtime of the battery 212 is below a threshold value and if the charging bay 304 of the base station 300 currently holds a charged replacement battery. Further, where the proximity monitoring component 414 detects that the medical device has moved from the predefined range 1204 to the predefined range 1208 (indicating the patient 102 may be leaving her home), the proximity monitoring component 414 notifies the location-specific processing component 416. The location-specific processing component 416, in turn, executes the location-specific process 800, determines that the garment 110 will be in need of service prior to her return home (according to the template schedule), and issues a notification to the patient to launder the garment 110 prior to leaving her home.

Continuing the example illustrated in FIG. 12, the patient 102 next visits her office. Her office includes the local network 1220, which like the network 1216 may include any communication network through which programmable devices may exchange information. As the patient 102 enters her office, the proximity monitoring component 414 identifies the SSID of the network 1220 as a range identifier of the predefined range 1202 and, consequently, determines that the medical device 100 has entered the predefined range 1202. In response to making this determination, the proximity monitoring component 414 notifies the location-specific processing component 416. The location-specific processing component 416, in turn, issues a notification to the patient to take her medicine, which is a task associated with her office desk.

In this example, the patient 102 next visits her caregiver, whose office is located at the geographic location 1222. As the patient nears her caregiver's office, the proximity monitoring component tracks the geographic location of the controller (e.g., via GPS), calculates a distance between the medical device and the geographic location 1222, and, where the distance is less than a threshold value, determines that the medical device has entered the predefined range 1210. In response to making this determination, the proximity monitoring component 414 notifies the location adaptation component 410. The location adaptation component 410, in turn, adapts the operation of the medical device so that the user interface presents the caregiver menu button 1008 on the display 220.

Other Examples

In one implementation, Bluetooth Low Energy beacon (BLE beacon) technology may be used in the base stations described above. Using this technology, a medical device can ascertain proximity, including a degree of proximity, to one or more base stations in a certain region. For example, BLE beacons associated with the bases station may periodically cast a beacon signal containing a universally unique identifier (UUID), and information regarding the location of the base station. A medical device may detect these signals and determine its proximity from the one or more base stations based on the information in the signals. The BLE beacon may include a calibration parameter indicating a nominal signal strength at a predetermined range from the beacon. Using the parameter, a medical device can measure a signal strength of a received signal to determine how close the device is to a base station. In an implementation, the medical device may include in memory a look-up table of base stations along with their known locations. Based on the signal strength, and information contained in the signal, a medical device may provide different types of notifications and/or use different notification modes based on proximity of the medical device to a base station. For example, if the medical device has a remaining battery charge below a set threshold (e.g., 25%) then the device may be configured to notify the patient in the following manner. If the patient is approximately 15 feet away from a base station (which also has charging capability), the medical device may inform the patient through a silent visual indicator that the battery is running out and because the patient is near the base station, the patient should consider charging the battery. If the patient is closer, e.g., less than 3 feet from the base station, the medical device and/or the base station may issue an audible or verbal notification requesting that the patient charge the battery as the patient is proximal to the base station.

Having thus described several aspects of at least one example, it is to be appreciated that various alterations, modifications, and improvements will readily occur to those skilled in the art. For instance, examples disclosed herein may also be used in other contexts. Such alterations, modifications, and improvements are intended to be part of this disclosure, and are intended to be within the scope of the examples discussed herein. Accordingly, the foregoing description and drawings are by way of example only.

Claims

1. A medical device configured to be worn by an ambulatory patient for monitoring and treating the ambulatory patient and executing location-specific processes, the medical device comprising: a plurality of sensing electrodes configured to be in contact with skin and acquire electrocardiogram (ECG) data from the ambulatory patient over an extended period of time;a garment configured to dispose the plurality of sensing electrodes at various positions about a torso of the ambulatory patient to continuously acquire the ECG data;at least one therapy electrode configured to deliver a therapeutic electrical shock to the ambulatory patient;a battery coupled with the at least one therapy electrode to power the therapeutic electrical shock;a user interface; andat least one processor coupled with the plurality of sensing electrodes, the at least one therapy electrode, and the user interface and configured to: determine whether a current location of the medical device is within a predefined range of a reference location of a home of the ambulatory patient,determine a location-specific process to execute based on a determination that the current location is within the predefined range, the location-specific process being configured to control the user interface to notify the ambulatory patient to perform one or more home-specific actions and remind the ambulatory patient to review a patient training module, andexecute the location-specific process to notify the ambulatory patient to perform the one or more home-specific actions.
2. The medical device of claim 1, wherein the one or more home-specific actions include one or more of change the battery, adjust at least one sensing electrode of the plurality of sensing electrodes, or launder the garment.
3. The medical device of claim 1, further comprising a memory storing a list of reference locations, the list including the reference location of the home of the ambulatory patient.
4. The medical device of claim 3, wherein: the list of reference locations further comprises a reference location of a workplace of the ambulatory patient and a network identifier associated with the workplace; andthe at least one processor is further configured to determine that the current location of the medical device is within a predefined range of the reference location of the workplace of the ambulatory patient based on detecting the network identifier.
5. The medical device of claim 3, wherein: the list of reference locations further comprises a reference location of a caregiver of the ambulatory patient;the at least one processor is further configured to, in response to determining that the current location of the medical device is within a predefined range of the reference location of the caregiver of the ambulatory patient, adapt the user interface to grant access to functionality associated with the caregiver.
6. The medical device of claim 1, wherein: the at least one processor is further configured to identify a next scheduled visitation to the home of the ambulatory patient; andthe at least one processor is further configured to determine the location-specific process to execute further based on determining that a serviceable component of the medical device should be serviced before the next scheduled visitation to the home of the ambulatory patient.
7. The medical device of claim 6, wherein the at least one processor is further configured to adjust a schedule listing scheduled visitations to the home of the ambulatory patient based on sampled movement observations of the ambulatory patient.
8. The medical device of claim 1, wherein: the at least one processor is further configured to determine whether the current location of the medical device is within a predefined range of an alternative reference location; andthe at least one processor is further configured to execute a conflict resolution process to determine whether to execute a location-specific process associated with the home of the ambulatory patient or an alternative location-specific process associated with the alternative reference location.
9. The medical device of claim 8, wherein the conflict resolution process resolves conflicts based on a predefined range within which the medical device is first detected.
10. The medical device of claim 8, wherein the conflict resolution process resolves conflicts based on location priorities specified in a list of reference locations that includes the reference location of the home of the ambulatory patient.
11. The medical device of claim 1, wherein the reference location of the home of the ambulatory patient is included in a list of reference locations that is stored in a remote server database.
12. The medical device of claim 1, wherein: the location-specific process is configured to control the user interface to notify the ambulatory patient to launder the garment; andthe at least one processor is further configured to determine the location-specific process to execute further based on a date and/or time that the garment was last laundered.
13. The medical device of claim 1, wherein: the location-specific process is configured to control the user interface to notify the ambulatory patient to change the battery; andthe at least one processor is further configured to determine the location-specific process to execute further based on a first additional determination that the battery holds a remaining charge that is less than a specified value.
14. The medical device of claim 13, wherein the at least one processor is further configured to determine the location-specific process to execute further based on a second additional determination that the home of the ambulatory patient has a base station with a charging bay that currently holds a charged replacement battery.
15. The medical device of claim 14, wherein controlling the user interface to notify the ambulatory patient to change the battery comprises: generating a silent visual indicator via the user interface when the current location is within a first range of the base station; andgenerating an audible notification when the current location is within a second range of the base station.
16. The medical device of claim 15, wherein the second range is smaller than the first range.
17. The medical device of claim 1, wherein determining whether the current location of the medical device is within the predefined range of the reference location of the home of the ambulatory patient further comprises determining that the current location of the medical device has left a first predefined range while remaining within a second predefined range, wherein the second predefined range encompasses the first predefined range.
18. The medical device of claim 1, wherein the at least one processor is configured to determine whether the current location of the medical device is within the predefined range in response to at least one of expiration of a timer or receipt of a request to determine whether the current location is within the predefined range.
19. The medical device of claim 18, further comprising a network interface coupled with the at least one processor, wherein the at least one processor is further configured to operate the network interface in a power conservation mode when not determining whether the current location of the medical device is within the predefined range.
20. The medical device of claim 18, further comprising a network interface coupled with the at least one processor, wherein the at least one processor is further configured to operate the network interface in a power conservation mode when the battery holds a remaining charge that is less than a specified value.
21. The medical device of claim 1, further comprising a network interface, the location-specific process further being configured to control the network interface to transmit a notification of a status of the medical device.
22. The medical device of claim 1, wherein the location-specific process is further configured to control the user interface to notify the ambulatory patient to take a medication.
23. A medical device configured to be worn by an ambulatory patient for monitoring and treating the ambulatory patient and executing location-specific processes, the medical device comprising: a memory storing a list of reference locations, the list including a home reference location corresponding to a home of the ambulatory patient and a caregiver reference location corresponding to a caregiver of the ambulatory patient;a plurality of sensing electrodes configured to be in contact with skin and acquire electrocardiogram (ECG) data from the ambulatory patient over an extended period of time;a garment configured to dispose the plurality of sensing electrodes at various positions about a torso of the ambulatory patient to continuously acquire the ECG data;at least one therapy electrode configured to deliver a therapeutic electrical shock to the ambulatory patient;a battery coupled with the at least one therapy electrode to power the therapeutic electrical shock;a user interface; andat least one processor coupled with the plurality of sensing electrodes, the at least one therapy electrode, and the user interface and configured to: determine whether a current location of the medical device is within a first predefined range of the home reference location,determine whether the current location of the medical device is within a second predefined range of the caregiver reference location,determine a location-specific process to execute based on a determination that the current location is within the first predefined range, the location-specific process being configured to control the user interface to notify the ambulatory patient to perform one or more home-specific actions,in response to determining that the current location of the medical device is within the second predefined range, adapt the user interface to grant access to functionality associated with the caregiver, andexecute the location-specific process to notify the ambulatory patient to perform the one or more home-specific actions.
24. The medical device of claim 23, wherein the location-specific process is configured to control the user interface to notify the ambulatory patient to change the battery.
25. The medical device of claim 23, wherein the at least one processor is further configured to determine the location-specific process to execute further based on an additional determination that the battery holds a remaining charge that is less than a specified value.
26. A medical device configured to be worn by an ambulatory patient for monitoring and treating the ambulatory patient and executing location-specific processes, the medical device comprising: a plurality of sensing electrodes configured to be in contact with skin and acquire electrocardiogram (ECG) data from the ambulatory patient over an extended period of time;a garment configured to dispose the plurality of sensing electrodes at various positions about a torso of the ambulatory patient to continuously acquire the ECG data;at least one therapy electrode configured to deliver a therapeutic electrical shock to the ambulatory patient;a battery coupled with the at least one therapy electrode to power the therapeutic electrical shock;a user interface; andat least one processor coupled with the plurality of sensing electrodes, the at least one therapy electrode, and the user interface and configured to: determine whether a current location of the medical device is within a predefined range of a reference location of a home of the ambulatory patient,determine a location-specific process to execute based on a determination that the current location is within the predefined range, and further based on a date and/or time that the garment was last laundered, wherein the location-specific process is configured to control the user interface to notify the ambulatory patient to perform one or more home-specific actions and launder the garment, andexecute the location-specific process to notify the ambulatory patient to perform the one or more home-specific actions.
27. The medical device of claim 26, wherein the at least one processor is configured to determine whether the current location of the medical device is within the predefined range in response to at least one of expiration of a timer or receipt of a request to determine whether the current location is within the predefined range.
28. The medical device of claim 26, wherein the location-specific process is further configured to control the user interface to remind the ambulatory patient to take a medication.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation of U.S. patent application Ser. No. 15/454,573 (filed 9 Mar. 2017, now U.S. Pat. No. 11,617,538), which claims the benefit of U.S. Provisional Patent Application No. 62/307,811 (filed 14 Mar. 2016). Each of these priority applications is herein incorporated by reference in its entirety.

US Referenced Citations (337)

Number	Name	Date	Kind
3724455	Unger	Apr 1973	A
3922665	Curry et al.	Nov 1975	A
4094310	McEachern et al.	Jun 1978	A
4576170	Bradley et al.	Mar 1986	A
4580572	Granek et al.	Apr 1986	A
4583547	Granek et al.	Apr 1986	A
4632122	Johansson et al.	Dec 1986	A
4729377	Granek et al.	Mar 1988	A
4926879	Sevrain et al.	May 1990	A
4928690	Heilman et al.	May 1990	A
4991217	Garrett et al.	Feb 1991	A
5078134	Heilman et al.	Jan 1992	A
5224479	Sekine	Jul 1993	A
5348008	Bornn et al.	Sep 1994	A
5365932	Greenhut	Nov 1994	A
5381798	Burrows	Jan 1995	A
5472453	Alt	Dec 1995	A
5544661	Davis et al.	Aug 1996	A
5558098	Fain	Sep 1996	A
5662689	Elsberry et al.	Sep 1997	A
5718242	McClure et al.	Feb 1998	A
5738102	Lemelson	Apr 1998	A
5741306	Glegyak et al.	Apr 1998	A
5792190	Olson et al.	Aug 1998	A
5827196	Yeo et al.	Oct 1998	A
5865736	Baker, Jr. et al.	Feb 1999	A
5929601	Kaib et al.	Jul 1999	A
5944669	Kaib	Aug 1999	A
6006132	Tacker, Jr. et al.	Dec 1999	A
6016445	Baura	Jan 2000	A
6065154	Hulings et al.	May 2000	A
6097982	Glegyak et al.	Aug 2000	A
6097987	Milani	Aug 2000	A
6160964	Imoto	Dec 2000	A
6178343	Bindszus et al.	Jan 2001	B1
6253099	Oskin et al.	Jun 2001	B1
6280461	Glegyak et al.	Aug 2001	B1
6304783	Lyster et al.	Oct 2001	B1
6336900	Alleckson et al.	Jan 2002	B1
6374138	Owen et al.	Apr 2002	B1
6390996	Halperin et al.	May 2002	B1
6405082	Borgenicht	Jun 2002	B1
6406426	Reuss et al.	Jun 2002	B1
6418346	Nelson et al.	Jul 2002	B1
6442433	Linberg	Aug 2002	B1
6546285	Owen et al.	Apr 2003	B1
6602191	Quy	Aug 2003	B2
6681003	Linder et al.	Jan 2004	B2
6690969	Bystrom et al.	Feb 2004	B2
6694191	Starkweather et al.	Feb 2004	B2
6751501	Schuler et al.	Jun 2004	B1
6804554	Ujhelyi et al.	Oct 2004	B2
6827695	Palazzolo et al.	Dec 2004	B2
6878121	Krausman et al.	Apr 2005	B2
6889078	Struble et al.	May 2005	B2
6889079	Bocek et al.	May 2005	B2
6908437	Bardy	Jun 2005	B2
6947565	Halleck et al.	Sep 2005	B2
6990373	Jayne et al.	Jan 2006	B2
7088233	Menard	Aug 2006	B2
7149579	Koh et al.	Dec 2006	B1
7220235	Geheb et al.	May 2007	B2
7340296	Stahmann et al.	Mar 2008	B2
7405653	Tice	Jul 2008	B2
7427921	Van Woudenberg	Sep 2008	B2
7453354	Reiter et al.	Nov 2008	B2
7476206	Palazzolo et al.	Jan 2009	B2
7488293	Marcovecchio et al.	Feb 2009	B2
7534212	Baker, Jr.	May 2009	B2
7712373	Nagle et al.	May 2010	B2
7728548	Daynes et al.	Jun 2010	B2
7831303	Rueter et al.	Nov 2010	B2
7860558	Feild et al.	Dec 2010	B2
7953478	Vaisnys et al.	May 2011	B2
7974689	Volpe et al.	Jul 2011	B2
7991460	Fischell et al.	Aug 2011	B2
8121683	Bucher et al.	Feb 2012	B2
8140154	Donnelly et al.	Mar 2012	B2
8271082	Donnelly et al.	Sep 2012	B2
8290574	Feild et al.	Oct 2012	B2
8319632	Vaisnys et al.	Nov 2012	B1
8331574	Powers	Dec 2012	B2
8364221	Mannheimer et al.	Jan 2013	B2
8369944	Macho et al.	Feb 2013	B2
8406842	Kaib et al.	Mar 2013	B2
8412323	Bauer	Apr 2013	B2
8644925	Volpe et al.	Feb 2014	B2
8649861	Donnelly et al.	Feb 2014	B2
8676313	Volpe et al.	Mar 2014	B2
8706215	Kaib et al.	Apr 2014	B2
8774917	Macho et al.	Jul 2014	B2
8880196	Kaib	Nov 2014	B2
8897860	Volpe et al.	Nov 2014	B2
8904214	Volpe et al.	Dec 2014	B2
9161723	Rodriguez-Llorente et al.	Oct 2015	B2
9283399	Donnelly et al.	Mar 2016	B2
9378637	Kaib et al.	Jun 2016	B2
9398007	Wegener et al.	Jul 2016	B1
9504423	Bardy et al.	Nov 2016	B1
9659475	Kaib et al.	May 2017	B2
9684767	Kaib et al.	Jun 2017	B2
10555704	Averina et al.	Feb 2020	B2
11504071	Terry et al.	Nov 2022	B2
20010031991	Russial	Oct 2001	A1
20020077689	Kirkland	Jun 2002	A1
20020181680	Linder et al.	Dec 2002	A1
20020188214	Misczynski et al.	Dec 2002	A1
20030004547	Owen et al.	Jan 2003	A1
20030032988	Fincke	Feb 2003	A1
20030054866	Byers et al.	Mar 2003	A1
20030060723	Joo et al.	Mar 2003	A1
20030095648	Kaib et al.	May 2003	A1
20030109904	Silver et al.	Jun 2003	A1
20030149462	White et al.	Aug 2003	A1
20030158593	Heilman et al.	Aug 2003	A1
20030174049	Beigel et al.	Sep 2003	A1
20030195567	Jayne et al.	Oct 2003	A1
20030212311	Nova et al.	Nov 2003	A1
20030216786	Russial	Nov 2003	A1
20040007970	Ma et al.	Jan 2004	A1
20040010294	Kleine	Jan 2004	A1
20040049233	Edwards	Mar 2004	A1
20040143297	Ramsey	Jul 2004	A1
20040162510	Jayne et al.	Aug 2004	A1
20040249419	Chapman et al.	Dec 2004	A1
20050049515	Misczynski et al.	Mar 2005	A1
20050049644	Warren et al.	Mar 2005	A1
20050131465	Freeman et al.	Jun 2005	A1
20050144043	Holland et al.	Jun 2005	A1
20050204310	De Zwart et al.	Sep 2005	A1
20050246199	Futch	Nov 2005	A1
20050283198	Haubrich et al.	Dec 2005	A1
20050288599	Macadam et al.	Dec 2005	A1
20060015148	McCabe et al.	Jan 2006	A1
20060036292	Smith et al.	Feb 2006	A1
20060085049	Cory et al.	Apr 2006	A1
20060095091	Drew	May 2006	A1
20060136000	Bowers	Jun 2006	A1
20060178706	Lisogurski et al.	Aug 2006	A1
20060202816	Crump et al.	Sep 2006	A1
20060211934	Hassonjee et al.	Sep 2006	A1
20060220809	Stigall et al.	Oct 2006	A1
20060259080	Vaisnys et al.	Nov 2006	A1
20060264776	Stahmann et al.	Nov 2006	A1
20060270952	Freeman et al.	Nov 2006	A1
20060293714	Salo et al.	Dec 2006	A1
20070016029	Donaldson et al.	Jan 2007	A1
20070073120	Li et al.	Mar 2007	A1
20070118056	Wang et al.	May 2007	A1
20070129769	Bourget et al.	Jun 2007	A1
20070143864	Cabana et al.	Jun 2007	A1
20070161913	Farrell et al.	Jul 2007	A1
20070162075	O'Hara	Jul 2007	A1
20070162390	Pancholy et al.	Jul 2007	A1
20070169364	Townsend et al.	Jul 2007	A1
20070196320	Yasin	Aug 2007	A1
20070197878	Shklarski	Aug 2007	A1
20070232946	Feild et al.	Oct 2007	A1
20070239214	Cinbis	Oct 2007	A1
20070239220	Greenhut et al.	Oct 2007	A1
20070265533	Tran	Nov 2007	A1
20070265671	Roberts et al.	Nov 2007	A1
20080004536	Baxi et al.	Jan 2008	A1
20080021532	Kveen et al.	Jan 2008	A1
20080030309	Darrouzet	Feb 2008	A1
20080030656	Watson et al.	Feb 2008	A1
20080031270	Tran et al.	Feb 2008	A1
20080033495	Kumar	Feb 2008	A1
20080045815	Derchak et al.	Feb 2008	A1
20080046015	Freeman et al.	Feb 2008	A1
20080058884	Matos	Mar 2008	A1
20080097793	Dicks et al.	Apr 2008	A1
20080103402	Stickney et al.	May 2008	A1
20080167535	Stivoric et al.	Jul 2008	A1
20080177193	Farringdon et al.	Jul 2008	A1
20080177341	Bowers	Jul 2008	A1
20080183090	Farringdon et al.	Jul 2008	A1
20080249591	Gaw et al.	Oct 2008	A1
20080266118	Pierson et al.	Oct 2008	A1
20080287749	Reuter	Nov 2008	A1
20080294019	Tran	Nov 2008	A1
20080306560	Macho et al.	Dec 2008	A1
20080306562	Donnelly et al.	Dec 2008	A1
20080312520	Rowlandson et al.	Dec 2008	A1
20080312522	Rowlandson et al.	Dec 2008	A1
20080312709	Volpe et al.	Dec 2008	A1
20090018428	Dias et al.	Jan 2009	A1
20090066366	Solomon	Mar 2009	A1
20090073991	Landrum et al.	Mar 2009	A1
20090076336	Mazar et al.	Mar 2009	A1
20090076340	Libbus et al.	Mar 2009	A1
20090076341	James et al.	Mar 2009	A1
20090076342	Amurthur et al.	Mar 2009	A1
20090076343	James et al.	Mar 2009	A1
20090076344	Libbus et al.	Mar 2009	A1
20090076345	Manicka et al.	Mar 2009	A1
20090076346	James et al.	Mar 2009	A1
20090076348	Manicka et al.	Mar 2009	A1
20090076349	Libbus et al.	Mar 2009	A1
20090076350	Bly et al.	Mar 2009	A1
20090076363	Bly et al.	Mar 2009	A1
20090076364	Libbus et al.	Mar 2009	A1
20090076397	Libbus et al.	Mar 2009	A1
20090076405	Amurthur et al.	Mar 2009	A1
20090076410	Libbus et al.	Mar 2009	A1
20090076559	Libbus et al.	Mar 2009	A1
20090093687	Telfort et al.	Apr 2009	A1
20090118808	Belacazar et al.	May 2009	A1
20090138059	Ouwerkerk	May 2009	A1
20090146822	Soliman	Jun 2009	A1
20090212984	Baker	Aug 2009	A1
20090221887	Mannheimer et al.	Sep 2009	A1
20090231124	Klabunde et al.	Sep 2009	A1
20090232286	Hurwitz	Sep 2009	A1
20090234410	Libbus et al.	Sep 2009	A1
20090243878	Ricordi et al.	Oct 2009	A1
20090264792	Mazar	Oct 2009	A1
20090275848	Brockway et al.	Nov 2009	A1
20090281394	Russell et al.	Nov 2009	A1
20090287120	Ferren et al.	Nov 2009	A1
20090292194	Libbus et al.	Nov 2009	A1
20090295326	Daynes et al.	Dec 2009	A1
20090307266	Fleizach et al.	Dec 2009	A1
20090312650	Maile et al.	Dec 2009	A1
20090318779	Tran	Dec 2009	A1
20100010559	Zhang et al.	Jan 2010	A1
20100052892	Allen et al.	Mar 2010	A1
20100052897	Allen et al.	Mar 2010	A1
20100056881	Libbus et al.	Mar 2010	A1
20100063756	Agrawal et al.	Mar 2010	A1
20100069735	Berkner	Mar 2010	A1
20100076513	Warren et al.	Mar 2010	A1
20100076533	Dar et al.	Mar 2010	A1
20100081962	Hamaguchi et al.	Apr 2010	A1
20100114243	Nowak et al.	May 2010	A1
20100151918	Annambhotla	Jun 2010	A1
20100171611	Gao et al.	Jul 2010	A1
20100175699	Varney et al.	Jul 2010	A1
20100231379	Hutzler	Sep 2010	A1
20100234716	Engel	Sep 2010	A1
20100241181	Savage et al.	Sep 2010	A1
20100295674	Hsieh et al.	Nov 2010	A1
20100298899	Donnelly et al.	Nov 2010	A1
20100305462	Callas et al.	Dec 2010	A1
20100312297	Volpe et al.	Dec 2010	A1
20110015533	Cox et al.	Jan 2011	A1
20110022105	Owen et al.	Jan 2011	A9
20110080294	Tanishima et al.	Apr 2011	A1
20110093840	Pynenburg et al.	Apr 2011	A1
20110098765	Patel	Apr 2011	A1
20110106736	Aharonson et al.	May 2011	A1
20110170692	Konrad et al.	Jul 2011	A1
20110172550	Martin et al.	Jul 2011	A1
20110288604	Kaib et al.	Nov 2011	A1
20110288605	Kaib	Nov 2011	A1
20120011382	Volpe et al.	Jan 2012	A1
20120016361	White et al.	Jan 2012	A1
20120053479	Hopenfeld	Mar 2012	A1
20120112903	Kaib et al.	May 2012	A1
20120126975	Gonzales	May 2012	A1
20120146797	Oskin et al.	Jun 2012	A1
20120150008	Kaib et al.	Jun 2012	A1
20120158075	Kaib et al.	Jun 2012	A1
20120191476	Reid et al.	Jul 2012	A1
20120242501	Tran	Sep 2012	A1
20120259377	Freeman	Oct 2012	A1
20120277642	Smith et al.	Nov 2012	A1
20120283794	Kaib et al.	Nov 2012	A1
20120289809	Kaib et al.	Nov 2012	A1
20120293323	Kaib	Nov 2012	A1
20120302860	Volpe et al.	Nov 2012	A1
20130013014	Donnelly et al.	Jan 2013	A1
20130024382	Dala et al.	Jan 2013	A1
20130060149	Song et al.	Mar 2013	A1
20130076523	Kwan	Mar 2013	A1
20130085538	Volpe et al.	Apr 2013	A1
20130113496	Craige, III et al.	May 2013	A1
20130144355	Macho et al.	Jun 2013	A1
20130171599	Bleich et al.	Jul 2013	A1
20130218252	Kaib et al.	Aug 2013	A1
20130231711	Kaib	Sep 2013	A1
20130237861	Margarida et al.	Sep 2013	A1
20130324868	Kaib et al.	Dec 2013	A1
20130325078	Whiting et al.	Dec 2013	A1
20130325096	Dupelle et al.	Dec 2013	A1
20130325396	Yuen et al.	Dec 2013	A1
20140004814	Elghazzawi	Jan 2014	A1
20140031884	Elghazzawi	Jan 2014	A1
20140031885	Elghazzawi et al.	Jan 2014	A1
20140039839	Jao et al.	Feb 2014	A1
20140039841	Jao et al.	Feb 2014	A1
20140073486	Ahmed et al.	Mar 2014	A1
20140125619	Panther et al.	May 2014	A1
20140163334	Volpe et al.	Jun 2014	A1
20140206974	Volpe et al.	Jul 2014	A1
20140249613	Kaib	Sep 2014	A1
20140277243	Maskara et al.	Sep 2014	A1
20140288609	Freeman	Sep 2014	A1
20140288610	Freeman	Sep 2014	A1
20140296656	Kasama	Oct 2014	A1
20140303680	Donnelly et al.	Oct 2014	A1
20140324112	Macho et al.	Oct 2014	A1
20140336514	Peyman	Nov 2014	A1
20140337826	Kiaie et al.	Nov 2014	A1
20140347187	Freathey	Nov 2014	A1
20150005588	Herken et al.	Jan 2015	A1
20150018014	Phan	Jan 2015	A1
20150035654	Kaib et al.	Feb 2015	A1
20150037636	Amsler et al.	Feb 2015	A1
20150039039	Macho et al.	Feb 2015	A1
20150039042	Amsler et al.	Feb 2015	A1
20150039053	Kaib et al.	Feb 2015	A1
20150080699	Kaib et al.	Mar 2015	A1
20150106020	Chung et al.	Apr 2015	A1
20150134018	Bonnamy	May 2015	A1
20150164436	Maron et al.	Jun 2015	A1
20150223731	Sahin	Aug 2015	A1
20150224330	Kaib	Aug 2015	A1
20150235541	Kaib et al.	Aug 2015	A1
20150265845	Sullivan	Sep 2015	A1
20160066808	Hijazi	Mar 2016	A1
20160174857	Eggers et al.	Jun 2016	A1
20160278652	Kaib	Sep 2016	A1
20160328529	Kaib	Nov 2016	A1
20170007129	Kaib	Jan 2017	A1
20170011210	Cheong et al.	Jan 2017	A1
20170172424	Eggers	Jun 2017	A1
20170193787	Devdas	Jul 2017	A1
20170238401	Sadwick	Aug 2017	A1
20170278370	Kaib et al.	Sep 2017	A1
20170296057	Freeman et al.	Oct 2017	A1
20180032691	Zur et al.	Feb 2018	A1
20180310892	Perschbacher et al.	Nov 2018	A1
20190325380	Johnson et al.	Oct 2019	A1
20200029843	Sullivan et al.	Jan 2020	A1
20200221952	Kaib et al.	Jul 2020	A1
20210121082	Wild	Apr 2021	A1

Foreign Referenced Citations (56)

Number	Date	Country
2644236	Apr 1981	DE
0396048	Nov 1990	EP
0295497	Sep 1993	EP
0335356	Mar 1996	EP
0707825	Apr 1996	EP
0761255	Mar 1997	EP
1642616	Apr 2006	EP
1455640	Jan 2008	EP
1720446	Jul 2010	EP
2689363	Jan 2014	EP
5115450	May 1993	JP
1998-505515	Jun 1998	JP
1999-149379	Jun 1999	JP
2002-509472	Mar 2002	JP
2002-514107	May 2002	JP
2002-000059	Jul 2002	JP
2004-318839	Nov 2004	JP
2006-091013	Apr 2006	JP
2006-136707	Jun 2006	JP
2007-522859	Aug 2007	JP
2008-302225	Dec 2008	JP
2008-302228	Dec 2008	JP
2009-510631	Mar 2009	JP
2009-521865	Jun 2009	JP
2009-528909	Aug 2009	JP
2009-536068	Oct 2009	JP
2012-003311	Jan 2012	JP
6166253	Jul 2017	JP
8304171	Dec 1983	WO
1997022297	Jun 1997	WO
1998039061	Sep 1998	WO
1998043537	Oct 1998	WO
1999059465	Nov 1999	WO
2000002484	Jan 2000	WO
2000030529	Jun 2000	WO
2004054656	Jul 2004	WO
2004067083	Aug 2004	WO
2004078259	Sep 2004	WO
2005082454	Sep 2005	WO
2006050325	May 2006	WO
2007019325	Feb 2007	WO
2009034506	Mar 2009	WO
2009122277	Oct 2009	WO
2010025432	Mar 2010	WO
2010077997	Jul 2010	WO
2012006524	Jan 2012	WO
2012100219	Jul 2012	WO
2012135059	Oct 2012	WO
2012149482	Nov 2012	WO
2012174659	Dec 2012	WO
2013040214	Mar 2013	WO
2013130957	Sep 2013	WO
2014018057	Jan 2014	WO
2014018160	Jan 2014	WO
2014097035	Jun 2014	WO
2014099986	Jun 2014	WO

Non-Patent Literature Citations (18)

Entry
“ATS statement: Guidelines for the Six-Minute Walk Test”, American Journal of Respiratory and Critical Care Medicine, vol. 166, pp. 111-117 (2002), American Thoracic Society, <URL: http://ajrccm.atsjournals.org/cgi/content/ull/166/1/111>.
http:/web.archive.org/web/20030427001846/http:/www.lifecor.comiimagelib/imageproduct.asp; Published by LifeCor, Inc., 2002 on a web page owned by LifeCor Inc.
Debock et al., “Captopril Treatment of Chronic Heart Failure in the Very Old”, J. Gerontol, 1994, 49:M148-M152.
International Search Report for Corresponding International Application No. PCT/US2012/030433, mailed Jul. 5, 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.
International Search Report and Written Opinion from Corresponding PCT Application No. PCT/US2012/030428, mailed Nov. 7, 2012.
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, ISBN1-57020-210-9; abstract; p. vi; p. 50, section 107.1.2.
International Search Report and Written Opinion from PCT/US2013/028598, mailed May 9, 2013.
Zoll Medical Corporation, “LifeVest Model WCD 3000 Operator's Manual”, Pittsburgh, PA (2012).
International Search Report and Written Opinion from Corresponding PCT Application No. PCT/US2015/015199, mailed on May 14, 2015.
PCT Search Report and Written Opinion for PCT Application No. PCT/US2015/066852, mailed on May 4, 2016, 16 pages.
Herlihy et al., “The Art of Multiple Processor Programming”, Chapter 1, p. 1, Mar. 3, 2008.
International Search Report and Written Opinion from Corresponding International Application No. PCT/US2011/043368, dated Nov. 17, 2011.
Wikipedia, Automated External Defibrillator, May 31, 2009, Wikipedia, Section on Mechanism of Operation.
Wikipedia, “Multi-Core Processor”, Dec. 11, 2009, <URL: http://web.archive.org/web/20091211134408/http://en.wikipedia.org/wiki/Multicore_processor#Hardware>.
PCT Search Report and Written Opinion for PCT Application No. PCT/US2016/023068, mailed on Jun. 3, 2016, 14 pages.
Extended European Search Report for European Application No. 13755470.5, dated Dec. 18, 2015, 6 pages.
PCT Search Report and Written Opinion for PCT Application No. PCT/US2015/039321, Oct. 15, 2015, 14 pages.

Related Publications (1)

	Number	Date	Country
	20230277131 A1	Sep 2023	US

Provisional Applications (1)

	Number	Date	Country
	62307811	Mar 2016	US

Continuations (1)

	Number	Date	Country
Parent	15454573	Mar 2017	US
Child	18178050		US

Proximity based processing systems and methods

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

International Classifications

Term Extension

Abstract