Operating an infusion pump system

Information

  • Patent Grant
  • 11471598
  • Patent Number
    11,471,598
  • Date Filed
    Thursday, February 20, 2020
    4 years ago
  • Date Issued
    Tuesday, October 18, 2022
    a year ago
Abstract
Some embodiments of an infusion pump system can be configured to control dispensation of medicine according to a closed-loop delivery mode that is responsive to feedback information provided from a monitoring device, and the infusion pump system permits a user to interrupt the closed-loop delivery mode for purposes of dispensing a user-selected manual bolus dosage.
Description
TECHNICAL FIELD

This document relates to an infusion pump system, such as a portable infusion pump system for dispensing insulin or another medicine.


BACKGROUND

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.


BRIEF SUMMARY

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,


where n is any positive whole number, and where Duration Factor(t)n, represents a factor discounting the dosage based on an amount of time (t) since its delivery.


According to one or more embodiments, the method further includes outputting an alert from the infusion pump system in response to a calculated stacking value exceeding a predetermined stacking threshold, the calculated stacking value includes the calculated dosage amount of the user-selected manual bolus dosage plus the Effective Insulin-on-board. According to one or more embodiments, the calculated dosage amount of the user-selected manual bolus dosage includes include a calculation of a suggested bolus dosage according to the following function:

Suggested Bolus Dosage=(Food Offsetting Component)+(Blood Glucose Correction Component)−(Effective Insulin-on-board Component).


According to one or more embodiments, the Estimated Basal Rate is calculated according to the following function:

Estimated Basal Rate=Total Dose/(T*Scale Down Factor), where T is a unit of time.


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.





BRIEF DESCRIPTION OF DRAWINGS


FIG. 1 is a perspective view of a first example infusion pump system, in accordance with some embodiments.



FIG. 2 is an exploded perspective view of a portion of the infusion pump system of FIG. 1.



FIG. 3 is an exploded perspective view of a controller device for the infusion pump system of FIG. 1.



FIG. 4A is a perspective view of the infusion pump system of FIG. 1 including a user interface display for inputting a manual bolus dosage, in accordance with some embodiments.



FIG. 4B is a perspective view of the infusion pump system of FIG. 1 including a user interface display for outputting an alert indicating a manual bolus dosage is not permitted.



FIG. 4C is a perspective view of the infusion pump system of FIG. 1 including a user interface display for providing menu options to correct the non-permitted manual bolus dosage.



FIG. 5 is a flowchart of an example process for operating an infusion pump system an interruptible closed-loop mode of control, in accordance with some embodiments.



FIG. 6A is a flowchart of a first example process for temporarily interrupting a closed-loop delivery mode for providing a manually-initiated bolus dosage, in accordance with some embodiments.



FIG. 6B is a flowchart of a second example process for temporarily interrupting a closed-loop delivery mode for providing a manually-initiated bolus dosage, in accordance with some embodiments.



FIG. 7 is a perspective view of a second example infusion pump system, in accordance with some embodiments.





Like reference symbols in the various drawings may indicate like elements.


DETAILED DESCRIPTION

Referring to FIG. 1, some embodiments of an infusion pump system 1 can include a pump assembly 10 featuring a pump device 100 and a controller device 200. Optionally, the controller device 200 can be configured to releasably attach with the pump device 100. The controller device 200 can electrically communicate with the pump device 100 to control a drive system housed in the pump device 100 to dispense a medicine to a user (e.g., through a tube 147 of an infusion set 146 in this example). When the controller device 200 and the pump device 100 are assembled together, the user can (in some embodiments) conveniently wear the infusion pump system 1 on the user's skin under clothing, in a pouch clipped at the waist, or in the user's pocket while receiving the fluid dispensed from the pump device 100.


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 FIG. 2, the controller device 200 can include a housing 210 having a number of features that mate with complementary features of the pump housing structure 110. In such circumstances, the controller device 200 can removably attach with the pump device 100 in a generally side-by-side configuration. The compact size permits the pump assembly 10 to be discrete and portable. The controller device 200 can receive user input for purposes of operating the infusion pump system 1. In some embodiments, as described further below in connection with FIGS. 4A-6B, the infusion pump system 1 can be configured (e.g., appropriately designed and programmed) to operate in a closed-loop delivery mode in which the controller device 200 operates the pump device 100 to dispense insulin to a user autonomously (e.g., without user interaction) based on a sensed physiological condition of the user. Optionally, the closed-loop delivery mode can be temporarily interrupted by the user to provide a manually-initiated bolus dosage (e.g., not an autonomous adjustment of the insulin dispensation). Preferably, the controller device 200 may automatically return to the closed-loop delivery mode following completion or termination of the manually-initiated bolus dosage. Once resumed, future operations of the closed-loop delivery mode can account for any insulin dispensed during the manually-initiated bolus dosage.


Still referring to FIG. 1, the infusion pump system 1 may optionally include a glucose monitoring device 50 in communication with the pump assembly 10 for the purpose of supplying data indicative of a user's blood glucose level to the controller device 200. In some embodiments, as described further below in connection with FIG. 5, the controller device 200 can utilize the data indicative of a user's blood glucose level during operations in the closed-loop delivery mode so as to autonomously adjust the insulin dispensation rate. The glucose monitoring device 50 can include a housing 52, a wireless communication device 54, and a sensor shaft 56. The wireless communication device 54 can be contained within the housing 52 and the sensor shaft 56 can extend outward from the housing 52. In use, the sensor shaft 56 can penetrate the skin 20 of a user to make measurements indicative of characteristics of the user's blood (e.g., the user's blood glucose level or the like). In response to the measurements made by the sensor shaft 56, the glucose monitoring device 50 can employ the wireless communication device 54 to transmit data to a corresponding wireless communication device 247 housed in the pump assembly 10. In some embodiments, the monitoring device 50 may include a circuit that permits sensor signals (e.g., data from the sensor shaft 56) to be communicated to the communication device 54. The communication device 54 can transfer the collected data to the controller device 200 (e.g., by wireless communication to the communication device 247). Alternatively, the monitoring device 50 can employ other suitable methods of obtaining information indicative of a user's blood characteristics and transferring that information to the controller device 200. For example, an alternative monitoring device may employ a micropore system in which a laser porator creates tiny holes in the uppermost layer of a user's skin, through which interstitial glucose is measured using a patch. In the alternative, the monitoring device can use iontophoretic methods to non-invasively extract interstitial glucose for measurement. In other examples, the monitoring device can include non-invasive detection systems that employ near IR, ultrasound or spectroscopy, and particular embodiments of glucose-sensing contact lenses. Invasive methods involving optical means of measuring glucose could also be added. In yet another example, the monitoring device can include an optical detection instrument that is inserted through the skin for measuring the user's glucose level.


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 infusion 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 FIG. 1), which then analyzes the characteristics of the user's blood and communicates the information (via a wired or wireless connection) to the controller device 200. In still other embodiments, characteristics of the user's blood glucose information can be entered directly into the pump assembly 10 via a user interface 220 on the controller device 200.


