Device and method for insulin dosing

Information

  • Patent Grant
  • 11294407
  • Patent Number
    11,294,407
  • Date Filed
    Monday, May 20, 2019
    5 years ago
  • Date Issued
    Tuesday, April 5, 2022
    2 years ago
Abstract
A device and method of providing instruction to a patient regarding the dosing of insulin is provided.
Description
FIELD OF THE INVENTION

The present invention relates generally to the administration of insulin in diabetics. More particularly, the present invention relates to a device and method that provides insulin dosage alterations for various conditions.


BACKGROUND AND SUMMARY

The art of self-care for a patient with Type-1 diabetes typically involves an assortment of professional Health Care counseling, hard-copy guide sheets provided by a Health Care Professional, self-care reading material and improvisation based on well established general principles of how the endocrine system operates. However, this knowledge is hard won and not easily put into practice by patients with Type-1 diabetes.


A person with type 1 diabetes will typically die well within a year without insulin. Even still, not all such persons are willing to make alterations to their (necessary—life sustaining) doses. They administer fixed fast-acting insulin doses in conjunction with meals and rarely, if ever, make alterations to those doses. Additionally, they administer doses of a slower-acting insulin to contend with their background needs (e.g., mobility) not associated with meals.


By contrast, for persons with type 2 diabetes: approximately only 30% of these persons inject insulin, more of those persons can benefit from injecting insulin, and not all of these persons need insulin, meaning diet, exercise and oral “meds” may suffice.


Accordingly, a device and method are provided that automates insulin dosing advice.


According to one aspect of the present invention, a device for providing improved drug dosing advice to a patient is provided. The device being a portable, handheld and battery powered device comprising: an evaluation and interpretation facility comprising a processor for executing a program, a memory for storing a program to be executed by the processor and for storing and retrieving data used by the program, a display for displaying data and instructions to the user, and a human interface for entering data, and instructions stored on the memory as part of the program. When the program is executed by the processor, it causes the evaluation and interpretation facility to: determine a first expected dose of the drug; determine a first actually administered dose of the drug, determine whether the first actually administered dose differs from a first expected dose of the drug, determine a second expected dose of the drug; determine a second actually administered dose of the drug, determine whether the second actually administered dose differs from a second expected dose, and calculate a third expected dose on the basis of the first actually administered dose and the second actually administered dose when the first actually administered dose is determined to differ from the first expected dose and the second actually administered dose is determined to differ from the second expected dose.


Additional features of the present invention will become apparent to those skilled in the art upon consideration of the following detailed description of the presently perceived best mode of carrying out the invention.





BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description of the drawings particularly refers to the accompanying figures in which:



FIG. 1 is a PDA capable of providing insulin dosing advice; and



FIG. 2 is an example of a screen shown on the PDA of FIG. 1;



FIGS. 3-15 are screens capable of being displayed on the PDA of FIG. 1.





DETAILED DESCRIPTION OF THE DRAWINGS

A PDA 10 is shown in FIG. 1 for providing insulin dosing advice to a user. PDA 10 includes a screen 12, a plurality of input devices/human interfaces 14 (which may include screen 12), a processor (not shown), and memory (not shown). Examples of PDA's are handheld computing devices made commercially available by Palm, Inc. and Handspring. While the methods and programs described herein will be discussed as taking place through the use of PDA 10, it should be appreciated that various devices capable of performing the methods or executing the programs are envisioned as suitable alternatives to a PDA 10.


PDA 10 is selectively connected to a desktop application such as a PC or a printer. PDA 10 is additionally capable of downloading data to a web based server where the data can be reviewed by a health care professional. The connections may be wired or wireless.


The memory of PDA 10 stores programs thereon which are executed by the processor of PDA 10. The processor performs the functions of an evaluation and interpretation facility for executing a program. The memory of PDA 10 also stores data used by and/or retrieved by the programs. One such program is an interactive program for dispensing insulin dosing regimen advice.


A “regimen” consists of a battery of base doses, also referred to as usual doses. In the field of insulin dose therapy are two kinds of alterations of these usual doses: adjustments and supplements. “Adjustments” are defined as persistent changes to usual doses, and supplements are defined as temporary changes to usual doses.


This temporal contrast can be shown on the basis of an alteration to a usual dose that relates either to the current session (AKA entry) alone, in which case the alteration is a supplement. For an alteration that relates both to the current session and to a next (or further) session, the alteration is an adjustment.


An opening screen shot for the insulin dosing program is shown running on a PDA 10 in FIG. 2. FIG. 2 shows a menu including an indication of a next scheduled injection, meal start, or pre-meal or bedtime entry 16. Additionally, the user is presented four buttons including New Entry 18, Diary 20, Reports 22, and Tools And Info 24. New Entry button 18 allows the user to enter new information relating to scheduled entries, injections, or meals. Diary button 20 allows a patient to review previous entries. Reports button 22 allows the user to create an on-screen report or a text exported report. Tools And Info button 24 allows the user to find information and review settings and tools.


The software allows a healthcare professional to assemble a prescription such that for each entry time, patients are provided with time sensitive advice and restrictions based upon the healthcare professional configured prescription. Furthermore, the software allows for each recommendation for each entry to vary according to the prescription, the entry time label, and patient's input. In general, a prescription includes usual doses for each time period at which a regiment dose is to be administered. The prescription further includes a plurality of dosing alterations for various factors, which are discussed below.


