Techniques enabling adaptation of parameters in aid systems by user input

Information

  • Patent Grant
  • 11738144
  • Patent Number
    11,738,144
  • Date Filed
    Monday, September 26, 2022
    a year ago
  • Date Issued
    Tuesday, August 29, 2023
    9 months ago
Abstract
Disclosed are techniques and devices that are operable to receive one or a number of generalized parameters of an automated insulin delivery algorithm. An input of at least one generalized parameter corresponding to a user may be used to set one or more of the number of specific parameters of the automated insulin delivery algorithm based on the inputted at least one generalized parameter. Physiological condition data related to the user may be collected. The automated insulin delivery algorithm may determine a dosage of insulin to be delivered based on the collected physiological condition. Signals may be output to cause a liquid drug to be delivered to the user based on an output of the automated insulin delivery algorithm related to the determined dosage of insulin.
Description
BACKGROUND

Wearable drug delivery devices operate using a number of parameters that may be based on a user's history with wearable drug delivery devices. However, when a person is recently diagnosed with diabetes, the user usually does not yet have a user history with a drug delivery device. As a result, the user or the user's healthcare provider may have to perform what can be the daunting and tedious task of inputting the number of parameters into an automated insulin delivery (AID) algorithm that controls the delivery of insulin from the wearable drug delivery device.


AID algorithms for patients with Type 1 and Type 2 diabetes are evolving to simplify the onboarding experience of new users (e.g., no need to enter clinical parameters, such as basal profile, insulin-to-carbohydrate (IC) ratio, and/or correction factor (CF)). This development correspondingly causes an increasing “obfuscation” in the ways new users can impact, which may be adversely, the performance of these systems. The complexity of the calculations performed by the AID algorithms using the clinical parameters may make new users as well as some healthcare providers weary of adjusting the parameter settings, as such, the adjusted parameter settings may not provide an optimal outcome for the user.


In addition, as AID systems for T1DM management approach the capability to provide fully automated control of a user's diabetes treatment plan, there is still a desire by users or their healthcare providers to be able to optionally alter the automated calculation of system settings. For instance, an AID system may assume initial values for the user's clinical input parameters such as the basal profile, the IC ratio and the CF based on the user's insulin history, but the users may desire to modify such input parameters for their own reasons.


It would be beneficial to have techniques and devices that enable generalized adjustment of the parameter settings of an AID algorithm without the inadvertent obfuscation of the functions of the AID algorithm.


BRIEF SUMMARY

In one aspect, a controller is presented. The controller includes a processor, an input/output device, and a memory storing instructions. The instructions when executed by the processor may configure the processor to present, on the input/output device, a graphical user interface offering an input field for a sole generalized parameter of an automated insulin delivery algorithm. An input of the sole generalized parameter may be received via the input/output device. In response to receiving the input of the sole generalized parameter, a specific parameter of the automated insulin delivery algorithm may be set based on the inputted sole generalized parameter. The automated insulin delivery algorithm with the set specific parameter may determine a dosage of insulin to be delivered to the user. The determined dosage of insulin may be caused to be delivered to the user.


In a further aspect, a method is provided. The method includes presenting, on an input/output device of a user device, a graphical user interface offering an input field for a sole generalized parameter of an automated insulin delivery algorithm. An input of the sole generalized parameter may be received. In response to receiving the input of the sole generalized parameter, a specific parameter of the automated insulin delivery algorithm may be set based on the inputted sole generalized parameter. A dosage of insulin to be delivered to a user may be determined by the automated insulin delivery algorithm using the set specific parameter. The determined dosage of insulin may be caused to be delivered to the user.


In another aspect, a system is provided that includes a non-transitory computer-readable storage medium. The computer-readable storage medium may include instructions that when executed by at least one processor, cause the at least one processor to present, on an input/output device, a graphical user interface offering an input field for a generalized parameter of the automated insulin delivery algorithm. An input of only one generalized parameter may be received via the input/output device. In response to receiving the input of the only one generalized parameter, a specific parameter of the automated insulin delivery algorithm may be set based on the inputted generalized parameter. The automated insulin delivery algorithm using the set specific parameter may determine a dosage of insulin to be delivered to the user. The determined dosage of insulin may be caused to be delivered to the user.





BRIEF DESCRIPTION OF THE DRAWINGS

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 disclosure are described with reference to the following drawings, in which:



FIG. 1A illustrates a flowchart of an example of a simplified onboarding process that allows for simplified input of a number of generalized parameters;



FIG. 1B illustrates a flowchart of another example of a simplified onboarding process that allows for simplified input of a sole generalized parameter;



FIG. 2A illustrates an example of a graphical user interface suitable for implementing the example onboarding process of FIG. 1A;



FIG. 2B illustrates an example of a graphical user interface suitable for implementing the example onboarding process of FIG. 1B;



FIG. 3 illustrates a flowchart of an example process utilizing a generalized parameter input via the examples of FIG. 1 and FIG. 2;



FIG. 4 illustrates a flowchart of an example process utilizing particular generalized parameter input via the examples of FIG. 1 and FIG. 2;



FIG. 5 illustrates a flowchart of an example process utilizing another particular generalized parameter input via the examples of FIG. 1 and FIG. 2;



FIG. 6 illustrates a flowchart of an example process utilizing yet another particular generalized parameter input via the examples of FIG. 1 and FIG. 2;



FIG. 7 illustrates a flowchart of an example process that determines a finalized setting of a specific parameter; and



FIG. 8 illustrates a drug delivery system operable to implement the examples of FIGS. 1-7.





DETAILED DESCRIPTION

The disclosed techniques and devices provide the user with input devices that allow for the input of generalized AID algorithm parameters that are interpretable by the AID algorithm for use in the complex calculations that control a wearable drug delivery device according to the user's diabetes treatment plan.



FIG. 1A illustrates a flowchart of an example onboarding process that allows for simplified input of a number of generalized parameters. The inputted general parameters may be usable by an automated insulin delivery (AID) algorithm. Different parameters, input during an onboarding process of the user with the AID algorithm, may provide the AID algorithm with enough information that in combination with default settings enable a user to begin using a wearable drug delivery device.


Although users are not required to enter any clinical parameters, such as basal profile, IC ratio and/or Correction Factor, during the initial set up (i.e., onboarding) of their wearable drug delivery device, their health care providers may review available blood glucose outcomes and may consider that the users may need increased or decreased insulin delivery compared to default dosages of the AID algorithm.


The AID algorithm may use safety constraints to limit the effects of some inputs to the AID algorithm from the user for safety purposes.


In block 102, the routine 100 presents on an input/output device of a user device, such as a controller, a graphical user interface input offering input fields for a generalized parameter of a number of generalized parameters of an automated insulin delivery algorithm. For example, the number of generalized parameter(s) usable by the AID algorithm may be 1, 2, or up to 3-6, or the like. For example, a generalized parameter may be a user's weight, an age, a reference basal, an activity level, and/or a type of diet, gender, a type of diabetes (e.g., Type 1, Type 2, Gestational), and/or an equipment brand (e.g., equipment being an infusion pump, a continuous glucose monitor, a heart rate monitor, a fitness device, blood oxygen sensor, or the like). The number of generalized parameters, for example, is less than a number of specific parameters of the automated insulin delivery algorithm. Meanwhile, there may be a number of specific parameters. Examples of specific parameters may include a blood glucose measurement value, a value for a user's HbA1c, an estimated initial total daily insulin (TDI), a calculated TDI, a an upper boundary of insulin delivery, a baseline basal rate delivery of insulin, basal/bolus ratio, an insulin-on-board (IOB), or a combination of two or more of the foregoing. In block 104, the routine 100 receives an input of at least one generalized parameter corresponding to a user.


In block 106, the routine 100 in response to receiving the input of the at least one generalized parameter, sets one or more of the number of specific parameters of the automated insulin delivery algorithm based on the inputted at least one generalized parameter. For example, the specific parameters that may be set may include an estimated initial total daily insulin (TDI) amount, an upper boundary of insulin delivery, a basal/bolus ratio, or an insulin-on-board (IOB) amount, or a combination of two or more of the foregoing. For example, the AID algorithm may compare the inputted at least one generalized parameter to a threshold. Based on a result of the comparison, the AID algorithm may revise coefficients or elements of a cost function.


In block 108, the routine 100 may begin collecting physiological condition data related to the user, such as wirelessly via a blood glucose meter or a continuous glucose monitor, or directly from a user input. In block 110, the automated insulin delivery algorithm implementing the routine 100 may determine a dosage of insulin to be delivered based on the collected physiological condition of the user. The AID algorithm may be communicatively coupled to a pump mechanism or the like that is coupled to a user and that is operable to deliver insulin or other medication to a user. In block 112, the routine 100 may cause a liquid drug to be delivered to the user based on the determined dosage of insulin that is output from the AID algorithm.


It is also envisioned that the onboarding process may be further simplified to permit input of a sole generalized parameter, for example, a user's weight in kilograms or pounds. An example process flow of this further simplified onboarding process is illustrated in FIG. 1B and described below.


In the routine 101, an input/output device of a controller may present, at 111, a graphical user interface input offering an input field for a sole generalized parameter of an automated insulin delivery algorithm. In a specific example, the sole generalized parameter is a user's weight (which refers to a user's current weight). In block 113, the routine 101 receives the input of the sole generalized parameter.


In block 115, the routine 101, in response to receiving the input of the sole generalized parameter, sets one or more of the number of specific parameters of the automated insulin delivery algorithm based on the inputted sole generalized parameter. For example, when the sole generalized parameter is weight, the AID algorithm may calculate a TDI value based on the inputted weight. This TDI value may be an initial TDI estimate for the user based on the user's weight. Based on the calculated TDI value, the AID algorithm may set or revise other coefficients, parameters, or elements of a cost function or model.


In block 117, the automated insulin delivery algorithm implementing the routine 100 may determine a dosage of insulin to be delivered based on the collected physiological condition data. The AID algorithm may be communicatively coupled to a pump mechanism or the like that is coupled to the user and that is operable to deliver insulin or other medication to the user.


In block 119, the routine 101 may cause a liquid drug to be delivered to the user based on the determined dosage of insulin that is output from the AID algorithm.


After initial parameters are entered (e.g., weight), calculated (e.g., TDI based on weight), or set (e.g., parameters, coefficients, or elements of a cost function or model), the system may collect physiological condition data related to the user, such as wirelessly via a blood glucose meter or a continuous glucose monitor, or directly from a user input. The collected physiological condition data may be used by the system going forward to update the various parameters (e.g., modify the initial TDI estimate, which was based on the user's weight, up or down to more accurately reflect the user's medicament needs).



FIG. 2 illustrates an example of a graphical user interface of a user device that is suitable for implementing the example onboarding process of FIG. 1. Generalized parameters that may be useful for entry into the AID algorithm by the user may include a reference basal value, a user's age, a user's activity level, and a diet type.


As shown in FIG. 2A, a controller 202 may be operable to receive inputs from a user via an input/output device 206. The input/output device 206 may be a touchscreen as shown in FIG. 2 or may include one or more of a keyboard, a digital personal assistant, such as Alexa®, Siri®, Cortana® or Google Assistant®, a display, a speaker, or the like. The graphic user interface 204 may present one or more input fields for input of the generalized parameters. For example, a slider bar, a radio button, a touch button, a check box, or the like may be used as an input device to enter a respective generalized parameter. The controller 202 may be equipped with a processor that is operable to execute programming instructions to implement the input/output device 206 and also execute an automated insulin delivery algorithm. In the example of a reference basal value, the slider bar may be used as the input field for a reference basal input 208. An example value for reference basal may be between 1 and 4 Units that may be input as the reference basal input 208. Similarly, the age input 210 and the activity level input 212 may also be input via slider bars. An alternative, input/output device 206 may be a radio button that a user manipulates using a circular gesture to indicate selection of a diet type and indicate the diet type input 214 of the user. Another alternative may enable the user to indicate different diet types for individual meals, such as breakfast, lunch, snack or dinner via a meal indicator input 216, which may be a checkbox input, or the like. Each type of meal may correspond to a particular diet type, and the user may specify a diet type for each type of meal using the meal indicator input 216 and diet type input 214 sequentially for each type of meal.


Of course, other input devices may be used to enter the generalized parameter, such as a keyboard, mouse, stylus, voice recognition, or the like. In addition, all of the generalized parameters do not need to be entered. The graphic user interface 204 may present the respective inputs of the reference basal input 208, age input 210, activity level input 212, diet type input 214, and the meal indicator input 216 on separate screens that are presented sequentially after a user has an opportunity to either make the requested input or choose not to input the requested generalized parameter.


The example of FIG. 2B illustrates a graphical user interface suitable for implementing an example onboarding process utilizing a sole generalized parameter. In FIG. 2B, the sole generalized parameter may be a user's weight. Alternatively, this user input may be used in conjunction with other user inputs (such as those depicted in FIG. 2A). But in one preferred embodiment, the user need only enter their weight for the system to be initialized and set up for delivering personalized medicament for the user.


For example, the controller 202 of FIG. 2B may be operable to receive inputs from a user via an input/output device 206. The input/output device 206 may be a touchscreen that is operable to present a graphical user interface 201. The graphical user interface 201 may present various prompts for a user to enter the sole generalized parameter. For example, prompt 203 may request a selection between kilograms or pounds for the units of the user's weight. Alternatively, the units of the inputted weight may be pounds or kilograms by default, depending on the user's geographic location, and the units may be displayed to the user. A numerical keypad 205 may be provided to allow the user to enter their weight. The presentation window 207 present the inputted user's weight and presentation window 209 may present an initial estimate of the user's total daily insulin (TDI) as calculated by the AID algorithm. As mentioned above, this initial TDI estimate may be used initially by the system to determine how much medicament (e.g., insulin) to deliver to the user initially, and may be changed over time based on blood glucose measurement data. An optional confirmation button 211 may be presented to allow the user to optionally confirm the presented initial TDI determination. In an alternative embodiment, the user may be allowed to change the initial TDI determination by tapping on the TDI amount in presentation window 209 and entering a new value (with a numerical keypad) or increasing or decreasing the initial TDI determination up or down (for example, with arrow keys). If the user changes the initial TDI determination, the modified value may be used as the initial TDI determination. Limitations or warnings may be applied to any changes the user attempts to make. For example, if the initial TDI determination based on the user's inputted weight was determined to be 42 Units of medicament, and the user attempts to change this value to 65 Units of medicament, the system may output an error or a confirmation screen to the user asking the user to either confirm the inputted TDI entry or confirm the user's inputted weight (and units). Alternatively, the system may only allow changes to the initial TDI determination up to certain threshold(s), such as 20% or 30% upward, and 40% or 60% downward; and if the user attempts to input a modified TDI amount in excess of the threshold(s), the system may output a message to the user and also change the modified TDI amount up to the threshold.