Referring now to FIG. 2, the pump device 100 in this embodiment includes a housing structure 110 that defines a cavity 116 in which a fluid cartridge 120 can be received. The pump device 100 also can include a cap device 130 to retain the fluid cartridge 120 in the cavity 116 of the housing structure 110. The pump device 100 can include a drive system (not shown) that advances a plunger 125 in the fluid cartridge 120 so as to dispense fluid therefrom. In this embodiment, the controller device 200 communicates with the pump device 100 to control the operation of the drive system. Optionally, the controller device 200 may be configured as a reusable component that provides electronics and a user interface to control the operation of the pump device 100. In such circumstances, the pump device 100 can be a disposable component that is disposed of after a single use. For example, the pump device 100 can be a “one time use” component that is thrown away after the fluid cartridge 120 therein is exhausted. Thereafter, the user can removably attach a new pump device (having a new fluid cartridge) to the reusable controller device 200 for the dispensation of fluid from a new fluid cartridge. Accordingly, the user is permitted to reuse the controller device 200 (which may include complex or valuable electronics, as well as a rechargeable battery) while disposing of the relatively low-cost pump device 100 after each use. Such a pump assembly 10 can provide enhanced user safety as a new pump device (and drive system therein) is employed with each new fluid cartridge.


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 housing structure 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 FIG. 2, the controller device 200 can be removably attached to the pump device 100 so that the two components are mechanically mounted to one another in a fixed relationship. In some embodiments, such a mechanical mounting can also form an electrical connection between the removable controller device 200 and the pump device 100. For example, the controller device 200 can be in electrical communication with a portion of the drive system (show shown) of the pump device 100. In some embodiments, the pump device 100 can include a drive system that causes controlled dispensation of the medicine or other fluid from the cartridge 120. In some embodiments, the drive system incrementally advances a piston rod (not shown) longitudinally into the cartridge 120 so that the fluid is forced out of an output end 122. A septum 121 at the output end 122 of the fluid cartridge 120 can be pierced to permit fluid outflow when the cap device 130 is connected to the pump housing structure 110. For example, the cap device 130 may include a penetration needle that punctures the septum 121 during attachment of the cap device to the housing structure 110. Thus, when the pump device 100 and the controller device 200 are mechanically attached and thereby electrically connected, the controller device 200 communicates electronic control signals via a hardwire-connection (e.g., electrical contacts or the like) to the drive system or other components of the pump device 100. In response to the electrical control signals from the controller device 200, the drive system of the pump device 100 causes medicine to incrementally dispense from the fluid cartridge 120. Power signals, such as signals from a battery (not shown) of the controller device 200 and from the power source (not shown) of the pump device 100, may also be passed between the controller device 200 and the pump device 100.


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 FIGS. 1-2). The display device 222 can include an active area in which numerals, text, symbols, images, or a combination thereof can be displayed. For example, the display device 222 can be used to communicate a number of settings or menu options for the infusion pump system 1 (FIG. 1). In this embodiment, the user may press one or more of the buttons to shuffle through a number of menus or program screens that show particular operational modes (e.g., closed-loop delivery mode and, optionally, an open-loop delivery mode in which a basal profile is implemented and then supplemented with user-selected bolus dosages), settings (e.g., dosage parameters) and data (e.g., review data that shows a medicine dispensing rate, a total amount of medicine dispensed in a given time period, an amount of medicine scheduled to be dispensed at a particular time or date, an approximate amount of medicine remaining in the cartridge 120, or the like). In some embodiments, the user can adjust the modes and/or settings, or otherwise program the controller device 200 by pressing one or more buttons 224 of the user interface 220. For example, the user may press one or more of the buttons to temporarily change the operation of the infusion pump system 1 from a closed-loop delivery mode to provide at least one manually-initiated bolus dosage. In some implementations, the display device 222 may also be used to communicate information regarding remaining battery life.


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 assembly 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 assembly 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 FIG. 1 as being held in a user's hand 5 so as to illustrate its size in accordance with some embodiments. This embodiment of the pump assembly 10 is compact so that the user can wear the portable pump assembly 10 (e.g., in the user's pocket, connected to a belt clip, adhered to the user's skin, or the like) without the need for carrying and operating a separate module. In such embodiments, the cap device 130 of the pump device 100 can be configured to mate with an infusion set 146. As shown in FIG. 1, the infusion set 146 can be a tubing system that connects the pump assembly 10 to the tissue or vasculature of the user (e.g., to deliver medicine into the tissue or vasculature under the user's skin). The infusion set 146 can include a flexible tube 147 that extends from the pump device 100 to a subcutaneous cannula 149 that may be retained by a skin adhesive patch (not shown) that secures the subcutaneous cannula 149 to the infusion site on the user's skin 20. The skin adhesive patch can retain the infusion cannula 149 in fluid communication with the tissue or vasculature of the user so that the medicine dispensed through the tube 147 passes through the cannula 149 and into the user's body. The cap device 130 can provide fluid communication between the output end 122 (FIG. 2) of the fluid cartridge 120 and the tube 147 of the infusion set 146.


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 FIG. 3, the controller device 200 (shown in an exploded view) houses a number of components that can be reused with a series of successive pump devices 100. In particular, the controller device 200 can include control circuitry 240 and a rechargeable battery pack 245, each arranged in the controller housing 210. The rechargeable battery pack 245 may provide electrical energy to components of the control circuitry 240, other components of the controller device (e.g., the display device 222 and other user interface components, sensors, or the like), and/or to components of the pump device 100. The control circuitry 240 may be configured to communicate control or power signals to the drive system of the pump device 100, or to receive power or feedback signals from the pump device 100.


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 FIG. 5). This type of closed-loop control can be executed by the control circuitry via any suitable control algorithm (e.g., a proportional-integral-derivative (PID), fuzzy logic, or model predictive control algorithm). For example, U.S. Pat. No. 8,548,544 provides various examples of suitable closed-loop techniques involving fuzzy logic and predictive models for automated insulin dispensation.


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 242, 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 242 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 FIGS. 4A-4C, the controller device 200 of the pump assembly 10 can be configured to receive user input triggering a temporary interruption of a closed-loop delivery mode of operations. For example, the user interface 220 can be employed to manually input a desired bolus dosage (e.g., in anticipation of a meal or to manually correct a high blood glucose level). As shown in FIG. 4A, the user may activate particular buttons 224 of the user interface 220 so as to select a particular menu option that prompts the user to input a value for the bolus dosage in terms of insulin units. Some examples of temporarily interrupting the closed-loop delivery mode to provide a manually-initiated bolus dosage are explained in further detail below in connections with FIGS. 5 and 6A-6B. Optionally, in this embodiment depicted in FIGS. 4A-4C, the controller device 200 can receive the bolus dosage value selected by the user and determine whether the requested bolus dosage may undesirably “stack” with previous dosages to cause an overdose of insulin (e.g., symptoms of hypoglycemia). Thus, for example, the controller device 200 may calculate a “stacking value” accounting for insulin previously delivered to the user during the closed-loop delivery mode of the pump assembly 10 in addition to the requested dosage entered by the user. In some implementations, the stacking value is calculated by aggregating the bolus dosage requested by the user together with the “effective insulin-on-board” (eIOB). The eIOB corresponds to 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:

Stacking Value=(Requested Bolus Dosage)+(eIOB).


eIOB=[Σ(Dosagen*Duration Factor(t)n)]−Estimated Basal Rate, where Dosagen represents the quantity of any insulin dosage among “n” number of dosages delivered to the user during the selected time period (“n” being any positive whole number), where Duration Factor(t)n, represents a factor discounting the dosage based on the amount of time “t” since its delivery, and where Estimated Basal Rate represents an estimate of the user's background insulin needs.


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 device 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), where Total Dose represents the quantity of insulin delivery during the time period “T,” and where Scale Down Factor represents a multiplier selected to scale down the total dose to a fractional value that only accounts for insulin delivered to meet the user's background insulin needs. For example, if the time period “T” is taken as 24 hours and the scale down factor is taken as 2.0, the estimated basal rate is calculated as the total daily dose divided by 48.0, which corresponds to the hourly rate needed to provide 50% of the total daily dose as basal insulin for fulfilling the user's background insulin needs. In some embodiments, the scale down factor can range from about 2.50 to about 1.50 (e.g., about 1.66).


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 FIG. 4B, if the value input by the user causes the stacking value to exceed a predetermined stacking threshold, the controller device 200 can output an alert to the user in the form of a textual alert message provided on the display device 222 and, optionally, an audible or vibratory alarm and a temporary illumination of the aforementioned inspection light device 230. In this example, the textual alert notifies the user of the amount eIOB and indicates that the manually entered bolus dosage is not permitted. In addition to providing the alert, the controller device 200 may also prompt the user to take a corrective action. For example, the user can select a button 224a, which causes the controller device 200 to respond by displaying various menu options to correct the non-permitted manual bolus dosage (e.g., an option to re-enter a corrected bolus dosage and an option to initiate a suggested bolus calculation, see FIG. 4C). Alternatively, the user can select a button 224b indicating that the user does not wish to continue with a manual bolus dosage, allowing the controller device 200 to cancel the attempt to initiate a manual bolus and thereby resume closed-loop delivery mode.


Referring now to FIG. 5, the control circuitry of an infusion pump system can implement a process 500 of operating the infusion pump system according to an interruptible closed-loop mode of control. Such a process 500, for example, can be implemented by the control circuitry 240 housed in the controller device 200 of an infusion pump assembly 10 (FIGS. 1-3). However, the description here is not necessarily limited to any particular infusion pump system with respect to process 500, and the process 500 may be implemented using, for example, an infusion pump system in which the control circuitry and drive system components are housed together in a reusable pump unit (see FIG. 7).


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 FIG. 5). This type of closed-loop control (often termed “artificial pancreas control”) can be executed by the control circuitry via any suitable control algorithm (e.g., a proportional-integral-derivative (PID), fuzzy logic, or model predictive control algorithm).


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 FIGS. 6A and 6B) and then automatically returns to the closed-loop delivery mode at operation 502.


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 memory 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.



FIG. 6A depicts a first example process 600a for interrupting the closed-loop delivery mode to provide a manually-initiated bolus dosage, for example, where medicine dosages (e.g., bolus dosages of insulin) are calculated in response to a request by the user and/or suggested by the controller device and confirmed by the user. In some embodiments, the controller device 200 may implement one or more operations of the process 600a to determine and suggest an insulin bolus dosage which includes a food offsetting component, a blood glucose correction component, and an eIOB component. 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. This component can be derived from one or more dosage parameters (e.g., insulin sensitivity and carbohydrate ratio), data indicative of a user's blood glucose level (e.g., the user's current blood glucose level) and the recent rate of change in the user's blood glucose level. As described above, the eIOB component corresponds to the net amount of remaining active insulin in the user's system over a selected time period immediately prior to the calculation. In some embodiments, the suggested bolus dosage value can be calculated based on at least two of the three components as previously described: the food offsetting component and/or the blood glucose correction component combined with the eIOB component. It should be understood from the description herein that the components can be contemporaneously calculated to provide the suggested bolus dosage value or, alternatively, calculated in discrete steps and then combined to provide the suggested bolus dosage value.


