Patent Grant
10603433
This document relates to an infusion pump system, such as a portable infusion pump system for dispensing insulin or another medicine.
Pump devices are commonly used to deliver one or more fluids to a targeted individual. For example, a medical infusion pump device may be used to deliver a medicine to a patient as part of a medical treatment. The medicine that is delivered by the infusion pump device can depend on the condition of the patient and the desired treatment plan. For example, infusion pump devices have been used to deliver insulin to the vasculature of diabetes patients so as to regulate blood-glucose levels.
Infusion pump devices often seek to deliver medicine in accurately controlled dosages. Over-dosages and under-dosages of medicine can be detrimental to patients. For example, an infusion pump device that delivers an over-dosage or under-dosage of insulin to a diabetes patient can significantly affect the blood-glucose level of the patient.
Some insulin pump devices may control the dispensation of insulin using a closed-loop controller in which the insulin dispensation is automatically adjusted in response to sensor feedback indicative of a user's blood glucose level. For example, these pump devices that operate using a closed-loop controller would subsequently increase the insulin dispensation after detecting a rise in a user's blood glucose level (e.g., after the user has consumed a meal). Some of these closed-loop insulin pump devices purport to act as an “artificial pancreas” in which no user input is prompted when the controller adjusts the insulin dispensation.
Some embodiments of an infusion pump system described herein can be configured to control the dispensation of medicine (e.g., insulin) according to an interruptible closed-loop delivery mode. During the closed-loop delivery mode, the infusion pump system may autonomously dispense medication to the user based on a sensed physiological state. For example, the infusion pump system may dispense insulin to a user in response to the user's blood glucose level while operating in a closed-loop delivery mode. In some embodiments, the closed-loop delivery mode may be temporarily interrupted to accommodate a user-prompted bolus dosage. For example, the user may elect to manually enter a specific bolus dosage or to initiate the calculation of a suggested bolus dosage by accessing a user interface of the infusion pump system. Optionally, the infusion pump system is configured to perform one or more dosage calculations for purposes of providing the user-prompted bolus dosage. Such a bolus dosage calculation may account for medication dispensed during operations in the closed-loop delivery mode over a predetermined time period immediately prior to the calculation. Thus, in some embodiments, the infusion pump system is configured to calculate the amount of effective insulin-on-board (eIOB), which corresponds to the net amount of remaining active insulin in the user's system from dosages during the predetermined time period.
Particular embodiments described herein include a method of operating a portable insulin infusion pump system. The method may include detecting a trigger event to initiate a user-selected manual bolus dosage while operating an infusion pump system to dispense insulin according to a closed-loop delivery mode. The method may further include temporarily interrupting the closed-loop delivery mode by dispensing from the infusion pump system the user-selected manual bolus dosage. Also, the method may include automatically returning to the closed-loop delivery mode after dispensation of the user-selected manual bolus dosage. A calculated dosage amount of the user-selected manual bolus dosage may be calculated by the infusion pump system based upon at least both user input of a particular value(s) and a calculated amount of insulin previously dispensed during the closed-loop delivery mode over a time period immediately prior to interruption of the closed-loop delivery mode.
In some embodiments, a method of operating a portable insulin infusion pump system may include detecting a trigger event to initiate a user-selected manual bolus dosage while operating an infusion pump system to dispense insulin according to a closed-loop delivery mode. The method may also include determining, at the infusion pump system, that the user-selected manual bolus dosage is permissible based on (at least) an amount of the bolus dosage and a calculated amount of insulin previously dispensed during the closed-loop delivery mode over a time period immediately prior to the trigger event. The method may further include initiating delivery of the permissible bolus dosage.
In certain embodiments, a method of operating a portable insulin infusion pump system may include detecting a trigger event to initiate a user-selected manual bolus dosage while operating an infusion pump system to dispense insulin according to a closed-loop delivery mode in which insulin is dispensed in response to feedback information of a user's blood glucose characteristic. Optionally, the method may further include temporarily interrupting the closed-loop delivery mode by dispensing from the infusion pump system the user-selected manual bolus dosage. Also, the method may include automatically returning to the closed-loop delivery mode after dispensation of the user-selected manual bolus dosage.
According to one or more embodiments, the closed-loop delivery mode causes the infusion pump system to dispense insulin in response to feedback information of a user's blood glucose level, and the trigger event includes actuation of a user interface button indicating a user's request to manually initiate a bolus dispensation that is independent from the feedback information of the user's blood glucose characteristic. According to one or more embodiments, the user-selected manual bolus dosage is dispensed independently of the feedback information of the user's blood glucose characteristic.
According to one or more embodiments, the trigger event includes actuation of a user interface button indicating a user's request to initiate calculation of a suggested bolus dosage by the infusion pump system.
According to one or more embodiments, the infusion pump system includes a controller, which may optionally comprise a user interface display device and control circuitry arranged in a controller housing and being programmed to perform the calculation of the manual bolus dosage. According to one or more embodiments, the infusion pump system may also include a pump device, which may optionally comprise a pump housing that houses a drive system and a space to receive a medicine (e.g., insulin in particular implementations). Also, in some embodiments, the controller housing may be removably mountable to the pump housing so that the controller is electrically connected to components of the pump device (e.g., the drive system, other components, or a combination thereof).
According to one or more embodiments, the amount of insulin dispensed during the closed-loop delivery mode over the time period includes an effective-insulin-on-board amount calculated as follows:
Effective Insulin-on-Board=[Σ(Dosagen*Duration Factor(t)n)]−Estimated Basal Rate,
Particular embodiments described herein include a medical infusion pump system, which may be (optionally) configured as a wearable pump system to dispense insulin or another medicine to a user. The system may include a portable pump housing configured to receive medicine for dispensation to a user. The pump housing may at least partially contain a pump drive system to dispense the medicine through a flow path to the user. The system may also include a controller that controls the pump drive system to dispense the medicine from the portable pump housing according to a closed-loop delivery mode in which, for example, the controller autonomously provides insulin dosages to the user in response to feedback information of a user's blood glucose level. The controller may be configured to, in response to receiving input indicative of a user-prompted bolus dosage, temporarily interrupt the closed-loop delivery mode by dispensing from the infusion pump system the user-prompted bolus dosage. The calculated dosage amount of the user-prompted bolus dosage is calculated by the infusion pump system based upon both user input of a particular value(s) and a calculated amount of insulin previously dispensed during the closed-loop delivery mode over a predetermined time period prior to the user-prompted bolus dosage.
According to one or more embodiments, the input indicative of the user-prompted bolus dosage includes actuation of a user interface button indicating a user request to manually enter a bolus dosage amount.
According to one or more embodiments, the input indicative of the user-prompted bolus dosage includes actuation of a user interface button indicating a user request to initiate a calculation, by the infusion pump system, of a suggested bolus dosage.
According to one or more embodiments, the controller includes a user interface including a display device and a plurality of buttons. According to one or more embodiments, the controller includes a controller housing that removably attaches to the pump housing. According to one or more embodiments, the controller is electrically connected to the pump drive system when the controller housing is removably attached to the pump housing. According to one or more embodiments, the controller is a reusable device and the pump housing and pump drive system are disposable and nonreusable (e.g., one or more structural components of the pump device that hinder reuse of the pump device after exhaustion of the medicine supply in the pump device).
According to one or more embodiments, the system further includes a monitoring device that communicates glucose information to the controller, the glucose information being indicative of a blood glucose level of the user.
Certain embodiments described herein include a portable infusion pump system, which may include a portable pump housing that defines a space to receive medicine for dispensation to a user. The pump housing may at least partially house a pump drive system to dispense the medicine through a flow path to the user. The system may also include control circuitry that controls the pump drive system to dispense the medicine from the portable pump housing according to a closed-loop delivery mode in which insulin is dispensed, for example, at differing rates in response to feedback information of a user's blood glucose characteristic. The system may further include a user interface in communication with the control circuitry and being configured to receive user input to interrupt the closed-loop delivery mode. The control circuitry may be configured to temporarily interrupt the closed-loop delivery mode by dispensing from the infusion pump system a user-selected manual bolus dosage. Optionally, the control circuitry may be configured to automatically restart the closed-loop delivery mode after dispensation of the user-selected manual bolus dosage (or may be configured to automatically prompt the user to confirm (via a user interface display) the restarting the closed-loop delivery mode after dispensation of the user-selected manual bolus dosage).
Some or all of the embodiments described herein may provide one or more of the following advantages. First, some embodiments of the infusion pump system described herein can include a portable design that is configured to be conveniently worn by user (e.g., on the user's skin or in a pocket) while operating in closed-loop delivery mode so as to automatically adjust insulin dispensation to a user in response to the user's blood glucose level (or other physiological state).
Second, some embodiments of the infusion pump system may dispense insulin to a user in response to the user's blood glucose level while operating in a closed-loop delivery mode, yet the user can conveniently interrupt the closed-loop delivery mode for purposes of demanding manually-initiated bolus dosage. Such interruption of the closed-loop delivery mode may be a temporary interruption, for example, when the controller is configured to automatically return to the closed loop delivery mode after dispensation of the manually-initiated bolus dosage (without intervention from the user). Accordingly, the user can wear the infusion pump system that operates according to the closed-loop delivery mode throughout the day, but the user can briefly interrupt the closed-loop delivery mode to manually initiate a “meal bolus” (or other type of bolus) prior to consuming a meal. For example, the user may elect to manually enter a specific bolus dosage or to initiate the calculation of a suggested bolus dosage based upon user input of an estimated number of carbohydrates to be consumed. Because the user can manually initiate the user-prompted bolus dosage prior to consuming the meal (e.g., before the user's blood glucose level rises due to consuming the food), the user may not experience a significant rise in his or her blood glucose level that might otherwise occur if operating under closed-loop control. After the manually-initiated bolus dosage is dispensed to the user, the infusion pump system can be configured to automatically return to the closed-loop delivery mode.
Fourth, in some embodiments described herein, the infusion pump system can be configured to calculate a dosage amount for the manually-initiated bolus dosage that accounts not only for the user input (e.g., of an estimated number of carbohydrates or other parameters), but also accounts for the insulin that was previously dispensed (during the closed-loop delivery mode) but has not yet acted in the user's body. For example, the infusion pump system can determine a calculated dosage amount for the manually-initiated bolus dosage based upon both user input and an amount of insulin dispensed during the closed-loop delivery mode over a time period prior to the user-prompted bolus dosage. In doing so, some implementations of the infusion pump system may calculate the eIOB, which corresponds to the net amount of remaining active insulin in the user's system from dosages during the predetermined time period (e.g., including the various insulin dispensations that occurred during the closed-loop delivery mode).
Fifth, some embodiments of the infusion pump system may provide an additional level of safety to prevent an overdose of medicine resulting from a manually-initiated bolus dosage that interrupts a closed-loop delivery mode. For example, the infusion pump system may be configured to calculate a stacking value in response to receipt of a manually entered bolus dosage requested by the user. The stacking value may represent the amount of insulin that would be active in the user's body if the requested dosage were dispensed. If the stacking value exceeds a predetermined stacking threshold, the infusion pump system may attempt to prevent an overdose of the insulin by one or more of the following operations: alerting the user to the amount of eIOB, preventing dispensation of the requested dosage, and prompting the user to select a corrected dosage. The stacking value may be calculated by aggregating the requested bolus dosage with the eIOB.
Similarly, in some embodiments, the amount of eIOB can be accounted for in the calculation of a suggested bolus dosage prompted by the user. As another example, the infusion pump system may be configured to calculate a predicted future blood glucose level in response to receipt of a manually entered bolus dosage requested by the user. The future blood glucose level may represent a blood glucose level that is predicted to occur in the user's body as a result of the requested bolus dosage. If future blood glucose level falls below a predetermined minimum blood glucose level (e.g., a blood glucose level below which the user is likely to suffer symptoms of hypoglycemia, such as about 60 to 70 mg/dL in some cases), the infusion pump system may attempt to prevent an overdose of the insulin by one or more of the above-recited operations. The future blood glucose level may be calculated as the product of the stacking value and the user's insulin sensitivity.
Sixth, some embodiments of the infusion pump system can facilitate the controlled dispensation of both insulin and glucagon. For example, the infusion pump system may provide a suggested glucagon dosage based on one or more particular parameters (e.g., the user's recent blood glucose characteristics, food intake data, an amount of insulin and/or glucagon already delivered to the user which has not yet acted on the user, glucagon sensitivity of the user, and the like). The suggested glucagon dosage may be dispensed directly from the infusion pump device or manually injected via a suitable applicator (e.g., an injection pen). In some circumstances, a controller device of the infusion pump system can receive information indicative of the user's blood glucose level and suggest a glucagon dosage that is at least partially dependent upon a stored glucagon sensitivity value that is predetermined for the user. Such a glucagon dosage suggestion feature can be initiated, for example, by the infusion pump system in response to input of a blood glucose level that is below a target level, or in response to a predicted future low glucose event. In some implementations, the controller device may interrupt a closed-loop delivery mode to provide the suggested glucagon dosage, or, alternatively, facilitate the glucagon dosage “on top” of the closed-loop operations.
The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.
Like reference symbols in the various drawings may indicate like elements.
Referring to
Briefly, in use, the pump device 100 in this embodiment is configured to removably attach to the controller device 200 in a manner that provides a secure fitting, an overall compact size, and a reliable electrical connection. For example, as described in more detail below in connection with
Still referring to
Furthermore, it should be understood that in some alternative embodiments, the monitoring device 50 can be in communication with the controller device 200 via a wired connection. In other embodiments of the infusion pump system 1, one or more test strips (e.g., blood test strips) containing a sample of the user's blood can be inserted into a strip reader portion of the pump system 1 to be tested for characteristics of the user's blood. Alternatively, the test strips (e.g., glucose test strips) containing a sample of the user's blood can be inserted into a glucose meter device (not shown in
Referring now to
The pump assembly 10 can be a medical infusion pump assembly that is configured to controllably dispense a medicine from the cartridge 120. As such, the fluid cartridge 120 can contain a medicine 126 to be infused into the tissue or vasculature of a targeted individual, such as a human or animal patient. For example, the pump device 100 can be adapted to receive a fluid cartridge 120 in the form of a carpule that is preloaded with insulin or another medicine for use in the treatment of Diabetes (e.g., Byetta®, Symlin®, or others). Such a cartridge 120 may be supplied, for example, by Eli Lilly and Co. of Indianapolis, Ind. Other examples of medicines that can be contained in the fluid cartridge 120 include: pain relief drugs, hormone therapy, blood pressure treatments, anti-emetics, osteoporosis treatments, or other injectable medicines. The fluid cartridge 120 may have other configurations. For example, the fluid cartridge 120 may comprise a reservoir that is integral with the pump housing structure 110 (e.g., the fluid cartridge 120 can be defined by one or more walls of the pump housing structure 110 that surround a plunger to define a reservoir in which the medicine is injected or otherwise received).
In some embodiments, the pump device 100 can include one or more structures that interfere with the removal of the fluid cartridge 120 after the fluid cartridge 120 is inserted into the cavity 116. For example, the pump housing structure 110 can include one or more retainer wings (not shown) that at least partially extend into the cavity 116 to engage a portion of the fluid cartridge 120 when the fluid cartridge 120 is installed therein. Such a configuration may facilitate the “one-time-use” feature of the pump device 100. In some embodiments, the retainer wings can interfere with attempts to remove the fluid cartridge 120 from the pump device 100, thus ensuring that the pump device 100 will be discarded along with the fluid cartridge 120 after the fluid cartridge 120 is emptied, expired, or otherwise exhausted. In another example, the cap device 130 can be configured to irreversibly attach to the pump body 110 so as to cover the opening of the cavity 116. For example, a head structure of the cap device 130 can be configured to turn so as to threadably engage the cap device 130 with a mating structure along an inner wall of the cavity 116, but the head structure may prevent the cap device from turning in the reverse direction so as to disengage the threads. Accordingly, the pump device 100 can operate in a tamper-resistant and safe manner because the pump device 100 can be designed with a predetermined life expectancy (e.g., the “one-time-use” feature in which the pump device is discarded after the fluid cartridge 120 is emptied, expired, or otherwise exhausted).
Still referring to
The controller device 200 can include a user interface 220 that permits a user to monitor and actively control the operation of the pump device 100. In some embodiments, the user interface 220 can include a display device 222 and one or more user-selectable buttons (e.g., several buttons 224 are shown in the embodiment of
The controller device 200 can also be equipped with an inspection light device 230. The inspection light device 230 can provide the user with a tool to illuminate and inspect a targeted location. For example, the inspection light device 230 can be directed at the infusion site on the user's skin to verify that the infusion set is properly embedded, or the inspection light device 230 can be directed at the pump device 100 to illuminate the cavity 116 or other areas. The inspection light device 230 can also be used to notify the user to an alert condition of the pump system 10. For example, as described in more detail below, the inspection light device 230 can be activated when the controller has detected a possible problem with the infusion set 146. An activation of the inspection light device 230 can thereby provide a visual notification (as an alternative to, or in addition to, the visual notification provided on the display device 222) to the user that attention to the pump system 10 is warranted.
The pump assembly 10 can be configured to be portable and can be wearable and concealable. For example, a user can conveniently wear the pump assembly 10 on the user's skin (e.g., skin adhesive) underneath the user's clothing or carry the pump device 100 in the user's pocket (or other portable location) while receiving the medicine dispensed from the pump device 100. The pump assembly 10 is depicted in
In some embodiments, the pump assembly 10 can be pocket-sized so that the pump device 100 and controller device 200 can be worn in the user's pocket or in another portion of the user's clothing. In some circumstances, the user may desire to wear the pump assembly 10 in a more discrete manner. Accordingly, the user can pass the tube 147 from the pocket, under the user's clothing, and to the infusion site where the adhesive patch can be positioned. As such, the pump assembly 10 can be used to deliver medicine to the tissues or vasculature of the user in a portable, concealable, and discrete manner.
In some embodiments, the pump assembly 10 can be configured to adhere to the user's skin directly at the location in which the skin is penetrated for medicine infusion. For example, a rear surface of the pump device 100 can include a skin adhesive patch so that the pump device 100 can be physically adhered to the skin of the user at a particular location. In these embodiments, the cap device 130 can have a configuration in which medicine passes directly from the cap device 130 into an infusion cannula 149 that is penetrated into the user's skin. In some examples, the user can temporarily detach the controller device 200 (while the pump device 100 remains adhered to the skin) so as to view and interact with the user interface 220.
Referring now to
The control circuitry 240 of the controller device 200 can include one or more microprocessors 241 configured to execute computer-readable instructions stored on one or more memory devices 242 so as to achieve any of the control operations described herein. For example, at least on memory device 242 of the control circuitry 240 may be configured to store computer-readable instructions for operating the pump device 100 according to a closed-loop delivery mode and an open-loop delivery mode.
In the closed-loop delivery mode, the control circuitry 240 of the controller device 200 can operate the pump device 100 to autonomously alter the dispensation of insulin to a user based upon a sensed physiological condition of the user. For example, if the infusion pump system is dispensing insulin, closed-loop operations facilitated by the control circuitry may cause the infusion pump system to imitate a pancreatic beta cell so that the insulin dispensation is adjusted according to increases or decreases in the user's blood glucose level (see
Additionally, as described herein, even when the controller device 200 is operating in the closed-loop delivery mode, the user can choose to temporarily interrupt the closed-loop delivery mode for purposes of demanding manually-initiated bolus dosage. In such circumstances, the user can advantageously wear the infusion pump system 1 that operates according to the closed-loop delivery mode throughout the day, but the user can briefly interrupt the closed-loop delivery mode to manually initiate a “meal bolus” (or other type of bolus). For example, the user can trigger (via the user interface 220) an interruption of the closed-loop delivery mode, so that the user can manually enter a specific bolus dosage or initiate the calculation of a suggested bolus dosage based upon user input of an estimated number of carbohydrates to be consumed. Because the user can manually initiate the user-prompted bolus dosage prior to consuming the meal (e.g., before the user's blood glucose level rises due to consuming the food), the user may not experience a significant rise in his or her blood glucose level that might otherwise occur if operating under closed-loop control. After the manually-initiated bolus dosage is dispensed to the user, the infusion pump system can be configured to automatically return to the closed-loop delivery mode.
In the open-loop delivery mode, the control circuitry 240 of the controller device 200 can operate the pump device 100 to deliver insulin to the user according to a basal rate profile and user-selected bolus dosages. The user may select one or more bolus deliveries, for example, to offset the blood glucose effects caused by food intake, to correct for an undesirably high blood glucose level, to correct for a rapidly increasing blood glucose level, or the like. In some examples, the bolus dosages can be determined based on calculations made by the controller device 200 in response to a request by the user. For example, when the user's blood glucose level is rapidly increasing and has reached a high level (e.g., as indicated by the data received from the glucose monitoring device 50), the user may request the controller device 200 to calculate an appropriate bolus dosage of insulin to correct for the rapid increase and elevated blood glucose level. In another example, the user can request (via the user interface 220) that the controller device 200 calculate and suggest a bolus dosage based, at least in part, on a proposed meal that the user plans to consume.
The insulin dispensed into the user's body during closed-loop delivery mode and during any manually-initiated bolus dosages may act over a period of time to control the user's blood glucose level. As such, the user can benefit from the embodiments of the infusion pump system 1 that can take into account different circumstances and information when determining a dosage amount. For example, when calculating an insulin dosage, the controller device 200 employed one or more user-specific dosage parameters that reflect the user's physiological response to insulin. In some embodiments, the controller device 200 can employ the user-specific dosage parameters in combination with data indicative of the user's blood glucose level, historical food intake data previously submitted by the user, the user's insulin load, and the like to provide an accurate dosage calculation. Exemplary information that can be derived from the user's blood glucose information that can be used by the controller device 200 in determining a bolus dosage can include the user's current blood glucose level, the rate of change in the user's blood glucose level, the 2nd derivative of the user's blood glucose data, the shape and/or appearance of the user's blood glucose curve, or the like. In some embodiments, the controller device 200 can use information from previously entered meals and previously delivered insulin dosages when calculating a suggested bolus dosage. In these embodiments, information regarding previously entered meals and previously delivered insulin dosages from 12 hours or more (e.g., 24 hours, 12 hours, 8 hours, 6 hours, 0.5 hours, or the like) can be used in the bolus dosage calculations.
Relevant user-specific dosage parameters may include, but are not limited to, one or more of the following: insulin sensitivity (e.g., in units of mg/dL/insulin unit), carbohydrate ratio (e.g., in units of g/insulin unit), insulin onset time (e.g., in units of minutes and/or seconds), insulin-on-board duration (e.g., in units of minutes and/or seconds), and basal rate profile (e.g., an average basal rate or one or more segments of a basal rate profile expressed in units of insulin unit/hour). These and other suitable dosage parameters may be pre-loaded into the control circuitry 240 or input by a user via the user interface. Further, in some examples, the control circuitry 240 can cause the memory device 242 to store any of the following parameters derived from the historical pump usage information: dosage logs, average total daily dose, average total user-initiated bolus dose per day, a ratio of correction bolus amount per day to food bolus amount per day, amount of correction boluses per day, a ratio of a correction bolus amount per day to the average total daily dose, average maximum bolus per day, and a frequency of cannula and tube primes per day. To the extent these aforementioned dosage parameters or historical parameters are not stored in the memory device 241, the control circuitry 240 can be configured to calculate any of these aforementioned dosage parameters or historical parameters from other data stored in the memory device 241 or otherwise input via the user interface 220.
The user interface 220 of the controller device 200 can include input components and/or output components that are electrically connected to the control circuitry 240. For example, the user interface 220 can include the display device 222 having an active area that outputs information to a user and buttons 224 that the user can use to provide input. Here, the display device 222 can be used to communicate a number of settings (e.g., user-specific dosage parameters) or menu options (e.g., options for interrupting a closed-loop delivery mode to provide a manually-initiated bolus dosage) for the infusion pump system 1. In some embodiments, the control circuitry 240 can receive input commands from a user's button selections and thereby cause the display device 222 to output a number of menus or program screens that show particular settings and data. The control circuitry 240 may be programmable to cause the control circuitry 240 to change any one of a number of settings or modes of operation for the infusion pump system 1. In some embodiments, the control circuitry 240 can include a cable connector (e.g., a USB connection port or another data cable port) that is accessible on an external portion of the controller housing 210. As such, a cable can be connected to the control circuitry 240 to upload or download data or program settings to the control circuitry.
Referring now to
Stacking Value=(Requested Bolus Dosage)+(eIOB).
eIOB=[Σ(Dosagen*Duration Factor(t)n)]−Estimated Basal Rate,
Due in part to pharmacokinetic effects (e.g., the time it takes for insulin to enter the blood stream from the subcutaneous point of delivery) and pharmacodynamic effects (e.g., the time it takes for a concentration of insulin in the blood to have the physiological effect of lower blood glucose level), insulin dispensed into the user's system may not act instantaneously, but instead may act over a period of time to control the user's blood glucose level. As such, at any given time the user's body may include some amount of insulin that has not yet acted. Thus, a duration factor determined as a function of time is applied to the quantity of each dosage during the specified time period to estimate a value of previously dispensed insulin that has not yet acted in the user's body. In some implementations, suitable duration factors may be determined based on a duration of action profile preloaded into the controller device 200. In some implementations, suitable duration factors may be calculated on demand by the controller device 200 based on historical logs of previous dosages and blood glucose data stored in computer memory.
As previously described, the pump controller 200 can optionally operate in an open-loop mode where scheduled basal dosages of insulin are supplied in addition to user-prompted bolus dosages. The basal delivery rate can be selected to maintain a user's blood glucose level in a targeted range during normal activity when the user is not consuming food items. Thus, the basal delivery rate may correspond to the user's background insulin needs. In the open-loop delivery mode, the user-selected bolus deliveries supplement the scheduled basal deliveries by providing substantially larger amounts of insulin in particular circumstances, such as when the user consumes food items, when the user's blood glucose level increases beyond a safe limit, when the user's blood glucose level rises faster than a threshold rate, or other scenarios in which the blood glucose level requires a significant correction.
When the infusion pump system 1 operates in a closed-loop mode, however, the insulin dispensation is autonomously adjusted in response to changes in the user's blood glucose level. As such, in the closed-loop mode, the infusion pump system 1 may not necessarily adhere to a pre-stored basal schedule (because the user's blood glucose level is changing). Thus, the user's background insulin needs cannot simply be taken as a constant, pre-stored basal delivery rate, but the controller device 200 may instead approximate an “Estimated Basal Rate” based on the insulin dispensations performed during the closed-loop delivery mode. The estimated basal rate may be preloaded into the controller device or calculated based on historical logs of previous insulin dosages and/or user input (e.g., user input indicating a total daily dose of insulin). In some embodiments, the estimated basal rate may calculated as:
Estimated Basal Rate=Total Dose/(T*Scale Down Factor),
In some embodiments, the estimated basal rate may be determined by calculating the average basal rate outside of detectable meal times for a given time period. More specifically, the controller device 200 may exclude insulin deliveries adjacent detected meal times from the average basal rate calculation. For example, the controller device 200 may exclude insulin delivers from a predetermined time before (e.g., 0 to 45 minutes) and after (e.g., 90 to 180 minutes) a detected meal from the average basal rate calculation. Any suitable meal-detection algorithm can be used for determining an estimated basal rate according to the above described technique. In some embodiments, a fuzzy-logic dosing rules matrix can be used to determine when meals have occurred. For example, certain cells of the matrix may be pre-set as associated with basal or meal-time bolus insulin; and/or statistical analytics may be employed to identify cells that tend to correspond with the onset of glucose rise after a meal for a particular user. Further, in some embodiments, the controller device 200 may determine that a meal has taken place based on direct scrutiny of the user's blood glucose level. For example, a rapid increase in blood glucose may signal that a meal is likely to have taken place.
In some embodiments, insulin delivers adjacent detectable exercise sessions may be excluded from the estimated basal rate calculation. For example, in some embodiments, activity sensors incorporated within the infusion pump system 1 or linked via telemetry could be used to identify exercise or elevated activity levels. Typically the need for insulin is reduced following exercise. Thus excluding insulin delivery data for a period of time after the detection of elevated activity would improve the detection of underlying basal delivery. As one particular, non-limiting example, after detecting 45 minutes of activity levels related to running or walking, the system could be designed to exclude insulin deliveries from the estimated basal calculation for a period of 2 to 8 hours.
As shown in
Referring now to
In operation 502, the controller device 200 delivers medicine (e.g., insulin in this embodiment) at a dispensation rate according to a closed-loop control protocol. As previously described, in the embodiments in which the infusion pump system is dispensing insulin, closed-loop operations facilitated by the control circuitry may cause the infusion pump system to imitate a pancreatic beta cell so that the insulin dispensation is adjusted according to increases or decreases in the user's blood glucose level (see
In operation 504, the controller device 200 can detect receipt of a trigger to initiate a user-prompted bolus dosage. Such a trigger can occur at any time during the closed-loop delivery mode. As previously described, in some embodiments, such a trigger event may include a user's selection of a particular button (e.g., a physical button or a touchscreen button) on the user interface of the controller, which may indicate the user's request for a manually-initiated bolus dosage. In operation 506, if the trigger is received (504), the controller device 200 can temporarily interrupt the closed-loop delivery mode to provide the user-prompted manual bolus (see
When no trigger is detected (504), the process 500 continues in the closed loop delivery mode. In operation 508, the pump system can receiving blood glucose information indicative of a sensed blood glucose level of the user. For example, as described above, blood glucose data can be received from a glucose monitoring device 50 in wireless communication with the pump assembly 10 (or received from a blood glucose test strip reader).
In operation 510, the sensed blood glucose level (as indicated by the received blood glucose data) is compared to a target blood glucose level (or otherwise compared to a target blood glucose range). In one implementation, one or more target blood glucose levels may be stored in memory device 242 of the control circuitry 240. The target blood glucose levels may correspond to one or more monitored sensory feedback signals. For instance, the target blood glucose level may vary according to the user's food intake and/or physiological status. As one example, the member device 242 stores data indicating at least a fasting target blood glucose level and a postprandial target blood glucose level. In some embodiments, a target blood glucose level can be expressed as a range. In some embodiments, the target blood glucose levels can be manually submitted to the controller device 200 via the user interface 220. In some embodiments, the target blood glucose levels can be determined statistically or empirically by the controller device 200 as a user-specific dosage parameter based on previous iterations of a closed-loop delivery scheme.
If operation 510 reveals that the sensed blood glucose level is different from the targeted blood glucose level, the process 500 continues to operation 512 so that the dispensation rate is autonomously adjusted according to the closed-loop control protocol. In some embodiments, the dispensation rate is adjusted according to PID control calculations, fuzzy logic control calculations, and/or model predictive control calculations. Then, the controller device 200 returns to operation 502 so that the medicine is dispensed at the newly adjusted dispensation rate while awaiting detection of a trigger (operation 504) and/or updated information indicative of a sensed blood glucose level (operation 508).
If operation 510 reveals that the sensed blood glucose level is not different from the targeted blood glucose level, the process 500 returns to operation 502 so that the medicine is dispensed at the previously implemented dispensation rate while awaiting detection of a trigger (operation 504) and/or updated information indicative of a sensed blood glucose level (operation 508).
As noted above, a suitable closed-loop delivery mode may also be implemented via predictive control techniques. For example, one or more predictive models or fuzzy-logic dosage matrices may be employed to drive the dispensation of insulin dosages based on predicted blood glucose levels, such as described in U.S. Pat. No. 8,548,544.
In some implementations, one or more processes or specific operations described herein can be used in conjunction with types of medication other than insulin—e.g., glucagon. The glucagon may be delivered to a user via an infusion pump device or injected using a manual syringe or a single use injection “pen.” In some circumstances, an injectable form of glucagon is used in emergency aid of severe hypoglycemia when the victim is unconscious or for other reasons cannot take glucose orally. The glucagon fluid can be rapidly injected to the patient by intramuscular, intravenous or subcutaneous injection, and quickly raises the blood glucose level of the patient.
Referring in more detail to
After the user's blood glucose information is obtained (e.g., via operations 602-606), in operation 608, the controller device 200 can determine a suggested bolus dosage based on the obtained data and the user-specific dosage parameters that were determined during the closed-loop delivery mode. As noted above, in some embodiments, the suggested bolus dosage value can be calculated by the controller device 200 based on the eIOB component and one or both of the food offsetting component and the blood glucose correction component. In such embodiments, the food offsetting component can represent an insulin bolus dosage to offset food intake data that have not previously been offset by an earlier bolus dosage. The blood glucose correction component can represent an insulin bolus dosage to maintain or return the user's blood glucose level to a targeted value within a predetermined range. The eIOB component can take into account the net amount of remaining active insulin in the user's system over a selected time period immediately prior to the calculation. One non-limiting example is described below:
Suggested Bolus Dosage=(Food Offsetting Component)+(Blood Glucose Correction Component)−(eIOB Component).
Food Offsetting Component=(Carbohydrate Intake)*(Insulin to Carb. Ratio),
In operation 610, the controller device 200 can determine if the user accepts the suggested bolus dosage. For example, the user can select the user interface button 224 corresponding to the “YES” or “NO” option presented on the display device 222 to accept or decline the suggested bolus dosage. In operation 612, if the accepts the suggested bolus dosage (610), the controller device 200 can initiate delivery of the suggested bolus dosage by the pump device 100. If the user declines the suggested bolus dosage (610), the controller device 200 can prompt the user for a modified dosage. In operation 614, the controller device 200 can determine if the user wishes to receive a modified bolus dosage. In operation 616, if the user wishes to receive a modified bolus dosage (614), the controller device 200 can obtain the modified bolus dosage. For example, the user can enter a modified bolus dosage or provide additional data that can be used to calculate a modified dosage via the user interface 220. In operation 618, the controller device 200 can initiate delivery of the modified bolus dosage by the pump device 100. After a suggested (612) or modified (618) bolus dosage has been initiated, or after the user has declined the suggested (612) and modified dosages (618), the controller device 200 automatically returns to the closed-loop delivery mode (see
Referring in more detail to
Future BG Level=(eIOB+Requested Dose)*Insulin Sensitivity
In some embodiments, the controller 200 determines whether the requested bolus dosage is permissible by determining whether a stacking value, calculated as the sum of the requested bolus dosage and the eIOB (see definition describe above), is above a predetermined threshold. The stacking threshold may be determined as the amount of insulin likely to cause the user to suffer symptoms of hypoglycemia, which may optionally be reduced by some safety margin (e.g., 10%-20%). In some embodiments, the stacking threshold is determined based on the unique physiological characteristics of the user. For example, the stacking threshold may be manually entered into the controller device 200 by a healthcare professional or determined based on historical logs of insulin dosage. For instance, the stacking threshold may be determined as the highest amount of total insulin-on-board during closed-loop operations. As another non-limiting example, the stacking threshold may be calculated as:
Stacking Threshold=(Current BG Level−Minimum BG Level)/Insulin Sensitivity,
In operation 658, if the requested bolus dosage is permissible (656), the controller device 200 initiates delivery of the manually entered bolus dosage. The controller device 200 then automatically returns to the closed-loop delivery mode (see
While the processes described above are directed to a technique including an interruptible closed-loop delivery mode. In some implementations, the controller device may facilitate the dispensation of a bolus dosage “on top” of the closed-loop operations. So, for example, the controller device may continue the automatic dispensation of insulin according to a suitable artificial pancreas scheme, without interruption, as the user manually requests and initiates a bolus dosage. The above-described operations for safely facilitating the user-requested bolus dosage based on eIOB may be conducted concurrently with the closed-loop operations. The dispensed bolus dosage can be accounted for by the controller device in predicting a future blood glucose level of the user in accordance with predictive closed-loop control techniques.
In some implementations, a controller device (e.g., the controller device 200) can operate an infusion pump system (e.g., the infusion pump system) according to a closed-loop mode of control configured to account for glucagon medication (as an alternative to, or in addition to, the insulin medication). The infusion pump system may be able to dispense the glucagon directly or merely suggest to the user that a manual dosage should be injected (e.g., via a pen applicator). In some implementations, the controller device may interrupt closed-loop operations to suggest and dispense (or suggest and wait for a manual injection) a glucagon bolus in response to a determination (or a prediction, as discussed above) that the user's blood glucose level is (or is likely to be) below a certain target level. In some implementations, the controller device may suggest and dispense the glucagon bolus “on top” (e.g., without interruption) of the closed-loop operations. For example, the controller device may continue any monitoring or calculating processes in the closed-loop delivery mode, and merely cease insulin dispensation, in response to a low BG level determination.
The controller device in these implementations can determine a suggested glucagon dose for the user to achieve the target blood glucose level. The suggested glucagon dose can be displayed to the user to cause the user to confirm dispensation by the infusion pump device or manually administer glucagon to achieve a blood glucose level that is proximate to the target level (or is within the target level range). If the target blood glucose level is a range, the suggested glucagon dose can be determined to cause the user's blood glucose level to reach the bottom value of the range, to reach a mid-point value of the range, or to reach another specified value within the range (for example, a suggested glucagon dose can be calculated to cause the user's blood glucose level to at least exceed a value that is 5 mg/dL greater than the bottom of the target blood glucose range). The controller device can use various parameters associated with the user to determine the suggested glucagon dose for the user. For example, the controller device can use the user's current blood glucose level, the target blood glucose level, and the user's glucagon sensitivity value to determine a suggested glucagon dose according to the following formula:
Suggested Glucagon Dose=(Target BG−Current BG)/Glucagon Sensitivity
Stepping through the above equation, if, for example, the user's current BG level is 50 mg/dL, the user's target BG level is 90 mg/dL, and the user's glucagon sensitivity is 20 mg/dL/Unit of Glucagon, then the above equation would be solved as:
Suggested Glucagon Dose=(90−50)/20=40/20=2Units of Glucagon
Depending upon the concentration of the glucagon fluid, a “Unit” of glucagon correlates to a particular number of milligrams (mg) or micrograms (mcg) of Glucagon. For example, in this embodiment, a “Unit” of glucagon correlates to 0.4 mg of glucagon, so the suggested glucagon dose of 2 Units of glucagon would be 0.8 mg of glucagon.
In some embodiments, rather than a current BG level for the user, a projected BG level for the user can be identified based on a determined BG level rate of change for the user and a previously identified BG level for the user. The controller device can then use the projected BG level to determine a suggested glucagon dose according to the following formula:
Suggested Glucagon Dose=(Target BG−Projected BG)/Glucagon Sensitivity
As described above, additional parameters can also be used when determining a suggested glucagon dosage to achieve a target BG level for the user. For example Insulin on Board (JOB) or Total Insulin Load (TIL) values can be used in combination with an insulin sensitivity for the user when determining a suggested glucagon dose. For example, IOB can be used to determine a suggested glucagon dose for the user according to the formula:
Suggested Glucagon Dose=(Target BG−Current BG−(IOB/insulin Sensitivity))/Glucagon Sensitivity
Similarly, TIL can be used to determine a suggested glucagon dose for the user according to the formula:
Suggested Glucagon Dose=(Target BG−Current BG−(TIL/Insulin Sensitivity))/Glucagon Sensitivity
Another factor that can be considered when determining the suggested glucagon dose is a recent activity of the user. The effect of an activity on a user can be quantified as an activity level divided by an activity sensitivity for the user (where the activity sensitivity defines how the user's BG level changes in response to activity). Activity level can be used to determine a suggested glucagon dose for the user according to the formula:
Suggested Glucagon Dose=(Target BG−Current BG−(Activity Level/Activity Sensitivity))/Glucagon Sensitivity
Yet another parameter that can be taken into consideration when determining the suggested glucagon dose for the user is Food on Board (FOB). For example, the FOB value can indicate a number of grams of carbohydrates ingested by the user. This value can be utilized along with a “carb ratio” for the user (i.e., a ratio indicating effect of carbohydrates on the BG level of the user). FOB can be a time sensitive function where food action is assumed to decay over a period of time from the time of ingestion. Food action may vary based on the content of the food, with protean and fat components having a longer time function in comparison to high glycemic index carbohydrates, which have a very short time function and low glycemic index carbohydrates, which have a moderate time function. FOB can be used to determine a suggested glucagon dose for the user according to the formula:
Suggested Glucagon Dose=(Target BG−Current BG+(FOB/Carb Ratio))/Glucagon Sensitivity
Another parameter that can be taken into consideration when calculating a suggested glucagon dose is glucagon on board (GOB). The GOB value can be, for example, received from a glucagon administration device, or be entered into a suggested glucagon dose calculator manually by a user. The GOB can be, for example, a measure of the amount of glucagon in a user's system that has not yet been processed. GOB can be used to determine a suggested glucagon dose for the user according to the formula:
Suggested Glucagon Dose=(Target BG−Current BG)/Glucagon Sensitivity−GOB
It should be understood from the teachings herein that, in some embodiments, any combination of the aforementioned parameters can be taken into consideration by the glucagon dosage calculator when calculating a suggested glucagon dose. For example, in particular embodiments, all of these aforementioned parameters can be taken into account when calculating a suggested glucagon dose:
Suggested Glucagon Dose=[Target BG−Current BG−(IOB/insulin Sensitivity)−(Activity Level/Activity Sensitivity)+(FOB/Carb Ratio)]/Glucagon Sensitivity−GOB
Other combinations of the above discussed parameters can be used when determining a suggested glucagon dose for the user. Additional parameters could also be used in determining a suggested blood glucagon dose for the user.
Referring now to
The pump system 700 can also communicate with the aforementioned glucose monitoring device 50 for the purpose of receiving data indicative of a user's blood glucose level. As shown in
As previously described in connection with
A number of embodiments of the invention have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention. Accordingly, other embodiments are within the scope of the following claims.
This application is a continuation application of and claims priority to U.S. application Ser. No. 14/699,341, filed on Apr. 29, 2015.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5984894 | Poulsen | Nov 1999 | A |
| 6126595 | Amano | Oct 2000 | A |
| 6233471 | Berner et al. | May 2001 | B1 |
| 6461331 | Van Antwerp | Oct 2002 | B1 |
| 6474219 | Klitmose et al. | Nov 2002 | B2 |
| 6485461 | Mason et al. | Nov 2002 | B1 |
| 6508788 | Preuthun | Jan 2003 | B2 |
| 6524280 | Hansen et al. | Feb 2003 | B2 |
| 6533183 | Aasmul et al. | Mar 2003 | B2 |
| 6537251 | Klitmose | Mar 2003 | B2 |
| 6540672 | Simonsen et al. | Apr 2003 | B1 |
| 6544229 | Danby et al. | Apr 2003 | B1 |
| 6547764 | Larsen et al. | Apr 2003 | B2 |
| 6551276 | Mann et al. | Apr 2003 | B1 |
| 6554798 | Mann et al. | Apr 2003 | B1 |
| 6554800 | Nezhadian et al. | Apr 2003 | B1 |
| 6558320 | Causey, III et al. | May 2003 | B1 |
| 6558351 | Steil et al. | May 2003 | B1 |
| 6562001 | Lebel et al. | May 2003 | B2 |
| 6562011 | Buch-Rasmussen et al. | May 2003 | B1 |
| 6564105 | Starkweather et al. | May 2003 | B2 |
| 6569126 | Poulsen et al. | May 2003 | B1 |
| 6571128 | Lebel et al. | May 2003 | B2 |
| 6572542 | Houben | Jun 2003 | B1 |
| 6577899 | Lebel et al. | Jun 2003 | B2 |
| 6582404 | Klitgaard et al. | Jun 2003 | B1 |
| 6585644 | Lebel et al. | Jul 2003 | B2 |
| 6585699 | Ljunggreen et al. | Jul 2003 | B2 |
| 6605067 | Larsen | Aug 2003 | B1 |
| 6613019 | Munk | Sep 2003 | B2 |
| 6641533 | Causey, III et al. | Nov 2003 | B2 |
| 6648821 | Lebel et al. | Nov 2003 | B2 |
| 6650951 | Jones et al. | Nov 2003 | B1 |
| 6656158 | Mahoney et al. | Dec 2003 | B2 |
| 6656159 | Flaherty | Dec 2003 | B2 |
| 6659948 | Lebel et al. | Dec 2003 | B2 |
| 6659978 | Kasuga | Dec 2003 | B1 |
| 6659980 | Moberg et al. | Dec 2003 | B2 |
| 6663602 | Møller | Dec 2003 | B2 |
| 6668196 | Villegas et al. | Dec 2003 | B1 |
| 6669669 | Flaherty et al. | Dec 2003 | B2 |
| 6687546 | Lebel et al. | Feb 2004 | B2 |
| 6690192 | Wing | Feb 2004 | B1 |
| 6691043 | Ribeiro, Jr. | Feb 2004 | B2 |
| 6692457 | Flaherty | Feb 2004 | B2 |
| 6692472 | Hansen et al. | Feb 2004 | B2 |
| 6694191 | Starkweather et al. | Feb 2004 | B2 |
| 6699218 | Flaherty et al. | Mar 2004 | B2 |
| 6702779 | Connelly et al. | Mar 2004 | B2 |
| 6715516 | Ohms et al. | Apr 2004 | B2 |
| 6716198 | Larsen | Apr 2004 | B2 |
| 6723072 | Flaherty et al. | Apr 2004 | B2 |
| 6723077 | Pickup et al. | Apr 2004 | B2 |
| 6733446 | Lebel et al. | May 2004 | B2 |
| 6736796 | Shekalim | May 2004 | B2 |
| 6740059 | Flaherty | May 2004 | B2 |
| 6740072 | Starkweather et al. | May 2004 | B2 |
| 6740075 | Lebel et al. | May 2004 | B2 |
| 6744350 | Blomquist | Jun 2004 | B2 |
| 6749587 | Flaherty | Jun 2004 | B2 |
| 6752787 | Causey, III et al. | Jun 2004 | B1 |
| 6758810 | Lebel et al. | Jul 2004 | B2 |
| 6768425 | Flaherty et al. | Jul 2004 | B2 |
| 6780156 | Haueter et al. | Aug 2004 | B2 |
| 6786246 | Ohms et al. | Sep 2004 | B2 |
| 6786890 | Preuthun et al. | Sep 2004 | B2 |
| 6796970 | Klitmose et al. | Sep 2004 | B1 |
| 6799149 | Hartlaub | Sep 2004 | B2 |
| 6809653 | Mann et al. | Oct 2004 | B1 |
| 6810290 | Lebel et al. | Oct 2004 | B2 |
| 6811533 | Lebel et al. | Nov 2004 | B2 |
| 6811534 | Bowman, IV et al. | Nov 2004 | B2 |
| 6813519 | Lebel et al. | Nov 2004 | B2 |
| 6827702 | Lebel et al. | Dec 2004 | B2 |
| 6830558 | Flaherty et al. | Dec 2004 | B2 |
| 6852104 | Blomquist | Feb 2005 | B2 |
| 6854620 | Ramey | Feb 2005 | B2 |
| 6854653 | Eilersen | Feb 2005 | B2 |
| 6855129 | Jensen et al. | Feb 2005 | B2 |
| 6872200 | Mann et al. | Mar 2005 | B2 |
| 6873268 | Lebel et al. | Mar 2005 | B2 |
| 6878132 | Kipfer | Apr 2005 | B2 |
| 6893415 | Madsen et al. | May 2005 | B2 |
| 6899695 | Herrera | May 2005 | B2 |
| 6899699 | Enggaard | May 2005 | B2 |
| 6922590 | Whitehurst | Jul 2005 | B1 |
| 6925393 | Kalatz et al. | Aug 2005 | B1 |
| 6936006 | Sabra | Aug 2005 | B2 |
| 6936029 | Mann et al. | Aug 2005 | B2 |
| 6945961 | Miller et al. | Sep 2005 | B2 |
| 6948918 | Hansen | Sep 2005 | B2 |
| 6950708 | Bowman, IV et al. | Sep 2005 | B2 |
| 6960192 | Flaherty et al. | Nov 2005 | B1 |
| 6979326 | Mann et al. | Dec 2005 | B2 |
| 6997911 | Klitmose | Feb 2006 | B2 |
| 6997920 | Mann et al. | Feb 2006 | B2 |
| 7005078 | Van Lintel et al. | Feb 2006 | B2 |
| 7008399 | Larson et al. | Mar 2006 | B2 |
| 7014625 | Bengtsson | Mar 2006 | B2 |
| 7018360 | Flaherty et al. | Mar 2006 | B2 |
| 7025743 | Mann et al. | Apr 2006 | B2 |
| 7029455 | Flaherty | Apr 2006 | B2 |
| 7054836 | Christensen et al. | May 2006 | B2 |
| 7104972 | Møller et al. | Sep 2006 | B2 |
| 7109878 | Mann et al. | Sep 2006 | B2 |
| 7128727 | Flaherty et al. | Oct 2006 | B2 |
| 7133329 | Skyggebjerg et al. | Nov 2006 | B2 |
| 7232423 | Mernoe et al. | Jun 2007 | B2 |
| 7278983 | Ireland et al. | Oct 2007 | B2 |
| 7291107 | Hellwig et al. | Nov 2007 | B2 |
| 8548544 | Kircher et al. | Oct 2013 | B2 |
| 20010056262 | Cabiri | Dec 2001 | A1 |
| 20020004651 | Ljndggreen et al. | Jan 2002 | A1 |
| 20020007154 | Hansen et al. | Jan 2002 | A1 |
| 20020040208 | Flaherty et al. | Apr 2002 | A1 |
| 20020091358 | Klitmose | Jul 2002 | A1 |
| 20020126036 | Flaherty et al. | Sep 2002 | A1 |
| 20030055380 | Flaherty | Mar 2003 | A1 |
| 20030065308 | Lebel et al. | Apr 2003 | A1 |
| 20030088238 | Poulsen | May 2003 | A1 |
| 20030104982 | Wittmann et al. | Jun 2003 | A1 |
| 20030199825 | Flaherty | Oct 2003 | A1 |
| 20030216683 | Shekalim | Nov 2003 | A1 |
| 20040010207 | Flaherty et al. | Jan 2004 | A1 |
| 20040019325 | Shekalim | Jan 2004 | A1 |
| 20040064088 | Gorman et al. | Apr 2004 | A1 |
| 20040064096 | Flaherty et al. | Apr 2004 | A1 |
| 20040078028 | Flaherty et al. | Apr 2004 | A1 |
| 20040087894 | Flaherty | May 2004 | A1 |
| 20040092865 | Flaherty et al. | May 2004 | A1 |
| 20040092878 | Flaherty | May 2004 | A1 |
| 20040116866 | Gorman et al. | Jun 2004 | A1 |
| 20040127844 | Flaherty | Jul 2004 | A1 |
| 20040153032 | Garribotto et al. | Aug 2004 | A1 |
| 20040167464 | Ireland et al. | Aug 2004 | A1 |
| 20040171983 | Sparks et al. | Sep 2004 | A1 |
| 20040176720 | Kipfer | Sep 2004 | A1 |
| 20040176727 | Shekalim | Sep 2004 | A1 |
| 20040204673 | Flaherty | Oct 2004 | A1 |
| 20040220551 | Flaherty et al. | Nov 2004 | A1 |
| 20040235446 | Flaherty et al. | Nov 2004 | A1 |
| 20040260233 | Garibotto et al. | Dec 2004 | A1 |
| 20050021005 | Flaherty et al. | Jan 2005 | A1 |
| 20050022274 | Campbell et al. | Jan 2005 | A1 |
| 20050065760 | Murtfeldt et al. | Mar 2005 | A1 |
| 20050090808 | Malave et al. | Apr 2005 | A1 |
| 20050095063 | Fathallah | May 2005 | A1 |
| 20050160858 | Mernoe | Jul 2005 | A1 |
| 20050171512 | Flaherty | Aug 2005 | A1 |
| 20050182366 | Vogt et al. | Aug 2005 | A1 |
| 20050192561 | Mernoe | Sep 2005 | A1 |
| 20050203461 | Flaherty et al. | Sep 2005 | A1 |
| 20050215982 | Estes | Sep 2005 | A1 |
| 20050222645 | Malave et al. | Oct 2005 | A1 |
| 20050238507 | DiIanni et al. | Oct 2005 | A1 |
| 20050245878 | Mernoe et al. | Nov 2005 | A1 |
| 20050251097 | Mernoe | Nov 2005 | A1 |
| 20050267402 | Stewart et al. | Dec 2005 | A1 |
| 20050273059 | Mernoe et al. | Dec 2005 | A1 |
| 20060041229 | Garibotto et al. | Feb 2006 | A1 |
| 20060069382 | Pedersen | Mar 2006 | A1 |
| 20060074381 | Malave et al. | Apr 2006 | A1 |
| 20060135913 | Ethelfeld | Jun 2006 | A1 |
| 20060142698 | Ethelfeld | Jun 2006 | A1 |
| 20060173406 | Hayes et al. | Aug 2006 | A1 |
| 20060178633 | Garibotto et al. | Aug 2006 | A1 |
| 20060184119 | Remde et al. | Aug 2006 | A1 |
| 20060200073 | Radmer et al. | Sep 2006 | A1 |
| 20060206054 | Shekalim | Sep 2006 | A1 |
| 20060247581 | Pedersen et al. | Nov 2006 | A1 |
| 20070073228 | Mernoe et al. | Mar 2007 | A1 |
| 20070073235 | Estes et al. | Mar 2007 | A1 |
| 20070073236 | Mernoe et al. | Mar 2007 | A1 |
| 20070118405 | Campbell et al. | May 2007 | A1 |
| 20070124002 | Estes et al. | May 2007 | A1 |
| 20070156092 | Estes et al. | Jul 2007 | A1 |
| 20070167905 | Estes et al. | Jul 2007 | A1 |
| 20070167912 | Causey et al. | Jul 2007 | A1 |
| 20070173761 | Kanderian, Jr. et al. | Jul 2007 | A1 |
| 20070179444 | Causey et al. | Aug 2007 | A1 |
| 20080125700 | Moberg et al. | May 2008 | A1 |
| 20080172027 | Blomquist | Jul 2008 | A1 |
| 20080177165 | Blomquist et al. | Jul 2008 | A1 |
| 20080294094 | Mhatre et al. | Nov 2008 | A1 |
| 20080294142 | Patel et al. | Nov 2008 | A1 |
| 20080306434 | Dobbles et al. | Dec 2008 | A1 |
| 20080306444 | Brister | Dec 2008 | A1 |
| 20100174266 | Estes | Jul 2010 | A1 |
| 20100286601 | Yodfat | Nov 2010 | A1 |
| 20100298765 | Budiman | Nov 2010 | A1 |
| 20120016304 | Patel et al. | Jan 2012 | A1 |
| 20140066890 | Sloan et al. | Mar 2014 | A1 |
| 20140180203 | Budiman et al. | Jun 2014 | A1 |
| 20140309615 | Mazlish | Oct 2014 | A1 |
| 20140323959 | Lebel et al. | Oct 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 2543545 | May 2005 | CA |
| 196 27 619 | Jan 1998 | DE |
| 102 36 669 | Feb 2004 | DE |
| 20 2005 012 358 | Oct 2005 | DE |
| 0 062 974 | Oct 1982 | EP |
| 0 275 213 | Jul 1988 | EP |
| 0 496 141 | Jul 1992 | EP |
| 0 612 004 | Aug 1994 | EP |
| 0 580 723 | Oct 1995 | EP |
| 1 045 146 | Dec 2000 | EP |
| 1 136 698 | Sep 2001 | EP |
| 1 177 802 | Feb 2002 | EP |
| 0 721 358 | May 2002 | EP |
| 1 495 775 | Jan 2005 | EP |
| 1 527 792 | May 2005 | EP |
| 1 754 498 | Feb 2007 | EP |
| 1 818 664 | Aug 2007 | EP |
| 2 585 252 | Jan 1987 | FR |
| 747 701 | Apr 1956 | GB |
| 2 218 831 | Nov 1989 | GB |
| WO 9015928 | Dec 1990 | WO |
| WO 9721457 | Jun 1997 | WO |
| WO 9811927 | Mar 1998 | WO |
| WO 9857683 | Dec 1998 | WO |
| WO 9921596 | May 1999 | WO |
| WO 9939118 | Aug 1999 | WO |
| WO 9948546 | Sep 1999 | WO |
| WO 0172360 | Oct 2001 | WO |
| WO 0191822 | Dec 2001 | WO |
| WO 0191833 | Dec 2001 | WO |
| WO 0240083 | May 2002 | WO |
| WO 02057627 | Jul 2002 | WO |
| WO 02100469 | Dec 2002 | WO |
| WO 03103763 | Dec 2003 | WO |
| WO 04056412 | Jul 2004 | WO |
| WO 04093648 | Nov 2004 | WO |
| WO 04110526 | Dec 2004 | WO |
| WO 05002652 | Jan 2005 | WO |
| WO 05039673 | May 2005 | WO |
| WO 05072794 | Aug 2005 | WO |
| WO 05072795 | Aug 2005 | WO |
| WO 06075016 | Jul 2006 | WO |
| WO 06105792 | Oct 2006 | WO |
| WO 06105793 | Oct 2006 | WO |
| WO 06105794 | Oct 2006 | WO |
| Entry |
|---|
| “Using the Deltec Cozmo Insulin Pump Correction Bolus Feature” believed to be publicly available before May 5, 2008, pp. 36-41. |
| “Which Insulin Pump is Right for Me?”, Albany Medical Center, Goodman Diabetes Service, Jan. 2006, 4 pages. |
| Asante Pearl, Insulin Pump User Manual, 2012, 180 pages. |
| Collins and Lee, “Microfluidic flow transducer based on the measurement of electrical admittance,” Lab Chip, 2003, 12 pages. |
| Debiotech News Release, “Debiotech reveals its new miniaturized Disposable Insulin Nanopump™ for Diabetes therapy,” available at http://www.debiotech.com/news/nw_159.html Apr. 24, 2006, 3 pages. |
| Medtronic News Release, “Medtronic Receives FDA Approval for World's First Insulin Pump with Real-time Continuous Glucose Monitoring,” Apr. 13, 2006, 3 pages. |
| Patent Abstracts of Japan, vol. 1999, No. 04, and JP 11 010036 , Apr. 30, 1999 and Jan. 19, 1999, Toray Ind. Inc., 6 pages. |
| Walsh et al., “Guidelines for Insulin Dosing in Continuous Subcutaneious Insulin Infusion Using New Formulas from a Retrospective Study of Individuals with Optimal Glucose Levels”, J. Diabetes Science and Technology, Sep. 2010, 4(5):8 pages. |
| Walsh et al., “Guidelines for Optimal Bolus Calculator Settings in Adults”, J. Diabetes Science and Technology, Jan. 2011, 5(1):7 pages. |
| International Search Report and Written Opinion in International Application No. PCT/US2016/029440, dated Sep. 27, 2016, 12 pages. |
| International Preliminary Report of Patentability in International Application No. PCT/US2016/029440, dated Nov. 9, 2017, 10 pages. |
| Invitation to Pay Additional Fees and where applicable, protest fee in International Application No. PCT/US2016/029440 dated Jul. 28, 2016, 2 pages. |
| European Extended Search Report in European Application No. 16787016.1, dated Mar. 21, 2018, 9 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20180133397 A1 | May 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14699341 | Apr 2015 | US |
| Child | 15848622 | US |