A pre-meal entry includes many pieces of information including a blood glucose result, an entry time label, a health/activity level, food intake information, insulin advice, actual insulin taken, physiological information, injection time, and meal time advice. The blood glucose result is typically received by either reading blood glucose results from a compatible blood glucose meter or from a numeric key pad on the screen used by the user to enter the blood glucose values. The software will check the time on the blood glucose result to make sure it is recent enough for actionable support or advice. When the blood glucose result is received from a compatible blood glucose meter, the result will have the time associated with the result as part of the received transmission. When the blood glucose result is received via the numeric keypad the user is either allowed to enter the time that the result was taken or the time of entry is used as the time the result was taken. In some embodiments, if the blood glucose result is entered via the numeric keypad and the time of the result is likewise entered via the keypad, the software requires that the time entered be within a defined range of when the entry is being inputted. For example, in such embodiment the software will require that if the reading was taken at 12:45 p.m. that it actually be entered into PDA 10 by 1:00 p.m. The advice and support available for each entry changes based upon the entry time label. This label allows the software to retrieve the correct prescription parameters for the entry time. Patients can also select physiological conditions that effect their insulin requirements, such as exercise, stress, menstrual status, and whether or not the patient is experiencing illness. Once such conditions are selected, the patient may enter a value related to that condition, select one of a set of pre-selected value associated with such conditions, or the value may be incorporated in the condition (e.g. light exercise or mild stress). The value may be a numerical value, such as to indicate a severity or level of the condition such as light, mild, etc., may be a yes or no, and may include words to describe the condition. The software uses prescription parameters that the healthcare professional sets to alter the patient's insulin advice based upon the entered patient conditions. The prescription parameters at least partially define how the patient conditions are interpreted by the software to alter dosing recommendations as discussed below.


The software also uses factors set by the healthcare professional in the prescription to provide food intake insulin supplements. These supplements allow patients to receive insulin advice for increased or decreased meal sizes and for snacks. The software consults the prescription to retrieve usual doses in an insulin regimen. It should be appreciated that the usual dose may be zero. It also retrieves any applicable prescription parameters that account for variances in normal levels of the blood glucose results, the health/activity factors, and food intake to provide patients with patient factor altered insulin advice.


Patients can also choose to accept the recommended insulin advice/expected insulin dose or to override the advised insulin dose. By disagreeing with the advised doses, patients can enter the insulin doses they actually plan to inject. The software then consults with the prescription for the insulin limits to guide how much patients can increase or decrease each insulin dose should they so choose. If the patient planned dose is outside of limits set in the program, alerts are generated and displayed to the user. Additionally, the number of the patient altered doses is logged and reported to the healthcare professional on the next instance of patient monitor data upload. After patients confirm insulin doses for actual use, the software uses the prescription and the patient's blood glucose results to display timing advice for when to administer the injection and when to ingest the related meal or snack.


Healthcare professionals are also able to provide lockouts for the advising software. The healthcare professional may define insulin limits and set notification items that help the patients manage their diabetes. The software uses these healthcare professional set limits to determine when to provide or suspend insulin therapy support. Notification items are generated when the input conditions and readings meet the set criteria such that the healthcare professional wishes to be notified thereof.


Many of the settings available to be changed by the healthcare professional, such as the prescription, are password protected to maintain the security of the prescription. This password limits the access to only allow the healthcare professional to make changes to the prescription and it ensures the privacy of the treatment plan. While the user or patient can view the prescription parameters by looking it up in the Tools And Info 24 section or creating text export, the user may be prohibited from making changes to the prescription via the password protection.


Diary button 20 provides a history of the patient's entries. The entries can be scrolled through or a calendar can be used to jump directly to a specific date. A diary day view lists entries that the patient has recorded for each day and the blood glucose results for each entry. Each entry can be selected to view details about the health and activity levels and the food intake, or to compare the advised insulin doses with the actually administered insulin doses.


Tools And Info section 24 of the software, shown in FIG. 3, provides meal time information. Before the patient can record entries, he/she uses the meal time screen, FIG. 4, to set up their schedule for meals and entries. Tools and Info section 24 may also give the patient's healthcare professional information. Here, the patient can look up contact information for their healthcare professional.


Tools And Info section 24 also allows the patient to look up his or her insulin regimen as shown in FIGS. 5 and 6. The patient can access a screen to view the insulin regimen prescribed by the healthcare professional. Patients can toggle the view to display the usual doses, which account for past adjustments, FIG. 5, or to view an altered regimen that includes supplements to account for changes in the health/activity state or food intake changes, FIG. 6.


The patient may also view a blood glucose correction table which displays scales set up in the prescription as shown in FIG. 7. The table defines the supplements in dosing that will be made in response to ranges of blood glucose readings reported to the device 10. The software automates these scales during a supported entry to automatically alter the recommended dose by the defined alteration amount. However, the patient may also access the screen to look up their blood glucose correction guidelines.


Blood glucose targets are also shown under Tools and Info section 24. As shown in FIG. 8, the blood glucose target screen displays the blood glucose goals set by a healthcare professional for the patient in the prescription. Patients may find it helpful to know the upper and lower limits of each target range.


As shown in FIG. 9, Tools and Info section 24 also provides a section where patients may enter weight updates. If set by the healthcare professional, the software reminds patients to enter weight updates at defined intervals, such as every two weeks.


Additionally, Tools And Info section 24 includes a carbohydrate calculator screen. The carbohydrate calculator screen displays a carbohydrate compensation tool that allows patients to enter carbohydrate grams and work with one or more insulin-to-carbohydrate ratios, morning or rest of day, set by a healthcare professional in the prescription, shown in FIGS. 10 and 11. These insulin-to-carbohydrate ratios are used by the prescription when increased or decreased food intake is entered by a patient to determine how much a usual dose will be supplemented to arrive at a recommended dose. The carbohydrate calculator screen is provided to a patient to give the patient an idea of how an inputted carbohydrate load will affect the recommended dose. While the patient is informed by this screen how the carbohydrate load will affect the recommended dose, it is for informational purposes only. The patient is not instructed to look up the supplement amount and unilaterally supplement their dose themselves.


The reporting features in the advising software allow a healthcare professional or a patient to review patient's entries and activities in two ways. The first way allows the creation of an on-screen report to review the information from the patient's PDA 10. Alternatively, the patient's PDA 10 is set up to create a text export that sends patient information from the PDA 10 to a healthcare professional's PC each time that a patient hot synchs their PDA 10 to a PC.


The software is set to categorize the received patient information and reports sent to the healthcare professional. The reports are organized such that those messages indicating severe readings are prioritized and sent to the top of the list to be first viewed by the healthcare professional.


