Persistent health monitoring of patients through application restart enabled medical systems

By automatically detecting and restarting the monitoring application in the medical system, using location data to determine whether it is in the certified area, the delay and inefficiency of medical care caused by monitoring application failure is solved, ensuring the continuity and safety of medical care.

CN118922893APending Publication Date: 2024-11-08MEDTRONIC INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380028375.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-23
Filing Date
2023-03-15
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

When existing medical systems monitor applications fail, they lead to delays and inefficiency in medical care in patients, and it is difficult to restart applications, affecting patients' health and safety.

Method used

By determining the failure status of the monitoring application in the computing device and using the patient's current location data to determine whether it is in the certified area, the monitoring application is automatically restarted to ensure the continuity of medical care.

Benefits of technology

It effectively solves the problems of delay and inefficiency in medical care caused by monitoring application failure, ensures the continuity and safety of patient health monitoring, reduces human errors, and improves the reliability of the medical system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118922893A_ABST
    Figure CN118922893A_ABST
Patent Text Reader

Abstract

The present disclosure relates to medical systems and techniques for enhancing health monitoring using location information. In one example, a method performed by processing circuitry of a computing device is described. The method includes determining that a monitoring application previously executed by the processing circuitry is inoperative; receiving, from an input device of the computing device, input data indicative of a current location of the patient; determining whether the current location of the patient corresponds to an authenticated area of the patient; and in response to determining that the current location corresponds to the authenticated area and in response to determining that the monitoring application is inoperative, restarting the monitoring application.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to medical systems, and more particularly to medical systems configured to monitor patient activity to understand changes in the patient's health status and / or provide treatment to the patient. Background Art

[0002] Certain types of medical systems may monitor various types of data from a patient or a group of patients for one or more purposes. In numerous examples, some medical systems may record measurements of a patient and their heart as indicators of the patient's cardiac health, which may be recorded in the format of raw data and / or processed data; for example, electrical signals representing cardiac activity over a period of time may be recorded as an electrocardiogram (EGM) and then processed into other indicators of the patient's cardiac health. In some examples, the medical system may monitor the EGM to detect one or more types of arrhythmias, such as bradycardia, tachycardia, fibrillation, or cardiac arrest (e.g., caused by sinus pause or AV block). In some examples, the medical system may include one or more of an implantable medical device or a wearable device to collect various measurements for detecting changes in a patient's cardiac health. In some examples, the medical system may provide treatment and may record information about providing treatment. Summary of the invention

[0003] Medical systems and techniques as described herein facilitate the implementation of medical care for patients while continuously monitoring patient activity and detecting changes in patient health, if any. This disclosure describes "medical care" as referring to any product and / or process that can make a patient healthier, and generally includes medical procedures, clinical assessments, methods for providing treatment, methods involving diagnosis and / or treatment, healthcare-related processes, etc. Implementing "medical care" for any given patient generally involves providing that patient with access to health monitoring services via the patient's personal device, and then successfully performing the medical procedure and / or providing the medical product.

[0004] Current methods for delivering patient medical care are inefficient and / or have delays that can jeopardize the patient's health. If a patient's personal device is turned off and / or a particular application intended to run on the personal device is determined to be non-functional, the medical system for the patient may be limited in operation and may be unable to transition to the next step in the patient's medical care.

[0005] For a particular application, there are multiple ways to transition from a working state to a non-working state. The particular application may not be actively running on the computing device, or the operating system may be running the particular application in the background rather than the foreground (i.e., as a background application). The particular application may have been previously executed and run in the computing device (at some point in the recent past), but later became a non-working application for some reason (including receiving an error, being inactive, and / or causing a failure). The operating system may, for example, de-prioritize the particular application and may shut down the particular application due to the application being inactive for more than a threshold amount of time. The operating system may automatically shut down the de-prioritized particular application to meet the resource requirements of other applications. There may be a fault in one or more components of the particular application or in one or more resources consumed by the particular application, which causes the particular application to be non-working. After becoming non-working, the computing device may lose the network connection that the particular application has with the computing service (such as a health monitoring service), and the operating system may destroy the particular application, such as by deleting any application data from the memory resources and releasing the processing resources. The particular application may fail in some way, and although no error code is displayed, the failure is obvious based on the application activity / behavior.

[0006] In each of the above examples, a particular application becoming inoperative causes significant delays and inefficiencies in the implementation of medical care for the patient, and restarting the particular application reduces those delays and inefficiencies. Otherwise, patient data uploaded from the medical device may be lost and / or communication between the health monitoring service and the patient device may cease. Regardless of how a particular application becomes inoperative, the medical systems and techniques described herein can initiate a mechanism for triggering the execution of a particular application in order to advance / facilitate the implementation of medical care for the patient.

[0007] In one example, a method performed by a processing circuit of a computing device is described. The method includes: determining that a monitoring application previously executed by the processing circuit is not working; receiving input data indicating a current location of a patient from an input device of the computing device; determining whether the current location of the patient corresponds to an authenticated area of ​​the patient; and in response to determining that the current location corresponds to the authenticated area and in response to determining that the monitoring application is not working, restarting the monitoring application.

[0008] In one example, a computing device is described, the computing device comprising: an input device; a memory; and a processing circuit configured to execute logic for a monitoring application stored in the memory. The computing device also includes a processing circuit, the processing circuit further configured to: determine that a monitoring application previously executed by the processing circuit is not working; receive input data indicating a current location of a patient from the input device of the computing device; determine whether the current location of the patient corresponds to an authenticated area of ​​the patient; and in response to determining that the current location corresponds to the authenticated area and in response to determining that the monitoring application is not working, restart the monitoring application.

[0009] In one example, a medical system is described. The medical system includes a processing circuit that executes logic stored in a memory, the processing circuit being configured to: determine that a monitoring application previously executed by the processing circuit is not working; receive input data indicating a current location of a patient from an input device of the computing device; determine whether the current location of the patient corresponds to an authenticated area of ​​the patient; and in response to determining that the current location corresponds to the authenticated area and in response to determining that the monitoring application is not working, restart the monitoring application.

[0010] In one example, a non-transitory computer-readable storage medium is described that includes program instructions that, when executed by a processing circuit of a medical device, cause the processing circuit to: determine that a monitoring application previously executed by the processing circuit is not functioning; receive input data indicating a current location of a patient from an input device of the computing device; determine whether the current location of the patient corresponds to an authenticated area of ​​the patient; and in response to determining that the current location corresponds to the authenticated area and in response to determining that the monitoring application is not functioning, restart the monitoring application.

[0011] The present disclosure is intended to provide an overview of the subject matter described in the present disclosure. The present disclosure is not intended to provide an exclusive or exhaustive explanation of the systems, devices, and methods described in detail in the following figures and description. Further details of one or more examples of the present disclosure are set forth in the following figures and description. Other features, objectives, and advantages will be apparent from the description and drawings, as well as from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 An example environment of an example medical system in conjunction with a patient according to one or more examples of the present disclosure is illustrated.

[0013] Figure 2 is a block diagram illustrating an example configuration of a medical device according to one or more examples of the present disclosure.

[0014] Figure 3One or more examples of the present disclosure are illustrated. Figure 1 A block diagram of an example configuration of an external device.

[0015] Figure 4 is an example of one or more examples according to the present disclosure. Figure 1 Working on a computing system Figure 1 A block diagram of an example architecture of a health monitoring service, the computing system can be coupled to Figures 1 to 4 Medical devices and external devices.

[0016] Figure 5 is a flow diagram illustrating example operations for managing medical care in a geo-fenced geographic area in accordance with one or more examples of the present disclosure.

[0017] Like reference characters represent like elements throughout the specification and drawings. DETAILED DESCRIPTION

[0018] Generally speaking, a medical system according to the present disclosure implements techniques for restarting an authenticated application after it becomes inoperative at a patient's computing device / system. The present disclosure describes various mechanisms for initiating functions at a computing device / system, and the techniques described herein advantageously utilize these mechanisms to accomplish authenticated application restarts. These techniques allow the medical system described herein to resume operation at a computing device without significant interruption in the delivery of medical care to a patient. This is because any delay in such delivery risks compromising the patient's health.

[0019] Figure 1 is a block diagram illustrating an example system 2 configured to detect health events for patient 4 and respond to such detections in accordance with one or more techniques of the present disclosure. As used herein, the terms "detection" and the like may refer to detecting a health event that patient 4 is currently experiencing (at the time data is collected), as well as detecting, based on the data, that patient 4's condition is such that they have a above-threshold likelihood of experiencing a health event within a particular time frame. Examples of health events are cardiac arrest, ventricular fibrillation, ventricular tachycardia, stroke, seizure, or a fall. The example techniques may be used with one or more patient sensing devices (e.g., implantable medical device (IMD) 10) that may wirelessly communicate with one or more patient computing devices (e.g., patient computing devices 12A and / or 12B (collectively referred to herein as "patient computing devices 12")). Although in Figure 1 Not illustrated in FIG. 4 , IMD 10 may include electrodes and other sensors to sense physiological signals of patient 4 , and may collect and store sensed physiological data based on these signals and detect an attack based on this data.

