Safety limits for closed-loop infusion pump control

Abstract

A system and process for providing safety limits on the delivery of an infusion formulation by an infusion pump system in response to a sensed biological state. The safety limits may comprise user-initiated event signals corresponding to events that may significantly affect the biological state. The safety limits may further comprise user-initiated event ranking signals for respective events which specify a degree, quantity, or measure for the respective event. The user-initiated event and event ranking signals may be communicated to a computing element associated with the infusion pump by an associated communication device having a user interface which comprises a plurality of user-selectable operators for entering information about the events and event rankings.

Claims

1. An infusion pump system for delivering an infusion media to a user, the infusion pump system comprising: a sensing device to monitor glucose levels in the user; a user interface for receiving user input relating to a food ingestation event; a pump for delivering an infusion media to a user; a computing element operatively connected to the pump and configured to adjust delivery of the infusion media dependent at least in part on glucose levels monitored by the sensing device and at least in part on user input received through the user interface; the computing element configured to adjust delivery of the infusion media by the pump, based at least in part on an initial user input received by the user interface, relating to the food ingestation event, the computing element configured to further adjust delivery of the infusion media by the pump, based at least in part on an updated user input received by the user interface, relating to the food ingestation event.

2. An infusion pump system as recited in claim 1, wherein the computing element is configured to further adjust delivery of the infusion media by the pump, based at least in part on both the initial input relating to the at least one food ingestation event and the updated input relating to the at least one food ingestation event.

3. An infusion pump system as recited in claim 1, wherein the computing element is configured to dynamically adjust delivery of the infusion media by the pump based at least in part on the updated input at a time when the pump is already delivering the infusion media based at least in part on the initial input.

4. An infusion pump system as recited in claim 1, wherein the initial input relating to the at least one food ingestation event comprises an initial event ranking and wherein the updated input relating to the at least one food ingestation event comprises an updated event ranking that is different from the initial event ranking.

5. An infusion pump system as recited in claim 1, wherein: the initial event ranking comprises a ranking selected from a plurality of rankings that include first, second and third rankings, where the first ranking is lighter than the second ranking, and wherein the second ranking is lighter than the third ranking; and the updated event ranking comprises a different ranking selected from the plurality of rankings that include first, second and third rankings.

6. An infusion pump system as recited in claim 1, wherein: the initial event ranking comprises a ranking selected from a plurality of rankings comprising a light ranking, a moderate ranking and a heavy ranking; and the updated event ranking comprises a different one of the plurality of rankings.

7. An infusion pump system as recited in claim 1, further comprising electronic memory for storing data corresponding to a history of user input relating to one or more food ingestation events.

8. An infusion pump system as recited in claim 1, further comprising electronic memory for storing data corresponding to a history of user input corresponding to one or more rankings of one or more food ingestation events.

9. An infusion pump system as recited in claim 1, further comprising a display device associated with the user interface, the display device coupled to the computing element and configured, with the computing element, to display a plurality of user selectable data relating to a food ingestation event.

10. An infusion pump system as recited in claim 1, wherein the initial input relating to the food ingestation event comprises input corresponding to an amount of carbohydrates, and wherein the updated input relating to the food ingestation event comprises input corresponding to a different amount of carbohydrates relative to the initial input.

11. An infusion pump system as recited in claim 1, wherein the initial input relating to the food ingestation event comprises input corresponding to an amount of at least one of fat and protein, and wherein the updated input relating to the food ingestation event comprises input corresponding to a different amount of at least one of fat and protein relative to the initial input.

12. An infusion pump system as recited in claim 1, wherein the food ingestation event comprises a single meal.

13. A method of making an infusion pump system for delivering an infusion media to a user, the method comprising: providing a sensing device to monitor glucose levels in the user; providing a user interface for receiving user input relating a food ingestation event; providing a pump for delivering an infusion media to a user; coupling a computing element to the pump; and configuring the computing element to adjust delivery of the infusion media dependent at least in part on glucose levels monitored by the sensing device and at least in part on user input received through the user interface; further configuring the computing element to adjust delivery of the infusion media by the pump, based at least in part on an initial user input received by the user interface, relating to the food ingestation event; and further configuring the computing element to further adjust delivery of the infusion media by the pump, based at least in part on an updated user input received by the user interface, relating to the food ingestation event.

14. A method as recited in claim 13, further comprising configuring the computing element to further adjust delivery of the infusion media by the pump, based at least in part on both the initial input relating to the at least one food ingestation event and the updated input relating to the at least one food ingestation event.

