System and method for monitoring compliance of patients wearing portable medical devices
The wearable defibrillator system addresses compliance issues by using electrodes and motion sensors to track wear time and provide feedback, ensuring consistent device use and reducing the risk of non-compliance in cardiac monitoring.
Patent Information
- Application Number
- JP2023520376
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2020-11-18
- Filing Date
- 2021-11-17
- Publication Date
- 2024-11-20
- Estimated Expiration
- 2041-11-17
AI Technical Summary
Existing wearable cardiac monitoring devices face challenges in ensuring continuous patient compliance, which is crucial for effective monitoring and treatment of cardiac arrhythmias, as patients may not consistently wear the devices as prescribed, leading to potential life-threatening situations.
A wearable defibrillator system that includes electrodes for monitoring electrical activity, motion sensors, and a processor to track wearing compliance by detecting start and end events based on electrical and motion signals, providing graphical representations and notifications to ensure consistent device use.
Enhances patient compliance by accurately tracking wear time and providing feedback, reducing the risk of non-compliance and enabling timely intervention for cardiac arrhythmias.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[Technical field]
[0001] This application claims priority under 35 U.S.C. § 120 to U.S. patent application Ser. No. 16 / 951,246, entitled "SYSTEM AND METHOD FOR MONITORING WEARING COMPLIANCE OF PATIENTS WEARING PORTABLE MEDICAL DEVICES," filed Nov. 18, 2020, which is hereby incorporated by reference in its entirety. [Background technology]
[0002] The present disclosure relates to monitoring patients prescribed wearable medical devices for wearer compliance.
[0003] Heart failure, if left untreated, can lead to certain life-threatening arrhythmias. Both atrial and ventricular arrhythmias are common in patients with heart failure. One of the most lethal cardiac arrhythmias is ventricular fibrillation, which occurs when normal, regular electrical impulses are replaced by irregular, rapid impulses that cause the heart muscle to stop contracting normally. Because patients receive no perceptible warning of the impending fibrillation, death often occurs before needed medical help can arrive. Other cardiac arrhythmias can include an excessively slow heart rate, known as bradycardia, or an excessively fast heart rate, known as tachycardia. Cardiac arrest can occur when a patient experiences various arrhythmias of the heart, including ventricular fibrillation, ventricular tachycardia, pulseless electrical activity (PEA), and asystole (the heart stops all electrical activity), causing the heart to provide insufficient levels of blood flow to the brain and other vital organs to support life. It is generally useful to monitor patients with heart failure in order to assess early signs of heart failure and provide interventional therapy as soon as possible.
[0004] A patient who is hospitalized due to or otherwise suffering from an at-risk or adverse cardiac condition may be prescribed a wearable cardiac monitoring and / or treatment device. In addition to the wearable device, the patient may also be given a battery charger and a set of rechargeable batteries. Because wearable devices are generally prescribed for continuous or near-continuous use (e.g., removed only during bathing), the patient wears the device during all daily activities, such as walking, sitting, climbing stairs, resting or sleeping, and other similar daily activities. Maintaining continuous use of the prescribed device can promote better reliability of data collected from monitoring the patient's progress and ensure better protection of the patient, including provision of treatment when necessary. Summary of the Invention
[0005] In at least one example, a wearable defibrillator for providing patient wear compliance information is provided, the wearable defibrillator comprising a plurality of electrodes configured to be continuously externally coupled to a patient over an extended period of time, the plurality of electrodes configured to monitor electrical activity on the patient's skin and to deliver a therapeutic shock to the patient in response to detection of a cardiac arrhythmia based on the monitored electrical activity, at least one motion sensor and associated circuitry configured to generate at least one motion signal based on movement of the patient, and at least one processor operably coupled to the plurality of electrodes and the at least one motion sensor and associated circuitry. The at least one processor is configured to receive at least one electrical signal based on the monitored electrical activity on the patient's skin from the multiple electrodes; record a wear start event based on the at least one electrical signal and the at least one movement signal indicating that the patient is wearing the wearable defibrillator; record a wear end event based on one or more of the at least one electrical signal and the at least one movement signal indicating that the patient is not wearing the wearable defibrillator; and output a graphical representation including information regarding the patient's wear compliance based on the recorded wear start event and the recorded wear end event.
[0006] Implementations of the wearable defibrillator may include one or more of the following features.
[0007] In an example, the wearable defibrillator may further include a display operably coupled to the at least one processor, the at least one processor configured to provide, via the display, the graphical representation of the patient's wear compliance based on output information regarding the patient's wear compliance.
[0008] In an example, the wearable defibrillator may further include a network interface operably coupled to the at least one processor, the at least one processor configured to transmit the information regarding the patient's wearing compliance to a remote server.
[0009] In the wearable defibrillator example, the at least one processor may be further configured to detect an electrocardiogram (ECG) signal based on the at least one electrical signal, and control the wearable defibrillator to deliver an ECG signal therapeutic shock to the patient in response to the detection of the cardiac arrhythmia based on the detected ECG signal.
[0010] In examples of the wearable defibrillator, recording the wearing start event includes detecting one or more ECG signals based on the at least one electrical signal, determining whether the one or more ECG signals meet one or more validity criteria, and recording the wearing start event if the one or more ECG signals meet at least one of the one or more validity criteria. In some examples, the one or more validity criteria include at least one ECG parameter derived from the one or more ECG signals that meet a validity threshold. In some examples, the at least one ECG parameter includes an R-peak amplitude, and meeting the validity threshold includes identifying at least five consecutive R-peak amplitudes that each exceed an amplitude threshold. In some examples, the at least one ECG parameter includes a QRS complex width, and meeting the validity threshold includes measuring at least five consecutive QRS complex widths that each are between 0.05 seconds and 0.15 seconds. In some examples, the at least one processor may be further configured to determine the patient's wear compliance based on a first ECG signal of the one or more ECG signals that meets the validity threshold.
[0011] In the example of the wearable defibrillator, recording the wear start event may include detecting a skin-sensor interface impedance level based on the at least one electrical signal in one or more of the plurality of electrodes, determining whether the impedance level is within an acceptable impedance range, and recording the wear start event if the impedance level is within the acceptable impedance range, and recording the wear end event may include determining whether the impedance level is no longer within the acceptable impedance range, and recording the wear end event based on a determination that the impedance level is no longer within the acceptable impedance range. In some examples, the acceptable impedance range includes at least one of a range from 20 ohms to 250 ohms, a range from 250 ohms to 1 kilohm, and a range from 1 kilohm to 20 kilohm.
[0012] In the wearable defibrillator example, recording the wearing start event may include determining whether the motion signal indicates movement of the patient and the wearable defibrillator, and recording the wearing start event if the motion signal indicates movement of the patient and the wearable defibrillator.
[0013] In some examples, the at least one processor may be further configured to detect one or more ECG signals based on the at least one electrical signal if the motion signal does not indicate movement of the patient and the wearable defibrillator, and to record the wear-onset event based on an analysis of the one or more ECG signals. In some examples, the at least one processor may be further configured to detect one or more noise components in the at least one electrical signal, and to confirm the absence of patient movement based on an analysis of the one or more noise components in the at least one electrical signal.
[0014] In the wearable defibrillator example, recording the wear-start event may include receiving input from the patient specifying that the patient is wearing the wearable defibrillator, and recording the wear-start event based on the input from the patient. In some examples, recording the wearing start event based on the input from the patient includes confirming that the patient is wearing the wearable defibrillator based on the at least one electrical signal and the at least one movement signal, and recording the wearing start event.
[0015] In the wearable defibrillator example, recording the end of wear event may include detecting a change in the at least one electrical signal indicative of an invalid ECG signal, and recording the end of wear event based on the invalid ECG signal.
[0016] In the example of the wearable defibrillator, recording the end of wear event may include detecting a change in a skin-sensor interface impedance level at one or more of the plurality of electrodes, determining whether the impedance level exceeds an impedance threshold, and recording the end of wear event if the impedance level exceeds the impedance threshold. In some examples, the impedance threshold may include one or more of 10 kilohms, 100 kilohms, 1 megahms, 2 megahms, 5 megahms, and 10 megahms.
[0017] In the wearable defibrillator example, recording the end of wear event may include determining that one or more of the plurality of electrodes and the at least one motion sensor and associated circuitry are disconnected from the wearable defibrillator, and recording the end of wear event when it is determined that one or more of the plurality of electrodes and the at least one motion sensor and associated circuitry are disconnected.
[0018] In the wearable defibrillator example, recording the end event may include detecting that the patient has removed the wearable defibrillator based on analysis of the at least one movement signal, confirming that the at least one electrical signal indicates that the patient has removed the wearable defibrillator, and recording the end event based on confirmation that the patient has removed the wearable defibrillator.
[0019] In the wearable defibrillator example, recording the end of wear event may include receiving input from the patient specifying that the patient is removing the wearable defibrillator, and recording the end of wear event based on the input from the patient. In some examples, recording the end-of-wear event based on the input from the patient includes confirming that the patient has removed the wearable defibrillator based on the at least one electrical signal and the at least one movement signal, and recording the end-of-wear event.
[0020] In the example of the wearable defibrillator, the at least one processor may be further configured to determine a current time and record at least one of the wearing start event and the wearing end event based on one or more of the at least one movement signal, the at least one electrical signal, and the current time. In some examples, determining the current time includes determining whether the patient has been in an active state or an inactive state based on the current time. In some examples, the at least one processor may be further configured to record at least one of the wearing start event and the wearing end event based on the at least one electrical signal if the patient has been in an inactive state at the current time. In some examples, the at least one processor may be further configured to record at least one of the wearing start event and the wearing end event based on the at least one electrical signal and the at least one motion signal if the patient has been in an active state at the current time. In some examples, the at least one processor may be further configured to determine whether the patient has been in an active state or an inactive state based on the current time and past patient activity information recorded by the wearable defibrillator.
[0021] In the wearable defibrillator example, the graphical representation may include an indication of patient wear compliance versus patient wear non-compliance.
[0022] In the wearable defibrillator example, the graphical representation may include an indication of recorded changes in wear compliance for the patient.
[0023] In the wearable defibrillator example, the graphical representation may include a timeline showing recorded wearing start and end events. In some examples, the timeline further indicates the total time the wearable defibrillator was worn by the patient and the total time the wearable defibrillator was not worn by the patient over a user-selectable period of time.
[0024] In the wearable defibrillator example, the graphical representation may include one or more user-selectable interface controls configured to provide access to recorded ECG information for one or more of a wear start event, a wear end event, and a period during which the patient wore the wearable defibrillator.
[0025] In the wearable defibrillator example, the at least one processor may be further configured to output a notification of the patient's wearing compliance. In some examples, outputting the notification of the patient's wearing compliance includes comparing the patient's wearing compliance to one or more notification criteria, and outputting the notification if the patient's wearing compliance meets at least one of the one or more notification criteria. In some examples, the one or more notification criteria may include the patient failing to wear the wearable defibrillator for a certain percentage of a period of time. In some examples, the one or more notification criteria may include a recorded change in the patient's wearing compliance that exceeds a compliance change threshold. In some examples, the at least one processor may be further configured to output the notification of the patient's wearing compliance to at least one of the patient, a care provider associated with the patient, and a prescriber of the wearable defibrillator.
[0026] In another example, a method is provided for providing wear compliance information recorded by a wearable defibrillator worn by a patient. The method further comprises: at least one processor transmitting at least one electrical signal determined based on the monitored electrical activity on the skin of the patient to the at least one processor; One processorreceiving, by the at least one processor, at least one motion signal based on the patient's movements and generated by at least one motion sensor and associated circuitry operably coupled to the at least one processor; recording, by the at least one processor, a start-of-wear event based on one or more of the at least one electrical signal and the at least one motion signal indicating that the patient is wearing the wearable defibrillator; recording, by the at least one processor, an end-of-wear event based on one or more of the at least one electrical signal and the at least one motion signal indicating that the patient is not wearing the wearable defibrillator; The method includes at least one processor providing a graphical representation of the patient's wearing compliance based on the recorded wearing start event and the recorded wearing end event; the at least one processor receiving one or more notification criteria from one or more of the patient's care provider and a prescriber of the wearable defibrillator; the at least one processor comparing the patient's wearing compliance and the one or more notification criteria; and if the patient's wearing compliance meets at least one of the one or more notification criteria, the at least one processor outputting a notification to the patient, the patient's care provider, and the prescriber of the wearable defibrillator.
[0027] Implementations of the method for providing wear compliance information recorded by a wearable defibrillator worn by a patient may include one or more of the following features.
[0028] In some examples of the methods, the method may further include the at least one processor outputting, to a display operatively coupled to the at least one processor, a graphical representation of the patient's wear compliance based on the output information regarding the patient's wear compliance.
[0029] In some examples of the methods, the method may further include the at least one processor transmitting the information regarding the patient's wear compliance via a network interface to a remote server operably coupled to the at least one processor.
[0030] In some examples of the methods, the method may further include the at least one processor detecting an ECG signal based on the at least one electrical signal, and the at least one processor controlling the wearable defibrillator to deliver a therapeutic shock to the patient in response to detection of a cardiac arrhythmia based on the detected ECG signal.
[0031] In the method, the step of recording the wear start event may include the at least one processor detecting one or more ECG signals based on the at least one electrical signal; the at least one processor determining whether the one or more ECG signals meet one or more validity criteria; and if the one or more ECG signals meet at least one of the one or more validity criteria, the at least one processor recording the wear start event; and the step of recording the wear end event may include the at least one processor determining whether the impedance level is no longer within the acceptable impedance range, and the at least one processor recording the wear end event based on the determination that the impedance level is no longer within the acceptable impedance range. In some examples, the one or more validity criteria include at least one ECG parameter derived from the one or more ECG signals that meet a validity threshold. In some examples, the at least one ECG parameter may include an R-peak amplitude, and meeting the validity threshold may include identifying at least five consecutive R-peak amplitudes that each exceed an amplitude threshold. In some examples, the at least one ECG parameter may include a QRS complex width and meeting the validity threshold may include measuring at least five consecutive QRS complex widths, each QRS complex width being between 0.05 seconds and 0.15 seconds. In some examples, the method further includes the at least one processor determining the patient's wear compliance based on a first ECG signal of the one or more ECG signals that meets the validity threshold.
[0032] In the method, recording the wear-onset event may include detecting a skin-sensor interface impedance level at one or more of the plurality of electrodes, determining whether the impedance level is within an acceptable impedance range, and recording the wear-onset event if the impedance level is within the acceptable impedance range. In some examples, the acceptable impedance range may include at least one of a range of 20 ohms to 250 ohms, a range of 250 ohms to 1 kilohm, and a range of 1 kilohm to 20 kilohm.
[0033] In the method, recording the wearing start event may include the at least one processor determining whether the motion signal indicates motion of the patient and the wearable defibrillator, and if the motion signal indicates motion of the patient and the wearable defibrillator, the at least one processor recording the wearing start event. In some examples, the method may further include the at least one processor detecting one or more ECG signals based on the at least one electrical signal if the motion signal does not indicate motion of the patient and the wearable defibrillator, and the at least one processor recording the wearing start event based on an analysis of the one or more ECG signals. In some examples, the method may further include the at least one processor detecting one or more noise components in the at least one electrical signal, and the at least one processor confirming the absence of patient motion based on an analysis of the one or more noise components in the at least one electrical signal.
[0034] In the method, the step of recording the wearing start event may include the step of the at least one processor receiving input from the patient specifying that the patient is wearing the wearable defibrillator, and the step of the at least one processor recording the wearing start event based on the input from the patient. In some examples, recording the wearing start event based on the input from the patient includes the at least one processor verifying that the patient is wearing the wearable defibrillator based on the at least one electrical signal and the at least one movement signal; The at least one processor may record the mounting start event.
[0035] In the method, the step of recording the end of wear event may include a step by the at least one processor detecting a change in the at least one electrical signal indicative of an invalid ECG signal, and a step by the at least one processor recording the end of wear event based on the invalid ECG signal.
[0036] In the method, recording the end-of-wear event may include: the at least one processor detecting a change in a skin-sensor interface impedance level at one or more of the plurality of electrodes; the at least one processor determining whether the impedance level exceeds an impedance threshold; and if the impedance level exceeds the impedance threshold, the at least one processor recording the end-of-wear event. In some examples, the impedance threshold may include one or more of 10 kilohms, 100 kilohms, 1 megahms, 2 megahms, 5 megahms, and 10 megahms.
[0037] In the method, recording the end-of-wear event may include the at least one processor determining that one or more of the plurality of electrodes and the at least one motion sensor and associated circuitry are disconnected from the wearable defibrillator, and, upon determining that one or more of the plurality of electrodes and the at least one motion sensor and associated circuitry are disconnected, the at least one processor recording the end-of-wear event.
[0038] In the method, recording the end event may include: the at least one processor detecting that the patient has removed the wearable defibrillator based on analysis of the at least one movement signal; the at least one processor confirming that the at least one electrical signal indicates that the patient has removed the wearable defibrillator; and the at least one processor recording the end event based on confirmation that the patient has removed the wearable defibrillator.
[0039] In the method, recording the end-of-wear event may include the at least one processor receiving input from the patient specifying that the patient is removing the wearable defibrillator, and the at least one processor recording the end-of-wear event based on the input from the patient. In some examples, recording the end-of-wear event based on the input from the patient may include the at least one processor determining that the patient has removed the wearable defibrillator based on the at least one electrical signal and the at least one movement signal, and the at least one processor recording the end-of-wear event.
[0040] In some examples of the method, the method may further include a step in which the at least one processor determines a current time, and a step in which the at least one processor records at least one of the wearing start event and the wearing end event based on one or more of the at least one movement signal, the at least one electrical signal, and the current time. In some examples, determining the current time may include the at least one processor determining whether the patient has been in an active state or an inactive state based on the current time. In some examples, the method may further include the at least one processor recording at least one of the wearing start event and the wearing end event based on the at least one electrical signal if the patient has been in an inactive state at the current time. In some examples, the method may further include the at least one processor recording at least one of the wearing start event and the wearing end event based on the at least one electrical signal and the at least one motion signal if the patient has been in an active state at the current time. In some examples, the method may further include the at least one processor determining whether the patient has been in an active state or an inactive state based on the current time and past patient activity information recorded by the wearable defibrillator.
[0041] In the method, the notification may include an indication of patient wear compliance versus patient wear non-compliance.
[0042] In the method, the notification may include an indication of a recorded change in wear compliance for the patient.
[0043] In the method, the notification may include a timeline showing recorded wearing start and end events. In some examples, the timeline may further show the total time the wearable defibrillator was worn by the patient and the total time the wearable defibrillator was not worn by the patient over a user-selectable period of time.
[0044] In the method, the notification may include one or more user-selectable interface controls configured to provide access to recorded ECG information for one or more of a wear start event, a wear end event, and a period during which the patient wore the wearable defibrillator.
[0045] In the method, outputting the notification of the patient's wear compliance may include the at least one processor comparing the patient's wear compliance to one or more notification criteria; and if the patient's wear compliance meets at least one of the one or more notification criteria, the at least one processor outputting the notification. In some examples, the one or more notification criteria may include the patient failing to wear the wearable defibrillator for a certain percentage of a period of time. In some examples, the one or more notification criteria may include a recorded change in the patient's wear compliance that exceeds a compliance change threshold.
[0046] In at least one example, a patient monitoring device for providing patient wear compliance is provided, such as a wearable defibrillator comprising a plurality of electrodes configured to be externally coupled to a patient over a period of time and configured to monitor electrical activity on the patient's skin and / or deliver a therapeutic shock to the patient in response to detection of a cardiac arrhythmia based on the monitored electrical activity, at least one motion sensor and associated circuitry configured to generate at least one motion signal based on movement of the patient, and at least one processor operably coupled to the plurality of electrodes and the at least one motion sensor and associated circuitry. The at least one processor is configured to receive at least one electrical signal based on the monitored electrical activity on the patient's skin from the multiple electrodes; record one or both of a wear start event and a wear end event, where the wear start event may be based on the at least one electrical signal and the at least one movement signal indicating that the patient is wearing the wearable defibrillator, and where the wear end event may be based on one or more of the at least one electrical signal and the at least one movement signal indicating that the patient is not wearing the wearable defibrillator, and where one or both of the wear start event and wear end event are recorded to determine the patient's wear compliance of the wearable defibrillator. [Brief description of the drawings]
[0047] Various aspects of at least one example are described below with reference to the accompanying drawings, which are not intended to be drawn to scale. The figures are included to provide an explanation and further understanding of the various aspects and examples, and are incorporated in and constitute a part of this specification, but are not intended to limit the scope of the disclosure. The drawings, together with the remainder of the specification, serve to explain the principles and operation of the described and claimed aspects and examples. In the figures, each identical or nearly identical component shown in the various figures is represented by a like numeral. For purposes of clarity, not all components may be labeled in every figure.
[0048] [Figure 1A] 1 illustrates a sample sensor placement for a patient according to an example of the present disclosure. [Figure 1B] 1 illustrates a sample sensor placement for a patient according to an example of the present disclosure.
[0049] [Diagram 2] 1 illustrates a sample accelerometer output according to an example of the present disclosure.
[0050] [Diagram 3] FIG. 1 shows a schematic diagram of a sample controller for a wearable medical device according to an example of the present disclosure.
[0051] [Figure 4] 1 illustrates a sample controller configured to monitor patient wear compliance according to an example of the present disclosure.
[0052] [Diagram 5] 1 illustrates a sample process flow for monitoring patient wear compliance according to an example of the present disclosure.
[0053] [Figure 6A] 1 illustrates a sample process flow for monitoring and validating a start event according to an example of the present disclosure.
[0054] [Figure 6B] 1 illustrates a sample process flow for monitoring and confirming an initiating event by identifying changes in one or more physiological signals, according to an example of the present disclosure.
[0055] [Figure 6C] 1 illustrates a sample process flow for monitoring and confirming an initiation event by identifying a change in one or more motion signals, according to an example of the present disclosure.
[0056] [Figure 6D] 1 illustrates a sample process flow for monitoring and confirming an initiating event by identifying a change in impedance in one or more electrodes, according to an example of the present disclosure.
[0057] [Figure 7A] 1 illustrates a sample process flow for monitoring and validating an end event according to an example of the present disclosure.
[0058] [Figure 7B] 1 illustrates a sample process flow for monitoring and validating events based on time of day, according to an example of the present disclosure.
[0059] [Figure 8] 1 illustrates a sample network overview according to an example of the present disclosure.
[0060] [Figure 9] 13 illustrates a sample diagram of a user interface that allows a physician to access and modify compliance monitoring settings according to an example of the present disclosure.
[0061] [Figure 10A] 13A-13C show sample diagrams of user interfaces including graphical feedback related to patient wear compliance information, according to an example of the present disclosure. [Figure 10B]13A-13C show sample diagrams of user interfaces including graphical feedback related to patient wear compliance information, according to an example of the present disclosure. [Figure 10C] 13A-13C show sample diagrams of user interfaces including graphical feedback related to patient wear compliance information, according to an example of the present disclosure. [Figure 10D] 13A-13C show sample diagrams of user interfaces including graphical feedback related to patient wear compliance information, according to an example of the present disclosure. [Figure 10E] 13A-13C show sample diagrams of user interfaces including graphical feedback related to patient wear compliance information, according to an example of the present disclosure. [Figure 10F] 13A-13C show sample diagrams of user interfaces including graphical feedback related to patient wear compliance information, according to an example of the present disclosure.
[0062] [Figure 11A] 1 illustrates a sample portable medical device that may be prescribed for a heart failure patient, according to one example of the present disclosure. [Figure 11B] 1 illustrates a sample portable medical device that may be prescribed for a heart failure patient, according to one example of the present disclosure. [Figure 11C] 1 illustrates a sample portable medical device that may be prescribed for a heart failure patient, according to one example of the present disclosure. [Figure 11D] 1 illustrates a sample portable medical device that may be prescribed for a heart failure patient, according to one example of the present disclosure.
[0063] [Figure 12] 1 illustrates a sample timing diagram showing patient-oriented wearing periods and corresponding start and end events according to an example of the present disclosure.
[0064] [Figure 13] 1 illustrates a sample input / output diagram of a compliance monitoring process according to an example of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0065] Wearable medical devices, such as cardiac event monitoring and / or therapy devices, are used in clinical or outpatient settings to monitor and / or record various ECG and other physiological signals of patients. These ECG and other physiological signals may be used to monitor arrhythmias, and in the exemplary devices described herein, provide therapy, such as defibrillation or pacing shocks in the event of a life-threatening arrhythmia. An exemplary cardiac monitoring and therapy device that can implement the wearing compliance functions and / or processes described herein includes a wearable defibrillator, also referred to as a wearable cardioverter-defibrillator (WCD). Another exemplary cardiac monitoring and therapy device that can implement the wearing compliance functions and / or processes described herein includes an in-hospital wearable cardioverter-defibrillator (HWD).
[0066] In order to effectively monitor and, if necessary, provide therapy to the patient, it is desirable for the patient to wear the device as continuously as possible. To this end, monitoring patient wear compliance information can provide feedback to both the patient's physician and the patient themselves. Adjusting the patient's habits regarding wearing the medical device increases both the overall effectiveness of cardiac monitoring for the patient and the likelihood that therapy will be provided to the patient if necessary.
[0067] The present disclosure relates to improved wear time monitoring techniques for providing reliable patient compliance information, including wear time start and end times, to patients and / or caregivers to determine overall patient wear compliance information. In implementations described herein, wear compliance is determined using one or more electrical signals from the patient from which ECG information and / or body impedance measurements can be derived. The one or more electrical signals can be analyzed alone or in combination with patient motion information and / or one or more additional physiological signals to more precisely determine wear compliance.
[0068] For example, a processor in a wearable medical device described herein may be configured to monitor for a wear compliance start event indicating that the patient is wearing the medical device. Following determination of the start event, the processor may further monitor for an end event indicating that the patient is no longer wearing the medical device. The time between the start event and the corresponding end event may be recorded and analyzed to determine overall wear compliance information for the patient over a period of time, such as a day, a week, two weeks, a month, and other periods described herein. In the examples described herein, the wear compliance start and end events may be based on physiological signals and other information, including, for example, ECG signals, body impedance measurements, patient motion information, time information, and / or other physiological signals and collected / observed information. With respect to physiological signals, including ECG signals, the systems and methods described herein evaluate such signals to determine that such signals are from wear by the patient, e.g., the underlying physiological and / or ECG sensors are in contact with the patient's skin.
[0069] In an example, the processor may be configured to monitor physiological signals collected by sensors associated with the medical device to determine a wear start event, such as an ECG signal and a body impedance measurement, a cardiac vibration signal, and / or a radio frequency (RF)-based physiological signal. Rather than relying solely on whether the medical device is on or off, or solely on patient motion information, at least some implementations herein use some combination of medical device on / off status, patient motion information, ECG signal, body impedance measurement, cardiac vibration signal, and / or RF-based physiological information. Each of these may be appropriately weighted in a predetermined manner. For example, a wear start event may be based on a combination in which the ECG signal is weighted over the patient motion information (60% ECG signal and 40% patient motion information). For example, the processor may monitor physiological signals received from a physiological sensor and combine the physiological signals with motion signals received from a motion sensor to identify changes that may indicate a wear start event. Once a wear start event is detected, the processor may continue to monitor the signal for changes that may indicate an end event. Once an end event is detected, the processor can process or otherwise generate information related to the patient's wear compliance, for display to, for example, the patient's physician or healthcare provider (HCP), the patient, or another person associated with the delivery of treatment for the patient.
[0070] The wear compliance monitoring described herein provides various advantages and benefits. In some examples described herein, by monitoring one or more types of physiological signals derived from the patient (e.g., ECG signals, cardiac vibration signals, RF-based signals, and / or bioimpedance signals), alone or in combination with other signals, such as patient motion information for start and end events, a processor can accurately obtain wear compliance information that indicates that the patient is actually wearing the medical device. The signals, such as ECG signals, cardiac vibration signals, bioimpedance signals, and RF-based signals, are received directly from the patient wearing the medical device. If the patient is not wearing the medical device, such signals will not be available. For example, in one scenario, the implementation herein uses both ECG signal information and patient motion information to determine wear compliance. Systems that use patient motion information can be enhanced and become more reliable by implementing the functions described herein. As a result, the implementation herein is less likely to make errors in determining patient wear compliance information (e.g., less likely to indicate that the patient is wearing the medical device when the patient is not actually wearing it).
[0071] Additionally, by providing improved wear compliance information to the patient's physician, the physician can be quickly alerted to any non-compliance by the patient. Given the reliability of the underlying wear compliance information described herein, the physician can act with a higher degree of confidence. In response to such an alert, the physician can take action to correct the non-compliance before the patient experiences any potential adverse events that could have been avoided if the patient had adhered to the wear compliance information associated with the wearable medical device.
[0072] In some examples, the systems and methods described herein provide improved wear compliance information to patients. For example, patients can access wear compliance information or receive alerts regarding certain conditions that may or may not be met based on the improved wear compliance information. For example, if a patient is deemed not to have worn a medical device for a pre-set period of four hours, the patient can receive a prompt on their phone to wear the medical device. Thus, by providing improved wear compliance information or portions of improved wear compliance information to patients, patients can monitor and adjust their own compliance while limiting or avoiding necessary follow-up from physicians.
[0073] To address these and other aspects to enhance the performance of patient wearing compliance monitoring, systems and processes configured to accurately record wearing compliance information are described herein. For example, a wearable defibrillator for providing patient wearing compliance information may include a plurality of electrodes configured to monitor the patient's electrical activity and provide a therapeutic shock to the patient in response to detection of a cardiac arrhythmia based on the monitored electrical activity. Similarly, the wearable defibrillator may include at least one motion sensor and associated circuitry configured to generate at least one motion signal based on the patient's movement. The wearable defibrillator may further include at least one processor operably coupled to the plurality of electrodes and the at least one motion sensor and associated circuitry. In some examples, the at least one processor is configured to receive at least one electrical signal based on the monitored electrical activity from the plurality of electrodes, and record a wearing start event based on an ECG signal sensed from the patient's skin and at least one motion signal indicating that the patient is wearing the wearable defibrillator. The at least one processor may be further configured to record a wear end event based on one or more of the at least one electrical signal and the at least one movement signal indicating that the patient is not wearing the wearable defibrillator. The process may be configured to process the wear compliance information based on the start event and the end event, and to output a graphical representation of the wear compliance information.
[0074] In a similar example, the processor may be configured to detect an electrocardiogram (ECG) signal from the one or more electrical signals and determine one or more of a start event and an end event based on a change in the ECG signal. In some examples, the processor may include a skin-sensor at one or more of the electrodes. interfaceThe processor may be configured to detect an impedance level and determine one or more of a start event and an end event based on a change in the impedance level. In some examples, the processor may be configured to determine or confirm the start event and / or the end event based on a motion signal indicative of patient movement. In another example, the processor may be configured to update the start event and the end event criteria based on a measured time of day.
[0075] These and various other similar examples, processes and approaches of the benefits and advantages of these techniques provided herein are described in further detail below.
[0076] Patients at increased risk for sudden cardiac death, unexplained syncope, precursors to heart failure, ejection fractions below 45%, below 35% or other such thresholds deemed of concern by a physician, and other similar patients with conditions of compromised cardiac health may be prescribed specialized cardiac monitoring and therapy devices. The wear compliance monitoring functions and / or processes described herein in connection with a WCD may be applied in a substantially similar manner in a HWD.
[0077] The various monitoring processes described herein are implemented either on the WCD or HWD device itself or on a data processing device, such as a remote server system in communication with or otherwise associated with the WCD or HWD. For example, at least some steps of the processes described herein may be performed on a server, and one or more of the results of such steps may be implemented by the device.
[0078] In one example, a WCD described herein may include a LifeVest® wearable cardioverter defibrillator from ZOLL Medical Corporation (Chelmsford, Massachusetts). As described in further detail below, such a device includes a garment configured to be worn around a patient's torso. The garment may be configured to house various components, such as ECG sensing electrodes, treatment electrodes, one or more accelerometers configured to measure patient motion data, one or more audio and / or vibration sensors configured to record vibration signals, such as the patient's cardiac vibration signals, and one or more RF sensors configured to measure RF-based physiological signals. The components within the garment may be operatively connected to a monitoring device disposed within a separate housing (which may be waterproof, for example, and / or protected from ingress of dust or other physical particles) configured to receive and process signals from the ECG sensing electrodes to determine a condition of the patient's heart and, if necessary, to control the delivery of therapy to the patient via the treatment electrodes.
[0079] The HWD may include two or more adhesive ECG sensing and / or treatment electrodes coupled via a cable to a monitoring device located in a housing similar to that described above for the WCD.
[0080] The monitoring devices of the WCDs described herein are configured to monitor start-of-wear and end-of-wear events as described herein and to calculate wear compliance information based on the monitored events.
[0081] 1A and 1B show various examples of a patient 100 wearing one or more sensors, such as sensing electrodes embedded in a garment, an accelerometer, an audio and / or vibration sensor, an RF sensor, a stretch or pressure sensor, and other similar sensors described herein. An accelerometer is described herein as an example of a motion sensor for illustrative purposes only. In certain implementations, additional motion sensors may be used, such as gyroscopes, magnetic sensors, pressure-based motion sensors, and other similar motion sensors.
[0082] As shown in Figure 1A, a patient may be prescribed a portable medical device, such as a WCD (or HWD for inpatient hospital use). The WCD may include a controller 102 operably connected to one or more sensing electrodes 104 and treatment electrodes 106. Additional details of examples of the controller 102, sensing electrodes 104 and treatment electrodes 106 may be found in the description of Figure 3 below.
[0083] The WCD may also include one or more accelerometers or other motion sensors. As shown in FIG. 1A, the WCD may include three accelerometers 108a, 108b, and 108c (collectively referred to as accelerometers 108) located at various locations on the body of the patient 100. For example, accelerometer 108a may be located on the front of the chest of the patient 100, accelerometer 108b may be located on the patient's back, and accelerometer 108c may be integrated into the controller 102. Each of the accelerometers 108 may be configured to measure motion associated with the patient 100 and output an electrical signal indicative of the direction and magnitude of the patient's motion.
[0084] The number and placement of accelerometers 108 shown in FIGS. 1A and 1B are by way of example only. In certain implementations, the number and location of accelerometers 108 may vary. Additionally, when included in a device such as a WCD, one or more of the accelerometers 108 may be integrated into a component of the WCD. For example, as described above, accelerometer 108c may be integrated into controller 102 of the WCD. Similarly, one or more of accelerometers 108a and 108b may be integrated into one or more components of the WCD. For example, front accelerometer 108a may be integrated into a treatment electrode 106 operably connected to controller 102 and configured to deliver a therapeutic shock to patient 100. In some implementations, accelerometer 108a may be integrated into one of sensing electrodes 104 configured to measure electrical signals generated by patient 100 and indicative of the patient's cardiac activity. Similarly, the accelerometer 108b may be integrated into one or more components of the WCD, such as the connection node, at least one sensing electrode 104, the treatment electrode 106, and other like components of the WCD described herein. Alternatively, or in addition, the one or more accelerometers 108 may be separate components of the WCD.
[0085] In an HWD implementation, the accelerometers may be integrated into one or more of the adhesive ECG sensing and / or treatment electrode patches. For example, a first accelerometer may be integrated into a first adhesive ECG sensing and / or treatment electrode patch and a second accelerometer may be integrated into a second adhesive ECG sensing and / or treatment electrode patch. Additional accelerometers may be located in a controller (similar to controller 102 of the WCD) associated with the HWD.
[0086] In addition to the accelerometer associated with the WCD described above in connection with FIG. 1A, a patient, such as patient 100, may also wear additional sensors. As shown in FIG. 1B, patient 100 may wear a vibration sensor 110 configured to record the patient's bio-vibration signals. For example, vibration sensor 110 may be configured to detect patient vibrations, for example associated with cardiac and pulmonary activity. In a particular implementation, vibration sensor 110 may be configured to detect cardiac vibration values including any one or all of S1, S2, S3, and S4. From these cardiac vibration values, certain cardiac vibration metrics or combination metrics may be calculated, including any one or more of electromechanical activation time (EMAT), left ventricular contraction time (LVST), or percentage left ventricular contraction time (%LVST). In some examples, vibration sensor 110 may include a vibration sensor configured to detect vibrations from the patient's cardiac system and provide an output signal response to the detected cardiac vibration values. The vibration sensor 110 may also include a multi-channel accelerometer, for example a three-channel accelerometer configured to sense motion in each of three orthogonal axes, such that patient movement / posture can be detected and correlated to detected cardiac vibration values. The vibration sensor 110 can transmit information describing the cardiac vibration values, for example to a sensor interface, for subsequent analysis as described below.
[0087] Additionally, the patient 100 may wear an RF sensor 112. For example, the RF sensor 112 may be configured to assess fluid levels and accumulation in the patient's body tissue using RF-based technology. For example, the RF sensor 112 may be configured to measure fluid content in the lungs, typically for diagnosis and follow-up of pulmonary edema or congestion in heart failure patients. Similarly, the RF sensor may be configured to measure thoracic fluid content for the patient. In certain implementations, the RF sensor 112 may include one or more antennas configured to direct radio frequency waves through the patient's tissue and measure an output radio frequency signal in response to the waves passing through the tissue. In certain implementations, the output radio frequency signal includes a parameter indicative of the fluid level in the patient's tissue. The RF sensor 112 may transmit information describing the tissue fluid level to a sensor interface for subsequent analysis, as described below.
[0088] 1A and 1B are shown by way of example only. In actual implementations of the wear compliance monitoring systems and methods described herein, the number and location of sensors may vary based on the type of patient monitoring and / or therapy being performed and various other factors.
[0089] To suitably obtain and output signals indicative of a patient's movement or lack thereof, an accelerometer, such as those described above, may be configured to output one or more output signals indicative of any detected movement or motion. For example, as shown in FIG. 2, accelerometer 200 may be configured to measure movement in three axes: x-axis, y-axis, and z-axis. Depending on the orientation of accelerometer 200 and the output configuration of the accelerometer, each axis may define the movement of the accelerometer in a particular direction.
[0090] 2, the accelerometer 200 may be configured to provide one or more outputs 202. In this example, the outputs 202 may include X-out (i.e., a signal indicative of movement measured along the x-axis), Y-out (i.e., a signal indicative of movement measured along the y-axis), and Z-out (i.e., a signal indicative of movement measured along the z-axis).
[0091] In some implementations, an accelerometer such as accelerometer 200 may be configured to output an electrical signal for each output 202 having one or more controlled characteristics, such as a voltage. For example, accelerometer 200 may be configured to output a signal for each output 202 between 0 and 5 volts. In some examples, the output voltage for each output 202 may be directly proportional to the measured motion on the corresponding axis. For example, if accelerometer 200 is configured to measure acceleration motion as a measure of gravity, the accelerometer may be configured to measure a particular range of g-forces, such as -5g to +5g. In one such example, the output voltage for each output 202 may be directly proportional to the measured g-forces on each axis. For example, if no g-forces are measured (i.e., accelerometer 200 is stationary), each output signal 202 may be measured at 2.5 volts. If motion with a positive g-force along an axis is measured, the voltage of the corresponding output 202 may increase. Conversely, if motion with a negative g-force along an axis is measured, the voltage of the corresponding output 202 may decrease. Based on these outputs 202, a processor, such as those described herein, can determine one or more motion parameters for the patient for use in determining whether the patient is actively wearing the medical device. Additional details regarding such a process are provided below.
[0092] Table 1 below shows sample voltage output levels for an accelerometer configured to measure -5g to +5g and output a signal from 0 to 5 volts. [Table 1] [Table 1]
[0093] The sample g-forces and voltages ranging from those shown in Table 1 above are provided as examples only for illustrative purposes and are not intended to represent the only manner in which the concepts described herein may be implemented. Thus, depending on the design and capabilities of the accelerometer used, the measured g-force range and corresponding output voltage may vary. For example, an output voltage of 10 volts may correspond to a measured g-force of 5 g. For example, an output voltage of 15 volts may correspond to a measured g-force of 5 g. For example, an output voltage of 20 volts may correspond to a measured g-force of 5 g. Similarly, an output voltage of 2 volts may correspond to a measured g-force of 1 g. For example, an output voltage of 4 volts may correspond to a measured g-force of 1 g. For example, an output voltage of 6 volts may correspond to a measured g-force of 1 g.
[0094] 3 illustrates an example component level diagram of a medical device controller 300 included in a wearable medical device, such as a WCD or HWD described herein. The medical device controller 300 is an example of one of the controllers 102 shown in FIGS. 1A and 1B and described above. As shown in FIG. 3, the medical device controller 300 may include a housing 301 configured to house a therapy delivery circuit 302 configured to provide one or more therapeutic shocks to a patient via at least two therapy electrodes 320 (e.g., the therapy electrodes 106 described above), data storage 304, a network interface 306, a user interface 308, at least one rechargeable battery 310 (e.g., in a battery chamber configured for such purpose), a sensor interface 312 (e.g., interfacing with both ECG sensing electrodes 322 (e.g., the sensing electrodes 104 described above), and non-ECG physiological sensors 323 such as vibration sensors (e.g., the vibration sensor 110, lung fluid sensors (e.g., RF sensors 112), infrared and near infrared based pulse oximetry sensors, blood pressure sensors), among others), a cardiac event detector 316, and at least one processor 318.
[0095] In some examples, a patient monitoring medical device may include a medical device controller 300 that includes similar components as those described above, but does not include the therapy delivery circuitry 302 and the therapy electrodes 320 (shown in dotted lines). That is, in certain implementations, the medical device may only include ECG monitoring components and may not provide therapy to the patient. In such implementations, the structure of the patient monitoring medical device may be similar in many respects to the medical device controller 300, but need not include the therapy delivery circuitry 302 and associated therapy electrodes 320.
[0096] As further shown in FIG. 3, the controller 300 may further include an accelerometer interface 330 and a set of accelerometers 332. The accelerometer interface 330 may be operatively coupled to each of the accelerometers 332 and configured to receive one or more outputs from the accelerometers. The accelerometer interface 330 may be further configured to condition the output signals, for example, by converting analog accelerometer signals to digital signals (if analog accelerometers are used), filtering the output signals, and combining the output signals into a combined directional signal (e.g., combining each x-axis signal into a composite x-axis signal, combining each y-axis signal into a composite y-axis signal, and combining each z-axis signal into a composite z-axis signal). In some examples, the accelerometer interface 330 may be configured to filter the signals using a high-pass or band-pass filter to separate the patient's acceleration due to motion from the component of acceleration due to gravity.
[0097] Additionally, the accelerometer interface 330 may configure the output for further processing. For example, the accelerometer interface 330 may be configured to arrange the output of the individual accelerometers 332 as a vector representing the x-axis, y-axis, and z-axis acceleration components received from each accelerometer. The accelerometer interface 330 may be operatively coupled to the processor 318 and configured to transfer the output signals from the accelerometers 332 to the processor for further processing and analysis.
[0098] As mentioned above, one or more of the accelerometers 332 (e.g., accelerometer 108 described above) may be integrated into one or more components of the medical device. For example, as shown in FIG. 3, the accelerometer 332 (e.g., accelerometer 108c described above) may be integrated into the controller 300. In some examples, the accelerometer 332 may be integrated into one or more of the treatment electrodes 320, the sensing electrodes 322, the physiological sensors 323, and into other components of the medical device. If the controller 300 is included in the HWD, the accelerometer may be integrated into an adhesive ECG sensing and / or treatment electrode patch.
[0099] As described herein and discussed above, the present disclosure includes monitoring medical device wear compliance for patients. More specifically, the wear compliance information monitored herein includes an accurate overview of where or how much of a particular period the patient has worn the medical device, and how this compares to the expected wear for the patient, for example, prescribed by a healthcare provider, if the medical device is prescribed. FIG. 4 shows an exemplary reduced component level diagram of a medical device controller 300 including a processor 318 configured to monitor the patient's wear compliance information as described herein. For example, as shown in FIG. 4, the processor 318 may include a wear compliance detector 402. It should be noted that the wear compliance detector 402 is shown as integrated into the processor 318. However, such a design is shown by way of example only. In certain implementations, the wear compliance detector 402 may be integrated as a separate processing component operably coupled to the processor 318. The wear compliance detector 402 may be implemented as a dedicated microprocessor and associated circuitry located on a printed circuit board (PCB) along with other components described herein. When implemented in a dedicated microprocessor or integrated into the processor 318, the wear compliance detector 402 may be based on a set of processor-readable instructions configured to be executed by the dedicated microprocessor or processor 318. For example, these instructions may be implemented in a programming language such as C, C++, assembly language, machine code, HDL, or VHDL. In an example, the dedicated microprocessor may be an Intel-based microprocessor, such as an X86 microprocessor, or a Motorola 68020 microprocessor, each of which may use a different set of binary code and / or instructions for similar functions. The dedicated microprocessor or processor 318 may be implemented in any of the manners shown in FIGS. 5-7. B The present invention may be configured to implement the attachment start event detection and attachment end event detection described in.
[0100] As further shown in FIG. 4, the mounting compliance detector 402 may include a start event detector 404 and an end event detector 406. As mentioned above, the mounting compliance detector 402 may be a dedicated microprocessor and associated circuitry located on a PCB along with other components described herein. In implementations, a first microprocessor may be implemented as the start event detector 404 and a second microprocessor may be implemented as the end event detector 404. In some implementations, both the start event detector 404 and the end event detector 406 may be implemented in the same microprocessor as described above. The start event detector 404 and / or the end event detector 406, when implemented in a dedicated microprocessor or integrated into the processor 318, may be based on a set of processor-readable instructions configured to be executed by the dedicated microprocessor or the processor 318. For example, these instructions may be implemented in a programming language such as C, C++, assembly language, machine code, HDL, or VHDL. In an example, the special purpose microprocessor may be an Intel-based microprocessor, such as an X86 microprocessor, or a Motorola 68020 microprocessor, each of which may use a different set of binary code and / or instructions for similar functions. The special purpose microprocessor or processor 318 is shown in FIGS. B The present invention may implement the attachment start event detection and / or attachment end event detection described in.
[0101] As described above, when the patient is wearing the medical device, a wear start event may be determined based on an analysis of signals received from one or more of the sensors described herein. For example, based on monitoring of the signals output by the ECG sensing electrodes and the signals output by the accelerometer 332, the start event detector 404 may determine a start event indicating that the patient is wearing or otherwise wearing the medical device. Similarly, the end event detector 406 may determine an end event from the monitoring indicating that the patient has turned off, removed, or otherwise stopped the medical device. Based on the measured start and end events, the wear compliance detector 402 and / or the processor 318 may determine wear compliance information for the patient. Exemplary operations performed by the processor 318, the wear compliance detector 402, and the start event detector 404 and end event detector 406 are illustrated in FIG. 5 through FIG. 7. B This will be explained in more detail in the following description.
[0102] 5 shows a sample process flow for monitoring and outputting patient wear compliance information as described herein. For example, the sample process 500 shown in FIG. 5 may be implemented by a processor, such as the processor 318 of the medical device controller 300 described above.
[0103] 5, the processor can receive (502) one or more sensor signals from one or more patient sensors. For example, the sensor signals can include signals from one or more physiological sensors, such as ECG sensors, RF-based physiological sensors, bioacoustic sensors, and other similar sensors. The sensor signals can include signals from one or more motion sensors, such as accelerometers. signal In some examples, the signals may also include electrical signals from one or more sensors from which various electrical parameters, such as impedance measurements, may be measured.
[0104] The processor can monitor (504) the received signals for an indication of a wear compliance initiation event. As described herein, a wear compliance initiation event, or simply an initiation event, is a change in one or more monitored signals that indicates a transition from a state in which the patient is not wearing the wearable medical device to a state in which the patient is wearing the wearable medical device. For example, as described herein, a patient is deemed to be wearing the wearable medical device if a predetermined threshold based on ECG signal information is met. By way of example, the following is an exemplary implementation of such functionality reproduced as a sample functional specification that lists various functions and / or requirements for implementation by a processor of, for example, a medical device controller. Find the QRS complex based on dual criteria of the amplitude and duration of the QRS complex. In one example, the Pan Tompkins algorithm is used to detect the QRS. Start the wearing time (e.g., "WearTimeStart") after a predefined time, e.g., called "WearTimePreOnPeriod" (e.g., 5 seconds of QRS signal or other predefined value, or a dynamically changing value). Dynamic variation of WearTimePreOnPeriod duration: If the signal is noisy (e.g., as indicated by the variable ECGnoiseFlagMask), the predefined time may be extended, for example by 10 seconds, to allow more ECG samples to be collected. ● Dynamic change of a predefined duration WearTimePreOnPeriod: if a QRS sample is detected for a predefined portion of the WearTimePreOnPeriod duration. For example, the predefined portion can be set to 80%. This means that if the double criterion is met for 80% of the WearTimePreOnPeriod, compliance tracking is started (WearTimeStart). Otherwise, the WearTimePreOnPeriod duration is extended by an additional period, for example 3 seconds. The above dynamic checks are then repeated for the extended WearTimePreOnPeriod duration. WearTimePreOnPeriod is reset when the total duration reaches a predefined maximum value (for example 15 seconds).
[0105] In certain implementations, the processor may be configured to receive a user input indicating that the patient has donned the wearable medical device. Depending on the implementation, the processor may monitor one or more additional signals to verify that the patient has donned the medical device described herein.
[0106] During monitoring (504), the processor may determine (506) whether a start event has occurred. If the processor determines (506) that a start event has not occurred, the processor may continue monitoring (504) the electrical signals for the start event. Conversely, if the processor determines (506) that a start event has occurred, the processor may record the start event and monitor (508) the electrical signals for a wear compliance end event. For example, as described herein, a wear compliance end event, or simply an end event, is a change in one or more monitored signals that indicates a transition from a state in which the patient is wearing the wearable medical device to a state in which the patient is not wearing the wearable medical device.
[0107] As further shown in FIG. 5, during monitoring (508), the processor can determine (510) whether an end event has occurred. If the processor determines (510) that an end event has not occurred, the processor can continue to monitor the electrical signal for the end event. Conversely, if the processor determines (510) that an end event has occurred, the processor can determine (512) wear compliance information for a period between the start event and the end event. The processor can then output (514) the wear compliance information, for example, to a remote server for storage and analysis. Additionally, the processor can be configured to output (514) at least a portion of the wear compliance information in a notification to the patient, the patient's care provider, and the prescribing physician. In one such example, the output notification can include any recorded changes in the patient's wear compliance, for example, exceeding a compliance change threshold. For example, if the patient's percentage of wear compliance changes by more than a certain amount in a day (e.g., 5%-15% over consecutive days), the notification can include information about the change in wear compliance.
[0108] To appropriately record the compliance information, the processor can record the event information in a table or other similar data structure. For example, for each start and end event measured during a particular period, the processor can record the associated occurrence time associated with the event. The processor can further calculate and record the total wear compliance time by calculating the time between the start event and the subsequent end event. Similarly, the processor can further calculate and record the total wear non-compliance time by calculating the time between the end event and the subsequent start event. When calculating the wear compliance on a daily basis, the processor can record the end event at midnight as a time transition from one day to another, and immediately record the start event at midnight as well. Such recording provides a multi-day boundary without recording every non-compliance period.
[0109] Table 2 below shows a sample data structure for recording wear compliance information as described herein. As shown, Table 2 includes wear compliance information calculated daily, and therefore includes a pair of end and start events at midnight each day. Table 2 also includes the total time between events (segments in time) and the total overall daily wear measurements (cumulative daily on time, cumulative daily off time, and total daily compliance %). [Table 2] [Table 2]
[0110] As described above, the processor may be configured to monitor one or more electrical signals for the occurrence of a starting event. However, in certain implementations, the processor may be configured to specifically monitor and rely on a change in the signal for an indication of a starting event. For example, the process 600 shown in FIG. 6A includes a more detailed process flow for monitoring (504) a sensor signal and determining (506) whether a starting event has occurred. In certain implementations, the sensor signal may include a combination of signals, such as a physiological signal and a motion signal. The process 620 shown in FIG. 6B includes a more specific implementation in which one or more physiological signals of the patient are monitored for an indication of a starting event. The process 640 shown in FIG. 6C includes a more specific implementation in which one or more motion signals are monitored for an indication of a starting event. The process 660 shown in FIG. 6D includes a more specific implementation in which one or more skin-sensor interface impedance levels are monitored for an indication of a starting event.
[0111] As mentioned above, the process 600 shown in FIG. 6A illustrates a more detailed process flow for monitoring (504) and determining (506) as shown in FIG. 5 and described above. As shown in FIG. 6A, a processor can monitor (602) a received signal. The processor can identify (604) any changes in the received signal that may indicate the occurrence of a start event. The processor can determine (606) whether the changes are indicative of a start event, for example, by comparing the changes in the received signal against one or more start event criteria. Examples of specific start event criteria are described in the following description of FIG. 6B and FIG. 6C.
[0112] As further shown in FIG. 6A, if the processor determines (606) that the change in the received signal is not indicative of a start event, the processor may continue to search for and identify (604) the change in the received electrical signal. However, if the processor determines (606) that the change in the received signal is indicative of a start event, the processor may continue to monitor (608) for the change. For example, depending on the type of start event criteria used to determine the occurrence of a start event, the change in the electrical signal must be maintained or observed for a certain period of time, such as, for example, 5 seconds. The processor may determine (610) whether the potential start event is a confirmed start event based on the extended monitoring for the change. If the processor does not determine (610) that the potential start event is a confirmed start event, the processor may continue to search for and identify (604) the change in the received signal. Conversely, if the processor determines (610) that the potential start event is a confirmed start event, the processor may generate (612) a confirmation of the start event and record the start event in a data structure, such as, for example, Table 2, discussed above.
[0113] In some examples, the wearable medical device may include a user interface that provides the patient with options to input various information. For example, the user interface may provide the user with an input indicating that the user is wearing the wearable medical device. In response to such an input, the processor may identify and record the initiating event using a process similar to that shown in FIG. 6A by analyzing at least one of the one or more physiological and / or movement signals. In some examples, the processor may record the initiating event based solely on the patient's input.
[0114] As mentioned above, the process 600 shown in FIG. 6A relates to detecting an initiating event by generally monitoring received signals from one or more sensors described herein. The process 620 shown in FIG. 6B illustrates a more detailed process flow for monitoring (504) and determining (506) as shown in FIG. 5 and described above, where physiological information about a patient is monitored and analyzed to determine an initiating event occurrence, for example. As shown in FIG. 6B, the processor can receive (622) signals from one or more physiological sensors and associated circuitry configured to output one or more electrical signals indicative of the patient's cardiac activity, such as, for example, an ECG sensor described herein. The processor can derive (624) one or more physiological metrics from the received physiological signals. For example, physiological metrics may include, for example, heart rate (such as mean, median, mode, or other statistical measure of heart rate, and / or maximum, minimum, resting, pre-exercise and post-exercise heart rate values and / or ranges), heart rate variability metrics, premature ventricular contraction (PVC) burden or count, atrial fibrillation burden metrics, ECG metrics including pauses, heart rate turbulence, QRS height, QRS width, changes in size or shape of the ECG information morphology, cosine RT, artificial pacing, QT interval, QT variability, T wave width, T wave, T wave variability, and ST segment changes. ECG metrics are described herein by way of example only, and additional physiological metrics may be processed by this process, such as those described, for example, in the detailed description of FIG. 3 below.
[0115] As further shown in FIG. 6B, the processor can determine (626) whether the derived metrics are indicative of an onset event, for example, by comparing changes and / or patterns of metrics in the received signal against one or more onset event criteria. For example, one onset event criterion that may be indicative of an onset event is an ECG signal determined to be valid for a particular period of time. In a particular implementation, at least one ECG parameter derived from the ECG signal should meet a validity threshold for the ECG signal to be determined to be valid. The processor can use exemplary criteria to meet the validity threshold described in the following examples. For example, the ECG parameters can include a set of at least five consecutive R-peaks having an R-peak amplitude that meets an R-peak amplitude threshold. For example, the R-peak amplitude threshold can be between about 0.75 millivolts and 1.50 millivolts. In some examples, the R-peak amplitude threshold can be selected from between about 0.50 millivolts and about 1.0 millivolts. In another example, the at least one ECG parameter can include a QRS complex width. In one such example, the validity threshold for a valid ECG signal may include five or more consecutive QRS complexes having a width of approximately 0.05 seconds to 0.15 seconds. By way of illustration, the following is an exemplary sample functional specification listing various functions and / or requirements for implementation by a processor of a medical device. Find the QRS complex based on dual criteria of the amplitude and duration of the QRS complex. In one example, the Pan Tompkins algorithm is used to detect the QRS complex. After a predefined time, e.g., WearTimePreOnPeriod (e.g., 5 seconds of QRS signal or other predefined value, or a dynamically changing value), start the wearing time (WearTimeStart) (validity criteria are met). The following are options for determining when the validity criteria are met: A set of at least five consecutive R-peaks with R-peak amplitudes that meet the R-peak amplitude threshold. The R peak amplitude threshold may be between about 0.75 millivolts and 1.50 millivolts. Optionally, the R peak amplitude threshold may be selected from between about 0.50 millivolts and about 1.0 millivolts. o The QRS complex width may be set to a user-defined value: 5 or more consecutive QRS complexes with a width of approximately 0.05 seconds to 0.15 seconds.
[0116] As further shown in FIG. 6B, if the processor determines (626) that the derived metrics are not indicative of a start event (e.g., the validity criteria are not met), the processor may continue to derive (624) metrics from the received physiological signal. However, if the processor determines (626) that the derived metrics in the received physiological signal are indicative of a start event (e.g., the validity criteria are met), the processor may continue to monitor (628) the derived metrics. As described above, in this example, to satisfy the exemplary set of validity criteria, five consecutive R-peak amplitudes should exceed the R-peak amplitude threshold. The processor may determine (630) whether the derived metrics are indicative of a confirmed start event. If the processor does not determine (630) that the potential start event is a confirmed start event, the processor may continue to derive metrics based on the received physiological signal. Conversely, if the processor determines (630) that the potential start event is a confirmed start event, the processor may generate (632) a confirmation of the start event and record the start event in a data structure such as Table 2 above.
[0117] Process 640 shown in FIG. 6C illustrates a more detailed process flow for monitoring (504) and determining (506) as shown in FIG. 5 and described above, where motion information about a patient is monitored and analyzed to determine the occurrence of an initiating event, for example. As shown in FIG. 6C, the processor can receive (642) signals from one or more motion sensors and associated circuitry configured to output one or more electrical signals indicative of the patient's physical activity or movement, such as, for example, an accelerometer as described herein. The processor can identify (644) one or more features in the motion signal indicative of a particular movement of the patient. For example, the motion signal can provide an indication that the patient is walking, running, climbing stairs, sitting up, standing up, sitting, lying down, and performing other similar physical activities.
[0118] As further shown in FIG. 6C, the processor can determine (646) whether the identified motion characteristics indicate an initiating event, for example, by determining whether the motion characteristics are consistent with the movement of the wearable medical device when worn by the patient. For example, the output of the accelerometer can be compared against past motion information for the patient. If the motion characteristics are consistent with the past motion information, the patient can be deemed to be wearing the wearable medical device.
[0119] As further shown in FIG. 6C , if the processor determines (646) that the identified features in the motion signal are not indicative of a start event, the processor may continue to identify (644) features in the received motion signal. However, if the processor determines (646) that the identified features in the motion signal are indicative of a start event, the processor may continue to monitor (648) the motion signal. For example, to be considered valid motion, the motion signal may need to indicate that the patient and the wearable medical device are in agreement over a period of time, such as five seconds. The processor may determine (650) whether the motion signal and the identified features in the motion signal indicate a confirmation of a start event. If the processor does not determine (650) that the potential start event is a confirmed start event, the processor may continue to identify (644) features in the received motion signal. Conversely, if the processor determines (650) that the potential start event is a confirmed start event, the processor may generate (652) a confirmation of the start event and record the start event in a data structure, such as Table 2, discussed above.
[0120] In addition to the physiological and motion signal analyses described above, additional signal analyses may be performed by the processor to determine an initiating event. For example, the processor may measure the skin-sensor interface impedance level for each of the sensors coupled to the patient's body. When the medical device is initially configured or otherwise programmed, the acceptable impedance range may be selected by a user, such as a device engineer. For example, the acceptable impedance range may be selected by design to be about 20 ohms to about 250 ohms, about 20 ohms to about 10 kilohms, about 20 ohms to about 20 kilohms, about 250 ohms to about 1 kilohms, about 1 kilohms to about 20 kilohms. Other acceptable impedance ranges may be implemented during the design phase, programming phase, testing phase, and other similar evaluation periods shown in the following exemplary implementation of sample pseudocode for a processor of a medical device controller. ●Measure skin-electrode interface impedance. ● Start wear time (e.g., WearTimeStart) after a predefined period of time, e.g., WearTimePreOnPeriod (e.g., 5 seconds), during which impedance values remain within 5% of a user-defined value (validity criteria are met). Below are options for determining when validity criteria are met: The measured skin-electrode interface impedance is within a user-defined impedance range of about 20 ohms to about 250 ohms. The measured skin-electrode interface impedance is within a user-defined impedance range of about 20 ohms to about 10 kiloohms. The measured skin-electrode interface impedance is within a user-defined impedance range of about 20 ohms to about 20 kiloohms. The measured skin-electrode interface impedance is within a user-defined impedance range of about 250 ohms to about 1 kiloohm; or The measured skin-electrode interface impedance is within a user-defined impedance range of about 1 kilohm to about 20 kilohm.
[0121] Based on the measurement of the change in impedance level, the processor can determine whether an initiating event has occurred. For example, in one implementation depending on the particular design choice, when the sensor is not in contact with the patient's skin, the impedance may be greater than 10 kilohms. When the sensor is in contact with the patient's skin, the impedance may drop significantly. Thus, when the processor measures a skin-sensor interface impedance level of about 20 ohms to about 250 ohms, it may determine that the sensor is in contact with the patient's skin and that an initiating event has occurred. In some examples, the impedance level for detecting an initiating event may be about 10 ohms to about 300 ohms. In an actual implementation, the impedance level may be determined based on the material used to construct the sensor and the location of the placement of the sensor on the patient. For example, depending on the type of sensor used, the impedance level during the initiating event may be between an acceptable impedance range, for example, about 250 ohms to about 1 kilohms or about 1 kilohms to about 20 kilohms.
[0122] More specifically, Figure 6D illustrates a sample process flow 660 for monitoring (504) and determining (506) as shown in Figure 5 and described above, where a skin-sensor interface impedance level is monitored and analyzed for one or more sensors coupled to the patient's body, e.g., to determine an initiation event occurrence. As shown in Figure 6D, the processor can receive (662) electrical signals from, for example, one or more sensors and associated circuitry contained therein, such as, for example, conditioning and / or skin-sensor interface modeling circuitry described in U.S. Patent Application No. 15 / 381,206, entitled "Electrode Fall-Off Detection," filed December 16, 2016, the contents of which are incorporated herein by reference in their entirety. Based on the received electrical signals, the processor can determine (664) a skin-sensor interface impedance level for each of the one or more sensors coupled to the patient's body.
[0123] As further shown in FIG. 6D, the processor may further determine (666) whether the skin-sensor interface impedance level of the one or more sensors indicates an initiating event, for example, by determining whether the current skin-sensor interface impedance level of one or more of the sensors indicates that the sensor is currently in contact with the patient's skin. For example, as described above, if the current skin-sensor interface impedance level of the sensor is between about 20 ohms and about 250 ohms, the processor may determine (666) that the sensor is in contact with the patient's skin and an initiating event may have occurred. Conversely, if the current skin-sensor interface impedance level of the sensor is outside of the impedance range and / or exceeds a particular impedance value, such as 10 kilohms or 20 kilohms, the processor may determine (666) that the sensor is not in contact with the patient's skin and an initiating event may not have occurred. In one such example, the processor may continue to determine (664) updated skin-sensor interface impedance levels for each of the one or more sensors.
[0124] As further shown in FIG. 6D , if the processor determines (666) that the current skin-sensor interface impedance level indicates a potential initiating event, the processor may continue to monitor (668) the skin-sensor interface impedance level. For example, the processor may continue to monitor the skin-sensor interface impedance level for a set period of time, such as 2 seconds, 5 seconds, 10 seconds, 15 seconds, 20 seconds, and / or 30 seconds. During the set period of time, the processor may determine (670) whether the skin-sensor interface impedance level of the one or more sensors, and any changes in the monitored skin-sensor interface impedance level during the set period of time, indicate confirmation of an initiating event. For example, if the monitored skin-sensor interface impedance level of each of the one or more sensors remains within a range of about 20 ohms to about 250 ohms throughout the set period of time, the processor may determine (670) and confirm that an initiating event has occurred. Conversely ... that an initiating event has occurred. interface If the impedance level is outside the impedance range for the set period of time, the processor may determine (670) that a confirmed initiating event has not occurred and may continue to determine (664) the skin-sensor interface impedance level as described above. If the processor determines (670) that the potential initiating event is a confirmed initiating event, the processor may generate (672) confirmation of the initiating event and record the initiating event in a data structure, such as Table 2, described above.
[0125] Process 700 shown in Figure 7A illustrates a more detailed process flow for monitoring (508) and determining (510) an end event as shown in Figure 5 and described above. As shown in Figure 7A, a processor can monitor (702) a received signal. The processor can identify (704) any changes in the received signal that may indicate the occurrence of an end event. The processor can determine (706) whether the change is indicative of an end event, for example, by comparing the change in the received signal against one or more end event criteria.
[0126] As further shown in FIG. 7A, if the processor determines (706) that the change in the received signal is not indicative of an end event, the processor may continue to search for and identify (704) the change in the received electrical signal. However, if the processor determines (706) that the change in the received signal is indicative of an end event, the processor may continue to monitor (708) for the change. For example, depending on the type of end event criteria used to determine the occurrence of an end event, the change in the electrical signal must be maintained or observed for a certain period of time, such as, for example, 5 seconds. The processor may determine (710) whether the potential end event is a confirmed end event based on the extended monitoring for the change. If the processor does not determine (710) that the potential end event is a confirmed end event, the processor may continue to search for and identify (704) the change in the received signal. Conversely, if the processor determines (710) that the potential end event is a confirmed end event, the processor may generate (712) a confirmation of the end event and record the end event in a data structure, such as, for example, Table 2, discussed above.
[0127] In the particular example of the process 700 shown in FIG. 7A, the criteria for determining the termination event may vary. For example, if a valid ECG signal transitions to an invalid ECG signal indicating removal of the wearable medical device, the processor may record a termination event. Similarly, if the processor detects a change in the skin-sensor interface impedance level that exceeds the impedance threshold and indicates removal of the sensor from the patient's skin, or if the skin-sensor interface impedance level is no longer within the acceptable impedance range, the processor may record a termination event. In some examples, the impedance threshold may include at least one of 10 kilohms, 20 kilohms, 100 kilohms, 1 megahms, 2 megahms, 5 megahms, and 10 megahms. In some examples, if the processor stops receiving signals from the one or more motion sensors, the processor may determine that the one or more motion sensors and associated circuitry are disconnected and record a termination event accordingly. The processor may further determine that a change in the one or more motion signals indicates that the patient has removed the wearable medical device and record a termination event accordingly. In some examples, the processor may receive an input from the patient indicating that the patient has removed the wearable medical device. The processor may determine that the patient has removed the wearable medical device based on changes in the one or more physiological signals and the one or more movement signals and record an end event accordingly.
[0128] In certain implementations, the determination of the initiating event may be based on a combination of signals. As such, the examples shown in FIG. 6B, FIG. 6C, and FIG. 6D are provided by way of example only. For example, as shown in FIG. 6A, the processor may be configured to simultaneously monitor both one or more physiological signals and one or more motion signals to determine whether a starting event has occurred or not. For example, the processor may determine a valid ECG signal as described in FIG. 6B. However, before determining that a starting event has occurred, the processor may further analyze one or more motion signals as described in FIG. 6C to verify that the one or more motion signals also provide an indication of a starting event. Conversely, if the processor does not detect the indicated movement in the motion signals or detects a high level of noise in the motion signals, the processor may record a starting event based solely on the analysis of the one or more physiological signals. Similarly, the processor may further monitor a skin-sensor interface impedance level as described in FIG. 6D simultaneously with monitoring the physiological signals and / or the motion signals to determine and confirm a starting event. Conversely, a skin-sensor interface impedance level indicating potential noise and / or other similar interference in the one or more sensors may be detected. interface If the processor determines a change in impedance level, the processor can rely on further analysis of one or more physiological and / or motion signals to identify a starting event as described herein. Similarly, the processor can analyze different types and combinations of signals before identifying an ending event as shown in FIG.
[0129] However, in certain examples, additional variables may affect the reliability of one or more signals. For example, at certain times of day, the patient's movement may be restricted. For example, at night, the patient's movement may be restricted, and therefore the criteria used to determine the start and end events may be adjusted accordingly. In one such example, the processor may be configured to record start and / or end events based on one or more physiological signals, one or more movement signals, and the time of day.
[0130] The process 720 shown in FIG. 7B includes consideration of time of day and adjusts the event criteria accordingly. As shown in FIG. 7B, the processor can monitor (722) the received signal. The processor can identify (724) any changes in the received signal that may indicate the occurrence of either a start or end event. Additionally, the processor can determine (726) the time of day and compare it against, for example, past patient activity data or other similar set information that may indicate whether the patient is typically active or inactive at that time. Based on the determined time of day and the patient activity information, the processor can adjust (728) the event criteria used to determine the start or end event occurrence. For example, if the time of day indicates that the patient is generally inactive, the processor can reduce reliance on one or more motion signals when determining the event occurrence, or ignore the one or more motion signals entirely. Conversely, if the determined time of day indicates that the patient is generally active, the processor can rely on a combination of both one or more physiological signals and one or more motion signals when determining the event occurrence.
[0131] As further shown in FIG. 7B , the processor can determine (730) whether the change in the received signal is indicative of an event, for example, by comparing the change in the received signal against one or more event criteria, such as the adjusted event criteria determined above. If the processor determines (730) that the change in the received signal is not indicative of an event, the processor can continue searching for and identifying (724) the change in the received electrical signal. However, if the processor determines (730) that the change in the received signal is indicative of an event, the processor can continue monitoring (732) for the change, in some examples using the adjusted event criteria. The processor can determine (734) whether the potential event is a confirmed event based on the extended monitoring for the change. If the processor does not determine (734) that the potential event is a confirmed event, the processor can continue searching for and identifying (724) the change in the received signal. Conversely, if the processor determines (734) that the potential event is a confirmed event, the processor can generate (736) a confirmation of the event and record the event in a data structure, such as, for example, Table 2, discussed above. In certain implementations, the processor may be further configured to provide, in the data structure, an indication that the event was recorded using the adjusted event criteria based on a time of the event occurrence.
[0132] In the above description of FIG. 5 through FIG. 7B, it is noted that the start and end event detection and confirmation may be performed by monitoring one or more received electrical signals for a physiological signal, such as an ECG signal. Based on the validity of the ECG signal, the processor described herein may determine whether a start or end event has occurred. However, during normal operation of the wearable medical device described herein, the processor may also continuously monitor the patient for cardiac arrhythmias. In certain implementations, if a cardiac arrhythmia occurs, the processor may interpret the resulting ECG as invalid. For example, if a patient experiences ventricular fibrillation (VF), the QRS complex timing detected in the patient's ECG signal may be altered such that the ECG signal is considered invalid for purposes of the determination of wearing compliance described herein. In one such example, the processor may be programmed or otherwise adjusted to prioritize arrhythmia detection over start and / or end event detection, and to ignore or otherwise stop start and / or end event detection until arrhythmia detection stops (e.g., no arrhythmia is detected) or the patient receives treatment and returns to normal (or is within an acceptable range of normal cardiac activity).
[0133] As described herein, the wearable medical device may be operably connected to one or more additional remotely located computing devices, such as a remote server. For example, FIG. 8 illustrates a sample network 800 in which a wearable medical device (e.g., a medical device including the medical device controller 300 shown in FIG. 3) may be operably connected to a remote server. As described above in connection with FIG. 3, the wearable medical device controller 300 may include a network interface 306 for transmitting data over a wireless link, such as a Bluetooth® wireless link, a broadband cellular link, or a Wi-Fi® communication link based on the IEEE 802.11 standard (e.g., via a “hot spot” or other base station or intermediate device). As shown in FIG. 8, the physician computer 802 and the wearable medical device 804 may be operably connected to a monitoring server 808 through a network 806. In certain implementations, the wearable medical device 804 may collect information related to the patient while worn, such as various patient metrics and parameters described herein. For example, the wearable medical device 804 can collect physiological and ECG data, RF-based measurement information, and wear compliance information associated with the patient over the period of time the patient is prescribed the wearable medical device. The wearable medical device 804 can also collect accelerometer data indicative of motion information associated with the patient, such as the number of steps taken during a period of time, such as 30 minutes, 1 hour, 2 hours, 6 hours, or 1 day, and duration information associated with periods of activity, such as how often and for how long the patient is exercising. Depending on the connection to the network 806 and the programming of the wearable medical device 804, the wearable medical device can be configured to regularly transmit the collected information to the monitoring server 808 for storage and further processing and analysis. The network 806 can be a private and secure network configured to enable intercommunication between authorized devices 804, the computer 802, and the server 808.For example, the private network may be implemented as a Virtual Private Network (VPN) that may be formed using a number of encrypted communication techniques, including the creation of secure communication channels (called "tunnels") within the public network. As an example, the device 804 or computer 802 may implement a temporary or permanent dedicated communications software application to securely communicate with the server 808 through such tunnels. The dedicated communications software application encrypts and transmits messages to the server 808 and from the server 808. Rame Some types of such dedicated communications software applications may embed encrypted messages into formatted data packets so that the encrypted messages are unreadable outside the secure communications channel.
[0134] When prescribing a wearable medical device as described herein, the prescribing physician or health care provider may be provided with one or more options for adjusting various settings or parameters of the wear compliance monitoring process. For example, FIG. 9 shows a sample diagram of a user interface screen 900 that may be accessed and utilized by a physician and / or other HCP to modify one or more wear compliance monitoring settings for a particular patient. A physician may interact with the user interface screen 900 by accessing an application, such as a browser or gateway application, executed by a processor integrated into the physician computer 802 described above.
[0135] As shown in FIG. 9 , the user interface screen 900 includes user interface controls 902, 904, 906, 908, and 910. In some examples, the user interface screen 900 provides access to patient-specific information, such as the patient's name, an identifier associated with the patient, and information about the prescribed device, such as a device identifier. In certain implementations, the patient identifier may be a medical record number associated with the patient, an insured person number associated with the patient, a number that directly identifies the patient, such as a social security number, or another similar identification number. Based on the patient-specific information, the processor can access the patient's medical record. Based on information contained in the medical record, such as patient status information, past patient information, demographic information, and rehabilitation baseline information, the processor can generate a set of default wear compliance monitoring parameters without additional information from a physician.
[0136] In some examples, the processor can display options to the physician for customizing the wear compliance monitoring parameters. For example, the user interface control 902 can provide access to specific information related to the minimum wear compliance monitoring parameters. The user interface control 902 can include one or more additional controls 903 that can include one or more user interactive or selectable inputs for receiving additional information related to the minimum wear compliance monitoring parameters. For example, the additional controls 903 can include a total wear time field, a number of approved removal periods, and a maximum removal time allowed per removal period. For example, as shown in FIG. 9, the additional controls 903 include a combination of text fields and drop-down menus. However, this specific implementation of the additional controls 903 is provided by way of example only. In this example, the additional controls 903 receive physician inputs of a total of 23 hours of wear per day, two removal periods allowed, and a maximum time per removal period of 30 minutes. The specific inputs and sample numbers included in the additional controls 903 are provided by way of example only.
[0137] As described above, the user interface screen 900 may further include a user interface control 904. The user interface control 904 may provide access to specific information related to the target wear compliance monitoring parameters. For example, the target wear compliance monitoring parameters may include goals set by a physician that the patient should achieve during the time the wearable medical device is prescribed to the patient. The user interface control 904 may include one or more additional controls 905 that may include one or more user interactive or selectable inputs for receiving additional information related to the target wear compliance monitoring parameters. For example, the additional control 905 may include a total wear time field, a number of approved removal periods, and a maximum removal time allowed per removal period. For example, as shown in FIG. 9, the additional control 905 includes a combination of a text field and a drop-down menu. However, this specific implementation of the additional control 905 is shown by way of example only. In this example, the additional control 905 receives a physician's input of a total of 23.5 hours of wear per day, one removal period allowed, and a maximum time per removal period of 30 minutes. However, it should be noted that the specific inputs and sample numbers included in additional controls 905 are provided as examples only.
[0138] As mentioned above, the user interface screen 900 may further include user interface controls 906. The user interface controls 906 can provide access to specific information related to the start and end event detection criteria described herein. The user interface controls 906 may include one or more additional controls 907. In some examples, the one or more additional controls 907 may include one or more user interactive or selectable inputs for receiving additional information related to the start and end event detection criteria. For example, the additional controls 907 may include a user selectable input for using default criteria or a user selectable input for using custom criteria.
[0139] As described above, the user interface screen 900 may further include user interface controls 908. The user interface controls 908 may provide access to specific information related to alert criteria for alerting one or more persons, such as a physician, another HCP, a patient, and other similar persons, of the patient's wear compliance information. The user interface controls 908 may include one or more additional controls 909. In some examples, the one or more additional controls 909 may include one or more user interactive or selectable inputs for indicating which criteria should be met before an alert is generated. For example, the additional controls 909 include a set of user selectable inputs for receiving an alert daily that the minimum compliance information is not met, receiving an alert after a set number of consecutive days that the minimum compliance information is not met, receiving an alert daily that the target compliance information is not met, receiving an alert after a set number of consecutive days that the target compliance information is not met, and receiving an alert after a set number of consecutive days that the target compliance information is met. The specific inputs in the additional controls 909 include a combination of user selectable inputs and customizable fields that the physician may use to provide additional information, such as the number of days shown in Figure 9. However, the number, placement and labels of the additional controls 909 shown in Figure 9 are by way of example only.
[0140] 9, the user interface control 910 includes a set of selectable buttons. In response to receiving a selection of the "Submit" button, the processor can update the set of wear compliance parameters for the patient. In response to receiving a selection of the "Clear" button, the processor can delete existing selections and / or entered information from the user interface screen 900. In response to receiving a selection of the "Cancel" button, the processor can abort the update of the wear compliance parameters described above.
[0141] As described herein, wear compliance information generated by the wearable medical device may be transmitted to a remote server for further processing and access, for example for review by the patient's physician. Additionally, the wear compliance information may be displayed to the patient on a user interface integrated into the wearable medical device (e.g., user interface 308 shown in FIG. 3 and described herein) or via a personal computing device assigned to or otherwise accessed by the patient, such as a smartphone.
[0142] In certain implementations, the wear compliance information may be displayed to the care provider via a network-based portal, such as a physician's web portal. For example, the portal may be accessed on a variety of electronic devices, such as a portable computing device assigned to or otherwise accessed by the physician, or a computer, such as the physician's computer 802 shown in FIG. 8 and described herein. It is desirable to provide the physician with relevant information regarding the patient's wear compliance in an easy-to-understand format. Additionally, as described above, the physician may wish to set alerts regarding deviations by the patient from minimum or target wear compliance guidelines. FIGS. 10A-10C illustrate one or more interfaces for providing wear compliance information to the physician, including, for example, a summary screen (or portion of a screen) where key compliance data is displayed for quick viewing, and a more detailed screen (or portion of a screen) where more detailed information underlying the key compliance data displayed on the summary screen is present.
[0143] For example, FIG. 10A shows a sample user interface screen 1000 including a sample set of fictitious patient data for demonstration purposes only. The user interface screen 1000 may include a set of data, such as patient information, login information, and other similar overall data. The user interface screen 1000 may further include a set of tabs 1002 including more specific summary information about the patient. As shown in FIG. 10A, the compliance tab has been selected and a set of summary wear compliance data is displayed. For example, the summary wear compliance information includes reporting period information, reporting range information, and patient usage range information. As shown in FIG. 10A, the reporting period information includes information about patient usage days, total patient usage information, average daily patient usage information, and alert days. Similarly, as shown in FIG. 10A, the reporting range information includes a user selectable input for adjusting the total period shown on the user interface screen 1000. The patient usage range includes a user selectable input for adjusting how additional detailed information is displayed on the user interface screen 1000.
[0144] As further shown in FIG. 10A, the user interface screen 1000 may include a details portion 1004 that includes more specific wear compliance information for the patient. The user selectable input for patient usage extent has been set to view by actual usage hours. In accordance with this user selection, the data included in the details portion 1004 is formatted based on total usage hours per day organized in a bar graph 1006. Hours of the day are provided on the y-axis and dates are provided on the x-axis. As shown in FIG. 10A, the bar graph 1006 may further include an indication of patient wear compliance compared to patient wear non-compliance.
[0145] It should be noted that the presentation of information in the details portion 1004 is shown as a bar graph 1006 in FIG. 10A for example only. Upon receiving an indication that the user-selectable input for the patient usage range has changed, the processor that generated the user interface screen 1000 can update the details portion 1004 accordingly. For example, as shown in FIG. 10B, the user-selectable input for the patient usage range has changed to "View by Total Usage Time" and the details portion 1004 can be updated to include a line graph 1008. As shown in FIG. 10B, the line graph 1008 includes total wear time per day on the y-axis and date on the x-axis. Thus, the line graph 1008 provides a quick view of any trends in total wear compliance for the patient, such as the total number of hours the patient wore the medical device each day and the recorded changes in wear compliance for the patient.
[0146] In some examples, the graphical representations, such as the bar graph 1006 and the line graph 1008, may include a view of the wearing compliance information encompassing the entire period during which the patient has been prescribed the wearable medical device. For example, the patient may be prescribed the device for 90 days. At the end of the 90-day prescription period, the physician may view the wearing compliance information for the entire period in a single graphical representation. In some examples, the prescription period may be changed. For example, the prescription period may be 7 days, 14 days, 30 days, 60 days, 180 days, 1 year, and other similar periods. In certain implementations, the physician may modify the graphical representations to view a portion of the wearing compliance information. For example, if the prescription period is 90 days, the physician may modify one or both of the bar graph 1006 and the line graph 1008 to show a portion of the period, such as 5 days, 1 week, 2 weeks, or 30 days.
[0147] In certain implementations, the user interface screen may further include one or more user selectable interface controls configured to provide access to recorded ECG information for one or more of the start event, the end event, and the period during which the patient wore the wearable medical device. For example, each of the bar graph 1006 and the line graph 1008 may include one or more user selectable interface controls for accessing the recorded ECG information. For example, as shown in FIG. 10B, the line graph 1008 may include one or more user selectable interface controls 1010 embedded into the graphical representation of the wear compliance information. Upon receiving a selection of one of the controls 1010, the user interface screen may be updated to include additional information, such as the recorded ECG information. For example, as shown in FIG. 10C, the window 1012 may be overlaid with a user interface screen 1000 including additional information related to the selected control 1010. For example, window 1012 may include ECG recording information 1014a recorded during an initial start event, intermediate ECG recording information 1014b recorded between start and end events, and ECG recording information 1014c recorded at an end event. The recorded ECG information shown in FIG. 10C is included by way of example only, and in some implementations, additional information may be displayed or otherwise provided on user interface screen 1000, such as information derived from one or more motion signals described herein, impedance information, ECG metric information, time information, and other similarly recorded information.
[0148] As described above in the description of FIG. 9, the physician can set one or more alert criteria for receiving alerts about patient wear compliance information. As shown in FIG. 10D, the user interface screen 1000 can also display an overlaid alert 1016 indicating one or more alerts about the patient's wear compliance information. For example, as shown in FIG. 10D, the alert 1016 indicates that the patient failed to meet the minimum compliance information on September 13, 2015 and has failed to meet the target compliance information for the past six days. It should be noted that the location on the screen 1000 and the overall alert including the information contained herein shown in FIG. 10D are provided by way of example only. Thus, depending on the physician's settings, the information contained in the alert may vary.
[0149] In addition to providing wear compliance information to a caregiver, such as a physician, it may be desirable to provide wear compliance information to the patient themselves. By providing the patient with immediate, immediate, or easily available feedback regarding the patient's wear compliance, the patient can immediately recognize non-compliance, thereby providing the patient with an opportunity to correct compliance shortcomings without physician intervention. Additionally, positive feedback may provide the patient with further motivation to continue good wear compliance.
[0150] 10E and 10F show sample feedback regarding the patient's wear compliance information that may be provided to the patient. The feedback may be transmitted to a personal computing device, such as the patient's smartphone, for processing and display. For example, a processor integrated into the personal computing device may process the feedback information and display it on a display of the personal computing device. For example, as shown in FIG. 10E, the device may display a user interface screen 1018. The user interface screen 1018 may include a high level summary of the patient's information. For example, as shown in FIG. 10E, the user interface screen 1018 may include wear compliance streak information, today's wear information, average daily heart rate information, and activity information for the patient.
[0151] In certain implementations, the device can further provide additional information related to wear compliance. For example, as shown in FIG. 10F, the device can display a user interface screen 1020 that includes additional, more specific wear compliance information for the patient. For example, the user interface screen 1020 can include a graph of wear time today, including highlighted portions of time the device was worn and time the device was not worn. The user interface screen 1020 can further include active streak information, such as the total number of consecutive days the patient has complied with the wear requirements, and historical information about how the current streak compares to past wear compliance streaks. The user interface screen 1020 can also include information such as wear compliance information for the current week.
[0152] The wear compliance information shown in Figures 10E and 10F is provided by way of example only. In a particular implementation, the type of information provided to the patient may vary based on, for example, input from the patient's physician, the type of wearable medical device prescribed for the patient, expected compliance standards for the patient, and other similar parameters.
[0153] It should also be noted that providing the wear compliance information in a graphical representation accessible, for example, via the web portal described above, is provided by way of example only. In certain implementations, providing the wear compliance information (e.g., outputting the wear compliance information (514) shown in FIG. 5 and described above) may also include generating a report that may be transmitted electronically to one or more recipients, such as the patient's physician. The report may include various data described herein, filtered based on criteria set, for example, by the patient's physician. The report may be organized according to daily, weekly, monthly, or other similar time periods and include wear compliance information for the patient over those time periods. The report may also include charts and / or graphs similar to those shown in FIGS. 10A and 10B and described above.
[0154] The teachings of the present disclosure may generally be applied to external medical monitoring and / or treatment devices that include one or more sensors described herein. Such external medical devices may include, for example, portable medical devices described herein that can and are designed to move with a patient as the patient performs his or her daily tasks. Exemplary portable medical devices may be wearable medical devices, such as WCDs, wearable cardiac monitoring devices, in-hospital devices, e.g., in-hospital wearable cardioverter defibrillators (HWDs), short-term wearable cardiac monitoring and / or treatment devices, mobile cardiac event monitoring devices, and other similar wearable medical devices.
[0155] The wearable medical device may enable continuous use by the patient. In some implementations, the continuous use may be effectively, substantially, or nearly continuous. That is, the wearable medical device may be used continuously, except for sporadic periods during which use temporarily ceases (e.g., while the patient is bathing, while the patient is fitting new and / or different garments, while the batteries are being charged / changed, while the garments are being washed and ironed, etc.). As described herein, such substantially or nearly continuous use may nevertheless be considered continuous use. For example, the wearable medical device may be configured to be worn by the patient for as long as 24 hours per day. In some implementations, the patient may remove the wearable medical device for short portions of the day (e.g., 30 minutes for taking a bath).
[0156] Further, the wearable medical device may be configured as a long-term or extended use medical device. Such devices may be configured to be used by a patient for extended periods of days, weeks, months, or even years. In some examples, the wearable medical device may be used by a patient for an extended period of at least one week. In some examples, the wearable medical device may be used by a patient for an extended period of at least 30 days. In some examples, the wearable medical device may be used by a patient for an extended period of at least one month. In some examples, the wearable medical device may be used by a patient for an extended period of at least two months. In some examples, the wearable medical device may be used by a patient for an extended period of at least three months. In some examples, the wearable medical device may be used by a patient for an extended period of at least six months. In some examples, the wearable medical device may be used by a patient for an extended period of at least one year. In some implementations, extended use may be uninterrupted until a physician or other HCP provides specific instructions to the patient to stop using the wearable medical device.
[0157] Regardless of long-term wear, use of a wearable medical device may include continuous or near-continuous wear by a patient, as described above. For example, continuous use may include continuous wearing or attachment of the wearable medical device to a patient, e.g., through one or more of the electrodes described herein, during both monitoring periods and periods when the device may not be monitoring the patient but is otherwise still worn by or otherwise attached to the patient. The wearable medical device may be configured to continuously monitor the patient for cardiac-related information (e.g., ECG information, including arrhythmia information, cardiac vibrations, etc.) and / or non-cardiac information (e.g., blood oxygen, patient temperature, glucose levels, tissue fluid levels, and / or pulmonary vibrations). The wearable medical device may perform the monitoring at periodic or non-periodic time intervals or times. For example, monitoring during the intervals or times may be triggered by a user's action or another event.
[0158] As mentioned above, the wearable medical device may be configured to monitor other non-ECG physiological parameters of the patient in addition to cardiac-related parameters. For example, the wearable medical device may be configured to monitor, among others, lung vibrations (e.g., using a microphone and / or accelerometer), expiratory vibrations, sleep-related parameters (e.g., snoring, sleep apnea), tissue fluids (e.g., using a radio frequency transmitter and a sensor).
[0159] Other exemplary wearable medical devices include automatic cardiac monitors and / or defibrillators for use in certain specialized conditions and / or environments, such as in combat zones or in emergency vehicles. Such devices may be configured to be immediately (or substantially immediately) used in critical care. In some examples, the portable medical devices described herein may be paceable, e.g., capable of providing therapeutic pacing pulses to a patient. In some examples, the portable medical devices may be configured to monitor and / or measure ECG metrics including, for example, heart rate (such as mean, median, mode, or other statistical measurements of heart rate, and / or maximum, minimum, resting, pre-exercise and post-exercise heart rate values and / or ranges), heart rate variability metrics, PVC burden or count, atrial fibrillation burden metrics, pauses, heart rate turbulence, QRS height, QRS width, changes in size or shape of the form of ECG information, cosine RT, artificial pacing, QT interval, QT variability, T wave width, T wave, T wave variability, and ST segment changes.
[0160] As mentioned above, FIG. 3 illustrates an exemplary component level diagram of a medical device controller 300 included in, for example, a wearable medical device. As further illustrated in FIG. 3, a therapy delivery circuit 302 can be coupled to one or more electrodes 320 configured to provide therapy to a patient. For example, the therapy delivery circuit 302 can include or be operably connected to circuit components configured to generate and deliver an electrical therapeutic shock. The circuit components can include, for example, resistors, capacitors, relays and / or switches, electrical bridges such as an H-bridge (e.g., including multiple insulated gate bipolar transistors, i.e., IGBTs), voltage and / or current measurement components, and other similar circuit components arranged and connected such that the circuit components operate in conjunction with the therapy delivery circuit and are under the control of one or more processors (e.g., processor 318) to provide at least one therapeutic shock to a patient, including, for example, one or more pacing cardioversion or defibrillation therapy pulses.
[0161] Pacing pulses may be used to treat cardiac arrhythmia conditions such as bradycardia (e.g., less than 30 beats per minute) and tachycardia (e.g., greater than 150 beats per minute), for example, using fixed rate pacing, demand pacing, anti-tachycardia pacing, etc. Defibrillation pulses may be used to treat ventricular tachycardia and / or ventricular fibrillation.
[0162] The capacitors may include parallel connected capacitor banks of multiple capacitors (e.g., 2, 3, 4 or more capacitors). In some examples, the capacitors may include single membrane or electrolytic capacitors as series connected devices including a bank of identical capacitors. These capacitors may be switched into a series connection during the discharge of a defibrillation pulse. For example, a single capacitor of approximately 140 uF or more, or four capacitors of approximately 650 uF may be used. These capacitors may have surge rates of 1600 VDC or more for a single capacitor, or approximately 350-500 VDC for multiple capacitors connected in parallel, and may be charged from the battery pack in approximately 15-30 seconds.
[0163] For example, each defibrillation pulse may deliver energy in the range of 60-180 Joules. In some implementations, the defibrillation pulse may be a biphasic truncated exponential waveform, whereby the signal may alternate between positive and negative portions (e.g., charge direction). This type of waveform may be effective in defibrillating a patient at lower energy levels compared to other types of defibrillation pulses (e.g., monophasic pulses, etc.). For example, the amplitude and width of these two phases of the energy waveform may be automatically adjusted to deliver a precise amount of energy (e.g., 150 Joules) regardless of the patient's body impedance. The therapy delivery circuit 302 may be configured to perform the switching and pulse delivery operations, for example, under the control of the processor 318. As energy is delivered to the patient, the amount of energy being delivered may be tracked. For example, the amount of energy may be held at a predetermined constant value even when the pulse waveform is dynamically controlled based on factors such as the body impedance of the patient to whom the pulse is being delivered.
[0164] In certain instances, the therapy delivery circuit 302 may be configured to deliver a set of cardioversion pulses, for example, to correct an improperly beating heart. In comparison to the defibrillation described above, cardioversion typically involves a weaker shock delivered at a particular frequency to mimic the heart's normal rhythm.
[0165] The data storage 304 may include one or more of non-transitory computer readable media, such as, for example, flash memory, solid state memory, magnetic memory, optical memory, cache memory, combinations thereof, etc. The data storage 304 may be configured to store executable instructions and data used in the operation of the medical device controller 300. In certain examples, the data storage may include executable instructions configured to cause the processor 318 to perform one or more operations when executed. In some examples, the data storage 304 may be configured to store information, such as, for example, ECG data received from a sensing electrode interface.
[0166] In some examples, the network interface 306 may facilitate communication of information between the medical device controller 300 and one or more other devices or entities over a communications network, such as the network 806 shown in FIG. 8. For example, the medical device controller 300 may be included in a portable medical device and the network interface 306 may be configured to communicate with a remote computing device, such as a remote server (e.g., the remote server 808 shown in FIG. 8), or other similar computing device. The network interface 306 may include communications circuitry for transmitting such data to an intermediate device according to the Bluetooth® wireless standard for exchanging data over short distances. For example, such an intermediate device may be configured as a base station, a “hotspot” device, a smartphone, a tablet, a portable computing device, and / or other device in the vicinity of the wearable medical device including the medical device controller 300. The intermediate device may then communicate the data to the remote server over a broadband cellular network communications link. This communication link may implement broadband cellular technologies (e.g., 2.5G, 2.75G, 3G, 4G, 5G cellular standards) and / or Long Term Evolution (LTE) technologies for high-speed wireless communication, or GSM / EDGE and UMTS / HSPA technologies. In some implementations, the intermediate device may communicate with the remote server via a Wi-Fi communication link based on the IEEE 802.11 standard.
[0167] In a particular example, the user interface 308 may include an input device, an output device, and Input device / output device combination10D and a software stack configured to cause the operation of these devices. These user interface elements may display visual, audio, and / or tactile content. Thus, the user interface 308 may receive input or provide output to enable a user to interact with the medical device controller 300. In a particular implementation, the user interface 308 may be configured to provide a user interface screen 1010 shown in FIG. 10D and a user interface screen 1012 shown in FIG. 10E to a user of the medical device controller 300.
[0168] The medical device controller 300 may also include at least one rechargeable battery 310 configured to provide power to one or more components integrated into the medical device controller 300. The rechargeable battery 310 may include a rechargeable multi-cell battery pack. In one exemplary implementation, the rechargeable battery 310 may include three or more 2200 mAh lithium-ion cells that provide power to other device components within the medical device controller 300. For example, the rechargeable battery 310 may provide a power output ranging from 20 mA to 1000 mA (e.g., 40 mA) output and may support 24 hours, 48 hours, 72 hours or more of run time between multiple charges. In a particular implementation, the battery capacity, run time and type (e.g., lithium-ion, nickel-cadmium or nickel-metal hydride) may be modified to best suit a particular application of the medical device controller 300.
[0169] The sensor interface 312 may include a physiological signal circuit coupled to one or more sensors configured to monitor one or more physiological parameters of the patient. As shown, the sensors may be coupled to the medical device controller 300 via a wired or wireless connection. The sensors may include one or more ECG sensing electrodes 322 and non-ECG physiological sensors 323, such as a vibration sensor 324, a tissue fluid monitor 326 (e.g., based on an ultra-high bandwidth RF device) and a motion sensor (e.g., an accelerometer, gyroscope, and / or magnetometer). In some implementations, the sensors may include multiple traditional ECG sensing electrodes in addition to the digital sensing electrodes.
[0170] The sensing electrodes 322 may be configured to monitor the patient's ECG information. For example, by design, the digital sensing electrodes 322 may include a skin-contacting electrode surface that may be considered polarizable or non-polarizable depending on various factors including the metal and / or coating used in the construction of the electrode surface. All such electrodes may be used with the principles, techniques, devices and systems described herein. For example, the electrode surface may be based on stainless steel, precious metals such as platinum, or Ag-AgCl.
[0171] In some examples, the electrodes 322 may be used with an electrolytic gel dispersed between the electrode surface and the patient's skin. In certain implementations, the electrodes 322 may be dry electrodes that do not require an electrolytic material. As an example, such dry electrodes may be based on tantalum metal and may have the tantalum pentoxide coating described above. Such dry electrodes may be more comfortable for long-term monitoring applications.
[0172] Referring again to FIG. 3, the vibration sensor 324 may be configured to detect cardiac or pulmonary vibration information. For example, the vibration sensor 324 may detect cardiac valve vibration information of the patient. For example, the vibration sensor 324 may be configured to detect cardiac vibration signal values including any one or all of S1, S2, S3, and S4. From these cardiac vibration signal values or cardiac vibration values, certain cardiac vibration metrics may be calculated including any one or more of electromechanical activation time (EMAT), average EMAT, percentage of EMAT (%EMAT), cardiac contractile dysfunction index (SDI), and left ventricular contraction time (LVST). The vibration sensor 324 may be configured to detect cardiac wall motion, for example, by positioning the sensor in the region of the apex beat. The vibration sensor 324 may include a vibration sensor configured to detect vibrations from the patient's cardiac and pulmonary system and provide an output signal in response to the detected vibrations of the target organ, for example, capable of detecting vibrations occurring in the trachea or lungs due to air flow during breathing. In certain implementations, additional physiological information may be determined from the lung vibration signal, such as, for example, lung vibration characteristics based on sounds generated within the lungs (e.g., wheezing, crepitation, etc.). The vibration sensor 324 may also include a multi-channel accelerometer, for example, a three-channel accelerometer configured to sense motion in each of three orthogonal axes, such that patient movement / position may be detected and correlated to the detected cardiac vibration information. The vibration sensor 324 may transmit information describing the cardiac vibration information to the sensor interface 312 for subsequent analysis.
[0173] The tissue fluid monitor 326 can assess fluid levels and accumulation in the patient's body tissue using RF-based technology. For example, the tissue fluid monitor 326 can be configured to measure fluid content in the lungs, typically for diagnosis and follow-up of pulmonary edema or congestion in heart failure patients. The tissue fluid monitor 326 can include one or more antennas configured to direct RF waves through the patient's tissue and measure an output RF signal in response to the waves passing through the tissue. In certain implementations, the output RF signal includes a parameter indicative of the fluid level in the patient's tissue. The tissue fluid monitor 326 can transmit information describing the tissue fluid level to the sensor interface 312 for subsequent analysis.
[0174] In certain implementations, the cardiac event detector 316 may be configured to monitor the patient's ECG signal for the occurrence of a cardiac event, such as an arrhythmia or other similar cardiac event. The cardiac event detector may be configured to operate in conjunction with the processor 318 to process the received ECG signal, for example from the sensing electrodes 322, and perform one or more methods to determine the likelihood that the patient is experiencing a cardiac event. The cardiac event detector 316 may be implemented using hardware or a combination of hardware and software. For example, in some examples, the cardiac event detector 316 may be implemented as a software component stored in the data storage 304 and executed by the processor 318. In this example, instructions included in the cardiac event detector 316 may cause the processor 318 to perform one or more methods to analyze the received ECG signal to determine whether an adverse cardiac event is occurring. In other examples, the cardiac event detector 316 may be an application specific integrated circuit (ASIC) coupled to the processor 318 and configured to monitor the ECG signal for the occurrence of an adverse cardiac event. Thus, examples of the cardiac event detector 316 are not limited to a particular hardware or software implementation.
[0175] In some implementations, the processor 318 includes one or more processors (or one or more processor cores), each configured to execute a set of instructions that result in manipulated data and / or to control the operation of other components of the medical device controller 300. In some implementations, when performing a particular process (e.g., cardiac monitoring), the processor 318 may be configured to make certain logic-based decisions based on received input data and may further be configured to provide one or more outputs that may be used to control or otherwise inform subsequent processing performed by the processor 318 and / or other processors or circuits to which the processor 318 is communicatively coupled. Thus, the processor 318 responds in a particular manner to a particular input stimulus and generates a corresponding output based on the input stimulus. In some illustrative cases, the processor 318 may go through a series of logic transitions, in which the states of various internal registers and / or other bit cells internal or external to the processor 318 may be set to logic high or logic low. As referred to herein, the processor 318 may be configured to execute functions for which software is stored in a data store coupled to the processor 318, the software causing the processor to make a series of various logical decisions that result in the execution of the functions. 318The processor 318 is configured to pass through a plurality of processing elements, each of which may include a processor, ...
[0176] As mentioned above, a portable medical device, such as a WCD, can be designed to include a digital front end where an analog signal sensed by a skin-contact electrode surface of a set of digital sensing electrodes is converted to a digital signal for processing. A typical portable medical device with an analog front end configuration uses circuitry to accommodate signals from a high source impedance (e.g., having an internal impedance range of approximately 100 kilohms to one or more megahms) from the sensing electrodes. This high source impedance signal is processed and transmitted to a monitoring device, such as the processor 318 of the controller 300 described above, for further processing. In a particular implementation, the monitoring device or another similar processor, such as a microprocessor, or another dedicated processor operably coupled to the sensing electrodes can be configured to receive a common noise signal from each of the sensing electrodes, sum the common noise signals, invert the summed common noise signal, and feed the inverted signal back to the patient as a driven ground by canceling the common mode signal using, for example, a driven right leg circuit.
[0177] FIG. 11A illustrates an exemplary medical device 1100 that is external, portable, and wearable by a patient 1102 and configured to implement one or more features described herein. For example, the medical device 1100 may be a non-invasive medical device configured to be placed substantially external to the patient. Such a medical device 1100 may be, for example, a portable medical device that can and is designed to move with the patient as the patient performs his or her daily tasks. For example, a medical device 1100 described herein, such as the LifeVest® wearable cardioverter defibrillator available from ZOLL® Medical Corporation, may be attached to the patient's body. Such wearable defibrillators are typically worn nearly or substantially continuously for two to three months at a time. Such wearable defibrillators may be configured to continuously or substantially continuously monitor the patient's vital signs during the period that they are worn by the patient, and may be configured to deliver one or more therapeutic electrical pulses to the patient upon a determination that treatment is required. For example, such therapeutic shocks may be pacing, defibrillation or transcutaneous electrical nerve stimulation (TENS) pulses.
[0178] The medical device 1100 may include a garment 1110, one or more ECG sensing electrodes 1112, one or more non-ECG physiological sensors 1113, one or more treatment electrodes 1114a and 1114b (collectively referred to herein as treatment electrodes 1114), a medical device controller 1120 (e.g., controller 300 described above in the description of FIG. 3), a connection pod 1130, a patient interface pod 1140, one or more of a belt 1150, or any combination thereof. In some examples, at least some of the components of the medical device 1100 may be configured to be attached to (or in some examples permanently integrated into) the garment 1110, which may be worn around a patient's torso.
[0179] The medical device controller 1120 may be operably coupled to the sensing electrodes 1112, which may be attached to the garment 1110, e.g., assembled to the garment 1110, or removably attached to the garment, e.g., using hooks and hook-and-loop fasteners. In some implementations, the sensing electrodes 1112 may be permanently integrated into the garment 1110. The medical device controller 1120 may be operably coupled to the treatment electrodes 1114. For example, the treatment electrodes 1114 may be assembled to the garment 1110, or in some implementations may be permanently integrated into the garment 1110. In one example, the medical device controller 1120 includes a patient user interface 1160 to allow the patient to interface with the externally worn device. For example, the patient can use the patient user interface 1160 to respond to activities related to the questions, prompts, and surveys described herein.
[0180] Component configurations other than those shown in FIG. 11A are possible. For example, the sensing electrodes 1112 may be configured to be attached at various locations around the body of the patient 1102. The sensing electrodes 1112 may be operably coupled to the medical device controller 1120 through a connection pod 1130. In some implementations, the sensing electrodes 1112 may be adhesively attached to the patient 1102. In some implementations, the sensing electrodes 1112 and at least one of the treatment electrodes 1114 may be included in a single integrated patch and adhesively attached to the patient's body.
[0181] The sensing electrodes 1112 may be configured to detect one or more cardiac signals. Examples of such signals include ECG signals and / or other sensed cardiac physiological signals from the patient. In certain examples, as described herein, non-ECG physiological sensors 1113, such as accelerometers, vibration sensors, RF-based sensors, and other measurement devices for recording additional non-ECG physiological parameters. For example, as described above, such non-ECG physiological sensors may be configured to detect other types of patient physiological parameters and acoustic signals, such as, for example, tissue fluid levels, cardiac vibrations, pulmonary vibrations, respiratory vibrations, patient motion, and the like.
[0182] In some examples, the therapy electrodes 1114 may be configured to include sensors configured to detect the patient's ECG signals and other physiological signals. In some examples, the connectivity pod 1130 may include a signal processor configured to amplify, filter, and digitize the cardiac signals before transmitting them to the medical device controller 1120. One or more of the therapy electrodes 1114 may be configured to deliver one or more therapeutic defibrillation shocks to the body of the patient 1102 if the medical device 1100 determines that such therapy is warranted based on signals detected by the sensing electrodes 1112 and processed by the medical device controller 1120. An exemplary therapy electrode 1114 may include a metal electrode, such as a stainless steel electrode, including one or more conductive gel placement devices configured to supply conductive gel to the metal electrode prior to delivery of the therapeutic shock.
[0183] In some implementations, the medical devices described herein may be configured to switch between a therapeutic medical device and a monitoring medical device configured to only monitor a patient (e.g., not provide or perform any therapeutic functions). For example, therapeutic components such as the therapeutic electrodes 1114 and associated circuitry may be optionally disconnected from (or coupled to) the medical device or switched off (or on) from (or to) the medical device. For example, the medical device may have optional therapeutic elements (e.g., defibrillation and / or pacing electrodes, components and associated circuitry) configured to operate in a therapeutic mode. The optional therapeutic elements may be physically disconnected from the medical device to convert the therapeutic medical device to a monitoring medical device for a particular application (e.g., for operation in a monitoring-only mode) or patient. Alternatively, the optional therapeutic elements may be deactivated (e.g., via a physical or software switch), such that the therapeutic medical device essentially becomes a monitoring medical device for a particular physiological purpose or for a particular patient. As an example of a software switch, an authorized person can access a protected user interface of a medical device and select a pre-configured option or perform some other user action via the user interface to deactivate a therapeutic element of the medical device.
[0184] FIG. 11B illustrates an in-hospital wearable defibrillator 1100A that is external, portable, and wearable by a patient 1102. In some implementations, the in-hospital wearable defibrillator 1100A can be configured to provide pacing therapy, for example, to treat bradycardia, tachycardia, and asystole conditions. The in-hospital wearable defibrillator 1100A can include one or more ECG sensing electrodes 1112a, one or more treatment electrodes 1114a and 1114b, a medical device controller 1120, and a connectivity pod 1130. For example, each of these components can be structured as and function like a similar number of components of the medical device 1100. For example, the electrodes 1112a, 1114a, 1114b can include disposable adhesive electrodes. For example, the electrodes can include sensing and treatment components disposed on separate sensing and treatment electrode adhesive patches. In some implementations, both sensing and therapy components may be integrated and placed on the same electrode adhesive patch, which is then attached to the patient. For example, an anterior adhesive attachable therapy electrode 1114a is attached to the anterior of the patient's torso to deliver pacing or defibrillation therapy. Similarly, a posterior adhesive attachable therapy electrode 1114b is attached to the posterior of the patient's torso. In an exemplary scenario, at least three ECG adhesive attachable sensing electrodes 1112a may be attached at least above the chest near the patient's right arm, above the chest near the patient's left arm, and toward the lower part of the patient's chest in a manner instructed by a trained professional.
[0185] Patients being monitored by in-hospital wearable defibrillators and / or pacing devices may be confined to a hospital bed or room for significant amounts of time (e.g., 75% or more of the patient's stay in the hospital). As a result, the user interface 1160a may be configured to interact with non-patient users, e.g., nurses, for device-related functions such as initial device baselining, setting and adjusting patient parameters, and changing device batteries.
[0186] In some examples, the in-hospital wearable defibrillator 1100A may further include one or more motion sensors, such as an accelerometer. For example, an accelerometer may be integrated into one or more of the sensing electrode 1112a (e.g., integrated into the same patch as the sensing electrode), the therapy electrode 1114a (e.g., integrated into the same patch as the therapy electrode), the medical device controller 1120, the connectivity pod 1130, and various other components of the in-hospital wearable defibrillator 1100A.
[0187] In some implementations, an example of a therapeutic medical device including a digital front end according to the systems and methods described herein may include a short-term defibrillator and / or a pacing device. For example, such a short-term device may be prescribed by a physician for a patient experiencing a syncope condition. The wearable defibrillator may be configured to monitor a patient experiencing a syncope condition, for example, by analyzing the patient's physiology and cardiac activity for aberrant patterns that may indicate abnormal physiology. For example, such aberrant patterns may occur before, during, or after the onset of syncope. In such an example implementation of a short-term wearable defibrillator, the electrode assembly may be adhesively attached to the patient's skin and may have a configuration similar to the in-hospital wearable defibrillator described above in connection with FIG. 11A.
[0188] 11C and 11D show an exemplary wearable patient monitoring device without treatment or therapy functions. For example, such a device is configured to monitor one or more physiological parameters of a patient, for example, to remotely monitor and / or diagnose the patient's condition. For example, such physiological parameters may include the patient's ECG information, tissue (e.g., lung) fluid levels, cardiac vibrations (e.g., using an accelerometer or microphone) and other related cardiac information. The cardiac monitoring device is a portable device that the patient can carry with them as they go about their daily routine.
[0189] 11C, an exemplary wearable patient monitoring device 1100C may include a tissue fluid monitor 1165 that uses RF-based technology to assess fluid levels and accumulation in a patient's body tissue. Such a tissue fluid monitor 1165 may be configured to measure fluid content in the lungs for diagnosis and follow-up of pulmonary edema or congestion, typically in heart failure patients. The tissue fluid monitor 1165 may include one or more antennas configured to direct RF waves through the patient's tissue and measure an output RF signal in response to the waves passing through the tissue. In a particular implementation, the output RF signal includes a parameter indicative of the fluid level in the patient's tissue. In an example, the device 1100C may be a cardiac monitoring device that also includes a digital sensing electrode 1170 for sensing the patient's ECG activity. The device 1100C may pre-process the ECG signal via one or more ECG processing and / or conditioning circuits, such as ADCs, operational amplifiers, digital filters, signal amplifiers, etc., under the control of a microprocessor. The device 1100C can transmit information describing ECG activity and / or tissue fluid levels to a remote server via a network interface for analysis. Additionally, in certain implementations, the device 1100C can include one or more sensors for measuring motion signals as described herein. Multiple It may include an accelerometer.
[0190] 11D, another exemplary wearable cardiac monitoring device 1100D may be attached to a patient via at least three adhesive digital cardiac sensing electrodes 1175 positioned around the patient's torso. Additionally, in certain implementations, the device 1100D may include one or more digital sensing electrodes integrated into one or more of the digital sensing electrodes for measuring motion signals, for example as described herein. Multiple It may include an accelerometer.
[0191] Cardiac devices 1100C and 1100D are used in cardiac monitoring and telemetry and / or continuous cardiac event monitoring applications, for example in patient populations complaining of irregular cardiac signs and / or conditions. These devices can transmit information describing ECG activity and / or tissue fluid levels via a network interface to a remote server for analysis. Exemplary cardiac conditions that may be monitored include atrial fibrillation (AF), bradycardia, tachycardia, atrioventricular block, Launguon-Levine syndrome, atrial flutter, sinoatrial node dysfunction, cerebral ischemia, pauses and / or heart palpitations. For example, such patients may be prescribed cardiac monitoring for extended periods of time, for example, 10-30 days or more. In some portable cardiac monitoring and / or telemetry applications, the portable cardiac monitoring device may be configured to substantially continuously monitor a patient for cardiac abnormalities, and if such an abnormality is detected, the monitor can automatically transmit data related to the abnormality to a remote server. The remote server may be located in a 24-hour staffed monitoring center where the data is interpreted by qualified cardiac-trained reviewers and / or HCPs and feedback is provided to the patient and / or designated HCP via detailed periodic or event-triggered reports. In certain cardiac event monitoring applications, the cardiac monitoring device is configured to allow the patient to manually press a button on the cardiac monitoring device to report symptoms. For example, the patient may report symptoms such as congestion, shortness of breath, lightheadedness, racing heartbeat, fatigue, fainting, chest discomfort, weakness, pseudovertigo and / or true dizziness. The cardiac monitoring device may record predetermined physiological parameters of the patient (e.g., ECG information) for a predetermined period of time (e.g., 1-30 minutes before and 1-30 minutes after the reported symptom). As described above, the cardiac monitoring device may be configured to monitor physiological parameters of the patient other than cardiac-related parameters.For example, the cardiac monitoring device may be configured to monitor, among others, for example, cardiac vibration signals (e.g., using an accelerometer or microphone), pulmonary vibration signals, expiratory vibrations, sleep-related parameters (e.g., snoring, sleep apnea), tissue fluids.
[0192] In some examples, devices described herein (e.g., FIGS. 11A-11D) can communicate with a remote server via an intermediate or gateway device 1180, such as that shown in FIG. 11D. For example, devices such as those shown in FIG. 11A-11D may be configured to include a network interface communication capability as described herein, e.g., with reference to FIG.
[0193] Additionally, devices described herein (e.g., FIGS. 11A-11D) may be configured to include one or more accelerometers described herein. For example, as described above in the description of FIGS. 1A and 1B, one or more sensors, such as accelerometers, vibration sensors, and RF sensors, may be integrated into various components of the wearable device or may be included as standalone sensors configured to measure various signals about the patient.
[0194] Although the subject matter contained herein has been described in detail for purposes of illustration, it should be understood that such detail is for that purpose only, and that the disclosure is not limited to the disclosed embodiments, but on the contrary, is intended to cover modifications and equivalent arrangements within the scope of the appended claims. For example, it should be understood that the disclosure contemplates that, to the extent possible, one or more features of any embodiment can be combined with one or more features of any other embodiment.
[0195] Other examples are within the scope of this specification and the claims. Additionally, certain functions described above may be implemented using software, hardware, firmware, hardwiring, or any combination of these. Also, features implementing the functions may be physically located (including distributed) in various locations such that some of these functions are implemented in different physical locations. [Example Implementation]
[0196] A medical device controller described herein may include one or more database tables configured to store wear compliance information. For example, the database tables may include a wear compliance table and a flag table. In some examples, the wear compliance information and flag data may be combined into a single database table. In one example, the database table may store how long the device has been worn with multiple rows for separate wear periods. A schema for creating such a database table may be as follows:
number
[0197] In some examples, the wear compliance process described herein may use ECG signal detection and monitoring to determine compliance. For example, observing valid ECG data on at least one ECG channel may provide an indication of wear compliance. In various sample implementations, the processor of the medical device controller described herein may be configured to implement functions as represented by the following pseudocode: When the belt is connected and the detection system is activated, the compliance monitoring module activates compliance tracking. ●Monitor ECG channel 1 and ECG channel 2. The ECG is uniquely captured via four ECG electrodes with some common mode noise rejection (e.g., of a predefined bandwidth of 1 MHz to 10 kHz or 10 MHz to 5 kHz). o Before digitization, the ECG signal is passed through a bandpass filter (0.1Hz to 60Hz). o The ECG signal is amplified in a dynamic amplifier. For example, the amount of amplification is controlled (e.g., every 2 seconds, 5 seconds, 7 seconds, 10 seconds, 15 seconds, or other dynamic duration depending on the rhythm) to ensure that the ECG signal detection module (including the arrhythmia detection module) and the noise detection module receive optimal levels of ECG signal samples.
[0198] The processor may be further configured to determine the wear compliance based on a valid ECG signal. For example, the processor may be configured to implement functionality as represented in the following pseudocode: ●Verify the ECG signal. Detecting a predetermined QRS complex in at least one of the ECG channels for a predetermined duration. The process finds the QRS complex based on dual criteria of the amplitude and duration of the QRS complex. In one example, Pan Tompkins is used to detect the QRS. After a predefined time called "WearTimePreOnPeriod" (e.g., 5 seconds of QRS signal or other predefined value, or a dynamically changing value), the wearing time ("WearTimeStart") starts. Dynamic variation of WearTimePreOnPeriod duration: If the signal is noisy (indicated by ECGnoiseFlagMask), the predefined time is extended, for example by 10 seconds to allow more ECG samples to be collected. ○ (Alternative Step 1:) Dynamic change of a predefined duration WearTimePreOnPeriod: If a QRS sample is detected for a predefined portion of the WearTimePreOnPeriod duration. For example, the predefined portion can be set to 80%. This means that if the double criteria is met for 80% of the WearTimePreOnPeriod, compliance tracking is started (WearTimeStart). Otherwise, the WearTimePreOnPeriod duration is extended by an additional period, for example 3 seconds. The dynamic check is then repeated for an extended WearTimePreOnPeriod duration, with WearTimePreOnPeriod being reset when the total duration reaches a predefined maximum (e.g., 15 seconds). When a predetermined time period (e.g., 5 seconds or other preset value, or a dynamically changing value) called "WearTimeGoesOffperiod" has elapsed during which a threshold level of the QRS signal is not detected, the compliance monitoring module indicates that compliance tracking is paused ("WearTimeEnd"). o Example of dynamic change of predefined duration WearTimeGoesOffperiod: If no QRS sample is detected for a predefined portion of the WearTimeGoesOffperiod duration. For example, the predefined portion can be set to 80%. This means that if the double criteria has not been met for 80% of the WearTimeGoesOffperiod, compliance tracking is paused (WearTimeEnd). Otherwise, the WearTimeGoesOffperiod duration is extended by an additional period, for example 3 seconds. The dynamic check is repeated for an extended WearTimeGoesOffperiod duration. WearTimeGoesOffperiod is reset when the total duration reaches a predefined maximum (e.g., 15 seconds). In this situation, this means that the ECG signal is still good and the patient compliance information indicates that the patient is wearing the device properly. o Check if a midnight crossing has occurred. If so, the compliance tracking routine updates the record to split this record that crosses midnight into two records. For the previous 24 hour period, the compliance module records how many cumulative hours and minutes the patient wore the device. For example, in Figure X, the patient wore the device from 00:00 to 08:00, then from 10:00 to 23:00. Therefore, the overall cumulative duration for the 24 hour period is 22 hours. If the belt is disconnected or the system is shut down (which means the detection system is deactivated), compliance monitoring is also paused (WearTimeEnd).
[0199] 12 illustrates a sample timing diagram 1200 depicting a visual representation of a patient's wear compliance information over a period of time. In this example, diagram 1200 includes a timeline 1202 representing a 24 hour period from 00:00 to 24:00. During this period, timeline 1202 includes various information related to wear compliance for the patient, such as wear duration 1204, recorded start events 1206, and recorded end events 1208. Based on the information shown in diagram 1200, a physician, patient, or other similar reviewer can quickly determine during what portion of this period the patient wore the medical device.
[0200] As further shown in FIG. 12, diagram 1200 includes a sample detailed view 1210 of a recorded end event 1208. As shown in the detailed view 1210, a series of measured R-waves 1212 are measured during the wear period 1204. The magnitude of the R-waves 1210 remains above a minimum R-wave magnitude threshold 1214 until the timeline approaches 08:00 hours. As the timeline approaches 08:00 hours, the magnitude of the measured R-waves 1212 begins to decline and crosses the threshold 1214 at 08:00 hours. Thus, at 08:00 hours, a processor performing a compliance monitoring process described herein can record an end event 1208 that ends the wear period 1204. The processor can then continue to monitor for a start event 1206 that indicates the patient is once again wearing the medical device.
[0201] In some examples, a medical device, such as a wearable medical device described herein, may be configured to inject or otherwise apply an electrical signal to a patient's body. By monitoring and measuring this electrical signal, a processor may determine whether the patient is wearing the medical device, and therefore, wear compliance. For example, a processor of a medical device controller may be configured to implement functionality as represented in the following pseudocode: • A low level AC signal (called a wear time signal) is applied to the body, for example via treatment electrodes. A signal of a predetermined frequency (e.g., 800 Hz). For example, it can be in the range of 100 Hz to 1 MHz. Detect the wear time signal in hardware using a high pass filter and store the resulting samples in an accumulator. If the output of the accumulator is compared to a predefined threshold (wear time signal accumulator threshold), a WearTimeStart detection flag can be set. - The output of the accumulator should remain above a predefined threshold for a dynamic duration, described below. o After a predefined time, WearTimePreOnPeriod (e.g., 5 seconds of the accumulator output remaining above the threshold, or other predefined value, or a dynamically changing value), the wearing time (WearTimeStart) begins. Example 1 of dynamic change of WearTimePreOnPeriod duration: If the signal is noisy (indicated by ECGnoiseFlagMask), the predefined time is extended, for example to 10 seconds or so, to allow for a longer period of time to detect additional wear time signal samples to determine if the wear time signal accumulator threshold has been met. o Example 2 of dynamic change of predefined duration WearTimePreOnPeriod: When a wearing time signal sample is detected for a predefined portion of the WearTimePreOnPeriod duration. For example, the predefined portion can be set to 80%. This means that if the wearing time accumulator threshold is met for 80% of the WearTimePreOnPeriod, compliance tracking is started (WearTimeStart). Otherwise, the WearTimePreOnPeriod duration is extended by an additional period, for example 3 seconds. The above dynamic check is then repeated for the extended WearTimePreOnPeriod duration. WearTimePreOnPeriod is reset when the total duration reaches a predefined maximum value (for example 15 seconds). When a predetermined time period (e.g., 5 seconds or other preset value, or a dynamically changing value) called WearTimeGoesOffperiod has elapsed during which the wear time signal accumulator threshold is not met, the compliance monitoring module indicates that compliance tracking is paused (WearTimeEnd). o Example of dynamic change of predefined duration WearTimeGoesOffperiod: if the wearing time signal accumulator threshold is not met for a predefined portion of the WearTimeGoesOffperiod duration. For example, the predefined portion can be set to 80%. This means that if the wearing time signal accumulator threshold is not met for 80% of the WearTimeGoesOffperiod, compliance tracking is paused (WearTimeEnd). Otherwise, the WearTimeGoesOffperiod duration is extended by an additional period, for example 3 seconds. The above dynamic check is repeated for the extended WearTimeGoesOffperiod duration. WearTimeGoesOffperiod is reset when the total duration reaches a predefined maximum value (for example 15 seconds). In this situation, this means that the wearing time signal accumulator threshold is met and the patient compliance information indicates that the patient is properly wearing the device. o The compliance module checks if a midnight crossing has occurred. If so, the compliance tracking routine updates the record to split this record that crosses midnight into two records. For the previous 24 hour period, the compliance module records how many cumulative hours and minutes the patient has worn the device. When the belt is disconnected or the system is shut down, which means the detection system is deactivated, compliance monitoring is also paused (WearTimeEnd).
[0202] As described herein, in certain implementations, the compliance monitoring process may include as inputs both physiological signals, such as an ECG signal, and motion information, such as the output of one or more accelerometers. For example, as shown in FIG. 13, a sample input / output diagram 1300 includes one or more ECG signals 1302 and motion information 1304 as inputs to a compliance monitoring process 1306. A processor may be configured to implement the compliance monitoring process 1306 and process the inputs to generate one or more outputs. For example, the process 1306 may be configured to output an output 1308 that includes an indication of an identified start event and a positive value of a variable WearTimeStart described herein. Similarly, the process may be configured to output an output 1310 that includes an indication of an identified end event and a positive value of a variable WearTimeEnd described herein. In certain implementations, if a test period is used to determine whether a start event or an end event has occurred, the outputs 1308 and 1310 may also include an indication of when the start event and / or end event began. In an example, the processor may be further configured to implement one or more additional functions represented in the following pseudocode: • When motion information (ACC signal) indicates that the patient is walking, running, climbing stairs, or otherwise moving. o The confidence threshold for such motion is high (e.g., greater than 0.75, 0.8 or other pre-set value, or a dynamically changing value). ○ Next, WearTimeStart can be set. o In an optional implementation, the ECG signal detection module (see details above) should also output a flag that agrees that WearTimeStart can be set. If both the ACC signal detection module and the ECG signal detection module agree, WearTimeStart can be set. If the ACC signal does not indicate that the patient is walking, running, climbing stairs, or otherwise moving. o For example, the confidence threshold for motion (determined above) is low. ○ The period of the day is predefined SleepPeriod=On (e.g., configurable, and set by default to 10pm - 6am) ■ Check the heart rate data to verify if the patient is asleep. ■ If the ACC signal and heart rate data indicate that the patient is asleep, WearTimeStart may be set. In an optional embodiment, the ECG signal detection module (see details above) should also output a flag to agree that WearTimeStart may be set. all If they match, then WearTimeStart may be set. ●If the ACC signal does not indicate that the patient is walking / running / climbing stairs and SleepPeriod is not on. o The ECG signal detection module (see details above) is used to output a flag indicating when WearTimeStart can be set, as described above.
[0203] In addition to the variables listed in connection with the database tables described herein above, other similar variables may be monitored and recorded in one or more database tables described herein. For example, the variable "totalHoursOfUse" may be recorded and may include data representing the first and last wear day segments in the calculation. In an example, the variable "averageDailyUse" may be recorded and may include the wear day segments of days that collectively exceed the minimum daily threshold of daily use. In an example, the variable "totalDays" may be recorded and may include the total number of days the patient wears the medical device. In an example, the variable "totalPatientUsePercent" may be recorded and may include the percentage of time the device was worn relative to the requested date range. In an example, the variable "firstWearDate" may be recorded and may include the first wear date. In an example, the variable "lastWearDate" may be recorded and may include the last wear date. In an example, the variable "calendarDate" may be recorded and may include the calendar date. In an example, a variable "dailyCompliance" may be recorded and may include the first and last wear day segments in which the patient exceeded the minimum daily threshold. In an example, a variable "totalSeconds" may be recorded and may include the combined wear duration of all segments in a given calendar day. In an example, a variable "compliancePercentage" may be recorded and may include the percentage of time the medical device was worn by the patient on a given day. The variables described herein are provided as examples only for illustrative purposes and are not intended to limit the scope of the database tables described herein.
[0204] The above-mentioned wearing compliance detection process refers to heart rate data. The heart rate used in compliance monitoring may be determined using one or more detection methods or processes. For example, implementations of heart rate detection may include, but are not limited to, one or more of the following: • Analysis of ECG time signal: By measuring the duration between two ECG complexes, the heart rate is assessed. Derivative-based detector: To detect complexes, a derivative filter is utilized to highlight the complexes. The output of the filter is then compared with a dynamic threshold to determine if an ECG complex has been detected. QRS Detector: To detect the heart rate, the detector analyzes the ECG signal slope to detect the presence of QRS complexes. This is achieved by applying a differential filter. The ECG signal from the ADC is first band-pass filtered (2Hz-20Hz) to remove baseline fluctuations and high frequency noise. The output of this band-pass filter is then fed to the QRS detector, which performs the slope analysis. If the QRS detector had otherwise detected a QRS complex and a zero, the output of the QRS detector will be a binary value equal to 1. The QRS rate is assessed by measuring the period between two successive peaks of the ECG signal and comparing the output to an adaptive threshold. Axial Detector: To detect complexes, a complex match filter operation is performed to find the similarity between the captured ECG and the incoming ECG. The idea behind the Axial Detector is to perform a waveform feature analysis. The analysis starts by capturing ECG waveforms from both channels. The captured waveform is compared with the incoming ECG via a complex match filter. If there is sufficient similarity between the captured ECG and the incoming ECG, a match is detected. The matched complexes per minute provide an indication of the heart rate. Analysis of ECG spectrum: Heart rate can be measured by decomposing the ECG signal into its spectrum. This method is suitable for ventricular tachycardia / fibrillation, where ECG time signal analysis often has difficulty in assessing the heart rate. The ECG signal to be analyzed is decimated from 200 Hz to 25 Hz. A spectrum analyzer can decompose the decimated ECG into its spectrum. Spectral analysis is achieved by calculating the energy distribution in the spectrum. Tachycardia or fibrillation often results in a spectrum that tends to be centered at a particular frequency corresponding to the heart rate. In an example, the spectrum analysis can be performed once per second. For example, the index of the largest peak magnitude between 2 Hz and 6 Hz is determined, thus indicating the fundamental frequency. The percentage of power at the fundamental frequency is determined. If this power exceeds a predefined threshold, the rate can be determined based on the fundamental frequency (e.g., the inverse of the frequency value).
Claims
1. 1. A wearable defibrillator for providing patient wear compliance information, comprising: a plurality of electrodes configured to be continuously externally coupled to a patient over an extended period of time, the plurality of electrodes configured to monitor electrical activity on the patient's skin and to deliver a therapeutic shock to the patient in response to detection of a cardiac arrhythmia based on the monitored electrical activity; at least one motion sensor and associated circuitry configured to generate at least one motion signal based on movement of the patient; and at least one processor operatively coupled to the plurality of electrodes and the at least one motion sensor and associated circuitry, receiving at least one electrical signal based on the monitored electrical activity on the skin of the patient from the plurality of electrodes; recording a wear-onset event based on the at least one electrical signal and the at least one motion signal indicating that the patient is wearing the wearable defibrillator. recording a wear-off event based on one or more of the at least one electrical signal or the at least one movement signal indicating that the patient is no longer wearing the wearable defibrillator; and outputting a graphical representation including information regarding the patient's wear compliance based on the recorded wear start events and the recorded wear end events. At least one processor configured to: A wearable defibrillator comprising:
2. Recording the mounting start event includes: detecting one or more ECG signals based on the at least one electrical signal; determining whether the one or more ECG signals meet one or more validity criteria; and recording the onset of wear event if the one or more ECG signals meet at least one of the one or more validity criteria. Including, The wearable defibrillator of claim 1 .
3. 3. The wearable defibrillator of claim 2, wherein the one or more validity criteria include at least one ECG parameter derived from the one or more ECG signals that meets a validity threshold.
4. 4. The wearable defibrillator of claim 3, wherein the at least one ECG parameter includes an R-peak amplitude, and wherein meeting the validity threshold includes identifying at least five consecutive R-peak amplitudes each exceeding an amplitude threshold.
5. 4. The wearable defibrillator of claim 3, wherein the at least one ECG parameter includes a QRS complex width, and wherein meeting the validity threshold includes measuring at least five consecutive QRS complex widths, each QRS complex width being between 0.05 seconds and 0.15 seconds.
6. 4. The wearable defibrillator of claim 3, wherein the at least one processor is further configured to determine the patient's wear compliance based on a first ECG signal of the one or more ECG signals that meets the validity threshold.
7. 7. The wearable defibrillator of claim 1, further comprising a display operably coupled to the at least one processor, the at least one processor configured to provide, via the display, the graphical representation of the patient's wear compliance based on output information regarding the patient's wear compliance.
8. 8. The wearable defibrillator of claim 1, further comprising a network interface operably coupled to the at least one processor, the at least one processor configured to transmit the information regarding the patient's wearing compliance to a remote server.
9. The at least one processor further comprises: detecting an electrocardiogram (ECG) signal based on the at least one electrical signal; and controlling the wearable defibrillator to deliver an ECG signal therapeutic shock to the patient in response to the detection of the cardiac arrhythmia based on the detected ECG signal.
4. The method of claim 3, A wearable defibrillator according to any one of claims 1 to 8.
10. Recording the mounting start event includes: detecting an impedance level of a skin-sensor interface based on the at least one electrical signal at one or more of the plurality of electrodes; determining whether the impedance level is within an acceptable impedance range; and recording the attachment start event if the impedance level is within the acceptable impedance range. and To record the end of record attachment event, determining whether the impedance level is no longer within the acceptable impedance range; and recording the end-of-wear event based on a determination that the impedance level is no longer within the acceptable impedance range. Includes The wearable defibrillator of claim 1 .
11. 11. The wearable defibrillator of claim 10, wherein the acceptable impedance ranges include at least one of a range from 20 ohms to 250 ohms, a range from 250 ohms to 1 kilohm, and a range from 1 kilohm to 20 kilohm.
12. Recording the mounting start event includes: determining whether the motion signal is indicative of movement of the patient and the wearable defibrillator; and recording the wear-onset event if the motion signal indicates movement of the patient and the wearable defibrillator. Including, The wearable defibrillator of claim 1 .
13. The at least one processor further comprises: detecting one or more ECG signals based on the at least one electrical signal if the motion signal is not indicative of movement of the patient and the wearable defibrillator; and recording the onset of wear event based on analysis of the one or more ECG signals.
4. The method of claim 3, 13. The wearable defibrillator of claim 12.
14. The at least one processor further comprises: detecting one or more noise components in the at least one electrical signal; and determining the absence of patient motion based on an analysis of the one or more noise components in at least one electrical signal; 4. The method of claim 3, 14. The wearable defibrillator of claim 13.
15. Recording the mounting start event includes: receiving an input from the patient specifying that the patient is wearing the wearable defibrillator; and recording the start of wear event based on the input from the patient; Including, The wearable defibrillator of claim 1 .
16. Recording the start of wear event based on the input from the patient includes: verifying that the patient is wearing the wearable defibrillator based on the at least one electrical signal and the at least one movement signal; and Recording the mounting start event. Including, 16. The wearable defibrillator of claim 15.
17. Recording the end-of-wear event includes: detecting a change in the at least one electrical signal indicative of an invalid ECG signal; and recording the end-of-wear event based on the invalid ECG signal. Including, A wearable defibrillator according to any one of claims 1 to 16.
18. Recording the end-of-wear event includes: detecting a change in impedance level of a skin-sensor interface at one or more of the plurality of electrodes; determining whether the impedance level exceeds an impedance threshold; and recording the end-of-wear event if the impedance level exceeds the impedance threshold. Including, 18. A wearable defibrillator according to any one of claims 1 to 17.
19. 20. The wearable defibrillator of claim 18, wherein the impedance thresholds include one or more of 10 kilohms, 100 kilohms, 1 megahms, 2 megahms, 5 megahms, or 10 megahms.
20. Recording the end-of-wear event includes: determining that one or more of the plurality of electrodes, or the at least one motion sensor and associated circuitry, are disconnected from the wearable defibrillator; and recording the end-of-wear event when it is determined that one or more of the plurality of electrodes, or the at least one motion sensor and associated circuitry, is disconnected. Including, 18. A wearable defibrillator according to any one of claims 1 to 17.
21. Recording the end-of-wear event includes: detecting that the patient has removed the wearable defibrillator based on analysis of the at least one motion signal; determining that the at least one electrical signal indicates that the patient has removed the wearable defibrillator; and recording the end-of-wear event upon confirmation that the patient has removed the wearable defibrillator. Including, 18. A wearable defibrillator according to any one of claims 1 to 17.
22. Recording the end-of-wear event includes: receiving an input from the patient specifying that the patient is removing the wearable defibrillator; and recording the end-of-wear event based on the input from the patient. Including, 18. A wearable defibrillator according to any one of claims 1 to 17.
23. recording the end-of-wear event based on the input from the patient, determining that the patient has removed the wearable defibrillator based on the at least one electrical signal and the at least one movement signal; and recording said end-of-wear event; Including, 23. The wearable defibrillator of claim 22.
24. The at least one processor further comprises: Determining a current time; and recording at least one of the wearing start event and the wearing end event based on one or more of the at least one movement signal, the at least one electrical signal, and the current time.
4. The method of claim 3, 24. A wearable defibrillator according to any one of claims 1 to 23.
25. 25. The wearable defibrillator of claim 24, wherein determining the current time includes determining whether the patient has ever been in an active state or an inactive state based on the current time.
26. 26. The wearable defibrillator of claim 25, wherein the at least one processor is further configured to record at least one of the wear start event and the wear end event based on the at least one electrical signal if the patient is previously inactive at the current time.
27. 26. The wearable defibrillator of claim 25, wherein the at least one processor is further configured to record at least one of the wear start event and the wear end event based on the at least one electrical signal and the at least one motion signal if the patient is ever in an active state at the current time.
28. 26. The wearable defibrillator of claim 25, wherein the at least one processor is further configured to determine whether the patient has ever been in an active state or an inactive state based on the current time and past patient activity information recorded by the wearable defibrillator.
29. 29. The wearable defibrillator of claim 1, wherein the graphical representation includes an indication of patient wear compliance versus patient wear non-compliance.
30. 29. The wearable defibrillator of claim 1, wherein the graphical representation includes an indication of a recorded change in wear compliance for the patient.
31. The wearable defibrillator of claim 1 , wherein the graphical representation includes a timeline illustrating recorded wear start and end events.
32. 32. The wearable defibrillator of claim 31 , wherein the timeline further indicates a total time the wearable defibrillator was worn by the patient and a total time the wearable defibrillator was not worn by the patient over a user selectable period of time.
33. 2. The wearable defibrillator of claim 1, wherein the graphical representation includes one or more user-selectable interface controls configured to provide access to recorded ECG information for one or more of a wear start event, a wear end event, and a period during which the patient wore the wearable defibrillator.
34. The wearable defibrillator of claim 1 , wherein the at least one processor is further configured to output a notification of the patient's wear compliance.
35. Outputting the indication of the patient's wear compliance includes: comparing said patient's wear compliance with one or more notification criteria; and outputting the notification if the patient's wear compliance meets at least one of the one or more notification criteria. Including, 35. The wearable defibrillator of claim 34.
36. 36. The wearable defibrillator of claim 35, wherein the one or more notification criteria include the patient failing to wear the wearable defibrillator for a particular percentage of a period of time.
37. 36. The wearable defibrillator of claim 35, wherein the one or more notification criteria include a recorded change in the patient's wear compliance exceeding a compliance change threshold.
38. 35. The wearable defibrillator of claim 34, wherein the at least one processor is further configured to output the notification of the patient's wear compliance to one or more of the patient, a care provider associated with the patient, or a prescriber of the wearable defibrillator.
39. 1. A method for providing wear compliance information recorded by a wearable defibrillator worn by a patient, comprising: receiving, by at least one processor, at least one electrical signal determined based on monitored electrical activity on the patient's skin from a plurality of electrodes operatively coupled to the at least one processor; receiving, by the at least one processor, at least one motion signal based on the patient's movement and generated by at least one motion sensor and associated circuitry operably coupled to the at least one processor; recording, by the at least one processor, a wearing start event based on one or more of the at least one electrical signal or the at least one motion signal indicating that the patient is wearing the wearable defibrillator; recording, by the at least one processor, a wear termination event based on one or more of the at least one electrical signal and the at least one motion signal indicating that the patient is not wearing the wearable defibrillator; providing, by the at least one processor, a graphical representation of the patient's wear compliance based on the recorded wear start events and the recorded wear end events; receiving, by the at least one processor, one or more notification criteria from one or more of the patient's care provider or a prescriber of the wearable defibrillator; the at least one processor comparing the patient's wear compliance and the one or more notification criteria; and If the patient's wear compliance meets at least one of the one or more notification criteria, the at least one processor outputs a notification to one or more of the patient, the patient's care provider, or the prescriber of the wearable defibrillator. A method comprising:
40. 40. The method of claim 39, further comprising the step of: outputting, to a display operatively coupled to the at least one processor, a graphical representation of the patient's wear compliance based on the output information regarding the patient's wear compliance.
41. 40. The method of claim 39, further comprising the at least one processor transmitting information regarding the patient's wear compliance via a network interface to a remote server operably coupled to the at least one processor.
42. The step of recording the mounting start event includes: detecting, by the at least one processor, one or more ECG signals based on the at least one electrical signal; the at least one processor determining whether the one or more ECG signals meet one or more validity criteria; and and recording, by the at least one processor, the onset of wearing event if the one or more ECG signals meet at least one of the one or more validity criteria. and The step of recording the end of mounting event comprises: the at least one processor determining whether the impedance level is no longer within an acceptable impedance range; and recording the end-of-wear event based on the at least one processor determining that the impedance level is no longer within the acceptable impedance range. have 40. The method of claim 39.
43. 43. The method of claim 42, wherein the one or more validity criteria include at least one ECG parameter derived from the one or more ECG signals that meets a validity threshold.
44. 44. The method of claim 43, wherein the at least one ECG parameter includes an R-peak amplitude, and wherein meeting the validity threshold includes identifying at least five consecutive R-peak amplitudes each exceeding an amplitude threshold.
45. 44. The method of claim 43, wherein the at least one ECG parameter includes a QRS complex width, and wherein meeting the validity threshold includes measuring at least five consecutive QRS complex widths, each QRS complex width being between 0.05 seconds and 0.15 seconds.
46. 44. The method of claim 43, further comprising the at least one processor determining the patient's wear compliance based on a first ECG signal of the one or more ECG signals that meets the validity threshold.
47. Recording the mounting start event includes: detecting an impedance level of a skin-sensor interface at one or more of the plurality of electrodes; determining whether the impedance level is within an acceptable impedance range; and recording the attachment start event if the impedance level is within the acceptable impedance range. Including, 40. The method of claim 39.
48. 48. The method of claim 47, wherein the acceptable impedance range includes at least one of a range from 20 ohms to 250 ohms, a range from 250 ohms to 1 kilohm, and a range from 1 kilohm to 20 kilohm.
49. The step of recording the mounting start event includes: the at least one processor determining whether the motion signal is indicative of movement of the patient and the wearable defibrillator; and and if the motion signal indicates movement of the patient and the wearable defibrillator, the at least one processor records the wear-onset event. Including, 40. The method of claim 39.
50. detecting, by the at least one processor, one or more ECG signals based on the at least one electrical signal if the motion signal is not indicative of movement of the patient and the wearable defibrillator; and recording the onset event based on analysis of the one or more ECG signals by the at least one processor.
50. The method of claim 49, further comprising:
51. the at least one processor detecting one or more noise components in the at least one electrical signal; and determining, by the at least one processor, that there is no motion of the patient based on an analysis of the one or more noise components in at least one electrical signal; 51. The method of claim 50, further comprising:
52. The step of recording the mounting start event includes: receiving, by the at least one processor, an input from the patient specifying that the patient is wearing the wearable defibrillator; and recording the start of wear event based on the input from the patient, having 40. The method of claim 39.
53. The step of recording the start of wear event based on the input from the patient comprises: verifying, by the at least one processor, that the patient is wearing the wearable defibrillator based on the at least one electrical signal and the at least one movement signal; and said at least one processor recording said mounting start event. Including, 53. The method of claim 52.
54. The step of recording the end of mounting event comprises: detecting, by the at least one processor, a change in the at least one electrical signal indicative of an invalid ECG signal; and the at least one processor recording the end-of-wear event based on the invalid ECG signal. Including, 40. The method of claim 39.
55. The step of recording the end of mounting event comprises: detecting a change in impedance level of a skin-sensor interface at one or more of the plurality of electrodes with the at least one processor; the at least one processor determining whether the impedance level exceeds an impedance threshold; and If the impedance level exceeds the impedance threshold, the at least one processor records the end-of-wear event. Including, 40. The method of claim 39.
56. 56. The method of claim 55, wherein the impedance threshold comprises one or more of 10 kilohms, 100 kilohms, 1 megahms, 2 megahms, 5 megahms, or 10 megahms.
57. The step of recording the end of mounting event comprises: determining, by the at least one processor, that one or more of the plurality of electrodes and the at least one motion sensor and associated circuitry are disconnected from the wearable defibrillator; and and upon determining that one or more of the plurality of electrodes and the at least one motion sensor and associated circuitry are disconnected, the at least one processor records the end-of-wear event. Including, 40. The method of claim 39.
58. The step of recording the end of mounting event comprises: detecting, by the at least one processor, that the patient has removed the wearable defibrillator based on analysis of the at least one motion signal; determining, by the at least one processor, that the at least one electrical signal indicates that the patient has removed the wearable defibrillator; and recording the end-of-wear event based on confirmation by the at least one processor that the patient has removed the wearable defibrillator. Including, 40. The method of claim 39.
59. The step of recording the end of mounting event comprises: receiving, by the at least one processor, an input from the patient specifying that the patient is removing the wearable defibrillator; and recording the end-of-wear event based on the input from the patient, having 40. The method of claim 39.
60. The step of recording the end of wear event based on the input from the patient comprises: determining, based on the at least one electrical signal and the at least one motion signal, that the patient has removed the wearable defibrillator; and said at least one processor recording said end-of-wear event. Including, 60. The method of claim 59.
61. said at least one processor determining a current time; and recording at least one of the wearing start event and the wearing end event based on one or more of the at least one movement signal, the at least one electrical signal, or the current time, by the at least one processor; 40. The method of claim 39, further comprising:
62. 62. The method of claim 61, wherein determining the current time comprises the at least one processor determining whether the patient is ever in an active state or an inactive state based on the current time.
63. 63. The method of claim 62, further comprising the at least one processor recording at least one of the wear start event and the wear end event based on the at least one electrical signal if the patient is previously inactive at the current time.
64. 63. The method of claim 62, further comprising the step of: if the patient is previously in an active state at the current time, the at least one processor recording at least one of the wear start event and the wear end event based on the at least one electrical signal and the at least one movement signal.
65. 63. The method of claim 62, further comprising the at least one processor determining whether the patient has ever been in an active state or an inactive state based on the current time and historical patient activity information recorded by the wearable defibrillator.
66. 40. The method of claim 39, wherein the notification includes an indication of patient wear compliance versus patient wear non-compliance.
67. 40. The method of claim 39, wherein the notification includes an indication of a recorded change in wear compliance for the patient.
68. 40. The method of claim 39, wherein the notification includes a timeline showing recorded wear start and wear end events.
69. 69. The method of claim 68, wherein the timeline further indicates a total time the wearable defibrillator was worn by the patient and a total time the wearable defibrillator was not worn by the patient over a user selectable period of time.
70. 40. The method of claim 39, wherein the notification includes one or more user-selectable interface controls configured to provide access to recorded ECG information for one or more of a wear start event, a wear end event, or a period during which the patient wore the wearable defibrillator.
71. The step of outputting the notification of the patient's wear compliance includes: said at least one processor comparing said patient's wear compliance to one or more notification criteria; and and outputting said notification when said patient's wear compliance meets at least one of said one or more notification criteria.
40. The method of claim 39, having the following structure:
72. 72. The method of claim 71, wherein the one or more notification criteria include the patient failing to wear the wearable defibrillator for a particular percentage of a period of time.
73. 72. The method of claim 71, wherein the one or more notification criteria comprises a recorded change in the patient's wear compliance exceeding a compliance change threshold.