[0020] In some examples, IMD 10 may be implanted outside the chest of patient 4 (e.g., subcutaneously in Figure 1 In some other examples, IMD 10 may be implanted at other subcutaneous locations on patient 108, such as at an abdominal location. IMD 10 may be implanted subcutaneously or submuscularly on the left mid-axillary of patient 4 such that IMD 10 may be positioned above the left thorax of patient 4.

[0021] IMD 10 may be positioned near the sternum of patient 4 at or just below the level of the heart, for example at least partially within the outline of the heart. TM In the form of an implantable cardiac event monitor (ICM). Although described primarily in the context of examples in which the IMD 10 takes the form of an ICM, the techniques of the present disclosure may be implemented in a system that includes any one or more implanted or external medical devices, including a monitor, a sensor, a pacemaker, a defibrillator, a wearable external defibrillator, a neurostimulator, or a drug pump. In addition, although described primarily in the context of examples that include a single implanted patient sensing device, in some examples, the system includes one or more patient sensing devices that may be implanted within the patient 4 or external to the patient 4 (e.g., worn by the patient).

[0022] In general, patient 4 may select their personal device from a variety of computing device types, assuming computing device 12 represents any suitable implementation of hardware / software that can be configured to execute and run software applications. Figure 1 In the illustrated example, computing device 12A may take the form of a smart phone, computing device 12B may take the form of a smart watch or other smart garment, and computing device 12C may take the form of any personal computer, such as a desktop computer, laptop computer, notebook computer, tablet computer, workstation, one or more servers, cellular telephone, or personal digital assistant, configured for wireless communication with IMD 10. One or more of computing devices 12 may be configured to communicate with one or more computing systems, such as computing systems 20A and 20B (collectively, “computing systems 20”), via network 16.

[0023] The computing device 12 may store in a memory and / or transmit various types of information as described herein via a network interface. Examples of data types managed by the computing device 12 include sensory data, such as values ​​of physiological parameters measured by the IMD 10 and in some cases by one or more computing devices in the computing device 12; data about arrhythmia attacks or other health events detected (initially) by the IMD 10 and the computing device 12; and other physiological signals or data recorded by the IMD 10 and / or the computing device 12. The HMS 22 may also retrieve data about the patient 4 from one or more electronic health records (EHR) 24 sources via a network. The EHR 24 may include data about historical (e.g., baseline) physiological parameter values, previous health events and treatments, disease states, comorbidities, demographics, height, weight, and body mass index (BMI) of patients (including patient 4). The HMS 22 may use data from the EHR 24 to configure algorithms implemented by the IMD 10 and / or computing device 12 to detect health events of the patient 4. In some examples, HMS 22 provides data from EHR 24 to computing device 12 and / or IMD 10 for storage therein and use as part of their algorithms for detecting health events.

[0024] Network 16 may include one or more computing devices, such as one or more non-edge switches, routers, hubs, gateways, security devices (such as firewalls), intrusion detection and / or intrusion prevention devices, servers, cellular base stations and nodes, wireless access points, bridges, cable modems, application accelerators, or other network devices. Network 16 may include one or more networks managed by a service provider and may thus form part of a large-scale public network infrastructure (e.g., the Internet). Network 16 may provide services such as Figure 1 The computing devices and systems illustrated in the example provide access to the Internet and may provide a communication framework that allows the computing devices and systems to communicate with each other. In some examples, network 16 may include a dedicated network that provides a communication framework that allows Figure 1 The computing devices and systems illustrated in the example communicate with each other, but some of the data flows are isolated from devices outside the private network for security purposes. In some examples, Figure 1 Communications between the computing device and the system illustrated in are encrypted.

[0025] In some examples, computing system 20A may include Medtronic CareLink TM Online or through Medtronic Carelink TM Network to implement. Figure 1In the illustrated example, computing system 20A implements health monitoring service (HMS) 22, but in other examples, either or both of computing systems 20 may implement HMS 22. As will be described in more detail below, HMS 22 may transmit a message instructing computing device 12 to automatically restart a monitoring application that is determined to be inoperative, such as when the monitoring application is closed, not running, or running in the background (e.g., hibernation), fails (e.g., unpredictable behavior including false alarms), or otherwise cannot detect false positives / does not have the ability to detect false positives. The monitoring application may be a third-party application or a client of HMS 22 running in a patient device.

[0026] The computing system 20B may include a beacon device 18 (or simply beacon 18) as an example implementation of a programmable beacon, which a computing service may utilize to process location data indicating the current location of the beacon 18 and / or the current patient location. A computing service that may be different from HMS22 may be a location service configured to transmit location data to the beacon 18, thereby prompting the computing system 20B to transmit various messages to the computing device 12. These communications may be processed by a second application (i.e., a beacon application), and based on the operating state of the monitoring application, the second application may enable a wake-up function, which is a function call requesting the operating system to execute the program code of the monitoring application. In some examples, a programmable beacon may receive the operating state of the monitoring application and determine that the application has become inoperative. It should be noted that in many examples, geo-fencing is not necessary. The patient device may derive the current location in a variety of ways that do not involve geo-fencing.

[0027] Computing device 12 may be configured to wirelessly communicate with various devices including IMD 10, another computing device 12, computing system 20, IoT device 30, etc. Computing device 12 may communicate with each other via near field communication (NFC) technology (e.g., inductive coupling, NFC, or other communication technology that can operate at a range of less than 10 cm to 20 cm) and far field communication technology (e.g., according to 802.11 or Computing device 12 may communicate with the beacon device according to, for example, a Bluetooth or Bluetooth Low Energy (BLE) protocol. In some examples, only one of computing devices 12 (e.g., computing device 12A) is configured to communicate with IMD 10, for example, due to operation of hardware (e.g., as part of a BLE receiver / transmitter module) and / or due to execution of software (e.g., as part of a monitoring application described herein) that enables communication and interaction with IMD 10.

[0028] Figure 1The various devices illustrated in the example of can be configured as beacon devices similar to beacon 18 of computing system 20B. These devices (including local computing devices (such as those used for computing system 20B or computing device 12C), external (non-patient) computing devices (such as those used for computing system 20A), Internet of Things (IoT) devices 30, and Figure 1 Other devices illustrated in the for example for areas such as area 28 or area 40) can be configured to communicate with computing device 12, for example, via wireless / wired network connectivity (e.g., a local area network or the Internet). These devices can operate independently of HMS 22 and are considered "independent" beacons for automatically restarting the monitoring application described herein.

[0029] Area 28 and area 40 may include one or more IoT devices, such as Figure 1 The IoT devices 30A to 30C (collectively referred to as "IoT devices 30") are illustrated in the example of FIG. 30. IoT devices 30 may include, for example, so-called "smart" speakers, cameras, lights, locks, thermostats, appliances, actuators, controllers, or any other smart home (or building) devices. Figure 1 In the example of , IoT device 30C is a smart speaker and / or controller, which may include a display. As described herein, any one or more of the IoT devices 30 may operate as a programmable beacon configured to facilitate restart of the monitoring application. The IoT device 30 may transmit a message that enables a wake-up function of the monitoring application on the computing devices 12A to 12C after determining that the monitoring application is not working and authenticating the restart using the location data. The wake-up function may be exposed by a beacon application corresponding to the beacon device of the IoT device 30.

[0030] Area 40 includes the residence of patient 4, and area 28 includes the clinic used by patient 4. Each geographic area has the necessary hardware devices / software programs to implement a local network, through which computing device 12, IoT device 30 and other devices communicate with each other. Each geographic area also has the necessary hardware devices / software programs for implementing network connections with remote networks. For example, area 28 can be configured with wireless technology, such as 802.11 wireless networks, 802.15 ZigBee networks, etc. Area 28 may include one or more wireless access points that provide support for wireless communications throughout area 28. Additionally or alternatively, for example when the local network is unavailable, computing device 12, IoT device 30 and other devices within area 28 can be configured to communicate with network 16 via cellular base station 36 and cellular network, such as communicating with HMS22.

[0031] HMS22 is an example of a computing service (including remote monitoring of patient 4 and health event detection based on patient data) that provides various computing resources (e.g., capacity and capabilities) through network 16. HMS can be considered a cloud computing service that provides additional storage, processing, and network resources to computing device 12 and any other external device of IMD 10. HMS22 can program the hardware / software components of computing device 12 so that patient data is transmitted to HMS22 via a wireless or wired connection, so that the data can be viewed remotely by doctors, device clinic personnel, and device manufacturer personnel. Because access to physical programmers and trained personnel in retirement communities is limited or non-existent, delays in device / patient assessments are common, resulting in inefficiencies in patient care. In order to overcome the increased costs, the medical systems and technologies disclosed herein implement persistent and continuous monitoring, which ensures access and control of peri-procedural device inquiries / patient assessments through network 16. Some medical systems and techniques utilize various techniques to program a beacon device to automatically restart a monitoring application on a patient device based on the current location (eg, patient location and / or patient device location) and upon request by the HMS 22 .

[0032] The HMS 22 may be configured to receive patient data from the IMD 10 and / or patient device 12 by triggering execution of a monitoring application (e.g., if determined to be inoperative). The computing system 20 facilitates remote monitoring of the patient 4 on behalf of various entities between the HMS 22 and the computing device 12 of the patient 4 in the geographic regions 28 and / or 40. In region 40, the computing system 20A may configure a computing service to operate on a local area network for computing device 12A, computing device 12C, and IoT device 30B; in doing so, the computing system 20A may instruct the IoT device 30A to output location data for the computing service and / or configure the computing device 12C to transmit a beacon message to the computing device 12A. In region 28, the computing system 20B may configure the computing service on the local area network as, for example, a local service, or alternatively as part of a remote service running from the computing system 20A.

[0033] HMS 22 can monitor computing devices 12, computing systems 20, IoT devices 30, and a given geographic area (e.g., Figure 1The hardware / software components in any other device in the area 40 of the computing system 20B) are programmed to automatically restart the monitoring application whenever the application becomes inoperative and the patient 4 is located within the authenticated area. For example, computing device 12A may include a receiver / transmitter that can communicate with a programmable beacon device (such as beacon 18 of computing system 20B) and receive input data indicating the current location. In response, computing device 12A may automatically restart the monitoring application and transmit a message (e.g., confirmation) indicating a successful restart via the transmitter.

[0034] Patient 4 residing in area 40 desires to receive medical care in the form of remote monitoring via HMS 22 and the monitoring applications described herein. Remote monitoring generally refers to the evaluation of patient data for different tasks, such as detecting various health events of patient 4. The monitoring application running in computing device 12A can facilitate remote monitoring of patient 4 in various ways. The medical systems and techniques described herein allow HMS 22 to enhance the care given to patient 4 by adding beneficial features to such remote monitoring.

[0035] To illustrate an example feature of enhancing the care given to patient 4, consider that patient 4 moves around different geographic areas, including their home / residence (e.g., a retirement community in region 40) and various medical facilities (e.g., hospital 38 or clinics in region 28), where, depending on the location data, HMS 22 can automatically restart a monitoring application that has become inoperative and / or unresponsive. The present disclosure interprets certain geographic areas as being sufficiently bound to patient 4 to authenticate such a restart. For a variety of reasons, the home of patient 4 in region 40 authenticates another party to exert control over the monitoring application. The present disclosure describes medical systems and techniques that advantageously use beacon technology and geo-fencing to accomplish automatic restarts.

[0036] As described herein, HMS22 can construct geo-fences within one or more geographic areas to prompt automatic restart of a non-working (example / instance) monitoring application in each patient device. For example, when patient 4 enters one or more geo-fenced areas with a non-working monitoring application, or when the monitoring application stops working while patient 4 and its patient device are physically present in one or more geo-fenced areas, the geo-fence triggers the execution of the monitoring application, which is configured to support remote monitoring by HMS22. In addition to or in lieu of geo-fences, HMS22 can utilize other controls and methods for monitoring the environment within a geographic area (such as area 28), which includes an authenticated area (such as area 40).

[0037] The present disclosure generally describes a certified area as a geographic area that has been verified as a known patient location. Outside the certified area, although it may be an actual patient location, the likelihood of the patient's presence is substantially lower. Area 28 and area 40 represent an uncertified area and a certified area, respectively. Therefore, in contrast, a beacon message directed to a computing device 12A in area 40 successfully enables a function call of the wake-up process (i.e., a wake-up function call) and triggers execution of the monitoring application. In contrast, a beacon message directed to a computing device 12A in area 28 fails to enable the wake-up function and restart the monitoring application. In some examples, beacon 18 can implement coverage criteria such that a beacon message directed to a computing device 12A in area 28 can enable a wake-up function, assuming that certain coverage criteria can be met.

[0038] An example authenticated region as defined herein may refer to a geographic area in which the presence of a patient device (e.g., computing device 12) used to run a monitoring application implies the presence of patient 4. Figure 1 , region 40 may represent an example authenticated region of the present disclosure. For patient 4, this geographic region 40 may be any known location of patient 4 that may be more private than other regions, for example, because access is restricted. In region 40, computing device 12A or computing device 12C may restart the monitoring application while taking into account patient 4, their caregiver, and / or clinician 26. Region 40 may be defined as a set of geographic coordinates within which a home / residence, retirement community, or office or business location (as examples) provides a safe and authorized environment to administer medical care to patient 4. Patient 4 may pre-select their home as an authenticated region via the monitoring application.

[0039] In some examples, area 28 may not be identified as a certified area for a variety of reasons. Considering the clinical environment of area 28, in addition to patient 4, there are quite a few people visiting the area, and the area is also the workplace of quite a few employees. If one of patient 4's devices is in a clinic, patient 4 may not necessarily be found there. In one example, HMS 22 can override this classification and proceed to restart the monitoring application if the override criteria are met.

[0040] In combination with the network 16, the HMS 22 enables the computing device 12A or the computing device 12C to communicate with the patient 4 at home (home Figure 1The monitoring application may be used to electronically interrogate IMD 10 when patient 4 is in region 40 (which may be represented as region 40), and then relay the device interrogation data to HMS 22, for example, via computing device 12C. When patient 4 is in region 40 and there is no patient involvement, a programmable beacon similar to beacon 18 may effectively restart the monitoring application, for example, if the monitoring application stops running in computing device 12A. The beacon application running in computing device 12A may receive a beacon message from a beacon device in region 40 and grant authorization to automatically restart the monitoring application.

[0041] Patient 4 may receive medical care while at a medical facility, such as a clinic in area 28 or hospital 38, but these areas are not authorized for automatic restart. If the monitoring application stops running in computing device 12A while patient 4 is in area 28, a programmable beacon device such as beacon 18 may not be able to effectively restart the monitoring application. The beacon application running in computing device 12A may receive the beacon message and then deny authorization to automatically restart the monitoring application.

[0042] Certain conditions warrant that an entity other than the patient is authorized to automatically restart the monitoring application. As an example condition, the present disclosure describes that the monitoring application is not working. To illustrate by way of example, when the patient 4 is at home in region 40 or in a clinic in region 28 or otherwise has access to the network 16, the HMS 22 can receive (e.g., periodically) uploaded patient data from the device query of the IMD 10, which is only possible if the monitoring application is working (e.g., running in the computing device 12). After the device query, the HMS 22 can initiate a remote examination by a cardiologist, but unless the monitoring application is working, for example, in the computing device 12 and running in the foreground according to the operating system, the remote viewing cannot be initiated.

[0043] HMS22 can determine that the monitoring application is not working through various mechanisms, such as based on the lack of communication from the computing device 12, such as in response to a message from the computing system 20 (e.g., query, request, check, etc.). HMS22 can use the second application running in the computing device 12 to provide status information about the monitoring application. If the second application returns status information indicating the non-working state, HMS22 can then transmit a message (e.g., a beacon message) indicating that the second application performs a wake-up process, thereby triggering the execution of the monitoring application. There are many ways to perform the wake-up process, and several examples use various hardware / software components (e.g., operating system components) configured to start (e.g., restart) the monitoring application. For example, in response to a message enabling the wake-up process, the second application can transmit an inter-process message pointing to an operating system component, which is configured to allocate resources (e.g., in terms of processing power, storage capacity, network bandwidth, etc.) for one or more threads / processes, and then schedule the software code for monitoring applications stored in the memory to be executed by the processing circuit in one or more threads / processes.

[0044] The beacon application associated with beacon 18 represents an example of the above-mentioned second application and an alternative to the second application as a client application for HMS22. In some examples, the beacon application determines that the monitoring application is not working, and in response to the determination, further determines whether the current position is in the authentication area as described herein. The beacon application can utilize input data (e.g., beacon messages) indicating the current position received from the beacon 18 (independent of or replacing HMS22 to transmit beacon messages pointing to the computing device 12). Beacon 18 can transmit a beacon message for enabling a wake-up function in the computing device 12A, which is intended to prompt the operating system to execute the monitoring application. As described in further detail below, if the current position corresponds to an authenticated area, the beacon application can successfully restart the monitoring application.

[0045] Computing device 12B may be incorporated into patient 14's attire, such as within clothing, shoes, glasses, a watch or wristband, a hat, etc. In some examples, computing device 12B is a smartwatch or other accessory or peripheral to computing device 12A. In some examples, Figure 1 The wearable computing device 12B in the illustrated example may include electrodes and other sensors to sense physiological signals of the patient 4, and may collect and store physiological data and detect seizures and other health events based on such signals.

[0046] In some examples, the processing circuit in a wearable device (e.g., wearable computing device 12B) or a laptop computer (e.g., personal computing device 12C) may execute the same or similar logic as the logic executed by the processing circuit of computing device 12A. Alternatively, computing device 12C may be a proprietary device provided by the manufacturer of IMD 10. In this way, wearable devices, laptop computing, and / or other devices may perform some or all of the techniques described herein in the same manner as described herein with respect to IMD 10. In some examples, the wearable device operates with IMD 10 and / or computing device 12A as a potential provider of computing / storage resources and sensors for monitoring patient activity and other patient parameters. For example, the wearable device may transmit patient data to computing device 12A or 12B, computing system 20A or 20B, and / or IoT device 30A, 30B, or 30C for storage in non-volatile memory and for calculating parameter values ​​or metric values ​​from patient physiological measurements and other sensed patient data.

[0047] Computing system 20B may be a local server device that operates a computing service locally (e.g., via a radio access technology (RAT)). The monitoring application of IMD 10 and / or computing device 12A may configure one or both devices to expose function calls via an API that is available only on the local area network. In response to receiving input data from a device of computing system 20B, computing device 12A may identify an indication of a function call on the API and initiate execution of the monitoring application in response to the identification.

[0048] An entity, such as a clinic in region 28, hospital 38, or a retirement community in region 40, may operate a computing system, such as computing device 12C in region 40 or computing system 20A in region 28, as a resource for providing medical care to patient 4 via HMS 22. Computing device 12C may include processing circuitry configured with logic that, when executed, operates to detect the presence of a patient device, such as computing device 12A, within region 40 based on a broadcast message (e.g., a heartbeat) distributed by the patient device. In one example, assuming that the broadcast message also indicates the operating state of a monitoring application, computing device 12C may return a beacon message to restart the monitoring application if the application becomes inoperative.

[0049] According to other examples, computing device 12C may utilize IoT device 30B to automatically restart the monitoring application. To illustrate at least one, IoT device 30B may detect the presence of patient 4 and / or its patient device in area 40 based on a broadcast message from computing device 12A. Computing device 12C may configure IoT device 30B to return a beacon message similar to the above example. In addition, IoT device 30B may be configured to return a beacon message in response to a broadcast message from computing device 12A, even if the broadcast message does not indicate a non-working monitoring application. As an alternative, computing device 12C may configure IoT device 30B to broadcast beacon messages to nearby devices to ensure that each patient device within area 40 has a working monitoring application running for the corresponding patient of these patient devices. As another alternative, computing device 12C may configure IoT device 30B to broadcast location data to a beacon application running in computing device 12A.

[0050] Generally speaking, the monitoring application is configured to initiate health event monitoring of various types of information, for example, by identifying tags of interest about the health of patient 4 (e.g., heart health) within a data set of patient 4. The monitoring application can be a client application for HMS22. Once the monitoring application is restarted, it can be communicatively coupled to HMS22 again. The second application in computing device 12B may be different from the monitoring application. In other examples, in the case where computing device 12A does not execute the monitoring application, the application logic may be executed to run in the background or foreground of computing device 12B as a monitoring application.

[0051] For the monitoring application running in the computing device 12A, the second and different application or process (e.g., the operating system process, beacon application or client application of HMS22) running in the computing device 12A can implement an API with functionality for restarting the monitoring application, for example, by means of a function call on the API. There are multiple mechanisms configured to enable such function calls in the computing device 12A, thereby causing the execution of appropriate monitoring application logic (e.g., software code) and / or starting the components of the logic for performing one or more operations including boot scripts or submitting data to HMS22. The API can implement a callback method (e.g., run ()) configured to execute the boot script for the monitoring application. When the second application receives a command (e.g., in a message payload) to enable a function call to execute the monitoring application startup process, the API passes the callback method to the operating system interface for running the application. The operating system interface instantiates the monitoring application context and then executes the boot script. There are a variety of example techniques for initiating any type of data submission, such as, for example, by configuring (application) logic with functionality that, when enabled, triggers computing device 12A to automatically transmit (eg, broadcast) output data to one or more receiving devices.

[0052] HMS22 can be configured to restart monitoring application and perform additional operations using additional technology. HMS22 can use BLE to trigger execution remotely, and may trigger the medical device inquiry performed by computing device 12. HMS22 can use BLE to set the desired operating mode, such as normal operating mode, for monitoring application remotely. When normal operating mode is active, IMD 10 and / or computing device 12A can be programmed to upload the data set of patient data according to the schedule. HMS22 can use BLE to cause further reprogramming of computing device 12A to change the operating mode, such as modifying the schedule. HMS22 can utilize computing device 12, IoT 30 and computing system 20 BLE hardware / software to complete restart and any additional operations, for example, by sending beacon messages to computing device 12 from IoT 30, computing system 20 and other devices in the certified area.

[0053] Medical systems and technologies create hardware / software components to improve the efficiency of evaluating patients with implantable medical devices. Some medical systems and technologies allow certain devices to control monitoring applications without a human user. By eliminating human error, HMS22 is able to keep the connection open to receive recent patient data including health event warnings. Therefore, system 2 allows clinics to continuously be informed of the increased demand for patient evaluation and / or device interrogation while maintaining / improving patient safety (by accurately diagnosing arrhythmias and device abnormalities) and convenience (by reducing or eliminating the number of trips to the doctor's office).

[0054] IMD 10 may generate a health event warning (e.g., including an audible and / or tactile alarm to immediately draw the attention of the patient 4 or clinician 26 of a potential health event) and receive a message from computing system 20A at a later point in time that directs IMD 10 to perform an action. In one example, computing system 20A may transmit the message to computing device 12A (e.g., via IoT device 30A, IoT device 30B, and / or another intermediate device) so that an application running in IMD 10 outputs a data set of patient data corresponding to a potential health event. An intermediate device such as IoT device 30A may operate as an agent of HMS 22 and directed by the HMS, or may operate independently of HMS 22 but still as an intermediary of messages that direct IMD 10 to perform an action.

[0055] HMS22 can determine that the potential health event is a false alarm, and transmit a message instructing IMD 10 to silence or cancel an alarm (e.g., an audible and / or tactile alarm) for the potential health event. There may be cancellation criteria that the potential health event must meet in order to qualify the alarm for cancellation. As an alternative or supplement to the alarm, IMD 10 can broadcast a warning message to any receiver within a certain proximity when a potential health event is detected. The detection of a potential health event by IMD 10 can be a result of an analysis based on current patient data (e.g., a recently sensed physiological signal of patient 4). HMS22 can predict that a warning issued by computing device 12A and / or an alarm issued by IMD 10 corresponds to a false detection, and then transmit a message instructing IMD 10 to cancel the warning and / or alarm.

[0056] Although computing device 12 may be communicatively coupled to IMD 10, it should be noted that several alternatives to IMD 10 include multiple medical devices or no medical device. In some examples, patient 4 may have computing device 12 and IMD 10 as part of a standalone system, and in at least one example, patient 4 does not have a medical device implanted in them. Because a patient's mobile device may allocate some of its resources for use with the patient's medical device, the medical systems and techniques described herein may configure the mobile device and the medical device to collaborate during medical device interrogation or patient data evaluation, for example, by operating on the same layer as a health monitoring service.

[0057] Figure 2 is an example Figure 1 A block diagram of an example configuration of an IMD 10 is shown. Figure 2As shown, IMD 10 includes processing circuitry 50 , memory 52 , sensing circuitry 54 coupled to electrodes 56A and 56B (hereinafter “electrodes 56 ”) and one or more sensors 58 , and communication circuitry 60 .

[0058] The processing circuit 50 may include fixed function circuits and / or programmable processing circuits. The processing circuit 50 may include any one or more of the following: a microprocessor, a controller, a graphics processing unit (GPU), a tensor processing unit (TPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or an equivalent discrete or analog logic circuit. In some examples, the processing circuit 50 may include multiple components (such as any combination of one or more microprocessors, one or more controllers, one or more GPUs, one or more TPUs, one or more DSPs, one or more ASICs, or one or more FPGAs), as well as other discrete or integrated logic circuits. The functions attributed to the processing circuit 50 herein may be embodied as software, firmware, hardware, or any combination thereof. In some examples, the memory 53 includes computer readable instructions that, when executed by the processing circuit 50, cause the IMD 10 and the processing circuit 50 to perform various functions attributed to the IMD 10 and the processing circuit 50 herein. The memory 53 may include any volatile, nonvolatile, magnetic, optical, or electrical media, such as random access memory (RAM), read only memory (ROM), nonvolatile RAM (NVRAM), electrically erasable programmable ROM (EEPROM), flash memory, or any other digital media.

[0059] Sensing circuitry 54 may monitor signals from electrodes 56 to, for example, monitor electrical activity of the heart of patient 4 and generate ECG data of patient 4. In some examples, processing circuitry 50 may identify features of the sensed ECG, such as heart rate, heart rate variability, intrabeat intervals, and / or ECG morphology features, to detect an arrhythmia episode of patient 4. Processing circuitry 50 may store the digitized ECG and features of the ECG used to detect an arrhythmia episode in memory 52 as episode data of a detected arrhythmia episode.

[0060] In some examples, sensing circuit 54 measures impedance of tissue near IMD 10, for example, via electrodes 56. The measured impedance may vary based on respiration and the degree of perfusion or edema. Processing circuit system 50 may determine physiological data related to respiration, perfusion, and / or edema based on the measured impedance.

[0061] In some examples, IMD 10 includes one or more sensors 58, such as one or more accelerometers, microphones, optical sensors, temperature sensors, pressure sensors, and / or any other sensors. In some examples, sensing circuit 52 may include one or more filters and amplifiers for filtering and amplifying signals received from one or more of electrodes 56 and / or sensors 58. In some examples, sensing circuit 54 and / or processing circuit 50 may include a rectifier, a filter and / or an amplifier, a sense amplifier, a comparator, and / or an analog-to-digital converter. Processing circuit 50 may determine physiological data (e.g., physiological parameter values ​​of patient 4) based on signals from sensor 58, which may be stored in memory 52.

[0062] The memory 52 may store applications 70, and data 80 that may be executed by the processing circuit 50. The applications 70 may include monitoring applications 72 and beacon applications 76. The processing circuit 50 may execute the monitoring application 72, thereby enabling event monitoring 74 to detect health events of the patient 4 based on a combination of one or more types of physiological data described herein, which may be stored as patient data 82. In some examples, the patient data 82 may additionally include data sensed by other devices (e.g., computing device 12) and received via the communication circuit 60. Event monitoring 74 may be configured to operate with the monitoring application 72 to apply rules 84 to the patient data 82. The rules 84 may include one or more models, algorithms, decision trees, and / or thresholds. In some cases, the rules 84 may be developed based on machine learning.

[0063] Processing circuitry 50 may execute monitoring application 72 and perform a plurality of operations according to the logic of the executed application. In some examples, in response to an indication of the current patient position, processing circuitry 50 transmits a data set of patient data 82 to a computer via communication circuitry 60. Figure 1 The computing device 12 and / or computing system 20 of the present invention may be included in a message indicating a health event, as described herein. The transmission of the message may occur on an ad hoc basis and as quickly as possible in response to the indication. The communication circuit 60 may include any suitable hardware, firmware, software, or any combination thereof for wirelessly communicating with another device, such as the design device 12 and / or the IoT device 30.

[0064] Some embodiments of the medical system couple IMD 10 to a remote computing system that is configured to run one or more computing services including a health monitoring (computing) service. The remote computing system (e.g., Figure 1The computing system 20 of the geofenced geographic area may transmit packaged data to the IMD 10 located in the geofenced geographic area, thereby prompting the IMD 10 to execute program code that implements the operation of interest. The packaged data may include a message in which the message data identifies the operation of interest. In some examples, the health monitoring service may classify a particular operation as an operation of interest. For example, the result of the operation may provide information that is beneficial to the patient 4. The health monitoring service may desire the result of the operation, for example, to improve the medical care provided to the patient 4. As an example of a health monitoring service, Figure 1 The HMS 22 may be configured to trigger a restart of the monitoring application 72 by the beacon application 76. Once triggered, automatic data submission may be based on certain conditions, such as operating status, recency of stored patient data, other functionality of the service, and the like.

[0065] The health monitoring service may enable functionality to perform an example action that, when initiated by an indication of the current patient location, triggers execution of a monitoring application based on the operating state of the monitoring application. When in operation, the IMD 10 uploads one or more data sets of patient data, but sometimes the IMD 10 fails to successfully upload any data. When the IMD 10 does not perform a data upload within an expected time frame, the IMD 10 may be determined to be non-functional.

[0066] In some examples, monitoring application 72 may be configured to submit various data sets of patient data 82 as responses to requests from a device such as a health monitoring service. Figure 1 HMS22), patient devices (such as Figure 1 computing device 12A) and / or a beacon device (such as Figure 1 The beacon application 76 may be configured to automatically restart the monitoring application 72, for example, by initiating a function call to cause the logic for the monitoring application 72 to execute (e.g., an operating system) and then run as a foreground process. This may be performed in response to a request from a local device (e.g., a beacon device) to a health monitoring service (e.g., HMS 22). As an option, the beacon application 76 may be executed in the IMD 10 to run as a client or agent for the health monitoring service.

[0067] The health monitoring service can initiate an action that causes the beacon application 76 to perform some functions with the monitoring application 72. IMD10 can receive a message identifying the beacon application 76 as a recipient from a device of the health monitoring service, a patient device, and / or a beacon device. Based on the content of the message, the beacon application 76 can be directed to transmit inter-process communications that enable appropriate function calls on the monitoring application 72. Receiving the communication can cause the monitoring application 72 to perform the action of the initiated health monitoring service. In one example, the function call can be configured to open / start or restart the monitoring application 72. In another example, the function call can be configured to cause the monitoring application 72 to transition from a dormant state or an active state. In yet another example, the function call can be configured to resume the stagnation, termination, and / or dormant operation of the monitoring application 72.

[0068] In some examples where monitoring application 72 is configured to receive communications from a health monitoring service over a network, monitoring application 72 may be running in the background and transition to running in the foreground in response to at least one communication. If monitoring application 72 is not running, some communication initiates execution of monitoring application 72. When monitoring application 72 begins running in the foreground after being restarted, IMD 10 may automatically complete data submission (e.g., Figure 1 The logic for the monitoring application 72 may utilize network connectivity with the computing system of the health monitoring service and transmit messages (e.g., response messages to queries) in packetized data.

[0069] The activation may be triggered by the beacon application 76 receiving an indication that the patient 4 entered the geo-fenced area. The health monitoring service may facilitate other forms of activation as set forth herein (without any participation from the patient 4).

[0070] As an example, event monitoring 74 can be configured to monitor the patient 4 based on recording cardiac activity data and / or instructing the patient 4 to Figure 1) of various physiological parameters of the electrical or mechanical activity of the heart 6 of the patient to detect arrhythmias, worsening heart failure, or other cardiac health events (or simply referred to as "cardiac events"). In some examples, event monitoring 74 can detect stroke based on cardiac activity data. In some examples, the sensing circuit 54 can detect brain activity data, such as an electroencephalogram (EEG), via electrodes 56, and event monitoring 74 can detect stroke or epilepsy based solely on brain activity or in combination with cardiac activity data or other physiological data. When event monitoring 74 detects a health event, event monitoring 74 can store patient data 82, which includes the sensing information that caused the detection (and in some cases, data windows before and / or after the detection). Before transmitting the patient data 82, the monitoring application 72 can apply a determination technique to confirm or reject the detected health event. Unless rejected by the determination technique, the monitoring application 72 can generate an alarm for the patient 4 or a warning for the health monitoring service.

[0071] The medical systems and techniques of the present disclosure may combine the IMD 10 with external computing resources, which enhances the IMD 10 in a variety of ways. Figure 1 The described medical systems and techniques include an external location having additional storage resources for patient data. Figure 1 The described medical systems and techniques benefit from participating in (remote) computing services initiated by a remote computing system rather than consuming local processing resources for new / updated software components. These functions can be new functions, firmware updates, supporting software, and other components that improve the operation of the IMD 10.

[0072] The external device of the IMD 10 may include software / hardware components that provide access to storage, processing, and network resources for software applications running in the IMD 10. The IMD 10 may use the external device to enhance the functionality of the monitoring application 72 running in the external device. When the external device is a mobile device, the mobile application may be configured to help the IMD 10 interrogation and patient data evaluation process be more efficient. By implementing the techniques of the present disclosure, the external device may improve the efficiency of device interrogation and patient data evaluation.

[0073] Another example external device may be a beacon device, which may be implemented as an IoT device (e.g., Figure 1IoT device 30). The beacon device can be attached to any physical object and positioned throughout the geo-fenced area. Via the beacon device, the beacon application 76 can be configured to receive beacon communications from a server of a health monitoring service and / or a local area network. In some examples, the beacon communication is a message similar to that described herein, including location data 86 (e.g., an indication of the current patient location). Some messages prompt the enabling of functionality provided by the beacon application 76. As guided in the example function call, the beacon application 76 can communicate with the monitoring application 72 (e.g., as an inter-process communication) based on messages received from the beacon device.

[0074] Monitoring application 72 may become inoperative after running in the background of the operating system of IMD 10. In this case, beacon application 76 must initiate execution of monitoring application 72 and / or transition the execution logic of monitoring application 72 from operating in the background to the foreground. If monitoring application 72 is running in the background (e.g., in sleep mode), beacon application 76 may run a wake-up process with the operating system of IMD 10 to transition monitoring application 72 to the foreground.

[0075] Figure 3 is a block diagram illustrating an example configuration of a computing device 12 of a patient 4, which may correspond to Figure 1 Either of the illustrated computing devices 12A and 12B (or both operating in coordination). In some examples, computing device 12 takes the form of a smartphone, laptop computer, tablet computer, personal digital assistant (PDA), smart watch, or other wearable computing device. In some examples, IoT device 30 may be similar to Figure 3 The configuration of the computing device 12 illustrated in FIG.

[0076] like Figure 3 As shown in the example of , the computing device 12 can be logically divided into a user space 102, a kernel space 104, and hardware 106. The hardware 106 may include one or more hardware components that provide an operating environment for components executing in the user space 102 and the kernel space 104. The user space 102 and the kernel space 104 may represent different sections or segments of memory, wherein the kernel space 104 provides higher privileges to processes and threads than the user space 102. For example, the kernel space 104 may include an operating system 120 that operates with higher privileges than components executing in the user space 102.

[0077] like Figure 3 As shown, hardware 106 includes processing circuitry 130, memory 132, one or more input devices 134, one or more output devices 136, one or more sensors 138, and communication circuitry 140. Although for purposes of illustration, Figure 3 1 is shown as a standalone device, but the computing device 12 may be any component or system including a processing circuit or other suitable computing environment for executing software instructions, and does not necessarily include, for example, Figure 3 One or more elements shown in .

[0078] Processing circuitry 130 is configured to implement functions and / or processing instructions for execution within computing device 12. For example, processing circuitry 130 may be configured to receive and process instructions stored in memory 132 that provide functionality for components included in kernel space 104 and user space 102 to perform one or more operations in accordance with the techniques of this disclosure. Examples of processing circuitry 130 may include any one or more microprocessors, controllers, GPUs, TPUs, DSPs, ASICs, FPGAs, or equivalent discrete or integrated logic circuits.

[0079] Memory 132 may be configured to store information within computing device 12 for processing during operation of computing device 12. In some examples, memory 132 is described as a computer-readable storage medium. In some examples, memory 132 includes temporary storage or volatile memory. Examples of volatile memory include random access memory (RAM), dynamic random access memory (DRAM), ferroelectric random access memory (FRAM), static random access memory (SRAM), and other forms of volatile memory known in the art. In some examples, memory 132 also includes one or more memories configured for long-term storage of information, such as non-volatile storage elements. Examples of such non-volatile storage elements include magnetic hard disks, optical disks, floppy disks, flash memory, or various forms of electrically programmable memory (EPROM) or electrically erasable and programmable (EEPROM) memory.

[0080] One or more input devices 134 of computing device 12 may receive input, for example, from patient 4 or another user. Examples of input are tactile, audio, dynamic, and optical input. As examples, input device 134 may include a mouse, keyboard, voice response system, camera, button, control pad, microphone, presence-sensitive or touch-sensitive component (e.g., screen), or any other device for detecting input from a user or machine.

[0081] One or more output devices 136 of computing device 12 may generate output, for example, to patient 4 or another user. Examples of output are tactile output, audio output, and visual output. Output devices 134 of computing device 12 may include a presence-sensitive screen, a sound card, a video graphics adapter card, a speaker, a cathode ray tube (CRT) monitor, a liquid crystal display (LCD), a light emitting diode (LED), or any type of device for generating tactile, audio, and / or visual output.

[0082] One or more sensors 138 of computing device 12 may sense physiological parameters or signals of patient 4. Sensors 138 may include electrodes, accelerometers, optical sensors, and other sensors, and sensing circuitry (e.g., including an ADC), similar to those described above with respect to IMD 10 and Figure 2 Those described.

[0083] The communication circuitry 140 of the computing device 12 may communicate with other devices by transmitting and receiving data. The communication circuitry 140 may include a network interface card, such as an Ethernet card, an optical transceiver, a radio frequency transceiver, or any other type of device that can send and receive information. For example, the communication circuitry 140 may include a radio transceiver configured for use in accordance with a wireless communication protocol such as 3G, 4G, 5G, WiFi (e.g., 802.11 or 802.15 ZigBee), Or BLE standards or protocols to communicate.

[0084] like Figure 3 As shown, the monitoring application 150 is executed in the user space 102 of the computing device 12. The monitoring application 150 can be logically divided into a presentation layer 152, an application layer 154, and a data layer 156. The presentation layer 152 may include a user interface (UI) component 160 that generates and presents a UI view of the health monitoring application 150. The presentation layer 152 may include an API component 162 that instantiates an API having functions for using software modules of the application layer 154.

[0085] The application layer 154 may include, but is not limited to, an event engine 170, an event assistant 172, a location service (client) 174, and a beacon service (client) 180. The event engine 172 may be responsive to receiving an indication of the current patient location from a device of the HMS 22 or from a different device. The event engine 172 may control the execution of any of the operations in response to the indication of the current patient location, particularly in the case where the current patient location indicates that the patient 4 has entered a geographic area (e.g., a geo-fenced area). The event engine 172 may be responsive to receiving a transmission from the IMD 10 indicating that the IMD 10 has detected a health event (e.g., an acute health event).

[0086] In some examples, event engine 170 analyzes sensed data 190, and in some examples, analyzes patient input 192 and / or EHR data 194 to determine if there is sufficient likelihood that patient 4 is experiencing a health event. Sensed data 190 may include data received as part of a transmission from IMD 10, additional data transmitted from IMD 10 (e.g., in "real time"), and physiological and other data collected by computing device 12 and / or IoT device 30 related to the condition of patient 4. As an example, sensed data 190 from computing device 12 may include one or more of the following: activity level, walking / running distance, resting energy, active energy, exercise minutes, quantification of standing, physical fitness, body mass index, heart rate, low heart rate events, high heart rate events and / or irregular heart rate events, heart rate variability, walking heart rate, heart beat series, digitized ECG, blood oxygen saturation, blood pressure (systolic and / or diastolic), respiratory rate, maximum oxygen volume, blood glucose, peripheral perfusion, and sleep patterns.

[0087] The computing system HMS22 for operating the health monitoring service can be configured to transmit a request for patient input 192 submitted as sample data over a network. The health monitoring application 150 can generally receive the request in the form of some content for presentation in a user interface (UI) view. In one example, the health monitoring application 150 generates a UI view having a UI element configured to receive patient input 192.

[0088] Patient input 192 may include responses to inquiries about the current condition of patient 4, input by patient 4 or another user (such as clinician 26) proposed by health monitoring application 150. Inquiries and responses may occur in response to entering a geo-fenced area and receiving messages from a device of HMS22, for example as part of long-term monitoring of the health of patient 4. The health data recorded by the user may include one or more of the following: exercise and activity data, sleep data, symptom data, medical history data, quality of life data, nutritional data, medication or compliance data, allergy data, demographic data, weight and height. EHR data 194 may include any information about the historical condition, symptoms or treatment of the above-mentioned patient 4. EHR data 194 may involve a history of cardiac arrest, tachyarrhythmia, myocardial infarction, stroke, epilepsy, chronic obstructive pulmonary disease (COPD), renal dysfunction or hypertension, a history of procedures (such as ablation or cardioversion), and healthcare utilization. EHR data 194 may also include demographic and other information of patient 4, such as age, gender, height, weight and BMI.

[0089] Assistant 172 can provide a conversational interface for patient 4 and / or clinician 26 to exchange information with computing device 12. Event assistant 176 can ask the user about the condition of patient 4. The response from the user can be included as patient input 192. Event assistant 172 can use natural language processing and contextual data to interpret the user's words. In some examples, in addition to receiving responses to queries raised by the assistant, assistant 172 can be configured to respond to queries raised by the user. In some examples, event assistant 172 can provide instructions to and respond to inquiries from patient 4 or clinician 26 about the treatment of patient 4.

[0090] Location service 174 may determine the location of computing device 12, and thereby determine the estimated location of patient 4. Location service 174 may use Global Positioning System (GPS) data, multilateration, and / or any other known technique for locating a computing device.

[0091] The beacon service 180 may receive messages from a (local or remote) health monitoring service running in the computing system. The health monitoring service may prompt the computing device 12 to restart the monitoring application 150 via the operating system and then perform one or more operations via the monitoring application 150. An operation may be a data commit, for example, a missed transaction that failed to complete for some reason (e.g., being shut down).

[0092] Further in response to the indication of the current location of the patient 4, the monitoring application 150 may configure the computing device 12 to synchronize the sensed patient data and the device query data with an external storage location. Figure 1 The user of the IMD 10) of the medical device generates sensed patient data from various signals. In some examples, the rule engine 172 can store information defining a schedule of clinic visits and services from the computing system of the HMS22 in the memory of the event assistant 172.

[0093] API component 162 may include functionality that performs desired operations when enabled. Figure 1 The HMS 22 of the health monitoring service or the computing service of the location service can transmit a message to initiate the desired operation. In one example, the computing system of the health monitoring service can transmit a message for the API component 162. The message can identify, for example, a function call for executing (e.g., restarting) the application in the event that the monitoring application 150 becomes inoperative.

[0094] As described herein, when an event including a non-health event is identified, various actions are allowed for the patient device. HMS22 can initiate an action that benefits from patient health monitoring (e.g., by restarting the monitoring application 150). The computing device under the guidance of HMS22 can transmit signal data that ultimately causes the event engine 172 to perform one or more operations. In some examples, the monitoring application 150 may become inoperative; however, the health monitoring service can continue to require / expect the latest patient data from the patient device, and for this purpose, perform one or more operations to trigger the restart of the monitoring application 150.

[0095] Medical systems and techniques may implement location-based and remote control techniques to implement such a restart in computing device 12, such as in response to determining that the current location of the patient and / or computing device 12 corresponds to an authenticated area and in response to determining that monitoring application 150 is not functioning. There are a number of ways to

[0096] The location data (e.g., geographic coordinates) of the geographic area where the patient resides can be programmed into a computing device associated with the HMS 22, so that a patient entering the geographic area (e.g., their home or residence) triggers a restart of the monitoring application 150. The computing device can determine that the patient is currently located within the geographic area through various mechanisms, and transmit a message (e.g., an indication of the current patient location); an example mechanism can enable the computing device to identify a patient device (or only a patient) within close proximity, for example, by broadcasting signal data to illegally respond and / or receiving signal data from a patient device (e.g., a broadcast of signal data). Detecting a patient device through such a mechanism causes the computing device to trigger a restart of the monitoring application 150 at the patient device. In some examples, detecting a patient can be optional; for example, a computing device can broadcast signal data that, when captured by a patient device, causes the patient device to initiate a restart of the monitoring application 150. Radio waves can embody signal data for indication. Therefore, geographic coordinates can be used to configure a geofence for a home or residence.

[0097] Medical systems and techniques may implement geo-fencing techniques to enable remote restart of any application, such as when a patient is at their residence and the monitoring application 150 becomes inoperative without their knowledge. Devices (e.g., beacon devices) within a geo-fenced area (such as the geographic area described above) may operate as part of a local health monitoring service running on a local computing system, such that a patient entering their residence causes the beacon device to detect the patient's presence, identify an event indicative of an inoperative monitoring application 150, and trigger a restart of the monitoring application 150 from the computing device 12.

[0098] Figure 4is a block diagram illustrating an operational perspective of HMS 22. HMS 22 may be implemented in computing system 20, which may include hardware components embodied in one or more physical devices, such as the hardware components of computing device 12. Figure 4 Provides an operational perspective of the HMS 22 when hosted as a cloud-based platform. Figure 4 In the example of FIG. 1 , the components of HMS 22 are arranged according to multiple logical layers that implement the technology of the present disclosure. Each layer can be implemented by one or more modules including hardware, software, or a combination of hardware and software.

[0099] Computing devices such as computing device 12, IoT device 30, computing device 38, and computing device 42 operate as clients that communicate with HMS 22 via interface layer 200. Computing devices typically execute client software applications, such as desktop applications, mobile applications, and web applications. Interface layer 200 represents a set of application programming interfaces (APIs) or protocol interfaces provided and supported by HMS 22 for client software applications. Interface layer 200 can be implemented with one or more web servers.

[0100] like Figure 4 As shown, HMS22 also includes an application layer 202, which represents a collection of services 210 for implementing the functionality attributed to HMS in this article. The application layer 202 receives information from client applications, for example, an alarm for receiving acute health events from a computing device 12 or an IoT device 30, and further processes the information according to one or more services in the service 210 to respond to the information. The application layer 202 can be implemented as one or more discrete software services 210 executed on one or more application servers (e.g., physical or virtual machines). That is, the application server provides a runtime environment for executing the service 210. In some examples, the functions of the functional interface layer 200 and the application layer 202 as described above can be implemented at the same server. The service 210 can communicate via a logical service bus 212. The service bus 212 generally represents a logical interconnection or interface group that allows different services 210 to send messages to other services such as through a publish / subscribe communication model.

[0101] The data layer 204 of the HMS 22 provides persistence for information in the PPEMS 6 using one or more data repositories 220. The data repository 220 can generally be any data structure or software that stores and / or manages data. Examples of data repositories 220 include, but are not limited to, relational databases, multidimensional databases, maps, and hash tables, to name a few.

[0102] like Figure 4As shown, each of the services 230-238 is implemented in a module form within HMS22. Although shown as a separate module for each service, in some examples, the functions of two or more services can be combined into a single module or component. Each of the services 230-238 can be implemented in software, hardware, or a combination of hardware and software. In addition, the services 230-238 can be implemented as independent devices, separate virtual machines or containers, processes, threads, or software instructions generally for execution on one or more physical processors.

[0103] The event processor service 230 may respond to receiving an alert transmission from the computing device 12 and / or IoT device 30 indicating that the IMD 10 has detected an acute health event for the patient and, in some examples, indicating that the transmission device confirms the detection. The event processor service 230 may initiate the performance of any operations in response to the detection of an acute health event attributed herein to the HMS 22, such as communicating with the patient 4, clinician 26, and care provider 40, launching the drone 46, and in some cases analyzing data to confirm or override the IMD 10's detection of the health event, and canceling any warnings or alarms generated for the health event.

[0104] The records management service 238 may store the patient data included in the received alert message within the event record 252. The alert service 232 may package some or all of the data from the event record (in some cases with additional information as described herein) into one or more alert messages for transmission to the clinician 26 and / or care provider 40. The care giver data 256 may store data used by the alert service 232 to identify to whom to send an alert based on the location of potential bystanders 26 and care givers 40 relative to the location of the patient 4 and / or the suitability of the care provided by the care giver 40 to the acute health event experienced by the patient 4.

[0105] In an example where the HMS 22 performs analysis to confirm or override the detection of a health event by the IMD 10, the event processor service 230 may apply one or more rules 250 to the data received in the alarm message, such as a feature vector derived from the data by the event processor service 230. The rules 250 may include one or more models, algorithms, decision trees, and / or thresholds that may be developed by the rule configuration service 234 based on machine learning. Example machine learning techniques that may be used to generate the rules 250 may include various learning styles, such as supervised learning, unsupervised learning, and semi-supervised learning. Example types of algorithms include Bayesian algorithms, clustering algorithms, decision tree algorithms, regularization algorithms, regression algorithms, example-based algorithms, artificial neural network algorithms, deep learning algorithms, dimensionality reduction algorithms, and the like. Various examples of specific algorithms include Bayesian linear regression, boosted decision tree regression and neural network regression, back-propagation neural network, a priori algorithm, K-means clustering, K-nearest neighbors (kNN), learning vector quantization (LVQ), self-organizing map (SOM), locally weighted learning (LWL), ridge regression, least absolute shrinkage and selection operator (LASSO), elastic net and least angle regression (LARS), principal component analysis (PCA), and principal component regression (PCR).

[0106] In some examples, in addition to the rules used by HMS22 to confirm the detection of health events (or in examples where HMS22 does not confirm the detection of events), the rules 250 maintained by HMS22 may include rules 196 utilized by computing device 12 and rules 84 used by IMD 10. In such examples, the rule configuration service 250 may be configured to develop and maintain rules 196 and rules 84. The rule configuration service 234 may be configured to modify these rules based on event feedback data 254 indicating whether the detection and confirmation of acute health events by IMD 10, computing device 12, and / or HMS 22 are accurate. The event feedback 254 may be received from the patient 4, for example, via the computing device 12, or from the care provider 40 and / or EHR 24. In some examples, the rule configuration service 234 may utilize event records from true and false detections (as indicated by the event feedback data 254) and confirmation of supervised machine learning to further train the model included as part of the rules 250.

[0107] like Figure 4 As illustrated in the example of , service 210 may also include an assistant configuration service 236 for configuring and interacting with an event assistant 176 implemented in computing device 12 or other computing devices.

[0108] In some examples, the health monitoring service 250 may be active on a different network or the same network as a patient who is also a medical device user. To operate within a geographic region, the health monitoring service 250 configures one or more computing devices as a network accessible (for example) by the patient's devices (including medical devices and possibly their mobile devices). The patient can enter the (e.g., geo-fenced) geographic region and gain (e.g., instant) access to the computing device (and, if desired, the health monitoring service 250) through at least one connection.

[0109] The present disclosure describes herein a variety of applicable technologies for connection between a patient's device and a device of a health monitoring service 250, including radio technologies that enable data communication between devices in the form of radio waves. The present disclosure generally describes signal data when referring to radio wave encoded data. The patient may have a mobile device that is configured to transmit various information in the form of signal data through any compatible connection (e.g., a wireless connection through NFC, Bluetooth, or BLE; a network connection through a local area network or the Internet; etc.). The patient's mobile device may be configured to capture signal data from a device located in a geographic area, and in response, initiate an action to restart the monitoring application 150 after becoming inoperative. Such a connection may be further characterized as a local connection with a local device, such as a beacon device, a device with a GPS module (e.g., via a transmitter and / or receiver), a local computing device such as a local computing device operated by the health monitoring service 250, a medical device, and any other device compatible with a local connection. Where appropriate, the medical device may be configured to initiate a restart of the monitoring application 150 when it is determined that the application becomes inoperative.

[0110] In general, the signal data described above may be generated to convey any type of information including location data. A computing device (e.g., under the direction of a computing service such as health monitoring service 250) may transmit signal data including an indication (e.g., a message) of a (e.g., current) patient location. The computing device may support other messages (e.g., control messages) including commands / indications to restart a non-functioning application, interface messages to enable a function call for restarting a non-functioning application, and the like.

[0111] As an alternative computing service to the health monitoring service 250, the patient's mobile device can receive a message (e.g., an indication of the current patient location) from a location service (e.g., a GPS service). The computing device associated with the location service can be configured within the patient's geographic area. According to another alternative example, the patient's mobile device can be configured (e.g., with a GPS receiver) to receive location data indicating the current patient location directly from the computing service and without the need for a computing device (e.g., operating on behalf of the health monitoring service 250 or the location service).

[0112] The medical systems and techniques described herein are applicable to computing systems for personal health monitoring of patients without actually being present in the same area and away from the patient's location (i.e., remotely). In summary, the medical systems and techniques described herein can reduce the time spent by the health monitoring service 250 to query an implantable medical device (such as an implantable pacemaker, a cardiac assist device (VAD), a defibrillator, a cardiac monitor, or other cardiac device). In addition to improving input from device experts when the patient is located at a distance and improving clinical decision making due to immediate input from experts, improved efficiency and patient flow can also be observed using this technology.

[0113] Alternatively, the geographic area may include a local health monitoring service 250 configured with a GPS receiver that operates to receive the coordinates of the patient at his current location and / or the coordinates of the clinic. Based on a comparison between the two sets of coordinates, the device of the local health monitoring service can determine the time when the patient is currently located at the clinic, and then, in response to the determination, initiate any data submission that is overdue or expires at the clinic appointment time or the current patient time. A different embodiment of the location data can be an indication (e.g., a message) that the current patient location is within a predefined proximity (e.g., an authenticated area).

[0114] Figure 5 is a flow diagram illustrating example operation of a computing device of a medical system operating in accordance with one or more techniques of this disclosure. Figure 5 The example operations depicted in Figure 1 and Figure 3 1, but may be described with respect to a computing device 12 depicted in FIG. 1 , but may be described with respect to a client application that may implement a health monitoring service and / or a service. Figures 1 to 4 The techniques described herein may be performed by processing circuits of any one or more of the devices (e.g., computing device 12, computing system 20, IoT device 30, IMD 10, or health monitoring service (HMS) 22). The techniques described herein may be performed by processing circuits of any one or more of these devices.

[0115] according to Figure 5 In the illustrated example, processing circuitry of system 2 (e.g., processing circuitry 130 of one or more computing devices 12) provides computing services for health event monitoring based on patient physiological data (e.g., sensing data 190) and patient input (e.g., patient input 192) generated by sensing circuitry 52 of IMD 10. Figure 5 In the illustrated example, the processing circuit detects a change in patient health caused by an acute health event such as arrhythmia or cardiac arrest.

[0116] This disclosure describes "health monitoring" as a computing service that engages one or more devices to support any given patient with a medical device, such as an implantable medical device or a wearable device. Such a patient may benefit from a health monitoring service that extends the patient's current medical care beyond, for example, the patient's personal device.

[0117] As described above, patients often rely on personal devices (e.g., medical devices and mobile devices) for health monitoring outside of clinical settings. When limited to the patient's personal device, the patient cannot benefit from external resources. Patients can accept health monitoring beyond their (personal) devices to some extent, such as monitoring from external devices over a network; however, the patient's own personal device inhibits such health monitoring methods due to delays in medical device inquiries, inconsistencies in patient data, inefficiencies in patient data evaluation, etc. The external device can be communicatively coupled to the patient's personal device and arrange the submission of patient data and other transmissions from the patient's device to the external device or to another external location via a variety of mechanisms.

[0118] As described herein, health monitoring services are typically based on patient data to detect changes in patient health. For example, with the patient participation described above, a computing system running a health monitoring service can utilize pacemakers, defibrillators, monitors, and implantable medical devices (e.g., Figure 1 The health monitoring service may configure the computing system to operate as a beacon device and advantageously employ beacon messages to trigger execution and / or activation of application logic on the patient device.

[0119] To get started Figure 5 In an example operation of a health monitoring service, a processing circuit determines the working state of a monitoring application in a patient device (300). The patient device can be a mobile device configured to receive a beacon message and enable appropriate functions for each corresponding application in response. As described herein, the monitoring application can be configured to run in the mobile device as a client application for a health monitoring service, and to this end, perform various functions on behalf of the health monitoring service and benefit the patient. The monitoring application provides various patient data generated by the medical device to the computing system.

[0120] exist Figure 5In the example of , the processing circuit determines whether the monitoring application is working or considered to be inoperative in the patient device (302). The patient device can provide the operating status of the monitoring application to another second application in a variety of ways. The second application can run in the same computing device or a different computing device. The operating system can generate the operating status as part of the diagnostic tool. It should be noted that there are alternatives to using the diagnostic tool to determine whether the monitoring application is working or not working, and therefore, the diagnostic tool is not necessary for this determination; for example, if the monitoring application fails to transmit any patient data to the health monitoring service despite being requested and / or planned to transmit any patient data to the health monitoring service, or fails to respond to a recent message from the health monitoring service, the processing circuit can determine that the monitoring application has stopped and become inoperative.

[0121] In response to determining that the monitoring application is not inoperative (and therefore operational) (NO of 302), the processing circuitry may return to determining the operational state of the monitoring application and waiting for the operational state to change from operational to inoperative (300).

[0122] In response to determining that the monitoring application is not working (yes of 302), the processing circuit receives input data indicating the current location of the patient (304). In one example, the input data can be an indication message for a second application for initiating a function call, which is configured to restart the monitoring application based on the patient being located in a geo-fenced geographic area that is authenticated as a known patient location (e.g., home or residence). The indication can be a set of GPS coordinates provided by a GPS receiver in a computing device within a certain proximity of one of the patient devices. The patient device can be configured with a GPS receiver for receiving the set of GPS coordinates from the computing device or alternatively directly from a location service such as a GPS service. In some examples, the local computing system can run a location service for a (e.g., geo-fenced) geographic area and transmit a message to the patient device in response to the patient's presence in the area. Alternatively, the input data can notify the patient of their proximity to the geographic area. The message can be arranged as packaged data according to any communication technology (e.g., protocol).

[0123] As described herein, the example remote health monitoring service 250 can be configured as a computing service (e.g., a cloud service) that can be accessed via a network from any geographic area using any number of communication protocols (such as the Internet) as described herein. The remote health monitoring service 250 can combine the local health monitoring service 250 with a network service (e.g., a cloud service) that runs on network-accessible resources and is built using network functions compatible with any number of protocols. The network-accessible resources at the external location can be used to store patient data and facilitate the medical care of the patient. Similar to the local health monitoring service 250, the remote health monitoring service 250 can initiate a main process of the monitoring application to perform several operations, including automatically restarting an application that is not working.

[0124] The computing system of the geo-fenced geographic area can utilize low-energy wireless communication technology such as BLE as the underlying protocol for transmitting messages indicating the current location of the patient. In some examples, the indication can be in the form of beacon messages (e.g., advertisements) broadcast at regular intervals by a beacon device with BLE capabilities. The computing system can operate as a beacon device and / or configure one or more beacon devices to operate within the geo-fenced geographic area.

[0125] The patient device receives the beacon message by capturing signal data (e.g., radio waves) of the wireless connection of the beacon device, and proceeds to determine that the current location of the beacon device is within the geo-fenced geographic area based on the message content. The patient device can determine that the beacon message is directed to the application and is configured to trigger an action of the patient device. In one example, the geo-fenced geographic area is based on iBeacon TM iBeacon Technology TM The computing system operated by the device can use iBeacon TM The advertisement message (as an example embodiment of a beacon message) is transmitted to any device in the area. In turn, the iBeacon running on the patient's device TM The application is listening for iBeacon TM When the device's signal is captured by iBeacon TM Advertising messages to sense iBeacons operated by the computing system TM In response to the advertisement, the iBeacon TM The application transmits confirmation of connection to a computing system running a computing service in a geofenced geographic area. The connection to the computing system allows the computing service to provide secure and hyper-contextual content (e.g., official documents). TM As an alternative to technology, the patient device can use Eddystone TM technology, also receives / transmits beacon messages and

[0126] exist Figure 5 In an example of, the processing circuit determines whether the patient is within an authenticated (e.g., geofenced) geographic area (e.g., Figure 1 The processing circuit may determine that the patient and / or the patient's device is not currently located in the authenticated area (306). Based on determining that the patient and / or the patient's device is not currently located in the authenticated area (306 no), the processing circuit may wait for a change to the current location, such as when the patient moves to a second geographic area and the patient device receives new input data indicating the second geographic area as the new current location (304). In one example, a beacon application running in the patient device may identify the second geographic area as an environment in which the patient resides, thereby authorizing the beacon application to trigger execution of the monitoring application. The connection to the computing system running the health monitoring service also facilitates execution of logic for the monitoring application and access to the patient account (e.g., without first providing credentials).

[0127] exist Figure 5 In the example of , based on determining that the patient and / or the patient's device is currently located in the authenticated area (306's), the processing circuit restarts the monitoring application (308), for example, via a computerized process enabled by means of a function call. An example implementation of the function call may be a wake-up function initiated by an API. As described herein, the API may be implemented by a second application referred to as a beacon application. Typically, without patient participation, the processing circuit of the patient's device may not be able to restart the monitoring application, for example, to initiate an inquiry of the medical device and possible additional actions. Enabling the API to implement functionality for use by a health computing service allows another computing device (and another application) to initiate a function call for automatically restarting the monitoring application and trigger the execution of various actions.

[0128] The medical systems and techniques described herein can implement geo-fencing techniques for a computing service that operates on a local and / or remote computing system and is configured to recognize certain events, such as when a patient is at home. Location data for the geographic area in which the patient's home is located can be programmed into a computing device at home, such that a patient entering the home (or simply being at home) causes the computing device to identify the patient and trigger execution of logic for a monitoring application from the patient's device (or just the patient). Thus, a geo-fence can be configured for a home using geographic coordinates.

[0129] The medical systems and techniques described herein may dedicate a health computing service to such restart / triggering. As an example action, restarting the monitoring application may further trigger a service request to the health monitoring service. Enabling the appropriate function call via the API may include initiating a service request from the patient account to the remote computing system of the health monitoring service as part of the function call. Restarting the monitoring application may be in response to determining that the current patient location corresponds to an authenticated region, generating a new network connection to the health monitoring service as part of the function call, or restoring a previous network connection to the health monitoring service as part of the function call.

[0130] The device of the local health monitoring service can be configured using a variety of alternative (e.g., non-geofencing) technologies, and as such, can be configured with a GPS receiver that operates to receive the coordinates of the patient at their current location. Based on a comparison between the two sets of coordinates, the device of the local health monitoring service can determine when the patient is currently located in their home or residential clinic, and then in response to the determination, restart the monitoring application and complete the authentication sequence for the health monitoring service (e.g., without providing credentials). A different embodiment of the location data can be an indication (e.g., a message) that the current patient location and the location of the patient's home are within a predefined proximity. An example of this indication can be transmitted from an NFC module.

[0131] To illustrate by way of example, the medical systems and techniques are configured to monitor device interrogation and identify situations where the device interrogation has been interrupted for any reason. In addition to the data set of patient data collected and stored by the medical device, the monitoring application may collect and store other data sets of patient data in the patient's mobile device and then submit both data sets for the interrupted interrogation. By mitigating such interruptions and keeping the monitoring application working and active, the medical systems and techniques may achieve low latency in the amount of time that elapses between the capture of a data set and the transmission of the data set for external (e.g., remote) storage.

[0132] As another example, in addition to receiving secure notifications about health event detection (e.g., cardiac arrhythmia), confidential notifications, and other private data, a computing system running a health monitoring service can also be immediately notified of device failures or application outages. These notifications are ensured by the service controlling the geo-fenced area.

[0133] If the patient device is turned off and / or the monitoring application is disabled or closed, the computing device initiates a process (e.g., a wake-up process) to load into memory and execute the logic of the monitoring application to run the main process and possible additional processes. The main process of the monitoring application performs multiple operations, including at least one data submission of patient data from the patient device to the computing device of the clinic. The medical system can implement functions on the API for prompting the main process to perform operations, such as the transmission of patient data submitted for scheduling data that expired in the past. The computing device at the clinic can enable a function call to trigger the (e.g., periodic) transmission of patient data to facilitate pending clinic appointments. If the local health monitoring service previously submitted a request for a specific data set for patient data and the request was not filled by the monitoring application, the computing device at the clinic can enable a function call to trigger the transmission of the requested data submission, otherwise the data submission is expired. Instead of being disabled or closed, the monitoring application can be dormant, for example, where the main process runs on the processing circuit, but is restricted to the background according to another example. In yet another example, the main process may have caused a failure and does not respond to any inter-process communication.

[0134] Figure 5 The illustrated order and flow of operations are examples. Figure 5 The steps of may be performed in a different order or simultaneously. For example, the processing circuitry may determine that the patient is within an authenticated (e.g., geo-fenced) geographic area and the monitoring application is not operating at the same time. In other examples according to the present disclosure, more or fewer thresholds may be considered. Further, in some examples, as directed by the user, the processing circuitry may or may not perform, for example, via external device 12 or computing device 100. Figure 5 For example, a patient, clinician, or other user can turn on or off functionality for identifying changes in a patient's health status (e.g., using Wi-Fi or cellular service) or locally (e.g., using an application provided on the patient's cell phone or using a medical device programmer).

[0135] The techniques described in the present disclosure may be implemented at least in part in the form of hardware, software, firmware, or any combination thereof. For example, various aspects of these techniques may be implemented in one or more microprocessors, DSPs, ASICs, FPGAs, or any other equivalent integrated or discrete logic QRS circuits, and any combination of such components, which are embodied in an external device (such as a physician or patient programmer, simulator, or other device). The terms "processor" and "processing circuit" may generally refer to any of the aforementioned logic circuits, alone or in combination with other logic circuits, or any other equivalent circuit, alone or in combination with other digital or analog circuits.

[0136] For various aspects implemented in software, at least some of the functionality attributed to the systems and devices described in this disclosure may be embodied as instructions on a computer-readable storage medium, such as RAM, DRAM, SRAM, magnetic disk, optical disk, flash memory, or various forms of EPROM or EEPROM. The instructions may be executed to support one or more aspects of the functionality described in this disclosure.

[0137] In addition, in some aspects, the functions described herein can be set in dedicated hardware and / or software modules. Describing different features as modules or units is intended to highlight different functional aspects, and does not necessarily imply that such modules or units must be implemented by separate hardware or software components. On the contrary, the functions associated with one or more modules or units can be performed by separate hardware or software components, or integrated in common or separate hardware or software components. In addition, these techniques can be fully implemented in one or more circuits or logic elements. The technology disclosed herein can be implemented in various devices or equipment, including an IMD, an external programmer, a combination of an IMD and an external programmer, an integrated circuit (IC) or a group of ICs and / or discrete circuits residing in an IMD and / or an external programmer.

[0138] The following examples are a non-limiting list of clauses in accordance with one or more techniques of the present disclosure.

[0139] Embodiment 1. A method executed by a processing circuit of a computing device, the method comprising: determining that a monitoring application previously executed by the processing circuit is not working; receiving input data indicating a current location of a patient from an input device of the computing device; determining whether the current location of the patient corresponds to a certified area of ​​the patient; and in response to determining that the current location corresponds to the certified area and in response to determining that the monitoring application is not working, restarting the monitoring application.

[0140] Embodiment 2. The method of embodiment 1, wherein receiving the input data comprises capturing signal data via a wireless connection to a global positioning service (GPS) receiver.

[0141] Embodiment 3. The method according to embodiment 1, wherein receiving the input data further comprises: capturing signal data through a network connection with a computing service.

[0142] Embodiment 4. The method of embodiment 1, wherein receiving the input data further comprises: capturing signal data via a wireless connection with a beacon device.

[0143] Embodiment 5. The method of embodiment 1, wherein receiving the input data further comprises: capturing signal data through a local connection with a medical device.

[0144] Embodiment 6. A method according to any one of embodiments 1 to 5, wherein determining that the current location corresponds to the authenticated area further comprises determining that the current location corresponds to a residence or home of the patient.

[0145] Embodiment 7. The method of any one of embodiments 1 to 6, wherein receiving the input data comprises receiving the input data in a message transmitted by a device of a computing service.

[0146] Embodiment 8. The method of any one of Embodiments 7, wherein the device is located within the authenticated area.

[0147] Embodiment 9. The method of any one of Embodiments 7, wherein the device is located in a location external to the authenticated area.

[0148] Embodiment 10. A method according to any one of embodiments 1 to 6, wherein the computing service includes a health monitoring service.

[0149] Embodiment 11. The method according to any one of embodiments 1 to 6, wherein the computing service includes a location service.

[0150] Embodiment 12. The method of any one of Embodiments 1 to 11, wherein the computing service operates on a computing system comprising at least one of a local computing system or a remote computing system.

[0151] Embodiment 13. A method according to any one of embodiments 1 to 12, wherein receiving the input data also includes receiving, by the input device, the connection request for the device in response to the connection request from the device of the computing service, and the method also includes: transmitting, by the output device of the computing service, a confirmation to the device in response to the connection request from the device of the computing service.

[0152] Embodiment 14. A method according to any one of embodiments 1 to 13, wherein restarting the monitoring application further comprises: in response to determining that the current patient location corresponds to the authenticated area, automatically completing an authentication sequence for a health monitoring service to access a patient account.

[0153] Embodiment 15. A method according to any one of embodiments 1 to 14, wherein restarting the monitoring application further comprises: in response to determining that the current patient position corresponds to the authenticated area, initiating a function call to trigger execution of the monitoring application.

[0154] Embodiment 16. A method according to any one of embodiments 1 to 15, wherein restarting the monitoring application further comprises: as part of the function call, initiating an active working mode of the monitoring application, wherein the monitoring application will run in the foreground of the computing device.

[0155] Embodiment 17. The method of any one of Embodiments 1 to 15, wherein restarting the monitoring application further comprises submitting credentials for an authentication sequence for a patient account as part of the function call.

[0156] Embodiment 18. The method of any one of Embodiments 1 to 15, wherein restarting the monitoring application further comprises, as part of the function call, overriding a requirement for credentials for an authentication sequence for a patient account.

[0157] Embodiment 19. A method according to any one of embodiments 1 to 15, wherein restarting the monitoring application further comprises: initiating a service request from the patient account to a remote computing system of a health monitoring service as part of the function call.

[0158] Embodiment 20. A method according to any one of embodiments 1 to 15, wherein restarting the monitoring application further comprises: in response to determining that the current patient location corresponds to the authenticated area, generating a new network connection with the health monitoring service as part of the function call, or restoring a previous network connection with the health monitoring service as part of the function call.

[0159] Embodiment 21. A method according to any one of embodiments 1 to 20, wherein restarting the monitoring application further comprises: in response to the input data, enabling a wake-up function to execute the monitoring application via the processing circuit, wherein the monitoring application operates to detect health events based on patient data.

[0160] Embodiment 22. The method of any one of embodiments 1 to 21, wherein restarting the monitoring application further comprises: storing data generated by the monitoring application and currently stored in the volatile memory in the non-volatile memory.

[0161] Embodiment 23. A computing device, comprising: an input device; a memory; and a processing circuit, the processing circuit being configured to execute logic for a monitoring application stored in the memory, the processing circuit being further configured to: determine that a monitoring application previously executed by the processing circuit is not working; receive input data indicating a current location of a patient from the input device of the computing device; determine whether the current location of the patient corresponds to an authenticated area of ​​the patient; and in response to determining that the current location corresponds to the authenticated area and in response to determining that the monitoring application is not working, restart the monitoring application.

[0162] Embodiment 24. A computing device according to embodiment 23, wherein the input device further comprises a communication circuit, the communication circuit comprising a Bluetooth module, the Bluetooth module being communicatively coupled to a device of the health monitoring service for receiving data indicating a current patient location.

[0163] Embodiment 25. A computing device according to any one of embodiments 23 to 24, wherein the input data is directed to a second application different from the monitoring application, wherein the second application is configured to enable a function call that causes the monitoring application to restart.

[0164] Embodiment 26. The computing device of any one of Embodiments 23 to 25, communicatively coupled to the device of the health monitoring service.

[0165] Embodiment 27. The computing device of any one of Embodiments 23 to 26, wherein the computing device operates as an intermediary between a medical device and a health monitoring service for health event detection within a certified region.

[0166] Embodiment 28. A medical system, comprising: a processing circuit, the processing circuit executing logic stored in a memory, the processing circuit being configured to: determine that a monitoring application previously executed by the processing circuit is not working; receive input data indicating a current location of a patient from an input device of the computing device; determine whether the current location of the patient corresponds to a certified area of ​​the patient; and in response to determining that the current location corresponds to the certified area and in response to determining that the monitoring application is not working, restart the monitoring application.

[0167] Embodiment 29. A medical system according to Embodiment 28, wherein the patient device is configured to operate as an intermediary between a medical device for monitoring a patient and a health monitoring service within a certified area, and the patient device includes the input device, the output device, and the processing circuit.

[0168] Embodiment 30. A medical system according to any one of Embodiments 28 to 29, wherein the input data is directed to a second application different from the monitoring application, wherein the second application is configured to enable a function call that causes the monitoring application to restart.

[0169] Embodiment 31. A medical system according to any one of Embodiments 28 to 30, wherein the medical device is communicatively coupled to the patient device, wherein the medical device comprises at least one of: an implantable device, a wearable device, a pacemaker, a defibrillator, or a ventricular assist device (VAD) comprising one or more sensors and sensing circuits.

[0170] Embodiment 32. A non-transitory computer-readable storage medium, comprising program instructions which, when executed by a processing circuit of a medical device, cause the processing circuit to: determine that a monitoring application previously executed by the processing circuit is not working; receive input data indicating a current location of a patient from an input device of the computing device; determine whether the current location of the patient corresponds to a certified area of ​​the patient; and in response to determining that the current location corresponds to the certified area and in response to determining that the monitoring application is not working, restart the monitoring application.

[0171] Embodiment 33. A method comprising any combination of the methods described herein.

[0172] Embodiment 34. A system comprising a processing circuit configured to perform the method according to any one or more of embodiments 1 to 17.

[0173] Embodiment 35. A non-transitory computer-readable storage medium comprising program instructions configured to cause a processing circuit to perform a method according to any one or more of Embodiments 1 to 17.

Claims

1. A computing device, comprising: Input device; Memory; and a processing circuit configured to execute logic for a monitoring application stored in the memory, the processing circuit being further configured to: determining that a monitoring application previously executed by the processing circuit is not operational; receiving input data indicative of a current position of a patient from an input device of the computing device; determining whether the current location of the patient corresponds to a certified zone for the patient; as well as In response to determining that the current location corresponds to the authenticated area and in response to determining that the monitoring application is not functioning, restarting the monitoring application.

2. The computing device of claim 1 , wherein the input device further comprises a communication circuit communicatively coupled to a device for receiving data indicative of a current patient location from a computing service, such as a health monitoring service or a location service.

3. The computing device of any one of claims 1 to 2, wherein the input data is directed to a second application different from the monitoring application, wherein the second application is configured to enable a function call that causes the monitoring application to restart.

4. The computing device according to any one of claims 1 to 3, wherein the computing device operates as an intermediary between a medical device for health event detection and a health monitoring service or a location service within a certified area.

5. The computing device of any one of claims 1 to 4, wherein determining that the current location corresponds to the authenticated area further comprises determining that the current location corresponds to a residence or home of the patient.

6. The computing device of any one of claims 1 to 5, wherein receiving the input data comprises: The input data is received in a message transmitted by a device of a computing service.

7. The computing device of any one of claims 1 to 6, wherein restarting the monitoring application further comprises one or more of the following: responsive to determining that the current patient location corresponds to the authenticated zone, automatically completing an authentication sequence with a health monitoring service to access a patient account; In response to determining that the current patient position corresponds to the authenticated region, initiating a function call to trigger execution of the monitoring application; As part of the function call, initiating an active operating mode of the monitoring application, wherein the monitoring application will run in the foreground of the computing device; As part of the function call, submitting credentials for an authentication sequence for a patient account; As part of the function call, overriding a requirement for credentials for an authentication sequence for a patient account; As part of the function call, initiating a service request from the patient account to a remote computing system of a health monitoring service; In response to determining that the current patient location corresponds to the authenticated region, generating a new network connection with a health monitoring service as part of the function call or restoring a previous network connection with the health monitoring service as part of the function call; In response to the input data, enabling a wake-up function to execute the monitoring application via the processing circuit, wherein the monitoring application operates to detect a health event based on the patient data; Data generated by the monitoring application and currently stored in the volatile memory is stored in the non-volatile memory.

8. A method performed by a processing circuit of a computing device, comprising: determining that a monitoring application previously executed by the processing circuit is not operational; receiving input data indicative of a current position of a patient from an input device of the computing device; determining whether the current location of the patient corresponds to a certified zone for the patient; as well as In response to determining that the current location corresponds to the authenticated area and in response to determining that the monitoring application is not functioning, restarting the monitoring application.

9. The method of claim 8, wherein receiving the input data comprises one or more of: Capture signal data via wireless connection to a Global Positioning Service (GPS) receiver; Capturing signal data via a network connection to a computing service; Capturing signal data via a wireless connection to a beacon device; or Signal data is captured via a local connection to the medical device.

10. The method of any one of claims 8 to 9, wherein determining that the current location corresponds to the authenticated area further comprises determining that the current location corresponds to a residence or home of the patient.

11. The method according to any one of claims 8 to 10, wherein receiving the input data comprises receiving the input data in a message transmitted by a device of a computing service, for example, the computing service is one of a health monitoring service or a location service.

12. The method of claim 11, wherein receiving the input data further comprises receiving, by the input device, the connection request to the device in response to a connection request from the device of the computing service, the method further comprising: An acknowledgement is transmitted by an output device of the computing service to the device in response to the connection request from the device of the computing service.

13. The method according to any one of claims 8 to 12, wherein restarting the monitoring application further comprises one or more of the following: responsive to determining that the current patient location corresponds to the authenticated zone, automatically completing an authentication sequence with a health monitoring service to access a patient account; In response to determining that the current patient position corresponds to the authenticated region, initiating a function call to trigger execution of the monitoring application; As part of the function call, initiating an active operating mode of the monitoring application, wherein the monitoring application will run in the foreground of the computing device; As part of the function call, submitting credentials for an authentication sequence for a patient account; As part of the function call, overriding a requirement for credentials for an authentication sequence for a patient account; As part of the function call, initiating a service request from the patient account to a remote computing system of a health monitoring service; In response to determining that the current patient location corresponds to the authenticated region, generating a new network connection with a health monitoring service as part of the function call or restoring a previous network connection with the health monitoring service as part of the function call; In response to the input data, enabling a wake-up function to execute the monitoring application via the processing circuit, wherein the monitoring application operates to detect a health event based on the patient data; Data generated by the monitoring application and currently stored in the volatile memory is stored in the non-volatile memory.

14. A non-transitory computer-readable storage medium comprising program instructions that, when executed by a processing circuit of a medical device, cause the processing circuit to: determining that a monitoring application previously executed by the processing circuit is not operational; receiving input data indicative of a current position of a patient from an input device of the computing device; determining whether the current location of the patient corresponds to a certified zone for the patient; as well as In response to determining that the current location corresponds to the authenticated area and in response to determining that the monitoring application is not functioning, restarting the monitoring application.