15. A method as recited in claim 13, further comprising configuring the computing element to dynamically adjust delivery of the infusion media by the pump based at least in part on the updated input at a time when the pump is already delivering the infusion media based at least in part on the initial input.

16. A method as recited in claim 13, wherein the initial input relating to the at least one food ingestation event comprises an initial event ranking and wherein the updated input relating to the at least one food ingestation event comprises an updated event ranking that is different from the initial event ranking.

17. A method as recited in claim 13, wherein: the initial event ranking comprises a ranking selected from a plurality of rankings that include first, second and third rankings, where the first ranking is lighter than the second ranking, and wherein the second ranking is lighter than the third ranking; and the updated event ranking comprises a different ranking selected from the plurality of rankings that include first, second and third rankings.

18. A method as recited in claim 13, wherein: the initial event ranking comprises a ranking selected from a plurality of rankings comprising a light ranking, a moderate ranking and a heavy ranking; and the updated event ranking comprises a different one of the plurality of rankings.

19. A method as recited in claim 13, further comprising providing an electronic memory for storing data corresponding to a history of user input relating to one or more food ingestation events.

20. A method as recited in claim 13, wherein the initial input relating to the food ingestation event comprises input corresponding to an amount of carbohydrates, and wherein the updated input relating to the food ingestation event comprises input corresponding to a different amount of carbohydrates relative to the initial input.

21. A method as recited in claim 13, wherein the initial input relating to the food ingestation event comprises input corresponding to an amount of at least one of fat and protein, and wherein the updated input relating to the food ingestation event comprises input corresponding to a different amount of at least one of fat and protein relative to the initial input.

22. A method as recited in claim 13, wherein the food ingestation event comprises a single meal.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 shows a fragmented cutaway view of an exemplary environment of use for embodiments of the present invention in the peritoneal delivery of an insulin formulation.

(2) FIG. 2 shows a flowchart of a closed-loop algorithm for adjusting insulin formulation delivery as a function of the rate of change over time of a sensed glucose level and/or a user-initiated signal according to an embodiment of the invention.

(3) FIG. 3 shows an exemplary communication device user interface comprising a plurality of user-selectable operators corresponding to particular events, according to an embodiment of the invention.

(4) FIG. 4 shows an exemplary communication device user interface comprising a plurality of user-selectable operators for selecting various event rankings corresponding to particular events, according to an embodiment of the invention.

(5) FIG. 5 shows an exemplary communication device user interface comprising a display for displaying events and event ranking information to a user, along with user-selectable operators for selecting and entering the events and event ranking information, according to an embodiment of the invention.

(6) FIG. 6 shows an exemplary communication device user interface comprising an event ranking selection screen, according to an embodiment of the invention.

(7) FIG. 7 shows an exemplary communication device user interface comprising a display for entering detailed dietary information about a meal event, according to an embodiment of the invention.

(8) FIG. 8 shows an exemplary communication device user interface comprising a display for displaying a menu of selectable food types, according to an embodiment of the invention;

(9) FIG. 9 shows an exemplary communication device user interface comprising a display for displaying a menu of foods corresponding to a selected food type, according to an embodiment of the invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

(10) In the following description of preferred embodiments, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration specific embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural changes may be made without departing from the scope of preferred embodiments of the present invention.

(11) Environment of Use

(12) As discussed above, the present invention relates generally to infusion pump systems for the delivery of infusion formulations. The invention may be employed in various infusion environments including, but not limited to a biological implant environment. In preferred embodiments, the infusion pump system and process is configured for an implant environment within a human body, as shown in FIG. 1. However, other embodiments may be employed in other biological implant or non-implant environments.

(13) Furthermore, in preferred embodiments, the infusion pump system and process is configured for delivery of an insulin formulation used to regulate glucose levels in a diabetic user. However, other embodiments may be employed in the delivery of other infusion formulations having other pharmacological properties.

(14) As discussed above, FIG. 1 shows IIP 10 according to an embodiment of the invention. IIP 10 may be configured to be surgically implanted into a user, for example, at a particular location in the venous system, along the spinal column, in the peritoneal cavity, or other suitable site to deliver an infusion formulation to the user. However, further embodiments of the invention may be implemented as external infusion pumps, which connect to patients through suitable catheter devices or the like.

(15) Infusion Pump System

(16) The infusion pump system according to preferred embodiments of the invention employs a pump for delivering measured doses of an infusion formulation. In one embodiment, the pump comprises an electromagnetic mechanism that is activated to selectively drive infusion formulation to the user. The pump may be activated according to a programmed dispensing rate or schedule, or according to an actuation signal from a sensing device, timer, manual operator or other suitable means. In one preferred embodiment, the pump may be activated by a control signal communicated to the pump from a computing element which may be included in the infusion pump system.

