Local communication of emergency alerts

Abstract

An example system includes an implantable medical device (IMD) configured to: sense physiological data; detect an acute health event based on the physiological data; and, in response to the acute health event, transmit a Universally Unique Identifier (UUID) notification according to a short-range wireless protocol; and a computing device configured to:, in response to receiving the UUID notification, send a protocol message to a central controller; and receive from the central controller a request to generate a communication path between the central controller and the IMD via the computing device. The computing device is configured to connect to the central controller via a network connection and is configured to connect to the IMD via the short-range wireless protocol. In response to the generation of the communication path, the IMD is configured to transmit an indication of the acute health event or the physiological data to the central controller via the communication path.

Description

[0001] This application claims the benefit of U.S. Provisional Patent Application Serial No. 63 / 610,270, filed December 14, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates in general to systems including medical devices, and more specifically to the use of such systems to monitor patient health. Background Technology

[0003] Various devices are configured to monitor a patient's physiological signals. These devices include implantable medical devices (IMDs). Physiological signals sensed by such devices include, for example, electrocardiogram (ECG) signals, respiratory signals, perfusion signals, activity and / or posture signals, pressure signals, blood oxygen saturation signals, body composition, and blood glucose or other blood component signals. Generally, using these signals, such devices facilitate the monitoring and assessment of a patient's health over months or years outside of a clinic setting.

[0004] In some cases, such devices are configured to detect acute health events, such as arrhythmias, myocardial infarction, stroke, or epileptic seizures, based on physiological signals. Example types of arrhythmias include cardiac arrest (e.g., cardiac arrest), ventricular tachycardia (VT), and ventricular fibrillation (VF). These devices can store ECG and other physiological signal data collected during the period including the seizure as seizure data. Such acute health events are associated with significant mortality, especially if not treated rapidly.

[0005] For example, VF and other malignant tachyarrhythmias are the most frequently identified arrhythmias in patients with sudden cardiac arrest (SCA). If such arrhythmias last for more than a few seconds, they can lead to cardiogenic shock and cessation of effective blood circulation. For every minute a patient waits for defibrillation, the survival rate from SCA decreases by 7% to 10%. Therefore, sudden cardiac death (SCD) can occur within minutes. Summary of the Invention

[0006] Generally, this disclosure describes techniques for establishing a communication path between the IMD and a central controller via a computing device when the IMD detects an acute health event. For example, a patient computing device intended to communicate with the IMD may be unable to receive communications from the IMD and / or transmit communications to the central controller, thus preventing the IMD from communicating with the central controller. Generating a communication path between the IMD and the central controller via another computing device (in addition to the intended patient computing device) can provide necessary communication between the IMD and the central controller during rest periods, such as when a patient has an acute health event and when the patient computing device is unable to receive communications from the IMD and / or transmit communications to the central controller. Generating a communication path according to the techniques described herein can facilitate communication between the IMD and the central controller to deliver outputs for emergency services and / or emergency treatment of patients suffering from acute health events when the intended patient computing device is unable to receive communications from the IMD and / or transmit communications to the central controller. Furthermore, the computing device may be able to generate a communication path as described herein in response to receiving notification signals and requests from the central controller, thereby providing effective emergency communication between the IMD and the central controller via the computing device without requiring significant dedicated configuration of the computing device or the use of dedicated messaging between the IMD and the computing device.

[0007] In one example, this disclosure describes a system comprising: an implantable medical device (IMD) configured to: sense physiological data of a patient; detect an acute health event of the patient based on the sensed physiological data; and, in response to detecting an acute health event, transmit a Universal Unique Identifier (UUID) notification according to a short-range wireless protocol; and a computing device configured to: receive the UUID notification;, in response to receiving the UUID notification, transmit a protocol message to a central controller, the protocol message including an indication that the computing device has received the UUID notification; and receive from the central controller a request to generate a communication path between the central controller and the IMD via the computing device, wherein the computing device is configured to be connected to the central controller via a network connection and is configured to be connected to the IMD via a short-range wireless protocol, the request being transmitted by the central controller in response to receiving the protocol message from the computing device; wherein, in response to the generation of the communication path, the IMD is configured to transmit to the central controller one or more of the indication of the detected acute health event or the sensed physiological data via the communication path.

[0008] In another example, this disclosure describes a method for operating a system including an implantable medical device (IMD) in response to an acute health event, the method comprising: sensing physiological data of a patient by the IMD; detecting an acute health event of the patient by the IMD based on the sensed physiological data; transmitting a Universally Unique Identifier (UUID) announcement by the IMD according to a short-range wireless protocol in response to the detection of the acute health event; receiving the UUID announcement by a computing device; sending a protocol message to a central controller in response to receiving the UUID announcement, the protocol message including an indication that the computing device has received the UUID announcement; receiving from the central controller a request to generate a communication path between the central controller and the IMD via the computing device, wherein the computing device is configured to be connected to the central controller via a network connection and is configured to be connected to the IMD via a short-range wireless protocol, the request being transmitted by the central controller in response to receiving the protocol message from the computing device; and in response to the generation of the communication path, sending to the central controller via the communication path one or more of the indication of the detected acute health event or the sensed physiological data.

[0009] In another example, this disclosure describes a computing device including: a communication circuit; and a processing circuit configured to: receive via the communication circuit a UUID notification transmitted by an implantable medical device (IMD) according to a short-range wireless protocol, the UUID notification being transmitted by the IMD in response to detecting an acute health event in a patient based on physiological data sensed by the IMD; and, in response to receiving the UUID notification, control the communication circuit to send a protocol message to a central controller, the protocol message including an indication that the computing device has received the UUID notification; and receive via the communication circuit from the central controller... The computing device requests the generation of a communication path between the central controller and the IMD, wherein the processing circuitry is configured to control the communication circuitry to connect to the central controller via a network connection and to the IMD via a short-range wireless protocol, the request being transmitted by the central controller in response to receiving a protocol message from the computing device; and in response to receiving the request, the computing device generates a communication path between the central controller and the IMD, wherein, in response to the generation of the communication path, the IMD is configured to send one or more of an indication of a detected acute health event or sensed physiological data to the central controller via the communication path.

[0010] This disclosure is intended to provide an overview of the subject matter described herein. The present invention is not intended to provide an exclusive or exhaustive explanation of the systems, apparatus, and methods described in detail in the following drawings and specification. Further details of one or more examples of the present disclosure are set forth in the following drawings and specification. Other features, objectives, and advantages will be apparent from the specification, drawings, and claims. Attached Figure Description

[0011] Figures 1A to 1B This is a block diagram illustrating an exemplary system configured to detect acute health events in a patient and respond to such detections according to one or more technologies of this disclosure.

[0012] Figure 2 This is a block diagram illustrating an exemplary configuration of an implantable medical device operating according to one or more technologies of this disclosure.

[0013] Figure 3 This is a block diagram illustrating an exemplary configuration of a computing device operating according to one or more technologies disclosed herein.