Many different reports are available to be produced by the advising software. One such report is a date report that sorts the patient entries according to the date each entry was recorded. This report shows the number of entries for each date, the blood glucose result average for the day, and the total units of insulin that the patient recorded. A second type of report that is available is a diary report shown in FIG. 12. This report sorts the entry information according to the entry time label. This report shows the number of entries for each entry time within a selected date range specified by the healthcare professional. It also shows the average blood glucose result and the standard deviation for the selected blood glucose results. Furthermore, the diary report will list the lowest and highest blood glucose results for each entry time. A third type of report available from the software is a warnings report. The warnings report lists the insulin therapy alert messages that the patient has received during his or her entries, such as for exceeding a maximum daily dose of insulin. The healthcare professional may view the date and the entry time label for each alert message. A fourth type of report available from the advising software is the notifications report. The notifications report allows a healthcare professional to check the status of each notification item that has been enabled in the prescription by the healthcare professional. The healthcare professional can monitor high and low blood glucose results and review the percentage of blood glucose results outside of the target blood glucose ranges.


The healthcare professional works with the software to set up a prescription for an individual patient. The healthcare professional can define when and how the patient interacts with the software by specifying prescription parameters regarding the insulin regimen, blood glucose targets, blood glucose corrections, carbohydrate compensations, health/activity alterations and safety notifications. These settings allow the healthcare professional to set the usual doses, the timing of the usual doses, and the alteration factors that change the usual doses to arrive at the recommended doses.


In setting up the insulin regimen, the healthcare professional selects the types and amounts of insulin and the schedule when a patient will inject the insulin. The healthcare professional defines blood glucose target ranges, FIG. 8, for a patient to establish therapeutic goals to identify when the patient needs blood glucose corrections. The healthcare professional specifies the amount of insulin above or below the usual dose that the software recommends when the patient's blood glucose result is outside of his or her target range, FIG. 7.


The healthcare professional may also enable health and activity compensation to specify how the software responds to changes in the patient's health and activity levels, such as a mild illness, menstrual status, and exercise. Similarly, to how the carbohydrate intake supplements work, health and activity supplements allow insulin advice to be provided to recommend more or less insulin to compensate for changes in the patient's health and activity levels by receiving input regarding health and activity levels and converting that input into an alteration in the recommended dose.


Additionally, the healthcare professional may configure the prescription to define safety limits for insulin injections and blood glucose readings. The healthcare professional can specify when a patient should call the healthcare professional to keep the healthcare professional aware of the patient's ongoing insulin needs.


The healthcare professional also enters patient information such as height, weight, age and gender, FIG. 13. The healthcare professional may also enter information regarding whether the patient is pubescent or post-menopausal. The healthcare professional is also permitted to define a change in the insulin dose factor for said pubescent or post-menopausal patients. For patients identified as pubescent the healthcare professional is also permitted to enter information regarding the Tanner stage, stage of pubescence, of the patient and to set insulin dose factors specific to individual Tanner stages.


In setting up an insulin regimen, the software starts by allowing the health care provider to select specific insulin types to be administered. The software then utilizes the patient's weight and a prescribed insulin dose factor to determine a total daily dose of insulin for the specific patient, as shown in FIG. 14. The insulin regimen then allows the healthcare professional to select an injection schedule for patients, such as a four injection schedule, which would include a breakfast time, lunchtime, suppertime, and bedtime injections. Once the schedule is selected/set up, the healthcare professional is presented with a table that allows the healthcare professional to select the specific insulin amounts to be administered at each of the injection times.


The healthcare professional is also provided with the screen to define the blood glucose target ranges, FIG. 8. The blood glucose target range screen also allows the healthcare professional to define a low and high range for the blood glucose readings at either one or two hours after each of the prescribed meal start times. The healthcare professional is also enabled to assemble a table that determines what insulin supplements or adjustments to the usual dose are to be made in response to a blood glucose reading outside of the target ranges, FIG. 7.


The healthcare professional configures the insulin dose supplements for changes in food intake and changes in health factors, FIG. 15. A food and health screen allows the healthcare professional to control the insulin supplements for food variations and also insulin supplements for the health and activity variations.


As seen in FIG. 15, the healthcare professional may select different insulin-to-carbohydrate ratios to alter for food variations at different defined times of the day. Similarly, the healthcare professional may choose to define or enable alterations for health and activity changes and may choose the magnitude of the alteration factors therefor.


Most of the screens and features that are present for the healthcare professional have analogous screens and inputs for the patient. In Tools And Info section 24 of the software, the patient inputs the times they typically start eating breakfast and supper, as shown in FIG. 4. Using the meal times input by the patient, and the blood glucose measuring times being either one or two hours after a meal that is set by the healthcare professional, the advising system provides the patient with the times when blood glucose readings should be taken. Additionally, by inputting actual meal/bed injection times, the software alters later expected meal and injection times. For example, if a patient has a scheduled breakfast dose time of 7:00 a.m., a scheduled lunch dose time of 12:00 p.m., and informs the software that the actual breakfast dose time was 7:30 a.m., the software pushes out the scheduled lunch dose time to 12:30 p.m. to maintain the desired 5 hour separation between breakfast and lunch doses. In addition to inputting meal dose times, the patient may also input the time of a bed time dose.


Also in Tools And Info section 24 the patient may view the regimen prescribed by the healthcare professional. The patient may choose to view the usual prescription which incorporates past adjustments, FIG. 5, or the prescription for the current day, FIG. 6, which incorporates any of the supplements for the health/activity states.


Additionally, the patient may view the blood glucose correction screen, FIG. 7. The blood glucose correction screen displays the blood glucose elements specified by the healthcare professional on a blood glucose correction scale screen in the prescription. The patient may only view information on the screen and is not permitted to modify the values. The screen shows the insulin supplements which correspond to specific blood glucose readings at the different times when blood glucose test times are prescribed. Additionally, the patient may view the blood glucose target ranges, FIG. 8, which are set up by the healthcare professional on a blood glucose target screen.


A diary detail screen provides a summary of the information displayed during the entry. This information includes both the blood glucose result and physiological conditions entered by the patient, as well as the insulin therapy advice and feedback provided by the software. The patient sees the diary detail after completing entries. The diary detail screen can also be accessed by selecting an entry on the diary day screen. The diary detail screen includes an entry time label, a health and activity level for the entry, actually taken (administered) insulin doses, and an indication of whether the blood glucose result is above, within or below a target. The actual blood glucose results for the entry, indications of whether notes regarding the entry are available, and indications whether the food intake was above, below, or within the usual amounts are also available.


