[0001] This application claims the benefit of U.S. Provisional Patent Application Serial No. 63/375,657, filed September 14, 2022, the entire content of which is incorporated herein by reference.

FIELD

[0002] This disclosure generally relates to systems including medical devices and, more particularly, to monitoring of patient health using such systems.

BACKGROUND

[0003] A variety of devices are configured to monitor physiological signals of a patient.

Such devices include implantable or wearable medical devices, as well as a variety of wearable health or fitness tracking devices. The physiological signals sensed by such devices include as examples, electrocardiogram (ECG) signals, respiration signals, perfusion signals, activity and/or posture signals, pressure signals, blood oxygen saturation signals, body composition, and blood glucose or other blood constituent signals. In general, using these signals, such devices facilitate monitoring and evaluating patient health over a number of months or years, outside of a clinic setting.

[0004] In some cases, such devices are configured to detect acute health events based on the physiological signals, such as episodes of cardiac arrhythmia, myocardial infarction, stroke, or seizure. Example arrhythmia types include cardiac arrest (e.g., asystole), ventricular tachycardia (VT), and ventricular fibrillation (VF). The devices may store ECG and other physiological signal data collected during a time period including an episode as episode data. Such acute health events are associated with significant rates of death, particularly if not treated quickly.

[0005] For example, VF and other malignant tachyarrhythmias are the most commonly identified arrhythmia in sudden cardiac arrest (SCA) patients. If this arrhythmia continues for more than a few seconds, it may result in cardiogenic shock and cessation of effective blood circulation. The survival rate from SCA decreases between 7 and 10 percent for every minute that the patient waits for defibrillation. Consequently, sudden cardiac death (SCD) may result in a matter of minutes. SUMMARY

[0006] In general, the disclosure describes techniques for detection of acute health events, such as SCA, by monitoring patient parameter data, such as ECG data. More particularly, the disclosure describes techniques that include providing responsive, cancellable alarms as a wellness check to determine whether the patient is responsive, or the acute health event is occurring. If not canceled within a period of time, action may be taken in response to the acute health event.

[0007] In some examples, a computing device that provides such alarms determines an alarm context, and configures the alarm based on the alarm context. In this manner, the duration and/or intensity of the alarm may be relatively greater when the patient is less likely to be alert or otherwise quickly able to cancel the alarm and/or when the acute health event is less severe and/or less likely to be actually occurring. The duration of the alarm may be relatively shorter when the patient is more likely to be alert or otherwise quickly able to cancel the alarm and/or when the type of acute health event is more se vere and/or more likely to be actually occurring. Adaptive alarms according to the techniques of this disclosure may advantageously improve the ability of the user to override alarms when appropriate, while shortening an alarm period when the acute health event is se vere and/or likely, e.g., a high probability of lethal tachyarrhythmia which may lead to SCA.

[0008] In an example, a computing device comprises: communication circuitry configured to wirelessly communicate with a sensor device on a patient or implanted within the patient; one or more output devices; and processing circuitry configured to: receive episode data for an acute health event detected by the sensor device via the communication circuitry, the episode data transmitted by the sensor device in response to detecting the acute health event; determine an alarm context in response to receiving the episode data; configure an alarm for the acute health event based on the alarm context; and control the one or more output devices to output the alarm that is configured based on the alarm context.

[0009] In another example, a system comprises a sensor device and a computing device as described above.

[0010] In another example, a method of operating a computing device comprises: receiving, via communication circuitry of the computing device, episode data for an acute health event detected by a sensor device, the episode data transmitted by the sensor device in response to detecting the acute health event; determining, by processing circuitry of the computing device, an alarm context in response to receiving the episode data; configuring, by the processing circuitry, an alarm for the acute health event based on the alarm context; and controlling, by the processing circuitry, one or more output devices of the computing device to output the alarm that is configured based on the alarm context.

[0011] In another example, a non-transitory computer-readable storage medium comprises instructions that cause processing circuitry to: receive episode data for an acute health event detected by a sensor device, the episode data transmitted by the sensor device in response to detecting the acute health event; determine an alarm context in response to receiving the episode data; configure an alarm for the acute health event based on the alarm context; and output the alarm that is configured based on the alarm context.

[0012] This summary is intended to provide an overview of the subject matter described in this disclosure. It is not intended to provide an exclusive or exhaustive explanation of the apparatus and methods described in detail within the accompanying drawings and description below. Further details of one or more examples are set forth in the accompanying drawings and the description below.

BRIEF DESCRIPTION OF DRAWINGS

[0013] FIG. 1 is a block diagram illustrating an example system configured detect acute health events of a patient, and to respond to such detections, in accordance with one or more techniques of this disclosure.

[0014] FIG. 2 is a block diagram illustrating an example configuration of a patient sensing device that operates in accordance with one or more techniques of the present disclosure.

[0015] FIG. 3 is a block diagram illustrating an example configuration of a computing device that operates in accordance with one or more techniques of the present disclosure.

[0016] FIG. 4 is a block diagram illustrating an example configuration of a health monitoring system that operates in accordance with one or more techniques of the present disclosure.

[0017] FIG. 5 is a flow diagram illustrating an example operation for applying rules to patient parameter data to determine whether an acute health event is detected.

[0018] FIG. 6 is a flow diagram illustrating another example operation for applying rules to patient parameter data to determine whether an acute health event is detected.

[0019] FIG. 7 is a flow diagram illustrating an example operation for configuring rules applied to patient parameter data to determine whether an acute health event is detected for a patient. [0020] FIG. 8 is a flow diagram illustrating another example operation for configuring rules applied to patient parameter data to determine whether an acute health event is detected for a patient.

[0021] FIG. 9 is a block diagram illustrating an example of an ensemble of neural networks configured to classify ventricular tachyarrhythmias.

[0022] FIG. 10 is a block diagram illustrating an example of a single classifier utilizing raw signals and derived features.

[0023] FIG. 11 is a block diagram illustrating a staged approach for classifying a ventricular tachyarrhythmia episode.

[0024] FIGS. 12A and 12B illustrate frequency decompositions of a monomorphic ventricular tachycardia episode and a supraventricular tachycardia episode, respectively. [0025] FIG. 13 is a flow diagram illustrating an example operation for configuring an acute health event alarm based on an alarm context.

[0026] FIG. 14 is a conceptual diagram illustrating an example machine learning model configured to determine an extent to which data of a patient indicates an acute health event. [0027] FIG. 15 is a conceptual diagram illustrating an example training process for a machine learning model, in accordance with examples of the current disclosure.

[0028] FIG. 16A is a perspective drawing illustrating an insertable cardiac monitor.

[0029] FIG. 16B is a perspective drawing illustrating another insertable cardiac monitor.

[0030] Like reference characters refer to like elements throughout the figures and description.

DETAILED DESCRIPTION

[0031] A variety of types of implantable and external devices are configured to detect arrhythmia episodes and other acute health events based on sensed ECGs and, in some cases, other physiological signals. External devices that may be used to non-invasively sense and monitor ECGs and other physiological signals include wearable devices with electrodes configured to contact the skin of the patient, such as patches, watches, rings, necklaces, hearing aids, a wearable cardiac monitor or automated external defibrillator (AED), clothing, car seats, orbed linens. Such external devices may facilitate relatively longer-term monitoring of patient health during normal daily activities.

[0032] Implantable medical devices (IMDs) also sense and monitor ECGs and other physiological signals and detect acute health events such as episodes of arrhythmia, cardiac arrest, myocardial infarction, stroke, and seizure. Example IMDs include pacemakers and implantable cardioverter-defibrillators, which may be coupled to intravascular or extravascular leads, as well as pacemakers with housings configured for implantation within the heart, which may be leadless. Some IMDs do not provide therapy, such as implantable patient monitors. One example of such an IMD is the Reveal LINQ™ and LINQ II™ Insertable Cardiac Monitors (ICMs), available from Medtronic, Inc., which may be inserted subcutaneously. Such IMDs may facilitate relatively longer-term monitoring of patients during normal daily activities, and may periodically transmit collected data, e.g., episode data for detected arrhythmia episodes, to a remote patient monitoring system, such as the Medtronic Carelink™ Network.

[0033] FIG. 1 is a block diagram illustrating an example system 2 configured detect acute health events of a patient 4, and to respond to such detection, in accordance with one or more techniques of this disclosure. As used herein, the terms “detect,” “detection,” and the like may refer to detection of an acute health event presently (at the time the data is collected) being experienced by patient 4, as well as detection based on the data that the condition of patient 4 is such that they have a suprathreshold likelihood of experiencing the event within a particular timeframe, e.g., prediction of the acute health event. The example techniques may be used with one or more patient sensing devices, e.g., IMD 10, which may be in wireless communication with one or more patient computing devices, e.g., patient computing devices 12A and 12B (collectively, “patient computing devices 12”). Although not illustrated in FIG. 1, IMD 10 include electrodes and other sensors to sense physiological signals of patient 4 and may collect and store sensed physiological data based on the signals and detect episodes based on the data.

[0034] IMD 10 may be implanted outside of a thoracic cavity of patient 4 (e.g., subcutaneously in the pectoral location illustrated in FIG. 1). IMD 10 may be positioned near the sternum near or just below the level of the heart of patient 4, e.g., at least partially within the cardiac silhouette. In some examples, IMD 10 takes the form of a LINQ ICM. Although described primarily in the context of examples in which IMD 10 takes the form of an ICM, the techniques of this disclosure may be implemented in systems including any one or more implantable or external medical devices, including monitors, pacemakers, defibrillators (e.g., subcutaneous or substemal), wearable external defibrillators (WAEDs), neurostimulators, or drug pumps. Furthermore, although described primarily in the context of examples including a single implanted patient sensing device, in some examples a system includes one or more patient sensing devices, which may be implanted within patient 4 or external to (e.g., worn by) patient 4. For example, a system with two IMDs 10 may capture different values of a common patient parameter with different resolution/accuracy based on their respective locations. In some examples, instead of or in addition to two IMDs 10, system 2 may include a ventricular assist device or WAED in addition to IMD 10.

[0035] Patient computing devices 12 are configured for wireless communication with IMD 10. Computing devices 12 retrieve event data and other sensed physiological data from IMD 10 that was collected and stored by the IMD. In some examples, computing devices 12 take the form of personal computing devices of patient 4. For example, computing device 12A may take the form of a smartphone of patient 4, and computing device 12B may take the form of a smartwatch or other smart apparel of patient 4. In some examples, computing devices 12 may be any computing device configured for wireless communication with IMD 10, such as a desktop, laptop, or tablet computer. Computing devices 12 may communicate with IMD 10 and each other according to the Bluetooth® or Bluetooth® Low Energy (BLE) protocols, as examples. In some examples, only one of computing devices 12, e.g., computing device 12A, is configured for communication with IMD 10, e.g., due to execution of software (e.g., part of a health monitoring application as described herein) enabling communication and interaction with an IMD.

[0036] In some examples, computing device(s) 12, e.g., wearable computing device 12B in the example illustrated by FIG. 1, may include electrodes and other sensors to sense physiological signals of patient 4, and may collect and store physiological data and detect episodes based on such signals. Computing device 12B may be incorporated into the apparel of patient 14, such as within clothing, shoes, eyeglasses, a watch or wristband, a hat, etc. In some examples, computing device 12B is a smartwatch or other accessory or peripheral for a smartphone computing device 12A.

[0037] One or more of computing devices 12 may be configured to communicate with a variety of other devices or systems via a network 16. For example, one or more of computing devices 12 may be configured to communicate with one or more computing systems, e.g., computing systems 20A and 20B (collectively, “computing systems 20”) via network 16. Computing systems 20A and 20B may be respectively managed by manufacturers of IMD 10 and computing devices 12 to, for example, provide cloud storage and analysis of collected data, maintenance and software services, or other networked functionality fortheir respective devices and users thereof. Computing system 20A may comprise, or may be implemented by, the Medtronic Carelink™ Network, in some examples. In the example illustrated by FIG. 1, computing system 20A implements a health monitoring system (HMS) 22, although in other examples, either of both of computing systems 20 may implement HMS 22. As will be described in greater detail below, HMS 22 facilities detection of acute health events of patient 4 by system 2, and the responses of system 2 to such acute health events.

[0038] Computing device(s) 12 may transmit data, including data retrieved from IMD 10, to computing system(s) 20 via network 16. The data may include sensed data, e.g., values of physiological parameters measured by IMD 10 and, in some cases one or more of computing devices 12, data regarding episodes of arrhythmia or other acute health events detected by IMD 10 and computing device(s) 12, and other physiological signals or data recorded by IMD 10 and/or computing device(s) 12. HMS 22 may also retrieve data regarding patient 4 from one or more sources of electronic health records (EHR) 24 via network. EHR 24 may include data regarding historical (e.g., baseline) physiological parameter values, previous health events and treatments, disease states, comorbidities, demographics, height, weight, and body mass index (BMI), as examples, of patients including patient 4. HMS 22 may use data from EHR 24 to configure algorithms implemented by IMD 10 and/or computing devices 12 to detect acute health events for patient 4. In some examples, HMS 22 provides data from EHR 24 to computing device(s) 12 and/or IMD 10 for storage therein and use as part of their algorithms for detecting acute health events.