[0014] Figure 4 This is a block diagram illustrating an exemplary configuration of a health monitoring system operating according to one or more technologies disclosed herein.

[0015] Figure 5 This is a flowchart illustrating an example of the technology disclosed herein.

[0016] Throughout the accompanying drawings and description, similar reference numerals refer to similar elements. Detailed Implementation

[0017] Patients with an IMD may experience acute health events such as cardiac arrest, stroke, acute myocardial infarction, or anaphylactic shock, resulting in incapacitation. In some systems, the IMD can detect acute health events in patients and send notifications to the patient's computing device (such as a phone or smartwatch) configured with, for example, software applications to communicate with the IMD. The patient's computing device can then contact a first responder via a network connection over Wi-Fi or a cellular network.

[0018] However, acute health events may occur when the patient's computing device lacks network access, such as when the power is off, the patient's computing device is outside the range of the IMD, network access is disabled, or the patient's computing device is in a structure and / or location where network access is unavailable. Without the ability to communicate with the IMD or access the network, the patient's computing device may be unable to communicate the occurrence of an acute health event, such as contacting emergency services (e.g., 911) for medical assistance.

[0019] This disclosure describes techniques for configuring a patient's IMD to send a Universally Unique Identifier (UUID) notification in response to the detection of an acute health event, ultimately generating an authenticated communication path between the central controller and the IMD via a nearby computing device, which may differ from the patient's computing device typically used to communicate with the IMD. In some examples, the UUID notification may be received by one or more nearby computing devices. The UUID notification may include, for example, an indication that the IMD has detected an acute health event. In some examples, the UUID notification may be defined using a specific communication protocol, such that any device compatible with that specific communication protocol can understand the UUID notification. The computing device is configured to send a protocol message to the central controller in response to receiving the UUID notification. The protocol message includes an indication that the computing device has received the UUID notification. In some examples, the protocol message may be defined using a specific communication protocol, such that any device compatible with that specific communication protocol can understand the protocol message. In response to receiving a protocol message, the central controller is configured to send a request to the computing device to establish a communication path between the central controller and the IMD, such as a bidirectional communication path between the IMD and the central controller via the computing device. In response to the establishment of this communication path, the IMD is configured to send one or more of an indication of a detected acute health event or sensed physiological data to the central controller via the communication path.

[0020] When a patient computing device fails to communicate as expected in response to an acute event detection, such as when the patient computing device cannot communicate with one or more of the IMD or the central controller, a communication path generated by the computing device between the central controller and the IMD provides an improved, certified communication path between the IMD and the central controller. This is for example, when the patient computing device loses power, is out of range of the IMD, or has no network access to communicate with the central controller. When the IMD may be unable to communicate securely with the central controller due to the patient computing device's inability to communicate via the network, the generated communication path provides necessary secure communication between the IMD and the central controller in emergency situations. Generating a communication path between the central controller and the IMD via the computing device enables the IMD to communicate rapidly with the central controller, allowing for the prompt provision of emergency assistance to patients experiencing acute health events. Emergency assistance may include treatment of the acute health event. Prompt treatment of acute health events can improve treatment outcomes and potentially reduce significant consequences for patients, such as, but not limited to, death.

[0021] Various types of implantable medical device (IMD) or wearable devices can be configured to detect arrhythmia episodes and other acute health events based on sensed ECGs and (in some cases) other physiological signals. Such IMDs facilitate relatively long-term monitoring of a patient's health during normal daily activities. IMDs also sense and monitor ECGs and other physiological signals and detect acute health events such as arrhythmias, cardiac arrest, myocardial infarction, stroke, and seizures. Example IMDs include pacemakers and implantable cardioverter defibrillators (ICDs) that can be coupled to intravascular or extravascular leads; and pacemakers with a shell configured for implantation in the heart, which may be leadless. Some IMDs do not provide therapy, such as implantable patient monitors. An example of such an IMD is the Reveal LINQ, commercially available from Medtronic, Inc. ™ Insertable cardiac monitor (ICM) or LINQ II ™ ICMs, which can be inserted subcutaneously, facilitate relatively long-term monitoring of patients during normal daily activities. Collected data, such as data on detected arrhythmia episodes, can be periodically transmitted to remote patient monitoring systems, such as Medtronic Carelink. ™ Network. In some examples, the system may include multiple IMDs, wherein a first IMD of the multiple IMDs is configured to sense physiological data and / or detect acute health events based on the sensed physiological data. In some examples, in response to the detection of an acute health event, the first IMD of the multiple IMDs may transmit an alarm to a second IMD of the multiple IMDs, such as via, but not limited to, in vivo communications and / or tissue conduction communications, to cause the second IMD to send a UUID notification, as described in the examples below. The second IMD may be different from the first IMD.

[0022] Figures 1A to 1B This is a block diagram illustrating an exemplary system 2 configured to detect and respond to an acute health event of patient 4 according to one or more techniques of this disclosure. As used herein, the term "detection," etc., can refer to the detection of an acute health event that patient 4 is currently experiencing (at the time of data collection), and the detection of data based on patient 4's condition that makes them have an over-threshold probability of experiencing an event within a specific time frame, such as the prediction of an acute health event. In some examples, an acute health event can refer to an emergency health event. In some examples, the IMD 10 can wirelessly communicate with the patient computing device 12 when the patient computing device 12 is powered on and has network access. Although in Figures 1A to 1B Not illustrated, but 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 seizures based on that data.

[0023] IMD 10 can be configured to send a UUID notification 11 according to a short-range wireless protocol in response to the detection of an acute health event. In some examples, the short-range wireless protocol may include low-power (BLE) or other wireless communication protocols. In some examples, the UUID notification 11 may not be a proprietary, patient-specific message, but rather a signal that another intelligent computing device not directly associated with IMD 10 may be able to interpret as an emergency. In some examples, the UUID notification 11 may include one or more of the following: an indication that an acute health event has occurred, an indication of the time of the event, and / or that IMD 10 is to be transmitted by a remote patient monitoring system (such as Medtronic Carelink). ™ The UUID notification 11 is an indication or identifier of a device monitored by the network. In some examples, the UUID notification 11 includes an emergency identifier indicating that the IMD 10 has sensed an acute health event requiring an emergency response. In some examples, the UUID notification 11 may not include information about the detected acute health event. In some examples, the UUID notification 11 includes identification information of the central controller 20 to instruct the computing device 14 to send protocol messages 15 to the central controller 20, such as the identifier and / or address of the central controller 20.

[0024] In various specific implementations of the technology described herein, IMD 10 may be configured to broadcast UUID announcement 11 at least within a variety of different ranges, such as at least 150 meters, at least 40 meters, at least 275 meters, at least 125 meters, at least 15 meters, or at least 1 meter to 100 meters of IMD 10. In some examples, IMD 10 may be configured to broadcast UUID announcement 11 up to a range limited by a specific wireless communication protocol used for broadcasting UUID announcement 11.

