Patent Application
20240075208
Many conventional automated drug delivery (ADD) systems are well known, including, for example, wearable drug delivery devices. The drug delivery device can be designed to deliver any type of liquid drug to a user. In specific embodiments, the drug delivery device can be, for example, an OmniPod® drug delivery device manufactured by Insulet Corporation of Acton, Massachusetts. The drug delivery device can be a drug delivery device such as those described in U.S. Pat. Nos. 7,303,549, 7,137,964, or 6,740,059, each of which is incorporated herein by reference in its entirety.
Such drug delivery devices typically include a positive displacement pumping mechanism to force a liquid drug from a reservoir through a fluid path to the patient. The fluid path typically comprises a flexible tube or needle coupled, at one end, to the reservoir. The other end of the fluid path is coupled to a cannula which is inserted under the skin of the patient for delivery of the liquid drug. The cannula may be inserted via a needle mechanism wherein a needle/cannula combination is forced by an actuator into the skin of the user and thereafter the needle is withdrawn, leaving the cannula in place. The cannula may have one or more ports defined on a distal end thereof through which the liquid drug is dispensed.
It is not uncommon for the one or more ports to become fully or partially clogged or occluded. The occlusions may be caused, for example, by body fluids, immunoglobulins, or protein aggregates, or even insulin aggregates, formed as the insulin denatures, which accumulate in the fluid path. Most commonly, the occlusions occur at or near the distal end of the cannula and may clog the one or more ports. Less commonly, the occlusions occur at other points along the fluid path. The occlusions may reduce the amount of the liquid drug that can be dispensed or may potentially preclude dispensing any quantity of the liquid drug.
Occlusions occurring at insulin delivery sites (pump sites) is a major challenge in ensuring safe and effective insulin delivery for people with diabetes that utilize subcutaneous insulin pumps. For continuous subcutaneous insulin infusion, a reduction in the insulin delivery due to a fluid occlusion can cause harm in people managing diabetes. The venous glucose of a T1 diabetic, for example, can change at a rate of up to about 1 mg/dL/minute. In the absence of a steady basal delivery of insulin, the patient may quickly become hyperglycemic.
Thus, it would be desirable to be able to detect when occlusions that reduce or stop the delivery of insulin occur, so as to enable the drug delivery system to take remedial action, or, alternatively, warn the user of a potentially dangerous situation, such that the user can take remedial action.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended as an aid in determining the scope of the claimed subject matter.
In one embodiment of the invention, disclosed herein is an automatic drug delivery (ADD) system which is designed to detect or confirm the detection of occlusions in the fluid path and a software-based method for detecting or confirming the detection of occlusions in the fluid path of an automated drug delivery system. The invention proposes the use of real time glucose readings from a continuous glucose monitor in collaboration with past insulin delivery history, and, where available, user indications of ingestion of carbohydrates, to determine cases where the user's glucose concentration is not being sufficiently impacted by the expected insulin delivery, which may indicate a significant pump site issue.
A hardware-based occlusion sensor was disclosed in U.S. Provisional Patent Application No. 63/359,010, filed Jul. 7, 2022, the contents of which are incorporated herein by reference in their entirety. The software-based method disclosed herein can be used in lieu of hardware-based methods or can augment hardware-based methods to confirm indications of an occlusion.
In the drawings, like reference characters generally refer to the same parts throughout the different views. In the following description, various embodiments of the present invention are described with reference to the following drawings, in which:
Various embodiments of the present invention include systems and methods for delivering a medication to a user using a drug delivery device, either autonomously, and/or in accordance with a wireless signal received from an electronic device. In various embodiments, the electronic device may be a user device comprising a smartphone, a smart watch, a smart necklace, a module attached to the drug delivery device, or any other type or sort of electronic device that may be carried by the user or worn on the body of the user and that executes an algorithm that computes the times and dosages of delivery of the medication. Alternatively, the drug delivery device operates an algorithm stored on the drug delivery device itself, without reliance on a remote electronic device for delivering medicament to the user.
For example, the user device or drug delivery device may execute an “artificial-pancreas” (AP) algorithm that computes the times and dosages of delivery of insulin. The user device and/or drug delivery device may also be in communication with a sensor, such as a glucose sensor or a continuous glucose monitor (CGM), that collects data on a physical attribute or condition of the user, such as a glucose level. The sensor may be disposed in or on the body of the user and may be part of the drug delivery device or may be a separate device.
Alternatively, the drug delivery device may be in communication with the sensor in lieu of or in addition to the communication between the sensor and the user device. The communication may be direct (if, e.g., the sensor is integrated with or otherwise a part of the drug delivery device) or remote/wireless (if, e.g., the sensor is disposed in a different housing than the drug delivery device). In these embodiments, the drug delivery device contains computing hardware (e.g., a processor, memory, firmware, etc.) that executes some or all of the algorithm that computes the times and dosages of delivery of the medication.
It should be understood that all computation steps, software steps, control steps and/or algorithm steps described in this disclosure may be carried out by a processor in a single device of the system, i.e. by a processor in the drug delivery device, by a processor in the user device, by a processor in the analyte sensor, by a processor in the accessory device or by a processor of the cloud server. Alternatively, the computation steps, software steps, control steps and algorithm steps described in this disclosure may be performed by two or more processors in the mentioned devices, i.e. in the drug delivery device, in the user device, in the analyte sensor, in the accessory device and/or in the cloud server. As these devices can communicate with each other, it is generally irrelevant which of these processors perform the respective steps.
Drug delivery system 100, in an optional example, may also include an accessory device 106, such as a smartwatch, a personal assistant device, a smart insulin pen, or the like, which may communicate with the other components of system 100 via either a wired or wireless communication links 191-193.
The user device 105 may be a computing device such as a smartphone, a smartwatch, a tablet, a personal diabetes management (PDM) device, a dedicated diabetes therapy management device, or the like. In an example, user device 105 may include a processor 151, device memory 153, a user interface 158, and a communication interface 154. The user device 105 may also contain analog and/or digital circuitry that may be implemented as a processor 151 for executing processes based on programming code stored in device memory 153, such as user application 160 incorporating medication delivery algorithm (MDA) 161 to manage a user's blood glucose levels and for controlling the delivery of the drug, medication, or therapeutic agent to the user, as well for providing other functions, such as calculating carbohydrate-compensation dosage, a correction bolus dosage and the like as discussed below. The user device 105 may be used to activate, deactivate, trigger a needle/canula insertion, program, adjust settings, and/or control operation of drug delivery device 102 and/or the analyte sensor 103 as well as the optional smart accessory device 106.
The processor 151 may also be configured to execute programming code stored in device memory 153, such as the user app 160. The user app 160 may be a computer application that is operable to deliver a drug based on information received from the analyte sensor 103, the cloud-based services 111 and/or the user device 105 or optional accessory device 106. The memory 153 may also store programming code to, for example, operate the user interface 158 (e.g., a touchscreen device, a camera or the like), the communication interface 154 and the like. The processor 151, when executing user app 160, may be configured to implement indications and notifications related to meal ingestion, blood glucose measurements, and the like. The user interface 158 may be under the control of the processor 151 and be configured to present a graphical user interface that enables the input of a meal announcement, adjust setting selections and the like as described herein.
In a specific example, when the user app 160 includes MDA 161, the processor 151 is also configured to execute a diabetes treatment plan (which may be stored in a memory) that is managed by user app 160. In addition to the functions mentioned above, when user app 160 is an AP application, it may further provide functionality to determine a carbohydrate-compensation dosage, a correction bolus dosage and determine a real-time basal dosage according to a diabetes treatment plan. In addition, as a MDA 161, user app 160 provides functionality to output signals to the drug delivery device 102 via communications interface 154 to deliver the determined bolus and/or basal dosages.
The communication interface 154 may include one or more transceivers that operate according to one or more radio-frequency protocols. In one embodiment, the transceivers may comprise a cellular transceiver and a Bluetooth® transceiver. The communication interface 154 may be configured to receive and transmit signals containing information usable by user app 160.
User device 105 may be further provided with one or more output devices 155 which may be, for example, a speaker or a vibration transducer, to provide various signals to the user.
In various exemplary embodiments, drug delivery device 102 may include a reservoir 124 and drive mechanism 125, which are controllable by controller 121, executing a medication delivery algorithm (MDA) 129 stored in memory 123, which may perform some or all of the functions of the AP application described above, such that user device 105 may be unnecessary for drug delivery device 102 to carry out drug delivery and control. Alternatively, controller 121 may act to control reservoir 124 and drive mechanism 125 based on signals received from user app 160 executing on a user device 105 and communicated to drug delivery device 102 via communication link 194. Drive mechanism 125 may operate to longitudinally translate a plunger through the reservoir, so as to force the liquid drug through an outlet fluid port to needle/cannula 186. Alternatively, other types of drive mechanisms may be used.
In an alternate embodiment, drug delivery device 102 may also include an optional second reservoir 124-2 and second drive mechanism 125-2 which enables the independent delivery of two different liquid drugs. As an example, reservoir 124 may be filled with insulin, while reservoir 124-2 may be filled with glucagon, or Pramlintide, or GLP-1. In some embodiments, each of reservoirs 124, 124-2 may be configured with a separate drive mechanism 125, 125-2, respectively, which may be separately controllable by controller 121 under the direction of MDA 129. Both reservoirs 124, 124-2 may be connected to a common needle/cannula 186.
Drug delivery device 102 may be optionally configured with a user interface 127 providing a means for receiving input from the user and a means for outputting information to the user. User interface 127 may include, for example, light-emitting diodes, buttons on a housing of drug delivery device 102, a sound transducer, a micro-display, a microphone, an accelerometer for detecting motions of the device or user gestures (e.g., tapping on a housing of the device) or any other type of interface device that is configured to allow a user to enter information and/or allow drug delivery device 102 to output information for presentation to the user (e.g., alarm signals or the like).
Drug delivery device 102 includes a patient interface 186 for interfacing with the user to deliver the liquid drug. Patient interface may be, for example, a needle or cannula for delivering the drug into the body of the user (which may be done subcutaneously, intraperitoneally, or intravenously). Drug delivery device 102 may further include a mechanism for inserting the needle/cannula 186 into the body of the user, which may be integral with or attachable to drug delivery device 102. The insertion mechanism may comprise, in one embodiment, an actuator that inserts the needle/cannula 186 under the skin of the user and thereafter retracts the needle, leaving the cannula in place. The actuator may be triggered by user device 105 or may be a manual firing mechanism comprising springs or other energy storing mechanism, that causes the needle/cannula 186 to penetrate the skin of the user.
In one embodiment, drug delivery device 102 includes a communication interface 126, which may be a transceiver that operates according to one or more radio-frequency protocols, such as Bluetooth®, Wi-Fi, near-field communication, cellular, or the like. The controller 121 may, for example, communicate with user device 105 and an analyte sensor 108 via the communication interface 126.
In some embodiments, drug delivery device 102 may be provided with one or more sensors 184. The sensors 184 may include one or more of a pressure sensor, a power sensor, or the like that are communicatively coupled to the controller 121 and provide various signals. For example, a pressure sensor may be configured to provide an indication of the fluid pressure detected in a fluid pathway between the patient interface 186 and reservoir 124. The pressure sensor may be coupled to or integral with the actuator for inserting the patient interface 186 into the user. In an example, the controller 121 may be operable to determine a rate of drug infusion based on the indication of the fluid pressure. The rate of drug infusion may be compared to an infusion rate threshold, and the comparison result may be usable in determining an amount of insulin onboard (IOB) or a total daily insulin (TDI) amount. In one embodiment, analyte sensor 108 may be integral with drug delivery device 102.
Drug delivery device 102 further includes a power source 128, such as a battery, a piezoelectric device, an energy harvesting device, or the like, for supplying electrical power to controller 121, memory 123, drive mechanisms 125 and/or other components of drug delivery device 102.
Drug delivery device 102 may be configured to perform and execute processes required to deliver doses of the medication to the user without input from the user device 105 or the optional accessory device 106. As explained in more detail, MDA 129 may be operable, for example, to determine an amount of insulin to be delivered, IOB, insulin remaining, and the like and to cause controller 121 to activate drive mechanism 125 to deliver the medication from reservoir 124. MDA 129 may take as input data received from the analyte sensor 108 or from user app 160.
The reservoirs 124, 124-2 may be configured to store drugs, medications or therapeutic agents suitable for automated delivery, such as insulin, Pramlintide, GLP-1, co-formulations of insulin and GLP-1, glucagon, morphine, blood pressure medicines, arthritis drugs, chemotherapy drugs, fertility drugs, hormonal drugs, or the like.
Drug delivery device 102 may be a wearable device and may be attached to the body of a user, such as a patient or diabetic, at an attachment location and may deliver any therapeutic agent, including any drug or medicine, such as insulin or the like, to a user at or around the attachment location. A surface of drug delivery device 102 may include an adhesive to facilitate attachment to the skin of a user.
When configured to communicate with an external device, such as the user device 105 or the analyte sensor 108, drug delivery device 102 may receive signals over the wired or wireless link 194 from the user device 105 or from the analyte sensor 108. The controller 121 of drug delivery device 102 may receive and process the signals from the respective external devices as well as implementing delivery of a drug to the user according to a diabetes treatment plan or other drug delivery regimen.
Optional accessory device 106 may be, a wearable smart device, for example, a smart watch (e.g., an Apple Watch®), smart eyeglasses, smart jewelry, a global positioning system-enabled wearable, a wearable fitness device, smart clothing, or the like. Accessory device 106 may alternatively be a smart insulin pen that works with drug delivery device 102 in managing blood glucose and treating diabetes of a user. Similar to user device 105, the accessory device 106 may also be configured to perform various functions including controlling or communicating with drug delivery device 102. For example, the accessory device 106 may include a communication interface 174, a processor 171, a user interface 178 and a memory 173. The user interface 178 may be a graphical user interface presented on a touchscreen display of the smart accessory device 107. The memory 173 may store programming code to operate different functions of the smart accessory device 107 as well as an instance of the user app 160, or a pared-down version of user app 160 with reduced functionality. In some instances, accessory device 107 may also include sensors of various types.
The analyte sensor 108 may include a controller 131, a memory 132, a sensing/measuring device 133, an optional user interface 137, a power source/energy harvesting circuitry 134, and a communication interface 135. The analyte sensor 108 may be communicatively coupled to the processor 151 of the management device 105 or controller 121 of drug delivery device 102. The memory 132 may be configured to store information and programming code 136.
The analyte sensor 108 may be configured to detect one or multiple different analytes, such as glucose, lactate, ketones, uric acid, sodium, potassium, alcohol levels or the like, and output results of the detections, such as measurement values or the like. The analyte sensor 108 may, in an exemplary embodiment, be configured as a continuous glucose monitor (CGM) to measure a blood glucose values at a predetermined time interval, such as every 5 minutes, every 1 minute, or the like. The communication interface 135 of analyte sensor 108 may have circuitry that operates as a transceiver for communicating the measured blood glucose values to the user device 105 over a wireless link 195 or with drug delivery device 102 over the wireless communication link 108. While referred to herein as an analyte sensor 108, the sensing/measuring device 133 of the analyte sensor 108 may include one or more additional sensing elements, such as a glucose measurement element, a heart rate monitor, a pressure sensor, or the like. The controller 131 may include discrete, specialized logic and/or components, an application-specific integrated circuit, a microcontroller or processor that executes software instructions, firmware, programming instructions stored in memory (such as memory 132), or any combination thereof.
Similar to the controller 121 of drug delivery device 102, the controller 131 of the analyte sensor 108 may be operable to perform many functions. For example, the controller 131 may be configured by programming code 136 to manage the collection and analysis of data detected by the sensing and measuring device 133.
Although the analyte sensor 108 is depicted in
Drug delivery system 100 may communicate with or receive services from a cloud server 122 providing cloud-based services 111. Services provided by cloud server 112 may include data storage that stores personal or anonymized data, such as blood glucose measurement values, historical IOB or TDI, prior carbohydrate-compensation dosage, and other forms of data. In addition, the cloud-based services 111 may process anonymized data from multiple users to provide generalized information related to TDI, insulin sensitivity, IOB and the like. The communication link 115 that couples the cloud server 112 to other components of system 100, for example, devices 102, 105, 106, 108 of system 100 may be a cellular link, a Wi-Fi link, a Bluetooth® link, or a combination thereof.
The wireless communication links 115 and 191-196 may be any type of wireless link operating using known wireless communication standards or proprietary standards. As an example, the wireless communication links 191-196 may provide communication links based on Bluetooth®, Zigbee®, Wi-Fi, a near-field communication standard, a cellular standard, or any other wireless protocol via the respective communication interfaces 126, 135, 154 and 174.
In an operational example, user application 160 implements a graphical user interface that is the primary interface with the user and may be used to activate drug delivery device 102, trigger a needle/cannula insertion, start and stop drug delivery device 102, program basal and bolus calculator settings for manual mode as well as program settings specific for automated mode (hybrid closed-loop or closed-loop).
User app 160, provides a graphical user interface 158 that allows for the use of large text, graphics, and on-screen instructions to prompt the user through the set-up processes and the use of system 100. It may also be used to program the user's custom basal insulin delivery profile, accept a recommended basal insulin delivery profile, check the status of drug delivery device 102, initiate bolus doses of insulin, make changes to a patient's insulin delivery profile, handle system alerts and alarms, or allow the user to switch between automated mode and manual mode.
User app 160 may be configured to operate in a manual mode in which user app 160 will deliver insulin at programmed basal rates and user-defined bolus amounts with the option to set temporary basal profiles. The controller 121 will also have the ability to function as a sensor-augmented pump in manual mode, using sensor glucose data provided by the analyte sensor 108 to populate the bolus calculator.
User app 160 may be configured to operate in an automated mode in which user app 160 supports the use of one or multiple target blood glucose values that may be adjusted manually or automatically by the system. For example, in one embodiment, target blood glucose values can range from 110-150 mg/dL, in 10 mg/dL increments, in 5 mg/dL increments, or other increments, but preferably 10 mg/dL increments. The experience for the user will reflect current setup flows whereby the healthcare provider assists the user to program basal rates, glucose targets and bolus calculator settings. These in turn will inform the user app 160 for insulin dosing parameters. The insulin dosing parameters will be adapted over time based on the total daily insulin (TDI) delivered during each use of drug delivery device 102. A temporary hypoglycemia protection mode or an activity mode may be implemented by the user for various time durations in automated mode. With hypoglycemia protection mode or an activity mode, the algorithm reduces insulin delivery and is intended for use over temporary durations when insulin sensitivity is expected to be higher, such as during exercise or fasting.
The user app 160 (or MDA 129) may provide periodic insulin micro-boluses based upon past glucose measurements and/or a predicted glucose over a prediction horizon (e.g., 60 minutes). Optimal post-prandial control may require the user to give meal boluses in the same manner as current pump therapy, but normal operation of the user app 160 will compensate for missed meal boluses and mitigate prolonged hyperglycemia. The user app 160 uses a control-to-target strategy that attempts to achieve and maintain a set target glucose value, thereby reducing the duration of prolonged hyperglycemia and hypoglycemia.
In some embodiments, user device 105 and the analyte sensor 108 may not communicate directly with one another. Instead, data (e.g., blood glucose readings) from analyte sensor may be communicated to drug delivery device 102 via link 196 and then relayed to user device 105 via link 194. In some embodiments, to enable communication between analyte sensor 108 and user device 105, the serial number of the analyte sensor must be entered into user app 160.
User app 160 may provide the ability to calculate a suggested bolus dose through the use of a bolus calculator. The bolus calculator is provided as a convenience to the user to aid in determining the suggested bolus dose based on ingested carbohydrates, most-recent blood glucose readings (or a blood glucose reading if using fingerstick), programmable correction factor, insulin to carbohydrate ratio, target glucose value, and insulin on board (IOB). IOB is estimated by user app 160 taking into account any manual bolus and insulin delivered by the algorithm.
The glucose concentration of a typical user of ADD system 100 can be impacted by a wide range of factors. Although an accurate model of the user's glucose concentrations may not be well implemented, the average mismatch between an assumed model and the user's actual glucose concentrations should, over time, be relatively consistent, assuming that the model is not modified and that the physiology or lifestyle of the user does not undergo major changes. Therefore, a significant, sudden increase in the mismatch between the typical deviation from the model predictions and the user's actual glucose levels can provide important insights to a potential issue with the user's insulin delivery, such as a pump occlusion or other site issues. The user's typical deviation from the model predictions can therefore be used to establish a baseline from which further deviations may be indicative of a possible occlusion in the fluid path of ADD system 100.
As shown in
IOB model 202 determines the expected impact of the user's insulin delivery history on the user's current glucose concentrations, based on the typical impact for a typical user. The model may be implemented by the following equations:
where 0.04 is a tunable parameter (in this case, 4%) that represents how much insulin in the body (IOB) is used by, or reduced in, the body in a 5-minute cycle. In this case, a value of 0.04 for the parameter may correspond to a reduction of approximately 50% of the remaining IOB over 90 minutes. The IOB at any cycle may be calculated by the following equation:
where past insulin delivery deviations from basal over an exemplary past 36 cycles are summed up, and each term is multiplied by a fraction in a matrix operation to account for the fact that the insulin has decayed (in this case, linear decay is assumed). The basal amount against which the deviation is calculated may correspond to the system's assumption of the user's basal needs and may be a value that is entered by the user directly, or a value automatically calculated based on prior insulin delivery history of the user. In the case of the use of prior insulin history, captured as the user's Total daily insulin, the insulin deviation can thus be calculated as follows:
where past insulin delivery deviations from basal are calculated, and “48” is the number of 5-minute cycles in 4 hours. Each equation is explained in further detail below.
As previously noted, MDA 129, as described above as part of ADD system 100 operates using 5-minute cycles. That is, a new blood glucose reading is typically received from sensor 108 at 5-minute intervals, at which time IOB model 202 and CHO model 204 described below are reevaluated. However, the invention is not meant to be limited thereby. Any time interval for reevaluating models 202, 204, whether tied to the receipt of a new blood glucose reading or not, is intended to be within the scope of the invention.
In IOB model 202, Eq. (1) gives the user's drop in blood glucose during each cycle during which the model is evaluated due to the consumption or reduction of insulin-on-board (IOB). Eq. (1) expresses a typical linear decay of insulin-on-board per each cycle. In Eq. (2) and Eq. (3), IOB model 202 calculates the deviation between the user's previous insulin delivery history and the user's expected basal insulin delivery per each cycle of MDA 129, converting this into the user's current estimated insulin-on-board. In each cycle of MDA 129, the model assumes that an estimated 4% of the user's insulin-on-board should be consumed by the body, given the estimated half-time of typical fast-acting insulin as 90 minutes. Specifically, a continuous application of a 4% reduction over 5 minutes will result in a reduction of approximately 50% from the initial value after 90 minutes. The consumed insulin-on-board can then be converted into an estimated glucose drop per consumed insulin via the use of an estimated correction factor, represented by the fraction in Eq. (1), which is a ratio of units of insulin to mg/dL of change of the user's blood glucose level. In the proposed equation, this value is calculated via a commonly used heuristic against the user's total daily insulin, but this term may also be customized for each user or directly entered by the user.
Next, a CHO model 204 estimates the effect on the user's blood glucose levels of the user's previous meal ingestion, where available. The model uses an estimated half-time of typical carbohydrate ingestion of 2.5 hours (150 minutes or 30 5-minute cycles), with similar considerations above (where a repeated reduction of 2.25% per 5 minutes results in a 50% reduction against the initial value after 150 minutes):
Here, Eq. (4) gives the user's expected rise in blood glucose due to ingestion of a meal. In certain embodiments, the user may provide, via user app 160, an indication 206 of the amount of carbohydrates which were ingested. Based on the typical heuristics of the correction factor and the insulin to carbohydrate (I:C) ratio, the typical increase in glucose concentration per lg of consumed carbohydrates is approximately 3.5 mg/dL/g of consumed carbohydrates. Further, an estimated 2.25% of remaining carbs on board is estimated to be ingested by the body each cycle based on a half time of 2.5 hours. These variables are exemplary and can be adjusted up or down.
Finally, Eq. (5) provides a method to incorporate the sum of the impact of previous carbohydrate ingestions over the last 5 hours in a single value from which the actual consumption of the ingested meals in the previous cycle can be calculated. This model of remaining ingested carbohydrates is calculated by a multiplication of the total quantity of ingested carbohydrates in the previous 5 hours, or 60 5-minute cycles, and is multiplied by a decaying factor that is reduced for each cycle based on the length of time that has passed since the ingestion, in a vector operation. In this equation, a linear decay over 5 hours is expressed; however, any reasonable shape and duration of the carbohydrate decay curve can be utilized.
The estimates provided by IOB model 202 and CHO model 204 are combined with the value of the expected blood glucose levels from the previous cycle 208 to calculate the expected blood glucose level 210 for the current cycle, in accordance with Eq. (6).
G
exp(k)=Gexp(k−1)+ΔGIOB(k)+ΔGCHO(k) (6)
Finally, in each cycle, the user's current average deviation 212 over a previous predetermined period of time between the expected blood glucose level 210 and the user's actual glucose concentration 214 can be calculated in accordance with Eq. (7). In preferred embodiments, the previous predetermined period of time is 30 minutes (6 cycles of MDA 129); however, any previous period of time could be used.
where “6” is the number of cycles in a 30-minute period.
This current average deviation 212 can then be compared against the user's overall average deviation 216 in each cycle in accordance with Eq. (8). If the current average deviation 212 is significantly and persistently higher than the user's overall average deviation 216, a potential site issue can be signaled. In one embodiment, if the difference 218 between the current average deviation 212 and the overall average deviation is more than 2 standard deviations from the mean of the overall average deviation 216, an alarm may be raised; however, any similar threshold for raising the alarm can be used.
where:
Alternately, the probability of whether an issue exists may be provided calculated as in equation (9), with the stated probability linearly increasing from 0 to 100% or higher as the deviation in the previous 30 minutes M30(k) exceeds 2 standard deviations from the typical offsets, as follows:
In Eq. (9), an issue may be determined to exist if Jp,occ exceeds a certain threshold of probability (such as 75%) or may simply be indicated as an event once it exceeds the full 100% probability.
If it is determined an issue exists, in accordance with Eq. (8) or Eq. (9), ADD system 100 may notify the user by one of several different means. For example, user application 160 may provide an alarm to the user via the user interface 158 of user device 105. The alarm may be, for example, a message displayed on a default screen of the user app 160. The message may be, for example, in the form of a modal window. The alarm may also comprise, in addition to or in lieu of the message display, an audible or haptic signal which may be sensed by the user. In the event that user device 105 is not present in ADD system 100, drug delivery device 102 may deliver the alarm, which may be in the form of a visual alarm, for example, blinking lights on the housing of drug delivery device 102, an audible alarm, for example, a series of beeps issued by drug delivery device 102, or haptic feedback, for example, a series of vibrations created by a vibratory element in the housing of the regular device 102. The alarm may inform the user of the problem and may suggest a course of action, for example, replacing drug delivery device 102.
An occlusion in the fluid delivery path of drug delivery device 102 will typically cause a rise in the user's blood glucose levels because less insulin is being delivered to the user than required. However, other issues with drug delivery device 102 may cause the user's blood glucose levels to fall (or rise), for example, a defect in the drive mechanism 125 which may cause an excess (or insufficient amount) of insulin to be delivered to the user. In this case, two negative standard deviations in Eq. (8), indicating an unusual decline in the user's blood glucose level may indicate an issue with drive mechanism 125 as opposed to an occlusion in the patient interface 186. Such issues may also be flagged to the user.
The IOB model 202 given by Eqs (1-3) and the CHO model 204 given by Eqs. (4-5) are based on average of a large population of users. The actual applicability of the models to the user in question is not as important as the user's deviations from these models, given by Eqs. (6-7), which should be consistent on a day-to-day basis. A deviation from the user's typical deviation from the models may be indicative of a problem.
Note that negative deviations (e.g., the impact of unknown exercise) are automatically incorporated as this detection algorithm and the pump occlusion both only consider increases in glucose concentrations.
The equations describing the models above assume that this method is implemented by ADD system 100, which uses 5-minute cycles. For example, the constant “288” in Eq. (8) denotes a 24-hour period. Use with other ADD systems or with ADD system 100 described herein using different durations of cycles is contemplated be within the scope of the invention.
It should be noted that the IOB model 202 and the CHO model 204 described herein by Eqs. (1-3) and Eqs. (4-5) respectively are exemplary in nature. It is contemplated that the invention could use any reasonable models to estimate the effect of insulin-on-board and carbohydrates ingested with respect to the use of blood glucose levels and to measure the user's deviation from those models. An alarm is only raised when the current deviation differs greatly from the user's typical or average deviation from the models.
The described process 300 may be part of MDA 129 which may execute on drug delivery device 102, on user device 105 or partially on drug delivery device 102 and partially on user device 105. The alarms raised to the user may be delivered via user interface 158 on user device 105, by output device 155 on user device 105, on drug delivery device 102, or by a combination of any of the foregoing. The alarm may further be raised by user interface 178 on accessory device 106 which may be, for example, a smartwatch or other smart accessory device.
As would be realized by one of skill in the art, many variations on the embodiments disclosed herein are possible. In particular, various models and intervals and thresholds used in the models are contemplated to be the within the scope of the invention and the invention is not meant to be limited by the specific embodiments disclosed herein.
Although the present invention has been described above and is defined in the claims, it should be understood that the present invention can also be defined according to the following embodiments:
1. A method comprising:
2. The method according to embodiment 1, wherein the one or more models includes an IOB model for determining the effect on the expected blood glucose level of the user due to insulin-on-board.
3. The method according to embodiment 1 or 2, wherein the IOB model calculates the deviation between an insulin delivery history of the user, and a periodic expected basal insulin delivery and converts the deviation into a current estimate of insulin-on-board.
4. The method according to one of embodiments 1 to 3, wherein the IOB model assumes that a predetermined percentage of the insulin-on-board is consumed during each periodic cycle during which the IOB model is evaluated.
5. The method according to one of embodiments 1 to 4, wherein the consumed insulin-on-board is converted into an estimated drop in the blood glucose level of the user per consumed unit of insulin via the use of an estimation correction factor.
6. The method according to one of embodiments 1 to 5, wherein the one or more models includes a CHO model for determining the effect on the expected blood glucose level of the user due to previous ingestion of carbohydrates by the user.
7. The method according to one of embodiment 6, wherein the CHO model uses an estimate of the increase in glucose concentration per gram of consumed carbohydrates.
8. The method according to one of embodiment 6, wherein the CHO model uses an estimate of a percentage of consumed carbohydrates used during each cycle during which the CHO model is evaluated.
9. The method according to one of embodiments 6 to 8, wherein the expected blood glucose level is calculated periodically during each cycle of a medication delivery algorithm of the automatic drug delivery system and further wherein the expected blood glucose level is based on an IOB model for determining an expected change in the blood glucose level due to insulin-on-board and a CHO model for determining an expected change in the blood glucose level due to consumed carbohydrates.
10. The method according to one of embodiments 1 to 9, wherein the expected blood glucose level is further based on the calculated expected blood glucose level from a previous cycle of the medication delivery algorithm.
11. The method according to one of embodiments 1 to 10, wherein the actual deviation from the expected blood glucose level is calculated over a predetermined period of time.
12. The method according to one of embodiments 1 to 11, wherein the alarm is raised if the actual deviation calculated over the predetermined period of time exceeds an average deviation calculated over a previous 24-hour time period by a predetermined threshold.
13. The method according to one of embodiments 1 to 12, wherein the predetermined threshold is two standard deviations.
14. The method according to one of embodiments 1 to 13, wherein the alarm is raised via a user interface of the user device portion of the automatic drug delivery system.
15. The method according to one of embodiments 1 to 14, wherein the alarm comprises a message displayed on a user interface of the user device portion, an audible alarm generated by the user device portion, a haptic signal generated by the user device portion, or combination of any of the foregoing.
16. The method according to one of embodiments 1 to 15, wherein the alarm comprises a visual, audible or haptic signal generated by a drug delivery device portion of the automatic drug delivery system.
17. An automatic drug delivery system comprising:
18. The system according to embodiment 17, wherein the expected blood glucose level is calculated periodically during each cycle of the medication delivery algorithm and further wherein the expected blood glucose level is based on an IOB model for determining the expected change in the blood glucose level due to insulin-on-board and a CHO model for determining the expected change in the blood glucose level due to consumed carbohydrates.
19. The system according to embodiment 17 or 18, wherein the expected blood glucose level is further based on the calculated expected blood glucose level from a previous cycle of the medication delivery algorithm.
20. The system according to one of embodiments 17 to 19, wherein the actual deviation from the expected blood glucose level is calculated over a predetermined period of time, and wherein the alarm is raised if the actual deviation calculated over the predetermined period of time exceeds the average deviation calculated over a previous 24-hour period by a predetermined threshold.
21. The system according to one of embodiments 17 to 20, wherein the alarm comprises a visual, audible or haptic signal generated by the automatic drug delivery system.
22. An automatic drug delivery system comprising:
23. The system of embodiment 22, wherein the one or more models includes an insulin-on-board (IOB) model (202) for determining the effect on the expected blood glucose level (210) of the user due to insulin-on-board (IOB).
24. The system of embodiment 23, wherein the insulin-on-board (IOB) model (202) calculates a deviation between an insulin delivery history of the user and a periodic expected basal insulin delivery, and converts the deviation into a current estimate of insulin-on-board.
25. The system of embodiment 22 or 23 wherein the insulin-on-board (IOB) model (202) assumes that a predetermined percentage of the insulin-on-board is consumed during each periodic cycle during which the insulin-on-board (IOB) model (202) is evaluated.
26. The system of embodiment 25, wherein the consumed insulin-on-board is converted into an estimated drop in the blood glucose level of the user per consumed unit of insulin via the use of an estimated correction factor.
27. The system of one of embodiment 1 to 5, wherein the one or more models includes a carbohydrate (CHO) model (204) for determining the effect on the expected blood glucose level of the user due to previous ingestion of carbohydrates by the user.
28. The system of embodiment 6, wherein the carbohydrate (CHO) model (204) uses an estimate of the increase in glucose concentration per gram of consumed carbohydrates.
29. The system of embodiment 6 or 7, wherein the carbohydrate (CHO) model (204) uses an estimate of a percentage of consumed carbohydrates used during each cycle during which the carbohydrate (CHO) model (204) is evaluated.
30. The system of one of embodiments 22 to 29, wherein the expected blood glucose level is calculated periodically during each cycle of a medication delivery algorithm of the automatic drug delivery system and further wherein the expected blood glucose level is based on an insulin-on-board (IOB) model (202) for determining an expected change in the blood glucose level due to insulin-on-board and a carbohydrate (CHO) model (204) for determining an expected change in the blood glucose level due to consumed carbohydrates.
31. The system of one of embodiments 22 to 30, wherein the expected blood glucose level is based or further based on the calculated expected blood glucose level from a previous cycle of the medication delivery algorithm.
32. The system of one of embodiments 22 to 31, wherein the actual deviation from the expected blood glucose level is calculated over a predetermined period of time.
33. The system of one of embodiments 22 to 32, wherein the alarm is raised if the actual deviation calculated over the predetermined period of time exceeds an average deviation calculated over a previous 24-hour period by a predetermined threshold.
34. The system of one of embodiments 22 to 33, wherein the predetermined threshold is a factor multiplied by the standard deviations, wherein the factor is greater than 1.3, in particular wherein the factor is 2.
35. The system of one of embodiments 22 to 34, wherein the alarm is raised via a user interface of a user device portion of the automatic drug delivery system.
36. The system of one of embodiments 22 to 35, wherein the alarm comprises a message displayed on a user interface of the user device portion, an audible alarm generated by the user device portion, a haptic signal generated by the user device portion, or a combination of any of the foregoing.
37. The system of one of embodiments 22 to 36, wherein the alarm comprises a visual, audible or haptic signal generated by a drug delivery device portion of the automatic drug delivery system.
38. The system of one of embodiments 22 to 37, wherein the insulin-on-board (IOB) model (202) and/or the carbohydrate (CHO) model (204) are based on the average of a large population of users, in particular on the average of a population of at least 100 or at least 1000 users.
39. The system of one of embodiments 22 to 38, wherein the system comprises a drug delivery device, a user device and an analyte sensor, wherein the software implementing the medication delivery algorithm is performed by a processor of the drug delivery device, a processor of the user device, or by a processor of the user device in combination with a processor of the drug delivery device.
40. The system of one of embodiments 22 to 39, wherein the system comprises an analyte sensor for measuring the actual or current blood glucose level (214) of the user.
41. The system of one of embodiments 22 to 40, wherein the user's expected blood glucose value (210) for a current cycle is calculated as a sum of the user's expected blood glucose value (208) from the previous cycle, the change in the user's blood glucose levels due to insulin-on-board, as calculated by the insulin-on-board (IOB) model (202) and the change in the user's blood glucose levels due to ingested carbohydrates as calculated by the carbohydrate (CHO) model (204).
Software related implementations of the techniques described herein may include, but are not limited to, firmware, application specific software, or any other type of computer readable instructions that may be executed by one or more processors. The computer readable instructions may be provided via non-transitory computer-readable media. Hardware related implementations of the techniques described herein may include, but are not limited to, integrated circuits (ICs), application specific ICs (ASICs), field programmable arrays (FPGAs), and/or programmable logic devices (PLDs). In some examples, the techniques described herein, and/or any system or constituent component described herein may be implemented with a processor executing computer readable instructions stored on one or more memory components.
To those skilled in the art to which the invention relates, many modifications and adaptations of the invention may be realized. Implementations provided herein, including sizes, shapes, ratings, compositions and specifications of various components or arrangements of components, and descriptions of specific manufacturing processes, should be considered exemplary only and are not meant to limit the invention in any way. As one of skill in the art would realize, many variations on implementations discussed herein which fall within the scope of the invention are possible. Moreover, it is to be understood that the features of the various embodiments described herein were not mutually exclusive and can exist in various combinations and permutations, even if such combinations or permutations were not made express herein, without departing from the spirit and scope of the invention. Accordingly, the method and apparatus disclosed herein are not to be taken as limitations on the invention but as an illustration thereof. The scope of the invention is defined by the claims which follow.
This application claims the benefit of U.S. Provisional Patent Application No. 63/374,311, filed Sep. 1, 2022, the entire contents of which are incorporated herein by reference in their entirety.
| Number | Date | Country | |
|---|---|---|---|
| 63374311 | Sep 2022 | US |