Referring in more detail to FIG. 6A, in operation 602, the user can optionally enter data indicative of food intake (e.g., a meal that is about to be consumed, a meal that has recently been consumed, or the like) using the user interface 220 of the controller device 200. In operation 604, the controller device 200 can determine a rate of change (e.g., increase or decrease) based on the dosage history and the blood glucose level. In operation 606, the controller device 200 determines the eIOB.


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), where Carbohydrate Intake represents the number of grams of carbohydrates consumed (or to be consumed) and Insulin to Carb. Ratio represents a user-specific ratio (which was preferably determined and stored during the closed-loop mode during this embodiment) of the amount of insulin required to offset the consumption of a gram of carbohydrates (e.g., 14.8 U/g or the like).


Blood Glucose Correction Component=(Current Blood Glucose Level−Target Glucose Level)*Insulin Sensitivity, where Current Blood Glucose Level represents the most recent blood glucose level, Target Glucose Level represents the user's desired blood glucose level, Insulin Sensitivity represents a user-specific value (which was preferably determined and stored during the closed-loop mode during this embodiment) that correlates the number of units of insulin required to alter the user's blood glucose level by 1 mg/dL.


eIOB Component=[Σ(Dosagen*Duration Factor(t)n)]−Estimated Basal Rate, where Dosagen represents the quantity of any insulin dosage among “n” number of dosages delivered to the user during the selected time period (“n” being any positive whole number), where Duration Factor(t)n, represents a factor discounting the dosage based on the amount of time “t” since its delivery, and where Estimated Basal Rate represents an estimate of the user's background insulin needs.


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 FIG. 5) at operation 620.



FIG. 6B depicts a second example process 600b for interrupting the closed-loop delivery mode to provide a manually-initiated bolus dosage, for example, where medicine dosages (e.g., bolus dosages of insulin) are entered manually by the user. As described above with reference to FIGS. 4A-4C, the controller device 200 may determine whether the manually entered bolus dosage is likely to stack with previous dosages implemented during closed-loop operations of the infusion pump system 1 to cause systems of hypoglycemia. If adverse symptoms are likely, the controller device 200 can alert the user and prevent delivery of the requested dosage.


Referring in more detail to FIG. 6B, in operation 650, the controller device 200 causes a menu option for manually inputting a bolus dosage to be displayed to the user via the display device 222 (see FIG. 4A). In operation 652, the controller device 200 receives user input indicating a bolus dosage requested by the user. In operation 654, the controller device 200 determines the eIOB. In operation 656, the controller device 200 determines whether the requested bolus dosage is permissible based on the eIOB in an attempt to prevent an overdose by stacking with previous dosages. In some embodiments, the controller device 200 determines whether the requested bolus dosage is permissible by calculating a likely future blood glucose level resulting from the dosage, and comparing the future blood glucose level to a predetermined minimum BG level (e.g., a BG level below which the user is likely to suffer symptoms of hypoglycemia, such as about 60 to 70 mg/dL). The future blood glucose level may be calculated using one or more suitable empirical models, predictive models (e.g., fuzzy logic matrices, classifiers, regressive predictors, neural networks and/or dynamic predictors, such as described in U.S. Pat. No. 8,548,544), and/or blood-glucose calculators based on user-specific parameters (e.g., insulin sensitivity). One non-limiting example is provided below:

Future BG Level=(eIOB+Requested Dose)*Insulin Sensitivity


In some embodiments, the controller device 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, where Minimum BG Level represents the blood glucose level below which a user may begin to experience symptoms of hypoglycemia.


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 FIG. 5) at operation 660. In operation 662, if the stacking requested bolus dosage is not permissible (656), the controller device 200 outputs and alert to the via the user interface 220 of the infusion pump system 1 (see FIG. 4B). Then, in operation 664, the controller device 200 prompts the user to enter a corrected bolus or to initiate a bolus calculation (see FIG. 4C). If the user elects to enter a corrected bolus dosage manually (666), the controller device 200 returns to operation 650, where the appropriate menu option is displayed. If the user elects to initiate a bolus calculation (668), the controller device progresses to a bolus calculator mode, such as described with reference to FIG. 6A. If the user neither elects to enter a corrected bolus manually (666) or to initiate a bolus calculation (668), the controller device 200 then automatically returns to the closed-loop delivery mode at operation 660. In some embodiments, the controller device 200 may automatically reduce the requested bolus dosage to a permissible amount without further user input.


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=2 Units 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


(Note that TIL can be implemented instead of IOB.)


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 FIG. 7, some embodiments of a portable infusion pump system 700 suitable for use in connection with one or more of the above-describes techniques (see, e.g., FIGS. 5, 6A and 6B) can employ a reusable pump apparatus (rather than a disposable pump device as previously described). In such circumstances, the infusion pump system 700 may comprise a reusable device that houses the control circuitry and the pump drive system within a single housing construct. Accordingly, the pump system 700 comprises a reusable pump device that houses both the control circuitry and the pump drive system (which may include a piston rod and one or more gears). Also, the pump system 700 can include a housing structure that defines a cavity in which a medicine cartridge can be received (not shown in FIG. 7; refer for example to cartridge 120 in FIG. 2). For example, the pump system 700 can be adapted to receive a medicine cartridge in the form of a carpule that is preloaded with insulin or another medicine. The pump drive system can act upon the fluid cartridge to controllably dispense medicine through an infusion set 146 and into the user's tissue or vasculature. In this embodiment, the user can wear the portable pump system 700 on the user's skin under clothing or in the user's pocket while receiving the medicine dispensed through the infusion set 146.


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 FIG. 7, the glucose monitoring device 50 can include the housing 52, the wireless communication device 54, and the sensor shaft 56 (similar to the embodiment described in connection with FIG. 1). In response to the measurements made by the sensor shaft 56, the glucose monitoring device 50 can employ the wireless communication device 54 to transmit data to a corresponding wireless communication device 747 housed in the pump system 700.


As previously described in connection with FIGS. 5, 6A and 6B, the control circuitry housed in the pump system 700 may be configured to facilitate the delivery of insulin dosages according to an interruptible closed-loop delivery mode of operations. That is, 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 requested bolus dosage or to initiate a bolus dosage calculation by the pump system 700 via the user interface 720 (e.g., the display device 722 and the user-interface buttons 724a-724e). The amount of eIOB, which corresponds to the net amount of remaining active insulin in the user's system over a selected time period, influences the any manually-initiated bolus dosage (which may be calculated by the pump system 700). For example, the pump system 700 may determine that a manually entered bolus dosage is likely to stack with the eIOB to cause the user to experience adverse symptoms. In this scenario, the pump system 700 may provide an alert to the user, prevent dispensation of the requested dosage, and prompt the user to pursue a corrected dosage. Similarly, the pump system 700 may account for the eIOB in any dosage calculations prompted by the user.


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.