[0039] 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 administered by service providers and may thus form part of a large-scale public network infrastructure, e.g., the Internet. Network 16 may provide computing devices and systems, such as those illustrated in FIG. 1, access to the Internet, and may provide a communication framework that allows the computing devices and systems to communicate with one another. In some examples, network 16 may include a private network that provides a communication framework that allows the computing devices and systems illustrated in FIG. 1 to communicate with each other but isolates some of the data flows from devices external to the private network for security purposes. In some examples, the communications between the computing devices and systems illustrated in FIG. 1 are encrypted.

[0040] As will be described herein, IMD 10 may be configured to detect acute health events of patient 4, such as SCA, based on data sensed by IMD 10 and, in some cases, other data, such as data sensed by computing devices 12A and/or 12B, and data from EHR 24. To detect acute health events, IMD 10 may apply rules to the data, which may be referred to as patient parameter data. In response to detection of an acute health event, IMD 10 may wirelessly transmit a message to one or both of computing devices 12A and 12B. The message may indicate that IMD 10 detected an acute health event of the patient. The message may indicate a time that IMD 10 detected the acute health event. The message may include physiological data collected by IMD 10, e.g., data which lead to detection of the acute health event, data prior to detection of the acute health event, and/or real-time or more recent data collected after detection of the acute health event. The physiological data may include values of one or more physiological parameters and/or digitized physiological signals. Examples of acute health events are SCA, a ventricular fibrillation, a ventricular tachycardia, myocardial infarction, a pause in heart rhythm (asystole), or Pulseless Electrical Activity (PEA), acute respiratory distress syndrome (ARDS), a stroke, a seizure, or a fall. [0041] In some examples, the detection of the acute health event by IMD 10 may include multiple phases. For example, IMD 10 may complete an initial detection of the acute health event, e.g., SCA or tachyarrhythmia, and initiate wireless communication, e.g., Bluetooth® or Bluetooth Low Energy®, with computing device(s) 12 in response to the initial detection. The initial detection may occur five to ten seconds after onset of the acute health event, for example. IMD 10 may continue monitoring to determine whether the acute health event is sustained, e.g., a sustained detection of SCA or tachyarrhythmia. In some examples, IMD 10 may use more patient parameters and/or different rules to determine whether event is sustained or otherwise confirm detection.

[0042] Initiating communication with computing device(s) 12 in response to an initial detection may facilitate the communication being established at the time the acute health event is confirmed as sustained. To conserve power of IMD 10 and computing device(s) 12, IMD 10 may wait to send the message, e.g., including sensed data associated with the acute health event, until it is confirmed as sustained, which may be determined about thirty seconds after onset of the event, or after a longer period of time. Less urgent events may have longer confirmation phases and may be alerted with less urgency, such being alerted as health care events rather than acute health events. However, the initiation of communication after initial detection may still benefit less urgent events. Conserving power may be significant in the case of non-rechargeable IMDs to prolong their life prior to needing surgery for replacement, as well as for rechargeable IMDs or external devices to reduce recharge frequency.

[0043] Based on the message from IMD 10, computing device(s) 12 may output an alarm that may be visual and/or audible and configured to immediately attract the attention of patient 4 or any person in environment 28 with patient 4, e.g., a bystander 26. Additionally or alternatively, computing device(s) 12 may transmit an alert or alarm message to devices and users outside the visible/audio range of computing device(s) 12, e.g., to loT devices 30, bystander computing device 42, or HMS 22. Environment 28 may be a home, office, or place of business, or public venue, as examples. An alert or alarm message sent to HMS 22 via network 16, or other messages sent by computing device(s) 12, may include the data received from IMD 10 and, in some cases, additional data collected by computing device(s) 12 or other devices in response to the detection of the acute health event by IMD 10. For example, the message may include a location of patient 4 determined by computing device(s) 12. In some examples, computing device(s) 12 may further configure or change the content of alert or alarm messages based on the location of patient 4, e.g., different messages may be sent depending on whether patient 4 is at home, another residence, an office or business, a public location, or in a health care facility. The health care needed by patient, and thus the messaging of system 2, may vary depending on the location of patient 4.

[0044] Other devices in the environment 28 of patient 4 may also be configured to output alarms or take other actions to attract the attention of patient 4 and, possibly, a bystander 26, or to otherwise facilitate the delivery of care to patient 4. For example, environment 28 may include one or more Internet of Things (loT) devices, such as loT devices 30A-30D (collectively “loT devices 30”) illustrated in the example of FIG. 1. loT devices 30 may include, as examples, so called “smart” speakers, cameras, televisions, lights, locks, thermostats, appliances, actuators, controllers, or any other smart home (or building) devices. In the example of FIG. 1, loT device 30C is a smart speaker and/or controller, which may include a display. loT devices 30 may provide audible and/or visual alarms when configured with output devices to do so. As other examples, loT devices 30 may cause smart lights throughout environment 28 to flash or blink and unlock doors. In some examples, loT devices 30 that include cameras, microphones, or other sensors may activate those sensors to collect data regarding patient 4, e.g., for evaluation of the condition of patient 4.

[0045] Computing device(s) 12 may be configured to wirelessly communicate with loT devices 30 to cause loT devices 30 to take the actions described herein. In some examples, HMS 22 communicates with loT devices 30 via network 16 to cause loT devices 30 to take the actions described herein, e.g., in response to receiving the alert message from computing device(s) 12 as described above. In some examples, IMD 10 is configured to communicate wirelessly with one or more of loT devices 30, e.g., in response to detection of an acute health event when communication with computing devices 12 is unavailable. In such examples, loT device(s) 30 may be configured to provide some or all of the functionality ascribed to computing devices 12 herein.

[0046] Environment 28 includes computing facilities, e.g., a local network 32, by which computing devices 12, loT devices 30, and other devices within environment 28 may communicate via network 16, e.g., with HMS 22. For example, environment 28 may be configured with wireless technology, such as IEEE 802.11 wireless networks, IEEE 802. 15 ZigBee networks, an ultra-wideband protocol, near-field communication, or the like. Environment 28 may include one or more wireless access points, e.g., wireless access points 34A and 34B (collectively, “wireless access points 34”) that provide support for wireless communications throughout environment 28. Additionally or alternatively, e.g., when local network is unavailable, computing devices 12, loT devices 30, and other devices within environment 28 may be configured to communicate with network 16, e.g., with HMS 22, via a cellular base station 36 and a cellular network.

[0047] Computing device(s) 12, and in some examples loT device(s) 30, may include input devices and interfaces to allow a user to override the alarm in the event the detection of the acute health event by IMD 10 was false. In some examples, one or more of computing device(s) 12 and loT device(s) 30 may implement an event assistant. The event assistant may provide a conversational interface for patient 4 and/or bystander 26 to exchange information with the computing device or loT device. The event assistant may query the user regarding the condition of patient 4 in response to receiving the alert message from IMD 10. Responses from the user may be used to confirm or override detection of the acute health event by IMD 10, or to provide additional information about the acute health event or the condition of patient 4 more generally that may improve the efficacy of the treatment of patient 4. For example, information received by the event assistant may be used to provide an indication of severity or type (differential diagnosis) for the acute health event. The event assistant may use natural language processing and context data to interpret utterances by the user. In some examples, in addition to receiving responses to queries posed by the assistant, the event assistant may be configured to respond to queries posed by the user. For example, patient 4 may indicate that they feel dizzy and ask the event assistant, “how am I doing?”.

[0048] In some examples, computing device(s) 12 and/or HMS 22 may implement one or more techniques to evaluate the sensed physiological data received from IMD 10, and in some cases additional physiological or other patient parameter data sensed or otherwise collected by the computing device(s) or loT devices 30, to confirm or override the detection of the acute health event by IMD 10. In some examples, computing device(s) 12 and/or computing system(s) 20 may have greater processing capacity than IMD 10, enabling more complex analysis of the data. In some examples, the computing device(s) 12 and/or HMS 22 may apply the data to one or more machine learning models or other artificial intelligence developed algorithms, e.g., to determine whether the data is sufficiently indicative of the acute health event.

[0049] In examples in which computing device(s) 12 are configured perform an acute health event confirmation analysis, computing device(s) 12 may output alert messages and/or transmit alert messages to HMS 22 and/or loT devices 30 in response to confirming the acute health event. In some examples, computing device(s) 12 may be configured to output/transmit the alert messages prior to completing the confirmation analysis, and output/transmit cancellation messages in response to the analysis overriding the detection of the acute health event by IMD 10. HMS 22 may be configured to perform a number of operations in response to receiving an alert message from computing device(s) 12 and/or loT device(s) 30. HMS 22 may be configured to cancel such operations in response to receiving a cancellation message from computing device(s) 12 and/or loT device(s) 30.

[0050] For example, HMS 22 may be configured to transmit alert messages to one or computing devices 38 associated with one or more care providers 40 via network 16. Care providers may include emergency medical systems (EMS) and hospitals, and may include particular departments within a hospital, such as an emergency department, catheterization lab, or a stroke response department. Computing devices 38 may include smartphones, desktop, laptop, or tablet computers, or workstations associated with such systems or entities, or employees of such systems or entities. The alert messages may include any of the data collected by IMD 10, computing device(s) 12, and loT device(s) 30, including sensed physiological data, time of the acute health event, location of patient 4, and results of the analysis by IMD 10, computing device(s) 12, loT device(s) 30, and/or HMS 22. The information transmitted from HMS 22 to care providers 40 may improve the timeliness and effectiveness of treatment of the acute health event of patient 4 by care providers 40. In some examples, instead of or in addition to HMS 22 providing an alert message to one or more computing devices 38 associated with an EMS care provider 40, computing device(s) 12 and/or loT devices 30 may be configured to automatically contact EMS, e.g., autodial 911, in response to receiving an alert message from IMD 10. Again, such operations may be cancelled by patient 4, bystander 26, or another user via a user interface of computing device(s) 12 or loT device(s) 30, or automatically cancelled by computing device(s) 12 based on a confirmatory analysis performed by the computing device(s) overriding the detection of the acute health event by IMD 10.

[0051] Similarly, HMS 22 may be configured to transmit an alert message to computing device 42 of bystander 26, which may improve the timeliness and effectiveness of treatment of the acute health event of patient 4 by bystander 26. Computing device 42 may be similar to computing devices 12 and computing devices 38, e.g., a smartphone. In some examples, HMS 22 may determine that bystander 26 is proximate to patient 4 based on a location of patient 4, e.g., received from computing device(s) 12, and a location of computing device 42, e.g., reported to HMS 22 by an application implemented on computing device 42. In some examples, HMS 22 may transmit the alert message to any computing devices 42 in an alert area determined based on the location of patient 4, e.g., by transmitting the alert message to all computing devices in communication with base station 36, using any of the networking methods described herein.

[0052] In some examples, the alert message to bystander 26 may be configured to assist a layperson in treating patient. For example, the alert message to bystander 26 may include a location (and in some cases a description) of patient 4, the general nature of the acute health event, directions for providing care to patient 4, such as directions for providing cardiopulmonary resuscitation (CPR), a location of nearby medical equipment for treatment of patient 4, such as an automated external defibrillator (AED) 44 or life vest, and instructions for use of the equipment. In some examples, computing device(s) 12, loT device(s) 30, and/or computing device 42 may implement an event assistant configured to use natural language processing and context data to provide a conversational interface for bystander 42. The assistant may provide bystander 26 with directions for providing care to patient 4 and respond to queries from bystander 26 about how to provide care to patient 4.

[0053] In some examples, HMS 22 may mediate bi-directional audio (and in some cases video) communication between care providers 40 and patient 4 or bystander 26. Such communication may allow care providers 40 to evaluate the condition of patient 4, e.g., through communication with patient 4 or bystander 26, or through use of a camera or other sensors of the computing device or loT device, in advance of the time they will begin caring for the patient, which may improve the efficacy of care delivered to the patient. Such communication may also allow the care providers to instruct bystander 42 regarding first responder treatment of patient 4.

[0054] In some examples, HMS 22 may control dispatch of a drone 46 to environment 28, or a location near environment 28 or patient 4. Drone 46 may be a robot and/or unmanned aerial vehicle (UAV). Drone 46 may be equipped with a number of sensors and/or actuators to perform a number of operations. For example, drone 46 may include a camera or other sensors to navigate to its intended location, identify patient 4 and, in some cases, bystander 26, and to evaluate a condition of patient. In some examples, drone 46 may include user interface devices to communicate with patient 4 and/or bystander 26. In some examples, drone 46 may provide directions to bystander 26, to the location of patient 4 and regarding how to provide first responder care, such as CPR, to patient 4. In some examples, drone 46 may carry medical equipment, e.g., AED 44, and/or medication to the location of patient 4.

[0055] Any of IMD 10, computing device(s) 12, loT device(s) 30, computing device(s) 38 and 42, AED 44, drone 46, or HMS 22 may, individually or in any combination, perform the operations described herein for detection of acute health events, such as SCA, by applying rules, which may include one or more machine learning models, to patient parameter data to detect acute health events. For example, one of these devices, or more than one of them in cooperation, may apply a first set of rules to patient parameter data for a first determination of whether an acute health event is detected and, based on whether one or more context criteria associated with the first determination are satisfied, determine whether to apply a second set of rules to patient parameter data to determine whether the acute health event is detected.