[0025] In some examples, IMD 10 can be implanted outside the pleural cavity of patient 4 (e.g., subcutaneously). Figure 1A middle Figure 1B (In the illustrated pectoral muscle location). IMD 10 can be positioned near the sternum at or just below the patient's heart level, for example, at least partially within the heart contour. In some examples, IMD 10 uses LINQ. ™In the form of an ICM. Although described primarily in the context of examples employing the ICM form in IMD 10, the techniques disclosed herein can be implemented in systems including any one or more implantable or external medical devices, including monitors, pacemakers, defibrillators, wearable external defibrillators, neurostimulators, drug pumps, wearable devices, or other such devices. Furthermore, although described primarily in the context of examples including a single implanted patient sensing device, in some examples, the system includes one or more patient sensing devices that can be implanted within or outside the patient (e.g., worn by the patient).

[0026] The patient computing device 12 can be configured to wirelessly communicate with the IMD 10. The patient computing device 12 retrieves or receives event data and other sensed physiological data collected and stored by the IMD 10. In some examples, the computing device 12 may take the form of a personal computing device of the patient 4. For example, the patient computing device 12 may take the form of a smartphone of the patient 4. In some examples, the patient computing device 12 may be any computing device configured to wirelessly communicate with the IMD 10, such as a desktop computer, laptop computer, smartwatch, or tablet computer. For example, the patient computing device 12 may be based on Bluetooth. ® ,Bluetooth ® Low-power (BLE) or other wireless communication protocols communicate with IMD 10. In some examples, patient computing device 12 may be configured to receive indications of acute health events of patient 4 from IMD 10.

[0027] One or more computing devices (such as 14A, 14B, 14C, 14D, 14E, 14F (collectively referred to as computing device 14)) are in the form of a personal computing device belonging to a bystander other than patient 4. For example, each computing device in computing device 14 may take the form of a smartphone belonging to the respective bystander. In some examples, computing device 14 may be any computing device configured for wireless communication, such as a desktop computer, laptop computer, tablet computer, smartwatch, smart home device, other smart device, or Internet of Things. As an example, IMD 10 may be configured to operate according to a short-range wireless protocol such as Bluetooth. ® ,Bluetooth ® The central controller 20 communicates with the computing device 14 via a low-power (BLE) or other short-range wireless communication protocol. The central controller 20 can be configured to communicate with the computing device 14 via a network 16.

[0028] In some examples, such as Figure 1AAs shown, computing device 14 can be configured to receive UUID announcement 11 and send protocol message 15 to central controller 20 via network 16. In some examples, protocol message 15 may include an indication that the corresponding computing device 14 has received UUID announcement 11. In some examples, protocol message 15 does not include UUID announcement 11 and / or does not include any information in UUID announcement 11. In some examples, protocol message 15 may include an identifier of the corresponding computing device 14 having information about the type of service (such as a genetic service identifier). In some examples, protocol message 15 may include registration information of the corresponding computing device 14 with central controller 20, such as credentials or tokens, to establish a trust relationship between central controller 20 and the corresponding computing device 14, thereby enabling a communication path to be established between IMD 10 and central controller 20 via the corresponding computing device 14. In some examples, protocol message 15 may include an indication of geographic location. For example, the indication of geographic location may include one or more of the geographic location of the corresponding computing device 14 transmitting protocol message 15, the geographic location of IMD 10, and / or the geographic location of computing device 14 at the time it receives UUID notification 11. In some examples, protocol message 15 may not include the content of UUID notification 11. In some examples, computing device 14 may have prior knowledge that UUID notification 11 is intended for use in emergency communication sessions for the purpose of generating communication between IMD and central controller to relay medical information. In some examples, UUID notification 11 may be a generic standard message, allowing any intelligent device such as computing device 14 to be configured to assist in acute health events as a transmitter and / or receiver of information related to acute health events.

[0029] One or more computing devices in computing device 14 may be configured to communicate with various other devices or systems via network 16. For example, one or more computing devices in computing device 14 may be configured to communicate with central controller 20 via network 16. Central controller 20 may be managed accordingly by the manufacturer of IMD 10 to provide, for example, cloud storage and analysis, maintenance and software services of collected data for their respective devices and users, or other networking functionality. In some examples, central controller 20 may include Medtronic Carelink. ™ Online, or via Medtronic Carelink ™ Implemented via the network. Figures 1A to 1B In the illustrated example, the central controller 20 can implement a health monitoring system (HMS) 22.

[0030] Central controller 20 may be configured to receive protocol message 15 from computing device 14 via network 16. In response to receiving protocol message 15, central controller 20 may be configured to send a request 17 to computing device 14 (such as, but not limited to, the computing device 14 transmitting protocol message 15) to generate a communication path between central controller 20 and IMD 10 via computing device 14. In some examples, the generated communication path is a bidirectional communication path between IMD 10 and central controller 20 via computing device 14. In some examples, central controller 20 may determine which computing device(s) 14 transmits the request to generate a communication path with IMD 10 based on a specific distance of the computing device(s) transmitting the protocol message from other computing devices(s). For example, other computing devices such as those within 150 meters of the computing device(s) transmitting the protocol message. Figure 1A As shown, computing devices 14B and 14C each receive a UUID announcement 11 from IMD 10, and each of computing devices 14B and 14C transmits a protocol message 15 to the central controller 20 via network 16. Figure 1B As shown, the central controller 20 transmits request 17 to computing devices 14B and 14C that transmit protocol message 15 via network 16, and also determines to transmit requests to computing devices 14A, 14E, and 14F based on computing device 14A being within a distance threshold X1 of computing device 14B and computing devices 14E and 14F being within a distance threshold X2 of computing device 14C. In some examples, the distance threshold can be as high as 100 meters. In some examples, the distance threshold can be as high as 150 meters. In some examples, the distance threshold can be as high as 200 meters. In some examples, request 17 may not be transmitted to computing devices 14 that are not within the distance threshold of computing devices 14 that transmit protocol message 15. In some examples, the central controller 20 may include hardware components, such as servers and / or hardware components of computing devices 14 embodied in one or more physical devices.

[0031] In response to the generation of a communication path between the central controller 20 and the IMD 10 via the computing device 14, the IMD 10 can be configured to send one or more of the indication of a detected acute health event and / or sensed physiological data to the central controller 20 via the computing device 14 through the generated communication path between the central controller 20 and the IMD 10. When the patient computing device 12 is unable to access the network 16 in an emergency, the communication path generated between the central controller 20 and the IMD 10 via the computing device 14 provides an improved certified communication path between the IMD 10 and the central controller 20. The technique of providing an improved certified communication path provides improved security for sensitive data (such as patient 4 medical data and / or patient 4 personal data) transmitted between the IMD 10 and the central controller 20 via the computing device 14, while also generating a certified communication path quickly enough to enable emergency assistance to be provided to patient 4 to help treat the acute health event as quickly as possible, which can improve treatment outcomes and potentially reduce the significant consequences of the acute health event, such as death. The generation of an authenticated communication path enables sensitive patient data to be transmitted from IMD 10 to central controller 20 via computing device 14, while maintaining patient data security for users of computing device 14.

