Patent Grant
11383043
This disclosure relates to therapy management systems, methods, and devices adapted to collect and/or transmit data relating to therapy (e.g., the timing of therapy) and/or other therapy related data and to provide a user with therapy recommendations. In particular embodiments, diabetes therapy management systems, devices, and methods are disclosed, which may be utilized with insulin injection devices, including components adapted to provide a user with insulin therapy recommendations based on stored therapy parameters, blood glucose data, meal size estimations, and/or other parameters.
Diabetes mellitus is a chronic metabolic disorder caused by the inability of a person's pancreas to produce sufficient amounts of the hormone insulin such that the person's metabolism is unable to provide for the proper absorption of sugar and starch. This failure leads to hyperglycemia, i.e., the presence of an excessive amount of glucose within the blood plasma. Persistent hyperglycemia has been associated with a variety of serious symptoms and life threatening long-term complications such as dehydration, ketoacidosis, diabetic coma, cardiovascular diseases, chronic renal failure, retinal damage and nerve damages with the risk of amputation of extremities. Because healing is not yet possible, a permanent therapy is necessary which provides constant glycemic control in order to constantly maintain the level of blood analyte within normal limits. Such glycemic control is achieved by regularly supplying external drugs to the body of the patient to thereby reduce the elevated levels of blood analyte.
An external biologically effective drug (e.g., insulin or its analog) is commonly administered by means of daily injections. In some cases, multiple, daily injections (MDI) of a mixture of rapid- and long-acting insulin via a reusable transdermal liquid dosing device (commonly referred to as an “insulin pen”) or a hypodermic syringe. The injections are typically administered by a person with diabetes (PWD), and so require self-monitoring of blood glucose and the self-administration of insulin. The PWD that manages their care using MDI often plans insulin injections for each day, in advance, based on basal insulin requirement as well as external factors such as meals, exercise, sleep, etc. A typical dosing plan will include the time of day for an injection, the type of insulin (e.g., fast acting, long acting, a mixture of fast acting and long acting, etc.), and amount of insulin for each dose. In addition, PWDs will self-monitor their blood glucose and self-administer “bolus” dose(s) of rapid-acting insulin if their blood glucose is too high or consume carbohydrates (or sometimes administer glycogen) if their blood glucose is too low.
The “correct” insulin dose is a function of the level of glucose in the blood, physiological factors such as a person's insulin sensitivity, and lifestyle factors such as meals (e.g., recently consumed carbohydrates that have yet to be metabolized into glucose and absorbed into the blood). Moreover, even with careful planning and self-monitoring, a PWD may skip doses, double dose, and dose the wrong amount and/or type of insulin. Insufficient insulin can result in hyperglycemia, and too much insulin can result in hypoglycemia, which can result in clumsiness, trouble talking, confusion, loss of consciousness, seizures, or death. Accordingly, PWDs face a considerable cognitive burden in determining appropriate doses of insulin.
In order to assist with self-treatment, some diabetes treatment devices (e.g., blood glucose meters, insulin pumps, etc.) are equipped with insulin bolus calculators that have the user input an estimate (e.g., numerical estimate) of the quantity of carbohydrates consumed or about to be consumed (or additionally or alternatively protein, fat, or other meal data) and the bolus calculator outputs a recommended size for the insulin bolus dosage. Although bolus calculators remove some of the mental calculations that need to be made by the user in determining an appropriate insulin bolus dosage, bolus calculators still burden the user with the mental task of evaluating the constituents of their meal, may require the use of a secondary device, and often require manual entry of data. Accordingly, there is a need for methods, systems, and devices that assist the user to make appropriate therapy decisions while minimizing the burdens (e.g., data entry, mental calculations, procedures, etc.) on the user.
The present disclosure may be understood more fully by reference to the following detailed description of example embodiments, which are illustrated in the accompanying figures.
Manual insulin delivery devices such as insulin pens, insulin inhalers, etc. (referred to herein, generally, as “manual insulin devices”) provide a convenient, reusable means of delivering insulin. The improper dosing of insulin, however, due to human error, malfunction of an insulin pen, skipping doses, double dosing, and incorrect dosing, is always a concern. Although methods, devices, and systems provided herein are described for the delivery of insulin, collection of blood glucose data, and/or the treatment of diabetes, methods, devices, and systems provided herein may be adapted for the delivery of other medications, the collection of other analyte data, and/or the treatment of other diseases. Additionally, although methods, devices, and systems provided herein are described primarily by describing features and functionalities included in pen cap accessory for insulin delivery pens or methods the use pen cap accessories, or systems including pen cap accessories, the features discussed herein are also contemplated as being incorporated directly into smart medication delivery pens or smart medication delivery inhalers, other accessories adapted to be secured to or used with other manual medication delivery devices, or methods or systems including such smart medication delivery devices or smart accessories.
Systems, devices, and methods described herein may be operated or performed, respectively, by a user for example, a PWD, a patient, a test subject, a healthcare professional, clinician and a caregiver. Unless otherwise stated, the terms health care professional, clinician, and a caregiver are used interchangeably in this disclosure.
In general, the embodiments of therapy management systems (e.g., diabetes management systems such as insulin therapy management systems), methods, and devices described herein may include user interfaces configured to receive user-specific dosage parameters from a user or healthcare professional and use those user-specific dosage parameters to provide recommendations and reports to a user. In some embodiments, a user interface for receiving user-specific dosage parameters may be incorporated into a mobile application or another computing device and a user interface for displaying an immediate medication delivery recommendation may be incorporated into an accessory for a manual medication delivery device or a smart manual medication delivery device. In some cases, a user interface for entering user-specific dosage parameters can additionally be used for viewing reports, recommendations, alarms, alerts, notifications, recommended user-dosage parameter changes.
Systems, devices, and methods provided herein can include a user interface that is adapted to simplify the entry of therapy relevant data to ease the burden of self-treatment. In some embodiments, systems, devices, and methods provided herein are adapted to assist a person with diabetes (PWD) or their caregiver in determining an appropriate dosage of insulin. In some embodiments, methods, devices, and systems provided herein can reduce or eliminate the manual entry of numerical data after an initial setup. In some embodiments, methods, devices, and systems provided herein may be adapted to simplify the monitoring of blood glucose levels. In some embodiments, methods, devices, and systems provided herein can permit a user to discreetly manage their therapy. In some embodiments, methods, devices, and systems provided herein can reduce the cognitive burden associated with making daily therapy decisions.
Systems, devices and methods provided herein can simplify the process for obtaining insulin therapy suggestions and/or simplifying the collection of estimated glucose values (EGVs) and/or insulin delivery data from one or more insulin delivery devices. Systems, devices, and methods provided herein may be designed to minimize the changes that persons with diabetes (PWDs) that administer insulin therapy using injections may be required to make to their therapy/daily routines in order to receive therapy recommendations and/or to receive notifications, alerts, or alarms.
In some embodiments, systems, methods, and devices provided herein can give a user options of when, where, and whether to receive notifications, alerts or alarms, which may be, at least in part, based upon the devices of the system being carried by the user. In some embodiments, the alarms and/or alerts may be customized over time based on feedback from the user (e.g., likes and dislikes from the user). In some embodiments, systems, methods, and devices provided herein can include notifications, alerts, and/or alarms that use a combination of EGV data and insulin delivery data to determine whether to trigger the notification, alert, and/or alarm.
In some embodiments, systems, devices, and methods provided herein can automatically capture insulin delivery data, which may be captured using a connected and/or smart insulin injection pen or a connected and/or smart insulin pen accessory (e.g., a connected pen cap accessory).
In some embodiments, systems, devices, and methods provided herein can recommend insulin doses (e.g., dosages of long-acting and/or rapid-acting insulin) using any suitable technique. In some embodiments, recommended insulin dosages may be based upon blood glucose data (e.g., current EGV from continuous glucose monitor (“CGM”), flash glucose monitor, blood glucose meter, or any other sensor, blood glucose trend data, etc.), insulin administration data (bolus dosage amounts of rapid-acting insulin, dosages of long-acting insulin, dosage times, calculation of Insulin-on-Board (“IOB”) and/or active insulin, etc.), meal data (mealtimes, user estimated carbohydrates, user estimated meal categorizations, user estimated glycemic impact of meal user meal history, user meal trends, etc.), and/or one or more insulin deliver parameters total daily dose of basal insulin or long-acting insulin, carbohydrate-to-insulin ratio (CR), insulin sensitivity factor (ISF), etc.). Methods, devices and systems provided herein can, in some embodiments, adjust insulin delivery parameters over time based on glucose data and/or insulin administration data.
Systems, devices, and methods provided herein can include or use a mobile device (e.g., a mobile application running on a smartphone or tablet) to permit the user to setup the device or system, to check status of the device or system, adjust therapy settings, and/or learn about how to improve their therapy choices. In some embodiments, a mobile device can include information about maintenance tasks (e.g., reminders to conduct certain maintenance tasks). In some embodiments, methods, systems, and devices provided herein can detect patterns in therapy relevant data and use that data to provide a user with tips, suggestions, alerts, and/or alarms based on the patterns, which may be displayed on a mobile device. In some embodiments, a mobile device may provide a user with graphical displays regarding the user's therapy relevant data and/or therapy decisions (e.g., blood glucose data and/or insulin injection times). In some embodiments, a mobile device may provide a user with an indication that the user might want to adjust their therapy (e.g., an amount of insulin for meals, an amount of insulin for the user's basal requirements, a timing of their insulin injections, etc.) and provide the user with a mechanism (e.g., a link) to make adjustments to their therapy. In some embodiments, a mobile device may provide a user with an indication that the system has automatically adjusted their therapy (e.g., an amount of insulin for meals, an amount of insulin for the user's basal requirements, a timing of their insulin injections, etc.) and optionally provide the user with a mechanism (e.g., a link) to reject the automatic adjustment, confirm the automatic adjustment, or make a manual therapy adjustment.
In some embodiments, diabetes management systems, devices, and methods provided herein can include a plurality of meal size categories (e.g., three meal sizes (Small, Medium, Large), time-based meals (Breakfast, Lunch, Dinner, Snack)) that may be set by the user (e.g., on a mobile device). In some embodiments, a mobile device includes a setup user interface where a user is prompted to enter the user's typical insulin dosage for differently sized meals (e.g., a dose for a small meal, a dose for a medium meal, a dose for a large meal). In some embodiments, the setup user interface displays to the user example pictures of meals that would be considered to be within each meal category. In some embodiments, the device may analyze the approximate size of the meal for the user (e.g., by analyzing an input from the user, such as an input relating to characteristics of the meal, a picture of the meal, etc.). In some embodiments, the setup user interface may provide estimates of what the user is expected to enter for each meal size based on the user's entered amount of long-acting insulin (e.g., dosage of LANTUS®).
Systems, devices, and methods provided herein can include, use, or communicate with one or more accessories for a medication delivery device, such as an insulin pen (e.g., a pen cap for the insulin pen) that is (a) adapted to be secured to an injection pen and detect when the pen cap is secured to and/or released from the injection pen, (b) adapted to receive blood glucose data from a glucose sensor, and/or (c) adapted to provide therapy relevant information and/or recommendations to the user.
In some cases, the accessory may be a pen cap accessory adapted to detect pen capping information. Pen capping information (e.g., information about when the pen cap is secured to and/or released from the injection pen) can include information about a current capping period (e.g., the time since the last capping), information about a duration of one or more uncappings (which may also be referred to herein as “decapping(s)”), and the timing (e.g., time-of-day or time elapsed since) of each uncapping and each capping. In some embodiments, pen capping information may be displayed on the pen cap accessory to a user. In some embodiments, pen capping information may be announced by a speaker in the pen cap. For example, in some embodiments, a pen cap may provide a timer clock that counts up from the last time the pen cap was secured to the injection pen. In some embodiments, a pen cap accessory can wirelessly communicate pen capping information to a remote computing device (e.g., a smartphone, tablet, etc.). In some embodiments that do not include pen cap accessories, the accessories or smart delivery devices can detect other events associated with medication delivery actions and use that information in ways that pen capping information is described herein. For example, in some cases an injection pen accessory may be secured to an injection pen such that it can detect the mechanical movement of the dosing mechanism to determine a time of a dose of medication.
Pen capping information may be used to modify the user experience (e.g., the display or information presented to the user). In some embodiments, the pen cap adjusts the presentation of the therapy relevant information and/or recommendations provided to the user based on the pen capping information. For example, in some embodiments, a pen cap may provide bolus recommendations to correct for elevated blood glucose levels based on data from a glucose sensor, but may limit the presentation of such correction bolus recommendations to time periods when the current pen capping duration is greater than a threshold period of time (e.g., at least 2 hours, at least 3 hours, at least 4 hours, or at least 5 hours). In some embodiments, the pen cap may provide notifications, alerts, or alarms to the user based on the pen capping information. For example, if the pen cap is removed from the injection pen within a threshold period of time (e.g., within 30 minutes or 1 hour) from a previous capping, the pen cap may provide a visual, audible, or vibrational notification to indicate that the user may have recently used the pen to administer insulin. In some embodiments, the pen cap may be in wireless communication with a mobile computing device (e.g., a smartphone, tablet) and one or more notifications, alerts, or alarms based on pen capping information may be announced or displayed on the mobile computing device.
Pen capping information may be stored, displayed, and/or analyzed in combination with glucose data to determine user behaviors, such as, for example, whether the person is appropriately dosing insulin for meals and/or to correct elevated blood glucose levels. In some embodiments, pen capping information may be presented on a graphical representation of blood glucose data for the user and presented to a user and/or to a healthcare professional. In some embodiments, blood glucose data from a period of time after each capping event may be evaluated to determine whether the user appropriately dosed insulin for that capping event, e.g., appropriate dose, under dose, or over dose.
In some embodiments, a pen capping event may be disregarded where other information indicates that a dose was not provided. For example, where no change in the dosage selection of the insulin pen (e.g., a dial) was detected, the event may be disregarded. In some embodiments, a pen uncapping and recapping event may be disregarded if the total uncapping time is less than a first threshold (e.g., 4-6 seconds). For example, the threshold may be determined by setting it at an amount of time too short to permit for an injection, but long enough to allow a user to check the end of the pen to see if there is insulin remaining or if there is a needle attached to the pen. In some cases, the total decapping time (the time between an uncapping event and the subsequent recapping) for a decapping event may be analyzed in combination with blood glucose data to determine if there was an injection during that decapping event. In some cases, if the total decapping time exceeds a second threshold period of time (e.g., at least 15 minutes, at least 30 minutes, etc.), blood glucose data may be used to determine an approximate time of an injection.
Accessories provided herein (e.g., pen caps), and associated methods and systems provided herein, may be adapted to obtain blood glucose data for use in providing therapy relevant information and/or therapy recommendations via the accessory (e.g., via a pen cap). In some embodiments, the therapy relevant information displayed on a pen cap accessory can include a current estimated glucose value (EGV) for the user. In some embodiments, the therapy relevant information displayed on the pen cap can include a current blood glucose trend or rate of change indicator (e.g., a trend arrow). In some embodiments, the pen cap can include a recommended dose, which may be based on glucose data or may be based on stored parameters without consideration of the current EGV.
Accessories provided herein (e.g., pen caps) may be adapted to receive blood glucose data from any suitable glucose sensor. In some embodiments, the glucose sensor may be a continuous glucose monitor (CGM), a flash glucose monitor, a blood glucose meter (BGM), or any other suitable sensor. In the case of CGMs and flash glucose monitor, they may be configured to provide glucose data based on interstitial fluid glucose levels of a user, which may be correlated to blood glucose levels. A BGM may be configured to provide blood glucose data, typically based on a blood sample. Accordingly, while the term “blood glucose” may, at times, be used as a general term simply for convenience, the disclosure is not limited to using just blood glucose data, values, levels, etc., but also interstitial fluid glucose levels, as well as any intermediate measurement values.
In some embodiments, the pen cap may automatically receive glucose data from a CGM automatically without user action so long as the pen cap is in range. In some embodiments, the pen cap may be adapted to wirelessly receive current EGVs (and, optionally, prior EGVs) from a flash glucose monitor when the pen cap is positioned in proximity to (e.g., swiped adjacent to) the flash glucose monitor. In some embodiments, EGVs may be obtained via a BGM, which may be in wireless communication with the pen cap or a mobile computing device (which can then transmit the EGV to the pen cap) or may be entered by a user into a remote computing device.
Accessories provided herein (e.g., pen caps), in some embodiments, may be configured to that they only retrieve glucose data upon a user interacting with the pen cap. For example, if a pen cap is adapted to obtain glucose data from a CGM or flash glucose monitor, the pen cap may be designed so that it needs to be swiped near the CGM or flash glucose monitor or may be designed so that it can only retrieve glucose data when a demand is made by the user (e.g., when a button is pressed). In some embodiments, a CGM may be in wireless communication with a mobile computing device (e.g., a smartphone, tablet) and data from the CGM only transferred to the pen cap when a button is pressed on the pen cap.
Accessories (e.g., pen caps) or mobile applications provided herein can, in some embodiments, provide reminders to a user to obtain glucose data. For example, in the case of methods and systems that include a flash glucose monitor, a reminder may be sent to the user to obtain glucose data by swiping the pen cap near the flash glucose monitor. In some embodiments, reminders to obtain glucose data may be timed based on pen capping information. For example, a reminder to obtain blood glucose data may be determined based on a time since the most recent capping (e.g., the current capping duration exceeding a threshold). In some embodiments, the threshold may be set to reduce the likelihood that a dosage of insulin may cause a hypoglycemic event. In some embodiments, a pen cap can wirelessly receive blood glucose data and analyze patterns of the blood glucose data in comparison to pen capping information to determine a likelihood of a future hypoglycemic event or a predicted future blood glucose value. In some embodiments, blood glucose data and pen capping information may be wirelessly transmitted to a remote computing device (e.g., smartphone, tablet, etc.) and analyzed in that remote computing device or in the cloud or other network or device to determine a likelihood of a future hypoglycemic event or a predicted future blood glucose value, which may be used to issue a notification, alert, or alarm and/or to set a reminder to obtain blood glucose data.
Pen caps provided herein can use any suitable technique to obtain pen capping information (e.g., information relating to removal/application of the pen cap during an insulin injection). In some embodiments, pen caps provided herein can include a biasing element, such as, for example, a leaf-spring on the inside of the cap that completes a circuit when the pen cap is secured to the injection pen. In other embodiments, the cap may include a sensor (e.g., an optical sensor, a mechanical sensor, an electronic sensor, a magnetic sensor, etc.) that detects when the cap is applied to and/or removed from the pen.
Accessories (e.g., pen caps), methods, and systems provided herein can use any suitable method for making therapy recommendations. In some embodiments, a user or healthcare professional can set recommended dosage amounts for initiation of the product, set one or more initial carbohydrate-to-insulin ratios, set one or more initial insulin sensitivity factors, create a table of correction doses to be used for a particular range of glucose values, and/or set one or more meal characterizations. For example, in some embodiments a user or healthcare professional may set the initial recommended dose of long-acting insulin and a carbohydrate-to-insulin ratio and an insulin sensitivity factor to be used in determining doses of rapid-acting insulin. In some embodiments, a user or healthcare professional may set typical meal sizes in carbohydrates for breakfast, lunch, and/or dinner. In some embodiments, a user or healthcare professional may set typical meal-based rapid-acting insulin doses for the user for breakfast, lunch, and dinner. In some embodiments, a user or healthcare professional may set characterizations of differently sized meals (small (S), medium (M), large (L)) for different times of day (e.g., 10 g of carbohydrates for S, 25 g for M, and 50 g for L). In some embodiments, blood glucose data and/or pen capping information may be analyzed to make adjustments to a user's dosage parameters and/or the meal-based dosage recommendations. In some embodiments, blood glucose data and/or pen capping information may be analyzed to make suggested changes to a user's dosage parameters and/or the meal-based dosage recommendations to a healthcare professional or to a user.
In some embodiments, accessories provided herein (e.g., pen caps) may provide meal-based bolus recommendations based on a time of day and/or meal categories. For example, in some embodiments, the pen cap may provide different meal-based bolus recommendations based on it being breakfast time (e.g., about 8 am), lunch time (e.g., about noon), or dinner time (e.g., about 6 pm). In some embodiments, the pen cap may provide different meal-based bolus recommendations for different meal categories, meal preferences, or historical meal statistics, such as, for example, small (S), medium (M), and large (L), which may be based on the number of carbohydrates or the glycemic impact of a meal as estimated or determined by a user. For example, for each therapy recommendation, a user may see a recommended meal-based bolus for a S meal, for a M meal, and for a L meal. In some embodiments, a user may press a button or user-selectable icon to request a recommendation for a S meal, for a M meal, or for a L meal. In some cases, the meal-based bolus recommendations for each meal category (S, M, and L) can change based on the time of day. In some embodiments, the meal-based bolus recommendations for each meal category (S, M, and L) may change based on a historical evaluation of the user's meal sizes and/or consistency. In some embodiments, a single display can indicate different suggested insulin dosages based on different meal characteristics and/or display a range of dosages based on the user's typical meal sizes (e.g., customized to the user's meal sizes based on historical data), which may be based on the time of the day, day of the week, day of the year, location of user, or any other collected data.
In some embodiments, a system provided herein can include one, two, or more connected pen caps for insulin pens or other accessories for an insulin pen (e.g., a connected dose-capture insulin pen cap), a continuous glucose monitoring system (CGM) (or a flash glucose monitoring system), a mobile application, an alert accessory, and/or critical web services cloud software. In some embodiments, connectivity to the cloud-based server can enable the storage of data for use by the system when needed and transfer of information to other devices outside of the system (e.g., optional secondary display of data, reports). In some embodiments, components of systems provided herein may be wirelessly connected or can wirelessly connect using either Bluetooth Low Energy (BLE), 433 MHZ ultra high frequency (UHF) radio, and/or a near-field communication (NFC) protocol.
One or more embodiments of the present disclosure may include an insulin delivery system that includes an insulin delivery device, a user interface on the insulin delivery device or adapted to be secured (either releasably or non-releasably) to the insulin delivery device, memory to store one or more user-specific dosage parameters, and one or more processors in communication with the memory and adapted to receive blood glucose data, determine a recommended insulin dosage, and/or determine an estimate of insulin administered using the insulin delivery device. The user interface can display one or more recommended insulin dosages using, at least in part, blood glucose data and/or previous estimates of insulin administered, data about prior insulin dosages (e.g., IOB characteristics associated with each of the user-selectable icons or buttons based on at least one of the user-specific dosage parameters. The processor may be adapted to update the meal characteristics associated with each of the user-selectable icons or buttons based upon the blood glucose data.
In accordance with one or more devices, systems, or methods of the present disclosure, the systems or methods may include a glucose monitor that may provide blood glucose data via one or more communication (e.g., wireless communication) techniques. In some embodiments, a glucose monitor of systems or methods provided herein can use multiple wireless communication techniques to transmit blood glucose data. For example, a glucose monitor can include a flash near field communication circuit and a wireless radio. In some embodiments, systems and methods provided herein can have one or more insulin pens or pen accessories receive blood glucose data from a glucose monitor via a first communication technique (e.g., NFC) and have another device (e.g., a mobile device) receive data from the glucose monitor and/or the insulin pens via a second communication technique (e.g., BLE or UHF). In some embodiments, smart pen or pen accessories in methods and systems provided herein may communicate with a continuous and/or glucose monitor of methods and systems provided herein only within a first range and the mobile device may be adapted to passively receive data whenever within a second range that is larger than the first range. In some embodiments, smart pens or pen accessories provided herein may be configured so that the smart pen or pen accessories only receive data when the user elects to take action to receive data (e.g., push a “wake up” button and/or bring the pen or pen accessory within a close proximity to the glucose monitor), but another device (e.g., an associated mobile device) may be adapted to passively receive data regardless of user action if within a range determined by the communication method or link.
In accordance with one or more devices, systems, or methods of the present disclosure, a user interface on the smart insulin delivery device or accessory therefore can include one or more user-selectable buttons or icons. In some embodiments, a user-selectable button or icon may be used to wake up the smart pen or pen accessory to receive blood glucose data from a blood glucose monitoring/sensor system (e.g., that includes a CGM, BGM, flash glucose monitor, etc.). In some embodiments, a user-selectable button or icon may be used to wake up a display on the smart pen or pen accessory to display a recommended insulin dosage amount for the insulin in the smart pen or in an insulin pen secured to the pen accessory. In some embodiments, a user-selectable button or icon may be used to toggle the display between different displays. In some embodiments, a single user-selectable button or icon may be used to wake up the smart pen or pen accessory to receive blood glucose data and to wake up the display, which can then display a recommended insulin dosage upon the smart pen or pen accessory that receives the blood glucose data. In accordance with one or more devices, systems, or methods of the present disclosure, the processor may determine a dosage recommendation of rapid-acting insulin based on factors selected from the number of carbohydrates divided by the PWD's carbohydrate-to-insulin ratio, a difference between the current blood glucose level and a target blood glucose level divided by the PWD's insulin sensitivity factor, a reading from a blood glucose meter (BGM), data from a continuous glucose monitor (CGM), blood glucose trend data, Insulin-on-Board (IOB) data, Carbohydrates on Board (COB) data, whether the PWD is exercising or plans to exercise, whether the PWD is sick, whether the PWD is pregnant, whether the PWD is experiencing menses, and whether the PWD has consumed certain medications.
In some embodiments, a reusable smart pent that may include a dosing detector, a reusable chamber one or more types of insulin cartridges, and a manual delivery mechanism. The detector may be configured to detect first insulin delivery events associated with a manual delivery mechanism.
System Architecture for Therapy Management System
While aspects of the embodiments of the disclosure are described in terms of accessories and caps, one of ordinary skill in the art would understand that many of the features could be performed in an electronics package (i.e., a smart electronics) that is integratable with an insulin delivery device, attachable to an insulin delivery device, attachable to an insulin container, and more, all of which are specifically contemplated by the inventors of this disclosure.
The first accessory 102 and second accessory 103 may be configured to capture information related to the delivery of insulin by manual delivery device 106 and manual delivery device 107, and, in various embodiments, may include internal sensors for dose capture; user interfaces for displaying information and receiving user input; and other interfaces for wireless or wired communication with one or more of the manual delivery device 106, manual delivery device 107, mobile application 104, the analyte sensor system 101, and mobile application 104.
The mobile application 104 may execute on any suitable mobile computing device that can store and execute a mobile application that is adapted to display and input therapy relevant information wirelessly received from the other components of the system as well as from a graphical user interface that enables user to interact with the application. In one embodiment, the mobile device can also store and execute a trusted mobile application within a trusted execution environment (hardware and/or software) that is not, generally speaking, accessible to users or devices communicating with the mobile device 140 but that is accessible to other applications executing on the mobile device 140. Various functions and calculations that relate to the therapy management system, including the alerts and recommendations that are presented to users may be, in part or in whole, performed by the trusted mobile application. Moreover, some or all communication with insulin pens, pen caps, glucose sensors, and other accessories may be restricted to the trusted mobile application.
Generally, the embodiments of the disclosure may use any suitable wireless communication protocol for communication among accessories, manual delivery devices, glucose sensors, and mobile devices. Examples of suitable wireless communication protocols include near-field-communication (ISO/IEC 14443 and 18092 compliant technology), wireless modems and routers (IEEE 802.11 compliant technology), and Bluetooth®/Bluetooth Low Energy (BLE) (IEEE 802.15 compliant technology).
The glucose sensor system 101 may be any suitable glucose sensor system 101, such as a blood glucose meter (BGM) adapted to determine blood glucose values using blood glucose test strips, and flash glucose monitor, or a continuous glucose monitor (CGM). In some cases, a glucose sensor system 101 can act as both a flash glucose monitor and a continuous glucose monitor by permitting both intermittent and on-demand transmissions of blood glucose data. In some embodiments, the glucose sensor system 101 can wirelessly transmit data when interrogated by a reader device (e.g., using NFC communication). In some embodiments, the glucose sensor can wirelessly transmit data at predetermined intervals (e.g., using radio frequencies) using any suitable communication standard (e.g., Bluetooth Low Energy (BLE)). In some cases, systems and methods provided herein can include multiple glucose sensor systems (e.g., a continuous or flash glucose monitor and a blood glucose meter).
In some embodiments, an accessory may be associated with a particular type of insulin, for example, the first accessory 102 is associated with long-acting insulin delivery and the second accessory 103 is associated with rapid-acting insulin delivery.
In some embodiments, the glucose sensor system 101 can transmit glucose data using multiple communication techniques. In some embodiments, the mobile application 104 and/or one or more of the manual delivery device 106, 107 or accessories 102, 103 may include an NFC reader adapted to obtain blood glucose data from the glucose sensor system 101 when brought within an interrogation distance of the glucose sensor system 101. In some embodiments, the mobile application 104 and/or one or more of the manual delivery device 106, 107 or accessories 102, 103 may wirelessly receive blood glucose data from the glucose sensor system 101 that is broadcast at predetermined periods of time (e.g., every 30 seconds, every minute, every 2 minutes, every 3 minutes, every 5 minutes, every 10 minutes, every 15 minutes, etc.).
In a polled (or interrogated) mode of operation, the glucose sensor system 101 may wirelessly send blood glucose data to one or more of the accessories 102, 103 and the mobile application 104, that corresponds to a historical period. For example, when the first accessory 102 interrogates the glucose sensor system 101 it may receive stored glucose data from the previous 1 hour, 2 hours, 3, hours, 4 hours, 5 hours, 6 hours, 7 hours, 8 hours, etc. In some cases, broadcast blood glucose data may only include a current or more recent blood glucose value. For example, in some cases blood glucose data received on the mobile application 104 received directly from the glucose sensor system 101 may include only the most current readings (e.g., from the last 10 minutes), which may be used by the mobile application 104 to issue alarms or alerts based on the most current blood glucose data.
Accessories 102, 103 can include one or more processors and memory for controlling wireless communications, controlling interfaces for wireless communication, controlling a user interface, and/or determining therapy recommendations.
In some embodiments, an application running at the accessories 102, 103 may execute one or more algorithms to determine estimated glucose values (EGVs) from raw glucose sensor data. In some embodiments, a glucose sensor system 101 can transmit EGVs to an accessory. In some embodiments, accessories and/or smart electronics provided herein can include memory that stores user-specific dosage parameters (e.g., a recommended daily dose of long-acting insulin or total daily basal dose (TDBD), insulin sensitivity factor (ISF), carbohydrate-to-insulin ratio (CR), correction amounts based on blood glucose level ranges, total daily insulin dose (TDD), target glucose value, recommended rapid-acting doses for different meal sizes or categories, etc.). In some embodiments, user-specific dosage parameters may be time or day dependent, such as CR and ISF values that depend on the hour of the day. In some embodiments, accessories 102, 103 provided herein can have memory that stores recommended doses of rapid-acting insulin for different meals or for different meal categories. In some embodiments, user-specific dosage parameters and/or different recommended doses for different meals may be updated via mobile application 104 in wireless communication with an accessory. For example, an algorithm in the mobile computing device or in the cloud can update these parameters or recommended doses. In some embodiments, parameters or recommended doses may be updated by a healthcare professional or manually by the PWD or a caregiver. In some embodiments, the accessory can include an algorithm in memory to be executed by a processor to automatically update the user-specific dosage parameters or recommended doses.
Accessories 102, 103 provided herein can, in some embodiments, display or otherwise provide notice to a user of a current blood glucose level and/or blood glucose trend data (e.g., a rate of change) based on glucose data received from the glucose sensor system 101 Accessories 102, 103 (or other smart electronics) provided herein may provide recommended doses of insulin based on one or more of blood glucose data, user-specific dosage parameters, recommended dosage amounts set by a user or healthcare professional, time-of-day, meal data or categorizations, or any other suitable input.
While system 10 is described with two accessories 102, 103, it is not limited and may include more or fewer accessories. For example, first accessory 102 may include a pairing or discoverable mode where it broadcasts information that is discoverable by mobile application 104. The broadcast may be according to a BLUETOOTH beacon or other suitable communication protocol. Responsive to pairing confirmation such as holding the first accessory 102 and mobile device hosting the mobile application 104 close together or depressing a button for sufficient time either at the first accessory 102 or mobile application 104, the mobile application 104 may create a profile for a manual delivery device that is associated with the first accessory 102. In one embodiment, the first accessory 102 may be specifically calibrated for a specific type of manual delivery device and may provide a delivery device type identifier to the mobile application 104. In another embodiment, when the first accessory 102 and mobile application 104 are paired, setup information may be provided at the mobile application 104 or at the interface of the accessory.
In one embodiment, pairing may also involve sharing encryption keys that the devices may use to decrypt/authenticate messages from devices within the system 10.
Each accessory that is paired with the system 10 may have a profile created by the mobile application 104. In one embodiment, the mobile application 104 may query web services 105 for whether a profile for a device already exists for a user, and, if it does, request that it be sent. This enables the mobile application 104 to avoid reduplicating setup as well as may make available to the recommendation algorithms running at the mobile application 104 more historical data or physiological attributes of the user (e.g., insulin sensitivity) that have been refined by actual glucose measurements and blood glucose response analysis.
Upon creating the profile, the mobile application 104 may save insulin therapy related settings with the profile. The insulin therapy related settings may include user-specific dosage parameters for a user, delivery characteristics of the device, specific techniques that may be used to determine recommendations.
In one embodiment, each manual delivery device profile may include, or be part of a user profile that includes, pre-configured correction doses for particular blood glucose ranges. In one embodiment, the pre-configured doses may be entered at the mobile application 104. In another embodiment the pre-configured doses may be entered at one of the web services 105 (e.g., by a healthcare provider or parent), and downloaded to the mobile application 104.
As will be described in more detail below, in one embodiment, a user may select from among the available doses and the system will monitor for dosing actions at an associated manual delivery device. As described more fully herein, dosing actions may be specifically detected (e.g., by detecting medication exiting a needle of a delivery device) or inferred (e.g., using capping information). In some cases, the correction doses may not be available for a limited period of time after insulin dose or detected possible dose. For example, methods, systems, and devices provided herein may be able to detect a dose or possible dose, but not be able to determine a dose amount, thus such systems, methods, and devices may not be able to determine an amount of active insulin (e.g., IOB) remaining in the user, thus such systems may prevent the calculation or suggestion of a correction does for a certain period of time (e.g., at least 2 hours, at least 3 hours, at least 4 hours, or at least 5 hours) after a prior detected dose or detected possible dose of rapid-acting insulin.
Since, meal dose recommendations may be calculated for a manual delivery device that has rapid-acting insulin, a profile may also include or refer to algorithms for calculating meal doses for offsetting the effects on blood glucose levels of small, medium, or large meals. In one embodiment, the algorithms may be personalized to a user, initially, with physiological information about the user, and over time, personalized using actual glucose sensor data and dosing event information.
The mobile application 104 is configured to record historical therapy related information, for example, a history of blood glucose levels, dosing amounts, dosed medication, and dosing timing information.
The system 10 is also configured such that an accessory may be removed. For example, at a setup screen of the mobile application 104 a user may select a manual delivery device 107 to be removed/unpaired from the system 10. Responsive to a selection, the manual delivery device 107 may initiate a confirmation prompt to the user. In one embodiment, a confirmation process involving a specific user action (e.g., holding down a button at a mobile device and a button at the accessory 4) may be used to confirm the removal. Responsive to the confirmation the device profile may be stored and the second accessory 103 may change to an unaffiliated state and power down.
The system 10 is also configured to add and remove glucose sensor system 101, and other glucose monitoring devices configured to send blood glucose data. For example, and as described below, swiping or waving second accessory 103 within proximity of glucose sensor system 101 may activate a communication link between second accessory 103 and the glucose sensor system 101. In one embodiment, the communication link may be initiated according to a near-field-communication (NFC) protocol where an antenna and reader IC at the accessory interrogates a tag (typically a chip) at the glucose sensor system 101. Affiliation/activation data may be shared among the system so that other devices (accessories, mobile devices, etc.) may access the blood glucose data at the glucose sensor system 101.
Background Activity and Sync
The following activities may be carried out in the background when the necessary devices are available and online. These activities are described in the following workflow and may vary based on system status. For the following description, the first accessory 102 is associated with long acting insulin delivery and the second accessory 103 is associated with rapid-acting insulin delivery.
Program Execution on First Accessory Associated with Long-Acting Insulin Delivery
In one embodiment, the first accessory 102, or a device in communication with the first accessory 102, may execute software to calculate a user's required long-acting insulin dose. In one embodiment glucose measurement values are sent to a long acting insulin dose recommendation service hosted in the cloud. In various embodiments, the glucose values may be sent to the cloud services (e.g., via a wireless or cellular connection) at regular intervals such that updates to the therapy parameters may be made, as described in the workflow above. In one embodiment the pen cap 112 may include wireless or cellular equipment and may send the glucose values to the cloud service via wireless or cellular connection. In another embodiment, the first accessory 102 may piggyback on the wireless or cellular connection of a mobile device at which the mobile application 104 executes. The first accessory 102 periodically backs up data to the cloud via the mobile application 104 (e.g., via a local connection, such as a BLUETOOTH® or BLE connection).
The first accessory 102 may receive updated therapy parameters back from the cloud or web services 105 when they are approved and available. Data flow examples are described, below.
Program Execution on a Second Accessory Associated with Rapid-Acting Insulin Delivery
In one embodiment, the second accessory 103 associated with rapid acting insulin delivery, or a device in communication with the second accessory 103, executes the software containing the algorithm to calculate the user's required rapid-acting insulin dose. Glucose values and meal choices may also be sent to a rapid-acting insulin dose recommendation service as well as (e.g., via a wireless or cellular connection) at regular intervals such that calculations may be made as described in the workflow above. In one embodiment the second accessory 103 may include wireless or cellular equipment and may send the glucose values to the cloud service via wireless or cellular connection. In another embodiment, second accessory 103 may piggyback on the wireless or cellular connection of a mobile device having the mobile application 104 installed and executing thereon. The second accessory 103 periodically backs up data to the cloud via the mobile application 104 (e.g., via a local connection, such as a BLUETOOTH® or BLE connection).
The second accessory 103 receives updated therapy parameters back from the cloud services when they are approved and available. This flow of data is discussed in a later section.
Program Execution on Mobile App
The mobile application 104 may run in the background to sync with BLE devices (e.g., first accessory 102 and second accessory 103, glucose sensor system 101) and the cloud to act as a conduit of information. Information is synced regularly per the descriptions above. Additionally, system status configuration, dose history, and glucose trends and forecasting may be viewed as they are calculated in the cloud and pushed to the mobile application 104.
Updating Therapy Parameters
As shown in
In some cases, a portal may alert an HCP that a new set of parameters is ready for review. The clinician may then review the values and either approve or reject them. If rejected, the cloud service is notified and no other action occurs.
If accepted, the cloud or web service 105 is notified and the values (e.g., the updated parameters) are pushed to the user's mobile application 104 for acceptance (e.g., via one of the local devices of the system, such as the accessories 102, 103, and/or the mobile application running on a mobile device). For example, the values may be transmitted to the mobile application, which then communicates the values locally to one or both of the accessories 102, 103.
In some cases, an algorithm can determine if an update is suggested and send a notice to the user that suggests that the user update the user's therapy parameters (perhaps in consultation with the user's doctor).
Pen Cap and Insulin Pen System Architecture
During use, insulin therapy management system 10 may assist a PWD (or their caregiver) responsible for determining when to inject insulin and how much insulin to inject. System 10 may be configured to provide recommendations to assist the PWD (or caregiver) in determining an appropriate insulin dose based on current data from the glucose sensor, based on stored therapy parameters, and/or based on data about insulin injections. In some embodiments, the accessories 102, 103 are configured to collect and provide data about insulin injection events.
In one embodiment the manual delivery devices 106 and 107 shown in
By way of example, manual delivery device 107 may be a long-acting insulin injection pen 110, and manual delivery device 106 may be a rapid-acting insulin injection pen 120 as shown in
The insulin pens 110, 120 may include dials (not shown) that may be used to configure the pens to inject a dose of insulin that corresponds to the dial turn. In some embodiments, each insulin injection pen may be a reusable insulin pen that includes a display or audio and/or input devices such as those disclosed for the pen caps disclosed herein. One example of a reusable insulin pen is an insulin pen that includes a chamber for unloading depleted insulin cartridges and loading new insulin cartridges. The insulin pens 110, 120 may include interfaces for wireless and/or wired communication with one or more of the pen caps, glucose sensor, mobile devices, and other accessories.
Pen capping information (i.e., information about when the pen cap is secured to and/or released from an insulin pen—also referred to herein as “capping” and “uncapping” respectively) can include information about a current capping period (e.g., the time since the last capping), information about a duration of one or more uncapping, and the timing (e.g., time-of-day or time elapsed since) of each uncapping and each capping. In some embodiments, pen capping information may be displayed at an interface of a pen cap to a user. In some embodiments, pen capping information may be announced by a speaker in the pen cap. For example, in some embodiments, a pen cap may provide a timer clock that counts up (or a timer that counts down) from the last time the pen cap was secured to an injection pen. In some embodiments, a pen cap can wirelessly communicate pen capping information to mobile device 140 (e.g., a smartphone, tablet, etc. running a mobile application).
Pen capping information may be used to adjust the user experience. In some embodiments, the pen cap adjusts the presentation of therapy relevant information and/or recommendations provided to the user responsive to the pen capping information. For example, in some embodiments, a pen cap may provide bolus recommendations to correct for elevated glucose levels based on data from a CGM 130, but may limit the presentation of such correction bolus recommendations to time periods when the current pen capping duration is greater than a threshold period of time (e.g., at least 3 hours, at least 4 hours, or at least 5 hours). In some embodiments, the pen caps 112 and 122 may provide notifications, alerts, and/or alarms to the user based on the pen capping information (e.g., based on the amount of time that a pen has been capped and/or uncapped). For example, if the pen caps 112 and 122 are removed from an injection pen within a threshold period of time (e.g., within 30 minutes or 1 hour for a rapid-acting insulin, within 6-12 hours for a long-acting insulin) from a previous capping, the pen cap may provide a visual, audible, and/or tactile notification to indicate that the user may have recently used the pen to administer insulin. In some embodiments, the pen caps 112 and 122 may be in wireless communication with a mobile device 140 and one or more notifications, alerts, and/or alarms based on pen capping information may be announced or displayed on the mobile computing device.
A capping sensor for detecting possible capping events, uncapping events, and recapping events may be an analog or digital electronic sensor integrated with a pen cap, or, more generally, with an accessory, that responds to being attached or removed from an insulin pen. In one embodiment, it may incorporate a piezoelectric material that generates a small current when pressure (e.g., from being firmly affixed to an insulin pen) is exerted on it. In another embodiment, it may respond to relative motion between itself and a small magnetic element affixed to the medical delivery device. In yet another embodiment, it may respond to an open and closed circuit (e.g., open loop when cap off, closed when cap is on). Any suitable sensor for detecting capping and uncapping may be used.
Capping/Uncapping Events and Dosing Events
Pen capping information may be stored, displayed, and analyzed in combination with glucose data to determine user behaviors, such as whether the person is appropriately dosing insulin for meals and/or to correct elevated blood glucose levels. In some embodiments, pen capping information may be presented on a graphical representation of blood glucose data for the user and presented to a user and/or to a healthcare professional. In some embodiments, blood glucose data from a period of time after each capping event may be evaluated to determine whether the user appropriately dosed insulin for that capping event, under-dosed, or over-dosed.
In some embodiments, a pen uncapping event, pen capping event, or pen recapping event may be disregarded where other information indicates that a dose was not provided. For example, where no change in the dosage selection of the insulin pen (e.g., a dial) was detected, the event may be disregarded.
In one embodiment, pen caps 112, 122 may be configured to track pen capping events that may be used to infer dosing actions. In various embodiments, the systems 11 and/or 12 may be configured to infer that a capping event corresponds to a dosing action and record it (e.g., as a dosing event), including one or more of the time, type of insulin, and amount of insulin delivered. In one embodiment, the amount of insulin delivered may be captured at the insulin pens 110, 120 and provided to the pen caps 112 and 122. In some embodiments, pen caps 112, 122 can determine and track remaining insulin in the insulin pens 110, 120 based on the amount of each dose. In another embodiment, the pen caps 112, 122 may track the amount of insulin that remains in an insulin cartridge and determine an amount of insulin associated with a dosing action based on a change of the amount of insulin in an insulin cartridge. In additional embodiments, smart pens or pen accessories can detect the dosages set or administered using other suitable techniques.
In some embodiments, the pen caps 112, 122 may include one or more of smart sensors to detect a substance on a user's fingers, sensors, such as a temperature sensor to determine (e.g., along with blood glucose data) if the insulin needs to be replaced or has gone bad, a touch screen, and a capacitive touch button. For example, one or more of the mobile application or the pen caps 112, 122 may include a temperature monitor that monitors one of more of average temperatures, high temperatures, or low temperatures experiences by the pens caps 112, 122. Such temperature ranges and/or minimum and maximums may be attributed to the therapy (e.g., insulin) attached to the pen caps 112, 122. Upon exposure to a minimum and/or maximum temperature (e.g., or a selected time period within a selected temperature range), the pen caps 112, 122 may provide an alert and/or alarm to the user that the insulin has been exposed to an out of range temperature (e.g., a level beyond recommendations for user and/or storage of the insulin).
In some embodiments, such a temperature sensor may be used in unison with the blood glucose sensor to indicate, where the insulin has been exposed to a select temperature level, that the insulin is not having an expected effect on the subject's blood glucose level. For example, an alarm and/or alert may be provided where the insulin has been exposed to an out of range temperature and where data from the blood glucose monitor data is indicating that the insulin is not having an expected effect on the subject's blood glucose levels (e.g., less than or more than an expected change). In some cases, methods, systems, and devices provided herein can condition notifications regarding temperature exposure based on additional data that indicates that the effectiveness of the insulin has been compromised or may have been compromised in order to mitigate against the user experiencing notification fatigue. In some embodiments, the mobile application or the pen caps 112, 122 may trigger a reminder for the user to make a post-injection reading to determine the effectiveness of the insulin that was recently provided to the subject.
In some embodiments, the mobile application or the pen caps 112, 122 may communicate with a wearable device on the PWD (e.g., a smartwatch) to determine an action being undertaken by the subject (e.g., if the subject is eating). For example, a wearable application may execute on the wearable device that enables a user to interface with one or more of the pen caps 112, 122, the insulin pens 110, 120, the mobile device 140, and other accessories. In some embodiments, the wearable application may interface with a mobile application executing on the mobile device 140, such as mobile application 104. The mobile application may perform the processing for various features described herein, and the wearable application may serve the alerts and recommendations to a user as well as serve information to the mobile application received from the user at the wearable device, such as indications of a meal, exercise, or dosing action.
Swiping/Gathering Glucose Information
Delivery Recommendations for Rapid Acting
In one embodiment, system 11 and/or system 12 may be configured to provide a correction dose recommendation and present the recommendation at a user interface. Turning to
A recommended correction dose may only be valid for a set period of time, for example, because blood glucose levels change due to factors such as basal metabolism, meals, and exercise. In one embodiment, the pen cap 122 may be configured to display a recommended correction dose for a set period of time (e.g., a period of time from the last scanning event as shown in
In one embodiment, responsive to expiration of the timer, the display 124 on the pen cap 122 may instruct the user that a new blood glucose reading is needed before an updated recommendation may be made based on the blood glucose data. In some cases, a pen cap that does not have current blood glucose data may provide recommendations based on the meal sizes alone, but may optionally additionally include an indication that the recommendation does not include a correction component.
In one embodiment, a correction dose may only be displayed if a current blood glucose value is available (for example, a valid blood glucose value from the previous 10 minutes, from the previous 15 minutes, or from the previous 30 minutes). If no valid blood glucose value is available, a message may be displayed to a user that a current blood glucose value is needed.
In some embodiments, pen caps 112 may refuse to provide a correction dose for a predetermined period of time after a prior dose and/or for a period of time after a prior dose based on a determination of an amount of active insulin (e.g., IOB) in the PWD. In some cases, correction doses may be adjusted based on an estimation of active insulin (e.g., an IOB estimate). In some cases an IOB may not be known, but an estimated percentage of the prior dose remaining active maybe be determined and displayed to a user. In some cases, a correction dose calculation may be reduced based on an estimated percentage of active insulin remaining being within a predetermined range (e.g., active insulin remaining being determined to be between 5% and 25% results in a 25-75% reduction in correction doses recommended). For example, the pen caps 112 may continue to increase a recommended correction dose over time between hours 2 and 4 after a prior dose based on estimated active insulin percentage in the subject.
Alarms/Alerts Thresholds on Dosing Actions
In some embodiments, if pen cap 122 has identified other recent doses (e.g., by detecting a capping action of the pen cap within the last 3 hours, the last 4 hours, or last 5 hours) without knowing the amount of the dose, the pen cap might refuse (e.g., initially refuse, with an optional override) to add a correction component in order to prevent the unintentional stacking of correction boluses. In some embodiments, meal icons 126a-126c can indicate whether the recommendation includes a correction component or not. In some embodiments, additional icons or displays can indicate if there is a recommended correction dose included and/or the size of the recommended correction dose. In some embodiments, by pushing button 123, the user can obtain a screen that displays the current blood glucose value, trend information (e.g., a trend arrow), and a recommended correction dose. In some embodiments, if there has been a recent dosage of insulin (e.g., within the last 1, 2, 3, or 4 hours) a warning screen might appear next to or over the recommendation to indicate that there has been a recent dose in order to prevent unintentional stacking of insulin. In some embodiments, a notice icon 128 can appear on pen cap 122 in order to indicate to the user that a more detailed suggestion, tip, alert, or alarm is available for the user in the mobile application on the mobile device 140.
Recommendation Specific to Long Acting Insulin Delivery
In some embodiments, if the user has recently uncapped pen cap 112 from pen 110, the display can depict information about when the pen cap 112 was uncapped or other warnings to prevent the unintentional double delivery of long-acting insulin. In some embodiments, pen cap 112 may provide a notice sound to indicate to a user that it is time to deliver the long-acting insulin based on stored therapy parameters. In some cases, methods, devices, and systems may provide an alarm, alert, or notification to a user (e.g., via a pen cap or via a mobile app) if the user has not taken a dose within a certain threshold period of time of a schedule dose time (i.e., a “missed dose”). In some embodiments, a suitable therapy titration algorithm may suggest that a user change the stored therapy parameters and/or automatically update the stored therapy parameters relevant to the dosing of long-acting insulin.
In some embodiments, long-acting insulin pen cap 112 may infer dosing actions using pen capping information. If a dosing action is not inferred for a certain time or within a certain time range, then pen cap 112 may detect a missed dose of long acting insulin. A missed dose alarm, alert, and/or notification to a user may be generated and provided to a user. A missed dose notification may include information about the missed dose, including an expected time and an expected amount of long acting insulin to be delivered.
In some embodiments, a time threshold parameter may be provided that defines a period of time since a last inferred dosing action. The time threshold parameter may be configurable, so a user may set different time periods (e.g., values may be entered by a user or selected from among a list of recommended time periods in a setup screen). If a time since a last inferred dosing action exceeds a time threshold parameter then a missed dose may be inferred and a missed dose alarm, alert, and/or notification may be generated and provided to a user.
In some embodiments, pen cap 112 can interrogate glucose monitor 130 to receive glucose data and/or receive blood glucose data via the mobile device 140 and/or pen cap 122. In some embodiments, display 114 can depict recent blood glucose data, the time of that data, and/or glucose trend data (e.g., a trend arrow). In some cases, pen cap 122 may be adapted so that it does not display a current blood glucose level in order to avoid a user confusing rapid-acting pen cap 122 with long-acting pen cap 112. In some embodiments, display 114 may include a recommended dose of long-acting insulin 117. In some cases, if a correction dose is needed, pen cap 112 may indicate that the user should also deliver a correction dose of rapid-acting insulin using pen 120.
Therapy Relevant Information
In some embodiments, one or more of the pen caps 112, 122 may track and display the estimated percentage of an administered dose over time. For example, the pen caps 112, 122 may track an estimated percentage of active insulin (e.g., IOB) remaining in a subject over time after each dose has been administered. In some cases, an IOB percentage left indicator may be displayed based on the time of the most recent capping (e.g., immediately after capping an IOB percentage left indicator may indicate that the IOB remaining is 100%, but then be reduced over time after the last capping until it hits zero). In some cases, pen cap 112 can include a rapid-acting insulin active percentage calculation, which may decay over a 3-6 hour period. In some cases, pen cap 122 can include a long-acting insulin active percentage calculation, which may decay over a 12-36 hour period. In some cases, a pen cap adapted for an intermediate-acting insulin may determine a percentage of active intermediate insulin, which may decay over a 6-12 hour period. In some cases, pen caps 112 and/or 122 may be adapted to determine an amount of insulin remaining in an insulin injection pen and thus determine dosage amounts and display a real-time estimation of active insulin as a number of units of insulin for each type of insulin.
Example System Architecture
In some embodiments, initial therapy parameters may be programmed into the mobile application on mobile device 140 and transmitted to the pen caps 112 and 122 via BLE communication links 211 and 221. In some embodiments, pen cap 122 can use therapy parameters received from the mobile app to recommend correction doses and meal doses. In some embodiments, the therapy parameters can include meal doses for differently sized meals (e.g., small meal, medium meal, and large meal). In some embodiments, the therapy parameters can include a therapy parameter for correcting glucose values, such as an insulin sensitivity factor. In some embodiments, the correction may be based on a linear sliding scale correction, such as discussed below. In some embodiments, pen cap 112 can receive a therapy parameter indicating a daily amount of long-acting insulin. In some embodiments, pen cap 112 can receive recommended times for dosing long-acting insulin from the mobile application of mobile device 140 (e.g., every day at 9 p.m., every day at 8 a.m., twice a day at 8 a.m. and 8 p.m., etc.).
Delivering a Rapid-Acting Insulin Dose
When the user decides to deliver a rapid-acting insulin dose (for example, before a meal), the system can initiate the following workflow. Some of the acts are optional and may not be invoked if particular devices are unavailable or if the user chooses not to use them.
Acquire Glucose Reading
The user may initiate an NFC transfer from the sensor to the rapid-acting insulin smart cap (RCap) by waking up the pen cap and waving it over the sensor, as shown in
After acquiring the glucose reading, the pen cap presents the user with their current glucose value and a trend line, along with a recommended correction dose or action. If there is no glucose value available from within the last ten minutes, the pen cap displays the home screen with no value and the system proceeds to the next step in the workflow when initiated by the user. In some embodiments, as discussed elsewhere, a suggested correction dose may be dependent on pen capping information. For example, in some embodiments, a recommended correction dose for an elevated glucose reading will only be displayed if the pen cap has been on the pen for at least a threshold period of time (e.g., at least 2 hours, at least 3 hours, or at least 4 hours). The time of the last dose may be displayed, which would be based on the most recent capping of the pen cap.
User Assessment of Glycemic Impact of Meal (Optional)
If the user intends to dose for a meal, they move to the next screen and are presented with three different dose recommendations, for meals that will have a small, medium, or large impact on their blood sugar. These recommendations may change over time to adapt to the user's habits and physiology. The recommended doses include a correction based on the user's glucose reading, if applicable.
Inject Rapid-Acting and Capture Insulin Dose
The user removes the RCap from the insulin pen and installs the needle onto the insulin pen. The needle is primed and then the user dials their desired dose and injects the insulin. The user removes the needle and replaces the cap on the rapid-acting insulin pen. The glucose values (if applicable) are transmitted via BLE to the mobile app where they are stored locally on a smartphone. When a connection to the cloud is available via cellular or Wi-Fi, the data is then synced to the cloud. In some embodiments, a portion of the system (e.g., the cap, the mobile application) may monitor use of the pens (e.g., based on data inputted by the user regarding usual use of the devices) to detect priming actions (e.g., clicks, such as two sets of clicks, from the pen and/or input from the user regarding the priming or lack thereof) and/or selection of dosages. In some cases, methods, systems, and devices provided herein can detect a needle presence to infer priming behavior (i.e., assume priming if the needle was removed and replaced). In some cases, methods, systems, and devices provided herein can assume priming based on dose volume and expected glucose impact.
Delivering a Long-Acting Insulin Dose
When the user decides to deliver a long-acting insulin dose, the system initiates the following workflow. Some of the steps are optional and may not be invoked if particular devices are unavailable or if the user chooses not to use them.
Acquire Glucose Reading
The user may initiate an NFC transfer from a glucose sensor (typically a CGM) to the long-acting insulin pen cap 112 by waking up the pen cap and waving it over the sensor.
After acquiring the glucose reading, the pen cap presents the user with their current glucose value and a trend-line, along with a recommended long-acting insulin dose. If there is no glucose value available from within the last ten minutes, the pen cap displays only the long-acting insulin dose recommendation, which is tailored to the user's habits and physiology and may change over time with clinician oversight and approval.
Inject Insulin Dose
The user removes pen cap 112 from the insulin pen and installs the needle onto the cartridge. The needle is primed and then the user dials their desired dose and injects the insulin. The user removes the needle and replaces the cap on the rapid-acting insulin pen. The glucose values (if applicable) are transmitted via BLE to the mobile app where they are stored locally on a smartphone. When a connection to the cloud is available via cellular or Wi-Fi, the data is then synced to the cloud. In some embodiments, a portion of the system (e.g., the cap, the mobile application) may monitor use of the pens (e.g., based on data inputted by the user regarding usual use of the devices) to detect priming actions (e.g., clicks, such as two sets of clicks, from the pen and/or input from the user regarding the priming or lack thereof) and/or selection of dosages.
Checking Status on Rapid-Acting Pen Cap and Long-Acting Pen Cap
Checking System Status
The user can check system status in the following locations:
Mobile Application User Interface
Methods and systems provided herein can additionally include a mobile application that runs on a mobile device (e.g., a smartphone or tablet) that is in wireless communication (e.g., via BLE) with one or more pen caps described herein. In some embodiments, blood glucose data may be transmitted from a glucose sensor system 101 (e.g., from a glucose monitor 130 and/or a blood glucose meter 150), either via the pen caps and/or directly from the glucose sensor system. In some embodiments, a mobile application can have a user interface that displays a graphical representation of the blood glucose data. In some embodiments, a graphical display of blood glucose data over time can include indicators communicating pen capping information.
Messages may be displayed on the home screen to provide the user with reminders about recommended actions that the user might take to improve their therapy. In some embodiments, a mobile app may provide coaching to a user based on a combination of the glucose data and/or pen capping information. In some embodiments, coaching via the app may be approved by a healthcare professional via a cloud connection before it is provided to the user. For example, in some embodiments, blood glucose data after a capping action may indicate that the user is typically under dosing or typically over dosing insulin for particular meals. In some embodiments, methods and systems provided herein can then adjust the user-specific therapy parameters or recommended dose amounts for rapid-acting insulin based on blood glucose data after each capping event. In some embodiments, glucose data after or surrounding each capping event may be sent to a healthcare professional to have the healthcare professional update user-specific dosage parameters or recommended dose amounts for that user, which may be based on the time of day. In some embodiments, data surrounding each capping event may indicate that the user is typically dosing rapid-acting insulin after the meal has begun, and might be adapted to coach the user to pre-bolus for meals when the user intends to eat. In some embodiments, data surrounding each capping event along with blood glucose levels may be utilized to recommend injection timings relative to when a meal is begun after the injection. In some embodiments, data surrounding each capping event and/or blood glucose levels may be utilized to recommend the modifications of doses of insulin taken by the subject. Again, such coaching may be automatic, approved by the healthcare professional, and/or developed by a healthcare professional.
In some embodiments, blood glucose levels may further be utilized to track and/or make recommendations for the type of insulin being taken. In some cases, blood glucose levels may be analyzed in conjunction with dose capture data to determine if the wrong insulin was taken. In some cases, blood glucose data in combination with temperature sensor data from a pen cap may be analyzed to determine if the insulin has gone bad., if the wrong insulin was taken (e.g., as discussed above), or if there are other issues with the therapy or associated devices.
The mobile application may be adapted to enable the user to provide additional information that may be used to determine how often the user is following the recommended doses. In some embodiments, a user may be provided with the possibility to input dose amounts for each capping event and/or may input multiple doses (e.g., an amount of insulin taken throughout a selected period of time, such as, over a day) into the mobile application or directly into the pen cap. For example, the markings along the graph may be tapped by a user to allow a user to enter to dose administered.
In embodiments where data is only intermittently received from a blood glucose monitor (e.g., where segments or blocks of data regarding BGVs are downloaded at discrete time periods on demand), the data preceding the current data point circle 302 indicating the latest glucose reading (e.g., the area between the current circle 302 and the immediately preceding circle 302) may be received from the glucose monitor and populated into the trend line 304. In some embodiments, another marker (e.g., a most recent circle 306) may be positioned at the latest reading (e.g., the most recent circle 302) and may be visually distinct from the preceding circles 302. In some embodiments, the time of the last scan may be displayed on the display 300. In some embodiments, the horizontal position on the trend line 304 of the most recent circle or marker 306 may also be indicated on the display 300 with a marker (e.g., vertical line 308).
In some embodiments, the pen cap may query the blood glucose sensor when the device is placed near the sensor and/or when a button (e.g., a virtual scan sensor button 310) is selected or pushed (e.g., and held) by a user. In some embodiments, the display 300 may include an indicator (e.g., meter 312 extending around the user button 310) that displays a measurement related to the system. For example, the meter 312 may display the remaining lifespan of the blood glucose sensor (e.g., the estimated time before the sensor needs to be replaced). As depicted, the meter 312 may increase (e.g., grow) or decrease (e.g., recede) around the button 310 as the related data changes. For example, the meter 312 may decrease or increase over time as the lifespan of the blood glucose sensor approaches zero (e.g., resulting in either a full meter 312 or an empty or outlined meter 312). In some embodiments, the meter 312 may display other metrics, such as, for example, time since last scan, time until next recommend scan, the percentage remaining of a previously administer dose (e.g., a correction dose), etc.
As shown in
In some embodiments, the most recent circle 306 (e.g., along with the vertical line 308) may be anchored to the most recent data position of the trend line 304 and may jump back to the most current position once the most recent circle 306 is released by the user. For example, the vertical line 308 may be deformed into a “slingshot” and spring the circle 306 back to the most current reading position when released by the user.
In some embodiments, a user might be asked to estimate a number of units of insulin remaining in a pen every so often. In some embodiments, a user might be asked to take a photo of the insulin pen and the app might be adapted to analyze the image of the insulin pen to determine an approximate number of units left in the pen. For example,
In one embodiment, the device may automatically analyze an insulin vial and infer meal information based on changes to an image of the insulin vial. For example, based on several successive images meal intake and meal times may be inferred based on changes in the amount of insulin in a vial and the type of insulin (i.e., rapid acting).
In some embodiments, the pen may include indicators e.g., graduated markings) that enable a user to easily identify a position of a portion of the pen (e.g., the plunger) and input an associated value into the application.
Pen caps may be configured to gain insights into which recommended dose the user is likely to be following. For example, as described in U.S. patent application Ser. No. 15/717,805, filed Sep. 27, 2017, entitled “Medicine Injection And Disease Management Systems, Devices and Methods,” and filed Sep. 27, 2017, the contents and disclose of which is hereby incorporated by reference in its entirety, a pen cap (whether or not there is any dose capture feature incorporated into the pen cap) can include meal announcement categorizations (such as S, M, L) and data from each announcement might indicate whether the user is likely to have dosed an appropriate amount for a S, M, or L meal. In some embodiments, a button on pen cap 122 might be pressed multiple times to show recommendations for successively a S meal, a M meal, and a L meal, and methods and systems provided herein may assume that the user dosed insulin based on the last displayed recommendation. In some embodiments, information added via the mobile application indicating an amount of insulin left in the pen at various intervals (once a day, once every few days, once a week) can indicate whether the user is generally following the therapy recommendations or whether the user is ignoring them. In some embodiments, methods and systems provided herein can analyze glucose data, pen capping information, data regarding amounts of insulin left in one or more pens, and/or answers to questions presented via the mobile app to determine a likelihood or rating of the user's conformance to recommended doses, which may be used by methods and systems provided herein to determine whether to adjust the recommended doses or to provide coaching to the user.
System Setup
Therapy management systems provided herein may be setup using any suitable method. In some embodiments, a health care professional can input initial therapy parameters from a web portal or directly into a user's mobile device (e.g., during an appointment). In some embodiments, the user may input initial therapy parameters based on advice from a doctor. Therapy management systems provided herein provide a way for users to clearly understand their therapy settings so that they gain trust in the system.
The mobile application might present the screen shown in
In the screen shown in
Diabetes management systems provided herein can, in some embodiments, use data relating to the user to customize one or more correctional doses.
In some embodiments, a user interface on the mobile device 140 or available via the cloud from a remote server can permit a health care professional or a PWD to set an ISF or input other data use to determine correction doses. In some embodiments, a glucose goal value set in
Correction dose=rounddown (Current Blood Glucose-Glucose Goal)/ISF.
In some embodiments, the glucose goal set in
As shown in
In either option, the mobile application may display a confirmation of the scale (e.g., non-linear scale) entered manually by the user under the first option or a confirmation of the scale (e.g., a linear scale) generated using the ISF value entered by the user under the second option.
Methods, devices, and systems provided herein may detect patterns in blood glucose levels and/or patterns of injections that enable the devices or systems to understand the impact of dosing and determine recommended therapy setting changes to improve glycemic outcomes. In some embodiments, the mobile device can determine appropriate therapy changes. In some embodiments, a remote server can determine appropriate therapy settings. In some embodiments, methods, devices, and systems can incrementally automatically adjust dosages for different meal sizes as described in U.S. patent application Ser. No. 15/717,805, which is hereby incorporated by reference. In some embodiments, algorithms can update the ISF or the correction doses based on detected patterns. In some embodiments, methods, devices, and systems can determine if there is a therapeutically relevant change recommended and then use that information to tell the user about the pattern or to tell the user about the pattern with a trigger, a tip, or a suggestion to the user e.g., a message in the mobile application); examples of which are depicted in
Alerts and Alarms
In some embodiments, diabetes management systems, devices, and methods provided herein may provide notifications, alarms, and/or alerts. In some embodiments, notifications, alarms, and/or alerts may be automatically triggered on one or more portions of the system, such as, for example, the mobile device, the pen caps, and/or one or more separate alert accessories. In some embodiments, therapy management systems, devices, and methods provided herein can include a smart pen or pen accessory (e.g., an accessory adapted to be secured to a pen, such as, for example, a pen cap and/or another accessory that is integral with or may be applied and/or coupled to the pen) that is adapted to provide notifications, therapy recommendations, and/or alerts upon the user taking action to retrieve blood glucose data. In some embodiments, therapy management systems, devices, and methods provided herein can include both one or more alert accessories and one or more smart pens or pen accessories that can each wirelessly receive blood glucose data (e.g., from a continuous glucose monitor). In some embodiments, therapy management systems, devices, and methods provided herein may have one or more smart pens or pen accessories that communicate with a blood glucose monitoring system (e.g., a continuous glucose monitor) via a first communication technique (e.g., NFC) and have one or more alert accessories that communicate with a blood glucose monitoring system (e.g., the same continuous glucose monitor) via a second communication technique (e.g., UHF, BLE). In some embodiments, the communication technique for communicating blood glucose data to the alert accessory has a larger range than the communication technique for communicating blood glucose data to the smart pens or pen accessories. In some embodiments, therapy management systems, devices, and methods provided herein can include one or more alert accessories that passively receive blood glucose data (e.g., via wireless communication), provided that it is in a communication range, and one or more smart pens or pen accessories that are configured to only wirelessly receive blood glucose data if a user takes action to have the smart pen or pen accessory receive blood glucose data (e.g., presses a button, swipes the pen or pen accessory adjacent to a glucose sensor, etc.). In some embodiments, having a smart pen or pen accessory that only receives blood glucose data upon user action can reduce the power consumption for the smart pen or pen accessory, thus reducing the burden on the user to recharge or replace batteries in the smart pen or pen accessory. In some embodiments, having an alert accessory as provided herein can enable the user to decide when and where to receive disruptive alarms, alerts, and notifications, and further permit the user to not feel a need to carry around their insulin pens between doses.
Methods, systems, and devices provided herein can include one or more alert accessories that can take any suitable form. In some embodiments, an alert accessory can include one or more illuminable icons. In some embodiments, an alert accessory can include a digital display screen. In some embodiments, an alert accessory can include one or more speakers and/or vibrational motors. In some embodiments, alert accessories contemplated herein may be secured to a smartphone (e.g., as a phone case). In some embodiments, alert accessories contemplated herein may be secured to a keychain. In some embodiments, alert accessories contemplated herein may be adapted to serve as a bedside alarm clock. In some embodiments, alert accessories are contemplated herein.
In some embodiments, methods, systems, and devices provided herein may provide guidance regarding an appropriate dosage of insulin. In some embodiments, the dosage of insulin may be administered with an insulin delivery pen or syringe. In some embodiments, the insulin may be long-acting insulin. In some embodiments, the insulin may be rapid-acting insulin. In some embodiments, an insulin delivery pen, or accessory therefor (e.g., a cap), can detect an amount of insulin delivered from the pen (or an amount of insulin that was set for delivery). In some embodiments, an insulin pen, or an accessory therefor, can include a user-interface, which can display data or recommendations to the user and/or permit the user to enter data into the insulin pen or accessory.
The following example therapy management system includes insulin delivery pens having dose-capture pen caps, but other embodiments are envisioned where the functionality disclosed herein is incorporated into other accessories for an insulin delivery pen or the insulin delivery pen itself. Additionally, the following example therapy management system includes a single alert accessory (e.g., a CGM fob), but other embodiments are envisioned that include multiple alert accessories or where the functionality of the alert accessory is merged into a smartphone or other web-connected mobile computing device (e.g., using Wi-Fi or cellular communications).
In some embodiments, one or more portions of the system (e.g., the pens, the mobile application, the alert accessory) may be configured to present one or more of the following alarms or alerts:
In some cases, methods and systems provided herein include an alarm or alert that is triggered if a user removes a long acting pen cap or rapid acting pen cap during a time period when a user should not (or should administer a different dose) administer long-acting insulin or rapid-acting insulin. For example, when an uncapping of a long-acting pen cap is detected, then insulin dose information about a recent dose of long-acting insulin may be reviewed. Reviewed dose information may include dose amount, dose time, type of insulin, and/or brand of insulin. Based on dose information and uncapping information, a risk of a user mistake may be inferred. Examples of user mistakes for which a risk may be inferred include, but are not limited to, administering a dose of long acting insulin instead of rapid acting insulin and administering a dose of long acting insulin and/or rapid acting insulin too soon after a previous dose. So, a contemplated operation of methods and systems of this disclosure includes, for example, an uncapping event is detected for a long acting pen cap at 9:30 AM. Dosing events corresponding to inferred dosing actions (e.g., based on capping events as described herein) are reviewed and a dosing event for long acting insulin at 8:00 AM is identified. Dosing information indicates that a dose of long acting insulin was administered at 8:00 AM, the amount of insulin administered corresponds to a basal dose, and a risk of a user mistakenly administering a second dose of long acting insulin is inferred (such a risk may also be characterized as a risk of insulin stacking). In some cases, the earlier dose may be confirmed based on blood glucose data, changes in which would be indicative of insulin action on a user's blood glucose levels. Upon inferring the risk of a user mistakenly administering long acting insulin, an alarm or alert may be generated and presented to a user. For example, a pen cap, injection pen, or mobile device may vibrate or emit an audible sound indicating to a user that there may be an error.
Upgradable System
Diabetes management systems provided herein may be adapted to add or remove components from use and/or to be configured based on the needs of the person with diabetes (PWD). For example,
For pen cap 122, display 124A may be the standard display when the pen cap is not in use. As discussed above, the display 124 may be a bistable display that can retain an image without excessive power supply. Display 124A can include a label of the type of insulin so that a user glancing at the pen cap 122 will immediately know the type of insulin. When a button is pressed or the pen cap 122 removed a time of a last dose may be displayed in display 124B. A retrieval of an EGV (e.g., via a scan of CGM 130) can cause display 124C to appear. As shown, display 124C includes a correction dose, which may be based on the EGV (and optionally trend data) using any suitable technique. In some cases, the correction dose may only appear if a time since the prior dose is greater than a predetermined number of hours and the pen cap 122 is still on the pen 120. In some cases, if the time since the last dose is less than a threshold (e.g., less than 1 hour, less than 30 minutes), a warning may appear and/or the pen cap may refuse to provide a recommended dose. In display screen 124D, meal dose recommendations are shown. In display screen 124E, meal+correction doses are shown. In some cases, display 124 can progress through display screens 124C-124E with successive button pushes.
The embodiments described herein may include the use of a special-purpose or general-purpose computer including various computer hardware or software modules, as discussed in greater detail below.
Embodiments described herein may be implemented using computer-readable media for carrying or having computer-executable instructions or data structures stored thereon. Such computer-readable media may be any available media that may be accessed by a general-purpose or special-purpose computer. Special-purpose computer is intended to be interpreted broadly and encompasses embedded systems, microcontrollers, application specific integrated circuits, digital signal processors, and general-purpose computers programmed for specific purposes. Segments (e.g., code segment or data segment) may refer to a portion (e.g., address) of memory, virtual memory, or an object file.
By way of example, and not limitation, such computer-readable media may include non-transitory computer-readable storage media including Random Access Memory (RAM), Read-Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Compact Disc Read-Only Memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, flash memory devices (e.g., solid-state memory devices), or any other storage medium which may be used to carry or store desired program code in the form of computer-executable instructions or data structures and which may be accessed by a general-purpose or special-purpose computer. Combinations of the above may be included within the scope of computer-readable media.
Computer-executable instructions comprise, for example, instructions and data which cause a general-purpose computer, special-purpose computer, or special-purpose processing device (e.g., one or more processors) to perform a certain function or group of functions. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Any ranges expressed herein (including in the claims) are considered to be given their broadest possible interpretation. For example, unless explicitly mentioned otherwise, ranges are to include their endpoints (e.g., a range of “between X and Y” would include X and Y). Additionally, ranges described using the terms “approximately” or “about” are to be understood to be given their broadest meaning consistent with the understanding of those skilled in the art. Additionally, the terms “approximately” or “substantially” include anything within 10%, or 5%, or within manufacturing or typical tolerances.
The features of the various embodiments described herein are not mutually exclusive and can exist in various combinations and permutations, even if such combinations or permutations are not expressly described herein, without departing from the scope of the disclosure. In fact, variations, modifications, and other implementations of what is described herein will occur to one of ordinary skill in the art without departing from the scope of the disclosure. As such, the invention is not to be defined only by the preceding illustrative description, but only by the claims which follow, and legal equivalents thereof.
Additional non-limiting embodiments of the disclosure relate, generally to a pen cap for insulin injection pens and associated methods and systems:
Embodiment 1: A pen cap for a manual insulin delivery device, comprising: a wireless communication interface configured to receive blood glucose data from a glucose sensor system; at least one detection circuit configured to detect one or more cappings and one or more decappings of the pen cap from the manual insulin delivery device; at least one user interface configured to present one or more of therapy relevant information, therapy recommendations, and timing information associated with detected cappings or detected decappings of the pen cap; and a processor and a memory, the memory comprising: a data segment configured to store one or more of at least one user-specific dosage parameter and a recommended dose; and a code segment configured to store instructions that, while executed by the processor, are adapted to enable the processor to determine content presentable by the at least one user interface responsive to the timing information associated with detected cappings or detected decappings of the pen cap.
Embodiment 2: The pen cap of Embodiment 1, wherein the user interface is configured to present a recommended correction dose of insulin responsive to a determination that the replacement cap has been capped on the manual insulin delivery device for at least a threshold period of time, wherein the recommendation correction dose of insulin is based on an insulin sensitivity factor and target glucose value stored at the data segment of the memory.
Embodiment 3: The pen cap of any one of the preceding Embodiments, wherein the wireless communication interface is configured to communicate with the glucose sensor system via a near field communication protocol when in proximity to at least one part of the glucose sensor system.
Embodiment 4: The pen cap of any one of the preceding Embodiments, wherein the wireless communication interface is configured to transmit messages that are associated with an insulin therapy.
Embodiment 5: The pen cap of any one of the preceding Embodiments, wherein the messages comprise indicators, and the indicators are associated with the insulin therapy.
Embodiment 6: The pen cap of any one of the preceding Embodiments, wherein the messages are configured to be received by one or more insulin therapy applications executing at one or more mobile computing devices.
Embodiment 7: The pen cap of any one of the preceding Embodiments, wherein the wireless communication interface is configured to transmit messages by broadcasting advertising messages.
Embodiment 8: The pen cap of any one of the preceding Embodiments, wherein the wireless communication interface is configured to transmit messages using data transmission.
Embodiment 9: The pen cap of any one of the preceding Embodiments, wherein wireless communication interface is configured to automatically transmit data ton insulin therapy application executing on a mobile device.
Embodiment 10: The pen cap of any one of the preceding Embodiments, wherein the wireless communication interface is configured to automatically communicate with the mobile application.
Embodiment 11: The pen cap of any one of the preceding Embodiments, wherein the wireless communication interface is adapted to communicate with the glucose sensor system using a first wireless communication technique having a first communication range and the wireless communication interface is adapted to communicate with the mobile computing device using a second wireless communication technique having a second communication range, the second communication range being greater than the first communication range.
Embodiment 12: The pen cap of any one of the preceding Embodiments, wherein the glucose sensor system comprises a flash glucose monitor.
Embodiment 13: The pen cap of any one of the preceding Embodiments, wherein the content includes a representation of a percentage of active insulin remaining within a user based on a time of a previous capping or decapping of the replacement pen cap and a current time.
Embodiment 14: The pen cap of any one of the preceding Embodiments, wherein the code segment is configured to store instructions that, while executed by a processor, are adapted to enable the processor to: determine an amount of insulin remaining in the manual insulin delivery device; and determine a dose amount for a time of a previous capping or decapping, and wherein the at least one user interface is configured to display an estimation of active insulin remaining within a user responsive to a current time and one or more dosing events.
Embodiment 15: The pen cap of any one of the preceding Embodiments, wherein the memory segment is configured to store dosing events over a first time period, the time period comprising: a first block of discrete time units; a start time unit of the first block of discrete time units; and an end time of the first block of discrete time units, and wherein the end time corresponds to the current time and at least one of the discrete time units is associated with a dosing event of the dosing events.
Embodiment 16: The pen cap of any one of the preceding Embodiments, wherein the code segment is configured to store instructions that, while executed by the processor, are adapted to enable the processor to record dosing events responsive to detected capping and/or detected decapping and associate the dosing events with one or more discrete time units of the discrete time units.
Embodiment 17: The pen cap of any one of the preceding Embodiments, wherein the code segment is configured to store instructions that, while executed by the processor, are adapted to enable the processor to: select a block of discrete time units that form the first time period responsive to an active insulin estimation request and the current time; select the one or more dosing events that are associated with the first time period; determine the estimation of active insulin remaining within the user responsive to the current time and the one or more dosing events.
Embodiment 18: The pen cap of any one of the preceding Embodiments, wherein the at least one user interface is configured to display the estimation of active insulin remaining as a percentage of a dose amount associated with a most recent dosing action.
Embodiment 19: The pen cap of any one of the preceding Embodiments, further comprising an inner sleeve and an outer housing, the inner sleeve and the outer housing defining a water tight cavity.
Embodiment 20: The pen cap of any one of the preceding Embodiments, wherein at least a part of one or more of the at least one detection circuit, processor, memory, and wireless communication interface is retained within the water tight cavity.
Embodiment 21: The pen cap of any one of the preceding Embodiments, further comprising an adapter configured to reversibly couple with a corresponding adapter at the manual insulin delivery device.
Embodiment 22: An insulin delivery system comprising: an insulin injection pen for delivering insulin; and a pen cap adapted to be reversibly secured to the insulin injection pen, the pen cap comprising: a wireless communication interface adapted to receive blood glucose data from a glucose sensor system; at least one circuit adapted to detect one whether the pen cap is secured to the insulin injection pen; and at least one user interface to communicate therapy relevant information, therapy recommendations, or a time of a previous capping or decapping of the pen cap from the insulin injection pen; memory to store at least one user-specific dosage parameter or recommended dose; and at least one processor adapted to determine content presented by the user interface, the at least one processor using information about one or more capping or decapping to determine the content.
Embodiment 23: The insulin delivery system of Embodiment 22, wherein the user interface is adapted to display a recommended correction dose of insulin based on an insulin sensitivity factor and target glucose value stored in memory if the pen cap has been capped on the insulin injection pen for at least a threshold period of time.
Embodiment 24: The insulin delivery system any one of the preceding Embodiments, wherein the content includes a representation of a percentage of active insulin remaining within a user based on a time of a previous capping or decapping of the pen cap and a current time.
Embodiment 25: The insulin delivery system of any one of the preceding Embodiments, wherein the replacement pen cap is adapted to determine an amount of insulin remaining in the insulin injection pen and determine a dose amount for the time of a previous capping or decapping, wherein the pen cap displays an estimation of active insulin remaining within the user based a current time and the times and dose amounts associated with one or more a previous capping or decapping of the pen cap.
Embodiment 26: A diabetes management system comprising: a mobile computing device configured to receive one or more user-specific dosage parameters or predetermined doses from a user; a glucose sensor system configured to collect and wirelessly transmit blood glucose data; and a pen cap adapted to be reversibly secured to an insulin injection pen, the pen cap comprising: a wireless communication interface adapted to receive the blood glucose data from the glucose sensor system and the one or more user-specific dosage parameters or predetermined doses from the mobile computing device; at least one circuit adapted to detect one whether the pen cap is secured to the insulin injection pen; and at least one user interface to communicate therapy relevant information, therapy recommendations, or a time of a previous capping or decapping of the pen cap from the insulin injection pen; memory to store the one or more user-specific dosage parameters or predetermined doses received from the mobile computing device; and at least one processor adapted to determine content presented by the user interface, the at least one processor using information about one or more capping or decapping to determine the content.
Embodiment 27: The diabetes management system of Embodiment 26, further comprising an insulin injection pen adapted to be reversibly secured to the pen cap.
Embodiment 28: The diabetes management system of any one of the preceding Embodiments, wherein the user interface is adapted to display a recommended correction dose of insulin based on an insulin sensitivity factor and target glucose value stored in memory if the replacement pen cap has been capped on the insulin injection pen for at least a threshold period of time.
Embodiment 29: The diabetes management system of any one of the preceding Embodiments, further comprising a long-acting insulin pen, a rapid-acting insulin pen, and at least two pen cap, the at least two of the pen caps including a first pen cap adapted to be secured to the long-acting insulin pen and a second pen cap adapted to be secured to the rapid-acting insulin pen.
Embodiment 30: The diabetes management system of any one of the preceding Embodiments, wherein the wireless communication interface is configured to communicate with the glucose sensor system via a near field communication protocol when the pen cap is positioned in proximity to at least one part of the glucose sensor system.
Embodiment 31: The diabetes management system of any one of the preceding Embodiments, wherein the wireless communication interface is adapted to communicate with the glucose sensor system using a first wireless communication technique having a first communication range and the wireless communication interface is adapted to communicate with the mobile computing device using a second wireless communication technique having a second communication range, the second communication range being greater than the first communication range.
Embodiment 32: The diabetes management system of any one of the preceding Embodiments, wherein the glucose sensor system comprises a flash glucose monitor.
Embodiment 33: A smart electronics module integratable with a manual insulin delivery device, comprising: a wireless communication interface configured to receive blood glucose data from a glucose sensor system; at least one detection circuit configured to detect one or more cappings and one or more decappings of a pen cap from the manual insulin delivery device; at least one user interface configured to present one or more of therapy relevant information, therapy recommendations, and timing information associated with detected cappings or detected decappings of the pen cap; and a processor and a memory, the memory comprising: a data segment configured to store one or more of at least one user-specific dosage parameter and a recommended dose; and a code segment configured to store instructions that, while executed by the processor, are adapted to enable the processor to determine content presentable by the at least one user interface responsive to the timing information associated with the detected cappings or detected decappings of the pen cap.
Embodiment 33: A system, method or device according to any one of the preceding embodiments, wherein the blood glucose data is an interstitial fluid glucose level or based on an interstitial fluid glucose level.
Embodiment 34: A system, method or device according to any one of the preceding embodiments, wherein the blood glucose data is a blood glucose level correlated to an interstitial fluid glucose level.
Embodiment 35: A system, method or device according to any one of the preceding embodiments, wherein the blood glucose data is a blood glucose level.
Additional non-limiting embodiments of the disclosure relate, generally, to therapy management systems, methods, and devices:
Embodiment 1: A reusable accessory for a manual medication delivery device, comprising: a wireless communication interface that is configured to receive analyte measurement data from an analyte sensor system; detection circuitry configured to: detect dosing events associated with dosing actions at the manual medication delivery device; and store a record for each of the one or more dosing events, wherein the record comprises a dosing time of the dosing events; a recommendation system configured to provide one or more medication dose recommendations responsive to one or more of the analyte measurement data and the dosing events; and an adapter configured to reversibly couple to a predetermined portion of the manual medication delivery device.
Embodiment 2: The reusable accessory of Embodiment 1, wherein the manual medication delivery device is a medication injection pen and the reusable accessory is a reusable pen cap for the medication injection pen, and wherein the dosing events associated with the one or more dosing actions are one or more of capping events or decapping events, and the detection circuitry is configured detect capping events or decapping events responsive to sensor signals.
Embodiment 3: The reusable accessory of any one of the preceding Embodiments, further comprising a timer configured to count a number of time units from a decapping event to a subsequent capping event, wherein the circuitry is configured to record a dose time responsive to a determined count greater than a threshold number of time units.
Embodiment 4: The reusable accessory of any one of the preceding Embodiments, wherein the wireless communication interface is configured to receive the analyte measurement data over a first wireless connection when the wireless communication interface is positioned in proximity to at least a portion of the analyte sensor system.
Embodiment 5: The reusable accessory of any one of the preceding Embodiments, wherein the wireless communication interface is configured to communicate, over a second wireless connection, dosing events, therapy parameters, and analyte measurement data with a mobile computing device.
Embodiment 6: The reusable accessory of any one of the preceding Embodiments, wherein the wireless communication interface is configured to receive therapy parameters from the mobile computing device.
Embodiment 7: The reusable accessory of any one of the preceding Embodiments, wherein the first wireless connection has a first communication range and the second wireless connection has a second communication range, wherein the second communication range is greater than the first communication range.
Embodiment 8: The reusable accessory of any one of the preceding Embodiments, wherein the wireless communication interface comprises an NFC chip and the first wireless connection consists of NFC communications between the reusable accessory and the analyte sensor system.
Embodiment 9: The reusable accessory of any one of the preceding Embodiments, wherein the wireless communication interface comprises a wireless radio adapted to enable BLUETOOTH Low Energy communication between the reusable accessory and one or more mobile computing devices.
Embodiment 10: The reusable accessory of any one of the preceding Embodiments, wherein the analyte sensing system comprises a blood glucose meter adapted to provide blood glucose data.
Embodiment 11. The reusable accessory of any one of the preceding Embodiments, wherein the analyte sensor system is a flash glucose monitor adapted to provide glucose data via near field communication.
Embodiment 12: The reusable accessory of any one of the preceding Embodiments, wherein the analyte sensor system is a continuous glucose monitor adapted to provide blood data via wireless radio communication (e.g., BLUETOOTH LOW ENERGY) and optionally near field communication (NFC).
Embodiment 13: The reusable accessory of any one of the preceding Embodiments, further comprising at least one button for enabling and disabling operational modes of the reusable accessory, including triggering receipt of analyte measurement data, changing a display, stopping or snoozing an alarm, or a combination thereof
Embodiment 14: A diabetes management system comprising: a glucose sensor system adapted wirelessly transmit blood glucose data; an insulin dosage monitoring device adapted to be reversibly connectable to an insulin delivery device, the insulin dosage monitoring device comprising a display, memory, and processor, the memory storing insulin therapy dosage parameters, the insulin dosage monitoring device being adapted to detect deliveries of insulin from the insulin delivery device, the insulin dosage monitoring device being adapted to wirelessly receive blood glucose data from the glucose sensor system, the processor being adapted to provide insulin dose recommendation based on the stored insulin therapy dosage parameters, the blood glucose data, or a combination thereof; and a mobile computing device including a processor, the mobile computing device being configured to intermittently connect to and receive the at least one characteristic relating to the insulin monitoring device, the blood glucose data, or a combination thereof from the insulin dosage monitoring device via wireless communication.
Embodiment 15: The system of Embodiment 14, wherein the insulin dosage monitoring device comprises a pen cap and the insulin delivery device is an insulin injection pen, wherein the pen cap is adapted to detect deliveries of insulin from the insulin injection pen by detecting pen cap capping events, which may be inferred to be dosing events.
Embodiment 16: The system of any one of the preceding Embodiments, wherein the insulin dosage monitoring device comprises a pen cap and the insulin delivery device is an insulin injection pen, wherein the pen cap is adapted to detect an amount of insulin remaining in the insulin injection pen to determine a timing of, and optionally a dose amount, for each dose.
Embodiment 17: The system of any one of the preceding Embodiments, wherein the insulin dosage monitoring device comprises an accessory that can detect the movement of a plunger or associated mechanical elements that move during an injection of insulin from an insulin injection pen.
Embodiment 18: The system of any one of the preceding Embodiments, wherein the mobile computing device is configured to receive data relating to the at least one characteristic over a selected period of time comprising past data values leading up to a substantially present time value.
Embodiment 19: A method of managing medication therapy by a manual medication delivery device, comprising: receiving analyte measurement data from an analyte sensor system; detecting dosing action events at an accessory configured to reversibly attach to a manual medication delivery device; storing a record for each of the one or more dosing action events, wherein the record comprises a dosing time of a dosing action; and providing one or more medication dose recommendations responsive to the analyte measurement data.
Embodiment 20: The method of Embodiment 19, further comprising receiving, over a first wireless connection, analyte measurement data responsive to the wireless communication interface positioned in proximity to at least a portion of the analyte sensor system.
Embodiment 21: The method of any one of the preceding Embodiments, further comprising communicating over a second wireless connection, dosing events, therapy parameters, and analyte measurement data with a mobile computing device.
Embodiment 22: The method of any one of the preceding Embodiments, further comprising receiving therapy parameters from the mobile computing device over the second wireless connection.
Embodiment 23: The method of any one of the preceding Embodiments, wherein the manual medication delivery device is a medication injection pen and the reusable accessory is a reusable pen cap for the medication injection pen, and wherein the dosing action events associated with one or more dosing actions are one or more of capping events and decapping events, and the detection circuitry is configured detect capping events and decapping events responsive to sensor signals.
Embodiment 24: A smart electronics module integratable with a manual medication delivery device, comprising: a wireless communication interface that is configured to receive analyte measurement data from an analyte sensor system; detection circuitry configured to: detect dosing action events; store a record for each of the one or more dosing actions, wherein the record comprises a dosing time of the dosing action; and receive analyte measurement data received from the analyte sensor system; a recommendation system configured to provide one or more medication dose recommendations responsive to the analyte measurement data; and an adapter configured to reversibly couple to a predetermined portion of the manual medication delivery device.
Embodiment 25: A system, method or device according to any one of the preceding embodiments, wherein the blood glucose data and/or glucose data is an interstitial fluid glucose level or based on an interstitial fluid glucose level.
Embodiment 26: A system, method or device according to any one of the preceding embodiments, wherein the blood glucose data and/or glucose data is a blood glucose level correlated to an interstitial fluid glucose level.
Embodiment 27: A system, method or device according to any one of the preceding embodiments, wherein the blood glucose data and/or glucose data is a blood glucose level.
Additional non-limiting embodiments of the disclosure relate, generally, to user interface for diabetes management systems including flash glucose monitor:
Embodiment 1: A diabetes management system comprising: a flash glucose monitor adapted to be secured to a person with diabetes (PWD), the flash glucose monitor comprising: a sensing portion adapted to detect blood glucose data at regular time intervals, the regular time intervals being less than or equal to every 15 minutes; and a wireless communication interface adapted to transmit blood glucose data when the wireless communication interface is activated by a user, wherein the transmitted blood glucose data for each wireless communication transmission comprises a blood glucose data collected over a data transmission window of at least 1 hour; and a user interface device comprising: a UI wireless communication interface adapted to receive the transmitted blood glucose data at irregular intervals governed at least in part by the actions of the user; a display comprising a touch screen; and a processor and memory, the processor being adapted to execute instructions in the memory to display a representation of glucose values comprising: a graphical representation having a time of the day along the bottom of the graphical representation and a curve of glucose values for each time of the day that has been received, wherein a current time of day is presented on the graphical representation to indicate if there is a gap between a most recent glucose value and the current time of day; and a single numerical value representing a single blood glucose measurement adjacent to the graphical representation; wherein the single numerical value is the most recent glucose value when the screen is not being touched by a user, wherein the processor and memory are configured to change the single numerical value to a prior glucose value when a user touches a portion of the screen corresponding to a prior time of day on the graphical representation.
Embodiment 2: The diabetes management system of Embodiment 1, wherein the graphical representation comprises a point indicator that is positioned along the time axis to correspond to the time of day when the single numerical value was detected.
Embodiment 3: The diabetes management system of any one of the preceding Embodiments, wherein the display is configured so that the user can change the position of the point indicator by pressing the portion of the screen corresponding to position along the time axis at a time prior to the moss recent glucose value.
Embodiment 4: The diabetes management system of any one of the preceding Embodiments, wherein the portion of the screen corresponding to a position along the time axis is a portion of the screen depicting the time axis.
Embodiment 5: The diabetes management system of any one of the preceding Embodiments, wherein the portion of the screen corresponding to a position along the time axis is a portion of the screen depicting the curve of glucose values.
Embodiment 6: The diabetes management system of any one of the preceding Embodiments, wherein the point indicator must be pressed and slid back along the graphical representation to move the point indicator.
Embodiment 7: The diabetes management system of any one of the preceding Embodiments, wherein the point indicator moves back along the curve of glucose values after a user stops pressing a portion of the graphical representation.
Embodiment 8: The diabetes management system of any one of the preceding Embodiments, wherein the display further depicts a trend arrow adjacent to the single numerical value depicting a rate of change of glucose values at the time of the single numerical value.
Embodiment 9: The diabetes management system of any one of the preceding Embodiments, further comprising a reusable accessory adapted to be reversibly secured to an insulin injection pen, wherein the reusable accessory comprises an accessory wireless communication interface adapted to be used by a user to interrogate the flash glucose monitor to receive the blood glucose data.
Embodiment 10: The diabetes management system of any one of the preceding Embodiments, wherein the accessory wireless communication interface is adapted to automatically transmit the blood glucose data to the user interface device.
Embodiment 11: The diabetes management system of any one of the preceding Embodiments, wherein the reusable accessory is adapted to detect an event associated with an administration of insulin from the insulin injection pen.
Embodiment 12: The diabetes management system of any one of the preceding Embodiments, further comprising displaying an injection indicator along the time axis of the graphical representation for each detected event.
Embodiment 13: The diabetes management system of any one of the preceding Embodiments wherein the injection indicator displays an amount of insulin administered.
Embodiment 14: The diabetes management system of any one of the preceding Embodiments, wherein the injection indicator displays a type of insulin administered.
Embodiment 15: The diabetes management system of any one of the preceding Embodiments, further comprising a second reusable accessory adapted to be reversibly secured to a second insulin injection pen, the second insulin injection pen retaining a second type of insulin, wherein the graphical representation includes different injection indicators along the time axis for each reusable accessory.
Embodiment 16: The diabetes management system of any one of the preceding Embodiments, wherein the reusable accessory is a replacement pen cap and the event associated with an administration of insulin from the insulin injection pen is a capping or decapping of the replacement pen cap from the insulin injection pen.
Embodiment 17: The diabetes management system of any one of the preceding Embodiments, wherein the reusable accessory comprises an accessory display, the accessory display depicting a most recent glucose value received from the flash glucose monitor.
Embodiment 18: The diabetes management system of any one of the preceding Embodiments, wherein the user interface device is adapted to receive insulin therapy settings and wirelessly communicate the insulin therapy settings to the reusable accessory, wherein the accessory display is adapted to provide a recommended insulin dose based on the received insulin therapy settings and a most recent glucose value.
Embodiment 19: The diabetes management system of any one of the preceding Embodiments, further comprising a blood glucose meter is wireless communication with one or more components of the system, wherein the graphical representation also includes BGM indicators representing blood glucose measurements from the blood glucose meter.
Embodiment 20: The diabetes management system of any one of the preceding Embodiments, wherein the single numerical value representing a single blood glucose measurement is adapted to depict the blood glucose measurements from the blood glucose meter or glucose values from the flash glucose monitor.
Embodiment 21: A system, method or device according to any one of the preceding embodiments, wherein the blood glucose data and/or glucose values are an interstitial fluid glucose level or based on an interstitial fluid glucose level.
Embodiment 22: A system, method or device according to any one of the preceding embodiments, wherein the blood glucose data and/or glucose values are a blood glucose level correlated to an interstitial fluid glucose level.
Embodiment 23: A system, method or device according to any one of the preceding embodiments, wherein the blood glucose data and/or glucose values are a blood glucose level.
Additional non-limiting embodiments of the disclosure relate, generally, to devices, systems, and methods for estimating active medication from injections:
Embodiment 1: A reusable accessory for a medication injection pen wherein the reusable accessory is adapted to be reversibly attached to a medication injection pen, the reusable accessory being configured to detect an event associated with an injection of medication from the medication injection pen and determine a percentage of medication that remains active for the injection of medication based on a current time and a time of the event associated with an injection.
Embodiment 2: The reusable accessory of Embodiment 1, wherein the reusable accessory is a replacement pen cap adapted to be secured to the medication injection pen such that medication cannot be injected into a user when the replacement pen cap is secured to the medication injection pen, wherein the event associated with an injection of medication is a capping or decapping event that is detected responsive to capping or decapping the medication injection pen with the replacement pen cap.
Embodiment 3: The reusable accessory of Embodiment 1 or Embodiment 2, wherein the reusable accessory comprises a display, wherein the display depicts a visual indicator of an amount of active medication remaining as a percentage.
Embodiment 4: The reusable accessory of one of Embodiments 1-3, wherein the reusable accessory is adapted to determine a dose amount for each detected event associated with an injection of medication, wherein the reusable accessory determines an amount of medication that remains active for a plurality of injections of medication based on a current time and a time of each of the plurality of injections.
Embodiment 5: The reusable accessory for one of Embodiments 1-3, wherein the reusable accessory does not detect or determine a dose amount for each detected event associated with an injection of medication.
Embodiment 6: The reusable accessory of one of Embodiments 1-5, wherein the medication injection pen is an insulin injection pen.
Embodiment 7: The reusable accessory of one of Embodiments 1-6, wherein the reusable accessory comprises a processor and memory, wherein the memory stores one or more user-specific dosage parameters, wherein the processor is adapted to determine a recommended dose of medication based at least in part on the user-specific dosage parameters and a calculation of active medication for one or more prior injections of medication.
Embodiment 8: The reusable accessory of one of Embodiments 1-7, wherein the reusable accessory comprises a wireless communication interface adapted to send or receive wireless communications.
Embodiment 9: The reusable accessory of any one of the preceding Embodiments, wherein the reusable accessory is adapted to receive analyte measurement data from an analyte senor system via the wireless communication interface, wherein the reusable accessory is adapted to determine a recommended dose of medication based at least in part on received analyte measurement data.
Embodiment 10: The reusable accessory of any one of the preceding Embodiments, wherein the reusable accessory is adapted to send data regarding the event associated with each injection of medication to a mobile computing device via the wireless communication.
Embodiment 11: The reusable accessory of any one of the preceding Embodiments, wherein the reusable accessory is adapted to receive user-specific dosage parameters from a mobile computing device via the wireless communication.
Embodiment 12: The reusable accessory of any one of the preceding Embodiments, wherein the wireless communication interface is configured to receive analyte measurement data from an analyte sensor system.
Embodiment 13: The reusable accessory of any one of the preceding Embodiments, wherein the reusable accessory comprises a recommendation system configured to provide one or more medication dose recommendations responsive to the analyte measurement data.
Embodiment 14: The reusable accessory of any one of the preceding Embodiments, wherein the wireless communication interface comprise a first wireless connection having a first communication range and a second wireless connection having a second communication range, wherein the first wireless connection is between the reusable accessory and an analyte sensor system, wherein the second wireless connection is between the reusable accessory and a mobile application on a remote computing device, wherein the second communication range is greater than the first communication range.
Embodiment 15: The reusable accessory of any one of the preceding Embodiments, wherein the wireless communication interface comprises an NFC chip and the first wireless connection consists of NFC communications between the reusable accessory and the analyte sensor system.
Embodiment 16: The reusable accessory of any one of the preceding Embodiments, wherein the wireless communication interface comprises a wireless radio adapted to permit BLUETOOTH Low Energy communications between the reusable accessory and one or more mobile computing devices.
Embodiment 17: The reusable accessory of any one of the preceding Embodiments, wherein the analyte sensor system is a flash glucose monitor adapted to provide glucose data via near field communication.
Embodiment 18: A diabetes therapy management system comprising: a mobile computing device being adapted to receive one or more user-specific dosage parameters or predetermined doses from a user; a glucose sensor system adapted to collect and wirelessly transmit blood glucose data; and reusable accessory adapted to be reversibly attached to an insulin injection pen, the reusable accessory comprising: a wireless communication interface adapted to receive the blood glucose data from the glucose sensor system and the one or more user-specific dosage parameters or predetermined doses from the mobile computing device; an injection detection mechanism adapted to detect an event associated with an injection of insulin; a processor to determine a percentage of insulin that remains active for each injection of insulin; and a display adapted to display an amount of active insulin remaining in the user as a percentage of the last injection of insulin.
Embodiment 19: The system of Embodiment 18, wherein the reusable accessory detects or determines a dose of insulin for each event associated with an injection of insulin and the display displays an amount of active insulin remaining in the user as a number of units of insulin, which can optionally include multiple doses of insulin at different times.
Embodiment 20: The system of any one of the preceding Embodiments, wherein the reusable accessory does not detect or determines a dose of insulin for each event associated with an injection of insulin.
Embodiment 21: A method of managing a diabetes therapy, comprising: detecting an event associated with an injection of medication from a medication injection pen responsive to an attaching or detaching of a reusable accessory to the medication injection pen; determining a percentage of medication that remains active for the injection of medication based on a current time and time of the event associated with the injection, wherein the event is associated with attaching or detaching a reusable accessory to the medication injection pen.
Embodiment 22: A smart electronics module integratable with a medication injection pen wherein the reusable accessory is adapted to be reversibly attached to a medication injection pen, the reusable accessory being configured to detect an event associated with an injection of medication from the medication injection pen and determine a percentage of medication that remains active for the injection of medication based on a current time and a time of the event associated with an injection.
Embodiment 23: A system, method or device according to any one of the preceding embodiments, wherein the blood glucose data and/or glucose data is an interstitial fluid glucose level or based on an interstitial fluid glucose level.
Embodiment 24: A system, method or device according to any one of the preceding embodiments, wherein the blood glucose data and/or glucose data is a blood glucose level correlated to an interstitial fluid glucose level.
Embodiment 25: A system, method or device according to any one of the preceding embodiments, wherein the blood glucose data and/or glucose data is a blood glucose level.
Additional non-limiting embodiments of the disclosure relate, generally, to insulin injection assistance systems, methods, and devices:
Embodiment 1: A system to assist with the manual dosing of insulin, the system comprising: at least a first glucose sensor system adapted to wirelessly transmit glucose data; at least a first reusable insulin dosing detector adapted to be reversibly connectable to at least a first disposable component comprising a chamber for a first insulin type to form at least part of a first insulin manual delivery assembly, the first reusable insulin dosing detector configured to detect first insulin delivery events associated with the first insulin manual delivery assembly, and a recommendation system comprising a mobile application and a computing device remote from the first reusable insulin dosing detector, wherein the mobile application, while executing at the computing device, is configured to: receive insulin therapy settings, the insulin therapy settings comprising a first insulin type setting; determine first timing data corresponding to one or more first insulin delivery event times of one or more of the first insulin delivery events; analyze the glucose data in combination with the first timing data; and determine an adjustment recommendation or automatic insulin therapy setting change responsive to the analysis.
Embodiment 2: The system of Embodiment 1, further comprising a remote server adapted to receive the glucose data and the first timing data over an interne connection between the mobile computing device and the remote server.
Embodiment 3: The system of any one of the preceding Embodiments, wherein the remote server is configured to analyze the first timing data and the glucose data, and determine the adjustment recommendation or the automatic insulin therapy setting change responsive to the analysis.
Embodiment 4: The system of any one of the preceding Embodiments, wherein the mobile application is configured to analyze the first timing data and the glucose data, determine the adjustment recommendation or the automatic insulin therapy setting change responsive to the analysis.
Embodiment 5: The system of any one of the preceding Embodiments, wherein the first reusable insulin dosing detector is a first reusable accessory, the first disposable component is a first insulin injection pen or a first insulin inhaler, and the first insulin delivery events are associate insulin injection or insulin inhalation, and wherein the first reusable accessory is adapted to reversibly connect to the first insulin injection pen or the first insulin inhaler.
Embodiment 6: The system of any one of the preceding Embodiments, wherein the first reusable accessory is a first replacement cap adapted to be placed over a needle of the first insulin injection pen or adapted to be placed over an inhalation pathway of the first insulin inhaler, wherein the first replacement cap is configured to detect capping and/or de-capping events.
Embodiment 7: The system of any one of the preceding Embodiments, wherein the first reusable accessory is configured to detect the first insulin delivery events responsive to the one or more capping and/or de-capping events.
Embodiment 8: The system of any one of the preceding Embodiments, wherein the first reusable insulin dosing detector is a first reusable smart pen or a first smart inhaler and the first disposable component comprises a first insulin cartridge, wherein the first reusable smart pen or the first smart inhaler is configured to receive the first insulin injection cartridge and configured to be actuated by a user to deliver the first insulin type from the first insulin cartridge.
Embodiment 9: The system of any one of the preceding Embodiments, further comprising: at least a second reusable insulin dosing detector adapted to be reversibly connectable to a second disposable component comprising a chamber for a second insulin type to form at least part of a second insulin manual delivery assembly, wherein the second reusable accessory comprises a second wireless communication interface configured to wirelessly receive a second insulin type setting of the insulin delivery settings from the mobile application, wherein the second reusable insulin dosing detector configured to detect second insulin delivery events associated with the second insulin manual delivery assembly, and wherein the recommendation system is configured to: determine second timing data corresponding to one or more second insulin delivery event times for one or more second insulin delivery events; analyze the glucose data in combination with the first timing data and the second timing data; and determine an adjustment recommendation or automatic change to an insulin delivery setting responsive to the analysis.
Embodiment 10: The system of any one of the preceding Embodiments, wherein the second reusable insulin dosing detector is configured to wirelessly receive glucose data from the first glucose sensor system.
Embodiment 11: The system of any one of the preceding Embodiments, wherein the system disables the wireless communication of the glucose data from the first glucose sensor system to the first reusable insulin dosing detector while the first glucose sensor system is in wireless communication with the second reusable insulin dosing detector.
Embodiment 12: The system of any one of the preceding Embodiments, wherein the second reusable insulin dosing detector is selected from the group consisting of a second smart pen configured to receive a second disposable pen cartridge containing a second insulin type, a second smart inhaler configured to receive a second disposable inhalable insulin cartridge containing a second insulin type, a second replacement pen cap adapted to be secured over a needle of a second disposable insulin injection pen containing the second insulin type, or a second replacement inhaler cap adapted to be secured over an inhalation pathway of an second insulin inhaler.
Embodiment 13: The system of any one of the preceding Embodiments, wherein the first insulin type is selected from a group consisting of a long acting insulin, a rapid acting insulin, and a combination long acting and rapid acting insulin.
Embodiment 14: The system of any one of the preceding Embodiments, wherein the first glucose sensor system is a blood glucose meter adapted to analyze blood in vitro.
Embodiment 15: The system of any one of the preceding Embodiments, wherein the recommendation system is adapted to analyze the timing data of one or more insulin delivery events and the glucose data to recommend adding a second glucose sensor system selected from the group consisting of continuous glucose monitors and flash glucose monitors.
Embodiment 16: The system of any one of the preceding Embodiments, wherein the first glucose sensor system is a flash glucose monitor.
Embodiment 17: The system of any one of the preceding Embodiments, wherein the first glucose sensor system is configured to communicate a limited glucose data set to the mobile application via a first communication technique having a first communication range and to communicate robust glucose data set to the first or second reusable insulin dosing detector via a second communication technique having a second communication range, the first communication range being greater than the second communication range.
Embodiment 18: The system of any one of the preceding Embodiments, wherein the mobile application can receive glucose data directly from the first glucose sensor system via the first communication technique and the second communication technique.
Embodiment 19: The system of any one of the preceding Embodiments, wherein the first reusable insulin dosing detector comprises a display, wherein the display is configured to provide a recommended first insulin dose of the first insulin type based on the first insulin setting.
Embodiment 20: The system of any one of the preceding Embodiments, wherein the first reusable insulin dosing detector or the mobile application is configured to issue an alert if a detected dose of the first insulin type fails to comply with the first insulin setting.
Embodiment 21: The system of any one of the preceding Embodiments, wherein the system is adapted to determine one or more insulin dose amounts of the first insulin type associated with each detected first insulin delivery event.
Embodiment 22: A method of assisted manual dosing of insulin, the method comprising: receiving first insulin delivery events associated with a first insulin manual delivery assembly, the first insulin manual delivery assembly comprising a first reusable insulin dosing detector reversibly connected to a first disposable component and adapted to detect the first insulin delivery events; determining first timing data corresponding to one or more first insulin delivery event times of one or more of the first insulin delivery events; analyzing the glucose data in combination with the first timing data; and determining an adjustment recommendation or an automatic insulin therapy setting change responsive to the analysis.
Embodiment 23: The method of Embodiment 22, further comprising receiving the first insulin delivery events at a communication interface configured for wireless communication with the first reusable insulin dosing detector.
Embodiment 24: The method of any one of the preceding Embodiments, further comprising: receiving second insulin delivery events associated with a second insulin manual delivery assembly, the second insulin manual delivery assembly comprising a second reusable insulin dosing detector reversibly connected to a second disposable component and adapted to detect the second insulin delivery events; and determining a second adjustment recommendation or a second automatic insulin therapy setting change responsive to the second insulin delivery events.
Embodiment 25: The method of any one of the preceding Embodiments, further comprising receiving glucose data from the first reusable dosing detector.
Embodiment 26: The method of any one of the preceding Embodiments, further comprising receiving glucose data from a first glucose sensor system.
Embodiment 27: A system for remotely assigning with the manual dosing of insulin, the system comprising: receiving first insulin delivery events associated with a first insulin manual delivery assembly, wherein the insulin delivery events are received at a communication interface configured for communication with a reusable insulin dosing detector; determining first timing data corresponding to one or more first insulin delivery event times for one or more first insulin delivery events; analyzing the glucose data in combination with the first timing data; determining an adjustment recommendation or an automatic insulin therapy setting change responsive to the analysis; and providing the adjustment recommendation or the automatic insulin therapy setting change to the communication interface to send to the reusable insulin dosing detector.
Embodiment 28: An insulin manual dosing assistance system, the system comprising: a recommendation system comprising a mobile application executing at a computing device, the mobile application configured to determine insulin delivery adjustment recommendations and insulin therapy setting changes responsive to glucose data associated with one or more insulin delivery events, the recommendation system further configured to: detect a first reusable insulin dosing detector; create an insulin manual delivery assembly profile responsive to the detection, the insulin manual delivery assembly profile associated with an insulin manual delivery assembly of the first reusable insulin dosing detector; and assign one or more insulin therapy settings to the insulin manual delivery assembly profile.
Embodiment 29: The system of Embodiment 28, wherein the recommendation system is configured to, responsive to one or more physiological parameters associated with a user of the recommendation system, either load the one or more insulin therapy settings from memory, or create the one or more insulin therapy settings.
Embodiment 30: The system of any one of the preceding Embodiments, wherein the recommendation system is configured to provide a user prompt at a display of the computing device, the user prompt comprising one an approval for pairing with the first reusable insulin dosing detector.
Embodiment 31: The system of any one of the preceding Embodiments, wherein the recommendation system is configured to send one or more of insulin delivery adjustment recommendations and changes to insulin therapy setting to the reusable insulin dosing detector.
Embodiment 32: The system of any one of the preceding Embodiments, wherein the recommendation system is further configured to receive an instruction to un-pair with a second insulin dosing detector, and, responsive to the instruction to un-pair, delete or deactivate a second insulin manual delivery assembly profile associated with the second insulin dosing detector.
Embodiment 33: The system of any one of the preceding Embodiments, wherein the recommendation system is further configured to: detect a second reusable insulin dosing detector; create a second insulin manual delivery assembly profile responsive to the detection, the second insulin manual delivery assembly profile associated with a second insulin manual delivery assembly of the second reusable insulin dosing detector; and assign one or more second insulin therapy settings to the second insulin manual delivery assembly profile.
Embodiment 34: The system of any one of the preceding Embodiments, wherein the recommendation system is configured to send insulin delivery adjustment recommendations and insulin therapy setting changes to the first and the second reusable insulin dosing detector.
Embodiment 35: The system of any one of the preceding Embodiments, wherein the recommendation system is configured to receive glucose data associated with one or more insulin delivery events of the first and the second reusable insulin dosing detector.
Embodiment 36: The system of any one of the preceding Embodiments, wherein the first reusable insulin dosing detector and the second reusable insulin dosing detector is each a different one of a reusable accessory, a smart insulin pen, and a smart insulin.
Embodiment 37: A system to assist with the manual dosing of insulin, the system comprising: at least a first glucose sensor system adapted to wirelessly transmit glucose data; smart electronics coupled with one or more parts of a first insulin manual delivery assembly, the smart electronics comprising at least a first reusable insulin dosing detector operably connected to at least a first disposable component comprising a chamber for a first insulin type to form at least part of the first insulin manual delivery assembly, the first reusable insulin dosing detector configured to detect first insulin delivery events associated with the first insulin manual delivery assembly; and a recommendation system comprising a mobile application and a computing device remote from the first reusable insulin dosing detector, wherein the mobile application, while executing at the computing device, is configured to: receive insulin therapy settings, the insulin therapy settings comprising a first insulin type setting; determine first timing data corresponding to one or more first insulin delivery event times for one or more first insulin delivery events; analyze the glucose data in combination with the first timing data; and determine an adjustment recommendation or automatic insulin therapy setting change responsive to the analysis.
Embodiment 38: A system, method or device according to any one of the preceding embodiments, wherein the glucose data is an interstitial fluid glucose level or based on an interstitial fluid glucose level.
Embodiment 39: A system, method or device according to any one of the preceding embodiments, wherein the glucose data is a blood glucose level correlated to an interstitial fluid glucose level.
Embodiment 40: A system, method or device according to any one of the preceding embodiments, wherein the glucose data is a blood glucose level.
Additional non-limiting embodiments of the disclosure relate, generally, to pen cap for medication injection pen having temperature sensor:
Embodiment 1: A replacement pen cap for a medication injection pen comprising at least one temperature sensor, wherein the at least one temperature sensor is configured to monitor a temperature of medication within the medication injection pen while the replacement pen cap is associated with the medication injection pen, wherein the replacement pen cap is adapted to detect possible dosing events, wherein the replacement pen cap is adapted to receive analyte measurement data from an analyte sensor system, wherein the replacement pen cap is adapted to determine if medication in the medication injection pen is denatured based on a combination of data from the at least one temperature sensor and the received analyte measurement data subsequent to each detected possible dosing event.
Embodiment 2: The replacement pen cap of Embodiment 1, wherein the at least one temperature sensor is configured to monitor ranges of temperature when the pen cap is associated with the insulin pen.
Embodiment 3: The replacement pen cap of any one of the preceding Embodiments, wherein the pen cap is configured to provide at least one of an alarm or alert to a user when a selected threshold temperature value is sensed, wherein an alert is presented when a threshold is exceeded as a visual display and an audible alarm is triggered when the threshold is exceeded and the pen cap receives glucose values that indicate that one or more prior insulin administrations have been ineffective.
Embodiment 4: The pen cap of any one of the preceding Embodiments, wherein the pen cap is configured to provide data to a user relating to the temperature exposure of the insulin.
Embodiment 5: A smart electronics module integratable with a medication injection pen comprising at least one temperature sensor, wherein the at least one temperature sensor is configured to monitor a temperature of medication within the medication injection pen while the smart electronics module is enabled, wherein the smart electronics module is configured to detect possible dosing events, wherein the smart electronics module is configured to receive analyte measurement data from an analyte sensor system, wherein the smart electronics module is configured to determine if medication in the medication injection pen is denatured based on a combination of data from the at least one temperature sensor and the received analyte measurement data subsequent to each detected possible dosing event.
Embodiment 6: A system, method or device according to any one of the preceding embodiments, wherein the glucose data is an interstitial fluid glucose level or based on an interstitial fluid glucose level.
Embodiment 7: A system, method or device according to any one of the preceding embodiments, wherein the glucose data is a blood glucose level correlated to an interstitial fluid glucose level.
Embodiment 8: A system, method or device according to any one of the preceding embodiments, wherein the glucose data is a blood glucose level.
Additional non-limiting embodiments of the disclosure relate, generally, to user interface for diabetes management systems and devices:
Embodiment 1: A diabetes management system comprising: a computing device including memory and a processor configured to: receive at least one data point relating to prior insulin use of a subject; and calculate a sliding scale glucose correction data set based, at least in part, on the at least one data point relating to prior insulin use of a subject.
Embodiment 2: The system of Embodiment 1, further comprising an insulin pen assembly, wherein the computing device is configured to provide at least some data from the sliding scale glucose correction data set to the insulin pen assembly, and wherein the insulin pen assembly is configured to display the at least some data as a recommended correction insulin dose.
Embodiment 3: The system of any one of the preceding Embodiments, wherein the insulin pen assembly comprises a reusable accessory for an insulin pen and a disposable insulin pen.
Embodiment 4: The system of any one of the preceding Embodiments, wherein the reusable accessory is a replacement pen cap for the disposable insulin pen.
Embodiment 5: The system of any one of the preceding Embodiments, wherein the insulin pen assembly is a reusable insulin injection pen adapted to receive prefilled insulin cartridges for administering insulin.
Embodiment 6: The system of any one of the preceding Embodiments, wherein the insulin pen assembly is adapted to receive blood glucose data from a glucose sensor system, wherein the recommended correction insulin dose is based on the received blood glucose data and that sliding scale glucose correction data set.
Embodiment 7: The system of any one of the preceding Embodiments, wherein the sliding scale glucose correction data set is a linear scale based on the at least one data point comprising an insulin sensitivity factor.
Embodiment 8: The system of any one of the preceding Embodiments, wherein the sliding scale glucose correction data set is a nonlinear scale based on the at least one data point comprising a plurality of data points inputted into the computing device.
Embodiment 9: The system of any one of the preceding Embodiments, wherein the plurality of data points each comprises a range of glucose values and an associated correction dose.
Embodiment 10: The system of any one of the preceding Embodiments, wherein the range of glucose values and the associated correction dose are based on historical insulin use of a subject.
Embodiment 11: A diabetes management system comprising: a computing device including memory and a processor configured to: display a plurality of pictures of meals grouped into a plurality of categories, each category having a similar glycemic impact; and receive a user input of a number of units of insulin that the user would normally administer for meals in that category for each of the plurality of categories; and an insulin pen assembly having a pen display, wherein the computing device is configured to provide the insulin pen assembly with the user inputs for each category, the pen display providing at least one recommended insulin dose based at least in part on the received user inputs for each category.
Embodiment 12: The system of Embodiment 11, wherein the insulin pen assembly displays a recommended insulin dose for each of the plurality of categories.
Embodiment 13: The system of any one of the preceding Embodiments, wherein the computing device receives user input defining a correction factor based on blood glucose levels, wherein the insulin pen assembly is adapted to receive blood glucose data from a glucose sensor system, wherein the insulin pen assembly receives the correction factor from the computing device, wherein each recommended insulin dose is based upon the correction factor and the blood glucose data.
Embodiment 14: The system of any one of the preceding Embodiments, wherein correction factor is a sliding scale glucose correction data set.
Embodiment 15: The system of any one of the preceding Embodiments, wherein the insulin pen assembly comprises a reusable accessory for an insulin pen and a disposable insulin pen.
Embodiment 16: The system of any one of the preceding Embodiments, wherein the reusable accessory is a replacement pen cap for the disposable insulin pen.
Embodiment 17: A system, method or device according to any one of the preceding embodiments, wherein the glucose data is an interstitial fluid glucose level or based on an interstitial fluid glucose level.
Embodiment 18: A system, method or device according to any one of the preceding embodiments, wherein the glucose data is a blood glucose level correlated to an interstitial fluid glucose level.
Embodiment 19: A system, method or device according to any one of the preceding embodiments, wherein the glucose data is a blood glucose level.
Additional non-limiting embodiments of the disclosure relate, generally, to alarms and alerts in diabetes management system:
Embodiment 1: A diabetes management system comprising: one or more signaling outputs configured to present one or more of alarms, alerts, and notifications discernable by a user; at least a first glucose sensor system adapted to wirelessly transmit glucose data via at least a first wireless communication method having a first communication range and a second wireless communication method having a second communication range, wherein the first wireless communication method requires user action and the second wireless communication method is automatic, wherein the second communication range is greater than the first communication range; at least a first reusable accessory adapted to be reversibly connectable to at least a first insulin injection pen, the first reusable accessory being adapted to wirelessly receive the glucose data from the first glucose sensor system via the first wireless communication method upon being moved through the first communication range; and a mobile application on a remote computing device adapted to receive glucose data automatically via the second wireless communication method, the mobile application issuing an alarm at the one or more signaling outputs responsive, at least in part, to the received glucose data.
Embodiment 2: The diabetes management system of Embodiment 1, further comprising an insulin type detector configured to detect a type of insulin in a chamber of an insulin manual delivery device, wherein the first reusable accessory is configured to issue an alarm at the one or more signaling outputs responsive to the detector, the alarm indicating an incorrect insulin type.
Embodiment 3: The diabetes managing system of any one of the preceding Embodiments, further comprising an insulin type detector configured to detect a type of insulin in a chamber of an insulin manual delivery device, wherein the mobile application is configured to issue an alarm at the one or more signaling outputs responsive to the detector, the alarm indicating an incorrect insulin type.
Embodiment 4: The diabetes management system of any one of the preceding Embodiments, wherein the mobile application is configured to compare a detected insulin type to an expected insulin type and output an error signal responsive to the comparison.
Embodiment 5: The diabetes management system of any one of the preceding Embodiments, wherein the mobile application is configured to determine an expected insulin type responsive to dosing action or based on a user provided parameter.
Embodiment 6: The diabetes management system of any one of the preceding Embodiments, further comprising a user confirmation system configured to present a prompt to a user responsive to dosing actions and one or more diabetes management system mode.
Embodiment 7: The diabetes management system of any one of the preceding Embodiments, wherein the user confirmation system is configured to present a prompt for physiological parameters responsive to a hyper system monitoring mode and a high correction dose associated with a recent dosing action.
Embodiment 8: The diabetes management system of any one of the preceding Embodiments, further comprising a user confirmation system configured to present a prompt for glucose measurements responsive to a current time or a time period.
Embodiment 9: The diabetes management system of any one of the preceding Embodiments, wherein the first reusable accessory does not receive glucose data via the first wireless communication method from the first glucose sensor system.
Embodiment 10: The diabetes management system of any one of the preceding Embodiments, wherein the first reusable accessory is adapted to receive glucose data from the mobile application via the second wireless communication method.
Embodiment 11: The diabetes management system of any one of the preceding Embodiments, wherein the first communication method is near field communication and the second communication method is BLUETOOTH low energy.
Embodiment 12: The diabetes management system of any one of the preceding Embodiments, wherein the alarm is based on a received glucose value being less than a threshold.
Embodiment 13: The diabetes management system of any one of the preceding Embodiments, wherein the alarm is based on a predicted future glucose value being less than a threshold.
Embodiment 14: The diabetes management system of any one of the preceding Embodiments, wherein the first accessory is adapted to detect the administration of insulin from the first insulin injection pen and communicate administration data to the mobile application via the second wireless communication method.
Embodiment 15: The diabetes management system of any one of the preceding Embodiments, wherein the alarm is based at least in part on the administration data.
Embodiment 16: The diabetes management system of any one of the preceding Embodiments, wherein the first insulin injection pen is a long-acting insulin injection pen and the alarm is a missed dose alarm.
Embodiment 17: The diabetes management system of any one of the preceding Embodiments, wherein the alarm is responsive to a high correction dose, a detected dosing event, and a time out.
Embodiment 18: The diabetes management system of any one of the preceding Embodiments, wherein the alarm is responsive to a missed dosing event, a high correction dose, and a time out.
Embodiment 19: A diabetes management system comprising: one or more signaling outputs configured to present one or more of alarms, alerts, and notifications discernable by a user; at least a first glucose sensor system adapted to wirelessly transmit glucose data via at least a first wireless communication method having a first communication range and a second wireless communication method having a second communication range, wherein the first wireless communication method requires user action and the second wireless communication method is automatic, wherein the second communication range is greater than the first communication range; at least a first smart electronics module configured to be integratable with a first insulin injection pen, the first smart electronics module being configured to wirelessly receive the glucose data from the first glucose sensor system via the first wireless communication method upon being moved through the first communication range; and a mobile application on a remote computing device adapted to receive glucose data automatically via the second wireless communication method, the mobile application issuing an alarm at the one or more signaling outputs responsive, at least in part, to the received glucose data.
Embodiment 20: A system, method or device according to any one of the preceding embodiments, wherein the glucose data is an interstitial fluid glucose level or based on an interstitial fluid glucose level.
Embodiment 21: A system, method or device according to any one of the preceding embodiments, wherein the glucose data is a blood glucose level correlated to an interstitial fluid glucose level.
Embodiment 22: A system, method or device according to any one of the preceding embodiments, wherein the glucose data is a blood glucose level.
This application claims the benefit of the filing date of U.S. Provisional Patent Application Ser. No. 62/597,809 filed Dec. 12, 2017, for “Medicine Injection and Disease Management Systems, Devices, and Methods;” of U.S. Provisional Patent Application Ser. No. 62/597,868, filed Dec. 12, 2017, for “Therapy Assist Information and/or Tracking Device and Related Methods and Systems;” of U.S. Provisional Patent Application Ser. No. 62/628,808, filed Feb. 9, 2018, for “Diabetes Therapy Management Systems, Methods and Devices;” and of U.S. Provisional Patent Application Ser. No. 62/682,872, filed Jun. 9, 2018, for “Diabetes Therapy Management Systems, Methods, and Devices,” the disclosure of each of which is hereby incorporated herein in its entirety by this reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4498904 | Turner et al. | Feb 1985 | A |
| 4515584 | Abe et al. | May 1985 | A |
| 4950216 | Weder | Aug 1990 | A |
| 4973318 | Holm et al. | Nov 1990 | A |
| 4988660 | Campbell | Jan 1991 | A |
| 5233571 | Wirtschafter | Aug 1993 | A |
| 5279586 | Balkwill | Jan 1994 | A |
| 5523560 | Manique et al. | Jun 1996 | A |
| 5536249 | Castellano et al. | Jul 1996 | A |
| 5564414 | Walker et al. | Oct 1996 | A |
| 5626566 | Petersen et al. | May 1997 | A |
| 5640954 | Pfeiffer et al. | Jun 1997 | A |
| 5645534 | Chanoch et al. | Jul 1997 | A |
| 5665065 | Coman et al. | Sep 1997 | A |
| 5678571 | Brown | Oct 1997 | A |
| 5681285 | Ford et al. | Oct 1997 | A |
| 5822715 | Worthington et al. | Oct 1998 | A |
| 5918603 | Brown | Jul 1999 | A |
| 5925021 | Castellano et al. | Jul 1999 | A |
| 5984900 | Mikkelsen | Nov 1999 | A |
| 6004297 | Steenfeldt-Jensen et al. | Dec 1999 | A |
| 6032119 | Brown et al. | Feb 2000 | A |
| 6042571 | Hjertman et al. | Mar 2000 | A |
| 6235004 | Steenfeldt-Jensen et al. | May 2001 | B1 |
| 6287283 | Ljunggreen et al. | Sep 2001 | B1 |
| 6302855 | Lav et al. | Oct 2001 | B1 |
| 6354996 | Drinan et al. | Mar 2002 | B1 |
| 6482185 | Hartmann | Nov 2002 | B1 |
| 6650951 | Jones et al. | Nov 2003 | B1 |
| 6685678 | Evans et al. | Feb 2004 | B2 |
| 6810290 | Lebel et al. | Oct 2004 | B2 |
| 6817986 | Slate et al. | Nov 2004 | B2 |
| 6827702 | Lebel et al. | Dec 2004 | B2 |
| 6956572 | Zaleski | Oct 2005 | B2 |
| 7025743 | Mann et al. | Apr 2006 | B2 |
| 7109878 | Mann et al. | Sep 2006 | B2 |
| 7133329 | Skyggebjerg et al. | Nov 2006 | B2 |
| 7241265 | Cummings et al. | Jul 2007 | B2 |
| 7291107 | Hellwig et al. | Nov 2007 | B2 |
| 7343197 | Shusterman | Mar 2008 | B2 |
| 7397730 | Skyggebjerg et al. | Jul 2008 | B2 |
| 7404796 | Ginsberg | Jul 2008 | B2 |
| 7454359 | Rosenfeld et al. | Nov 2008 | B2 |
| 7553281 | Hellwig et al. | Jun 2009 | B2 |
| 7570980 | Ginsberg | Aug 2009 | B2 |
| 7591801 | Brauker et al. | Sep 2009 | B2 |
| 7647237 | Malave et al. | Jan 2010 | B2 |
| 7713229 | Veit et al. | May 2010 | B2 |
| 7751907 | Blomquist | Jul 2010 | B2 |
| 7837647 | Estes et al. | Nov 2010 | B2 |
| 7850641 | Lebel et al. | Dec 2010 | B2 |
| 7871376 | Brown | Jan 2011 | B2 |
| 7878975 | Liljeryd et al. | Feb 2011 | B2 |
| 7905833 | Brister et al. | Mar 2011 | B2 |
| 7931613 | Haueter et al. | Apr 2011 | B2 |
| 7955303 | Burren et al. | Jun 2011 | B2 |
| 7976492 | Brauker et al. | Jul 2011 | B2 |
| 8012119 | Estes et al. | Sep 2011 | B2 |
| 8052655 | Møller et al. | Nov 2011 | B2 |
| 8127946 | Winig et al. | Mar 2012 | B2 |
| 8132101 | Buck et al. | Mar 2012 | B2 |
| 8156070 | Buck et al. | Apr 2012 | B2 |
| 8206340 | Arefieg | Jun 2012 | B2 |
| 8217946 | Halpern et al. | Jul 2012 | B2 |
| 8219222 | Blomquist | Jul 2012 | B2 |
| 8221345 | Blomquist | Jul 2012 | B2 |
| 8221356 | Enggaard et al. | Jul 2012 | B2 |
| 8229535 | Mensinger et al. | Jul 2012 | B2 |
| 8231531 | Brister et al. | Jul 2012 | B2 |
| 8231562 | Buck et al. | Jul 2012 | B2 |
| 8237715 | Buck et al. | Aug 2012 | B2 |
| 8250483 | Blomquist | Aug 2012 | B2 |
| D667948 | Moldenhauer | Sep 2012 | S |
| 8257652 | Drucker et al. | Sep 2012 | B2 |
| 8257653 | Drucker et al. | Sep 2012 | B2 |
| 8266906 | Wu et al. | Sep 2012 | B2 |
| 8273296 | Drucker et al. | Sep 2012 | B2 |
| 8279226 | Krieftewirth | Oct 2012 | B2 |
| RE43834 | Steenfeldt-Jensen et al. | Nov 2012 | E |
| 8310415 | McLaughlin et al. | Nov 2012 | B2 |
| 8333752 | Veit et al. | Dec 2012 | B2 |
| 8337469 | Eberhart et al. | Dec 2012 | B2 |
| 8357091 | Say et al. | Jan 2013 | B2 |
| 8365065 | Gejdos et al. | Jan 2013 | B2 |
| 8372005 | Say et al. | Feb 2013 | B2 |
| 8439834 | Schmelzeisen-Redeker et al. | May 2013 | B2 |
| 8444595 | Brukalo et al. | May 2013 | B2 |
| 8460231 | Brauker et al. | Jun 2013 | B2 |
| 8514086 | Harper et al. | Aug 2013 | B2 |
| 8529838 | Drucker et al. | Sep 2013 | B2 |
| 8529839 | Drucker et al. | Sep 2013 | B2 |
| 8529841 | Drucker et al. | Sep 2013 | B2 |
| 8551039 | Veit et al. | Oct 2013 | B2 |
| 8556865 | Krulevitch et al. | Oct 2013 | B2 |
| 8556867 | Krulevitch et al. | Oct 2013 | B2 |
| 8562558 | Kamanth et al. | Oct 2013 | B2 |
| 8565848 | Brister et al. | Oct 2013 | B2 |
| D694252 | Helm | Nov 2013 | S |
| 8579815 | Galley et al. | Nov 2013 | B2 |
| 8591455 | Mensinger et al. | Nov 2013 | B2 |
| 8601005 | Bousamra et al. | Dec 2013 | B2 |
| 8615366 | Galley et al. | Dec 2013 | B2 |
| 8622906 | Say et al. | Jan 2014 | B2 |
| 8657779 | Blomquist | Feb 2014 | B2 |
| 8663109 | Brister et al. | Mar 2014 | B2 |
| 8719945 | Birtwhistle et al. | May 2014 | B2 |
| 8721585 | Brauker et al. | May 2014 | B2 |
| 8743662 | SjöLund et al. | Jun 2014 | B2 |
| 8750955 | Brister et al. | Jun 2014 | B2 |
| 8756074 | Brzustowicz | Jun 2014 | B2 |
| 8761940 | Long et al. | Jun 2014 | B2 |
| 8774887 | Say et al. | Jul 2014 | B2 |
| 8808228 | Brister et al. | Aug 2014 | B2 |
| 8816862 | Harper et al. | Aug 2014 | B2 |
| 8817258 | Whalley et al. | Aug 2014 | B2 |
| 8821452 | Dasbach et al. | Sep 2014 | B2 |
| 8882722 | Bode et al. | Nov 2014 | B2 |
| 8882741 | Brauker et al. | Nov 2014 | B2 |
| 8895315 | Batman et al. | Nov 2014 | B2 |
| 8920401 | Brauker et al. | Dec 2014 | B2 |
| 8926585 | Brauker et al. | Jan 2015 | B2 |
| 8932250 | Montgomery et al. | Jan 2015 | B2 |
| 8961465 | Blomquist | Feb 2015 | B2 |
| 8992464 | Bashan | Mar 2015 | B2 |
| D727928 | Allison et al. | Apr 2015 | S |
| 9008803 | Blomquist | Apr 2015 | B2 |
| 9020572 | Mensinger et al. | Apr 2015 | B2 |
| 9022996 | Eberhart et al. | May 2015 | B2 |
| 9033877 | Werner et al. | May 2015 | B2 |
| 9041730 | Johnson et al. | May 2015 | B2 |
| 9050409 | Haueter et al. | Jun 2015 | B2 |
| 9050413 | Brauker et al. | Jun 2015 | B2 |
| 9072477 | Say et al. | Jul 2015 | B2 |
| 9089650 | Nielsen et al. | Jul 2015 | B2 |
| 9101723 | Larsen | Aug 2015 | B2 |
| 9108006 | Jensen et al. | Aug 2015 | B2 |
| D738385 | Lim et al. | Sep 2015 | S |
| 9125991 | Schabbach et al. | Sep 2015 | B2 |
| 9134823 | Grant et al. | Sep 2015 | B2 |
| 9136939 | Galley et al. | Sep 2015 | B2 |
| 9143569 | Mensinger et al. | Sep 2015 | B2 |
| 9155843 | Brauker et al. | Oct 2015 | B2 |
| 9159148 | Boyer et al. | Oct 2015 | B2 |
| 9186113 | Harper et al. | Nov 2015 | B2 |
| 9198623 | Fern et al. | Dec 2015 | B2 |
| D747333 | Supino et al. | Jan 2016 | S |
| D748101 | Bang et al. | Jan 2016 | S |
| D748126 | Sarukkai et al. | Jan 2016 | S |
| 9233210 | Bock et al. | Jan 2016 | B2 |
| D749103 | Song | Feb 2016 | S |
| 9250111 | Whalley et al. | Feb 2016 | B2 |
| 9255830 | Whalley et al. | Feb 2016 | B2 |
| D753685 | Zimmerman et al. | Apr 2016 | S |
| D754689 | Lee | Apr 2016 | S |
| D759684 | Bijlani et al. | Jun 2016 | S |
| 9358334 | Arefieg | Jun 2016 | B2 |
| D761280 | Chung et al. | Jul 2016 | S |
| D763308 | Wang et al. | Aug 2016 | S |
| D766958 | Salazar et al. | Sep 2016 | S |
| 9435666 | Richter | Sep 2016 | B2 |
| 9446194 | Kamath et al. | Sep 2016 | B2 |
| 9483620 | Reimer | Nov 2016 | B2 |
| 9498155 | Brauker et al. | Nov 2016 | B2 |
| 9501219 | Yoshimoto et al. | Nov 2016 | B2 |
| 9526838 | Baran et al. | Dec 2016 | B2 |
| D777760 | Zhao | Jan 2017 | S |
| 9545482 | Binier | Jan 2017 | B2 |
| 9561324 | Estes | Feb 2017 | B2 |
| D781890 | Gathman et al. | Mar 2017 | S |
| 9604004 | Jakobsen | Mar 2017 | B2 |
| D783037 | Hariharan et al. | Apr 2017 | S |
| D783648 | Vazquez et al. | Apr 2017 | S |
| D784391 | Yuguchi et al. | Apr 2017 | S |
| D785025 | Zimmerman et al. | Apr 2017 | S |
| 9619625 | Bengtsson | Apr 2017 | B2 |
| 9623188 | Nielsen et al. | Apr 2017 | B2 |
| 9629901 | Estes | Apr 2017 | B2 |
| D786273 | Herman et al. | May 2017 | S |
| 9636461 | Bengtsson et al. | May 2017 | B2 |
| 9636464 | Binier | May 2017 | B1 |
| 9638564 | Whalley et al. | May 2017 | B2 |
| 9642968 | Whalley et al. | May 2017 | B2 |
| 9649448 | Madsen | May 2017 | B2 |
| 9651482 | Biei et al. | May 2017 | B2 |
| 9672328 | Saint et al. | Jun 2017 | B2 |
| 9675761 | Hoeholt et al. | Jun 2017 | B2 |
| D791806 | Brewington et al. | Jul 2017 | S |
| D794047 | Gandhi et al. | Aug 2017 | S |
| D795900 | Bischoff et al. | Aug 2017 | S |
| D795919 | Bischoff et al. | Aug 2017 | S |
| D795927 | Bischoff et al. | Aug 2017 | S |
| 9721176 | Prager | Aug 2017 | B2 |
| 9734302 | Nielsen et al. | Aug 2017 | B2 |
| 9737665 | Heumann et al. | Aug 2017 | B2 |
| D797760 | Tsujimura et al. | Sep 2017 | S |
| D798312 | Tsujimura et al. | Sep 2017 | S |
| 9750882 | Blei et al. | Sep 2017 | B2 |
| 9750886 | Plambech et al. | Sep 2017 | B2 |
| 9775543 | Brister et al. | Oct 2017 | B2 |
| 9782543 | Groeschke et al. | Oct 2017 | B2 |
| 9782544 | Heumann et al. | Oct 2017 | B2 |
| 9789260 | Binier | Oct 2017 | B1 |
| 9790977 | Baran et al. | Oct 2017 | B2 |
| D802760 | Neby | Nov 2017 | S |
| 9833576 | Windum et al. | Dec 2017 | B2 |
| 9848774 | Bergstrom et al. | Dec 2017 | B2 |
| D808986 | Dudey | Jan 2018 | S |
| D809544 | Ambielli | Feb 2018 | S |
| D809545 | Ban et al. | Feb 2018 | S |
| D811425 | Olsen et al. | Feb 2018 | S |
| D815127 | Phillips et al. | Apr 2018 | S |
| D815667 | Yeung | Apr 2018 | S |
| D819043 | Yamaura et al. | May 2018 | S |
| D820297 | Gardner et al. | Jun 2018 | S |
| 9996668 | Reihman et al. | Jun 2018 | B2 |
| 10016565 | Nielsen et al. | Jul 2018 | B2 |
| 10043093 | Allerdings et al. | Aug 2018 | B2 |
| 10071205 | Blei et al. | Sep 2018 | B2 |
| D831049 | Agarwal et al. | Oct 2018 | S |
| D831684 | Ghosh | Oct 2018 | S |
| D832292 | Hu et al. | Oct 2018 | S |
| 10086141 | Steel et al. | Oct 2018 | B2 |
| 10105094 | Baran et al. | Oct 2018 | B2 |
| 10105497 | Dreier et al. | Oct 2018 | B2 |
| D832870 | Hu | Nov 2018 | S |
| D833469 | Coleman et al. | Nov 2018 | S |
| D834710 | Michael | Nov 2018 | S |
| 10117996 | Stefansen | Nov 2018 | B2 |
| 10117999 | Andersen | Nov 2018 | B2 |
| 10133948 | Hammen | Nov 2018 | B2 |
| D835118 | Lee et al. | Dec 2018 | S |
| 10155090 | Larsen et al. | Dec 2018 | B2 |
| 10159797 | Andersen | Dec 2018 | B2 |
| 10159798 | Blei et al. | Dec 2018 | B2 |
| D837807 | Baber et al. | Jan 2019 | S |
| D838734 | Kruse et al. | Jan 2019 | S |
| 10166338 | Nielsen et al. | Jan 2019 | B2 |
| 10166340 | Blei et al. | Jan 2019 | B2 |
| 10169539 | Reihman et al. | Jan 2019 | B2 |
| 10173015 | West et al. | Jan 2019 | B2 |
| 10179207 | Haupt | Jan 2019 | B2 |
| 10183119 | Andersen et al. | Jan 2019 | B2 |
| 10183120 | Sihlanick et al. | Jan 2019 | B2 |
| 10190901 | Whalley et al. | Jan 2019 | B2 |
| 10195351 | Allerdings et al. | Feb 2019 | B2 |
| 10195352 | Baran et al. | Feb 2019 | B2 |
| 10195355 | Allerdings et al. | Feb 2019 | B2 |
| D842888 | Krainer et al. | Mar 2019 | S |
| D843402 | Casse et al. | Mar 2019 | S |
| D846590 | Cabrera et al. | Apr 2019 | S |
| D847165 | Kolbenheyer | Apr 2019 | S |
| D849757 | Jing et al. | May 2019 | S |
| 10667759 | Duke et al. | Jun 2020 | B2 |
| 10702658 | Shekalim | Jul 2020 | B2 |
| 20030032868 | Graskov et al. | Feb 2003 | A1 |
| 20030065536 | Hansen et al. | Apr 2003 | A1 |
| 20040039255 | Simonsen et al. | Feb 2004 | A1 |
| 20040062148 | Skyggebjerg et al. | Apr 2004 | A1 |
| 20040093331 | Garner et al. | May 2004 | A1 |
| 20040153257 | Munk | Aug 2004 | A1 |
| 20050038674 | Braig et al. | Feb 2005 | A1 |
| 20050049179 | Davidson et al. | Mar 2005 | A1 |
| 20050192557 | Brauker et al. | Sep 2005 | A1 |
| 20060036144 | Brister et al. | Feb 2006 | A1 |
| 20060173417 | Rosen et al. | Aug 2006 | A1 |
| 20070021715 | Kohlbrenner et al. | Jan 2007 | A1 |
| 20070173708 | Dobbles et al. | Jul 2007 | A9 |
| 20070186923 | Poutiatine et al. | Aug 2007 | A1 |
| 20070239486 | Gordon | Oct 2007 | A1 |
| 20080119705 | Patel et al. | May 2008 | A1 |
| 20080162192 | Vonk et al. | Jul 2008 | A1 |
| 20080188813 | Miller et al. | Aug 2008 | A1 |
| 20080201169 | Galasso et al. | Aug 2008 | A1 |
| 20080228057 | Graskov et al. | Sep 2008 | A1 |
| 20080234663 | Yodfat et al. | Sep 2008 | A1 |
| 20080235053 | Ray et al. | Sep 2008 | A1 |
| 20080262469 | Brister et al. | Oct 2008 | A1 |
| 20080287755 | Sass et al. | Nov 2008 | A1 |
| 20080300572 | Rankers et al. | Dec 2008 | A1 |
| 20080310676 | Silver | Dec 2008 | A1 |
| 20080312512 | Brukalo et al. | Dec 2008 | A1 |
| 20080312584 | Montgomery et al. | Dec 2008 | A1 |
| 20090036771 | Fago et al. | Feb 2009 | A1 |
| 20090048561 | Burren et al. | Feb 2009 | A1 |
| 20090120716 | Yamamoto et al. | May 2009 | A1 |
| 20090131875 | Green | May 2009 | A1 |
| 20090144089 | Heywood et al. | Jun 2009 | A1 |
| 20090163793 | Koehler et al. | Jun 2009 | A1 |
| 20090209938 | Aalto-Setala | Aug 2009 | A1 |
| 20090299276 | Brauker et al. | Dec 2009 | A1 |
| 20090299279 | Richter | Dec 2009 | A1 |
| 20090318865 | Moller et al. | Dec 2009 | A1 |
| 20100017141 | Campbell et al. | Jan 2010 | A1 |
| 20100049126 | Feld et al. | Feb 2010 | A1 |
| 20100063438 | Bengtsson | Mar 2010 | A1 |
| 20100081993 | O'Connor | Apr 2010 | A1 |
| 20100095229 | Dixon et al. | Apr 2010 | A1 |
| 20100292634 | Kircher et al. | Nov 2010 | A1 |
| 20100305965 | Benjamin et al. | Dec 2010 | A1 |
| 20100331656 | Mensinger et al. | Dec 2010 | A1 |
| 20110009727 | Mensinger et al. | Jan 2011 | A1 |
| 20110124996 | Reinke et al. | May 2011 | A1 |
| 20110178462 | Moberg | Jul 2011 | A1 |
| 20110184343 | Veit et al. | Jul 2011 | A1 |
| 20110191343 | Heaton et al. | Aug 2011 | A1 |
| 20110201911 | Johnson et al. | Aug 2011 | A1 |
| 20110270158 | Brauker et al. | Nov 2011 | A1 |
| 20110275986 | Bashan et al. | Nov 2011 | A1 |
| 20110281791 | Zion et al. | Nov 2011 | A1 |
| 20110282409 | Ternes et al. | Nov 2011 | A1 |
| 20110295215 | Nielsen et al. | Dec 2011 | A1 |
| 20110313350 | Krulevitch et al. | Dec 2011 | A1 |
| 20110313395 | Krulevitch et al. | Dec 2011 | A1 |
| 20120046606 | Arefieg | Feb 2012 | A1 |
| 20120072236 | Atkin | Mar 2012 | A1 |
| 20120078665 | Johnson et al. | Mar 2012 | A1 |
| 20120165746 | Harms et al. | Jun 2012 | A1 |
| 20120186581 | Brauker et al. | Jul 2012 | A1 |
| 20120190953 | Brauker et al. | Jul 2012 | A1 |
| 20120191063 | Brauker et al. | Jul 2012 | A1 |
| 20120215201 | Brauker et al. | Aug 2012 | A1 |
| 20120220979 | Brauker et al. | Aug 2012 | A1 |
| 20120238852 | Brauker et al. | Sep 2012 | A1 |
| 20120238853 | Arefieg | Sep 2012 | A1 |
| 20120271557 | Sekimoto et al. | Oct 2012 | A1 |
| 20120296311 | Brauker et al. | Nov 2012 | A1 |
| 20130004844 | Hosoe et al. | Jan 2013 | A1 |
| 20130030841 | Bergstrom et al. | Jan 2013 | A1 |
| 20130035575 | Mayou et al. | Feb 2013 | A1 |
| 20130035865 | Mayou et al. | Feb 2013 | A1 |
| 20130035871 | Mayou et al. | Feb 2013 | A1 |
| 20130047084 | Sanders et al. | Feb 2013 | A1 |
| 20130171938 | Mears et al. | Jul 2013 | A1 |
| 20130184996 | Zivitz et al. | Jul 2013 | A1 |
| 20130197479 | Butler et al. | Aug 2013 | A1 |
| 20130211248 | Cowan et al. | Aug 2013 | A1 |
| 20130291116 | Homer | Oct 2013 | A1 |
| 20130298063 | Joy et al. | Nov 2013 | A1 |
| 20130310756 | Whalley et al. | Nov 2013 | A1 |
| 20130331659 | Koski et al. | Dec 2013 | A1 |
| 20130338453 | Duke et al. | Dec 2013 | A1 |
| 20140012117 | Mensinger et al. | Jan 2014 | A1 |
| 20140012118 | Mensinger et al. | Jan 2014 | A1 |
| 20140012510 | Mensinger et al. | Jan 2014 | A1 |
| 20140012511 | Mensinger et al. | Jan 2014 | A1 |
| 20140018733 | Sjolund et al. | Jan 2014 | A1 |
| 20140019396 | Carlsgaard et al. | Jan 2014 | A1 |
| 20140025400 | Galley et al. | Jan 2014 | A1 |
| 20140058749 | Galley et al. | Feb 2014 | A1 |
| 20140068487 | Steiger et al. | Mar 2014 | A1 |
| 20140074041 | Pedersen et al. | Mar 2014 | A1 |
| 20140091941 | Johnson et al. | Apr 2014 | A1 |
| 20140113856 | Pohl et al. | Apr 2014 | A1 |
| 20140114161 | Kamath et al. | Apr 2014 | A1 |
| 20140128705 | Mazlish | May 2014 | A1 |
| 20140148659 | Sloan et al. | May 2014 | A1 |
| 20140187889 | Cohen et al. | Jul 2014 | A1 |
| 20140200426 | Taub et al. | Jul 2014 | A1 |
| 20140207080 | Allerdings | Jul 2014 | A1 |
| 20140257065 | Brister et al. | Sep 2014 | A1 |
| 20140276531 | Walsh | Sep 2014 | A1 |
| 20140288494 | Brister et al. | Sep 2014 | A1 |
| 20140309615 | Mazlish | Oct 2014 | A1 |
| 20140324020 | Stefansen | Oct 2014 | A1 |
| 20140371682 | Bengtsson et al. | Dec 2014 | A1 |
| 20150018770 | Baran et al. | Jan 2015 | A1 |
| 20150073337 | Saint et al. | Mar 2015 | A1 |
| 20150151050 | Estes | Jun 2015 | A1 |
| 20150164415 | Bashan | Jun 2015 | A1 |
| 20150193595 | McNamara et al. | Jul 2015 | A1 |
| 20150202375 | Schabbach et al. | Jul 2015 | A1 |
| 20150202377 | Haupt | Jul 2015 | A1 |
| 20150205947 | Berman et al. | Jul 2015 | A1 |
| 20150246179 | Zur et al. | Sep 2015 | A1 |
| 20150260726 | Refvik | Sep 2015 | A1 |
| 20150289823 | Rack-Gomer et al. | Oct 2015 | A1 |
| 20150290396 | Nagar et al. | Oct 2015 | A1 |
| 20150306304 | Schabbach et al. | Oct 2015 | A1 |
| 20150350147 | Shepherd et al. | Dec 2015 | A1 |
| 20150351683 | Brauker et al. | Dec 2015 | A1 |
| 20150356273 | Cave | Dec 2015 | A1 |
| 20150359490 | Massey et al. | Dec 2015 | A1 |
| 20150359965 | O'Connor et al. | Dec 2015 | A1 |
| 20160030673 | White et al. | Feb 2016 | A1 |
| 20160030679 | Nielsen et al. | Feb 2016 | A1 |
| 20160030680 | Veasey et al. | Feb 2016 | A1 |
| 20160030683 | Taylor et al. | Feb 2016 | A1 |
| 20160038675 | Estes et al. | Feb 2016 | A1 |
| 20160047685 | Blei et al. | Feb 2016 | A1 |
| 20160047743 | Blei et al. | Feb 2016 | A1 |
| 20160051760 | Krusell et al. | Feb 2016 | A1 |
| 20160065799 | Haupt et al. | Mar 2016 | A1 |
| 20160066843 | Mensinger et al. | Mar 2016 | A1 |
| 20160081632 | Kamath et al. | Mar 2016 | A1 |
| 20160082192 | Veasey et al. | Mar 2016 | A1 |
| 20160101232 | Kamath et al. | Apr 2016 | A1 |
| 20160101234 | Bock et al. | Apr 2016 | A1 |
| 20160106927 | Moeller et al. | Apr 2016 | A1 |
| 20160113558 | Bhavaraju et al. | Apr 2016 | A1 |
| 20160117481 | Booth et al. | Apr 2016 | A1 |
| 20160155081 | Legisa et al. | Jun 2016 | A1 |
| 20160213848 | Whalley et al. | Jul 2016 | A1 |
| 20160223380 | Whalley et al. | Aug 2016 | A1 |
| 20160235925 | Kuhn et al. | Aug 2016 | A1 |
| 20160263327 | Radmer et al. | Sep 2016 | A1 |
| 20160266752 | Wu et al. | Sep 2016 | A1 |
| 20160287804 | Madsen et al. | Oct 2016 | A1 |
| 20160287807 | Madsen et al. | Oct 2016 | A1 |
| 20160324463 | Simpson et al. | Nov 2016 | A1 |
| 20170053101 | Booth et al. | Feb 2017 | A1 |
| 20170053552 | Zhong et al. | Feb 2017 | A1 |
| 20170068799 | Messinger et al. | Mar 2017 | A1 |
| 20170103175 | Chopra et al. | Apr 2017 | A1 |
| 20170106052 | Spat | Apr 2017 | A1 |
| 20170124275 | Reihman et al. | May 2017 | A1 |
| 20170131993 | Salameh et al. | May 2017 | A1 |
| 20170132120 | Salameh et al. | May 2017 | A1 |
| 20170132392 | Gerken | May 2017 | A1 |
| 20170138769 | Jones et al. | May 2017 | A1 |
| 20170139974 | Javed et al. | May 2017 | A1 |
| 20170151390 | Muller-Pathle | Jun 2017 | A1 |
| 20170173261 | O'Connor | Jun 2017 | A1 |
| 20170181645 | Mahalingam et al. | Jun 2017 | A1 |
| 20170181678 | Newberry | Jun 2017 | A1 |
| 20170182258 | Michael | Jun 2017 | A1 |
| 20170185283 | Bhavaraju et al. | Jun 2017 | A1 |
| 20170185284 | Bhavaraju et al. | Jun 2017 | A1 |
| 20170189615 | Estes | Jul 2017 | A1 |
| 20170189616 | Bengtsson et al. | Jul 2017 | A1 |
| 20170189625 | Cirillo et al. | Jul 2017 | A1 |
| 20170215811 | Newberry | Aug 2017 | A1 |
| 20170216518 | Davis et al. | Aug 2017 | A1 |
| 20170216524 | Haider et al. | Aug 2017 | A1 |
| 20170219486 | Blei et al. | Aug 2017 | A1 |
| 20170220751 | Davis | Aug 2017 | A1 |
| 20170224922 | Lepple-Wienhues | Aug 2017 | A1 |
| 20170224927 | Windum et al. | Aug 2017 | A1 |
| 20170228518 | Booth | Aug 2017 | A1 |
| 20170232203 | Krusell | Aug 2017 | A1 |
| 20170235919 | Bauss et al. | Aug 2017 | A1 |
| 20170235920 | Bauss et al. | Aug 2017 | A1 |
| 20170251982 | Koehler et al. | Sep 2017 | A1 |
| 20170266389 | McLoughlin et al. | Sep 2017 | A1 |
| 20170270276 | Saint et al. | Sep 2017 | A1 |
| 20170270829 | Bauss | Sep 2017 | A1 |
| 20170286194 | Morris et al. | Oct 2017 | A1 |
| 20170286614 | Morris et al. | Oct 2017 | A1 |
| 20170286638 | Searle et al. | Oct 2017 | A1 |
| 20170304538 | Renstad et al. | Oct 2017 | A1 |
| 20170304541 | Bauss et al. | Oct 2017 | A1 |
| 20170304552 | Prager | Oct 2017 | A1 |
| 20170312446 | Kunz et al. | Nov 2017 | A1 |
| 20170316178 | Riedel et al. | Nov 2017 | A1 |
| 20170338864 | Rolsted et al. | Nov 2017 | A1 |
| 20170340808 | Andersen et al. | Nov 2017 | A1 |
| 20170340826 | Draper | Nov 2017 | A1 |
| 20170351842 | Booth et al. | Dec 2017 | A1 |
| 20170366617 | Mensinger et al. | Dec 2017 | A1 |
| 20170367627 | Brister et al. | Dec 2017 | A1 |
| 20170368263 | Ploch | Dec 2017 | A1 |
| 20170368265 | Groeschke et al. | Dec 2017 | A1 |
| 20180001027 | Klemm et al. | Jan 2018 | A1 |
| 20180008773 | Hautaviita et al. | Jan 2018 | A1 |
| 20180008778 | Erbstein | Jan 2018 | A1 |
| 20180008779 | Hautaviita et al. | Jan 2018 | A1 |
| 20180028759 | Riedel et al. | Feb 2018 | A1 |
| 20180028760 | Gugl et al. | Feb 2018 | A1 |
| 20180036484 | Andersen | Feb 2018 | A1 |
| 20180036495 | Searle et al. | Feb 2018 | A1 |
| 20180042559 | Cabrera et al. | Feb 2018 | A1 |
| 20180043104 | Mueller Pathle | Feb 2018 | A1 |
| 20180050157 | Whalley et al. | Feb 2018 | A1 |
| 20180060008 | Bender et al. | Mar 2018 | A1 |
| 20180064879 | Sall et al. | Mar 2018 | A1 |
| 20180085532 | Desborough | Mar 2018 | A1 |
| 20180099084 | Schabbach et al. | Apr 2018 | A1 |
| 20180103879 | Masciotti et al. | Apr 2018 | A1 |
| 20180121630 | Portnoy | May 2018 | A1 |
| 20180147362 | Arenas et al. | May 2018 | A1 |
| 20180154086 | Toporek et al. | Jun 2018 | A1 |
| 20180161505 | Prager | Jun 2018 | A1 |
| 20180185587 | Brauker et al. | Jul 2018 | A1 |
| 20180217917 | Hayter et al. | Aug 2018 | A1 |
| 20180221582 | Klemm et al. | Aug 2018 | A1 |
| 20180224315 | Schabbacha et al. | Aug 2018 | A1 |
| 20180226150 | Hayter et al. | Aug 2018 | A1 |
| 20180228977 | Schabbach et al. | Aug 2018 | A1 |
| 20180236172 | Schabbach et al. | Aug 2018 | A1 |
| 20180236185 | Sall et al. | Aug 2018 | A1 |
| 20180243504 | Scott et al. | Aug 2018 | A1 |
| 20180268236 | Klemm | Sep 2018 | A1 |
| 20180272072 | Radmer et al. | Sep 2018 | A1 |
| 20180277246 | Zhong et al. | Sep 2018 | A1 |
| 20180289901 | Bggild-Damkvist et al. | Oct 2018 | A1 |
| 20180296767 | Daniel | Oct 2018 | A1 |
| 20180303417 | Mensinger et al. | Oct 2018 | A1 |
| 20180304028 | Riedel | Oct 2018 | A1 |
| 20180326164 | Bauss et al. | Nov 2018 | A1 |
| 20180339113 | Wendland et al. | Nov 2018 | A1 |
| 20180341826 | Allerdings et al. | Nov 2018 | A1 |
| 20180353694 | Riedel et al. | Dec 2018 | A1 |
| 20180353698 | Saint | Dec 2018 | A1 |
| 20180353699 | Helmer et al. | Dec 2018 | A1 |
| 20180353700 | Sall et al. | Dec 2018 | A1 |
| 20180361067 | Sall et al. | Dec 2018 | A1 |
| 20180361076 | Klemm et al. | Dec 2018 | A1 |
| 20180361082 | Sall et al. | Dec 2018 | A1 |
| 20180368683 | Hu et al. | Dec 2018 | A1 |
| 20180369479 | Hayter et al. | Dec 2018 | A1 |
| 20180369488 | Carlsson et al. | Dec 2018 | A1 |
| 20180369490 | Rehbein et al. | Dec 2018 | A1 |
| 20190001060 | Gylleby et al. | Jan 2019 | A1 |
| 20190001069 | Carlsson et al. | Jan 2019 | A1 |
| 20190009032 | Hautaviita et al. | Jan 2019 | A1 |
| 20190015020 | Brister et al. | Jan 2019 | A1 |
| 20190015596 | Saint et al. | Jan 2019 | A1 |
| 20190022320 | Carlsson et al. | Jan 2019 | A1 |
| 20190029590 | Baran et al. | Jan 2019 | A1 |
| 20190030250 | Steel et al. | Jan 2019 | A1 |
| 20190035500 | Saint et al. | Jan 2019 | A1 |
| 20190076070 | Nogueira et al. | Mar 2019 | A1 |
| 20190125224 | Kamath et al. | May 2019 | A1 |
| 20190125969 | Montgomery et al. | May 2019 | A1 |
| 20190132801 | Kamath et al. | May 2019 | A1 |
| 20190149887 | Williams et al. | May 2019 | A1 |
| 20190173885 | Kamath et al. | Jun 2019 | A1 |
| 20190175833 | Sjolund et al. | Jun 2019 | A1 |
| 20190175841 | Sjolund et al. | Jun 2019 | A1 |
| 20190183434 | Sjolund et al. | Jun 2019 | A1 |
| 20190184092 | Sjolund et al. | Jun 2019 | A1 |
| 20190184093 | Sjolund et al. | Jun 2019 | A1 |
| 20190184094 | Sjolund et al. | Jun 2019 | A1 |
| 20190184107 | Sjolund et al. | Jun 2019 | A1 |
| 20190184108 | Sjolund et al. | Jun 2019 | A1 |
| 20190184109 | Sjolund et al. | Jun 2019 | A1 |
| 20190184111 | Sjolund et al. | Jun 2019 | A1 |
| 20190192071 | Taub et al. | Jun 2019 | A1 |
| 20190237181 | Steinberg | Aug 2019 | A1 |
| 20190239825 | Kumar et al. | Aug 2019 | A1 |
| 20190282141 | Causey et al. | Sep 2019 | A1 |
| 20200016336 | Patek et al. | Jan 2020 | A1 |
| 20200205724 | Lee et al. | Jul 2020 | A1 |
| 20200350052 | Saint et al. | Nov 2020 | A1 |
| 20200360794 | Intonato et al. | Nov 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 2925458 | Apr 2015 | CA |
| 0298067 | Jan 1989 | EP |
| 0513128 | Nov 1992 | EP |
| 0927057 | Jul 1999 | EP |
| 1571582 | Sep 2005 | EP |
| 1680175 | Jul 2006 | EP |
| 2401011 | Jan 2012 | EP |
| 2572740 | Mar 2013 | EP |
| 2767297 | Aug 2014 | EP |
| 2911717 | Sep 2015 | EP |
| 2926846 | Oct 2015 | EP |
| 3049132 | Aug 2016 | EP |
| 2879740 | Mar 2017 | EP |
| 3167393 | May 2017 | EP |
| 6058673 | Jan 2017 | JP |
| WO-8502544 | Jun 1985 | WO |
| 9110460 | Jul 1991 | WO |
| 9638190 | Dec 1996 | WO |
| 9810813 | Mar 1998 | WO |
| 2005046559 | May 2005 | WO |
| 2010037828 | Apr 2010 | WO |
| 2010052275 | May 2010 | WO |
| 2010056718 | May 2010 | WO |
| 2010098927 | Sep 2010 | WO |
| 2011041007 | Apr 2011 | WO |
| 2011091238 | Jul 2011 | WO |
| 2012046199 | Apr 2012 | WO |
| 2013004844 | Jan 2013 | WO |
| 2013053695 | Apr 2013 | WO |
| 2014029621 | Feb 2014 | WO |
| 2014064691 | May 2014 | WO |
| 2014020010 | Jun 2014 | WO |
| 2014128157 | Aug 2014 | WO |
| 2015047870 | Apr 2015 | WO |
| 2015169814 | Nov 2015 | WO |
| 2015185686 | Dec 2015 | WO |
| 2016004210 | Jan 2016 | WO |
| 2016019192 | Feb 2016 | WO |
| WO-2016019192 | Feb 2016 | WO |
| 2016007935 | Apr 2016 | WO |
| 2016071912 | May 2016 | WO |
| 2017123523 | Aug 2017 | WO |
| 2017132577 | Aug 2017 | WO |
| Entry |
|---|
| “Calculating Insulin Dose.” Diabetes Education Online, University of California, San Francisco, dtc.ucsf.edu/types-of-diabetes/type2/treatment-of-type-2-diabetes/medications-and-therapies/type-2-insulin-rx/calculating-insulin-dose/. Retrieved Nov. 2020. |
| “Calculating Insulin Dose.” Diabetes Education Online, University of California, San Francisco, https://web.archive.org/web/20110711172015/dtc.ucsf.edu/types-of-diabetes/type2/treatment-of-type-2-diabetes/medications-and-therapies/type-2-insulin-rx/calculating-insulin-dose/. Retrieved Feb. 2021. (Year: 2011). |
| Near Field Communication versus Bluetooth, Jan. 3, 2016, NearFieldCommunication.org via web.archive.org (Year: 2016). |
| International Search Report from International Application No. PCT/US2018/0065069, dated Mar. 25, 2019, 5 pages. |
| International Written Opinion from International Application No. PCT/US2018/0065069, dated Mar. 25, 2019, 11 pages. |
| Baker, New Technologies for Diabetes, Mar. 25, 2017, XP055568829, 76, https://diabetes-education.com/wp-content/uploads/2017/03/Baker-HCP3.pdf. |
| Hu et al., An Improved PID Algorithm Based on Insulin-on-Board Estimate for Blood Glucose Control with Type 1 Diabetes, Jan. 1, 2015, Computational and Mathematical Methods in Medicine, 1-8, 2015. |
| White, Common Sensing, May 2, 2017, XP055568837, 15, Mar. 13, 2019. |
| Sara Krugman, Bionic Pancreas User Interface (¾): Interface Details, Tidepool.org, Jul. 20, 2015. |
| T:slimx2 Insulin Pump User Guide, Tandem Diabetes Care, Jul. 22, 2016. |
| Cision PR News Wire, “Companion Medical Announces Insights by InPen, the Future of MDI Reports”, Jun. 20, 2018. |
| Number | Date | Country | |
|---|---|---|---|
| 20190184091 A1 | Jun 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62682872 | Jun 2018 | US | |
| 62628808 | Feb 2018 | US | |
| 62597809 | Dec 2017 | US | |
| 62597868 | Dec 2017 | US |