[0056] FIG. 2 is a block diagram illustrating an example configuration of IMD 10 of FIG.

1. As shown in FIG. 2, IMD 10 includes processing circuitry 50, memory 52, sensing circuitry 54 coupled to electrodes 56A and 56B (hereinafter, “electrodes 56”) and one or more sensor(s) 58, and communication circuitry 60.

[0057] Processing circuitry 50 may include fixed function circuitry and/or programmable processing circuitry. Processing circuitry 50 may include any one or more of 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 to processing circuitry 50 herein may be embodied as 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 various functions attributed herein to IMD 10 and processing circuitry 50. Memory 53 may include any volatile, non-volatile, magnetic, optical, or electrical media, such as a random-access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), electrically- erasable programmable ROM (EEPROM), flash memory, or any other digital media.

[0058] Sensing circuitry 54 may monitor signals from electrodes 56 in order to, for example, monitor electrical activity of a heart of patient 4 and produce ECG data for patient 4. In some examples, processing circuitry 50 may identify features of the sensed ECG, such as heart rate, heart rate variability, T-wave altemans, intra-beat intervals (e.g., QT intervals), and/or ECG morphologic features, to detect an episode of cardiac arrhythmia of patient 4. Example Processing circuitry 50 may store the digitized ECG and features of the ECG used to detect the arrhythmia episode in memory 52 as episode data for the detected arrhythmia episode.

[0059] In some examples, sensing circuitry 54 measures impedance, e.g., of tissue proximate to IMD 10, via electrodes 56. The measured impedance may vary based on respiration, cardiac pulse or flow, and a degree of perfusion or edema. Processing circuitry 50 may determine physiological data relating to respiration, cardiac pulse or flow, perfusion, and/or edema based on the measured impedance.

[0060] In some examples, IMD 10 includes one or more sensors 58, such as one or more accelerometers, gyroscopes, microphones, optical sensors, temperature sensors, pressure sensors, and/or chemical sensors. In some examples, sensing circuitry 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 circuitry 54 and/or processing circuitry 50 may include a rectifier, filter and/or amplifier, a sense amplifier, comparator, and/or analog-to-digital converter. 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. Patient parameters determined from signals from sensors 58 may include oxygen saturation, glucose level, stress hormone level, heart sounds, body motion, body posture, or blood pressure.

[0061] Memory 52 may store applications 70 executable by processing circuitry 50, and data 80. Applications 70 may include an acute health event surveillance application 72. Processing circuitry 50 may execute event surveillance application 72 to detect an acute health event of patient 4 based on combination of one or more of the types of physiological data described herein, which may be stored as sensed data 82. In some examples, sensed data 82 may additionally include patient parameter data sensed by other devices, e.g., computing device(s) 12 or loT device(s) 30 and received via communication circuitry 60. Event surveillance application 72 may be configured with a rules engine 74. Rules 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, e.g., may include one or more machine learning models.

[0062] As examples, event surveillance application 72 may detect SCA, a ventricular fibrillation, a ventricular tachycardia, supra-ventricular tachycardia (e.g., conducted atrial fibrillation), ventricular asystole, or a myocardial infarction based on an ECG and/or other patient parameter data indicating the electrical or mechanical activity of the heart of patient 4. In some examples, event surveillance application 72 may detect stroke based on such cardiac activity data. In some examples, sensing circuitry 54 may detect brain activity data, e.g., an electroencephalogram (EEG) via electrodes 56, and event surveillance application 72 may detect stroke or a seizure based on the brain activity alone, or in combination with cardiac activity data or other physiological data. In some examples, event surveillance application 72 detects whether the patient has fallen based on data from an accelerometer alone, or in combination with other physiological data. When event surveillance application 72 detects an acute health event, event surveillance application 72 may store the sensed data 82 that lead to the detection (and in some cases a window of data preceding and/or following the detection) as event data 86, also referred to herein as episode data.

[0063] In some examples, in response to detection of an acute health event, processing circuitry 50 transmits, via communication circuitry 60, event data 86 for the event to computing device(s) 12 (FIG. 1). This transmission may be included in a message indicating the acute health event, as described herein. Transmission of the message may occur on an ad hoc basis and as quickly as possible. Communication circuitry 60 may include any suitable hardware, firmware, software, or any combination thereof for wirelessly communicating with another device, such as computing devices 12 and/or loT devices 30.

[0064] FIG. 3 is a block diagram illustrating an example configuration of a computing device 12 of patient 4, which may correspond to either (or both operating in coordination) of computing devices 12A and 12B illustrated in FIG. 1. In some examples, computing device 12 takes the form of a smartphone, a laptop, a tablet computer, a personal digital assistant (PDA), a smartwatch or other wearable computing device. In some examples, loT devices 30, computing devices 38 and 42, AED 44, and/or drone 46 may be configured similarly to the configuration of computing device 12 illustrated in FIG. 3. [0065] As shown in the example of FIG. 3, computing device 12 may be logically divided into user space 102, kernel space 104, and hardware 106. Hardware 106 may include one or more hardware components that provide an operating environment for components executing in user space 102 and kernel space 104. User space 102 and kernel space 104 may represent different sections or segmentations of memory, where kernel space 104 provides higher privileges to processes and threads than user space 102. For instance, kernel space 104 may include operating system 120, which operates with higher privileges than components executing in user space 102.

[0066] As shown in FIG. 3, 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 shown in FIG. 3 as a stand-alone device for purposes of example, computing device 12 may be any component or system that includes processing circuitry or other suitable computing environment for executing software instructions and, for example, need not necessarily include one or more elements shown in FIG. 3.

[0067] Processing circuitry 130 is configured to implement functionality and/or process 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 of components included in kernel space 104 and user space 102 to perform one or more operations in accordance with 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 circuitry.

[0068] Memory 132 may be configured to store information within computing device 12, for processing during operation of computing device 12. Memory 132, in some examples, is described as a computer-readable storage medium. In some examples, memory 132 includes a temporary memory or a volatile memory. Examples of volatile memories include random access memories (RAM), dynamic random access memories (DRAM), static random access memories (SRAM), and other forms of volatile memories known in the art. Memory 132, in some examples, also includes one or more memories configured for long-term storage of information, e.g., including non-volatile storage elements. Examples of such non-volatile storage elements include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In some examples, memory 132 includes cloud- associated storage. [0069] One or more input devices 134 of computing device 12 may receive input, e.g., from patient 4 or another user. Examples of input are tactile, audio, kinetic, and optical input. Input devices 134 may include, as examples, a mouse, keyboard, voice responsive system, camera, buttons, control pad, microphone, presence -sensitive or touch-sensitive component (e.g., screen), or any other device for detecting input from a user or a machine.

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

[0071] One or more sensors 138 of computing device 12 may sense physiological parameters or signals of patient 4. Sensor(s) 138 may include electrodes, accelerometers (e.g., 3-axis accelerometers), an optical sensor, impedance sensors, temperature sensors, pressure sensors, heart sound sensors (e.g., microphones), and other sensors, and sensing circuitry (e.g., including an ADC), similar to those described above with respect to IMD 10 and FIG. 2.

[0072] Communication circuitry 140 of computing device 12 may communicate with other devices by transmitting and receiving data. 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, communication circuitry 140 may include a radio transceiver configured for communication according to standards or protocols, such as 3G, 4G, 5G, WiFi (e.g., 802.11 or 802.15 ZigBee), Bluetooth®, or Bluetooth® Low Energy (BLE).

[0073] As shown in FIG. 3, health monitoring application 150 executes in user space 102 of computing device 12. Health monitoring application 150 may be logically divided into presentation layer 152, application layer 154, and data layer 156. Presentation layer 152 may include a user interface (UI) component 160, which generates and renders user interfaces of health monitoring application 150.

[0074] Application layer 154 may include, but is not limited to, an event engine 170, rules engine 172, rules configuration component 174, event assistant 176, and location service 178. Event engine 172 may be responsive to receipt of an alert transmission from IMD 10 indicating that IMD 10 detected an acute health event. Event engine 172 may control performance of any of the operations in response to detection of an acute health event ascribed herein to computing device 12, such as activating an alarm, transmitting alert messages to HMS 22, controlling loT devices 30, and analyzing data to confirm or override the detection of the acute health event by IMD 10.

[0075] Rules engine 174 analyzes sensed data 190, and in some examples, patient input 192 and/or EHR data 194, to determine whether there is a sufficient likelihood that patient 4 is experiencing the acute health event detected by IMD 10. Sensed data 190 may include data received from IMD 10 as part of the alert transmission, additional data transmitted from IMD 10, e.g., in “real-time,” and physiological and other data related to the condition of patient 4 collected by, for example, computing device(s) 12 and/or loT devices 30. As examples sensed data 190 from computing device(s) 12 may include one or more of: activity levels, walking/running distance, resting energy, active energy, exercise minutes, quantifications of standing, body mass, body mass index, heart rate, low, high, 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 volume of oxygen, blood glucose, peripheral perfusion, and sleep patterns.

[0076] Patient input 192 may include responses to queries posed by health monitoring application 150 regarding the condition of patient 4, input by patient 4 or another user, such as bystander 26. The queries and responses may occur responsive to the detection of the event by IMD 10, or may have occurred prior to the detection, e.g., as part long-term monitoring of the health of patient 4. User recorded health data may include one or more of: exercise and activity data, sleep data, symptom data, medical history data, quality of life data, nutrition data, medication taking or compliance data, allergy data, demographic data, weight, and height. EHR data 194 may include any of the information regarding the historical condition or treatments of patient 4 described above. EHR data 194 may relate to history of SCA, tachyarrhythmia, myocardial infarction, stroke, seizure, one or more disease states, such as status of heart failure chronic obstructive pulmonary disease (COPD), renal dysfunction, or hypertension, aspects of disease state, such as ECG characteristics, cardiac ischemia, oxygen saturation, lung fluid, activity, or metabolite level, genetic conditions, congenital anomalies, history of procedures, such as ablation or cardioversion, and healthcare utilization. EHR data 194 may also include cardiac indicators, such as ejection fraction and left-ventricular wall thickness. EHR data 194 may also include demographic and other information of patient 4, such as age, gender, race, height, weight, and BMI.

[0077] Rules engine 172 may apply rules 196 to the data. Rules 196 may include one or more models, algorithms, decision trees, and/or thresholds. In some cases, rules 196 may be developed based on machine learning, e.g., may include one or more machine learning models. In some examples, rules 196 and the operation of rules engine 172 may provide a more complex analysis the patient parameter data, e.g., the data received from IMD 10, than is provided by rules engine 74 and rules 84. In examples in which rules 196 include one or more machine learning models, rules engine 172 may apply feature vectors derived from the data to the model(s).

[0078] Rules configuration component 174 may be configured to modify rules 196 (and in some examples rules 84) based on feedback indicating whether the detections and confirmations of acute health events by IMD 10 and computing device 12 were accurate. The feedback may be received from patient 4, or from care providers 40 and/or EHR 24 via HMS 22. In some examples, rules configuration component 174 may utilize the data sets from true and false detections and confirmations for supervised machine learning to further train models included as part of rules 196.

[0079] Rules configuration component 174, or another component executed by processing circuitry of system 2, may select a configuration of rules 196 based on etiological data for patient, e.g., any combination of one or more of the examples of sensed data 190, patient input 192, and EHR data 194 discussed above. In some examples, different sets of rules 196 tailored to different cohorts of patients may be available for selection for patient 4 based on such etiological data.

[0080] As discussed above, event assistant 176 may provide a conversational interface for patient 4 and/or bystander 26 to exchange information with computing device 12. Event assistant 176 may query the user regarding the condition of patient 4 in response to receiving the alert message from IMD 10. Responses from the user may be included as patient input 192. Event assistant 176 may use natural language processing and context data to interpret utterances by the user. In some examples, in addition to receiving responses to queries posed by the assistant, event assistant 176 may be configured to respond to queries posed by the user. In some examples, event assistant 176 may provide directions to and respond to queries regarding treatment of patient 4 from patient 4 or bystander 26.

[0081] Location service 178 may determine the location of computing device 12 and, thereby, the presumed location of patient 4. Location service 178 may use global position system (GPS) data, multilateration, and/or any other known techniques for locating computing devices.

[0082] FIG. 4 is a block diagram illustrating an operating perspective of HMS 22. HMS 22 may be implemented in a computing system 20, which may include hardware components such as those of computing device 12, e.g., processing circuitry, memory, and communication circuitry, embodied in one or more physical devices. FIG. 4 provides an operating perspective of HMS 22 when hosted as a cloud-based platform. In the example of FIG. 4, components of HMS 22 are arranged according to multiple logical layers that implement the techniques of this disclosure. Each layer may be implemented by one or more modules comprised of hardware, software, or a combination of hardware and software.

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