Claims
  • 1. A method of operating a portable insulin infusion pump system, comprising: while operating an infusion pump system to automatically dispense insulin according to a closed-loop delivery mode, detecting a trigger event from a user to initiate a user-selected manual bolus dosage;for insulin dispensed during the closed-loop delivery mode, calculating an effective-insulin-on-board amount calculated as follows: Effective Insulin-on-Board=[Σ(Dosagen*Duration Factor(t)n)]−Estimated Basal Rate, where n is any positive whole number, and where Duration Factor(t)n, represents a factor discounting the dosage based on an amount of time (t) since its delivery;calculating, by the infusion pump system, a calculated dosage amount of the user-selected manual bolus dosage based at least in part upon user input of an estimated number of carbohydrates to be consumed and the calculated effective-insulin-on-board amount; anddispensing from the infusion pump system the calculated dosage amount.
  • 2. The method of claim 1, wherein 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 wherein the trigger event comprises actuation of a user interface button indicating a user's request to manually initiate a bolus dispensation that is independent from said feedback information of the user's blood glucose characteristic.
  • 3. The method of claim 1, wherein the trigger event comprises actuation of a user interface button indicating a user's request to initiate calculation of a suggested bolus dosage by the infusion pump system.
  • 4. The method of claim 1, wherein the infusion pump system comprises a controller including: a user interface display device, control circuitry arranged in a controller housing and being programmed to perform said calculation of the calculated dosage amount of the user-selected manual bolus dosage.
  • 5. The method of claim 4, wherein the infusion pump system comprises a pump device including: a pump housing that houses a drive system and an insulin reservoir, the controller housing being removably mountable to the pump housing so that the controller is electrically connected to the drive system.
  • 6. The method of claim 1, wherein the calculated dosage amount of the user-selected manual bolus dosage comprises a calculation of a suggested bolus dosage according to the following function: Suggested Bolus Dosage=(Food Offsetting Component)+(Blood Glucose Correction Component)−(Effective Insulin-on-board Component).
  • 7. The method of claim 1, wherein the Estimated Basal Rate is calculated according to the following function: Estimated Basal Rate=Total Dose/(T*Scale Down Factor), where T is a unit of time.
  • 8. A medical infusion pump system, comprising: a portable pump housing configured to receive medicine for dispensation to a user, the pump housing at least partially containing a pump drive system to dispense the medicine through a flow path to the user; anda 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 the controller autonomously provides insulin dosages to the user in response to feedback information of a user's blood glucose level;receive user input to initiate a user-prompted bolus dosage;calculate an effective-insulin-on-board amount calculated as follows: Effective Insulin-on-Board=[Σ(Dosagen*Duration Factor(t)n)]−Estimated Basal Rate, where n is any positive whole number, and where Duration Factor(t)n, represents a factor discounting the dosage based on an amount of time (t) since its delivery;receive a user input of a number of an estimated number of carbohydrates to be consumed for the user-prompted bolus dosage;calculate, by the infusion pump system, a calculated dosage amount of the user-prompted bolus dosage based upon both the estimated number of carbohydrates to be consumed and the effective-insulin-on-board amount; anddispense from the infusion pump system the user-prompted bolus dosage.
  • 9. The system of claim 8, wherein the calculated dosage amount of the user-prompted bolus dosage comprises a calculation of a suggested bolus dosage according to the following function: Suggested Bolus Dosage=(Food Offsetting Component)+(Blood Glucose Correction Component)−(Effective Insulin-on-board Component).
  • 10. The system of claim 8, wherein the Estimated Basal Rate is calculated according to the following function: Estimated Basal Rate=Total Dose/(T*Scale Down Factor), where T is a unit of time.
  • 11. The system of claim 8, wherein the input to initiate the user-prompted bolus dosage comprises actuation of a user interface button indicating a user request to manually enter a bolus dosage amount.
  • 12. The system of claim 8, wherein the input to initiate the user-prompted bolus dosage comprises actuation of a user interface button indicating a user request to initiate a calculation, by the infusion pump system, of a suggested bolus dosage.
  • 13. The system of claim 8, wherein the controller comprises a user interface including a display device and a plurality of buttons.
  • 14. The system of claim 13, wherein the controller comprises a controller housing that removably attaches to the pump housing.
  • 15. The system of claim 14, wherein the controller is electrically connected to the pump drive system when the controller housing is removably attached to the pump housing.
  • 16. The system of claim 15, wherein the controller is a reusable device and the pump housing and pump drive system are disposable and nonreusable.
  • 17. The system of claim 8, further comprising a monitoring device that communicates glucose information to the controller, the glucose information being indicative of a blood glucose level of the user.
  • 18. A portable infusion pump system, comprising: a portable pump housing configured to receive medicine for dispensation to a user, the pump housing at least partially containing a pump drive system to dispense the medicine through a flow path to the user;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 in response to feedback information of a user's blood glucose characteristic; anda user interface in communication with the control circuitry and being configured to receive user input to manually administer a bolus of insulin,wherein the control circuitry is configured to: calculate an effective-insulin-on-board amount calculated as follows: Effective Insulin-on-Board=[Σ(Dosagen*Duration Factor(t)n)]−Estimated Basal Rate, where n is any positive whole number, and where Duration Factor(t)n, represents a factor discounting the dosage based on an amount of time (t) since its delivery;receive manual bolus dosage information indicative of an estimated number of carbohydrates to be consumed received by the user interface;calculate a calculated dosage amount for the manual bolus dosage based upon the estimated number of carbohydrates to be consumed and the calculated effective-insulin-on-board amount; anddispense from the infusion pump system the manual bolus dosage.
  • 19. The system of claim 18, wherein the calculated dosage amount of the user-selected manual bolus dosage comprises a calculation of a suggested bolus dosage according to the following function: Suggested Bolus Dosage=(Food Offsetting Component)+(Blood Glucose Correction Component)−(Effective Insulin-on-board Component).
  • 20. The system of claim 18, wherein the Estimated Basal Rate is calculated according to the following function: Estimated Basal Rate=Total Dose/(T*Scale Down Factor), where T is a unit of time.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of and claims priority to U.S. application Ser. No. 15/848,622, filed on Dec. 20, 2017, now U.S. Pat. No. 10,603,433, issued Mar. 31, 2020, which is a continuation application of and claims priority to U.S. application Ser. No. 14/699,341, filed on Apr. 29, 2015, now U.S. Pat. No. 9,878,097, issued Jan. 30, 2018.

