System for managing insulin dosage data

A method is provided for managing insulin dosage data collected over a complete day and a partial day. The method includes providing, by an insulin pump, a plurality of insulin dosages over a complete day and a partial day and recording the insulin dosages. The method also includes recognizing a completion of the complete day, recording an end-of-day marker, and associating the end-of-day marker to the dosages delivered during the complete day. Moreover, the method includes identifying complete day dosage data and partial day dosage data. Additionally, the method includes performing a calculation of insulin dosage statistics and/or displaying and distinguishing between the complete day dosage data and the partial day dosage data. The calculation includes the complete day dosage data and excludes the partial day dosage data.

FIELD

The present disclosure relates to data management and, more particularly, relates to a system for managing insulin dosage data.

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. Diabetes can be treated by injecting predetermined dosages of insulin to the patient to control the level of glucose in the bloodstream. For instance, some diabetes patients rely on an insulin pump to deliver the predetermined dosages to the patient.

Patients can receive multiple types of insulin dosages, and the dosages can be delivered according to varying schedules. For instance, the insulin pump can deliver basal insulin dosages (i.e., insulin that is delivered continuously at an adjustable basal rate to deliver necessary insulin between meals and at night). The insulin pump can also deliver bolus dosages (i.e., insulin delivered at specific times before the patient eats and/or to correct a high blood glucose level). Moreover, the pump can be configured to deliver multiple types of bolus dosages (e.g., a “standard bolus,” an “extended bolus,” a “combination bolus/multiwave bolus,” or other type. These dosages can be adjusted according to the patient's particular physiology, eating habits, etc.

Patients with diabetes and/or medical professionals sometimes record data relating to the insulin dosages that are delivered. This data can be used for identifying the effectiveness of the patient's particular insulin delivery schedule in maintaining the patient's blood glucose within a desirable range. The data can also be used for improving the patient's insulin delivery schedule, insulin delivery parameters such as time blocks and bolus advice parameters. Because there are many dosage amounts, dosage types, delivery times, etc., gathering and managing the data can be very difficult.

SUMMARY

A computer-implemented method for managing insulin dosage data collected over the course of multiple days to a person having diabetes is disclosed. The method includes providing, by an insulin pump, a plurality of insulin dosages over a time period. The time period includes a complete day and a partial day. The method also includes recording, by the insulin pump into a memory device, the plurality of insulin dosages. Additionally, the method includes recognizing, by the insulin pump, a completion of the complete day. Furthermore, the method includes recording, by the insulin pump into the memory device, an end-of-day marker as a result of recognizing the completion of the complete day. Moreover, the method includes associating, by the insulin pump, the end-of-day marker to those of the plurality of insulin dosages delivered during the complete day. Still further, the method includes identifying, by a data managing device, those of the plurality of insulin dosages associated with the end-of-day marker as complete day dosage data and identifying, by the data managing device, those of the plurality of insulin dosages unassociated with the end-of-day marker as partial day dosage data. The method can also include performing, by the data managing device, a calculation of insulin dosage statistics, wherein the calculation includes the complete day dosage data and the calculation excludes the partial day dosage data. Additionally, the method can include displaying, by the data managing device, both the complete day dosage data and the partial day dosage data to distinguish between the complete day dosage data and the partial day dosage data.

An insulin management system is also disclosed that manages insulin dosage data collected over the course of multiple days to a person having diabetes. The insulin management system includes an insulin pump with a memory device. The insulin pump is operable to provide a plurality of insulin dosages over a time period including a complete day and a partial day. The insulin pump is also operable to record the plurality of insulin dosages into the memory device. Moreover, the insulin pump is operable to recognize a completion of the complete day and record an end-of-day marker into the memory device as a result of the completion of the complete day. The insulin pump is further operable to associate the end-of-day marker to those of the plurality of insulin dosages delivered during the complete day. Furthermore, the insulin management system includes a data managing device that is operable to receive from the insulin pump the plurality of insulin dosages and the end-of-day marker associated with those of the plurality of insulin dosages delivered during the complete day. The data managing device is also operable to identify those of the plurality of insulin dosages associated with the end-of-day marker as complete day dosage data and to identify those of the plurality of insulin dosages unassociated with the end-of-day marker as partial day dosage data. The data managing device can also include a processor that is operable to perform a calculation of insulin dosage statistics. The calculation includes the complete day dosage data and excludes the partial day dosage data. Additionally, the data managing device can include a display that is operable to display both the complete day dosage data and the partial day dosage data to distinguish between the complete day dosage data and the partial day dosage data.

Furthermore, a computer-implemented method for managing insulin dosage data collected by an insulin pump over the course of multiple days to a person having diabetes is disclosed. The method includes receiving, by a data managing device from an insulin pump, a collection of data that reflects a plurality of insulin dosages delivered by the insulin pump over the course of a complete day and a partial day. The collection of data also includes an end-of-day marker that the insulin pump has associated with those of the plurality of insulin dosages delivered throughout the complete day. Also, the method includes identifying, by the data managing device, those of the plurality of insulin dosages associated with the end-of-day marker as complete day dosage data and identifying, by the data managing device, those of the plurality of insulin dosages unassociated with the end-of-day marker as partial day dosage data. Moreover, the method can include performing, by the data managing device, a calculation of insulin dosage statistics, wherein the calculation includes the complete day dosage data and excludes the partial day dosage data. Also, the method can include displaying, by the data managing device, both the complete day dosage data and the partial day dosage data to distinguish between the complete day dosage data and the partial day dosage data.

Still further, a computer-implemented method for managing insulin dosage data administered over the course of multiple days to a person having diabetes is disclosed. The method includes providing, by an insulin pump, a plurality of insulin dosages over a time period including a complete day and a partial day. The plurality of insulin dosages includes a plurality of basal insulin dosages and a plurality of bolus insulin dosages. Also, the method includes recording, by the insulin pump into a memory device, the plurality of insulin dosages. The method additionally includes recognizing, by the insulin pump, a completion of the complete day and recording, by the insulin pump into the memory device, an end-of-day marker as a result of recognizing the completion of the complete day. Furthermore, the method includes associating, by the insulin pump, the end-of-day marker to those of the plurality of insulin dosages delivered during the complete day. Additionally, the method includes transferring the plurality of insulin dosages and the end-of-day marker associated with those of the plurality of insulin dosages delivered during the complete day from the insulin pump to a data managing device. Moreover, the method includes identifying, by the data managing device, those of the plurality of insulin dosages associated with the end-of-day marker as complete day dosage data and identifying, by the data managing device, those of the plurality of insulin dosages unassociated with the end-of-day marker as partial day dosage data. Also, the method includes performing, by the data managing device, a calculation of insulin dosage statistics. The calculation includes the complete day dosage data, and the calculation excludes the partial day dosage data. Furthermore, the method includes displaying, by the data managing device, both the complete day dosage data and the partial day dosage data to distinguish between the complete day dosage data and the partial day dosage data.

DETAILED DESCRIPTION

Referring initially toFIG. 1, an insulin management system10is illustrated schematically. The system10can generally include an insulin pump12, an infusion set14, and a data managing device18.

The insulin pump12can incorporate various features of a known insulin pump12. Thus, the insulin pump12can include at least one refillable reservoir20, which contains insulin, and that selectively delivers insulin (e.g., via the selective mechanical action of a cartridge within the reservoir20, etc.). The pump12can also include a processor22(i.e., controller). The processor can include programmed logic and other elements for controlling the amount of insulin delivered from the reservoir20, the time that the insulin is delivered, the rate of delivery, etc. The pump12can additionally include a memory device24, which can collect and store insulin dosage data as well as other data as will be discussed below. The memory device24can also include one or more predefined dosage schedules (i.e., dosage “profiles”) that are tailored to the particular patient, and the processor22can access these profiles for controlling the amount of insulin delivered, the time of delivery, the rate of delivery, etc. Also, the pump12can include a clock26, which keeps track of the current date and time. By monitoring the clock26, the processor22can detect completion of a day (i.e., can detect an end-of-day event) for purposes that will be discussed below. For instance, if the current time reads 11:59 PM and 59 seconds on the clock26, the processor22can determine that the end-of-day event has occurred. In additional embodiments, the clock26can automatically set a twenty-four hour timer at the beginning of every day (e.g., at 12:00 AM), and when the timer runs out or resets, the processor22can determine that the end-of-day event has occurred. The end-of-day event can be detected in other ways without departing from the scope of the present disclosure as well. Moreover, the pump12can include a power source, such as a battery28, for providing power to the components of the pump12. The battery28can include a main battery that supplies power for normal operations of the pump12, and the battery28can include a backup battery that supplies power for only essential operations of the pump12when the main battery fails. It will be appreciated that the pump12can include additional or alternative power sources (e.g., one or more capacitors, etc.) without departing from the scope of the present disclosure.

Thus, the processor22can output control commands for causing predetermined amounts of insulin to be delivered at predetermined times and/or at predetermined flow rates. Also, as will be discussed in greater detail below, the insulin pump12can collect data relating to the amount of insulin delivered, the delivery time, the delivery rate, etc.

The pump12can further include a communications device29. The communication device29can establish communications between the pump12and the data managing device18as will be discussed in detail below. Thus, data collected by the insulin pump12can be transmitted to the data managing device18. The communications device29can include a wireless transmitter (e.g., BLUETOOTH™ transmitter, etc.), and/or the communications device29can include a connector for connecting a wire between the pump12and the data managing device18. Also, the communications device29can transmit data to the data managing device18via the internet. It will be appreciated that the pump12can include additional or alternative communication devices and communication methods without departing from the scope of the present disclosure.

In additional embodiments, the insulin pump12can include an output device. For instance, in the embodiments illustrated, the insulin pump12includes a display32, such as a computer monitor. Other types of output devices are within the scope of the present disclosure, however, such as a speaker, a printer, etc. The output device can output information of various types to the patient as will be discussed in greater detail below. The insulin pump12can further include an input device, such as buttons, dials, a touchscreen, etc. With the input device, the patient can input commands for controlling the pump12.

Also, the infusion set14can be of a known type. Thus, the infusion set14can include a cannula that is inserted subcutaneously into the patient (i.e., the user, the person with diabetes, etc.). The infusion set14can be fluidly connected to the reservoir20of the pump12. As such, insulin can be delivered from the reservoir20and into the patient's bloodstream via the infusion set14.

Moreover, the data managing device18can be embodied on a computer (e.g., a desktop computer or portable computer such as a laptop, tablet, PDA, etc.). The data managing device18can include a processor30that implements various software, such as a data manager31, for performing calculations and otherwise processing the data collected by the pump12as will be discussed in greater detail below. The data managing device18can further include a display32that can visually output the data that has been processed by the processor30. Moreover, the data managing device18can include an input device34, such as a keyboard, a touchscreen, etc., with which the user can input commands for controlling the data managing device18. Also, the data managing device18can include a communication device36that can selectively communicate with the communications device29for receiving data collected by the pump12. The communications device36of the data managing device18can communicate with the communications device29of the pump12wirelessly, via a hardwire connection, over the internet, etc.

In the embodiments represented inFIG. 1, the data managing device18is separate and distinct from the insulin pump12. As such, data can be transmitted from the pump12to the data managing device18, and the user can use the data managing device18separately from the pump12for analyzing and outputting the data. However, in some embodiments, the data managing device18can be included within the insulin pump12(e.g., embodied within the housing of the insulin pump12) without departing from the scope of the present disclosure. In these latter embodiments, the pump12can include components, such as a computerized display, for implementing the data managing device18therein.

As shown inFIG. 1, the system10can further include a blood glucose meter38. The blood glucose meter38can be of a known type. As such, the meter38can be used for detecting the current (i.e., actual) blood glucose level of the patient. More specifically, the patient can apply blood to a test strip (not shown), and the meter38can receive the strip and detect the amount of glucose in the blood thereon. In some embodiments, the meter38can be in operative communication with the pump12, and the blood glucose level can be communicated to the pump12for controlling the amount of insulin (e.g., a bolus dosage of insulin) delivered to the patient. Although the blood glucose meter38is shown inFIG. 1as being distinct from the data managing device18, it will be appreciated that the blood glucose meter38and data managing device18could be combined into a single device within a single housing. Moreover, it will be appreciated that, in some embodiments, the blood glucose meter38or the data managing device18could be used for remotely controlling the pump12(e.g., to send control commands to the pump12to start and stop pumping, etc.).

Referring now toFIG. 4, exemplary embodiments of a method40of operating the insulin pump12will be discussed. As shown, the method40can begin in block42, wherein basal insulin dosages and bolus insulin dosages are delivered to the patient. Then, in block44, the insulin pump12can record the plurality of insulin dosages delivered in block42into the memory device24.

More specifically, the memory device24of the insulin pump12can include one or more predetermined, programmed “delivery profiles” (i.e., schedules) for the automatic delivery of basal and/or bolus insulin dosages. These profiles can dictate the time of delivery, the amount of insulin to deliver, the rate that the insulin is delivered, etc. In block42of the method40ofFIG. 4, the processor22can access the profile(s) stored in the memory device24, and the processor22can send corresponding command signals to deliver the basal and/or bolus dosages from the reservoir20and into the patient's bloodstream via the infusion set14according to the profile(s). Also, in some embodiments, the user can manually input commands such that user-determined bolus dosages are delivered at desired times to reduce current blood glucose levels.

Then, in block44, the processor22can record the actual basal and/or actual bolus insulin dosages delivered in block42of the method40. For instance, the pump12can detect the amount of bolus insulin actually delivered and the corresponding time of delivery (i.e., the calendar date and the time of day). Also, the pump12can detect the amount of basal insulin actually delivered, the flow rate of the basal insulin, and the time of delivery (i.e., the range of time that the basal insulin is delivered). The processor22can obtain the time of delivery of these dosages from the clock26. Then, the processor22can record this dosage data into the memory device24.

FIG. 2is an exemplary embodiment of the data collected in block44. As shown, basal and bolus dosages are delivered over a time period from 12:00 AM on Nov. 14, 2011 and 9:38 PM on Nov. 17, 2011. The bolus dosages are individual events with predetermined insulin amounts (units) (column C, lines 1-18) delivered on specific dates (column A, lines 1-18) and at specific times (column B, lines 1-18). The basal dosages are those delivered at a predetermined rate (units/hour) that can vary over time according to a predetermined flow profile (column C, lines 19-26). In the embodiments illustrated, there is a “flow profile 1” and a “flow profile 2,” each dictating a particular flow rate that can vary according to the date (column A, lines 19-26) and time (column B, lines 19-26). However, it will be appreciated that there can be any number of flow profiles.

In the embodiments shown inFIG. 2, dosage data is collected over a time period including three complete days (i.e., November 14, 15, and 16) and a partial day (i.e., November 17). For purposes of discussion, the data for November 14, 15, and 16 will be considered “complete day dosage data,” and data for November 17 will be considered “partial day dosage data.”

Next, in block46ofFIG. 4, the pump12can determine whether it is the end of the particular day (i.e., recognize completion of a day or an end-of-day event). As mentioned, the processor22can recognize an end-of-day event when the clock reads 11:59 PM and 59 seconds at the end of each day of operation; however, the end-of-day event can be detected using an automatically resetting twenty-four hour timer or in any other way without departing from the scope of the present disclosure.

If the current time is prior to the end of the current day (i.e., block46answered negatively), then blocks42and44can be repeated. Thus, bolus and basal insulin dosages, delivery times, flow rates, etc. can be continuously recorded over the course of each day.

However, once the particular day has ended (i.e., block46answered positively), then block48can follow, and an end-of-day marker can be recorded. Then, in block50, the end-of-day marker can be associated with that day's dosage data. More specifically, the processor22can monitor the clock26and as soon as the clock26indicates completion of the particular day (e.g., the clock26reads 11:59 PM and 59 seconds), the processor22can determine that the end of the day has been reached, and block46can be answered affirmatively. As a result, the processor22can record and associate an end-of-day marker with the respective insulin dosage data in the memory device. The end-of-day markers for the data shown inFIG. 2are represented by an “X” in column D.

In the example ofFIG. 2, since data was obtained over the course of the entire days of November 14, 15, and 16, there is an end-of-day marker for the insulin dosage data for those days. However, since the data was obtained over part of the day of November 17, there is no end-of-day marker for that insulin dosage data.

Subsequently, in block52of the method40ofFIG. 4, the pump12determines whether a data transfer request has been received from the data managing device18. If not (i.e., block52answered negatively), then the method40can loop back to block42. However, if the data managing device18does request that the insulin dosage data be transferred (i.e., block52answered positively), then block54follows, and the insulin dosage data represented inFIG. 2is transferred from the memory device24of the pump12to the data managing device18. The data can be transferred via the communication devices29,36of the pump12and data managing device18, respectively.

It will be appreciated that the data transfer request of block52can be received in various ways. For instance, in some embodiments, the data transfer request might only be received by the pump12when the pump12is selectively placed in a so-called “communication mode” (i.e., communication with the data managing device18is enabled), such that the pump12is able to receive the data transfer request from the data managing device18. Also, in some embodiments, the pump12can request to communicate with the data managing device18before the pump12receives the data transfer request from the device18. Moreover, it will be appreciated that the pump12can continue to pump insulin when communicating and transferring data to the data managing device18.

FIG. 5represents an exemplary method60of operating the data managing device18for processing and outputting the insulin dosage data transferred in block54ofFIG. 4. As shown, the method60can begin in block62, wherein the insulin dosage data62is received by the data managing device18(via the communication device36shown inFIG. 1). Then, in block64, the processor30can determine whether any partial day dosage data is included in the data received in block62. The processor30can rely on the end-of-day markers (described above and represented in column D ofFIG. 2) for making this determination. For instance, the processor30can analyze the received data and if any data does not include an associated end-of-day marker, then it can be assumed that that particular data is “partial day dosage data” (i.e., block64answered affirmatively) and block70can follow. If all of the data received in block62includes associated end-of-day markers, then the processor30can determine that all of the data is “complete day dosage data” (i.e., block64answered negatively), and block66can follow.

In block66, the processor30can utilize the data manager31software to calculate various dosage statistics using the data received in block62. For instance, if only the complete day dosage data (lines 1-12 and 19-25 ofFIG. 2) is received, then the processor30can calculate an average total units of insulin delivered per day, an average bolus units of insulin delivered per day, and/or an average basal units of insulin delivered per day. Then, in block68the data manager31can output the statistics in one or more ways. For instance, the data manager31can display the statistics textually and/or graphically (e.g., in a line graph) on the display32. Also, the data manager31can send commands to a printer to output one or more hard copies of the statistics for use by physicians, the patient, etc.

In additional embodiments, block64can include a determination whether the data received in block62includes any basal data. If not (e.g., if the data only includes bolus data), then all the data can be used for calculating dosage statistics (block66) and displayed (block68). However, if the data received in block62includes basal data, then block70can follow.

Assuming that all of the data shown inFIG. 2is transferred to the data managing device18, then in block64, the processor30can determine that there is both complete day dosage data and partial day dosage data included. Thus, in block70, the data managing device18can parse the complete day dosage data (lines 1-12 and 19-25 ofFIG. 2) from the partial day dosage data (lines 13-18 and 26).

In additional embodiments, the processor22of the pump12can continuously parse partial day data from the complete day data. Thus, when data is transferred to the data managing device18, the received data is already parsed. As such, the processor30need not make the determination of block64. Instead, block62can be followed directly by block72. In still additional embodiments, the data managing device18can receive all data62and can then attempt to parse partial day data from complete day data even if there is no partial day data included. Stated differently, the data managing device18need not perform the determination of block64.

In block72, the processor30can utilize the data manager31software to calculate dosage statistics using only the complete day dosage data (lines 1-12 and 19-25 ofFIG. 2) and excluding the partial day dosage data (lines 13-18 and 26 ofFIG. 2). As mentioned above, the statistics can include an average total units of insulin delivered per day, an average bolus units of insulin delivered per day, and/or an average basal units of insulin delivered per day. These statistics can be output for review by a physician, the patient, etc. For instance, the data manager31can send the statistics to be displayed on the display32of the data managing device18as represented at the bottom ofFIG. 3A. Specifically, as shown inFIG. 3A, the respective percentages of bolus and basal dosages, the average units of insulin delivered per day, the units of bolus insulin delivered per day, and the units of basal insulin delivered per day can be displayed. Additionally, the display32can include a statement saying that the “statistics exclude data from days with incomplete pump data” to thereby inform the viewer that the statistics are not skewed due to inclusion of the partial day dosage data.

Accordingly, the data managing device18can automatically calculate the statistics for the convenience of the patient, the medical professional, etc. Also, since the partial day data is excluded from the calculations, the dosage calculations performed in block72can be very accurate.

Moreover, in block74, the display32can display the dosage data and/or the statistics calculated in block72. Also, in block74, the display32can display both the complete day dosage data and the partial day dosage data. The data manager31can output the data and/or calculated statistics in other ways as well (e.g., by printing hard copies, by outputting the information audibly, etc.).

As shown inFIG. 3A, the display32can display the data included inFIG. 2in a graphic, such as a line graph. (A key to the symbols included inFIG. 3Ais included inFIG. 3B). It will be appreciated, however, that the data could be displayed as any other type of graphic (e.g., a pie chart, a scatter plot, tabular reports, etc.) and can include any appropriate symbols, colors, etc. without departing from the scope of the present disclosure.

As shown in the line graph ofFIG. 3A, the display32can display the calendar date on the X-axis, the bolus insulin amount on the left-hand Y-axis, and the basal insulin flow rate on the right-hand Y-axis. Complete day bolus dosages (delivered November 14-16) can be displayed as solid, vertical bars that extend from the top of the graph. Partial day bolus dosages (delivered November 17) can be displayed as broken, vertical bars. Complete day basal dosages (delivered November 14-16) can be displayed as solid, stepped lines that extend horizontally across the graph, and partial day basal dosages (delivered November 17) can be displayed as broken, stepped lines. Accordingly, the complete day data (bolus and basal) can be quickly and clearly distinguished visually from the partial day data.

It will be appreciated that the display32can distinguish the complete day data from the partial day data in other ways as well. For instance, the lines representing the complete day data can have a different color from the lines representing the partial day data. Specifically, the display32can display complete day bolus dosages in a first color (e.g., red, etc.), the complete day basal dosages in a second color (e.g., blue, etc.), and the partial day bolus and basal dosages both in a third color (e.g., gray or other muted color). Moreover, in some embodiments, lines of different weights (thinner and thicker lines), different appearance (e.g., solid versus broken lines), etc. can be used to distinguish between the complete and partial day data. As such, the viewer can quickly and easily distinguish between the types of data.

In additional embodiments included inFIG. 3A, the display32can display additional information as well. For instance, during the measured time period (here, Nov. 14, 2011 to Nov. 17, 2011), the pump12can detect and record various events, such as a “shutdown event” of the insulin pump12, and the display32can display the time that the shutdown event occurred. Specifically, if the reservoir20becomes empty, the battery28loses sufficient charge, or other condition arises in which the pump12is temporarily incapable of delivering insulin, then the processor22of the pump12can detect that the shutdown event has occurred, and the pump12can record the time of the shutdown event (e.g., the time of occurrence of the shutdown event, the duration of the shutdown event, etc.) into the memory device24. The time of the shutdown event can be transferred to the data managing device18(e.g., with the data transferred in blocks42and62), and the display32can include this information on the line graph with the dosage information. For instance, in the embodiments ofFIG. 3A, times of several shutdown events are displayed with the letter “X” and a line extending downward to the X-axis.

The processor22can also detect other events. For instance, the processor22can detect an insulin refill event of the pump12. Specifically, the processor22can detect rewind of the cartridge of the reservoir20(i.e., indicating a refill of the reservoir20), and the processor22can detect the time that refill occurs (i.e., the refill time) from the clock26. The processor22can also record the refill time into the memory device24, and the refill time can be transferred to the data managing device18. Then, the data manager31can use the display32for displaying the refill event and the corresponding refill time on the line graph as shown inFIG. 3A. In the embodiments ofFIGS. 3A and 3B, the refill event is noted as two adjacent left-facing arrows.

Similarly, the processor22can be operable for detecting priming of the infusion set14for removing blockages therefrom (i.e., detecting a “priming event”) and the time of occurrence of this event. The memory device24can record this information, and the communication device29can transfer this information to the data managing device18. Then, the processor30can cause the display32to include this information on the line graph as shown inFIG. 3A. In the embodiments ofFIGS. 3A and 3B, the priming event can be indicated as an icon resembling a screwdriver.

Those having ordinary skill in the art will understand that other events could also be detected and recorded by the pump12. Corresponding data can then be transferred to the data managing device18for display on the display32.

Additionally, as mentioned above, the processor22can control the amount, flow rate, and/or time of delivery based on one or more alternative programmed dosage profiles. In the embodiments ofFIG. 2, there is a first basal dosage profile (indicated by the number “1”) and a second basal dosage profile (indicated by the number “2”). In the illustrated embodiments, the basal insulin is delivered according to the first basal dosage profile in all but the time period of 8:54 AM to 11:58 AM on Nov. 14, 2011 (column C, line 20). The processor22can automatically change the profile according to programmed logic, or the user can manually input commands for changing the profile. Regardless, the insulin pump12can record “profile data” that indicates whether the basal dosages are delivered according to the first profile or the second profile. The pump12can transfer this “profile data” to the data managing device18in blocks54(FIG. 4) and block62(FIG. 5), and the display32can display the “profile data.” For instance, as shown inFIG. 3A, the line graph can include flags with either the number “1” or the number “2” to indicate which profile was governing the basal dosages. The lines following the flags representing the different basal dosages can also be graphically different (e.g., the basal dosage lines following the “1” flags can be displayed in one color while the basal dosage line following the “2” flag can be displayed in a different color).

Accordingly, the dosage data and the calculated statistics can be presented and summarized in a convenient and useful manner for the patient, a medical professional, etc. Also, using the displayed data and/or the statistics, future dosages can be planned, treatment can be altered, etc. Also, because the partial day dosage data is automatically recognized and excluded from the statistical calculations, the statistics can be an accurate reflection of the delivery of insulin.

As a simplified example of why the statistics would be more accurate, consider a pump12that delivers dosages at a steady rate for a total of ten units of insulin per day. Also, the pump12delivers the insulin according to this schedule for three complete days and for twelve hours on the fourth day. Data is transferred to the data managing device18at the end of the twelfth hour on the fourth day. The methods disclosed herein (i.e., excluding the twelve hours on the fourth day from the statistical calculation) would accurately show that the average daily dosage was ten units per day (i.e., 30 units/3 days=10 units/day). However, if the partial day data were included in the statistical calculation, then the calculated average daily dosage would be 8.75 units per day (i.e., 35 units/4 days=8.75 units/day).

Moreover, as shown inFIG. 3A, the display32of the data managing device18can display the data and statistics in a manner that allows the user to customize what is displayed and/or allows the user to interact with the displayed information. For instance, as shown inFIG. 3A, the time period can be selectively adjusted using pull-down menus and/or data entry boxes. (An exemplary pull-down menu labeled “Custom Range” is shown inFIG. 3A, and an exemplary data entry box is labeled “Nov. 14, 2011-Nov. 17, 2011”). Thus, the user can select which time period should be used for performing the calculations and/or for displaying dosage data. Moreover, as indicated by the “<<” and “<” symbols inFIG. 3A, the display32can allow the user to scroll to data collected at an earlier date, and as indicated by the “>>” and “>” symbols, the display32can allow the user to scroll to data collected at later dates.

In some embodiments, the pump12collects the dosage data in a continuous manner until the pump12receives a command to transfer the collection of data to the data managing device18. It will be appreciated that the pump12can receive the transfer command before the completion of the respective day; therefore, the pump12will transfer partial day data for the day the command is received by the pump12. (In the embodiments ofFIG. 2, the pump12receives the command at 9:38 PM on Nov. 17, 2011, making the dosages of Nov. 17, 2011 partial day data). However, the pump12can continue to record dosage data for the remainder of that day (i.e., the pump12can record “remainder data”) even after the transfer command is received. In this case, the processor22can associate the remainder data with the previously recorded partial day data. Then, upon completion of the day (e.g., 11:59 PM and 59 seconds on Nov. 17, 2011), the processor22can detect the end-of-day event and associate the end-of-day marker with the data for that entire day. Next, the data and associated end-of-day marker can be transferred to the data managing device18, which will now consider that day's data as complete day data. Thus, the data for that day can be included in the calculations of the average daily dosage, etc. as described above. Moreover, the data for that day can be displayed with the other complete day data.

In additional embodiments, data on the pump12might include only partial day data. When transferred to the data managing device18, the processor30can determine that only partial day data is included. As a result, the processor30can display the partial day data graphically according to the above discussion. Also, in some embodiments, the processor30can prevent daily dosage averages or other statistics to be calculated using this partial day data.