[0032] In response to the establishment of a communication path between the central controller 20 and the IMD 10 via the computing device 14, the IMD 10 may transmit data to the central controller 20. This data may include: sensed data, such as values ​​of physiological parameters measured by the IMD 10 and, in some cases, previously sensed by the patient computing device 12; data regarding arrhythmia episodes or other acute health events detected by the IMD 10; and other physiological signals or data recorded by the IMD 10. The HMS 22 may also retrieve data about the patient 4 via a network from one or more electronic health records (EHRs) 24 sources. The EHRs 24 may include data regarding the patient's (including the patient 4's) historical (e.g., baseline) physiological parameter values, previous health events and treatments, disease status, comorbidities, demographics, height, weight, and body mass index (BMI). The HMS 22 may use data from the EHRs 24 to configure algorithms implemented by the IMD 10 to detect acute health events in the patient 4.

[0033] 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 thus may form part of a large-scale public network infrastructure (e.g., the Internet). Network 16 can provide access to computing devices and systems (such as...) Figures 1A to 1B The computing devices and systems illustrated herein 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 the communication framework, which allows Figures 1A to 1B The computing devices and systems illustrated communicate with each other, but for security purposes, some data streams are isolated from devices outside the private network. In some examples, Figures 1A to 1B The communication between the computing device and the system illustrated in the figure is encrypted.

[0034] As will be described herein, IMD 10 can be configured to detect an acute health event in patient 4 based on data sensed by IMD 10 and, in some cases, on other data (such as data sensed by patient computing device 12) and data from EHR 24. In response to detecting an acute health event, IMD 10 may attempt to wirelessly send an indication of the acute health event, such as a message, to patient computing device 12. This message may indicate that IMD 10 has detected an acute health event in patient 4 and may include a request for an indication from patient computing device 12 that a message indicating an acute health event has been received and that patient computing device 12 has network 16 access. In some examples, if IMD 10 does not receive an indication from computing device 12 within a certain time period (e.g., examples of a time period are up to 5 seconds, up to 10 seconds, up to 15 seconds, up to 30 seconds, or up to 1 minute) that an indication has been received indicating an acute health event and that patient computing device 12 has network 16 access, then IMD 10 may send a UUID announcement 11. In some examples, IMD 10 may send a UUID notification 11 in response to IMD 10 detecting an acute health event.

[0035] In response to the generation of a communication path between the central controller 20 and the IMD 10 via the computing device 14, the IMD 10 may transmit, via the generated communication path, one or more of an indication of a detected acute health event and / or sensed physiological data of the patient 4 to the central controller 20. The sensed physiological data may include physiological data collected by the IMD 10, such as data that caused the detection of the acute health event, data prior to the detection of the acute health event, and / or real-time or more recent data collected after the detection of the acute health event. The sensed physiological data may include values ​​of one or more physiological parameters and / or digitized physiological signals. Some examples of acute health events are cardiac arrest, ventricular fibrillation, ventricular tachycardia, myocardial infarction, thermal rhythm arrest (cardiac arrest), pulseless electrical activity (PEA), acute respiratory distress syndrome (ARDS), stroke, seizure, fall, anaphylactic shock, or respiratory failure.

[0036] In some examples, in response to receiving a UUID notification 11 from IMD 10, computing device 14 may output an alarm, which may be visual and / or auditory, and is configured to immediately attract the attention of patient 4 or anyone near patient 4 within environment 28. In some examples, after a communication path is established between central controller 20 and IMD 10 via computing device 14 and IMD 10 transmits one or more of an indication of a detected acute health event and / or sensed physiological data of patient 4 to central controller 20 via the established communication path, computing device 14 may receive a trigger signal from central controller 20 to output an alarm, which may be visual and / or auditory and is configured to immediately attract the attention of patient 4 or anyone near patient 4.

[0037] Environment 28 includes computing facilities (e.g., local network 32) through which IMD 10, patient computing device 12, computing device 14, and / or other devices within environment 28 can communicate via network 16, for example, with central controller 20, HMS 22, or other devices on local network 32. Environment 28 may be configured with wireless technologies such as 802.11 wireless network, 802.15 ZigBee network, ultra-wideband protocol, near-field communication, etc. Environment 28 may include one or more wireless access points, such as wireless access points 34A and 34B (collectively, “Wireless Access Point 34”), to support wireless communication throughout environment 28. Additionally or alternatively, for example when the local network is unavailable, computing device 14 within environment 28 may be configured to communicate with network 16 via cellular base station 36 and cellular network, for example, with central controller 20 and / or HMS 22.

[0038] In some examples, in response to identifying and / or confirming an acute health event in patient 4, the central controller 20 may send an alarm to a care provider, emergency medical technician, or other designated person in or near environment 28. For example, the alarm may be a communication with an emergency medical technician, or a local community alarm system with automated external defibrillator (AED) service, with a care provider, etc. In some examples, the alarm includes data collected from IMD 10, enabling medical personnel to prepare for rapid action upon arrival at environment 28. In some examples, the alarm includes at least one of telephone calls, SMS service messages, emails, internet messages, security system alarms, social media alarms, audible alarms, or visual alarms. In some examples, the central controller 20 may transmit alarms or warnings to every person and device around environment 28.

[0039] For example, the central controller 20 may be configured to send alert messages via network 16 to one or more computing devices 38 associated with one or more care providers 40. Care providers may include emergency medical systems (EMS) and hospitals, and may include specific departments within hospitals, such as emergency departments, catheterization laboratories, or stroke response departments. Computing devices 38 may include smartphones, desktop computers, laptop computers, or tablet computers, or workstations associated with such systems or entities, or employees of such systems or entities. Alert messages may include any data collected by the IMD 10, including sensed physiological parameters, the time of the acute health event, the location of patient 4, and results analyzed by the IMD 10 and / or HMS 22. Information transmitted from the HMS 22 to care providers 40 can improve the timeliness and effectiveness of care providers 40's treatment of patient 4's acute health event. In some examples, as an alternative or supplement to HMS 22 providing alert messages to one or more computing devices 38 associated with EMS care provider 40, central controller 20 may be configured to automatically contact EMS in response to receiving detected acute health events and / or sensed physiological data from IMD 10 via a communication path, such as automatically dialing 911 (e.g., using a telephone system in the United States or North America to contact the 911 call center). Such operation may be cancelled by a bystander's computing device 14.

[0040] Similarly, the central controller 20 can be configured to transmit alarm messages to the bystander's computing device 14, which can improve the timeliness and effectiveness of the bystander's treatment of the patient 4's acute health event. In some examples, the central controller 20 can determine that the bystander's computing device 14 is close to the patient 4 based, for example, the location of the patient 4 received from the IMD 10 or from the computing device 14 transmitting protocol messages, and the location of the computing device 14 reported to the central controller 20 by, for example, an application implemented on the computing device 14. In some examples, the central controller 20 can send alarm messages to any computing device 14 within an alarm area determined based on the patient 4's location, for example, by sending alarm messages to all computing devices communicating with the base station 36.

