Patent Grant
11628251
The disclosed examples generally relate to medication delivery. More particularly, the disclosed examples relate to techniques, processes, devices or systems for managing operation of a wearable drug delivery device based on detected activity levels of a user, detected locations of the user, or learned behavior of the user.
Many conventional wearable drug delivery devices may include settings that allow for temporary adjustments to regular insulin delivery. The setting may include a setting that permits the suspension of delivery of insulin. These conventional drug delivery devices, however, may not enable adjusting the delivery of insulin, either automatically or through manual instruction, based on increased activity levels of the user or detected periods of increased insulin requirements.
Accordingly, there is a need for a wearable drug delivery device that may adjust insulin delivery based on manual request or automatically during detected increases in or expected increased activity levels of the user or based on detected locations of the user where adjustments to delivery were previously implemented.
Disclosed is a wearable drug delivery device. The disclosed wearable drug delivery device is operable to deliver insulin to a user. The wearable drug delivery device includes a reservoir, a pump mechanism, an inertial measurement unit, and a controller. The reservoir configured to store insulin. The pump mechanism is coupled to the reservoir and operable to expel the stored insulin from the reservoir. The inertial measurement unit is operable to detect an activity level of the user. The controller is communicatively coupled to the pump mechanism and the inertial measurement unit. The controller, when in an activity mode of operation, is operable to receive an input from the inertial measurement unit, wherein the input indicates one or more measurements of motion. The controller may determine, from the received input, an activity level change. Based on the determined activity level change, the controller may modify an amount of insulin to be delivered by the pump mechanism. The controller may output a signal to the pump mechanism actuating delivery of the modified amount of insulin.
Disclosed is a non-transitory computer readable medium embodied with programming code executable by a processor, and the processor when executing the programming code is operable to perform functions. The functions performed by the processor include receiving inputs associated with an activity mode. The processor may evaluate the received inputs with reference to activity mode thresholds and determine whether the evaluated inputs exceed the activity mode thresholds. In response to the evaluated inputs exceeding the activity mode thresholds, the processor initiates the activity mode. Based on initiation of the activity mode, the processor may adjust parameters of a diabetes treatment plan. The processor may actuate delivery of insulin via a pump mechanism according to the adjusted parameters of the diabetes treatment plan.
This disclosure presents various systems, components, and methods operable to adjust insulin delivery to a user based on an available activity mode of operation of a drug delivery device worn by the user. Each of the systems, components, and methods disclosed herein provides one or more advantages over conventional systems, components, and methods.
An example provides a process that may be used with any additional algorithms or computer applications that manage blood glucose levels and insulin therapy. As discussed herein, the algorithms may be referred to as an “artificial pancreas” algorithm-based system, or more generally, an artificial pancreas (AP) application. An AP application may be programming code stored in a memory device and that is executable by a processor, controller or computer device, such as a smart phone, tablet, personal diabetes management device or the like. Examples of artificial pancreas (AP) application as discussed herein provide automatic delivery of an insulin based on inputs from a blood glucose sensor input, such as that received from a CGM or the like, an inertial measurement unit (IMU), global positioning system devices and the like.
In an example, the artificial pancreas (AP) application when executed by a processor may enable a system to monitor a user's glucose values, determine an appropriate level of insulin for the user based on the monitored glucose values (e.g., blood glucose concentrations or blood glucose measurement values) and other information, such as user-provided information, such as carbohydrate intake, meal times or the like, and take actions to maintain a user's blood glucose value within an appropriate range. The appropriate blood glucose value range may be considered a target blood glucose value of the particular user. For example, a target blood glucose value may be acceptable if it falls within the range of 80 mg/dL to 140 mg/dL, which is a range satisfying the clinical standard of care for treatment of diabetes. However, an AP application as described herein may account for an activity level of a user to more precisely establish a target blood glucose value and may set the target blood glucose value at, for example, 110 mg/dL, or the like. As described in more detail with reference to the examples of
As shown in the example, the controller 102 may receive a desired blood glucose (BG) level signal 110, which may be a first signal, indicating a desired blood glucose (BG) level or range for a user. The desired BG level signal 110 may be received from a user interface to the controller or other device, or by an algorithm that automatically determines a BG level for a user. The sensor 108 may be coupled to the user and be operable to measure an approximate value of a BG level of the user. The measured BG value, the measured BG level, the measured BG level value, or the approximate measured value of the actual BG level are only approximate values of a user's BG level and it should be understood that there may be errors in the measured BG levels or values. The errors may, for example, be attributable to a number of factors such as age of the sensor 108, location of the sensor 108 on a body of a user, environmental factors (e.g., altitude, humidity, barometric pressure), or the like. The terms measured BG value and approximate measured value of the BG level may be used interchangeably throughout the specification and drawings. In response to the measured BG level or value, the sensor 108 generate a signal indicating the measured BG value. As shown in the example, the controller 102 may also receive from the sensor 108 via a communication path, a measured BG level signal 112, which may be a second signal, indicating an approximate measured value of the measured BG level of the user.
Based on the desired BG level signal 110 and the measured BG level signal 112, the controller 102 may generate one or more control signals 114 for directing operation of the pump 104. For example, one of the control signals 114 may cause the pump 104 to deliver a specified amount of insulin 116 to a user via output 106. The specified amount of insulin 116 may, for example, be determined based on a difference between the desired BG level signal 110 and the actual BG signal level 112. The specified amount of insulin may be determined as an appropriate amount of insulin to drive the measured BG level of the user to the desired BG level. Based on operation of the pump 104 as determined by the control signals 114, the user may receive the insulin 116 from the pump 104.
The AP system 100 may operate as a closed-loop system or may operate as an open-loop system. In various examples, one or more components of the AP system 100 may be incorporated into a wearable or on body drug delivery system that is attached to the user.
The simplified block diagram of the example AP system 100 provides a general illustration of the operation of the system. An example of a more detailed implementation of devices usable in such an AP system is illustrated in
Various examples of an AP system include a wearable drug delivery device that may operate in the system to manage treatment of a diabetic user according to a diabetes treatment plan. The diabetes treatment plan may include a number of parameters related to the delivery of insulin that may be determined and modified by a computer application referred to as an AP application.
A wearable drug delivery device as described herein may include a controller operable to direct operation of the wearable drug delivery device via the AP application. For example, a controller of the wearable drug delivery device may provide a selectable activity mode of operation for the user. Operation of the drug delivery device in the activity mode of operation may reduce a probability of hypoglycemia during times of increased insulin sensitivity for the user and may reduce a probability of hyperglycemia during times of increased insulin requirements for the user. The activity mode of operation may be activated by the user or may be activated automatically by the controller. The controller may automatically activate the activity mode of operation based on a detected activity level of the user and/or a detected location of the user.
In the example of
The needle deployment component 228 may, for example include a needle (not shown), a cannula (not shown), and any other fluid path components for coupling the stored liquid drug in the reservoir 225 to the user. The cannula may form a portion of the fluid path component coupling the user to the reservoir 225. After the needle deployment component 228 has been activated, a fluid path (not shown) to the user is provided, and the pump mechanism 224 may expel the liquid drug from the reservoir 225 to deliver the liquid drug to the user via the fluid path. The fluid path may, for example, include tubing (not shown) coupling the wearable drug delivery device 202 to the user (e.g., tubing coupling the cannula to the reservoir 225).
The wearable drug delivery device 202 may further include a controller 221 and a communications interface device 226. The controller 221 may be implemented in hardware, software, or any combination thereof. The controller 221 may, for example, be a processor, a logic circuit or a microcontroller coupled to a memory. The controller 221 may maintain a date and time as well as other functions (e.g., calculations or the like) performed by processors. The controller 221 may be operable to execute an artificial pancreas algorithm stored in the memory that enables the controller 221 to direct operation of the drug delivery device 202. In addition, the controller 221 may be operable to receive data or information indicative of the activity of the user from the IMU 207, as well as from any other sensors (such as those (e.g., accelerometer, location services application or the like) on the management device 206 or CGM 204) of the drug delivery device 202 or any sensor coupled thereto, such as a global positioning system (GPS)-enabled device or the like.
The controller 221 may process the data from the IMU 207 or any other coupled sensor to determine if an alert or other communication is to be issued to the user and/or a caregiver of the user or if an operational mode of the drug delivery device 202 is to be adjusted. The controller 221 may provide the alert, for example, through the communications interface device 226. The communications interface device 226 may provide a communications link to one or more management devices physically separated from the drug delivery device 202 including, for example, a management device 206 of the user and/or a caregiver of the user (e.g., a parent). The communication link provided by the communications interface device 226 may include any wired or wireless communication link operating according to any known communications protocol or standard, such as Bluetooth or a cellular standard.
The example of
The management device 206 may be maintained and operated by the user or a caregiver of the user. The management device 206 may control operation of the drug delivery device 202 and/or may be used to review data or other information indicative of an operational status of the drug delivery device 202 or a status of the user. The management device 206 may be used to direct operations of the drug delivery device 202. For example, the management device 206 may be a dedicated personal diabetes management (PDM) device, a smart phone, a tablet computing device, other consumer electronic device including, for example, a desktop, laptop, or tablet, or the like. The management device 206 may include a processor 261 and memory devices 263. The memory devices 262 may store an artificial pancreas application 269 including programming code that may implement the activity mode, the hyperglycemia protection mode, and/or the hypoglycemia protection mode. The management device 206 may receive alerts, notifications, or other communications from the drug delivery device 202 via one or more known wired or wireless communications standard or protocol.
The drug delivery system 200 may be operable to implement an AP application that includes functionality to determine a movement of a wearable drug delivery device that is indicative of physical activity of the user, implement an activity mode, a hyperglycemia mode, a hypoglycemia mode, and other functions, such as control of the wearable drug delivery device. The drug delivery system 200 may be an automated drug delivery system that may include a wearable drug delivery device (pump) 202, a sensor 204, and a personal diabetes management device (PDM) 206.
In an example, the wearable drug delivery device 202 may be attached to the body of a user, such as a patient or diabetic, and may deliver any therapeutic agent, including any drug or medicine, such as insulin or the like, to a user. The wearable drug delivery device 202 may, for example, be a wearable device worn by the user. For example, the wearable drug delivery device 202 may be directly coupled to a user (e.g., directly attached to a body part and/or skin of the user via an adhesive or the like). In an example, a surface of the wearable drug delivery device 202 may include an adhesive to facilitate attachment to a user.
The wearable drug delivery device 202 may frequently be referred to as a pump, or an insulin pump, in reference to the operation of expelling a drug from the reservoir 225 for delivery of the drug to the user.
In an example, the wearable drug delivery device 202 may include a reservoir 225 for storing the drug (such as insulin), a needle or cannula (not shown) for delivering the drug into the body of the user (which may be done subcutaneously, intraperitoneally, or intravenously), and a pump mechanism (mech.) 224, or other drive mechanism, for transferring the drug from the reservoir 225, through a needle or cannula (not shown), and into the user. The reservoir 225 may be configured to store or hold a liquid or fluid, such as insulin, morphine, or another therapeutic drug. The pump mechanism 224 may be fluidly coupled to reservoir 225, and communicatively coupled to the controller 221. The wearable drug delivery device 202 may also include a power source (not shown), such as a battery, a piezoelectric device, or the like, for supplying electrical power to the pump mechanism 224 and/or other components (such as the controller 221, memory 223, and the communication device 226) of the wearable drug delivery device 202. Although also not shown, an electrical power supply for supplying electrical power may similarly be included in each of the sensor 204, the smart accessory device (if present), and the management device (PDM) 206.
In an example, the blood glucose sensor 204 may be a device communicatively coupled to the processor 261 or 221 and may be operable to measure a blood glucose value at a predetermined time interval, such as approximately every 5 minutes, or the like. The blood glucose sensor 204 may provide a number of blood glucose measurement values to the AP applications operating on the respective devices. For example, the blood glucose sensor 204 may be a continuous blood glucose sensor that provides blood glucose measurement values to the AP applications operating on the respective devices periodically, such as approximately every 5, 10, 12 minutes, or the like.
The wearable drug delivery device 202 may also include the IMU 207. The IMU 207 may be operable to detect various motion parameters (e.g., acceleration, deceleration, speed, orientation, such as roll, pitch, yaw, compass direction, or the like) that may be indicative of the activity of the user. For example, the IMU 207 may output signals in response to detecting motion of the wearable drug delivery device 202 that is indicative of a status of any physical condition of the user, such as, for example, a motion or position of the user. Based on the detected activity of the user, the drug delivery device 202 may adjust operation related to drug delivery, for example, by implementing an activity mode as discussed herein.
The wearable drug delivery device 202 may when operating in a normal mode of operation may provide insulin stored in reservoir 225 to the user based on information (e.g., blood glucose measurement values, inputs from an inertial measurement unit, global positioning system-enabled devices, Wi-Fi-enabled devices, or the like) provided by the sensor 204 and/or the management device (PDM) 206.
For example, the wearable drug delivery device 202 may contain analog and/or digital circuitry that may be implemented as a controller 221 (or processor) for controlling the delivery of the drug or therapeutic agent. The circuitry used to implement the controller 221 may include discrete, specialized logic and/or components, an application-specific integrated circuit, a microcontroller or processor that executes software instructions, firmware, programming instructions or programming code (enabling, for example, the artificial pancreas application (AP App) 229 as well as the process examples of
The devices in the system 200, such as management device 206, wearable drug delivery device 202, and sensor 204, may also be operable to perform various functions including controlling the wearable drug delivery device 202. For example, the management device 206 may include a communication device 264, a processor 261, and a management device memory 263. The management device memory 263 may store an instance of the AP application 269 that includes programming code, that when executed by the processor 261 provides the process examples described with reference to the examples of
Although not shown, the system 200 may include a smart accessory device may be, for example, an Apple Watch®, other wearable smart device, including eyeglasses, provided by other manufacturers, a global positioning system-enabled wearable, a wearable fitness device, smart clothing, or the like. Similar to the management device 206, the smart accessory device (not shown) may also be operable to perform various functions including controlling the wearable drug delivery device 202. For example, the smart accessory device may include a communication device, a processor, and a memory. The memory may store an instance of the AP application that includes programming code for providing the process examples described with reference to the examples of
The sensor 204 of system 200 may be a continuous glucose monitor (CGM) as described above, that may include a processor 241, a memory 243, a sensing or measuring device 244, and a communication device 246. The memory 243 may store an instance of an AP application 249 as well as other programming code and be operable to store data related to the AP application 249. The AP application 249 may also include programming code for providing the process examples described with reference to the examples of
Instructions for determining the delivery of the drug or therapeutic agent (e.g., as a bolus dosage) to the user (e.g., the size and/or timing of any doses of the drug or therapeutic agent) may originate locally by the wearable drug delivery device 202 or may originate remotely and be provided to the wearable drug delivery device 202. In an example of a local determination of drug or therapeutic agent delivery, programming instructions, such as an instance of the artificial pancreas application 229, stored in the memory 223 that is coupled to the wearable drug delivery device 202 may be used to make determinations by the wearable drug delivery device 202. In addition, the wearable drug delivery device 202 may be operable to communicate via the communication device 226 and communication link 288 with the wearable drug delivery device 202 and with the blood glucose sensor 204 via the communication device 226 and communication link 289.
Alternatively, the remote instructions may be provided to the wearable drug delivery device 202 over a wired or wireless link by the management device (PDM) 206. The PDM 206 may be equipped with a processor 261 that may execute an instance of the artificial pancreas application 269, if present in the memory 263. The wearable drug delivery device 202 may execute any received instructions (originating internally or from the management device 206) for the delivery of insulin to the user. In this way, the delivery of the insulin to a user may be automated.
In various examples, the wearable drug delivery device 202 may communicate via a wireless communication link 288 with the management device 206. The management device 206 may be an electronic device such as, for example, a smart phone, a tablet, a dedicated diabetes therapy management device, or the like. Alternatively, the management device 206 may be a wearable wireless accessory device, such as a smart watch, or the like. The wireless links 287-289 may be any type of wireless link provided by any known wireless standard. As an example, the wireless links 287-289 may enable communications between the wearable drug delivery device 202, the management device 206 and sensor 204 based on, for example, Bluetooth®, Wi-Fi®, a near-field communication standard, a cellular standard, or any other wireless optical or radio-frequency protocol.
The sensor 204 may also be coupled to the user by, for example, adhesive or the like and may provide information or data on one or more medical conditions and/or physical attributes of the user. The information or data provided by the sensor 204 may be used to adjust drug delivery operations of the wearable drug delivery device 202. For example, the sensor 204 may be a glucose sensor operable to measure blood glucose and output a blood glucose value or data that is representative of a blood glucose value. For example, the sensor 204 may be a glucose monitor that provides periodic blood glucose measurements a continuous glucose monitor (CGM), or another type of device or sensor that provides blood glucose measurements.
The sensor 204 may include a processor 241, a memory 243, a sensing/measuring device 244, and communication device 246. The communication device 246 of sensor 204 may include an electronic transmitter, receiver, and/or transceiver for communicating with the management device 206 over a wireless link 222 or with wearable drug delivery device 202 over the link 208. The sensing/measuring device 244 may include one or more sensing elements, such as a blood glucose measurement element, a heart rate monitor, a blood oxygen sensor element, or the like. The processor 241 may include discrete, specialized logic and/or components, an application-specific integrated circuit, a microcontroller or processor that executes software instructions, firmware, programming instructions stored in memory (such as memory 243), or any combination thereof. For example, the memory 243 may store an instance of an AP application 249 that is executable by the processor 241.
Although the sensor 204 is depicted as separate from the wearable drug delivery device 202, in various examples, the sensor 204 and wearable drug delivery device 202 may be incorporated into the same unit. That is, in one or more examples, the sensor 204 may be a part of the wearable drug delivery device 202 and contained within the same housing of the wearable drug delivery device 202 (e.g., the sensor 204 may be positioned within or embedded within the wearable drug delivery device 202). Glucose monitoring data (e.g., measured blood glucose values) determined by the sensor 204 may be provided to the wearable drug delivery device 202 and/or the management device 206, which may use the measured blood glucose values to determine movement of the wearable drug delivery device indicative of physical activity of the user, an activity mode, a hyperglycemia mode and a hyperglycemia mode.
In an example, the management device 206 may be a personal diabetes manager. The management device 206 may be used to program or adjust operation of the wearable drug delivery device 202 and/or the sensor 204. The management device 206 may be any portable electronic device including, for example, a dedicated controller, such as processor 261, a smartphone, or a tablet. In an example, the management device (PDM) 206 may include a processor 261, a management device memory 263, and a communication device 264. The management device 206 may contain analog and/or digital circuitry that may be implemented as a processor 261 (or controller) for executing processes to manage a user's blood glucose levels and for controlling the delivery of the drug or therapeutic agent to the user. The processor 261 may also be operable to execute programming code stored in the management device memory 263. For example, the management device memory 263 may be operable to store an artificial pancreas application 269 that may be executed by the processor 261. The processor 261 may when executing the artificial pancreas application 269 may be operable to perform various functions, such as those described with respect to the examples in
The wearable drug delivery device 202 may communicate with the sensor 204 over a wireless link 208 and may communicate with the management device 206 over a wireless link 220. The sensor 204 and the management device 206 may communicate over a wireless link 222. The smart accessory device, when present, may communicate with the wearable drug delivery device 202, the sensor 204 and the management device 206 over wireless links 287, 288 and 289, respectively. The wireless links 287, 288 and 289 may be any type of wireless link operating using known wireless standards or proprietary standards. As an example, the wireless links 287, 288 and 289 may provide communication links based on Bluetooth®, Wi-Fi, a near-field communication standard, a cellular standard, or any other wireless protocol via the respective communication devices 226, 246 and 264. In some examples, the wearable drug delivery device 202 and/or the management device 206 may include a user interface 227 and 268, respectively, such as a keypad, a touchscreen display, levers, buttons, a microphone, a speaker, a display, or the like, that is operable to allow a user to enter information and allow the management device to output information for presentation to the user.
In various examples, the drug delivery system 200 may be an insulin drug delivery system. For example, the wearable drug delivery device 202 may be the OmniPod® (Insulet Corporation, Billerica, Mass.) insulin delivery device as described in U.S. Pat. Nos. 7,303,549, 7,137,964, or 6,740,059, each of which is incorporated herein by reference in its entirety.
In the examples, the drug delivery system 200 may implement the artificial pancreas (AP) algorithm (and/or provide AP functionality) to govern or control automated delivery of insulin to a user (e.g., to maintain euglycemia—a normal level of glucose in the blood). The AP application may be implemented by the wearable drug delivery device 202 and/or the sensor 204. The AP application may be used to determine the times and dosages of insulin delivery. In various examples, the AP application may determine the times and dosages for delivery based on information known about the user, such as the user's sex, age, weight, or height, and/or on information gathered about a physical attribute or condition of the user (e.g., from the sensor 204). For example, the AP application may determine an appropriate delivery of insulin based on glucose level monitoring of the user through the sensor 204. The AP application may also allow the user to adjust insulin delivery. For example, the AP application may allow a user to select (e.g., via an input) commands for output to the wearable drug delivery device 202, such as a command to set a mode of the wearable drug delivery device, such as an activity mode, a hyperglycemia protect mode, a hypoglycemia protect mode, deliver an insulin bolus, or the like. In one or more examples, different functions of the AP application may be distributed among two or more of the management device 206, the wearable drug delivery device (pump) 202 or the sensor 204. In other examples, the different functions of the AP application may be performed by one device, such the management device 206, the wearable drug delivery device (pump) 202 or the sensor 204. In various examples, the drug delivery system 200 may include features of or may operate according to functionalities of a drug delivery system as described in U.S. patent application Ser. No. 15/359,187, filed Nov. 22, 2016 and Ser. No. 16/570,125, filed Sep. 13, 2019, which are both incorporated herein by reference in their entirety.
As described herein, the drug delivery system 200 or any component thereof, such as the wearable drug delivery device may be considered to provide AP functionality or to implement an AP application. Accordingly, references to the AP application (e.g., functionality, operations, or capabilities thereof) are made for convenience and may refer to and/or include operations and/or functionalities of the drug delivery system 200 or any constituent component thereof (e.g., the wearable drug delivery device 202 and/or the management device 206). The drug delivery system 200—for example, as an insulin delivery system implementing an AP application—may be considered to be a drug delivery system or an AP application-based delivery system that uses sensor inputs (e.g., data collected by the sensor 204).
In an example, the drug delivery device 202 includes a communication device 264, which as described above may be a receiver, a transmitter, or a transceiver that operates according to one or more radio-frequency protocols, such as Bluetooth, Wi-Fi, a near-field communication standard, a cellular standard, that may enable the respective device to communicate with the cloud-based services 211. For example, outputs from the sensor 204 or the wearable drug delivery device (pump) 202 may be transmitted to the cloud-based services 211 for storage or processing via the transceivers of communication device 264. Similarly, wearable drug delivery device 202, management device 206 and sensor 204 may be operable to communicate with the cloud-based services 211 via the communication link 288.
In an example, the respective receiver or transceiver of each respective device 202, 206 or 207 may be operable to receive signals containing respective blood glucose measurement values of the number of blood glucose measurement values that may be transmitted by the sensor 204. The respective processor of each respective device 202, 206 or 207 may be operable to store each of the respective blood glucose measurement values in a respective memory, such as 223, 263 or 273. The respective blood glucose measurement values may be stored as data related to the artificial pancreas algorithm, such as 229, 249, or 269. In a further example, the AP application operating on the management device 206 or sensor 204 may be operable to transmit, via a transceiver implemented by a respective communication device, 264, 274, 246, a control signal for receipt by a wearable drug delivery device. In the example, the control signal may indicate an amount of insulin to be expelled by the wearable drug delivery device 202.
In an example, one or more of the devices 202, 204, or 206 may be operable to communicate via a wired communication links 277, 278 and 279, respectively. The cloud-based services (not shown) may utilize servers and data storage (not shown). A communication link that couples the drug delivery system 200 to the cloud-based services may be a cellular link, a Wi-Fi link, a Bluetooth link, or a combination thereof, that is established between the respective devices 202, 204, or 206 of system 200. For example, the data storage (not shown) provided by the cloud-based services may store anonymized data, such as user weight, blood glucose measurements, age, meal carbohydrate information, or the like. In addition, the cloud-based services 211 may process the anonymized data from multiple users to provide generalized information related to the various parameters used by the AP application. For example, an age-based general target blood glucose value related to activity levels or particular exercises or sports may be derived from the anonymized data, which may be helpful when a user selects an activity mode (or a hyperglycemia protect mode, or a hypoglycemia protect modes) or the system 200 automatically implements the activity mode (or the hyperglycemia protect, or the hypoglycemia protect modes). The cloud-based services may also provide processing services for the system 200, such as performing a process described with reference to later examples.
The wearable drug delivery device 202 may also include a user interface 227. The user interface 227 may include any mechanism for the user to input data to the drug delivery device 202, such as, for example, a button, a knob, a switch, a touch-screen display, or any other user interaction component. The user interface 227 may include any mechanism for the drug delivery device 202 to relay data to the user and may include, for example, a display, a touch-screen display, or any means for providing a visual, audible, or tactile (e.g., vibrational) output (e.g., as an alert). The user interface 227 may also include a number of additional components not specifically shown in
Various operational scenarios and examples of processes performed by the system 200 are described herein. For example, the system 200 may be operable to implement process examples related to an activity mode including a hyperglycemia protect mode and a hypoglycemia protect mode as described in more detail below.
In an example, the drug delivery device 202 may operate as an artificial pancreas (AP) system (e.g., as a portion of the AP system 100) and/or may implement techniques or an algorithm via an AP application that controls and provides functionality related to substantially all aspects of an AP system or at least portions thereof. Accordingly, references herein to an AP system or AP algorithm may refer to techniques or algorithms implemented by an AP application executing on the drug delivery device 202 to provide the features and functionality of an AP system. The drug delivery device 202 may operate in an open-loop or closed-loop manner for providing a user with insulin.
Additional features may be implemented as part of the AP application such as the activity mode, the hyperglycemia mode, the hypoglycemia mode, or the like. For example, the drug delivery device 202 when programming code is executed that enables the activity mode, hyperglycemia mode, hypoglycemia mode or the like of the AP application. As the AP application including the programming code for the activity mode, the hyperglycemia mode, and the hypoglycemia mode is executed, the AP application may adjust operations, such as detecting motion or movement of the wearable drug delivery device that is indicative of physical activity of the user. For example, motion and movement of the wearable drug delivery device 202 that induces motions characteristic of physical activity of the user (e.g., movements, such as jumping, dancing, running, weightlifting, cycling or the like) may be detected by the IMU 207. In addition, the IMU 207, as described in more detail with reference to
In an example, the AP algorithm may learn from repeated interaction with the user who may input an indication at particular times that they are about to perform physical activity. Alternatively, or in addition, the wearable drug delivery device 202 may upon detection of a particular location (e.g., gym, sports field, stadium, track, or the like) determine that the user is about to increase their physical activity. In an operational example, the controller 221 may be operable to receive a location associated with the wearable drug delivery device 202 from the IMU 207 or Wi-Fi location services provided via the communication device 226. The controller may obtain locations of physical activity from the memory 223 and be operable to compare the received location to locations of physical activity obtained from the memory. The controller 221, based on a result of the comparison indicating that the location associated with the wearable drug delivery device is substantially the same as a location in the locations of physical activity obtained from the memory, may indicate that an activity mode threshold has been exceed. In which case, if not having already done so, the controller 221 may initiate an activity mode or a hypoglycemia protect mode.
It may be helpful to describe the number of components included in the IMU 207 that provide motion and movement measurement data or values to the controller 221. An example of an inertial measurement unit (IMU) is shown in
The output connections 307 enable the IMU 302 to be coupled other components of a wearable drug delivery device, such as 202 of
For example, the accelerometer 304 may generate one or more signals indicative of, for example, a detected or measured acceleration force. The magnetometer 306 may generate one or more signals indicative of, for example, a detected or measured magnetic field. The gyroscope 308 may generate one or more signals indicative of, for example, an orientation of the gyroscope 308 or the IMU 302, or a device in which either component is integrated. The signals generated by the accelerometer 304, the magnetometer 306, and the gyroscope 308 may be provided to other components and devices (e.g., the processor or controller 221 of
The IMU 302 may also be equipped with a global positioning system (GPS) component 309 that receives signals from which a location of the IMU 302 may be determined. The determined location may be provided to the controller 221 of the wearable drug delivery device 202 via a communication link 277 or 287 as well as to the processor 261 of the management device 206. In addition, the blood glucose sensor 204, if executing an instance of the AP application, such as 249, may also receive a signal from the GPS 309.
The activity mode component 412 may be additional programming code that may be a plug-in to the AP application 402. The activity mode component 412 may provide functions related to activity mode, such as those mentioned above, that responds to the detection of movement related to physical activity of a user wearing a wearable drug delivery device, such as 202 of
The hyperglycemia protect mode component 414 may provide additional functions, constraints and limits to the insulin dosages provided while the activity mode is initiated to protect a user from having blood glucose measurements that exceed clinically acceptable blood glucose levels (e.g., greater than or approximately equal to 180 mg/dL). Conversely, the hypoglycemia protect mode component 416 may provide additional functions, constraints and limits to the insulin dosages provided while the activity mode is initiated to protect a user from having blood glucose measurements that fall below clinically acceptable blood glucose levels (e.g., less than or approximately equal to 70 mg/dL).
In an example, operation of the AP application may be operable to receive inputs from a user, a blood glucose sensor, such as 204 of
While the foregoing examples described the hardware and software components that may be used to provide an AP application 402 augmented with functionality provided by an activity mode, a hyperglycemia protect mode and a hypoglycemia protect mode, each of the respective modes of operation may present different processes to provide the respective functionality.
The AP application 402 of
As disclosed herein, when the drug delivery device 202 in the example of
For example, the activity mode disclosed herein may be used for reducing the probability of hypoglycemia due to increased insulin sensitivity. In an example, the activity mode disclosed herein may be used to manage general increases of average blood glucose to prevent hypoglycemia during times of high glucose variability. In addition, the activity mode may reduce the probability of hyperglycemia due to increased insulin requirements. The activity mode may also be used to reduce alarm requirements (cause alarms to occur earlier or later) to prevent excessive periods of high glucose concentrations during times of increased insulin resistance by informing the user initiating changes in manual or automatic insulin delivery. In an example, multiple settings of the activity mode (or any additional or sub-mode thereof) may be available to set operation to different degrees of conservativeness or aggressiveness.
In closed loop operation, the AP application may manage a user's diabetes treatment plan using various parameters and functions, such as cost functions and the like, as discussed in described in U.S. patent application Ser. No. 15/359,187, filed Nov. 22, 2016 and Ser. No. 16/570,125, filed Sep. 13, 2019, which are both incorporated herein by reference in their entirety. As an example, a conservative mode of operation may include use of a setpoint equal to approximately 120 to 150 mg/dL, setting a maximum insulin delivery equal to approximately 1 to 3 times the user's basal rate, and setting the input basal to the AP algorithm equal to approximately 50% to 90% of the user's entered basal rate. Alternatively, an aggressive mode of operation may include use of a setpoint equal to approximately 100 to 120 mg/dL, setting a maximum insulin delivery to at most approximately 3 to 6 times the user's basal over approximately 3 to 6 hours, and reducing the hyperglycemia alarm threshold(s) to triggering alarms for any glucose values above approximately 250 to 350 mg/dL for more than approximately 15 minutes to 60 minutes.
In the process 500, the AP application may use settings similar to the above insulin delivery parameters and alarm thresholds as a baseline during daily management of a user's diabetes treatment plan (i.e., without the initiation of activity mode). While the AP application is executing by a processor or controller, such as 221, the AP application may receive inputs associated with the activity mode at 510. The inputs may be received from several different sources including from the controller 221. For example, the AP application executing on the drug delivery device 202 may monitor inputs from the IMU 207, the heart rate monitor 237, and the user interface 227 for signals or indications associated to activity mode. The outputs from the IMU 207 and/or the heart rate monitor 237 may include timestamps so the controller 221 may determine a duration of the physical activity indicated by the received inputs.
Alternatively, at 510, the drug delivery device 202 may, for example, receive via the user interface 227 a selection specifying activation of the activity mode of operation via the user interface 227. Alternatively, the AP application executing on the wearable drug delivery device may determine the occurrence of increased physical activity based on signals indicating, for example, increased heart rate or pulse rate received from the heart rate monitor 237, movement indicators from the IMU 207, or a combination of both.
Based on the signals received from the IMU, heart rate monitor 237 and the user interface, the AP application may evaluate the received inputs to determine whether to initiate the activity mode at 520. In various examples, the evaluation of the received inputs, at 520, may include an evaluation of default values for duration and an intensity level of the physical activity indicated by the received inputs. For example, the AP application may receive an indication of a heart rate over a predetermined threshold, e.g., 50-70 percent of the maximum age-appropriate heart rate or the like, an accelerometer reading indicating motion exceeding a walking pace, gyroscopic readings indicating motion in up/down and lateral directions, or the like for a period of time that exceeds an activity duration threshold. Alternatively, or in addition, the user may specify an amount of time and/or a different activity intensity level when the activity mode of operation is entered manually. For example, the duration of the activity mode of operation may be a timed session (e.g., 1 hour, 2 hours, a common duration of a sports event (e.g., 2.5 hours for a baseball game, or the like) or may be turned off manually by a user or caregiver.
For example, the AP application may evaluate the received inputs against activity mode thresholds stored in a memory, such as 223. The activity mode thresholds may be based on user history accumulated over days, months or years, user preference settings, or as a default, clinical information based on the user's age, weight, height and the like. In another example, the evaluation at 520 may include comparing the monitored indicators to activity mode thresholds set by the user. In various examples, the AP application may automatically initiate the activity mode of operation based on activity of the user detected by the IMU 207.
In an example, the controller 221 may retrieve the activity mode thresholds from a memory, such as 223. The controller 221 may determine a duration of an indication of physical activity. The controller 221 may compare the determined duration of the indication of physical activity to a default duration value from among the retrieved activity mode thresholds. Based on a result of the comparison, the controller 221 may indicate that the duration of the indication of physical activity exceeds an activity mode threshold for duration of physical activity. In response to the indication that the duration of the indication of physical activity exceeds an activity mode threshold for duration of physical activity, output an instruction to initiate activity mode. Alternatively, the activity mode thresholds may be set by a user, who may use default or user specified presets that assign a set of operational parameters that may be varied for an activity.
In another example, the AP application may monitor and access a data storage (e.g., a memory), which may contain a spreadsheet, a calendar, or the like, for scheduling information related to events or physical activity input by a user as either additional received inputs or as the sole received inputs at 510. The scheduling information may include a schedule of physical activity or events in which the user participates or that may affect diabetes management, such as airplane travel, conferences, holidays, or the like that the user is participating in during a period of time (e.g., a day, hour, month, week, or year). The scheduling information may include physical fitness (i.e., exercise) classes, sports events, marathon schedules, travel arrangements, conference dates (and agenda), and the like. The AP application may be operable to access (according to user permissions) the schedule and evaluate scheduled events (e.g., travel, conferences, birthdays) or scheduled physical activity.
After accessing the scheduling information stored in the data storage, the evaluation of the scheduled events or scheduled physical activity by the AP application at 520 may include comparing dates and times with a current time and date maintained by the controller 221. Based on the results of the comparison, identify an event and a scheduled physical activity that a user is participating. The controller 221 executing the AP application may generate an alert, either via the user interface 227 or cause a signal to be transmitted to the management device 206, for presentation of a prompt requesting confirmation of initiation of the activity mode.
The AP application may at 530 determine whether the inputs evaluated at 520 exceed any activity mode thresholds. If the determination is NO, the process 500 may return to 500 and continue. Alternatively, should the AP application determine that YES, the evaluated inputs exceed the activity mode thresholds, the process 500 may proceed with the AP application initiating the activity mode at 540.
In yet another example, the user may also schedule via the user interface 227 activation of the activity mode of operation for a certain future day or time in which case the evaluation at 520 may be whether the physical activity was scheduled in which case the result of the evaluation is that the activity mode threshold is exceeded.
In response to the initiation of the activity mode at 540, the process 500 at step 550 may modify or adjust the diabetes treatment plan. For example, the AP algorithm executing on the drug delivery device 202 may recommend administering or may automatically administer a correction bolus prior to the expected increased period of insulin requirements based on, for example, a scheduled time of event, a determined glucose value, a determined lack of insulin on board, or any combination thereof.
For example, the AP application executed by the controller 221 may adapt or modify and adjust the parameters of a diabetes treatment plan according to the adjusted or modified parameters as the activity mode of operation is implemented multiple times over a period of time based on actual learned patient response to any parameter associated with a particular activity mode of operation. For example, the AP application, while in the activity mode, may continue to receive inputs related to the user's diabetes treatment plan. For example, the received inputs may include determined glucose values, determined glucose rates or change, motion or activity detected by components (shown and described with reference to the example of
At 555, the AP application may, in response to the adjusted parameters of the diabetes treatment plan, cause the controller 221 to actuate the pump mechanism 224 to deliver insulin according to the adjusted diabetes treatment plan (which was adjusted in 550).
In an example, when the AP application utilizes the scheduled events or physical activity to initiate the activity mode, the AP application may look at scheduled events or physical activity that are scheduled in the future (e.g., several hours or the like in the future). In response to evaluating the future scheduled events or physical activity, the AP application may, prior to the occurrence of the scheduled activity or event, initiate activity mode in advance and begin adjusting the diabetes treatment plan. For example, the AP application may determine that the amount of insulin on board (e.g., prior to exercise scheduled for the user) is to be reduced to meet limits established for the user. In a specific example, when an activity may be scheduled to begin, for example, at 10:00 am, the drug delivery device 202 may start the activity mode of operation at, for example, 8:30 am to allow time for the user's blood glucose to elevate and to reduce an amount of insulin on board (i.e., within the body of the user). By starting the activity mode in advance of the scheduled event or physical activity, the AP application may either suspend delivery of insulin or reduce an amount of insulin scheduled to be delivered to allow the amount of insulin on board to diminish and the measured blood glucose value to increase. Alternatively, the scheduled event may be an event for which the increase in insulin resistance is expected. As a result, the AP application executing on the drug delivery device 202 may initiate the activity mode of operation prior to an expected increase in insulin resistance in order to adjust the diabetes treatment plan of the user to increase the amount of insulin on board prior to the event for which the increase in insulin resistance is expected. The foregoing adjustments to the diabetes treatment plan may be in response to monitoring the scheduled events.
The techniques or processes 500 implemented by the AP application related to the activity mode may also implement a hyperglycemia protect mode and a hypoglycemia protect mode. For example, an activity mode may be operable through the hypoglycemia protect mode to reduce the potential for an occurrence of hypoglycemia during periods of increased insulin sensitivity such as, for example, during exercise or other moderate-to-intense physical activity. In addition, the activity mode may, for example, be operable to reduce a likelihood of an occurrence of hyperglycemia during times of increased insulin requirements, such as, for example, when the user is suffering from an illness (stress), is on a long plane flight (environmental conditions associated with air travel such as reduced air pressure that affects glucose monitoring, reduced ability to control diet, and the like), or the like. As an example, a conservative mode of operation may include use of a setpoint equal to approximately 120 to 150 mg/dL, setting a maximum insulin delivery equal to approximately 1 to 3 times the user's basal rate, and setting the input basal to the AP algorithm equal to approximately 50% to 90% of the user's entered basal rate. Alternatively, an aggressive mode of operation may include use of a setpoint equal to approximately 100 to 120 mg/dL, setting a maximum insulin delivery to at most approximately 3 to 6 times the user's basal over approximately 3 to 6 hours, and reducing the hyperglycemia alarm threshold(s) to triggering alarms for any glucose values above approximately 250 to 350 mg/dL for more than approximately 30 minutes.
The activity mode of operation may include or may separately specify a hypoglycemia mode of operation and/or a hyperglycemia mode of operation. When operating in the activity mode, the AP algorithm may also implement the hypoglycemia protection mode of operation and the hyperglycemia protection mode of operation.
At 560, the AP application may process blood glucose measurements received from the blood glucose sensor 204 over time, amounts of insulin delivered over time according to the diabetes treatment plan of the user, and calculate and analyze trends determined related to insulin delivery and the blood glucose measurements. Based on the processing, the AP application may evaluate whether a hyperglycemia protect mode is to be entered, such as if the AP application determines a persistently elevated raw glucose concentration or trend during increasing insulin delivery, or unchanging raw glucose concentration or trend during reduced insulin delivery, or elevated raw glucose value or trend over significant periods of time regardless of insulin delivery, or the like. For example, the AP application may enter hyperglycemia mode in cases where persistently high glucose values are detected even if a significant amount of insulin has been delivered. Based on the result of the evaluation, the AP application may determine that YES, a hyperglycemia protect mode is to be entered and the process 500 proceeds as a precautionary measure to the process shown in
In an operational example, the controller 221 (or a processor) may be operable to receive blood glucose measurements from the blood glucose sensor 204. The controller 221 (or processor) may process the blood glucose measurements. The processing may reveal the blood glucose measurements are increasing toward exceeding a maximum blood glucose set point. The maximum blood glucose set point may be a blood glucose value that the AP application (or the user manually) sets as a maximum upper limit of a blood glucose value for the user. Based on an indication that the blood glucose measurements are increasing toward exceeding the maximum blood glucose set point, the controller may enter the hyperglycemia protect mode. Alternatively, or in addition, the AP application executing on the controller may generate an alarm signal indicating that the blood glucose measurements are increasing toward exceeding the maximum blood glucose set point to enable the user to take remedial action.
Conversely, if the AP application determines, at 560, NO, the hyperglycemia protect mode does not need to be entered and the process 500 proceeds to 570.
At 570, the AP application may process blood glucose measurements received from the blood glucose sensor 204 over time, amounts of insulin delivered over time according to the diabetes treatment plan of the user, and trends determined related to insulin delivery and the blood glucose measurements. Based on the processing, the AP application may evaluate whether a hypoglycemia protect mode is to be entered, such as if the AP application determines a persistently reduced raw glucose concentration or trend during decreasing insulin delivery, or unchanging raw glucose concentration or trend during increased insulin delivery or reduced raw glucose value or trend over significant periods of time regardless of insulin delivery, or the like. For example, the AP application may determine to enter hypoglycemia protect mode if the measured blood glucose value continues to drop despite reduced insulin delivery or suspension. Based on the result of the evaluation, the AP application may determine that YES, a hypoglycemia protect mode is to be entered and the process 500 proceeds as a precautionary measure to the process shown in
In an operational example, the controller 221 (or a processor) may be operable to receive blood glucose measurements from the blood glucose sensor 204. The controller 221 (or processor) may process the blood glucose measurements. The processing may reveal the blood glucose measurements are decreasing toward a minimum blood glucose set point. The minimum blood glucose set point may be a blood glucose value that the AP application (or the user manually) sets as a minimum lower limit of a blood glucose value for the user. Based on an indication that the blood glucose measurements are decreasing toward falling below the minimum blood glucose set point, the controller may enter the hypoglycemia protect mode. Alternatively, or in addition, the AP application executing on the controller may generate an alarm signal indicating that the blood glucose measurements are decreasing toward falling below the minimum blood glucose set point to enable the user to take remedial action.
Conversely, if the AP application determines NO, the hypoglycemia protect mode does not need to be entered and the process 500 proceeds to 580.
The hypoglycemia and hyperglycemia protection modes may either, in a first scenario, be modes of operation that are distinct from one another, (i.e., that are separately selectable or automatically entered into) or, in a second scenario, may be sub-modes of operation under the activity mode of operation and may be entered into automatically during execution of the activity mode of operation. Under either scenario, the techniques and devices disclosed herein enable operation according to these modes (e.g., activity mode, hypoglycemia protection mode or hyperglycemia protection mode) of operation to provide the protection and risk management benefits and advantages of an AP application enabled with these additional modes of operation as disclosed herein.
At 580, the AP application determines whether to remain in activity mode. For example, if the user set duration for activity mode has not expired the AP application may continue operating in activity mode. Alternatively, the received inputs from the IMU 207 or heart rate monitor 237 may continue to indicate physical activity. As a result of either the set duration not expiring or the continued indication of physical activity, the determination at 580 may be YES and the process 500 returns to 550 for adjustment of the diabetes treatment plan. Note that the adjustment of the diabetes treatment plan may be on-going as updated blood glucose measurements continue to be received by the AP application and are evaluated. Alternatively, the determination at 580 may be NO, do not remain in activity mode in which case the process 500 returns to 510 to receive inputs associated with the activity mode to determine if the user will be participating in other physical activity.
The increased activity may be detected using indicators such as, for example, increased heart rate or pulse rate, and comparing the monitored indicators to threshold activity levels. The drug delivery device 202 may adjust monitoring of the indicators and any thresholds based on learned behavior and patterns of the user.
The process 600 may also proceed to 620 at which the thresholds for triggering hyperglycemia alarms may be lowered. In addition, the process 600 may enable the blood glucose setpoint (i.e., the user's target blood glucose level) to be reduced (630).
The limits of the AP system's (or any algorithm executed by the drug delivery system 202) total possible insulin delivery over a duration may change gradually, instead of instantly, based on an observed increase in mean glucose concentration values. In other examples, the hyperglycemia mode may change parameters or inputs of the AP application (e.g., a cost function or gain) to cause the AP application to be less conservative and/or more aggressive in the determination of insulin dosage amounts and in the delivery schedules of the determined insulin dosage amounts.
At 612, the process 601 may reduce the basal input to the AP application, for example, being executed by a controller 221 of the drug delivery device 202. The reduced basal input may indicate to the AP application that a reduced basal insulin dosage that may be different than the basal input indicated by the user. For example, the basal input may be a basal insulin delivery value input by a user as part of a user's standard basal insulin dosage setting by the user, who may not have all the blood glucose measures, calculations of insulin on board, insulin sensitivity, other diabetes treatment plan information, or the like that the AP application has or is able to access and process. In response to being provided with the basal input, the AP application may correspondingly process the basal input and determine to reduce the amount of insulin delivery even when the user's standard basal insulin dosage settings as indicated by the provided basal input remain substantially the same.
At 613, the AP application may increase a blood glucose setpoint. For example, a user may have their blood glucose setpoint set at 100 mg/dL, in step 613, the AP application when in the hypoglycemia protect mode, may increase the blood glucose setpoint to 130 mg/dL or greater. As noted above, hypoglycemia may be induced by intense physical activity. In the hypoglycemia protect mode, the AP algorithm executing on the drug delivery device 202 may as part of any of steps 611-613, recommend with a prompt presented on a user interface or the like that the user intake carbohydrates prior to any planned exercise or during exercise based on, for example, a scheduled time of exercise, a detected glucose rate, a determined amount of insulin on board, or any combination thereof.
In an example, the hypoglycemia protect mode of operation may further include a step of reducing insulin delivery if the user experiences increased instances of hypoglycemia during earlier activations of the hypoglycemia protect mode of operation.
To ensure proper use of the available hypoglycemia protect mode, the drug delivery device 202 may ensure entry into this available mode of operation even when the user forgets to manually specify activation (e.g., forgetting to request the mode of operation prior to exercising).
In further examples, alerts may be provided by the AP application may generate alerts for output the user regarding the hypoglycemia protect mode of operation or automatic entry into the mode may occur when, for example, increased activity is detected, and the mode is not selected and/or when a location associated with increased activity levels is detected and the mode is also not selected for output via the user interface 227 or user interface 268 of the management device 206. Under these scenarios, the drug delivery device 202 may alert the user to the detected conditions, as described herein. To facilitate entry into the hypoglycemia protect mode of operation even when not specified by the user, the AP application executing on the controller 221 of the drug delivery device 202 may implement techniques to monitor the following conditions and provided feedback to the user. For example, the AP application may determine user activity is increased based upon motion data and biometric sensing, for example, by the IMU 207 or other sensor; and the user is in a geographic location where increased activity has been previously detected (e.g., based on increased activity in certain recognized locations).
By detecting activity levels and locations (e.g., via a GPS device, Wi-Fi location service or device, or another location determination device or sensor), the AP algorithm executing on the drug delivery device 202 may facilitate entry into the hypoglycemia protect mode of operation by alerting the user to the detected conditions where entry into the hypoglycemia protect mode of operation may be desired but has not occurred simply due to user error (e.g., the user forgot to enter the mode of operation). For example, the controller 221 of the drug delivery device 202 may upon execution of the AP application implement techniques that detect increased activity by the user (e.g., detects the user exercising) and/or detects locations where past increased levels of activity typically occur (e.g., recognizing locations such as a gym, a jogging trail or track, a swimming pool, a bike trail, a golf course, ice skating arena, soccer field, baseball field, football field, other sports field, beach, or the like as locations where the user typically exercises).
Techniques implemented by the drug delivery device 202, including during configuration of the drug delivery device 202, may enable the following parameters to be monitored and included with of the inputs associated with an activity level of a user received by the controller 221:
In addition, the AP application of the drug delivery device 202 may provide alerts to the user—for example, audible, tactile (e.g., vibrational), and/or visual alerts or similar alerts through the management device 206 or the user interface 227—to remind the user to enter into the hypoglycemia protect mode of operation if current activity levels of the user increase and/or predicted increased activity is expected.
Although some of the examples referenced the controller 221 of the wearable drug delivery device 202 performing some or all of the processes described in the foregoing examples, the disclosed subject matter should not be limited. For example, the described processes may also be performed by the processor 261 of the management device 206 or the processor 241 of the blood glucose sensor 204. Alternatively, some or all of the processes described in the foregoing examples may be distributed among the various processors or controllers, such as 261, 241 and 221 with information shared over the wired communication links 277, 278, 279 or wireless communication links 28, 288, 289.
The techniques described herein for providing an activity mode, hyperglycemia protect mode, or a hypoglycemia protect mode as described herein for a drug delivery system (e.g., the systems 100, 200 or any components thereof) may be implemented in hardware, software, or any combination thereof. Any component as described herein may be implemented in hardware, software, or any combination thereof. For example, the systems 100 and 200 or any components thereof may be implemented in hardware, software, or any combination thereof. Software related implementations of the techniques described herein may include, but are not limited to, firmware, application specific software, or any other type of computer readable instructions that may be executed by one or more processors. Hardware related implementations of the techniques described herein may include, but are not limited to, integrated circuits (ICs), application specific ICs (ASICs), field programmable arrays (FPGAs), and/or programmable logic devices (PLDs). In some examples, the techniques described herein, and/or any system or constituent component described herein may be implemented with a processor executing computer readable instructions stored on one or more memory components.
Some examples of the disclosed devices may be implemented, for example, using a storage medium, a computer-readable medium, or an article of manufacture which may store an instruction or a set of instructions that, if executed by a machine (i.e., processor or controller), may cause the machine to perform a method and/or operation in accordance with examples of the disclosure. Such a machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware and/or software. The computer-readable medium or article may include, for example, any suitable type of memory unit, memory, memory article, memory medium, storage device, storage article, storage medium and/or storage unit, for example, memory (including non-transitory memory), removable or non-removable media, erasable or non-erasable media, writeable or re-writeable media, digital or analog media, hard disk, floppy disk, Compact Disk Read Only Memory (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or disks, various types of Digital Versatile Disk (DVD), a tape, a cassette, or the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, programming code, and the like, implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language. The non-transitory computer readable medium embodied programming code may cause a processor when executing the programming code to perform functions, such as those described herein.
Certain examples of the present disclosed subject matter were described above. It is, however, expressly noted that the present disclosed subject matter is not limited to those examples, but rather the intention is that additions and modifications to what was expressly described herein are also included within the scope of the disclosed subject matter. Moreover, it is to be understood that the features of the various examples described herein were not mutually exclusive and may exist in various combinations and permutations, even if such combinations or permutations were not made express herein, without departing from the spirit and scope of the disclosed subject matter. In fact, variations, modifications, and other implementations of what was described herein will occur to those of ordinary skill in the art without departing from the spirit and the scope of the disclosed subject matter. As such, the disclosed subject matter is not to be defined only by the preceding illustrative description.
Program aspects of the technology may be thought of as “products” or “articles of manufacture” typically in the form of executable code and/or associated data that is carried on or embodied in a type of machine readable medium. Storage type media include any or all of the tangible memory of the computers, processors or the like, or associated modules thereof, such as various semiconductor memories, tape drives, disk drives and the like, which may provide non-transitory storage at any time for the software programming. It is emphasized that the Abstract of the Disclosure is provided to allow a reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, various features are grouped together in a single example for streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed examples require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed example. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate example. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein,” respectively. Moreover, the terms “first,” “second,” “third,” and so forth, are used merely as labels and are not intended to impose numerical requirements on their objects.
The foregoing description of example examples has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the present disclosure to the precise forms disclosed. Many modifications and variations are possible in light of this disclosure. It is intended that the scope of the present disclosure be limited not by this detailed description, but rather by the claims appended hereto. Future filed applications claiming priority to this application may claim the disclosed subject matter in a different manner and may generally include any set of one or more limitations as variously disclosed or otherwise demonstrated herein.
This application claims priority to U.S. Provisional Application No. 62/738,531, filed on Sep. 28, 2018, the entire contents of which are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 303013 | Horton | Aug 1884 | A |
| 2797149 | Skeggs | Jun 1957 | A |
| 3631847 | Hobbs | Jan 1972 | A |
| 3634039 | Brondy | Jan 1972 | A |
| 3812843 | Wootten et al. | May 1974 | A |
| 3841328 | Jensen | Oct 1974 | A |
| 3963380 | Thomas, Jr. et al. | Jun 1976 | A |
| 4055175 | Clemens et al. | Oct 1977 | A |
| 4146029 | Ellinwood, Jr. | Mar 1979 | A |
| 4151845 | Clemens | May 1979 | A |
| 4245634 | Albisser et al. | Jan 1981 | A |
| 4368980 | Aldred et al. | Jan 1983 | A |
| 4373527 | Fischell | Feb 1983 | A |
| 4403984 | Ash et al. | Sep 1983 | A |
| 4464170 | Clemens et al. | Aug 1984 | A |
| 4469481 | Kobayashi | Sep 1984 | A |
| 4475901 | Kraegen et al. | Oct 1984 | A |
| 4526568 | Clemens et al. | Jul 1985 | A |
| 4526569 | Bernardi | Jul 1985 | A |
| 4529401 | Leslie et al. | Jul 1985 | A |
| 4559033 | Stephen et al. | Dec 1985 | A |
| 4559037 | Franetzki et al. | Dec 1985 | A |
| 4573968 | Parker | Mar 1986 | A |
| 4624661 | Arimond | Nov 1986 | A |
| 4633878 | Bombardieri | Jan 1987 | A |
| 4657529 | Prince et al. | Apr 1987 | A |
| 4685903 | Cable et al. | Aug 1987 | A |
| 4731726 | Allen, III | Mar 1988 | A |
| 4743243 | Vaillancourt | May 1988 | A |
| 4755173 | Konopka et al. | Jul 1988 | A |
| 4781688 | Thoma et al. | Nov 1988 | A |
| 4781693 | Martinez et al. | Nov 1988 | A |
| 4808161 | Kamen | Feb 1989 | A |
| 4854170 | Brimhall et al. | Aug 1989 | A |
| 4886499 | Cirelli et al. | Dec 1989 | A |
| 4900292 | Berry et al. | Feb 1990 | A |
| 4919596 | Slate et al. | Apr 1990 | A |
| 4925444 | Orkin et al. | May 1990 | A |
| 4940527 | Kazlauskas et al. | Jul 1990 | A |
| 4975581 | Robinson et al. | Dec 1990 | A |
| 4976720 | Machold et al. | Dec 1990 | A |
| 4981140 | Wyatt | Jan 1991 | A |
| 4994047 | Walker et al. | Feb 1991 | A |
| 5007286 | Malcolm et al. | Apr 1991 | A |
| 5097834 | Skrabal | Mar 1992 | A |
| 5102406 | Arnold | Apr 1992 | A |
| 5109850 | Blanco et al. | May 1992 | A |
| 5125415 | Bell | Jun 1992 | A |
| 5134079 | Cusack et al. | Jul 1992 | A |
| 5153827 | Coutre et al. | Oct 1992 | A |
| 5165406 | Wong | Nov 1992 | A |
| 5176662 | Bartholomew et al. | Jan 1993 | A |
| 5178609 | Ishikawa | Jan 1993 | A |
| 5207642 | Orkin et al. | May 1993 | A |
| 5232439 | Campbell et al. | Aug 1993 | A |
| 5237993 | Skrabal | Aug 1993 | A |
| 5244463 | Cordner, Jr. et al. | Sep 1993 | A |
| 5257980 | Van Antwerp et al. | Nov 1993 | A |
| 5273517 | Barone et al. | Dec 1993 | A |
| 5281808 | Kunkel | Jan 1994 | A |
| 5299571 | Mastrototaro | Apr 1994 | A |
| 5308982 | Ivaldi et al. | May 1994 | A |
| 5342298 | Michaels et al. | Aug 1994 | A |
| 5377674 | Kuestner | Jan 1995 | A |
| 5380665 | Cusack et al. | Jan 1995 | A |
| 5385539 | Maynard | Jan 1995 | A |
| 5389078 | Zalesky et al. | Feb 1995 | A |
| 5411889 | Hoots et al. | May 1995 | A |
| 5421812 | Langley et al. | Jun 1995 | A |
| 5468727 | Phillips et al. | Nov 1995 | A |
| 5505709 | Funderburk et al. | Apr 1996 | A |
| 5505828 | Wong et al. | Apr 1996 | A |
| 5507288 | Bocker et al. | Apr 1996 | A |
| 5533389 | Kamen et al. | Jul 1996 | A |
| 5558640 | Pfeiler et al. | Sep 1996 | A |
| 5569186 | Lord et al. | Oct 1996 | A |
| 5584813 | Livingston et al. | Dec 1996 | A |
| 5609572 | Lang | Mar 1997 | A |
| 5665065 | Colman et al. | Sep 1997 | A |
| 5678539 | Schubert et al. | Oct 1997 | A |
| 5685844 | Marttila | Nov 1997 | A |
| 5685859 | Komerup | Nov 1997 | A |
| 5693018 | Kriesel et al. | Dec 1997 | A |
| 5697899 | Hillman et al. | Dec 1997 | A |
| 5700695 | Yassinzadeh et al. | Dec 1997 | A |
| 5703364 | Rosenthal | Dec 1997 | A |
| 5714123 | Sohrab | Feb 1998 | A |
| 5716343 | Kriesel et al. | Feb 1998 | A |
| 5722397 | Eppstein | Mar 1998 | A |
| 5741228 | Lambrecht et al. | Apr 1998 | A |
| 5746217 | Erickson et al. | May 1998 | A |
| 5755682 | Knudson et al. | May 1998 | A |
| 5758643 | Wong et al. | Jun 1998 | A |
| 5800405 | McPhee | Sep 1998 | A |
| 5800420 | Gross et al. | Sep 1998 | A |
| 5801057 | Smart et al. | Sep 1998 | A |
| 5804048 | Wong et al. | Sep 1998 | A |
| 5817007 | Fodgaard et al. | Oct 1998 | A |
| 5820622 | Gross et al. | Oct 1998 | A |
| 5823951 | Messerschmidt | Oct 1998 | A |
| 5840020 | Heinonen et al. | Nov 1998 | A |
| 5848991 | Gross et al. | Dec 1998 | A |
| 5851197 | Marano et al. | Dec 1998 | A |
| 5858005 | Kriesel | Jan 1999 | A |
| 5865806 | Howell | Feb 1999 | A |
| 5871470 | McWha | Feb 1999 | A |
| 5879310 | Sopp et al. | Mar 1999 | A |
| 5902253 | Pfeiffer et al. | May 1999 | A |
| 5931814 | Alex et al. | Aug 1999 | A |
| 5932175 | Knute et al. | Aug 1999 | A |
| 5935099 | Peterson et al. | Aug 1999 | A |
| 5947911 | Wong et al. | Sep 1999 | A |
| 5971941 | Simons et al. | Oct 1999 | A |
| 5993423 | Choi | Nov 1999 | A |
| 5997501 | Gross et al. | Dec 1999 | A |
| 6017318 | Gauthier et al. | Jan 2000 | A |
| 6024539 | Blomquist | Feb 2000 | A |
| 6032059 | Henning et al. | Feb 2000 | A |
| 6036924 | Simons et al. | Mar 2000 | A |
| 6040578 | Malin et al. | Mar 2000 | A |
| 6049727 | Crothall | Apr 2000 | A |
| 6050978 | Orr et al. | Apr 2000 | A |
| 6058934 | Sullivan | May 2000 | A |
| 6066103 | Duchon et al. | May 2000 | A |
| 6071292 | Makower et al. | Jun 2000 | A |
| 6072180 | Kramer et al. | Jun 2000 | A |
| 6077055 | Vilks | Jun 2000 | A |
| 6090092 | Fowles et al. | Jul 2000 | A |
| 6101406 | Hacker et al. | Aug 2000 | A |
| 6102872 | Doneen et al. | Aug 2000 | A |
| 6115673 | Malin et al. | Sep 2000 | A |
| 6123827 | Wong et al. | Sep 2000 | A |
| 6124134 | Stark | Sep 2000 | A |
| 6126637 | Kriesel et al. | Oct 2000 | A |
| 6128519 | Say | Oct 2000 | A |
| 6142939 | Eppstein et al. | Nov 2000 | A |
| 6143164 | Heller et al. | Nov 2000 | A |
| 6157041 | Thomas et al. | Dec 2000 | A |
| 6161028 | Braig et al. | Dec 2000 | A |
| 6162639 | Douglas | Dec 2000 | A |
| 6196046 | Braig et al. | Mar 2001 | B1 |
| 6200287 | Keller et al. | Mar 2001 | B1 |
| 6200338 | Solomon et al. | Mar 2001 | B1 |
| 6214629 | Freitag et al. | Apr 2001 | B1 |
| 6226082 | Roe | May 2001 | B1 |
| 6244776 | Wiley | Jun 2001 | B1 |
| 6261065 | Nayak et al. | Jul 2001 | B1 |
| 6262798 | Shepherd et al. | Jul 2001 | B1 |
| 6270455 | Brown | Aug 2001 | B1 |
| 6271045 | Douglas et al. | Aug 2001 | B1 |
| 6280381 | Malin et al. | Aug 2001 | B1 |
| 6285448 | Kuenstner | Sep 2001 | B1 |
| 6309370 | Haim et al. | Oct 2001 | B1 |
| 6312888 | Wong et al. | Nov 2001 | B1 |
| 6334851 | Hayes et al. | Jan 2002 | B1 |
| 6375627 | Mauze et al. | Apr 2002 | B1 |
| 6379301 | Worthington et al. | Apr 2002 | B1 |
| 6402689 | Scarantino et al. | Jun 2002 | B1 |
| 6470279 | Samsoondar | Oct 2002 | B1 |
| 6475196 | Vachon | Nov 2002 | B1 |
| 6477901 | Tadigadapa et al. | Nov 2002 | B1 |
| 6484044 | Lilienfeld-Toal | Nov 2002 | B1 |
| 6491656 | Morris | Dec 2002 | B1 |
| 6512937 | Blank et al. | Jan 2003 | B2 |
| 6525509 | Petersson et al. | Feb 2003 | B1 |
| 6528809 | Thomas et al. | Mar 2003 | B1 |
| 6540672 | Simonsen et al. | Apr 2003 | B1 |
| 6544212 | Galley et al. | Apr 2003 | B2 |
| 6546268 | Ishikawa et al. | Apr 2003 | B1 |
| 6546269 | Kumik | Apr 2003 | B1 |
| 6553841 | Blouch | Apr 2003 | B1 |
| 6554798 | Mann et al. | Apr 2003 | B1 |
| 6556850 | Braig et al. | Apr 2003 | B1 |
| 6558351 | Steil et al. | May 2003 | B1 |
| 6560471 | Heller et al. | May 2003 | B1 |
| 6561978 | Conn et al. | May 2003 | B1 |
| 6562001 | Lebel et al. | May 2003 | B2 |
| 6562014 | Lin et al. | May 2003 | B2 |
| 6569125 | Jepson et al. | May 2003 | B2 |
| 6572542 | Houben et al. | Jun 2003 | B1 |
| 6572545 | Knobbe et al. | Jun 2003 | B2 |
| 6574490 | Abbink et al. | Jun 2003 | B2 |
| 6575905 | Knobbe et al. | Jun 2003 | B2 |
| 6580934 | Braig et al. | Jun 2003 | B1 |
| 6618603 | Varalli et al. | Sep 2003 | B2 |
| 6633772 | Ford et al. | Oct 2003 | B2 |
| 6645142 | Braig et al. | Nov 2003 | B2 |
| 6653091 | Dunn et al. | Nov 2003 | B1 |
| 6662030 | Khalil et al. | Dec 2003 | B2 |
| 6669663 | Thompson | Dec 2003 | B1 |
| 6678542 | Braig et al. | Jan 2004 | B2 |
| 6699221 | Vaillancourt | Mar 2004 | B2 |
| 6718189 | Rohrscheib et al. | Apr 2004 | B2 |
| 6721582 | Frepagnier et al. | Apr 2004 | B2 |
| 6728560 | Kollias et al. | Apr 2004 | B2 |
| 6740059 | Flaherty | May 2004 | B2 |
| 6740072 | Starkweather et al. | May 2004 | B2 |
| 6751490 | Esenaliev et al. | Jun 2004 | B2 |
| 6758835 | Close et al. | Jul 2004 | B2 |
| 6780156 | Haueter et al. | Aug 2004 | B2 |
| 6810290 | Lebel et al. | Oct 2004 | B2 |
| 6837858 | Cunningham et al. | Jan 2005 | B2 |
| 6837988 | Leong et al. | Jan 2005 | B2 |
| 6846288 | Nagar et al. | Jan 2005 | B2 |
| 6862534 | Sterling et al. | Mar 2005 | B2 |
| 6865408 | Abbink et al. | Mar 2005 | B1 |
| 6890291 | Robinson et al. | May 2005 | B2 |
| 6936029 | Mann et al. | Aug 2005 | B2 |
| 6949081 | Chance | Sep 2005 | B1 |
| 6958809 | Sterling et al. | Oct 2005 | B2 |
| 6989891 | Braig et al. | Jan 2006 | B2 |
| 6990366 | Say et al. | Jan 2006 | B2 |
| 7008404 | Nakajima | Mar 2006 | B2 |
| 7009180 | Sterling et al. | Mar 2006 | B2 |
| 7016713 | Gardner et al. | Mar 2006 | B2 |
| 7018360 | Flaherty et al. | Mar 2006 | B2 |
| 7025743 | Mann et al. | Apr 2006 | B2 |
| 7025744 | Utterberg et al. | Apr 2006 | B2 |
| 7027848 | Robinson et al. | Apr 2006 | B2 |
| 7043288 | Davis, III et al. | May 2006 | B2 |
| 7060059 | Keith et al. | Jun 2006 | B2 |
| 7061593 | Braig et al. | Jun 2006 | B2 |
| 7096124 | Sterling et al. | Aug 2006 | B2 |
| 7115205 | Robinson et al. | Oct 2006 | B2 |
| 7128727 | Flaherty et al. | Oct 2006 | B2 |
| 7139593 | Kavak et al. | Nov 2006 | B2 |
| 7139598 | Hull et al. | Nov 2006 | B2 |
| 7144384 | Gorman et al. | Dec 2006 | B2 |
| 7171252 | Scarantino et al. | Jan 2007 | B1 |
| 7190988 | Say et al. | Mar 2007 | B2 |
| 7204823 | Estes et al. | Apr 2007 | B2 |
| 7248912 | Gough et al. | Jul 2007 | B2 |
| 7267665 | Steil et al. | Sep 2007 | B2 |
| 7271912 | Sterling et al. | Sep 2007 | B2 |
| 7278983 | Ireland et al. | Oct 2007 | B2 |
| 7291107 | Hellwig et al. | Nov 2007 | B2 |
| 7291497 | Holmes et al. | Nov 2007 | B2 |
| 7303549 | Flaherty et al. | Dec 2007 | B2 |
| 7303622 | Loch et al. | Dec 2007 | B2 |
| 7303922 | Jeng et al. | Dec 2007 | B2 |
| 7354420 | Steil et al. | Apr 2008 | B2 |
| 7388202 | Sterling et al. | Jun 2008 | B2 |
| 7402153 | Steil et al. | Jul 2008 | B2 |
| 7404796 | Ginsberg | Jul 2008 | B2 |
| 7429255 | Thompson | Sep 2008 | B2 |
| 7460130 | Salganicoff | Dec 2008 | B2 |
| 7481787 | Gable et al. | Jan 2009 | B2 |
| 7491187 | Van Den Berghe et al. | Feb 2009 | B2 |
| 7500949 | Gottlieb et al. | Mar 2009 | B2 |
| 7509156 | Flanders | Mar 2009 | B2 |
| 7547281 | Hayes et al. | Jun 2009 | B2 |
| 7569030 | Lebel et al. | Aug 2009 | B2 |
| 7608042 | Goldberger et al. | Oct 2009 | B2 |
| 7651845 | Doyle, III et al. | Jan 2010 | B2 |
| 7680529 | Kroll | Mar 2010 | B2 |
| 7734323 | Blomquist et al. | Jun 2010 | B2 |
| 7766829 | Sloan et al. | Aug 2010 | B2 |
| 7785258 | Braig et al. | Aug 2010 | B2 |
| 7806854 | Damiano et al. | Oct 2010 | B2 |
| 7806886 | Kanderian, Jr. et al. | Oct 2010 | B2 |
| 7918825 | OConnor et al. | Apr 2011 | B2 |
| 7946985 | Mastrototaro et al. | May 2011 | B2 |
| 7972296 | Braig et al. | Jul 2011 | B2 |
| 8221345 | Blomquist | Jul 2012 | B2 |
| 8251907 | Sterling et al. | Aug 2012 | B2 |
| 8449524 | Braig et al. | May 2013 | B2 |
| 8452359 | Rebec et al. | May 2013 | B2 |
| 8454576 | Mastrototaro et al. | Jun 2013 | B2 |
| 8467980 | Campbell et al. | Jun 2013 | B2 |
| 8478557 | Hayter et al. | Jul 2013 | B2 |
| 8547239 | Peallield et al. | Oct 2013 | B2 |
| 8597274 | Sloan et al. | Dec 2013 | B2 |
| 8622988 | Hayter | Jan 2014 | B2 |
| 8810394 | Kalpin | Aug 2014 | B2 |
| 9061097 | Holt et al. | Jun 2015 | B2 |
| 9171343 | Fischell et al. | Oct 2015 | B1 |
| 9233204 | Booth et al. | Jan 2016 | B2 |
| 9486571 | Rosinko | Nov 2016 | B2 |
| 9579456 | Budiman et al. | Feb 2017 | B2 |
| 9743224 | San Vicente et al. | Aug 2017 | B2 |
| 9907515 | Doyle, III et al. | Mar 2018 | B2 |
| 9980140 | Spencer et al. | May 2018 | B1 |
| 9984773 | Gondhalekar et al. | May 2018 | B2 |
| 10248839 | Levy et al. | Apr 2019 | B2 |
| 10335464 | Michelich et al. | Jul 2019 | B1 |
| 10583250 | Mazlish et al. | Mar 2020 | B2 |
| 10737024 | Schmid | Aug 2020 | B2 |
| 10987468 | Mazlish et al. | Apr 2021 | B2 |
| 11197964 | Sjolund et al. | Dec 2021 | B2 |
| 11260169 | Estes | Mar 2022 | B2 |
| 20010021803 | Blank et al. | Sep 2001 | A1 |
| 20010034023 | Stanton, Jr. et al. | Oct 2001 | A1 |
| 20010034502 | Moberg et al. | Oct 2001 | A1 |
| 20010051377 | Hammer et al. | Dec 2001 | A1 |
| 20010053895 | Vaillancourt | Dec 2001 | A1 |
| 20020010401 | Bushmakin et al. | Jan 2002 | A1 |
| 20020010423 | Gross et al. | Jan 2002 | A1 |
| 20020016568 | Lebel et al. | Feb 2002 | A1 |
| 20020040208 | Flaherty et al. | Apr 2002 | A1 |
| 20020123740 | Flaherty et al. | Sep 2002 | A1 |
| 20020128543 | Leonhardt | Sep 2002 | A1 |
| 20020147423 | Burbank et al. | Oct 2002 | A1 |
| 20020155425 | Han et al. | Oct 2002 | A1 |
| 20020161288 | Shin et al. | Oct 2002 | A1 |
| 20030023148 | Lorenz et al. | Jan 2003 | A1 |
| 20030050621 | Lebel et al. | Mar 2003 | A1 |
| 20030060692 | L. Ruchti et al. | Mar 2003 | A1 |
| 20030086074 | Braig et al. | May 2003 | A1 |
| 20030086075 | Braig et al. | May 2003 | A1 |
| 20030090649 | Sterling et al. | May 2003 | A1 |
| 20030100040 | Bonnecaze et al. | May 2003 | A1 |
| 20030130616 | Steil et al. | Jul 2003 | A1 |
| 20030135388 | Martucci et al. | Jul 2003 | A1 |
| 20030144582 | Cohen et al. | Jul 2003 | A1 |
| 20030163097 | Fleury et al. | Aug 2003 | A1 |
| 20030195404 | Knobbe et al. | Oct 2003 | A1 |
| 20030208113 | Mault et al. | Nov 2003 | A1 |
| 20030208154 | Close et al. | Nov 2003 | A1 |
| 20030212379 | Bylund et al. | Nov 2003 | A1 |
| 20030216627 | Lorenz et al. | Nov 2003 | A1 |
| 20030220605 | Bowman, Jr. et al. | Nov 2003 | A1 |
| 20040010207 | Flaherty et al. | Jan 2004 | A1 |
| 20040034295 | Salganicoff | Feb 2004 | A1 |
| 20040045879 | Shults et al. | Mar 2004 | A1 |
| 20040051368 | Caputo et al. | Mar 2004 | A1 |
| 20040064259 | Haaland et al. | Apr 2004 | A1 |
| 20040097796 | Berman et al. | May 2004 | A1 |
| 20040116847 | Wall | Jun 2004 | A1 |
| 20040122353 | Shahmirian et al. | Jun 2004 | A1 |
| 20040133166 | Moberg et al. | Jul 2004 | A1 |
| 20040147034 | Gore et al. | Jul 2004 | A1 |
| 20040171983 | Sparks et al. | Sep 2004 | A1 |
| 20040203357 | Nassimi | Oct 2004 | A1 |
| 20040204868 | Maynard et al. | Oct 2004 | A1 |
| 20040215492 | Choi | Oct 2004 | A1 |
| 20040220517 | Starkweather et al. | Nov 2004 | A1 |
| 20040241736 | Hendee et al. | Dec 2004 | A1 |
| 20040249308 | Forssell | Dec 2004 | A1 |
| 20050003470 | Nelson et al. | Jan 2005 | A1 |
| 20050020980 | Inoue et al. | Jan 2005 | A1 |
| 20050022274 | Campbell et al. | Jan 2005 | A1 |
| 20050033148 | Haueter et al. | Feb 2005 | A1 |
| 20050049179 | Davidson et al. | Mar 2005 | A1 |
| 20050065464 | Talbot et al. | Mar 2005 | A1 |
| 20050065465 | Lebel et al. | Mar 2005 | A1 |
| 20050075624 | Miesel | Apr 2005 | A1 |
| 20050105095 | Pesach et al. | May 2005 | A1 |
| 20050137573 | McLaughlin | Jun 2005 | A1 |
| 20050171503 | Van Den Berghe et al. | Aug 2005 | A1 |
| 20050182306 | Sloan | Aug 2005 | A1 |
| 20050192494 | Ginsberg | Sep 2005 | A1 |
| 20050192557 | Brauker et al. | Sep 2005 | A1 |
| 20050197621 | Poulsen et al. | Sep 2005 | A1 |
| 20050203360 | Brauker et al. | Sep 2005 | A1 |
| 20050203461 | Flaherty et al. | Sep 2005 | A1 |
| 20050238507 | Dilanni et al. | Oct 2005 | A1 |
| 20050261660 | Choi | Nov 2005 | A1 |
| 20050272640 | Doyle, III et al. | Dec 2005 | A1 |
| 20050277912 | John | Dec 2005 | A1 |
| 20060009727 | OMahony et al. | Jan 2006 | A1 |
| 20060079809 | Goldberger et al. | Apr 2006 | A1 |
| 20060100494 | Kroll | May 2006 | A1 |
| 20060134323 | OBrien | Jun 2006 | A1 |
| 20060167350 | Monfre et al. | Jul 2006 | A1 |
| 20060173406 | Hayes et al. | Aug 2006 | A1 |
| 20060189925 | Gable et al. | Aug 2006 | A1 |
| 20060189926 | Hall et al. | Aug 2006 | A1 |
| 20060197015 | Sterling et al. | Sep 2006 | A1 |
| 20060200070 | Callicoat et al. | Sep 2006 | A1 |
| 20060204535 | Johnson | Sep 2006 | A1 |
| 20060229531 | Goldberger et al. | Oct 2006 | A1 |
| 20060253085 | Geismar et al. | Nov 2006 | A1 |
| 20060264895 | Flanders | Nov 2006 | A1 |
| 20060270983 | Lord et al. | Nov 2006 | A1 |
| 20060276771 | Galley et al. | Dec 2006 | A1 |
| 20060282290 | Flaherty et al. | Dec 2006 | A1 |
| 20070016127 | Staib et al. | Jan 2007 | A1 |
| 20070060796 | Kim | Mar 2007 | A1 |
| 20070060869 | Tolle et al. | Mar 2007 | A1 |
| 20070060872 | Hall et al. | Mar 2007 | A1 |
| 20070083160 | Hall et al. | Apr 2007 | A1 |
| 20070106135 | Sloan et al. | May 2007 | A1 |
| 20070116601 | Patton | May 2007 | A1 |
| 20070118405 | Campbell et al. | May 2007 | A1 |
| 20070129690 | Rosenblatt et al. | Jun 2007 | A1 |
| 20070142720 | Ridder et al. | Jun 2007 | A1 |
| 20070173761 | Kanderian et al. | Jul 2007 | A1 |
| 20070173974 | Lin | Jul 2007 | A1 |
| 20070179352 | Randlov et al. | Aug 2007 | A1 |
| 20070191716 | Goldberger et al. | Aug 2007 | A1 |
| 20070197163 | Robertson | Aug 2007 | A1 |
| 20070225675 | Robinson et al. | Sep 2007 | A1 |
| 20070244381 | Robinson et al. | Oct 2007 | A1 |
| 20070249007 | Rosero | Oct 2007 | A1 |
| 20070264707 | Liederman et al. | Nov 2007 | A1 |
| 20070282269 | Carter et al. | Dec 2007 | A1 |
| 20070287985 | Estes et al. | Dec 2007 | A1 |
| 20070293843 | Ireland et al. | Dec 2007 | A1 |
| 20080033272 | Gough et al. | Feb 2008 | A1 |
| 20080051764 | Dent et al. | Feb 2008 | A1 |
| 20080058625 | McGarraugh et al. | Mar 2008 | A1 |
| 20080065050 | Sparks et al. | Mar 2008 | A1 |
| 20080071157 | McGarraugh et al. | Mar 2008 | A1 |
| 20080071158 | McGarraugh et al. | Mar 2008 | A1 |
| 20080078400 | Martens et al. | Apr 2008 | A1 |
| 20080097289 | Steil et al. | Apr 2008 | A1 |
| 20080132880 | Buchman | Jun 2008 | A1 |
| 20080161664 | Mastrototaro et al. | Jul 2008 | A1 |
| 20080172026 | Blomquist | Jul 2008 | A1 |
| 20080177165 | Blomquist et al. | Jul 2008 | A1 |
| 20080188796 | Steil et al. | Aug 2008 | A1 |
| 20080200838 | Goldberger et al. | Aug 2008 | A1 |
| 20080206067 | De Corral et al. | Aug 2008 | A1 |
| 20080208113 | Damiano et al. | Aug 2008 | A1 |
| 20080214919 | Harmon et al. | Sep 2008 | A1 |
| 20080228056 | Blomquist et al. | Sep 2008 | A1 |
| 20080249386 | Besterman et al. | Oct 2008 | A1 |
| 20080269585 | Ginsberg | Oct 2008 | A1 |
| 20080269714 | Mastrototaro et al. | Oct 2008 | A1 |
| 20080269723 | Mastrototaro et al. | Oct 2008 | A1 |
| 20080287906 | Burkholz et al. | Nov 2008 | A1 |
| 20090006061 | Thukral et al. | Jan 2009 | A1 |
| 20090018406 | Yodat et al. | Jan 2009 | A1 |
| 20090030398 | Yodat et al. | Jan 2009 | A1 |
| 20090036753 | King | Feb 2009 | A1 |
| 20090043240 | Robinson et al. | Feb 2009 | A1 |
| 20090054753 | Robinson et al. | Feb 2009 | A1 |
| 20090069743 | Krishnamoorthy et al. | Mar 2009 | A1 |
| 20090069745 | Estes et al. | Mar 2009 | A1 |
| 20090069787 | Estes et al. | Mar 2009 | A1 |
| 20090099521 | Gravesen et al. | Apr 2009 | A1 |
| 20090105573 | Malecha | Apr 2009 | A1 |
| 20090131861 | Braig et al. | May 2009 | A1 |
| 20090156922 | Goldberger et al. | Jun 2009 | A1 |
| 20090156924 | Shariati et al. | Jun 2009 | A1 |
| 20090163781 | Say et al. | Jun 2009 | A1 |
| 20090198350 | Thiele | Aug 2009 | A1 |
| 20090221890 | Saffer et al. | Sep 2009 | A1 |
| 20090228214 | Say et al. | Sep 2009 | A1 |
| 20090318791 | Kaastrup | Dec 2009 | A1 |
| 20090326343 | Gable et al. | Dec 2009 | A1 |
| 20100057042 | Hayter | Mar 2010 | A1 |
| 20100114026 | Karratt et al. | May 2010 | A1 |
| 20100121170 | Rule | May 2010 | A1 |
| 20100137784 | Cefai et al. | Jun 2010 | A1 |
| 20100152658 | Hanson et al. | Jun 2010 | A1 |
| 20100174228 | Buckingham et al. | Jul 2010 | A1 |
| 20100211003 | Sundar et al. | Aug 2010 | A1 |
| 20100228110 | Tsoukalis | Sep 2010 | A1 |
| 20100262117 | Magni et al. | Oct 2010 | A1 |
| 20100262434 | Shaya | Oct 2010 | A1 |
| 20100295686 | Sloan et al. | Nov 2010 | A1 |
| 20100298765 | Budiman et al. | Nov 2010 | A1 |
| 20110021584 | Berggren et al. | Jan 2011 | A1 |
| 20110028817 | Jin et al. | Feb 2011 | A1 |
| 20110054390 | Searle et al. | Mar 2011 | A1 |
| 20110054399 | Chong et al. | Mar 2011 | A1 |
| 20110124996 | Reinke et al. | May 2011 | A1 |
| 20110144586 | Michaud et al. | Jun 2011 | A1 |
| 20110145747 | Wong | Jun 2011 | A1 |
| 20110160652 | Yodat et al. | Jun 2011 | A1 |
| 20110178472 | Cabiri | Jul 2011 | A1 |
| 20110190694 | Lanier, Jr. et al. | Aug 2011 | A1 |
| 20110202005 | Yodat et al. | Aug 2011 | A1 |
| 20110208155 | Palerm | Aug 2011 | A1 |
| 20110218495 | Remde | Sep 2011 | A1 |
| 20110230833 | Landman et al. | Sep 2011 | A1 |
| 20110251509 | Beyhan et al. | Oct 2011 | A1 |
| 20110257496 | Terashima | Oct 2011 | A1 |
| 20110313680 | Doyle et al. | Dec 2011 | A1 |
| 20110316562 | Cefai et al. | Dec 2011 | A1 |
| 20120003935 | Lydon et al. | Jan 2012 | A1 |
| 20120010594 | Holt et al. | Jan 2012 | A1 |
| 20120030393 | Ganesh et al. | Feb 2012 | A1 |
| 20120053556 | Lee | Mar 2012 | A1 |
| 20120078067 | Kovatchev et al. | Mar 2012 | A1 |
| 20120078161 | Masterson et al. | Mar 2012 | A1 |
| 20120078181 | Smith et al. | Mar 2012 | A1 |
| 20120101451 | Boit et al. | Apr 2012 | A1 |
| 20120123234 | Atlas et al. | May 2012 | A1 |
| 20120136336 | Mastrototaro et al. | May 2012 | A1 |
| 20120190955 | Rao et al. | Jul 2012 | A1 |
| 20120203085 | Rebec | Aug 2012 | A1 |
| 20120203178 | Tverskoy | Aug 2012 | A1 |
| 20120215087 | Cobelli et al. | Aug 2012 | A1 |
| 20120225134 | Komorowski | Sep 2012 | A1 |
| 20120226259 | Yodat et al. | Sep 2012 | A1 |
| 20120232520 | Sloan et al. | Sep 2012 | A1 |
| 20120238851 | Kamen et al. | Sep 2012 | A1 |
| 20120271655 | Knobel et al. | Oct 2012 | A1 |
| 20120277668 | Chawla | Nov 2012 | A1 |
| 20120282111 | Nip et al. | Nov 2012 | A1 |
| 20120295550 | Wilson et al. | Nov 2012 | A1 |
| 20130030358 | Yodfat et al. | Jan 2013 | A1 |
| 20130158503 | Kanderian, Jr. et al. | Jun 2013 | A1 |
| 20130178791 | Javitt | Jul 2013 | A1 |
| 20130231642 | Doyle et al. | Sep 2013 | A1 |
| 20130253472 | Cabiri | Sep 2013 | A1 |
| 20130261406 | Rebec et al. | Oct 2013 | A1 |
| 20130296823 | Melker et al. | Nov 2013 | A1 |
| 20130317753 | Kamen et al. | Nov 2013 | A1 |
| 20130338576 | OConnor et al. | Dec 2013 | A1 |
| 20140005633 | Finan | Jan 2014 | A1 |
| 20140066886 | Roy et al. | Mar 2014 | A1 |
| 20140074033 | Sonderegger et al. | Mar 2014 | A1 |
| 20140121635 | Hayter | May 2014 | A1 |
| 20140128839 | Dilanni et al. | May 2014 | A1 |
| 20140135880 | Baumgartner et al. | May 2014 | A1 |
| 20140146202 | Boss et al. | May 2014 | A1 |
| 20140180203 | Budiman et al. | Jun 2014 | A1 |
| 20140180240 | Finan et al. | Jun 2014 | A1 |
| 20140200426 | Taub et al. | Jul 2014 | A1 |
| 20140200559 | Doyle et al. | Jul 2014 | A1 |
| 20140230021 | Birtwhistle et al. | Aug 2014 | A1 |
| 20140276554 | Finan et al. | Sep 2014 | A1 |
| 20140276556 | Saint et al. | Sep 2014 | A1 |
| 20140278123 | Prodhom et al. | Sep 2014 | A1 |
| 20140309615 | Mazlish | Oct 2014 | A1 |
| 20140316379 | Sonderegger et al. | Oct 2014 | A1 |
| 20140325065 | Birtwhistle et al. | Oct 2014 | A1 |
| 20150018633 | Kovachev et al. | Jan 2015 | A1 |
| 20150025329 | Amarasingham et al. | Jan 2015 | A1 |
| 20150025495 | Peyser | Jan 2015 | A1 |
| 20150120317 | Mayou et al. | Apr 2015 | A1 |
| 20150134265 | Kohlbrecher et al. | May 2015 | A1 |
| 20150165119 | Palerm et al. | Jun 2015 | A1 |
| 20150173674 | Hayes et al. | Jun 2015 | A1 |
| 20150213217 | Amarasingham et al. | Jul 2015 | A1 |
| 20150217052 | Keenan et al. | Aug 2015 | A1 |
| 20150217053 | Booth et al. | Aug 2015 | A1 |
| 20150265767 | Vazquez et al. | Sep 2015 | A1 |
| 20150306314 | Doyle et al. | Oct 2015 | A1 |
| 20150351671 | Vanslyke et al. | Dec 2015 | A1 |
| 20150366945 | Greene | Dec 2015 | A1 |
| 20160015891 | Papiorek | Jan 2016 | A1 |
| 20160038673 | Morales | Feb 2016 | A1 |
| 20160038689 | Lee et al. | Feb 2016 | A1 |
| 20160051749 | Istoc | Feb 2016 | A1 |
| 20160082187 | Schaible et al. | Mar 2016 | A1 |
| 20160089494 | Guerrini | Mar 2016 | A1 |
| 20160175520 | Palerm et al. | Jun 2016 | A1 |
| 20160228641 | Gescheit et al. | Aug 2016 | A1 |
| 20160243318 | Despa et al. | Aug 2016 | A1 |
| 20160256087 | Doyle et al. | Sep 2016 | A1 |
| 20160287512 | Cooper et al. | Oct 2016 | A1 |
| 20160302054 | Kimura et al. | Oct 2016 | A1 |
| 20160331310 | Kovatchev | Nov 2016 | A1 |
| 20160354543 | Cinar et al. | Dec 2016 | A1 |
| 20170049386 | Abraham et al. | Feb 2017 | A1 |
| 20170143899 | Gondhalekar et al. | May 2017 | A1 |
| 20170143900 | Rioux et al. | May 2017 | A1 |
| 20170156682 | Doyle et al. | Jun 2017 | A1 |
| 20170173261 | OConnor et al. | Jun 2017 | A1 |
| 20170189625 | Cirillo et al. | Jul 2017 | A1 |
| 20170281877 | Marlin et al. | Oct 2017 | A1 |
| 20170296746 | Chen et al. | Oct 2017 | A1 |
| 20170311903 | Davis et al. | Nov 2017 | A1 |
| 20170348482 | Duke et al. | Dec 2017 | A1 |
| 20180036495 | Searle et al. | Feb 2018 | A1 |
| 20180040255 | Freeman et al. | Feb 2018 | A1 |
| 20180075200 | Davis et al. | Mar 2018 | A1 |
| 20180075201 | Davis et al. | Mar 2018 | A1 |
| 20180075202 | Davis et al. | Mar 2018 | A1 |
| 20180092576 | Ambrosio | Apr 2018 | A1 |
| 20180126073 | Wu et al. | May 2018 | A1 |
| 20180169334 | Grosman et al. | Jun 2018 | A1 |
| 20180200434 | Mazlish et al. | Jul 2018 | A1 |
| 20180200438 | Mazlish et al. | Jul 2018 | A1 |
| 20180200441 | Desborough et al. | Jul 2018 | A1 |
| 20180204636 | Edwards et al. | Jul 2018 | A1 |
| 20180277253 | Gondhalekar et al. | Sep 2018 | A1 |
| 20180289891 | Finan et al. | Oct 2018 | A1 |
| 20180296757 | Finan et al. | Oct 2018 | A1 |
| 20180342317 | Skirble et al. | Nov 2018 | A1 |
| 20180369479 | Hayter et al. | Dec 2018 | A1 |
| 20190076600 | Grosman et al. | Mar 2019 | A1 |
| 20190240403 | Palerm et al. | Aug 2019 | A1 |
| 20190290844 | Monirabbasi et al. | Sep 2019 | A1 |
| 20190336683 | O'Connor et al. | Nov 2019 | A1 |
| 20190336684 | OConnor et al. | Nov 2019 | A1 |
| 20190348157 | Booth et al. | Nov 2019 | A1 |
| 20200046268 | Patek et al. | Feb 2020 | A1 |
| 20200101222 | Lintereur et al. | Apr 2020 | A1 |
| 20200101223 | Lintereur et al. | Apr 2020 | A1 |
| 20200101225 | OConnor et al. | Apr 2020 | A1 |
| 20200219625 | Kahlbaugh | Jul 2020 | A1 |
| 20200342974 | Chen et al. | Oct 2020 | A1 |
| 20210050085 | Hayter et al. | Feb 2021 | A1 |
| 20210098105 | Lee et al. | Apr 2021 | A1 |
| 20220023536 | Graham et al. | Jan 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 2015200834 | Mar 2015 | AU |
| 2015301146 | Mar 2017 | AU |
| 1297140 | May 2001 | CN |
| 19756872 | Jul 1999 | DE |
| 0341049 | Nov 1989 | EP |
| 0496305 | Jul 1992 | EP |
| 0549341 | Jun 1993 | EP |
| 1491144 | Dec 2004 | EP |
| 1571582 | Sep 2005 | EP |
| 0801578 | Jul 2006 | EP |
| 2666520 | Oct 2009 | EP |
| 2139382 | Jan 2010 | EP |
| 2397181 | Dec 2011 | EP |
| 2695573 | Feb 2014 | EP |
| 2830499 | Feb 2015 | EP |
| 2943149 | Nov 2015 | EP |
| 3177344 | Jun 2017 | EP |
| 3314548 | May 2018 | EP |
| 2897071 | May 2019 | EP |
| 3607985 | Feb 2020 | EP |
| 2443261 | Apr 2008 | GB |
| 51125993 | Nov 1976 | JP |
| 02131777 | May 1990 | JP |
| 2004283378 | Oct 2004 | JP |
| 2017525451 | Sep 2017 | JP |
| 2018153569 | Oct 2018 | JP |
| 2019525276 | Sep 2019 | JP |
| 200740148 | Oct 2007 | TW |
| M452390 | May 2013 | TW |
| 9800193 | Jan 1998 | WO |
| 9956803 | Nov 1999 | WO |
| 0030705 | Jun 2000 | WO |
| 0032258 | Jun 2000 | WO |
| 0172354 | Oct 2001 | WO |
| 2002015954 | Feb 2002 | WO |
| 0243866 | Jun 2002 | WO |
| 02082990 | Oct 2002 | WO |
| 03016882 | Feb 2003 | WO |
| 03039362 | May 2003 | WO |
| 03045233 | Jun 2003 | WO |
| 2004043250 | May 2004 | WO |
| 04092715 | Oct 2004 | WO |
| 2005051170 | Jun 2005 | WO |
| 2005082436 | Sep 2005 | WO |
| 05110601 | Nov 2005 | WO |
| 2005113036 | Dec 2005 | WO |
| 2006053007 | May 2006 | WO |
| 2007064835 | Jun 2007 | WO |
| 2007078937 | Jul 2007 | WO |
| 2008024810 | Feb 2008 | WO |
| 2008029403 | Mar 2008 | WO |
| 2008133702 | Nov 2008 | WO |
| 2009045462 | Apr 2009 | WO |
| 2009049252 | Apr 2009 | WO |
| 2009066287 | May 2009 | WO |
| 2009066288 | May 2009 | WO |
| 2009098648 | Aug 2009 | WO |
| 2009134380 | Nov 2009 | WO |
| 2010053702 | May 2010 | WO |
| 2010132077 | Nov 2010 | WO |
| 2010138848 | Dec 2010 | WO |
| 2010147659 | Dec 2010 | WO |
| 2011095483 | Aug 2011 | WO |
| 2012045667 | Apr 2012 | WO |
| 2012108959 | Aug 2012 | WO |
| 2012134588 | Oct 2012 | WO |
| 2012177353 | Dec 2012 | WO |
| 2012178134 | Dec 2012 | WO |
| 2013078200 | May 2013 | WO |
| 2013134486 | Sep 2013 | WO |
| 20130149186 | Oct 2013 | WO |
| 2013177565 | Nov 2013 | WO |
| 2013182321 | Dec 2013 | WO |
| 2014109898 | Jul 2014 | WO |
| 2014110538 | Jul 2014 | WO |
| 2014194183 | Dec 2014 | WO |
| 2015056259 | Apr 2015 | WO |
| 2015061493 | Apr 2015 | WO |
| 2015073211 | May 2015 | WO |
| 2015081337 | Jun 2015 | WO |
| 2015187366 | Dec 2015 | WO |
| 2016004088 | Jan 2016 | WO |
| 2016022650 | Feb 2016 | WO |
| 2016041873 | Mar 2016 | WO |
| 2016089702 | Jun 2016 | WO |
| 2016141082 | Sep 2016 | WO |
| 2016161254 | Oct 2016 | WO |
| 2017004278 | Jan 2017 | WO |
| 2017091624 | Jun 2017 | WO |
| 2017105600 | Jun 2017 | WO |
| 2017184988 | Oct 2017 | WO |
| 2017205816 | Nov 2017 | WO |
| 2018009614 | Jan 2018 | WO |
| 2018067748 | Apr 2018 | WO |
| 2018120104 | Jul 2018 | WO |
| 2018136799 | Jul 2018 | WO |
| 2018204568 | Nov 2018 | WO |
| 2019077482 | Apr 2019 | WO |
| 2019094440 | May 2019 | WO |
| 2019213493 | Nov 2019 | WO |
| 2019246381 | Dec 2019 | WO |
| 2020081393 | Apr 2020 | WO |
| 2021011738 | Jan 2021 | WO |
| Entry |
|---|
| US 5,954,699 A, 09/1999, Jost et al. (withdrawn) |
| Montaser Eslam et al., “Seasonal Local Models for Glucose Prediction in Type 1 Diabetes”, IEE Journal of Biomedical and Health Informatics, IEEE, Piscataway, NJ, USA, vol. 24, No. 7, Nov. 29, 2019, pp. 2064-2072. |
| Samadi Sediqeh et al., “Automatic Detection and Estimation of Unannouced Meals for Multivariable Artificial Pancreas System”, Diabetis Technology & Therapeutics, vol. 20m No. 3, Mar. 1, 2018, pp. 235-246. |
| Samadi Sediqeh et al., “Meal Detection and Carbohydrate Estimation Using Continuous Glucose Sensor Data” IEEE Journal of Biomedical and Health Informatics, IEEE, Piscataway, NJ, USA, vol. 21, No. 3, May 1, 2017, pp. 619-627. |
| Khodaei et al., “Physiological Closed-Loop Contol (PCLC) Systems: Review of a Modern Frontier in Automation”, IEEE Access, IEEE, USA, vol. 8, Jan. 20, 2020, pp. 23965-24005. |
| E. Atlas et al., “MD-Logic Artificial Pancreas System: A pilot study in adults with type 1 diabetes”, Diabetes Care, vol. 33, No. 5, Feb. 11, 2010, pp. 1071-1076. |
| Anonymous: “Fuzzy control system”, Wikipedia, Jan. 10, 2020. URL: https://en.wikipedia.org/w/index.php?title=Fuzzy_control_system&oldid=935091190 Retrieved: May 25, 2021. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/016283, dated Jun. 2, 2021, 15 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/022694, dated Jun. 25, 2021, 13 pages. |
| European Search Report for the European Patent Application No. 21168591.2, dated Oct. 13, 2021, 4 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/041954, dated Oct. 25, 2021, 13 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/047771, dated Dec. 22, 2021, 11 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/052855, dated Dec. 22, 2021, 11 pages. |
| Anonymous: “Artificial pancreas—Wikipedia”, Mar. 13, 2018 (Mar. 13, 2018), XP055603712, Retrieved from the Internet: URL: https://en.wikipedia.org/wiki/Artificial_pancreas [retrieved on Jul. 9, 2019] section “Medical Equipment” and the figure labeled “The medical equipment approach to an artifical pancreas”. |
| Kaveh et al., “Blood Glucose Regulation via Double Loop Higher Order Sliding Mode Control and Multiple Sampling Rate.” Paper presented at the proceedings of the 17th IFAC World Congress, Seoul, Korea (Jul. 2008). |
| Dassau et al., “Real-Time Hypoglycemia Prediction Suite Using Contineous Glucose Monitoring,” Diabetes Care, vol. 33, No. 6, 1249-1254 (2010). |
| International Search Report and Written Opinion for International Patent Application No. PCT/US17/53262, dated Dec. 13, 2017, 8 pages. |
| Van Heusden et al., “Control-Relevant Models for Glucose Control using a Priori Patient Characteristics”, IEEE Transactions on Biomedical Engineering, vol. 59, No. 7, (Jul. 1, 2012) pp. 1839-1849. |
| Doyle III et al., “Run-to-Run Control Strategy for Diabetes Management.” Paper presented at 23rd Annual International Conference of the IEEE Engineering in Medicine and Biology Society, Istanbul, Turkey (Oct. 2001). |
| Bequette, B.W., and Desemone, J., “Intelligent Dosing Systems”: Need for Design and Analysis Based on Control Theory, Diabetes Technology and Therapeutics 9(6): 868-873 (2004). |
| Parker et al., “A Model-Based Agorithm for Blood Gucose Control in Type 1 Diabetic Patients.” IEEE Transactions on Biomedical Engineering, 46 (2) 148-147 (1999). |
| International Search Report and Written Opinion for International Patent Application No. PCT/US2017/015601, dated May 16, 2017, 12 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2018/018901, dated Aug. 6, 2018, 12 pages. |
| International Search Report and Written Opinion for International Patent Application No. PCT/US2018/052467, dated Jan. 4, 2019, 13 pages. |
| “How to Create a QR Code that Deep Links to Your Mobile App”, Pure Oxygen Labs, web<https://pureoxygenlabs.com/how-to-create-a-qr-codes-that-deep-link-to-your-mobile-app/>. Year:2017. |
| “Read NFC Tags with an iPHone App on iOS 11”, GoToTags, Sep. 11, 2017, web <https://gototags.com/blog/read-nfc-tags-with-an-iphone-app-on-ios-11/>. (Year:2017). |
| International Search Report and Written Opinion for International Patent Application No. PCT/US2016/063350, dated Mar. 27, 2017, 9 pages. |
| Extended Search Report dated Aug. 13, 2018, issued in European Patent Application No. 16753053.4, 9 pages. |
| International Search Report and Written Opinion for International Patent Application No. PCT/US16/18452, dated Apr. 29, 2015, 9 pages. |
| International Preliminary Report on Patentability dated Aug. 31, 2017, issued in PCT Patent Application No. PCT/US2016/018452, 7 pages. |
| International Search Report and Written Opinion for International Patent Application No. PCT/US2019/055862, dated Mar. 11, 2020. |
| Unger, Jeff, et al., “Glucose Control in the Hospitalized Patient,” Emerg. Med 36(9):12-18 (2004). |
| Glucommander FAQ downloaded from https://adaendo.com/GlucommanderFAQ.html on Mar. 16, 2009. |
| Finfer, Simon & Heritier, Stephane. (2009). The NICE-SUGAR (Normoglycaemia in Intensive Care Evaluation and Survival Using Glucose Algorithm Regulation) Study: statistical analysis plan. Critical care and resuscitation : journal of the Australasian Academy of Critical Care Medicine. 11. 46-57. |
| Letters to the Editor regarding “Glucose Control in Critically Ill Patients,” N Engl J Med 361: 1, Jul. 2, 2009. |
| “Medtronic is Leading a Highly Attractive Growth Market,” Jun. 2, 2009. |
| Davidson, Paul C., et al. “Glucommander: An Adaptive, Computer-Directed System for IV Insulin Shown to be Safe, Simple, and Effective in 120,618 Hours of Operation,” Atlanta Diabetes Associates presentation Nov. 16, 2003. |
| Davidson, Paul C., et al. “Pumpmaster and Glucommander,” presented at the MiniMed Symposium, Atlanta GA, Dec. 13, 2003. |
| Kanji S., et al. “Reliability of point-of-care testing for glucose measurement in critically ill adults,” Critical Care Med, vol. 33, No. 12, pp. 2778-2785, 2005. |
| Krinsley James S., “Severe hypoglycemia in critically ill patients: Risk factors and outcomes,” Critical Care Med, vol. 35, No. 10, pp. 1-6, 2007. |
| International Searching Authority, Invitation to Pay Additional Fees, International Application No. PCT/US2006/004929, dated Jul. 27, 2006. |
| Farkas et al. ““Single-Versus Triple-Lumen Central Catheter-Related Sepsis: A Prospective Randomized Study in a Critically Ill Population”” The American Journal of Medicine Sep. 1992 vol. 93 p. 277-282. |
| Davidson, Paul C., et al., A computer-directed intravenous insulin system shown to be safe, simple,and effective in 120,618 h of operation, Diabetes Care, vol. 28, No. 10, Oct. 2005, pp. 2418-2423. |
| Gorke, A. “Microbial contamination of haemodialysis catheter connections.” EDTNA/ERCA journal (English ed.) vol. 31,2 (2005): 79-84. doi:10.1111/j.1755-6686.2005.tb00399.x. |
| Lovich et al. “Central venous catheter infusions: A laboratory model shows large differences in drug delivery dynamics related to catheter dead volume” Critical Care Med 2007 vol. 35, No. 12. |
| Van Den Berghe, Greet, M.D., Ph.D., et al., Intensive Insulin Therapy in Critically Ill Patients, The New England Journal of Medicine, vol. 345, No. 19, Nov. 8, 2001, pp. 1359-1367. |
| Templeton et al, “Multilumen Central Venous Catheters Increase Risk for Catheter-Related Bloodstream Infection Prospective Surveillance Study” Infection 2008; 36: 322-327. |
| Wilson, George S., et al., Progress toward the Development of an Implantable Sensor for Glucose, Clin. Chem., vol. 38, No. 9, 1992, pp. 1613-1617. |
| Yeung et al. “Infection Rate for Single Lumen v Triple Lumen Subclavian Catheters” Infection Control and Hospital Epidemiology, vol. 9, No. 4 (Apr. 1988) pp. 154-158 The University of Chicago Press. |
| International Search Report and Written Opinion, International Application No. PCT/US2010/033794 dated Jul. 16, 2010. |
| International Search Report and Written Opinion in PCT/US2008/079641 dated Feb. 25, 2009. |
| Berger, ““Measurement of Analytes in Human Serum and Whole Blood Samples by Near-Infrared Raman Spectroscopy,”” Ph.D. Thesis, Massachusetts Institute of Technology, Chapter 4, pp. 50-73, 1998. |
| Berger, “An Enhanced Algorithm for Linear Multivariate Calibration,” Analytical Chemistry, vol. 70, No. 3, pp. 623-627, Feb. 1, 1998. |
| Billman et al.,“Clinical Performance of an In line Ex-Vivo Point of Care Monitor: A Multicenter Study,” Clinical Chemistry 48: 11, pp. 2030-2043, 2002. |
| Widness et al., “Clinical Performance on an In-Line Point-of-Care Monitor in Neonates”; Pediatrics, vol. 106, No. 3, pp. 497-504, Sep. 2000. |
| Finkielman et al., “Agreement Between Bedside Blood and Plasma Glucose Measurement in the ICU Setting”; retrieved from http://www.chestjournal.org; CHEST/127/5/May 2005. |
| Glucon Critical Care Blood Glucose Monitor; Glucon; retrieved from http://www.glucon.com. |
| Fogt, et al., “Development and Evaluation of a Glucose Analyzer for a Glucose-Controlled Insulin Infusion System (Biostator)”; Clinical Chemistry, vol. 24, No. 8, pp. 1366-1372, 1978. |
| Vonach et al., “Application of Mid-Infrared Transmission Spectrometry to the Direct Determination of Glucose in Whole Blood,” Applied Spectroscopy, vol. 52, No. 6, 1998, pp. 820-822. |
| Muniyappa et al., “Current Approaches for assessing insulin sensitivity and resistance in vivo: advantages, limitations, and appropriate usage,” AJP—ndocrinol Metab, vol. 294, E15-E26, first published Oct. 23, 2007. |
| R Anthony Shaw, et al., “Infrared Spectroscopy in Clinical and Dianostic Analysis,” Encyclopedia of Analytical Chemistry, ed. Robert A. Meyers, John Wiley & Sons, Ltd., pp. 1-20, 2000. |
| International Preliminary Report on Patentability for the International Patent Application No. PCT/US2019/053603, dated Apr. 8, 2021, 9 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2019/053603, dated Jan. 7, 2020, 16 pages. |
| Dassau et al., “Detection of a meal using continuous glucose monitoring: Implications for an artificial [beta]-cell.” Diabetes Care, American Diabetes Association, Alexandria, VA, US, 31(2):295-300 (2008). |
| Cameron et al., “Probabilistic Evolving Meal Detection and Estimation of Meal Total Glucose Appearance Author Affiliations”, J Diabetes Sci and Tech,vol., Diabetes Technology Society ;(5):1022-1030 (2009). |
| Lee et al., “A closed-loop artificial pancreas based on model predictive control: Human-friendly identification and automatic meal disturbance rejection”, Biomedical Signal Processing and Control, Elsevier, Amsterdam, NL, 4(4):1746-8094 (2009). |
| International Search Report and Written Opinion for the IntemationalPatent Application No. PCT/US2021/018297, mailed May 18, 2021, 18 pages. |
| An Emilia Fushimi: “Artificial Pancreas: Evaluating the ARG Algorithm Without Meal Annoucement”, Journal of Diabetes Science and Technology Diabetes Technology Society, Mar. 22, 2019, pp. 1025-1043. |
| International Search Report and Written Opinion for the InternationalPatent Application No. PCT/US2021/017441, dated May 25, 2021, 12 pages. |
| International Search Report and Written Opinion for the IntemationalPatent Application No. PCT/US2021/017664, dated May 26, 2021, 16 pages. |
| Mirko Messori et al: “Individualized model predictive control for the artificial pancreas: In silico evaluation of closed-loop glucose control”, IEEE Control Systems, vol. 38, No. 1, Feb. 1, 2018, pp. 86-104. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/017662, dated May 26, 2021, 14 pages. |
| Anonymous: “Reservoir Best Practice and Top Tips” Feb. 7, 2016, URL: https://www.medtronic-diabetes.co.uk/blog/reservoir-best-practice-and-top-tips, p. 1. |
| Gildon Bradford: “InPen Smart Insulin Pen System: Product Review and User Experience” Diabetes Spectrum, vol. 31, No. 4, Nov. 15, 2018, pp. 354-358. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/016050, dated May 27, 2021, 16 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2020/065226, dated May 31, 2021, 18 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/017659, dated May 31, 2021, 13 pages. |
| Anonymous: “Fuzzy control system”, Wikipedia, Jan. 10, 2020. URL: https://en.wikipedia.org/w/index.php?title=Fuzzy_control_system&oldid=935091190 |
| International Search Report and Written Opinion for International Patent Application No. PCT/US2021/051027, dated Jan. 7, 2022, 16 pages. |
| International Search Report and Written Opinion for International Patent Application No. PCT/US2021/052372, dated Jan. 26, 2022, 15 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/046607, dated Jan. 31, 2022, 20 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2021/055745, dated Feb. 14, 2022, 13 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2020/052125, dated Aug. 12, 2020, 15 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2020/050332, dated Sep. 12, 2020, 12 pages. |
| European Patent Office, “Notification of Transmittal of the ISR and the Written Opinion of the International Searching Authority, or the Declaration,” in PCT Application No. PCT/GB2015/050248, dated Jun. 23, 2015, 12 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2022/013470, dated May 6, 2022, 14 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2022/013473, dated May 6, 2022, 13 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2022/019079, dated Jun. 2, 2022, 14 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2022/018453, dated Jun. 2, 2022, 13 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US22/018700, dated Jun. 7, 2022, 13 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US22/019080, dated Jun. 7, 2022, 14 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US22/019664, dated Jun. 7, 2022, 14 pages. |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US21/060618, dated Mar. 21, 2022, 15 pages. |
| Herrero Pau et al: “Enhancing automatic closed-loop glucose control in type 1 diabetes with an adaptive meal polus calculator-in silicoevaluation under intra-day variability”, Computer Methods and Programs in Biomedicine, Elsevier, Amsterdam, NL, vol. 146, Jun. 1, 2017 (Jun. 1, 2017), pp. 125-131, XP085115607, ISSN: 0169-2607, D0I:10.1016/J.CMPB.2017.05.010. |
| Marie Aude Qemerais: “Preliminary Evaluation of a New Semi-Closed-Loop Insulin Therapy System over the prandial period in Adult Patients with type I diabetes: the WP6. 0 Diabeloop Study”, Journal of Diabetes Science and Technology Diabetes Technology Society Reprintsand permissions, Jan. 1, 2014, pp. 1177-1184, Retrieved from the Internet: URL:http://journals.sagepub.com/doi/pdf/10.1177/1932296814545668 [retrieved on Jun. 6, 2022] chapter “Functioning of the Algorithm” chapter “Statistical Analysis” p. 1183, left-hand column, line 16- line 23. |
| Anonymous: “Kernel density estimation”, Wikipedia, Nov. 13, 2020 (Nov. 13, 2020), pp. 1-12, XP055895569, Retrieved from the Internet: URL:https://en.wikipedia.org/w/index.php?title=Kemnel_density_estimation&oldid=988508333 [retrieved on Jun. 6, 2022]. |
| Anonymous: “openaps / oref0 /lib/determine-basal-js”, openaps repository, Nov. 9, 2019 (Nov. 9, 2019), pp. 1-17, XP055900283, Retrieved from the Internet: URL:https://github.com/openaps/oref0/blob/master/lib/determine-basal/determine-basal.js [retrieved on Jun. 6, 2022] line 116-line 118, line 439-line 446. |
| Anonymous: “AndroidAPS screens”, AndroidAPS documentation, Oct. 4, 2020 (Oct. 4, 2020), pp. 1-12, XP055894824, Retrieved from the Internet: URL:https://github.com/openaps/AndroidAPSdocs/blob/25d8acf8b28262b411b34f416f173ac0814d7e14/docs/EN/Getting-Started/Screenshots.md [retrieved on Jun. 6, 2022]. |
| Kozak Milos et al: “Issue #2473 of AndroidAPS”, MilosKozak / AndroidAPS Public repository, Mar. 4, 2020 (Mar. 4, 2020), pp. 1-4, XP055900328, Retrieved from the Internet: URL:https://github.com/MilosKozak/AndroidAPS/isues/2473 [retrieved on Jun. 6, 2022]. |
| Medication Bar Code System Implementation Planning Section I: A Bar Code Primer for Leaders, Aug. 2013. |
| Medication Bar Code System Implementation Planning Section II: Building the Case for Automated Identification of Medications, Aug. 2013. |
| Villareal et al. (2009) in: Distr. Comp. Art. Intell. Bioninf. Soft Comp. Amb. Ass. Living; Int. Work Conf. Art. Neural Networks (IWANN) 2009, Leet. Notes Comp. Sci vol. 5518; S. Omatu et al. (Eds.), pp. 870-877. |
| Fox, Ian G.; Machine Learning for Physiological Time Series: Representing and Controlling Blood Glucose for Diabetes Management; University of Michigan. ProQuest Dissertations Publishing, 2020. 28240142. (Year: 2020). |
| International Search Report and Written Opinion for the International Patent Application No. PCT/US2022/012896, dated Apr. 22, 2022, 15 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20200101225 A1 | Apr 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62738531 | Sep 2018 | US |
