Patent Grant
12128213
The general field of this disclosure is glucose sensing and disease management systems.
Diabetes is a chronic disease that impacts many individuals, both adults and children. The management of diabetes may include the measurement of glucose within the interstitial space including blood and/or interstitial fluid of a patient and administration of insulin to the patient. A closed loop insulin administration system includes both a sensor to take glucose measurements from the interstitial space including blood and/or interstitial fluid of the patient and an insulin administration device which administers insulin to the patient based on the glucose measurements. Closed loop insulin administration systems allow individuals impacted by diabetes to go about daily life with much less worry about their insulin or glucose levels which can vastly improve a diabetic's quality of life.
The present disclosure provides redundant staggered glucose sensors and disease management system. The system includes a system which includes a glucose sensor and insulin pump to administer insulin to a patient based on glucose measurements from the glucose sensor. The system further includes another system with a separate glucose sensor. The separate glucose sensor provides redundancy for the system to ensure continuous monitoring when one of the glucose sensors is in a warmup period, a stabilization period, or an end of life period.
In some configurations, a disease management system can include a first disease management system and a second disease management system. The first disease management system can include a first glucose sensor and a first insulin pump. The second disease management system can include a second glucose sensor and a second insulin pump. In some configurations, the first disease management system and second disease management system can be configured to simultaneously attach to a patient and communicate with each other. In some configurations, the first glucose sensor can be in a settling period, the second glucose sensor is configured to provide patient glucose information to at least one of the first disease management system or the second disease management system.
In some configurations, the settling period can include a warmup period and/or a stabilization period.
In some configurations, the at least one of the first disease management system or the second disease management system can be configured to calculate a proper dosage of insulin based on patient glucose information from at least one of the first glucose sensor or the second glucose sensor. In some configurations, calculating the proper dosage of insulin can be further based on patient entered data. The patient entered data can include age, height, weight, and/or sex. In some configurations, calculating the proper dosage of insulin is further based on a customized glucose metabolization rating for the patient. The customized glucose metabolization rating can be based on the patient's weight, age, digestion rate, and/or insulin sensitivity.
In some configurations, the first disease management system or the second disease management system can be configured to communicate with a user device, such as a mobile phone, smart phone, tablet, computer, smart watch, other wearable device, or any other electronic user device.
In some configurations, the first disease management system or the second disease management system can be configured to communicate with user device through Bluetooth and/or RF signal.
In some configurations, at least one of the first disease management system or the second disease management system can be configured to communicate with the user device. The user device can be configured to communicate with the smartwatch.
In some configurations, a first disease management system can further include a first insulin storage container fluidly connected to the first insulin pump. The first insulin pump can be fluidly connected to a needle which is capable of being inserted into a cannula that is implanted into a patient. The insulin storage container can include a flexible insulin pouch and the first disease management system can further include a spring that can be configured to apply pressure to the flexible insulin pouch. The flexible insulin pouch can be prefilled with insulin.
In some configurations, a first insulin pump can include a valve that is controlled in order administer a specific dosage of insulin to the patient. The valve can include 3 or more piezoelectric crystal valves. The valve can include 3 or more voice coil valves. The valve can include 3 or more piezoelectric stack valves. The first insulin pump can further include a filter connected between the valve and the needle. The valve can include a beginning valve, an end valve, and one or more intermediate valves located between the beginning valve and the end valve, the intermediate valves individually controllable in order to administer the specific dosage of insulin.
In some configurations, the first insulin pump can include a peristaltic pump. The peristaltic pump can include a circular gear; a circular portion attached to the circular gear such that when the circular gear rotates the circular portion can rotate at the same rotational speed, the circular portion located below the circular gear; two or more rollers located radially outward from the circular portion and in physical contact with the circular portion such that the roller can rotate as the circular portion rotates; a casing which wraps around the circumference of the rollers and the circular portion such that the casing and the rollers cooperate to form a circular channel, wherein the rollers are located at an inside portion of the circular channel and the casing is located on the outside of the circular channel; and a tubing located within the circular channel such that the tubing physically contacts both the casing and the rollers, wherein when the circular gear is rotated, the circular portion drives the two or more rollers which apply pressure to the tubing such that liquid within the tubing is driven from an inlet of the tubing to an outlet of the tubing.
In some configurations, a peristaltic pump can be a ratcheting peristaltic pump comprising a ratcheting driving mechanism in physical contact with the circular gear, wherein the ratcheting driving mechanism is capable of ratcheting teeth within the circular gear at one tooth at a time. The peristaltic pump can include: a circular gear with a circular hollow center; two or more rollers located within the circular hollow center and in physical contact with an inner wall of the circular gear such that the rollers rotate when the circular gear rotates; a stationary inner portion which is fixed, the stationary inner portion and the roller cooperate to form a circular channel, wherein the rollers are located at an outside portion of the circular channel and the stationary inner portion is located at the inner portion of the channel; and a tubing located within the circular channel such that the tubing physical contacts both the stationary inner portion and the rollers, wherein when the circular gear is rotated, the two or more rollers rotate which applies pressure to the tubing such that liquid within the tubing is driven from an inlet of the tubing to an outlet of the tubing. The peristaltic pump can include a ratcheting peristaltic pump can include a ratcheting driving mechanism in physical contact with the circular gear, wherein the ratcheting driving mechanism is capable of ratcheting teeth within the circular gear at one tooth at a time.
In some configurations, the first disease management system can include a case; a computing device capable of controlling the first insulin pump and receiving measurements from the first glucose sensor; a battery configured to power the first glucose sensor, the first insulin pump; the computing device; and an antenna connected to the computing device. The computer device can be configured to broadcast information through the antenna. The computing device, battery, first glucose sensor and the first insulin pump can be housed within the case. The antenna can be located outside or inside of the case. The case can include one or more needle insertion holes capable of having a needle inserted. The first disease management system can be mounted to a patient through an adhesive which connects to the case. The first disease management system can further include at least one of a light source, a photodiode, a vibration device, a tissue impedance measurement device, an insulin cannula impedance measurement device, an accelerometer, or a gyroscope. The first disease management system can further include one or more flexion points which may allow the first disease management system to flex. The one or more flexion points can include two flexion points.
In some configurations, the first disease management system can include: a first case housing the first insulin pump, a first computing device, an antenna, and a first battery; and a second case housing the first glucose sensor, a second computing device, an antenna, and a second battery. At least one of the first case or the second case further can house at least one of a light source, a photodiode, a vibration device, an accelerometer, or a gyroscope.
In some configurations, a peristaltic pump can include: a circular gear; a circular portion attached to the circular gear such that when the circular gear rotates the circular portion can rotate at the same rotational speed, the circular portion located below the circular gear; two or more rollers located radially outward from the circular portion and in physical contact with the circular portion such that the roller can rotate as the circular portion rotates; a casing which can wrap around the circumference of the rollers and the circular portion such as to cooperate to form a circular channel, wherein the rollers are located at an inside portion of the circular channel and the casing is located on the outside of the circular channel; and a tubing located within the circular channel such that the tubing physically contacts both the casing and the rollers, wherein when the circular gear is rotated, the circular portion can drive the two or more rollers which apply pressure to the tubing such that liquid within the tubing is driven from an inlet of the tubing to an outlet of the tubing.
In some configurations, a peristaltic pump can include: a circular gear with a circular hollow center; two or more rollers located within the circular hollow center and in physical contact with an inner wall of the circular gear such that the rollers can rotate when the circular gear rotates; a stationary inner portion which can be fixed, the stationary inner portion and the roller can cooperate to form a circular channel, wherein the roller can be located at an outside portion of the circular channel and the stationary inner portion can be located at the inner portion of the channel; and a tubing located within the circular channel such that the tubing physical can contact both the stationary inner portion and the rollers, wherein when the circular gear is rotated, the two or more rollers rotate which can apply pressure to the tubing such that liquid within the tubing is driven from an inlet of the tubing to an outlet of the tubing.
In some configurations, a ratcheting peristaltic pump can include: a peristaltic pump, such as described above; a ratcheting driving mechanism in physical contact with the circular gear, wherein the ratcheting driving mechanism can be capable of ratcheting teeth within the circular gear at one tooth at a time. The ratcheting driving mechanism can include a solenoid, muscle wire, a ratchet motor, and/or a direct current motor.
In some configurations, a method of priming a peristaltic pump can include: providing a peristaltic pump; connecting the inlet of the tubing an insulin source; running the peristaltic pump to pump insulin from the insulin source from the inlet to the outlet until insulin exits the outlet; connecting the outlet of the tubing to a buffered solution source; running the peristaltic pump to pump buffered solution from the buffered solution source until the buffered solution enters all of the tubing contacting each of the rollers.
In some configurations, a primed peristaltic pump can include: a peristaltic pump such as described above, wherein the input of the tubing is connected to an insulin source, wherein the portion of the tubing from the closest roller to the input of the tubing all the way to the output of the tubing is filled with a buffered solution, and wherein the portion of the tubing starting where the buffered solution is located all the way to the input of the tubing connected to the insulin source is filled with insulin.
In some configurations, a method of using a primed peristaltic pump can include: providing the primed peristaltic pump; connecting the outlet of the tubing to a patient; monitoring the patient's glucose level; determining the patient's glucose level is at a safe range to accept a small dosage of insulin; operating the primed peristaltic pump until all of the buffered solution has exited the tubing; and verifying that the patient's glucose level has not changed.
In some configurations, a method of operating redundant glucose sensors can include: operating a first glucose sensor on a patient; operating a second glucose sensor on the patient; wherein at least one of the first glucose sensor or second glucose sensor is not in a warmup period, a stabilization period, or an end of life period; operating an insulin pump based on the measurements of the first glucose sensor or second glucose sensor not operating during a warmup period, a stabilization period, or an end of life period. The first glucose sensor or the second glucose sensor and the insulin pump can be housed in one unit. The insulin pump and at least one of the first glucose sensor or second glucose sensor operating during a warmup period, a stabilization period, or an end of life period can be housed in one unit. The first glucose sensor or second glucose sensor not operating during a warmup period, a stabilization period, or an end of life period and another insulin pump can be housed in another unit. The insulin pump can be based on the measurements of the first glucose sensor or second glucose sensor not operating during a warmup period when the insulin pump is not operating. The one unit can include a first insulin source storing insulin and the another unit can include a second insulin source storing insulin, and wherein the insulin pump and another insulin pump deliver insulin from the first insulin source and the second insulin source such that the insulin in the first insulin source and the second insulin source is emptied before the insulin in the first insulin source and the second insulin source expires.
In some configurations, a method can further include notifying the patient when it is time to replace the one unit or the other unit. Notifying the patient can include sending a message through the patient's user device or enabling the one unit or the other unit to vibrate.
In some configurations, the first glucose sensor, the second glucose sensor, and the insulin pump can all be housed in separate units. The first glucose sensor or the second glucose sensor and the insulin pump can be housed in one unit. The first glucose sensor or the second glucose sensor and another insulin pump can be housed in one unit, and wherein the insulin pump can be housed in another system.
In some configurations, a method can include replacing the first glucose sensor or the second glucose sensor with a third glucose sensor when the not replaced first glucose sensor or second glucose sensor is not operating in a warmup period, a stabilization period, or an end of life period, wherein the not replaced first glucose sensor or second glucose sensor will not be operating in an end of life period when the third glucose sensor is running in a warmup period or a stabilization period.
In some configurations, a method of using an applicator for applying a disease management system, the method can include: providing the disease management system within packaging; opening the top of the packaging to expose the top of the disease management system, wherein the disease management system is preloaded with needles, the needles including tips which face towards the bottom of the packaging; grasping the disease management system within the applicator; positioning the applicator with the disease management system on a patient; launching the disease management system onto the patient such that the needles puncture the patient's skin, wherein the applicator comprises a retracting mechanism which retracts the needles after they puncture the patient's skin; and ejecting the used needles from the applicator such that the applicator is ready to apply another disease management system. The needles can be housed within guidance tubes before launching the insulin dosage unit onto the patient. When in the packaging, the disease management system can be preloaded with lancet backings, wherein when the needles are retracted, the needles can retract into the lancet backings, and wherein ejecting the used needles can include ejecting the used needles within the lancet backings. A method can include removing the applicator after launching the disease management system onto the patient, wherein removing the applicator can include leaving the applicator on the patient while removing the needles within the lancet backings.
In some configurations, a disease management system can include: a case; a glucose sensor; an insulin storage chamber; an insulin pump in fluid connection with the insulin storage chamber; a battery; a computing device configured to receive measurements from the glucose sensor and control the insulin pump provide dosages of insulin to a patient based on measurements from the glucose sensor; and an antenna connected to the computing device, wherein the computing device can be further configured to send measurements from the glucose sensor to other disease management units, a smart device, and/or a smartwatch through the antenna, receive glucose measurements from other disease management units, a smart device, and/or a smartwatch, and send dosage instructions through the antenna to other disease management units, and wherein the case houses the glucose sensor, the insulin storage chamber, the insulin pump, the battery, and the computer device.
In some configurations, a disease management system can include a near field communication (NFC) device including a unique ID tag associated with the disease management system, wherein a user device is capable of causing the NFC device to send the unique ID tag to the user device which allows the user device to identify the disease management unit and pair with the disease management system. The NFC device can be configured to communicate with the user device to trigger the disease management system to manually administer a dosage of insulin to the patient. The NFC device can be configured to communicate with a wearable NFC device to trigger the disease management system to manually administer a dosage of insulin to the patient. The wearable NFC device can include a safety mechanism to prevent the wearable NFC device from triggering the disease management system from manually administering a dosage of insulin to the patient unless the safety mechanism is enabled. The safety mechanism can include a switch, toggle, button, and/or knob. The wearable NFC device can be mounted on a bracelet, watch, necklace, or belt. The NFC device can be configured to differentiate between different wearable NFC devices such that one of the wearable NFC devices communicates with the NFC device to trigger the disease management system to manually administer a different dosage of insulin to the patient than another of the wearable NFC devices. The computing device can be configured to block a manual administration of a dosage from the wearable NFC device at least during a portion of the time.
In some configurations, a case can include a manual dosage mechanism which is capable of triggering the disease management system to manually administer a dosage of insulin to the patient. The case can be segmented such that the portion of the case with the manual dosage mechanism is removable and replaceable. The computing device can be configured to communicate with an additional manual dosage device which can be configured to be physically connected with the case, the additional manual dosage device can be configured to trigger the disease management system to manually administer a dosage of insulin to the patient. The antenna can be embedded within the case or on the outside of the case.
In some configurations, a disease management system can include: a first disease management system and a second disease management system. The first disease management system can include: a first glucose sensor; a first insulin pump; a first computing device can be configured to receive measurements from the first glucose sensor and control the first insulin pump provide dosages of insulin to a patient based on measurements from the first glucose sensor; a first antenna connected to the first computing device; a first near field communication (NFC) device can include a first unique ID tag associated with the first disease management unit, wherein a user device is capable of causing the first NFC device to send the first unique ID tag to the user device which allows the user device to identify the disease management unit and pair with the disease management unit. A second disease management system can include: a second glucose sensor; a second insulin pump; a second computing device configured to receive measurements from the second glucose sensor and control the second insulin pump provide dosages of insulin to a patient based on measurements from the second glucose sensor; a second antenna connected to the second computing device; a second near field communication (NFC) device can include a second unique ID tag associated with the second disease management unit, wherein the user device is capable of causing the second NFC device to send the second unique ID tag to the user device which allows the user device to identify the second disease management unit, and wherein the first disease management system can be configured to pair to the second disease management system through request of the user device. The second disease management system can be configured to pair with the user device. The user device can include a smartphone, tablet, wearable device, or other electronic device. In some examples, the other electronic device can include an emergency glucagon device.
In some configurations, a flexible disease management system can include: a glucose sensor; a computer device; an antenna, wherein the computing device can be configured to transmit glucose data received from the glucose sensor through the antenna; a flexible battery configured to power the computer device and the glucose sensor; and a flexible bandage configured to adhere the flexible battery, computer device, and the glucose sensor to the patient.
In some configurations, an applicator for a disease management system can include: a cylindrical applicator wheel capable of storing one or more patient treatment units; a handle attached to the applicator wheel at the center of two opposing sides of the applicator wheel, wherein the applicator wheel can be configured to physically contact a patient and roll on a patient and, when rolling, apply at least one of the one or more patient treatment units to a patient. The one or more disease management systems can include one or more glucose sensor units, one or more insulin pump systems, and/or one or more combined glucose sensor and insulin pump units.
In some configurations, a method of distracting a patient during application of a disease management system can include: providing the disease management system for application to the patient, wherein the disease management system comprises one or more needles; applying the disease management system to the patient; and using a distraction device to distract the patient during application of the disease management system to the patient, wherein the distraction device interacts with the disease management system such that the distraction device times a distracting event with application of the disease management system. The distraction device can include a user device or another disease management system including a vibration device. The distraction device can include a user device which allows a patient to play a game, watch a movie, or read a story before and during application of the disease management system, and wherein the distracting event comprises the climax of the game, movie, or story. The distraction device can include another disease management system including the vibration device, and wherein the distracting event comprises vibration of the vibration device just before and during application of the disease management system. The method can include operating a vibration device within the patient treatment unit after application of the disease management system to the patient. The disease management system can include an indicator which can indicate when a distracting event is occurring in order to indicate that the timing is optimal to apply the disease management system to the patient. An indicator can include a light emitter or a vibrating module. In some configurations this event sequence and timing can be an API that allows other 3rd parties to develop games around the event process and timing to have new distraction games created.
In some configurations, a needle for implanting a glucose sensor or cannula can include a top portion and a bottom portion, wherein the bottom portion is rigid at some times and flexible at some times. The bottom portion can include a material which is flexible when exposed to water and rigid when not exposed to water. The bottom portion can include hydrogel or collagen. The bottom portion can include an inner layer and an outer layer, wherein the inner layer and outer layer can be made out of different materials. One of the inner layer or the outer layer can include hydrogel or collagen and the other of the inner layer or the outer layer can include metal or plastic. The bottom portion can be rigid when not exposed to ultra-violet light and flexible when exposed to ultra-violet light. The bottom portion can include a bioresorbable material. The needle can be a hollow needle. The needle can be a solid needle.
d illustrate various cross sectional views of the applicator of
Aspects of the disclosure will now be set forth in detail with respect to the figures and various examples. One of skill in the art will appreciate, however, that other configurations of the devices and methods disclosed herein will still fall within the scope of this disclosure even if not described in the same detail. Aspects of various configurations discussed do not limit the scope of the disclosure herein, which is instead defined by the claims following this description.
Systems and methods described herein may be applicable to diabetic disease management or other patient condition that may be treated with an implant or other minimally or non-invasive device configured to monitor a patient state and deliver medication on an ongoing or temporary basis. While reference may be made to a specific disease, such as diabetes, systems and methods described herein may be applicable to other diseases and conditions.
While in some examples, systems and methods described herein may reference monitoring or sensing of a specific parameter or blood analyte, such as glucose, other physiological conditions, physiological states, physiological parameters, physiological markers, blood analytes, the like or a combination thereof may be monitored or determined in addition or in the alternative to glucose. Similarly, while in some examples, reference may be made to a specific type of sensor, such as a glucose sensor, other analyte sensors may additionally or alternatively be used. For example, a glucose sensor may be configured to additionally measure other analytes. Additionally or alternatively, while reference may be made to specific types of invasive or non-invasive sensors, such as an invasive glucose sensor, any type of invasive or non-invasive sensor may be used, such as a non-invasive analyte sensor.
Additionally or alternatively, while in some examples, systems and methods described herein may reference specific medication, such as insulin or glucagon, to be delivered to the patient, other medications, fluids, or treatments may be administered in addition or in the alternative to medications such as insulin or glucagon. Similarly, while in some examples, reference may be made a specific type of pump or other component associated with a medication or fluid, such as an insulin pump, the components described herein may be used with any fluid or medication.
Additionally, while reference may be made to the use of a certain number or type of device, any combination and number of devices may be used, such as one, two, three, four or more redundant or different devices. In some examples, a single device may be used to manage aspects of a patient's health, such as a combined medication pump and analyte sensor. In some examples, redundant devices may be used to manage aspects of a patient's health, such as two combined medication pump and analyte sensor devices. In some examples, different devices may be used and in communication to manage different aspects of a patient's health or different aspects of disease management, such as a separate medication pump and analyte sensor.
It has been discovered that when first beginning operation, glucose sensors have a settling period which may include a warmup period where the glucose sensors do not give off measurements and a stabilization period where the glucose sensors produce measurements but these measurements are inaccurate. The warmup period may typically last for one to two hours and the stabilization period may typically last for up to 24 hours. Further, during the end of the glucose sensors' operational life, there is another period where the glucose sensors produce measurements but these measurements are often inaccurate. This period is often referred to as the end of life period and typically covers the last few days of the sensor's operational life. During the settling period and the end of life period, it is advantageous to supplement the glucose measurements with other more accurate readings.
Disclosed is a disease management system including a first disease management system including a first glucose sensor and a first insulin pump and a second disease management system including a second glucose sensor and a second insulin pump. The first disease management system and the second disease management system are configured to simultaneously attach to a patient and communicate with each other. While the first glucose sensor is in a settling period, the second glucose sensor is configured to provide blood glucose information about the patient to the first glucose sensor. Thus, while the first glucose sensor is giving no measurements or inaccurate measurements, the second glucose sensor may be used to provide accurate glucose measurements to increase the likelihood of accurate administration of insulin.
The present disclosure also describes an integrated system that incorporates the dosage system and glucose sensor into one unit. Various components of the unit are described in detail such as various insulin pumps and applicators that may be used to apply the unit to a patient.
In some examples, systems and methods described herein can include at least one disease management system, such as an insulin pump, CGM, combined insulin pump and CGM or applicator for applying a device to a patient or user.
A disease management system can have form factor parameters that improve upon current CGM and/or insulin pump system such as having a smaller, thinner, or more body conforming form. More body conforming can include a form factor, such as a belt, bandage, soft silicone, or similar form. In some examples, a smaller form factor may include smaller form as compared to current insulin pumps (for example, X mm×Y mm×5-10 mm).
In some examples, a disease management system may have an appealing visual appearance. The appearance of the device may be intuitive to its function.
A disease management system may have intuitive and easy placement such that a user may be able to intuitively perform the procedure after initial use or uses. A disease management system may have intuitive and easy removal such that a user may be able to intuitively perform the procedure after initial use or uses.
A device may be resistant to electrical, moisture, temperature, or other operating conditions. For example, a device may be configured to operate throughout and after defibrillation. In another example, a device may be configured operate without insulin in 50-113° F. (10-45° C.) and humidity of 10-95% between ground level and 12,000 feet of elevation. In another example, a device may be configured to operate with insulin in 50-98.6° F. (10-37° C.) and humidity of 10-95% between ground level and 12,000 feet of elevation. In another example, a device may be configured to operate in 7-130° F. (10-48° C.) with heat resistant genetically engineered proteins. In another example, device may be configured to operate after prolonged storage in a variety of conditions, such as up to 6 months in 35.6-77 (2-25° C.) and humidity of 10-95% between ground level and 12,000 feet of elevation. A device may be configured to operate in the presence of MRI. A device may be configured to operate through and not alarm metal detectors. A device may be configured to operate while submersed under water. For example, a device may be able to be submersed and functioning but not necessarily communicating with a mobile device while connected to the body in 1.5 meters (5 feet) of water for 60 minutes (IPX8). In another example, a device may be able to be submersed and functioning but not necessarily communicating with a mobile device while connected to the body in 7.6 meters (25 feet) of water for 60 minutes. A device may be configured to be dust resistant. For example, a device may be configured to have IP5X dust protection.
A device may be configured to be placed on a plurality of tissue sites, such as an arm, abdomen, lower back, upper buttocks, thigh or other site.
A device may be configured to stay on a tissue site for an extended period, such as for 3 days, 6 days, or 12 days. For example, a device may be configured to operate in an interleaved configuration, with a life of 3 days for an insulin pump component(s) and 6 days for a CGM component(s). In another example, a device may be configured to stay on the body for 12 days in an interleaved configuration, with a life of 6 days for an insulin pump component(s) and 12 days for a CGM component(s).
One or more interleaved disease management systems may be configured to use up to the entire amount of insulin in an insulin pump. Advantageously, the full use of insulin may prevent insulin extraction by a user. In some examples, as an interleaved device approaches end of insulin (for example, approximately 3 days), the treatment system may prompt the user to add a new interleaved device prior to the end of insulin. For example, a system may alert a user before insulin runs out with up to 6 hours, 12 hours, or other amount of time.
In some examples, one or more disease management systems may be preloaded with insulin and stored in refrigerated state (12 months) before use. A device may be able to withstand shipping in 36-77° F. (2-25° C.). A device may be able to withstand shipping in 20-120° F. (−6-48° C.) with heat resistant genetically engineered proteins and/or additional testing. Prior to usage, a device may be configured to have reduced air bubble formation as the insulin warms to room temperature. In some examples, a device may be shipped in sterile packaging until ready to be used by the patient.
In some examples, a device may be configured to use one or more separate applicators to facilitate insertion of a CGM sensor and insulin cannula. In some examples, one or more applicators and/or other disease management systems may utilize pain reduction or distraction systems and methods to reduce anticipatory, actual, or residual pain, such as haptic distraction on a device not being inserted to prevent anticipation pain.
In some examples, one or more disease management systems may not have any visible or external tubes.
In some examples, a treatment system may include one or more visual, audible, or haptic indicators configured to notify a user of one or more device and/or biological states associated with managing insulin and/or glucose. The one or more indicators may be generated, displayed, or otherwise indicated on a mobile device paired with a disease management system, an application, or on a disease management system. The one or more indicators may indicate a status such as working, expired, will expire in 12 hours, or next one to be replaced. In some examples, a device may display an intuitive status of, for example: overall system function (by, for example, Green, yellow, or red color coded indicators), good to go, warnings (such as low battery or insulin supply), or errors. This intuitive display include interfaces beyond visual such as but not limited to feedback such as audible or tactile patterns.
In some examples, a device can include multiple insertion sites, such as an insertion site for a CGM and an insertion site for insulin administration.
A device can be configured to avoid injecting a venous air bubble of lethal dosage, such as greater than 12 ml.
A device may be configured to use U-200 insulin (or equivalents) to decrease an insulin reservoir size by half as compared to other disease management systems.
A device may include a continuous glucose monitor (CGM), continuous analyte monitor (CAM), or insulin assay on the tip of the insulin cannula.
A device or applicator may be configured to prime insulin for administration.
In some examples, a device may have physically separated components. For example, a device may have an insulin cannula and a continuous analyte monitor electrode(s) (CAM or CGM) separated at tip to tip by, for example, at least 50 mm.
In some examples, a device may include a continuous analyte monitor (CAM). A CAM may be configured to measure analytes including but not limited to chylomicrons, triglycerides, and cholesterol.
A device may be sterile to 1E-6 SAL. A device may be manufacturable without a clean room.
A device may include a glucose accuracy of less than or equal to and including 8% mean absolute relative difference (MARD) or more. A device may not require SMBG bias measurements to reach 8% MARD.
A device may have an insulin dosing accuracy such that a device may pump all discrete insulin volume to within 5% for U-100 or 2.5% if U-200 maximum error.
In some examples, a disease management system may be configured to have a minimum insulin dosage of 0.175 uL for U-200 insulin.
In some examples, a disease management system may include multiple electrodes. In some examples, an electrode may have a diameter of less than or equal to approximately 300 um.
A pump of a disease management system may be configured to emit low noise levels. For example, a pump may be quiet enough to allow discrete usage of an insulin pump.
A cannula and electrode may be configured to resist breaking by in-body or extraction forces.
An insulin cannula may have an outer diameter of up to and including 600 um or more. A cannula or electrode may be longer than 4 mm stratum corneum surface to deepest point in tissue. A cannula or electrode of a length up to and including 13 mm or more from a stratum corneum surface to deepest point.
A device may include a buffer to prevent over insertion by children between 7-12 years of age. For example, a device may have a 1 mm buffer added to an adhesive to make the insertions penetrate no deeper than 3 mm. In another example, pre-teens and adults 13 and older may have no additional thickness added to the adhesive to make the insertions penetrate no deeper than 4 mm.
In some examples, a device may include an adhesive. An adhesive may be configured to not create a rash. An adhesive may retain contact to a tissue site for a period of time up to and including 6 days. An adhesive may contain an anesthetic around the insertion site location that may last long enough to address movement paint, such as for a few hours.
A device may be configured to detect if it is on body or off body. Advantageously, this may help prevent titration while in unusual circumstances (for example, even in situations where a device is removed from the body such that an active sensor is removed and then placed in sugar water bath while a device is still in applicator).
A device may be configured to observe one or more biometric parameters, such as a user's pulse rate or a user's SpO2. In some configurations, a device may be configured to detect compression, such as by a force sensor.
A device may have a ratcheted peristaltic or piezo or solenoid pump mechanism. A device may include an insulin pouch. The insulin pouch, pathway, and cannula may be configured to not facilitate crystallization, aggregation, leeching (of insulin or preservatives), denaturing, adsorption, or bubble formation. A device may be configured to utilize multiple brands of pre-filled insulin.
In some examples, a treatment system can include a starter or CGM only device that does not contain an insulin cannula, pump or insulin reservoir. A starter or CGM only device may be configured to connect to one or more companion applications via SDK to communicate blood glucose values.
A disease management system that includes both a CGM and insulin pump may be configured to connect to one or more companion applications via SDK to give blood communicate blood glucose values. In some examples, a device may be configured to receive recommended or directly dose cloud-based control algorithm insulin doses. In some examples, a device may be configured to run a simple algorithm that gives recommendations to the user in the app of insulin bolus values. In some examples, a device may be configured to control basal insulin and set points even without a connected companion application or cloud service.
A device may be configured to include arsenic-free glass, Mercury-free, Brominated flame retardant-free, PVC-free, Beryllium-free or other recycled or compostable materials.
A device may be able to apply a bolus of insulin without other instruments. This should be possible either manually or in an automatic method. For example, in emergency situation the device may have a physical method that allows an insulin bolus to be administered. In some examples, a physical bolus administration may have a maximum amount it can administer in a single time period. A device may prevent manual boluses when a user is in a hypoglycemic or tending towards a hypoglycemic state.
In some examples, an interleaved device(s) may be configured to dynamically or statically synchronize states. For example, one or more interleaved devices may be configured to minimally or less frequently synchronize all states at a time of new device setups and device stabilizations, but synchronize more frequently to improve confidence of control system. A device may be able to sample a measurement as frequently as once per minute.
In some examples, a device or companion application or connected cloud storage may be configured to store multiple days of data, such on treatment decisions and observations. For example, a device may have 6 days of secure data storage and be able to track all treatment decisions and observations (for example, manual overrides, user states, controller decisions). Stored results may be retained after device expiry. In some examples, a device or companion application or connected cloud storage may store secure personalized configuration(s). Data may be stored in a secure way to prevent unauthorized access.
A disease management system may include a real time clock, accelerometer and Bluetooth or similar communication capability. A connection between a disease management system and a mobile device may include a secure communication protocol, such as encryption, and reliability. A device may utilize an NFC connection in order to deliver a life critical function, such as remote insulin bolus or change a critical insulin parameter from a user device, such as a phone, tablet, computer or other user electronic device. A device may ignore related bolus requests when a user is not in need of insulin. In some examples, a device may ignore NFC related bolus requests when a pattern is detected that suggests a replay attack (superfluous requests).
A disease management system may include one or more sensors. For example, a treatment system may include an electrode temperature sensor to help facilitate compensation for electrical/enzymatic drift or disturbance. A disease management system may be configured to have an insulin temperature sensor to detect insulin spoilage or degradation due to body or ambient temperature. An insulin reservoir may be temperature controlled away from body temperature to extend its useful life and improve its activity. Advantageously, this may help allow longer interleaved cycles such as 7 to 14 days. A disease management system may have an environmental temperature sensor. A disease management system may have a 3 axis accelerometer to detect and classify types of exercise. The disease management system can also be used for body orientation (such as for an emergency glucagon system) if given two known states and insulin absorption rate of the location. A disease management system may have a 3 axis gyroscope to detect fine movements for improved exercise classification. A disease management system may have a communication system, such as Bluetooth, for communication with a user device and reduced power consumption. A disease management system may have a Near Field Communication (NFC) tag to interface with an NFC reader on a user device for easy setup of Bluetooth pairing and opening or downloading an application. A disease management system may have automated or manual retraction of a cannula. The retraction may help facilitate wound healing, such as on day 3. A disease management system may be powered by external or integrated batteries (for example, a CR2032 3V). A disease management system may have haptic and/or audible feedback components. A disease management system may have an SOC and memory. A disease management system may have an actuator and drive circuitry for insulin delivery. A disease management system may have a frontend for continuous analyte monitor (CAM) or continuous glucose monitor (CGM). A disease management system may have LEDs, detectors, and frontend for diffuse reflectance SpO2 sensor. A disease management system may have LEDs, detectors, and frontend for a diffuse reflectance pulse rate sensor. Respiration rate may also be measured by a treatment system sensor.
Closed loop systems are inherently high risk due to their use and treatment with a biologic and performing life-sustaining functions to persons with Type 1 diabetes. The need for redundancy to ensure error free and accurate glucose titration is paramount. CGM devices often have periods of no measurements when first applied to a user's body called “warm-up time”. This period can typically last 1-2 hours. CGM devices also have periods of inaccuracy after the warm-up time called “Stabilization time”. This period can last up to 24 hours. Devices also have “end of life” issues such as sensitivity decrease and noise increase. Sensitivity decreases by use over time and environmental stimuli. Tracking this is a non-linear process and uncertain, therefore decreases in sensor sensitivity is a key source of error for devices on market today.
Having a combined CGM (or CAM)/insulin pump device can greatly reduce overall cost for users. By using an interleaved configuration the percentage time in a reliable closed loop can be increased because the user will virtually never be out of closed loop during a warmup time or any other uncertain period. Current modern CGM's also allow the user to titrate during stabilization and end-of-life periods and frequently have false-alarms the night of insertion. By interleaving devices, this situation may be greatly alleviated. Having interleaved devices also enables complete emptying of insulin reservoirs. This addresses a major concern of persons with Type 1 which is insulin waste.
In systems and methods described herein, two devices may be used to provide redundant measurements. In contrast, in traditional systems, while some users may be used to two devices in a closed loop CGM system, each of the devices in a traditional system may serve a different function (for example, one device for a CGM and one device for an insulin pump) and thus do not provide redundancy.
During the first ever insertion of a device, the user may begin with either a secondary or a primary device. In some embodiments, both devices may contain both an insulin pump and a CGM. A secondary device may be a device which has emptied or expired its insulin supply and only has a CGM remaining.
In such a case where a secondary device is used first, the initial secondary device may contain a dummy or empty insulin pouch when a disposable lot of devices are shipped out together. This care of providing a dummy insulin device enables a user to immediately begin closed loop use with redundant coverage.
In some examples, it may take roughly 1 month to fully use 10 devices. However, other use rates are also possible. For a new user, a starter pack may be provided that has a dummy device (with no insulin) and a number of primary devices (for example, 9 devices in order to last a user a 1 month interval in the case of a 10 device a month use rate) that are ready to start in a primary configuration. In addition, or in the alternative to a starter pack, a set of primary devices could be provided (also referred to as a refill-lot). Should a user start with a refill-lot and not a starter pack lot, two insulin containing devices could be placed on the body but the closed loop system may only use a single insulin containing device and the other may not be used by the closed loop system.
A mobile device as well as the two applied devices can communicate wirelessly via Bluetooth or another communication method, such as RF. The devices may communicate data associated with the device operation or status, such as current insulin reservoir statuses, the mode each device is operating in (primary or secondary), CGM values, embedded device model states, user calibrations or settings or configurations, personalization variables, battery states, error states, user activity states, orientations, the like or a combination thereof.
Advantageously, the use of overlapping devices may provide a consistently reliable CGM value with few exceptions (such as during first time warmup or stabilization periods). This consistency may allow for avoidance of non-measurement periods or moments in time where closed loop would otherwise be unavailable due to follow-up devices placement in warmup time. Stabilization period measurements can also be dynamically averaged with stable measurements from a secondary device, or they can be altogether probed off. End of sensor life measurements can also be dynamically averaged with stable measurements from a primary device, or they can be altogether probed off. End of life measurements being validated by primary devices are particularly helpful to improve sensor predictions in ultra-long life CGMs that may wish to stabilize measurements with an interleaved configuration. For example, interleaved devices may improve sensor predictions on 6-day life devices that can be extended to 7, 10, 12, 14, or longer day lifetimes of modern CGMs.
Additionally, systems and methods described herein may stabilize insulin and lipohyperatrophy could be reduced by switching devices to longer periods than CGMs at current technological standards. Additionally, systems and methods described herein may enable fewer insertions and much longer wear time, resulting in better user experience and potentially better compliance.
Interleaved devices can occur at any suitable area of the body, including but not limited to: stomach, butt, chest, back of arms, side of arms, lower back, legs, the like or combination thereof.
While
As illustrated in
In some examples, a disease management environment may include an applicator 1007 configured to facilitate application or removal of at least one of a disease management system and glucagon administration system. In some examples, the applicator 1007 may be reusable. In some examples, an applicator 1007 may include an applicator such as described with reference to
Thus, there exists circumstances where a sensor may be operating on a patient during the warmup period 1010, the stabilization period 1012, and the end of life period where there will be no measurement or inaccurate measurement. For example, when a disease management system combining an insulin pump and a glucose sensor, such as the disease management system described herein in
After the second device runs out of insulin, the first device may be replaced 1112 and the replacement first device may pump insulin into the patient while the second device is used for glucose measurements while the new first device is in a warmup period 1102 and stabilization period 1104. This operation can continue with the second device being replaced 1112 when the first device runs out of insulin. The schedule illustrates a primary mode 1106 which is a mode where the device is pumping insulin and may be providing glucose measurements whereas a secondary mode 1108 is a mode where the device may be providing only glucose measurements. Of course, it is to be understood that a larger or smaller insulin reservoir may be used that may last longer or shorter than 3 days. Further, it is to be understood that the first pump can continue to pump insulin even after the second device is attached. In this way, the first pump can entirely deplete its insulin reservoir so that no insulin is wasted, and the second pump can seamlessly continue where the first pump left off. In addition, the insertion of the second device can be scheduled to occur at an opportune time for the patient because the handoff between the devices may occur without user intervention. This would avoid alarms which alert a patient to switch one or more treatment devices at inconvenient times (for example, at night when the patient is sleeping) in conventional treatment devices. Thus, depending on the nature and capacities of the respective devices, different overlap time periods can be used as would be understood by the disclosure herein.
Calculating the dosage of insulin for the patient may occur on the first device or the second device or the cloud. The first device may send insulin dosage instructions or glucose measurements to the second device. The second device may send insulin dosage instructions or glucose measurements to the first device. The first device and second device may communicate wirelessly by such a manner as Bluetooth or RF signals. In some implementations, the first device and/or the second device may calculate the dosage of insulin based on an algorithm such as a glucose insulin meal model.
It is understood that a first device is replaced such that the replacement first device ends a warmup period and a stabilization period before the second device begins an end of life period. Further, a second device is replaced such that the replacement second device ends a warmup period and a stabilization period before the first device begins an end of life period. It is also understood that a first device or a second device has insulin supply remaining such that at least one device is capable of supplying insulin to the patient. It is also understood that the insulin supply has natural expiration dates that may alter the device replacement schedule. In some implementations, the patient may be alerted that one or more of the devices should be replaced based on the replacement schedules of
As illustrated in
A disease management system 1101 may include an analyte sensor 1120. The analyte sensor 1120 may be configured to detect analytes in the patient's blood. For example, an analyte sensor 1120 can include a glucose sensing probe configured to pierce the surface of the skin 1121. In some examples, a disease management system 1101 may include a plurality of analyte sensors 1120 to detect one or more analytes. In some examples, an analyte sensor 1120 may be configured to detect a plurality of analytes. Sensed analytes may include, but are not limited to, glucose, insulin, and other analytes. An analyte sensor 1120 may be configured to communicate with an analyte detector 1126. The analyte detector 1126 may be configured to receive a signal of one or more analyte sensors 1120 in order to measure one or more analytes in the blood of the patient. The analyte detector 1126 may be configured to communicate with the controller 1138. For example, the analyte detector 1126 may be configured to, for example, send analyte values to the controller 1138 and receive control signals from the controller.
A disease management system 1101 may include a medication catheter 1122. The medication catheter 1122 may be configured to administer medication, including, but not limited to insulin, to the patient. The medication catheter 1122 may receive medication from a medication bladder 1128 configured to contain medication to be administered. The medication bladder 1128 may be configured to contain medication for a prolonged period, such as 1 day, 3 days, 6 days, or more. The medication bladder 1128 may be configured to contain certain medication types, such as insulin. In some examples, a disease management system 1101 may include a plurality of medication bladders 1128 for one or more reservoirs of the same or different medications. In some examples, a disease management system 1101 may be configured to mix medications from medication bladders 1128 prior to administration to the patient. A pump 1130 may be configured to cause medication to be administered from the bladder 1128 to the patient through the insulin catheter 1122. A pump 1130 may include, but is not limited to, a pump such as described herein with reference to
A disease management system 1101 may include a physiological sensor 1124. The physiological sensor 1124 may include a pulse rate sensor, temperature sensor, pulse oximeter, the like or a combination thereof. In some examples, a disease management system 1101 may be configured to include a plurality of physiological sensors. The physiological sensor 1124 may be configured to communicate with a physiological detector 1134. The physiological detector 1134 may be configured to receive a signals of the physiological sensor 1124. The physiological detector 1134 may be configured to measure or determine and communicate a physiological value from the signal. The physiological detector 1134 may be configured to communicate with the controller 1138. For example, the physiological detector 1134 may be configured to, for example, send measured physiological values to the controller 1138 and receive control signals from the controller.
A disease management system 1101 may include one or more local user interfacing components 1136. For examples, a local user interfacing component 1136 may include, but is not limited to one or more optical displays, haptic motors, audio speakers, and user input detectors. In some examples, an optical display may include an LED light configured to display a plurality of colors. In some examples, an optical display may include a digital display of information associated with the disease management system 1101, including, but not limited to, device status, medication status, patient status, measured analyte or physiological values, the like or a combination thereof. In some examples, a user input detector may include an inertial measurement unit, tap detector, touch display, or other component configured to accept and receive user input. In some examples, audio speakers may be configured to communicate audible alarms related to device status, medication status user status, the like or a combination thereof. A controller 1138 may be configured to communicate with the one or more local interfacing components 1136 by, for example, receiving user input from the one or more user input components or sending control signals to, for example, activate a haptic motor, generate an output to the optical display, generate an audible output, or otherwise control one or more of the local user interfacing components 1136.
A disease management system 1101 may include one or more communication components 1140. A communication component 1140 can include, but is not limited to one or more radios configured to emit Bluetooth, cellular, Wi-Fi, or other wireless signals. In some examples, a communication component 1140 can include a port for a wired connection. Additionally, a disease management system 1101 may include an NFC tag 1142 to facilitate in communicating with one or more hardware processors. The one or more communication components 1140 and NFC tag 1142 may be configured to communicate with the controller 1138 in order to send and/or receive information associated with the disease management system 1101. For example, a controller 1138 may communicate medication information and measured values through the one or more communication components 1140 to an external device. Additionally, the controller 1138 may receive instructions associated with measurement sampling rates, medication delivery, or other information associated with operation of the management system 1101 through the one or more communication components 1140 from one or more external devices.
A disease management system 1101 may include one or more power components 1144. The power components may include, but are not limited to one or more batteries and power management components, such as a voltage regulator. Power from the one or more power components 1144 may be accessed by the controller and/or other components of the disease management system 1101 to operate the disease management system 1101.
A disease management system 1101 may have one or more power and sleep modes to help regulate power usage. For example, a disease management system 1101 may have a sleep mode. The sleep mode may be a very low power mode with minimal functions, such as the RTC (or real time clock) and alarms to wake the system and take a temperature measurement of the system, or the like. In another example, a disease management system 1101 may include a measure temperature mode which may correspond to a low power mode with reduced functions. The measure temperature mode may be triggered by the RTC where the system is configured to take a temperature measurement, save the value, and return the system to a sleep mode. In another example, a disease management system 1101 may include a wake up mode. The wake up mode may be triggered by an NFC device and allow the system to pair with an external device with, for example, Bluetooth. If a pairing event does not occur, the system may return to sleep mode. In another example, a disease management system 1101 may include a pairing mode. The pairing mode may be triggered by an NFC device. When a controlling application is recognized, the system may proceed to pair with the application and set the system to an on condition and communicate to the cloud or other external device to establish initial data movement. In another example, a disease management system 1101 may include a rest mode where the system is configured to enter a lower power mode between measurements. In another example, a disease management system 1101 may include a data acquisition mode where the system is configured to enter a medium power mode where data acquisition takes place. In another example, a disease management system 1101 may include a parameter calculation mode where the system is configured to enter a medium power mode where parameter calculations, such as a blood glucose calculations, are performed and data is communicated to an external device and/or the cloud. In another example, a disease management system 1101 may include a pump mode where the system is configured to enter a higher power mode where the pump draws power to deliver medication to the patient.
A disease management system 1101 may include one or more connector test points 1146. The connecter test points may be configured to aid in programming, debugging, testing or other accessing of the disease management system 1101. In some examples, connector test points 1146 may include, for example, a GPIO spare, UART receiver or transmitter, the like or a combination thereof.
The adhesive layer 1168 may be configured to provide adhesion for a prolonged period. For example, the adhesive layer 1168 may be configured to adhere the disease management system 1103 to the skin of a patient for a period of 1 day, 3 days, 6 days, or more or fewer days or hours. In some examples, the adhesive layer may be configured to have an adhesive force sufficient to prevent accidental removal or movement of the disease management system 1103 during the intended period of use of the disease management system 1103. In some examples, the adhesive layer 1168 may be a single layer of adhesive across at least a portion of a surface the disease management system 1103 that is configured to interface with the patient. In some examples, the adhesive layer 1168 may include a plurality of adhesive areas on a surface of the disease management system 1103 that is configured to interface with the patient. In some examples, the adhesive layer 1168 may be configured to be breathable, adhere to the patient's skin after wetting by humidity or liquids such as tap water, saltwater, and chlorinated water. A thickness of the adhesive may be, for example, be in a range of 0.1 to 0.5 mm or in a range of more or less thickness.
In some examples, a needle 1158, 1162 may be inserted at different depths based on a patient age, weight, or other parameter. For example, a depth of insertion of a medication cannula may be approximately 3 mm for 7 to 12 year olds. In another example, a depth of insertion of a medication cannula may be approximately 4 mm for 13 year olds and older. In another example, a depth of insertion of a medication needle may be approximately 4 to 4.5 mm for 7 to 12 year olds. In another example, a depth of insertion of a medication needle may be approximately 5 to 5.5 mm for 13 year olds and older. In another example, a depth of insertion of an analyte sensor may be approximately 3 mm for 7 to 12 year olds. In another example, a depth of insertion of an analyte sensor may be approximately 4 mm for 13 year olds and older. In another example, a depth of insertion for a needle associated with an analyte sensor may be approximately 4 to 4.5 mm for 7 to 12 year olds. In another example, a depth of insertion for a needle associated with an analyte sensor may be approximately 5 to 5.5 mm for 13 year olds and older. However, other values or ranges for any of the inserted components are also possible.
In some examples, one or more components of a disease management system and/or environment may be reusable, disposable, or refurbishable.
As shown in
1. Example Insulin Pump and Glucose Sensor System
In some implementations the insulin bladder 110 may be adapted to store various types of insulin such as U-100 insulin and U-200 insulin. U-200 insulin may be of higher strength and higher concentration than U-100 insulin and thus an insulin bladder 110 filled with U-200 insulin may take up less space for the same dosage when compared to U-100. Other insulin types may be used without departing from the present invention.
A light source 118 such as a light emitting diode (LED) and photodiode may also be included. A vibration device such as a haptic feedback vibrator may also be included. The light source 118 and vibration device may be used to alert the patient of certain events such as a malfunction of a device, when it is time to change the disease management system 100, or alerts that can indicate spikes in glucose.
The antenna 104 can be compatible with Bluetooth or radio frequency (RF) such as Wi-Fi. In some implementations, the insulin bladder 110 can be a flexible insulin pouch capable of flexing under pressure in order to force out insulin. In these implementations, the insulin bladder 110 may be connected to an insulin pump which is a valve. In some implementations, the insulin bladder 110 may be a rigid storage structure. In these implementations, the insulin bladder 110 is connected to an insulin pump which applies pressure to the insulin in order to force out the insulin. The PCB 108 may include an accelerometer, gyroscope, and communications module.
A case 102 houses the PCB 108, the insulin pump, the insulin bladder 110, the battery 114, the spring 112, the light source 118, and the vibration device 116. The case 102 is rigid such that the spring 112 may press against the case 102 when applying pressure to the insulin bladder 110. The case may be made from a metal such as aluminum or plastic. The aluminum may be polished for aesthetic purposes. The case 102 may be mounted on an adhesive 120 in order to mount the disease management system 100 on a patient. The case 102 may include one or more needle insertion pass through 106 which allows a needle to pass from the top of the case 102 through the insulin pump and into the patient. The needle may be used to implant a cannula from the insulin pump into the patient allowing the insulin pump access to the patient's interstitial fluid or blood. The one or more needle insertion pass through 106 may also allow access to the patient's interstitial fluid or blood to the glucose sensor. These one or more needle insertion pass through 106 may be on opposite sides of the device in order to provide adequate spacing for the glucose sensor and the insulin being provided from the pump into the patient. The antenna 104 may be applied on the case 102, embedded with the case, or may divide the case 102 into two portions. The case 102 can further include an auxiliary device space 116 which may include one or more auxiliary devices such as a vibration device (for example, a haptic feedback vibrator).
The sensor system 200B and the insulin pump system 200A may or may not both include a PCB 108B, 108A. The PCBs 108B, 108A may both include a computing device with an electronic processor and memory with instructions executable by the electronic processor capable of receiving glucose measurements from a glucose sensor and controlling an insulin pump to provide a specific dosage of insulin to a patient based on the glucose measurements. In some implementations, the PCB 108B of the sensor system 200B may merely send measurements to the PCB 108A of the insulin pump system 200A and a computing device of the insulin pump system 200A may compute the proper dosage of insulin and operate the insulin pump to administer the proper dosage to the patient. Alternatively, the computing device located on the PCB 108B of the sensor system 200B may calculate the proper insulin dosage and send instructions to the PCB 108A of the insulin pump system 200A to pump the proper dosage of insulin. The insulin pump system 200A may merely follow instructions from the computing device located on the PCB 108B of the sensor system 200B. Further, the PCBs 108A, 108B may both include antennas which may be connected to the computing devices to transmit information between the computing devices and also other devices such as a user device (for example a smartphone or smartwatch) or another disease management system.
The sensor system 200B and the insulin pump system 200A may both include a battery 114B, 114A. The battery 114B of the sensor system 200B may be used to power the PCB 108B which includes the glucose sensor and the computing device. The battery 114A of the insulin pump system 200A may be used to power the PCB 108A which is connected to an insulin pump (not shown) and the computing device. The insulin pump system 200A may further include a spring 112 which applies force to the insulin bladder 110. Similar to implementations of the disease management system described above, the spring 112 may not be present when the insulin pump forces the liquid out of the bladder 110. Rather it can be a valve that gates the flow of insulin.
The sensor system 200B and the insulin pump system 200A both include a case 102B, 102A. The case may be made of the same materials as the implementations of the disease management system described above. Alternatively, the cases 102A, 102B may also be made of a softer material such as silicone. The cases 102A, 102B include needle insertion points 106A and 106B in which needles may be inserted to penetrate from the top of the cases 102A, 102B and into the patient. The cases 102A, 102B may be adhered to a patient with an adhesive 118A, 118B.
Advantageously, the implementations of the disease management system described above, such as disease management system 100 of
In addition or in the alternative to one or more of the implementations described above, a disease management system may be combined into a compact design, such as illustrated in
For example, as illustrated in
With continued reference to
In some examples, a disease management system may have one or more buzzers, alarms, or speakers 4210, or optical displays configured to display or communicate information to a patient. For example, a disease management system 100 may include a plurality of light emitting diodes (LEDs) 103, 105. In some examples, a disease management system 100 may include a connection status LED 103 and a patient status LED 105. In some examples, the disease management system 100 may be configured to change a property of illumination of the LED to display information. For example, a disease management system 100 may change color or pattern of illumination of a connection status LED 103 to indicate a connection status of the disease management system with one or more of: user device(s), other disease management system(s), other patient monitoring or treatment system(s), and the cloud. In another example, a disease management system 100 may change color or pattern of illumination of a connection status LED 105 to indicate a patient status, such as a glycemic state or condition.
In some examples, a disease management system 100 may include a port to facilitate delivery of a manual bolus of medication. A port can include an opening in a shell of the disease management system 100. The opening may be configured to receive a medication needle and allow delivery of a manual bolus of medication to the patient from the medication needle. In some examples, the port may be a pass through to the skin of the patient. In some examples, the port may allow an injection of medication through the cannula of the disease management system 100.
A top shell or housing 4201 of the disease management system 100 be configured to cover other components of the disease management system 100. The top housing 4201 can be a thickness in a range of approximately 0.5 mm to 5 mm, or a value less than or greater than that range. For example, a top housing 4201 can be approximately 1 mm thick.
In some examples, a bottom of the disease management system 100 can include a bottom assembly, such as a bottom frame portion 4211. The bottom frame portion 4211 may include a metal plate. The metal plate may, for example, have a thickness of approximately 0.1 to 1 mm, or a value less than or greater than that range. For example, a metal plate can be approximately 0.2 mm thick. In some examples, a bottom assembly can include an adhesive plate 4213 configured to connect the metal plate and/or other portions of the disease management system 100 to an adhesive material or layer of adhesive material 4214. The adhesive plate may, for example, have a thickness of approximately 0.1 to 2 mm, or a value less than or greater than that range. For example, an adhesive plate 4213 may have a thickness of approximately 0.7 mm. The adhesive material or layer of adhesive material 4214 may, for example, have a thickness of approximately 0.05 mm to 1 mm, or a value less than or greater than that range. For example, the adhesive material may have a thickness of approximately 0.15 mm.
In some examples, a disease management system 100 can include a battery 4204. The battery may be configured to rest on or couple to at least a portion of the bottom frame, such as the metal plate 4211. The battery may be electrically connected to a PCBA board 4202. In some examples, the battery 4204 may have a thickness in a range of, for example, approximately 2.5 mm to 5 mm, or a value less than or greater than that range. For example, the battery 4204 may have a thickness of approximately 3.3 mm. In some examples of a PCBA may have a thickness in a range of, for example, approximately 0.1 to 1 mm or a value less than or greater than that range. For example, a PCBA may have a thickness of approximately 0.5 mm. In some examples, a space 4203 between the PCBA and the antenna 4224 may be approximately 1 to 1.2 mm, or a value less than or greater than that range.
In some examples, a disease management system 1103 can include a bottom housing 1197 and top housing 1194. One or more of the top housing 1194 or the bottom housing 1197 can include a plastic, such as polycarbonate (PC) or ABS. At least a portion of the bottom housing can be configured to couple to a metal plate (for example, a stainless steel plate) 1193. The plate 1193 may be configured to support the bend or bending mechanism 1195 of the disease management system 1103. The plate 1193 may be thin. The plate may have a thickness, for example, of approximately 0.005 inches or more or less thickness. In some examples, the plate 1193 may be configured to couple to an adhesive plate 1191. An adhesive layer 1196 may be configured to couple to the adhesive plate 1191. The adhesive layer 1196 may be configured to attach at least a portion of the disease management system 1103 to the attachment site of the patient. The adhesive layer 1196 may be configured to adhere to the patient for a prolonged period, such as 1 day, 3 days, 6 days, a different number of days or more or less time. The adhesive layer 1196 may be configured to adhere to the patient for the intended life or period of use of the disease management system 1103.
A bending mechanism 1195 can include a flexible material or bendable portion of the disease management system 1103. The bending mechanism 1195 may allow at least a portion of the disease management system 1103 to bend or otherwise change shape or configuration to approximately conform to an attachment site on a patient. In some examples, the bending mechanism 1195 may facilitate an improved contact of at least a portion of the disease management system 1103 with the patient.
With continued reference to
A medication pouch 4216 may include one or more sealed or sealable portions 4302. For example, a medication pouch 4216 may include a sealed flange. The sealed flange may be heat sealed or otherwise sealed. The flange may be configured to allow for the pouch to be mounted to the glucose storage system or vice versa. The flange may be configured to help ensure that the medication pouch collapses flat. For example, as the medication pouch 4216 is emptied, the flange may help ensure that the medication pouch collapses flat instead of in another shape. One or more surfaces of the medication pouch may be covered in a film, such as a polymer film (for example, a COC film). The film may advantageously help ensure integrity of the pouch and/or medication during storage, sterilization of the pouch, or other manufacturing or refurbishing processes.
As illustrated in
In some examples, a mount 4206 may include features to position the analyte sensor and needle properly. For example, a mount 4206 may include portions 4454 configured to position the sensor properly so as to avoid upward shift of the sensor before, during, or after insertion. In some examples, one or more of a needle and sensor can include dimples 4456 or other positioning features to help prevent a sensor from touching the needle and being damages when the needle is withdrawn.
The disease management system 2600A may further include a battery 2614 capable of powering components such as a circuit board 2604 and the insulin pump 2602. The circuit board 2604 may be in communication with the insulin pump 2602 and/or the actuator in order to power and control these components. The disease management system 2600A may further include a glucose probe. The glucose probe may be connected to a glucose sensor which may reside on the circuit board 2604. A needle holder 2610 may be connected to a needle which may be used to implant the glucose probe into the patient. The disease management system 2600A mounted on a patient through an adhesive pad 2616.
In some implementations, the mechanism 2704 may only trigger the disease management system 2700B to communicate with a NFC device or a user device to trigger the disease management system 2700B to administer a manual dosage of insulin to the patient. Thus, the mechanism 2704 may only be a safety mechanism to keep unwanted dosages from reaching the patient. In some implementations, the case 2702B described in connection with
Described herein are a plurality of different types of pumps and fluidic paths of a medication, such as insulin, from a medication reservoir (such as a pouch) to a patient.
A pouch material may be made of a material configured to contain a medication for a prolonged period. In some examples, a pouch material may be a silicone material (including platinum cure) or Cyclic Olefin Copolymer a special polymer. The pouch material may be soft enough to flatten up when the drug is pumped out and the pouch internal volume is reduced. The pouch material may be strong enough to handle pressure inside the pouch when pressurized. Other materials can be used as that does not degrade the medication contained in the pouch 4502 and the desired mechanical properties (such as the strength and flexibility of the pouch) is met. The tubing 4510, inlet 4506, or outlet 4504 can be made with a material having similar or the same properties as the pouch 4502. For example, the material can be a silicone material (including platinum cure).
One or more types of insulin may be utilized in the pump system(s) described herein. For example, a pump may utilize a fast acting insulin. Fast acting insulin is one that creates glucose concentration changes in less than 20 minutes. It is important that this change happens in less than 20 minutes so that a person with Type 1 diabetes who eats a meal (which can also appear within 20 minutes) can counteract their blood sugar change to food in a timely manner.
The two states of insulin: monomeric and hexameric, are two insulin states generally correspond to fast and slow body response, respectively. Traditionally, insulins used in pumps are of the relative concentration U100 and are fast acting. In some embodiments of the systems and methods described herein, an insulin pump may utilize U200 insulin, reducing storage size by half and allowing for a smaller pump apparatus.
As illustrated in
The exit 4522 of the pump 4503 can connect to the tubing 4510. The tubing 4510 can extend into the cannula 4512, which may be inserted under patient skin. The pump 4503 may be configured to push the drug into the patient tissue under skin. A bolus mechanism may accordingly be a set of repeated pump actions in a short time that yields a desired bolus size.
The pouch 4502, tubing 4510, and cannula 4512 are part of the fluidic system of the disease management system. Pump tubing 4510 may be internal to the device with the exception of the insulin cannula 4512. While the tubing 4510 will transfer fluid from the pouch 4502 to the cannula 4512, the roller 4524 inside the peristaltic pump will stop and control the un-desire leakage or dosage. The peristaltic pump 4503 is able to lock and hold up designated pressure from the pouch 4502. The pouch 4502 may be designed such that it will not deliver pressure more than the pressure the pump 4503 cannot hold. In addition, the fluidic system may be designed to prevent users to alter the prefilled insulin pouch 4502 by adding or extracting medication from it. In some examples, the disease management system may have no refill capability to ensure high quality closed loop performance. The pump may allow discrete usage by maintaining low audible noise levels.
A pump controller may include one or more hardware processors configured to cause the pump to perform one or more pumping actions. In some examples, a pump controller may include a PCBA of the device or separate electronics. The pump may be connected to and controlled by the controller. In pump configurations with actuator components, the controller may be configured to have a microprocessor and actuator control circuit.
In some examples, the controller may be configured to provide notifications of pump activity to a patient. For examples, the controller may be configured to display a notification using audible, tactile, or visual means using components of the disease management system or associated device. In some examples, the controller may be configured to communicate pump activity or status to a user device or the cloud.
The pump activity or status may be displayed on a device interface through, for example, an associated application. Aspects of a pump may be controlled by the associated or companion mobile device application (for example, on a smart phone and smart watch). For example, settings, controls, and alarms can all be set and managed in this interface. Additionally or alternatively, the pump can have a mechanical mechanism for dosing of a predetermined bolus insulin amount. The mechanical interface can have a two-step interface to reduce chance of accidental dosing. In some examples, the pump may have visual feedback of system status and alerts. In some examples, the pump may have a haptic feedback motor to communicate alarm events to the user as well as assist with device replacement process.
1. Example Peristaltic Pump System
As illustrated, three or more rollers 308 are in physical contact with the circular portion 302A such that when the circular portion 302A rotates, the rollers 308 rotate. A casing 304 wraps around the circumference of the rollers 308 and the circular portion 302A. The casing 304 and the rollers 308 cooperate to form a circular channel. The rollers 308 are located at an inside portion of the circular channel and the casing 304 is located on the outside of the circular channel. A tubing 306 is located within the circular channel and the tubing physically contacts both the casing 304 and the rollers 308. When the circular gear 302 rotates, the circular portion 302A drives the rollers 308 which apply pressure to the tubing 306 such that insulin is driven from an inlet 306A of the tubing 306 to an outlet 306B of the tubing 306.
In some implementations, the number of rollers 308 can vary. There can be as few as two rollers however there can also be more than three rollers depending on the application. Further, while the primary operation of the peristaltic pump 300 is driving insulin from the inlet 306A of the tubing 306 to the outlet 306B of the tubing, the peristaltic pump 300 may also operate in reverse where insulin is driven from the outlet 306B to the inlet 306A. Further, the peristaltic pump 300 may pump other liquids than insulin such as a saline buffer solution.
In some implementations, the number of rollers 408 can vary. There can be two or more rollers 408 and the number of rollers 408 can depend on the application. Further, similar to the peristaltic pump 300 of
Advantageously, the peristaltic pump 400 of
2. Example Insulin Priming in a Pump System
Insulin priming is a frequent concern among persons with type 1 diabetes. An unprimed insulin pump can result in hyperglycemia. However, a primed insulin pump may have leaky insulin due to pressure differentials during insertion. Conventional solutions often require user awareness and visual observation of properly primed insulin at the tip of a cannula and can leading to sometimes unexpected results. Systems and methods described herein may improve the priming process to reduce issues of leaky insulin and provide more consistent and expected results.
Peristalsis gears may lock fluid in place and prevent diffusion between gears and insulin reservoirs. Let us define tubing track 1 as between the cannula tip, gear 1, and gear 2 where there exists a buffered solution with no insulin. This region could also be air but a buffered solution is considered more advantageous so as to prevent air bubbles. A buffered solution can be safely injected into interstitial space. Let us define tubing track 2 as beyond gear 2 and all the way to the insulin reservoir resides pre-filled insulin. The quantity of buffered solution in tubing track 1 is known due to the inner diameter and length of tubing track 1. This value in one embodiment will be less than 0.25 U of equivalent insulin. The device may also contain or be connected to a CGM which can be monitored to determine if it is safe to bolus the equivalent of 0.25 U of insulin (Even though, at this stage there is no insulin in tubing track 1). Once a CGM verifies the users interstitial (or plasma if regressed) glucose is in a safe range the peristaltic system will move forward to inject the buffered solution into user.
The above injection could occur during a “warmup” period for the device which has just been inserted. This situation is especially beneficial to interleaved CGM devices. To double check only saline has been administered another device, CGM, can monitor glucose levels to determine if the body is or is not responding to insulin over a 1 hour period. If the body does appear to be responding to an insulin injection the device could be flagged as a faulty unit or a flag of possible insulin injection could be passed to a closed loop controller.
Once the system has gone through this procedure (which may be up to and including 1 hour), the insulin pump can be considered primed and ready for full and normal operation.
In block 504, the peristaltic pump 604 is run to pump insulin 650 from the insulin source 602 through the inlet 606A to the outlet 606B until insulin exits the outlet 606B.
In block 506, the outlet 606B of the peristaltic pump 604 may be connected to a buffered solution source. In some implementations, the buffered solution in the buffered solution source may be saline. The buffered solution source may be connected to the outlet 606B through the needle 610. The needle 610 may also be removed or not present and installed after priming the peristaltic pump.
In block 508, the peristaltic pump 604 is run in an opposite direction to pump insulin from the buffered solution source to the inlet until the buffered solution 652 enters all the tubing 606 contacting each of the rollers 608.
During the manufacturing procedure, a brand new, empty device can be preloaded with insulin by following the procedure:
As an additional quality to prevent buffer leakage/dehydration, the system can be capped with a hydrogel matrix or silicone that is removed at time of insertion by an applicator or user.
At block 704, it is determined whether the patient's glucose level is at a safe range to accept a small dosage of insulin. This step is performed to make sure that if the peristaltic pump 602 malfunctions while operating, that the patient is not harmed with a dosage of insulin 650. The patient's glucose level may be determined through the use of a glucose sensor such as the glucose sensor of any implementation of the disease management system described herein which may include a glucose sensor and insulin pump as one system or glucose sensor of the sensor system 200B of
At block 706, the peristaltic pump 602 is operated until all the buffered solution 652 within the tubing 606 has exited the tubing 606.
At block 706, it is determined whether the patient's glucose level significantly changed. As in block 704, the glucose level may be determined using a glucose sensor such as those mentioned above. If it is determined that the patient's glucose level has significantly changed then, at block 712, the peristaltic pump is determined to be defective since insulin was likely administered to the patient when only the buffered solution should be administered to the patient. If it is determined that the patient's glucose level has not significantly changed, then, at block 710, the peristaltic pump is determined to be operating properly since it is likely that only buffered solution was administered to the patient.
3. Example Valve Style Insulin Pump System
In some implementations, the intermediate second valve 802B may be multiple valves in order to vary the dosage. For example, there may be two valves and only one is opened to provide a smaller dosage than if both valves were opened. Further, the intermediate second valve 802B may be an adjustable valve which may not open fully depending on an input such as a voltage applied to the second valve 802B. In some implementations, there may be a filter at the output 814 or someplace from the output 812 to the valve style insulin pump 800 in order to avoid particles from the patient from being trapped between actuator components within the valves 802A-c. At the stage of
The piezo crystal valves may be manufactured using a piezoelectric ceramic, fine PZT powder mixed in specific proportions and then heated to form a uniform powder. The piezoelectric powder may be mixed with an organic binder and formed into structural elements having a certain shape (for example, discs, rods, or plates). Piezo crystal valves provide adequate power while being a small form factor and low power consumption.
The valve style insulin pump 930 may operate similar to the valve style insulin pump 800 described in connection with
In some implementations, the valve style insulin pump 930 may include a flow chamber which may control the maximum flow rate when all the solenoids 932A, 932B, 932C, 932D. In some implementations, a photo sensor may be included at the exit of the insulin flow channel 940. The photo sensor may detect whether the exit valve is open or closed and may measure the presence of air bubbles. In some implementations, a membrane made out of a permeable material such as polytetrafluoroethylene (PTFE) or one or more small holes may be added to vent accumulated air.
4. Example Gear and Plunger Pumps
In some examples, a pump head can utilize plungers to squeeze tubing and cause fluid to flow from a medication pouch to a cannula.
When not powered, a core spring 4511 may cause a plunger 4515 to extend at least part of its length outside the solenoid assembly. The plunger 4515 may be configured to squeeze or pinch tubing 4517 when extended. In some examples, a controller may send current through a solenoid 4513. When powered, the plunger 4515 inside the solenoid assembly may pull the plunger 4515 back into the solenoid assembly. As illustrated, a pump 4507 may include a plurality of solenoid assemblies and plungers. By controlling the power to each of the solenoid assemblies, a controller may be configured to cause the pump 4507 to alternate the application of pressure to different areas of tubing 4517 to, for example, deliver a bolus to a patient.
The tubing 4702 may, in some examples, be composed of a silicon material, such as a platinum cured silicon. An inner diameter of the tubing may be in a range of 0.1 to 1 mm, or a value outside that range, such as a value more or less than in that range. For, example, an inner diameter may be approximately 0.5 mm. An outer diameter of the tubing may be in a range of 0.1 to 2 mm, or a value outside that range, such as a value more or less than in that range. For example, an outer diameter may be approximately 1 mm. A working temperature of the tubing may be approximately 80 to 500 degrees Fahrenheit or a value outside that range. In some examples, a durometer hardness may be approximately 50 A or a value greater or less than 50 A. The tubing may be configured to hold fluid at a desired pressure when force is applied. For example, if a 20 gF is applied to the plunger, the tubing may be configured to hold fluid in the tubing at a pressure of 300 mmHg or more or less. This holding force can, advantageously, help ensure proper operation of a pouch bursting safety mechanism.
In some examples, such as illustrated in
The actuator(s) 4704 may be configured to engage with the gear(s) 4712 using at least one cleat(s) 4714. The actuator(s) 4704 may be configured to include a solenoid coil and metal rod. The metal rod may be coupled to the cleat 4714. By controlling the power to the solenoid coil, the actuator 4704 may be configured to move the metal rod and accordingly, the cleat 4714. The positioning of the actuator may be such that the cleat 4714 engages with teeth 4711 of the gear 4712, rotating the gear a set amount. The hardness of the cleat 4714 may be similar to the hardness of the gear and/or gear teeth. Advantageously, this may help prevent failure by encouraging equal wear between components. Also helpful in preventing wear is the reduction of strain or force needed to actuate. A longer cleat may help reduce strain and accordingly, reduce fatigue rate.
A lock 4718 may be used to help prevent unintended rotation of the gear. For example, the lock 4718 can allow the gear 4712 to rotate forward with minimal interference but will induce high blocking force to prevent reverse operation.
One or more plungers 4710 may be configured to apply pressure to the tubing 4702 upon being engaged by the gear 4712.
As illustrated in
A storage state of the device may have two plungers down that are, for example, the plungers closest to the pouch. This storage state may reduce the number of air pockets possible to form during manufacture or fill of the pouch. Advantageously, starting at this state may give a reliable starting state for programming in priming the disease management system for first time use.
A device priming cycle may be configured to perform quickly. For example, a device priming cycle may be performed in less than 1 minute, less than 30 seconds, less than 15 seconds, less than 10 seconds, or other amount of time more or less than 1 minute. In some examples, a priming cycle may occur in roughly thirteen seconds. This time may be defined by the tube length and diameters from the cannula tip to the middle peristaltic plunger. The priming process may occur prior to, during, or after application of the device to the user. For example, the priming process may occur between the removal of the device from packaging and the application to the patient's body. The priming process may be initiated by firmware through a decision logic based on wireless connections to another device or the cloud. The pressure generated from the priming process may cause the fluid 4654 to blow through a sterilization gel cap in the fluidic path 4656. Where priming occurs prior to application, upon application, the remaining gel cap may be ripped off by the applicator action.
5. Example Muscle Wire Pumps
6. Example Piston Pump
The piston assembly 4670 may include a combination of one or more standard springs 4680 and muscle wire springs 4682. The muscle wire springs 4682 may be configured to contract when powered, causing a rod 4672 to extend outward from the piston assembly 4670 and engage a valve assembly 4660. In some examples, the valve assembly 4660 may include a valve 4678 configured to move fluid from an inlet 4674 to an outlet 4676 as it changes position horizontally in response to engagement by the piston 4672. The valve 4678 may include a cylindrical valve with two or more larger cylinders on ends of the valve. In some examples, the larger cylinders may form a seal with the inner diameter of the valve such that fluid 4668 is moved with the movement of the valve. In some examples, the valve 4678 may include a spool valve or other directional control valve. As illustrated, a piston assembly may be in a contracted state 4664, drawing fluid 4668 from a pouch or bladder. When the piston assembly is in an extension state 4666, fluid 4668 may be pushed out of the valve assembly 4660 and towards a cannula.
Air bubbles pumped into a user through an insulin pump can pose a serious health risk during closed loop care. While air bubbles alone entering into the interstitial space may not be considered a significant risk to a patient, there are some concerns about air bubbles entering vasculature when they reach a size upwards of 20 mL. In some examples, risk may also arise where an air bubble displaces insulin such that a patient becomes underdosed, which may lead to a patient becoming hyperglycemic. This alone may be a minor risk as the volumes of underdosed insulin are on the order of less than 1 unit. In some examples, risk may arise if underdosing occurs frequently enough an algorithm that personalizes dosing begins estimating that a person with type 1 diabetes is insulin resistant, which may over time pose significant risk to a patient.
A treatment system described herein may include one or more air bubble detection sensors for monitoring or detecting air bubbles from drug delivery devices, such as an insulin pump, infusion pump for saline, or other drug delivery device. An air bubble detection sensor can determine an amount of air bubble in an insertion tube, so that a drug delivery device can compensate for air bubble displacement of a drug in an injection dose and/or notify a user to perform an action to remove the air bubble. In some examples, long-term air bubble quantification can be tracked and used to correct for potentially wrongly assigned insulin resistance by an algorithm that personalizes dosing of insulin.
An air bubble detection sensor may include an optical sensor system (using light emitting diode and photodiode), pressure sensor system (mechanical), ultrasonic sound system, and/or capacitive sensor system.
In some examples, an air bubble detection sensor may include an optical detection system. For example, an optical detection system may include absorptive, scattering, or other optical sensing method to detect air bubbles. For example, detection may occur if knowledge of an initial intensity Jo of light from a light source (such as an LED) is known or characterized and a change in signal as the light passes through a channel containing the insulin, such as an insertion tube. Drugs or nutrition have higher light absorption or scatter than air. As illustrated in
In another example, an optical detection system may include a system based on refraction. For example, drugs or nutrition may have refractive index different than air. An orientation of at least one light source and matching detector may be positioned so as to take advantage of the different angle of refraction that may occur as a result of the different refractive indices of air and nutrition or drugs, such as insulin. For example, as illustrated in
In another example, an optical detection system may include a system based on a detected discontinuity in a signal. For example, as illustrated in
Another example method to measure air bubble volume is using a capacitor along an insertion tube. When a current is applied between two conductive wires, or conductive powder layers, as shown in
A capacitance of a whole tube with air bubbles can be written as:
For example, where a tube length is 6 mm, a conductive width is 0.2 mm, an inner diameter is 0.5 mm, then a capacitance may be around 1 pF. In another example, where a tube length is 12 mm, a conductive width is 0.2 mm, an inner diameter is 0.3 mm, then a capacitance may be around 2.9 pF. An air bubble volume or insulin to air ratio in the tube or channel may be determined based on a capacitance value.
In some examples, a treatment system may remove air bubbles in order to reduce risk associated with delivering air bubbles to a user via a drug delivery device. For example, an air bubble removal system can include utilizing a micro mesh, membrane, or holes along a cannula. Air bubble can pass through a small hole on a hydrophobic surface but a liquid will not pass through. Using this concept, an air bubble can be removed by micro-holes or micro-membrane using a hydrophobic or hydrophilic (surface tension) mechanism. For example, an air bubble can be removed by micrometer holes or micrometer membrane at certain pressures by using the concept of hydrophobicity. A pressure needed to remove air bubbles can be described as:
Thus, the size of the holes may be reduced when the liquid pressure is increased. A number of membranes can be used to remove air bubbles, including but not limited to polypropylene and polyester membranes having pore sizes between 0.1 and 5 micron, thickness between 3 and 10 mil, air permeability between 0.05 and 8 ft3/min-fit2 at 125 Pa, water entry pressure of between 1 greater than 60 psi, an IPA bubble point of between greater than 0.5 and 20 psi, a surface treatment of hydrophobic or oleophobic, or some other combination of parameters, that have greater or lesser values.
The air bubble removal can be designed to include membrane or holes, such as shown in
1. Example Working Electrode of a Sensor System
An in-vivo, CGM sensor may be constructed with a working electrode (also referred to as a “WE” or cathode). The working electrode may include an alloy, such as for example, a platinum-iridium alloy (“Pt/Ir”) wire onto which enzyme glucose oxidase (GOx) is deposited. A working electrode may be configured to work with a reference electrode (also referred to as an “RE” or anode). In one example, a wire working electrode may be inserted within a tubular electrode having a larger diameter than the wire working electrode that may be configured to serve as the reference electrode. The reference electrode may include a Silver chloride (or Ag/AgCl) electrode. The WE wire and tubular RE may be separated by an insular material, such as a thin insulating coating.
The enzyme GOx may be deposited and trapped onto the surface of the WE wire using some combination of electro-deposition, electro-polymerization, and physical adsorption of a polymer such as o-phenylenediamine, aniline, or other polymer. The inclusion of the polymer may have multiple purposes. For example, the polymerized mesh may physically trap the GOx enzyme and adsorb it to the WE surface. In another example, the polymer backbone may be electrically conductive and facilitate the transfer of electrons to the WE. Additionally or alternatively, other polymer layers constructed of, for example, Nafion, Cellulose acetate, the like or a combination thereof, deposited below or above the GOx deposition layer may normalize the levels of glucose and oxygen. These other polymer layers may help linearize a current response to physiologically relevant glucose concentrations. Additionally or alternatively, the other polymer layers, (such as cellulose acetate) may protect the activated WE metal surface (such as the Pt/Ir surface). This protection is beneficial because the activated surface of the WE is important in developing a sensitive glucose sensor because the reaction of the Pt/Ir surface with hydrogen peroxide is primarily responsible for the creation of the electrical signal which is measured by the electrical circuits of the system.
In another example, a sensor may be configured to remove or reduce the CGM's dependence on dissolved oxygen and help substitute the function of oxygen with the use of a small molecule, sometimes referred to as the “mediator”. The mediator may function in a similar fashion to oxygen in the context of the sensor system to facilitate the transfer of electrons from the enzyme (GOx) catalytic center to the electrode. The mediator may be fabricated into the sensor head in a proportion that may enable this functionality. In some examples, the proportion may be empirically determined. The mediator may be constructed out of molecules that can accept electrons in a stable manner and/or give up the electrons in certain conditions, such as at the electrode surface. A mediator can include any number of materials, such as ferrocene, ferricyanide, Osmium based transition metal complexes or the like. In some examples, the enzyme (GOx), the mediator(s) and/or polymers may be covalently bound to the metal electrode to form the sensor for detecting glucose. In this sensor configuration, construction may also be encapsulated with multiple layers of polymers (such as Nafion). The layers of polymers may serve specific purposes. Additionally or alternatively, the polymers may limit the concentration of glucose at the enzyme to linearize the current response to various concentrations of glucose. In some examples, the addition of mediators may include additional steps to ensure biocompatibility of the mediator molecules along with the stability of the sensor fabrication to keep the molecules from leeching after invasive implantation. In some examples, an electrode that includes a mediator may be constructed using a of Gold (Au) or Pt/Ir electrode.
Advantageously, the selected polymer layers and GOx are biocompatible. Similarly, Pt/Ir, Au and Ag are noble metals with excellent biocompatibility.
Various methods of recording electrical signal may be used. For example, cyclic voltammometry, amperometry, voltammetry, or another method of recording electrical signal may be used A method may be selected based on parameters such as reproducibility and accuracy of glucose concentrations over the lifetime of the sensor.
A CGM sensor may detect and convert concentrations of glucose to a proportional electrical signal (current or potential) by a series of electron transfer steps between GOx, FAD, peroxide molecules and finally to the working electrode. However, this proportionality constant is sensitive to a range of physical and biochemical parameters. These parameters may be controlled and standardized during fabrication in order to help produce more consistent signal. For example, such parameters and example (but not exclusive) method(s) of standardizing these parameters for fabrication can include, but are not limited to: 1) geometry and size of the sensor head, which may be evaluated by cyclic voltammometry of a known and well-behaved redox compound like ferrocene or potassium ferrocyanide for consistency; 2) amount of glucose oxidase enzyme captured on the sensor head, which may be evaluated by electrical signal detected on the Pt/Ir electrode to known concentrations of peroxide and compared with the glucose response; 3) applied voltage between the working electrode and the reference electrode, wherein the working voltage can be determined by cycling through or probing of various voltages for a known concentration of glucose; 4) polymer coating(s) that may normalize the concentration of glucose and oxygen, which can be evaluated based on the linearization of electrical response to glucose concentration with various concentration of polymer coatings; 5) the surface “activation” and preservation of platinum electrode that oxidizes hydrogen peroxide, wherein the inclusion of cellulose acetate polymer coating of Pt/Ir electrode may protect the surface “activation” in a functioning glucose sensor for the purposes of standardization and consistency; 6) the polymer coating that filters out interfering species such as ascorbic acid, urea, acetaminophen, wherein a Nafion polymer coating may be utilized to reduce interference in electrical measurements; 7) the conducting polymer that provides an efficient “pathway” for the electrons to reach the platinum electrode, some polymers such as PANI, PoPD and other polymers that may include conducting polymers may be used for this purpose; 8) the local diffusion behavior of glucose and oxygen near the sensor, wherein the diffusion behavior can be characterized by comparing the electrical response of the constructed sensor to standard equations of electrochemistry; 9) leeching or degradation of polymer layers, mediators and glucose oxidase enzyme, wherein the binding strength of the components of the sensor will be characterized by following the “leakage” of these components during long-term usage and incubation of the sensor in in-vitro buffer or blood/plasma. UV/Vis spectroscopy, chemical determination, Raman spectroscopy and atomic force microscopy are some of the biophysical methods that can be used to characterize this phenomenon; 10) the drift/stability of the reference electrode (Ag/AgCl), wherein the Ag/AgCl reference electrode is constructed with any number of methods and wherein the electrodes may be calibrated against industry leading, low-noise and long-term stable commercial Ag/AgCl electrodes; 11) temperature and pH of the measurement location, which can be accounted for in testing in an electrochemical cell to test for the temperature and pH consistent with the human body (pH 7.4 and 37° C.); 12) depth of penetration of the sensor into the ISF. Ideally, the depth of insertion of the sensor head should be fairly precisely controlled using the applicator. This depth will partially determine the lag time of glucose values between blood and ISF. Location of the CGM (abdomen vs arm) is another factor that determines lag. This can be tested using a bio-simulator and/or animal testing.
To address the comfort of a user having to use a sensor device, the reduction in size (diameter) of sensor electrodes is important, as is the durability of the probe design to withstand the rigors of a physically active patient and importance of repeatable accuracy and economical production of these probes to keep CGM unit costs reasonable for typical patients. Systems and methods described herein help address the above concerns.
When constructing the electrochemical probe, the use of specific metals and electrode surface platting may be used to achieve a desired signal return. Some metals that may be used for this purpose include but are not limited to Platinum, Gold, Silver, and Silver-Chloride. Other combinations of metals and surface platting may also be possible. Other iterations could include other materials, such as electrodes made of carbon nanotubes, graphene electrodes, gold nanoparticles deposited on other metallic surfaces, glassy carbon, Zinc Oxide nanorods, indium tin oxide, the like or a combination thereof.
Once the probe is constructed of the correct combination of metal electrodes, many probe designs also require the application of chemical agents and buffers to either exaggerate or manage the gain of the electro-chemical reaction to target the desired molecule; in this case Glucose.
2. Example Sensor Calibration
Glucose estimation in a sensor system may be determined based off one or more physical measurements. In some examples, one or more parallel engines may recombine multiple analyte or glucose estimates once a physical measurement has been acquired. The sensor system may include a plurality of hardware elements. The plurality of hardware elements may include: a 3-electrode system (reference, counter, and working) and one or more temperature sensors, such as one or more thermistors.
In some examples, a sensor system may include a single thermistor. The thermistor may be applied to a user at the same or similar depth fat the tissue site as the working electrode so as to measure internal skin temperature. In some examples, a sensor system may include two thermistors. For example, a first thermistor may measure a skin surface temperature and a second thermistor may measure an ambient temperature. The sensor system may then determine or extrapolate an estimate of temperature into the tissue at the depth of a working electrode. The selection of a single thermistor or dual thermistor system may be based on empirical testing, such as animal testing.
In some examples, an electrochemical signal from the interface of the working electrode may be quantified on an ADC. The sensor system may then temperature correct the raw digital signal and/or may utilize a calibration curve to linearize the CGM response with respect to glucose. In some examples, the calibration curve may be based on one or more empirical characterizations of one or more electrodes of the sensor system. For example, each unique electrode may have an empirical characterization. In another example, unique electrode characterization may be avoided and a generalized calibration curve may be used. In some examples, individual sensor calibration may not be needed or used.
The sensor system may determine a confidence parameter associated with one or more hardware components or a combination thereof of the system. In some examples, the confidence parameter may be based on one or more parameters associated with the sensor system, such as some combination of: sensor manufacture date, ship date, current date, insertion date, skin and/or ambient temperatures during use, high frequency electrical noise, insertion site consideration, observed sensitivity level, the present glucose prediction as compared to a voluntary SMBG or glucose insulin meal models, insulin considerations, and/or the like.
In some examples, the sensor system may make retrospective adjustments to the sensor calibration. For example, the sensor system may make adjustments with respect to a glucose trend, glucose insulin meal model, or other calculated value to account for interstitial lag. Advantageously, the adjustment may improve the analysis and display of historical data. In some examples, an actual glucose prediction presented at the time of prediction for every time point may also be stored.
In some examples, a device may coordinate one or more glucose estimates with a Kalman filter or weighted average to give an improved accuracy, precision, and resilience over traditional CGM systems.
A treatment system may include an applicator to provide a disease management system, such as an insulin administration device, to a tissue site of a user or patient. In some examples, an applicator may be reusable or one time use. In some examples, an applicator may include one or more measures to reduce anxiety of application and/or pain associated with application of a disease management system. In some examples, an insulin cannula may be retractable by an applicator once insulin reservoir is emptied. Advantageously, the retraction may allow wound healing to begin. An applicator may be configured to insert both CGM and insulin pump needles simultaneously. An applicator may be configured to hide one or more needles from view at various stages of insertion, including, but not limited to opening sterile pack, loading any springs, insertion, applicator removal, and applicator disposal. The applicator may be usable with a single hand. An applicator may be usable with either a user's left or right hand. An applicator may have one or more features which releases a safety mechanism. An applicator may fire through a simple mechanism once a safety is released. In some examples, a safety mechanism may not be accessible from outside the sterile packaging. Advantageously, such a limit to accessibility may help prevent accidental firing while peeling off a sterile wrapper top, in shipment or in storage. An applicator may be intuitive and require minimal effort to apply. An applicator may have a rapid anesthetic injector to prevent feeling insertion pain. An applicator may limit the pieces of disposable items, such as merely a sterile container and/or applicator (if disposable). In some examples, an applicator may not have tape adhesive trash because a sterile unit may include adhesive protectant. In some examples, a size of the applicator may be larger than a disease management system being applied, such as twice the volume of a disease management system.
A spring loaded holding mechanism 1406 is capable of securely holding the disease management system 1410 within the housing 1402. A button 1404 is located on the top of the housing 1402 which is connected to a force mechanism 1404A which is in contact with the disease management system 1410 with the needles 1412. When the button 1404 is pressed, the force mechanism 1404A is activated such that the spring loaded holding mechanism 1406 is released and the disease management system 1410 with the needles 1416 is propelled downwards towards the patient. After the disease management system 1410 is applied to the patient, the needles 1416 are retracted by needle holding mechanisms 1414 while the cannulas 1416 stay within the patient. Thus the disease management system 1410 is able to access the patient's interstitial fluid or blood.
The needle holding mechanisms 1414 attached to the needles 1416 are ejected by pushing another button 1408. While the button 1408 is located on the side and the button 1404 is located on top, in other implementations, the buttons may be located on other portions of the housing 1402. Further, by ejecting the needles 1416, the applicator 1400 may be loaded with a fresh set of needles 1416 and another disease management system 1410 and thus be reusable. In some implementations, the applicator 1400 may be one time use with the needles 1416 being disposed of with the applicator 1400 thus making the applicator 1400 disposable.
One or more clamping mechanisms 1506 is capable of securely holding the disease management system 1510 within the housing 1502. One or more force mechanisms 1504 are connected to the outer portion 1502A of the housing 1502. When the outer portion 1502A is pressed down into the inner portion 1502B, the clamping mechanisms 1506 releases the disease management system 1510 and the forcing mechanisms 1504 propel the disease management system 1510 with the needles 1512 downwards toward the patient. After the disease management system 1510 is applied to the patient, the needles 1512 are retracted by needle holding mechanisms 1514 which may be forced upwards by springs 1518.
In some implementations, portions of the applicator 1500 may be disposable while other portions may be reusable. For example, as shown in
In some implementations, the applicator 1500 and the disease management system 1510 are presented to the patient as a packaged unit with the disease management system 1510 docked within the applicator 1500. The needles 1512 and the needle holding mechanisms 1514 may be disposed of with the applicator 1500 after application of the disease management system 1510.
1. Example Applicator Wheel
2. Example Distraction During System Application
Application of treatment systems may result in anticipated pain in certain users. Anticipatory pain can be high in, for example, new users who have needle phobia and can be a hindrance for children or their parents applying a treatment system to their children. Systems and methods described herein may help reduce anticipatory pain.
In one embodiment, a system may reduce anticipatory pain by distracting the patient during application of a treatment system. In some examples, the system may utilize companion software, such as an application on a user's mobile device or other graphical user interface or platform. In some examples, the companion software may communicate with one or more aspects of the treatment system, such as an applicator tool. The applicator tool may provide status of the placement of one or more aspects of the treatment system, such as a CGM sensor. The applicator tool may communicate with the mobile device running the companion software directly or indirectly, with wires or wirelessly, such as through Bluetooth and/or NFC communication.
The companion software may gamify the application process. A goal of the game is to distract the attention of the patient with visuals, audio, and tactile feedback. The game may be themed according to the interests and tastes of the user, maturity level of the user, familiarity with treatment system. The companion software may communicate stimuli based on a position of the applicator tool or other component of the treatment system and stimuli based associated with the process of the un-packing and application steps from preparing site to injecting needles to finally securing the device. The positioning may be captured by the CGM/pump device's accelerometer, gyroscope, and/or RFID tags within packing or based on the user's acknowledgement of steps through the entertainment game. A climax of the distraction stimuli can be timed with or just after the true injection action into the skin which will help to reduce the anticipatory pain.
3. Example Reduced Pain Application Systems
In addition or in the alternative to distraction systems for anticipatory pain, residual pan and actual pain can be reduced by one or more application systems.
For example,
In some implementations, the less painful of the glucose probe 2402A or the cannula 2402B may be implanted first. With the implantation of one of the glucose probe 2402A or the cannula 2402B, an analgesic may be administered to the patient which may numb the patient before the implantation of the other of the glucose probe 2402A or the cannula 2402B. Thus, when the other of the glucose probe 2402A or the cannula 2402B is implanted, the patient may experience less discomfort.
In some examples, residual pain can also be reduced with hard needles that transition to become the soft cannula itself or dissolve away. Traditional insertion needles are hard needles are made of metal or hard plastic that may result in residual pain for a patient. Systems and methods described herein may allow for reduced residual pain.
In one embodiment for reducing residual pain, a treatment system may use a dehydrated-hydrated needle (DHN) to reduce residual pain. The DHN may be made of one or more materials, such as collagen or hydrogel or other materials that have following properties: soft at wet state (hydrated) and hard at dry state (dehydrated). The DHN may be constructed by dehydrated-hydrate materials by itself or with plastic support.
In some implementations, the solid needle 2506 may be made out of a collagen or hydrogel.
In another embodiment, a needle of the treatment system can be made by segments and which then can control hard or soft through muscle wires. When current is applied through the muscle wire, the wire may shorten to hold all segments straight (inserted state). Without the current, wires may be loose and the segments movable (relaxed state).
In some implementations, at least a portion of the needle may be made out of a material which is soft when a radiation source such as ultra-violet (UV) light is applied to the material and rigid or hard when the radiation source is not applied to the material. In some implementations, at least a portion of the needle may be made out of a material which is hard or rigid when a radiation source such as UV light is applied to the material and soft or pliable when the radiation source is not applied to the material.
In another method, the needle can be a bioresorptable material that never needs to be removed and therefore also never needs an applicator to remove it. In this instance, the total height of a built-into-device applicator can also advantageously be reduced as much as 5 [mm], for example, because no retrieval springs or like methods need to be incorporated into the insertion mechanism. Additionally, as it is a bioresorptable material, the body may seal the wound and wound healing may be promoted to be faster than normal at the site. Additionally, there may also be better water-proofing and more resistance to external infection. Such materials can also have additional medicinal value with adsorbed, absorbed, or chemically altered material properties as they resorb into the body.
In some implementations, at least a portion of the needle may be made a material which degrades when exposed to the inside of the patient. The material which degrades may be a bioresorbable material. Advantageously, using a material which degrades when exposed to the inside of the patient allows for the needle not to be retracted after it is implanted within the patient. Thus, the applicator may not include springs for retracting the needles. For example, the springs 1518 of the applicator 1500 which are described in connection with
Additionally or alternatively, pain relief or analgesic may be administered to reduce both actual and residual pain. For example, analgesic can be incorporated into an adhesive layer of a CGM device or sensor. In one embodiment, a device would first attach to the user with the adhesive layer before launching needles. Before launching needles, the analgesic in the adhesive could diffuse over a period of time (for example, 15 minutes) in order to numb the site prior to needle insertion. Once numb, a built-into-device, re-usable, or disposable applicator can be fired to less painfully insert the device into the body.
In another example, pain relief can be administered in a time series based method. For example, first, a less painful needle could be inserted into the user at the insertion site that would sub-dermally deliver analgesic. Then after a period of time, the Cannula could be inserted in a manner that may less painfully (in terms of both physical and apprehensive pain) insert the device into the body.
In another example, analgesic can be administered by a pressurized jet that may be capable of delivering numbness in a relatively short period of time (for example, seconds). Once completed, a built-into-device, re-usable, or disposable applicator can be fired to less painfully (in terms of both physical and apprehensive pain) insert the device into the body.
At block 2106, the user loads the disease management system within the applicator. The user may load the disease management system by putting the applicator on the insulin dosage unit and pushing the applicator on the disease management system such that the applicator grasps the disease management system. At block 2108, while disease management system is loaded within the applicator, the applicator is positioned on the patient. An adhesive may be used to hold the applicator onto the patient.
At block 2110, the applicator launches the disease management system onto the patient. The applicator may include a button which is capable of releasing the applicator's grasp on the disease management system and therefore launching the disease management system onto the patient. Alternatively, the applicator may include an outer portion and an inner portion such as the applicator 1500 of
After the applicator is removed from the patient, at block 2112, the applicator ejects the used needles and is thus ready to apply another disease management system and thus the applicator may be removable. The user may eject the needles by pressing a button or pulling a level. Alternatively, the applicator may be one time use and thus could be disposed of with the needles and thus the applicator may be disposable.
The user device 1202 or the smartwatch 1204 may be used to display a variety of data or settings such as: glucose measurement data; insulin dosage settings; glucose dosage system status including status of individual disease management systems; glucose sensor life remaining within each disease management system; insulin remaining within each individual disease management system including estimated time the insulin within the individual disease management systems will be exhausted; time left until glucose expires or spoils within each individual disease management system; current or most recent patient glucose measurements; current or most recent patient insulin delivery amounts; graphs and charts depicting historical glucose measurements; comparisons between historical glucose measurements and current glucose measurements; graphs and charts depicting historical insulin administrations; comparisons between recent insulin administrations and historic insulin administrations; graphs and charts depicting historic basal insulin levels; graphs and charts depicting historic and recent dosage times; graphs and charts depicting historic patient carbohydrate consumption; estimated average patient glucose levels; estimated patient hemoglobin levels (for example, hemoglobin A1C levels); time the patient is within normal glucose range; time the patient is hypoglycemic; time the patient is hyperglycemic.
The smart device 1202 or the smartwatch 1204 may be configured to receive authentication credentials, such as a passcode, to actuate a party of the treatment system. In some examples, input of false authentication credentials may result in a cool down period, such as a 1 minute period before the system may accept more authentication credentials. In some examples, the smart device 1202 or the smartwatch 1204 may be configured to allow a user to manually bolus variable amounts of insulin, manually notify companion application of variable amounts of carbohydrate load with variable amounts of absorption time, manually notify the application of impending adverse pre-programmed event types (such as stress, exercise, food, and presentation mode), validate a heuristic guess from the application of possible upcoming adverse event or off-use insulin, or perform other actions. In some examples, the smart device 1202 or the smartwatch 1204 may be configured to present notifications associated with the treatment system or the user.
The smart device 1202 or the smartwatch 1204 may receive and respond to notifications, alarms, and/or alerts. Examples of user devices include, but are not limited to smartphones and tablets. The smart device 1202 or the smartwatch 1204 may be configured to manually send a command to one or more disease management systems to administer a dosage of insulin to the patient.
The smart device 1202 or the smartwatch 1204 may be configured to allow for the following inputs:
The logging of food intake or liquid intake may be performed manually, automatically, and/or artificial intelligence assisted. The smart device 1202 or smartwatch 1204 may be configured to react to an input by recommending temporary or permanent insulin dosage corrections adjustments. The insulin dosage corrections or adjustments may be gradual. The insulin dosage corrections or adjustments may correct a patient's basal insulin levels based on the input. The smart device 1202 or smartwatch 1204 may trigger the disease management system including one or more disease management systems to change the insulin dosage plan based on a patient's input. The smart device 1202 or smartwatch 1204 may require authentication of a user in order to receive the above mentioned inputs and/or make changes to the patient's insulin dosage plan. Authentication of the user may be facial identification, fingerprint identification, pin code identification, and/or password identification.
Different users may be allowed different levels of access to a patient's settings. For example, a caregiver or parent or the patient may be allowed to input whereas certain third parties may be allowed only to view a patient's settings. There may be intermediate levels of access allowed to some third party users which may allow the third party users to only access certain settings. Further certain third party users may be allowed access to manually administer a dosage to the patient. For example, emergency response personnel may be allowed access to manually administer a dosage to the patient in an emergency situation. Further, the patient's information may be accessible by third parties via electronic heath record or electronic medical record connectivity. The patient information may be accessed obscuring the patient's identity in order to provide access to third parties to perform statistical analysis. Also, for example, the patient information may be accessed by emergency response personnel to respond to an emergency situation. The smart device 1202 or smartwatch 1204 may provide access to instructional videos, instructional guides, and various health and wellness education. The access to the videos, guides, and education may be based on the patient's settings and inputs. A smartwatch 1204 may have different interface and displayed detail when compared to a smart device 1202. For example, the displayed controls or settings may be limited on a smartwatch 1204 when compared to a larger smart device 1202.
The smart device 1202 or the smartwatch 1204 may be used to input a variety of data or settings such as aggressiveness of insulin dosage, and/or meal data. The smart device 1202 or the smart watch 1204 may display information to the user such as a reminder to replace a disease management system, a reminder to fill a prescription, a reminder to eat a meal, a reminder to drink. The smart device 1202 or the smart watch 1204 may display warnings or alerts such as warnings of potential malfunctions of a disease management unit or warnings based on spikes in glucose.
Advantageously, the system described herein may facilitate changing of applied devices, such as an insulin pump and CGM sensor. Traditional insulin pumps must be changed every three days to refresh their insulin and each changing time may require the user to go through a multi-step process (14 steps or more and take up to 30 minutes) to connect their pump with a user device or a Personal Diabetes Manager (PDM). As the market moves towards a closed Loop system with two units (a CGM and a Pump), these types of connectivity steps could increase mental burden and introduce confusion, mistakes, and/or take too much time. Systems and methods described herein may reduce the effort and time of a first use and more importantly for repeating users from having to spend time setting up a new pump or closed loop device every three days. By simply scanning the closed loop CGM/Insulin pump device with their user device, a user device may communicate with the CGM/insulin pump device, open a complimentary application on the user device and/or automatically setup the Bluetooth connection between the devices. The application may then give the user feedback that the CGM/Pump device is correctly inserted, communicating, and functioning.
In some examples, a closed loop CGM/pump system (Device) may have communication electronics, such as a Near Field Communication (NFC) tag and an antenna. The communication electronics may be configured to interact and provide a trigger when a host device with a NFC reader and antenna comes near (such as within a few centimeters of) a device antenna. Once the contents of the NFC tag are read by the host device, the host device may open a companion application. Additionally, or alternatively, if no application is installed, the host device may open facilitate download of the companion application (such as by opening an application store link or application). Once the user's user device has the application open, the appropriate screen for new device setup may appear and communicate setup information.
In some examples, when a user brings their smart device within close proximity of their first body installed disease management system, an NFC tag of the disease management system may create a successful Bluetooth communication with the host device and a compendium application can launch (or if no app is installed, then a link to the app store would open to download the app). Once the app is launched, the appropriate screen sequence may load that walks the user through any necessary steps to successful engaged their disease management system to start monitoring and delivering insulin or other medication based on default settings and user adjusted settings that were selected in setup or through other means. These settings could be delivered in a manner to allow the user to think of the first device as a standard CGM and only prompt settings based on CGM features, which a user may be more familiar with. These settings may include, but are not limited to, glucose standard target ranges, glucose activity and food profile ranges.
When a second placed device is being placed for the first time, a user may be prompted to set up insulin pump based features, such as but not limited to insulin sensitivity, suspend thresholds, max basal rates, max bolus amounts, carb ratios, the like or a combination thereof. This secondary device placement may also be done by an applicator with NFC that initiates a cannula insertion on the disease management system when one is already being identified as the CGM the other would activate and insert a insulin cannula.
In another embodiment, all setup screen prompts could come during application of the first device or all during application of the second applied device for the first time. In an additional embodiment, the entire setup process could occur before the device is applied to the body.
In either method of first time use the next time of applying a replacement unit the user would bring the host device close to the new sensor and a Bluetooth connection would be established and the compendium app would launch a single confirmation of previous settings and then be done with setup. If either of the disease management systems the user is wearing reach end of life (for example, is out of or expired insulin) the user can be notified within the application using a feedback message to assure the user that all the insulin in that device was used before they are requested to take it off.
In some embodiments, a parent or other user may be given permission to use their own smart device to make changes to the dosing with an NFC close proximity wave of their child's or other patient's disease management system if that patient is too low to respond or unconscious or otherwise incapacitated.
If multiple disease management systems are used, the companion application on the smart device will also setup the communication between disease management systems to allow standalone operation without the use of a smart device.
Different wearable devices 1308 may be coded differently to trigger the disease management system 1304 to administer different dosages. For instance, a parent may be provided with a wearable device 1308 that may trigger the disease management system 1304 to administer a larger dosage to the patient than a wearable device 1308 given to the patient when the patient is a child. Further, different rules can be applied to each of the wearable devices 1308. One wearable device 1308 may be allowed to manually trigger the disease management system 1304 at any time whereas another wearable device 1308 may be coded to only manually trigger the disease management system 1304 at certain times such as meal times. Further, wearable device 1308 given to different individuals may be separately color coded to enable individuals to differentiate the different wearable devices 1308. Advantageously, the wearable device 1308 may trigger the disease management system 1304 when an individual's user device is out of reach or is depleted of power.
While the wearable devices 1308 may be self-powered without an embedded battery, the wearable device 1308 may also be more robust and include a screen where a user may set specific details on the manual dosage to trigger the disease management system to apply to the patient. The specific details on the dosage may include suspend amounts or timing of the dosage such as how quickly to administer the dosage to the patient. In some implementations, the wearable device 1308 may include the capability of providing the electrocardiogram (EKG) signal of the patient's heart when the wearable device 1308 is worn by the patient and communicate this EKG signal with the disease management system 1304. The EKG signal could be used as a physiological check of the patient before receiving a dosage of insulin.
A disease management system may be configured to communicate with, be operated by, or in conjunction with one or more companion applications. The one or more companion applications may be configured to run in whole or in part on a user's computing device, such as a mobile phone device or wearable device. In some examples, a device may have native software configured to run the device.
A user interface of example companion application or native software may remain simple and intuitive to use for a patient or user. The application may facilitate easy setup of a disease management system through, for example, NFC, Bluetooth connectivity, application download/open, or device enumeration (such as ID, lot number, manufacturing date, shelf life expiry date.
An application may require authentication to configure critical insulin parameters, such as a passcode, password, face lock, or fingerprint in order to change insulin sensitivity, administer manual insulin bolus, external insulin types. If on a smart watch, critical insulin parameters may be implemented in a configurable manner. A companion application may include two factors of authentication to log into a companion application. The authentication may include one or more of a: password, google authenticator, text message, face lock, or email. A face lock may utilize an additional form of engagement such as pressing of a phone side-button or a sliding button gesture to verify that the user really did want their face to provide authentication for the system.
An application may utilize an NFC connection in order to deliver a remote insulin bolus. A companion application may utilize NFC to setup up Bluetooth connections with CGM or CAM devices, and/or Emergency glucagon systems (EGS). A companion application may interface with a device to identify remaining insulin life, CGM life, battery life. A device may utilize a mobile device to interface to a device to facilitate start, setup, or removal. However, the device may be able to operate independently during the rest of its lifetime without communicating with a mobile device when not in setup of a new device. A companion application may be able to synchronize with the cloud through a mobile device to a disease management system. This can include access of multiple days of data, for example, 6 days of secure data storage and personal configuration(s) at different domains (embedded, phone, and cloud). If a cloud connection is unavailable, data storage and configuration(s) may be stored securely on a mobile device and/or embedded on a disease management system. Once a cloud connection is restored, a mobile application and/or device may upload stored data to the cloud.
A companion application may allow a user to select their own insulin sensitivity for a pre-filled insulin brand. As this brand is used, the device may make recommendations in a configuration menu of a graphical user interface. In some examples, an application may notify a user what insulin sensitivity will work best for the pre-filled or other brand. A companion application may allow user to input and handle insulin intake from an external source (i.e. Inhaled insulin etc.) through a graphical user interface in a companion application on a mobile device. In some examples, a user may be able to use their own suggested insulin sensitivity to a brand of insulin. A companion application may allow user to input and handle alternative therapies (medications) from an external source (i.e. GLP-1 etc.) through a graphical user interface on a mobile device.
A companion application may be able to provide notifications or recommendations for helping a user handle hypoglycemic or other events. For example, an application may provide a personalized rescue candy notification for lows and simplified input thereof for pre-defined quantities. A companion application may engage a user if a user is dealing with a hypoglycemic event to prevent sleep until a user has recovered. In some examples, a companion application may facilitate tracking which caregivers participate in hypoglycemic events. A companion application may prevent manual boluses when a user is in a hypoglycemic or tending towards a hypoglycemic state. A companion application may allow user to configure a network of caregivers to be automatically notified in the event of hypoglycemia, hyperglycemia, disconnected cloud connection, empty insulin (across both devices), only single CAM or CGM active, no CAM or CGM active.
A companion application may be able to offer a bolus recommendation based on the meal input (and other states) and subsequently administer the insulin request after user confirmation. A companion application may display CAM or CGM Sensor Confidence Feedback (SIQ) (embedded algorithm may use the signal confidence to titrate therapy). A companion application may display insulin delivery confidence based on occlusion detection, insulin absorptivity, or other parameter.
A companion application may use Augmented Reality for information delivery to user through a graphical user interface or in AR glasses. A companion application may use Augmented Reality to retrieve information from a user's environment to predict patterns in food consumption and exercise. The application may enable AR food quantification and timing. AR detects unusual insulin actions. For example, a system may recognize picking up an insulin syringe to use when glucose is low or insulin on board is high.
A companion application may allow a user to select the site location of device placement. In some examples, an algorithm configured to create personal historical insulin absorptivity values may use this information. A companion application may allow meal and insulin entry from a smart watch command, verbal command, or other input.
A companion application may allow NFC active reading and/or background reading when it becomes available to setup up new disease management systems. In some examples, a graphical user interface of a companion application may allow viewing of absolute glucose/insulin/insulin on board and trending values. A companion application may allow meal entry with time, quantity, and type or other meal related parameters. In some examples, a user may be able to customize base basal rates, insulin sensitivity, and carbohydrate ratio through the mobile application. A companion application may include one or more control modes, such as full closed-loop mode or manual mode (with recommendations). In some examples, a starter or CGM only device may disable application features such as closed loop mode and manual boluses. A companion application may allow a user to synchronize or manually enter their weight. A companion application may allow a user to manually enter or otherwise determine a user's gender, height or age. A companion application may check that a user's weight falls within expected statistics correlated to age, gender and height. This check may be used as a determining factor in insulin dosing via a control algorithm, such as MPC or PID algorithms. A companion application may verify user weight with user and/or caregivers after 3 months of use without a user updating weight. The application may be able to allow user to utilize and configure their off-use insulin (for example, insulin not basal or bolused from insulin pump) by type (for example, ultra-long, long, medium, fast, ultra-fast) and vendor (for example, Novolog, Humalog). A companion application may provide a configuration to allow behavioral prediction of a user's off-use insulin dose and notify the user preemptively for easy entry.
In some examples, a graphical user interface of an application may display a graph with historical and predictive confidence intervals of glucose values. The application may display a graph with historical and predictive confidence intervals of insulin values. The application may display a graph with historical and predictive confidence intervals of meal values. The application may display a graph with historical and predictive values of exercise. The companion application may display an intuitive status of: overall system function (Green, yellow, or red) (Good to go, warnings (such as low battery or insulin supply), or errors). The companion application may display a status of expiring device near 6 day mark in a configurable way. The companion application may display a status of device maintenance every time insulin is empty in a configurable way. The companion application may display a status of CGM warmup time (for example, if only 1 device is active). The application may display a status of CGM stabilization time (for example, if only 1 device is active). The application may display a status and notify caregivers of user configurable alarms, such as current thresholds and predictive thresholds. The application may display a status what insulin sensitivity will work best for the user and bring them to the configuration menu. The notification may also share with the user the expected benefit of following a recommendation. The application may display a status to the user that they are not presently contained within the GIMM or GLIMM envelope. This may suggest that the CGM or CAM is out of calibration or that the user did not enter a meal/insulin/activity. The user may be able to configure display of statuses, such as alarms, notifications, or event history to have control over severity annoyance. Additional options should be possible for caregiver notification severities. A companion application may allow user to silence the most critical alarms of hypoglycemia for a period of time, such as up to 15 minutes. A companion application may request or detect what intervention was taken to silence the alarm. The application may be configurable to allow alarms on a wearable device, such as a smart watch. The application may display a status of low device battery on the mobile device. The application may display a status of device life. The application may display a status of abnormal user body model states (for example, insulin on board, lipids). The application should show how the face, body and mind will look in 5, 10, 20 and 50 years based on recent habit and measures tied to historical data. The application may display a status of out of norm user metadata activity (for example, GPS, activity, pulse rate, spO2, pressure sensor). A companion application may utilize a distraction game to prevent anticipation pain. The application may include an API that enables OAUTH sharing of measurements, user decisions, and model states outbound to other apps such as a companion application, emergency glucagon systems (EGS), external EMRs, or telehealth, such as DocTella. A companion application may provide educational content related to disease management, significance of other measurements, device management, application management, cloud management, or other aspect of the treatment system. The application may enable manual or automated logging, education, and charting of ketones, cholesterol, triglycerides, blood pressure, sleep, and exercise. The application may provide positive reinforcement and warnings when a user makes a lifestyle change that is beneficial and new or not.
In some examples, a backend system or cloud based system (sometimes herein referred to as cloud) may be in communication with a disease management system or mobile device. A cloud based system may send notifications to registered caregiver devices in the event of one or more occurrences, such as hypoglycemia, hyperglycemia, empty insulin (across both devices), only single CAM or CGM active, no CAM or CGM active, if enabled. Cloud may allow storage of all historical data from the user, provided that the cloud has been given adequate time to synchronize with the device and mobile device. A cloud system may provide cross regional cloud architecture, where customer traffic is load balanced across multiple regions, and data is kept eventually in sync using a distributed cross-regional NoSQL database. A cloud system may analyze stored data to provide personalized coefficients to the mobile device and device. A cloud system may enable electronic health record (EHR) connections to allow easy data sharing. A cloud system may enable a user to allow full record allowance with other entities, such as a hospital. A cloud system may enable a user to retrieve CGM data, such as in a spreadsheet format. A cloud system may enable a user to request identifiable data not be tracked or used. A cloud system may provide functionality to record caregiver/coaches decisions/suggestions on behalf/towards the patient when provided. A cloud system may enable a user to request all their data be deleted from device associated databases. A cloud system may allow users to access their historical data and analysis of that data from a web browser.
A cloud system may allow device users and caregivers to make management decisions and observations for the closed loop system. A cloud system may allow device users who are of consenting ability to add caregivers as solely observers or managers of their closed loop system. A cloud system may allow parents of type one diabetes patients who cannot give consent to both own and manage closed loop systems of device users. Cloud based managers of closed loop systems may be able to configure and lock configurations in an application if the device user is unable to consent. Cloud managers of closed loop systems may not be able to insulin bolus a user from the cloud. A cloud system may allow healthcare providers a mechanism to override unsafe configurations and generally provide a method of safe operation ranges a user or caregiver should be personally constrained to for parameters such as carbohydrate ratio or insulin sensitivity. Cloud system may produce a healthcare provider, caregiver and user reports related to user weekly and monthly progress in glycemic control.
A cloud system may provide backup services. A cloud system may provide data aggregation to a coach's dashboard. A cloud system may provide ability for a coach to look into and respond via email, mobile device, or text to chronic and episodic type one diabetes events. A cloud system may contain chatbot to assist with technical support knowledge questions, FAQs, or symptom and side effects. A cloud system may enable troubleshooting of malfunctioning devices for technology support agents. A cloud system may provide payers population management reports. A cloud system may run an MPC control algorithm that is personalized to user. If instability is detected the cloud system controller may move to personal fallback configuration. If instability is still detected controller may move to safe mode configuration. A cloud system may determine a maximum and minimum theoretical limit for the system given current user inputs (for example, meal, insulin, activity, sleep). A connection between mobile device and cloud system may be secured, such as by TLS 1.2 or newer.
In some examples, a companion application may be configured to provide one or more recommendations for managing a user's disease based on one or more inputs. For example, a companion application may be configured to recommend updates to insulin sensitivity, carbohydrate ratio, bolus prediction amounts and timing, or other parameter based on collected user data. In some examples, a companion application may determine a recommendation once a sufficient amount of user data is collected to provide a recommendation over a threshold confidence value. User data may include an amount of insulin administered, glucose values, meal information or other data.
In some examples, a companion application may determine a recommendation through communication with a backend system. For example, a companion application may upload data to a backend system through a network. The backend system may determine a recommendation and communicate that recommendation to the companion application. In some examples, a companion application may determine a recommendation locally, such as through one or more processers associated with a user device, such as a mobile phone or smart watch. In some examples, one or more local processors and a backend system may both perform aspects of a recommendation algorithm. For example, one or more local processors may pre-process data for analysis by a backend system and a backend system may analyze the data to determine a recommendation.
The companion application may be configured to then transmit the one or more recommendations to one or more disease management systems. In other examples, one or more disease management systems may directly communicate with a backend system to transmit user data and/or receive one or more recommendations.
In some examples, a companion application may be configured to utilize a mobile device camera to provide an augmented reality experience. In other examples, a companion application may be configured to interact with an augmented reality device or application to provide an augmented reality experience. An augmented reality experience related to system notifications can include providing virtual content associated with system information, including but not limited to button names, LED light feedback, insulin remaining, section views of a product, failure drawings, active and working renderings or other content, within a user's real world view as perceived through the mobile device or augmented reality device camera. In some examples, an augmented reality experience can include gamification of application of a disease management system (such as the distraction system described herein). In some examples, an augmented reality experience can include using augmented reality tools to communicate food consumption estimations, carbs, food or macronutrient volume, calories, or other food related values through virtual content displayed within a user's real world view as perceived through the mobile device or augmented reality device camera.
A companion application may be configured to allow a user to configure one or more aspects of the treatment system, such as one or more closed loop aspects, one or more notifications settings, one or more connections settings, or other settings. For example, a closed loop configuration can include a closed loop toggle, a carbohydrate ratio, an insulin sensitivity, a suspend threshold, basal ranges, bolus confirmations, or other setting. In some examples, notifications settings can include settings related to notifications regarding predicted plasma or interstitial glucose hypoglycemic events, predicted plasma or interstitial glucose hyperglycemic events, current plasma or interstitial glucose hypoglycemic events, current plasma or interstitial glucose hyperglycemic events, insulin related status, pump related status, CGM related status, heuristic lifestyle related status (such as off-use insulin guesses, meal guesses, adverse event guesses, the like or a combination thereof), disease management system status (or device health), or caregiver notification of patient status. In some examples, connections settings can include configurations related to a primary disease management system, a secondary disease management system, Apple Healthkit™, or 3rd party connections. In some examples, other settings may include audio or haptic settings, airplane mode, serial number, certifications, copyrights, patents, user guides, the like or a combination thereof.
A companion application or other aspect of a treatment system may be configured to display one more notifications associated with a disease management system, companion application, or other aspect of a treatment system. For example, a companion application may have one or more system status icons or states. The status icons or states may include a color based indicator, such as a green, yellow, or red indicator. In some examples, a disease management system may have a light indicator, such as an LED light configured to display one or more colors, such as yellow, red, or green. In some examples, a green color in an icon or light indicator may indicate a control algorithm status, such as an activation of closed loop mode. In some examples, a yellow color in an icon or light indicator may indicate a warning status, such as Bluetooth connection failure, low insulin, or low battery. In some examples, a red color in an icon or light indicator may indicate a caution status, such as where an action by a user is required or a dangerous condition is detected. For example, a caution status can include a system replacement required, such as insulin out, cannula error, sensor error, the like or a combination thereof. In some examples, a system may contact or cause a companion application or backend system to contact a caregiver if an action to address the caution status is not taken in a threshold period of time. In some examples, a blinking indicator or status icon may indicate a different status from a non-blinking indicator or status indicator. For example, a blinking green light may indicate that all systems are functioning as expected.
Other notifications are also possible. For example, a system may notify a user via audio, graphics, text, or haptic feedback of one or more parameters or statuses of the system. In some examples, a most recent glucose level (such as within the last 5 minutes) may be displayed to a user, optionally in conjunction with a time the measurement was obtained. In some examples, an insulin remaining within one or more of the disease management systems may be displayed, such as a total insulin remaining across two interleaved disease management systems. In some examples an active insulin value may be displayed. In some examples, a sensor life remaining, such as some combination of battery life, CGM duration and insulin, may be displayed. In some examples, device warm up progress and/or stabilization may be displayed. In some examples, a history log may be displayed. In some examples, one or more graphs associated with system data may be displayed over a default or selected period of time. A default period of time can include 6 hours, 1 day, or other amount of time. In some examples, the system data can include glucose target range, observed and predicted glucose with confidence interval (CI if cloud connectivity is available) and event (such as insulin, exercise, food, and other events) markers visible and interactable by the user. In some examples, the system may display an insulin graph, an insulin basal and/or bolus graph that may include suspend descriptions, a meal digestion graph, the like or a combination thereof.
In some examples, a system may notify a user of glucose related states of a user, such as hypoglycemic state, near hypoglycemic state (such as within 30 minutes or other period of time), hyperglycemic state, near hyperglycemic state (such as within 30 minutes or other period of time), glucose trending high out of target range, or glucose trending low out of target range, or the like. In some examples, a system may notify a user of insulin status, such as a warning associated with bolus administration, a changing basal notification, an adverse event insulin detected, or the like. In some examples, a system may notify a user when a periodic report, such as described above, is available for review.
In some examples, a treatment system may be configured to determine a hypoglycemic event or a near hypoglycemic event based on collected user data. A hypoglycemic event can be relative to a recent eating or exercise time, time of day, or other values. Symptoms of hypoglycemia can include, but are not limited to clumsiness, trouble talking, confusion, loss of consciousness, seizures, and death. In some examples, symptoms can include hunger, sweating, shakiness, and/or weakness. Impaired awareness of hypoglycemia (IAH) may afflict up to 28 percent of type one diabetics. Thus, tools for assessing IAH can be useful in helping users avoid dangerous hypoglycemic events. Advantageously, a treatment system may identify a hypoglycemic event or improve user awareness of hypoglycemia through the tracking and analysis of biometric parameters, such as heart rate variability (HRV), ECG (such as QT intervals from ECG), heart rate, BMI (which can be a high risk factor for insulin resistance and diabetes), race (which can be a factor in incidence and mortality of diabetes), body or skin temperature and sweat (body temperature may lower when in a hypoglycemic state and sweat may have an inverse relationship with hypoglycemia), seasonal variations in parameters, years diagnosed, age (which can be more important to understand years diagnosed), type 1 or type 2 diabetes type, other parameters, or a combination thereof.
QT intervals from ECG may be used as a marker in type 1 and type 2 diabetics. For example, many diabetics have a prolonged QT interval (for example, greater than 440 ms). Diabetics with a prolonged QT interval may be associated with an increased mortality compared with diabetics with a normal QT normal. Thus, tracking a QT interval can be used to identify a user's increased risk of mortality.
In some examples, a treatment system may provide recommendations, notifications, or reports based on detection of hypoglycemic events or near hypoglycemic events. In some examples, a treatment system may classify one or more users as having Impaired awareness of hypoglycemia or not. The treatment system may provide short and/or long term predictions based on detected parameters for both non-IAH and IAH classified users. For example, if a non-IAH type 1 diabetic user has a heart rate and QT interval increase followed 5-10 minutes later by a wrist or abdomen sweat increase, they may be approaching a hypoglycemic event in 5 to 10 minutes. A treatment system may then notify the patient or user of a predicted hypoglycemic event. In another example, if a pattern of declining heart rate pattern with 10 beats per minute fluctuation 70 minutes prior and optionally a slight increase in sweat 70 minutes prior, the system may predict a longer term risk of predicted hypoglycemic event and notify the patient or user of a predicted hypoglycemic event. A notification may include an audible alarm, graphical alarm, or haptic feedback, such as buzzing on a user's mobile device to capture to attention of the user. In some examples, a treatment system may communicate with a wearable device to notify a user, such as a smart watch or other wearable device that may audibly or vibrationally alert the user to a predicted hypoglycemic event. In some examples, a treatment system may provide one or more notifications based on an identified pattern or risk of hypoglycemia, hyperglycemia, glucose variability, and/or testing deficiencies.
In some examples, a companion application may be configured to provide periodic reports on one or more parameters, such as but not limited to time in proactive closed loop, time in reactive closed loop, time in manual mode, time in range for different modes, estimated average glucose, calculated HbA1C, exercise impact on glucose, sleep impact on glucose, and food impact on glucose. Reports may be daily, weekly, monthly, or cover another time frame. In some examples, a companion application may be configured to provide a current on instant report on one or more parameters, such as estimated average glucose, exercise impact on glucose, sleep impact on glucose, and food impact on glucose.
Advantageously, periodic reports described herein may help a user better track and/or manage their disease. In contrast, while current systems for Continuous Glucose Monitoring provide a life changing awareness of near real time glucose levels and trends, these systems often fall short of offering a user with feedback as to the impact or damage caused by severe hypoglycemic or hyperglycemic events, lifestyle, food, time of day or cycles at which their body processes glucose and insulin differently or if any patterns in sleep, carbs, diurnal or nocturnal activities affect their glucose levels. For example, a type 1 diabetic with a good HbA1C can still suffer high mortality from previous or future glycemic related events1. Advantageously, the periodic reports described herein may help address this issue by facilitating better data tracking and helping a user make sense of the subtleties of what effects their body's glycemic swings by providing a summary of findings and facilitating or providing recommended opportunities to improve disease management.
In some examples, a companion application may include a graphical user interface with a dashboard component. The dashboard component may include a graphical or textual overview or icon of the user's status, such as an index percentage number and/or graphical representation of user data. The overview may be interactive. For example, in the case of the companion application running on a touch screen device, the overview that can be tapped or otherwise selected. The selection may be to open an aspect of a graphical user interface of the companion application that is configured to display a periodic report.
In some examples, a periodic report may include a glucose impact report. The glucose impact report may include one or more metrics based on some combination of calculations that may be beneficial to a user in understanding lifetime management of diabetes, a Personal Glycemic State Index (PGS) or other index which may be based on some combination of time, frequency, or severity out of and in range, glycemic variability, and mean glucose, other tracked details including, but not limited to: weight to height ratio, waist to height ratio, pulse rate, pulse rate variability, sweat (measured, for example, via skin conductance), ECG QR interval, active minutes or steps, exercise, food and/or carbohydrates, medications, sleep, weather, temperature, and humidity (determined, for example, from GPS location).
In some examples, a metric can include a combination of factors that work together to provide a better assessment of an individual's state of glycemic management. The individual could work to maintain the index above a specific level but can also drill down into details, such as understanding how specific amounts of sleep affect them (such as 6 hours compared to 8 hours of sleep) and understanding how and if certain locations or times of day can correlate with different glucose patterns. In addition or in the alternative to these metrics and/or parameters, a report may delineate how many hypoglycemic events may have been felt by a user if they are becoming hypoglycemic unaware, how humidity and temperature from weather may impact their biometric parameters, such as glucose values, and how activity may contribute or prevent severe hypoglycemic events.
In some examples, a report may be determined by a companion application. In some examples, a report may be determined by a backend system. In some examples, a report may be determined based on historical user data. In some examples, a report may be determined based on population data, such as de-identified user data, by machine learning. In some examples, a machine learning algorithm may analyze population data in order to find trends across populations of users and make predictions or recommend self-corrective actions to improve a user's report values. Self-corrective actions may include, for example, self-adjusting insulin levels and timing, food changes, sleep or changes, or other lifestyle changes.
Current classes of closed loop control often fall in two categories: reactive closed loop and hybrid closed loop. Reactive closed loop can be defined as a control system that only changes its stimuli based on observation of analytes. A hybrid closed loop system utilizes user supplied information such as notification of meal or insulin information. To date the best models have utilized hybrid closed loop models. However, these models generally are still highly insufficient to reach normalcy. Closed loop control remains a challenging problem involving the integration of algorithms, optimization, embedded systems, cloud support, mobile apps, 3rd party hardware, and potentially complex user interactions. Systems and methods described herein may uniquely addresses the above overlapping issues with a first goal of being as safe as possible and a second goal of being as simple as possible.
In terms of a control aspect of a closed loop system, the tools available to a medical device can be disadvantaged to the natural control algorithm that exists in a normal (non-diabetic) body. In a natural control system, glucose may is nearly directly measured by the pancreas, liver, and other cells throughout the body. In a medical device control system glucose may be measured less directly, such as interstitially and with delay (for example, approximately a 15 minute delay). In the natural control system, insulin is dispensed by the pancreas almost directly into blood. In a medical device control system, insulin may be dispensed interstitially and with delay (for example, approximately a 15 minute delay). However, a good model of the body may enable forward accounting of these delays.
In some examples, a treatment system may utilize a multi-tiered algorithm to facilitate improved glycemic control for a user given different levels of connectivity of system devices to a network and/or each other. In some examples, a multi-tiered algorithm may include 3 tiers. In a first tier, a user may have connectivity between a disease management system, such as an insulin administration and/or CGM device, a mobile device, such as a smart mobile device, and a cloud or network. In a second tier, a user may have connectivity between a disease management system, such as an insulin administration and/or CGM device, and a mobile device, such as a smart mobile device, but may not have connectivity to a cloud or network. In a third tier, a user may lack connectivity between a disease management system, such as an insulin administration and/or CGM device, a mobile device, such as a smart mobile device, and a cloud or network. Advantageously, a multi-tiered system may reduce computational strain on local devices, such as a mobile device or disease management system by performing more complex processing to an external backend system so that local devices may devote their processing power to more basic processes.
Connectivity between one or more devices and/or the cloud or network may be through any number of wireless or wired connections. For example, a disease management system may wirelessly connect to a mobile device through an NFC connection or Bluetooth. In another example, a mobile device may have connectivity to the cloud or a network via Wi-Fi or a cellular network. It should be noted that a mobile device may not be a permanent communication line and may not be required by the system to keep a user in tight glycemic control.
In the first tier, a user may have connectivity between the disease management system, mobile device, and cloud. Since there is virtually unlimited processing and memory in the cloud, more computationally expensive algorithms, such as MPC (Model Predictive Control), can be performed in the cloud or a backend system connected to a network that the mobile device or disease management system is also connected to. In some examples, an MPC can include a control algorithm configured to utilize a physiological model of the user to predict future glucose values and determine the optimal sequence of stimuli necessary to achieve a desired outcome, such as a desired glucose value. A cloud algorithm may take past and present observations to generate a model that simulates glucose and insulin transfer between different organs or compartments of the body. Thus, the cloud algorithm can foresee the effect of meal intake and insulin injection on the plasma and interstitial fluid glucose at future points in time. In this way, the algorithm can recommend a set of insulin doses in the present and future to compensate for glucose excursions due to meals and other effects. A backend system running the cloud algorithm may then communicate those recommendations to the mobile device through the network and the mobile device may then communicate with the disease management system based on the recommendations to facilitate insulin treatment and/or analyte measurements. In some examples, the backend system may directly communicate recommendations with the disease management system.
In the second tier, a user may have connectivity between the disease management system, and the mobile device, but may have no or limited connectivity with the cloud and/or network. In some examples, a mobile device may not be configured to run computationally expensive or a proprietary algorithm code because the code running on the mobile device cannot be ensured to be secure. In a second tier, an algorithm may still allow a user to interact with a disease management system with a mobile device by, for example, allowing user input to specify when a meal will occur with the number of carbohydrates or other nutritional information. Thus, an algorithm may correctly bolus an amount of insulin to counteract the effect of carbohydrates and/or keep the user in a target range of blood glucose. In some examples, the algorithm may allow a user to set user may also set temporary basal effects in anticipation of future exercise, sleep, stress, caffeine, etc., which will affect the user's insulin sensitivity and requirements.
In the third tier, a user may have no or limited connectivity between a disease management system and a mobile device and/or a network or cloud. In the third tier, an algorithm may deliver insulin reactively to recent glucose measurements to keep the user in the target range. In some examples, a third tier algorithm may also supply a prediction and planned stimuli of how a user may respond given only first tier or second tier algorithmic control.
It should be understood that a user may not be continuously in a single tier (such as a first tier, a second tier, or a third tier). For example, as connectivity changes, the algorithm chosen to dose insulin safely for that time period may dynamically change. As an example, a user may have just received a 30 minute time prediction from the third tier algorithm. This prediction and planned stimuli looking forward in time may be saved for access by the disease management system, such as in embedded software of the device. At a next time step, connectivity may cease to both the cloud and the user's mobile device. The disease management system may choose to hybridize its first tier basal closed loop algorithm with the high confidence 30 minute extrapolation of the third tier algorithm over the next few measurements. This hybridized result would be valid so long as the device is not notified of any new environmental stimuli such as an insulin bolus or the disease management system continues to see the CGM outputs course be very similar to the third tier's 30 minute extrapolation. Should the device see a deviation from the third tier extrapolation it may resume entirely to first tier algorithmic control and comparisons to the prediction and planned stimuli therein. Should the device see a deviation from the first tier extrapolation it may suspend all insulin dosing and even raise an alarm.
As another example, a user may have just received the 30 minute time prediction from the third tier algorithm. This prediction and planned stimuli looking forward in time may be saved for access by the disease management system, such as in the embedded software of the device. At the next time step, connectivity may cease to the cloud. The disease management system may choose to hybridize its second tier hybrid closed loop algorithm with the high confidence 30 minute extrapolation of the third tier algorithm over the next few measurements. This hybridized result would be valid so long as the device is not notified of any new environmental stimuli such as an insulin bolus, food bolus, or the device continues to see the CGM outputs course be very similar to the third tiers 30 minute extrapolation. Should the device see a deviation from the third tier's extrapolation, it may resume to second tier algorithmic control and comparisons to the prediction and planned stimuli therein. Should the device see a deviation from the second tier extrapolation it may suspend all insulin dosing and even raise an alarm. Other hybridizations of the multi-tier algorithm process may also be possible.
In some examples, a treatment system may facilitate different access levels to user information and/or device control. For example, should any user have insufficient mental capacity or education where they could make life threatening choices, a need exists to utilize increasingly higher levels of user authority that have the final judgement on behavior available and that may limit system operations. In some examples, it may be preferable and/or highly dependent on the situation at hand whether the user should have access to features relevant to control of the closed loop system at subsystems, such as the three major subsystems of the one or more disease management systems, the user's mobile device, or the cloud.
An algorithm may be able to recognize patterns in individuals' physiology and reaction to stimuli as well as user behavior and insulin response to provide a better control algorithm. This may cover user observations (individual and population) (long-term) and model based (short-term). Time in range (TIR) may be greater than 70% and closed loop remains on without being forced into manual mode by a probe-off greater than 90% of the time while having a cloud connection. TIR may be greater than 60% and closed loop remains on without being forced into manual mode by a probe-off greater than 90% of the time while having only an app connection but no cloud connection. TIR may be greater than 50% and closed loop remains on without being forced into manual mode by a probe-off greater than 90% of the time while only using embedded device.
The algorithm may suspend insulin on low detected absolute or derivative CGM glucose or model prediction value configurable thresholds and may notify app. An algorithm may have a glucose set point or target range mode based on user context. These set points or target range modes made be temporary in nature and detected. There may exist at least one embedded closed loop control algorithm that can function independent of an application or cloud. There may exist at least one embedded closed loop control algorithm that may function independent of cloud but utilize the app for dosing verification and meal entry. There may exist an arbitrator algorithm that determines the best insulin dose based off of some combination of conditions or algorithms, such as embedded only, embedded and mobile device, embed and mobile device and cloud algorithms, meta information, and heuristic information of user.
In some examples, a TIR performance and user safety may be improved by cloud connection. An algorithm may configurably incorporate external insulin injections by, for example: syringe (muscle or ISF), patch, and inhaled from various vendors. A user's personal insulin sensitivity may be assessed after OGTT-like meals are consumed and logged. Records of the insulin type used may be retained for possible future calibrations with that insulin type.
In some examples, an algorithm may utilize EHR records to improve personalization around sparse variables of interest such as: HbA1C, fasting glucose test, existing disease progression, or other blood works considered gold standards. In some examples, an algorithm may utilize lipid information to make meal time corrections. In some examples, an algorithm may utilize lipid information to make meal time confidences. In some examples, an algorithm may dynamically re-estimate quantity of meal quantities based on CAM measurements. In some examples, an algorithm may use rate of appearance and food quantity to retrospectively modify a foods particle size in order to properly account for large CGM oscillations (30 minute time periods). In some examples, an algorithm may use fine sampling rates (1 minute measurements) to assess the personal delay time of users pyloris when CGM short oscillations occur (5 minute time frame) due to high nutrient levels. Additionally or alternatively, an algorithm may assess the trigger threshold for opening and closing the pyloris. In some examples, user body temperature may be measured to provide alarms related to whether the user is having a fever or not. In some examples, an algorithm may determine body orientation of each device, such as if a user is on back, belly, or butt and allowed a user-engaged calibration. In some examples, an algorithm may use users described body placement to historically and personally analyze insulin absorptivity rate. In some examples an algorithm may have an SIQ system that takes into account electrical instability, and/or known sensor-body responses. In some examples, an algorithm in cloud may monitor its confidence that it is likely in full-use (User is supplying all required information such as 3 meals, insulin injections, and activity). In some examples, an algorithm may monitor that CGM or CAM output(s) stay contained in at least one state of a glucose prediction model, such as a glucose-insulin-lipid meal model (GLIMM). If a user deviates from a predication or target, an algorithm may communicate a notification to an application. An algorithm may monitor internal model (such as MPC) states with simple thresholds to prevent erroneous dosing. An algorithm may monitor outbound insulin dosing with simple rules to act as a sanity check. Insulin on board may be monitored with simple rules to prevent overdosing from the app. An algorithm may monitor personalized insulin dosing based on heuristic dosing of user and compare it with current dosing to prevent overdosing from the app or cloud. An algorithm may determine physical activity and/or physical activity confidence value(s) via one or more sensors, such as an accelerometer, gyroscope, pulse rate, spo2, or a GPS. In some examples, an algorithm may determine time of day and other parameters associated with whole body model states.
An algorithm may alarm on oxygen lows that may indicate hypoglycemic or compression related low events or independently bad events such as opioid overdoes with the SpO2 and/or use an SpO2 monitor to detect sleep apnea. An algorithm may monitor diffuse reflectance SpO2 to estimate insulin metabolism at one or more measurement sites to assess oxygen consumption by a sensor, such as a GOx sensor.
An algorithm and/or disease management system(s) may include one or more safe mode configurations. In some examples, an algorithm may maintain a historically safe personalized user configuration.
An algorithm may build cloud-based confidence in expected patterns for insulin bolus, based on one or more user parameters, such as exercise behavior, food bolus, mobile device GPS location, time of day, sleep status, pulse rate, or SpO2.
An algorithm may predict at what time an insulin reservoir will approach zero. A threshold may be used to determine the time at which a new device should to be put on the body in order to ensure adequate insulin supply. This time, threshold, or alarm may be communicated to a companion application.
An algorithm may predict the effectiveness of insulin based on temperatures and time and dose accordingly for primary and secondary devices insulin reservoirs. This prediction may be separate and/or operate in parallel or in conjunction with a control algorithm to correct an insulin dose.
An algorithm may detect when user is moving towards hypo or hyperglycemia and may test into the future, such as a few hours from a current time.
Amperometric CGMs can measure electrical current produced by enzymatic oxidation of glucose at a constant electrode potential and translate the measured current value into a glucose concentration using a predefined value for sensitivity. Drift in this sensitivity can present a major challenge in long-term accuracy of CGMs. This drift could have multiple causes. For example, the drift can be caused by a change in the polymer films on the electrode, a change in the electrode surface properties that affect the charge transfer kinetics at the electrode surface, and/or a change in the enzyme (e.g., GOx) activity. Since the only output in amperometry is a single current value at each time point, amperometry alone is unable to detect drift in sensitivity and its possible causes.
A possible method for detecting sensitivity drifts in a CGM sensor is electrochemical impedance spectroscopy (EIS). Unlike amperometry, EIS can simultaneously reveal multiple parameters that represent different physical and chemical properties of the sensor. By correlating the value of each parameter found using EIS with the amperometric sensitivity of the CGM, periodic EIS scans can help diagnose and correct for changes in sensitivity in order to improve the long-term accuracy of the CGM. For example, slow and long-term detachment of a polymer film from the sensor results in certain changes in a specific parameter output of EIS. If the correlation between that specific parameter output and amperometric sensitivity is known, the sensitivity can be adjusted accordingly during the operation of the sensor by periodic EIS scanning.
When testing for major issues such as improper initial insertion that represent a binary test (e.g., proper or improper insertion), impedance measurements at a single or a few frequencies may be enough to diagnose the problem. In contrast, in EIS scans an entire range of frequencies may need to be scanned to give quantitative estimates of specific physical and chemical parameters of the sensor. Therefore, the range and number of frequencies used for electrochemical impedance measurements can largely vary based on the desired test.
In EIS, a sinewave AC potential is applied on the working electrode of an electrochemical system, the AC current produced as a result of this potential is measured, and an impedance value is calculated. This procedure is then performed at a range of frequencies to give impedance as a function of frequency. Multiple electrochemical processes contribute to this impedance. For example, as shown in
Z=R−j/ωC
For the parallel RC circuit, the relationship can be represented by the following equation:
To understand the relationship between EIS circuit elements and the amperometric sensitivity of a CGM, a number of sensors can be studied in vitro by performing both periodic EIS and sensitivity measurements using known glucose concentrations. The correlation between EIS circuit element values and CGM sensitivity can then be extracted from this dataset. This correlation can then be incorporated into the CGM online during operation. During in vivo use, the CGM can automatically perform EIS, extract the circuit elements, find the expected drift in sensitivity using the pre-defined correlation, and adjust the sensitivity to improve the sensor accuracy.
The periodic EIS can be performed at various DC potentials. Typically, EIS is performed at the open circuit potential (i.e., while no DC potential is applied to the electrode). However, it is possible to perform EIS even at a non-zero applied DC potential. For example, one possibility is to perform EIS at the same DC potential as the amperometry potential (e.g. +0.6 V). In that case, the amperometry does not need to be stopped during the EIS scan because the same constant DC potential is applied and the DC current is still measured. This method has the advantage that the DC potential is not turned on and off, which avoids creating any transient currents due to potential being turned on/off. Another modification of the EIS technique involves performing EIS during a potential sweep (i.e., superimposing an AC potential on a slowly and linearly varying potential (
Other than AC voltammetry, there are multiple modifications of the EIS method that can be used for self-calibration. A first example involved modifying the equivalent circuit model used to extract circuit elements. Many different models exist, and depending on the sensor structure, a unique model may result in better correlations between extracted circuit elements and sensitivity. A second example involves modifying the range of frequencies scanned in EIS. A third example involves modifying the number of points scanned in an EIS scan. A fourth example involved adjusting the timing and interval of the periodic EIS scans based on the need for self-calibration of the sensor.
Electrochemical impedance measurements can indicate potential issues in the sensor. Most importantly, if a sensor does not have proper contact with liquid (e.g., interstitial fluid) upon the initial insertion, the impedance will be vastly different than if the sensor is inserted properly and is in contact with bodily fluids. Therefore, impedance measurements in general, and EIS in particular, can allow detection of erroneous insertion of the CGM sensor.
Electrochemical impedance can be measured at a single or a few different frequencies shortly after the insertion of the sensor in the body. The impedance value can be compared with a range of pre-defined acceptable impedance values. If the measured impedance lies within this range, the sensor is considered “properly inserted”. If not, the device can alert the user that the sensor is not inserted properly and corrective action must be taken. The measured impedance value can also inform about the initiation state of the sensor and whether the sensor is hydrated enough to begin making glucose measurements.
A similar method can be used to detect any significant damage to sensor, loss of contact with bodily fluids, or other major issues. Single-frequency impedance can be measured periodically to diagnose these major problems with a binary answer (e.g., the sensor is working or the sensor has undergone significant change and needs to be replaced).
There are multiple modifications of the impedance-based diagnostic method that can be implemented. A first example is modifying the frequency at which impedance is measured. A second example is measuring impedance at multiple specific frequencies and using a combination of these values to make a decision about whether the sensor is damaged or improperly inserted. A third example is adjusting the timing and interval of the periodic impedance measurements based on the need for self-diagnosis in the sensor.
Insulin infusion may fail for many reasons including catheter failure, pain at the infusion site, pull out, adhesive failure, and infection. For example, a catheter may fail due to kinking of the catheter and/or a patient's immune response. Additionally, when kinking occurs an unexpected and unquantified additional dose of insulin can occur. Thus, an impedance measurement with a measuring element inside a cannula can be used to address insulin infusion failure due to a catheter failure (for example, due to kinking and the patient's immune response). Moreover, by using the catheter as described herein, the system can estimate an amount of the unexpected additional dose of insulin to be sent back to a close loop algorithm to fine tune control. The use of an impedance measurement can also be used when the cannula is straight to quantify the amount of aggregated insulin on the helical spring element and/or the amount of encapsulation outside of the cannula.
The cannulas 3500, 3520, 3540, 3560 can be configured to detect kinking in the cannula 3500, 3520, 3540, 3560. For example, the double helix cannula 3520 and the c-straight helix cannula 3560 can be configured to detect kinking by detecting a change in resistance. These configurations 3520, 3560 can include first and second wires. The first wire can be configured to separate resistance changes in series. The second wire may or may not be configured to have resistance in series. When the cannula 3520, 3560 is straight the circuit can be modeled by Ohms law, as represented by the following equation:
RT=ΣRj
If a kink occurs in the cannula 3520, 3560, then the circuit can become a parallel measurement, as represented by the following equation:
Therefore, a change in resistance can be expected when a kink occurs in the cannula 3520, 3560. If there multiple kinks in the cannula 3520, 3560, then more parallel elements can occur, as represented by the following equation:
In order to identify the location of the kink, the resistance must be varied along at least one of the first and second wires. If the resistance remains the same, it will be unclear whether the kink is in the top half or the bottom half of the cannula 3520, 3560. The resistance can be continuously or discretely varied down the first wire and/or the second wire. Thus, the parallel resistance can be unique as the kinking occurs differently at two different symmetric locations, as represented by the following equations:
Where RT1 is equal to RT2 (i.e., RT1=RT2) when Ri, Rj, and Rk are equal (i.e., Ri=Rj=Rk). When Ri<Rj<Rk, then RT2<RT1. When there are multiple kinks, more resistances in parallel can be added, as shown in the following equation:
Based on the total measured resistance, the location(s) of the kink(s) in the cannula 3520, 3560 can have a regressable or classifiable variable. These cannulas 3520, 3560 can also be configured to conduct impedance analysis, as the cannulas 3520, 3560 can naturally have some impedance and capacitance, which can improve the ability to determine the location(s) of the kink(s) in the cannula 3520, 3560.
The cannulas 3500, 3520, 3540, 3560 can be configured to estimate of an amount of the unexpected additional dose of a drug (e.g., insulin) that can occur with kinking in the cannula 3500, 3520, 3540, 3560. For example, the location of the kinking can be used in conjunction with the location of flow holes in the cannula 3500, 3520, 3540, 3560 and respective size of the flow holes to estimate the amount of the unexpected additional dose of insulin. With a known kink location, a diameter of the cannula 3500, 3520, 3540, 3560, and a length of the cannula 3500, 3520, 3540, 3560, the displaced insulin upon bending or kinking can be estimated. This estimation can be based on an empirical estimation, an analytical estimation via Bernoulli equations and/or simple kinetic diffusion approximations at steady state, or by a priori fluid flow models (e.g., Navier-Stokes simulations) stored and utilized upon various kink locations observations.
The viscosity of insulin (e.g., U100 vs U200) and ISF viscosity can be utilized to improve the estimation of the displaced insulin. For example, excipients for a medication (e.g., insulin or glucagon) may be advantageously chosen such that the ionic character of the solvent or solutes can allow a larger dynamic range of signals to be observed. The larger dynamic range of signals can occur due to diffusion changing the concentrations of the ionic character of the solvent or solutes in or around the cannula 3500, 3520, 3540, 3560. Moreover, the changing concentrations of the ionic character of the solvent or solutes can cause a change in impedance in or around the cannula 3500, 3520, 3540, 3560. Additionally, diffusion can be determined over time via a model to discern when insulin may have been fractionally displaced via diffusion through the infusion holes even if a bend or kink occurs. Under this circumstance, it will be known that despite the kink no medication volume was displaced, only diffused ISF or a fractional amount of ISF and medication.
Impedance characteristics can be used to determine a diffusion coefficient of the filtration effect of the helical spring on insulin over the use life of the cannula 3500, 3520, 3540, 3560. Additionally, impedance characteristics can be used to determine the clogging or encapsulation state of the cannula 3500, 3520, 3540, 3560. These measurements can be taken when the cannula 3500, 3520, 3540, 3560 is not kinked or bent. Additionally, all of these measurements together can be used to estimate how much longer the cannula 3500, 3520, 3540, 3560 can remain in the body before there is complete biofouling or encapsulation of the cannula 3500, 3520, 3540, 3560.
In some configurations, any of the resistive elements of the cannulas 3500, 3520, 3540, 3560 discussed herein may comprise one or more temperature sensitive elements, which can be naturally resistive. The temperature sensitive elements can measure a temperature under the patient's skin, which can be used, for example, in a closed loop system. In some configurations, a plurality of temperature sensitive elements can be used to predict the patient's core body temperature. For example, the plurality of temperature sensitive elements can generate a temperature gradient of the location of the cannula 3500, 3520, 3540, 3560 in use (e.g., under the patient's skin).
Haptic motion can also be induced in a cannula or outside of a cannula. The choice of haptic frequency and power can be chosen such that a resonant force can appear near infusion holes to maximize the dislodging affect. Other modes of haptic motion may be utilized that optimally dislodge blockage or kinking in the cannula or surrounding tissue space with a travelling wave. This wave can move debris away from infusing holes. Multiple failure modes can potentially be addressed by such motion, such as failure due to aggregated insulin, which can be dislodged to allow clearance of an infusion hole, failure due to fibrin encapsulated sensors, which can be shaken free allowing a pathway out of the to allow clearance of an infusion hole, and/or failure due to kinks in the infusion cannula, which can be straightened by haptic motion if lodged in a compromising fashion.
Disclosed herein are additional examples of a disease management system. Any of the examples disclosed herein may be combined in whole or in part.
Example 1: A disease management system comprising:
Example 2: The disease management system of Claim 1, wherein the settling period comprises a warmup period or a stabilization period.
Example 3: The disease management system of Claim 1, wherein at least one of the first disease management system or the second disease management system is configured to calculate a proper dosage of insulin based on patient glucose information from at least one of the first glucose sensor or the second glucose sensor.
Example 4: The disease management system of Claim 3, wherein calculating the proper dosage of insulin is further based on patient entered data.
Example 5: The disease management system of Claim 4, wherein the patient entered data comprises age, height, weight, or weight.
Example 6: The disease management system of Claim 3, wherein calculating the proper dosage of insulin is further based on a customized glucose metabolization rating for the patient.
Example 7: The disease management system of Claim 6, wherein the customized glucose metabolization rating is based on the patient's weight, age, digestion rate, or insulin sensitivity.
Example 8: The disease management system of Claim 1, wherein at least one of the first disease management system or the second disease management system is configured to communicate with a smart device or a smartwatch.
Example 9: The disease management system of Claim 8, wherein the first disease management system or the second disease management system is configured to communicate with the smartphone or the smartwatch through Bluetooth or RF signal.
Example 10: The disease management system of Claim 8, wherein the at least one of the first disease management system or the second disease management system is configured to communicate with the smart device and wherein the smart device is configured to communicate with the smartwatch.
Example 11: The disease management system of Claim 1, wherein the first disease management system further comprises a first insulin storage container fluidly connected to the first insulin pump.
Example 12: The disease management system of Claim 11, wherein the first insulin pump is fluidly connected to a needle which is capable of being inserted into a cannula that is implanted into a patient.
Example 13: The disease management system of Claim 11, wherein the first insulin storage container comprises a flexible insulin pouch and the first disease management system further comprises a spring configured to apply pressure to the flexible insulin pouch.
Example 14: The disease management system of Claim 13, wherein the flexible insulin pouch is prefilled with insulin.
Example 15: The disease management system of Claim 13, wherein the first insulin pump comprises a valve that is controlled in order administer a specific dosage of insulin to the patient.
Example 16: The disease management system of Claim 15, wherein the valve comprises 3 or more piezoelectric crystal valves.
Example 17: The disease management system of Claim 15, wherein the valve comprises 3 or more voice coil valves.
Example 18: The disease management system of Claim 15, wherein the valve comprises 3 or more piezoelectric stack valves.
Example 19: The disease management system of Claim 15, wherein the first insulin pump further comprises a filter connected between the valve and the needle.
Example 20: The disease management system of Claim 13, wherein the valve comprises a beginning valve, an end valve, and one or more intermediate valves located between the beginning valve and the end valve, the intermediate valves individually controllable in order to administer the specific dosage of insulin.
Example 21: The disease management system of Claim 11, wherein the first insulin pump comprises a peristaltic pump.
Example 22: The disease management system of Claim 21, wherein the peristaltic pump comprises:
Example 23: The disease management system of Claim 22, wherein the peristaltic pump is a ratcheting peristaltic pump comprising a ratcheting driving mechanism in physical contact with the circular gear, wherein the ratcheting driving mechanism is capable of ratcheting teeth within the circular gear at one tooth at a time.
Example 24: The disease management system of Claim 21, wherein the peristaltic pump comprises:
Example 25: The disease management system of Claim 24, wherein the peristaltic pump is a ratcheting peristaltic pump comprising a ratcheting driving mechanism in physical contact with the circular gear, wherein the ratcheting driving mechanism is capable of ratcheting teeth within the circular gear at one tooth at a time.
Example 26: The disease management system of Claim 1, wherein the first disease management system comprises:
Example 27: The disease management system of Claim 26, wherein the case includes one or more needle insertion holes capable of having a needle inserted.
Example 28: The disease management system of Claim 26, wherein the first disease management system is mounted to a patient through an adhesive which connects to the case.
Example 29: The disease management system of Claim 26, wherein the first disease management system further comprises at least one of a light source, a photodiode, a vibration device, a tissue impedance measurement device, an insulin cannula impedance measurement device, an accelerometer, or a gyroscope.
Example 30: The disease management system of Claim 26, wherein the first disease management system further comprises one or more flexion points which allows the first disease management system to flex.
Example 31: The disease management system of Claim 30, wherein the one or more flexion points comprises two flexion points.
Example 32: The disease management system of Claim 1, wherein the first disease management system comprises:
Example 33: The disease management system of Claim 32, wherein at least one of the first case or the second case further houses at least one of a light source, a photodiode, a vibration device, an accelerometer, or a gyroscope.
Example 34: A peristaltic pump comprising:
Example 35: A peristaltic pump comprising:
Example 36: A ratcheting peristaltic pump comprising:
Example 37: The ratcheting peristaltic pump of Claim 36, wherein the ratcheting driving mechanism comprises a solenoid, muscle wire, a ratchet motor, or a direct current motor.
Example 38: A method of priming a peristaltic pump, the method comprising:
Example 39: A primed peristaltic pump comprising:
Example 40: A method of using a primed peristaltic pump comprising: providing the primed peristaltic pump of Claim 34;
Example 41: A method of operating redundant glucose sensors, the method comprising:
Example 42: The method of Claim 41, wherein the first glucose sensor or the second glucose sensor and the insulin pump are housed in one unit.
Example 43: The method of Claim 41, wherein the insulin pump and at least one of the first glucose sensor or second glucose sensor operating during a warmup period, a stabilization period, or an end of life period are housed in one unit.
Example 44: The method of Claim 43, wherein the first glucose sensor or second glucose sensor not operating during a warmup period, a stabilization period, or an end of life period and another insulin pump are housed in another unit.
Example 45: The method of Claim 44, further comprising operating the another insulin pump based on the measurements of the first glucose sensor or second glucose sensor not operating during a warmup period when the insulin pump is not operating.
Example 46: The method of Claim 45, wherein the one unit comprises a first insulin source storing insulin and wherein the another unit comprises a second insulin source storing insulin, and wherein the insulin pump and another insulin pump deliver insulin from the first insulin source and the second insulin source such that the insulin in the first insulin source and the second insulin source is emptied before the insulin in the first insulin source and the second insulin source expires.
Example 47: The method of Claim 46, further comprising notifying the patient when it is time to replace the one unit or the another unit.
Example 48: The method of Claim 47, wherein notifying the patient comprises sending a message through the patient's smart device or enabling the one unit or the another unit to vibrate.
Example 49: The method of Claim 41, wherein the first glucose sensor, the second glucose sensor, and the insulin pump are all housed in separate units.
Example 50: The method of Claim 41, wherein the first glucose sensor or the second glucose sensor and the insulin pump are housed in one unit.
Example 51: The method of Claim 41, wherein the first glucose sensor or the second glucose sensor and another insulin pump are housed in one unit, and wherein the insulin pump is housed in another system.
Example 52: The method of Claim 41, further comprising replacing the first glucose sensor or the second glucose sensor with a third glucose sensor when the not replaced first glucose sensor or second glucose sensor is not operating in a warmup period, a stabilization period, or an end of life period, wherein the not replaced first glucose sensor or second glucose sensor will not be operating in an end of life period when the third glucose sensor is running in a warmup period or a stabilization period.
Example 53: A method of using an applicator for applying a disease management system, the method comprising:
Example 54: The method of Claim 53, wherein the needles are housed within guidance tubes before launching the insulin dosage unit onto the patient.
Example 55: The method of Claim 53, wherein, when in the packaging, the disease management system is preloaded with lancet backings, wherein when the needles are retracted, the needles retract into the lancet backings, and wherein ejecting the used needles comprises ejecting the used needles within the lancet backings.
Example 56: The method of Claim 55, further comprising removing the applicator after launching the disease management system onto the patient, wherein removing the applicator comprises leaving the applicator on the patient while removing the needles within the lancet backings.
Example 57: A disease management system comprising:
Example 58: The disease management system of Claim 57, further comprising a near field communication (NFC) device including a unique ID tag associated with the disease management system, wherein a smart device is capable of causing the NFC device to send the unique ID tag to the smart device which allows the smart device to identify the disease management unit and pair with the disease management system.
Example 59: The disease management system of Claim 58, wherein the NFC device is configured to communicate with the smart device to trigger the disease management system to manually administer a dosage of insulin to the patient.
Example 60: The disease management system of Claim 58, wherein the NFC device is configured to communicate with a wearable NFC device to trigger the disease management system to manually administer a dosage of insulin to the patient.
Example 61: The disease management system of Claim 60, wherein the wearable NFC device comprises a safety mechanism to prevent the wearable NFC device from triggering the disease management system from manually administering a dosage of insulin to the patient unless the safety mechanism is enabled.
Example 62: The disease management system of Claim 61, wherein the safety mechanism comprises a switch, toggle, button, or knob.
Example 63: The disease management system of Claim 60, wherein the wearable NFC device is mounted on a bracelet, watch, necklace, or belt.
Example 64: The disease management system of Claim 60, wherein the NFC device is configured to differentiate between different wearable NFC devices such that one of the wearable NFC devices communicates with the NFC device to trigger the disease management system to manually administer a different dosage of insulin to the patient than another of the wearable NFC devices.
Example 65: The disease management system of Claim 60, wherein the computing device is configured to block a manual administration of a dosage from the wearable NFC device at least during a portion of the time.
Example 66: The disease management system of Claim 57, wherein the case comprises a manual dosage mechanism which is capable of triggering the disease management system to manually administer a dosage of insulin to the patient.
Example 67: The disease management system of Claim 66, wherein the case is segmented such that the portion of the case with the manual dosage mechanism is removable and replaceable.
Example 68: The disease management system of Claim 57, wherein the computing device is configured to communicate with an additional manual dosage device which is configured to be physically connected with the case, the additional manual dosage device is configured to trigger the disease management system to manually administer a dosage of insulin to the patient.
Example 69: The disease management system of Claim 57, wherein the antenna embedded within the case or on the outside of the case.
Example 70: A disease management system comprising:
Example 71: The disease management system of Claim 70, wherein the second disease management system is configured to pair with the smart device.
Example 72: The disease management system of Claim 70, wherein the smart device comprises a smartphone or tablet.
Example 73: A flexible disease management system comprising:
Example 74: An applicator for a disease management system comprising:
Example 75: The applicator of Claim 74, wherein the one or more disease management systems comprises one or more glucose sensor units, one or more insulin pump systems, or one or more combined glucose sensor and insulin pump units.
Example 76: A method of distracting a patient during application of a disease management system, the method comprising:
Example 77: The method of Claim 76, wherein the distraction device comprises a smart device or another disease management system including a vibration device.
Example 78: The method of Claim 77, wherein the distraction device comprises the smart device which allows a patient to play a game, watch a movie, or read a story before and during application of the disease management system, and wherein the distracting event comprises the climax of the game, movie, or story.
Example 79: The method of Claim 77, wherein the distraction device comprises the another disease management system including the vibration device, and wherein the distracting event comprises vibration of the vibration device just before and during application of the disease management system.
Example 80: The method of Claim 76, further comprising operating a vibration device within the patient treatment unit after application of the disease management system to the patient.
Example 81: The method of Claim 76, wherein the disease management system comprises a indicator which indicates when a distracting event is occurring in order to indicate that the timing is optimal to apply the disease management system to the patient.
Example 82: The method of Claim 81, wherein the indicator comprises a light emitter or a vibrating module.
Example 83: A needle for implanting a glucose sensor or cannula comprising a top portion and a bottom portion, wherein the bottom portion is rigid at some times and flexible at some times.
Example 84: The needle of Claim 83, wherein the bottom portion comprises a material which is flexible when exposed to water and rigid when not exposed to water.
Example 85: The needle of Claim 84, wherein the bottom portion comprises hydrogel or collagen
Example 86: The needle of Claim 84, wherein the bottom portion comprises an inner layer and an outer layer, wherein the inner layer and outer layer are made out of different materials.
Example 87: The needle of Claim 86, wherein one of the inner layer or the outer layer comprises hydrogel or collagen and the other of the inner layer or the outer layer comprises metal or plastic.
Example 88: The needle of Claim 83, wherein the bottom portion is rigid when not exposed to ultra-violet light and flexible when exposed to ultra-violet light.
Example 89: The needle of Claim 83, wherein the bottom portion comprises a bioresorbable material.
Example 90: The needle of Claim 83, wherein the needle is a hollow needle.
Example 91: The needle of Claim 83, wherein the needle is a solid needle.
Example 92: A disease management system comprising:
Example 93: The disease management system of Claim 92 wherein the bottom portion comprises an adhesive layer.
Example 94: The disease management system of Claim 93, wherein the bottom portion comprises an adhesive layer locking mechanism configured to join the adhesive layer to at least a second portion of the bottom portion of the housing.
Example 95: The disease management system of Claim 92, wherein the bottom portion comprises a metal plate configured to provide support for components of the disease management system.
Example 96: The disease management system of Claim 92, wherein the at least one analyte sensor and a cannula of the medication administration system are offset from each other in relation to a center line of the glucose administration system.
Example 97: The disease management system of Claim 92, wherein the at least one analyte sensor comprises an invasive sensor applied using a needle configured to retract from the skin after application.
Example 98: The disease management system of Claim 92, wherein the medication administration system comprises a medication pouch, pump, and cannula configured to be administered to the patient using a needle configured to retract from the skin after application.
Example 99: The disease management system of Claim 98, wherein the pouch is prefilled with medication.
Example 100: The disease management system of Claim 99, wherein the medication is insulin.
Example 101: The disease management system of Claim 99, wherein the pouch is sealed with a stopper configured to accept a needle for access to the medication.
Example 102: The disease management system of Claim 92, wherein the medication administration system comprises a pressure relief valve configured to release pressure from a fluid line in the medication administration system in the event of excess pressure.
Example 103: The disease management system of Claim 102, wherein the event of excess pressure comprises collapse of at least a portion of the disease management system due to a crushing force.
Example 104: The disease management system of Claim 92 further comprising at least one non-invasive sensor.
Example 105: The disease management system of Claim 104, wherein the non-invasive sensor comprises a pulse rate sensor.
Example 106: The disease management system of Claim 104, wherein the non-invasive sensor comprises a temperature sensor.
Example 107: The disease management system of Claim 92 comprising a buzzer configured to output audible feedback to the patient associated with the disease management system.
Example 108: The disease management system of Claim 92, comprising a haptic motor configured to output haptic feedback associated with the disease management system.
Example 109: The disease management system of Claim 92, comprising at least one battery configured to power components of the disease management system for a prolonged period.
Example 110: The disease management system of Claim 109, wherein the prolonged period comprises greater than 3 days.
Example 111: The disease management system of Claim 111, wherein the prolonged period comprises 6 days.
Example 112: The disease management system of Claim 92, comprising at least one communication component.
Example 113: The disease management system of Claim 112, wherein the at least one communication component comprises a Bluetooth antenna.
Example 114: The disease management system of Claim 112, wherein the at least one communication component comprises an NFC antenna.
Example 115: The disease management system of Claim 112, wherein the disease management system is configured to communicate with a user device.
Example 116: The disease management system of Claim 115, wherein the disease management system is configured to receive bolus instructions for administration of medication to the patient through the at least one communication component.
Example 117: The disease management system of Claim 115, wherein the glucose administration system is configured to communicate one or more physiological parameters to the user device.
Example 118: The disease management system of Claim 115, wherein the glucose administration system is configured to update a status of the device based on a connection status with the user device.
Example 119: The disease management system of Claim 92, wherein a pump of the medication administration system comprises a peristaltic pump.
Example 120: The disease management system of Claim 92, wherein a pump of the medication administration system comprises a valve pump.
Example 121: The disease management system of Claim 92, wherein a pump of the medication administration system comprises a plunger pump.
Example 122: The disease management system of Claim 121, wherein the plunger pump comprises: at least one plunger and at least one actuation component configured to cause the at least one plunger to apply pressure to a tube of fluid containing medication so that medication is transferred from a medication reservoir to a cannula inserted into the patient.
Example 123: The disease management system of Claim 122, wherein the at least one actuation component comprises at least one solenoid and spring assembly.
Example 124: The disease management system of Claim 122, wherein the at least one actuation component comprises at least one muscle wire and spring assembly.
Example 125: The disease management system of Claim 124, wherein the at least one actuation component comprises a plurality of rollers configured to allow the muscle wire to move the plungers when activated.
Example 126: The disease management system of Claim 122, wherein the at least one actuation component comprises an actuator and gear configured to engage the at least one plunger.
Example 127: The disease management system of Claim 126, wherein the gear comprises a plurality of humps and wherein the at least one plunger comprises an engagement portion configured to move in response to the position of a hump.
Example 128: The disease management system of Claim 127, wherein a hump of the plurality of humps comprises a thirty degree slope.
Example 129: The disease management system of Claim 126, wherein the actuator comprises a solenoid actuator configured to move a cleat, wherein the cleat is configured to engage the gear.
Example 130: The disease management system of Claim 128, wherein the pump comprises a lock configured to prevent unintended rotation of the gear.
Example 131: The disease management system of Claim 122, wherein the at least one plunger comprises a flat portion configured to contact the tubing of the medication administration system.
Example 132: The disease management system of Claim 122, wherein the at least one plunger comprises a cylindrical portion configured to contact the tubing of the medication administration system.
Example 133: The disease management system of Claim 122, wherein the at least one actuation component comprises a gear and an engagement portion configured to engage one or more plungers to move in an approximately radial direction from the gear.
Example 134: The disease management system of Claim 133 wherein the one or more plungers are configured to apply pressure to tubing between the gear and the one or more plungers.
Example 135: The disease management system of Claim 92, wherein a pump of the medication administration system comprises a piston pump.
Example 136: The disease management system of Claim 135, wherein the piston pump comprises a piston driven by a muscle wire spring and standard spring.
Example 137: The disease management system of Claim 136 wherein the piston is configured to engage a valve assembly in fluid communication with a medication pouch and medication cannula configured to be inserted into the patient.
Example 138: The disease management system of Claim 137 wherein fluid is moved through the valve assembly to the medication cannula as a result of the piston engaging a valve in the valve assembly.
Example 139: The disease management system of Claim 92, wherein the medication administration system comprises an electroactive cannula.
Example 140: The disease management system of Claim 139, wherein the electroactive cannula comprises a helical spring in an inside portion of the cannula.
Example 141: The disease management system of Claim 140, wherein the helical spring is configured to trap medication aggregated in the cannula.
Example 142: The disease management system of Claim 139, wherein the electroactive cannula is configured to detect a change in fluid conductance.
Example 143: The disease management system of Claim 142 wherein the change in fluid conductance is a result of a kink in the cannula or expiring or expired medication.
Example 144: The disease management system of Claim 139, wherein measurements of the electroactive cannula are used to estimate lifetime remaining for the cannula.
Example 145: The disease management system of Claim 144, wherein a lifetime is associated with a usable life of the cannula before there is biofouling or encapsulation.
Example 146: The disease management system of Claim 92, wherein the medication administration system comprises a haptic motion mechanism to aid in dislodging blockages in a cannula of the medication administration system.
Conditional language used herein, such as, among others, “can,” “could,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain, certain features, elements and/or steps are optional. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required or that one or more implementations necessarily include logic for deciding, with or without other input or prompting, whether these features, elements and/or steps are included or are to be always performed. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list.
Conjunctive language such as the phrase “at least one of X, Y, and Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to convey that an item, term, etc. may be either X, Y, or Z. Thus, such conjunctive language is not generally intended to imply that certain implementations require the presence of at least one of X, at least one of Y, and at least one of Z.
Language of degree used herein, such as the terms “approximately,” “about,” “generally,” and “substantially” as used herein represent a value, amount, or characteristic close to the stated value, amount, or characteristic that still performs a desired function or achieves a desired result. For example, the terms “approximately”, “about”, “generally,” and “substantially” may refer to an amount that is within less than 10% of, within less than 5% of, within less than 1% of, within less than 0.1% of, and within less than 0.01% of the stated amount. As another example, in certain implementations, the terms “generally parallel” and “substantially parallel” refer to a value, amount, or characteristic that departs from exactly parallel by less than or equal to 15 degrees, 10 degrees, 5 degrees, 3 degrees, 1 degree, 0.1 degree, or otherwise.
Any methods disclosed herein need not be performed in the order recited. The methods disclosed herein include certain actions taken by a practitioner; however, they can also include any third-party instruction of those actions, either expressly or by implication.
The methods and tasks described herein may be performed and fully automated by a computer system. The computer system may, in some cases, include multiple distinct computers or computing devices (for example, physical servers, workstations, storage arrays, cloud computing resources, etc.) that communicate and interoperate over a network to perform the described functions. Each such computing device typically includes a processor (or multiple processors) that executes program instructions or modules stored in a memory or other non-transitory computer-readable storage medium or device (for example, solid state storage devices, disk drives, etc.). The various functions disclosed herein may be embodied in such program instructions, and/or may be implemented in application-specific circuitry (for example, ASICs or FPGAs) of the computer system. Where the computer system includes multiple computing devices, these devices may, but need not, be co-located. The results of the disclosed methods and tasks may be persistently stored by transforming physical storage devices, such as solid state memory chips and/or magnetic disks, into a different state. The computer system may be a cloud-based computing system whose processing resources are shared by multiple distinct business entities or other users.
Depending on the implementation, certain acts, events, or functions of any of the processes or algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (for example, not all described operations or events are necessary for the practice of the algorithm). Moreover, in certain implementations, operations or events can be performed concurrently, for example, through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially.
The various illustrative logical blocks, modules, routines, and algorithm steps described in connection with the disclosure herein can be implemented as electronic hardware (for example, ASICs or FPGA devices), computer software that runs on general purpose computer hardware, or combinations of both. Various illustrative components, blocks, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as specialized hardware versus software running on general-purpose hardware depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.
Moreover, the various illustrative logical blocks and modules described in connection with the disclosure herein can be implemented or performed by a machine, such as a general purpose processor device, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor device can be a microprocessor, but in the alternative, the processor device can be a controller, microcontroller, or state machine, combinations of the same, or the like. A processor device can include electrical circuitry configured to process computer-executable instructions. A processor device can include an FPGA or other programmable device that performs logic operations without processing computer-executable instructions. A processor device can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Although described herein primarily with respect to digital technology, a processor device may also include primarily analog components. For example, some or all of the rendering techniques described herein may be implemented in analog circuitry or mixed analog and digital circuitry. A computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.
The elements of a method, process, routine, or algorithm described in connection with the disclosure herein can be embodied directly in hardware, in a software module executed by a processor device, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of a non-transitory computer-readable storage medium. An exemplary storage medium can be coupled to the processor device such that the processor device can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor device. The processor device and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor device and the storage medium can reside as discrete components in a user terminal.
While the above detailed description has shown, described, and pointed out novel features, it can be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As can be recognized, certain portions of the description herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. The scope of certain implementations disclosed herein is indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
This application claims the benefit of priority under 35 U.S.C. § 119(e) to U.S. Provisional Application No. 62/968,107, filed on Jan. 30, 2020, entitled “CLOSED LOOP INSULIN DELIVERY SYSTEM,” U.S. Provisional Application No. 62/978,480, filed Feb. 19, 2020, entitled “REDUNDANT STAGGERED GLUCOSE SENSOR DISEASE MANAGEMENT SYSTEM,” U.S. Provisional Application No. 63/015,272, filed on Apr. 24, 2020, entitled “REDUNDANT STAGGERED GLUCOSE SENSOR DISEASE MANAGEMENT SYSTEM,” and U.S. Provisional Application No. 63/044,831, filed on Jun. 26, 2020, entitled “REDUNDANT STAGGERED GLUCOSE SENSOR DISEASE MANAGEMENT SYSTEM” the disclosures of each of which are hereby incorporated by reference herein in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4960128 | Gordon et al. | Oct 1990 | A |
| 4964408 | Hink et al. | Oct 1990 | A |
| 5319355 | Russek | Jun 1994 | A |
| 5337744 | Branigan | Aug 1994 | A |
| 5341805 | Stavridi et al. | Aug 1994 | A |
| D353195 | Savage et al. | Dec 1994 | S |
| D353196 | Savage et al. | Dec 1994 | S |
| 5377676 | Vari et al. | Jan 1995 | A |
| D359546 | Savage et al. | Jun 1995 | S |
| 5431170 | Mathews | Jul 1995 | A |
| 5436499 | Namavar et al. | Jul 1995 | A |
| D361840 | Savage et al. | Aug 1995 | S |
| D362063 | Savage et al. | Sep 1995 | S |
| D363120 | Savage et al. | Oct 1995 | S |
| 5456252 | Vari et al. | Oct 1995 | A |
| 5479934 | Imran | Jan 1996 | A |
| 5482036 | Diab et al. | Jan 1996 | A |
| 5494043 | O'Sullivan et al. | Feb 1996 | A |
| 5533511 | Kaspari et al. | Jul 1996 | A |
| 5561275 | Savage et al. | Oct 1996 | A |
| 5590649 | Caro et al. | Jan 1997 | A |
| 5602924 | Durand et al. | Feb 1997 | A |
| 5638816 | Kiani-Azarbayjany et al. | Jun 1997 | A |
| 5638818 | Diab et al. | Jun 1997 | A |
| 5645440 | Tobler et al. | Jul 1997 | A |
| 5671914 | Kalkhoran et al. | Sep 1997 | A |
| 5726440 | Kalkhoran et al. | Mar 1998 | A |
| D393830 | Tobler et al. | Apr 1998 | S |
| 5743262 | Lepper, Jr. et al. | Apr 1998 | A |
| 5747806 | Khalil et al. | May 1998 | A |
| 5750994 | Schlager | May 1998 | A |
| 5758644 | Diab et al. | Jun 1998 | A |
| 5760910 | Lepper, Jr. et al. | Jun 1998 | A |
| 5890929 | Mills et al. | Apr 1999 | A |
| 5911716 | Rake et al. | Jun 1999 | A |
| 5919134 | Diab | Jul 1999 | A |
| 5987343 | Kinast | Nov 1999 | A |
| 5997343 | Mills et al. | Dec 1999 | A |
| 6002952 | Diab et al. | Dec 1999 | A |
| 6010937 | Karam et al. | Jan 2000 | A |
| 6027452 | Flaherty et al. | Feb 2000 | A |
| 6040578 | Malin et al. | Mar 2000 | A |
| 6066204 | Haven | May 2000 | A |
| 6115673 | Malin et al. | Sep 2000 | A |
| 6124597 | Shehada et al. | Sep 2000 | A |
| 6128521 | Marro et al. | Oct 2000 | A |
| 6129675 | Jay | Oct 2000 | A |
| 6144868 | Parker | Nov 2000 | A |
| 6152754 | Gerhardt et al. | Nov 2000 | A |
| 6184521 | Coffin, IV et al. | Feb 2001 | B1 |
| 6232609 | Snyder et al. | May 2001 | B1 |
| 6241683 | Macklem et al. | Jun 2001 | B1 |
| 6253097 | Aronow et al. | Jun 2001 | B1 |
| 6255708 | Sudharsanan et al. | Jul 2001 | B1 |
| 6280381 | Malin et al. | Aug 2001 | B1 |
| 6285896 | Tobler et al. | Sep 2001 | B1 |
| 6308089 | von der Ruhr et al. | Oct 2001 | B1 |
| 6317627 | Ennen et al. | Nov 2001 | B1 |
| 6321100 | Parker | Nov 2001 | B1 |
| 6334065 | Al-Ali et al. | Dec 2001 | B1 |
| 6360114 | Diab et al. | Mar 2002 | B1 |
| 6368283 | Xu et al. | Apr 2002 | B1 |
| 6411373 | Garside et al. | Jun 2002 | B1 |
| 6415167 | Blank et al. | Jul 2002 | B1 |
| 6430437 | Marro | Aug 2002 | B1 |
| 6430525 | Weber et al. | Aug 2002 | B1 |
| 6463311 | Diab | Oct 2002 | B1 |
| 6470199 | Kopotic et al. | Oct 2002 | B1 |
| 6487429 | Hockersmith et al. | Nov 2002 | B2 |
| 6505059 | Kollias et al. | Jan 2003 | B1 |
| 6525386 | Mills et al. | Feb 2003 | B1 |
| 6526300 | Kiani et al. | Feb 2003 | B1 |
| 6534012 | Hazen et al. | Mar 2003 | B1 |
| 6542764 | Al-Ali et al. | Apr 2003 | B1 |
| 6580086 | Schulz et al. | Jun 2003 | B1 |
| 6584336 | Ali et al. | Jun 2003 | B1 |
| 6587196 | Stippick et al. | Jul 2003 | B1 |
| 6587199 | Luu | Jul 2003 | B1 |
| 6595316 | Cybulski et al. | Jul 2003 | B2 |
| 6597932 | Tian et al. | Jul 2003 | B2 |
| 6606511 | Ali et al. | Aug 2003 | B1 |
| 6635559 | Greenwald et al. | Oct 2003 | B2 |
| 6639668 | Trepagnier | Oct 2003 | B1 |
| 6640116 | Diab | Oct 2003 | B2 |
| 6640117 | Makarewicz et al. | Oct 2003 | B2 |
| 6658276 | Kiani et al. | Dec 2003 | B2 |
| 6661161 | Lanzo et al. | Dec 2003 | B1 |
| 6697656 | Al-Ali | Feb 2004 | B1 |
| 6697658 | Al-Ali | Feb 2004 | B2 |
| RE38476 | Diab et al. | Mar 2004 | E |
| RE38492 | Diab et al. | Apr 2004 | E |
| 6738652 | Mattu et al. | May 2004 | B2 |
| 6760607 | Al-Ali | Jul 2004 | B2 |
| 6788965 | Ruchti et al. | Sep 2004 | B2 |
| 6816241 | Grubisic | Nov 2004 | B2 |
| 6822564 | Al-Ali | Nov 2004 | B2 |
| 6850787 | Weber et al. | Feb 2005 | B2 |
| 6850788 | Al-Ali | Feb 2005 | B2 |
| 6876931 | Lorenz et al. | Apr 2005 | B2 |
| 6920345 | Al-Ali et al. | Jul 2005 | B2 |
| 6934570 | Kiani et al. | Aug 2005 | B2 |
| 6943348 | Coffin, IV | Sep 2005 | B1 |
| 6956649 | Acosta et al. | Oct 2005 | B2 |
| 6961598 | Diab | Nov 2005 | B2 |
| 6970792 | Diab | Nov 2005 | B1 |
| 6985764 | Mason et al. | Jan 2006 | B2 |
| 6990364 | Ruchti et al. | Jan 2006 | B2 |
| 6998247 | Monfre et al. | Feb 2006 | B2 |
| 7003338 | Weber et al. | Feb 2006 | B2 |
| 7015451 | Dalke et al. | Mar 2006 | B2 |
| 7027849 | Al-Ali | Apr 2006 | B2 |
| D526719 | Richie, Jr. et al. | Aug 2006 | S |
| 7096052 | Mason et al. | Aug 2006 | B2 |
| 7096054 | Abdul-Hafiz et al. | Aug 2006 | B2 |
| D529616 | Deros et al. | Oct 2006 | S |
| 7133710 | Acosta et al. | Nov 2006 | B2 |
| 7142901 | Kiani et al. | Nov 2006 | B2 |
| 7225006 | Al-Ali et al. | May 2007 | B2 |
| RE39672 | Shehada et al. | Jun 2007 | E |
| 7254429 | Schurman et al. | Aug 2007 | B2 |
| 7254431 | Al-Ali et al. | Aug 2007 | B2 |
| 7254434 | Schulz et al. | Aug 2007 | B2 |
| 7274955 | Kiani et al. | Sep 2007 | B2 |
| D554263 | Al-Ali et al. | Oct 2007 | S |
| 7280858 | Al-Ali et al. | Oct 2007 | B2 |
| 7289835 | Mansfield et al. | Oct 2007 | B2 |
| 7292883 | De Felice et al. | Nov 2007 | B2 |
| 7341559 | Schulz et al. | Mar 2008 | B2 |
| 7343186 | Lamego et al. | Mar 2008 | B2 |
| D566282 | Al-Ali et al. | Apr 2008 | S |
| 7356365 | Schurman | Apr 2008 | B2 |
| 7371981 | Abdul-Hafiz | May 2008 | B2 |
| 7373193 | Al-Ali et al. | May 2008 | B2 |
| 7377794 | Al-Ali et al. | May 2008 | B2 |
| 7395158 | Monfre et al. | Jul 2008 | B2 |
| 7415297 | Al-Ali et al. | Aug 2008 | B2 |
| 7438683 | Al-Ali et al. | Oct 2008 | B2 |
| 7483729 | Al-Ali et al. | Jan 2009 | B2 |
| D587657 | Al-Ali et al. | Mar 2009 | S |
| 7500950 | Al-Ali et al. | Mar 2009 | B2 |
| 7509494 | Al-Ali | Mar 2009 | B2 |
| 7510849 | Schurman et al. | Mar 2009 | B2 |
| 7514725 | Wojtczuk et al. | Apr 2009 | B2 |
| 7519406 | Blank et al. | Apr 2009 | B2 |
| D592507 | Wachman et al. | May 2009 | S |
| 7530942 | Diab | May 2009 | B1 |
| 7593230 | Abul-Haj et al. | Sep 2009 | B2 |
| 7596398 | Al-Ali et al. | Sep 2009 | B2 |
| 7606608 | Blank et al. | Oct 2009 | B2 |
| 7620674 | Ruchti et al. | Nov 2009 | B2 |
| D606659 | Kiani et al. | Dec 2009 | S |
| 7629039 | Eckerbom et al. | Dec 2009 | B2 |
| 7640140 | Ruchti et al. | Dec 2009 | B2 |
| 7647083 | Al-Ali et al. | Jan 2010 | B2 |
| D609193 | Al-Ali et al. | Feb 2010 | S |
| D614305 | Al-Ali et al. | Apr 2010 | S |
| 7697966 | Monfre et al. | Apr 2010 | B2 |
| 7698105 | Ruchti et al. | Apr 2010 | B2 |
| RE41317 | Parker | May 2010 | E |
| RE41333 | Blank et al. | May 2010 | E |
| 7729733 | Al-Ali et al. | Jun 2010 | B2 |
| 7761127 | Al-Ali et al. | Jul 2010 | B2 |
| 7764982 | Dalke et al. | Jul 2010 | B2 |
| D621516 | Kiani et al. | Aug 2010 | S |
| 7791155 | Diab | Sep 2010 | B2 |
| 7811246 | Koops | Oct 2010 | B2 |
| RE41912 | Parker | Nov 2010 | E |
| 7875004 | Yodfat et al. | Jan 2011 | B2 |
| 7880626 | Al-Ali et al. | Feb 2011 | B2 |
| 7909772 | Popov et al. | Mar 2011 | B2 |
| 7919713 | Al-Ali et al. | Apr 2011 | B2 |
| 7937128 | Al-Ali | May 2011 | B2 |
| 7937129 | Mason et al. | May 2011 | B2 |
| 7941199 | Kiani | May 2011 | B2 |
| 7957780 | Lamego et al. | Jun 2011 | B2 |
| 7962188 | Kiani et al. | Jun 2011 | B2 |
| 7976472 | Kiani | Jul 2011 | B2 |
| 7990382 | Kiani | Aug 2011 | B2 |
| 8008088 | Bellott et al. | Aug 2011 | B2 |
| RE42753 | Kiani-Azarbayjany et al. | Sep 2011 | E |
| 8028701 | Al-Ali et al. | Oct 2011 | B2 |
| 8048040 | Kiani | Nov 2011 | B2 |
| 8050728 | Al-Ali et al. | Nov 2011 | B2 |
| RE43169 | Parker | Feb 2012 | E |
| 8118620 | Al-Ali et al. | Feb 2012 | B2 |
| 8130105 | Al-Ali et al. | Mar 2012 | B2 |
| 8182443 | Kiani | May 2012 | B1 |
| 8190223 | Al-Ali et al. | May 2012 | B2 |
| 8203438 | Kiani et al. | Jun 2012 | B2 |
| 8203704 | Merritt et al. | Jun 2012 | B2 |
| 8219172 | Schurman et al. | Jul 2012 | B2 |
| 8224411 | Al-Ali et al. | Jul 2012 | B2 |
| 8229532 | Davis | Jul 2012 | B2 |
| 8233955 | Al-Ali et al. | Jul 2012 | B2 |
| 8255026 | Al-Ali | Aug 2012 | B1 |
| 8265723 | McHale et al. | Sep 2012 | B1 |
| 8267921 | Yodfat et al. | Sep 2012 | B2 |
| 8274360 | Sampath et al. | Sep 2012 | B2 |
| 8280473 | Al-Ali | Oct 2012 | B2 |
| 8315683 | Al-Ali et al. | Nov 2012 | B2 |
| RE43860 | Parker | Dec 2012 | E |
| 8346330 | Lamego | Jan 2013 | B2 |
| 8353842 | Al-Ali et al. | Jan 2013 | B2 |
| 8355766 | Macneish, III et al. | Jan 2013 | B2 |
| 8374665 | Lamego | Feb 2013 | B2 |
| 8388353 | Kiani et al. | Mar 2013 | B2 |
| 8401602 | Kiani | Mar 2013 | B2 |
| 8414499 | Al-Ali et al. | Apr 2013 | B2 |
| 8418524 | Al-Ali | Apr 2013 | B2 |
| 8428967 | Olsen et al. | Apr 2013 | B2 |
| 8430817 | Al-Ali et al. | Apr 2013 | B1 |
| 8437825 | Dalvi et al. | May 2013 | B2 |
| 8455290 | Siskavich | Jun 2013 | B2 |
| 8457707 | Kiani | Jun 2013 | B2 |
| 8471713 | Poeze et al. | Jun 2013 | B2 |
| 8473020 | Kiani et al. | Jun 2013 | B2 |
| 8486005 | Yodfat et al. | Jul 2013 | B2 |
| 8509867 | Workman et al. | Aug 2013 | B2 |
| 8515509 | Bruinsma et al. | Aug 2013 | B2 |
| 8523781 | Al-Ali | Sep 2013 | B2 |
| D692145 | Al-Ali et al. | Oct 2013 | S |
| 8571617 | Reichgott et al. | Oct 2013 | B2 |
| 8571618 | Lamego et al. | Oct 2013 | B1 |
| 8571619 | Al-Ali et al. | Oct 2013 | B2 |
| 8577431 | Lamego et al. | Nov 2013 | B2 |
| 8584345 | Al-Ali et al. | Nov 2013 | B2 |
| 8588880 | Abdul-Hafiz et al. | Nov 2013 | B2 |
| 8630691 | Lamego et al. | Jan 2014 | B2 |
| 8641631 | Sierra et al. | Feb 2014 | B2 |
| 8652060 | Al-Ali | Feb 2014 | B2 |
| 8666468 | Al-Ali | Mar 2014 | B1 |
| 8670811 | O'Reilly | Mar 2014 | B2 |
| RE44823 | Parker | Apr 2014 | E |
| RE44875 | Kiani et al. | Apr 2014 | E |
| 8688183 | Bruinsma et al. | Apr 2014 | B2 |
| 8690799 | Telfort et al. | Apr 2014 | B2 |
| 8696570 | Yodfat et al. | Apr 2014 | B2 |
| 8702627 | Telfort et al. | Apr 2014 | B2 |
| 8712494 | MacNeish, III et al. | Apr 2014 | B1 |
| 8715206 | Telfort et al. | May 2014 | B2 |
| 8723677 | Kiani | May 2014 | B1 |
| 8740792 | Kiani et al. | Jun 2014 | B1 |
| 8755535 | Telfort et al. | Jun 2014 | B2 |
| 8755872 | Marinow | Jun 2014 | B1 |
| 8764671 | Kiani | Jul 2014 | B2 |
| 8768423 | Shakespeare et al. | Jul 2014 | B2 |
| 8771204 | Telfort et al. | Jul 2014 | B2 |
| 8777924 | Kanderian, Jr. et al. | Jul 2014 | B2 |
| 8781544 | Al-Ali et al. | Jul 2014 | B2 |
| 8790268 | Al-Ali | Jul 2014 | B2 |
| 8801613 | Al-Ali et al. | Aug 2014 | B2 |
| 8821397 | Al-Ali et al. | Sep 2014 | B2 |
| 8821415 | Al-Ali et al. | Sep 2014 | B2 |
| 8830449 | Lamego et al. | Sep 2014 | B1 |
| 8840549 | Al-Ali et al. | Sep 2014 | B2 |
| 8852094 | Al-Ali et al. | Oct 2014 | B2 |
| 8852994 | Wojtczuk et al. | Oct 2014 | B2 |
| 8894632 | Yodfat et al. | Nov 2014 | B2 |
| 8897847 | Al-Ali | Nov 2014 | B2 |
| 8911377 | Al-Ali | Dec 2014 | B2 |
| 8989831 | Al-Ali et al. | Mar 2015 | B2 |
| 8998809 | Kiani | Apr 2015 | B2 |
| 9066666 | Kiani | Jun 2015 | B2 |
| 9066680 | Al-Ali et al. | Jun 2015 | B1 |
| 9072476 | Shah et al. | Jul 2015 | B2 |
| 9095316 | Welch et al. | Aug 2015 | B2 |
| 9106038 | Telfort et al. | Aug 2015 | B2 |
| 9107625 | Telfort et al. | Aug 2015 | B2 |
| 9131881 | Diab et al. | Sep 2015 | B2 |
| 9138180 | Coverston et al. | Sep 2015 | B1 |
| 9153112 | Kiani et al. | Oct 2015 | B1 |
| 9179870 | Shah et al. | Nov 2015 | B2 |
| 9192329 | Al-Ali | Nov 2015 | B2 |
| 9192351 | Telfort et al. | Nov 2015 | B1 |
| 9192713 | Yodfat et al. | Nov 2015 | B2 |
| 9195385 | Al-Ali et al. | Nov 2015 | B2 |
| 9211095 | Al-Ali | Dec 2015 | B1 |
| 9218454 | Kiani et al. | Dec 2015 | B2 |
| 9245668 | Vo et al. | Jan 2016 | B1 |
| 9259175 | Stafford | Feb 2016 | B2 |
| 9267572 | Barker et al. | Feb 2016 | B2 |
| 9277880 | Poeze et al. | Mar 2016 | B2 |
| 9307928 | Al-Ali et al. | Apr 2016 | B1 |
| 9323894 | Kiani | Apr 2016 | B2 |
| D755392 | Hwang et al. | May 2016 | S |
| 9326712 | Kiani | May 2016 | B1 |
| 9392945 | Al-Ali et al. | Jul 2016 | B2 |
| 9408542 | Kinast et al. | Aug 2016 | B1 |
| 9436645 | Al-Ali et al. | Sep 2016 | B2 |
| 9445759 | Lamego et al. | Sep 2016 | B1 |
| 9474474 | Lamego et al. | Oct 2016 | B2 |
| 9480435 | Olsen | Nov 2016 | B2 |
| 9510779 | Poeze et al. | Dec 2016 | B2 |
| 9517024 | Kiani et al. | Dec 2016 | B2 |
| 9532722 | Lamego et al. | Jan 2017 | B2 |
| 9560996 | Kiani | Feb 2017 | B2 |
| 9579039 | Jansen et al. | Feb 2017 | B2 |
| 9603558 | Burnett | Mar 2017 | B2 |
| 9615779 | Pryor et al. | Apr 2017 | B2 |
| 9622692 | Lamego et al. | Apr 2017 | B2 |
| D788312 | Al-Ali et al. | May 2017 | S |
| 9649054 | Lamego et al. | May 2017 | B2 |
| 9693722 | Shah et al. | Jul 2017 | B2 |
| 9697928 | Al-Ali et al. | Jul 2017 | B2 |
| 9717458 | Lamego et al. | Aug 2017 | B2 |
| 9724016 | Al-Ali et al. | Aug 2017 | B1 |
| 9724024 | Al-Ali | Aug 2017 | B2 |
| 9724025 | Kiani et al. | Aug 2017 | B1 |
| 9749232 | Sampath et al. | Aug 2017 | B2 |
| 9750442 | Olsen | Sep 2017 | B2 |
| 9750461 | Telfort | Sep 2017 | B1 |
| 9775545 | Al-Ali et al. | Oct 2017 | B2 |
| 9778079 | Al-Ali et al. | Oct 2017 | B1 |
| 9782077 | Lamego et al. | Oct 2017 | B2 |
| 9787568 | Lamego et al. | Oct 2017 | B2 |
| 9808188 | Perea et al. | Nov 2017 | B1 |
| 9839379 | Al-Ali et al. | Dec 2017 | B2 |
| 9839381 | Weber et al. | Dec 2017 | B1 |
| 9847749 | Kiani et al. | Dec 2017 | B2 |
| 9848800 | Lee et al. | Dec 2017 | B1 |
| 9861298 | Eckerbom et al. | Jan 2018 | B2 |
| 9861305 | Weber et al. | Jan 2018 | B1 |
| 9877650 | Muhsin et al. | Jan 2018 | B2 |
| 9891079 | Dalvi | Feb 2018 | B2 |
| 9924897 | Abdul-Hafiz | Mar 2018 | B1 |
| 9936917 | Poeze et al. | Apr 2018 | B2 |
| 9955937 | Telfort | May 2018 | B2 |
| 9965946 | Al-Ali et al. | May 2018 | B2 |
| D820865 | Muhsin et al. | Jun 2018 | S |
| 9986952 | Dalvi et al. | Jun 2018 | B2 |
| D822215 | Al-Ali et al. | Jul 2018 | S |
| D822216 | Barker et al. | Jul 2018 | S |
| 10010276 | Al-Ali et al. | Jul 2018 | B2 |
| 10086138 | Novak, Jr. | Oct 2018 | B1 |
| 10111591 | Dyell et al. | Oct 2018 | B2 |
| D833624 | DeJong et al. | Nov 2018 | S |
| 10123729 | Dyell et al. | Nov 2018 | B2 |
| 10137242 | Neta et al. | Nov 2018 | B2 |
| D835282 | Barker et al. | Dec 2018 | S |
| D835283 | Barker et al. | Dec 2018 | S |
| D835284 | Barker et al. | Dec 2018 | S |
| D835285 | Barker et al. | Dec 2018 | S |
| 10149616 | Al-Ali et al. | Dec 2018 | B2 |
| 10154815 | Al-Ali et al. | Dec 2018 | B2 |
| 10159412 | Lamego et al. | Dec 2018 | B2 |
| 10188348 | Al-Ali et al. | Jan 2019 | B2 |
| RE47218 | Al-Ali | Feb 2019 | E |
| RE47244 | Kiani et al. | Feb 2019 | E |
| RE47249 | Kiani et al. | Feb 2019 | E |
| 10205291 | Scruggs et al. | Feb 2019 | B2 |
| 10226187 | Al-Ali et al. | Mar 2019 | B2 |
| 10231657 | Al-Ali et al. | Mar 2019 | B2 |
| 10231670 | Blank et al. | Mar 2019 | B2 |
| RE47353 | Kiani et al. | Apr 2019 | E |
| 10251605 | Liu et al. | Apr 2019 | B2 |
| 10265464 | Yodfat et al. | Apr 2019 | B2 |
| 10279247 | Kiani | May 2019 | B2 |
| 10292664 | Al-Ali | May 2019 | B2 |
| 10293101 | Brewer | May 2019 | B2 |
| 10299720 | Brown et al. | May 2019 | B2 |
| 10327337 | Schmidt et al. | Jun 2019 | B2 |
| 10327713 | Barker et al. | Jun 2019 | B2 |
| 10332630 | Al-Ali | Jun 2019 | B2 |
| 10383520 | Wojtczuk et al. | Aug 2019 | B2 |
| 10383527 | Al-Ali | Aug 2019 | B2 |
| 10388120 | Muhsin et al. | Aug 2019 | B2 |
| D864120 | Forrest et al. | Oct 2019 | S |
| 10441181 | Telfort et al. | Oct 2019 | B1 |
| 10441196 | Eckerbom et al. | Oct 2019 | B2 |
| 10448844 | Al-Ali et al. | Oct 2019 | B2 |
| 10448871 | Al-Ali et al. | Oct 2019 | B2 |
| 10456038 | Lamego et al. | Oct 2019 | B2 |
| 10463340 | Telfort et al. | Nov 2019 | B2 |
| 10471159 | Lapotko et al. | Nov 2019 | B1 |
| 10505311 | Al-Ali et al. | Dec 2019 | B2 |
| 10524738 | Olsen | Jan 2020 | B2 |
| 10532174 | Al-Ali | Jan 2020 | B2 |
| 10537285 | Shreim et al. | Jan 2020 | B2 |
| 10542903 | Al-Ali et al. | Jan 2020 | B2 |
| 10555678 | Dalvi et al. | Feb 2020 | B2 |
| 10568553 | O'Neil et al. | Feb 2020 | B2 |
| RE47882 | Al-Ali | Mar 2020 | E |
| 10608817 | Haider et al. | Mar 2020 | B2 |
| D880477 | Forrest et al. | Apr 2020 | S |
| 10617302 | Al-Ali et al. | Apr 2020 | B2 |
| 10617335 | Al-Ali et al. | Apr 2020 | B2 |
| 10637181 | Al-Ali et al. | Apr 2020 | B2 |
| 10660201 | Frick et al. | May 2020 | B2 |
| D886849 | Muhsin et al. | Jun 2020 | S |
| D887548 | Abdul-Hafiz et al. | Jun 2020 | S |
| D887549 | Abdul-Hafiz et al. | Jun 2020 | S |
| 10667764 | Ahmed et al. | Jun 2020 | B2 |
| D890708 | Forrest et al. | Jul 2020 | S |
| 10721785 | Al-Ali | Jul 2020 | B2 |
| 10736518 | Al-Ali et al. | Aug 2020 | B2 |
| 10750984 | Pauley et al. | Aug 2020 | B2 |
| D897098 | Al-Ali | Sep 2020 | S |
| 10779098 | Iswanto et al. | Sep 2020 | B2 |
| 10827961 | Iyengar et al. | Nov 2020 | B1 |
| 10828007 | Telfort et al. | Nov 2020 | B1 |
| 10832818 | Muhsin et al. | Nov 2020 | B2 |
| 10849554 | Shreim et al. | Dec 2020 | B2 |
| 10856750 | Indorf | Dec 2020 | B2 |
| D906970 | Forrest et al. | Jan 2021 | S |
| D908213 | Abdul-Hafiz et al. | Jan 2021 | S |
| 10918281 | Al-Ali et al. | Feb 2021 | B2 |
| 10932705 | Muhsin et al. | Mar 2021 | B2 |
| 10932729 | Kiani et al. | Mar 2021 | B2 |
| 10939878 | Kiani et al. | Mar 2021 | B2 |
| 10956950 | Al-Ali et al. | Mar 2021 | B2 |
| D916135 | Indorf et al. | Apr 2021 | S |
| D917046 | Abdul-Hafiz et al. | Apr 2021 | S |
| D917550 | Indorf et al. | Apr 2021 | S |
| D917564 | Indorf et al. | Apr 2021 | S |
| D917704 | Al-Ali et al. | Apr 2021 | S |
| 10987066 | Chandran et al. | Apr 2021 | B2 |
| 10991135 | Al-Ali et al. | Apr 2021 | B2 |
| D919094 | Al-Ali et al. | May 2021 | S |
| D919100 | Al-Ali et al. | May 2021 | S |
| 11006867 | Al-Ali | May 2021 | B2 |
| D921202 | Al-Ali et al. | Jun 2021 | S |
| 11024064 | Muhsin et al. | Jun 2021 | B2 |
| 11026604 | Chen et al. | Jun 2021 | B2 |
| D925597 | Chandran et al. | Jul 2021 | S |
| D927699 | Al-Ali et al. | Aug 2021 | S |
| 11076777 | Lee et al. | Aug 2021 | B2 |
| 11114188 | Poeze et al. | Sep 2021 | B2 |
| D933232 | Al-Ali et al. | Oct 2021 | S |
| D933233 | Al-Ali et al. | Oct 2021 | S |
| D933234 | Al-Ali et al. | Oct 2021 | S |
| 11145408 | Sampath et al. | Oct 2021 | B2 |
| 11147518 | Al-Ali et al. | Oct 2021 | B1 |
| 11185262 | Al-Ali et al. | Nov 2021 | B2 |
| 11191484 | Kiani et al. | Dec 2021 | B2 |
| D946596 | Ahmed | Mar 2022 | S |
| D946597 | Ahmed | Mar 2022 | S |
| D946598 | Ahmed | Mar 2022 | S |
| D946617 | Ahmed | Mar 2022 | S |
| 11272839 | Al-Ali et al. | Mar 2022 | B2 |
| 11289199 | Al-Ali | Mar 2022 | B2 |
| RE49034 | Al-Ali | Apr 2022 | E |
| 11298021 | Muhsin et al. | Apr 2022 | B2 |
| D950580 | Ahmed | May 2022 | S |
| D950599 | Ahmed | May 2022 | S |
| D950738 | Al-Ali et al. | May 2022 | S |
| D957648 | Al-Ali | Jul 2022 | S |
| 11382567 | O'Brien et al. | Jul 2022 | B2 |
| 11389093 | Triman et al. | Jul 2022 | B2 |
| 11406286 | Al-Ali et al. | Aug 2022 | B2 |
| 11417426 | Muhsin et al. | Aug 2022 | B2 |
| 11439329 | Lamego | Sep 2022 | B2 |
| 11445948 | Scruggs et al. | Sep 2022 | B2 |
| D965789 | Al-Ali et al. | Oct 2022 | S |
| D967433 | Al-Ali et al. | Oct 2022 | S |
| 11464410 | Muhsin | Oct 2022 | B2 |
| 11504058 | Sharma et al. | Nov 2022 | B1 |
| 11504066 | Dalvi et al. | Nov 2022 | B1 |
| D971933 | Ahmed | Dec 2022 | S |
| D973072 | Ahmed | Dec 2022 | S |
| D973685 | Ahmed | Dec 2022 | S |
| D973686 | Ahmed | Dec 2022 | S |
| D974193 | Forrest et al. | Jan 2023 | S |
| D979516 | Al-Ali et al. | Feb 2023 | S |
| D980091 | Forrest et al. | Mar 2023 | S |
| 11596363 | Lamego | Mar 2023 | B2 |
| 11627919 | Kiani et al. | Apr 2023 | B2 |
| 11637437 | Al-Ali et al. | Apr 2023 | B2 |
| D985498 | Al-Ali et al. | May 2023 | S |
| 11653862 | Dalvi et al. | May 2023 | B2 |
| D989112 | Muhsin et al. | Jun 2023 | S |
| D989327 | Al-Ali et al. | Jun 2023 | S |
| 11678829 | Al-Ali et al. | Jun 2023 | B2 |
| 11679579 | Al-Ali | Jun 2023 | B2 |
| 11684296 | Vo et al. | Jun 2023 | B2 |
| 11692934 | Normand et al. | Jul 2023 | B2 |
| 11701043 | Al-Ali et al. | Jul 2023 | B2 |
| D997365 | Hwang | Aug 2023 | S |
| 11721105 | Ranasinghe et al. | Aug 2023 | B2 |
| 11730379 | Ahmed et al. | Aug 2023 | B2 |
| D998625 | Indorf et al. | Sep 2023 | S |
| D998630 | Indorf et al. | Sep 2023 | S |
| D998631 | Indorf et al. | Sep 2023 | S |
| D999244 | Indorf et al. | Sep 2023 | S |
| D999245 | Indorf et al. | Sep 2023 | S |
| D999246 | Indorf et al. | Sep 2023 | S |
| 11766198 | Pauley et al. | Sep 2023 | B2 |
| D1000975 | Al-Ali et al. | Oct 2023 | S |
| 11803623 | Kiani et al. | Oct 2023 | B2 |
| 11832940 | Diab et al. | Dec 2023 | B2 |
| D1013179 | Al-Ali et al. | Jan 2024 | S |
| 11872156 | Telfort et al. | Jan 2024 | B2 |
| 11879960 | Ranasinghe et al. | Jan 2024 | B2 |
| 11883129 | Olsen | Jan 2024 | B2 |
| 11951186 | Krishnamani et al. | Apr 2024 | B2 |
| 20010034477 | Mansfield et al. | Oct 2001 | A1 |
| 20010039483 | Brand et al. | Nov 2001 | A1 |
| 20020010401 | Bushmakin et al. | Jan 2002 | A1 |
| 20020058864 | Mansfield et al. | May 2002 | A1 |
| 20020133080 | Apruzzese et al. | Sep 2002 | A1 |
| 20030013975 | Kiani | Jan 2003 | A1 |
| 20030018243 | Gerhardt et al. | Jan 2003 | A1 |
| 20030144582 | Cohen et al. | Jul 2003 | A1 |
| 20030156288 | Barnum et al. | Aug 2003 | A1 |
| 20030212312 | Coffin, IV et al. | Nov 2003 | A1 |
| 20040106163 | Workman, Jr. et al. | Jun 2004 | A1 |
| 20050055276 | Kiani et al. | Mar 2005 | A1 |
| 20050234317 | Kiani | Oct 2005 | A1 |
| 20060073719 | Kiani | Apr 2006 | A1 |
| 20060189871 | Al-Ali et al. | Aug 2006 | A1 |
| 20070073116 | Kiani et al. | Mar 2007 | A1 |
| 20070180140 | Welch et al. | Aug 2007 | A1 |
| 20070244377 | Cozad et al. | Oct 2007 | A1 |
| 20080064965 | Jay et al. | Mar 2008 | A1 |
| 20080094228 | Welch et al. | Apr 2008 | A1 |
| 20080103375 | Kiani | May 2008 | A1 |
| 20080221418 | Al-Ali et al. | Sep 2008 | A1 |
| 20090036759 | Ault et al. | Feb 2009 | A1 |
| 20090093687 | Telfort et al. | Apr 2009 | A1 |
| 20090095926 | MacNeish, III | Apr 2009 | A1 |
| 20090216100 | Ebner et al. | Aug 2009 | A1 |
| 20090247984 | Lamego et al. | Oct 2009 | A1 |
| 20090275844 | Al-Ali | Nov 2009 | A1 |
| 20100004518 | Vo et al. | Jan 2010 | A1 |
| 20100030040 | Poeze et al. | Feb 2010 | A1 |
| 20100099964 | O'Reilly et al. | Apr 2010 | A1 |
| 20100174239 | Yodfat et al. | Jul 2010 | A1 |
| 20100234718 | Sampath et al. | Sep 2010 | A1 |
| 20100270257 | Wachman et al. | Oct 2010 | A1 |
| 20110028806 | Merritt et al. | Feb 2011 | A1 |
| 20110028809 | Goodman | Feb 2011 | A1 |
| 20110040163 | Telson et al. | Feb 2011 | A1 |
| 20110040197 | Welch et al. | Feb 2011 | A1 |
| 20110082711 | Poeze et al. | Apr 2011 | A1 |
| 20110087081 | Kiani et al. | Apr 2011 | A1 |
| 20110118561 | Tari et al. | May 2011 | A1 |
| 20110137297 | Kiani et al. | Jun 2011 | A1 |
| 20110172498 | Olsen et al. | Jul 2011 | A1 |
| 20110230733 | Al-Ali | Sep 2011 | A1 |
| 20120123231 | O'Reilly | May 2012 | A1 |
| 20120165629 | Merritt et al. | Jun 2012 | A1 |
| 20120209084 | Olsen et al. | Aug 2012 | A1 |
| 20120226117 | Lamego et al. | Sep 2012 | A1 |
| 20120283524 | Kiani et al. | Nov 2012 | A1 |
| 20130023775 | Lamego et al. | Jan 2013 | A1 |
| 20130041343 | Toumazou et al. | Feb 2013 | A1 |
| 20130041591 | Lamego | Feb 2013 | A1 |
| 20130060147 | Welch et al. | Mar 2013 | A1 |
| 20130096405 | Garfio | Apr 2013 | A1 |
| 20130296672 | O'Neil et al. | Nov 2013 | A1 |
| 20130345921 | Al-Ali et al. | Dec 2013 | A1 |
| 20140005633 | Finan | Jan 2014 | A1 |
| 20140081202 | Tsoukalis | Mar 2014 | A1 |
| 20140166076 | Kiani et al. | Jun 2014 | A1 |
| 20140180160 | Brown et al. | Jun 2014 | A1 |
| 20140187973 | Brown et al. | Jul 2014 | A1 |
| 20140243634 | Huang et al. | Aug 2014 | A1 |
| 20140275871 | Lamego et al. | Sep 2014 | A1 |
| 20140275872 | Merritt et al. | Sep 2014 | A1 |
| 20140316217 | Purdon et al. | Oct 2014 | A1 |
| 20140316218 | Purdon et al. | Oct 2014 | A1 |
| 20140323897 | Brown et al. | Oct 2014 | A1 |
| 20140323898 | Purdon et al. | Oct 2014 | A1 |
| 20150005600 | Blank et al. | Jan 2015 | A1 |
| 20150011907 | Purdon et al. | Jan 2015 | A1 |
| 20150073241 | Lamego | Mar 2015 | A1 |
| 20150080754 | Purdon et al. | Mar 2015 | A1 |
| 20150099950 | Al-Ali et al. | Apr 2015 | A1 |
| 20160196388 | Lamego | Jul 2016 | A1 |
| 20160283665 | Sampath et al. | Sep 2016 | A1 |
| 20160367173 | Dalvi et al. | Dec 2016 | A1 |
| 20170024748 | Haider | Jan 2017 | A1 |
| 20170173632 | Al-Ali | Jun 2017 | A1 |
| 20170251974 | Shreim et al. | Sep 2017 | A1 |
| 20170281864 | Searle | Oct 2017 | A1 |
| 20170311891 | Kiani et al. | Nov 2017 | A1 |
| 20180103874 | Lee et al. | Apr 2018 | A1 |
| 20180207356 | Joseph et al. | Jul 2018 | A1 |
| 20180228416 | Frick | Aug 2018 | A1 |
| 20180242926 | Muhsin et al. | Aug 2018 | A1 |
| 20180247353 | Al-Ali et al. | Aug 2018 | A1 |
| 20180247712 | Muhsin et al. | Aug 2018 | A1 |
| 20180256087 | Al-Ali et al. | Sep 2018 | A1 |
| 20180300919 | Muhsin et al. | Oct 2018 | A1 |
| 20180310822 | Indorf et al. | Nov 2018 | A1 |
| 20180310823 | Al-Ali et al. | Nov 2018 | A1 |
| 20190015023 | Monfre | Jan 2019 | A1 |
| 20190076068 | Yang | Mar 2019 | A1 |
| 20190117070 | Muhsin et al. | Apr 2019 | A1 |
| 20190200941 | Chandran et al. | Jul 2019 | A1 |
| 20190239787 | Pauley et al. | Aug 2019 | A1 |
| 20190320906 | Olsen | Oct 2019 | A1 |
| 20190374139 | Kiani et al. | Dec 2019 | A1 |
| 20190374713 | Kiani et al. | Dec 2019 | A1 |
| 20200060869 | Telfort et al. | Feb 2020 | A1 |
| 20200093989 | Koops et al. | Mar 2020 | A1 |
| 20200111552 | Ahmed | Apr 2020 | A1 |
| 20200113435 | Muhsin | Apr 2020 | A1 |
| 20200113488 | Al-Ali et al. | Apr 2020 | A1 |
| 20200113496 | Scruggs et al. | Apr 2020 | A1 |
| 20200113497 | Triman et al. | Apr 2020 | A1 |
| 20200113520 | Abdul-Hafiz et al. | Apr 2020 | A1 |
| 20200138288 | Al-Ali et al. | May 2020 | A1 |
| 20200138368 | Kiani et al. | May 2020 | A1 |
| 20200163597 | Dalvi et al. | May 2020 | A1 |
| 20200196877 | Vo et al. | Jun 2020 | A1 |
| 20200253474 | Muhsin et al. | Aug 2020 | A1 |
| 20200253544 | Belur Nagaraj et al. | Aug 2020 | A1 |
| 20200275841 | Telfort et al. | Sep 2020 | A1 |
| 20200288983 | Telfort et al. | Sep 2020 | A1 |
| 20200321793 | Al-Ali et al. | Oct 2020 | A1 |
| 20200329983 | Al-Ali et al. | Oct 2020 | A1 |
| 20200329984 | Al-Ali et al. | Oct 2020 | A1 |
| 20200329993 | Al-Ali et al. | Oct 2020 | A1 |
| 20200330037 | Al-Ali et al. | Oct 2020 | A1 |
| 20210022628 | Telfort et al. | Jan 2021 | A1 |
| 20210104173 | Pauley et al. | Apr 2021 | A1 |
| 20210113121 | Diab et al. | Apr 2021 | A1 |
| 20210117525 | Kiani et al. | Apr 2021 | A1 |
| 20210118581 | Kiani et al. | Apr 2021 | A1 |
| 20210121582 | Krishnamani et al. | Apr 2021 | A1 |
| 20210161465 | Barker et al. | Jun 2021 | A1 |
| 20210236729 | Kiani et al. | Aug 2021 | A1 |
| 20210256267 | Ranasinghe et al. | Aug 2021 | A1 |
| 20210256835 | Ranasinghe et al. | Aug 2021 | A1 |
| 20210275101 | Vo et al. | Sep 2021 | A1 |
| 20210290060 | Ahmed | Sep 2021 | A1 |
| 20210290072 | Forrest | Sep 2021 | A1 |
| 20210290080 | Ahmed | Sep 2021 | A1 |
| 20210290120 | Al-Ali | Sep 2021 | A1 |
| 20210290177 | Novak, Jr. | Sep 2021 | A1 |
| 20210290184 | Ahmed | Sep 2021 | A1 |
| 20210296008 | Novak, Jr. | Sep 2021 | A1 |
| 20210330228 | Olsen et al. | Oct 2021 | A1 |
| 20210386382 | Olsen et al. | Dec 2021 | A1 |
| 20210402110 | Pauley et al. | Dec 2021 | A1 |
| 20220026355 | Normand et al. | Jan 2022 | A1 |
| 20220039707 | Sharma et al. | Feb 2022 | A1 |
| 20220053892 | Al-Ali et al. | Feb 2022 | A1 |
| 20220071562 | Kiani | Mar 2022 | A1 |
| 20220096603 | Kiani et al. | Mar 2022 | A1 |
| 20220151521 | Krishnamani et al. | May 2022 | A1 |
| 20220218244 | Kiani et al. | Jul 2022 | A1 |
| 20220287574 | Telfort et al. | Sep 2022 | A1 |
| 20220296161 | Al-Ali et al. | Sep 2022 | A1 |
| 20220361819 | Al-Ali et al. | Nov 2022 | A1 |
| 20220379059 | Yu et al. | Dec 2022 | A1 |
| 20220392610 | Kiani et al. | Dec 2022 | A1 |
| 20230028745 | Al-Ali | Jan 2023 | A1 |
| 20230038389 | Vo | Feb 2023 | A1 |
| 20230045647 | Vo | Feb 2023 | A1 |
| 20230058052 | Al-Ali | Feb 2023 | A1 |
| 20230058342 | Kiani | Feb 2023 | A1 |
| 20230069789 | Koo et al. | Mar 2023 | A1 |
| 20230087671 | Telfort et al. | Mar 2023 | A1 |
| 20230110152 | Forrest et al. | Apr 2023 | A1 |
| 20230111198 | Yu et al. | Apr 2023 | A1 |
| 20230115397 | Vo et al. | Apr 2023 | A1 |
| 20230116371 | Mills et al. | Apr 2023 | A1 |
| 20230135297 | Kiani et al. | May 2023 | A1 |
| 20230138098 | Telfort et al. | May 2023 | A1 |
| 20230145155 | Krishnamani et al. | May 2023 | A1 |
| 20230147750 | Barker et al. | May 2023 | A1 |
| 20230210417 | Al-Ali et al. | Jul 2023 | A1 |
| 20230222805 | Muhsin et al. | Jul 2023 | A1 |
| 20230222887 | Muhsin et al. | Jul 2023 | A1 |
| 20230226331 | Kiani et al. | Jul 2023 | A1 |
| 20230284916 | Telfort | Sep 2023 | A1 |
| 20230284943 | Scruggs et al. | Sep 2023 | A1 |
| 20230301562 | Scruggs et al. | Sep 2023 | A1 |
| 20230346993 | Kiani et al. | Nov 2023 | A1 |
| 20230368221 | Haider | Nov 2023 | A1 |
| 20230371893 | Al-Ali et al. | Nov 2023 | A1 |
| 20230389837 | Krishnamani et al. | Dec 2023 | A1 |
| 20240016418 | Devadoss et al. | Jan 2024 | A1 |
| 20240016419 | Devadoss et al. | Jan 2024 | A1 |
| 20240047061 | Al-Ali et al. | Feb 2024 | A1 |
| 20240049310 | Al-Ali et al. | Feb 2024 | A1 |
| 20240049986 | Al-Ali et al. | Feb 2024 | A1 |
| 20240081656 | DeJong et al. | Mar 2024 | A1 |
| 20240122486 | Kiani | Apr 2024 | A1 |
| Number | Date | Country |
|---|---|---|
| 0 351 891 | Sep 1993 | EP |
| 1 957 135 | May 2015 | EP |
| 3 329 847 | Jun 2018 | EP |
| 2019661 | Apr 2019 | NL |
| WO 2011162843 | Dec 2011 | WO |
| WO 2017198116 | Nov 2017 | WO |
| WO 2019083354 | May 2019 | WO |
| WO 2021155048 | Aug 2021 | WO |
| Entry |
|---|
| US 2024/0016391 A1, 01/2024, Lapotko et al. (withdrawn) |
| “24-Bit Capacitance to Digital Converter with Temperature Sensor”, Analog Devices, AD7745/AD7746, 2005, https://www.analog.com/media/en/technical-documentation/data-sheets/AD7745_7746.pdf, pp. 28. |
| Donnelly et al., “Hydrogel-Forming Microneedles Prepared from ‘Super Swelling’ Polymers Combined with Lyophilised Wafers for Transdermal Drug Delivery”, PLOS One, Oct. 2014, vol. 9, No. 10, e111547, pp. 12. |
| Ghoreishizadeh et al., “Study of Electrochemical Impedance of a Continuous Glucose Monitoring Sensor and its Correlation With Sensor Performance”, IEEE Sensors Letters, 2018, pp. 4. |
| Pauliukaite et al., “Electrochemical impedance studies of chitosan-modified electrodes for application in electrochemical sensors and biosensors”, Electrochimica Acta, vol. 55, 2010, pp. 6239-6247. |
| International Search Report and Written Opinion received in PCT Application No. PCT/US2021/015559, dated Jul. 27, 2021 in 18 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20210236729 A1 | Aug 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 63044831 | Jun 2020 | US | |
| 63015272 | Apr 2020 | US | |
| 62978480 | Feb 2020 | US | |
| 62968107 | Jan 2020 | US |