[0041] In some examples, alert messages to bystanders can be configured to assist laypeople in treating a patient. For example, an alert message to a bystander may include the location of patient 4 (and in some cases a description), the general nature of the acute health event, instructions for providing care to patient 4 (such as instructions to provide cardiopulmonary resuscitation (CPR), the location of nearby medical equipment for treating patient 4 (such as an automated external defibrillator (AED) or life vest), and instructions for using the equipment.

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

[0043] Processing circuitry 50 may include fixed-function circuitry and / or programmable processing circuitry. Processing circuitry 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 equivalent discrete or analog logic circuitry. In some examples, processing circuitry 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 circuitry. The functions attributed herein to processing circuitry 50 may be embodied in software, firmware, hardware, or any combination thereof. In some examples, memory 53 includes computer-readable instructions that, when executed by processing circuitry 50, cause IMD 10 and processing circuitry 50 to perform the various functions attributed herein to IMD 10 and processing circuitry 50. The memory 53 may include any volatile, non-volatile, magnetic, optical, or electrical medium, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), electrically erasable programmable ROM (EEPROM), flash memory, or any other digital medium.

[0044] Sensing circuit 54 can monitor signals from electrode 56 to, for example, monitor the electrical activity of the patient 4's heart and generate ECG data for the patient 4. In some examples, processing circuit 50 can identify features of the sensed ECG, such as heart rate, heart rate variability, intrabeat interval, and / or ECG morphological features, to detect arrhythmia episodes in the patient 4. Processing circuit 50 can store the digitized ECG and the features of the ECG used to detect arrhythmia episodes in memory 52 as episode data of the detected arrhythmia episode.

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

[0046] In some examples, IMD 10 includes sensing circuitry 58, such as one or more accelerometers, microphones, optical sensors, temperature sensors, and / or pressure sensors. In some examples, sensing circuitry 54 may include one or more filters and amplifiers for filtering and amplifying signals received from one or more of the electrodes 56 and / or sensors 58. In some examples, sensing circuitry 54 and / or processing circuitry 50 may include rectifiers, filters and / or amplifiers, sensing amplifiers, comparators, and / or analog-to-digital converters. Processing circuitry 50 may determine physiological data (e.g., values ​​of physiological parameters of patient 4) based on signals from sensors 58, which may be stored in memory 52.

[0047] Memory 52 may store an application 70 executable by processing circuitry 50 and data 80. Application 70 may include an acute health event monitoring application 72. Processing circuitry 50 may execute event monitoring application 72 to detect acute health events in patient 4 based on a combination of one or more types of physiological data described herein, which may be stored as sensed data 82. In some examples, sensed data 82 may additionally include data sensed by other devices (e.g., patient computing device 12) and received via communication circuitry 60. Event monitoring application 72 may be configured with a rule engine 74. Rule engine 74 may apply rules 84 to sensed data 82. Rules 84 may include one or more models, algorithms, decision trees, and / or thresholds. In some cases, rules 84 may be developed based on machine learning.

[0048] For example, the event monitoring application 72 can be based on ECG and / or indicate patient 4 ( Figures 1A to 1B The event monitoring application 72 can detect cardiac arrest, ventricular fibrillation, ventricular tachycardia, cardiac arrest, pulseless electrical activity (PEA), or myocardial infarction by detecting the electrical or mechanical activity of the heart, or other physiological data. In some examples, the event monitoring application 72 can detect stroke based on such cardiac activity data. In some examples, the sensing circuit 54 can detect brain activity data, such as electroencephalography (EEG), via electrodes 56, and the event monitoring application 72 can detect stroke or epilepsy based solely on brain activity or in combination with cardiac activity data or other physiological data. In some examples, the event monitoring application 72 can detect whether a patient has fallen based solely on data from an accelerometer or in combination with other physiological data. When the event monitoring application 72 detects an acute health event, it can store the sensing data 82 that led to the detection (and in some cases, a data window before and / or after the detection) as event data 86.

[0049] In some examples, in response to the detection of an acute health event, processing circuitry 50 may attempt to send event data 86 of the event to computing device 12 via communication circuitry 60. This transmission may be included in a message indicating an acute health event and may include a request for an indication from computing device 12 that a message indicating an acute health event has been received and that computing device 12 has network 16 access. In some examples, if IMD 10 does not receive an indication from computing device 12 that a message indicating an acute health event has been received and that computing device 12 has network 16 access, IMD 10 may send a UUID announcement 11, such as... Figures 1A to 1B As shown. In some examples, IMD 10 may send a UUID notification 11 in response to IMD 10 detecting an acute health event.

[0050] The central controller 20 can transmit a request to the computing device 14 to establish a communication path between the central controller 20 and the IMD 10 via the computing device 14, as described above. Figures 1A to 1B As shown in the diagram. In response to establishing a communication path between the central controller 20 and the IMD 10 via the computing device 14, the IMD 10 may transmit one or more of the indication of the detected acute health event and / or the sensed physiological data of the patient 4. In response to establishing a communication path between the central controller 20 and the IMD 10 via the computing device 14, the central controller 20 may authenticate the validity of the IMD 10, such as by requesting a unique authentication term from the IMD 10.

[0051] The communication circuit 60 may include any suitable hardware, firmware, software, or any combination thereof for wireless communication with another device, such as patient computing device 12 and / or computing device 14 and / or device 30.

[0052] Figure 3 This is a block diagram illustrating an exemplary configuration of computing device 14, which may correspond to... Figures 1A to 1B Any one of the illustrated computing devices 14A, 14B, 14C, 14D, 14E and / or 14F (or two computing devices operating in coordination). In some examples, computing device 14 takes the form of a smartphone, smart speaker or other smart home or IoT device, laptop computer, tablet computer, personal digital assistant (PDA), smartwatch or other wearable computing device.

[0053] like Figure 3 As shown, the computing device 14 includes processing circuitry 130, memory 132, one or more input devices 134, one or more output devices 136, sensing circuitry 138, and communication circuitry 140. Although for illustrative purposes... Figure 3While shown as a standalone device, computing device 14 can be any component or system including processing circuitry or other suitable computing environment for executing software instructions, and need not, for example, include... Figure 3 One or more elements are shown.

[0054] Processing circuitry 130 is configured to implement functional and / or processing instructions for execution within computing device 14. 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.

[0055] Memory 132 may be configured to store information within computing device 14 for processing during operation of computing device 14. In some examples, memory 132 may store data or software configured to identify UUID notification 11 as a unique command indicating an acute health emergency. In some examples, memory 132 is described as a computer-readable storage medium. In some examples, memory 132 includes temporary memory or volatile memory. Examples of volatile memory include random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), and other forms of volatile memory known in the art. In some examples, memory 132 may also include one or more memories configured for long-term storage of information, such as including 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 programmable memory (EEPROM).

