FIELD
The present disclosure relates to a handheld diabetes manager that has a module for the personal data of the diabetes patient.
BACKGROUND
Diabetes mellitus, often referred to as diabetes, is a chronic condition in which a person has elevated blood glucose levels that result from defects in the body's ability to produce and/or use insulin. According to the American Diabetes Association, diabetes mellitus, or simply, diabetes, is a group of diseases characterized by high blood glucose levels that result from defects in the body's ability to produce and/or use insulin. Type 1 diabetes is usually diagnosed in children and young adults, and was previously known as juvenile diabetes. In type 1 diabetes, the body does not produce insulin. Type 2 diabetes is the most common form of diabetes. In type 2 diabetes, either the body does not produce enough insulin or the cells ignore the insulin. During pregnancy—usually around the 24th week—many women develop gestational diabetes. A diagnosis of gestational diabetes doesn't mean that you had diabetes before you conceived, or that you will have diabetes after giving birth.
Diabetes is managed primarily by controlling the level of glucose in the bloodstream. This level is dynamic and complex, and is affected by multiple factors including the amount and type of food consumed, and the amount of insulin (which mediates transport of glucose across cell membranes) in the blood. Blood glucose levels are also sensitive to exercise, sleep, stress, smoking, travel, illness, menses, and other psychological and lifestyle factors unique to individual patients. The dynamic nature of blood glucose and insulin, and all other factors affecting blood glucose, often require a person with diabetes to forecast blood glucose levels. Therefore, therapy in the form of insulin or oral medications, or both, can be timed to maintain blood glucose levels in an appropriate range.
Management of diabetes is time-consuming for patients because of the need to consistently obtain reliable diagnostic information, follow prescribed therapy, and manage lifestyle on a daily basis. Diagnostic information, such as blood glucose, is typically obtained from a capillary blood sample with a lancing device and is then measured with a handheld blood glucose meter. Interstitial glucose levels may be obtained from a continuous glucose sensor worn on the body. Prescribed therapies may include insulin, oral medications, or both. Insulin can be delivered with a syringe, an ambulatory infusion pump, or a combination of both. With insulin therapy, determining the amount of insulin to be injected can require forecasting meal composition of fat, carbohydrates and proteins along with effects of exercise or other physiologic states. The management of lifestyle factors such as body weight, diet, and exercise can significantly influence the type and effectiveness of a therapy.
Management of diabetes involves large amounts of diagnostic data and prescriptive data acquired in a variety of ways: from medical devices, from personal healthcare devices, from patient-recorded logs, from laboratory tests, and from healthcare professional recommendations. Medical devices include patient-owned bG meters, continuous glucose monitors, ambulatory insulin infusion pumps, diabetes analysis software, and diabetes device configuration software. Each of these systems generates and/or manages large amounts of diagnostic and prescriptive data. Personal healthcare devices include weight scales, blood pressure cuffs, exercise machines, thermometers, and weight management software. Patient recorded logs include information relating to bG levels, meals, exercise and lifestyle. Lab test results include HbA1C, cholesterol, triglycerides, and glucose tolerance. Healthcare professional recommendations include prescriptions, diets, test plans, therapy changes and other information relating to the patient's treatment.
The present teachings are directed to a handheld diabetes manager that includes a user interface communicating with an external insulin pump and including a module for the personal data of the diabetes patient.
SUMMARY
This section provides a general summary of the disclosure, and is not a comprehensive disclosure of its full scope or all of its features.
The present teachings provide a handheld diabetes manager that communicates with an external insulin pump and includes a port for blood glucose measurement, a blood glucose measurement module, a communications module that selectively communicates wirelessly with the insulin pump, and a user interface module. The user interface module communicates with the blood glucose measurement module and the communications module and operates to provide a graphical user interface on a display of the diabetes manager. The graphical user interface includes a personal data menu screen from which a logbook option can be selected to display a logbook screen. The logbook screen displays a plurality of time data records. Each time data record may include blood glucose data, bolus insulin data, basal insulin data, carbohydrate data, meal time data, health event data and free entry notes for a corresponding time and a plurality of data icons indicating corresponding events.
A trend graph option can be selected from the personal menu screen to display a trend graph screen. The trend graph screen displays within a graph area a blood glucose line graph, a carb bar graph, a basal rate line graph and a bolus bar graph representing corresponding data during a selected time interval.
Further areas of applicability will become apparent from the description provided herein. The description and specific examples in this summary are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure.
BRIEF DESCRIPTION OF THE DRAWINGS
The drawings described herein are for illustrative purposes only of selected embodiments and not all possible implementations, and are not intended to limit the scope of the present disclosure.
FIG. 1 shows a patient with a continuous glucose monitoring (CGM) patch, an ambulatory durable insulin infusion pump, an ambulatory non-durable insulin infusion pump, and a diabetes manager;
FIG. 2 shows a diabetes management system used by patients and clinicians to manage diabetes;
FIG. 3 is a functional block diagram of a diabetes manager according to the present teachings;
FIG. 4 is a block diagram illustrating a user interface with personal data (“my data”) module for a diabetes manager according to the present teachings;
FIG. 5 illustrates an exemplary main menu screen for the diabetes manager according to the present teachings;
FIG. 6 illustrates an exemplary menu screen of the “my data” module of the diabetes manager according to the present teachings;
FIG. 7A illustrates an exemplary logbook screen of the “my data” module of the diabetes manager according to the present teachings;
FIG. 7B illustrates an exemplary locked detailed bG record screen for the diabetes manager according to the present teachings;
FIG. 7C illustrates an exemplary locked detailed meal time screen for the diabetes manager according to the present teachings;
FIG. 8 illustrates an activity diagram for the logbook of the “my data” module of the diabetes manager according to the present teachings;
FIG. 9 illustrates an exemplary “trend graph” screen of the “my data” module of the diabetes manager according to the present teachings;
FIG. 10 illustrates an exemplary “configure graph” screen for the trend graph screen of FIG. 9;
FIG. 11 illustrates an exemplary “trend icon help” screen for the trend graph screen of FIG. 9;
FIG. 12 illustrates an exemplary “data options” screen for the “configure graph” screen of FIG. 10;
FIG. 13 illustrates an exemplary “meal time” screen for the “configure graph” screen of FIG. 10; and
FIG. 14 illustrates an activity diagram for the trend graph of the “my data” module of the diabetes manager according to the present teachings;
Corresponding reference numerals indicate corresponding parts throughout the several views of the drawings.
DETAILED DESCRIPTION
The following description is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. For purposes of clarity, the same reference numbers will be used in the drawings to identify similar elements. As used herein, the phrase at least one of A, B, and C should be construed to mean a logical (A or B or C), using a non-exclusive logical “or”. It should be understood that steps within a method may be executed in different order without altering the principles of the present disclosure.
Referring now to FIG. 1, a person with diabetes 100 using various medical devices is illustrated. Persons with diabetes include persons with metabolic syndrome, persons with pre-diabetes, type 1 diabetes, type 2 diabetes, and gestational diabetes and are collectively referred to as a patient. Healthcare providers for diabetes are diverse and include nurses, nurse practitioners, physicians, diabetes nurse educators, nutritionists and endocrinologists and are collectively referred to as a clinician.
During a healthcare consultation, the patient 100 typically shares with the clinician a variety of patient data including blood glucose measurements, continuous glucose monitor data, amounts of insulin infused, amounts of food and beverages consumed, exercise schedules, and other lifestyle information. The clinician may obtain additional patient data that includes measurements of HbA1C, cholesterol levels, triglycerides, blood pressure, and weight of the patient 100. The patient data can be recorded manually or electronically on a handheld diabetes management device (“diabetes manager”) 104 having a display 103, a diabetes analysis software executed on a personal computer (PC not shown), and/or a web-based diabetes analysis site (not shown). The clinician can analyze the patient data manually or electronically using the diabetes manager 104, diabetes analysis software and/or the web-based diabetes analysis site. After analyzing the patient data and reviewing adherence of the patient 100 to previously prescribed therapy, the clinician can decide whether to modify the therapy for the patient 100.
Referring now to FIG. 1, the patient 100 can use a continuous glucose monitoring (CGM) device or CGM patch 200, an ambulatory non-durable insulin infusion pump 202 or an ambulatory durable insulin infusion pump 204 (hereinafter insulin pump 202 or 204), and the handheld diabetes manager 104 (hereinafter the diabetes manager or meter 104). In some embodiments, the CGM patch 200 can include includes a body mount, a reusable component and a subcutaneous sensor to sense and monitor the amount of glucose in interstitial fluid of the patient 100 and communicate corresponding data to the diabetes manager 104.
The diabetes manager 104 can perform various tasks including measuring and recording blood glucose levels, determining an amount of insulin to be administered to the patient 100 via the insulin pump 202 or 204, receiving patient data via a user interface, archiving the patient data, etc. The diabetes manager 104 periodically receives glucose levels of the patient 100 from the CGM patch 200, or data from which glucose levels of the patient 100 may be computed. The diabetes manager 104 transmits instructions to the insulin pump 202 or 204, which delivers insulin to the patient 100. Insulin can be delivered in a scheduled manner in the form of a basal dose, which maintains a predetermined insulin dose to the patient 100. Additionally, insulin can be delivered in the form of a bolus dose, which raises the amount of insulin delivered to the patient 100 by a determined amount.
Generally, and referring now to FIG. 2, a diabetes management system 300 used by the patient 100 and the clinician can include one or more of the following devices: the diabetes manager 104, the continuous glucose monitor (CGM patch) 200, the insulin pump 202 or 204, a mobile device 302, the PC 106 with diabetes analysis and/or configuration software, and other healthcare devices 304. The diabetes manager 104 can be configured as a system hub that communicates with the devices of the diabetes management system 300. Alternatively, the mobile device 302 can serve as the system hub. Communication between the devices in the diabetes management system 300 can be performed using wireless interfaces (e.g., Bluetooth) and/or wired interfaces (e.g., USB). Communication protocols used by these devices can include protocols compliant with the IEEE 11073 standard, as extended using guidelines provided by Continua® Health Alliance Design Guidelines. Further, healthcare records systems such as Microsoft® HealthVault™ and Google™ Health can be used by the patient 100 and clinician to exchange information.
The diabetes manager 104 can receive glucose readings from one or more sources (e.g., from the CGM patch 200). The CGM patch 200 regularly monitors the interstitial glucose level of the patient 100. The CGM patch 200 periodically communicates glucose levels to the diabetes manager 104. The diabetes manager 104 and the CGM patch 200 communicate wirelessly using generally a proprietary wireless protocol, such as, for example, the standard Bluetooth Low Energy protocol. Any other suitable wireless protocol can be used instead.
Additionally, the diabetes manager 104 includes a blood glucose meter (BGM) and a port that communicates with the BGM (not shown). The port can receive a blood glucose measurement strip 306. The patient 100 deposits a sample of blood on the blood glucose measurement strip 306. The BGM analyzes the sample and measures the blood glucose level in the sample. The blood glucose level measured from the sample is used to determine the amount of insulin to be administered to the patient 100 using, for example, the insulin pump 202, 204.
The diabetes manager 104 also communicates with the insulin pump 202 or 204. The insulin pump 202 or 204 can be configured to receive instructions from the diabetes manager 104 to deliver a predetermined amount of insulin to the patient 100 in the form of basal dose or bolus dose. In some embodiments, the insulin pump 202 or 204 can receive other information including meal and/or exercise schedules of the patient 100. The insulin pump 202 or 204 can determine the amount of insulin to administer based on the additional information as a basal dose or bolus dose. In other embodiments the bolus calculation is on the diabetes manager 104.
The insulin pump 202 or 204 can also communicate data to the diabetes manager 104 via wireless communication module including, for example, a pump transceiver or a communications radio. The data can include amounts of insulin delivered to the patient 100, corresponding times of delivery, and pump status. The diabetes manager 104 and the insulin pump 202 or 204 can communicate using a wireless communication protocol such as Bluetooth. Other wireless communication protocols can also be used.
In addition, the diabetes manager 104 can communicate with the other healthcare devices 304. For example, the other healthcare devices 304 can include a blood pressure meter, a weight scale, a pedometer, a fingertip pulse oximeter, a thermometer, etc. The other healthcare devices 304 obtain and communicate personal health information of the patient 100 to the diabetes manager 104 through wireless, USB, or other interfaces. The other healthcare devices 304 may use communication protocols compliant with ISO/IEEE 11073 extended using guidelines from Continua® Health Alliance. The diabetes manager 104 can communicate with the other healthcare devices 304 using interfaces including Bluetooth, USB, etc. Further, the devices of the diabetes management system 300 can communicate with each other via the diabetes manager 104.
The diabetes manager 104 can communicate with the PC 106 using Bluetooth, USB, or other wireless interfaces. A diabetes management software running on the PC 106 includes configuration software (configurator) that stores configuration information of the devices of the diabetes management system 300. The configurator has a database to store configuration information of the diabetes manager 104 and the other devices. The configurator can communicate with users through standard web or computer screens in non-web applications. The configurator transmits user-approved configurations to the devices of the diabetes management system 300. The analyzer retrieves data from the diabetes manager 104, stores the data in a database, and outputs analysis results through standard web pages or computer screens in non-web based applications.
The diabetes manager 104 can communicate with the mobile device 302 using Bluetooth or another suitable wireless communication protocol. The mobile device 302 may include a cellular phone, a pager, or a personal digital assistant (PDA). The diabetes manager 104 can send messages to an external network through the mobile device 302. The mobile device 302 can transmit messages to the external network upon receiving requests from the diabetes manager 104. In some embodiments, a cellphone chip can be built into the diabetes manager 104 for direct communication to the external network.
Referring now to FIG. 3, the diabetes manager 104 includes a blood glucose measuring (BGM) module 400, a communication module 402, a user interface module 404, various user interface elements 406, a processing module 408, a memory 410, and a power module 412. The user interface module 404 and the processing module 408 can be implemented by an application processing module 409. The BGM module 400 includes a blood glucose measuring engine that analyzes samples provided by the patient 100 on the blood glucose measurement strip 306 and measures the amount of blood glucose in the samples. The communication module 402 can include a transceiver and/or multiple radios that communicate with different devices of the diabetes management system 300. The user interface module 404 interfaces the diabetes manager 104 to various user interface elements 406 that the patient 100 can use to interact with the diabetes manager 104. For example, the user interface elements 406 can include a touchscreen or other display, touchscreen keys or other physical keys, physical switches, a speaker, a microphone, a secure digital (SD) card port, a USB port, etc. (not shown).
The processing module 408 processes data received from the BGM module 400, the communication module 402, and the user interface module 404. The processing module 408 uses memory 410 for processing and storing data. The memory 410 can include volatile and nonvolatile memory. The processing module 408 outputs data to and receives data from the user interface elements 406 via the user interface module 404. The processing module 408 outputs data to and receives data from the devices of the diabetes management system 300 via the communication module 402. The power module 412 supplies power to the components of the diabetes manager 104. The power module 412 can include a rechargeable battery. The battery can be charged via the USB port of the diabetes manager 104 using an adapter that plugs into a wall outlet or using a cable that plugs into a PC.
Referring to FIG. 4, a logical navigation architecture of the user interface module for handheld diabetes manager 104 is illustrated. The following modules can be integrated in the navigation architecture of the handheld diabetes manager 104: a startup module 150, a home module 152, a meter module 154, a bolus advice module 156, a “my data” module 158 for personal data of the patient or user of the diabetes manager, a system settings module 160, a device connectivity module 162, a travel module 164, a pump module 166 and a data module 140. The data module 140 includes databases, settings and configurations, and acts as a central hub that communicates with the other modules to store and provide information related regarding data, settings, configuration related to the other modules. In some embodiments, some of the modules can be removed or inactivated or additional modules can be added. For example, the pump module 166 may be removed or inactivated in models of the handheld diabetes manager 104 for non-pump users. In other modules, a continuous glucose monitoring module (CGM) 168 can be added, as illustrated in dashed lines.
As briefly outlined in reference to FIG. 4, the handheld diabetes manager 104 of the present teachings integrates in a single handheld device various functions, controls, calculations, tests and reports that, in prior art devices, are typically split among different specialized devices, such as single-purpose bG meters, single-purpose remote devices for insulin pumps and other similar single or limited-purpose diabetes managers. Integrating the multiple tasks and functions of the plurality of modules of the handheld diabetes manager 104 of the present teachings requires a user interface that does not simply superpose various functions in an additive manner, but anticipates behaviors and use case scenarios that are unique and emerge from the interaction of the multiplicity of modules when all these modules are integrated in the same handheld device. Such interactions arise not just from the hardware aspects of the device, but from the various possibilities or use scenarios that a user may subject the device based in the user-perceived and/or actual capabilities of the device. For example, although portability is common to many prior art diabetes devices, portability and use in restricted or semi-restricted environments, such as during air travel, requires anticipation of alternative use case or use scenarios to avoid conflicts, without totally disabling the device. In the following, the term pump is used interchangeably for an insulin pump and insulin patch with a CGM device, CGM patch, micro-pump or other similar device or combination, unless differentiation is required.
In the context of the user interface for the handheld diabetes manager 104, a use case is an observable result based upon an action by a user. A use case describes the behavior and navigation along a primary or alternate path including any standard business rules for diabetes management and is graphically represented in an activity or behavior diagram, as shown, for example, in FIGS. 8 and 14.
Referring to FIG. 4, the present teachings are directed generally to the “my data” module 158 of the user interface. Generally, the “my data” module 158 interacts via the data module 140 with the meter module 154, the bolus advice module 156 and pump module 166 (and/or the CGM module 168). The “my data” module 158 can be accessed, for example, via a “my data” button 678 of a main menu screen 660, shown in FIG. 5 and described below. The bolus advice module 156 receives blood glucose measurements from the blood glucose measurement module 400 (FIG. 3) and determines various insulin recommendations in the form of a bolus for a patient based in part on the blood glucose measurements, meals, lifestyle factors, health events, etc.
Referring to FIG. 5, the main menu screen 660 can display time and date information, and various status icons, such as, for example a temperature icon 662, sound icon 664 (including vibrate mode), battery status icon 668 and flight mode icon 670. Some status icons are only displayed when they are enabled or active. For example, if flight mode is enabled, the flight mode icon 670 is displayed. Similarly, the sound and sound/vibrate icons 664 are displayed when the corresponding functions are enabled. The temperature icon 662 is displayed when the diabetes manager 104 detects that the temperature is outside a bG test warning temperature or a bG test lockout range, as defined by a code key for the test strip 306. The battery icon 668 displays the current charge condition of the battery. The main menu screen 660 includes various buttons (mechanical or touch buttons) that can be activated by touch or stylus or other selector device to display a corresponding detailed screen. The button labeled meter 672 represents a graphical user interface for the meter module 154 and interfaces with the BGM module 400. The button labeled pump 676 illustrates a graphical user interface for an external device, in this case an insulin pump, as shown in the pump module 166 (FIG. 4) and in FIG. 2 at 202 and 204. The pump button 676 is used to represent graphically any such external medical device, with the insulin infusion pumps 202, 204 and the CGM patch 200 being exemplary external medical devices.
With continued reference to FIG. 5, the main menu screen 660 can include a bolus button 674 corresponding to the bolus advice module 156, a “my data” button 678 corresponding to the “my data” module 158, a communications button 680 corresponding to the “device connectivity” (or communications) module 162 and a settings button 682 corresponding to the system settings module 160. The main menu screen 660 can also include a status button 684 and a quick notes button 686. A flight mode button 688 and a help button 690 (indicated as a question mark) can be presented and accessed by swiping the screen along its length to shift the buttons on the main menu screen 660 when the number of buttons exceeds the length of the screen. Some of the preceding set of buttons may go out of view as a result.
Referring to FIGS. 5 and 6, starting from the main menu screen 660 of FIG. 5 and pressing the “my data” button 678 displays a “my data” screen 700 that includes a logbook button 702, a trend button 704, a standard week button 706, a standard day button 708, a target button 710 and a bG averages button 712. These buttons, when pressed, display corresponding information for the specific patient showing events and bG results in various graphical forms for a week or a day as well as trends and averages. The “my data” screen 700 can also include a back button 714 leading to the previous screen (main menu screen 660) and an “add data” button 716 allowing the user to enter new data. Additionally, when the diabetes manger is connected to an insulin pump 202, 204, a pump button 718 can be used to display the user's pump-related data.
Pressing the logbook button 702 from the “my data” screen 700, displays a logbook screen 730, as seen in FIG. 7A. The logbook screen 730 displays logbook information for each of multiple days in tabular form including a plurality of cells arranged in rows 732 corresponding to different times during the day and in four columns 734, 736, 738 and 740. Each cell in the first column 734 is a time (or data record) button 735 that when pressed displays a detailed screen of data records, such as a bG record screen or a quick notes detail screen associated with the time shown on the time button 735. A maximum number of numerical data records and corresponding time buttons 735 can be set. Each cell of the first column 734 includes icons associated with bG data records. For example, icon 742 (shown as heart-shaped) represents health events or conditions, such as exercise, stress, illness, etc. Icon 744 (illustrated as a clock with a fork) represents meal time information, such as before meal, after meal, bedtime, etc. Icon 746 (keyboard with finger indicating touch typing) indicates current notes in text form and icon 748 indicates quick notes that include choices of events or conditions to be selected from a check list (meal, snack, exercise, illness, premenstrual, stress, etc.). Icon 750 represents basal data associated with a pen/syringe injection (only used for multiple daily injection users). Another icon 752 is added, if the insulin pump was paused during delivery of a bolus associated with the record.
With continued reference to FIG. 7A, the second column 736 can be used to provide a numerical bG value in units mg/dL or mmol/L and a bG indicator icon 754 that indicates a corresponding bG range status. The icon 754 can be, for example a red blood drop on a color-coded shape indicating bG range status with color. The following colors can be used, for example, green color for normal range, yellow color for low bG, red for hypo bG (hypoglycemia) and blue for hyper bG (hyperglycemia). In some embodiments, text such as “hypo” or hyper” may be also displayed.
The third column 738 of the logbook screen 730 can provide bolus insulin data in insulin units U, an icon representing the type of bolus and an icon indicating whether a bolus advice recommendation was accepted or not. In the illustrative logbook screen 730 of FIG. 7A, icon 756 indicates a standard bolus, icon 758 an extended bolus and icon 760 a multi-wave bolus. Additionally or alternatively, the icons 756, 758 and 760 can be color coded. Icon 762 (shown as a light bulb) indicates that the bolus advice recommendation has been accepted. Icon 764 (shown as a pencil) indicates that the bolus advice recommendation has not been accepted. If there is no bolus advice recommendation, no icon is shown.
With continued reference to FIG. 7A, the fourth column 740 of the logbook screen 730 can provide carbohydrate (carb) data in selected carb units or equivalents, such as grams (g), BE (bread equivalent; generally 12 g), KE (Kohlenhydrateinheiten, generally 10 g) or CC (carbohydrate choice; generally 15 g). If carb advice is not provided, a carb data icon 768 (shown as an apple, color coded green) is shown. If carb advice is provided with a bolus advice recommendation (e.g., for a hypo warning), then an additional icon is superposed on the carb data icon 768 to indicate whether the carb advice is taken or not. For example, icons 762 and 764 can also be used in relation to carb advice. Accordingly, carb data icon 768 together with light bulb icon 762 indicates that the carb advice recommendation has been accepted. Carb data icon 768 together with pencil icon 764 indicates that the carb advice recommendation has not been accepted.
The logbook screen 730 can also include a back button 770 for returning to the previous screen and an “add data” button 772 for displaying an “add data” menu screen for editing and/or adding various parameters, including time, date, meal time related conditions, health events, carb values, bolus insulin values and basal insulin values.
Referring to FIG. 8, an exemplary activity diagram associated with the logbook is illustrated. With reference to FIGS. 6, 7A, 7B, 7C and 8, pressing the logbook button 702 from the “my data” menu screen 700 displays the logbook screen 730 (block 800 in FIG. 8). Pressing one of the time buttons 735 of the logbook screen (block 806), displays a “quick notes” screen (block 802), if there is a quick note entry in the data record associated with the time button 735. If there is no quick note entry associated with the data record, a detailed bG record screen 741 is displayed. The bG record screen 741 includes the bG status and the current bG value, and various buttons for displaying meal time settings 747, carbohydrates value 749, heath event settings 731, bolus data 733 and basal insulin data 737 (if not paired with the pump), as well as a back button 770 and a note button 739. If the time button 735 of the logbook screen 730 is associated with a corresponding bulb icon 762, i.e., if the bolus advice recommendation has been accepted for the particular time record, then the detailed bG screen is locked and the above buttons 747, 749, 731, 733 and 737 cannot be used to make changes. A lock icon 745 appears at the top left of the screen in association with the bG record icon 743. Pressing the meal time button 747, for example, leads to a locked meal time screen 950L, in which no selections can be made. The locked meal time screen 950L displays the lock icon 745 next to the meal time icon 745 and is similar to the mealtime screen 950FIG. 13, which is not locked and is described below. Corresponding elements are referenced with the same numerals between FIGS. 7C and 13, with the difference that the letter “L” is added to indicate locked items in the meal time screen 950L. For example, the before-meal radio button is referenced as 954L and 954, respectively in FIGS. 7C and 13. It is noted that the meal time screen 950L, 950 can be reached from different screens of the diabetes manager 104 and some of the buttons may not appear in all screen configurations without scrolling the screen up or down.
Additionally, if the pump paused during bolus delivery associated with a bG record, the pump-paused icon 752 is shown superimposed on the corresponding standard bolus icon 756, extended bolus icon 758 and/or multiwave bolus icon 760. An example is shown as icon 757 in FIG. 7B for a an extended bolus icon 758 shown with the pump-paused icon 752 as a combined icon 757.
With continued reference to FIG. 8, pressing the “add data” button 716 of the “my data” screen 700 (block 808) displays a screen for entering data (block 810). Pressing the back button 714 (block 812) displays the previous screen (block 814) and stops the activity at 816.
Referring to FIGS. 6 and 9-14, pressing the trend button 704 from the “my data” menu screen 700 displays the trend graph screen 830 illustrated in FIG. 9. The trend graph screen 830 displays a bG line graph 832, a carb bar graph 834, a basal rate line graph 836 and a bolus bar graph 838 over a period of time that can be configured by the user to be over a time interval of 6 hours, 12 hours, one day (24 hours), three days or seven days, for example. In FIG. 9, the selected graph time interval 840 is illustrated as seven days (10 Jan. 2011 to 16 Jan. 2011, as an example) and is shown at the top of the trend graph screen 830 in a report information area (or field) 876. The time interval 840 can be scrolled backward and forward using corresponding scroll arrows 842 and 844, updating accordingly the various graphs in the trend graph screen 830. A time scale 846 corresponding to the selected time interval 840 is displayed at the bottom of the graph area along a horizontal axis. In the illustrated example, the time scale 846 is configured in day increments and the numbers on the time scale 846 correspond to seven consecutive days with the exemplary dates of 10 to 16 of Jan. 2011. Similarly, if a graph time interval of hours is selected, the time scale is configured in hourly increments or multiples of hourly increments depending on the length of the selected graph time interval 840. The trend graph screen 830 can also include a “configure” button 848 that can be pressed to display a “configure graph” screen 900, shown in FIG. 10 and discussed below.
Each of the four graphs displayed in the trend graph screen 830 of FIG. 9 has its own corresponding value scale (vertical axis) and units. The bG line graph 832 is associated with a bG scale 860 (bottom of left vertical axis) and the bG units are displayed at 870 next to a bG icon 872 (shown as a blood drop) at the bottom left under the graph area. The bG units illustrated in FIG. 9 are mg/L but other units can be used for display. The bG line graph 832 is illustrated in FIG. 9 shows a piecewise linear graph connecting with straight lines the measured bG values (marked by “x”). In this graphical representation, the bG line graph 832 provides a quick visualization of the bG trend for the selected time interval. The user 100 can also select to display the results in tabular form, for example. In association with the bG values, a straight line 833 indicates the lower limit of a normal range of bG and another straight line 835 indicates the upper limit of the normal range of bG. The area between lines 833 and 835 can be color coded, for example, with a light green color to indicate normal range. A third straight line 831 can be drawn to indicate a hypo (hypoglycemia) limit and can be color-coded in red color, for example.
The carb scale 862 for the carb bar graph 834 is shown at the right bottom vertical axis. The selected carb units, chosen as g (grams) in this example, are shown at the bottom left of the graph area at 874 next to the carb data icon 768 (illustrated as an apple). The carb bar graph 834 is illustrated in FIG. 9 as a bar graph along the bottom graph area.
The basal rate scale 866 for the basal rate line graph 836 is shown at the left top vertical axis. The basal data icon 750 is indicated at the upper left of the graph area along with the insulin units symbol “U”. Similarly, the bolus scale 864 for the bolus bar graph 838 is shown at the right top vertical axis. The bolus data icon 756 is indicated at the upper right of the graph area along with insulin units symbol U. The bolus data 756 is displayed for standard bolus, 758 for extended bolus and 760 for multiwave bolus. Additionally, a mealtime icon is displayed in the report information area (field) 876 of the trend graph screen 830 between the scroll buttons 842, 844. The mealtime icon corresponds to a filter selected for the trend graph and is one of the icons shown in an icon help screen 970 displayed by pressing the icon help button 850. The mealtime options include: all bG measurements, before meal bG measurements, after meal bG measurements, bedtime bG measurements and fasting bG measurements with corresponding icons: all bG measurements icon 878 (showing circled items), before meal bG measurements icon 880 (showing an entire apple with a leaf and color-coded red), an after meal icon bG measurements 882 (apple core), a bedtime bG measurements icon 884 (bed with letter Z), a fasting bG measurements icon 886 (crossed out fork and spoon) and an “other” icon 888 (star-shaped) for other times that do not fall within the above categories. Additional icons in the trend icon help screen 970 include the basal data icon 750, the carb data icon 768, the bolus data icon 756, the health event icon 742, and a “pump stopped” icon 890 (color coded red, for example) and a “pump paused” icon 752 (square color coded blue, for example). Pressing the help icon button 850 displays the trend icon help screen 970 showing a description of all the icons discussed above. Additionally, the graphs and corresponding scales can be color-coded with the matching colors.
With continued reference to FIG. 9, a top portion of 894 of the graph area of the trend graph screen 830 displays from left to right health event icons 742, pump stopped icons 890 and pump paused icons 752 for each corresponding event as it occurred in the trend graph's time interval. The color-coding of the different icons combined with their different shapes helps visual identification when two or more icons partially overlap. Color coding of some of the icons is shown in FIG. 11 with different shading patterns.
Referring to FIGS. 9, 10, 12 and 13, pressing the configure button 848 displays a “configure graph” screen 900 that includes a time scale button 902 for setting a selected time duration for the trend graphs, a data options button 904 and a meal time button 906. Pressing the data options button 904 displays a data options screen 920 with a check list of data that can be selected by checking one or more checkboxes 921 using corresponding checkbox buttons, such as health events check button 922, basal insulin check button 924, bolus check button 926 and carbohydrates check button 928. The selections can be saved by pressing the save button 930 or the changes can be canceled by pressing the cancel button 932. In the present disclosure, “check marks” or “check buttons” refer to buttons that allow multiple selections on a given screen, as opposed to “radio marks” or “radio buttons” that refer to marks or buttons that do not allow multiple selections.
Pressing the meal time button 906 displays a meal time screen 950 from which various options for mealtime data can be selected, only one at a time, in radio marks 951 by pressing a corresponding radio button to set the selection, such as “all” radio button 952, before mealtime radio button 954, after mealtime radio button 956, bedtime radio button 958, fasting radio button 960 and an “other” radio button 962. The selections can be saved by pressing the save button 964 or the changes can be canceled by pressing the cancel button 966.
Summarizing the above discussion, an exemplary activity diagram for the trend graph is illustrated in FIG. 14. Referring to FIGS. 6, 8 and 14, pressing the trend button 704 of the “my data” screen 700 (FIG. 6), displays the trend graph screen 830 (FIG. 9), block 980 of the activity diagram of FIG. 14. Pressing the right scroll button 844 (block 982) updates the report information area 876 and graph with the data from the next (newest) time interval (block 984). Pressing the left scroll button 842 (block 986) updates the report information area 876 and graph with the data from the previous (older) time interval (block 988). As discussed above, pressing the configure button 848 (block 990) displays the configure graph screen 900 of FIG. 10 (block 992). Pressing the back button 852 (block 994) displays the previous screen (block 996).
As used herein, the term module may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC); an electronic circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor (shared, dedicated, or group) that executes code; other suitable components that provide the described functionality; or a combination of some or all of the above, such as in a system-on-chip. The term module may include memory (shared, dedicated, or group) that stores code executed by the processor.
The term code, as used above, may include software, firmware, and/or microcode, and may refer to programs, routines, functions, classes, and/or objects. The term shared, as used above, means that some or all code from multiple modules may be executed using a single (shared) processor. In addition, some or all code from multiple modules may be stored by a single (shared) memory. The term group, as used above, means that some or all code from a single module may be executed using a group of processors. In addition, some or all code from a single module may be stored using a group of memories.
The apparatuses and methods described herein may be implemented by one or more computer programs executed by one or more processors. The computer programs include processor-executable instructions that are stored on a non-transitory tangible computer-readable medium. The computer programs may also include stored data. Non-limiting examples of the non-transitory tangible computer readable medium are nonvolatile memory, magnetic storage, and optical storage.
The broad teachings of the disclosure can be implemented in a variety of forms. Therefore, while this disclosure includes particular examples, the scope of the disclosure should not be so limited since other modifications will become apparent to the skilled practitioner upon a study of the drawings, the specification, and the following claims.
Patent Application
20130172710