[0084] As shown in FIG. 4, HMS 22 also includes an application layer 202 that represents a collection of services 210 for implementing the functionality ascribed to HMS herein. Application layer 202 receives information from client applications, e.g., an alert of an acute health event from a computing device 12 or loT device 30, and further processes the information according to one or more of the services 210 to respond to the information. 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 servers provide runtime environments for execution of services 210. In some examples, the functionality interface layer 200 as described above and the functionality of application layer 202 may be implemented at the same server. Services 210 may communicate via a logical service bus 212. Service bus 212 generally represents a logical interconnection or set of interfaces that allows different services 210 to send messages to other services, such as by a publish/subscription communication model.

[0085] Data layer 204 of HMS 22 provides persistence for information in PPEMS 6 using one or more data repositories 220. A data repository 220, generally, may 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, multi-dimensional databases, maps, and hash tables, to name only a few examples.

[0086] As shown in FIG. 4, each of services 230-238 is implemented in a modular form within HMS 22. Although shown as separate modules 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-238 may be implemented in software, hardware, or a combination of hardware and software. Moreover, services 230-238 may be implemented as standalone devices, separate virtual machines or containers, processes, threads or software instructions generally for execution on one or more physical processors.

[0087] Event processor service 230 may be responsive to receipt of an alert transmission from computing device(s) 12 and/or loT device(s) 30 indicating that IMD 10 detected an acute health event of patient and, in some examples, that the transmitting device confirmed the detection. Event processor service 230 may initiate performance of any of the operations in response to detection of an acute health event ascribed herein to HMS 22, such as communicating with patient 4, bystander 26, and care providers 40, activating drone 46 and, in some cases, analyzing data to confirm or override the detection of the acute health event by IMD 10.

[0088] Record management service 238 may store the patient data included in a received alert message within event records 252. Alert service 232 may package the some or all of the data from the event record, in some cases with additional information as described herein, into one more alert messages for transmission to bystander 26 and/or care providers 40. Care giver data 256 may store data used by alert service 232 to identify to whom to send alerts based on locations of potential bystanders 26 and care givers 40 relative to a location of patient 4 and/or applicability of the care provided by care givers 40 to the acute health event experienced by patient 4.

[0089] In examples in which HMS 22 performs an analysis to confirm or override the detection of the acute health event by IMD 10, event processor service 230 may apply one or more rules 250 to the data received in the alert message, e.g., to feature vectors derived by event processor service 230 from the data, or to raw data, e.g., digitized ECG or other waveforms. Rules 250 may include one or more models, algorithms, decision trees, and/or thresholds, which may be developed by rules configuration service 234 based on machine learning. Example machine learning techniques that may be employed to generate rules 250 (as well as rules 84 and/or 196) can 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, instance-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 Networks, Convolution Neural Networks (CNN), Long Short Term Networks (LSTM), the Apriori algorithm, K-Means Clustering, k-Nearest Neighbour (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).

[0090] In some examples, in addition to rules used by HMS 22 to confirm acute health event detection, (or in examples in which HMS 22 does not confirm event detection) rules 250 maintained by HMS 22 may include rules 196 utilized by computing devices 12 and rules 84 used by IMD 10. In such examples, rules configuration service 250 may be configured to develop and maintain rules 196 and rules 84. Rules configuration service 234 may be configured to develop different sets of rules 84, 196, 250, e.g., different machine learning models, for different cohorts of patients. Rules configuration service 234 may be configured to modify these rules based on event feedback data 254 that indicates whether the detections and confirmations of acute health events by IMD 10, computing device 12, and/or HMS 22 were accurate. Event feedback 254 may be received from patient 4, e.g., via computing device(s) 12, or from care providers 40 and/or EHR 24. In some examples, rules configuration service 234 may utilize event records from true and false detections (as indicated by event feedback data 254) and confirmations for supervised machine learning to further train models included as part of rules 250.

[0091] As illustrated in the example of FIG. 4, services 210 may also include an assistant configuration service 236 for configuring and interacting with event assistant 176 implemented in computing device 12 or other computing devices. For example, assistant configuration service 236 may provide event assistants updates to their natural language processing and context analyses to improve their operation over time. In some examples, assistant configuration service 236 may apply machine learning techniques to analyze sensed data and event assistant interactions stored in event records 252, as well as the ultimate disposition of the event, e.g., indicated by EHR 24, to modify the operation of event assistants, e.g., for patient 4, a class of patients, all patients, or for particular users or devices, e.g., care givers, bystanders, etc.

[0092] FIG. 5 is a flow diagram illustrating an example operation for applying rules to patient parameter data to determine whether an acute health event is detected. The example operation of FIG. 5 may be performed by processing circuitry of any one of IMD 10, computing device(s) 12, 38, 42, loT devices 30, AED 44, drone 46, or HMS 22 (e.g., by processing circuitry 50 or 130 implementing rules engine 74 or 172 and applying rules 84 or 196), or by processing circuitry of two or more of these devices respectively performing portions of the example operation.

[0093] According to the example of FIG. 5, the processing circuitry applies a first set of rules to first patient parameter data for a first determination of whether an acute health event, e.g., SCA, is detected (300). The processing circuitry determines whether one or more context criteria associated with the first determination are satisfied (302). If the one or more context criteria are not satisfied (NO of 302), the processing circuitry may determine whether the acute health event is detected based on the first determination (304). If the acute health event is detected (YES of 304), the processing circuitry may generate an alert, e.g., a message to another device and/or a user-perceptible alert as described herein (306). If the acute health event is not detected (NO of 304) or the alert has been generated, the example operation of FIG. 5 may end. If the one or more context criteria are satisfied (YES of 302), the processing circuitry may apply a second set of rules to second patient parameter data for a second determination of whether the acute health event, e.g., SCA, is detected (308), and determine whether the acute health event is detected based on the second determination (304).

[0094] The first and second sets of rules are different in at least one aspect. In some examples, the second set of rules comprises at least one machine learning model. In some examples, both the first and second sets of rules comprise at least one machine learning model.

[0095] In some examples, the processing circuitry determines a risk score of the acute health event, e.g., SCA, based on the application of the first set of rules to the first patient parameter data, and compares the risk score to a threshold to determine whether the one or more context criteria are satisfied. In some examples, the context indicating that the second set of rules should be applied to the second patient parameter data may be that the risk score produced by the first determination does not meet a threshold indicating a sufficient certainty that the acute health event is occurring. The risk score may be a percentage likelihood of the acute health event.

[0096] In some examples, the processing circuitry determines a confidence level of the first determination of whether the acute health event is detected and compares the confidence level to a threshold. In some examples, the one or more context criteria may be satisfied where the first determination does not have a threshold degree of confidence, or where the first determination is associated with a likelihood of being a false positive that exceeds a threshold. In such examples, application of the second set of rules to the second patient parameter data may act as a “tie-breaker” when the first determination is not confident. In some examples, the processing circuitry determines that the one or more context criteria are satisfied when input from a user, e.g., the patient, contradicts the first determination (e.g., that the acute health event was detected or not detected), indicating that the likelihood that the first determination is false may be relatively high.

[0097] The processing circuitry may determine a confidence level of the first determination of whether the acute health event is present using a variety of techniques. For example, the application of the first set of rules to the first patient parameter data may produce a level of confidence through its output, e.g., a risk score. In such examples, a higher output indicating a higher likelihood of the acute health event may indicate a higher level of confidence. Examples of rules that may produce such outputs include machine learning models and time-domain signal processing algorithms.

[0098] In some examples, the processing circuitry may determine a noise level of one or more signals from which the first patient parameter data is determined. In such examples, the processing circuitry may determine a confidence level of the first determination of whether the acute health event is present based on a noise level. In general, confidence level and noise level may be inversely related. In some examples, the processing circuitry may determine the confidence level based on health record data for patient 4. For example, if a clinician has indicated in a health record or via programming IMD 10 that patient 4 has experienced a myocardial infarction or has heart failure, confidence levels may be increased and/or thresholds included in the rules applied to the first patient parameter data may be lowered.

[0099] In some examples, a context criterion may be satisfied when a component of system 2, e.g., IMD 10 or computing devices 12, has sufficient power to enable the application of the second set of rules to the second patient parameter data. In some examples, to determine whether the one or more context criteria are satisfied, the processing may determine a power level of system 2, e.g., of the relevant device, and compare the power level threshold. In some examples, the second patient parameter data includes data of at least one patient parameter that is not included in the first patient parameter data. In some examples, the processing circuitry activates a sensor to sense this patient parameter, e.g., when the device including the sensor has sufficient power for the measurement.

[0100] In some examples, the first patient parameter data and the second patient parameter data are both sensed by an implantable medical device. In some examples, the at least one patient parameter that is included in the second patient parameter data but not included in the first patient parameter data is sensed by an external device. In some examples, processing circuitry 50 of IMD 10 or processing circuitry 130 of computing device(s) 12 (or loT devices 30 or the other devices discussed herein) performs each of suboperations 300-308. In other examples, processing circuitry 50 of IMD 10 performs the first determination of whether the acute health event, e.g., SCA, is detected (300), and processing circuitry 130 of computing device(s) 12 (or loT devices 30 or the other devices discussed herein) performs each of sub-operations 302-308.

[0101] In some examples, the first patient parameter data includes at least one patient parameter determined from ECG data, and the at least one patient parameter comprises a patient parameter determined from at least one of heart sounds of the patient, an impedance of the patient, motion of the patient (e.g., whether a fall occurred or is suspected), respiration of the patient, posture of the patient, blood pressure of the patient, a chemical detected in the patient, or an optical signal from the patient. In some examples, the first patient parameter data and second patient parameter data may be determined using different combinations of sensors, e.g., internal and/or external sensors. The first and second determinations may be considered different tiers, with the second determination utilizing additional sensor(s), data, and/or power if the context suggests it would be desirable to supplement the first determination.

[0102] In some examples, the processing circuitry selects at least one of the second set of rules or the parameters used for the second patient parameter data based on at least one of user (e.g., patient or care giver or bystander) input or medical record information of the patient. In some examples, the user input and/or medical history information may include information entered by a clinician when programming IMD 10. For example, the processing circuitry may select at least one of the second set of rules or the parameters used for the second patient parameter data based on user input or medical record information indicating a particular symptom or condition of the patient. In some examples, the first patient parameter data comprises data for a first set of patient parameters, and the processing circuitry may select at least one of the second set of rules or a second patient parameter for the second patient parameter data based on the level. A level for a particular parameter that is clinically significant but contrary to the first determination (either a detection or non-detection), may suggest that the second determination should be performed, and should be performed with a particular parallel (but different) or orthogonal patient parameter to resolve the uncertainty about whether the acute health event is detected. [0103] In some examples, the first patient parameter data includes at least one patient parameter determined from ECG data of the patient, and the second patient parameter data comprises at least one of a morphological change or a frequency shift of the ECG data over time. The processing circuitry may analyze ECG data for timing or morphology changes. For example, morphological or frequency changes as a ventricular fibrillation persists may indicate an increase lethality of the ventricular fibrillation. In some examples, the rules applied processing circuitry may determine a higher likelihood of the acute health event, e.g., lethal ventricular fibrillation or SCA, the presence of such morphological or frequency shifts. [0104] The example operation of FIG. 5 may result in a hierarchy of rules or even sensor measurements. In some examples, one or more sensors may be activated in certain contexts, and may be inactive for first determinations of whether the acute health event is detected, e.g., to conserve power of IMD 10. For example, if in a first determination ECG data indicates ventricular fibrillation and other sensor data indicates no pulse and no heart sounds, there may be no need for the second determination. But if those levels of evidence are not high, e.g., not sure if it definitely ventricular fibrillation, there might be faint heart sounds, faint pulses, a fall, or a gait change, then a second determination could be employed.

[0105] Further, the rules and sensors used in either or both of the first and second determinations can be configured/personalized for each patient based on their medical history from EMR or their history of previous events or by their physicians/caregivers depending on the situation. For example, if a caregiver has to leave town for few days, the processing circuitry could configure the rules to be satisfied by lower levels of evidence, e.g., automatically, which may advantageously tailor the monitoring provided by system 2 to the context of patient 4 and care givers of the patient.

[0106] FIG. 6 is a flow diagram illustrating another example operation for applying rules to patient parameter data to determine whether an acute health event is detected. The example operation of FIG. 6 may be performed by processing circuitry of any one of IMD 10, computing device(s) 12, 38, 42, loT devices 30, AED 44, drone 46, or HMS 22 (e.g., by processing circuitry 50 or 130 implementing rules engine 74 or 172 and applying rules 84 or 196), or by processing circuitry of two or more of these devices respectively performing portions of the example operation.

[0107] According to the example of FIG. 6, the processing circuitry applies a set of rules to patient parameter data to determine whether an acute health event, e.g., SCA, is detected (320). The processing circuitry determines whether one or more context criteria associated with the determination are satisfied (322). If the one or more context criteria are not satisfied (NO of 322), the processing circuitry may determine whether the acute health event is detected based on the determination (324). If the acute health event is detected (YES of 324), the processing circuitry may generate an alert, e.g., a message to another device and/or a user-perceptible alert as described herein (326). If the acute health event is not detected (NO of 324) or the alert has been generated, the example operation of FIG. 6 may end. If the one or more context criteria are satisfied (YES of 322), the processing circuitry may apply modify the set of rules (328), apply second patient parameter data to the second set of rules (330), and determine whether the acute health event is detected based on the application of the second patient parameter data to the second set of rules (324).