[0056] One or more input devices 134 of the computing device 14 may receive input, for example, from a 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 panel, microphone, presence-sensitive or touch-sensitive component (e.g., screen), or any other device for detecting input from a user or machine. In some examples, input device 134 may additionally or alternatively include a humidity sensor, such as a PPG sensor, ECG sensor, temperature sensor, impedance sensor, etc., which may enhance and / or assist in the diagnosis of acute health events and / or assist in guiding emergency responders in caring for patient 4.

[0057] One or more output devices 136 of the computing device 14 may generate outputs, for example, to the patient 4 or another user. Examples of outputs are tactile outputs, audio outputs, and visual outputs. The output devices 136 of the computing device 14 may include a 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 outputs.

[0058] The communication circuitry 140 of the computing device 14 can communicate with other devices by transmitting and receiving data. For example, the communication circuitry 140 may be configured to communicate with the IMD 10 and the central controller 20. 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 capable of transmitting and receiving information. For example, the communication circuitry 140 may include a radio transceiver configured to operate according to technologies such as 3G, 4G, 5G, WiFi (e.g., 802.11 or 802.15 ZigBee), or Bluetooth. ® ,Bluetooth ® Communicate using standards or protocols in the form of low-power (BLE) or satellite communication.

[0059] Figure 4 This is a block diagram illustrating the operational perspective of HMS 22. HMS 22 may be implemented in a central controller 20, and the computing system may include hardware components embodied in one or more physical devices, such as computing device 14 and / or server hardware components. Figure 4 Provides an operational perspective of HMS 22 when hosted as a cloud-based platform. Figure 4 In the example, the components of HMS 22 are arranged according to multiple logical layers implementing the technology of this disclosure. Each layer may be implemented by one or more modules including hardware, software, or a combination of hardware and software.

[0060] Computing devices (such as IMD 10 and / or computing device 12) can operate as clients communicating with HMS 22 via interface layer 200. IMD 10 can operate as a client communicating with HMS 22 via computing device 14 when central controller 20 transmits a request to establish a communication path between central controller 20 and IMD 10 via computing device 14 and when a communication path is established. In some examples, IMD 10 can communicate with HMS 22 via computing device 14 and interface layer 200. Interface layer 200 represents a set of application programming interfaces (APIs) or protocol interfaces presented and supported by HMS 22 for client software applications. Interface layer 200 can be implemented using one or more web servers.

[0061] like Figure 4As shown, HMS 22 also includes an application layer 202, which represents a set of services 210 for implementing the functionality categorized herein as HMS. After a communication path is established between the central controller 20 and the IMD 10 via computing device 14, application layer 202 can use the established communication path to receive information from the IMD 10 via computing device 14, such as alarms for acute health events and / or sensed physiological data, and further process the information to respond to it according to one or more of the services 210. Application layer 202 may be implemented as one or more discrete software services 210 executing on one or more application servers (e.g., physical or virtual machines). That is, the application server provides the runtime environment for executing the services 210. In some examples, the functionality of the functional interface layer 200 and application layer 202 as described above may be implemented on the same server. Services 210 may communicate via a logical service bus 212. Service bus 212 generally represents a logical interconnect or interface group that allows different services 210 to send messages to other services, such as through a publish / subscribe communication model.

[0062] The data layer 204 of HMS 22 may provide information using one or more data repositories 220. Data repositories 220 can typically be any data structure or software used to store and / or manage data. Examples of data repositories 220, to name just a few, include, but are not limited to, relational databases, multidimensional databases, maps, and hash tables.

[0063] like Figure 4 As shown, each of services 230 to 238 is implemented as a module within HMS 22. Although shown as a separate module for each service, in some examples, the functionality of two or more services may be combined into a single module or component. Each of services 230 to 238 may be implemented in software, hardware, or a combination of hardware and software. Furthermore, services 230 to 238 may be implemented as a separate device, a separate virtual machine or container, a process, a thread, or software instructions generally intended for execution on one or more physical processors.

[0064] In some examples, in response to receiving a protocol message 15 from computing device 14 instructing the corresponding computing device 14 to receive UUID notification 11, central controller 20 may transmit a request to computing device 14 to generate a communication path between central controller 20 and IMD 10 via computing device 14. In response to the generation of the communication path, event processor 230 may respond to the reception of detected acute health events of patient 4 and / or sensed physiological data sensed by IMD 10 via the generated communication path.

[0065] Event processor 230 may initiate the execution of any of the following operations in response to the detection of an acute health event belonging to HMS 22, such as communicating with the computing device 14 of bystanders and care providers 40, activating verification devices or systems, and in some cases analyzing data to confirm or deny the IMD 10's detection of an acute health event.

[0066] The record management service 238 may store patient data included in received alarm messages in the event log 252. The alarm service 232 may encapsulate some or all of the data from the event log (with additional information as described herein in some cases) into one or more alarm messages to be sent to the computing device 14 of the bystander and / or care provider 40.

[0067] The care provider data 256 may store data used by the alarm service 232 to identify who to send an alarm to based on the location of the computing device 14 of the potential bystander and care provider 40 relative to the location of the patient 4 and / or the applicability of the care provided by care provider 40 to the acute health event experienced by the patient 4.

[0068] In the example where HMS 22 performs analysis to confirm, validate, or reject the detection of an acute health event by IMD 10, event processor 230 may apply one or more rules 250 to the data received in the alert message, such as to a feature vector derived from that data by event processor 230. Rules 250 may include one or more models, algorithms, decision trees, and / or thresholds that can be developed by rule configuration service 234 based on machine learning. Example machine learning techniques that can be used to generate 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, etc. Examples of specific algorithms include Bayesian linear regression, augmented decision tree regression and neural network regression, backpropagation neural network, convolutional neural network (CNN), long short-term network (LSTM), prior algorithm, K-means clustering, K nearest neighbors (kNN), learned 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).

[0069] In some examples, in addition to the rules used by HMS 22 to confirm acute health event detection, rule 250 maintained by HMS 22 may also include rule 84 used by IMD 10. In such examples, rule configuration service 234 may be configured to develop and maintain rule 84. 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 and / or HMS 22 are accurate. In some examples, rule configuration service 234 may utilize event records from true / false detections (as indicated by event feedback data 254) and confirmation of supervised machine learning to further train the model included as part of rule 250. Figure 4 As illustrated in the example, service 210 may also include an assistant configuration service 236 for configuring and interacting with the computing device.