In an operational example, a user may be new to infusion pump therapy and may not know what TDI to use for their system. To accommodate these and other situations, this embodiment allows a user to only input their weight (e.g., in pounds or kilograms). If inputted in pounds, the programming code providing this function for the AID algorithm may convert the inputted weight in pounds to kilograms for purposes of determining an initial TDI estimate for the user; or, a different conversion factor may be used that corresponds to using pounds instead of kilograms such that no lb-kg conversion is necessary. In either case, a proper conversion factor will be used that corresponds to the units of the weight input by the user. The AID algorithm may use a predetermined factor to automatically calculate an initial TDI for the user. In an example, the TDI may be the only specific parameter that is set in response to the user's weight being input as the sole generalized parameter. For example, a multiplier may be applied to the user's weight. The multiplier may have a preselected value that is approximately equivalent to a steady state TDI value for a large population of users when multiplied by the user's weight. For example, a value of 0.6 may be used as the conversion factor or multiplier when the inputted weight is in kilograms. Alternatively, the multiplier may be preselected to be 0.3 or 0.2 (when the inputted weight is in kilograms) to result in a more conservative initial TDI estimate for the user. Other conversion factors or multipliers may be used. And corresponding conversion factors or multipliers may be used when the inputted weight is in units of pounds. By way of example, if the user indicates at 203 that their weight will be input in pounds and inputs a weight of 155 pounds, the routine may be operable to convert the 155 pounds to 70.3 kilograms. Based on the number of kilograms, the AID algorithm may automatically further calculate the user's starting or initial TDI as 42.2 Units (i.e., 70.3×0.6 is 42.2, which may be rounded to 42 Units in some embodiments). However, the 0.6 preselected multiplier may be considered too aggressive, so the preselected multiplier may be a more conservative value of 0.3 or 0.2. The multiplier may be preselected by the manufacturer of the drug infusion system. Based on the calculated (and optionally confirmed) TDI, the AID algorithm further determines a basal delivery rate for the user, which may be based on a 1:1 basal/bolus ratio. For example, if the initial TDI estimate was determined to be 42 Units, the system may determine that 21 Units should be allocated to basal deliveries, and if this amount is delivered uniformly over 24 hours, the user would initially receive 0.875 Units of medicament per hour. Bolus dosages may also be calculated using this initial TDI estimate and the system's bolus calculator may rely (at least initially) on this initial TDI estimate when calculating how much medicament to deliver in response to meals or as correction boluses. As mentioned elsewhere in this disclosure, the initial TDI estimate may change over time to more accurately reflect the user's medicament needs. In other words, as additional data is gathered regarding the user (e.g., blood glucose measurement values), various system parameters, including a TDI for the user, may change over time. Additionally, or alternatively, if the user enters additional generalized parameters, the initial TDI estimate may increase or decrease based on the user's entries. But if no other parameters are entered by the user, the system may use the initial TDI estimate that is determined based on the sole input of the user's weight.



FIG. 3 illustrates a flowchart of an example process utilizing a generalized parameter input via the examples of FIG. 1 and FIG. 2.


Reference basal may be a rate, such as a number of units (U) per hour, units per day, or the like. In an example, the AID algorithm may have a default basal rate setting of 1 U per hour. In block 302, the routine 300 receives via a graphical user interface, such as graphic user interface 204 of FIG. 2, an input indicating a reference basal rate of insulin (i.e., indicated by a Bref), in units per time period, such as hour or day. Based on this single input, other parameters may also be determined by the AID algorithm and managed by the system, such as amount and time of bolus dosages, recommended dosages and times of open-loop insulin deliveries, and the like.


In an example, automated delivery systems are operable to deliver a certain basal amount of insulin, and that amount of insulin is usually dependent on a default setting of 1 unit of insulin per hour, for example. In some situations, the user or healthcare provider may enter 1.5 U per hour, which is a 50% increase over the 1 unit per hour default setting. However, an upper boundary safety constraint may limit the basal insulin delivery to, for example, 1.2 U per hour as shown in the following equation. In other words, the percentage increase may be limited to 20% (i.e., 100×0.2) in this example. Of course, the percentage increase boundary may be tunable. The degree of tunability may be based on additional details related to the user, such as age, weight, gender and the like. The user or the healthcare provider can input an estimate of the user's basal rate as a reference basal for use as a generalized parameter by the AID algorithm.


In block 304, a processor executing routine 300 as part of the AID algorithm may determine a percentage of a user's total daily insulin that is represented by the reference basal rate of insulin. In response to the input of the reference basal, the AID algorithm may determine an upper boundary for the amount of insulin that is to be delivered so a user does not over deliver insulin.


The reference basal rate parameter Bref (as described in more detail below) may be input by a user into the AID algorithm. In one example, the reference basal rate parameter Bref may be input by the user as a single parameter, which the user may track and may be input to the AID algorithm as described herein. Alternatively, the user at onboarding may set their TDI as a default, or alternatively, the user may input a TDI value that was calculated for the user by a clinician and the system based on the inputted TDI value may calculate a Bref value for use by the AID algorithm as described herein.


Although users are not required to enter any clinical parameters, such as basal profile, IC ratio and/or Correction Factor, their health care providers may review the glucose outcomes and may consider that the users may need increased or decreased insulin delivery compared to the average AID insulin deliveries. The users and/or HCPs can then provide this reference basal, Bref, to the AID system's algorithm. The AID algorithm may be operable to modify the maximum delivery constraint, upper boundary UBoriginal, of the AID algorithm based on this Bref as follows:










UB
ref

=


UB
original

·

min

(


max

(



B
ref


0.5
·
TDI


,


lower



mod
.

value



)

,


upper



mod
.

value



)






Equation


1








where UBoriginal is the maximum delivery constraint for insulin to be delivered over the course of a day, the lower modification (mod.) value is a minimum factor that modifies UBoriginal the least amount, the upper modification (mod.) value is a maximum factor that modifies UBoriginal the greatest amount, and Bref divided by 0.5×TDI represents the ratio of user basal (Bref) to the nominal TDI basal (0.5×TDI).


In an example, Equation 1 may be used during an boarding process. In an onboarding example, the TDI value in Equation 1 may be a system generated TDI. In an example, TDI is specific parameter that may be set by the AID algorithm based on a user input during onboarding. For example, the AID algorithm may generate a TDI based on a user's insulin history. If a user's insulin history does not exist, the TDI may be generated based on a user weight-based calculation. For example, a user when onboarding may enter their weight as a sole generalized parameter, the AID algorithm may generate an estimated TDI based on the weight and the estimated TDI may be set as the TDI for use by the AID algorithm to generate insulin dosages for delivery to the user. The AID algorithm may update the TDI as the AID algorithm gains additional information.


