Patent Description:
Conventional basal insulin management systems require a user to manually enter start times, end times, and basal rates for each time segment of a basal program in a tabular format. Once data for each time segment is entered, these conventional systems display the basal program built by the user in a time-based tabular format. Users are typically overwhelmed with the time-based tabular format of the presented data. As a result, users often make mistakes when entering data or may be less likely to make adjustments to the basal program when doing so would be beneficial, thereby reducing the effectiveness of the diabetes management system.

<CIT> relates to techniques for simultaneously displaying representations , such as graphical representations, of both a selected dosing program of an implantable fluid delivery device and a pending dosing program of the implantable fluid delivery device. In one example, a system includes an implantable fluid delivery device that delivers fluid to a patient according to a selected dosing program, and a programmer device that includes a user interface comprising a display to present a graphical representation of doses of fluid to be delivered to a patient via an implantable fluid delivery device, and a processor that controls the user interface to simultaneously present on the display a first indication of a selected dosing program of the implantable fluid delivery device and a second indication of a pending dosing program of the implantable fluid delivery pump. A user may therefore compare the selected dosing program with the pending dosing program.

Accordingly, what is needed is a basal insulin management system that presents information related to a basal insulin program in a more effective and intuitive manner, thereby increasing the effectiveness of the basal insulin management system.

The present invention relates to a system as defined in the claims.

This disclosure presents various systems, components, and methods related to a basal insulin management system and a user interface provided by the basal insulin management system. Each of the systems, components, and methods disclosed herein provides one or more advantages over conventional systems, components, and methods.

Various embodiments provide an improved basal insulin management system and an improved user interface for interacting with the basal insulin management system. In various embodiments, user interfaces are provided that dynamically display basal rate information and corresponding time segment information for a basal insulin program in a graphical format. The graphical presentation of the basal insulin program as it is being built by a user and the graphical presentation of a completed basal insulin program provides insulin management information to the user in a more intuitive and useful format. Various embodiments further provide user interfaces enabling a user to make temporary adjustments to a predefined basal insulin program with the adjustments presented graphically to improve the user's understanding of the changes. As a result of being provided with the user interfaces described herein, users are less likely to make mistakes and are more likely to adjust basal rates more frequently, thereby contributing to better blood glucose control and improved health outcomes.

<FIG> illustrates an exemplary block diagram of a portable electronic device <NUM>. The portable electronic device <NUM> can be, for example, a cellphone, a smartphone, a laptop, a tablet, or any other handheld and/or portable electronic computing device. The portable electronic device <NUM> can include a number of components as shown in <FIG>. Specifically, the portable electronic device <NUM> can include a communications interface <NUM>, a display and a display controller <NUM>, input devices and input device interfaces <NUM>, a central processing unit (CPU) or a processor <NUM>, and a memory <NUM>.