(17) The infusion pump system according to preferred embodiments of the invention further employs a sensing device for monitoring a selected biological state. In one embodiment, the selected biological state to be monitored may be the glucose level detected in the body of the pump user.

(18) The infusion pump system according to preferred embodiments of the invention further employs a computing element which may, along with other pump control functions, execute a closed-loop algorithm which may continuously adjust infusion formulation delivery as a function of the sensed biological state. In one preferred embodiment, the closed-loop algorithm may continuously adjust insulin formulation delivery as a function of the rate of change of glucose levels over time. The computing element may comprise one or more programmable processors, logic circuits, or other hardware, firmware or software components configured for implementing the control functions described herein.

(19) The infusion pump system according to preferred embodiments of the invention further employs a communication device for communicating user-initiated signals to the computing element. The user-initiated signals may be representative of events that affect the selected biological state. In one preferred embodiment, the communication device communicates with the computing element via a radio frequency (“RF”) transceiver. However, in other embodiments other suitable means of data communication may be employed, such as, for example, ultrasonics.

(20) Events Affecting Glucose Levels

(21) As discussed above, certain events may significantly affect glucose production levels in the human body. Thus, these events may also significantly affect the amount of insulin produced in order to metabolize the glucose. For example, the ingestion of food may significantly increase the production of glucose in the body. This results in part from the fact that during digestion carbohydrates are broken down into glucose that then enters the bloodstream.

(22) In addition, the amount and type of foods ingested affect the amount of glucose produced.

(23) Similarly, exercise has been shown to lower glucose levels in the human body. Thus, exercise may result in a dip in glucose levels and a corresponding decrease in the amount of insulin formulation delivered by the body. Longer or more strenuous exercise events may result in a greater dip in glucose level than shorter and less strenuous exercise events.

(24) Furthermore, sleep and stress may affect the body's ability to burn carbohydrates and therefore may affect glucose levels. For example, glucose metabolism has been found to be slower in asleep deprived state. In addition, elevations of certain stress hormones within the body may also result in slower glucose metabolism. Thus, longer or shorter periods of sleep or stress may result in more or less significant changes in glucose levels.

(25) An additional event that may affect insulin production is the ingestion of medication. Certain medications may affect an individual's sensitivity to insulin, i.e. a given amount of insulin may be more or less sufficient depending on whether a particular medication has been taken. The insulin sensitivity level of a user to a particular medication may be determined either by the user or by the user's physician, for example, by observing the user's glucose level after taking a particular medication.

(26) Closed-Loop Algorithm Safety Limits

(27) An infusion pump system for the automatic regulation of the delivery of insulin formulation should detect changes in glucose levels that may result from any of these events and adjust the amount of insulin formulation delivered accordingly. In an exemplary infusion pump system for the automatic regulation of the delivery of insulin formulation, a sensing device used in conjunction with the infusion pump may detect changes in the glucose level and provide this information as an input to a closed-loop algorithm. The typical closed-loop algorithm may then accordingly adjust the amount of insulin formulation delivered to the user.

(28) However, dangers exists in the typical infusion pump system for the automatic regulation of the delivery of insulin formulation. One of the dangers is that the input to the closed-loop algorithm may be erroneous. In typical existing infusion pump systems for the automatic regulation of the delivery of insulin formulation, there may be no safety limits on the amount of insulin formulation that is delivered based on an erroneous input. In other words, the typical closed-loop algorithm may only examine the glucose level input and may have no way to verify whether the change in glucose level is a reasonable change, i.e., one that is consistent with an event affecting glucose levels.

(29) Furthermore, as discussed above, the human body shows evidence of a leading insulin secretion reflex in response to anticipation of the ingestion of a meal. Typical existing infusion pump systems for the automatic regulation of the delivery of insulin formulation may not replicate this reflex, because the delivery of insulin formulation by the pump may not occur until triggered by the detection of glucose by the sensing device.

(30) Therefore, according to preferred embodiments of the infusion pump system and process, the communication device comprises a user interface for entering user-initiated signals representative of events which may affect glucose levels in a biological system such as the human body. The user-initiated signals are provided to a computing element within the system which executes a closed-loop algorithm for adjusting insulin formulation delivery as a function of, for example, the rate of change over time of a sensed glucose level.