Also, during the example of the onboarding process that utilizes the input of multiple generalized parameters, in addition to the user entering their weight, the user may enter a Bref value. In the routine 300 at block 306, the processor may determine a maximum value between the percentage of the user's total daily insulin that is represented by the reference basal rate of insulin (i.e., Bref divided by (0.5×TDI)) and a lower modification value (i.e., lower mod. value of Equation 1). In an operational example, the AID algorithm, using Equation 1, may determine a maximum value between the entered Bref value divided by half of the user's TDI (i.e., 0.5 times the user's TDI) and a lower modification threshold value (i.e., lower mod. value in Eq. 1 above), such as 0.8 or the like.


In block 308, the routine 300 may determine a minimum between the determined maximum and an upper modification value. For example, in response to determining the maximum value, the AID algorithm may utilize a minimum function to evaluate the determined maximum value against an upper modification threshold value (i.e., upper mod. value in Eq. 1 above), such as 1.2 or the like. The outcome of the evaluation of the minimum function may provide a modification factor that may be used to modify the original upper boundary, UBoriginal. The minimum function is formulated to provide a value that may be between 0.8 and 1.2 based on the example lower and upper modification factors provided above.


In block 310, the routine 300 may multiply a default original upper boundary of insulin delivery by the determined minimum. Continuing with the operational example, the original upper boundary, UBoriginal may be a value, such as 4 Units of insulin. Assume in the example that the minimum function returned a value of 0.9, the reference upper boundary, UBref, may be UBoriginal times 0.9. Or, using the example value of 4 U for UBoriginal, UBref is 4 U times 0.9, which equals 3.6 U. Using the example values for the lower modification threshold value (e.g., 0.8) and the upper modification threshold value (e.g., 1.2) and the example 4 U for the original upper boundary (i.e., UBoriginal), an example range of the reference upper boundary of insulin (i.e., UBref) may be between 3.2 U and 4.8 U.


In block 312, the processor executing routine 300 may use a result of the multiplying (i.e., UBref) to calculate basal insulin dosages. When the basal insulin dosages are calculated, the processor upon executing the AID algorithm may cause a wearable drug delivery device to deliver the calculated basal insulin dosages to a user, for example, as part of a diabetes treatment plan.


Different processes may be implemented in response to the other generalized parameters entered by the user.



FIG. 4 illustrates a flowchart of an example process utilizing a generalized parameter input via the examples of FIG. 1 and FIG. 2. The graphical user interface for the AID algorithm may provide an optional Age entry that enables the insulin cost function to be modified based on a user's age. For example, the AID algorithm may modify the cost function when the age entry to the graphical user interface is lower than a certain threshold, such as 6 years old. The AID algorithm may determine dosages of insulin to be delivered based on minimizing a cost function. The cost function may be manipulated using a pair of weighted coefficients.


An example of a general parameter for input, such as age, may be used when younger children are the user of the wearable drug delivery device. Based on the generalized parameter of the child's age, the routine 400 may modify the calculation of one of the weighted coefficients. For example, healthcare providers may particularly desire to make a fine-tuned adjustment of the AID algorithm because the impact of the pump resolution may cause significant variations in insulin needs for the very low total daily insulin (TDI) amounts of younger children (e.g., the 0.05 U pump resolution versus 5 U of TDI=1% variation based on a single pulse of insulin). To limit the potential for wide variations in TDI, the AID algorithm may include an input field in a graphical user interface for entry of an age of the user, such as age input 210 of FIG. 2. For example, the entered age may be compared to a certain threshold, such as 6 years of age. If the entered age is lower than the certain threshold, such as 6, the AID algorithm may decrease, for example, a minimum scaling rate of insulin costs to a lower value.


As mentioned above, one or more of the generalized parameters may cause the AID algorithm to adjust the cost function to address one or more conditions that may be influenced by the one or more generalized parameters. As a starting point, it is helpful to review a typical conventional cost function. A typical formulation for cost J is:









J
=


Q
·




i
=
1

M





G
p

(
i
)

2



+

R
·




i
=
1

n




I
p

(
i
)

2








Equation


2







where Q and R are the pair weighted coefficients mentioned above. The factor

Gp(i)2


is the square of the deviation between the projected blood glucose level for an insulin dosage at cycle i and the projected blood glucose level for the basal insulin dosage, and M is the number of cycles in the prediction horizon.


The factor

Ip(i)2


is the square of the deviation between the projected insulin delivered at cycle i and the insulin for basal insulin delivery, and n is the control horizon in cycles.


Thus, the factor:






Q
·




i
=
1

M





G
p

(
i
)

2







is the weighted glucose cost, and the factor:






R
·




i
=
1

n




I
p

(
i
)

2






is the weighted insulin cost. The total cost J is the sum of the weighted glucose cost and the weighted insulin cost. A cycle has a fixed interval, such 5 minutes.


The coefficient R, referred to as “a scaling rate of insulin,” is a tunable value that may affect the total cost J and that is based on delivery of insulin. Healthcare providers may particularly desire to have fine-tuned adjustment of AID systems for younger children, such as those around the age of 5-7. One example of the generalized parameters is age, and the AID algorithm may modify the coefficient R based on age. In the Equation 2, the example age is 6, but other ages for children may also be considered. Young children simply need less insulin than teen aged children or adults. A drug delivery device in a single pulse of the pump mechanism (also referred to as the “pump resolution”) may deliver 0.05 Units of insulin to a user. When one considers that a total daily amount of insulin (i.e., TDI) for young children may be 5 Units, the pump resolution (of 0.05 U) as compared to a TDI of 5U represents a 1% variation based on the single pulse of the pump mechanism. As a result, changes in the number of pulses of the pump mechanism may cause significant variations in insulin needs for users that function with very low TDI, such as younger children. Therefore, it is beneficial to be more conservative for people with low TDI—for example, people who are younger because small changes in the amount of insulin delivered by the pumps to young users may have a significant impact on the young user's TDI.


In the cost function, the scaling rate of insulin R may include an aggressiveness factor having an approximate value 9000 that may be used for users with mid-range TDI and that represents an adjusted weight on insulin deviation versus glucose deviation. The higher value of the aggressiveness factor, the more heavily the AID algorithm penalizes the insulin deviation versus any glucose excursions. In a standard implementation, the aggressiveness factor is fixed. However, the aggressiveness of the scaling rate of insulin R may be attenuated to accommodate the needs of younger users.


The graphical user interface for the AID algorithm may provide an optional age entry that enables the insulin cost function to be modified based on a user's age. For example, the AID algorithm may modify the cost function when the age entry to the graphical user interface is lower than an age threshold, such as 6. As shown in Equation 3 below, the AID algorithm may decrease the minimum scaling rate of insulin (i.e., coefficient R) to a lower value, as follows:










R

h

i


=

{




9


000
·



(


4

1


max

(


min

(

TDI
,
10.25

)

,

6


1
.
5



)


)

2






Age
>
6






9


000
·



(


4

1


max

(


min

(

TDI
,
8.2

)

,

6


1
.
5



)


)

2






Age

6









Equation


3








where, in this example, the value 41 is the TDI of a “standard” patient, who has an unmodified Rhi of 9000. Patients having another TDI value may have their Rhi scaled, for example, according to the inverse square law, but the scaling may be set stop at a maximum TDI, for example, of 61.5 at the high end and a TDI of 10.25 or 8.2, for example, at the low end for users over 6 years of age or equal to 6 or under, respectively.


The AID algorithm may process the inputted age according to routine 400. In routine 400, if the user's age is greater than the age threshold, the AID algorithm may as the user's TDI goes down—e.g., below an over-age threshold, such as 10.25 units or the like, the aggressiveness factor may be increased. For example, the value Rhi directly feeds into the cost function of Equation 2 as a substitute for the value R. But typically, algorithms have a scaling aggressiveness, where the higher the TDI is the more aggressive the AID algorithm is designed to behave, and vice versa. If a user has a low TDI, the AID algorithm still aims to be aggressive but is more conservative (e.g., changes have lesser magnitudes and are less drastic) when the user's TDI is mid-range.


In an operational example, the routine 400 receives via a graphical user interface an input indicating an age of a user at block 402. In block 404, the routine 400 modifies parameters of a cost function based on the inputted age. The cost function of Equation 2 is usable by the AID algorithm to determine an amount of a dosage of insulin for the user. In block 406, the routine 400 determines a value of a scaling factor in the cost function by using the modified parameters. Based on a value of the age input, the AID algorithm may determine the scaling factor differently. For example, the AID algorithm executing routine 400 at block 406 may in response to the age of the user being greater than an age threshold, determine a minimum between an over-age constant and the user's total daily insulin value. The AID algorithm may determine a maximum between the determined minimum and a delivery threshold. A timing threshold may be divided by the determined maximum and the quotient may be squared. A default scaling factor value may be multiplied by a result of the squaring, where the result is the value of the scaling factor. Alternatively, at block 406, the AID algorithm may, in response to the age of the user being less than or equal to an age threshold, determine a minimum between an underage constant and the user's total daily insulin value. A maximum between the determined minimum and a delivery threshold may be determined. The AID algorithm may divide a timing threshold by the determined maximum. squaring the quotient of the division and multiplying a default scaling factor value by a result of the squaring, where the result is the value of the scaling factor.


In block 408, the routine 400 calculates basal insulin dosages by the determined scaling factor in the cost function. The AID algorithm may generate signals that cause the calculated basal insulin dosages from block 408 to be delivered to the user via a wearable drug delivery device.


Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.



FIG. 5 illustrates a flowchart of an example process utilizing a further generalized parameter input via the examples of FIG. 1 and FIG. 2.


A common rule of thumb is a 50/50 split of insulin delivery provided via basal and bolus dosages, respectively. In other words, half of the user's total daily insulin is provided by basal dosages and the other half is provided by bolus dosages. An active user when participating in activities typically needs less insulin since during activity their cells are more sensitive to insulin and the uptake of insulin is more efficient.


The graphical user interface for the AID algorithm may provide an activity level input 212 entry that enables the determination of insulin dosages to be modified. Users that execute a high level of activity may use significantly less basal insulin compared to those who have less active lifestyles. In these cases, the user or healthcare provider may indicate to the system that they want to cover an insulin amount less than 50% of their total insulin as basal. For example, the AID algorithm may modify the basal/bolus split based on the inputted activity level input 212.


This Basal/bolus Split, SBasal, can be set to a lower value, such as 40% for high activity users, instead of 50% for standard activity users if users indicate this trigger when inputting the generalized parameters. The AID algorithm may determine the basal split parameter, Sbasal, based on the activity level input 212 according to the following tunable settings:







S
basal

=

{




0.5



Standard


Activity





0.4



High


Activity






Basal


split


parameter






The AID algorithm may determine the basal TDI amount based on the following calculation:

BasalTDI=Sbasal·TDI   Equation 3


In alternate embodiments, the 0.4 value for high activity can be made variable between a range, such as 0.35 to 0.5, based on the user's draggable setting of activity level input 212 of FIG. 2.


In an operational example, the routine 500 may be operable at block 502 to receive via a graphical user interface an input indicating an activity level of a user. This setting may be cross-checked with an accelerometer accessible to the AID algorithm. For example, if the user is not active for several hours (e.g., 3 hours, 4 hours, 5 hours, or 6 hours), the AID algorithm may be operable to generate an alert that the user's basal split value is less than 50% and might need adjusting.


In block 504, the AID algorithm executing the routine 500 may be operable, in response to the indicated activity level, to set a basal split parameter used in a total daily insulin formula.


In block 506, the AID algorithm executing the routine 500 may determine a total daily insulin (TDI) value of the user. The determination of TDI may be based on age, physiological condition information received from user or the like.


In block 508, the routine 500 may enable determination of a basal total daily insulin amount to be provided to the user.


In block 510, the routine 500 may calculate basal insulin dosages based on the determined basal total daily insulin. The AID algorithm may generate signals that cause the calculated basal insulin dosages from block 510 to be delivered to the user via a wearable drug delivery device.


Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.


The basal split parameter may also be modified based on the input of yet another generalized parameter in the graphic user interface 204 of FIG. 2. FIG. 6 illustrates a flowchart of an example process utilizing yet another particular generalized parameter input via the examples of FIG. 1 and FIG. 2. This generalized parameter is for a type of diet. For example, some users may adhere to non-standard diets, such as a Keto (low carbohydrate) diet, that may require significantly higher basal insulin delivery amounts (relative to bolus insulin delivery amounts) as compared to standard dietary lifestyles that are higher in carbohydrate intake. The AID algorithm may enable the user to indicate a type of diet or at least offer an option to indicate a non-standard diet.


If you are not eating carbohydrates, the need for bolus insulin is reduced but the need for basal insulin may increase to cover overall insulin needs of the user. Users that partake in non-standard diets may instead require significantly higher basal compared to standard lifestyles, such as in a keto diet. For example, if the user indicates a keto diet, the basal split parameter Sbasal, which is a tunable parameter, can be set to a higher value, such as 60%, instead of 50% as shown below:







S
basal

=

{



0.5



Standard


Diet





0.6



Keto



(

Low


Carb

)



Diet









Because the user is not ingesting as many carbohydrates with a low carbohydrate diet, the relative amount of basal insulin increases, as the required amount of insulin delivered via bolus dosages goes down. As mentioned, the basal split parameter is tunable, for example, the diet type input 214 may cause the basal split parameter to range between 0.65 to 0.5 instead of being fixed at 0.6 based on user's draggable setting of relative amount of carbohydrate ingestion.


The AID algorithm may, in response to the basal amount being greater than a threshold, generate a prompt on the graphic user interface 204 of FIG. 2 asking the user if they are still on the low carbohydrate diet.


During onboarding processes at the set up for a wearable drug delivery device, the use of generalized parameters enables users to input simpler values as compared to the intimidating calculations performed by diabetes healthcare professionals while still enabling the AID algorithm to establish an insulin delivery regimen for the user.


In an operational example, the routine 600 may be operable at block 602 to receive via a graphical user interface an input indicating a type of diet of a user.


In block 604, the processor executing the routine 600, in response to the indicated diet type, may set a basal split parameter used in a total daily insulin formula.


In block 606, the processor executing the routine 600 may determine a total daily insulin value of the user.


In block 608, the processor executing the routine 600 may determine a basal total daily insulin to be provided to the user.


In block 610, processor executing the routine 600 calculates basal insulin dosages based on the determined basal total daily insulin. The AID algorithm may generate signals that cause the calculated basal insulin dosages calculated at block 610 to be delivered to the user via a wearable drug delivery device.



FIG. 7 illustrates a flowchart of an example process that determines a finalized setting of a specific parameter.


The earlier examples discuss the generalized parameters that a user may input that are used by the AID algorithm to modify a setting of one or more specific parameters.


In this example, the AID algorithm may initially calculate specific parameters of a user's insulin delivery regimen, such as a user's typical basal dosage value (e.g., Bauto), correct factor (CF) value (e.g., CFauto), and Insulin-to-carbohydrate (IC) ratio value (e.g., ICauto), automatically based on the user's total daily insulin needs in the user's available treatment plan history.


In operation, the AID algorithm may use the following equations to automatically set the respective specific parameters based on a user's total daily insulin (TDI) setting for operation of the user's wearable drug delivery device:










B
auto

=

0.5
·

TDI
24






Equation


4













CF
auto

=

1800
TDI





Equation


5













IC
auto

=

450
TDI





Equation


6







The parameter values of Equations 4, 5 and 6 may be default settings for each of the respective specific parameters. Equation 4 is an example of an automatic basal delivery amount, Equation 5 is an example of a correction factor, and Equation 6 is an example calculation of a user's insulin-to-carbohydrate ratio.


Equation 4 determines an hourly basal rate of insulin delivery Bauto based on a rule of thumb related to TDI mentioned in an earlier example related to the basal split parameter. As an initial or default basal split parameter setting, the AID algorithm may utilize 50% or 0.5 as the basal split parameter. In this case, the automatic basal setting is determined according to Equation 4 in which the user's TDI is divided by the number of hours in a day (24) and the quotient is multiplied by the initial or default basal split parameter (0.5). The parameter Bauto is the default amount of basal that is provided by basal delivery and the other 50% is provided by bolus deliveries of insulin.


Equation 5 is a correction factor CFauto that is used by the AID algorithm to estimate how much a user's blood glucose drops for each unit of insulin. The correction factor CFauto may be calculated differently for fast-acting insulin and for regular insulin. For example, Equation 5 illustrates the correction factor calculation based on the use of short-acting insulin, which is referred to as the “1800 rule.” For example, if a user takes 30 Units of short-acting insulin daily, the user's correction factor is determined by dividing 1800 by 30, which equals 60. The result (e.g., 60) means the user's insulin sensitivity factor is 1:60, or that one unit of short-acting insulin is expected to lower the user's blood glucose by about 60 mg/dL. For regular insulin, a “1500 rule” in which the value 1500 is substituted for the value 1800 of the “1800” rule may be used to determine a user's correction factor.


Equation 6 is an example calculation of a user's insulin-to-carbohydrate ratio ICauto, which is an amount of insulin used to lower the user's blood glucose from a particular amount of carbohydrates the user consumed. The particular calculation of Equation 6 may be used to determine the number of grams of carbohydrates that are approximately covered by 1 unit of insulin. The factor in the numerator, 450, is used when the user controls their diabetes with regular insulin, while a factor of 500 is used when the user controls their diabetes with fast-acting insulin.


These values Bauto, CFauto, and ICauto may then subsequently be automatically adapted based on the changes in the user's insulin needs over time. In addition, a user may desire to make changes to these automatically-generated parameters, Bauto, CFauto, and ICauto, for more aggressive or less aggressive insulin deliveries both via the AID algorithm.


An example of a formula to calculate a daily insulin delivery factor may be a calculation of an amount of insulin that was delivered to the user per hour over the course of a period of time, such as the previous week (hence, the division by 7) is provided below.








(




i
=
1

7


TDI
i


)

/
7




daily


Insulin


delivery


factor





where the 7 in the numerator indicates the number of days in a week and i is for each day of the previous 7 days.


The daily insulin delivery factor may be a calculation of an amount of insulin that was delivered to the user per hour over the course of a period of time, such as the previous week (hence, the division by 7) via basal insulin delivery:









(




i
=
1

7


TDI
i


)

/
7

48




hourly


basal


Insulin


Delivery


Factor





where the 7 in the numerator indicates the number of days in a week, the denominator value of 48 is the result of 24 times 0.5, where 24 represents the number of hours in a day and 0.5 represents the percentage amount of insulin received by the user via basal delivery. The expectation is that the user receives half (i.e., 0.5 or 50%) of their insulin need via basal delivery and the other half (i.e., 0.5 or 50%) via bolus deliveries.


The AID algorithm may be operable to consider the typical accepted clinical ranges in insulin delivery, and incorporate the user's changes as a mix of the user's current average insulin needs in, for example, the previous week, the user's suggested insulin changes may be implemented using the following parameter calculations:










B
final

=

min
(


max

(


0.8
·
0.4
·



(




i
=
1

7


TDI
i


)

/
7

48


,


0.6
·

B
auto


+

0.4
·

B
user




)

,

1.2
·
0.6
·



(




i
=
1

7


TDI
i


)

/
7

48








Equation


7













CF
final

=

min

(


max

(


0.8
·

1600


(




i
=
1

7


TDI
i


)

/
7



,


0.6
·

CF
auto


+

0.4
·

CF
user




)

,

1.2
·

2200


(




i
=
1

7


TDI
i


)

/
7




)





Equation


8













IC
final

=

min

(


max

(


0.8
·

400


(




i
=
1

7


TDI
i


)

/
7



,


0.6
·

IC
auto


+

0.4
·

IC
user




)

,

1.2
·

550


(




i
=
1

7


TDI
i


)

/
7




)





Equation


9







In the maximum function of Equation 7, the first term of—upper bound—0.8 and 0.4 that are used to reduce the insulin delivery factor (as shown above)—where 0.4 is considered the lowest feasible basal dosage boundary considering TDI. For example, a worst case basal/bolus split is 40:60, thus the value 0.4 or 40%). The AID algorithm may further reduce the 40% basal split by 20% by multiplying by 0.8. The AID algorithm sets the upper and the lower bounds at expected values based on insulin history. The second term of the maximum function (or overall middle term) (i.e., 0.6 Bauto+0.4 Buser) is an automated calculation that considers a user's input value (with a user trust of, for example, 40%). The first term and third term are the upper and lower bounds.


In Equation 7, the min/max envelopes may be typical ranges of each of the heuristics utilized by healthcare providers to estimate a user's insulin delivery parameters and may be allowed to be exceeded by up to 20% to account for changes in a user's lifestyle. The user's judgment may be trusted to a point of 40%, in the example. However, the user's judgment may be relied upon to a reasonable margin based on usage history and the like.


Equation 8 similarly accounts for user settings when calculating a final correction factor, CFfinal. As shown in Equation 5, the correction factor is commonly calculated with 1800 in the numerator. In the determination of CFfinal in Equation 8, a value less than 1800, such as the 1600, may work better when basal insulin dosages make up less than 50% of the TDI. In addition, a value greater than 1800, such as 2200, may provide values that are better for those whose basal doses make up more than 50% of their TDI.


Equation 9 also is configured to account for user settings when calculating a final insulin-to-carbohydrate ratio, ICfinal. The insulin to carbohydrate ratio is frequently calculated using a value of 400 in the numerator, but may also use values such as 450, 500, 550, 600 or other clinically relevant value.


In an embodiment, these adjustments can be implemented “behind the scenes” and impact automated components of insulin delivery, such as the AID algorithm and suggested boluses. In another embodiment, these adjustments can be proposed to the users via a prompt in a graphical user interface, such as graphic user interface 204, and the users can make further changes as desired. In this embodiment, the graphical user interface may present a setting with an input that the user may toggle to override (“reset”) the adapted settings of the AID algorithm and force the AID algorithm to start adapting based on the user's input settings.


In an operational example, the routine 700 at block 702 receives a request to modify a specific parameter, wherein the specific parameter is based on a total daily insulin setting. In block 704, the routine 700 reduces the value of a general insulin delivery factor by a predetermined percentage to provide a minimized general insulin delivery factor. In block 706, the routine 700 determines a maximum value between the minimized general insulin delivery factor and a sum of a modified recommended specific parameter and a modified user-selected specific parameter. In block 708, the routine 700 determines a minimum between the determined maximum value and a maximized general insulin delivery factor. In block 710, the routine 700 sets a respective finalized specific parameter to the determined minimum.



FIG. 8 illustrates a drug delivery system operable to implement the examples of FIGS. 1-7.


In some examples, the drug delivery system 800 that is suitable for delivering insulin to a user in accordance with exemplary embodiments. The drug delivery system 800 includes a wearable drug delivery device 802. The wearable drug delivery device 802 may be a wearable device that is worn on the body of the user. The wearable drug delivery device 802 may be directly coupled to a user (e.g., directly attached to a body part and/or skin of the user via an adhesive or the like). In an example, a surface of the wearable drug delivery device 802 may include an adhesive to facilitate attachment to the user.


The wearable drug delivery device 802 may include a processor 810. The processor 810 may be implemented in hardware, software, or any combination thereof. The processor 810 may, for example, be a microprocessor, a logic circuit, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC) or a microprocessor coupled to a memory. The processor 810 may maintain a date and time as well as other functions (e.g., calculations or the like). The processor 810 may be operable to execute a control application 816 stored in the storage 814 that enables the processor 810 to direct operation of the wearable drug delivery device 802. The control application 816 may control insulin delivery to the user per an AID control approach as describe herein. The storage 814 may hold histories 815 for a user, such as a history of automated insulin deliveries, a history of bolus insulin deliveries, meal event history, exercise event history and the like. In addition, the processor 810 may be operable to receive data or information. The storage 814 may include both primary memory and secondary memory. The storage 814 may include random access memory (RAM), read only memory (ROM), optical storage, magnetic storage, removable storage media, solid state storage or the like.


The wearable drug delivery device 802 may include a reservoir 812. The reservoir 812 may be operable to store drugs, medications or therapeutic agents suitable for automated delivery, such as insulin, morphine, methadone, hormones, glucagon, glucagon-like peptide, blood pressure medicines, chemotherapy drugs, combinations of drugs, such as insulin and glucagon-like peptide, or the like. A fluid path to the user may be provided, and the wearable drug delivery device 802 may expel the insulin from the reservoir 812 to deliver the insulin to the user via the fluid path. The fluid path may, for example, include tubing coupling the wearable drug delivery device 802 to the user (e.g., via tubing coupling a cannula to the reservoir 812).


There may be one or more communications links with one or more devices physically separated from the wearable drug delivery device 802 including, for example, a controller 804 of the user and/or a caregiver of the user and/or a sensor 806. The communication links may include any wired or wireless communication link operating according to any known communications protocol or standard, such as Bluetooth®, Wi-Fi, a near-field communication standard, a cellular standard, or any other wireless protocol. The wearable drug delivery device 802 may also include a user interface 817, such as an integrated display device for displaying information to the user and in some embodiments, receiving information from the user. The user interface 817 may include a touchscreen and/or one or more input devices, such as buttons, knob or a keyboard.


The wearable drug delivery device 802 may interface with a network 842. The network 842 may include a local area network (LAN), a wide area network (WAN) or a combination therein. A computing device 826 may be interfaced with the network, and the computing device may communicate with the insulin delivery device 802. The computing device 826 may be a healthcare provider device through which the user may interact with the user's controller 804. The AID algorithm controlled via the control application 820 may present a graphical user interface on the computing device 826 similar to the graphic user interface 204 of FIG. 2 so a healthcare provider or guardian may input information, such as that described with reference to the earlier examples.


The drug delivery system 800 may include a sensor 806 for sensing the levels of one or more analytes. The sensor 806 may be coupled to the user by, for example, adhesive or the like and may provide information or data on one or more medical conditions and/or physical attributes of the user. The sensor 806 may be a continuous glucose monitor (CGM), or another type of device or sensor that provides blood glucose measurements that is operable to provide blood glucose concentration measurements. The sensor 806 may be physically separate from the wearable drug delivery device 802 or may be an integrated component thereof. The sensor 806 may provide the processor 810 with data indicative of measured or detected blood glucose levels of the user. The information or data provided by the sensor 806 may be used to adjust drug delivery operations of the wearable drug delivery device 802.


The drug delivery system 800 may also include the controller 804. In some embodiments, no controller is needed. The controller 804 may be a special purpose device, such as a dedicated personal diabetes manager (PDM) device. The controller 804 may be a programmed general-purpose device, such as any portable electronic device including, for example, a dedicated processor, such as processor, a micro-processor or the like. The controller 804 may be used to program or adjust operation of the wearable drug delivery device 802 and/or the sensor 806. The controller 804 may be any portable electronic device including, for example, a dedicated device, a smartphone, a smartwatch or a tablet. In the depicted example, the controller 804 may include a processor 819 and a memory/storage 818. The processor 119 may execute processes to manage a user's blood glucose levels and for control of the delivery of a drug or therapeutic agent to the user. The processor 819 may also be operable to execute programming code stored in the storage 818. For example, the storage may be operable to store one or more control applications 820, such as an AID algorithm for execution by the processor 819. The one or more control applications 820 may be responsible for controlling the wearable drug delivery device 802, including the automatic delivery of insulin based on recommendations and instructions provided by the AID algorithm to the user. For example, the AID algorithm as part of the one or more control applications 820 may generate a signal according to a determined dosage of insulin and cause the processor 819 to forward the signal via a transceiver, such as 828 or 827 of the communication device 822, to the wearable drug delivery device 802. The memory or storage 818 may store the one or more control applications 820, histories 821 like those described above for the insulin delivery device 802 and other data and/or programs.


The controller 804 may include a user interface (UI) 823 for communicating with the user. The user interface 823 may include a display, such as a touchscreen, for displaying information. The touchscreen may also be used to receive input when it is a touch screen. The user interface 823 may also include input elements, such as a keyboard, button, knob or the like.


The controller 804 may interface via a wireless communication link of the wireless communication links 888 with a network, such as a LAN or WAN or combination of such networks that provides one or more servers or cloud-based services 828. The cloud-based services 828 may be operable to store user history information, such as blood glucose measurement values over a set period of time (e.g., days, months, years), insulin delivery amounts (both basal and bolus dosages), insulin delivery times, types of insulin, indicated mealtimes, blood glucose measurement value trends or excursions or other user-related diabetes treatment information.


Other devices, like smart accessory device 830 (e.g., a smartwatch or the like), fitness device 832 and wearable device 834 may be part of the drug delivery system 800. These devices may communicate with the wearable drug delivery device 802 to receive information and/or issue commands to the wearable drug delivery device 802. These devices 830, 832 and 834 may execute computer programming instructions to perform some of the control functions otherwise performed by processor 810 or processor 819. These devices 830, 832 and 834 may include input/output devices, such as touchscreen displays for displaying information such as current blood glucose level, insulin on board, insulin deliver history, or other parameters or treatment-related information and/or receiving inputs, which may include signals containing the information from the analyte sensor 806. The display may, for example, be operable to present a graphical user interface for providing input, such as request a change in basal insulin dosage or delivery of a bolus of insulin. These devices 830, 832 and 834 may also have wireless communication connections with the sensor 806 to directly receive blood glucose level data.


In an operational example, the controller 804 includes a processor. The processor 819 of the controller 804 may execute an AID algorithm that is one of the control applications 820 stored in the memory or storage 818. The processor may be operable to present, on an input/output device that is the user interface 823, a graphical user interface that offers input fields for a generalized parameter of a number of generalized parameters of the AID algorithm. The number of generalized parameters is substantially less than a number of specific parameters of the AID algorithm. The processor 819 may receive an input of at least one generalized parameter corresponding to a user. In response to receiving the input of the at least one generalized parameter, the processor may set one or more of the number of specific parameters of the automated insulin delivery algorithm based on the inputted at least one generalized parameter. The processor 819 may begin collecting physiological condition data related to the user from sensors, such as the analyte sensor 806 or heart rate data from the fitness device 832 or smart accessory device 830. The processor 819 executing the AID algorithm may determine a dosage of insulin to be delivered based on the collected physiological condition of the user. The processor 819 may output a signal via one of the transceivers 827 or 828 to the wearable drug delivery device 802. The outputted signal may cause the pump 813 to deliver an amount of related to the determined dosage of insulin in the reservoir 812 to the user based on an output of the AID algorithm.


In another operational example, the controller 804 may be operable to execute programming code that causes the processor 819 of the controller 804 to perform the following functions. The processor 819 may in response to receipt of a user selected basal setting, determine value of an hourly basal insulin delivery factor. The value of the hourly basal insulin delivery factor may be reduced by a predetermined percentage to provide a minimized hourly basal insulin delivery factor. A maximum value between the reduced-percentage insulin delivery factor and a sum of a modified recommended basal dosage and a modified, user-selected basal dosage may also be determined. The processor 819 may determine a minimum between the determined maximum and a maximized hourly basal insulin delivery factor and may set a final basal dosage setting of the AID algorithm to the determined minimum. The AID algorithm may generate instructions for the pump 813 to deliver basal insulin to the user that remains below the determined minimum amount which is the final basal dosage setting for a period of time such as a day or the like.


In yet another operational example, the controller 804 may be operable to execute programming code that causes the processor 819 of the controller 804 to perform the following functions. The processor 819 may in response to receipt of a user selected correction factor setting, determine a value of a daily correction factor. The value of the daily correction factor may be reduced by a predetermined percentage to provide a minimized daily correction factor. A maximum value between the minimized daily correction factor and a sum of a modified recommended correction factor and a modified, user-selected correction factor may be determined. The processor 819 may determine a minimum between the determined maximum and a maximized daily correction factor. The processor 819 may set a final correction factor setting to the determined minimum. The AID algorithm may generate instructions for the pump 813 to deliver basal insulin to the user according to the final correction factor setting.


In a further operational example, the controller 804 may be operable to execute programming code that causes the processor 819 of the controller 804 to perform the following functions. The processor 819 may in response to receipt of a user selected insulin-to-carbohydrate setting, determine a value of a daily insulin-to-carbohydrate factor. The value of the daily insulin-to-carbohydrate factor may be reduced by a predetermined percentage to provide a minimized daily correction factor. A maximum value between the minimized daily insulin-to-carbohydrate factor and a sum of a modified recommended insulin-to-carbohydrate factor and a modified, user-selected insulin-to-carbohydrate factor may be determined by the processor 819. In addition, the processor 819 may determine a minimum between the determined maximum and a maximized daily insulin-to-carbohydrate factor. The processor 819 may set a final insulin-to-carbohydrate setting to the determined minimum. The AID algorithm may generate instructions for the pump 813 to deliver basal insulin to the user according to the final insulin-to-carbohydrate setting.


Further the insulin delivery recommendations provided by the AID algorithm may be individualized based on the user's response in the past. Glucose excursion patterns, incidences of hyperglycemia/hypoglycemia, and the like may be used to optimize insulin delivery for the future.


Some examples of the disclosed device or processes may be implemented, for example, using a storage medium, a computer-readable medium, or an article of manufacture which may store an instruction or a set of instructions that, if executed by a machine (i.e., processor or controller), may cause the machine to perform a method and/or operation in accordance with examples of the disclosure. Such a machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware and/or software. The computer-readable medium or article may include, for example, any suitable type of memory unit, memory, memory article, memory medium, storage device, storage article, storage medium and/or storage unit, for example, memory (including non-transitory memory), removable or non-removable media, erasable or non-erasable media, writeable or re-writeable media, digital or analog media, hard disk, floppy disk, Compact Disk Read Only Memory (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or disks, various types of Digital Versatile Disk (DVD), a tape, a cassette, or the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, programming code, and the like, implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language. The non-transitory computer readable medium embodied programming code may cause a processor when executing the programming code to perform functions, such as those described herein.


Certain examples of the present disclosure were described above. It is, however, expressly noted that the present disclosure is not limited to those examples, but rather the intention is that additions and modifications to what was expressly described herein are also included within the scope of the disclosed examples. Moreover, it is to be understood that the features of the various examples described herein were not mutually exclusive and may 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 disclosed examples. In fact, variations, modifications, and other implementations of what was described herein will occur to those of ordinary skill in the art without departing from the spirit and the scope of the disclosed examples. As such, the disclosed examples are not to be defined only by the preceding illustrative description.


Program aspects of the technology may be thought of as “products” or “articles of manufacture” typically in the form of executable code and/or associated data that is carried on or embodied in a type of non-transitory, machine readable medium. Storage type media include any or all of the tangible memory of the computers, processors or the like, or associated modules thereof, such as various semiconductor memories, tape drives, disk drives and the like, which may provide non-transitory storage at any time for the software programming. It is emphasized that the Abstract of the Disclosure is provided to allow a reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, various features are grouped together in a single example for streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed examples require more features than are expressly recited in each claim. Rather, as the following claims reflect, novel subject matter lies in less than all features of a single disclosed example. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate example. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein,” respectively. Moreover, the terms “first,” “second,” “third,” and so forth, are used merely as labels and are not intended to impose numerical requirements on their objects.


The foregoing description of examples has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the present disclosure to the precise forms disclosed. Many modifications and variations are possible considering this disclosure. It is intended that the scope of the present disclosure be limited not by this detailed description, but rather by the claims appended hereto. Future filed applications claiming priority to this application may claim the disclosed subject matter in a different manner and may generally include any set of one or more features as variously disclosed or otherwise demonstrated herein.

Claims
  • 1. A controller, comprising: a processor;an input/output device; anda memory storing instructions that, when executed by the processor, configure the processor to: present, on the input/output device, a graphical user interface offering a plurality of input fields that correspond to a plurality of generalized parameters of an automated insulin delivery algorithm, wherein at least one input field of the plurality of input fields presents a first reference value and a second reference value of a generalized parameter on the graphical user interface;receive in the at least one input field via the input/output device an input of the generalized parameter between the first reference value and the second reference value;in response to receiving the input of the generalized parameter, set a specific parameter of the automated insulin delivery algorithm based on the inputted generalized parameter;determine, by the automated insulin delivery algorithm using the set specific parameter that was set based on the inputted generalized parameter, a dosage of insulin to be delivered to the user; andcause the determined dosage of insulin to be delivered to the user.
  • 2. The controller of claim 1, wherein the specific parameter includes an estimated initial total daily insulin (TDI) amount, an upper boundary of insulin delivery, a basal/bolus ratio, an insulin-on-board (IOB) amount, or a combination of two or more of the foregoing.
  • 3. The controller of claim 1, wherein the inputted generalized parameter is a reference basal of the user.
  • 4. The controller of claim 1, wherein the inputted generalized parameter is a user's weight and the processor, when setting the specific parameter of the automated insulin delivery algorithm based on the inputted sole generalized parameter, is operable to: set an upper boundary for an amount of insulin to be delivered to the user.
  • 5. The controller of claim 1, wherein the processor is further operable to: generate a request for confirmation of a value of the set specific parameter by presenting a confirmation button in the graphical user interface on the input/output device;allow the user to increase or decrease the value of the set specific parameter; andreceive an input confirming the value of the set specific parameter.
  • 6. The controller of claim 1, wherein the processor is further operable to: generate a signal according to the determined dosage of insulin; andforward the signal to a wearable drug delivery device.
  • 7. The controller of claim 1, wherein the processor is further operable to: collect physiological condition data related to the user; andmodify the set specific parameter up or down over time to reflect an insulin need of the user.
  • 8. A method, comprising: presenting, on an input/output device of a user device, a graphical user interface offering a plurality of input fields that correspond to a plurality of generalized parameters of an automated insulin delivery algorithm, wherein at least one input field of the plurality of input fields of the graphical user interface presents a first reference value and a second reference value of a generalized parameter on the graphical user interface;receiving in the at least one input field via the input/output device an input of the generalized parameter within the first reference value and the second reference value;in response to receiving the input of the generalized parameter, setting a specific parameter of the automated insulin delivery algorithm based on the inputted generalized parameter;determining, by the automated insulin delivery algorithm using the set specific parameter that was set based on the inputted generalized parameter, a dosage of insulin to be delivered to a user; andcausing the determined dosage of insulin to be delivered to the user.
  • 9. The method of claim 8, wherein the number of specific parameters includes at least one of an estimated initial total daily insulin (TDI) amount, an upper boundary of insulin delivery, a basal/bolus ratio, and an insulin-on-board (IOB) amount.
  • 10. The method of claim 8, wherein the inputted generalized parameter is a reference basal of the user.
  • 11. The method of claim 10, wherein the method further comprises: setting an upper boundary an amount of insulin to be delivered to the user.
  • 12. The method of claim 8, wherein the method further comprises: generating a request for confirmation of a value of the set specific parameter by presenting a confirmation button in the graphical user interface on the input/output device;presenting an option to allow the user to modify the value of the set specific parameter; andreceiving an input confirming the value, whether modified or not, of the set specific parameter.
  • 13. The method of claim 8, wherein causing the determined dosage of insulin to be delivered to the user, further comprises: generating a signal according to the determined dosage of insulin; andforwarding the signal to a wearable drug delivery device.
  • 14. A system comprising: a non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that when executed by at least one processor, cause the at least one processor to: present, on an input/output device, a graphical user interface offering a plurality of input fields that correspond to a plurality of generalized parameters of an automated insulin delivery algorithm, wherein at least one input field of the plurality of input fields presents a first reference value and a second reference value of a generalized parameter on the graphical user interface;receive in the at least one input field via the input/output device via the input/output device an input of only one generalized parameter between the first reference value and the second reference value presented on the graphical user interface;in response to receiving the input of the only one generalized parameter, set a specific parameter of the automated insulin delivery algorithm based on the only one inputted generalized parameter;determine, by the automated insulin delivery algorithm using the set specific parameter that was set based on the only one inputted generalized parameter, a dosage of insulin to be delivered to the user; andcause the determined dosage of insulin to be delivered to the user.
  • 15. The system of claim 14, wherein the specific parameter includes an estimated initial total daily insulin (TDI) amount, an upper boundary of insulin delivery, a basal/bolus ratio, an insulin-on-board (IOB) amount, or a combination of two or more of the foregoing.
  • 16. The system of claim 14, wherein the only one inputted generalized parameter is a reference of the user.
  • 17. The system of claim 16, wherein the instructions further cause the at least one processor, when setting the specific parameter of the automated insulin delivery algorithm based on the inputted only one generalized parameter, to: set an upper boundary for an amount of insulin to be delivered to the user.
  • 18. The system of claim 14, wherein the instructions further cause the at least one processor to: generate a request for confirmation of a value of the set specific parameter by presenting a confirmation button in the graphical user interface on the input/output device;allow the user to increase or decrease the value of the set specific parameter; andreceive an input confirming the value of the set specific parameter.
  • 19. The system of claim 14, further comprising: a wearable drug delivery device having a processor executing the automated insulin delivery algorithm, and the processor of the wearable drug delivery device is operable to: perform the determining of the dosage of insulin to be delivered to the user using the set specific parameter.
  • 20. The system of claim 14, wherein the instructions further cause the processor to: collect physiological condition data related to the user; andmodify the set specific parameter up or down to reflect an insulin need of the user indicated by the collected physiological condition data.
RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Patent Application No. 63/248,844, filed Sep. 27, 2021, the contents of which are incorporated herein by reference in their entirety.

US Referenced Citations (589)
Number Name Date Kind
303013 Horton Aug 1884 A
2797149 Skeggs Jun 1957 A
3631847 Hobbs Jan 1972 A
3634039 Brondy Jan 1972 A
3812843 Wootten et al. May 1974 A
3841328 Jensen Oct 1974 A
3963380 Thomas, Jr. et al. Jun 1976 A
4055175 Clemens et al. Oct 1977 A
4146029 Ellinwood, Jr. Mar 1979 A
4151845 Clemens May 1979 A
4245634 Albisser et al. Jan 1981 A
4368980 Aldred et al. Jan 1983 A
4373527 Fischell Feb 1983 A
4403984 Ash et al. Sep 1983 A
4464170 Clemens et al. Aug 1984 A
4469481 Kobayashi Sep 1984 A
4475901 Kraegen et al. Oct 1984 A
4526568 Clemens et al. Jul 1985 A
4526569 Bernardi Jul 1985 A
4529401 Leslie et al. Jul 1985 A
4559033 Stephen et al. Dec 1985 A
4559037 Franetzki et al. Dec 1985 A
4573968 Parker Mar 1986 A
4624661 Arimond Nov 1986 A
4633878 Bombardieri Jan 1987 A
4657529 Prince et al. Apr 1987 A
4685903 Cable et al. Aug 1987 A
4731726 Allen, III Mar 1988 A
4743243 Vaillancourt May 1988 A
4755173 Konopka et al. Jul 1988 A
4781688 Thoma et al. Nov 1988 A
4781693 Martinez et al. Nov 1988 A
4808161 Kamen Feb 1989 A
4854170 Brimhall et al. Aug 1989 A
4886499 Cirelli et al. Dec 1989 A
4900292 Berry et al. Feb 1990 A
4919596 Slate et al. Apr 1990 A
4925444 Orkin et al. May 1990 A
4940527 Kazlauskas et al. Jul 1990 A
4975581 Robinson et al. Dec 1990 A
4976720 Machold et al. Dec 1990 A
4981140 Wyatt Jan 1991 A
4994047 Walker et al. Feb 1991 A
5007286 Malcolm et al. Apr 1991 A
5097834 Skrabal Mar 1992 A
5102406 Arnold Apr 1992 A
5109850 Blanco et al. May 1992 A
5125415 Bell Jun 1992 A
5134079 Cusack et al. Jul 1992 A
5153827 Coutre et al. Oct 1992 A
5165406 Wong Nov 1992 A
5176662 Bartholomew et al. Jan 1993 A
5178609 Ishikawa Jan 1993 A
5207642 Orkin et al. May 1993 A
5232439 Campbell et al. Aug 1993 A
5237993 Skrabal Aug 1993 A
5244463 Cordner, Jr. et al. Sep 1993 A
5257980 Van Antwerp et al. Nov 1993 A
5273517 Barone et al. Dec 1993 A
5281808 Kunkel Jan 1994 A
5299571 Mastrototaro Apr 1994 A
5308982 Ivaldi et al. May 1994 A
5342298 Michaels et al. Aug 1994 A
5377674 Kuestner Jan 1995 A
5380665 Cusack et al. Jan 1995 A
5385539 Maynard Jan 1995 A
5389078 Zalesky Feb 1995 A
5411889 Hoots et al. May 1995 A
5421812 Langley et al. Jun 1995 A
5468727 Phillips et al. Nov 1995 A
5505709 Funderburk et al. Apr 1996 A
5505828 Wong et al. Apr 1996 A
5507288 Bocker et al. Apr 1996 A
5533389 Kamen et al. Jul 1996 A
5558640 Pfeiler et al. Sep 1996 A
5569186 Lord et al. Oct 1996 A
5584813 Livingston et al. Dec 1996 A
5609572 Lang Mar 1997 A
5665065 Colman et al. Sep 1997 A
5678539 Schubert et al. Oct 1997 A
5685844 Marttila Nov 1997 A
5685859 Kornerup Nov 1997 A
5693018 Kriesel et al. Dec 1997 A
5697899 Hillman et al. Dec 1997 A
5700695 Yassinzadeh et al. Dec 1997 A
5703364 Rosenthal Dec 1997 A
5714123 Sohrab Feb 1998 A
5716343 Kriesel et al. Feb 1998 A
5722397 Eppstein Mar 1998 A
5741228 Lambrecht et al. Apr 1998 A
5746217 Erickson et al. May 1998 A
5755682 Knudson et al. May 1998 A
5758643 Wong et al. Jun 1998 A
5800405 McPhee Sep 1998 A
5800420 Gross et al. Sep 1998 A
5801057 Smart et al. Sep 1998 A
5804048 Wong et al. Sep 1998 A
5817007 Fodgaard et al. Oct 1998 A
5820622 Gross et al. Oct 1998 A
5823951 Messerschmidt Oct 1998 A
5840020 Heinonen et al. Nov 1998 A
5848991 Gross et al. Dec 1998 A
5851197 Marano et al. Dec 1998 A
5858005 Kriesel Jan 1999 A
5865806 Howell Feb 1999 A
5871470 McWha Feb 1999 A
5879310 Sopp et al. Mar 1999 A
5902253 Pfeiffer et al. May 1999 A
5931814 Alex et al. Aug 1999 A
5932175 Knute et al. Aug 1999 A
5935099 Peterson et al. Aug 1999 A
5947911 Wong et al. Sep 1999 A
5971941 Simons et al. Oct 1999 A
5993423 Choi Nov 1999 A
5997501 Gross et al. Dec 1999 A
6017318 Gauthier et al. Jan 2000 A
6024539 Blomquist Feb 2000 A
6032059 Henning et al. Feb 2000 A
6036924 Simons et al. Mar 2000 A
6040578 Malin et al. Mar 2000 A
6049727 Grothall Apr 2000 A
6050978 Or et al. Apr 2000 A
6058934 Sullivan May 2000 A
6066103 Duchon et al. May 2000 A
6071292 Makower et al. Jun 2000 A
6072180 Kramer et al. Jun 2000 A
6077055 Vilks Jun 2000 A
6090092 Fowles et al. Jul 2000 A
6101406 Hacker et al. Aug 2000 A
6102872 Doneen et al. Aug 2000 A
6115673 Malin et al. Sep 2000 A
6123827 Wong et al. Sep 2000 A
6124134 Stark Sep 2000 A
6126637 Kriesel et al. Oct 2000 A
6128519 Say Oct 2000 A
6142939 Eppstein et al. Nov 2000 A
6143164 Heller et al. Nov 2000 A
6157041 Thomas et al. Dec 2000 A
6161028 Braig et al. Dec 2000 A
6162639 Douglas Dec 2000 A
6196046 Braig et al. Mar 2001 B1
6200287 Keller et al. Mar 2001 B1
6200338 Solomon et al. Mar 2001 B1
6214629 Freitag et al. Apr 2001 B1
6226082 Roe May 2001 B1
6244776 Wiley Jun 2001 B1
6261065 Nayak et al. Jul 2001 B1
6262798 Shepherd et al. Jul 2001 B1
6270455 Brown Aug 2001 B1
6271045 Douglas et al. Aug 2001 B1
6280381 Malin et al. Aug 2001 B1
6285448 Kuenstner Sep 2001 B1
6309370 Haim et al. Oct 2001 B1
6312888 Wong et al. Nov 2001 B1
6334851 Hayes et al. Jan 2002 B1
6375627 Mauze et al. Apr 2002 B1
6379301 Worthington et al. Apr 2002 B1
6402689 Scarantino et al. Jun 2002 B1
6470279 Samsoondar Oct 2002 B1
6475196 Vachon Nov 2002 B1
6477901 Tadigadapa et al. Nov 2002 B1
6484044 Lilienfeld-Toal Nov 2002 B1
6491656 Morris Dec 2002 B1
6512937 Blank et al. Jan 2003 B2
6525509 Petersson et al. Feb 2003 B1
6528809 Thomas et al. Mar 2003 B1
6540672 Simonsen et al. Apr 2003 B1
6544212 Galley et al. Apr 2003 B2
6546268 Ishikawa et al. Apr 2003 B1
6546269 Kurnik Apr 2003 B1
6553841 Blouch Apr 2003 B1
6554798 Mann et al. Apr 2003 B1
6556850 Braig et al. Apr 2003 B1
6558351 Steil et al. May 2003 B1
6560471 Heller et al. May 2003 B1
6561978 Conn et al. May 2003 B1
6562001 Lebel et al. May 2003 B2
6562014 Lin et al. May 2003 B2
6569125 Jepson et al. May 2003 B2
6572542 Houben et al. Jun 2003 B1
6572545 Knobbe et al. Jun 2003 B2
6574490 Abbink et al. Jun 2003 B2
6575905 Knobbe et al. Jun 2003 B2
6580934 Braig et al. Jun 2003 B1
6618603 Varalli et al. Sep 2003 B2
6633772 Ford et al. Oct 2003 B2
6645142 Braig et al. Nov 2003 B2
6653091 Dunn et al. Nov 2003 B1
6662030 Khalil et al. Dec 2003 B2
6669663 Thompson Dec 2003 B1
6678542 Braig et al. Jan 2004 B2
6699221 Vaillancourt Mar 2004 B2
6718189 Rohrscheib et al. Apr 2004 B2
6721582 Trepagnier et al. Apr 2004 B2
6728560 Kollias et al. Apr 2004 B2
6740059 Flaherty May 2004 B2
6740072 Starkweather et al. May 2004 B2
6751490 Esenaliev et al. Jun 2004 B2
6758835 Close et al. Jul 2004 B2
6780156 Haueter et al. Aug 2004 B2
6810290 Lebel et al. Oct 2004 B2
6837858 Cunningham et al. Jan 2005 B2
6837988 Leong et al. Jan 2005 B2
6846288 Nagar et al. Jan 2005 B2
6862534 Sterling et al. Mar 2005 B2
6865408 Abbink et al. Mar 2005 B1
6890291 Robinson et al. May 2005 B2
6936029 Mann et al. Aug 2005 B2
6949081 Chance Sep 2005 B1
6958809 Sterling et al. Oct 2005 B2
6989891 Braig et al. Jan 2006 B2
6990366 Say et al. Jan 2006 B2
7008404 Nakajima Mar 2006 B2
7009180 Sterling et al. Mar 2006 B2
7016713 Gardner et al. Mar 2006 B2
7018360 Flaherty et al. Mar 2006 B2
7025743 Mann et al. Apr 2006 B2
7025744 Utterberg et al. Apr 2006 B2
7027848 Robinson et al. Apr 2006 B2
7043288 Davis, III et al. May 2006 B2
7060059 Keith et al. Jun 2006 B2
7061593 Braig et al. Jun 2006 B2
7096124 Sterling et al. Aug 2006 B2
7115205 Robinson et al. Oct 2006 B2
7128727 Flaherty et al. Oct 2006 B2
7139593 Kavak et al. Nov 2006 B2
7139598 Hull et al. Nov 2006 B2
7144384 Gorman et al. Dec 2006 B2
7171252 Scarantino et al. Jan 2007 B1
7190988 Say et al. Mar 2007 B2
7204823 Estes et al. Apr 2007 B2
7248912 Gough et al. Jul 2007 B2
7267665 Steil et al. Sep 2007 B2
7271912 Sterling et al. Sep 2007 B2
7278983 Ireland et al. Oct 2007 B2
7291107 Hellwig et al. Nov 2007 B2
7291497 Holmes et al. Nov 2007 B2
7303549 Flaherty et al. Dec 2007 B2
7303622 Loch et al. Dec 2007 B2
7303922 Jeng et al. Dec 2007 B2
7354420 Steil et al. Apr 2008 B2
7388202 Sterling et al. Jun 2008 B2
7402153 Steil et al. Jul 2008 B2
7404796 Ginsberg Jul 2008 B2
7429255 Thompson Sep 2008 B2
7460130 Salganicoff Dec 2008 B2
7481787 Gable et al. Jan 2009 B2
7491187 Van Den Berghe et al. Feb 2009 B2
7500949 Gottlieb et al. Mar 2009 B2
7509156 Flanders Mar 2009 B2
7547281 Hayes et al. Jun 2009 B2
7569030 Lebel et al. Aug 2009 B2
7608042 Goldberger et al. Oct 2009 B2
7651845 Doyle, III et al. Jan 2010 B2
7680529 Kroll Mar 2010 B2
7734323 Blomquist et al. Jun 2010 B2
7766829 Sloan et al. Aug 2010 B2
7785258 Braig et al. Aug 2010 B2
7806854 Damiano et al. Oct 2010 B2
7806886 Kanderian, Jr. et al. Oct 2010 B2
7918825 OConnor et al. Apr 2011 B2
7946985 Mastrototaro et al. May 2011 B2
7972296 Braig et al. Jul 2011 B2
8221345 Blomquist Jul 2012 B2
8251907 Sterling et al. Aug 2012 B2
8449524 Braig et al. May 2013 B2
8452359 Rebec et al. May 2013 B2
8454576 Mastrototaro et al. Jun 2013 B2
8467980 Campbell et al. Jun 2013 B2
8478557 Hayter et al. Jul 2013 B2
8547239 Peatfield et al. Oct 2013 B2
8597274 Sloan et al. Dec 2013 B2
8622988 Hayter Jan 2014 B2
8810394 Kalpin Aug 2014 B2
9061097 Holt et al. Jun 2015 B2
9171343 Fischell et al. Oct 2015 B1
9233204 Booth et al. Jan 2016 B2
9486571 Rosinko Nov 2016 B2
9579456 Budiman et al. Feb 2017 B2
9743224 San Vicente et al. Aug 2017 B2
9907515 Doyle, III et al. Mar 2018 B2
9980140 Spencer et al. May 2018 B1
9984773 Gondhalekar et al. May 2018 B2
10248839 Levy et al. Apr 2019 B2
10335464 Michelich et al. Jul 2019 B1
10583250 Mazlish et al. Mar 2020 B2
10737024 Schmid Aug 2020 B2
10987468 Mazlish et al. Apr 2021 B2
11197964 Sjolund et al. Dec 2021 B2
11260169 Estes Mar 2022 B2
20010021803 Blank et al. Sep 2001 A1
20010034023 Stanton, Jr. et al. Oct 2001 A1
20010034502 Moberg et al. Oct 2001 A1
20010051377 Hammer et al. Dec 2001 A1
20010053895 Vaillancourt Dec 2001 A1
20020010401 Bushmakin et al. Jan 2002 A1
20020010423 Gross et al. Jan 2002 A1
20020016568 Lebel et al. Feb 2002 A1
20020040208 Flaherty et al. Apr 2002 A1
20020123740 Flaherty et al. Sep 2002 A1
20020128543 Leonhardt Sep 2002 A1
20020147423 Burbank et al. Oct 2002 A1
20020155425 Han et al. Oct 2002 A1
20020161288 Shin et al. Oct 2002 A1
20030023148 Lorenz et al. Jan 2003 A1
20030050621 Lebel et al. Mar 2003 A1
20030060692 L. Ruchti et al. Mar 2003 A1
20030086074 Braig et al. May 2003 A1
20030086075 Braig et al. May 2003 A1
20030090649 Sterling et al. May 2003 A1
20030100040 Bonnecaze et al. May 2003 A1
20030130616 Steil et al. Jul 2003 A1
20030135388 Martucci et al. Jul 2003 A1
20030144582 Cohen et al. Jul 2003 A1
20030163097 Fleury et al. Aug 2003 A1
20030195404 Knobbe et al. Oct 2003 A1
20030208113 Mault et al. Nov 2003 A1
20030208154 Close et al. Nov 2003 A1
20030212379 Bylund et al. Nov 2003 A1
20030216627 Lorenz et al. Nov 2003 A1
20030220605 Bowman, Jr. et al. Nov 2003 A1
20040010207 Flaherty et al. Jan 2004 A1
20040034295 Salganicoff Feb 2004 A1
20040045879 Shults et al. Mar 2004 A1
20040051368 Caputo et al. Mar 2004 A1
20040064259 Haaland et al. Apr 2004 A1
20040097796 Berman et al. May 2004 A1
20040116847 Wall Jun 2004 A1
20040122353 Shahmirian et al. Jun 2004 A1
20040133166 Moberg et al. Jul 2004 A1
20040147034 Gore et al. Jul 2004 A1
20040171983 Sparks et al. Sep 2004 A1
20040203357 Nassimi Oct 2004 A1
20040204868 Maynard et al. Oct 2004 A1
20040215492 Choi Oct 2004 A1
20040220517 Starkweather et al. Nov 2004 A1
20040241736 Hendee et al. Dec 2004 A1
20040249308 Forssell Dec 2004 A1
20050003470 Nelson et al. Jan 2005 A1
20050020980 Inoue et al. Jan 2005 A1
20050022274 Campbell et al. Jan 2005 A1
20050033148 Haueter et al. Feb 2005 A1
20050049179 Davidson et al. Mar 2005 A1
20050065464 Talbot et al. Mar 2005 A1
20050065465 Lebel et al. Mar 2005 A1
20050075624 Miesel Apr 2005 A1
20050105095 Pesach et al. May 2005 A1
20050137573 McLaughlin Jun 2005 A1
20050171503 Van Den Berghe et al. Aug 2005 A1
20050182306 Sloan Aug 2005 A1
20050192494 Ginsberg Sep 2005 A1
20050192557 Brauker et al. Sep 2005 A1
20050197621 Poulsen et al. Sep 2005 A1
20050203360 Brauker et al. Sep 2005 A1
20050203461 Flaherty et al. Sep 2005 A1
20050238507 Dilanni et al. Oct 2005 A1
20050261660 Choi Nov 2005 A1
20050272640 Doyle, III et al. Dec 2005 A1
20050277912 John Dec 2005 A1
20060009727 OMahony et al. Jan 2006 A1
20060079809 Goldberger et al. Apr 2006 A1
20060100494 Kroll May 2006 A1
20060134323 OBrien Jun 2006 A1
20060167350 Monfre et al. Jul 2006 A1
20060173406 Hayes et al. Aug 2006 A1
20060189925 Gable et al. Aug 2006 A1
20060189926 Hall et al. Aug 2006 A1
20060197015 Sterling et al. Sep 2006 A1
20060200070 Callicoat et al. Sep 2006 A1
20060204535 Johnson Sep 2006 A1
20060229531 Goldberger et al. Oct 2006 A1
20060253085 Geismar et al. Nov 2006 A1
20060264895 Flanders Nov 2006 A1
20060270983 Lord et al. Nov 2006 A1
20060276771 Galley et al. Dec 2006 A1
20060282290 Flaherty et al. Dec 2006 A1
20070016127 Staib et al. Jan 2007 A1
20070060796 Kim Mar 2007 A1
20070060869 Tolle et al. Mar 2007 A1
20070060872 Hall et al. Mar 2007 A1
20070083160 Hall et al. Apr 2007 A1
20070106135 Sloan et al. May 2007 A1
20070116601 Patton May 2007 A1
20070118405 Campbell et al. May 2007 A1
20070129690 Rosenblatt et al. Jun 2007 A1
20070142720 Ridder et al. Jun 2007 A1
20070173761 Kanderian et al. Jul 2007 A1
20070173974 Lin et al. Jul 2007 A1
20070179352 Randlov et al. Aug 2007 A1
20070191716 Goldberger et al. Aug 2007 A1
20070197163 Robertson Aug 2007 A1
20070225675 Robinson et al. Sep 2007 A1
20070244381 Robinson et al. Oct 2007 A1
20070249007 Rosero Oct 2007 A1
20070264707 Liederman et al. Nov 2007 A1
20070282269 Carter et al. Dec 2007 A1
20070287985 Estes et al. Dec 2007 A1
20070293843 Ireland et al. Dec 2007 A1
20080033272 Gough et al. Feb 2008 A1
20080051764 Dent et al. Feb 2008 A1
20080058625 McGarraugh et al. Mar 2008 A1
20080065050 Sparks et al. Mar 2008 A1
20080071157 McGarraugh et al. Mar 2008 A1
20080071158 McGarraugh et al. Mar 2008 A1
20080078400 Martens et al. Apr 2008 A1
20080097289 Steil et al. Apr 2008 A1
20080132880 Buchman Jun 2008 A1
20080161664 Mastrototaro et al. Jul 2008 A1
20080172026 Blomquist Jul 2008 A1
20080177165 Blomquist et al. Jul 2008 A1
20080188796 Steil et al. Aug 2008 A1
20080200838 Goldberger et al. Aug 2008 A1
20080206067 De Corral et al. Aug 2008 A1
20080208113 Damiano et al. Aug 2008 A1
20080214919 Harmon et al. Sep 2008 A1
20080228056 Blomquist et al. Sep 2008 A1
20080249386 Besterman et al. Oct 2008 A1
20080269585 Ginsberg Oct 2008 A1
20080269714 Mastrototaro et al. Oct 2008 A1
20080269723 Mastrototaro et al. Oct 2008 A1
20080287906 Burkholz et al. Nov 2008 A1
20090006061 Thukral et al. Jan 2009 A1
20090018406 Yodfat et al. Jan 2009 A1
20090030398 Yodfat et al. Jan 2009 A1
20090036753 King Feb 2009 A1
20090043240 Robinson et al. Feb 2009 A1
20090054753 Robinson et al. Feb 2009 A1
20090069743 Krishnamoorthy et al. Mar 2009 A1
20090069745 Estes et al. Mar 2009 A1
20090069787 Estes et al. Mar 2009 A1
20090099521 Gravesen et al. Apr 2009 A1
20090105573 Malecha Apr 2009 A1
20090131861 Braig et al. May 2009 A1
20090156922 Goldberger et al. Jun 2009 A1
20090156924 Shariati et al. Jun 2009 A1
20090163781 Say et al. Jun 2009 A1
20090198350 Thiele Aug 2009 A1
20090221890 Saffer et al. Sep 2009 A1
20090228214 Say et al. Sep 2009 A1
20090318791 Kaastrup Dec 2009 A1
20090326343 Gable et al. Dec 2009 A1
20100057042 Hayter Mar 2010 A1
20100114026 Karratt et al. May 2010 A1
20100121170 Rule May 2010 A1
20100137784 Cefai et al. Jun 2010 A1
20100152658 Hanson et al. Jun 2010 A1
20100174228 Buckingham et al. Jul 2010 A1
20100211003 Sundar et al. Aug 2010 A1
20100228110 Tsoukalis Sep 2010 A1
20100262117 Magni et al. Oct 2010 A1
20100262434 Shaya Oct 2010 A1
20100295686 Sloan et al. Nov 2010 A1
20100298765 Budiman et al. Nov 2010 A1
20110021584 Berggren et al. Jan 2011 A1
20110028817 Jin et al. Feb 2011 A1
20110054390 Searle et al. Mar 2011 A1
20110054399 Chong et al. Mar 2011 A1
20110124996 Reinke et al. May 2011 A1
20110144586 Michaud et al. Jun 2011 A1
20110160652 Yodfat et al. Jun 2011 A1
20110178472 Cabiri Jul 2011 A1
20110190694 Lanier, Jr. et al. Aug 2011 A1
20110202005 Yodfat et al. Aug 2011 A1
20110218495 Remde Sep 2011 A1
20110230833 Landman et al. Sep 2011 A1
20110251509 Beyhan et al. Oct 2011 A1
20110313680 Doyle et al. Dec 2011 A1
20110316562 Cefai et al. Dec 2011 A1
20120003935 Lydon et al. Jan 2012 A1
20120010594 Holt et al. Jan 2012 A1
20120030393 Ganesh et al. Feb 2012 A1
20120053556 Lee Mar 2012 A1
20120078067 Kovatchev et al. Mar 2012 A1
20120078161 Masterson et al. Mar 2012 A1
20120078181 Smith et al. Mar 2012 A1
20120101451 Boit et al. Apr 2012 A1
20120123234 Atlas et al. May 2012 A1
20120136336 Mastrototaro et al. May 2012 A1
20120190955 Rao et al. Jul 2012 A1
20120203085 Rebec Aug 2012 A1
20120203178 Tverskoy Aug 2012 A1
20120215087 Cobelli et al. Aug 2012 A1
20120225134 Komorowski Sep 2012 A1
20120226259 Yodfat et al. Sep 2012 A1
20120232520 Sloan et al. Sep 2012 A1
20120238851 Kamen et al. Sep 2012 A1
20120271655 Knobel et al. Oct 2012 A1
20120277668 Chawla Nov 2012 A1
20120282111 Nip et al. Nov 2012 A1
20120295550 Ison et al. Nov 2012 A1
20130030358 Yodat et al. Jan 2013 A1
20130158503 Kanderian, Jr. et al. Jun 2013 A1
20130178791 Javitt Jul 2013 A1
20130231642 Doyle et al. Sep 2013 A1
20130253472 Cabiri Sep 2013 A1
20130261406 Rebec et al. Oct 2013 A1
20130296823 Melker et al. Nov 2013 A1
20130317753 Kamen et al. Nov 2013 A1
20130338576 OConnor et al. Dec 2013 A1
20140005633 Finan Jan 2014 A1
20140200426 Taub et al. Jan 2014 A1
20140066886 Roy et al. Mar 2014 A1
20140074033 Sonderegger et al. Mar 2014 A1
20140121635 Hayter May 2014 A1
20140128839 Dilanni et al. May 2014 A1
20140135880 Baumgartner et al. May 2014 A1
20140146202 Boss et al. May 2014 A1
20140180203 Budiman et al. Jun 2014 A1
20140180240 Finan et al. Jun 2014 A1
20140200559 Doyle et al. Jul 2014 A1
20140230021 Birthwhistle et al. Aug 2014 A1
20140276554 Finan et al. Sep 2014 A1
20140276556 Saint et al. Sep 2014 A1
20140278123 Prodhom et al. Sep 2014 A1
20140309615 Mazlish Oct 2014 A1
20140316379 Sonderegger et al. Oct 2014 A1
20140325065 Birtwhistle et al. Oct 2014 A1
20150018633 Kovachev et al. Jan 2015 A1
20150025329 Amarasingham et al. Jan 2015 A1
20150025495 Peyser Jan 2015 A1
20150120317 Mayou et al. Apr 2015 A1
20150134265 Kohlbrecher et al. May 2015 A1
20150165119 Palerm et al. Jun 2015 A1
20150173674 Hayes et al. Jun 2015 A1
20150213217 Amarasingham et al. Jul 2015 A1
20150217052 Keenan et al. Aug 2015 A1
20150217053 Booth et al. Aug 2015 A1
20150265767 Vazquez et al. Sep 2015 A1
20150306314 Doyle et al. Oct 2015 A1
20150351671 Vanslyke et al. Dec 2015 A1
20150366945 Greene Dec 2015 A1
20160015891 Papiorek Jan 2016 A1
20160038673 Morales Feb 2016 A1
20160038689 Lee et al. Feb 2016 A1
20160051749 Istoc Feb 2016 A1
20160082187 Schaible et al. Mar 2016 A1
20160089494 Guerrini Mar 2016 A1
20160175520 Palerm et al. Jun 2016 A1
20160228641 Gescheit et al. Aug 2016 A1
20160243318 Despa et al. Aug 2016 A1
20160256087 Doyle et al. Sep 2016 A1
20160287512 Cooper et al. Oct 2016 A1
20160302054 Kimura et al. Oct 2016 A1
20160331310 Kovatchev Nov 2016 A1
20160354543 Cinar et al. Dec 2016 A1
20170049386 Abraham et al. Feb 2017 A1
20170143899 Gondhalekar et al. May 2017 A1
20170143900 Rioux et al. May 2017 A1
20170156682 Doyle et al. Jun 2017 A1
20170173261 O'Connor et al. Jun 2017 A1
20170189625 Cirillo et al. Jul 2017 A1
20170203039 Desborough Jul 2017 A1
20170281877 Marlin et al. Oct 2017 A1
20170296746 Chen et al. Oct 2017 A1
20170311903 Davis et al. Nov 2017 A1
20170348482 Duke et al. Dec 2017 A1
20180036495 Searle et al. Feb 2018 A1
20180040255 Freeman et al. Feb 2018 A1
20180075200 Davis et al. Mar 2018 A1
20180075201 Davis et al. Mar 2018 A1
20180075202 Davis et al. Mar 2018 A1
20180092576 O'Connor et al. Apr 2018 A1
20180126073 Wu et al. May 2018 A1
20180169334 Grosman et al. Jun 2018 A1
20180200434 Mazlish et al. Jul 2018 A1
20180200438 Mazlish et al. Jul 2018 A1
20180200441 Desborough et al. Jul 2018 A1
20180204636 Edwards et al. Jul 2018 A1
20180277253 Gondhalekar et al. Sep 2018 A1
20180289891 Finan et al. Oct 2018 A1
20180296757 Finan et al. Oct 2018 A1
20180342317 Skirble et al. Nov 2018 A1
20180369479 Hayter et al. Dec 2018 A1
20190076600 Grosman et al. Mar 2019 A1
20190143031 Admani May 2019 A1
20190240403 Palerm et al. Aug 2019 A1
20190290844 Monirabbasi et al. Sep 2019 A1
20190336683 O'Connor et al. Nov 2019 A1
20190336684 O'Connor et al. Nov 2019 A1
20190348157 Booth et al. Nov 2019 A1
20200046268 Patek et al. Feb 2020 A1
20200101222 Lintereur et al. Apr 2020 A1
20200101223 Lintereur et al. Apr 2020 A1
20200101225 O'Connor et al. Apr 2020 A1
20200219625 Kahlbaugh Jul 2020 A1
20200342974 Chen et al. Oct 2020 A1
20210050085 Hayter et al. Feb 2021 A1
20210098105 Lee et al. Apr 2021 A1
20220023536 Graham et al. Jan 2022 A1
Foreign Referenced Citations (105)
Number Date Country
2015200834 Mar 2015 AU
2015301146 Mar 2017 AU
2859561 Jun 2013 CA
1297140 May 2001 CN
19756872 Jul 1999 DE
0341049 Nov 1989 EP
0496305 Jul 1992 EP
0549341 Jun 1993 EP
1491144 Dec 2004 EP
0801578 Jul 2006 EP
2139382 Jan 2010 EP
2397181 Dec 2011 EP
2666520 Nov 2013 EP
2695573 Feb 2014 EP
2830499 Feb 2015 EP
2943149 Nov 2015 EP
3177344 Jun 2017 EP
3314548 May 2018 EP
1571582 Apr 2019 EP
2897071 May 2019 EP
3607985 Feb 2020 EP
2443261 Apr 2008 GB
51125993 Nov 1976 JP
02131777 May 1990 JP
2004283378 Oct 2007 JP
2017525451 Sep 2017 JP
2018153569 Oct 2018 JP
2019525276 Sep 2019 JP
201820021 Apr 2019 TR
200740148 Oct 2007 TW
M452390 May 2013 TW
9800193 Jan 1998 WO
9956803 Nov 1999 WO
0030705 Jun 2000 WO
200032258 Jun 2000 WO
0172354 Oct 2001 WO
2002015954 Feb 2002 WO
2002043866 Jun 2002 WO
2002082990 Oct 2002 WO
2003016882 Feb 2003 WO
2003039362 May 2003 WO
2003045233 Jun 2003 WO
2004043250 May 2004 WO
2005110601 May 2004 WO
2004092715 Oct 2004 WO
2005051170 Jun 2005 WO
2005082436 Sep 2005 WO
2005113036 Dec 2005 WO
2006053007 May 2006 WO
2007064835 Jun 2007 WO
2007078937 Jul 2007 WO
2008024810 Feb 2008 WO
2008029403 Mar 2008 WO
2008133702 Nov 2008 WO
2009045462 Apr 2009 WO
2009049252 Apr 2009 WO
2009066287 May 2009 WO
2009066288 May 2009 WO
2009098648 Aug 2009 WO
2009134380 Nov 2009 WO
2010053702 May 2010 WO
2010132077 Nov 2010 WO
2010138848 Dec 2010 WO
2010147659 Dec 2010 WO
2011095483 Aug 2011 WO
2012045667 Apr 2012 WO
2012108959 Aug 2012 WO
2012134588 Oct 2012 WO
2012177353 Dec 2012 WO
2012178134 Dec 2012 WO
2013078200 May 2013 WO
2013134486 Sep 2013 WO
20130149186 Oct 2013 WO
2013177565 Nov 2013 WO
2013182321 Dec 2013 WO
2014109898 Jul 2014 WO
2014110538 Jul 2014 WO
2014194183 Dec 2014 WO
2015056259 Apr 2015 WO
2015061493 Apr 2015 WO
2015073211 May 2015 WO
2015081337 Jun 2015 WO
2015187366 Dec 2015 WO
2016004088 Jan 2016 WO
2016022650 Feb 2016 WO
2016041873 Mar 2016 WO
2016089702 Jun 2016 WO
2016141082 Sep 2016 WO
2016161254 Oct 2016 WO
2017004278 Jan 2017 WO
2017091624 Jun 2017 WO
2017105600 Jun 2017 WO
2017184988 Oct 2017 WO
2017205816 Nov 2017 WO
2018009614 Jan 2018 WO
2018067748 Apr 2018 WO
2018120104 Jul 2018 WO
2018136799 Jul 2018 WO
2018204568 Nov 2018 WO
2019077482 Apr 2019 WO
2019094440 May 2019 WO
2019213493 Nov 2019 WO
2019246381 Dec 2019 WO
2020081393 Apr 2020 WO
2021011738 Jan 2021 WO
Non-Patent Literature Citations (106)
Entry
US 5,954,699 A, 09/1999, Jost et al. (withdrawn)
Translation of TR201820021 (Year: 2019).
International Search Report and Written Opinion for the International Patent Application No. PCT/US2020/052125, dated Aug. 12, 2020, 15 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2020/050332, dated Sep. 12, 2020, 12 pages.
European Patent Office, “Notification of Transmittal of the ISR and the Written Opinion of the International Searching Authority, or the Declaration,” in PCT Application No. PCT/GB2015/050248, dated Jun. 23, 2015, 12 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/012246, dated Apr. 13, 2021, 15 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/013639, dated Apr. 28, 2021, 14 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2020/063326, dated May 3, 2021, 17 pages.
European Search Report for the European Patent Application No. 21168591, dated Oct. 13, 2021, 4 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/041954, dated Oct. 25, 2021, 13 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/022694, dated Jun. 25, 2021, 13 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/017664, dated May 26, 2021, 16 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2022/012896, dated Apr. 22, 2022, 15 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2022/013470, dated May 6, 2022, 14 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2022/013473, dated May 6, 2022, 13 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2022/019079, dated Jun. 2, 2022, 14 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2022/018453, dated Jun. 2, 2022, 13 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US22/018700, dated Jun. 7, 2022, 13 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US22/019080, dated Jun. 7, 2022, 14 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US22/019664, dated Jun. 7, 2022, 14 pages.
International Search Report and Written Opinion for International Patent Application No. PCT/US2021/051027, dated Jan. 7, 2022, 16 pages.
International Search Report and Written Opinion for International Patent Application No. PCT/US2021/052372, dated Jan. 26, 2022,15 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/046607, dated Jan. 31, 2022, 20 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/055745, dated Feb. 14, 2022, 13 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US21/060618, dated Mar. 21, 2022, 15 pages.
Herrero Pau et al: “Enhancing automatic closed-loop glucose control in type 1 diabetes with an adaptive meal bolus calculator-in silicoevaluation under intra-day variability”, Computer Methods and Programs in Biomedicine, Elsevier, Amsterdam, NL, vol. 146, Jun. 1, 2017 (Jun. 1, 2017), pp. 125-131, XP085115607, ISSN: 0169-2607, DOI:10.1016/J.CMPB.2017.05.010.
Marie Aude Qemerais: “Preliminary Evaluation of a New Semi-Closed-Loop Insulin Therapy System over the prandial period in Adult Patients with type I diabetes: the WP6. 0 Diabeloop Study”, Journal of Diabetes Science and Technology Diabetes Technology Society Reprintsand permissions, Jan. 1, 2014, pp. 1177-1184, Retrieved from the Internet: URL:http://journals.sagepub.com/doi/pdf/10.1177/1932296814545668 [retrieved on Jun. 6, 2022] chapter “Functioning of the Algorithm” chapter “Statistical Analysis” p. 1183, left-hand column, line 16-line 23.
Anonymous: “Kernel density estimation”, Wikipedia, Nov. 13, 2020 (Nov. 13, 2020), pp. 1-12, XP055895569, Retrieved from the Internet: URL:https://en.wikipedia.org/w/index.php?title=Kernel_density_estimation&oldid=988508333 [retrieved on Jun. 6, 2022].
Anonymous: “openaps / oref0 /lib/determine-basal-js”, openaps repository, Nov. 9, 2019 (Nov. 9, 2019), pp. 1-17, XP055900283, Retrieved from the Internet: URL:https://github.com/openaps/oref0/blob/master/lib/determine-basal/determine-basal.js [retrieved on Jun. 6, 2022] line 116-line 118, line 439-line 446.
Anonymous: “AndroidAPS screens”, AndroidAPS documentation, Oct. 4, 2020 (Oct. 4, 2020), pp. 1-12, XP055894824, Retrieved from the Internet: URL:https://github.com/openaps/AndroidAPSdocs/blob/25d8acf8b28262b411b34f416f173ac0814d7e14/docs/EN/Getting-Started/Screenshots.md [retrieved on Jun. 6, 2022].
Kozak Milos et al: “Issue #2473 of AndroidAPS”, MilosKozak / AndroidAPS Public repository, Mar. 4, 2020 (Mar. 4, 2020), pp. 1-4, XP055900328, Retrieved from the Internet: URL:https://github.com/MilosKozak/AndroidAPS/issues/2473 [retrieved on Jun. 6, 2022].
International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/052855, dated Dec. 22, 2021, 11 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/047771, dated Dec. 22, 2021, 11 pages.
Medication Bar Code System Implementation Planning Section I: A Bar Code Primer for Leaders, Aug. 2013.
Medication Bar Code System Implementation Planning Section II: Building the Case for Automated Identification of Medications, Aug. 2013.
Villareal et al. (2009) in: Distr. Comp. Art. Intell. Bioninf. Soft Comp. Amb. Ass. Living; Int. Work Conf. Art. Neural Networks (IWANN) 2009, Leet. Notes Comp. Sci vol. 5518; S. Omatu et al. (Eds.), pp. 870-877.
Fox, Ian G.; Machine Learning for Physiological Time Series: Representing and Controlling Blood Glucose for Diabetes Management; University of Michigan. ProQuest Dissertations Publishing, 2020. 28240142. (Year: 2020).
Anonymous: “Artificial pancreas—Wikipedia”, Mar. 13, 2018 (Mar. 13, 2018), XP055603712, Retrieved from the Internet: URL: https://en.wikipedia.org/wiki/Artificial_pancreas [retrieved on Sep. 7, 2019] section “Medical Equipment” and the figure labeled “The medical equipment approach to an artifical pancreas”.
Kaveh et al., “Blood Glucose Regulation via Double Loop Higher Order Sliding Mode Control and Multiple Sampling Rate.” Paper presented at the proceedings of the 17th IFAC World Congress, Seoul, Korea (Jul. 2008).
Dassau et al., “Real-Time Hypoglycemia Prediction Suite Using Contineous Glucose Monitoring,” Diabetes Care, vol. 33, No. 6, 1249-1254 (2010).
International Search Report and Written Opinion for International Patent Application No. PCT/US17/53262, dated Dec. 13, 2017, 8 pages.
Van Heusden et al., “Control-Relevant Models for Glucose Control using A Priori Patient Characteristics”, IEEE Transactions on Biomedical Engineering, vol. 59, No. 7, (Jul. 1, 2012) pp. 1839-1849.
Doyle III et al., “Run-to-Run Control Strategy for Diabetes Management.” Paper presented at 23rd Annual International Conference of the IEEE Engineering in Medicine and Biology Society, Istanbul, Turkey (Oct. 2001).
Bequette, B.W., and Desemone, J., “Intelligent Dosing Systems”: Need for Design and Analysis Based on Control Theory, Diabetes Technology and Therapeutics 9(6): 868-873 (2004).
Parker et al., “A Model-Based Agorithm for Blood Gucose Control in Type 1 Diabetic Patients.” IEEE Transactions on Biomedical Engineering, 46 (2) 148-147 (1999).
International Search Report and Written Opinion for International Patent Application No. PCT/US2017/015601, dated May 16, 2017, 12 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2018/018901, dated Aug. 6, 2018,12 pages.
International Search Report and Written Opinion for International Patent Application No. PCT/US2018/052467, dated Jan. 4, 2019, 13 pages.
“How to Create a QR Code that Deep Links to Your Mobile App”, Pure Oxygen Labs, web<https://pureoxygenlabs.com/how-to-create-a-qr-codes-that-deep-link-to-your-mobile-app/>. Year:2017.
“Read NFC Tags with an iPHone App on iOS 11”, GoToTags, Sep. 11, 2017, web <https://gototags.com/blog/read-nfc-tags-with-an-iphone-app-on-ios-11/>. (Year:2017).
International Search Report and Written Opinion for International Patent Application No. PCT/US2016/063350, dated Mar. 27, 2017, 9 pages.
Extended Search Report dated Aug. 13, 2018, issued in European Patent Application No. 16753053.4, 9 pages.
International Search Report and Written Opinion for International Patent Application No. PCT/US16/18452, dated Apr. 29, 2015, 9 pages.
International Preliminary Report on Patentability dated Aug. 31, 2017, issued in PCT Patent Application No. PCT/US2016/018452, 7 pages.
International Search Report and Written Opinion for International Patent Application No. PCT/US2019/055862, dated Mar. 11, 2020.
International Search Report and Written Opinion for Application No. PCT/US2019/030562, dated Sep. 25, 2019, 19 pages.
Unger, Jeff, et al., “Glucose Control in the Hospitalized Patient,” Emerg. Med 36(9):12-18 (2004).
“Glucommander FAQ” downloaded from https://adaendo.com/GlucommanderFAQ.html on Mar. 16, 2009.
Finfer, Simon & Heritier, Stephane. (2009). The NICE-SUGAR (Normoglycaemia in Intensive Care Evaluation and Survival Using Glucose Algorithm Regulation) Study: statistical analysis plan. Critical care and resuscitation : journal of the Australasian Academy of Critical Care Medicine. 11. 46-57.
Letters to the Editor regarding “Glucose Control in Critically III Patients,” N Engl J Med 361: 1, Jul. 2, 2009.
“Medtronic is Leading a Highly Attractive Growth Market,” Jun. 2, 2009.
Davidson, Paul C., et al. “Glucommander: An Adaptive, Computer-Directed System for IV Insulin Shown to be Safe, Simple, and Effective in 120,618 Hours of Operation,” Atlanta Diabetes Associates presentation.
Davidson, Paul C., et al. “Pumpmaster and Glucommander,” presented at the MiniMed Symposium, Atlanta GA, Dec. 13, 2003.
Kanji S., et al. “Reliability of point-of-care testing for glucose measurement in critically ill adults,” Critical Care Med, vol. 33, No. 12, pp. 2778-2785, 2005.
Krinsley James S., “Severe hypoglycemia in critically ill patients: Risk factors and outcomes,” Critical Care Med, vol. 35, No. 10, pp. 1-6, 2007.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/016283, dated Jun. 2, 2021, 15 pages.
Farkas et al. “Single-Versus Triple-Lumen Central Catheter-Related Sepsis: A Prospective Randomized Study in a Critically III Population” The American Journal of Medicine, Sep. 1992, vol. 93, p. 277-282.
Davidson, Paul C., et al., A computer-directed intravenous insulin system shown to be safe, simple,and effective in 120,618 h of operation, Diabetes Care, vol. 28, No. 10, Oct. 2005, pp. 2418-2423.
R Anthony Shaw, et al., “Infrared Spectroscopy in Clinical and Dianostic Analysis,” Encyclopedia of Analytical Chemistry, ed. Robert A. Meyers, John Wiley & Sons, Ltd., pp. 1-20, 2006.
Gorke, A “Microbial Contamination Of Haemodialysis Catheter Connections” Journal of Renal Care, European Dialysis & Transplant Nurses Association.
Lovich et al. “Central venous catheter infusions: A laboratory model shows large differences in drug delivery dynamics related to catheter dead volume” Critical Care Med 2007 vol. 35, No. 12.
Van Den Berghe, Greet, M.D., Ph.D., et al., Intensive Insulin Therapy in Critically III Patients, The New England Journal of Medicine, vol. 345, No. 19, Nov. 8, 2001, pp. 1359-1367.
Schlegel et al., “Multilumen Central Venous Catheters Increase Risk for Catheter-Related Bloodstream Infection: Prospective Surveillance Study” Infection 2008; 36: 322-327.
Wilson, George S., et al., Progress toward the Development of an Implantable Sensor for Glucose, Clin. Chem., vol. 38, No. 9, 1992, pp. 1613-1617.
Yeung et al. “Infection Rate for Single Lumen v Triple Lumen Subclavian Catheters” Infection Control and Hospital Epidemiology, vol. 9, No. 4 (Apr. 1988) pp. 154-158 The University of Chicago Press.
International Search Report and Written Opinion, International Application No. PCT/US2010/033794 dated Jul. 16, 2010 (OPTIS.247VPC).
International Search Report and Written Opinion in PCT/US2008/079641 (Optis.203VPC) dated Feb. 25, 2009.
Berger, “Measurement of Analytes in Human Serum and Whole Blood Samples by Near-Infrared Raman Spectroscopy,” Ph.D. Thesis, Massachusetts Institute of Technology, Chapter 4, pp. 50-73, 1998.
Berger, “An Enhanced Algorithm for Linear Multivariate Calibration,” Analytical Chemistry, vol. 70, No. 3, pp. 323-627, Feb. 1, 1998.
Billman et al.,“Clinical Performance of an In line Ex-Vivo Point of Care Monitor: A Multicenter Study,” Clinical Chemistry 48: 11, pp. 2030-2043, 2002.
Widness et al., “Clinical Performance on an In-Line Point-of-Care Monitor in Neonates”; Pediatrics, vol. 106, No. 3, pp. 497-504, Sep. 2000.
Finkielman et al., “Agreement Between Bedside Blood and Plasma Glucose Measurement in the ICU Setting”; retrieved from http://www.chestjournal.org; CHEST/127/5/May 2005.
Glucon Critical Care Blood Glucose Monitor; Glucon; retrieved on Dec. 29, 2010 from http://www.glucon.com.
Fogt, et al., “Development and Evaluation of a Glucose Analyzer for a Glucose-Controlled Insulin Infusion System (Biostator)”; Clinical Chemistry, vol. 24, No. 8, pp. 1366-1372, 1978.
Vonach et al., “Application of Mid-Infrared Transmission Spectrometry to the Direct Determination of Glucose in Whole Blood,” Applied Spectroscopy, vol. 52, No. 6, 1998, pp. 820-822.
Muniyappa et al., “Current Approaches for assessing insulin sensitivity and resistance in vivo: advantages, limitations, and appropriate usage,” AJP-Endocrinol Metab, vol. 294, E15-E26, first published Oct. 23, 2007.
International Preliminary Report on Patentability for the International Patent Application No. PCT/US2019/053603, dated Apr. 8, 2021, 9 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2019/053603, dated Jan. 7, 2020, 16 pages.
Dassau et al., “Detection of a meal using continuous glucose monitoring: Implications for an artificial [beta]-cell.” Diabetes Care, American Diabetes Association, Alexandria, VA, US, 31(2):295-300 (2008).
Cameron et al., “Probabilistic Evolving Meal Detection and Estimation of Meal Total Glucose Appearance Author Affiliations”, J Diabetes Sci and Tech,vol., Diabetes Technology Society ;(5):1022-1030 (2009).
Lee et al., “A closed-loop artificial pancreas based on model predictive control: Human-friendly identification and automatic meal disturbance rejection”, Biomedical Signal Processing and Control, Elsevier, Amsterdam, NL, 4(4):1746-8094 (2009).
Anonymous: “Fuzzy control system”, Wikipedia, Jan. 10, 2020. URL: https://en.wikipedia.org/w/index.php?title=Fuzzy_control_system&oldid=935091190.
An Emilia Fushimi: “Artificial Pancreas: Evaluating the ARG Algorithm Without Meal Annoucement”, Journal of Diabetes Science and Technology Diabetes Technology Society, Mar. 22, 2019, pp. 1025-1043.
International Search Report and Written Opinion for the IntemationalPatent Application No. PCT/US2021/017441, dated May 25, 2021, 12 pages.
Mirko Messori et al: “Individualized model predictive control for the artificial pancreas: In silico evaluation of closed-loop glucose control”, IEEE Control Systems, vol. 38, No. 1, Feb. 1, 2018, pp. 86-104.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/017662, dated May 26, 2021, 14 pages.
Anonymous: “Reservoir Best Practice and Top Tips” Feb. 7, 2016, URL: https://www.medtronic-diabetes.co.uk/blog/reservoir-best-practice-and-top-tips, p. 1.
Gildon Bradford: “InPen Smart Insulin Pen System: Product Review and User Experience” Diabetes Spectrum, vol. 31, No. 4, Nov. 15, 2018, pp. 354-358.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/016050, dated May 27, 2021, 16 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2020/065226, dated May 31, 2021, 18 pages.
International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/017659, dated May 31, 2021, 13 pages.
Montaser Eslam et al., “Seasonal Local Models for Glucose Prediction in Type 1 Diabetes”, IEE Journal of Biomedical and Health Informatics, IEEE, Piscataway, NJ, USA, vol. 24, No. 7, Nov. 29, 2019, pp. 2064-2072.
Samadi Sediqeh et al., “Automatic Detection and Estimation of Unannouced Meals for Multivariable Artificial Pancreas System”, Diabetis Technology & Therapeutics, vol. 20m No. 3, Mar. 1, 2018, pp. 235-246.
Samadi Sediqeh et al., “Meal Detection and Carbohydrate Estimation Using Continuous Glucose Sensor Data” IEEE Journal of Biomedical and Health Informatics, IEEE, Piscataway, NJ, USA, vol. 21, No. 3, May 1, 2017, pp. 619-627.
Khodaei et al., “Physiological Closed-Loop Contol (PCLC) Systems: Review of a Modern Frontier in Automation”, IEEE Access, IEEE, USA, vol. 8, Jan. 20, 2020, pp. 23965-24005.
E. Atlas et al., “MD-Logic Artificial Pancreas System: A pilot study in adults with type 1 diabetes”, Diabetes Care, vol. 33, No. 5, Feb. 11, 2010, pp. 1071-1076.
Related Publications (1)
Number Date Country
20230095302 A1 Mar 2023 US
Provisional Applications (1)
Number Date Country
63248844 Sep 2021 US