Patient entries regarding administered insulin injection times may alter subsequent scheduled injection times. For example, with prescriptions containing an intermediate acting insulin, if a patient's scheduled bedtime entry is 11 PM, the patient is provided with a window of up to an hour on either side in which to make that entry. If the patient records the bedtime entry at 11:30, the software identifies the patient's actual injection time as 11:30 PM. Because the patient's bedtime injection is 30 minutes after the scheduled time, the software will move the next stage pre-breakfast entry time later by 30 minutes, and the software will alert the patient of the change. Such movement helps maintain a desired eight hour time span between a bedtime and pre-breakfast insulin injection. Likewise, injecting the pre-breakfast insulin dose before or after the scheduled time can effect pre-lunch and pre-supper insulin injections.


To update meal entry times the software identifies three pieces of information. First, the software identifies the scheduled time for the pre-breakfast insulin injection which is obtained from the times the patient set up on the mealtime screen. Second, the software identifies when the patient actually injects the pre-breakfast usual dose of insulin. This time is displayed during the pre-breakfast entry as injection advice indicating when he/she should inject the insulin dose. Third, the software identifies the scheduled times for the pre-lunch and pre-supper blood glucose test times. These test times are set up on the mealtimes according to the breakfast and supper mealtimes the patient specifies.


The software compares the scheduled time for pre-breakfast insulin injections to the actual injection time. Both the pre-lunch and pre-supper times update to maintain the original interval of time between the pre-lunch/pre-supper time and the pre-breakfast entry time shown on the mealtime screen. If the patient injects the pre-breakfast usual insulin dose more than five minute before or after a scheduled time, the software shifts the pre-lunch and pre-supper times by the same amount. An alert message is also generated to display the updated time for the next scheduled entry which is pre-lunch in the provided example. The patient is then provided a mealtime screen that shows the updated meal and entry times for the patient. Alternatively, the patient is shown the main menu that displays a “next event” field.


The information entry process for a patient includes four main screens: A new entry screen (not shown), where patients can enter their blood glucose result, a control result, or indicate that they wish to record an entry without entering a blood glucose result. The second main screen is an entry input screen (not shown). Here, the software provides feedback on a patient's blood glucose result and allows patients to specify conditions impacting their insulin advice, such as their current health, activity state, and carbohydrate intake. The third main screen is the entry advice screen (not shown). The entry advice screen retrieves usual insulin doses from the regimen prescribed by the healthcare professional, blood glucose corrections and any conditions patients enter on the previous screens, and the software displays insulin dose advice. On the entry advice screen the patient is also invited to agree with the insulin advice provided or to disagree, and then enter the insulin dose(s) they actually intend to inject.


The fourth main screen is the entry insulin screen(not shown). This final screen in the entry allows patients to confirm their insulin dose and it also displays meal and insulin timing advice.


When entering the intended carbohydrate intake, on the second main screen, a carbohydrate compensation algorithm can come into effect if the patient-declared carbohydrate intake excursion or increment exceeds the defined carbohydrate limits. In such a case, the currently declared carbohydrate intake is compared to the defined carbohydrate limits and then the insulin-to-carbohydrate ratio is applied to place the increment within the carbohydrate limits. In the event that the declared carbohydrates are above the carbohydrate limit the patient will also be provided with a warning indicating that their declared carbohydrate intake is above the prescribed carbohydrate limit, and that they should reduce the amount of carbohydrates they are planning to ingest at the current meal. Similar programming exists for events where the declared carbohydrate intake is deemed too low. The patient then chooses whether or not to alter their carbohydrate intake or proceed with the previously entered carbohydrate intake.


The software then progresses to an entry advice screen that reinforces the entry time label and the blood glucose result for the entry and displays advised insulin doses. The screen indicates both the adjusted usual insulin doses for each type of prescribed insulin and any supplemental doses that are recommended for each type of insulin based upon the change factors, and then displays the total recommended dose that is the sum of the adjusted usual dose and the supplemental dose.


The patient is also invited to agree or disagree with this advice. If the patient agrees with the insulin advice and intends to take the amount of insulin shown in the total column, he/she chooses “agree.” If the patient does not agree with the advice, he/she taps “disagree.” This brings up a screen instructing the patient to enter the actual dose that he/she intends to take. When a patient taps the “accept” to continue with the entry, the software will compare the patient's actual intended dose to the insulin limits calculated for the entry. An alert message will appear to tell the patient when an insulin dose is above or below an insulin limit. The alert message further provides the patient with the option to return to the interaction insulin screen and change the insulin dose. Alternatively, the patient is allowed to choose that they do not wish to change the actual insulin dose and they plan on proceeding with their previously entered dose. In the event that the patient chooses to proceed with a dose that is outside of predefined limits, a notice or warning is created. Furthermore, under certain circumstances predefined by the healthcare professional, such as exceeding the total daily dose or the patient's blood glucose reading being outside of a desired range, notifications or warnings are transmitted to the patient and potentially to the healthcare professional or another third party via e-mail or other communication.


As part of the functionality allowing the patient to disagree with recommended doses, the software runs an algorithm that detects consistent deviation from recommended doses. More specifically, if a patient disagrees with a dose on a first day, for example, Monday, and specifically the pre-breakfast entry, and likewise disagrees on a second day, for example, Tuesday, with the breakfast entry again, the algorithm will note the consistent deviation from a recommended dose and adjust the recommended dose to be the average of the two patient altered doses. Such adjustment will be performed by the algorithm taking into account the recommended usual dose and any alteration present in the altered recommended dose. For example, if a patient indicates typical health and exercise status on both Monday and Tuesday at the pre-breakfast dosing times then the recommended doses for Monday and Tuesday pre-breakfast are possibly equal. If the user has indicated an administered dose that differs from the recommended dose at pre-breakfast of both Monday and Tuesday, the algorithm will know that the usual dose for the pre-breakfast time should be adjusted to be the average of the two patient inputted administered/actual doses. Similarly, if the pre-breakfast dosings for typical conditions are being followed by the patient, but the recommended dosings on days when there is increased exercise are being altered by the patient, the software looks for two consecutive increased exercise days on which the pre-breakfast dose is altered by the patient. In such an event, the algorithm adjusts the factor by which the usual dose is altered for exercise such that the recommended dose for pre-breakfast on days with increased exercise is the average of the two doses that were altered by the patient. It should be noted that the two consecutive increased exercise days do not have to be consecutive calendar days. For example, if there is increased exercise on Monday and the patient rejects the recommended pre-breakfast dose, followed by normal exercise on Tuesday and the patient accepts the recommended pre-breakfast dose, followed by increased exercise on Wednesday and the patient rejects the recommended pre-breakfast dose, then the algorithm recognizes that with respect to days with increased exercise, the previous two such days are associated with the patient rejecting the recommended pre-breakfast dose. Accordingly, the alteration factor associated with exercise will be adjusted to allow the recommended pre-breakfast dose to be the average of the previous two actually administered pre-breakfast doses under the defined conditions (the average of Monday and Wednesday).