US Referenced Citations (770)
Number Name Date Kind
2605765 Kollsman Aug 1952 A
3688764 Reed Sep 1972 A
3886938 Szabo et al. Jun 1975 A
4077405 Haerten et al. Mar 1978 A
4151845 Clemens May 1979 A
4231368 Becker Nov 1980 A
4235234 Martin et al. Nov 1980 A
4265241 Portner et al. May 1981 A
4300554 Hessberg et al. Nov 1981 A
4313439 Babb et al. Feb 1982 A
4373527 Fischell Feb 1983 A
4398908 Siposs Aug 1983 A
4435173 Siposs et al. Mar 1984 A
4443218 Decant et al. Apr 1984 A
4475901 Kraegen et al. Oct 1984 A
4493704 Beard et al. Jan 1985 A
4529401 Leslie et al. Jul 1985 A
4552561 Eckenhoff et al. Nov 1985 A
4564054 Gustavsson Jan 1986 A
4652260 Fenton et al. Mar 1987 A
4668220 Hawrylenko May 1987 A
4681569 Coble et al. Jul 1987 A
4731726 Allen, III Mar 1988 A
4734092 Millerd Mar 1988 A
4749109 Kamen Jun 1988 A
4768506 Parker et al. Sep 1988 A
4838857 Strowe et al. Jun 1989 A
4850817 Nason et al. Jul 1989 A
4902278 Maget et al. Feb 1990 A
5029591 Teves Jul 1991 A
5045064 Idriss Sep 1991 A
5088981 Howson et al. Feb 1992 A
5088990 Hivale et al. Feb 1992 A
5176632 Bernardi Jan 1993 A
5190522 Wojcicki et al. Mar 1993 A
5209230 Swedlow et al. May 1993 A
5225763 Krohn et al. Jul 1993 A
5250027 Lewis et al. Oct 1993 A
5261882 Sealfon Nov 1993 A
5314412 Rex May 1994 A
5335994 Weynant nee Girones Aug 1994 A
5338157 Blomquist Aug 1994 A
5342180 Daoud Aug 1994 A
5349575 Park Sep 1994 A
5389078 Zalesky et al. Feb 1995 A
5395340 Lee Mar 1995 A
5411487 Castagna May 1995 A
5527288 Gross et al. Jun 1996 A
5545143 Fischell et al. Aug 1996 A
5551850 Williamson et al. Sep 1996 A
5554123 Herskowitz Sep 1996 A
5569186 Lord et al. Oct 1996 A
5626566 Petersen et al. May 1997 A
5637095 Nason et al. Jun 1997 A
5656032 Kriesel et al. Aug 1997 A
5665065 Colman et al. Sep 1997 A
5672167 Athayde et al. Sep 1997 A
5693018 Kriesel et al. Dec 1997 A
5718562 Lawless et al. Feb 1998 A
5741216 Hemmingsen et al. Apr 1998 A
5766155 Hyman et al. Jun 1998 A
5772635 Dastur et al. Jun 1998 A
5800420 Gross et al. Sep 1998 A
5816306 Giacomel Oct 1998 A
5822715 Worthington et al. Oct 1998 A
5851197 Marano et al. Dec 1998 A
5852803 Ashby et al. Dec 1998 A
5858001 Tsals et al. Jan 1999 A
5858005 Kriesel Jan 1999 A
5873731 Prendergast Feb 1999 A
5893838 Daoud et al. Apr 1999 A
5914941 Janky Jun 1999 A
5919167 Mulhauser et al. Jul 1999 A
5925018 Ungerstedt Jul 1999 A
5928201 Poulsen et al. Jul 1999 A
5947934 Hansen et al. Sep 1999 A
5951530 Steengaard et al. Sep 1999 A
5957889 Poulsen et al. Sep 1999 A
5984894 Poulsen Nov 1999 A
5984897 Petersen et al. Nov 1999 A
5997475 Bortz Dec 1999 A
6003736 Ljunggren Dec 1999 A
6010485 Buch-Rasmussen et al. Jan 2000 A
6033377 Rasmussen et al. Mar 2000 A
6045537 Klitmose Apr 2000 A
6056728 Von Schuckmann May 2000 A
6074372 Hansen Jun 2000 A
6106498 Friedli et al. Aug 2000 A
6110149 Klitgaard et al. Aug 2000 A
6126595 Amano Oct 2000 A
6127061 Shun et al. Oct 2000 A
6156014 Petersen et al. Dec 2000 A
6171276 Lippe et al. Jan 2001 B1
6231540 Smedegaard May 2001 B1
6233471 Berner et al. May 2001 B1
6248067 Causey et al. Jun 2001 B1
6248090 Jensen et al. Jun 2001 B1
6248093 Moberg Jun 2001 B1
6251113 Appelbaum et al. Jun 2001 B1
6269340 Ford et al. Jul 2001 B1
6277098 Klitmose et al. Aug 2001 B1
6292440 Lee Sep 2001 B1
6302855 Lav et al. Oct 2001 B1
6302869 Klitgaard Oct 2001 B1
6368314 Kipfer et al. Apr 2002 B1
6375638 Nason et al. Apr 2002 B2
6379301 Worthington et al. Apr 2002 B1
6379339 Klitgaard et al. Apr 2002 B1
6381496 Meadows et al. Apr 2002 B1
6397098 Uber et al. May 2002 B1
6404098 Kayama et al. Jun 2002 B1
6427088 Bowman et al. Jul 2002 B1
D461241 Moberg et al. Aug 2002 S
D461891 Moberg Aug 2002 S
6434528 Sanders Aug 2002 B1
6436072 Kullas et al. Aug 2002 B1
6461329 Van et al. Oct 2002 B1
6461331 Van Antwerp Oct 2002 B1
6474219 Klitmose et al. Nov 2002 B2
6485461 Mason et al. Nov 2002 B1
6491684 Joshi et al. Dec 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
6537268 Gibson et al. Mar 2003 B1
6540672 Simonsen et al. Apr 2003 B1
6544212 Galley et al. Apr 2003 B2
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
6558345 Houben 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
6572545 Knobbe et al. Jun 2003 B2
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
6587199 Luu Jul 2003 B1
6589229 Connelly et al. Jul 2003 B1
6599281 Struys et al. Jul 2003 B1
6605067 Larsen Aug 2003 B1
6605072 Struys et al. Aug 2003 B2
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
6669668 Kleeman et al. Dec 2003 B1
6669669 Flaherty et al. Dec 2003 B2
6685674 Douglas et al. Feb 2004 B2
6687546 Lebel et al. Feb 2004 B2
6689100 Connelly 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
6752785 Van et al. Jun 2004 B2
6752787 Causey, III et al. Jun 2004 B1
6758810 Lebel et al. Jul 2004 B2
6761286 Py 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
6796957 Carpenter 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
6923763 Kovatchev et al. Aug 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
7060059 Keith et al. Jun 2006 B2
7066910 Bauhahn et al. Jun 2006 B2
7070580 Nielsen Jul 2006 B2
7098803 Mann et al. Aug 2006 B2
7104972 Møller et al. Sep 2006 B2
7109878 Mann et al. Sep 2006 B2
7123964 Betzold et al. Oct 2006 B2
7128727 Flaherty et al. Oct 2006 B2
7133329 Skyggebjerg et al. Nov 2006 B2
7172572 Diamond et al. Feb 2007 B2
7179226 Crothall et al. Feb 2007 B2
7204823 Estes et al. Apr 2007 B2
7220240 Struys et al. May 2007 B2
7232423 Mernoe et al. Jun 2007 B2
7267665 Steil et al. Sep 2007 B2
7278983 Ireland et al. Oct 2007 B2
7291107 Hellwig et al. Nov 2007 B2
7354420 Steil et al. Apr 2008 B2
7402153 Steil et al. Jul 2008 B2
7404796 Ginsberg Jul 2008 B2
7429255 Thompson Sep 2008 B2
7491187 Van et al. Feb 2009 B2
7494481 Moberg et al. Feb 2009 B2
7553281 Hellwig et al. Jun 2009 B2
7569030 Lebel et al. Aug 2009 B2
7569050 Moberg et al. Aug 2009 B2
7570980 Ginsberg Aug 2009 B2
7591801 Brauker et al. Sep 2009 B2
7597682 Moberg Oct 2009 B2
7641649 Moberg et al. Jan 2010 B2
7651845 Doyle et al. Jan 2010 B2
7654982 Carlisle et al. Feb 2010 B2
7670288 Sher Mar 2010 B2
7708717 Estes et al. May 2010 B2
7785313 Mastrototaro Aug 2010 B2
7789859 Estes et al. Sep 2010 B2
7794426 Briones et al. Sep 2010 B2
7806853 Wittmann et al. Oct 2010 B2
7806854 Damiano et al. Oct 2010 B2
7815602 Mann et al. Oct 2010 B2
7819843 Mann et al. Oct 2010 B2
7828528 Estes et al. Nov 2010 B2
7850641 Lebel et al. Dec 2010 B2
7904061 Zaffino et al. Mar 2011 B1
7938797 Estes May 2011 B2
7938801 Hawkins et al. May 2011 B2
7946985 Mastrototaro et al. May 2011 B2
7959598 Estes Jun 2011 B2
7967812 Jasperson et al. Jun 2011 B2
7976492 Brauker et al. Jul 2011 B2
8029459 Rush et al. Oct 2011 B2
8062249 Wilinska et al. Nov 2011 B2
8105268 Lebel et al. Jan 2012 B2
8114023 Ward et al. Feb 2012 B2
8152789 Starkweather et al. Apr 2012 B2
8206296 Jennewine Jun 2012 B2
8206350 Mann et al. Jun 2012 B2
8208984 Blomquist et al. Jun 2012 B2
8221385 Estes Jul 2012 B2
8226556 Hayes et al. Jul 2012 B2
8246540 Ginsberg Aug 2012 B2
8262616 Grant et al. Sep 2012 B2
8267893 Moberg et al. Sep 2012 B2
8273052 Damiano et al. Sep 2012 B2
D669165 Sims et al. Oct 2012 S
8282626 Wenger et al. Oct 2012 B2
8287487 Estes Oct 2012 B2
8318154 Frost et al. Nov 2012 B2
8348844 Kunjan et al. Jan 2013 B2
8348886 Kanderian et al. Jan 2013 B2
8348923 Kanderian et al. Jan 2013 B2
8352011 Van et al. Jan 2013 B2
8372039 Mernoe et al. Feb 2013 B2
8417311 Rule Apr 2013 B2
8430847 Mernoe et al. Apr 2013 B2
8439834 Schmelzeisen-Redeker et al. May 2013 B2
8439897 Yodfat et al. May 2013 B2
8454576 Mastrototaro et al. Jun 2013 B2
8460231 Brauker et al. Jun 2013 B2
8467972 Rush Jun 2013 B2
8475409 Tsoukalis Jul 2013 B2
8480655 Jasperson et al. Jul 2013 B2
8548544 Kircher et al. Oct 2013 B2
8548552 Tsoukalis Oct 2013 B2
8551045 Sie et al. Oct 2013 B2
8560082 Wei Oct 2013 B2
8560131 Haueter et al. Oct 2013 B2
8562558 Kamath et al. Oct 2013 B2
8562587 Kovatchev et al. Oct 2013 B2
8568713 Frost et al. Oct 2013 B2
8579854 Budiman et al. Nov 2013 B2
8579879 Palerm et al. Nov 2013 B2
8585591 Sloan et al. Nov 2013 B2
8585593 Kovatchev et al. Nov 2013 B2
8585637 Wilinska et al. Nov 2013 B2
8585638 Blomquist Nov 2013 B2
8597274 Sloan et al. Dec 2013 B2
8615366 Galley et al. Dec 2013 B2
8622988 Hayter Jan 2014 B2
8679016 Mastrototaro et al. Mar 2014 B2
8679060 Mernoe et al. Mar 2014 B2
8690820 Cinar et al. Apr 2014 B2
8694115 Goetz et al. Apr 2014 B2
8706691 McDaniel et al. Apr 2014 B2
8718949 Blomquist et al. May 2014 B2
8721585 Brauker et al. May 2014 B2
8727982 Jennewine May 2014 B2
8734422 Hayter May 2014 B2
8734428 Blomquist May 2014 B2
8747315 Brauker et al. Jun 2014 B2
8762070 Doyle et al. Jun 2014 B2
8771222 Kanderian et al. Jul 2014 B2
8777896 Starkweather et al. Jul 2014 B2
8777924 Kanderian et al. Jul 2014 B2
8784364 Kamen et al. Jul 2014 B2
8784369 Starkweather et al. Jul 2014 B2
8784370 Lebel et al. Jul 2014 B2
8795224 Starkweather et al. Aug 2014 B2
8795252 Hayter Aug 2014 B2
8808230 Rotstein Aug 2014 B2
8876755 Taub et al. Nov 2014 B2
8882741 Brauker et al. Nov 2014 B2
8903501 Perryman Dec 2014 B2
8919180 Gottlieb et al. Dec 2014 B2
8920401 Brauker et al. Dec 2014 B2
8926585 Brauker et al. Jan 2015 B2
8945094 Nordh Feb 2015 B2
8956291 Valk et al. Feb 2015 B2
8956321 Dejournett Feb 2015 B2
8977504 Hovorka Mar 2015 B2
8992475 Mann et al. Mar 2015 B2
9034323 Frost et al. May 2015 B2
9050413 Brauker et al. Jun 2015 B2
9056165 Steil et al. Jun 2015 B2
9056168 Kircher et al. Jun 2015 B2
9078963 Estes Jul 2015 B2
9089305 Hovorka Jul 2015 B2
9149233 Kamath et al. Oct 2015 B2
9155843 Brauker et al. Oct 2015 B2
9247901 Kamath et al. Feb 2016 B2
9314566 Wenger et al. Apr 2016 B2
9320471 Hayes et al. Apr 2016 B2
9333298 Kim et al. May 2016 B2
9415157 Mann et al. Aug 2016 B2
9474855 McCann et al. Oct 2016 B2
9480796 Starkweather et al. Nov 2016 B2
9486172 Cobelli et al. Nov 2016 B2
9486578 Finan et al. Nov 2016 B2
9561324 Estes Feb 2017 B2
9878097 Estes Jan 2018 B2
9968729 Estes May 2018 B2
10449294 Estes Oct 2019 B1
10569015 Estes Feb 2020 B2
20010003542 Kita Jun 2001 A1
20010041869 Causey et al. Nov 2001 A1
20010056262 Cabiri Dec 2001 A1
20020004651 Ljndggreen et al. Jan 2002 A1
20020007154 Hansen et al. Jan 2002 A1
20020013784 Swanson Jan 2002 A1
20020016534 Trepagnier et al. Feb 2002 A1
20020016568 Lebel et al. Feb 2002 A1
20020032402 Daoud et al. Mar 2002 A1
20020040208 Flaherty et al. Apr 2002 A1
20020046315 Miller et al. Apr 2002 A1
20020055845 Ueda et al. May 2002 A1
20020072720 Hague et al. Jun 2002 A1
20020091358 Klitmose Jul 2002 A1
20020107476 Mann et al. Aug 2002 A1
20020126036 Flaherty et al. Sep 2002 A1
20020156462 Stultz Oct 2002 A1
20020164973 Janik et al. Nov 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
20030121055 Kaminski et al. Jun 2003 A1
20030125672 Adair et al. Jul 2003 A1
20030161744 Vilks et al. Aug 2003 A1
20030198558 Nason et al. Oct 2003 A1
20030199825 Flaherty Oct 2003 A1
20030208113 Mault et al. Nov 2003 A1
20030216683 Shekalim Nov 2003 A1
20030216686 Lynch et al. Nov 2003 A1
20030236498 Gross et al. Dec 2003 A1
20040006316 Patton Jan 2004 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
20040068230 Estes 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
20040158207 Hunn 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
20040187952 Jones Sep 2004 A1
20040204673 Flaherty Oct 2004 A1
20040204744 Penner et al. Oct 2004 A1
20040220551 Flaherty et al. Nov 2004 A1
20040235446 Flaherty et al. Nov 2004 A1
20040260233 Garibotto et al. Dec 2004 A1
20050010165 Hickle Jan 2005 A1
20050021005 Flaherty et al. Jan 2005 A1
20050021104 DiLorenzo Jan 2005 A1
20050022274 Campbell et al. Jan 2005 A1
20050038332 Saidara et al. Feb 2005 A1
20050049179 Davidson et al. Mar 2005 A1
20050065760 Murtfeldt et al. Mar 2005 A1
20050090808 Malave et al. Apr 2005 A1
20050090851 Devlin Apr 2005 A1
20050095063 Fathallah May 2005 A1
20050101933 Marrs et al. May 2005 A1
20050107743 Fangrow, Jr. May 2005 A1
20050113745 Stultz May 2005 A1
20050124866 Elaz et al. Jun 2005 A1
20050137530 Campbell et al. Jun 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
20050234404 Vilks et al. Oct 2005 A1
20050238507 DiIanni et al. Oct 2005 A1
20050240544 Kil 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
20050277890 Stewart et al. Dec 2005 A1
20060036214 Mogensen et al. Feb 2006 A1
20060041229 Garibotto et al. Feb 2006 A1
20060042633 Bishop et al. Mar 2006 A1
20060069351 Safabash et al. Mar 2006 A9
20060069382 Pedersen Mar 2006 A1
20060074381 Malave et al. Apr 2006 A1
20060075269 Liong et al. Apr 2006 A1
20060095014 Ethelfeld May 2006 A1
20060125654 Liao et al. Jun 2006 A1
20060135913 Ethelfeld Jun 2006 A1
20060142698 Ethelfeld Jun 2006 A1
20060151545 Imhof et al. Jul 2006 A1
20060173406 Hayes et al. Aug 2006 A1
20060173410 Moberg et al. Aug 2006 A1
20060178633 Garibotto et al. Aug 2006 A1
20060184104 Cheney et al. Aug 2006 A1
20060184119 Remde et al. Aug 2006 A1
20060200073 Radmer et al. Sep 2006 A1
20060206054 Shekalim Sep 2006 A1
20060214511 Dayan Sep 2006 A1
20060247574 Maule et al. Nov 2006 A1
20060247581 Pedersen et al. Nov 2006 A1
20060253086 Moberg et al. Nov 2006 A1
20060258973 Volt Nov 2006 A1
20060258976 Shturman et al. Nov 2006 A1
20060264835 Nielsen et al. Nov 2006 A1
20060264890 Moberg et al. Nov 2006 A1
20060264894 Moberg et al. Nov 2006 A1
20070016127 Staib et al. Jan 2007 A1
20070060870 Tolle et al. Mar 2007 A1
20070073228 Mernoe et al. Mar 2007 A1
20070073235 Estes et al. Mar 2007 A1
20070073236 Mernoe et al. Mar 2007 A1
20070078818 Zivitz et al. Apr 2007 A1
20070079836 Reghabi et al. Apr 2007 A1
20070088271 Richards Apr 2007 A1
20070093750 Jan et al. Apr 2007 A1
20070093786 Goldsmith et al. Apr 2007 A1
20070100222 Mastrototaro et al. May 2007 A1
20070106218 Yodfat et al. May 2007 A1
20070112298 Mueller et al. May 2007 A1
20070118364 Wise et al. May 2007 A1
20070118405 Campbell et al. May 2007 A1
20070123819 Mernoe et al. May 2007 A1
20070124002 Estes et al. May 2007 A1
20070142776 Kovelman et al. Jun 2007 A9
20070155307 Ng et al. Jul 2007 A1
20070156092 Estes et al. Jul 2007 A1
20070156094 Safabash et al. Jul 2007 A1
20070166170 Nason et al. Jul 2007 A1
20070167905 Estes et al. Jul 2007 A1
20070167912 Causey et al. Jul 2007 A1
20070169607 Keller et al. Jul 2007 A1
20070173761 Kanderian, Jr. et al. Jul 2007 A1
20070179444 Causey et al. Aug 2007 A1
20070191702 Yodfat et al. Aug 2007 A1
20070219432 Thompson Sep 2007 A1
20070219480 Kamen et al. Sep 2007 A1
20070233521 Wehba et al. Oct 2007 A1
20070239116 Follman et al. Oct 2007 A1
20070248238 Abreu Oct 2007 A1
20070252774 Qi et al. Nov 2007 A1
20070255250 Moberg et al. Nov 2007 A1
20070282299 Hellwig Dec 2007 A1
20070287931 Dilorenzo Dec 2007 A1
20080009824 Moberg et al. Jan 2008 A1
20080015422 Wessel Jan 2008 A1
20080027574 Thomas Jan 2008 A1
20080031481 Warren et al. Feb 2008 A1
20080045891 Maule et al. Feb 2008 A1
20080051697 Mounce et al. Feb 2008 A1
20080051698 Mounce et al. Feb 2008 A1
20080051714 Moberg et al. Feb 2008 A1
20080051716 Stutz Feb 2008 A1
20080051730 Bikovsky Feb 2008 A1
20080051738 Griffin Feb 2008 A1
20080077081 Mounce et al. Mar 2008 A1
20080097326 Moberg et al. Apr 2008 A1
20080097375 Bikovsky Apr 2008 A1
20080097381 Moberg et al. Apr 2008 A1
20080103022 Dvorak et al. May 2008 A1
20080109050 John May 2008 A1
20080125700 Moberg et al. May 2008 A1
20080125701 Moberg et al. May 2008 A1
20080129535 Thompson et al. Jun 2008 A1
20080172027 Blomquist Jul 2008 A1
20080177149 Weinert et al. Jul 2008 A1
20080177165 Blomquist et al. Jul 2008 A1
20080183060 Steil et al. Jul 2008 A1
20080188796 Steil et al. Aug 2008 A1
20080198012 Kamen Aug 2008 A1
20080201325 Doniger et al. Aug 2008 A1
20080208627 Skyggebjerg Aug 2008 A1
20080215035 Yodfat et al. Sep 2008 A1
20080234630 Iddan et al. Sep 2008 A1
20080255516 Yodfat et al. Oct 2008 A1
20080269683 Bikovsky Oct 2008 A1
20080269687 Chong et al. Oct 2008 A1
20080269714 Mastrototaro et al. Oct 2008 A1
20080269723 Mastrototaro et al. Oct 2008 A1
20080294094 Mhatre et al. Nov 2008 A1
20080294109 Estes et al. Nov 2008 A1
20080294142 Patel et al. Nov 2008 A1
20080300572 Rankers et al. Dec 2008 A1
20080306434 Dobbles et al. Dec 2008 A1
20080306444 Brister Dec 2008 A1
20080312512 Brukalo et al. Dec 2008 A1
20080312634 Helmerson et al. Dec 2008 A1
20080319381 Yodfat et al. Dec 2008 A1
20080319383 Byland et al. Dec 2008 A1
20080319384 Yodfat et al. Dec 2008 A1
20080319394 Yodfat et al. Dec 2008 A1
20080319414 Yodfat et al. Dec 2008 A1
20080319416 Yodfat et al. Dec 2008 A1
20090036760 Hayter Feb 2009 A1
20090036870 Mounce et al. Feb 2009 A1
20090043291 Thompson Feb 2009 A1
20090048584 Thompson Feb 2009 A1
20090069745 Estes et al. Mar 2009 A1
20090069746 Miller et al. Mar 2009 A1
20090069749 Miller et al. Mar 2009 A1
20090069784 Estes et al. Mar 2009 A1
20090069785 Miller et al. Mar 2009 A1
20090069787 Estes et al. Mar 2009 A1
20090076453 Mejlhede et al. Mar 2009 A1
20090076849 Diller Mar 2009 A1
20090082728 Bikovsky Mar 2009 A1
20090093756 Minaie et al. Apr 2009 A1
20090099507 Koops Apr 2009 A1
20090105636 Hayter et al. Apr 2009 A1
20090112333 Sahai Apr 2009 A1
20090118664 Estes et al. May 2009 A1
20090143916 Boll et al. Jun 2009 A1
20090156990 Wenger et al. Jun 2009 A1
20090164190 Hayter Jun 2009 A1
20090177142 Blomquist et al. Jul 2009 A1
20090177154 Blomquist Jul 2009 A1
20090192722 Shariati et al. Jul 2009 A1
20090198191 Chong et al. Aug 2009 A1
20090198215 Chong et al. Aug 2009 A1
20090221890 Saffer et al. Sep 2009 A1
20100010330 Rankers et al. Jan 2010 A1
20100057040 Hayter Mar 2010 A1
20100057041 Hayter Mar 2010 A1
20100094078 Weston Apr 2010 A1
20100121167 McGarraugh May 2010 A1
20100165795 Elder et al. Jul 2010 A1
20100168538 Keenan et al. Jul 2010 A1
20100168820 Maniak et al. Jul 2010 A1
20100174229 Hsu et al. Jul 2010 A1
20100174266 Estes Jul 2010 A1
20100179409 Kamath et al. Jul 2010 A1
20100211005 Edwards et al. Aug 2010 A1
20100249530 Rankers et al. Sep 2010 A1
20100273738 Valcke et al. Oct 2010 A1
20100286601 Yodfat Nov 2010 A1
20100286653 Kubel et al. Nov 2010 A1
20100298685 Hayter et al. Nov 2010 A1
20100298765 Budiman Nov 2010 A1
20100324382 Cantwell et al. Dec 2010 A1
20100324977 Dragt Dec 2010 A1
20100325864 Briones et al. Dec 2010 A1
20110009813 Rankers Jan 2011 A1
20110015511 Bousamra et al. Jan 2011 A1
20110040247 Mandro et al. Feb 2011 A1
20110071464 Palerm Mar 2011 A1
20110098637 Hill Apr 2011 A1
20110098674 Vicente et al. Apr 2011 A1
20110105955 Yudovsky et al. May 2011 A1
20110106050 Yodfat et al. May 2011 A1
20110118699 Yodfat et al. May 2011 A1
20110124996 Reinke et al. May 2011 A1
20110130716 Estes et al. Jun 2011 A1
20110163880 Halff et al. Jul 2011 A1
20110199194 Waldock et al. Aug 2011 A1
20110224523 Budiman Sep 2011 A1
20110313390 Roy et al. Dec 2011 A1
20110319813 Kamen et al. Dec 2011 A1
20120016304 Patel et al. Jan 2012 A1
20120029468 Diperna et al. Feb 2012 A1
20120046606 Arefieg Feb 2012 A1
20120065894 Tubb et al. Mar 2012 A1
20120078067 Kovatchev et al. Mar 2012 A1
20120123234 Atlas et al. May 2012 A1
20120150556 Galasso et al. Jun 2012 A1
20120172694 Desborough et al. Jul 2012 A1
20120172802 Blomquist Jul 2012 A1
20120185267 Kamen et al. Jul 2012 A1
20120197207 Stefanski Aug 2012 A1
20120203467 Kamath et al. Aug 2012 A1
20120209208 Stefanski Aug 2012 A1
20120227737 Mastrototaro et al. Sep 2012 A1
20120238851 Kamen et al. Sep 2012 A1
20120238853 Arefieg Sep 2012 A1
20120238999 Estes et al. Sep 2012 A1
20120245448 Shariati et al. Sep 2012 A1
20120245556 Kovatchev et al. Sep 2012 A1
20120245855 Kamath et al. Sep 2012 A1
20120246106 Atlas et al. Sep 2012 A1
20120259191 Shariati et al. Oct 2012 A1
20120277723 Skladnev et al. Nov 2012 A1
20120283694 Yodfat et al. Nov 2012 A1
20120289931 Robinson et al. Nov 2012 A1
20120302991 Blomquist et al. Nov 2012 A1
20120323590 Udani Dec 2012 A1
20120330270 Colton Dec 2012 A1
20130046281 Javitt Feb 2013 A1
20130053818 Estes Feb 2013 A1
20130053819 Estes Feb 2013 A1
20130053820 Estes et al. Feb 2013 A1
20130102867 Desborough et al. Apr 2013 A1
20130116649 Breton et al. May 2013 A1
20130138205 Kushwaha et al. May 2013 A1
20130159456 Daoud et al. Jun 2013 A1
20130165041 Bukovjan et al. Jun 2013 A1
20130204186 Moore et al. Aug 2013 A1
20130204202 Trombly et al. Aug 2013 A1
20130218126 Hayter et al. Aug 2013 A1
20130237932 Thueer et al. Sep 2013 A1
20130245563 Mercer et al. Sep 2013 A1
20130245604 Kouyoumjian et al. Sep 2013 A1
20130253418 Kamath et al. Sep 2013 A1
20130275139 Coleman Oct 2013 A1
20130281965 Kamen et al. Oct 2013 A1
20130297334 Galasso et al. Nov 2013 A1
20130338629 Agrawal et al. Dec 2013 A1
20130338630 Agrawal et al. Dec 2013 A1
20130345663 Agrawal et al. Dec 2013 A1
20140005633 Finan Jan 2014 A1
20140025015 Cross et al. Jan 2014 A1
20140031759 Kouyoumjian et al. Jan 2014 A1
20140039383 Dobbles et al. Feb 2014 A1
20140052091 Dobbles et al. Feb 2014 A1
20140052092 Dobbles et al. Feb 2014 A1
20140052093 Dobbles et al. Feb 2014 A1
20140052094 Dobbles et al. Feb 2014 A1
20140052095 Dobbles et al. Feb 2014 A1
20140066884 Keenan et al. Mar 2014 A1
20140066885 Keenan et al. Mar 2014 A1
20140066886 Roy et al. Mar 2014 A1
20140066887 Mastrototaro et al. Mar 2014 A1
20140066888 Parikh et al. Mar 2014 A1
20140066889 Grosman et al. Mar 2014 A1
20140066890 Sloan et al. Mar 2014 A1
20140066892 Keenan et al. Mar 2014 A1
20140088557 Mernoe et al. Mar 2014 A1
20140094766 Estes et al. Apr 2014 A1
20140107607 Estes Apr 2014 A1
20140114278 Dobbles et al. Apr 2014 A1
20140121635 Hayter May 2014 A1
20140128705 Mazlish May 2014 A1
20140128803 Dobbles et al. May 2014 A1
20140180203 Budiman et al. Jun 2014 A1
20140180240 Finan et al. Jun 2014 A1
20140228627 Soffer et al. Aug 2014 A1
20140228668 Wakizaka et al. Aug 2014 A1
20140235981 Hayter Aug 2014 A1
20140249500 Estes Sep 2014 A1
20140276553 Rosinko et al. Sep 2014 A1
20140276554 Finan et al. Sep 2014 A1
20140276555 Morales Sep 2014 A1
20140276583 Chen et al. Sep 2014 A1
20140309615 Mazlish Oct 2014 A1
20140323959 Lebel et al. Oct 2014 A1
20150018633 Kovachev et al. Jan 2015 A1
20150025471 Enggaard Jan 2015 A1
20150025495 Peyser Jan 2015 A1
20150030641 Anderson et al. Jan 2015 A1
20150045737 Stefanski Feb 2015 A1
20150073337 Saint et al. Mar 2015 A1
20150080789 Estes et al. Mar 2015 A1
20150120323 Galasso et al. Apr 2015 A1
20150136336 Huang May 2015 A1
20150148774 Yao May 2015 A1
20150157794 Roy et al. Jun 2015 A1
20150164414 Matthews Jun 2015 A1
20150165119 Palerm et al. Jun 2015 A1
20150217051 Mastrototaro et al. Aug 2015 A1
20150217052 Keenan et al. Aug 2015 A1
20150265767 Vazquez et al. Sep 2015 A1
20150265768 Vazquez et al. Sep 2015 A1
20150314062 Blomquist et al. Nov 2015 A1
20150320933 Estes Nov 2015 A1
20150328402 Nogueira et al. Nov 2015 A1
20150351683 Brauker et al. Dec 2015 A1
20150352282 Mazlish Dec 2015 A1
20150352283 Galasso Dec 2015 A1
20160000998 Estes Jan 2016 A1
20160030669 Harris et al. Feb 2016 A1
20160038673 Morales Feb 2016 A1
20160082187 Schaible et al. Mar 2016 A1
20160082188 Blomquist et al. Mar 2016 A1
20160158438 Monirabbasi et al. Jun 2016 A1
20160162662 Monirabbasi et al. Jun 2016 A1
20160213841 Geismar et al. Jul 2016 A1
20160256629 Grosman et al. Sep 2016 A1
20170182248 Rosinko Jun 2017 A1
20170189614 Mazlish et al. Jul 2017 A1
20170203036 Mazlish et al. Jul 2017 A1
Foreign Referenced Citations (98)
Number Date Country
2543545 May 2005 CA
1859943 Nov 2006 CN
19627619 Jan 1998 DE
19912459 Sep 2000 DE
10236669 Feb 2004 DE
202005012358 Oct 2005 DE
200401893 Dec 2004 DK
PA200401893 Dec 2004 DK
0062974 Oct 1982 EP
0098592 Jan 1984 EP
0275213 Jul 1988 EP
0496141 Jul 1992 EP
0612004 Aug 1994 EP
0580723 Oct 1995 EP
1045146 Dec 2000 EP
1136698 Sep 2001 EP
1177802 Feb 2002 EP
0721358 May 2002 EP
1495775 Jan 2005 EP
1527792 May 2005 EP
1754498 Feb 2007 EP
1818664 Aug 2007 EP
1824536 Aug 2007 EP
1951340 Aug 2008 EP
2764881 Aug 2014 EP
2585252 Jan 1987 FR
747701 Apr 1956 GB
2218831 Nov 1989 GB
09-504974 May 1997 JP
11-010036 Jan 1999 JP
2000-513974 Oct 2000 JP
2002-085556 Mar 2002 JP
2002-507459 Mar 2002 JP
2002-523149 Jul 2002 JP
2003-531691 Oct 2003 JP
2010-502361 Jan 2010 JP
2010-524639 Jul 2010 JP
WO 1990015928 Dec 1990 WO
WO 1997021457 Jun 1997 WO
9804301 Feb 1998 WO
WO 1998011927 Mar 1998 WO
WO 1998057683 Dec 1998 WO
9907425 Feb 1999 WO
WO 1999021596 May 1999 WO
WO 1999039118 Aug 1999 WO
WO 1999048546 Sep 1999 WO
0154753 Aug 2001 WO
WO 2001072360 Oct 2001 WO
WO 2001091822 Dec 2001 WO
WO 2001091833 Dec 2001 WO
WO 2002040083 May 2002 WO
WO 2002057627 Jul 2002 WO
0268015 Sep 2002 WO
0281012 Oct 2002 WO
0284336 Oct 2002 WO
WO 2002100469 Dec 2002 WO
0323728 Mar 2003 WO
0326728 Mar 2003 WO
0326726 Apr 2003 WO
WO 2003103763 Dec 2003 WO
2004041330 May 2004 WO
WO 2004056412 Jul 2004 WO
WO 2004093648 Nov 2004 WO
WO 2004110526 Dec 2004 WO
WO 2005002652 Jan 2005 WO
2005011779 Feb 2005 WO
2005011799 Feb 2005 WO
WO 2005039673 May 2005 WO
WO 2005072794 Aug 2005 WO
WO 2005072795 Aug 2005 WO
2006061354 Jun 2006 WO
2006067217 Jun 2006 WO
WO 2006075016 Jul 2006 WO
2006097453 Sep 2006 WO
WO 2006105792 Oct 2006 WO
WO 2006105793 Oct 2006 WO
WO 2006105794 Oct 2006 WO
2007005219 Jan 2007 WO
2007056247 May 2007 WO
2007056504 May 2007 WO
2007056592 May 2007 WO
2007071255 Jun 2007 WO
2007078992 Jul 2007 WO
2007141786 Dec 2007 WO
2008016621 Feb 2008 WO
2008073609 Jun 2008 WO
2008089184 Jul 2008 WO
2008134146 Nov 2008 WO
2009032402 Mar 2009 WO
2009035759 Mar 2009 WO
2010045460 Apr 2010 WO
2010097796 Sep 2010 WO
2014062399 Apr 2014 WO
2014074476 May 2014 WO
2014134459 Sep 2014 WO
2014172467 Oct 2014 WO
2015191459 Dec 2015 WO
2016004210 Jan 2016 WO
Non-Patent Literature Citations (41)
Entry
“Using the Deltec Cozmo Insulin Pump Correction Bolus Feature” 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.
European Extended Search Report in European Application No. 16787016.1, dated Mar. 21, 2018, 9 pages.
International Preliminary Report of Patentability in International Application No. PCT/US2016/029440, dated Nov. 9, 2017, 10 pages.
International Search Report and Written Opinion in International Application No. PCT/US2016/029440, dated Sep. 27, 2016, 12 pages.
Invitation to Pay Additional Fees and where applicable, protest fee in International Application No. PCT/US2016/029440 dated Jul. 28, 2016, 2 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.
“Minimed Inc. Introduces 407C Infusion Pump for General Medication Use” [online]. Business Wire, AllBusiness.com, Aug. 10, 1999 [retrieved on Feb. 28, 2011], Retrieved from the Internet: <URL: http://www.allbusiness.com/company-activities-management/product-management/6734565-1.html>.
Accu-Chek Spirit, “Pump Therapy Made for You,” Roche, 2006, 6 pages.
Animas Corporation, IR1200 User Guide Manual, pp. 29-31, revised Sep. 2006.
Brown et al., “CGM, Pumps, and SMBG.” American Diabetes Association—71st Scientific Sessions, San Diego, CA, Jun. 24-28, 2011, 38 pages.
Copp et al., “Simultaneous Model Predictive Control and Moving Horizon Estimation for Blood Glucose Regulation in Type 1 Diabetes,” Optim. Control Appl. Meth. 2016, 15 pages.
Cox et al. “Prediction of Severe Hypoglycemia.” Diabetes Care, vol. 30, No. 6, Jun. 2007, 4 pages.
Dassau et al., “12-Week 24/7 Ambulatory Artificial Pancreas With Weekly Adaptation of Insulin Delivery Settings: Effect on Hemoglobin Alc and Hypoglycemia” Diabetes Care, Dec. 1, 2017, 40(12):1719-26.
DOCNEWS; The latest in high-tech and convenient devices; American Diabetes Assoc.; 2(7); retrieved from the internet: (http://web.archive.org/web/20080526162751/http://docnews.diabetesjournals.org/cgi/content/full/2/7/13?); 3 pgs.; Jul. 1, 2005.
Duden Deutsches Universaiworterbuch, Dudenveriag, Mannheim, 1989, p. 822.
Dumont, “Feedback control for clinicians,” Journal of clinical monitoring and computing, Feb. 1, 2014, 28(1):5-11.
Fischer et al., “In Vivo Comparison of Different Algorithms for the Artificial Beta-Cell,” Artificial organs, May 1, 1985, 9(2):173-9.
Guarnieri et al.; Flexible versus rigid catheters for chronic administration of exogenous agents into central nervous system tissues (abstract only); J Neurosc Meth; 144(2); pp. 147-152; Jun. 2005.
Honan, Matthew. “Apple unveils iPhone” Jan. 9, 2007. MacCentral. Accessed Dec. 29, 2011. 2 pages.
Insulet Corporation; Innovative New System for Managing Diabetes Receives FDA Clearance; The OmniPod (Registered) Insulin Management System (press release); retrieved from the internet: (http://phx.corporate-ir.net/phoenix.zhtml?c=209336&p=irol-newsArticle_pf&ID=988708&highlight=); 2 pgs.; Feb. 1, 2005.
Insulet Corporation; OmniPod (Registered) Insulin Management System (quick-start guide); 2 pgs.; (Copyright) 2008.
Keith Hynes et al., “DiAs User Interface: A Patient-Centric Interface for Mobile Artificial Pancreas Systems,” J Diabetes Sci Tech 7(6):1416-1426, Nov. 2013.
Kovatchev et al., “Safety of Outpatient Closed-Loop Control: First Randomized Crossover Trials of a Wearable Artificial Pancreas,” Diabetes Care 37(7):1789-1796, Jul. 2014.
OmniPod Insulin Management System—Investor Relations—Press Release, Feb. 1, 2005, http://investors.insulet.com/phoenix.zhtml?c=209336&p=irol-newsA-rticle&ID=988708&highlight= 1 page.
OmniPod Quick Start Guide, 2007, 2 pages.
Oxford Advanced Learners Dictionary, 4th Ed., Oxford University Press, Oxford, 1989, p. 178.
Percival et al., “Closed-Loop Control and Advisory Mode Evaluation of an Artificial Pancreatic Beta Cell: Use Of Proportional-Integral-Derivative Equivalent Model-Based Controllers,” J Diabetes Sci Tech 2(4):636-644, Jul. 2008.
Salzsieder et al., “Estimation of individually adapted control parameters for an artificial beta cell,” Biomed. Biochim. Acta, Jan. 1, 1984, 43(5):585-596.
Shiavon et al., “Quantitative Estimation of Insulin Sensitivity in Type 1 Diabetic Subjects Wearing a Sensor-Augmented Insulin Pump,” Diabetes care, May 1, 2014, 37(5):1216-23.
The Content of Investigational Device Exemption (IDE) and Premarket Approval (PMA) Application for Low Glucose Suspend (LGS) Device System. Rockville, MD, Food and Drug Administration, 2011, 59 pages.
The Medtronic Diabetes Connection, 2006, 6 pages.
U.S. Appl. No. 11/362,616.
Vozeh et al., “Feedback Control Methods for Drug Dosage Optimisation, Concepts, Classifications and Clinical Application,” Clinical pharmacokinetics, Nov. 1, 1985, 10(6):457-76.
Xilas Temp Touch, “The latest in high-tech and convenient devices,” DOCNews, vol. 2, No. 7, Jul. 1, 2005, http://docnews.diabetesioumals.ord/cgi/content/full/2/7/13, 3 pages.
Related Publications (1)
Number Date Country
20200188588 A1 Jun 2020 US
Continuations (2)
Number Date Country
Parent 15848622 Dec 2017 US
Child 16796184 US
Parent 14699341 Apr 2015 US
Child 15848622 US