[0108] The processing circuitry may determine whether the one or more context criteria are satisfied in the manner described with respect to FIG. 5. In some examples, the first and second patient parameter data may be determined from the same patient parameters or (with respect to at least one parameter) different patient parameters. In some examples, the first patient parameter data and the second patient parameter data include at least one common patient parameter, and the processing circuitry may change a mode sensing for the common patient parameter between the first patient parameter data and the second patient parameter data in response to satisfaction of the one or more context criteria. For example, the processing circuitry may change a sampling frequency for the common patient parameter. [0109] In some examples in which IMD 10 senses patient parameters used to determine the first patient parameter data, the processing circuitry may determine that a context criterion is satisfied by detecting that IMD 10 has flipped or otherwise migrated within patient 4. Such migration may lead to significant changes in patient parameter data, e.g., ECG data, impedance data, or heart sound data. Changing a mode employed by IMD 10 to sense one or more patient parameters or changing rules to account for changes in patient parameter data resulting from device migration, may help ameliorate the device migration and maintain effective acute health event detection. In addition to the mode of sensing and/or rules, the processing circuity may adjust other aspects of system, such mode of wireless communication between the IMD and other devices. Techniques for detecting and mitigating migration of IMD 10 are described in commonly-assigned U.S. Patent Application No.

17/101,945, filed November 23, 2020 by Anderson et al., titled “DETECTION AND MITIGATION OF INACCURATE SENSING BY AN IMPLANTED SENSOR OF A MEDICAL SYSTEM,” which is incorporated herein by reference in its entirety.

[0110] In some examples, the processing circuitry determines that the one or more context criteria are satisfied when the processing circuitry determines that the acute health event, e.g., ventricular tachyarrhythmia or SCA, is detected, but the patient or another user cancels the alarm or otherwise provides user input contradicting the determination. In such examples, the processing circuitry may modify one or both of the sensed patient parameters or the rules applied to the patient parameter data.

[0111] For example, the patient may have tolerated a rapid ventricular tachycardia that lasted for a sustained period (e.g., a programmed 10 or 20 seconds), but could experience another arrhythmia, e.g., syncope, soon even though the patient believes they are OK. The modification may include adapting the rules based on the rhythm. Sometimes a long duration episode accelerates to ventricular fibrillation or more rapid ventricular tachycardia.

Sometimes ventricular fibrillation slows down. In either case, the modification could include changing a heart rate threshold, e.g., applying hysteresis to the heart rate threshold. In some examples, ventricular fibrillation becomes difficult to sense. In such examples, the modification may include changing a ventricular depolarization detection threshold to allow more undersensing of depolarizations.

[0112] In some examples, the processing circuitry determines that the one or more context criteria are satisfied based on a recent history of high arrhythmia burden. Some patients have electrical storms. Their electrolytes may be imbalanced, and they may experience a cluster of ventricular arrhythmias, but the patient parameter data may not satisfy the rules for detection of the acute health event. In such cases, the processing circuitry may adapt a tachyarrhythmia duration the threshold, may alert patient and caregivers and inform them to seek care ASAP, and/or may alert a clinician and send patient parameter data, e.g., ECG data, so the clinician can review.

[0113] FIG. 7 is a flow diagram illustrating an example operation for configuring rules applied to patient parameter data to determine whether an acute health event is detected for a patient. The example operation of FIG. 7 may be performed by processing circuitry that implements HMS 22, e.g., that implements rules configuration service 234. In some examples, the operation of FIG. 7 may be performed by processing circuitry of any one of IMD 10, computing device(s) 12, 38, 42, loT devices 30, AED 44, drone 46, or HMS 22, e.g., implementing a rules configuration module, or by processing circuitry of two or more of these devices respectively performing portions of the example operation.

[0114] According to the example operation of FIG. 7, the processing circuitry determines whether an acute health event, e.g., SCA, is detected (340). The processing circuitry receives feedback for the event (342). The feedback indicates whether the detection a true or false positive, or the non-detection is a true or false negative. The processing circuitry may receive the feedback from patient 4, care giver 40, bystander 26, or EHR 24. The processing circuity updates rules (e.g., rules 84, rules 196, and/or rules 250) based on the feedback and event data, e.g., event data 86 or event records 252. In some examples, uses the event data as a training set for one or more machine learning models based on the feedback.

[0115] Through predictive and “self-learning” techniques, the operation of a system used to provide an alert for SCA can be improved. Time-to-treatment (either CPR or a shock from AED 44) may be improved by providing a timely alert, either to bystanders 26 or the EMS care givers 40. The information used to improve the performance could include physiologic sensor data that may indicate an SCA event is likely (QT prolongation, T-wave altemans, changes in respiration rate or thoracic impedance, history of PVCs or non-sustained VT, reduction in 02 saturation and/or perfusion, etc.). The information used to improve the performance could include information indicating whether the prior SCA event was alerted appropriately and accurately, clinical or physiologic characteristics of the patient (disease state, weight, gender, etc.), data from EHR 24, and data input from the patient (e.g., symptom logging, confirmation that he/she is OK and not suffering from SCA, etc.).

[0116] Implementing the example operation of FIG. 7, the processing circuitry may personalize the rules for patient 4 over time. If patient 4 has a lot of false positives, the example operation of FIG. 7 may modify the rules to be less sensitive and, conversely, if the patient 4 has a lot of false negatives may modify the rules to be more sensitive. In some examples, the processing circuitry may use the feedback and event data to update rules, e.g., machine learning models, for other patients, such as all patients whose IMDs are served by EMS 22, or a particular population or cohort of patients. In some examples, the processing circuitry may use data from a number of sources (e.g., computing devices 12, loT devices 30, AED 44, or drone 46) to modify the rules or the collection of patient parameter data. Data used by processing circuitry to update rules may include data indicating a duration of CPR, e.g., input by a user, or data collected using an accelerometer, speaker, light detector, or camera on a computing device or loT device.

[0117] FIG. 8 is a flow diagram illustrating another example operation for configuring rules applied to patient parameter data to determine whether an acute health event is detected for a patient. The example operation of FIG. 7 may be performed by processing circuitry that implements HMS 22, e.g., that implements rules configuration service 234. In some examples, the operation of FIG. 8 may be performed by processing circuitry of any one of IMD 10, computing device(s) 12, 38, 42, loT devices 30, AED 44, drone 46, or HMS 22, e.g., implementing a rules configuration module, or by processing circuitry of two or more of these devices respectively performing portions of the example operation.

[0118] According to the example operation of FIG. 8, the processing circuitry determines an etiology or risk stratification of patient 4 (360). The processing circuitry selects a set of rules (e.g., a set of rules 84, rules 196, and/or rules 250), which may be a first set of rules and/or a second set of rules, for acute health event, e.g., SCA, detection for patient 4 based on the patient etiology (362). In some examples, rules 250 include different sets of rules for different patient cohorts having different etiologies, and processing circuitry may select different rule sets to implement as rules 84 in IMD 10 and rules 196 in computing device(s) 12 for a given patient based on the etiology of that patient. The processing circuitry may apply the selected set of rules to patient parameter data to determine whether the acute health event is detected using any of the techniques described herein (364).

[0119] Detection of SCA can be achieved by looking at a number of possible markers that occur prior to and during the event. The best markers to detect an impending or ongoing event are likely to be different based on an etiology of the patient. An SCA detection algorithm which uses a generic algorithm designed for a broad population may not achieve satisfactory sensitivity and specificity. The etiology of patient 4 may include baseline characteristics, medical history, or disease state. The etiology of patient 4 may include any EHR data 194 described herein, as well as patient activity level or metabolite level. With such possible inputs, the rules could look for certain markers to exhibit certain trends or threshold crossings to detect an impending or ongoing acute health event, e.g., SCA.

[0120] In some examples, selection of a set of rules may include modification of a universal rule set to turn certain rules (or markers of the acute health event) on or off or change the weight of certain rules or markers. In some examples, a family of devices could be designed such that individual models have sensors or calculation for only a limited set of inputs motivated by a need to reduce manufacturing costs or energy consumption.

[0121] While SCA is typically detected by heart rate/rhythm, rules related to other patient parameter data may be set to a heightened alert-based patient etiology. For example, a patient with prior myocardial infarction may have rules that weigh ischemia factors such as ST segment elevation more heavily than for patients lacking this etiology. As another example, a patient with long QT syndrome may have rules that more heavily weight QT interval and activity. As another example, rules for a heart failure patient may have rules that apply greater weight to patient parameter data related to lung fluid and QRS duration. [0122] In some examples, processing circuitry of system 2 may use patient etiology to “personalize” other aspects of the operation of system 2 for patient 4 or a cohort including patient 4. For example, the processing circuitry may provide alerts and user interfaces that guide care givers 40, bystanders 26, patient 4, or others based on the etiology. The processing circuitry can provide patient-specific care recommendations (e.g., AED or potential drug therapy for prevention or therapy of SCA). The ability of the system to detect the acute health event with adequate sensitivity and specificity may, for example, guide an EMS care giver 40 to what they can expect when they arrive on the scene and how best to treat the presenting rhythm, e.g., is the patient hypoxic, hypovolemic, hypothermic, tension pneumothorax, cardiac tamponade (the H’s and T’s of Advanced Cardiac Life Support). The etiology may indicate of patient 4 is more at risk for pulseless electrical activity vs. ventricular fibrillation/ventricular tachycardia. The processing circuitry of system 2 may provide care givers information based on the etiology current patient parameter data of patient 4, such as recommendations to provide CPR or defibrillation, provide drugs, or induce hypothermia. The processing circuitry of system 2 may recommend patient-specific care actions based on the etiology, e.g., purchase an AED or Chest Compression System (LUCAS).

[0123] Although described primarily in the context of detection of SCA, system 2 may be used to detection any of a number of acute health events of patient 4. For example, system 2 may be used to detect stroke. Stroke can often present in the form of facial droop. This change in facial tone could be identified using facial image processing on a computing device 12, e.g., a smartphone, or loT 30. Such image processing could be a primary indicator of possible stroke or a part of a confirmation after another device indications changes related to stroke.

[0124] Some computing devices 12, e.g., smartphones, include facial processing for access, e.g., face ID, and are accessed in this manner frequently throughout the day. Processing circuitry, e.g., of the computing device, may analyze the facial images to detect subtle changes in facial tone overtime. The processing circuitry could detect possible stroke, and various devices of system 2 could provide alerts as described herein.

[0125] In some examples, in response to detection based on the camera images, the device could output a series of prompts (audible and/or visual) to access a current state of patient 4. Patient 4 could be prompted to repeat a phrase or answer audible questions to assess cognitive ability. The device could use additional motion processing to further verify the state of patient 4, e.g., using an accelerometer of computing device 12A and/or 12B. Changes in body motion and asymmetry, e.g., of the face and/or body motion, are indictive of stroke. In some examples, the device may ask patient 4 questions. Processing circuitry may analyze the response to detect speech difficulties associated with stroke. In some examples, the alert could include information on where the facial tone has changed, which could aid in diagnosis by guiding care givers 40 to possible primary locations for scans (ex: left side droop= right side clot).

[0126] As described herein, processing circuitry of one or more devices of system 2, e.g., IMD 10, edge devices such as computing devices 12 or loT devices 30, and/or HMS 22 (or other cloud services), may be configured to analyze episode data associated with an acute health event, such a ventricular tachyarrhythmia or SCA, detected by IMD 10. The episode data may include ECG and other physiological parameter data collected by IMD 10 for the event, e.g., leading up to, during, and/or after the event. As described herein, the analysis may include the application of a second set of rules (as opposed to a first set applied by IMD 10), e.g., a machine learning model or other artificial intelligence algorithm, decision trees, and/or thresholds, to the episode data and, in some cases, a variety of patient data collected by devices of system 2.

[0127] The initial detection of a ventricular tachyarrhythmia episode by IMD 10 may be based on a first set rules relating to rate and regularity of RR intervals as well as morphological features of the ECG, e.g., of the R-wave. These rules may lead to inappropriate detections due to oversensing R-waves. Further, true ventricular tachyarrhythmia can be of supraventricular origin, e.g., SVT, or ventricular origin such as VF and VT. VT may be monomorphic or polymorphic. In general, polymorphic VT (PVT) and VF are life threatening, while monomorphic VT (MVT) are life threatening if sustained for durations on the order of minutes, and SVTs are generally not life threatening unless sustained for greater than 1 hour. The techniques of this disclosure may include use of a second set of rules that includes machine learning models or other Al algorithms to improve accuracy of classification of these different forms of ventricular tachyarrhythmia that maybe detected by IMDs.

[0128] In some examples, the second set of rules may comprise an ensemble of deep learning neural networks configured to discriminate or classify these rhythms. Techniques for configuring an ensemble of deep learning neural networks for classifying cardiac rhythms are described in U.S. Provisional Application Serial No. 63/194,451, filed May 28, 2021, and titled “DYNAMIC AND MODULAR CARDIAC EVENT DETECTION,” the entire contents of which are incorporated herein by reference. In some examples, the second set of rules may comprise a single classifier that receives, as input, a raw ECG data or a specific feature derived from raw ECG data.