[0070] Figure 5 This is a flowchart illustrating an example of the technology of this disclosure. Figure 5In the example, IMD 10 senses physiological data of patient 4 (502) and detects an acute health event of patient 4 based on the sensed physiological data (504). In response to the detection of an acute health event, IMD 10 sends a UUID announcement 11 (506). IMD 10 may send the UUID announcement 11 according to a short-range wireless protocol. Computing device 14 receives the UUID announcement 11 (508) and, in response to receiving the UUID announcement 11, sends a protocol message 15 to central controller 20 (510). Central controller 20 receives the protocol message 15 (512) and, in response to receiving the protocol message 15, sends a request 17 (514) to computing device 14 to establish a communication path 518 between central controller 20 and IMD 10 via computing device 14. In response to the generation of communication path 518, IMD 10 sends one or more of the indication of a detected acute health event or the sensed physiological data to central controller 20 via communication path 518 (516). In some examples, the generated communication path 518 is a bidirectional communication path between IMD 10 and central controller 20 via computing device 14. In some examples, in response to receiving one or more of the indication of a detected acute health event or the sensed physiological data via communication path 518, central controller 20 may be configured to transmit an emergency message to one or more computing devices 14 (520). In some examples, the emergency message may include an alert to care providers, emergency medical technicians, or other designated personnel in or near environment 28. In some examples, UUID notification 11 may not be a proprietary, patient-specific message, but rather a signal that another intelligent computing device not directly associated with IMD 10 may be able to interpret as an emergency. In some examples, UUID notification 11 may include one or more of the following: an indication that an acute health event has occurred, an indication of the time of the event, and / or an indication or identifier of the device to be monitored by the remote patient monitoring system. In some examples, protocol message 15 may include an indication that computing device 14 has received UUID notification 11. In some examples, protocol message 15 may include an indication of geographic location. For example, an indication of geographic location may include one or more of the geographic location of computing device 14 transmitting protocol message 15, the geographic location of IMD 10, and / or the geographic location of computing device 14 at the time it receives UUID notification 11.

[0071] It should be understood that the various aspects disclosed herein can be combined with combinations different from those specifically presented in the specification and drawings. It should also be understood that, depending on the example, certain actions or events of any of the processes or methods described herein may be performed in a different order, or may be completely added, combined, or omitted (e.g., performing these techniques may not require all the described actions or events). Furthermore, although some aspects of this disclosure are described for clarity as being performed by a single module, unit, or circuit, it should be understood that the techniques of this disclosure can be performed by combinations of units, modules, or circuits associated with, for example, a medical device.

[0072] In one or more examples, the described techniques may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored as one or more instructions or code on a computer-readable medium and executed by a hardware-based processing unit. The computer-readable medium may include a non-transitory computer-readable medium that corresponds to a tangible medium, such as a data storage medium (e.g., RAM, ROM, EEPROM, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that is accessible by a computer).

[0073] Instructions can be executed by one or more processors (such as one or more digital signal processors (DSPs)), general-purpose microprocessors, application-specific integrated circuits (ASICs), field-programmable arrays (FPGAs), or other equivalent integrated or discrete logic circuits. Therefore, the terms "processor" or "processing circuitry" as used herein may refer to any of the foregoing structures or any other physical structure suitable for implementing the described techniques. Furthermore, these techniques can be fully implemented in one or more circuit or logic elements.

[0074] The following examples illustrate the techniques described herein.

[0075] Example 1: A system comprising an implantable medical device (IMD) configured to: sense physiological data of a patient; detect an acute health event of the patient based on the sensed physiological data; and, in response to detecting the acute health event, transmit a Universal Unique Identifier (UUID) notification according to a short-range wireless protocol; and a computing device configured to: receive the UUID notification; and, in response to receiving the UUID notification, send a protocol message to a central controller, the protocol message including an indication that the computing device has received the UUID notification; and receive from the central controller a request to generate a communication path between the central controller and the IMD via the computing device, wherein the computing device is configured to be connected to the central controller via a network connection and the computing device is configured to be connected to the IMD via the short-range wireless protocol, the request being transmitted by the central controller in response to receiving the protocol message from the computing device; wherein, in response to the generation of the communication path, the IMD is configured to send to the central controller one or more of an indication of the detected acute health event or the sensed physiological data via the communication path.

[0076] Example 2: The system according to Example 1, wherein the generated communication path is a bidirectional communication path between the IMD and the central controller via the computing device.

[0077] Example 3: The system according to any one of Examples 1 to 2, wherein the computing device is a second computing device, and the IMD is further configured to: determine that the patient's first computing device cannot communicate with one or more of the IMD or the central controller; and send the UUID notification in response to detecting the acute health event and determining that the first computing device cannot communicate with one or more of the IMD or the central controller.

[0078] Example 4: The system according to any one of Examples 1 to 3, wherein the protocol message includes an indication of geographical location.

[0079] Example 5: The system according to Example 4, wherein the indication of geographical location includes one or more of the geographical location of the computing device, the geographical location of the IMD, or the geographical location of the computing device when it receives the UUID notification.

[0080] Example 6: The system according to any one of Examples 1 to 5, wherein the UUID announcement includes an emergency identifier.

[0081] Example 7: The system according to any one of Examples 1 to 6, wherein the UUID announcement includes the identification information of the central controller.

[0082] Example 8: The system according to any one of Examples 1 to 7, wherein the UUID notification does not include information on the detected acute health events.

[0083] Example 9: The system according to any one of Examples 1 to 7, wherein the UUID notification does not include the patient's physiological data.

[0084] Example 10: The system according to any one of Examples 1 to 9, wherein the protocol message does not include the content of the UUID announcement.

[0085] Example 11: The system according to any one of Examples 1 to 10, the system further includes, in response to receiving the protocol message, transmitting a request to another computing device within a predetermined distance of the computing device to generate a communication path between the central controller and the IMD via the other computing device.

[0086] Example 12: A method for an operating system, the method comprising: sensing physiological data of a patient by an IMD; detecting an acute health event of the patient by the IMD based on the sensed physiological data; transmitting a Universal Unique Identifier (UUID) announcement by the IMD according to a short-range wireless protocol in response to detecting the acute health event; receiving the UUID announcement by a computing device; sending a protocol message to a central controller in response to receiving the UUID announcement, the protocol message including an indication that the computing device has received the UUID announcement; receiving from the central controller a request by the computing device to generate a communication path between the central controller and the IMD via the computing device, wherein the computing device is configured to be connected to the central controller via a network connection and the computing device is configured to be connected to the IMD via the short-range wireless protocol, the request being transmitted by the central controller in response to receiving the protocol message from the computing device; and, in response to the generation of the communication path, sending to the central controller via the communication path one or more of an indication of the detected acute health event or sensed physiological data.

[0087] Example 13: The method according to Example 12, wherein the computing device is a second computing device, and the method further includes: determining by the IMD that the first computing device cannot communicate with one or more of the IMD or the central controller; and sending the UUID notification in response to detecting the acute health event and determining that the first computing device cannot communicate with one or more of the IMD or the central controller.

[0088] Example 14: The method according to any one of Examples 12 to 13, the method further includes, in response to receiving the protocol message, the central controller transmitting a request to another computing device within a predetermined distance of the computing device to generate a communication path between the central controller and the IMD via the other computing device.

[0089] Example 15: The method according to any one of Examples 12 to 14, wherein the generated communication path is a bidirectional communication path between the IMD and the central controller via the computing device.

[0090] Example 16: The method according to any one of Examples 12 to 15, wherein the protocol message includes an indication of geographical location.