More generally, when making alterations in the recommended doses, the algorithm considers past doses taken and recommendations that were provided when the patient was experiencing health and activity levels (or states) similar to the current levels (or states) for which a recommendation is being generated. As another example, if a patient indicates that she is starting her menstrual cycle, the algorithm takes into account the doses recommended and taken the last time that the patient indicated that she was starting her menstrual cycle as well as considering the blood glucose control that resulted from the recommended/taken doses on those days.


Another example usual dose alteration algorithm deals with when a low blood glucose level is received by the dosing program, by example of a low blood glucose received before lunch. In such an event, the algorithm adjusts the breakfast bolus dose on the following day. More generally, the algorithm will analyze the dose administered prior to a low blood glucose reading to determine what factor of the earlier taken dose needs to be adjusted. Using historical recommended doses, historical actual doses, historical patient factors, the usual dose, alterations, and patient factors for the prior dose, all of which are stored in PDA 10 or another computing device, the algorithm determines which, if any, of the usual doses, the alteration doses, or supplemental doses need to be altered.


The algorithm also watches for unscheduled insulin doses. If a patient indicates that he has made an injection at a time when the advising system has not recommended a dose, the administered dose is labeled as an unscheduled dose. Similarly to how the algorithm processes repeated doses that deviate from the recommended doses, repeated unscheduled doses at similar times under similar physiological conditions result in the adjustment of the expected doses or the addition of a regularly scheduled extra dose.


Additionally, the software has the ability to require that a blood glucose reading be entered, either into a blood glucose monitor or to be keyed into the advisor, within a defined window around an expected time for the blood glucose reading. For example, if the advisor system expects a blood glucose reading at noon, the advisor system can define a window from 11:00 a.m. to 1:00 p.m. in which the patient is required to manually enter a blood glucose reading or to have the reading taken on a blood glucose meter capable of noting the time and beaming the results to the advisor system. Failure to enter a reading within the window causes the advisor system to label the entry as non-conforming and prevent the patient from receiving an insulin dose recommendation. Requiring that the blood glucose reading be entered within the window or being able to show that the reading was taken at a specific time by having the results beamed to the advisor system provides increased likelihood that the reading was actually taken rather than being fabricated by the patient.


In one embodiment, the ability of the algorithm to quickly alter the recommended doses is aided by requesting many pre- and post-meal blood glucose readings. In, for example, a first week of use by a patient, the advising system requests all possible pre- and post-meal blood glucose readings, with the possible exception of a 3-am reading, and uses these readings to customize the recommended regimen. A low blood glucose reading causes adjustment of the regimen of the next day. A high blood glucose reading requires the previously discussed two day repetition to cause adjustment of the regimen. After the algorithm has received enough data, for example, a week, post-meal blood glucose readings are only conditionally requested. Such conditional requests may be requested to verify that dose alteration levels are properly set or when a new health or activity condition is defined or selected by the patient.


Although the invention has been described in detail with reference to certain preferred embodiments, variations and modifications exist within the spirit and scope of the invention as described and defined in the following claims.

Claims
  • 1. A device for providing improved drug dosing advice to a patient, comprising: an evaluation and interpretation facility comprising a processor for executing a program,a memory for storing a program to be executed by the processor,a display for displaying data and instructions to the user,a human interface for entering data, andinstructions stored on the memory as part of the program such that when the program is executed by the processor, the processor causes the evaluation and interpretation facility to: determine a first expected dose of the drug;determine a first actually administered dose of the drug,determine whether the first actually administered dose differs from a first expected dose of the drug,determine a second expected dose of the drug;determine a second actually administered dose of the drug,determine whether the second actually administered dose differs from a second expected dose,respond to a condition wherein the first actually administered dose differs from the first expected dose and the second actually administered dose differs from the second expected dose by calculating a third expected dose on the basis of the first actually administered dose and the second actually administered dose; andrespond to a received value of a physiological condition of the patient being different from a defined normal value of the physiological condition by defining the first expected dose as equal to a given dose administered in the past when the value of the physiological condition was similarly different from the defined normal value;wherein the device is further configured to upload dosing history to a healthcare professional computer.
  • 2. The device of claim 1, wherein the evaluation and interpretation facility calculates the third expected dose by averaging the first actually administered dose and the second actually administered dose.
  • 3. The device of claim 1, wherein the evaluation and interpretation facility defines the third expected dose to be equal to the first expected dose if the first expected dose is equal to the actually administered first dose or if the second expected dose is equal to the actually administered second dose.
  • 4. The device of claim 1, wherein the evaluation and interpretation facility determines each of the first and second doses by utilizing previously determined differences between expected and actually administered doses.
  • 5. The device of claim 1, wherein the first expected dose is for a defined time on a first day, the second expected dose is for the defined time on a second day, and the third expected dose is for the defined time on a third day.
  • 6. The device of claim 1, wherein execution of the instructions by the processor further causes the evaluation and interpretation facility to: define the received value for a physiological condition as the normal value and define a usual dose associated with the normal value of the physiological condition;determine if the received value of the physiological condition of the patient is equal to the defined normal value; anddefine the first expected dose as equal to the usual dose in response to the received value of the physiological condition of the patient being equal to the defined normal value.
  • 7. The device of claim 1, wherein execution of the instructions by the processor further causes the evaluation and interpretation facility to instruct the patient to either 1) agree to the administration of the third expected dose or 2) to disagree with the administration of the third expected dose and input a third actually administered dose.
RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. Pat. No. 10,311,209, filed Jul. 10, 2012, titled “DEVICE AND METHOD FOR INSULIN DOSING” which claims priority to U.S. Pat. No. 8,251,904, filed Jun. 7, 2006, titled “DEVICE AND METHOD FOR ADJUSTING INSULIN DOSING” which claims priority to U.S. Provisional Patent Application Ser. No. 60/689,166, filed Jun. 9, 2005, to Zivitz et al., titled “ACCU-CHEK ADVISOR INSULIN GUIDANCE SOFTWARE HEALTHCARE PROFESSIONAL'S GUIDE,” U.S. Provisional Patent Application Ser. No. 60/689,751, filed Jun. 9, 2005, to Zivitz et al., titled “ACCU-CHEK ADVISOR INSULIN GUIDANCE SOFTWARE USER'S GUIDE,” U.S. Provisional Patent Application Ser. No. 60/689,703, filed Jun. 9, 2005, to Zivitz et al., titled “INSULIN DOSING FOR ACUTE PHYSIOLOGICAL SHIFTS,” U.S. Provisional Patent Application Ser. No. 60/689,702, filed Jun. 9, 2005, to Zivitz et al., titled “INSULIN DOSING ALTERATIONS FOR DEVIANT INSULIN INJECTIONS,” and U.S. Provisional Patent Application Ser. No. 60/689,303, filed Jun. 9, 2005, to Zivitz et al., titled “INSULIN DOSAGE ADJUSTMENTS FOR HIGH BLOOD GLUCOSE READING,” the priority of which and disclosures of which are each expressly incorporated by reference herein.