[0129] In some examples, an ensemble of neural networks may include CNNs and/or recurrent neural networks. One or more neural networks of the ensemble may be trained to discriminate or classify based on raw ECG data collected by IMD 10 as an input. One or more networks of the ensemble may be trained to discriminate or classify based on custom features determined by IMD 10 from the ECG or other signals sensed by IMD 10 or determined by the processing circuitry implementing the second set of rules (e.g., processing circuitry of any of, or any combination of, the devices of system 2). An ensemble of neural networks may improve sensitivity and specificity of the overall analysis by allowing for different inputs to have respective networks of different forms, e.g., one can use recurrent neural networks for one or more specific inputs and CNNs for one or more other inputs. In some examples, the output of each network may be concatenated and flattened, and then fed as input into the final stages of the ensemble network which may have fully connected layers and classification layers.

[0130] FIG. 9 is a block diagram illustrating an example of an ensemble 400 of neural networks configured to classify ventricular tachyarrhythmias. Processing circuitry, e.g., processing circuitry 130 of computing device 12 or loT device 30, may apply a plurality of inputs 402 to a plurality of neural networks 404 of ensemble 400. Inputs 402 include raw signal inputs 406A or other raw parameter data of patient 4, e.g., from IMD 10 or other devices as described herein, and inputs 406B comprising features derived from the raw data. Inputs 406A may include a raw ECG segment sensed by IMD 10 including a ventricular tachyarrhythmia onset detected by IMD 10 based on the ECG, and a raw ECG segment sensed by IMD 10 including a portion of the ECG by which IMD 10 determined the ventricular tachyarrhythmia was sustained.

[0131] Inputs 406B may include features derived from the raw ECG sensed by IMD 10 and data indicating timing of and intervals between R-waves detected by IMD 10 during, and in some cases before and/or after, an episode of ventricular tachyarrhythmia sensed by IMD 10. The features may include a sequence of R-R intervals during, and in some cases prior to, detection of the ventricular tachyarrhythmia by IMD 10, an overly of raw ECG data and R- sense timing information, autocorrelation, cross-correlation, and/or wavelet transformation of ECG signal data, a histogram of R-R intervals, and a temporal history of prior ventricular tachyarrhythmia episodes detected by IMD 10 and their adjudication by the processing circuitry applying the ensemble 400. Inputs 402 may also include any other sensed parameters of patient 4, e.g., sensed by IMD 10 or other devices as described above. In some examples, inputs 406B may include a feature determined by the processing circuitry based on a temporal history of other sensed parameters of patient 4.

[0132] In some examples, one or more inputs 402 or portions thereof may be fed into separate individual neural networks 404, which may include 1 or 2-dimensional CNNs, RNNs, or long short-term memory (LSTM) memory networks (which may be a type of RNN). The processing circuitry may flatten 408 and concatenate 410 the outputs from the plurality of neural networks to provide ensemble 400. The processing circuitry may apply the flattened and concatenated outputs to a fully connected layer 412, and the outputs of the fully connected layer to one or more SoftMax functions 414. The outputs of the one or more SoftMax functions 414 are probabilities 416, e.g., respective probabilities of different classifications of the data for the episode of ventricular tachyarrhythmia detected by IMD 10. In the example illustrated by FIG. 9, the classifications are different classifications are PVT, MVT, SVT, noise, and oversensing.

[0133] The processing circuitry, e.g., processing circuitry 130 of computing device 12 or loT device 30, may determine a classification of the episode based on probabilities 416. In this manner processing circuitry may confirm or overrule the detection of a ventricular tachyarrhythmia by IMD 10. Ensemble 400 may be an example of a second set of rules as described above.

[0134] In some examples, however, the processing circuitry may combine the raw signals and derived features in a 2D array format (to form an input ensemble) for a single CNN or other neural network. FIG. 10 is a block diagram illustrating an example of a single classifier 430 utilizing raw signals and derived features as inputs 432. Inputs 432 of FIG. 10 may be substantially similar to inputs 406B of FIG. 9.

[0135] The processing circuitry, e.g., processing circuitry 130 of computing device 12 or loT device 30, may concatenate 434 inputs 432. In the example of FIG. 10, the processing circuitry may concatenate 434 inputs 432 to form a concatenated 2D array 436 of input values to be applied to a neural network 438 including one or more of an LSTM/RNN, rectifier function, and/or multiplex pooling layers. The processing circuitry may concatenate 440 the output of neural network 438 for application to a fully connected layer 442 and SoftMax function 444 to produce probabilities 446 in the manner described above with respect to FIG. 9. Classifier 430 may be an example of a second set of rules as described above. [0136] In some examples, the processing circuitry uses different segments of ECG, such as a segment from period of time at onset of arrhythmia, another segment when the episode reaches sustained detection, and multiple ongoing segments thereafter, as respective inputs to the one or more neural networks, e.g., of ensemble classifier 400 or classifier 430. In some examples, the processing circuitry uses features derived from different segments of the ECG in the episode data as respective inputs to the one or more neural networks, such as RR intervals during the episode and prior to start of episode, RR interval stability or variability, or short term HRV prior to onset of the episode. In general, the segments may be timewise, e.g., respective periods of the ECG. The segments may be contiguous, separated by time, and/or overlapping.

[0137] In some examples, the processing circuitry uses data from other sensors, e.g., of IMD 10, computing devices 12, and/or loT devices 30. The additional data may include patient motion (e.g., gait) or posture, e.g., from an accelerometer, which may indicate activity level during arrhythmia or gait/posture during arrhythmia or if patient 4 had a fall during the detected episode. In some examples, other data, e.g., historical data, may be obtained from IMD 10, computing devices 12, HMS 22, and/or EHR 24. The other data may include, as examples, ventricular tachyarrhythmia episode detection history, Al based episode classification history, AF burden history, or clinical history. The processing circuitry may derive features from sensor signals using signal processing techniques such as autocorrelation, Short Time Fourier transforms, Continuous Wavelet transforms, principal component analysis, independent component analysis, etc.

[0138] In some examples, the processing circuitry may use a staged approach to classify an episode detected by IMD 10. FIG. 11 is a block diagram illustrating a staged classifier 460 for classifying a ventricular tachyarrhythmia episode. For example, the processing circuitry, e.g., processing circuitry 130 of computing device 12 or loT device 30, may first apply a 5-class classifier 462, e.g., similar to ensemble classifier 400 or classifier 430, and the most dominant classes, such as inappropriate detections, noise, and oversensing episodes, are removed. The processing circuitry then classifies episodes that are classified as appropriate tachycardia (PVT, MVT, and SVT) using a 3 -class classifier 464. Then the next dominant class (SVT) is removed. The processing circuitry then classifies the remainder episodes using a 2-class classifier 466 to classify PVT vs MVT episodes.

[0139] In some examples, the processing circuitry may discriminate SVT from other ventricular tachyarrhythmia classifications based on a comparison of ECG data for the episode to a historical ECG segment. The episode ECG data may be received from IMD 10 as described herein, and the historical ECG segment may be retrieved from HMS 22. The historical ECG segment may be from a previous transmission from IMD 10 to HMS 22, e.g., a daily transmission, such as the most recent transmission. The historical ECG segment may be a segment prior, e.g., most recently prior to a fast heart rate associated with the detected ventricular tachyarrhythmia, or a most recent periodically, e.g., every hour, collected ECG. The historical ECG segment may be a segment of normal sinus rhythm ECG collected when the device was not currently detecting any cardiac events nor arrhythmias, or may be a segment previously verified as SVT, e.g., based on a user or algorithmic analysis of the segment.

[0140] In such examples, the processing circuitry may apply a convolutional filter and/or bank of convolutional filters to the ECG data for an episode to discriminate SVT from other classifications. The processing circuitry may generate the convolutional filter based on the historical ECG segment, which may be about 8 seconds in length. The processing circuitry may generate the bank of convolutional filters based on a wavelet or other decomposition of the historical ECG segment. The processing circuitry may classify the episode as SVT based on a suprathreshold output of the convolutional filter(s). In some examples, an additional classifier may further classify SVT as one of sinus tachycardia, atrial arrhythmia, SVT with aberrancy, junctional rhythms, atrioventricular nodal reentry tachycardia, or others.

[0141] In some examples, the processing circuitry, e.g., processing circuitry 130 of computing device 12 or loT device 30, or any processing circuitry of any device of system 2 described herein, may discriminate SVT from other ventricular tachyarrhythmia classifications based on a feature indicative of the presence of absence of high frequency harmonics in the episode ECG data. FIGS. 12A and 12B illustrate frequency decompositions 470 and 480 of a MVT episode and an SVT episode, respectively. As illustrated by FIGS. 12A and 12B, the magnitude at certain higher frequency harmonics is greater in the decomposed ECG 480 for the SVT episode (FIG. 12B) than the decomposed ECG 470 for the MVT episode (FIG. 12A). In some examples, the processing circuitry applies a bank of complex exponential functions as convolutional filters to the ECG data for the episode. The frequency range of the bank may be configured to span a frequencies of interest, which may be integer multiples of a lowest frequency in the decomposed ECG data for the episode. For example, the lowest frequency may be about 60 Hertz (Hz), and the bank may span a range from 100 Hz to 500 Hz, continuously across the range or via bands centered on respective integer multiples of 60 Hz. The processing circuitry may classify the episode as SVT based on a suprathreshold output of the convolutional filter(s). [0142] In some examples, the processing circuitry, e.g., processing circuitry 130 of computing device 12 or loT device 30, or any processing circuitry of any device of system 2 described herein, may apply a beat-wise morphological comparator to discriminate PVT from MVT. In such examples, the processing circuitry may generate a convolutional fdter from a selected beat, e.g., the first beat, in the ECG stored by IMD 10 for the episode. The processing circuitry may generate a plurality of convolutional filters based on a decomposition, e.g., Walsh, Fourier, or wavelet, of the selected beat. The processing circuitry may apply the filter(s) to some or all of the other beats in the ECG stored by IMD 10 for the episode, e.g., sequentially. The processing circuitry may classify the episode as PVT based on a suprathreshold variability in the output of the convolutional filter(s).

[0143] As discussed herein, computing device 12 may output an alert or alarm, e.g., audible/visible/tactile via one or more output devices 136, based on receipt of episode (event) data transmitted by IMD 10 in response to the IMD 10 detecting an acute health event, e.g., a fast and sustained tachyarrhythmia. The alarm may be intended to facilitate a wellness check of patient 4, e.g., checking with patient 4 to see if they are responsive. If patient 4 is responsive and not experiencing the acute health event, they may cancel the alarm via one or more input devices 134 of computing device 12.

[0144] In some examples, IMD 10 detected the acute health event using a first set of one or more rules, and processing circuitry 130 of external device 12 applies a second set of one or more rules to the episode data to confirm the acute health event, e.g., based on classification of the episode data. In such examples, processing circuitry 130 may cause one or more output devices 136 to output the alarm based on the confirmation. Because IMD 10 may falsely detect acute health events, use of an alarm may advantageously allow patient 4, bystanders (caregivers) 26, or other users of computing device 12 to cancel a false alarm and other actions (e.g., alerting EMS) in response to false detection of an acute health event. [0145] According to the techniques this disclosure, processing circuitry 130 determines an alarm context, and configures the alarm based on the alarm context. The alarm context may vary based on the likelihood that the patient will be alert and able to respond to the alarm and/or the severity/likelihood of the acute health event. In this manner, the duration and/or intensity of the alarm may be relatively greater when the patient is less likely to be alert or less likely to quickly be able to cancel the alarm and/or when the acute health event is less severe and/or less likely to be actually occurring. The duration of the alarm may be relatively shorter when the patient is more likely to be alert or otherwise quickly able to cancel the alarm and/or when the type of acute health event is more severe and/or more likely to be actually occurring.

[0146] In some examples, processing circuitry 130 selects a duration, intensity, or modality of the alarm based on the alarm context. Intensity may include, as examples, volume of an audible alarm, brightness of a visible alarm, magnitude of a tactile alarm, or rate of flashing/blinking/pulsing of an audible, visible, or tactile alarm. Selecting a modality of the alarm may include selecting which one or more of audible, visual, and/or tactile is the alarm, and/or selecting which of one or more output devices 136 of computing device 12 provide the alarm. In some examples, processing circuitry 130 is configured to transmit a communication to another device to cause the other device to output the alarm, alone or in combination with computing device 12, based on the alarm context. The other device may be a smart speaker or other loT device 30.

[0147] In some examples, processing circuitry 130 is configured to determine the alarm context based on the location of patient 4 and/or time of day, both of which may affect the speed at which patient 4 may respond to the alarm. Processing circuitry 130 may be configured to determine the alarm context based on how recently the patient interacted with computing device 12, which may indicate how likely patient 4 is near computing device 12. [0148] The episode data received from IMD 10 may be first patient parameter data, and processing circuitry 130 may be configured to determine the alarm context based on second patient parameter data. The second patient parameter data may be received from IMD 10, another computing device 12 (e.g., smartwatch), or loT device(s) 30, or determined based on signals from one or more sensors 138 of computing device 12. Processing circuitry 130 may determine the alarm context based on the second patient parameter data.