The communications interface <NUM> can facilitate communication between the portable electronic device <NUM> and a number of remote devices (not depicted in <FIG>. The communications interface <NUM> can provide communications over wired or wireless links or interfaces according to any known wired or wireless communication standard or protocol. For example, the communications interface <NUM> can enable the portable electronic device <NUM> to communicate with one or more remote devices using, for example, Wi-Fi, a cellular communications standard, or Bluetooth.

The display and display controller <NUM> can represent a visual display that can render visual information and a display controller for controlling the rendering of any visual information. The visual information can be any graphical or textual information. The display <NUM> can be a touchscreen or a touch-sensitive display. The input devices and input device interfaces <NUM> can represent any number of input devices and interfaces that can process any inputs provided through an input device. For example, the input devices <NUM> can include a mouse, a keyboard, a touchscreen, and/or a microphone. The input device interfaces <NUM> can include one or more receivers for receiving input signals from any corresponding input device.

The CPU or processor <NUM> can be a processor for executing instructions stored in the memory <NUM>. The processor <NUM> can control and direct operation of any of the components of the portable electronic device <NUM>. In particular, the processor <NUM> can control the operation or functionality of the communications interface <NUM>, the display/di splay controller <NUM>, and the input devices/input device interfaces <NUM>.

The communications interface <NUM>, the display/di splay controller <NUM>, and the input devices/input device interfaces <NUM> can be implemented in hardware, software, or any combination thereof. The portable electronic device <NUM> can include other modules.

components, or devices implemented in hardware, software, or any combination thereof and not shown in <FIG> to facilitate communication with remote devices, the receiving of input signals from a user, and the presentation of visual information to the user.

The portable electronic device <NUM> can operate with or as part of a diabetes management system (or other user monitoring and drug delivery system). For example, the portable electronic device <NUM> can operate with or as part of a diabetes management system that can control the delivery of insulin to a user. The portable electronic device <NUM> can be coupled to an insulin pump. For example, the portable electronic device <NUM> can be coupled to a drug delivery device such as the OmniPod® (Insulet Corporation, Billerica, MA) insulin delivery device and/or a drug delivery device such as those described in <CIT>, <CIT>, or <CIT>.

The portable electronic device <NUM> can further be coupled to any number of additional devices or components such as a glucose meter, remote sensors, and remote computing devices or servers. The processor <NUM> can execute instructions stored in the memory <NUM> to implement a diabetes management system - for example, to direct a drug delivery device to deliver a determined amount of insulin to a user based on one or more sensor inputs (e.g., data from a glucose monitoring device) and/or user inputs.

The portable electronic device <NUM> can provide a user interface to a user - for example, as part of a diabetes management system. The provided user interface can be used to control and monitor operation of the diabetes management system - such as controlling or monitoring delivery of insulin to a user over time.

The user interface can be provided by one or more of the components depicted in <FIG>. The user interface can be provided based on input signals received from communications interface <NUM> and input devices/input interfaces <NUM>. The display/display controller <NUM> can present the user interface visually and can modify the user interface based on such received input signals. Further, the display/di splay controller <NUM> can retrieve data - such as graphics, icons, and text - from the memory <NUM> for display on the user interface based on the received input signals.

Each of the constituent components of the portable electronic device <NUM> can operate based on direction provided by the processor <NUM> in order to provide the user interface. For example, the user interface may include different operational modes. When a different mode is selected, the display/di splay controller <NUM> can retrieve different graphics from the memory <NUM> for presentation on the display <NUM>. The different mode can be selected by the user through the touchscreen display <NUM> for example. Further, data received from a remote device by way of the communications interface <NUM> can also be presented on the user interface. Exemplary features of the user interface provided by the portable electronic device <NUM> are described in more detail herein.

<FIG> illustrates an exemplary drug delivery system <NUM>. The drug delivery system <NUM> can represent the drug delivery systems described herein. The drug delivery system <NUM> can include the portable electronic device <NUM>. The drug delivery system <NUM> can further include a drug delivery device <NUM> and a sensor <NUM>. The drug delivery device <NUM> can represent the drug delivery devices described herein. The drug delivery device <NUM> can administer any drug or therapeutic agent to a user. The sensor <NUM> can detect one or more physical, biological, and/or medical conditions of the user and can represent any of the sensors described herein. In various embodiments, the drug delivery device <NUM> can be an insulin drug pump (such as the insulin drug pump described herein) and the sensor <NUM> can be a glucose monitor. Generally, the drug delivery device <NUM> and the sensor <NUM> are worn on the body of the user. In various embodiments, the drug delivery device <NUM> and the sensor <NUM> can be combined into a single device.

As shown in <FIG>, the portable electronic device <NUM>, the drug delivery device <NUM>, and the sensor <NUM> can communicate over communications links <NUM>. The communication links <NUM> can be wired or wireless communication links that operate according to any known wired or wireless communication protocol or standard such as, for example, Wi-Fi, a cellular communications standard, or Bluetooth. The communication links <NUM> can provide bidirectional communication between each of the components of the drug delivery system <NUM> such that any data or information can be shared between the portable electronic device <NUM>, the drug delivery device <NUM>, and the sensor <NUM>.

In various embodiments, the drug delivery device <NUM> can deliver an amount of insulin to the user based on control or input provided by the portable electronic device <NUM>. The control of the drug delivery device <NUM> can be based on information provided by the sensor <NUM>. For example, glucose measurements of the user can be determined by the sensor <NUM> and shared with the portable electronic device <NUM>. The user, by interacting with the user interface provided by the portable electronic device <NUM>, can monitor, adjust, or otherwise control the delivery of insulin by the drug delivery device <NUM>. The user interface provided by the portable electronic device <NUM> can allow the user to adjust basal delivery of insulin to the user and can be used to initiate bolus deliveries of insulin. In various embodiments, the user interface provided by the portable electronic device <NUM> enables the user to specify basal delivery and to direct the drug delivery device <NUM> to provide insulin to the user in accordance with the basal delivery specified by the user as described further herein.

Many insulin pumps that operate as a part of a diabetes management system deliver small doses of insulin continuously throughout the day. This continuous delivery of small doses of insulin is often referred to as basal insulin. Each patient may need more or less insulin at certain times of the day based on a variety of factors. Many insulin pumps/diabetes management systems allow the patient to carve up a period of time into different time segments and to enter a rate of basal insulin delivery they desire during each individual time segment. Generally, users can create multiple time segments over a <NUM> hour period. The variable rates of insulin delivery within the time segments over <NUM> hours can define a basal program.

Conventional insulin pumps/diabetes management systems and their corresponding user interfaces require the user to manually enter start and end times to define a time segment and to manually enter the basal rate for each time segment in a tabular format. Basal programs are then displayed to the user in a time-based tabular format for confirmation. In contrast to these conventional systems and user interfaces, the user interface and techniques described herein allow the user to optionally view a static basal program graph after the basal program is completed and saved. Further, the user interface and techniques described herein enables a graph or timeline of the basal program to be displayed in real-time as the user builds the basal program. Specifically, the user interface and techniques described herein provides a graph showing the basal rates for each time segment as the basal program is built, thereby improving the experience of the user. The basal program can then be used to direct the delivery of insulin to the user - e.g., by having the basal program built on the portable electronic device <NUM> transferred to the drug delivery device <NUM> as instructions for implementation.

In various embodiments, the user interface and techniques described herein present a real-time basal program graph as the user builds her basal program. For example, at each step of the process, the graph can change to reflect the user's input and can immediately show the user the effect of the data that is entered as the user builds a basal program. <FIG> illustrate various embodiments of a user interface for building and depicting a basal program. The various embodiments depicted in <FIG> can be provided by the portable electronic device <NUM> as part of a diabetes management system/insulin delivery system as described herein (e.g., within the drug delivery system <NUM>).

<FIG> illustrates an exemplary user interface <NUM> for initially starting or creating a basal program. That is, <FIG> illustrates the user interface <NUM> provided to a user when the user first selects the option of adding or building a new basal program. The user interface <NUM> can be presented on the touchscreen of the portable electronic device <NUM> as described herein.

As shown in <FIG>, an identifier <NUM> specifies the type of program or mode being presented by the user interface <NUM>. As shown, the identifier <NUM> specifies that the user interface <NUM> is presenting an interface for building a basal program (e.g., by indicating "Create Basal Program" as shown).

A first portion of the user interface <NUM> can provide a graphical area of the user interface <NUM>. In particular, the graphical area <NUM> can be used to display data graphically or to enter or receive input data from a user in a graphical manner.

A second portion of the user interface <NUM> can provide a textual area of the user interface <NUM>. In particular, the textual area <NUM> can be used to display data textually or to enter or receive input data from the user in a textual manner.

Within the textual area <NUM>, various data labels or descriptions and corresponding data values can be presented. Specifically, a start time <NUM>, an end time <NUM>, and a basal rate <NUM>, along with corresponding values, can be presented. In various embodiments, as a default or as part of an initial presentation to the user, the start time <NUM> and end time <NUM> can be set to or can define a <NUM> hour interval. Additionally, a default basal rate <NUM> can be presented or a not yet defined basal rate <NUM> can be presented. The user, by interacting with the touchscreen on which the user interface <NUM> is presented, can adjust the start time <NUM>, the end time <NUM>, and the basal rate <NUM> by touching the corresponding value indicator areas and entering new values (e.g., through a pop-up keyboard or scroll wheel or other user input selection tool).

The start time <NUM> and end time <NUM> depicted textually in the area <NUM> can be depicted graphically in the area <NUM> on a timeline <NUM>. In particular, a start bar <NUM> can graphically represent the start of a basal program time interval. As shown in <FIG>, the start bar <NUM> graphically depicts the start time <NUM> on the timeline <NUM> (e.g., the start bar <NUM> is depicted along the timeline <NUM> at a position corresponding to the start time <NUM>). Similarly, an end bar <NUM> can graphically represent the end of a basal program time interval. As shown in <FIG>, the end bar <NUM> graphically depicts the end time <NUM> on the timeline (e.g., the end bar <NUM> is depicted along the timeline <NUM> at a position corresponding to the end time <NUM>). The timeline <NUM> can initially graphically depict a <NUM> hour interval of time.

Area <NUM> of the user interface <NUM> can enable a user to select actions related to building a basal program. Specifically, the area <NUM> provides a user with a mechanism for indicating a particular basal program should be canceled or should proceed to a next step.

The user interface <NUM> depicted in <FIG> (as well as all user interfaces depicted herein) can be provided on a touchscreen such that a user can touch and enter or manipulate any presented data. For example, the graphical area <NUM> can graphically depict any data shown or manipulated by the user in the textual area <NUM>, such that altering the data shown in the textual area <NUM> is reflected graphically in the area <NUM>. For example, when the user adjusts the value of the start time <NUM>, the depicted position of the start bar <NUM> along the timeline <NUM> can be adjusted dynamically as the adjustment is made. Similarly, when the user adjusts the value of the end time <NUM>, the depicted position of the end bar <NUM> along the timeline <NUM> can be adjusted dynamically as the adjustment is made. Accordingly, the start bar <NUM> and end bar <NUM> can slide along the timeline <NUM> as the user adjusts the values of the start time <NUM> and end time <NUM>, respectively, within the area <NUM>.

Correspondingly, the textual area <NUM> can textually depict any data shown or manipulated by the user in the graphical area <NUM>, such that altering the data shown in the graphical area <NUM> is reflected textually in the area <NUM>. For example, a user may engage and manipulate the start bar <NUM> and can slide it along the timeline <NUM>. In response, the start time <NUM> can be dynamically updated to reflect the time value corresponding to the depicted position of the start bar <NUM> along the timeline <NUM>. In various embodiments, a user can only enter or manipulate data values in the textual area <NUM> and the graphical area <NUM> is only used to graphically represent data shown and adjusted by a user in the textual area <NUM>.

In various embodiments, the graphical area <NUM> can present the timeline <NUM> in a manner such that it can be broken into different time segments. The user can then specify corresponding basal rates for each time segment defined by the user as shown in the exemplary user interfaces depicted in <FIG> and described in more detail below.

<FIG> illustrates an exemplary user interface <NUM> for defining a first time segment <NUM>. To enter the end of the first time segment <NUM>, a user can first tap on the end time <NUM> label or icon or corresponding data value and can then subsequently enter an end time value. The end time value can be selected using, for example, a scroll wheel that appears when the user taps on the user interface <NUM> (not shown in <FIG>).

Once the user selects an end time value, the end bar <NUM> can move to the corresponding position on the timeline <NUM> - to match the value shown by the end time indicator <NUM>. As a result, the area between the start bar <NUM> and the end bar <NUM> can visually depict the first time segment <NUM>. As the user scrolls through possible values of the end time, the end bar <NUM> can dynamically move to illustrate the changing duration of the first time segment <NUM> as the user manipulates the duration through data entry. In various embodiments, the user can drag the end bar <NUM> along the timeline <NUM> to a position corresponding to a desired end time value to define the first time segment <NUM>.

<FIG> illustrates an exemplary user interface <NUM> for defining a first basal rate for the first time segment <NUM>. To enter the basal rate for the first time segment <NUM>, the user can tap on the basal rate <NUM> label or icon or corresponding data value and then subsequently enter a basal rate value. The basal rate can be selected using, for example, a scroll wheel that appears when the user taps on the user interface <NUM> (not shown in <FIG>).

In various embodiments, as the user scrolls the wheel to select the basal rate, indicator <NUM> dynamically shows the changing basal rate. The indicator <NUM> can be positioned between the start bar <NUM> and the end bar <NUM>. A height or thickness of the indicator <NUM> (e.g., relative to the timeline <NUM>) can correspond to the basal rate being selected. For example, the indicator <NUM> can increase or decrease dynamically as a user scrolls through various basal rate possibilities, thereby automatically reflecting possible basal rates graphically for the selected time segment (e.g., the first time segment <NUM>) defined as the period of time between the start bar <NUM> and the end bar <NUM>. The indicator <NUM> can be a horizontally oriented bar with a thickness proportional to a selected basal rate such that higher basal rates are represented by a relatively thicker bar and lower basal rates are represented by a relatively thinner bar. Once a user settles on a basal rate as depicted by the indicator <NUM>, the user can tap on the next icon <NUM> to move on to creating a second time segment.

<FIG> illustrates an exemplary user interface <NUM> for initiating creation of a subsequent time segment. Once a time segment has been defined and a corresponding basal rate selected (e.g., for the first time segment <NUM>), a user can provide an input indicating that she is ready to define a subsequent time segment (e.g., by tapping the next icon <NUM> as shown in <FIG>).

To begin the process of defining another time segment, the user interface <NUM> can automatically move the start bar <NUM> to the end time of the prior time segment (e.g., the end of the first time segment <NUM>). The start time <NUM> can reflect the change or movement of the start bar <NUM>. Further, the end bar <NUM> can default to the end of the entire time segment (e.g., the end of the <NUM> hour period shown by the timeline <NUM>). The end time <NUM> can reflect the change or movement of the end bar <NUM>.

A default basal rate can also be selected and depicted by the user interface <NUM>. Specially, the basal rate for the subsequent time segment being defined can default to the value of the immediately prior segment (e.g., as shown by indicator <NUM> for the first time segment <NUM>). Alternatively, as shown in <FIG>, the basal rate for the subsequent time segment can initially be undefined and unspecified.

<FIG> illustrates a user interface <NUM> for completing creation of the subsequent time segment which can form a second time segment <NUM>. Similar to defining the end of the first time segment <NUM>, to enter the end time for a second time segment <NUM>, a user can tap on the end time <NUM> label or icon or corresponding data value and then subsequently enter an end time value. The end time value can be selected using, for example, a scroll wheel that appears when the user taps on the user interface <NUM> (not shown in <FIG>).

Once the user selects an end time value, the end bar <NUM> can move to the corresponding position on the timeline <NUM> - to match the user entered end time <NUM>. As a result, the area between the start bar <NUM> and the end bar <NUM> can visually depict the second time segment <NUM>.

<FIG> illustrates an exemplary user interface <NUM> for defining a basal rate for the second time segment <NUM>. To enter the basal rate for the second time segment <NUM>, the user can tap on the basal rate <NUM> label or icon or corresponding data value and then subsequently enter a basal rate value. The basal rate can be selected using, for example, a scroll wheel that appears when the user taps on the user interface <NUM> (not shown in <FIG>).

In various embodiments, as the user scrolls the wheel to select the basal rate, indicator <NUM> dynamically shows the changing basal rate. The indicator <NUM> can be positioned between the start bar <NUM> and the end bar <NUM>. A height or thickness of the indicator <NUM> can correspond to the basal rate being selected. For example, the indicator <NUM> can increase or decrease dynamically as a user scrolls through various basal rate possibilities, thereby automatically reflecting possible basal rates graphically for the selected time segment (e.g., the second time segment <NUM>) defined as the period of time between the start bar <NUM> and the end bar <NUM>. The indicator <NUM> can be a horizontally oriented bar with a thickness proportional to a selected basal rate such that higher basal rates are represented by a relatively thicker bar and lower basal rates are represented by a relatively thinner bar.

Once a user settles on a basal rate as depicted by the indicator <NUM>, the user can tap on the next icon <NUM> to move on to creating another time segment. Until a user indicates that she has settled on a particular time segment and corresponding basal rate, the indicator <NUM> can remain a different color or shade of color relative to the indicator <NUM> to indicate that the particular time segment and basal rate are not fully set. In various embodiments, the user interface <NUM> can indicate the not yet completed basal rate and time segment selection through different colors, shading, icons or other graphical depictions on the timeline.

The process for defining time segments and corresponding basal rates can be repeated until the user has defined time segments and corresponding basal rates for an entire <NUM> hour period (or for any desired period of time). The user interface described herein enables any number of time segments to be defined and any basal rate to be selected.

<FIG> illustrates an exemplary user interface <NUM> for reviewing and saving a basal program. As shown in <FIG>, an entire <NUM> hour period of time has been broken into different time segments having corresponding basal rates - including first and second time segments <NUM> and <NUM> and additional time segments <NUM> and <NUM>. The graphical area <NUM> of the user interface <NUM> provides a visual preview <NUM> of the entire basal program that the user has entered - for example, the defined time segments and corresponding basal rates. The visual preview <NUM> graphically depicts each time segment and corresponding basal rate values relative to all other time segments and basal rates. Further, the textual area <NUM> provides a tabular listing <NUM> of the time segments and basal rate values as depicted in the visual preview <NUM>. In this way, the user interface <NUM> provides both a visual representation <NUM> and a tabular representation <NUM> of the basal program for the user.

As further shown in <FIG>, the user interface <NUM> can include a menu area <NUM>. The menu area allows a user to either cancel or save the current (e.g., depicted) basal program.

<FIG> illustrates an exemplary user interface <NUM> for further reviewing and saving a basal program. As shown in <FIG>, the user interface <NUM> can provide an area <NUM> for a user to enter a name for the basal program. Further, the user interface <NUM> can allow a user can to tag or label the type of basal program created using the tags or labels <NUM>. The user interface <NUM> can be presented when creation of a basal program is first initiated or after the basal program has been defined and a user would like to save and tag the program.

The user interfaces described in relation to <FIG> provide numerous benefits over conventional user interfaces. The user interfaces described herein allow a user to view a basal program graphically in real-time as the user builds the program. A correct basal profile is key to diabetes management. It is therefore very important that a user's basal program is correctly established. Many individuals understand the basal program information better when it is presented graphically. Market testing has revealed that many users are overwhelmed when only presented with basal program data in a tabular format. Overall, the user interfaces described herein provide the following: (a) enable patients to better understand the variability of their basal rates throughout the day; (b) decrease the cognitive load of understanding a basal program solely through numbers via tabular display only; and (c) make it easier for patients to create and edit basal profiles. As a result, patients using the user interfaces described herein are more likely to adjust basal rates more frequently in conjunction with their health care providers, thereby contributing to better blood glucose control and improved health outcomes.

The basal program built by a user (e.g., as shown graphically in the preview <NUM>) can be used to direct operation of a drug delivery device. In various embodiments, the basal program built on the portable electronic device <NUM> can be transmitted to the drug delivery device <NUM> as a set of instructions directing the drug delivery device <NUM> to deliver the defined amounts of insulin (e.g., by specifying different basal rates) over different periods of time (e.g., by specifying different time segments for each different basal rate). The drug delivery device <NUM> can use the provided information regarding the basal program to deliver insulin to the user in accordance with the basal program defined by the user.

Many diabetes management systems/insulin delivery systems (e.g., insulin pumps) allow a patient to temporarily change a preset basal rate for a certain period of time (e.g., usually less than <NUM> hours). Conventional diabetes management systems/insulin delivery systems typically require the user to enter a percentage (%) variation from the basal profile or a rate of basal insulin (e.g., in U/hr. ) and the duration of the temporary basal rate. Once the temporary basal rate has been confirmed, the conventional diabetes management systems/insulin delivery systems display the new basal rate in U/hr. and often the time remaining on the temporary setting. Accordingly, these conventional systems are generally limited to displaying the modified information in a textual or tabular format. The user interfaces described herein provide an improved user experience by graphically displaying the temporary basal rate over the full duration to the user.

<FIG> illustrates various embodiments of a user interface for modifying a basal program. The various embodiments depicted in <FIG> can be provided by the portable electronic device <NUM> as part of a diabetes management system/insulin delivery system (e.g., as part of the drug delivery system <NUM>).

<FIG> illustrates an exemplary user interface <NUM> for initially starting a temporary basal program and/or modifying temporarily a preset basal program. That is, <FIG> illustrates the user interface <NUM> provided to a user when the user first selects the option of temporarily modifying basal rates set from a basal program.

As shown in <FIG>, within the graphical area <NUM>, a graphical representation <NUM> of a basal program is shown (e.g., similar to the preview <NUM> shown in <FIG>). The identifier <NUM> indicates that a temporary adjustment to a basal program is being established. A start bar <NUM> indicates a starting time of the temporary basal rate adjustment. By default, the start bar <NUM> can start at a current time (e.g., labeled as "Now"). The textual area <NUM> of the user interface <NUM> includes a duration identifier <NUM> and a basal rate identifier <NUM>. The duration and basal rate identifiers <NUM> and <NUM> can further include default data (e.g., prior to any adjustment) or can indicate that values are not yet specified or defined (as shown in <FIG>). The user interface <NUM> can further include an input <NUM> for selecting adjustments from already stored presets (e.g., preset adjustments stored in the memory <NUM>).

<FIG> illustrates an exemplary user interface <NUM> when a decreased temporary basal rate relative to an initial basal rate is entered or specified by the user. To adjust the basal rate, a user can tap on the basal rate identifier and/or value <NUM>. In various embodiments, tapping on the basal rate identifier or value <NUM> can cause the user interface <NUM> to present a scroll wheel for the user to manipulate (not shown in <FIG>). The scroll wheel can allow a user to increase or decrease the basal rate for the basal program shown in the graphical area <NUM>. When the user selects a basal rate that is lower than the preset basal rate, the graphical section <NUM> can show the basal rate adjustment dynamically. Specifically, the basal rate adjustment can be shown by indicating the new basal rate relative to the prior basal rate.

As an example, for a time segment <NUM>, the initial or prior basal rate is shown by indicator <NUM> and the new or adjusted basal rate is shown by indicator <NUM>. The indicators <NUM> and <NUM> can be shown by any graphical means such as text, lines, colors or shading. As shown in <FIG>, the prior basal rate is indicated by a dotted or dashed line <NUM> such that the distance between the line <NUM> and the indicator <NUM> represents the change in basal rate (e.g., corresponding to the value specified by the basal rate input <NUM>). The area between the indicator <NUM> and <NUM> can be colored or shaded or depicted in any manner to indicate the change. The time segment <NUM> can also depict the new value <NUM> of the adjusted basal rate. The representations of the basal rate changes shown with respect to the time segment <NUM> can be similarly shown in the other time segments of the displayed basal program. If a user is satisfied with the changes to the basal rate, an input <NUM> can be selected by the user to confirm or lock in the changes to the basal rate.

<FIG> illustrates an exemplary user interface <NUM> for entering a duration of the temporary basal adjustment period. To set a duration, a user can tap on the duration value <NUM> and can select a duration value. In various embodiments, tapping on the duration value <NUM> can cause the user interface <NUM> to present a scroll wheel for the user to manipulate (not shown in <FIG>). As the user adjusts the duration value <NUM>, an end bar <NUM> dynamically moves along the timeline <NUM> shown in the graphical area <NUM>. As a result, the start bar <NUM> and the end bar <NUM> dynamically display the duration of the temporary basal program. Once a duration value is selected, the end bar <NUM> can stop moving. The duration value <NUM> will reflect the duration value graphically depicted in the area <NUM>.

Accordingly, <FIG> illustrates the user interface <NUM> for specifying the change (e.g., as a percent change) in the basal rate and <FIG> illustrates the user interface <NUM> for specifying the duration (e.g., as an amount of time) of the temporary basal rate and program adjustment. Once a user specifies the change and duration, the user can confirm the changes. The adjustments to any time segment can then be used to adjust delivery of insulin to the user as described above in relation to the drug delivery system <NUM>.

<FIG> illustrates an exemplary user interface <NUM> showing adjustment of a basal program with an increased temporary basal rate. The basal rate can be adjusted to be increased in a manner similar to that discussed above in relation to <FIG> and <FIG>. As an example, for a time segment <NUM>, the initial or prior basal rate is shown by indicator <NUM> and the new or adjusted basal rate is shown by indicator <NUM>. The indicators <NUM> and <NUM> can be shown by any graphical means such as text, lines, colors or shading. As shown in <FIG>, the new or adjust basal rate <NUM> is shown as above or on top of the prior or initial basal rate <NUM>. The difference between the prior rate and the new rate can be indicated by the area between the indicator <NUM> and <NUM> and can be colored or shaded or depicted in any manner to indicate the change. The time segment <NUM> can also depict the new value <NUM> of the adjusted basal rate. The representations of the basal rate changes shown with respect to the time segment <NUM> can be similarly shown in the other time segments of the displayed basal program. If a user is satisfied with the changes to the basal rate, an input <NUM> can be selected by the user to confirm or lock in the changes to the basal rate.

<FIG> illustrates an exemplary user interface <NUM> for confirming changes to a basal program and/or confirming temporary changes to a basal rate over a specified period of time. As shown in <FIG>, once the user completes entry of the temporary basal rate adjustment, the graphical section <NUM> provides a visual preview graph <NUM> of the entire temporary basal period. The graphical section <NUM> also shows a comparison of the initial basal rate <NUM> and the newly selected temporary basal rate <NUM> so that a user can compare the changes visually. Further, the textual section <NUM> provides a tabular listing <NUM> indicating the duration of the temporary adjustment and the amount of change (e.g., as a percentage of the initial rate). If the adjustments meet with the user's approval, then the user can use input <NUM> to activate the basal rate adjustments.

As with the user interfaces shown in <FIG> for providing a user with a real-time basal programming graph, the user interfaces shown in <FIG> provide a user with graphical views of a temporary basal programming graph that can aid a user's understanding of the basal rate adjustments. In turn, the user's experience is improved such that more frequent and better adjustments to basal rates are made by the user for improved diabetes management. Further, after activation, the temporary basal adjustments can be transmitted to a drug delivery device for implementation.

The user interface provided by the portable electronic device <NUM> can also provide a dynamic keyboard as shown in <FIG>. The dynamic keyboard can display default values with a first type of text <NUM> (e.g., a faded text). User entered values that fall outside of a permissible range can be indicated with a second type of text <NUM> (e.g., a red text). User entered values that fall within a permissible range can be indicated with a third type of text <NUM> (e.g., a black text or a green text). Dynamic messages <NUM> can also be provided to the user when the user enters data values. The dynamic messages <NUM> can indicate if certain values are default values, permitted values, or values that fall outside of a permissible range of values. Such indications can be provided via text and by different text colors - for example, a dynamic message <NUM> can be provided in red with a message indicating a value is outside a permitted range and can be provided in green with a message indicating a value is within a permitted range. The dynamic keyboard <NUM> provides an enhanced user experience and enables a user to quickly determine if an entered value is acceptable or not and can also provide an explanation as to why a value is permitted or not.

<FIG> illustrates an embodiment of a logic flow <NUM> for providing the user interfaces described herein. The logic flow <NUM> may be representative of some or all of the operations executed by one or more embodiments described herein. As an example, the logic flow <NUM> can be implemented by the portable electronic device <NUM> to provide the user interfaces depicted in <FIG>.

At <NUM>, one or more input signals can be received. The input signals can originate locally (e.g., by a local user input provided through a touchscreen) or can originate remotely (e.g., by a remote device in communication with a local device implementing the logic flow <NUM>). At <NUM>, an input signal receiver, operable on a processor, may be configured to receive one or more input signals from one or more input devices, such as a touchscreen. At <NUM>, a communications receiver, operable on a processor, may be configured to receive one or more input signals from one or more remote devices.

At <NUM>, input information from the input signals can be determined. A control module, operable on the processor, may be configured to determine the input information from the one or more input signals. The input information may include instructions and/or data values.

At <NUM>, a user interface is displayed. The user interface may be displayed on a display device. The display device may be a touchscreen. The user interface can include a graphical portion for displaying information and/or for receiving input information. The control module may cause the display device to display the user interface. The control module may specify graphics or other visual elements stored in a memory for display on the display device.

At <NUM>, the user interface can be adjusted based on the received input information. The control module can direct the display device to adjust the provided display to provide a dynamically updated user interface responsive to received input information. As an example, the graphical portion can dynamically display a time segment of a basal program as described above in relation to <FIG>. The graphical portion can dynamically display a basal rate for a time segment of a basal program as described above in relation to <FIG>. The graphical portion can also display a complete graph of a basal program specified by a user as described above in relation to <FIG>. The graphical portion can dynamically display a temporary adjustment made by a user to a predetermined basal program (e.g., a change to one or more basal rates over one or more time segments) as described in relation to <FIG>.

<FIG> illustrates an embodiment of a storage medium <NUM>. Storage medium <NUM> may comprise any non-transitory computer-readable storage media or machine-readable storage media, such as an optical, magnetic or semiconductor storage media. In various embodiments, storage medium <NUM> may comprise an article of manufacture. In some embodiments, storage medium <NUM> may store computer-executable instructions, such as computer-executable instructions to implement logic flow <NUM> of <FIG>.

Examples of a computer-readable storage medium or machine-readable storage medium may include any tangible media capable of storing electronic data, including volatile memory or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and so forth. Examples of computer-executable instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like. The storage medium <NUM> may include instructions to be executed by the processor <NUM> for implementing the user interfaces described herein.

Claim 1:
A basal insulin management system, comprising:
a processor operable with a memory and a display device;
one or more input devices;
an input signal receiver operable on the processor to receive one or more input signals from the one or more input devices; and
a display controller operable on the processor to receive input information from the input signal receiver and to retrieve user interface information from the memory based upon the input information for the display of a user interface for modifying temporarily a preset basal program on the display device, the user interface including:
a first portion for displaying user selected numerical values for an end time of a temporary basal rate adjustment and a temporary basal rate adjustment indicating the amount of change in percentage for a portion of a basal insulin program; and
a second portion for graphically representing a start time for the temporary basal rate adjustment, the end time, and the basal rate on a timeline representing a duration of the basal insulin program, the start time graphically represented by a start bar along the timeline and corresponding to a current time, the end time graphically represented by an end bar along the timeline, and the temporary basal rate adjustment graphically represented as a difference between an initial basal rate of the basal insulin program and the selected temporary basal rate adjustment for the selected portion of the basal insulin program.