US Referenced Citations (318)
Number Name Date Kind
4370950 Furukubo Feb 1983 A
4560104 Nagumo et al. Dec 1985 A
4606302 Huemer et al. Aug 1986 A
4621594 Kubis Nov 1986 A
4731726 Allen, III Mar 1988 A
4976462 Hirata et al. Dec 1990 A
5216597 Beckers Jun 1993 A
5238185 Saur et al. Aug 1993 A
5251126 Kahn et al. Oct 1993 A
5307263 Brown Apr 1994 A
5385296 Kurz et al. Jan 1995 A
5420108 Shohet May 1995 A
5434611 Tamura Jul 1995 A
5441047 David et al. Aug 1995 A
5459317 Small et al. Oct 1995 A
5558638 Evers et al. Sep 1996 A
5576952 Stutman et al. Nov 1996 A
5589045 Hyodo Dec 1996 A
5601435 Quy Feb 1997 A
5626144 Tacklind et al. May 1997 A
5633910 Cohen May 1997 A
5678562 Sellers Oct 1997 A
5678571 Brown Oct 1997 A
5730654 Brown Mar 1998 A
5752976 Duffin et al. May 1998 A
5781455 Hyodo Jul 1998 A
5822715 Worthington et al. Oct 1998 A
5828943 Brown Oct 1998 A
5832448 Brown Nov 1998 A
5867688 Simmon et al. Feb 1999 A
5872713 Douglas et al. Feb 1999 A
5879163 Brown et al. Mar 1999 A
5887133 Brown et al. Mar 1999 A
5897493 Brown Apr 1999 A
5899855 Brown May 1999 A
5913310 Brown Jun 1999 A
5918603 Brown Jul 1999 A
5919141 Money et al. Jul 1999 A
5919216 Houben et al. Jul 1999 A
5933136 Brown Aug 1999 A
5940801 Brown Aug 1999 A
5950630 Portwood et al. Sep 1999 A
5951300 Brown Sep 1999 A
5956501 Brown Sep 1999 A
5960403 Brown Sep 1999 A
5967975 Ridgeway Oct 1999 A
5985559 Brown Nov 1999 A
5997476 Brown Dec 1999 A
6024699 Surwit et al. Feb 2000 A
6032119 Brown et al. Feb 2000 A
6068615 Brown et al. May 2000 A
6101478 Brown Aug 2000 A
6116148 Allen Sep 2000 A
6117076 Cassidy Sep 2000 A
6131090 Basso, Jr. et al. Oct 2000 A
6134504 Douglas et al. Oct 2000 A
6144837 Quy Nov 2000 A
6144922 Douglas et al. Nov 2000 A
6151586 Brown Nov 2000 A
6161095 Brown Dec 2000 A
6162180 Miesel et al. Dec 2000 A
6167362 Brown et al. Dec 2000 A
6168563 Brown Jan 2001 B1
6186145 Brown Feb 2001 B1
6192891 Gravel et al. Feb 2001 B1
D439242 Brown et al. Mar 2001 S
6196970 Brown Mar 2001 B1
6210272 Brown Apr 2001 B1
6216096 Obermeier Apr 2001 B1
6233539 Brown May 2001 B1
6246966 Perry Jun 2001 B1
6246992 Brown Jun 2001 B1
6248065 Brown Jun 2001 B1
6260022 Brown Jul 2001 B1
6264614 Albert et al. Jul 2001 B1
6269314 Iitawaki et al. Jul 2001 B1
6270455 Brown Aug 2001 B1
6270457 Bardy Aug 2001 B1
6277071 Hennessy et al. Aug 2001 B1
6280380 Bardy Aug 2001 B1
6290646 Cosentino et al. Sep 2001 B1
6292698 Duffin et al. Sep 2001 B1
6295506 Heinonen et al. Sep 2001 B1
6309884 Cooper et al. Oct 2001 B1
6311163 Sheehan et al. Oct 2001 B1
6315719 Rode et al. Nov 2001 B1
6330426 Brown et al. Dec 2001 B2
6334778 Brown Jan 2002 B1
6352505 Bortz Mar 2002 B1
6364834 Reuss et al. Apr 2002 B1
6368273 Brown Apr 2002 B1
6375469 Brown Apr 2002 B1
6377894 Deweese et al. Apr 2002 B1
6379301 Worthington et al. Apr 2002 B1
6381577 Brown Apr 2002 B1
6401085 Gershman et al. Jun 2002 B1
6402691 Peddicord et al. Jun 2002 B1
6406426 Reuss et al. Jun 2002 B1
6424996 Killcommons et al. Jul 2002 B1
6442432 Lee Aug 2002 B2
6442433 Linberg Aug 2002 B1
6454705 Cosentino et al. Sep 2002 B1
6471645 Warkentin et al. Oct 2002 B1
6493747 Simmon et al. Dec 2002 B2
6497655 Linberg et al. Dec 2002 B1
6505059 Kollias et al. Jan 2003 B1
6507868 Simmon et al. Jan 2003 B2
6512986 Harmon Jan 2003 B1
6540672 Simonsen et al. Apr 2003 B1
6544173 West et al. Apr 2003 B2
6551276 Mann et al. Apr 2003 B1
6554798 Mann et al. Apr 2003 B1
6558320 Causey, III et al. May 2003 B1
6558321 Burd et al. May 2003 B1
6561978 Conn et al. May 2003 B1
6571294 Simmon et al. May 2003 B2
6577901 Thompson Jun 2003 B2
6579242 Bui et al. Jun 2003 B2
6582366 Porumbescu Jun 2003 B1
6589229 Connelly et al. Jul 2003 B1
6598084 Edwards et al. Jul 2003 B1
6599250 Webb et al. Jul 2003 B2
6604050 Trippel et al. Aug 2003 B2
6612984 Kerr, II Sep 2003 B1
6633772 Ford et al. Oct 2003 B2
6641533 Causey, III et al. Nov 2003 B2
6650951 Jones et al. Nov 2003 B1
6656114 Poulsen Dec 2003 B1
6681003 Linder et al. Jan 2004 B2
6685633 Albert et al. Feb 2004 B2
6694177 Eggers et al. Feb 2004 B2
6705990 Gallant et al. Mar 2004 B1
6723045 Cosentino et al. Apr 2004 B2
6723046 Lichtenstein et al. Apr 2004 B2
6735479 Fabian et al. May 2004 B2
6744350 Blomquist Jun 2004 B2
6755783 Cosentino et al. Jun 2004 B2
6761321 Takahashi Jul 2004 B2
6783492 Dominguez et al. Aug 2004 B2
6804558 Haller et al. Oct 2004 B2
6805667 Christopherson et al. Oct 2004 B2
6820057 Loch et al. Nov 2004 B1
6824512 Warkentin et al. Nov 2004 B2
6968375 Brown Nov 2005 B1
6980958 Surwit et al. Dec 2005 B1
7041468 Drucker et al. May 2006 B2
7291107 Hellwig et al. Nov 2007 B2
7553281 Hellwig et al. Jun 2009 B2
7769600 Iliff Aug 2010 B2
7785313 Mastrototaro Aug 2010 B2
7869851 Hellwig et al. Jan 2011 B2
20010011224 Brown Aug 2001 A1
20010013006 Brown Aug 2001 A1
20010016310 Brown et al. Aug 2001 A1
20010021801 Bardy Sep 2001 A1
20010023315 Flach et al. Sep 2001 A1
20010031997 Lee Oct 2001 A1
20010032278 Brown et al. Oct 2001 A1
20010037060 Thompson et al. Nov 2001 A1
20010039503 Chan et al. Nov 2001 A1
20010047252 Brown Nov 2001 A1
20010049096 Brown Dec 2001 A1
20010051787 Haller et al. Dec 2001 A1
20010056229 Cosentino et al. Dec 2001 A1
20010056328 Trippel et al. Dec 2001 A1
20020010596 Matory Jan 2002 A1
20020013613 Haller et al. Jan 2002 A1
20020013614 Thompson Jan 2002 A1
20020016530 Brown Feb 2002 A1
20020019707 Cohen et al. Feb 2002 A1
20020019748 Brown Feb 2002 A1
20020026223 Riff et al. Feb 2002 A1
20020028989 Pelletier et al. Mar 2002 A1
20020028995 Mault Mar 2002 A1
20020040208 Flaherty et al. Apr 2002 A1
20020045804 Christopherson et al. Apr 2002 A1
20020052539 Haller et al. May 2002 A1
20020065682 Goldenberg May 2002 A1
20020072858 Cheng Jun 2002 A1
20020081559 Brown et al. Jun 2002 A1
20020082665 Haller et al. Jun 2002 A1
20020096543 Juselius Jul 2002 A1
20020099283 Christ et al. Jul 2002 A1
20020107452 Kwong Aug 2002 A1
20020120201 Chio et al. Aug 2002 A1
20020133377 Brown Sep 2002 A1
20020138017 Bui et al. Sep 2002 A1
20020143576 Nolvak et al. Oct 2002 A1
20020156384 Eggers et al. Oct 2002 A1
20020158775 Wallace Oct 2002 A1
20020173704 Schultze et al. Nov 2002 A1
20020183976 Pearce Dec 2002 A1
20020186821 Eggers Dec 2002 A1
20020188477 Ackermann et al. Dec 2002 A1
20020193679 Malave et al. Dec 2002 A1
20020198445 Dominguez et al. Dec 2002 A1
20030003522 Goldman Jan 2003 A1
20030011646 Levine et al. Jan 2003 A1
20030032077 Itoh et al. Feb 2003 A1
20030032867 Crothall et al. Feb 2003 A1
20030032868 Graskov et al. Feb 2003 A1
20030040821 Case Feb 2003 A1
20030040824 Feige et al. Feb 2003 A1
20030041866 Linberg et al. Mar 2003 A1
20030054428 Monfre et al. Mar 2003 A1
20030055606 Christ et al. Mar 2003 A1
20030065536 Hansen et al. Apr 2003 A1
20030069752 LeDain et al. Apr 2003 A1
20030069753 Brown Apr 2003 A1
20030100040 Bonnecaze et al. May 2003 A1
20030105403 Istvan et al. Jun 2003 A1
20030130590 Bui et al. Jul 2003 A1
20030139785 Riff et al. Jul 2003 A1
20030158707 Doi Aug 2003 A1
20030160683 Blomquist Aug 2003 A1
20030163351 Brown et al. Aug 2003 A1
20030176774 Hickle et al. Sep 2003 A1
20030177177 Oka et al. Sep 2003 A1
20030179292 Provost et al. Sep 2003 A1
20030211617 Jones Nov 2003 A1
20030212317 Kovatchev et al. Nov 2003 A1
20030212379 Bylund et al. Nov 2003 A1
20030212579 Brown et al. Nov 2003 A1
20030216628 Bortz et al. Nov 2003 A1
20030229514 Brown Dec 2003 A2
20040006278 Webb et al. Jan 2004 A1
20040015102 Cummings et al. Jan 2004 A1
20040019259 Brown et al. Jan 2004 A1
20040034288 Hennessy et al. Feb 2004 A1
20040039255 Simonsen et al. Feb 2004 A1
20040039261 Bardy Feb 2004 A1
20040039264 Bardy Feb 2004 A1
20040039606 Loch et al. Feb 2004 A1
20040044272 Moerman et al. Mar 2004 A1
20040049355 Maus et al. Mar 2004 A1
20040054263 Moerman et al. Mar 2004 A1
20040054352 Adams et al. Mar 2004 A1
20040059201 Gingsberg Mar 2004 A1
20040059599 McIvor Mar 2004 A1
20040068230 Estes et al. Apr 2004 A1
20040073095 Causey, III et al. Apr 2004 A1
20040077995 Ferek-Petric et al. Apr 2004 A1
20040078065 Kroll Apr 2004 A1
20040078219 Kaylor et al. Apr 2004 A1
20040087845 Katarow et al. May 2004 A1
20040093167 Braig et al. May 2004 A1
20040093239 Ott et al. May 2004 A1
20040102683 Khanuja et al. May 2004 A1
20040102685 Cosentino et al. May 2004 A1
20040106855 Brown Jun 2004 A1
20040107116 Brown Jun 2004 A1
20040116780 Brown Jun 2004 A1
20040117207 Brown Jun 2004 A1
20040117208 Brown Jun 2004 A1
20040117209 Brown Jun 2004 A1
20040117210 Brown Jun 2004 A1
20040122353 Shahmirian et al. Jun 2004 A1
20040122701 Dahlin et al. Jun 2004 A1
20040126832 Wang et al. Jul 2004 A1
20040128162 Schlotterbeck et al. Jul 2004 A1
20040130446 Chen et al. Jul 2004 A1
20040133455 McMahon Jul 2004 A1
20040142403 Hetzel et al. Jul 2004 A1
20040146149 Rogers et al. Jul 2004 A1
20040147034 Gore et al. Jul 2004 A1
20040147979 Bardy Jul 2004 A1
20040148199 Dixon, Jr. Jul 2004 A1
20040152956 Korman Aug 2004 A1
20040158232 Schetky et al. Aug 2004 A1
20040167464 Ireland et al. Aug 2004 A1
20040193377 Brown Sep 2004 A1
20040199221 Fabian et al. Oct 2004 A1
20040199409 Brown Oct 2004 A1
20040210458 Evans et al. Oct 2004 A1
20040215049 Zdeblick et al. Oct 2004 A1
20040215089 Bergelson et al. Oct 2004 A1
20040215490 Duchon et al. Oct 2004 A1
20040219500 Brown et al. Nov 2004 A1
20040225199 Evanyk et al. Nov 2004 A1
20040225533 Cosentino et al. Nov 2004 A1
20040249250 McGee et al. Dec 2004 A1
20040252031 Taylor Dec 2004 A1
20040254434 Goodnow et al. Dec 2004 A1
20040260156 David et al. Dec 2004 A1
20040260189 Eggers et al. Dec 2004 A1
20040260233 Garibotto et al. Dec 2004 A1
20040267100 Faupel et al. Dec 2004 A1
20050017864 Tsoukalis Jan 2005 A1
20050020887 Goldberg Jan 2005 A1
20050021372 Mikkelsen et al. Jan 2005 A1
20050027400 Wang et al. Feb 2005 A1
20050027562 Brown Feb 2005 A1
20050033120 Cohen Feb 2005 A1
20050033127 Ciurezak et al. Feb 2005 A1
20050038674 Braig et al. Feb 2005 A1
20050043965 Heller et al. Feb 2005 A1
20050049464 Lassers et al. Mar 2005 A1
20050054940 Almen Mar 2005 A1
20050055242 Bello et al. Mar 2005 A1
20050059895 Brown Mar 2005 A1
20050060194 Brown Mar 2005 A1
20050065760 Murtfeldt et al. Mar 2005 A1
20050066969 Rick et al. Mar 2005 A1
20050080652 Brown Apr 2005 A1
20050086083 Brown Apr 2005 A1
20050114444 Brown et al. May 2005 A1
20050171503 Van Den Berghe Aug 2005 A1
20050172021 Brown Aug 2005 A1
20050172022 Brown Aug 2005 A1
20050228883 Brown Oct 2005 A1
20050235060 Brown Oct 2005 A1
20050256739 Brown Nov 2005 A1
20050273509 Brown Dec 2005 A1
20060004611 Brown Jan 2006 A1
20060010014 Brown Jan 2006 A1
20060080152 Brown Apr 2006 A1
20060089969 Brown et al. Apr 2006 A1
20060100910 Brown May 2006 A1
Foreign Referenced Citations (4)
Number Date Country
2729715 Jul 1996 FR
06-207685 Jul 1994 JP
08-232660 Sep 1996 JP
10-220633 Aug 1998 JP
Non-Patent Literature Citations (2)
Entry
C. Juhasz, B. Asztalos, B. Lerner and Z. Benyo, “AdASDiM: application of adaptive control technique to diabetic management,” Proceedings of 16th Annual International Conference of the IEEE Engineering in Medicine and Biology Society, 1994, pp. 928-929 vol. 2, doi: 10.1109/IEMBS.1994.415217 (Year: 1994).
International Search Report received for PCT Patent Application No. PCT/JP2002/003516, dated Jul. 30, 2002, 4 pages.
Related Publications (1)
Number Date Country
20190279755 A1 Sep 2019 US
Continuations (1)
Number Date Country
Parent 10311209 Dec 2002 US
Child 16416517 US