[0149] The second patient parameter data may include respiration data, fluid data, posture data, activity data, heart state data, electrocardiogram data, heart rate variability data, oxygen saturation data, blood pressure data, or sleep stage data. Posture data, respiration data, and sleep stage data may indicate alertness of patient 4 or whether patient may have collapsed or lost consciousness due to the acute health event. Processing circuitry 130 may be configured to increase at least one of a duration or intensity of the alarm based on such data satisfying one or more low alertness criteria. In some examples, computing device 12 may include at least one of a camera configured to generate video data or a microphone configured to generate audio data, and processing circuitry 130 may be configured to determine the alarm context based on the video data or the audio data. In some examples, computing device 12 may receive at least one of video data or audio data from another device, e.g., loT device 30 or smartwatch.

[0150] In some examples, processing circuitry 130 is configured to determine the alarm context based on a type or severity of the acute health event, e.g., a type of tachyarrhythmia, such as SVT, MVT, PVT, or VF. In some examples, processing circuitry 130 is configured to determine a classification of the acute health event based on the episode data, e.g., using one or more ML models as described herein, and determine the alarm context based on the classification. In some examples, processing circuitry 130 is configured to determine at least one of a probability or a confidence level of the classification based on the application of the episode data to one or more ML models. In some examples, processing circuitry 130 respectively analyzes timewise segments of the episode data, e.g., M second segments ofN seconds of episode data transmitted by IMD 10, to determine respective segment classifications and probabilities, and determines the alarm context based on the segment classifications and/or probabilities.

[0151] As an example, based on one or more of a relatively high probability of a relatively severe acute health event, e.g., a probability score of 0.999917 for VF, or agonal breathing indicated by impedance and audio data, processing circuitry 130 may reduce a duration of the alarm, e.g., from 30 seconds to fifteen seconds, and increase the intensity of the alarm, e.g., loud alert on phone, rooms lights flashing, and smart bed vibrating.

[0152] As another example, based on one or more of a relatively low probability of a relatively severe acute health event, e.g., a probability score of 0.6 for VF, second patient parameter indicating that patient 4 is in a deep sleep, or time of day being night, processing circuitry 130 may increase the duration of the alarm, e.g., to one minute or more, and reduce an intensity of the alarm, at least during an initial part of the duration. As another example, based on a classification of MVT, which may be tolerated by patient 4, processing circuitry 130 may determine the alarm context primarily based on second patient parameter data, audio/audio video data, etc.

[0153] In some examples, processing circuitry 130 determines the alarm context based on feedback from patient 4, e.g., a response of patient 4 to previous alarms or to questions. In some examples, the responses may be verbal and via an event assistant as described herein. For example, if patient 4 responds that they are okay but feeling symptomatic, the duration of the duration of a subsequent alarm may be shorter and the intensity of the alarm may be greater. If patient 4 responds that they are okay and not feeling symptoms, the duration of the alarm may be extended. [0154] FIG. 13 is a flow diagram illustrating an example operation for configuring an acute health event alarm based on an alarm context. The example operation of FIG. 13 is described with respect to computing device 12 but could additionally or alternatively be performed by any device described herein, such as loT devices 30.

[0155] According to the example of FIG. 13, processing circuitry, e.g., processing circuitry 130 of computing device 12, receives episode data (also referred to as event data) from IMD 10 (400). IMD 10 may have transmitted the episode data to computing device 12 in response to detecting a tachyarrhythmia or other health event based on application of a first set of rules as described herein. Processing circuitry 130 may determine an alarm context in response to receiving the episode data (402) and configure an alarm for the acute health event based on the alarm context (404). Processing circuitry 130 may control the one or more output devices 136 to output the alarm configured based on the alarm context (406).

[0156] FIG. 14 is a conceptual diagram illustrating an example machine learning model 600 configured to determine an extent to which patient parameter data is indicative of an acute health event, such as a ventricular tachyarrhythmia or SCA. Machine learning model 600 is an example of neural networks 404 and 438 described with respect to FIGS. 9 and 10, or any set of rules implemented by any rules engine described herein, any of which may be implemented by processing circuitry 130 and/or rules engine 172 of computing device 12 in wireless communication with IMD 10, as discussed above. Machine learning model 600 is an example of a deep learning model, or deep learning algorithm, trained to determine whether a particular set of patient parameter data indicates the presence of an acute health event, e.g., whether a particular segment of ECG signal data indicates SCA or a certain classification related to ventricular tachyarrhythmia, as described herein.

[0157] One or more of IMD 10, computing device 12, an loT device 30, or a computing system 20 may train, store, and/or utilize machine learning model 600, but other devices may apply inputs associated with a particular patient to machine learning model 600 in other examples. As discussed above, other types of machine learning and deep learning models or algorithms may be utilized in other examples. For example, a CNN model of ResNet-18 may be used. Some non-limiting examples of models that may be used for transfer learning include AlexNet, VGGNet, GoogleNet, ResNet50, or DenseNet, etc. Some non-limiting examples of machine learning techniques include Support Vector Machines, K-Nearest Neighbor algorithm, and Multi-layer Perceptron.

[0158] As shown in the example of FIG. 21, machine learning model 600 may include three layers. These three layers include input layer 602, hidden layer 604, and output layer 606. Output layer 606 comprises the output from the transfer function 605 of output layer 606. Input layer 602 represents each of the input values XI through X4 provided to machine learning model 600. The number of inputs may be equal to, less than, or greater than 4, including much greater than 4, e.g., hundreds or thousands. In some examples, the input values may any of the of values input into a machine learning model, as described above. In some examples, input values may include samples of an ECG signal. In addition, in some examples input values of machine learning model 600 may include additional data, such as R-wave data, R-R interval data, or other data relating to one or more additional parameters of patient 4, as described herein.

[0159] Each of the input values for each node in the input layer 602 is provided to each node of hidden layer 604. In the example of FIG. 14, hidden layers 604 include two layers, one layer having four nodes and the other layer having three nodes, but fewer or greater number of nodes may be used in other examples. Each input from input layer 602 is multiplied by a weight and then summed at each node of hidden layers 604. During training of machine learning model 600, the weights for each input are adjusted to establish the relationship between the inputs, e.g., input ECG segment, to determining whether a particular set of inputs represents an acute health event and/or determining a score indicative of whether a set of inputs may be representative of SCA, MVT, PVT, VR, or another acute health event. In some examples, one hidden layer may be incorporated into machine learning model 600, or three or more hidden layers may be incorporated into machine learning model 600, where each layer includes the same or different number of nodes.

[0160] The result of each node within hidden layers 604 is applied to the transfer function of output layer 606. The transfer function may be liner or non-linear, depending on the number of layers within machine learning model 600. Example non-linear transfer functions may be a sigmoid function or a rectifier function. The output 607 of the transfer function may be a classification that indicates whether the particular ECG segment or other input set represents an acute health event, e.g., ventricular tachyarrhythmia, and/or a score indicative of an extent to which the input data set represents an acute health event. In some examples, output 607 may include respective probabilities for a plurality of classifications, e.g., as discussed herein with respect to FIGS. 9-11.

[0161] By applying the ECG signal data and/or other patient parameter data to a machine learning model, such as machine learning model 600, processing circuitry, such as processing circuitry 130 of computing device 12, is able to determine a patient is experiencing or will soon experience an acute health event with great accuracy, specificity, and sensitivity. This may facilitate determinations of risk of sudden cardiac death and may lead to alerts and other interventions as described herein. Machine learning model 600 may correspond to any one or more of rules 84, rules 196, and rules 250 described herein.

[0162] FIG. 15 is an example of a machine learning model 600 being trained using supervised and/or reinforcement learning techniques. Machine learning model 600 may be implemented using any number of models for supervised and/or reinforcement learning, such as but not limited to, an artificial neural network, a decision tree, naive Bayes network, support vector machine, or k-nearest neighbor model, to name only a few of the examples discussed above. In some examples, processing circuitry one or more of IMD 10, computing device 12, an loT device 30, and/or computing system(s) 20 (e.g., rules configuration modules 174 and/or 234) initially trains the machine learning model 600 based on training set data 700 including numerous instances of input data corresponding to acute health events and non-acute health events, e.g., as labeled by an expert. A prediction or classification by the machine learning model 600 may be compared 704 to the target output 703, e.g., as determined based on the label. Based on an error signal representing the comparison, the processing circuitry implementing a leaming/training function 705 may send or apply a modification to weights of machine learning model 600 or otherwise modify/update the machine learning model 600. For example, one or more of IMD 10, computing device 12, loT device 30, and/or computing system(s) 20 may, for each training instance in the training set 700, modify machine learning model 600 to change a score generated by the machine learning model 600 in response to data applied to the machine learning model 600.

[0163] FIG. 16A is a perspective drawing illustrating an IMD 10A, which may be an example configuration of IMD 10 of FIGS. 1 and 2 as an ICM. In the example shown in FIG. 16 A, IMD 10A may be embodied as a monitoring device having housing 812, proximal electrode 816A and distal electrode 816B. Housing 812 may further comprise first major surface 814, second major surface 818, proximal end 820, and distal end 822. Housing 812 encloses electronic circuitry located inside the IMD 10A and protects the circuitry contained therein from body fluids. Housing 812 may be hermetically sealed and configured for subcutaneous implantation. Electrical feedthroughs provide electrical connection of electrodes 816A and 816B.

[0164] In the example shown in FIG. 16A, IMD 10A is defined by a length L, a width W and thickness or depth D and is in the form of an elongated rectangular prism wherein the length L is much larger than the width W, which in turn is larger than the depth D. In one example, the geometry of the IMD 10A - in particular a width W greater than the depth D - is selected to allow IMD 10A to be inserted under the skin of the patient using a minimally invasive procedure and to remain in the desired orientation during insertion. For example, the device shown in FIG. 16A includes radial asymmetries (notably, the rectangular shape) along the longitudinal axis that maintains the device in the proper orientation following insertion. For example, the spacing between proximal electrode 816A and distal electrode 816B may range from 5 millimeters (mm) to 55 mm, 30 mm to 55 mm, 35 mm to 55 mm, and from 40 mm to 55 mm and may be any range or individual spacing from 5 mm to 60 mm. In addition, IMD 10A may have a length L that ranges from 30 mm to about 70 mm. In other examples, the length L may range from 5 mm to 60 mm, 40 mm to 60 mm, 45 mm to 60 mm and may be any length or range of lengths between about 30 mm and about 70 mm. In addition, the width W of major surface 814 may range from 3 mm to 15, mm, from 3 mm to 10 mm, or from 5 mm to 15 mm, and may be any single or range of widths between 3 mm and 15 mm. The thickness of depth D of IMD 10A may range from 2 mm to 15 mm, from 2 mm to 9 mm, from 2 mm to 5 mm, from 5 mm to 15 mm, and may be any single or range of depths between 2 mm and 15 mm. In addition, IMD 10A according to an example of the present disclosure is has a geometry and size designed for ease of implant and patient comfort. Examples of IMD 10A described in this disclosure may have a volume of three cubic centimeters (cm) or less, 1.5 cubic cm or less or any volume between three and 1.5 cubic centimeters.

[0165] In the example shown in FIG. 16A, once inserted within the patient, the first major surface 814 faces outward, toward the skin of the patient while the second major surface 818 is located opposite the first major surface 814. In addition, in the example shown in FIG. 16A, proximal end 820 and distal end 822 are rounded to reduce discomfort and irritation to surrounding tissue once inserted under the skin of the patient. IMD 10A, including instrument and method for inserting IMD 10A is described, for example, in U.S. Patent Publication No. 2014/0276928, incorporated herein by reference in its entirety.

[0166] Proximal electrode 816A is at or proximate to proximal end 820, and distal electrode 816B is at or proximate to distal end 822. Proximal electrode 816A and distal electrode 816B are used to sense cardiac EGM signals, e.g., ECG signals, thoracically outside the ribcage, which may be sub-muscularly or subcutaneously. Cardiac signals may be stored in a memory of IMD 10A, and data may be transmitted via integrated antenna 830A to another device, which may be another implantable device or an external device, such as external device 812. In some example, electrodes 816A and 816B may additionally or alternatively be used for sensing any bio-potential signal of interest, which may be, for example, an EGM, EEG, EMG, or a nerve signal, or for measuring impedance, from any implanted location.

[0167] In the example shown in FIG. 16A, proximal electrode 816A is at or in close proximity to the proximal end 820 and distal electrode 816B is at or in close proximity to distal end 822. In this example, distal electrode 816B is not limited to a flattened, outward facing surface, but may extend from first major surface 814 around rounded edges 824 and/or end surface 826 and onto the second major surface 818 so that the electrode 816B has a three- dimensional curved configuration. In some examples, electrode 816B is an uninsulated portion of a metallic, e.g., titanium, part of housing 812.