[0091] Example 17: The method according to Example 16, wherein the indication of geographic location includes one or more of the geographic location of the computing device, the geographic location of the IMD, or the geographic location of the computing device when it receives the UUID notification.

[0092] Example 18: The method according to any one of Examples 12 to 17, wherein the UUID announcement includes an emergency identifier.

[0093] Example 19: The method according to any one of Examples 12 to 18, wherein the UUID notification includes the identification information of the central controller.

[0094] Example 20: The method according to any one of Examples 12 to 19, wherein the UUID notification does not include information about the detected acute health event.

[0095] Example 21: The system according to any one of Examples 12 to 19, wherein the UUID notification does not include the patient's physiological data.

[0096] Example 22: The method according to any one of Examples 12 to 21, wherein the protocol message does not include the content of the UUID announcement.

[0097] Example 23: A computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of Examples 12 to 22.

[0098] Example 24: A computing device comprising: a communication circuit; and a processing circuit configured to: receive, via the communication circuit, a UUID notification transmitted by an implantable medical device (IMD) according to a short-range wireless protocol, the UUID notification being transmitted by the IMD in response to detecting an acute health event of the patient based on physiological data sensed by the IMD; in response to receiving the UUID notification, control the communication circuit to send a protocol message to a central controller, the protocol message including an indication that the computing device has received the UUID notification; and receive, via the communication circuit, a notification from the central controller via the computing device. A request to establish a communication path between the controller and the IMD, wherein the processing circuitry is configured to control the communication circuitry to connect to the central controller via a network connection and to the IMD via the short-range wireless protocol, the request being transmitted by the central controller in response to receiving the protocol message from the computing device; and in response to receiving the request, establishing the communication path between the central controller and the IMD via the computing device, wherein, in response to the establishment of the communication path, the IMD is configured to send one or more of an indication of a detected acute health event or sensed physiological data to the central controller via the communication path.

[0099] Example 25: The computing device according to Example 24, wherein the generated communication path is a bidirectional communication path between the IMD and the central controller via the computing device.

[0100] Example 26: A computing device according to any one of Examples 24 to 25, wherein the protocol message includes an indication of a geographical location.

[0101] Example 27: The computing device according to Example 26, wherein the indication of geographic location includes one or more of the geographic location of the computing device, the geographic location of the IMD, or the geographic location of the computing device when it receives the UUID notification.

[0102] Example 28: A computing device according to any one of Examples 24 to 27, wherein the UUID announcement includes an emergency identifier.

[0103] Example 29: A computing device according to any one of Examples 24 to 28, wherein the UUID announcement includes identification information of the central controller.

[0104] Example 30: A computing device according to any one of Examples 24 to 28, wherein the UUID notification does not include information about the detected acute health event.

[0105] Example 31: A computing device according to any one of Examples 24 to 30, wherein the protocol message does not include the content of the UUID announcement.

[0106] Various embodiments have been described. These and other embodiments are within the scope of the appended claims.

Claims

1. A system comprising: Implantable medical device (IMD), the IMD being configured as follows: Sensing the patient's physiological data; The patient's acute health events are detected based on the sensed physiological data; as well as In response to the detection of the acute health event, a Universal Unique Identifier (UUID) notification is sent according to the Short Range Radio Protocol; Computing device, the computing device being configured to: Receive the UUID notification; In response to receiving the UUID notification, a protocol message is sent to the central controller, the protocol message including an indication that the computing device has received the UUID notification; as well as A request is received from the central controller to generate a communication path between the central controller and the IMD via the computing device, wherein the computing device is configured to be connected to the central controller via a network connection and the computing device is configured to be connected to the IMD via the short-range wireless protocol, and the request is transmitted by the central controller in response to receiving the protocol message from the computing device; In response to the generation of the communication path, the IMD is configured to send one or more of an indication of a detected acute health event or sensed physiological data to the central controller via the communication path.

2. The system of claim 1, wherein the generated communication path is a bidirectional communication path between the IMD and the central controller via the computing device.

3. The system according to any one of claims 1 to 2, wherein the computing device is a second computing device, and the IMD is further configured to: The patient's first computing device is determined to be unable to communicate with one or more of the IMD or the central controller; and In response to detecting the acute health event and determining that the first computing device cannot communicate with one or more of the IMD or the central controller, the UUID notification is sent.

4. The system according to any one of claims 1 to 3, wherein the protocol message includes an indication of a geographic location, wherein the indication of the geographic location includes one or more of the geographic location of the computing device, the geographic location of the IMD, or the geographic location of the computing device at the time it receives the UUID notification.

5. The system according to any one of claims 1 to 4, wherein the UUID notification includes an emergency identifier.

6. The system according to any one of claims 1 to 5, wherein the UUID notification includes the identification information of the central controller.

7. The system according to any one of claims 1 to 6, wherein the UUID notification does not include information on the detected acute health event.

8. The system according to any one of claims 1 to 7, wherein the UUID notification does not include the patient's physiological data.

9. The system according to any one of claims 1 to 8, wherein the protocol message does not include the content of the UUID announcement.

10. The system according to any one of claims 1 to 9, the system further comprising the central controller, wherein the central controller is further configured to: in response to receiving the protocol message, transmit a request to another computing device within a predetermined distance of the computing device to generate a communication path between the central controller and the IMD via the other computing device.

11. A computing device, the computing device comprising: Communication circuits; and Processing circuit, the processing circuit being configured to: The communication circuit receives a UUID notification sent by an implantable medical device (IMD) according to a short-range wireless protocol. The UUID notification is sent by the IMD in response to the detection of an acute health event in the patient based on physiological data sensed by the IMD. In response to receiving the UUID notification, the communication circuit is controlled to send a protocol message to the central controller, the protocol message including an indication that the computing device has received the UUID notification; The processing circuit receives a request from the central controller via the communication circuit to generate a communication path between the central controller and the IMD via the computing device, wherein the processing circuit is configured to control the communication circuit to connect to the central controller via a network connection and to the IMD via the short-range wireless protocol, and the request is transmitted by the central controller in response to receiving the protocol message from the computing device; as well as In response to receiving the request, the communication path is generated between the central controller and the IMD via the computing device. In response to the generation of the communication path, the IMD is configured to send one or more of an indication of a detected acute health event or sensed physiological data to the central controller via the communication path.

12. The computing device of claim 11, wherein the generated communication path is a bidirectional communication path between the IMD and the central controller via the computing device.

13. The computing device according to any one of claims 11 to 12, wherein the protocol message includes an indication of geographical location, The indication of geographic location includes one or more of the geographic location of the computing device, the geographic location of the IMD, or the geographic location of the computing device when it receives the UUID notification.

14. The computing device according to any one of claims 11 to 13, wherein the UUID notification includes at least one of an emergency identifier or identification information of the central controller, and The protocol message mentioned therein does not include the content of the UUID announcement.

15. The computing device according to any one of claims 11 to 14, wherein the UUID notification does not include information about the detected acute health event.

Images