(31) FIG. 2 shows a flowchart of a closed-loop algorithm for adjusting insulin formulation delivery as a function of the rate of change over time of a sensed glucose level which incorporates one embodiment of the invention's system and process. As shown in step 202, the closed-loop algorithm may continuously check for changes in glucose level. A sensing device may detect the change in glucose level and may communicate the change to the computing element as a glucose level input to the algorithm. If no change is detected, the closed-loop algorithm may loop back to step 202, repeating this process until a change is detected. When a change occurs, the closed-loop algorithm may determine whether the amount of insulin formulation required based on the change in glucose level is within normal basal limits for the user, as shown in step 204.

(32) The normal basal limits for the user may have been pre-programmed into the algorithm by the user or the user's physician, The normal basal limits may include maximum and minimum values of insulin formulation that may be delivered at one time. For example, if the user is in a basal state (i.e., a state requiring a basal rate of insulin secretion), the closed-loop algorithm may limit the delivery of insulin formulation to a maximum of fifty percent higher than a pre-programmed nominal basal rate of delivery. Similarly, the closed-loop algorithm may not allow the delivery rate to drop below a minimum allowable rate, for example, 0.2 units per hour.

(33) Furthermore, the user (or the user's physician) may pre-program a user's basal profile into the closed-loop algorithm. This basal profile may indicate to the closed-loop algorithm, for example, that the user has a lower need for insulin at night.

(34) Referring again to FIG. 2, if the change in glucose level requires an amount of insulin formulation that is within the pre-programmed basal limits and profile, the closed-loop algorithm may make a suitable adjustment to the delivery rate, as shown in step 206. The closed-loop algorithm may then loop back to step 202, repeating steps 204 through 206 described above.

(35) However, if the detected change in glucose level requires the delivery of an amount of insulin formulation not within the basal limits or profile of the user, the closed-loop algorithm may scan “event inputs” to the closed-loop algorithm in order to determine if a user-initiated signal is present, as shown in step 208. If a user-initiated signal is present, the closed-loop algorithm may then process the signal to determine the adjustment in the insulin formulation delivery rate that corresponds to the user-initiated signal that is present at the event input, as shown in step 210.

(36) On the other hand, in one embodiment, if no user-initiated signal is present at the event input to the closed-loop algorithm, the user may be queried, for example, via the communication device user interface, whether an event has occurred which requires the user to communicate a signal to the computing element, as shown in step 212. The communication device user interface may include user-selectable responses to the query.

(37) If the user confirms that an event has occurred, as shown in step 214, the user may then be prompted to select the event, as shown in step 216. Once the user-initiated signal corresponding to the selected event is received at an event input of the closed-loop algorithm. The closed-loop algorithm may then process the signal to determine the adjustment in the insulin formulation delivery rate that corresponds to the user-initiated signal that is present at the event input, as shown in step 218.

(38) In one preferred embodiment, if the user does not confirm that an event requiring an insulin formulation delivery amount outside of the pre-programmed basal limits has occurred, the closed-loop algorithm may alert the user to a possible malfunction in the infusion pump system, as shown in step 220. The closed-loop algorithm may then cease automatic control of the infusion pump and return to a manual operation so that the user or the user's physician may control the delivery rate.

(39) Furthermore, in one preferred embodiment, the closed-loop algorithm may be programmed to perform diagnostic checks to ensure that a user-initiated signal communicated to an event input of the closed-loop algorithm is consistent with the glucose level detected by the sensing device. For example, if the user enters a meal event and the sensing device does not detect a corresponding change in the glucose level within a pre-programmed time, the closed-loop algorithm may alert the user to a possible malfunction in the infusion pump system. The closed-loop algorithm may then cease automatic control of the infusion pump and return to a manual operation so that the user or the user's physician may control the delivery rate.

(40) As shown by the flowchart in FIG. 2, embodiments of the invention's system and process advantageously incorporates safety limits into the closed-loop algorithm to ensure that insulin formulation delivery amounts outside of a pre-programmed normal basal delivery rate correspond to events which may significantly affect glucose level. These events may be communicated by the user to the closed-loop algorithm event inputs via a communication device user interface. In one preferred embodiment, the events that may significantly affect glucose levels may comprise, for example, a meal event, an exercise event, a sleep event, a stress event, and a medication event.

(41) Communication Device User Interface

(42) The events may be communicated by the user to the closed-loop algorithm event inputs via a communication device user interface. User-selectable operators may be provided on the communication device user interface which allow a user to initiate a signal representing an event.

(43) Thus, for example, the user may be able to press or otherwise select a user-selectable operator representing a sleep event before the user sleeps. In preferred embodiments, the closed-loop algorithm accepts the user-initiated signal at an event input and verifies that the glucose level input provided by the sensing device is consistent with the presence of the user-initiated signal at the event input of the closed-loop algorithm, as described above in relation to FIG. 2.

(44) In one preferred embodiment, a user-initiated signal may initiate changes in the delivery amount of the infusion formulation independently of the sensing device input. For example, in one embodiment, a user may select a “meal” user-selectable operator on the user interface when the user is about to consume a meal. The user-initiated signal corresponding to the meal event communicated to the computing element may then initiate an immediate bolus delivery of insulin formulation by the pump even though the sensing device has not yet detected any rise in the glucose level.

(45) Thus, the naturally occurring leading insulin secretion reflex phenomenon may be advantageously replicated by preferred embodiments of the infusion pump system and process by programming the closed-loop algorithm to deliver a suitable amount of insulin formulation based on the signal initiated by the user selecting the “meal” user-selectable operator. without the sensing device detecting any rise in glucose level.

(46) In other preferred embodiments, the user interface may comprise user-selectable operators for selecting an “event ranking,” for example, a degree, quantity, or measure of the selected event. As an example, if the user has selected a meal event, the user may be able to supplement this event information by selecting the size of the meal, for example, “light,” “moderate,” or “heavy.” In addition, in some preferred embodiments, the user may be able to further supplement the event information by entering dietary information about the meal. For example, the user may be able to enter the meal's carbohydrate content, fat content, or other dietary information about the meal to be consumed. This information may be used to more accurately determine the expected effect of the meal on the glucose level.

(47) In yet other preferred embodiments, if the user initially inputs one size for a meal but later decides to eat more or less, the user may be able to update the meal information although delivery of the insulin formulation by the infusion pump is already in progress based on the initial input. This may be done, for example, by selecting and inputting the event ranking which corresponds to the new size of the meal. In this embodiment, the computing element may dynamically (i.e. while delivery is in progress) re-calculate the amount of insulin formulation delivered based on both inputs.

(48) As an example of this embodiment, the user may first select a light meal and input a corresponding signal. Then, after delivery is in progress, the user may decide that a heavy meal is preferable. The user may then select and input the event ranking which corresponds to a heavy meal. The computing element may then dynamically adjust the amount of insulin formulation delivered based on both the light and heavy inputs.

(49) Similarly, the user interface may comprise user-selectable operators for selecting an event ranking for an exercise event. As an example, if the user has selected an exercise event, the user may be able to supplement this event information by selecting the type of exercise, the duration of the exercise, and/or whether the exercise is “light,” “moderate,” or “heavy.”

(50) In addition, the user interface may comprise user-selectable operators for selecting an event ranking for a sleep event. As an example, if the user has selected a sleep event, the user may be able to supplement this event information by selecting the amount of time the user expects to sleep.

(51) Alternatively, the user may select an event ranking such as, but not limited to, “short,” “moderate,” or “long,” corresponding to a short, moderate, or long interval of sleep. As an additional example, the user may simply press a “sleep” user-selectable operator before the sleep event and a “wake” user-selectable operator when the user awakes. In addition, or in the alternative, some preferred embodiments may enable the user to enter a time when the user expects to wake and the computing element may automatically calculate the duration of the sleep event and adjust the amount of delivered insulin formulation accordingly.

(52) The user interface may further comprise user-selectable operators for selecting an event ranking for a stress event. As an example, if the user has selected a stress event, the user may be able to supplement this event information by selecting the ranking of stress, for example, “light,” “moderate,” or “heavy.”

(53) Furthermore, the user interface may comprise user-selectable operators for selecting an event ranking for a medication event. As an example, if the user has selected a medication event, the user may be able to supplement this event information by selecting the type of medication and/or the amount of the medication.

(54) Alternatively, the user interface may comprise user-selectable operators which enable the user to, for example, simply select a level of sensitivity to insulin that is associated with the ingestion of a particular medication. A particular user's insulin sensitivity level associated with the ingestion of a particular medication may have been previously determined either by the user or by the user's physician. For example, a particular user's insulin sensitivity level may have been previously determined by observing the user's glucose level after taking the medication, Thus, the medication event ranking may be, for example, “low,” “moderate,” or “high,” corresponding respectively to a low, moderate, or high sensitivity to insulin after taking a particular medication.

(55) In one embodiment, the user-initiated signals are communicated to the computing element where they may be provided as an input to the closed-loop algorithm. The closed-loop algorithm may then incorporate the user-initiated signals into the algorithm's calculation of insulin formulation output, as described in reference to FIG. 2.

(56) FIG. 3 illustrates an example of a communication device user interface according to one preferred embodiment. In preferred embodiments, the communication device 300 is provided with a power source, for example, a battery, independent of the infusion pump power source. In other embodiments, the communication device 300 may be powered from the infusion pump power source.

(57) Communication device 300 comprises an outer case or housing. This case or housing may be plastic, metal, or any other suitable material. Situated on the outer housing is the user interface. In the present preferred embodiment, the user interface comprises a plurality of user-selectable operators, each of the plurality of user-selectable operators corresponding to a particular event. Thus, communication device 300 comprises a simple user interface which enables a user to select an event simply by pressing or otherwise selecting the corresponding user-selectable operator.

(58) In one preferred embodiment, the user may confirm the selection of an event by selecting an “enter” user-selectable operator 314. The inclusion of the “enter” user-selectable operator 314 may provide a measure of safety against accidental selection of an event user-selectable operator by, for example, bumping the communication device against another object. Thus, both the user-selectable operator corresponding to the desired event and the “enter” user-selectable operator 314 must be depressed in succession in order for a signal to be communicated to the computing element. In another embodiment, a confirmation screen may be used for a particularly important event, such as, for example, delivering a bolus. For example, upon the entering of a large meal event, the screen may respond by displaying “Large Meal Entered. Confirm?” Then, the user may depress enter again to confirm the event. This operation provides an extra level of safety.

(59) In other embodiments, the “enter” user-selectable operator may be absent and other safety measures used against accidental selection. For example, in one embodiment, the user-selectable operators may be situated in a recessed portion of the communication device housing in order to avoid accidental selection. The user may be provided with a selection device, for example, a wand or pointer device, in order to access the user-selectable operators. In yet other embodiments, both safety measures may be employed.

(60) In the embodiment of the communication device user interface shown in. FIG. 3, a user may select the “meal” user-selectable operator 302 and then select the “enter” user-selectable operator 314 in order to communicate a signal to the computing element that the user is about to ingest a meal or is currently ingesting a meal. The closed-loop algorithm may then receive the user-initiated signal as an event input. In preferred embodiments, the computing element may confirm that the user-initiated signal was received, for example, by beeping, displaying a “signal received message,” or other suitable method of informing the user that the computing element has received the signal.

(61) Similarly, the user may select user-selectable operators 304, 306, 308, 310, or 312 in order to select the “exercise,” “sleep,” “wake,” “medication,” and “stress” events, respectively, and then select the “enter” user-selectable operator 314 in order to communicate the respective signal to the computing element that the user is about to exercise, is about to sleep, is now awake after sleeping, has taken medication, or is experiencing stress.

(62) The embodiment of the communication device user interface shown in FIG. 3, advantageously provides the user with a user-friendly interface for communicating event information to the computing element. The amount of event information communicated to the computing element is kept to a minimum. However, embodiments of the infusion pump system and process may advantageously use even this minimal amount of event information to provide safety limits to insulin formulation delivery. For example, in one preferred embodiment using the communication device user interface shown in FIG. 3, the user's physician may be provided with password-protected access to the user's communication device in order to modify the closed-loop algorithm in accordance with parameters specific to the user.

(63) As an example, a physician may determine the impact that taking a particular medication may have on the user's insulin sensitivity. The physician may then program the closed-loop algorithm in such a way that when the event input to the closed-loop algorithm receives a user-initiated signal corresponding to the “medication” user-selectable operator 310, the closed-loop algorithm may adjust the insulin formulation delivery in accordance with the physician's programmed instructions.

(64) Similarly, the physician may modify the closed-loop algorithm to respond in a particular way to the selection by the user of user-selectable operators corresponding to other events. In addition, in some preferred embodiments, the computing element may maintain a history of user-initiated events that may be accessed by the user and/or the physician. For example, a history of the pump user's “meal” events may be maintained and accessed by the physician. The physician may advantageously use this information to advise the user on, for example, lifestyle patterns that may be affecting the user's health and well-being.

(65) FIG. 4 illustrates an example of a communication device user interface according to another preferred embodiment. Communication device 400 is provided with a power source, for example, a battery, independent of the infusion pump power source. In other embodiments, the communication device 400 may be powered from the infusion pump power source.

(66) Communication device 400 comprises an outer case or housing. This case or housing may be plastic, metal, or any other suitable material. Situated on the outer housing is the user interface. In the present preferred embodiment, the user interface comprises a plurality of user-selectable operators for selecting various event rankings corresponding to particular events. The events may be indicated on the communication device 400 user interface by printed words, pictures, or other indicia representing the event. As an example, in FIG. 4, the events are indicated vertically along the left side of the communication device 400 user interface as “meal” 402, “exercise” 410, “stress” 418, “sleep” 426, and “medication” 434.

(67) Event rankings associated with each event are situated to the right and in the same row as the associated event. In the embodiment shown in FIG, 4, the event indicators are not selectable but merely indicate the event associated with the user-selectable operators located in that particular row. For example, “meal” 402 event indicator is not selectable, but merely indicates that event rankings “light” 404, “moderate” 406, and “heavy” 410, located in the row indicated by reference numeral 401, are event rankings associated with the “meal” 402 event.

(68) Similarly, event rankings “light” 412, “moderate” 414, and “heavy” 416 are event rankings associated with the “exercise” 410 event; event rankings “light” 420, “moderate” 422, and “heavy” 424 are event rankings associated With the “stress” 418 event; event rankings “short” 428, “moderate” 430, and “long” 432 are event rankings associated with the “sleep” 426 event; and event rankings “low” 436, “moderate” 438, and “high” 440 are event rankings associated with the “medication” 434 event.

(69) In addition to the event ranking user-selectable operators described above, the communication device 400 user interface also comprises an “enter” user-selectable operator 442 which operates in a manner similar to that of “enter” user-selectable operator 314 described above in relation to FIG. 3.

(70) In the embodiment of the communication device 400 user interface shown in FIG. 4, the user is able to enter more detailed information about a particular event than was the case for the communication device 300 user interface, shown in FIG. 3. As an example, for a “meal” event the user may locate the row on the communication device 400 user interface that has the “meal” 402 indicator. To the right of the “meal” 402 indicator there are three event rankings associated with the “meal” event, “light” 404, “moderate” 406, and “heavy” 408. These event rankings correspond, generally, to a light meal, a moderate meal, and a heavy meal, respectively.

(71) Although in the embodiment shown in FIG. 4 there are three event rankings associated with each event, other embodiments may have more or less than three event rankings associated with a particular event. Furthermore, although in the embodiment shown in FIG. 4 certain event rankings are associated with a particular event, other event rankings are also possible in other embodiments. For example, although in the embodiment shown in FIG. 4 the event rankings associated with a meal event are light, moderate, and heavy, in other embodiments the event ranking descriptions may comprise more accurate quantitative descriptions. For example, in one embodiment, the event rankings associated with the meal event could be “less than X grams of carbohydrates,” and “more than X grams of carbohydrates.” The effects for a particular user of selecting any one of these event ranking user-selectable operators may be pre-programmed into the closed-loop algorithm and may, in some embodiments, be modified by a user's physician as described above in relation to FIG. 3.

(72) FIG. 5 illustrates an example of a communication device user interface according to another preferred embodiment. Communication device 500 is provided with a power source, for example, a battery, independent of the infusion pump power source. In other embodiments, the communication device 500 may be powered from the infusion pump power source.

(73) Communication device 500 comprises an outer case or housing. This case or housing may be plastic, metal, or any other suitable material. Situated on the outer housing is the user interface. In the present preferred embodiment, communication device 500 user interface comprises display 502, “select” user-selectable operator 504, “enter” user-selectable operator 506, “cursor left” user-selectable operator 508, “cursor right” user-selectable operator 510, “cursor up” user-selectable operator 512, and “cursor down” user-selectable operator 514.

(74) Display 502 may comprise any electronic display device for representing images and text. Display 502 may comprise, for example, a liquid crystal display (“LCD”), a thin film transistor (“TFT”), or any other type of suitable display device. Communication device 500 user interface may enable the user to display particular information on display 502 by selecting the “select” user-selectable operator 504 either alone or in combination with one or more other user-selectable operators.

(75) For example, by initially selecting “select” user-selectable operator 504, a menu of events may be displayed to the user, as shown in FIG. 5. The user may then scroll through events on the menu by, for example, using the cursor user-selectable operators 508, 510, 512, and 514. The cursor highlights the currently selected event. In FIG. 5, the currently selected event is the “meal” event. In one preferred embodiment, once the desired event is highlighted, the user may then select the “enter” user-selectable operator 506 to proceed, for example, to an event ranking menu, as displayed in display 602, shown in FIG. 6.

(76) FIG. 6 shows an event ranking selection screen on display 502 of the communication device 500 user interface. Assuming that the user selected the meal event, the event rankings associated with the “meal” event are displayed on display 502. In one preferred embodiment, these event rankings are “light,” “moderate” and “heavy.” The user may then scroll through the displayed event rankings on the menu by, for example, using the cursor user-selectable operators 508, 510, 512. and 514. The cursor highlights the currently selected event ranking. In FIG. 6, the currently selected event ranking is the “light” event ranking. In one preferred embodiment, once the desired event ranking is highlighted, the user may then select, for example, the “enter” user-selectable operator 506 or the “select” user-selectable operator 504 to communicate a signal corresponding to the selected event ranking to the computing element.

(77) FIG. 7 shows another embodiment of the communication device 500 user interface wherein more detailed information may be entered regarding the meal event. In the embodiment of the communication device 500 user interface shown in FIG. 7, particular dietary substances and/or compounds may be displayed to the user in display 502. The user may enter an amount for each substance and/or compound. The amount may be expressed in a suitable unit of measurement, for example in grams. As an example, the user may use the cursor user-selectable operators 508, 510, 512, and 514 to highlight a particular substance or compound, The user may then select, for example, the “select” user-selectable operator 504 to select the substance or compound currently highlighted.

(78) The user may then use, for example, the “cursor up” user-selectable operator 512 and “cursor down” user-selectable operator 514 to either increase or decrease, respectively, the displayed units of measurement. When the user has entered the dietary information, the user may select the “enter” user-selectable operator 506 in order to communicate the dietary information to the computing element.

(79) In yet other preferred embodiments, the user may select foods from food menus, as shown in FIG. 8. In one preferred embodiment, a menu of selectable food types may be displayed to the user in display 502 of the communication device 500 user interface after the meal event has been selected by the user. The user may then use the cursor user-selectable operators 508, 510, 512, and 514 to highlight a particular food type. In FIG. 8, the user has highlighted the “vegetable” food type. The user may then select, for example, the “select” user-selectable operator 504 or the “enter” user-selectable operator 506 in order to select the food type currently highlighted.

(80) In one preferred embodiment, when the currently highlighted food type is selected, a menu of foods corresponding to that food type may be displayed to the user, as shown in FIG. 9. FIG. 9 shows a selectable menu of vegetables in display 502. The user may use the cursor user-selectable operators 508, 510, 512, and 514 to highlight a particular vegetable. In one embodiment, the user may then use, for example, the “cursor up” user-selectable operator 512 and “cursor down” user-selectable operator 514 to either increase or decrease, respectively, the displayed number of serving sizes. Once the number of serving sizes has been selected, the user may then select, for example, either the “enter” user-selectable operator 506 or the “select” user-selectable operator 504 in order to communicate the dietary information to the computing element.

(81) In preferred embodiments of the communication device 500 user interface shown in FIGS. 8 and 9, information about a particular food, such as, but not limited to, grams of fat per serving, grams of carbohydrates per serving, and grams of protein per serving, may be stored in a storage device located, for example, either in the computing element or within the communication device 500 itself. Thus, when a user selects a particular food and serving size, the dietary information may be calculated automatically by the computing element using the previously stored information. The closed-loop algorithm may then advantageously use this dietary information to more accurately determine the amount of insulin formulation to deliver.

(82) Therefore, embodiments of the invention's infusion pump system and process provide a communication device user interface for entering user-initiated signals for communication to a computing element within the system. The user-initiated signals may be provided as event inputs to a closed-loop algorithm executed by a computing element. When the system's sensing device detects changes in a biological state, the closed-loop algorithm may be programmed to verify that an event input is present before delivering an amount of infusion formulation outside of pre-programmed basal limits.

(83) The amount of insulin formulation to be delivered based on a particular event may be determined by pre-programmed data concerning the user. This pre-programmed data may be entered, for example, by the user and/or the user's physician or other medical professional. Thus, the event inputs provide safety limits to the amount of infusion formulation delivered in response to changes in a particular biological state.

(84) Accordingly, a number of aspects and features of preferred embodiments of the communication device user interface described above may provide individually, or may be combined to provide user-initiated signals to a computing element within an infusion pump system. However, the foregoing description of preferred embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teaching.

(85) For example, the events described above in preferred embodiments of the invention's system and process are examples of events which may lead to changes in insulin production by the pancreas of a non-diabetic person, and for which a user-initiated signal may be provided to a closed-loop algorithm. However, the above-named events should not be considered to be a limitation on the events which may affect glucose levels in the human body, and thus on the events for which a user-initiated signal may be provided to the closed-loop algorithm by embodiments of the invention's system and process.

(86) Having disclosed exemplary embodiments and the best mode, modifications and variations may be made to the disclosed embodiments while remaining within the scope of the invention as defined by the following claims.