[0168] In the example shown in FIG. 23 A, proximal electrode 816A is located on first major surface 814 and is substantially flat, and outward facing. However, in other examples proximal electrode 816A may utilize the three-dimensional curved configuration of distal electrode 816B, providing a three-dimensional proximal electrode (not shown in this example). Similarly, in other examples distal electrode 816B may utilize a substantially flat, outward facing electrode located on first major surface 814 similar to that shown with respect to proximal electrode 816A. The various electrode configurations allow for configurations in which proximal electrode 816A and distal electrode 816B are located on both first major surface 814 and second major surface 818. In other configurations, such as that shown in FIG. 16A, only one of proximal electrode 816A and distal electrode 816B is located on both major surfaces 814 and 818, and in still other configurations both proximal electrode 816A and distal electrode 816B are located on one of the first major surface 814 or the second major surface 818 (e.g., proximal electrode 816A located on first major surface 814 while distal electrode 816B is located on second major surface 818). In another example, IMD 10A may include electrodes on both major surface 814 and 818 at or near the proximal and distal ends of the device, such that a total of four electrodes are included on IMD 10A. Electrodes 816A and 816B may be formed of a plurality of different types of biocompatible conductive material, e.g., stainless steel, titanium, platinum, iridium, or alloys thereof, and may utilize one or more coatings such as titanium nitride or fractal titanium nitride.

[0169] In the example shown in FIG. 16A, proximal end 820 includes a header assembly 828 that includes one or more of proximal electrode 816A, integrated antenna 830A, antimigration projections 882, and/or suture hole 834. Integrated antenna 830A is located on the same major surface (i.e., first major surface 814) as proximal electrode 816A and is also included as part of header assembly 828. Integrated antenna 830A allows IMD 10A to transmit and/or receive data. In other examples, integrated antenna 830A may be formed on the opposite major surface as proximal electrode 816A or may be incorporated within the housing 812 of IMD 10A. In the example shown in FIG. 16A, anti-migration projections 832 are located adjacent to integrated antenna 830A and protrude away from first major surface 814 to prevent longitudinal movement of the device. In the example shown in FIG. 16A, anti-migration projections 832 include a plurality (e.g., nine) small bumps or protrusions extending away from first major surface 814. As discussed above, in other examples antimigration projections 832 may be located on the opposite major surface as proximal electrode 816A and/or integrated antenna 830A. In addition, in the example shown in FIG. 16A, header assembly 828 includes suture hole 834, which provides another means of securing IMD 10A to the patient to prevent movement following insertion. In the example shown, suture hole 834 is located adjacent to proximal electrode 816A. In one example, header assembly 828 is a molded header assembly made from a polymeric or plastic material, which may be integrated or separable from the main portion of IMD 10A.

[0170] FIG. 16B is a perspective drawing illustrating another IMD 10B, which may be another example configuration of IMD 10 from FIGS. 1 and 2 as an ICM. IMD 10B of FIG. 16B may be configured substantially similarly to IMD 10A of FIG. 16A, with differences between them discussed herein.

[0171] IMD 10B may include a leadless, subcutaneously-implantable monitoring device, e.g., an ICM. IMD 10B includes housing having a base 840 and an insulative cover 842. Proximal electrode 816C and distal electrode 816D may be formed or placed on an outer surface of cover 842. Various circuitries and components of IMD 10B, e.g., described above with respect to FIG. 2, may be formed or placed on an inner surface of cover 842, or within base 840. In some examples, a battery or other power source of IMD 10B may be included within base 840. In the illustrated example, antenna 830B is formed or placed on the outer surface of cover 842 but may be formed or placed on the inner surface in some examples. In some examples, insulative cover 842 may be positioned over an open base 840 such that base 840 and cover 842 enclose the circuitries and other components and protect them from fluids such as body fluids. The housing including base 840 and insulative cover 842 may be hermetically sealed and configured for subcutaneous implantation.

[0172] Circuitries and components may be formed on the inner side of insulative cover 842, such as by using flip-chip technology. Insulative cover 842 may be flipped onto a base 840. When flipped and placed onto base 840, the components of IMD 10B formed on the inner side of insulative cover 842 may be positioned in a gap 844 defined by base 840. Electrodes 816C and 816D and antenna 830B may be electrically connected to circuitry formed on the inner side of insulative cover 842 through one or more vias (not shown) formed through insulative cover 842. Insulative cover 842 may be formed of sapphire (i.e., corundum), glass, parylene, and/or any other suitable insulating material. Base 840 may be formed from titanium or any other suitable material (e.g., a biocompatible material). Electrodes 816C and 846D may be formed from any of stainless steel, titanium, platinum, iridium, or alloys thereof. In addition, electrodes 846C and 846D may be coated with a material such as titanium nitride or fractal titanium nitride, although other suitable materials and coatings for such electrodes may be used.

[0173] In the example shown in FIG. 16B, the housing of IMD 10B defines a length L, a width W and thickness or depth D and is in the form of an elongated rectangular prism wherein the length L is much larger than the width W, which in turn is larger than the depth D, similar to IMD 10A of FIG. 16A. For example, the spacing between proximal electrode 816C and distal electrode 816D may range from 5 mm to 50 mm, from 30 mm to 50 mm, from 35 mm to 45 mm, and may be any single spacing or range of spacings from 5 mm to 50 mm, such as approximately 40 mm. In addition, IMD 10B may have a length L that ranges from 5 mm to about 70 mm. In other examples, the length L may range from 30 mm to 70 mm, 40 mm to 60 mm, 45 mm to 55 mm, and may be any single length or range of lengths from 5 mm to 50 mm, such as approximately 45 mm. In addition, the width W may range from 3 mm to 15 mm, 5 mm to 15 mm, 5 mm to 10 mm, and may be any single width or range of widths from 3 mm to 15 mm, such as approximately 8 mm. The thickness or depth D of IMD 10B may range from 2 mm to 15 mm, from 5 mm to 15 mm, or from 3 mm to 5 mm, and may be any single depth or range of depths between 2 mm and 15 mm, such as approximately 4 mm. IMD 10B may have a volume of three cubic centimeters (cm) or less, or 1.5 cubic cm or less, such as approximately 1.4 cubic cm.

[0174] In the example shown in FIG. 16B, once inserted subcutaneously within the patient, outer surface of cover 842 faces outward, toward the skin of the patient. In addition, as shown in FIG. 16B, proximal end 846 and distal end 848 are rounded to reduce discomfort and irritation to surrounding tissue once inserted under the skin of the patient. In addition, edges of IMD 10B may be rounded.

[0175] It should be understood that various aspects disclosed herein may be combined in different combinations than the combinations specifically presented in the description and accompanying drawings. It should also be understood that, depending on the example, certain acts or events of any of the processes or methods described herein may be performed in a different sequence, may be added, merged, or left out altogether (e.g., all described acts or events may not be necessary to carry out the techniques). In addition, while certain aspects of this disclosure are described as being performed by a single module, unit, or circuit for purposes of clarity, it should be understood that the techniques of this disclosure may be performed by a combination of units, modules, or circuitry associated with, for example, a medical device.

[0176] In one or more examples, the described techniques may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or code on a computer-readable medium and executed by a hardware -based processing unit. Computer-readable media may include non-transitory computer-readable media, which corresponds to a tangible medium such as data storage media (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 can be accessed by a computer).

[0177] Instructions may 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 logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Accordingly, the term “processor” or “processing circuitry” as used herein may refer to any of the foregoing structure or any other physical structure suitable for implementation of the described techniques. Also, the techniques could be fully implemented in one or more circuits or logic elements.

[0178] The following examples are illustrative of the techniques described herein.

[0179] Example 1. A computing device comprising: communication circuitry configured to wirelessly communicate with a sensor device on a patient or implanted within the patient; one or more output devices; and processing circuitry configured to: receive episode data for an acute health event detected by the sensor device via the communication circuitry, the episode data transmitted by the sensor device in response to detecting the acute health event; determine an alarm context in response to receiving the episode data; configure an alarm for the acute health event based on the alarm context; and control the one or more output devices to output the alarm that is configured based on the alarm context.

[0180] Example 2. The computing device of example 1, wherein, to configure the alarm, the processing circuitry is configured to select a duration of the alarm based on the alarm context. [0181] Example 3. The computing device of example 1 or 2, wherein, to configure the alarm, the processing circuitry is configured to select an intensity of the alarm based on the alarm context.

[0182] Example 4. The computing device of example 3, wherein the intensity comprises a volume of an audible alarm.

[0183] Example 5. The computing device of any one or more of examples 1 to 4, wherein, to configure the alarm, the processing circuitry is configured to select a modality of the alarm based on the alarm context.

[0184] Example 6. The computing device of any one or more of examples 1 to 5, wherein, to configure the alarm, the processing circuitry is configured to transmit, via the communication circuitry, a communication to another device configured to cause the other device to output at least a portion of the alarm.

[0185] Example 7. The computing device of example 6, wherein the other device comprises an Internet of Things device.

[0186] Example 8. The computing device of example 7, wherein the Internet of

Things device comprises a smart speaker.

[0187] Example 9. The computing device of any one or more of examples 1 to 8, wherein the processing circuitry is configured to determine the alarm context based on a type of the acute health event.

[0188] Example 10. The computing device of any one or more of examples 1 to 9, wherein the processing circuitry is configured to determine the alarm context based on a location of the patient.

[0189] Example 11. The computing device of any one or more of examples 1 to 10, wherein the processing circuitry is configured to determine the alarm context based on a time of day.

[0190] Example 12. The computing device of any one or more of examples 1 to 11, wherein the episode data comprises first patient parameter data, wherein the processing circuitry is configured to: receive second patient parameter data from the sensor device; and determine the alarm context based on the second patient parameter data.

[0191] Example 13. The computing device of any one or more of examples 1 to 11, further comprising one or more sensors, separate from the sensor device, configured to sense one or physiological signals of the patient, wherein the episode data comprises first patient parameter data, wherein the processing circuitry is configured to: determine second patient parameter data based on the one or more physiological signals; and determine the alarm context based on the second patient parameter data.

[0192] Example 14. The computing device of example 12 or 13, wherein the second patient parameter data comprises one or more of respiration data, fluid data, posture data, activity data, heart state data, electrocardiogram data, heart rate variability data, oxygen saturation data, blood pressure data, or sleep stage data.

[0193] Example 15. The computing device of examples 3 and 14, wherein the processing circuitry is configured to increase at least one of a duration or intensity of the alarm based on at least one of posture data, respiration data, or sleep stage data satisfying one or more low alertness criteria.

[0194] Example 16. The computing device of any one or more of examples 1 to 15, further comprising at least one of a camera configured to generate video data or a microphone configured to generate audio data, wherein the processing circuitry is configured to determine the alarm context in response to receiving the episode data and based on the video data or the audio data.

[0195] Example 17. The computing device of any one or more of examples 1 to 15, wherein the processing circuitry is configured to: receive at least one of video data or audio data from another device via the communication circuitry; and determine the alarm context in response to receiving the episode data and based on the video data or the audio data.

[0196] Example 18. The computing device of example 17, wherein the other device comprises one of a smart watch or an Internet of Things device.

[0197] Example 19. The computing device of any one or more of examples 1 to 18, wherein the processing circuitry is configured to: determine a classification of the acute health event based on the episode data; and determine the alarm context based on the classification.

[0198] Example 20. The computing device of example 19, wherein the processing circuitry is configured to apply the episode data to one or more machine learning models to determine the classification.

[0199] Example 21. The computing device of example 20, wherein the processing circuitry is configured to: determine at least one of a probability or a confidence level of the classification based on the application of the episode data to one or more machine learning models; and determine the alarm context based on the probability or confidence level.

[0200] Example 22. The computing device of any one or more of examples 1 to 21, wherein the computing device comprises a smartphone. [0201] Example 23. The computing device of any one or more of examples 1 to 21, wherein the computing device comprises an Internet of Things device.

[0202] Example 24. The computing device of any one or more of examples 1 to 23, wherein the processing circuitry is configured to determine the alarm context based on patient feedback.

[0203] Example 25. A system comprising: a sensor device; and a computing device of any one or more of examples 1 to 24.

[0204] Example 26. The system of example 25, wherein the sensor device comprises an implantable medical device.

[0205] Example 27. The system of example 26, wherein the implantable medical device comprises an insertable cardiac monitor.

[0206] Example 28. The system of example 27, wherein the episode data comprises electrocardiogram data and the insertable cardiac monitor comprises: a housing configured for subcutaneous implantation in a patient, the housing having a length between 40 millimeters (mm) and 60 mm between a first end and a second end, a width less than the length, and a depth less than the width; a first electrode at or proximate to the first end; a second electrode at or proximate to the second end; and circuitry within the housing and configured to sense an electrocardiogram corresponding to the electrocardiogram data via the first electrode and the second electrode and detect the acute health event based on the electrocardiogram .

[0207] Example 29. A method of operating a computing device, the method comprising: receiving, via communication circuitry of the computing device, episode data for an acute health event detected by a sensor device, the episode data transmitted by the sensor device in response to detecting the acute health event; determining, by processing circuitry of the computing device, an alarm context in response to receiving the episode data; configuring, by the processing circuitry, an alarm for the acute health event based on the alarm context; and controlling, by the processing circuitry, one or more output devices of the computing device to output the alarm that is configured based on the alarm context.

[0208] Example 30. A non-transitory computer-readable storage medium comprising instructions that cause processing circuitry to: receive episode data for an acute health event detected by a sensor device, the episode data transmitted by the sensor device in response to detecting the acute health event; determine an alarm context in response to receiving the episode data; configure an alarm for the acute health event based on the alarm context; and output the alarm that is configured based on the alarm context. [0209] Various examples have been described. These and other examples are within the scope of the following claims.