Patent Grant
11147914
This document relates to an infusion pump system, such as a portable infusion pump system for dispensing a medicine.
Pump devices are commonly used to deliver one or more fluids to a targeted individual. For example, a medical infusion pump device may be used to deliver a medicine to a patient as part of a medical treatment. The medicine that is delivered by the infusion pump device can depend on the condition of the patient and the desired treatment plan. For example, infusion pump devices have been used to deliver insulin to the vasculature of diabetes patients so as to regulate blood-glucose levels.
Users of infusion pump devices often need to communicate with the infusion pump via a user interface to control the operations of the infusion pump in a safe and effective manner. For example, a user may press a series of buttons on the user interface to enter food intake data into the infusion pump, such as a number of grams of carbohydrates that is indicative of a recently or soon-to-be consumed meal. The food intake data can be combined by the infusion pump system with other parameters to calculate a suggested bolus dosage of insulin based on the grams of carbohydrates entered by the user. In another example, a user may enter information into the infusion pump system via a user interface that indicates that the user is going to perform a level of physical exercise. In some circumstances, the infusion pump system may reduce the amount of a planned dispensation of insulin in response to the exercise information entered by the user.
Some embodiments of an infusion pump system may be configured to send and receive data communications using near field communication (“NFC”) technology. By incorporating NFC technology within the infusion pump system, user communications with the pump system can be enhanced and simplified. For example, NFC can facilitate the convenient sharing of user commands or other data to an infusion pump system a NFC that is equipped with NFC functionality. In some embodiments, pre-programmed NFC communicator devices (“NFC tags”) can be used to transfer data from the NFC tag to the infusion pump system via a simple hand motion or the like by the user of the infusion pump system. The data that is transferred may cause the infusion pump system to execute particular operations as defined by the data or in correspondence to the data. For example, a NFC tag can be configured to communicate a set of user input commands to an infusion pump system (e.g., user input commands that might otherwise be input via a series of menu selections and data entry steps on the user interface of the pump system) so as to rapidly indicate to the pump system that particular amount of food or carbohydrates will be consumed for a meal. In some embodiments, data can be written from the infusion pump system to a NFC tag. For example, a back-up copy of user settings that are used to configure an infusion pump system for a particular user may be downloaded using NFC from the infusion pump system and saved onto a NFC tag. In particular embodiments, the infusion pump system can be equipped with one or more accelerometers that can be used to activate the potential for NFC communications to take place when an acceleration at or above the threshold level is detected.
In particular embodiments, a medical infusion pump system may include a portable pump housing that defines a space to receive a medicine. The infusion pump system may include a pump drive system to dispense medicine from the portable housing when the medicine is received in the space. The infusion pump system may further include control circuitry that communicates control signals to the pump drive system to control dispensation of the medicine from the portable housing when the medicine is received in the space. Optionally, the infusion pump system may also include a near field communication (NFC) circuit electrically connected with the control circuitry to communicate infusion pump task data to the control circuitry. The NFC circuit can be configured to wirelessly receive the infusion pump task data from a NFC communicator device when the NFC circuit and NFC communicator device are positioned with in a NFC proximity range.
In some implementations, the system may optionally include the NFC communicator device that is separate from the pump housing. For example, the NFC communicator device can be a near field communication tag storing the infusion pump task data. The infusion pump task data may comprise a unique identifier that identifies the near field communication tag, and in response to receiving the unique identifier, the control circuitry may execute user interface operations that correspond to the unique identifier. Optionally, the user interface operations may comprise user interface settings for calculating a suggested bolus dispensation of the medicine. In another option, the infusion pump system may further include an accelerometer electrically connected to the control circuitry, wherein the accelerometer may be configured to detect acceleration movement of the portable housing and to communicate the detected movement to the control circuitry. In a further option, the control circuitry is configured to compare a characteristic value of the detected movement to a threshold movement value. The control circuitry may be configured to activate near field communication with the NFC communicator device based on the comparison of the characteristic value to the threshold movement value. Optionally, the control circuitry may be housed in a controller housing that is removably attachable to the portable housing.
In some implementations described herein, the system may optionally include a remote control device that is separate from the pump housing. The remote control device can be configured to wirelessly communicate with a wireless communication device connected to the control circuitry (for example, a wireless communication device that is different from the aforementioned the NFC circuit). Optionally, the remote control device may further include a second NFC circuit that is configured to wirelessly receive the infusion pump task data from the NFC communicator device when the second NFC circuit and NFC communicator device are positioned within the NFC proximity range. In some cases, the NFC proximity range has a maximum working distance of less than 12 inches. The infusion pump task data may be indicative of a value of carbohydrates of a food item.
In particular embodiments, a medical infusion pump system may include a pump device and a controller device. The pump device may include a pump housing that defines a space to receive a medicine, and a drive system positioned in the pump housing to dispense the medicine from the pump device when the medicine is received in the space of the pump housing. Optionally, the controller device may be removably attachable to the pump device. For example, the controller device may be removably attachable to the pump housing so as to electrically connect with the pump device. The controller device may house control circuitry configured to communicate control signals to the drive system positioned in the pump housing to control dispensation of the medicine from the pump device. The controller device may also house a NFC circuit electrically connected with the control circuitry to communicate infusion pump task data to the control circuitry. Optionally, the NFC circuit is configured to wirelessly receive the infusion pump task data from a NFC communicator device when the NFC circuit and NFC communicator device are positioned with in a NFC proximity range.
In some implementations, the system may further comprise the NFC communicator device that is separate from the pump device and the controller device. For example, the NFC communicator device may be a near field communication tag storing the infusion pump task data. Optionally, the infusion pump task data may comprise a unique identifier that identifies the near field communication tag, and in response to receiving the unique identifier, the control circuitry may execute user interface operations that correspond to the unique identifier. In one example, the user interface operations may comprise user interface settings for calculating a bolus dispensation of the medicine. Optionally, the system may further include at least one accelerometer electrically connected to the control circuitry. The accelerometer may be configured to detect acceleration movement of the portable pump housing and to communicate the detected movement to the control circuitry. The control circuitry may be configured to compare a characteristic value of the detected movement to a threshold movement value. The control circuitry may be configured to activate near field communication with the NFC communicator device based on the comparison of the characteristic value to the threshold movement value.
In various implementations of the system, the pump device may optionally be a one-time-use device equipped with one or more structures configured to prevent reuse of the pump device. Also, in some implementations, the controller device may optionally be a reusable controller device. For example, the controller device may include one or more of: a controller housing that is removably attachable to the pump housing in a fixed relationship; one or more electrical contacts disposed on the controller housing, the electrical contacts of the controller device being engageable with corresponding electrical contacts of the pump device when removably attached.
Additionally, particular embodiments described herein may include a method of controlling a portable infusion pump system. The method may include receiving input via near field communication (NFC) from a NFC tag storing data indicative of a task associated with using the portable infusion pump system. The method may optionally include controlling the portable infusion pump system to change an operation of the portable infusion pump system in based upon the data the input from the NFC tag. In some implementations, the method may further comprise prompting a user via a user interface display to confirm the operation change of the portable infusion pump system in response to receiving the input from the NFC tag. For example, the operation change to be confirmed via the user interface may include calculating or initiating a bolus dispensation of a medicine from the portable infusion pump system.
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 may be configured to send and receive data communications using NFC technology. Second, some embodiments of an infusion pump system equipped with NFC technology may facilitate convenient user input of information to the infusion pump system. Third, the safety and efficacy of an infusion pump system may be enhanced because the rapid manner of inputting data to the infusion pump using NFC may facilitate more timely and complete data entry by the user. Fourth, in some circumstances, some users who may not be mentally or physically able to reliably operate a conventional user interface of an infusion pump system may be able to reliably input data to an infusion pump system using NFC communication interface. Fifth, the infusion pump system equipped with NFC equipment may be configured to be portable, wearable, and (in some circumstances) concealable. For example, a user can conveniently wear the infusion pump system on the user's skin under clothing or can carry the pump system in the user's pocket (or other portable location) while receiving the medicine dispensed from the pump device.
It should be understood from the description herein that the term “NFC” (as used herein) or “NFC” capability (as used herein) is different from traditional radio frequency identification (“RFID”). For example, NFC is a more specific version of wireless communication that can be configured for one-way or two-way communications and that operates at a maximum range of less than about 12 inches, about 8 inches or less, and preferably about 4 inches or less (e.g., unlike the much greater communication range of the traditional RFID technology that extends for many feet or more).
The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.
Like reference symbols in the various drawings indicate like elements.
Referring to
NFC can be used, for example, to rapidly input user commands or other data into the portable pump 60, thereby at least partially reducing the need to actuate the buttons 63a-63b, 64a-64c or other components of the user interface 62. As explained further herein, the data input to the portable pump 60 via NFC may cause the portable pump 60 to execute particular actions, such as automatically calculating an amount of a recommended bolus delivery of insulin (or another medication) and prompting the user with an option to confirm and initiate such a bolus delivery. By incorporating NFC equipment within the infusion pump system 10, user communications with the portable pump 60 can be enhanced and simplified. As a result, the accuracy and completeness of the data entered by the user into the portable pump 60 can be improved, and the user can experience greater convenience and time efficiency. Optionally, the portable pump 60 can further include an accelerometer 50 arranged in the pump housing structure 66. In some embodiments, the accelerometer 50 can be used to activate the NFC communications when an acceleration at or above the threshold level is detected, as explained further below.
The infusion pump system 10 is configured to controllably dispense a medicine to be infused into the tissue or vasculature of a targeted individual, such as a human or animal patient. In some embodiments, the portable pump 60 includes the housing structure 66 that defines a cavity in which a fluid cartridge (not shown) can be received. For example, the fluid cartridge can be a carpule that is either user-fillable or is preloaded with insulin or another medicine for use in the treatment of Diabetes (e.g., BYETTA®, SYMLIN®, or others). Such a cartridge 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 include: pain relief drugs, hormone therapy, blood pressure treatments, anti-emetics, osteoporosis treatments, or other injectable medicines. The fluid cartridge may have other configurations. For example, in some embodiments the fluid cartridge may comprise a reservoir that is integral with the pump housing structure 66 (e.g., the fluid cartridge can be defined by one or more walls of the pump housing structure 66 that surround a plunger to define a reservoir in which the medicine is injected or otherwise received).
The portable pump 60 includes a cap device 68 to retain the fluid cartridge in the cavity of the housing structure 66 and, optionally, to penetrate a septum of the fluid cartridge for purposes of establishing fluid communication with the infusion set 70. The portable pump 60 includes a drive system (one example is described in more detail below in connection with
In some embodiments, the infusion pump system 10 can be configured to supply scheduled basal dosages of insulin (or another medication) along with user-selected 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. The user-selected bolus deliveries may provide substantially larger amounts of insulin in particular circumstances in which the user's blood glucose level requires a significant correction. In some embodiments, the infusion pump system 10 can suggest a bolus dosage to the user in a manner that accounts for the user's food intake, the user's recent blood glucose level (e.g., input into the portable pump 60 by the user, from an integral blood test strip analyzer, transmitted to the portable pump 60 from an external blood glucose monitoring device, or the like), the rate of change in the user's blood glucose level, and previously delivered insulin that has not acted on the user. For example, a user can enter a carbohydrate value indicative of a meal into the portable pump 60, and in response thereto, the portable pump 60 can output a suggested bolus dosage to the user.
In some embodiments, the infusion pump system 10 may modify a bolus delivery (e.g., a bolus delivery after the user consumes a meal) in response to certain circumstances. For example, the infusion pump system 10 may decrease or otherwise modify a post-meal bolus delivery based on a rapidly falling blood glucose level, a current blood glucose level that is below a threshold limit, based on an increased level of physical activity, or the like.
The infusion pump system 10 can be configured to be portable and can be wearable and concealable. For example, a user can conveniently wear the infusion pump system 10 on the user's skin (e.g., using skin adhesive) underneath the user's clothing or carry the portable pump 60 in the user's pocket (or other portable location) while receiving the medicine dispensed from the infusion pump system 10. As such, the infusion pump system 10 can be used to deliver medicine to the tissues or vasculature of the user in a portable, concealable, and discrete manner.
Still referring to
In some embodiments, the user can adjust the settings or otherwise program the portable pump 60 by pressing one or more buttons 63a, 63b, 64a, 64b, and 64c of the user interface 62. For example, in embodiments of the infusion pump system 10 configured to dispense insulin, the user may press one or more of the buttons 63a, 63b, 64a, 64b, and 64c to change the dispensation rate of insulin or to request that a bolus of insulin be dispensed immediately, at a scheduled later time, over a period of time, or following a particular time-based profile. In another example, the user may use the buttons 63a, 63b, 64a, 64b, and 64c to manually input information such as the user's current blood glucose level (e.g., as measured by an external blood glucose meter), the current rate of change in the user's blood glucose level, or the like into the portable pump 60.
In some embodiments, the NFC circuit 40 is housed in the portable pump 60 to provide an additional functionality that can enhance and simplify user interactions with the portable pump 60. For instance, using NFC, the need for user activation of multiple buttons 63a, 63b, 64a, 64b, and 64c for shuffling through menus may be eliminated or otherwise reduced in some circumstances. In one example depicted in
To initiate the desired bolus dispensation, the user can first position the portable pump 60 containing the NFC circuit 40 in close proximity with the NFC tag 45 (e.g., preferably within a range 4 inches or less, including for example, a physical “bump” with the NFC tag 45). Wireless near field communications can thereby be established between the NFC circuit 40 and the NFC tag 45 (as signified by wireless communication symbol 47). In some embodiments, the user is provided with a notification that near field communications have been established. The notification can be visual, audible, tactile (vibratory), or a combination thereof. In response to the communication between the NFC tag 45 and the portable pump 60, the portable pump 60 provides a prompt to the user on the display 65. The prompt on the display 65 requests the user to confirm that the user desires to receive a 4.0 unit dispensation of insulin related to the intake of 60 grams of carbohydrates. To confirm and initiate the dispensation of the suggested bolus amount, the user can simply press button 64c to select “Enter.” By this example, it can be appreciated that the incorporation of NFC equipment in the infusion pump system 10 can enhance and simplify user interactions with the infusion pump system 10, because in order to initiate appropriate suggested bolus dosage of insulin, the user simply bumped the NFC tag 45 with the pump housing structure 66 and then pressed a single acknowledgement button in response to the prompt on the display 65. As will be described further, in some embodiments other techniques for user confirmation or acknowledgement can be used, and in some instances user confirmation or acknowledgement may be optional.
NFC provides short-range wireless communication. As described herein, the maximum working distance for NFC is less than 12 inches, about 8 inches or less, and about 4 inches or less in the aforementioned embodiment depicted in
Referring again to
In alternative arrangements, the particular computer program script to be executed in correspondence to the NFC tag 45 can be stored within the internal control circuitry of the portable pump 60. In such arrangements, the NFC tag 45 can transfer a unique identifier such as a serial number to the NFC circuit 40. Upon receipt of the unique identifier, the portable pump 60 can execute the particular computer program script that corresponds to the identifier. In some embodiments, a combination of both arrangements can be used. In any case, from the description herein it can be appreciated that a particular NCF tag (e.g., NFC tag 45) can be used to automatically trigger a corresponding particular action or change in operation of the portable pump 60. As such, a variety of NFC tags can be conveniently used with an infusion pump system 10 so as to enhance and simplify user interactions with the infusion pump system 10 in regard to a variety of scenarios and user desires.
In some embodiments, an accelerometer 50 can be optionally positioned in the portable pump 60 and connected to the control circuitry inside the housing structure 66. In particular embodiments, more than one accelerometer 50 can be included in the housing structure 66. The accelerometer 50 can operate in conjunction with control circuitry and the NFC circuit 40 to supplement the criteria for activating communications between the NFC circuit 40 and the NFC tag 45. In other words, while in some embodiments communications between the NFC circuit 40 and the NFC tag 45 are activated based merely on the proximity therebetween, in other embodiments a threshold movement of the housing structure 66 (as detected by the accelerometer 50) is used (at least as a factor) in activating the NFC circuit 40 for communication with the nearby NFC tag 45. For example, in some embodiments the accelerometer 50 can serve to require that the user “bump” or otherwise tap the portable pump 60 onto the NFC tag 45 or another object before the NFC circuit 40 is activated. An objective for including this feature can be to more clearly ascertain that the user desires to activate NFC when the NFC tag 45 is within the required proximity with the NFC circuit 40. That is, by requiring the user to tap the portable pump 60 onto the NFC tag 45, the user's intentions for activating NFC can be confirmed with a greater level of confidence.
In some embodiments, this optional feature of using the accelerometer 50 in conjunction with the NFC circuit 40 can function as follows. When a movement is detected by accelerometer 50, the characteristics of the movement can be compared by the control circuitry to a predetermined threshold value (e.g., a threshold movement indicative of the aforementioned “bump” or tap movement). If the detected movement is greater than or equal to the threshold value, the NFC circuit 40 can potentially be activated. But, if no movement that is greater than or equal to the threshold value is detected, the NFC circuit 40 is not activated (even if the NFC circuit 40 is within the required proximity of the NFC tag 45 such that NFC communications can potentially be performed). Therefore, in some embodiments this feature operates to enable NFC when the following two conditions are simultaneously met, or are both met within an establish time interval: (i) an acceleration or an acceleration profile that is greater than or equal to a threshold value is detected (indicating, e.g., a tap or other “bump” action between the portable pump 60 and the NFC tag 45), and (ii) the NFC circuit 40 is in proximity with the NFC tag 45 such that communications therebetween using NFC can occur. In some embodiments, the feature provided by the accelerometer 50 can be activated or deactivated based on a user's or clinician's selection of the feature via the configuration parameters of the portable pump 60. In some embodiments, the accelerometer 50 can be used in conjunction with the NFC circuit 40 in other ways so as to include the detection of a movement into the process for activating or completing changes to the portable pump 60 that correspond to the NFC tag 45.
In some embodiments, the portable pump 60 can be configured to respond differently when the acceleration threshold value is detected by the accelerometer 50 as compared to when the acceleration threshold value is not detected. For example, as described previously, in response to the detection of the NFC tag 45 by the NFC circuit 40 the user may be asked to confirm via the user interface 62 whether to initiate a change to the portable pump 60, such as initiating a bolus of insulin. However, if an acceleration that meets or exceeds the established threshold is detected by accelerometer 50, and the NFC tag 45 is simultaneously detected (or detected within a threshold time limit) by the NFC circuit 40, in some cases the portable pump 60 may initiate a bolus without requiring additional user confirmation. Still, in some cases additional user confirmation may nevertheless be required before the bolus is initiated.
Referring now to
In one example, a parent may pack a lunch for a diabetic child to take to school, and one or more NFC tags 46 corresponding to the particular lunch food can be packed along with the lunch. Or, the NFC tags 46 can be carried by the child (e.g., in a pocket, worn on a necklace or article of clothing). At the school lunchroom, the child can simply tap the child's infusion pump to the NFC tags 46 in order to command the pump to deliver an appropriate bolus dispensation of insulin in correspondence to the food consumed. Thus, as this example shows, using the NFC tags 46 the user can efficiently, accurately, and conveniently initiate commands to the infusion pump system 10 by activating NFC communications between the infusion pump system 10 and the NFC tags 46 (and, optionally, without the need to input a series of menu selections or other more complex user interface actions). In addition, as will be described further, particular NFC tags 46 can be used to receive and store data from the infusion pump system 10.
Some people often eat the same types of foods on a relatively regular basis. A user of the infusion pump system 10 can therefore obtain or make NFC tags that correspond to the food items that the user commonly consumes. For example, the NFC tag 46a (
Still further, other data, in addition to grams of carbohydrates and preferred insulin delivery schedules, can be associated with the NFC tags 46. For example, in some embodiments the fat content, type of fat content, fiber content, protein content, and the like, of the food represented by the NFC tags 46 can be associated with the NFC tags. In some embodiments, such data can be incorporated into a recommended insulin dispensation for the user as calculated by the control circuitry of the portable pump 60. For example, in some instances meals with increased fat can lead to delayed absorption of the carbohydrates, and thus a bolus determined based on other food contents beyond just carbohydrates, (e.g., fat and protein) may be beneficial.
While a user of the infusion pump system 10 may consume certain foods like a peanut butter and jelly sandwich fairly regularly, in some circumstances the user may consume a food item for which the user does not have a dedicated NFC tag 46. In those circumstances, NFC tags 46b, 46c, 46d, and 46e can be used if the user so desires. To use the NFC tags 46b, 46c, 46d, and 46e, the user will estimate the carbohydrate content of the foods that the user has or will soon consume. If, for example, the user will consume food having a carbohydrate content of about 10 grams, the user can activate NFC between the portable pump 60 and the NFC tag 46b (where the NFC tag 46b corresponds to 10 grams of carbohydrates). In response, the portable pump 60 may determine a recommended bolus of insulin and either initiate the dispensation of the bolus or prompt the user to confirm via the user interface 62 the initiation of the recommended bolus of insulin. The NFC tags 46c, 46d, and 46e can be similarly used in situations where about 20, 50, or 100 grams of carbohydrates, respectively, have been or will soon be consumed. Of course, the carbohydrate quantities of 10, 20, 50, and 100 grams associated with NFC tags 46b, 46c, 46d, and 46e are merely illustrative, as NFC tags 46 having any other quantities of carbohydrates (and other data content) can be created and used in accordance with the systems and methods provided herein.
In another example that is relevant to the use of NFC tags 46b, 46c, 46d, and 46e, it may be determined that the user has or will consume food having a carbohydrate content of about 30 grams. In a first example for handling such a scenario, in some embodiments the portable pump 60 can be configured to add together successive NFC tag data entries to input the total carbohydrate quantity desired by the user. For example, to input 30 grams of carbohydrates, the user may first activate NFC between the portable pump 60 and the NFC tag 46b to input 10 grams of carbohydrates. Before confirming a bolus dispensation corresponding to the 10 grams, the user can then activate NFC between the portable pump 60 and the NFC tag 46c to input an additional 20 grams of carbohydrates, for 30 total grams of carbohydrates. In other words, the portable pump 60 can add the first NFC input of 10 grams of carbohydrates and the second NFC input of 20 grams of carbohydrates together to arrive at a total of 30 grams of carbohydrates. The portable pump 60 can then present to the user via the display 65 a prompt that asks the user to confirm the input of 30 grams of carbohydrates to be consumed, and to confirm the acceptance of the associated recommended bolus dispensation of insulin. For example, in the example portable pump 60 provided, the user can confirm the acceptance of such information by activating the button 64c. In other examples, other techniques for confirming acceptance can be used, as described further herein.
While the first example immediately above used NFC tags 46b and 46c to enter a total of 30 grams of carbohydrates into portable pump 60, in a second example technique for entering 30 grams of carbohydrates, the single NFC tag 46b (10 grams of carbohydrates) can be used to activate NCF circuit 40 three times to cause three successive data entries of 10 grams of carbohydrates each. The three successive data entries of 10 grams of carbohydrates each can be added together by portable pump 60 in the manner described above, resulting in a total entry of 30 grams of carbohydrates. The user can then confirm the entry of 30 grams and accept the recommended bolus using the user interface 62. By way of these examples, it should be appreciated that by combining successive data entries using various NFC tags 46, such as NFC tags 46b, 46c, 46d, and 46e, any desired amount of grams of carbohydrates can be entered into portable pump 60 using NFC technology. While in these examples the portable pump 60 was configured to add together successive NFC data entries, in some embodiments the portable pump 60 can alternatively be configured to not add such successive entries together. In some embodiments, the user (or another individual such as a parent or clinician) can selectively configure the portable pump 60 to either add successive entries together or to not add successive entries together.
Still referring to
NFC tag 46k is an example of a NFC tag that includes an iconic identifier on a surface of the NFC tag 46k. In this example, an icon of a hamburger is printed on the NFC tag 46k. Using icons, symbols, and other types of non-text identifiers can be advantageous for some users. For example, certain users of the NFC tags 46 may not have fluency in the language printed on the NFC tags 46. Or, a user of the NFC tags 46 may be illiterate, a child, or have poor eyesight. In another example, the NFC tags 46 can include Braille or other raised patterns or shapes for use by blind users or users with limited vision.
NFC tags 46m and 46n are examples of NFC tags that correspond to an exercise activity to be performed by the user of the infusion pump system 10. Diabetic individuals typically experience a blood sugar reduction in response to the performance of exercise. Therefore, to maintain the user's blood sugar level within a target range it can be beneficial to temporarily reduce the user's basal rate to an extent that correlates to the level of physical exertion performed or to be performed. When reducing basal insulin, the appropriate extent of reduction will depend on factors such as intensity, duration, the individual, and mode of exercise. A basal rate can be reduced prior to, during, and after exercise depending on the situation. For example, in response to performing light exercise over a 30 minute period, the user may present NFC tag 46m to the user's portable pump 60. The NFC tag 46m, for example, may be associated with a command for a 50% reduction of the basal insulin dosages over the next 6 hours. In another example, in response to performing 30 minutes of strenuous exercise, the user may present NFC tag 46n to the user's portable pump 60. The NFC tag 46n may, for example, be associated with a command for a 50% reduction of basal insulin over the next 10 hours. Such factors can be individualized for the particular user, and the particular user's NFC tags 46m and 46n can be programmed accordingly. In some embodiments, the NFC tags 46m and 46n can be used in combinations to additively arrive at other levels of exertion or duration in a manner analogous to that described above in reference to NFC tags 46b-e.
NFC tags 46o, 46p, 46q, and 46r are examples of NFC tags that can be used to automate the entry and time-based archival of event occurrences into the portable pump 60. In other words, the NFC tags 46o-46r can be used to add descriptive information to the data that is stored within the portable pump 60. Such labeling of data is also known as data tagging or the creation of metadata. For example, if the user is feeling ill, the user can present the NFC tag 46o to the user's portable pump 60. Upon the activation of NFC between the NFC tag 46o and the NFC circuit 40, a command is executed that causes the portable pump 60 to store metadata identifying that the user feels ill at the time that the NFC was activated. In other examples, when the user is exercising, eating, or has installed a new medicine cartridge, the user can present the NFC tags 46p, 46q, or 46r, respectively, to the user's portable pump 60. Upon the activation of NFC between the NFC tags 46p, 46q, or 46r and the NFC circuit 40, a command is executed that causes the portable pump 60 to store metadata identifying that the user is exercising, eating, or has installed a new medicine cartridge at that time. In another example (not shown in
NFC tags 46 can also be used to automatically enter other types of commands to the portable pump 60. NFC tags 46 can thereby reduce the need for using buttons 63a-b and 64a-c of the user interface 62 to shuffle through various menus. One example of a type of command that can be automated is the entry of a blood glucose reading using a NFC tag 46s. For example, the user may periodically measure the user's blood glucose level using a blood glucose meter that analyzes a sample of the user's blood using a test strip. The numerical results provided by such a test can then be entered into the user's portable pump 60 to provide the portable pump 60 with the user's actual current blood glucose level. The NFC tag 46s can be used to “key-up” the portable pump 60 for the entry of the numeric blood glucose level. For example, when the user presents the NFC tag 46s to the portable pump 60 and NFC is established therebetween, a command is executed that causes the portable pump 60 to get ready to receive the blood glucose data with no other preliminary button pushing required. In such fashion, the user can save time and can operate the infusion pump system 10 with greater convenience using the NFC tag 46s. Of course, many other types of commands for the portable pump 60 can be similarly automated using the NFC tags 46.
NFC tag 46t is an example of a “blank” NFC tag that can be programmed or scripted and thereafter used to input a variety of commands to the portable pump 60. In some embodiments, the NFC tag 46t can be programmed by the portable pump 60. In particular embodiments, the NFC tag 46t can be programmed by another device that has NFC functionality (e.g., a smart phone, tablet computer, personal computer, and the like). In some embodiments, the NFC tag 46t can be written to only once, and thereafter the NFC tag 46t becomes a read-only NFC tag. In other embodiments, the NFC tag 46t can be written to, and re-written to, multiple times.
The programmable NFC tag 46t can be utilized in a variety of advantageous ways. For instance, as described above a user of the infusion pump system 10 can program the NFC tag 46t to be associated with data corresponding to a certain type of food that the user consumes (e.g., a large apple having 30 carbs, etc.). In another category of examples, the user can configure the NFC tag 46t to be used to initiate a particular operation by the portable pump 60. For example, when changing an infusion set 70 or a medicine cartridge, the user may first want to pause the portable pump 60. Accordingly, the programmable NFC tag 46t can be programmed to pause the portable pump 60 if the portable pump 60 is in the run mode at the time that NFC is activated between the programmed NFC tag 46t and the portable pump 60. Then, after changing the infusion set 70 or the medicine cartridge, the user may desire to prime the infusion set 70 and begin normal operations of the infusion pump system 70. Therefore, the programmable NFC tag 46t can be programmed to prime and thereafter start the portable pump 60 if the portable pump 60 is in the pause mode at the time that NFC is activated between the programmed NFC tag 46t and the portable pump 60. In accordance with the examples provided above, it can be appreciated that programmable NFC tag 46t provides a versatile and customizable functionality whereby users of infusion pump system 10 can enhance and simplify interactions with the user interface 62 and operational capabilities of the portable pump 60.
It should be understood from the description herein that a multitude of other beneficial uses for the NFC tags are envisioned for use in combination with a medical infusion pump system. Here, the infusion pump system 70 performs a variety of tasks or receives a various types of user entry associated with operating the infusion pump system 70. Any one of these tasks or types of user entry associated with operating the infusion pump system 70 can be communicated to the control circuitry of the portable pump 60 via the NFC circuit 40 using the corresponding NFC tag. For example, a NFC tag can be used to confirm a user input or pump parameter setting. A NFC tag of this type can be used in conjunction with other NFC tags or input methods to eliminate the need for entering a confirmation using the user interface 62. In another example, a NFC tag can be used to enter a task command to calibrate a glucose sensor. That is, for example, a NFC tag can trigger the portable pump 60 to use the last blood glucose value entered by the user to calibrate a continuous glucose monitor that is in communication with the infusion pump system 70. In another example, in some circumstances, such as when the infusion pump system 70 is used by a child or when the infusion pump system 70 is used during sports activities, it may be desirable to temporarily deactivate the functionality of the buttons 63a, 63b, 64a, 64b, and 64c of the user interface 62. In such circumstances, NFC tags can be used to lock, and subsequently unlock, the buttons 63a, 63b, 64a, 64b, and 64c of the user interface 62. In still another example, a NFC tag can be used to stop or pause the portable pump 60, such as when the user has disconnected the portable pump 60 from the infusion set 70 to bathe. NFC tags can also be used to enter a task or user command to change to a different basal pattern. Such changes may be beneficial during weekends versus weekdays, during menses versus the rest of the month, and so on. It should be understood that the example uses for NFC tags provided herein are non-limiting, and that other uses for the NFC tags are also envisioned.
NFC tag 46u is an example of another use for a “blank” NFC tag that can be written to. In this example, the NFC tag 46u is used to store the user configuration settings for the user's portable pump 60. Using the NFC tag 46u in this manner can provide a way to create a back-up copy of the user's configuration settings. Having a back-up copy of the user's configuration settings can be advantageous in a variety of circumstances. For example, if the user's portable pump 60 is damaged such that a repair is necessitated, the NFC tag 46u containing the user's settings can be used to conveniently reprogram the repaired portable pump 60 by presenting the NFC tag 46u to the repaired portable pump 60. Or, if the user's portable pump 60 is damaged beyond repair, the user's settings can be conveniently uploaded to a replacement portable pump 60 by presenting the NFC tag 46u to the replacement portable pump 60. Or, if the user desires different settings for different situations, such NFC tags comprising user settings can conveniently be used to change the settings.
Referring now to
In operation 310, the control circuitry of a medical device can receive input via wireless communication from a NFC tag. The input can be indicative of a task associated with using the medical device. A medical device that can perform operation 310 is exemplified in
In some embodiments, NFC tags can be scripted with executable code that can be transferred to the medical device's control circuitry via the NFC circuit in communication with the control circuitry. In those embodiments, the control circuitry can execute the code as received from the NFC tag. In other embodiments, the NFC tag can communicate a unique identifier, such as a serial number, to the control circuitry via the NFC circuit. In response to the receipt of such a unique identifier by the control circuitry, the control circuitry can execute certain coded operations that are associated with the particular unique identifier received.
An example of operation 310 is provided in
In operation 320, the control circuitry optionally provides a prompt via the user interface display to confirm a change in operation of the medical device in response to said input from the near field communication tag. Such a prompt may be advantageously used to confirm the user's intent to change the operation of the medical device before the control circuitry actually implements the change.
An example of operation 320 is provided in
In operation 330, after receiving confirmation from the user to implement the change associated with the input from the NFC tag, the control circuitry can control the medical device to change the operation of the medical device in accordance with the user's confirmation of the change. Again in regard to the example of
Now referring to
The pump controller device 460 includes a control module 461 that can be made up of one or more components. In this embodiment, the control module 461 is configured to communicate control or power signals to the other components of the infusion pump system 400, and to receive inputs and signals therefrom. In some embodiments, the control circuitry can include a main processor board that is in communication with a power supply board. The control circuitry can include at least one processor that coordinates the electrical communication to and from the control module 461 and other components of the pump system 400. For example, the user interface 462 of the pump controller device 460 can include input components and output components that are electrically connected to the control circuitry of the control module 461. In some embodiments, the control module 461 can receive input commands from a user's button selections (e.g., buttons as shown in
The processor of the control module 461 can be arranged on a main processor circuit board of the control module 461 along with a number of other electrical components such as computer-readable memory devices. The control circuitry can be programmable in that the user or a clinician may provide one or more instructions to adjust a number of settings for the operation of the infusion pump system 400. Such settings may be stored in the memory devices of the control module 461. Furthermore, the control module 461 may include one or more dedicated memory devices that store executable software instructions for the processor. The control module 461 may include other components, such as sensors, that are electrically connected to the main processor board. A rechargeable battery pack (not shown) may provide electrical energy to the control module 461, and to other components of the pump controller device 460 (e.g., user interface 462, NFC circuit 463, and others).
The user interface 462 of the pump controller device 460 permits a user to monitor and control the operation of the pump controller device 460. For example, the user interface 462 can include a display device having an active area that outputs information to a user, and buttons (e.g., actuatable buttons as shown in
The pump controller device 460 also includes the NFC circuit 463 in electrical communication with the control module 461, such that power and signal data can be transferred between the NFC circuit 463 and the control module 461. The NFC circuit 463 in this embodiment includes a NFC transceiver circuit that is coupled to a loop inductor (e.g., coil) that serves as an antenna for wirelessly communicating with external NFC tags (e.g., NFC tags 410, 422, and 432). The NFC circuit 463 can act as an interface to facilitate the transfer of data between the example NFC tags 410, 422, and 432 and the control module 461 using NFC protocols. The coil of the NFC circuit 463 inductively supplies electrical power to the NFC tags 410, 422, and 432 by way of secondary coils located in the NFC tags 410, 422, and 432 themselves. The respective coils of the NFC circuit 463 and the NFC tags 410, 422, and 432 can also wirelessly exchange two-way data transmissions using the same inductive coupling between the Coils.
The example NFC tags 410, 422, and 432 depict some additional advantageous ways of configuring NFC tags to be used in conjunction with the infusion pump system 400. In general, NFC tags 410, 422, and 432 include a coil and a microchip. The NFC tags 410, 422, and 432 act as passive listening devices. But when the NFC circuit 463 is located in the requisite proximity to the NFC tags 410, 422, or 432, the coil of the NFC tags 410, 422, or 432 inductively couples with a coil of the NFC circuit 463. When the coils are inductively coupled, electrical power is supplied to the NFC tags 410, 422, or 432 and data can be exchanged between the NFC tags 410, 422, or 432 and the NFC circuit 463. In some embodiments, about a kilobyte of data or more can be stored in the NFC tags 410, 422, and 432 and transferred to the control module 461 via the NFC circuit 463.
The NFC tag 410 is an example of a compact and versatile NFC tag. In some embodiments, NFC tag 410 is about the size of a quarter and is flexible. NFC tag 410 can have an adhesive coating on one surface. In some embodiments, the NFC tag 410 can be incorporated into configurations such as pendants, tiles, chips, stickers, and the like.
The NFC tag 422 is an example of a NFC tag that has been conveniently incorporated onto a keychain 420. In one example use of such a configuration, the keychain 420 can be attached to a gym bag and the NFC tag 422 can be programmed like the NFC tags 46m or 46n of
The NFC tag 432 in an example of a NFC tag that has been conveniently incorporated onto a food package 430. In this example, the food package 430 is a sandwich container like those commonly available from a vending machine or convenience store. As shown, the NFC tag 432 can be adhered to or otherwise incorporated directly on the exterior of the food package 430. The NFC tag 432 can be preprogrammed with data corresponding to the contents of the food package 430. For example, the NFC tag 432 can be programmed with the number of grams of carbohydrates in the sandwich contained in the food package 430. The user of the infusion pump system 400 can conveniently present the NFC tag 432 to the NFC circuit 463 of the pump controller device 460 (e.g., tapping the pump controller device 460 against the tag 432 or in proximity to the tag 432) to enter a command corresponding to the consumption of the sandwich inside of the food package 430.
The pump controller device 460 can also optionally include an accelerometer 464 in electrical communication with the control module 461. In some embodiments, more than one accelerometer 464 can be optionally included. Embodiments of the pump controller device 460 that include the optional accelerometer 464 can utilize the functionality of the accelerometer 464 in conjunction with the NFC circuit 463. That is, the accelerometer 464 can operate in conjunction with the control module 461 and the NFC circuit 463 to supplement the criteria for activating or completing communications between the NFC circuit 463 and the NFC tags 410, 422, or 432. In other words, while in some embodiments communications between the NFC circuit 463 and the NFC tags 410, 422, or 432 are activated solely based on the proximity therebetween, in other embodiments a threshold acceleration, as determined by the accelerometer 464, must also be detected. An objective for including this feature can be to more clearly ascertain that the user intends to activate NFC when a NFC tag 410, 422, or 432 is within the required proximity with the NFC circuit 463. That is, for example, by requiring the user to tap the pump controller device 460 and the NFC tag 410, 422, or 432 together, the user's intentions for activating NFC may be ascertained with a greater level of confidence.
This optional feature using the accelerometer 464 can function as follows. When motion of the pump controller device 460 is detected by accelerometer 464, a characteristic value of the detected motion can be compared by the control module 461 to a predetermined threshold movement value. If the characteristic value of the detected movement is greater than the threshold value, the NFC circuit 463 can potentially be activated. But, if the characteristic value of the detected movement is not greater than the threshold value, the NFC circuit 463 is not activated (even if the NFC circuit 463 is within the required proximity of the NFC tags 410, 422, or 432 such that NFC communications can be performed). Therefore, in some embodiments this feature operates to enable NFC when the following two conditions are simultaneously met, or are both met within an establish time interval: (i) a characteristic value of the detected movement (e.g., acceleration value) that is greater than a threshold value is detected (indicating, for example, a tap), and (ii) the NFC circuit 463 is in proximity with the NFC tags 410, 422, or 432 such that communications therebetween using NFC can occur.
Still referring to
Still referring to
In brief, in embodiments of the infusion pump system 400 that include the separate pump device 470, the pump controller device 460 may be configured as a reusable component that provides electronics and a user interface to control the operation of the infusion pump system 400, and the separate pump device 470 can be a disposable component that is discarded after a single use. For example, the separate pump device 470 can be a “one time use” component that is thrown away after the fluid cartridge therein is exhausted. Thereafter, the user can wirelessly connect or removably mount a new separate pump device 470 to the reusable pump controller device 460 for the dispensation of a new supply of medicine from the new pump device 470. Accordingly, the user is permitted to reuse the pump controller device 460 (which may include complex or valuable electronics) while disposing of the relatively low-cost separate pump device 470 after each use. Such an infusion pump system 400 can provide enhanced user safety as a new separate pump device 470 is employed with each new fluid cartridge.
Still referring to
Referring now to
In some embodiments, the controller device 200 communicates with the pump device 100 to control the operation of the drive system 140. When the controller device 200, the pump device 100 (including the cap device 130), and the fluid cartridge 120 are assembled together, the user can (in some embodiments) conveniently wear the infusion pump system 500 on the user's skin under clothing, in a pouch clipped at the waist (e.g., similar to a cell phone pouch), or in the user's pocket while receiving the fluid dispensed from the pump device 100. 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 100 (having a new fluid cartridge 120) to the reusable controller device 200 for the dispensation of fluid from a new fluid cartridge 120. 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 system 500 can provide enhanced user safety as a new pump device 100 (and drive system therein) is employed with each new fluid cartridge 120.
Briefly, in use, the pump device 100 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 that can be resistant to water migration. For example, 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 infusion pump system 500 to be discrete and portable. Moreover, at least one of the pump device 100 or the controller device 200 can include a release member that facilitates an easy-to-use detachment and replacement process.
As shown in
The pump device 100 may include a drive system 140 that is controlled by the removable controller device 200. Accordingly, the drive system 140 can accurately and incrementally dispense fluid from the pump device 100 in a controlled manner. The drive system 140 may include a flexible piston rod 141 that is incrementally advanced toward the fluid cartridge 120 so as to dispense the medicine from the pump device 100. At least a portion of the drive system 140 is mounted, in this embodiment, to the pump housing structure 110. In some embodiments, the drive system 140 may include a number of components, such as an electrically powered actuator (e.g., reversible motor 142 or the like), a drive wheel 143, a bearing 145, the flexible piston rod 141, and a plunger engagement device 144. In this embodiment, the reversible motor 142 drives a gear system to cause the rotation of the drive wheel 143 that is coupled with the bearing 145. The drive wheel 143 may include a central aperture with an internal thread pattern, which mates with an external thread pattern on the flexible piston rod 141. The interface of the threaded portions of the drive wheel 143 and flexible piston rod 141 may be used to transmit force from the drive wheel to the piston rod 141. Accordingly, in the embodiment of
Still referring to
The controller device 200 can also be equipped with an inspection light device 230. The inspection light device 230 can provide the user with a tool to illuminate and inspect a targeted location. For example, the inspection light device 230 can be directed at the infusion site on the user's skin to verify that the infusion set is properly embedded, or the inspection light device 230 can be directed at the pump device 100 to illuminate the cavity 116 or other areas. The inspection light device 230 can also be used to notify the user to an alert condition of the pump system 500. 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 infusion pump system 500 is warranted.
The controller device 200 of the pump system 500 also includes a NFC circuit 240. The NFC circuit 240 can wirelessly communicate with external NFC tags, such as example NFC tags 246a, 246b, 246c, and 246d. As described previously, such wireless communications using NFC technology can enhance and simplify user interactions with the infusion pump system 500. For instance, using NFC, the need for user activation of buttons 224 for shuffling through menus may be reduced in some circumstances.
Optionally, the controller device 200 can further include at least one accelerometer 250. In some embodiments, the accelerometer 250 can be used as a criteria to activate or complete the NFC communications when a characteristic value of a detected movement of the controller device 200 is at or above the threshold level, as previously described above in connection with
Referring now to
In this embodiment, the pump assembly 660 includes a housing structure 610 that defines a cavity in which a fluid cartridge 625 can be received. The pump assembly 660 also includes a cap device 630 to retain the fluid cartridge 625 in the cavity of the housing structure 610. The pump assembly 660 includes a drive system (e.g., described in more detail in connection with
Still referring to
In some embodiments, the monitoring device 500 may include a circuit that permits sensor signals (e.g., data from the sensor shaft 556) to be communicated to the communication device 554. The communication device 554 can transfer the collected data to the pump assembly 660 (e.g., by wireless communication to a communication device 647 arranged in the pump assembly 660). In some embodiments, the monitoring device 500 can employ other methods of obtaining information indicative of a user's blood characteristics and transferring that information to the infusion pump assembly 660. 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. Alternatively, 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 embodiments, the monitoring device 500 can be in communication with the pump assembly 660 via a wired connection. In other embodiments of the pump system 600, test strips (e.g., blood test strips) containing a sample of the user's blood can be inserted into a strip reader portion of the pump assembly 660 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
Still referring to
In some embodiments, the user may press one or more of the buttons 624a, 624b, 624c, and 624d to shuffle through a number of menus or program screens that show particular status indicators, settings, and/or data (e.g., review data that shows the medicine dispensing rate, the amount of medicine delivered during the last bolus, the delivery time of the last bolus, the total amount of medicine dispensed in a given time period, the amount of medicine scheduled to be dispensed at a particular time or date, the approximate amount of medicine remaining in the fluid cartridge 625, or the like). In some embodiments, the user can adjust the settings or otherwise program the pump assembly 660 by pressing one or more buttons 624a, 624b, 624c, and 624d of the user interface 620. For example, in embodiments of the infusion pump system 600 configured to dispense insulin, the user may press one or more of the buttons 624a, 624b, 624c, and 624d to change the dispensation rate of insulin or to request that a bolus of insulin be dispensed immediately or at a scheduled, later time. In another example, the user may use the buttons 624a-d to manually input information such as the user's current blood glucose level (e.g., as measured by an external blood glucose meter), the current rate of change in the user's blood glucose level, or the like into the pump system 600.
The pump assembly 660 also includes a NFC circuit 640. The NFC circuit 640 can wirelessly communicate with external NFC tags, such as example NFC tags 646a, 646b, 646c, and 646d. As described previously, such wireless communications using NFC technology can enhance and simplify user interactions with the infusion pump system 600. For instance, using NFC, the need for user activation of buttons 624a-d for shuffling through menus may be reduced in some circumstances.
Optionally, the pump assembly 660 can further include at least one accelerometer 650. In some embodiments, the accelerometer 650 can be used to activate or complete the NFC communications when a characteristic value of a detected movement of the pump assembly 660 is at or above the threshold level, as previously described above in connection with
Referring now to
In general, the remote control device 770 includes a control system for controlling the infusion pump assembly 760, including user interface components such as touchscreen user interface 775 for allowing a user to receive and provide instructions relative to the infusion pump assembly 760. The remote control device 770 also includes a wireless interface 757 for communicating with a wireless interface 752 of the pump assembly 760. The wireless interfaces 752 and 757 for communicating between the pump assembly 760 and the remote control device 770 can utilize any of a variety of wireless communication technologies, such as Bluetooth, WiFi, RF, infrared, ultrasonic, electromagnetic induction, NFC, or combinations thereof. The pump assembly 760 can be used to dispense insulin or another medication to a user via, for example, an infusion set 70 as described in regard to other infusion pump system embodiments herein.
In this embodiment, the pump assembly 760 includes a housing structure 710 that defines a cavity in which a fluid cartridge (e.g., an insulin carpule or other medicine cartridge) can be received. The pump assembly 760 also includes a cap device 730 to retain the fluid cartridge in the cavity of the housing structure 710. The pump assembly 760 includes a drive system (e.g., described in more detail in connection with
In some embodiments, the infusion pump system 700 can be configured to supply scheduled basal dosages of insulin (or another medication) along with user-selected 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. The user-selected bolus deliveries may provide 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. In some embodiments, the infusion pump system 700 may modify a bolus delivery (e.g., a bolus delivery after the user consumes a meal) in response to certain circumstances. For example, the infusion pump system 700 may decrease or otherwise modify a post-meal bolus delivery based on a rapidly falling blood glucose level, a current blood glucose level that is below a threshold limit, a detection of a high level of physical activity, or the like.
Still referring to
In some embodiments, the user may press one or more of the buttons 764a, 764b, 764c, 763a, and 763b to shuffle through a number of menus or program screens that show particular status indicators, settings, and/or data (e.g., review data that shows the medicine dispensing rate, the amount of medicine delivered during the last bolus, the delivery time of the last bolus, the total amount of medicine dispensed in a given time period, the amount of medicine scheduled to be dispensed at a particular time or date, the approximate amount of medicine remaining in the cartridge, or the like). In some embodiments, the user can adjust the settings or otherwise program the pump assembly 760 by pressing one or more buttons 764a, 764b, 764c, 763a, and 763b of the user interface 762. For example, in embodiments of the infusion pump system 700 configured to dispense insulin, the user may press one or more of the buttons 764a, 764b, 764c, 763a, and 763b to change the dispensation rate of insulin or to request that a bolus of insulin be dispensed immediately or at a scheduled, later time. In another example, the user may use the buttons 764a, 764b, 764c, 763a, and 763b to manually input information such as the user's current blood glucose level (e.g., as measured by an external blood glucose meter), the current rate of change in the user's blood glucose level, or the like into the pump system 700.
As an alternative to, or in addition to, using user interface 762 to control the pump assembly 760, the remote control device 770 can be used to control the pump assembly 760 in this embodiment. Such an arrangement may be convenient, for example, if the user is wearing the pump assembly 760 in a concealed location under clothing. The remote control device 770 can wirelessly communicate with the pump assembly 760 via the wireless interfaces 757 and 752. The wireless communications between the pump assembly 760 and the remote control device 770 can utilize any of a variety of wireless communication technologies, such as Bluetooth, WiFi, RF, infrared, ultrasonic, electromagnetic induction, NFC, and the like, and combinations thereof. Using remote control device 770, a user can enter and receive information whereby the user can control the pump assembly 760 using the touchscreen user interface 775 of the remote control device 770 as an alternative to, or in addition to, using the user interface 762 of the pump assembly 760. In some alternative embodiments, the pump assembly 760 may be configured without a user interface display 765 or other user interface components for purposes of reducing manufacturing costs, in which case the user interface 775 of the remote control device 770 would serve as the user interface for the pump system 700.
The remote control device 770 also includes a NFC circuit 745. The NFC circuit 745 can wirelessly communicate with external NFC tags, such as the example NFC tag 746. As described previously, such wireless communications using NFC technology can enhance and simplify user interactions with the infusion pump system 700. For instance, using NFC, the need for user activation of buttons 764a, 764b, 764c, 763a, and 763b, or for using user the touchscreen user interface 775, for shuffling through menus may be reduced in some circumstances.
In response to the communication from the NFC tag 746 to the remote control device 770, the remote control device 770 can provide a prompt to the user on the touchscreen user interface 775. In this example, the prompt on the touchscreen user interface 775 requests the user to confirm whether the user desires to receive a 4.0 Unit dispensation of insulin because of the intake of 60 grams of carbohydrates. To confirm the dispensation of the suggested bolus amount, the user can simply touch the portion of the touchscreen user interface 775 that is labeled “YES.” Or, the user can decline the dispensation of the suggested bolus amount by touching the portion of the touchscreen user interface 775 that is labeled “NO.” By this example, it can be appreciated that the incorporation of NFC technology in the infusion pump system 700 can enhance and simplify user interactions with the infusion pump system 700, because to initiate an appropriate bolus dosage of insulin the user simply had to present a NFC tag 746 to the NFC circuit 745 of the remote control device 770 and then touch the portion of the touchscreen user interface 775 that is labeled “YES.”
Optionally, the remote control device 770 can further include at least one accelerometer 755. In some embodiments, the accelerometer 755 can be used to activate the NFC communications when a characteristic value of a detected movement of the remote control device 770 is at or above the threshold level, as previously described above in connection with
While the infusion pump system 700 includes the remote control device 770 that includes NFC circuit 745, in some embodiments the pump assembly 760 can also include a NFC circuit 740. Therefore, the user can alternatively present NFC tags to the pump assembly 760 to input information to the pump assembly 760. Similarly, the pump assembly 760 can optionally include at least one accelerometer 750 that can be used to activate the NFC communications when a characteristic value of a detected movement of the pump assembly 760 is at or above the threshold level, as previously described above in connection with
A number of embodiments of the invention have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention. Accordingly, other embodiments are within the scope of the following claims.
This application is a divisional of Ser. No. 15/383,176, filed on Dec. 19, 2016, now U.S. Pat. No. 10,207,047, issued on Feb. 19, 2019, which is a continuation application of and claims priority to U.S. application Ser. No. 13/946,330, filed on Jul. 19, 2013, now U.S. Pat. No. 9,561,324, issued on Feb. 7, 2017.
| 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 et al. | 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 et al. | Dec 2003 | B1 |
| 6659980 | Moberg et al. | Dec 2003 | B2 |
| 6663602 | Moller | 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 | 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 |
| 7547281 | Hayes et al. | Jun 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 |
| 7734323 | Blomquist et al. | Jun 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 |
| 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 |
| 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 |
| 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 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 | 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 |
| 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 | 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 |
| 20100094251 | Estes | 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 | Aug 2010 | A1 |
| 20100249530 | Rankers et al. | Sep 2010 | A1 |
| 20100273738 | Valcke et al. | Oct 2010 | A1 |
| 20100286601 | Yodfat et al. | Nov 2010 | A1 |
| 20100286653 | Kubel et al. | Nov 2010 | A1 |
| 20100298685 | Hayter et al. | Nov 2010 | A1 |
| 20100298765 | Budiman et al. | 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 | 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 | 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 | 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 | 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 | Sep 2013 | A1 |
| 20130253418 | Kamath et al. | Sep 2013 | A1 |
| 20130275139 | Coleman | Oct 2013 | A1 |
| 20130281965 | Kamen | 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 | Mastrototaro et al. | 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 |
| Number | Date | Country |
|---|---|---|
| 2543545 | May 2005 | CA |
| 1859943 | Nov 2006 | CN |
| 196 27 619 | Jan 1998 | DE |
| 19912459 | Sep 2000 | DE |
| 102 36 669 | Feb 2004 | DE |
| 20 2005 012 358 | Oct 2005 | DE |
| 200401893 | Dec 2004 | DK |
| PA200401893 | Dec 2004 | DK |
| 0062974 | Oct 1982 | EP |
| 0098592 | Jan 1984 | EP |
| 0275213 | Jul 1988 | EP |
| 0 496 141 | Jul 1992 | EP |
| 0 612 004 | Aug 1994 | EP |
| 0 580 723 | Oct 1995 | EP |
| 1 045 146 | Oct 2000 | EP |
| 1 136 698 | Sep 2001 | EP |
| 1 177 802 | Feb 2002 | EP |
| 0 721 358 | May 2002 | EP |
| 1 495 775 | Jan 2005 | EP |
| 1 527 792 | May 2005 | EP |
| 1 754 498 | Feb 2007 | EP |
| 1818664 | Aug 2007 | EP |
| 1824536 | Aug 2007 | EP |
| 1951340 | Aug 2008 | EP |
| 2 764 881 | Aug 2014 | EP |
| 2 585 252 | Jan 1987 | FR |
| 747 701 | Apr 1956 | GB |
| 2 218 831 | Nov 1989 | GB |
| 09-504974 | May 1997 | JP |
| 11-010036 | Jan 1999 | JP |
| 2000-513974 | Oct 2000 | JP |
| 2002-507459 | Mar 2002 | JP |
| 2002-523149 | Jul 2002 | JP |
| WO 199015928 | Dec 1990 | WO |
| WO 199721457 | Jun 1997 | WO |
| 9804301 | Feb 1998 | WO |
| WO 199811927 | Mar 1998 | WO |
| WO 199857683 | Dec 1998 | WO |
| 9907425 | Feb 1999 | WO |
| WO 199921596 | May 1999 | WO |
| WO 199939118 | Aug 1999 | WO |
| WO 199948546 | Sep 1999 | WO |
| 0154753 | Aug 2001 | WO |
| WO 200172360 | Oct 2001 | WO |
| WO 200191822 | Dec 2001 | WO |
| WO 200191833 | Dec 2001 | WO |
| WO 200240083 | 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 |
| 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 |
| WO 2008089184 | Jul 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 |
| Entry |
|---|
| Collins and Lee, “Microfluidic flow transducer based on the measurement of electrical admittance,” Lab Chip, 2003, 12 pages. |
| Debiotech News Release, “Debiotech reveals its new miniaturized Disposable Insulin Nanopump™ for Diabetes therapy,” available at http://www.debiotech.com/news/nw_159.html Apr. 24, 2006, 3 pages. |
| Medtronic News Release, “Medtronic Receives FDA Approval for World's First Insulin Pump with Real-time Continuous Glucose Monitoring,” Apr. 13, 2006, 3 pages. |
| Patent Abstracts of Japan, vol. 1999, No. 04, and JP 11 010036 , Apr. 30, 1999 and Jan. 19, 1999, Toray Ind. Inc., 6 pages. |
| Walsh et al.,“Guidelines for Optimal Bolus Calculator Settings in Adults”, J. Diabetes Science and Technology, Jan. 2011, 5(1):7 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. |
| Asante Pearl, Insulin Pump User Manual, 2012, 180 pages. |
| International Search Report and Written Opinion in International Application No. PCT/US2014/047023, dated Nov. 28, 2014, 19 pages. |
| Supplemental European Search Report in Application No. EP 14826694, dated Jul. 1, 2016, 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>. |
| “Using the Deltec Cozmo Insulin Pump Correction Bolus Feature” believed to be publicly available before May 5, 2008, pp. 36-41. |
| “Which Insulin Pump is Right for Me?”, Albany Medical Center, Goodman Diabetes Service, Jan. 2006, 4 pages. |
| 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. |
| 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. filed Dec. 23, 2005., U.S. Appl. No. 60/753,984. |
| U.S. Appl. No. 11/362,616. |
| U.S. Patent Application filed on Nov. 8, 2005., U.S. Appl. No. 60/734,382. |
| U.S. Provisional Application filed on Dec. 23, 2005., U.S. Appl. No. 60/753,684. |
| 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/ful1/2/7/13, 3 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20180161495 A1 | Jun 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15383176 | Dec 2016 | US |
| Child | 15893145 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13946330 | Jul 2013 | US |
| Child | 15383176 | US |
