Occlusion resolution in medication delivery devices, systems, and methods

Abstract
Methods, devices, and systems of delivering infusion fluid (e.g., medication such as insulin) can detect, at multiple times during a dispensation period of time, a pressure level of the infusion fluid in an infusion fluid pathway, either directly or indirectly. Based on the detected pressure levels, one or more actual dispensation times that are after an intended dispensation time can be determined. In some cases, methods, devices, and systems provided herein can use variable occlusion alarm thresholds, which can depend on variables such as an age of an infusion set and/or a current analyte level. In some cases, methods, devices, and systems provided herein can automate medication delivery and use the actual dispensation times in a control algorithm determining medication deliveries.
Description
TECHNICAL FIELD

This document relates to systems and methods for the detection and resolution of occlusions in medication delivery devices. In some cases, the system can be adapted to use feedback from one or more sensors to detect an occlusion in a flow path from an automated medication delivery devices and, optionally, to determine how to resolve an occlusion. In some cases, methods, systems, and devices provided herein can use sensor information from occlusion detectors to determine an amount or timing of medication delivery.


BACKGROUND

Pump devices are commonly used to deliver one or more fluids to targeted individuals. In some cases, pump devices can receive feedback information from a patient to determine an amount of a fluid medication to administer to the patient. For example, an insulin infusion pump device may be used to deliver insulin to a person with diabetes (PWD) in order to control blood glucose levels and can receive information from a glucose sensor in order to determine an amount of insulin to be delivered. In use, however, occlusions can occur at either the infusion site or along the catheter (tubing) between the infusion pump and the infusion site, which can stop the delivery of medication until the occlusion is resolved. Some infusion pumps have incorporated sensors that can trigger an occlusion alarm if a threshold pressure is detected (see e.g., U.S. Pat. Nos. 8,409,142; 8,057,436; 7,892,199; 7,833,196; 7,828,528; 7,938,797; 8,808,230). Some occlusions may self-resolve overtime, after being jostled, or after sufficient pressure builds up, while other occlusions may require a user to change the infusion site or fix or change the catheter between the infusion pump and the infusion site. If an occlusion alarm triggers too early for back pressure that would have self-resolved, this can unnecessarily stress the user and potentially cause the user to experience alarm fatigue. On the other hand, significant delays in the delivery of insulin due to an occlusion can cause the PWD's blood glucose to rise, which may cause hyperglycemic events.


BRIEF SUMMARY

Methods, devices, and systems provided herein are adapted to safely and effectively provide automated medication delivery (preferably, automated medication delivery (AMD)) using based at least partially upon feedback from one or more occlusion sensors and (optionally) physiological feedback from the patient. In many circumstances, the methods, devices, and systems described herein provide an improvement in differentiating between the occlusions that require user intervention and those that do not, and to gain better information regarding whether insulin is actually being delivered to the PWD. In some cases, an occlusion sensor can be a pressure sensor in a medication reservoir or along a fluid flow path from the reservoir, or a force sensor used to detect a force of a mechanism used to apply pressure to a medication reservoir. In particular embodiments, AMD the devices, systems, and methods provided herein can be adapted to deliver insulin to a person with diabetes (PWD) based on feedback from a glucose sensor and feedback from an occlusion sensor.


In particular embodiments, devices, systems, and methods provided herein can determine or estimate an amount of medication stuck-in-transit (MST) and/or an amount of active medication on board (AMOB). In one example described below, an amount of AMOB can be estimated based on the amount of medication delivered and the time the medication was delivered using a decay curve for the medication. In some implementations, the amount of AMOB can be determined based on the amounts and timing of medication delivered, but subtracting an amount of MST determined based on back pressure detected by one or more occlusion or pressure sensors, with the MST being added back to AMOB once the back pressure resolves. Also, feedback information from one or more occlusion sensors can be correlated to amounts of MST. In some cases, the medication delivered can be insulin, and an amount of Insulin On Board (IOB) can be determined based on the timing of insulin deliveries made with an insulin infusion pump, but subtracting amounts of insulin detected as being insulin stuck-in-transit (IST) when an occlusion is detected due to pressure build up and adding it back if the pressure resolves without an infusion set change. Optionally, AMD systems, devices, and methods provided herein can determine an amount of additional medication to deliver based on AMOB while ignoring the MST. In particular embodiments, AMD systems, devices, and methods provided herein can determine whether a bolus of the MST and the additional medication is safe prior to delivering the additional amount of medication. For example, an automated insulin delivery (AID) system receiving feedback from a continuous glucose monitor (CGM) and an occlusion detector can use IOB, excluding any determined IST, to determine an amount of insulin to deliver assuming that the IST will remain constant (e.g., due to a slow release of insulin that releases pressure), but also determine if a bolus of the IST would be safe for the PWD if a temporary occlusion resolves upon that delivery of insulin. For example, methods, systems, and devices provided herein can determine if the delivery of the IST insulin, in addition to the determined amount, would likely send the PWD below a safe threshold blood glucose level. If determined to be safe, the additional insulin can be administered and the occlusion sensor monitored to see if the additional insulin causes the occlusion to resolve or if pressure continues to build, which can trigger an occlusion alarm by either causing the pressure/force to increase by a determined amount or to exceed a threshold. By delivering insulin assuming that IOB does not include the IST, the systems, methods, and devices provided herein can force an occlusion alarm to trigger more quickly if the occlusion is not self-resolving by delivering an additional dosage of insulin, but ensure safety by checking to see if the delivery of all the IST would be safe. In such cases, a determination that an amount of IST is unsafe may trigger an occlusion alarm or a message to the user that the user should disconnect an infusion set to prevent a full delivery of the IST. In some cases, a replacement of an infusion set can result in the IST being cleared from the system without being delivered to the user, thus methods, devices, and systems provided herein can have an IOB calculation that excludes undelivered IST from an IOB calculation, thus improving the accuracy of a control algorithm that uses IOB to determine insulin delivery rates.


In particular embodiments, methods, devices, and systems provided herein can detect an elevated pressure in a medication reservoir or in a delivery catheter and can determine a safe amount of additional medication that can be delivered to determine if the occlusion condition will self-resolve or not. Systems, devices, and methods provided herein can also issue an occlusion alarm if the additional medication is administered and the method, device, or system determines that the occlusion condition will not self-resolve. In some cases, methods, systems, and devices may provide troubleshooting instructions to the user in response to an occlusion alarm (e.g., instructions to check a catheter for kinks, to change the infusion site, to prime the catheter, etc.). In some implementations, methods, devices, and systems provided herein can estimate an amount of medicine that remains undelivered based on data from the occlusion detector. For example, a detected pressure in a catheter can be correlated to an amount of insulin that remains undelivered, which can depend on the length, rate of delivery, lumen thickness, and material of the catheter. As described herein, methods, devices, and systems can be adapted to deliver insulin to a PWD, and these systems can additionally receive blood glucose data from the PWD to determine an amount of insulin that can be delivered to the PWD safely without causing the PWD to experience hypoglycemia. For example, methods, systems, and devices provided herein may have an insulin sensitivity factor programmed in for a PWD and may have a current blood glucose level and optionally a current blood glucose trend, and may calculate a risk of a hypoglycemic event if an additional amount of insulin is administered to the user. In some implementations, methods, devices, and systems provided herein can provide users with non-disruptive tips on how to better use the system based on data from an occlusion sensor. For example, in some cases methods, systems, and devices provided herein can detect back pressure possibly due to hydrostatic pressure (i.e., pressure due to an altitude difference between the pump and an infusion site) and can provide the user with a notice that the pump should ideally be placed approximately at the same height as the infusion site.


Methods, systems, and devices provided herein can also adjust estimates of an amount of active medication remaining in a patient's body based on data from an occlusion sensor. For example, many medications have an active half-life after being administered to a patient, thus a determination or estimation of an amount of active medication in the user's body can be used to make future therapy decisions (either automatically or by the user). An occlusion condition, however, can delay when medication is actually delivered to the user. For example, pressure in a catheter can indicate that a certain volume of medication remains in the catheter, thus data from occlusion sensors can be used in methods, devices, and systems provided herein to produce a more accurate estimation of an amount of medication that remains active in a patient's body by not including medicine that remains in the catheter and/or by knowing when the medication was actually delivered to the user by tracking when the occlusion was resolved. In some cases, methods, systems, and devices provided herein can collect data regarding how an occlusion was resolved to make a determination of whether the medication was actually delivered. For example, methods, devices, and systems provided herein can use a troubleshooting tutorial to determine if that occlusion was resolved by removing the catheter from the infusion site or by replacing the infusion site, which would allow methods, systems, and devices provided herein to assume that the medication remaining in the catheter was not delivered. In some cases, methods, devices, and systems provided herein may make assumptions regarding the delivery of medication that maximize the safety of the patient. For example, if the data makes it unclear if a PWD received insulin, methods, devices, and systems provided herein may assume that that insulin was delivered in order to mitigate against the risk of a hypoglycemic event.


Methods, systems, and devices provided herein can also use pressure data or pressure proxy data (optionally from an occlusion detector) to detect possible disconnects from an infusion site. In particular embodiments, discrete pumping operations may cause a temporary pressure increase in the catheter during each pumping operation. In some cases, systems, methods, and devices provided herein can alarm if a pressure increase during a discrete pumping operation does not exceed a threshold. For example, a disconnected catheter may produce a small pressure rise. In some such situations, a larger pressure rise than normal might indicate that the infusion site may begin to occlude soon. In particular embodiments, the pressure spike profile for each discrete pumping operation may provide additional information about the infusion site (e.g., the location on the body, the age of the infusion site, whether medication is tunneling back towards the surface of the patient's skin). In some cases, methods, systems, and devices may alert the user against placing an infusion site at certain locations, about an upcoming need to change the infusion site, or to confirm that the catheter is properly secured to the infusion site.


Methods, systems, and devices provided herein can also use pressure data or pressure proxy data (optionally form an occlusion detector) to determine a relative position of the infusion site with respect to an infusion pump, which can be used to advise a user regarding an ideal relative positioning. An altitude difference between an infusion pump and an infusion site can result in hydrostatic pressure. If the pump is below the infusion site, the hydrostatic pressure increases the pressure detected in the catheter or reservoir. For example, a user sleeps in a bunkbed and places the pump on a night stand causing there to be a significant hydrostatic pressure. This hydrostatic pressure cause false occlusion alarms in systems that alarm immediately alarm immediately after any pressure is detected. Methods, devices, and systems provided herein, however, can observe detected pressures that remain approximately constant and determine that the pressure is due to a hydrostatic pressure and not an occlusion. If it is determined that a prolonged detected pressure is not an occlusion (due to an approximately steady state detected pressure), methods, devices, and systems provided herein can provide a non-disruptive tip or notice to a user explaining that an altitude difference was noticed for a prolonged period of time and/or telling the user to try to keep the pump at a height/altitude approximately the same as the infusion site. Additionally, if the infusion site is significantly below the pump and here is a particularly sensitive pressure sensor, a pressure rise during a pumping operation may not be as great as expected for the system, thus a troubleshooting evaluation questioning whether the infusion site is disconnected might also ask a user about the relative heights of the pump and infusion site.


In particular embodiments, methods, devices, and systems provided herein can automate the delivery of insulin to a person with diabetes (PWD) based on the PWD's blood glucose levels and/or occlusion detector data. In some cases, methods, devices, and systems provided herein can suspend, reduce, or increase an amount of basal insulin delivered to a PWD based on blood glucose data. Methods, devices, and systems provided herein can calculate an amount of active insulin in the PWD's body (e.g., calculate an IOB) based on deliveries of insulin to the PWD, using occlusion detector data to adjust the timing of insulin delivery based on any resolved occlusion conditions. In some implementations, an occlusion detector may require a threshold pressure in an insulin reservoir or in the infusion catheter before any back pressure will register, thus the detection of any back pressure may indicate that an amount of insulin thought to have been delivered was not delivered. Optionally, methods, devices, and systems can subtract an amount of insulin from the IOB upon an occlusion detector registering a threshold back pressure or registering any back pressure or methods, devices, and systems can trigger a delivery of a line-clearing bolus upon a determination that a first threshold occlusion condition is present and a determination that the delivery of the line-clearing bolus is safe for the PWD. For example, a safe line-clearing bolus can be based on the insulin sensitivity factor (ISF) of the PWD, the current blood glucose level of the user and optionally a blood glucose trend (e.g., from a continuous glucose monitor), an estimate of the IOB, and optionally projected blood glucose levels for the PWD based on said information. In some implementations, methods, devices, and systems provided herein can require an attempted delivery of a line-clearing bolus to determine if the occlusion condition is an occlusion that is likely to self-resolve prior to the issuance of an occlusion alarm. For example, if it is not safe to deliver the line-clearing bolus, it may indicate that the failure to deliver insulin is not yet dangerous to the PWD. In particular embodiments, an occlusion alarm threshold for an occlusion alarm may be lower than a threshold to deliver a line-clearing bolus. Methods, devices, and systems provided herein can monitor occlusion detector data during and after the delivery of a line-clearing bolus to determine if the additional insulin delivery further increases the back pressure in the insulin reservoir or infusion catheter or if it caused an occlusion condition to self-resolve. For example, if the pressure increases consistent with a full occlusion, this may trigger an occlusion alarm. In some cases, for example, a near zero change to the pressure detected after the line-clearing bolus may indicate that the detected pressure is possibly due to hydrostatic pressure, which may indicate that a disruptive alarm is not needed. Optionally, methods, devices, and systems provided herein may reduce future basal insulin deliveries to the PWD based on the delivery of the line-clearing bolus. For example, if the line-clearing bolus delivers 0.5 units of insulin, the basal insulin delivery may be delayed for a period of time during which that amount of insulin would have been delivered via the basal insulin delivery (e.g., the number of units delivered divided by the basal rate). In particular embodiments, methods, devices, and systems may only deliver line-clearing boluses when continuous blood glucose data is available and when basal insulin therapy is being actively automated.


Some embodiments of an infusion pump system may include one or more sensors for detecting a fluid pressure within an infusate flow pathway. The detected fluid pressures can be advantageously used by the infusion pump system in various ways. For example, in some embodiments, the detected fluid pressure can indicate when an occlusion exists in the infusate fluid pathway, and an alarm can alert the user to the presence of such an occlusion. In some embodiments, the detected fluid pressure can be used to determine an accurate time and amount of infusate delivered to the user. Such information can be used by the infusion pump system, for example, to accurately predict the user's future blood glucose levels. In some embodiments, the detected fluid pressure can be used to confirm whether a dispensation of infusate was actually delivered into the user's body (e.g., the user's vasculature).


Some or all of the embodiments described herein may provide one or more of the following advantages. First, the infusion pump system may include a pressure detection configuration that accurately detects occlusions in the infusate flow path extending from the pump device to the user. As such, the occlusion sensor feature can provide a notice (e.g., an alarm, an alert, etc.) to the user if he or she is receiving no dosage or a lower than desired dosage of infusate due to an occlusion in the infusate flow path. Such an occlusion may occur, for example, when the infusate fluid flow line (e.g., a cannula, infusion set tubing, or the like) is kinked.


Second, some embodiments of the infusion pump system may include a pressure detection configuration that can be used to determine an accurate time and an accurate amount of infusate actually delivered to the user. In some implementations, an occlusion in the infusate pathway is a transient occlusion. That is, for example, an occlusion may exist at the time of an infusate delivery, but later the occlusion may become fully or partially eliminated. In such a case, a desired dispensation of an amount of infusate may initially be either fully or partially reduced, and at a time thereafter the residual pressurized infusate in the pathway may be subsequently delivered to the user when the occlusion is eliminated. The pressure detection configuration can thereby be used to detect the actual amounts and the actual times at which both the initial and the subsequent infusate deliveries are made. Such information can be advantageously used by the infusion pump system for various purposes. For example, such information can be used to accurately predict the user's future blood glucose levels (e.g., when insulin is the infusate), which can be used in a control algorithm used to automate infusate delivery.


Third, some embodiments of the infusion pump system may include an analyte sensor. In some cases, the analyte can be used to determine an alarm threshold for triggering an occlusion alarm. For example, when insulin is the infusate, a rising blood glucose level can indicate the possibility of a new occlusion, thus a rising blood glucose trend may indicate a higher probability of an occlusion, thus an alarm threshold can be lowered so that an occlusion alarm is triggered sooner. If a PWD's blood glucose level is steady at a target level or within a target range, however, it may not be necessary to trigger an occlusion alarm as quickly if the occlusion may self-resolve. Optionally, rather than merely changing the alarm threshold for an occlusion alarm, analyte sensor data can be used to determine if an additional administration of infusate is safe. For example, if insulin is the infusate and the user is a PWD, then analyte sensor data can be used to determine if the administration of an additional dose of insulin is safe for the PWD based on the PWD's insulin sensitivity factor (ISF) and an amount of insulin stuck-in-transit (IST). For example, if an insulin pump is determined to have a back pressure corresponding to 0.5 units of IST, that can be used to determine if that IST plus an additional administration of 0.2 units is likely to send the user into a hypoglycemic condition. If it is determined to be safe, it can be delivered to see if the pressure continues to increase in a way consistent with a non-resolving occlusion. In some cases, the additional administration can be designed to send the back pressure to an amount above an occlusion alarm threshold if the additional administration does not cause the occlusion to resolve. In particular embodiments, methods, systems, and devices provided herein can evaluate a pressure increase after the additional administration to evaluate if the increase is consistent with a non-self-resolving occlusion. In some implementations, data from an analyte sensor can be used in the automation of infusate delivery, but the pressure sensor can be used to stop the automatic delivery of extra infusate above a baseline amount when an occlusion is suspected. For example, when insulin is the infusate, data from a continuous glucose monitor (CGM) for a PWD can be used to stop insulin delivery, methods, devices, and systems provided herein that can deliver insulin at a preprogrammed basal rate, at one or more larger rates, and optionally at one or more lower rates (which can be a rate of zero). In some cases, such methods, devices, and systems can prevent the delivery of the one or more larger rates of insulin delivery when a pressure sensor indicates a possible occlusion or a significant amount of IST, even before an occlusion alarm is triggered, which can prevent an amount of IST from becoming too large prior to an occlusion self-resolving. In these cases, additional insulin deliveries can be used during this period of time to test whether the occlusion condition is likely to self-resolve to determine whether to sound an occlusion alarm.


Third, some embodiments of the infusion pump system may include a pressure detection configuration that can be used to indicate whether a dispensation of infusate was actually delivered into the user's body (e.g., into the user's vasculature). For example, when an infusate is being dispensed into the user's body, the pressure in the infusate pathway will expectantly increase because of back pressure associated with the user's body. If, however, the infusate fluid flow line is not coupled to the user at the time of the infusate dispensation, no such back pressure will be present, and the pressure in the infusate pathway will therefore be less than expected. When a lower than expected infusate pathway pressure is detected during an infusate dispensation, the infusion pump system may ascertain that no infusate was delivered to the user because the infusate fluid flow line was not coupled to the user. In some cases, appropriate countermeasures can then be initiated by the infusion pump system, such as an alert or alarm to the user to prompt the user to properly install the infusate fluid flow line.


Fourth, some embodiments of the infusion pump system may be configured to be portable, wearable, and (in some circumstances) concealable. For example, a user can conveniently wear the infusion pump system on the user's skin under clothing or can carry the pump device in the user's pocket (or other portable location) while receiving the medicine dispensed from the pump device.


Thus, the embodiments described herein provide the benefit of a medicine delivery system that can better differentiate between occlusions that require user intervention and those that do not, and allowing users to gain better information regarding whether insulin is actually being delivered to the PWD.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is an exploded perspective view of an example diabetes management system.



FIG. 2A depicts details about an exemplary insulin pump.



FIG. 2B depicts details about an exemplary insulin pump controller of the exemplary insulin pump of FIG. 2A.



FIGS. 3A and 3B are schematic diagrams of an exemplary occlusion sensor.



FIGS. 4A and 4B are cross-sectional views of a portion of a fluid channel for the sensor of FIGS. 3A and 3B.



FIG. 5 depicts the details of a cap device of FIGS. 2A and 2B including an occlusion sensor.



FIGS. 6A-6C illustrate examples of how light can be directed at the occlusion sensor of the cap device of FIG. 5 to detect occlusions.



FIG. 7 is a flowchart of an example method for using the occlusion sensor to generate an occlusion alarm.



FIG. 8A is a graphical representation illustrating a relationship between data from an occlusion detector, pressure, and units of medication in the line.



FIG. 8B illustrates a possible relationship between a pressure sensor and units of medication in the line.



FIG. 8C illustrates a possible relationship between a force sensor and units of medication in the line.



FIGS. 9A and 9B illustrate an alternative example of an insulin pump.



FIG. 10 is a flowchart of an example method for triggering an occlusion alarm.



FIG. 11 is a flowchart of an example method for determining an amount of infusate on board.



FIG. 12 is a flowchart of an example method for determining if an infusion set is disconnected.





DETAILED DESCRIPTION

Medication delivery methods, devices, and systems provided herein can use occlusion sensor data to more quickly and/or more accurately identify occlusions, to improve the automation of medication delivery, use analyte data to improve the accuracy and timing of occlusion alarms, and can detect disconnected infusion sets. In some cases, methods, devices, and systems provided herein can use occlusion sensor data to distinguish between AMOB and medication stuck-in-transit (MST), which can be used to improve the automation of medication delivery. In particular embodiments, the medication delivery methods, devices, and systems, can be insulin delivery methods, devices, and systems. In some cases, methods, devices, and systems provided herein can be Automated Insulin Delivery (AID) methods, devices, and systems.



FIG. 1 provides an example of an infusion pump system 10 (also referred to herein as a diabetes management system (DMS)) that includes an infusion pump assembly 15, a mobile computing device 60, a continuous glucose monitor 50, and a blood glucose monitor 70. FIG. 2A depicts the infusion pump system 10 in greater detail. FIG. 2B depicts the details of an exemplary pump controller device 200, which can be used with infusion pump system 10. While infusion pump system 10 is referred to herein as a DMS system, it should be understood that infusion pump system 10 is not limited to such a context. In some cases, the systems and methods may be adapted for use with additional chronic diseases or conditions, for example, unresponsive infections, cancer, cancer-related pain, chronic pain, gastrointestinal diseases or disorders, congestive heart failure, hemophilia, immune deficiencies, multiple sclerosis, and rheumatoid arthritis. Similarly, while the infusate delivered from infusion pump assembly 15 is referred to herein as insulin, it should be understood that other types of infusate may also be delivered using infusion pump assembly 15. The DMS 10 and methods provided herein may be used and performed, respectively, by a user, for example, a type 1 or 2 diabetes patient or a caregiver of a diabetes patient.


Additional details about DMS 10 is discussed below in reference to FIGS. 1, 2A, and 2B. FIGS. 3A-6C depict the particular occlusion sensor used in DMS 10, and illustrate how it can work. FIG. 7 is a flowchart depicting how an occlusion can be detected using the occlusion sensor of FIGS. 3A-6C. These are discussed in greater detail below. Moreover, details about the occlusion sensor is additionally described in U.S. Pat. No. 8,808,230, which is hereby incorporated by reference. Other occlusion sensing arrangements are also described in U.S. Pat. Nos. 8,790,294; 7,828,528; and 8,852,141, which are hereby incorporated by reference.



FIGS. 9A and 9B depict an alternative infusion device 900, which can include a force sensor as part of a drive system to detect possible occlusion conditions. In some cases, infusion device 900 can be incorporated into DMS 10 in place of infusion pump assembly 15, or may be used in place of both infusion pump assembly 15 and mobile computing device 60. As described below, data from the force sensor can be used to detect possible occlusion conditions and to determine when to trigger an occlusion alarm. Additionally, in particular embodiments, data from the force sensor can be used to trigger an additional dosage of infusate (if that additional dosage is determined to be safe) to either cause the possible occlusion condition to resolve or trigger conditions that trigger an occlusion alarm. In some cases, a threshold for triggering the alarm using force sensor data can be variable based on data from an analyte monitor. In some cases, data from a force sensor can be sensitive enough to detect if an infusion set is disconnected.



FIG. 8A illustrates how occlusion sensor data from a sensor described below in relation to FIGS. 3A-6C can be correlated to a pressure. FIG. 8B graphically illustrates how discrete dosage amounts can increase the pressure detected when a pump is in an occluded condition. FIG. 8C graphically illustrates how discrete dosage amounts can increase the force detected with a pump is in an occluded condition. Occlusion sensors and infusion pumps can be tested to determine the behavior of the occlusion sensor/infusion pump when infusate is pumped into the catheter when the catheter is in a fully occluded condition (e.g., by clamping an end of an infusion catheter while pumping infusate). FIG. 8A is specific for an occlusion sensor described below in regards to FIGS. 3A-6C, but can be applicable to other occlusion sensors, such as force sensors. FIG. 8B generically depicts an expected change in data from a pressure sensor in response to a fully occluded condition as additional units of medication are pumped. FIG. 8C depicts an expected change in data from a force sensor in response to a fully occluded condition as additional units of medication are pumped. These graphs are illustrative, and each infusion pump/occlusion detector arrangement may have different curves and different detection limits.



FIG. 10 is a flowchart illustrating an exemplary method for issuing occlusion alarms or additional dosages of infusate. FIG. 11 is a flowchart illustrating an exemplary method for determining when infusate is actually delivered and optionally determining an amount of infusate on board (or active medication on board (AMOB)). FIG. 12 is a flowchart illustrating an exemplary method of determining issuing an occlusion alarm.


Methods, systems, and devices provided herein can use non-binary data from an occlusion sensor, which can be a pressure sensor or a force sensor, to more quickly identify occlusion condition in an infusion pump that require user intervention, to minimize alarms issued for self-resolving occlusion conditions, and to optionally trigger administrations of medication designed to safely test whether a non-self-resolving occlusion condition exists. Additionally, methods, systems, and devices provided herein can use non-binary data from an occlusion detector to improve the automation of medication delivery by having more accurate information about an amount of active medication on board (AMOB) by knowing an amount of medication stuck-in-transit (MST).


Determining when Medication has been Delivered


Methods, devices, and systems provided herein can use non-binary occlusion detector data to determine an amount of infusate on board or active medication on board (AMOB) by determining an amount of medication stuck-in-transit (MST). In some cases, the medication can be insulin, and methods, devices, and systems provided herein can determine an amount of Insulin-on-Board (IOB) or some other calculation of active insulin by determining an amount of Insulin Stuck-in-transit (IST). In describing these concepts, the description below references the charts of FIGS. 8A-8C to help illustrate the concepts.


Medications such as insulin typically have activity profiles which differ depending on the specific medication, and can depend on how it is delivered, the specific biochemistry of the patient, and other factors. AMOB is an estimation of how much active medication remains in the patient, and can be used to determine whether an additional administration of medication is safe and/or recommended. For example, IOB is a calculation of an amount of active insulin remaining in a person with diabetes (PWD), and can be used by the PWD to determine if the PWD should administer an additional bolus. In some cases, automated insulin delivery systems can monitor data from a glucose monitor and use that data along with a calculation of IOB to determine a subsequent insulin dosage (e.g., a bolus or a basal adjustment). Because an estimation of AMOB requires knowledge of when the medication was delivered, better data on when medication was delivered can produce more accurate estimations of an amount of AMOB. Accordingly, data from an occlusion detector can be used to determine an amount of MST.


Referring to FIG. 8A, data from a light detector in an occlusion detector can be correlated to a number of units of medication delivered for that particular infusion device, producing a chart 800. Accordingly, once the occlusion detector detects anything beyond the detection limit at 811, which corresponds to about 4 unit increments, methods, devices, and systems provided herein can determine that about 4 unit increments of medication are stuck-in-transit, thus 4 unit increments can be subtracted from the AMOB. If the pressure continues to increase such that the light detector only detects about 30% light, methods, systems, and devices provided herein can determine that about 5 unit increments of medication are stuck-in-transit by correlating point 812 along curve 810, thus avoiding adding that medication to the AMOB. If the pressure continues to increase such that an alarm threshold is met, such as an amount of light detected being less than 10% as shown, then an occlusion alarm might sound, which can trigger the user to replace the infusion set. If an infusion set is replaced, methods, systems, and devices can avoid adding the MST to the AMOB, thus improving the administration of medication after the infusion set is replaced. In some cases, an occlusion condition may self-resolve prior to reaching the alarm threshold, such that methods, systems, and devices provided herein can add the MST, or a portion thereof, to the AMOB and/or determine the timing of the MST admiration. As shown in FIG. 8A, some occlusion sensors might not be configured to detect any data when a pressure is below a detection limit, thus the light detector does not detect the occlusion for the first 3 clicks, thus below the detection limit, the curve is flat at 815. In some cases, occlusion detectors can be more sensitive and detect small pressure increases, thus reducing or eliminating flat section 815 for their detection curve.


Referring to FIG. 8B, data can be collected from a generic pressure sensor, which can be a pressure sensor that uses reflected light or any other type of pressure sensor. This collected pressure date is used to determine a pressure curve for a particular infusion pump such as shown as chart 820. Again, this chart can be developed by testing an infusion pump in a fully occluded condition. Similar to chart 800, chart 820 can have a detection limit and an alarm threshold, and can correlate a plurality of points 831-834 along curve 830 so that a detected pressure corresponds to a number of unit increments of medication stuck-in-transit (MST), which can similarly be used to produce a better determination of AMOB.


Referring to FIG. 8C, data can be collected from a force sensor, such as that described below in reference to FIGS. 9A and 9B. This collected force sensor data is used to determine a force curve for a particular infusion pump such as shown as chart 840. Again, this chart can be developed by testing an infusion pump in a fully occluded condition. Similar to charts 800 and 820, chart 840 can have a detection limit and an alarm threshold, and can correlate a plurality of points 851-855 along curve 850 so that a detected force corresponds to a number of unit increments of medication stuck-in-transit (MST), which can similarly be used to produce a better determination of AMOB.


In some cases, these curves can depend on the material(s) and/or length(s) of the particular infusion catheter or infusion sets used, thus in some cases, methods, devices, and systems provided herein can use data about a particular infusion set or infusion catheter being used to make adjustments to the correlation between occlusion sensor data and a determined amount of MST. The detection limit of each sensor can be due to compliance in the sensor design.


Referring to FIG. 11, an example method 400 can be used for operating an infusion pump system configured with an infusate pressure detection system (as described above) in regards to FIGS. 8A-8C. Such an infusion pump system may include one or more sensors for detecting a fluid pressure within the infusate flow pathway (e.g., within an infusion set). As discussed above, data from any occlusion sensor, including a light detecting occlusion sensor or a force sensor, can be correlated to a pressure.


Method 400 begins at step 410 with the initiation of a dispensation of infusion fluid. For example, in some embodiments, step 410 can comprise an activation (by an infusion pump controller) of a drive system of the infusion pump with the purpose of dispensing a particular amount of infusate to the user of the infusion pump. In some examples, a particular number of units of infusate (e.g., the medication, which can be insulin) may be intended to be delivered to the user by virtue of the activation of the infusion pump drive system. The drive system of the infusion pump can be designed to dispense an accurately controlled amount of infusate. The controller of the infusion pump can initiate and control the activation of the pump drive system so that a targeted (intended) amount of infusate is dispensed as a result of the activation (assuming there are no unintended occlusions within the infusate flow path).


At step 420, the fluid pressure within the infusate flow pathway is detected by the controller of the infusion pump. The pressure detection may be performed using various devices and techniques, as described herein. In some cases, pressure signals are collected on a periodic basis (e.g., once per second, once per 5 seconds, once per 10 seconds, once per 20 seconds, once per 30 seconds, once per 45 seconds, once per minute, less frequently than once per minute, and the like, and within ranges thereof). In some cases, pressure signals may be collected multiple times during the actuation of the mechanical delivery to characterize the pressure profile during the delivery. Signals from pressure detectors can be sent to and received by a control circuitry of the infusion pump. The control circuitry can store the detected pressure signals in memory for analysis and processing. In some cases, the control circuitry stores a timestamp in association with the detected pressure signals. Hence, a time-based pressure profile of the fluid pressure within the infusate flow pathway can be created by the control circuitry. Such data can be further analyzed and processed by the control circuitry. For example, the data can be compared to threshold values, the data can be analyzed to identify times when changes in pressure occurred, the data can be analyzed to identify trends, and the like.


At step 430, the controller of the infusion pump determines the time and amount of infusate deliveries. The controller can use the pressure data collected in step 420 to perform step 430. As described further in the following example, using the pressure data collected in step 420 can, in some cases, enhance the accuracy of the determination of the time and amount of infusate deliveries (as compared to merely relying on the initiation of intended infusate deliveries from step 410). For example, an amount of MST can be determined based on a detected pressure or a pressure estimate based on a force sensor or other type of occlusion sensor, and the amount of MST can be excluded from a calculation of AMOB. Such accuracy enhancements can provide user advantages such as better management of blood glucose levels.


For example, the controller in step 430 can identify an occlusion in the infusate flow pathway by measuring and analyzing the fluid pressure within the infusate flow pathway during such a dispensation. Additionally, fluid pressure within the infusate pathway can be due to hydrostatic pressure. Infusate dispensations (timing and amount) that are affected by partial occlusions, transient occlusions, and/or hydrostatic pressure can be identified by the controller by measuring and analyzing the fluid pressure within the infusate flow pathway after the pump drive mechanism is activated for such a dispensation. For example, in some cases a transient occlusion can reside in the infusate flow pathway. When a transient occlusion resides in the infusate flow pathway, an intended dispensation will be initially partially or fully prevented from actually reaching the user, but later (after the occlusion is obviated) the intended dispensation will be actually delivered. By measuring and analyzing the fluid pressure within the infusate flow pathway during such a dispensation, the infusion pump control circuitry can identify the amount(s) and time(s) when the infusate was actually delivered to the user. Similarly, an altitude difference between the infusion pump and infusion site can result in back pressure and result in MST until the height difference is eliminated. Such information about MST can be advantageous, for example, to calculate the insulin-on-board for a user and in algorithms that use insulin-on-board as a parameter for managing the user's blood glucose level. Insulin-on-board is a term of art generally describing an amount of insulin that has been dosed to the user but whose blood glucose lowering effect has not yet occurred due to delayed action in the pharmacodynamics of subcutaneously infused insulin.


When a transient occlusion resides in the infusate flow pathway, a dispensation will cause the infusate pressure to rise and remain above the steady-state level for period of time that is longer than normal (here “normal” refers to the scenario with no unintended occlusions in the infusate flow pathway). Subsequently, at some time thereafter, the infusate pressure will reduce to the normal the steady-state level (indicating that the entire amount of infusate has then actually been delivered). By measuring and analyzing the fluid pressure within the infusate flow pathway during such a dispensation, the control circuitry can identify such an occurrence and can ascertain the time(s) when the infusate was actually delivered.


In some cases, the lack of temporary back pressure during a pumping operation may indicate that an infusion set is disconnected and that the user is not receiving medication, or that the infusion site is much lower in altitude than the infusion pump. Typically, a dispensation of infusate will result in a short-lived rise in the fluid pressure within the infusate flow pathway. The rise will occur while the infusate is flowing from the infusion pump to the user. During such flows, the pressure will rise from a steady-state pressure level and then return to approximately the same steady-state pressure level when the dispensation has been completed. By measuring and analyzing the fluid pressure within the infusate flow pathway during such a dispensation, if there is a pressure sensor sensitive enough to detect this temporary back pressure during a pumping operation, the infusion pump control circuitry can confirm that the intended amount of infusate was actually delivered to the user at the intended time. By extension, the control circuitry can also identify deviations from such intended infusate dispensations (timing and amount) by measuring and analyzing the fluid pressure within the infusate flow pathway during such a dispensation, and query the user to check that the infusion site is properly installed and/or the relative heights of the infusion pump and the infusion site.


A repetitious loop can exist between steps 430 and 420. That is, pressure detection and pressure data analysis can be repeated again and again to ascertain accurate knowledge (by the infusion pump controller) of the timing and amounts of the actual deliveries of the infusate to the user.


In optional step 440, the controller can determine an amount of active medication on board (AMOB), which can also be referred to as infusate on board, using the information determined in previous step 430. This step is just one example of how the information determined in previous step 430 can be used in an advantageous manner. The effectiveness of blood glucose management by a closed-loop infusion pump system (and/or an open-loop system) is negatively affected when intended dispensations of insulin are not actually delivered to the user. Such a situation is exacerbated when the device or person(s) making decisions about the times and amounts of future dispensations of insulin is/are unaware of the discrepancies between the intended and actual dispensations. Hence, method 400 provides awareness of such discrepancies, and the awareness can be put to practical use here in step 440. For example, in the case of a transient occlusion as described above, some or all of the insulin dispensation was delayed (i.e., some or all of the insulin dispensation occurred later than at the intended time). As such, the user's blood glucose level may be above a targeted level for longer than expected (because the delayed insulin has not yet been metabolized). If the fact that the dispensation was merely delayed as a result of a transient occlusion is known by the decision-maker (either device or person(s)), the decision-maker will not “over-react” by initiating an unneeded or excessive dispensation to bring the blood glucose level down. Instead, the decision-maker will understand that the user has the insulin-on-board as needed to perhaps eventually bring the blood glucose level down to the targeted level.


Detecting Disconnected Infusion Set


In some cases, certain occlusion detectors with detection thresholds that permit the detection of transient pressure increases during the pumping of infusate or medication can be used to determine if an infusion set is disconnected to trigger an alarm. Referring to FIG. 12, an example method 500 can be used for operating an infusion pump system configured with an infusate pressure detection system (as described above). Such an infusion pump system may include one or more sensors for detecting a fluid pressure within the infusate flow pathway (e.g., within an infusion set).


Method 500 can be used to detect whether a dispensation of infusate was actually delivered into the user's body (e.g., subcutaneously). For example, when an infusate dispensation is being made into the user's body, the pressure in the infusate pathway will expectantly increase because of back pressure associated with the user's body. If, however, the infusate fluid flow line is not coupled to the user at the time of the infusate dispensation, no such back pressure will be present, and the pressure in the infusate pathway will therefore be less than expected. When a lower than expected infusate pathway pressure is detected during an infusate dispensation, the infusion pump system may ascertain that no infusate was delivered to the user because the infusate fluid flow line was not coupled to the user. In some cases, appropriate countermeasures can then be initiated by the infusion pump system, such as an alert or alarm to the user to prompt the user to properly install the infusate fluid flow line.


Method 500 begins at step 510 with the initiation of a dispensation of infusion fluid. For example, in some embodiments, step 510 can comprise an activation (by an infusion pump controller) of a drive system of the infusion pump with the purpose of dispensing a particular amount of infusate to the user of the infusion pump. In some examples, a particular number of units of insulin may be intended to be delivered to the user by virtue of the activation of the infusion pump drive system. The drive system of the infusion pump can be designed to dispense an accurately controlled amount of infusate. The controller of the infusion pump can initiate and control the activation of the pump drive system so that a targeted (intended) amount of infusate is dispensed as a result of the activation (assuming there are no unintended occlusions within the infusate flow path).


At step 520, the fluid pressure within the infusate flow pathway is detected by the controller of the infusion pump. The pressure detection may be performed using various devices and techniques, as described above. In some cases, pressure signals are collected on a periodic basis (e.g., between every discrete dispensing operation, once per second, once per 5 seconds, once per 10 seconds, once per 20 seconds, once per 30 seconds, once per 45 seconds, once per minute, less frequently than once per minute, and the like, and within ranges thereof). In some cases, pressure signals may be collected multiple times during the actuation of the mechanical delivery to characterize the pressure profile during the delivery. Signals from pressure detectors can be sent to and received by a control circuitry of the infusion pump. The control circuitry can store the detected pressure signals in memory for analysis and processing. In some cases, the control circuitry stores a timestamp in association with the detected pressure signals. Hence, a time-based pressure profile of the fluid pressure within the infusate flow pathway can be created by the control circuitry. Such data can be further analyzed and processed by the control circuitry. For example, the data can be compared to threshold values, the data can be analyzed to identify times when changes in pressure occurred, the data can be analyzed to identify trends, and the like.


When an infusion set is properly coupled to the user, a dispensation of infusate will result in a short-lived rise in the fluid pressure within the infusate flow pathway. The pressure rise will result because of back-pressure from the user's body (e.g., vasculature), and occur while the infusate is flowing from the infusion pump to the user. During such flows, the pressure will rise from a steady-state pressure level and then return to approximately the same steady-state pressure level when the dispensation has been completed. By measuring and analyzing the fluid pressure within the infusate flow pathway during such a dispensation, the infusion pump control circuitry can confirm that the infusion set is coupled to the patient. By extension, the control circuitry can also identify deviations from such intended infusate dispensations by measuring and analyzing the fluid pressure within the infusate flow pathway during such a dispensation. The analysis of the pressure level during the actuation of the delivery may include characterizing any number of metrics such as the shape of the pressure profile during delivery, the maximum pressure level during delivery, the time to return to within some percentage of base pressure level, etc.


At step 530, the controller can determine whether the fluid pressure within the infusate flow pathway actually exhibited the aforementioned expected short-lived rise in the fluid pressure (which indicates that the infusion set is coupled to the user). If the infusion set is not coupled to the user, little back-pressure will exist and therefore the fluid pressure within the infusate flow pathway will not rise to the expected level during a dispensation. When such a scenario occurs, the controller can ascertain that the infusion set is not coupled to the user. Other measured metrics such as the shape of the pressure profile or the time to return to base pressure level may also be used to infer whether the infusion set is not coupled to the user.


A repetitious loop can exist between steps 530 and 510. That is, infusate dispensations and pressure data analysis can be repeated to ascertain accurate, ongoing knowledge (by the infusion pump controller) of whether the infusion set is coupled to the user.


At step 540, in response to an identification by the controller that the infusion set is not coupled to the user, the controller can initiate a notification to the user. Such a notification can be an alarm or alert of various types such as described above in regard to occlusion detection.


Timing Occlusion Alarms


In some cases, methods, devices, and systems provided herein can use different alarm thresholds for an occlusion detector based on data received from an analyte sensor. In some cases, methods, devices, and systems provided herein can use different alarm thresholds for an occlusion detector based on whether a bolus of medication has recently been delivered. In some cases, methods, devices, and systems provided herein can have an alarm threshold be adjusted based on the age of an infusion set. As such, the alarm thresholds in FIGS. 8A-8C can be shifted to the left or right based on data from an analyte sensor, data about the age of an infusion set, and/or data on recent medication delivery data. For example, in some cases, a changing or out-of-range analyte level may indicate that an occlusion condition is impacting the therapy regime for the patent and thus render a quicker remediation of the occlusion condition prudent, and thus an alarm threshold can be reduced in order to cause an occlusion alarm to trigger more quickly. In some cases, an analyte level being within range may indicate that the lack of delivery of medication is less dangerous, and thus the alarm threshold can be increased. For example, in the case of an insulin pump using data from a glucose monitor, a high or rising blood glucose level can cause an alarm threshold to be reduced, while a low or decreasing blood glucose level can be used to increase the alarm threshold and/or suspend insulin delivery. Additionally, a recent meal announcement can be considered in adjusting thresholds for a PWD. Additionally, some infusion sets for insulin pumps may have an intended use of between 2 and 7 days, and methods, systems, and devices may be adapted to receive data regarding when the infusion set was last changed, thus an alarm threshold may be reduced based on the age of the infusion set and/or whether or not it is older than a designated use life. Additionally, particular infusion sites may become more prone to occlusions as time passes, thus methods, systems, and devices may be adapted to receive data regarding the particular infusion site and how long it has been used, thus an alarm threshold may be reduced based on how long the particular infusion site has been used (e.g., the number of days it has been used).


In some cases, methods, devices, and systems provided herein can test a detected occlusion condition to determine if it is a self-resolvable occlusion condition and/or if it is the type of occlusion condition that requires user intervention. Accordingly, the test can determine if an occlusion alarm should be raised more quickly (e.g., if it requires user intervention) or if the alarm should be delayed in order to allow the occlusion condition to possibly self-resolve. In some cases, methods, devices, and systems provided herein can use analyte data to determine if the test is safe and/or whether it is safe to delay the alarm. In some cases, the test can include the administration of additional medication and an observation of occlusion sensor data to determine if a resulting increase in pressure (or force or change in light) indicates that the occlusion condition is complete and/or whether the occlusion condition is likely to self-resolve. For example, referring to FIG. 8A, a detection of light at a point between 811 and 812 can trigger an administration of one or more unit increments of medication to determine if the resulting change in light detected tracks the shape of curve 810. If there is a complete occlusion, a resulting light detected should move along curve 810, but if there is some release of pressure due to a partial occlusion, then the light detected will not by an amount corresponding to curve 810, which may indicate that medication is still be delivered and that the occlusion may self-resolve. Similarly, changes in pressure (FIG. 8B) and force (FIG. 8C) for a full occlusion corresponding to a delivery of one unit of medication would track curves 830 and 850 respectively for a complete occlusion. In some cases, the increase in pressure can cause the occlusion to self-resolve, thus a delay in testing the light, pressure, and/or force can be delayed for a predetermined amount of time. In some cases, an occlusion alarm can be triggered if a change in light, pressure, and/or force before and after a test delivery of medication is above a threshold. In some cases, the test administration of medication can be a next scheduled dose or can be an additional, non-scheduled dose of medication.



FIG. 10 illustrates an exemplary flow chart 600 of a method of delivering medication/infusate (e.g., insulin) and determining whether to sound an occlusion alarm. In step 610, infusate is administered to the user based on a user's demand, based on an algorithm, or based on a preprogrammed schedule. For example, if the infusate is insulin, the insulin can be a bolus of insulin delivered by the user for a meal or a correction, or the insulin can be basal insulin delivered according to a preprogrammed schedule, or the insulin can be automated insulin delivery based on a control algorithm using data from a glucose sensor. In step 620, a pressure in the fluid pathway (or in a medication reservoir) is detected. This can be detected directly or by reference to another type of occlusion detector that correlates to pressure (e.g., a light detecting occlusion detector or a force detector). In step 630, a processor can determine if a detected pressure (or detected light or force) exceeds a first threshold value. In some cases, the first threshold value can be a detection limit value, such as those depicted in FIGS. 8A-8C. If the detected pressure (or detected light or force) is less than a first threshold value, the process returns to step 610 for a subsequent delivery of medication.


If the detected pressure (or detected light or force) is at or greater than the first threshold value, the processor detects whether the pressure is above a second alarm threshold value in step 640, which can be the alarm thresholds depicted in FIGS. 8A-8C. As discussed above, the alarm thresholds can vary based on analyte data and/or recent administrations of medication. For example, an alarm threshold can be increased immediately after a bolus of insulin and/or decreased if a user's blood glucose data is elevated or rising. In some cases, an alarm threshold immediately after a new infusion site insertion can be increased to accommodate for the initial back pressure that a new infusion site typically provides. If the pressure is above the second alarm threshold, methods, devices, and systems provided herein can sound an occlusion alarm in step 645. In some cases, a sounded occlusion alarm can be audible, visual, and/or haptic.


If the detected pressure (or detected light or force) is less than the second alarm threshold value but above the first threshold value, then step 650 can determine if an additional administration of infusate is safe. This additional administration can be off schedule infusate delivery or delivery that is not based on the algorithm reference above for step 610. In some cases, the additional administration of infusate can be a minimum medication unit increment based on the infusion pump. In some cases, the additional administration of infusate can be an amount of medication calculated to result in a pressure exceeding the second alarm threshold value if the infusion pump is fully occluded. In some cases, the additional administration can be a maximum amount calculated to be safe according to a predictive algorithm, which may be limited to a maximum amount. For example, in the case of insulin being delivered using the pumps depicted in FIGS. 1-6C, 9A, and 9B, an amount of an additional delivery of insulin may be between 0.05 units of insulin and 0.5 units of insulin. In step 650, an additional delivery of medication (which can be a predetermined amount) can be determined to be safe if a predictive algorithm predicts that the delivery of the additional medication (plus all of a calculated MST as discussed above) would result in a dangerous condition. For example, if the infusate/medication is insulin, a predictive algorithm that adds IST and the additional administration (e.g., between 0.05 and 0.5 units) of insulin to an estimated IOB and determines if that administration will cause the PWD to experience a hypoglycemic condition using a predictive algorithm, which may assume the continuation of insulin delivered according to a preprogrammed schedule or according to an algorithm.


If the additional administration in step 660 is not safe, then the procedure 600 can return to step 610 for the next administration of medication according a user request, to an algorithm, or according to a schedule.


If the additional administration is safe in step 660, additional infusate is delivered in step 670. In step 680, a pressure (or force or light) is detected again, and step 690 determines if the pressure rise (or lack thereof) is consistent with an occlusion. In some cases, step 680 can occur immediately after step 670. In some cases, step 680 can be delayed for a predetermined period of time after step 670. In some cases, the delay can be between 1 second and 5 minutes. In some cases, the delay can be at least 5 seconds, at least 10 seconds, at least 30 seconds, or at least 1 minute. In some cases, the delay can be less than 5 minutes, less than 3 minutes, or less than 2 minutes.


Step 690 can determine if the pressure increase is consistent with a non-self-resolving occlusion. In some cases, the additional delivery of infusate is calculated to be an amount likely to send the pressure above the second alarm threshold value and step 690 can merely detect whether the pressure (or force or light) detected in step 680 is at or above the second alarm threshold value. In some cases, step 690 can analyze a change in pressure (or light or force) to see if it is consistent with a curve indicating a total occlusion, such as example curves 810, 830, and 850 depicted in FIGS. 8A-8C. In some cases, a threshold for determining whether to alarm in step 645 after step 690 is a pressure (or force or light) change that is a percentage of a change predicted by an occlusion curve, such as curves 810, 830, and 850. If the pressure rise is not sufficient to indicate an occlusion condition in step 690, then the procedure 600 can return to step 610 for the next administration of medication according a user request, to an algorithm, or according to a schedule. In some cases, step 690 can analyze the pressure change to see if it is approximately steady state to determine if the back pressure could be due to hydrostatic pressure, which may trigger a non-disruptive tip, notice, or query to the user regarding the relative heights of the infusion pump and the infusion site.


Exemplary Medication Delivery System


Methods, devices, and systems provided herein can be used to deliver any suitable medication, and can include an infusion pump of any appropriate design that includes some sensor designed to detect an occlusion condition. In some cases, the occlusion sensor is a pressure sensor, a force sensor, or a sensor that is adapted to detect other changes to correlate to a pressure increase in a medication reservoir and/or an infusion catheter. In the examples discussed below, the methods, devices and systems are used to deliver insulin.


Referring back to FIG. 1, an infusate delivery system can be diabetes management system (DMS) 10 that includes an infusion pump assembly 15, a mobile computing device 60, a continuous glucose monitor 50, and a blood glucose monitor 70. Infusion pump assembly 15 includes an infusion set tubing 147 adapted to deliver an infusate (e.g., insulin) to an infusion set 146. As discussed above, the materials, lengths, and thicknesses (among other factors) of the infusion set tubing 147 can impact the shapes of curves correlating pressure to a volume of medication stuck-in-transit (MST) (such as insulin stuck-in-transit (IST)). As shown, a mobile computing device 60, in wireless communication with insulin pump assembly 15, can serve as the primary user interface. As shown, mobile computing device 60 displays user interface home screen 300, which can allow a user to see actionable data and send commands to pump assembly 15. In some cases, a mobile computing device 60 can be absent (or optional) and the infusion pump assembly 15 can include a primary user interface.


In some cases, an analyte sensor, such as continuous glucose monitor 50, can be used as part methods, systems, and devices provided herein to automate medication delivery, change occlusion alarm thresholds, and/or determine whether an additional delivery of medication is safe. As shown, insulin pump assembly 15 is in wireless communication with continuous glucose monitor 50 and data from continuous glucose monitor 50 can be transferred to the mobile computing device 60 via insulin pump assembly 15. In some cases, a blood glucose meter 70 can be in wireless communication with infusion pump assembly 15. Alternatively, other methods and paths of communication are contemplated, including wired communication. In some cases, a continuous glucose monitor 50 can be incorporated into a single unit with an infusion pump assembly.


In some embodiments, DMS 10 can be a closed-loop insulin delivery system that uses glucose data from continuous glucose monitor 50 and/or blood glucose monitor 70 in one or more feedback loops to change basal delivery rates, update parameters, settings, and/or models for dosage delivery that are specific to the user. In some cases, a pump controller (e.g., pump controller device 200) is part of pump assembly 15 and includes one or more processors adapted to alter basal delivery rates, change parameters, settings and/or models for dosage delivery based on glucose data from a continuous glucose monitor 50 and/or a blood glucose meter 70. In some cases, algorithms for changing basal delivery rates, update parameters, settings, and/or models for dosage delivery that are specific to the user can be present on mobile computing device 60 and/or on a remote server that is accessed by the mobile computing device 60 via the cloud.


Occlusion alarms or alerts discussed herein can be sounded using any suitable manner, which can include one or more of audible tones, haptic feedback, and/or visual indications, which can come from the pump assembly 15, mobile computing device 60, CGM 50, and/or BGM 70. In some cases, pump assembly 15 can include between one or more LED indicators adapted to light to inform the user of certain conditions, which can include an occlusion condition. In some cases, mobile computing device 60 can provide troubleshooting tips and/or instructions regarding how to resolve an occlusion if an occlusion alarm sounds. In some cases, the troubleshooting tips can include an audiovisual presentation illustrating one or more of (a) a depiction of how to check for kinks in an occlusion catheter; (b) checking the infusion site; (c) instruction to change the infusion set; and/or (d) questions about the last time the occlusion set was changed. Alternatively, the infusion pump assembly can include robust user interface that can provide the user with text instructions or suggestions regarding how to fix an occlusion.


In some cases, methods, systems, and devices provided herein can track when an infusion set was last changed and change alarm thresholds based on length of time that the infusion set has been used. In some cases, an infusion set age can be estimated based on actions that the user takes to prime the cannula of the infusion set (e.g., fill the infusion set catheter with infusate). In some cases, methods, devices, and systems provided herein can ask the user to input infusion set changes. Changing alarm thresholds based on infusion set age can improve user compliance with the labeled use of an infusion set. Additionally, non-self-resolving occlusions can become more common as an infusion set ages. In some cases, a troubleshooting guide provided to the user during/after an occlusion alarm can be different based on the age of an infusion set.


Mobile computing device 60 can be any of a variety of appropriate computing devices, such as a smartphone, a tablet computing device, a wearable computing device, a smartwatch, a fitness tracker, a laptop computer, a desktop computer, and/or other appropriate computing devices. In some cases, mobile computing device 60 can be used to transfer data from controller device 200 to the cloud. In some cases, the mobile computing device 60 provides a user interface (e.g., graphical user interface (GUI), speech-based user interface, motion-controlled user interface) through which users can provide information to control operation of the controller device 200 and the insulin delivery system 10. For example, the mobile computing device 60 can be a mobile computing device running a mobile app that communicates with the controller device 200 over short-range wireless connections (e.g., BLUETOOTH® connection, Wi-Fi Direct connection) to provide status information for the insulin delivery system 10 and to allow a user to control operation of the insulin delivery system 10 (e.g., toggle between delivery modes, adjust settings, log food intake, confirm/modify/cancel bolus dosages, and the like).


Continuous glucose monitor 50 can include a housing 52, a wireless communication device 54, and a sensor shaft 56. The wireless communication device 54 can be contained within the housing 52 and the sensor shaft 56 can extend outward from the housing 52. In use, the sensor shaft 56 can penetrate the skin 20 of a user to make measurements indicative of characteristics of the user's blood (e.g., the user's blood glucose level or the like). In some cases, the sensor shaft 56 can measure glucose or another analyte in interstitial fluid or in another fluid and correlate that to blood glucose levels. In response to the measurements made by the sensor shaft 56, continuous glucose monitor 50 can employ the wireless communication device 54 to transmit data to a corresponding wireless communication device 247 housed in the pump assembly 15. In some cases, the monitoring device 50 may include a circuit that permits sensor signals (e.g., data from the sensor shaft 56) to be communicated to the communication device 54. The communication device 54 can transfer the collected data to the controller device 200 (e.g., by wireless communication to the communication device 247). Alternatively, the monitoring device 50 can employ other methods of obtaining information indicative of a user's blood characteristics and transferring that information to the controller device 200. For example, an alternative monitoring device may employ a micropore system in which a laser porator creates tiny holes in the uppermost layer of a user's skin, through which interstitial glucose is measured using a patch. In the alternative, the monitoring device can use iontophoretic methods to non-invasively extract interstitial glucose for measurement. In other examples, the monitoring device can include non-invasive detection systems that employ near IR, ultrasound or spectroscopy, and particular implementations of glucose-sensing contact lenses. Invasive methods involving optical means of measuring glucose could also be added. In yet another example, the monitoring device can include an optical detection instrument that is inserted through the skin for measuring the user's glucose level. Furthermore, it should be understood that in some alternative implementations, the monitoring device 50 can be in communication with the controller device 200 or another computing device via a wired connection.


DMS 10 may optionally communicate with blood glucose meter 70 in addition to (or as an alternative to) continuous glucose monitor 50. For example, one or more test strips (e.g., blood test strips) can be inserted into a strip reader portion of blood glucose meter 70 and then receive blood to be tested. In some cases, blood glucose meter 70 is configured to analyze the characteristics of the user's blood and to communicate (e.g., via a BLUETOOTH® wireless communication connection) the information to the controller device 200. In some cases, a user can manually input a glucose meter reading. Blood glucose meter 70 can be manually operated by a user and may include an output subsystem (e.g., display, speaker) that can provide the user with blood glucose readings that can be subsequently entered into the controller or user interface (to collect the data from an unconnected BGM into the system). Blood glucose meter 70 may be configured to communicate data (e.g., blood glucose readings) obtained to the controller device 200 and/or other devices, such as the mobile computing device 60. Such communication can be over a wired and/or wireless connection, and the data can be used by the controller device 200 and/or the mobile computing device 60 to perform multiple delivery modes and/or a secondary feedback loop for the insulin delivery system 10.


DMS 10 may include one or more external medication delivery devices 80 (e.g., syringe, an insulin pen, a smart syringe with device communication capabilities, or the like) through which additional medicine dosages (e.g., insulin, glucagon) can be manually administered to a user. In some cases, user interfaces provided herein allow users to input a medication, a dosage amount, and the timing so that a closed-loop control algorithm can account for the additional medication. In some cases, mobile computing device 60 can make a recommendation for an amount of insulin to be delivered using an external delivery device.


Still referring to FIGS. 1, 2A, and 2B, in some embodiments pump assembly 15 can include pump device 100 configured to removably attach to the controller device 200 in a manner that provides a secure fitting, an overall compact size, and a reliable electrical connection. Pump assembly 15 can be pocket-sized so that the pump device 100 and controller device 200 can be worn in the user's pocket or in another portion of the user's clothing. In some circumstances, the user may desire to wear the pump assembly 15 in a more discrete manner. Accordingly, the user can pass the infusion set tubing 147 from the pocket, under the user's clothing, and to the infusion site where the adhesive patch can be positioned. As such, the pump assembly 15 can be used to deliver medicine to the tissues or vasculature of the user in a portable, concealable, and discrete manner.


In some cases, the pump assembly 15 can be configured to adhere to the user's skin directly at the location in which the skin is penetrated for medicine infusion. For example, a rear surface of the pump device 100 can include a skin adhesive patch so that the pump device 100 can be physically adhered to the skin of the user at a particular location. In these cases, the cap device 130 can have a configuration in which medicine passes directly from the cap device 130 into an infusion set 146 that is penetrated into the user's skin. In some examples, the user can temporarily detach the controller device 200 (while the pump device 100 remains adhered to the skin) so as to view and interact with the user interface.


The pump device 100 in this example includes a housing structure 110 that defines a cavity 116 in which a fluid cartridge 120 can be received. The pump device 100 also can include a cap device 130 to retain the fluid cartridge 120 in the cavity 116 of the housing structure 110. The pump device 100 can include a drive system (e.g., including a battery powered actuator, a gear system, a drive rod, and other items that are not shown) that advances a plunger 125 in the fluid cartridge 120 so as to dispense fluid therefrom. In this example, the controller device 200 communicates with the pump device 100 to control the operation of the drive system. Optionally, the controller device 200 may be configured as a reusable component that provides electronics and a user interface to control the operation of the pump device 100. In such circumstances, the pump device 100 can be a disposable component that is disposed of after a single use. For example, the pump device 100 can be a “one time use” component that is thrown away after the fluid cartridge 120 therein is exhausted. Thereafter, the user can removably attach a new pump device (having a new fluid cartridge) to the reusable controller device 200 for the dispensation of fluid from a new fluid cartridge. Accordingly, the user is permitted to reuse the controller device 200 (which may include complex or valuable electronics, as well as a rechargeable battery) while disposing of the relatively low-cost pump device 100 after each use. Such a pump assembly 15 can provide enhanced user safety as a new pump device (and drive system therein) is employed with each new fluid cartridge. Additional and/or alternative implementations of the controller device 200 are also possible, including magnetic drive turbine (MDT) monolithic architecture pumps and/or omnipods.


The pump assembly 15 can be a medical infusion pump assembly that is configured to controllably dispense a medicine from the fluid cartridge 120. As such, the fluid cartridge 120 can contain a medicine 126 to be infused into the tissue or vasculature of a targeted individual, such as a human or animal patient. For example, the pump device 100 can be adapted to receive a fluid cartridge 120 in the form of a carpule that is preloaded with insulin or another medicine for use in the treatment of Diabetes (e.g., Exenatide (BYETTA, BYDUREON) and liraglutide (VICTOZA) SYMLIN, or others). Such a fluid cartridge 120 may be supplied, for example, by Eli Lilly and Co. of Indianapolis, IN. Other examples of medicines that can be contained in the fluid cartridge 120 include: pain relief drugs, hormone therapy, blood pressure treatments, anti-emetics, osteoporosis treatments, or other injectable medicines. The fluid cartridge 120 may have other configurations. For example, the fluid cartridge 120 may comprise a reservoir that is integral with the pump housing structure 110 (e.g., the fluid cartridge 120 can be defined by one or more walls of the pump housing structure 110 that surround a plunger to define a reservoir in which the medicine is injected or otherwise received).


In some cases, the pump device 100 can include one or more structures that interfere with the removal of the fluid cartridge 120 after the fluid cartridge 120 is inserted into the cavity 116. For example, the pump housing structure 110 can include one or more retainer wings (not shown) that at least partially extend into the cavity 116 to engage a portion of the fluid cartridge 120 when the fluid cartridge 120 is installed therein. Such a configuration may facilitate the “one-time-use” feature of the pump device 100. In some cases, the retainer wings can interfere with attempts to remove the fluid cartridge 120 from the pump device 100, thus ensuring that the pump device 100 will be discarded along with the fluid cartridge 120 after the fluid cartridge 120 is emptied, expired, or otherwise exhausted. In another example, the cap device 130 can be configured to irreversibly attach to the pump housing 110 so as to cover the opening of the cavity 116. For example, a head structure of the cap device 130 can be configured to turn so as to threadably engage the cap device 130 with a mating structure along an inner wall of the cavity 116, but the head structure may prevent the cap device from turning in the reverse direction so as to disengage the threads. Accordingly, the pump device 100 can operate in a tamper-resistant and safe manner because the pump device 100 can be designed with a predetermined life expectancy (e.g., the “one-time-use” feature in which the pump device is discarded after the fluid cartridge 120 is emptied, expired, or otherwise exhausted).


Referring to FIGS. 2A and 2B, the controller device 200 can be removably attached to the pump device 100 so that the two components are mechanically mounted to one another in a fixed relationship. In some cases, such a mechanical mounting can also form an electrical connection between the removable controller device 200 and the pump device 100 (for example, at electrical connector 118 of the pump device 100). For example, the controller device 200 can be in electrical communication with a portion of the drive system (show shown) of the pump device 100. In some cases, the pump device 100 can include a drive system that causes controlled dispensation of the medicine or other fluid from the fluid cartridge 120. In some cases, the drive system incrementally advances a piston rod (not shown) longitudinally into the fluid cartridge 120 so that the fluid is forced out of an output end 122. A septum 121 at the output end 122 of the fluid cartridge 120 can be pierced to permit fluid outflow when the cap device 130 is connected to the pump housing structure 110. For example, the cap device 130 may include a penetration needle that punctures the septum 121 during attachment of the cap device 130 to the housing structure 110. Thus, when the pump device 100 and the controller device 200 are mechanically attached and thereby electrically connected, the controller device 200 communicates electronic control signals via a hardwire-connection (e.g., electrical contacts along connector 118 or the like) to the drive system or other components of the pump device 100. In response to the electrical control signals from the controller device 200, the drive system of the pump device 100 causes medicine to incrementally dispense from the fluid cartridge 120. Power signals, such as signals from a battery (not shown) of the controller device 200 and from the power source (not shown) of the pump device 100, may also be passed between the controller device 200 and the pump device 100.


Cap device 130 of the pump device 100 can be configured to mate with an infusion set 146. In general, the infusion set 146 can be a tubing system that connects the pump assembly 15 to the tissue or vasculature of the user (e.g., to deliver medicine into the tissue or vasculature under the user's skin). The infusion set 146 can include a flexible infusion set tubing 147 that extends from the pump device 100 to a subcutaneous cannula 149 that may be retained by a skin adhesive patch (not shown) that secures the subcutaneous cannula 149 to the infusion site. The skin adhesive patch can retain the subcutaneous cannula 149 in fluid communication with the tissue or vasculature of the user so that the medicine dispensed through the infusion set tubing 147 passes through the subcutaneous cannula 149 and into the user's body. The cap device 130 can provide fluid communication between the output end 122 (FIG. 2A) of the fluid cartridge 120 and the infusion set tubing 147 of the infusion set 146.


First Exemplary Occlusion Detector


Referring now to FIGS. 3A-6C, the pump assembly 15 can be equipped with a pressure sensor as part of cap device 130 that detects pressures in the infusate fluid flow path extending to the user. For example, the controller device 200 may include an optical sensor system 250 that detects the amount of light reflected from a portion of the cap device 130. In this embodiment, the optical sensor system 250 can detect changes in the amount of light reflected from the cap device 130 in response to an occlusion that causes an increase in the fluid pressure in the infusate fluid flow path. For example, as described below in connection with FIGS. 6A-6C below, the optical sensor system 250 may operate using the principle of total internal reflection.


Referring to FIG. 3A, the cap device 130 can have a multi-piece construction that provides a flow path from the medicine cartridge 120 to the infusion set tubing 147 (e.g., via an output port 139). At least a portion of the flow path through the cap device 130 may be monitored by the occlusion detection system 250 to determine if an occlusion exists downstream of the cap device 130 using the methods and procedures described herein. The multi-piece construction of the cap device 130 can facilitate proper alignment of the cap device 130 and proper engagement with the medicine cartridge 120 during attachment of the cap device 130 to the pump housing structure 110. For example, during attachment of the cap device 130 to the pump housing, a needle penetrator 133 attached to a portion of the cap device can be advanced toward the septum of the medicine cartridge 120 to pierce the septum and open a fluid flow path. The flow path for the medicine that is dispensed from the medicine cartridge 120 can pass through the needle penetrator 133, through a fluid channel 260 (described below), through the infusion set tubing 147, and to the user.


The fluid channel 260 arranged in the cap device 130 may include a secondary channel 262 that extends to a flexible membrane 265. In this embodiment, one side of the flexible membrane 265 is exposed to the fluid channel 260 (via the secondary channel 262) while the opposite side of the flexible membrane 265 is adjacent to an air cavity 267, which provides a volume into which the flexible membrane 265 can expand as pressure rises in the fluid channel 260. The flexible membrane 265 may comprise a flexible polymer material that bulges or otherwise deforms as the fluid pressure in the flow channel 260 rises and is preferably composed of silicon. As such, the flexible membrane 265 can flex into the air cavity 267 when the fluid pressure rises due to an occlusion in the flow path downstream of the fluid channel 260.


Referring to FIG. 3B, the occlusion detection system 250 may include a number of components that are housed in the controller device 200. For example, the occlusion detection system 250 may include one or more light emitters and a light sensor arranged on the sensor circuit 252 that is housed by the controller device 200, thereby permitting these components to be reused along with the controller device (while the relatively low cost components in the pump device 100 are discarded after the “one time use” of the pump device 100). In a preferred embodiment, the sensor circuit 252 includes a primary light emitter 253, a reference light emitter 255, and a light sensor 258.


The sensor circuit 252 can be arranged so that the cap device 130 is aligned with the light emitters 253, 255 and the light sensor 258 when the pump device 100 is attached to the controller device 200. It should be understood that the pump housing structure 110 and the controller housing 210 have been removed from FIGS. 9A and 9B for purposes of showing the relative position of the sensor circuit 252 (in the controller device 200 as shown in FIGS. 2 and 4) and the cap device 130 (attached to the pump housing structure 110 as shown in FIG. 1).


The sensor circuit 252 can be connected to the control circuitry 240 of the controller device 200 (FIG. 2A) via a flexible circuit substrate or one or more wires. In a preferred embodiment, the sensor circuit 252 connects with the main processor board via the flexible circuit substrate illustrated in FIGS. 6A-6C. As such, the control circuitry 240 can receive sensor signals and employ detection software stored in one or more memory devices to determine if an occlusion exists. If the sensor signals from the occlusion detection system 250 indicate that an occlusion exists in the fluid flow path, the controller device 200 can trigger an alert to inform the user. The alert may include a visual or audible alarm communicated via the user interface 220 of the controller device 200.


The light collector 256 can be made of any reflective material, preferably polished aluminum, and is designed to collect light from both the reference light emitter 255 and the primary light emitter 253. For example, apertures are advantageously constructed in the light collector 256 to allow light to reach the light sensor 258 from specific directions corresponding to light originating from the reference light emitter 255 and from the primary light emitter 253.


In some embodiments, the reference light emitter 255 can provide a reference light reading at the sensor 258, which can be advantageously compared to a light reading from the primary light emitter 253 for purposes of determining when a reduced light reading from the main light emitter 253 is caused by a buildup of fluid pressure in the fluid channel 260 (e.g., from an occlusion in the infusion set tubing 147) or is caused by some other reason not related to the presence of an occlusion (e.g., environmental conditions such as ambient temperature). For example, in some embodiments, the amount of light emitted from the primary light emitter 253 begins to degrade or otherwise changes with fluctuations in ambient temperature and ambient light condition. If the control circuitry was configured to rely upon the light sensor readings detected by the light sensor 258 from the primary light emitter 253 alone, such reductions in the amount of the light readings from the primary light emitter 253 would possibly induce false occlusion warnings (e.g., occlusion alerts where in fact the suboptimal temperatures are responsible for the reduced light readings and no occlusion is present in the infusion set tubing 147). In this embodiment, each of the primary light emitter 253 and the reference light emitter 255 are substantially equally affected by the fluctuations in ambient temperature and ambient light condition. Accordingly, a comparison of the amount of the light received from the primary light emitter 253 with the amount of the light received from the reference light emitter 255 (rather than an absolute light measurement from the primary light emitter 253 alone) can be employed to substantially reduce or eliminate the number of false occlusion warnings.



FIGS. 4A and 4B depict what happens when there is an occlusion in the device of FIGS. 3A and 3B. FIG. 4A depicts the normal operation of flow channel 260 when there is not an occlusion, represented by the two arrows. As shown, flexible membrane 265 is not expanded into air cavity 267, thus light is internally reflected when it meets the interface between internal light transmissive member 254 and air cavity 267. If there is an occlusion, as shown in FIG. 4B (illustrated by the X), fluid presses into secondary channel 262 to cause flexible membrane 265 to expand and press against the internal light transmissive member 254, which can cause the light to not reflect. The thickness of air cavity 267 can determine the sensitivity of the sensor. For example, referring back to FIG. 8A, the length of curve segment can be changed, thus the detection limit can be changed, by changing the thickness of air cavity 267. Additionally, the flexibility and elasticity of flexible membrane 265 can change the sensitivity of the sensor. After the pressure increases such that any portion of the flexible membrane 265 touches internal light transmissive member 254, additional pressure will cause the diameter of the portion of flexible membrane 265 touching internal light transmissive member 254 to expand, thus less light will be reflected with increasing pressures. FIG. 8A depicts a possible correlation between an amount of light reflected (listed as a percentage) and an approximate pressure within fluid channel 260.



FIG. 5 is an exploded view of the cap device 130, in accordance with some embodiments. Internal light transmissive member 254 can be affixed to the remaining components of the cap device 130 using a bonding material 266, such as an adhesive film or glue. The flexible membrane 265 is positioned to form a seal between the fluid channel 262 and light transmissive member 254. That is, once the flexible membrane 265 is assembled into the cap device 130, the flexible membrane 265 deforms in response to a buildup of fluid pressure in the fluid channel 260 (which is communicated via the secondary channel 262), but does not allow fluid in the fluid channel 260 to escape pass the flexible membrane 265 into the air cavity 267 or otherwise interfere with other components of the pump device 100 or the controller device 200.



FIGS. 6A-6C illustrate how the light works in the occlusion detector. FIG. 7 is a flow chart illustrating a method of detecting an occlusion. As shown in FIGS. 6A and 6B, when no substantial pressure exists in the flow path, the medicine can be dispensed under normal operating conditions from the medicine cartridge 120, through the cap device 130, and into the infusion set tubing 147. As such, the flexible membrane 265 that is adjacent to the fluid channel 260 is not substantially deformed such that it deforms to touch internal light transmissive member 254, thus the occlusion detector system 250 does not detect any pressure. Referring to FIG. 6A, in some embodiments, the occlusion sensor system 250 may operate by activating the reference light emitter 255 in isolation from the primary light emitter 253. When the reference light emitter 255 is activated, the light is received by the light collector 256 and directed toward the light sensor 258 without passing through the light transmissive member 254 or any other portion of the cap device 130. For example, as shown in FIG. 6A, at least a portion of the light from the reference light emitter 255 (e.g., a wide-angle LED emitter in this embodiment) reflects off a surface of the light collector 256 and is received by the light sensor 258. In some cases, a generally opaque portion of the controller housing 210 may optionally prevent the light from the reference light emitter 255 from passing outside the controller housing 210. Here, because the reference light emitter 255 does not transmit light through the light transmissive member 254, the amount of light transmitted by the reference light emitter 255 and received by the light sensor 258 is generally unaffected by a buildup of fluid pressure in the fluid channel 260 (as will be described in more detail in reference to FIGS. 6B and 6C).


In other words, the amount of light emitted by the reference light emitter 255 and received by the light sensor 258 does not fluctuate according to fluid pressure but may fluctuate according to other environmental factors, such as ambient temperature (and it should be understood that primary light emitter 253 is similarly affected by these same environmental factors). This configuration can be employed to aid in the detection of an occlusion that accounts for changes in environmental factors affecting the primary light emitter 253. For example, when the infusion pump assembly 15 is operating in regions having lower ambient temperatures, both the reference light emitter 255 and the primary light emitter 253 will have reduced light outputs. In those circumstances, the occlusion detection system 250 can use the reduction in the amount of light from the reference light emitter 255 to account for the reduction in the amount of light from the primary light emitter 253. In other circumstances in which the light sensor 258 receives a reduced light signal only from the primary light emitter 253 while the light sensor 258 receive a normal light signal from the reference light emitter 255, then there is a greater likelihood of the presence of an occlusion and the user may be warned accordingly.


Referring to FIG. 6C, when the medicine flow path is in a non-occluded state under normal operating circumstances, the light from the light emitter 253 can be reflected at the interface where the internal light transmissive member 254 meets the air cavity 267. In some embodiments, this light reflection may occur due to total internal reflection that the interface. Total internal reflection can occur in some circumstances when light passes through a first medium (e.g., the internal light transmissive member 254) and strikes an interface between the first medium and a second medium (e.g., the air cavity 267) at an angle greater than the critical angle. If the refractive index of the second medium (e.g., the air cavity 267) is lower than refractive index of the first medium (e.g., the internal light transmissive member 254), the light may undergo total internal reflection within the first medium.


For example, as shown in FIG. 6B, the light emitter 253 can be an infrared light emitter that is directed toward the internal light transmissive member 254. The infrared light passes through the generally transparent first window 136 and then transmits through the light transmissive member 254. In some embodiments, the surface of the light transmissive member 254 may be curved and may operate as a focusing lens that directs the infrared light toward the air cavity 267 proximate to the fluid channel 260, although a non-curved surface is shown for the embodiments of FIGS. 6A-6C.


Referring still to FIG. 6B, when the medicine is dispensed under normal operating conditions below a detection limit (see FIG. 8A), the flexible membrane 265 does not flex downwardly into the air cavity 267 to abut the internal light transmissive member 254. Accordingly, the infrared light passing through the internal light transmissive member 254 reflects at the interface where the internal light transmissive member 254 meets the air cavity 267. This reflected light continues through the internal light transmissive member 254 toward the light sensor 258. In this embodiment, the reflected light transmitted through the light transmissive member 254 passes through the second window and is subsequently received by the light collector 256 (described in reference to FIGS. 9A and 9B) and directed toward the light sensor 258. The light sensor 258 may comprise an infrared photo detector that is capable of converting the receipt of infrared light into electrical signals. These electrical signals from the light sensor 258 can be transmitted via the sensor circuit 252 to the control circuitry for processing to determine if an occlusion alarm should be provided to the user.


Referring to FIG. 6C, when pressure in the flowpath exists exceeds a detection limit, the flexible membrane 265 can expand into air cavity 267 and touch internal light transmissive member 254, which can result in less light reflecting. As pressure builds, the area of the flexible membrane 265 touching internal light transmissive member 254 increases, thus less light is reflected. FIG. 6C illustrates the reduction of measurable light with dotted lines. FIG. 8A, discussed above, shows a hypothetical curve 810 for this arrangement, where a percentage of light reflected along the right axis corresponds to a pressure (left axis) and a number of clicks of insulin (bottom axis). For example, if pump device 100 attempts to dispense another incremental dosage of medicine when the infusion set tubing 147 is clogged or kinked, the fluid pressure upstream of the occlusion (e.g., in the medicine cartridge 120 and in the cap device 130) may be increased. As discussed above, occlusion alarm thresholds can be greater than the detection threshold, and can be variable, so that users do not become annoyed with unnecessary alarms.



FIG. 7 show process 1600 that can be performed for purposes of detecting the presence of an occlusion or elevated pressure in the medicine flow path to the pump user. The process 1600 may be at least partially implemented in an occlusion detection software algorithm that is stored on a memory device and executed by a processor of the control circuitry. In this embodiment, the control circuitry 240 may implement a first iterative step shown by box 1605 so to activate the wide-angle reference light emitter 255 to turn on in step 1602. For example, because the control circuitry 240 is in electrical communication with the reference light emitter 255, the control circuitry 240 can generate an electrical signal that when received by the wide-angle reference light emitter 255 causes the wide-angle light emitter 255 to emit light. In addition, the absence of the electrical signal may cause the reference light emitter 255 to deactivate.


In a step shown by box 1604, the control circuitry 240 detects a signal corresponding to the light emitted by the reference light emitter 255 and received by the light sensor 258. For example, light transmitted from the reference light emitter 255 may reflect off of the interior surface of the light collector 256 and interact with the light sensor 258. As described in more detail above, the light sensor 258 can generate an electrical signal corresponding to the received light. Because the control circuitry 240 is in electrical communication with the light sensor 258, the control circuitry 240 detects the signal corresponding to the light emitted by the wide-angle reference light emitter 255 when the control circuitry 240 receives the electrical signal from the light sensor 258. In a preferred embodiment, each of the detected signals corresponding to light emitted by the reference light emitter 255 is a floating point value within the range of [0-1] and is stored on one more dedicated memory devices included in the control circuitry 240.


In a decision shown by step 1606, the control circuitry 240 determines whether a minimum number of light samples transmitted by the wide-angle light emitter 255 has been received. For example, in a preferred embodiment, the control circuitry 240 determines whether sixteen iterations of activating the reference light emitter 255 and detecting the corresponding sixteen electrical signals from the light sensor 258 have been completed. If the minimum number of light samples has not been received, than the control circuitry 240 may instruct the reference light emitter 255 to activate again, repeating the steps included in the first iterative step shown by box 1605. In this embodiment, the sixteen iterations can be consecutively performed in a period of 0.5 seconds or less.


Once the minimum number of light samples has been received (e.g., sixteen in this embodiment), the control circuitry 240 may perform operation 1612 to determine an average detected value of the reference light emitter samples received. For example, in a preferred embodiment, because the control circuitry 240 receives sixteen light samples from the reference light emitter 255, the sixteen light samples are added together and the total divided by sixteen to determine the average detected value of the wide-angle reference samples received. In a preferred embodiment, the determined average value corresponding to light transmitted by the reference light emitter 255 is a floating point value within the range of [0-1] and is stored on one or more dedicated memory devices included in the control circuitry 240.


In a second iterative step shown by box 1620, the control circuitry 240 activates the primary light emitter 253 as shown in a step 1614. For example, because the control circuitry 240 is in electrical communication with the primary light emitter 253, the control circuitry 240 can generate an electrical signal that when received by the primary light emitter 253 activates the primary light emitter 253 to emit light. In addition, the absence of the electrical signal may instruct the primary light emitter 253 to deactivate.


In a step 1616, the control circuitry 240 can detect a signal corresponding to the light emitted by the primary light emitter 253 and received at the light sensor 258. For example, the light transmitted from the primary light emitter 253 that passes through the light transmissive member 254, may be reflected by the interface between the light transmissive member 254 and the air cavity 267 toward the light sensor 258. As described in more detail above, the light sensor 258 can generate an electrical signal corresponding to the received light. Because the control circuitry 240 is in electrical communication with the light sensor 258, the control circuitry 240 detects the signal corresponding to the light emitted by the primary light emitter 253 when the control circuitry 240 receives the electrical signal from the light sensor 258. In a preferred embodiment, each of the detected signals corresponding to the light emitted by the primary light emitter 253 is a floating point value within the range of [0-1] and is stored on one more dedicated memory devices included in the control circuitry 240.


Still referring to FIG. 7, the process may continue to a decision shown by box 1618, in which the control circuitry 240 determines whether a minimum number of light samples transmitted by the primary light emitter 253 has been received. For example, in a preferred embodiment, the control circuitry 240 determines whether sixteen iterations of activating the primary light emitter 253 and detecting the corresponding sixteen electrical signals from the light sensor 258 have been completed. If the minimum number of light samples has not been received, than the control circuitry 240 may activate the primary light emitter 253 again, thereby repeating the steps included in the second iterative step shown by box 1620.


Once the minimum number of light samples has been received, in a step shown by box 1622, the control circuitry 240 determines an average detected value of the primary light emitter samples received. For example, in a preferred embodiment, because the control circuitry 240 receives 16 light samples from the primary light emitter 253, the 16 light samples are added together and the total divided by 16 to determine the average detected value of the primary light emitter samples received. In a preferred embodiment, the determined average value corresponding to light transmitted by the primary light emitter 253 is a floating point value within the range of [0-1] and is stored on one or more dedicated memory devices included in the control circuitry 240.


The process 1600 for to determining whether to sound an occlusion alarm may include an operation that compares the detected value of the light emitted by the primary light emitter 253 with the detected value of the light emitted by the reference light emitter 253. For example, in this embodiment, the step 1624 indicates that the control circuitry 240 compares the average detected value of the light emitted by the primary light emitter 253 (determined by the step shown by box 1622) with the average detected value of the light emitted by the wide-angle reference light emitter 253 (determined by the step shown by box 1612). In one example of this comparison function, the average detected value of the light emitted by the primary light emitter 253 is divided by the average detected value of the light emitted by the wide-angle reference light emitter 255. Also, in particular embodiments, the resulting comparison value is a floating point value within the range of [0-1] and is stored on one more dedicated memory devices included in the control circuitry 240.


In an optional step shown by dashed box 1626, the control circuitry 240 normalized the comparison value determined in the step shown by box 1624. For example, in a preferred embodiment, the floating point comparison value in the range of [0-1] is multiplied by 100, normalizing the comparison value to an integer value in the range of [0-100]. These percentages make up the percentages show in the right axis of FIG. 8A.


Once a percentage is determined, it can be compared to one or more threshold values to determine whether to sound an occlusion alarm in step 1628. As discussed above, thresholds can be variable for the reasons discussed above. Moreover, it in some cases, the percentages calculated in step 1626 or some other comparison coming out of step 1624 can be used to estimate a pressure and/or make other decisions illustrated in FIGS. 10-12, which are discussed above. For example, the process 1600 includes a step 1628 in which the control circuitry 240 determines if the comparison value (e.g., either of the values determined by the step shown by box 1624 or the normalized comparison value determined in the step shown by box 1626) is outside a threshold range (e.g., less than or equal to a minimum threshold value, or greater than or equal to a maximum threshold value, or the like). The process 1600 can be performed immediately prior or immediately after each drive cycle of the pump device 100.


Exemplary Medication Delivery System Having Force Sensor



FIGS. 9A and 9B illustrate an alternative fluid infusion device 900 that includes a force sensor, which can be an insulin infusion device. FIG. 9A is an exploded perspective view and FIG. 9B is a cross-sectional view, which are simplified and does not include all of the elements, components, and features that would be present in a typical embodiment. Like infusion pump assembly 15 from FIG. 1, fluid infusion device 900 can automate medication delivery and/or can communicate with a CGM 50, a BGM 70, and/or a mobile computing device 60.


Fluid infusion device 900 is designed to be carried or worn by the patient. A fluid infusion device 900 accommodates a fluid reservoir 911 for the fluid to be delivered to the user. A length of tubing 908 is the flow path that couples the fluid reservoir to the infusion set (not shown). A removable cap or fitting 910 is suitably sized and configured to accommodate replacement of fluid reservoirs (which are typically disposable) as needed. In this regard, the fitting 910 is designed to accommodate the fluid path from the fluid reservoir to the tubing 908.


Fluid infusion device includes a housing 912 and a housing end cap 914 that is coupled to an end 916 of the housing 912 to enclose components within the housing 912. These internal components include, without limitation: a battery tube subassembly 918; a sleeve 920; a slide 921; an electronics assembly 922; a drive motor assembly 924 having a drive screw 925; a force sensor 926; and a motor support cap 928. Some components that are located outside the housing 912, namely, a keypad assembly 930 and a graphic keypad overlay 932 for the keypad assembly 930. The keypad assembly 930 and the graphic keypad overlay 932 may be considered to be part of a user interface of the fluid infusion device 900. The outer edge of the motor support cap 928 is attached to the interior side of the housing 912, and the motor support cap 928 contacts the force sensor 926 to remove assembly tolerances from the drive motor assembly 924. Fluid reservoir 911 is inserted into a reservoir cavity defined within the housing 912. The reservoir cavity is configured, sized, and shaped to accommodate fluid reservoirs, and the fluid reservoir 911 is maintained in the reservoir cavity using the fitting 910. The electronics assembly 922 may include a suitably configured electronics module, which may include or cooperate with a power supply, at least one memory element, at least one processor, processing logic, and device software, firmware, and application programs.



FIG. 9B depicts the state of the fluid infusion device 900 after the fluid reservoir 911 has been inserted into the reservoir cavity 934 and after the fitting 910 has been secured to the housing 912 to hold the fluid reservoir 911 in place. While certain embodiments accommodate disposable, prefilled reservoirs, alternative embodiments may use refillable cartridges, syringes or the like. A cartridge can be prefilled with insulin (or other drug or fluid) and inserted into the housing 912. Alternatively, a cartridge could be filled by the user using an appropriate adapter and/or any suitable refilling device.


Force sensor 926 is configured to react in response to force imparted thereto. In this regard, electrical, mechanical, magnetic, and/or other measurable or detectable characteristics of the force sensor 926 vary in accordance with the amount of force applied to the force sensor 926. Accordingly, force sensor 926 can detect forces being applied to the drive system, which is indicative of a pressure in the fluid reservoir 911. FIG. 8C depicts a possible curve 850 that correlates detected forces in a drive system to unit increments of medication forced into a fully occluded infusion set. Accordingly, the methods described herein can be implemented on the fluid infusion device 900 and systems including it.


Force sensor 926 might implement or otherwise leverage known sensor technologies, such as the sensor technology described in U.S. Pat. No. 6,485,465. As shown in FIG. 9A, the force sensor 926 includes at least one electrical lead 954 that is electrically coupled to the electronics module (or controller) of the fluid infusion device 900. Alternatively, the force sensor 926 could use wireless data communication technology to provide force-related data to the electronics module. In certain implementations, the force sensor 926 is suitably configured to indicate or generate a plurality of different output levels that can be monitored and/or determined by the electronics module. In practice, the output levels obtained from the force sensor 926 are initially conveyed as analog voltages or analog currents, and the electronics module includes an analog-to-digital converter that transforms a sampled analog voltage into a digital representation. Conversion of sensor voltage into the digital domain is desirable for ease of processing, comparison to threshold values, and the like.


When assembled as shown in FIG. 9B, the drive motor assembly 924 is located in the housing 912. The force sensor 926 is operatively associated with the drive motor assembly 924. For this particular embodiment, the force sensor 926 is coupled to the drive motor assembly 924, and it is located between a base end of the drive motor assembly 924 and the motor support cap 928. In one implementation, the force sensor 926 is affixed to the base end of the drive motor assembly 924 such that the force sensor 926 reacts when it bears against the motor support cap 928. In another implementation, the force sensor 926 is affixed to the housing end cap 914 such that the force sensor 926 reacts when the drive motor assembly 924 bears against the force sensor 926. This configuration and arrangement of the drive motor assembly 924 and the force sensor 926 allows the force sensor 926 to react to forces imparted thereto by the drive motor assembly 924 and/or forces imparted to the drive motor assembly 924 via the fluid pressure of the fluid reservoir 911.


The drive motor assembly 924 includes an electric motor 936 that is actuated and controlled by the electronics module of the fluid infusion device 900. The motor 936 can be realized as a stepper motor that rotates in a stepwise or discrete manner corresponding to the desired number of fluid delivery strokes. Alternatively, the motor 936 could be a DC motor, a solenoid, or the like. The motor 936 may optionally include an encoder (not shown), which cooperates with the electronics module of the pump device 100 to monitor the number of motor rotations or portions thereof. This in turn can be used to accurately determine the position of the slide 921, thus providing information relating to the amount of fluid dispensed from the fluid reservoir 911.


The drive motor assembly 924 can be mounted in the housing 912 using an appropriate mounting feature, structure, or element. Alternatively, the mounting could be accomplished using a shaft bearing and leaf spring or other known compliance mountings. The illustrated embodiment of the drive motor assembly 924 includes a drive member (such as the externally threaded drive gear or drive screw 925) that engages an internally threaded second drive member (such as the slide 921) having a coupler 942. The coupler 942 may be attached to or integrated with the slide 921. The slide 921 is sized to fit within the housing of the fluid reservoir 911, which enables the slide 921 to operatively cooperate with the fluid reservoir 911. The fluid reservoir 911 includes a plunger or piston 944 with at least one sealing element or feature (e.g., one or more O-rings, integral raised ridges, or a washer) for forming a fluid and air tight seal with the inner wall of the fluid reservoir 911. As mentioned previously, the fluid reservoir 911 is secured into the housing 912 with the fitting 910, which also serves as the interface between the fluid reservoir 911 and the infusion set tubing 908. For this embodiment, the piston 944 is in contact with a linear actuation member, such as the slide 921. For example, the piston 944 may have a female portion 946 that receives the coupler 942 carried by the slide 921. The female portion 946 is positioned at the end face of the piston 944, and it is sized to receive and accommodate the coupler 942. In certain embodiments, the female portion 946 includes a threaded cavity that engages external threads of the coupler 942.


Referring to FIG. 9B, rotation of the drive shaft of the motor 936 results in corresponding rotation of the drive screw 925, which in turn drives the slide 921 via the threaded engagement. Thus, rotation of the drive screw 925 results in axial displacement of the slide 921 and, therefore, axial displacement of the coupler 942. Such displacement of the coupler 942 moves the piston 944 (upward in FIG. 9B) to deliver a predetermined or commanded amount of medication or liquid from the fluid infusion device 900, which corresponds to a unit increment in FIG. 8C. In this manner, the drive motor assembly 924 is configured to regulate delivery of fluid by actuating the piston 944 (under the control of the electronics module and/or control system of the fluid infusion device 900). As described above, if a stepper motor is employed, then the drive motor assembly 924 can regulate delivery of fluid from the fluid infusion device 900 in discrete actuation or delivery strokes (which can be the unit increments noted in relationship to FIG. 8C). The fluid infusion device 900 can employ the sleeve 920 or an equivalent feature (such as an anti-rotation key) to inhibit rotation of the drive motor assembly 924, which might otherwise result from torque generated by the motor 936. In some embodiments, the drive shaft of the drive motor assembly 924, the drive screw 925, and the slide 921 are all coaxially centered within the longitudinal axis of travel of the piston 944. In certain alternative embodiments, one or more of these components may be offset from the center of the axis of travel and yet remain aligned with the axis of travel, which extends along the length of the fluid reservoir 911.


In particular embodiments, the force sensor 926 is realized as an electromechanical component having at least one variable resistance that changes as the force applied to the force sensor 926 changes. In alternative embodiments, the force sensor 926 is a capacitive sensor, a piezoresistive sensor, a piezoelectric sensor, a magnetic sensor, an optical sensor, a potentiometer, a micro-machined sensor, a linear transducer, an encoder, a strain gauge, or the like, and the detectable parameter or characteristic might be compression, shear, tension, displacement, distance, rotation, torque, force, pressure, or the like. In practice, changing characteristics of the force sensor 926 are associated with output signal characteristics that are responsive to a physical parameter to be measured. Moreover, the range and resolution of the monitored output signal provides for the desired number of output levels (e.g., different states, values, quantities, signals, magnitudes, frequencies, steps, or the like) across the range of measurement. For example, the force sensor 926 might generate a low or zero value when the applied force is relatively low, a high or maximum value when the applied force is relatively high, and intermediate values when the applied force is within the detectable range.


A number of embodiments of the invention have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention. Accordingly, other embodiments are within the scope of the following claims.

Claims
  • 1. A method for detecting an occlusion in an automated medication delivery system comprising: detecting at least one real-time analyte level for a user;based at least partially on the detected at least one real-time analyte level, determining a variable pressure threshold;determining a dosage of medication for delivery to the user based on the at least one real-time analyte level, wherein the dosage of medication is determined without user input;initiating a dispensation of the determined dosage of the medication using a medication delivery device;measuring a pressure of the medication in an infusion fluid pathway of the medication delivery device; andinitiating an occlusion alarm if the measured pressure exceeds the variable pressure threshold.
  • 2. The method of claim 1, wherein the variable pressure threshold is further dependent on a timing of one or more recent dispensations, amount of one or more recent dispensations, type of one or more recent dispensations, or a combination thereof.
  • 3. The method of claim 1, wherein the medication is insulin and the analyte levels are glucose levels.
  • 4. The method of claim 1, wherein measuring the pressure of the medication in the infusion fluid pathway of the medication delivery device comprises measuring the pressure of the medication in the infusion fluid pathway of the medication delivery device at multiple times during a dispensation period of time, the method further comprising: comparing each of the pressure measurements detected at the multiple times during the dispensation period to the variable pressure threshold; anddetermining, based on one or more of the detected pressure measurements exceeding the variable pressure threshold, that an intended dispensation did not enter the user.
  • 5. The method of claim 1, wherein measuring the pressure of the medication in the infusion fluid pathway of the medication delivery device comprises measuring the pressure of the medication in the infusion fluid pathway of the medication delivery device at multiple times during a dispensation period of time, the method further comprising: comparing each of the pressure measurements detected at the multiple times during the dispensation period to the variable pressure threshold; andindicating via an alert, based on one or more of the detected pressure measurements exceeding the variable pressure threshold, that the dispensation was delayed.
  • 6. A method for detecting an occlusion in an automated medication delivery system comprising: detecting at least one real-time analyte level for a user;based at least partially on the detected at least one real-time analyte level, determining a variable pressure threshold;determining a dosage of medication for delivery to the user based on the at least one real-time analyte level;initiating a dispensation of the determined dosage of the medication using a medication delivery device;measuring a pressure of the medication in an infusion fluid pathway of the medication delivery device; andinitiating an occlusion alarm if the measured pressure exceeds the variable pressure threshold.
  • 7. The method of claim 6, wherein the variable pressure threshold is further dependent on a timing of one or more recent dispensations, amount of one or more recent dispensations, type of one or more recent dispensations, or a combination thereof.
  • 8. The method of claim 6, wherein the medication is insulin and the analyte is glucose.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional application of and claims priority to U.S. application Ser. No. 15/404,442, filed on Jan. 12, 2017, now U.S. Pat. No. 10,610,643, issued Apr. 7, 2020, which claims priority to U.S. Provisional Application Ser. No. 62/278,974, filed on Jan. 14, 2016.

US Referenced Citations (1787)
Number Name Date Kind
303013 Horton Aug 1884 A
445545 Crane Feb 1891 A
588583 Lade Aug 1897 A
1441508 Marius et al. Jan 1923 A
2283925 Harvey May 1942 A
2605765 Kollsman Aug 1952 A
2797149 Skeggs Jun 1957 A
2886529 Guillaud May 1959 A
3413573 Nathanson et al. Nov 1968 A
3574114 Monforte Apr 1971 A
3614554 Shield et al. Oct 1971 A
3631847 Hobbs Jan 1972 A
3634039 Brondy Jan 1972 A
3688764 Reed Sep 1972 A
3812843 Wootten et al. May 1974 A
3841328 Jensen Oct 1974 A
3885662 Schaefer May 1975 A
3886938 Szabo et al. Jun 1975 A
3963380 Thomas et al. Jun 1976 A
3983077 Fuller et al. Sep 1976 A
4055175 Clemens et al. Oct 1977 A
4077405 Haerten et al. Mar 1978 A
4108177 Pistor Aug 1978 A
4146029 Ellinwood, Jr. Mar 1979 A
4151845 Clemens May 1979 A
4231368 Becker Nov 1980 A
4235234 Martin et al. Nov 1980 A
4245634 Albisser et al. Jan 1981 A
4265241 Portner et al. May 1981 A
4268150 Chen May 1981 A
4295176 Wittwer Oct 1981 A
4300554 Hessberg et al. Nov 1981 A
4313439 Babb et al. Feb 1982 A
4368980 Aldred et al. Jan 1983 A
4373527 Fischell Feb 1983 A
4398908 Siposs Aug 1983 A
4400683 Eda et al. Aug 1983 A
4403984 Ash et al. Sep 1983 A
4424720 Bucchianeri Jan 1984 A
4435173 Siposs et al. Mar 1984 A
4443218 DeCant et al. Apr 1984 A
4464170 Clemens et al. Aug 1984 A
4469481 Kobayashi Sep 1984 A
4475901 Kraegen et al. Oct 1984 A
4493704 Beard et al. Jan 1985 A
4498843 Schneider et al. Feb 1985 A
4507115 Kambara et al. Mar 1985 A
4523170 Huth, III Jun 1985 A
4526568 Clemens et al. Jul 1985 A
4526569 Bernardi Jul 1985 A
4529401 Leslie et al. Jul 1985 A
4551134 Slavik et al. Nov 1985 A
4552561 Eckenhoff et al. Nov 1985 A
4559033 Stephen et al. Dec 1985 A
4559037 Franetzki et al. Dec 1985 A
4562751 Nason et al. Jan 1986 A
4564054 Gustavsson Jan 1986 A
4573968 Parker Mar 1986 A
4585439 Michel Apr 1986 A
4601707 Albisser et al. Jul 1986 A
4624661 Arimond Nov 1986 A
4633878 Bombardieri Jan 1987 A
4634427 Hannula et al. Jan 1987 A
4646038 Wanat Feb 1987 A
4652260 Fenton et al. Mar 1987 A
4657529 Prince et al. Apr 1987 A
4668220 Hawrylenko May 1987 A
4678408 Nason et al. Jul 1987 A
4681569 Coble et al. Jul 1987 A
4684368 Kenyon Aug 1987 A
4685903 Cable et al. Aug 1987 A
4731726 Allen, III Mar 1988 A
4734092 Millerd Mar 1988 A
4743243 Vaillancourt May 1988 A
4749109 Kamen Jun 1988 A
4755169 Sarnoff et al. Jul 1988 A
4755173 Konopka et al. Jul 1988 A
4759120 Bernstein Jul 1988 A
4768506 Parker et al. Sep 1988 A
4781688 Thoma et al. Nov 1988 A
4781693 Martinez et al. Nov 1988 A
4808161 Kamen Feb 1989 A
4838857 Strowe et al. Jun 1989 A
4850817 Nason et al. Jul 1989 A
4854170 Brimhall et al. Aug 1989 A
4859492 Rogers et al. Aug 1989 A
4880770 Mir et al. Nov 1989 A
4886499 Cirelli et al. Dec 1989 A
4898578 Rubalcaba, Jr. Feb 1990 A
4898579 Groshong et al. Feb 1990 A
4900292 Berry et al. Feb 1990 A
4902278 Maget et al. Feb 1990 A
4919596 Slate et al. Apr 1990 A
4925444 Orkin et al. May 1990 A
4940527 Kazlauskas et al. Jul 1990 A
4944659 Labbe et al. Jul 1990 A
4967201 Rich, III Oct 1990 A
4969874 Michel et al. Nov 1990 A
4975581 Robinson et al. Dec 1990 A
4976720 Machold et al. Dec 1990 A
4981140 Wyatt Jan 1991 A
4994047 Walker et al. Feb 1991 A
5007286 Malcolm et al. Apr 1991 A
5007458 Marcus et al. Apr 1991 A
5029591 Teves Jul 1991 A
5045064 Driss Sep 1991 A
5061424 Karimi et al. Oct 1991 A
5062841 Siegel Nov 1991 A
5084749 Losee et al. Jan 1992 A
5088981 Howson et al. Feb 1992 A
5088990 Hivale et al. Feb 1992 A
5097834 Skrabal Mar 1992 A
5102406 Arnold Apr 1992 A
5109850 Blanco et al. May 1992 A
5125415 Bell Jun 1992 A
5130675 Sugawara Jul 1992 A
5134079 Cusack et al. Jul 1992 A
5139999 Gordon et al. Aug 1992 A
5153827 Coutre et al. Oct 1992 A
5154973 Imagawa et al. Oct 1992 A
5165406 Wong Nov 1992 A
5176632 Bernardi Jan 1993 A
5176662 Bartholomew et al. Jan 1993 A
5178609 Ishikawa Jan 1993 A
5189609 Tivig et al. Feb 1993 A
5190522 Wojcicki et al. Mar 1993 A
5198824 Poradish Mar 1993 A
5205819 Ross et al. Apr 1993 A
5207642 Orkin et al. May 1993 A
5209230 Swedlow et al. May 1993 A
5213483 Flaherty et al. May 1993 A
5217754 Santiago-Aviles et al. Jun 1993 A
5219377 Poradish Jun 1993 A
5225763 Krohn et al. Jul 1993 A
5232439 Campbell et al. Aug 1993 A
5237993 Skrabal Aug 1993 A
5244463 Cordner et al. Sep 1993 A
5250027 Lewis et al. Oct 1993 A
5254096 Rondelet et al. Oct 1993 A
5257980 Van et al. Nov 1993 A
5261882 Sealfon Nov 1993 A
5263198 Geddes et al. Nov 1993 A
5272485 Mason et al. Dec 1993 A
5273517 Barone et al. Dec 1993 A
5281202 Weber et al. Jan 1994 A
5281808 Kunkel Jan 1994 A
5299571 Mastrototaro Apr 1994 A
5308982 Ivaldi et al. May 1994 A
5314412 Rex May 1994 A
5335994 Weynant nee Girones Aug 1994 A
5338157 Blomquist Aug 1994 A
5342180 Daoud Aug 1994 A
5342298 Michaels et al. Aug 1994 A
5346476 Elson Sep 1994 A
5349575 Park Sep 1994 A
5364342 Beuchat et al. Nov 1994 A
5377674 Kuestner Jan 1995 A
5380665 Cusack et al. Jan 1995 A
5385539 Maynard Jan 1995 A
5389078 Zalesky et al. Feb 1995 A
5395340 Lee Mar 1995 A
5403797 Ohtani et al. Apr 1995 A
5411487 Castagna May 1995 A
5411889 Hoots et al. May 1995 A
5421812 Langley et al. Jun 1995 A
5427988 Sengupta et al. Jun 1995 A
5433710 Vanantwerp et al. Jul 1995 A
5456945 McMillan et al. Oct 1995 A
5468727 Phillips et al. Nov 1995 A
5478610 Desu et al. Dec 1995 A
5505709 Funderburk et al. Apr 1996 A
5505828 Wong et al. Apr 1996 A
5507288 Boecker et al. Apr 1996 A
5513382 Agahi-Kesheh et al. Apr 1996 A
5527288 Gross et al. Jun 1996 A
5533389 Kamen et al. Jul 1996 A
5535445 Gunton Jul 1996 A
5540772 McMillan et al. Jul 1996 A
5543773 Evans et al. Aug 1996 A
5545143 Fischell et al. Aug 1996 A
5551850 Williamson et al. Sep 1996 A
5554123 Herskowitz Sep 1996 A
5558640 Pfeiler et al. Sep 1996 A
5569186 Lord et al. Oct 1996 A
5582593 Hultman Dec 1996 A
5584053 Kommrusch et al. Dec 1996 A
5584813 Livingston et al. Dec 1996 A
5590387 Schmidt et al. Dec 1996 A
5609572 Lang Mar 1997 A
5614252 McMillan et al. Mar 1997 A
5625365 Tom et al. Apr 1997 A
5626566 Petersen et al. May 1997 A
5635433 Sengupta Jun 1997 A
5637095 Nason et al. Jun 1997 A
5656032 Kriesel et al. Aug 1997 A
5665065 Colman et al. Sep 1997 A
5665070 McPhee Sep 1997 A
5672167 Athayde et al. Sep 1997 A
5678539 Schubert et al. Oct 1997 A
5685844 Marttila Nov 1997 A
5685859 Kornerup Nov 1997 A
5693018 Kriesel et al. Dec 1997 A
5697899 Hillman et al. Dec 1997 A
5700695 Yassinzadeh et al. Dec 1997 A
5703364 Rosenthal Dec 1997 A
5707459 Itoyama et al. Jan 1998 A
5707715 Derochemont et al. Jan 1998 A
5713875 Tanner, II Feb 1998 A
5714123 Sohrab Feb 1998 A
5716343 Kriesel et al. Feb 1998 A
5718562 Awless et al. Feb 1998 A
5722397 Eppstein Mar 1998 A
5741216 Hemmingsen et al. Apr 1998 A
5741228 Lambrecht et al. Apr 1998 A
5746217 Erickson et al. May 1998 A
5747350 Sattler May 1998 A
5747870 Pedder May 1998 A
5748827 Holl et al. May 1998 A
5755682 Knudson et al. May 1998 A
5758643 Wong et al. Jun 1998 A
5759923 McMillan et al. Jun 1998 A
5764189 Lohninger Jun 1998 A
5766155 Hyman et al. Jun 1998 A
5771567 Pierce et al. Jun 1998 A
5772635 Dastur et al. Jun 1998 A
5776103 Kriesel et al. Jul 1998 A
5779676 Kriesel et al. Jul 1998 A
5785688 Joshi et al. Jul 1998 A
5797881 Gadot Aug 1998 A
5800397 Wilson et al. Sep 1998 A
5800405 McPhee Sep 1998 A
5800420 Gross et al. Sep 1998 A
5801057 Smart et al. Sep 1998 A
5804048 Wong et al. Sep 1998 A
5807075 Jacobsen et al. Sep 1998 A
5816306 Giacomel Oct 1998 A
5817007 Fodgaard et al. Oct 1998 A
5820622 Gross et al. Oct 1998 A
5822715 Worthington et al. Oct 1998 A
5823951 Messerschmidt Oct 1998 A
5839467 Saaski et al. Nov 1998 A
5840020 Heinonen et al. Nov 1998 A
D403313 Peppel Dec 1998 S
5848991 Gross et al. Dec 1998 A
5851197 Marano et al. Dec 1998 A
5852803 Ashby et al. Dec 1998 A
5854608 Leisten Dec 1998 A
5858001 Tsals et al. Jan 1999 A
5858005 Kriesel Jan 1999 A
5858239 Kenley et al. Jan 1999 A
5859621 Leisten Jan 1999 A
5865806 Howell Feb 1999 A
5871470 McWha Feb 1999 A
5873731 Prendergast Feb 1999 A
5879310 Sopp et al. Mar 1999 A
5889459 Hattori et al. Mar 1999 A
5891097 Saito et al. Apr 1999 A
5892489 Kanba et al. Apr 1999 A
5893838 Daoud et al. Apr 1999 A
5897530 Jackson Apr 1999 A
5902253 Pfeiffer et al. May 1999 A
5903421 Furutani et al. May 1999 A
5906597 McPhee May 1999 A
5911716 Rake et al. Jun 1999 A
5914941 Janky Jun 1999 A
5919167 Mulhauser et al. Jul 1999 A
5925018 Ungerstedt Jul 1999 A
5928201 Poulsen et al. Jul 1999 A
5931814 Alex et al. Aug 1999 A
5932175 Knute et al. Aug 1999 A
5933121 Rainhart et al. Aug 1999 A
5935099 Peterson et al. Aug 1999 A
5945963 Leisten Aug 1999 A
5947911 Wong et al. Sep 1999 A
5947934 Hansen et al. Sep 1999 A
5951530 Steengaard et al. Sep 1999 A
5957889 Poulsen et al. Sep 1999 A
5957890 Mann et al. Sep 1999 A
5961492 Kriesel et al. Oct 1999 A
5965848 Altschul et al. Oct 1999 A
5971941 Simons et al. Oct 1999 A
5984894 Poulsen et al. Nov 1999 A
5984897 Petersen et al. Nov 1999 A
5993423 Choi Nov 1999 A
5997475 Bortz Dec 1999 A
5997501 Gross et al. Dec 1999 A
6003736 Ljunggren Dec 1999 A
6005151 Herrmann et al. Dec 1999 A
6010485 Buch-Rasmussen et al. Jan 2000 A
6017318 Gauthier et al. Jan 2000 A
6019747 McPhee Feb 2000 A
6023251 Koo et al. Feb 2000 A
6024539 Blomquist Feb 2000 A
6027826 Derochemont et al. Feb 2000 A
6028568 Asakura et al. Feb 2000 A
6031445 Marty et al. Feb 2000 A
6032059 Henning et al. Feb 2000 A
6033377 Rasmussen et al. Mar 2000 A
6036924 Simons et al. Mar 2000 A
6040578 Malin et al. Mar 2000 A
6040805 Huynh et al. Mar 2000 A
6045537 Klitmose Apr 2000 A
6046707 Gaughan et al. Apr 2000 A
6049727 Crothall Apr 2000 A
6050978 Orr et al. Apr 2000 A
6052040 Hino Apr 2000 A
6056728 Von Schuckmann May 2000 A
6058934 Sullivan May 2000 A
6066103 Duchon et al. May 2000 A
6071292 Makower et al. Jun 2000 A
6072180 Kramer et al. Jun 2000 A
6074372 Hansen Jun 2000 A
6077055 Scott Jun 2000 A
6090092 Fowles et al. Jul 2000 A
6101406 Hacker et al. Aug 2000 A
6102872 Doneen et al. Aug 2000 A
6106498 Friedli et al. Aug 2000 A
6110149 Klitgaard et al. Aug 2000 A
6111544 Dakeya et al. Aug 2000 A
6115673 Malin et al. Sep 2000 A
6123827 Wong et al. Sep 2000 A
6124134 Stark Sep 2000 A
6126595 Amano et al. Oct 2000 A
6126637 Kriesel et al. Oct 2000 A
6127061 Shun et al. Oct 2000 A
6128519 Say Oct 2000 A
6142939 Eppstein et al. Nov 2000 A
6143164 Heller et al. Nov 2000 A
6143432 De et al. Nov 2000 A
6154176 Fathy et al. Nov 2000 A
6156014 Petersen et al. Dec 2000 A
6157041 Thomas et al. Dec 2000 A
6161028 Braig et al. Dec 2000 A
6162639 Douglas Dec 2000 A
6171276 Lippe et al. Jan 2001 B1
6174300 Kriesel et al. Jan 2001 B1
6176004 Rainhart et al. Jan 2001 B1
6181297 Leisten Jan 2001 B1
6188368 Koriyama et al. Feb 2001 B1
6190359 Heruth Feb 2001 B1
6195049 Kim et al. Feb 2001 B1
6196046 Braig et al. Mar 2001 B1
6200287 Keller et al. Mar 2001 B1
6200293 Kriesel et al. Mar 2001 B1
6200338 Solomon et al. Mar 2001 B1
6204203 Narwankar et al. Mar 2001 B1
6208843 Huang et al. Mar 2001 B1
6214629 Freitag et al. Apr 2001 B1
6222489 Tsuru et al. Apr 2001 B1
6226082 Roe May 2001 B1
6231540 Smedegaard May 2001 B1
6233471 Berner et al. May 2001 B1
6244776 Wiley Jun 2001 B1
6248067 Causey et al. Jun 2001 B1
6248090 Jensen et al. Jun 2001 B1
6248093 Moberg Jun 2001 B1
6251113 Appelbaum et al. Jun 2001 B1
6261065 Nayak et al. Jul 2001 B1
6262798 Shepherd et al. Jul 2001 B1
6266020 Chang Jul 2001 B1
6269340 Ford et al. Jul 2001 B1
6270455 Brown Aug 2001 B1
6271045 Douglas et al. Aug 2001 B1
6277098 Klitmose et al. Aug 2001 B1
6280381 Malin et al. Aug 2001 B1
6285448 Kuenstner Sep 2001 B1
6292440 Lee Sep 2001 B1
6300894 Lynch et al. Oct 2001 B1
6302855 Lav et al. Oct 2001 B1
6302869 Klitgaard Oct 2001 B1
6309370 Haim et al. Oct 2001 B1
6312888 Wong et al. Nov 2001 B1
6320547 Fathy et al. Nov 2001 B1
6323549 Derochemont et al. Nov 2001 B1
6334851 Hayes et al. Jan 2002 B1
6363609 Pickren Apr 2002 B1
6368314 Kipfer et al. Apr 2002 B1
6375627 Mauze et al. Apr 2002 B1
6375638 Nason et al. Apr 2002 B2
6379301 Worthington et al. Apr 2002 B1
6379339 Klitgaard et al. Apr 2002 B1
6381496 Meadows et al. Apr 2002 B1
6397098 Uber et al. May 2002 B1
6402689 Scarantino et al. Jun 2002 B1
6404098 Kayama et al. Jun 2002 B1
6413244 Bestetti et al. Jul 2002 B1
6427088 Bowman et al. Jul 2002 B1
D461241 Moberg et al. Aug 2002 S
D461891 Moberg Aug 2002 S
6434528 Sanders Aug 2002 B1
6436072 Kullas et al. Aug 2002 B1
6461329 Van et al. Oct 2002 B1
6461331 Van Antwerp Oct 2002 B1
6470279 Samsoondar Oct 2002 B1
6474219 Klitmose et al. Nov 2002 B2
6475196 Vachon Nov 2002 B1
6477065 Parks Nov 2002 B2
6477901 Tadigadapa et al. Nov 2002 B1
6484044 Lilienfeld-Toal Nov 2002 B1
6485461 Mason et al. Nov 2002 B1
6485462 Kriesel Nov 2002 B1
6491656 Morris Dec 2002 B1
6491684 Joshi et al. Dec 2002 B1
6492949 Breglia et al. Dec 2002 B1
6496149 Birnbaum et al. Dec 2002 B1
6501415 Viana et al. Dec 2002 B1
6508788 Preuthun Jan 2003 B2
6512937 Blank et al. Jan 2003 B2
6520936 Mann Feb 2003 B1
6524280 Hansen et al. Feb 2003 B2
6525509 Petersson et al. Feb 2003 B1
6527744 Kriesel et al. Mar 2003 B1
6528809 Thomas et al. Mar 2003 B1
6533183 Aasmul et al. Mar 2003 B2
6537249 Kriesell et al. Mar 2003 B2
6537251 Klitmose Mar 2003 B2
6537268 Gibson et al. Mar 2003 B1
6540260 Tan Apr 2003 B1
6540672 Simonsen et al. Apr 2003 B1
6541820 Bol Apr 2003 B1
6544212 Galley et al. Apr 2003 B2
6544229 Danby et al. Apr 2003 B1
6546268 Ishikawa et al. Apr 2003 B1
6546269 Kurnik Apr 2003 B1
6547764 Larsen et al. Apr 2003 B2
6551276 Mann et al. Apr 2003 B1
6552693 Leisten Apr 2003 B1
6553841 Blouch Apr 2003 B1
6554798 Mann et al. Apr 2003 B1
6554800 Nezhadian et al. Apr 2003 B1
6556850 Braig et al. Apr 2003 B1
D474778 Barnes May 2003 S
6558320 Causey et al. May 2003 B1
6558345 Houben et al. May 2003 B1
6558351 Steil et al. May 2003 B1
6559735 Hoang et al. May 2003 B1
6560471 Heller et al. May 2003 B1
6561978 Conn et al. May 2003 B1
6562001 Lebel et al. May 2003 B2
6562011 Buch-Rasmussen et al. May 2003 B1
6562014 Lin et al. May 2003 B2
6564105 Starkweather et al. May 2003 B2
6569115 Barker et al. May 2003 B1
6569125 Jepson et al. May 2003 B2
6569126 Poulsen et al. May 2003 B1
6571128 Lebel et al. May 2003 B2
6572542 Houben et al. Jun 2003 B1
6572545 Knobbe et al. Jun 2003 B2
6574490 Abbink et al. Jun 2003 B2
6575905 Knobbe et al. Jun 2003 B2
6577899 Lebel et al. Jun 2003 B2
6580934 Braig et al. Jun 2003 B1
6582404 Klitgaard et al. Jun 2003 B1
6583699 Yokoyama Jun 2003 B2
6585644 Lebel et al. Jul 2003 B2
6585699 Ljunggreen et al. Jul 2003 B2
6587199 Luu Jul 2003 B1
6589229 Connelly et al. Jul 2003 B1
6595956 Gross et al. Jul 2003 B1
6599281 Struys et al. Jul 2003 B1
6605067 Larsen Aug 2003 B1
6605072 Struys et al. Aug 2003 B2
6611419 Chakravorty Aug 2003 B1
6613019 Munk Sep 2003 B2
6618603 Varalli et al. Sep 2003 B2
6620750 Kim et al. Sep 2003 B2
6633772 Ford et al. Oct 2003 B2
6635958 Bates et al. Oct 2003 B2
6639556 Baba Oct 2003 B2
6641533 Causey et al. Nov 2003 B2
6642908 Pleva et al. Nov 2003 B2
6645142 Braig et al. Nov 2003 B2
6648821 Lebel et al. Nov 2003 B2
6650303 Kim et al. Nov 2003 B2
6650951 Jones et al. Nov 2003 B1
6653091 Dunn et al. Nov 2003 B1
6656158 Mahoney et al. Dec 2003 B2
6656159 Flaherty Dec 2003 B2
6659948 Lebel et al. Dec 2003 B2
6659978 Kasuga et al. Dec 2003 B1
6659980 Moberg et al. Dec 2003 B2
6662030 Khalil et al. Dec 2003 B2
6663602 Moeller Dec 2003 B2
6668196 Villegas et al. Dec 2003 B1
6669663 Thompson Dec 2003 B1
6669668 Kleeman et al. Dec 2003 B1
6669669 Flaherty et al. Dec 2003 B2
6670497 Tashino et al. Dec 2003 B2
6678542 Braig et al. Jan 2004 B2
6680700 Hilgers Jan 2004 B2
6683576 Achim Jan 2004 B2
6685674 Douglas et al. Feb 2004 B2
6686406 Tomomatsu et al. Feb 2004 B2
6687546 Lebel et al. Feb 2004 B2
6689100 Connelly et al. Feb 2004 B2
6690192 Wing Feb 2004 B1
6690336 Leisten et al. Feb 2004 B1
6691043 Ribeiro, Jr. Feb 2004 B2
6692457 Flaherty Feb 2004 B2
6692472 Hansen et al. Feb 2004 B2
6694191 Starkweather et al. Feb 2004 B2
6697605 Atokawa et al. Feb 2004 B1
6699218 Flaherty et al. Mar 2004 B2
6699221 Vaillancourt Mar 2004 B2
6702779 Connelly et al. Mar 2004 B2
6715516 Ohms et al. Apr 2004 B2
6716198 Larsen Apr 2004 B2
6718189 Rohrscheib et al. Apr 2004 B2
6720926 Killen et al. Apr 2004 B2
6721582 Trepagnier et al. Apr 2004 B2
6723072 Flaherty et al. Apr 2004 B2
6723077 Pickup et al. Apr 2004 B2
6727785 Killen et al. Apr 2004 B2
6728560 Kollias et al. Apr 2004 B2
6731244 Killen et al. May 2004 B2
6731248 Killen et al. May 2004 B2
6733446 Lebel et al. May 2004 B2
6733890 Imanaka et al. May 2004 B2
6736796 Shekalim May 2004 B2
6740059 Flaherty May 2004 B2
6740072 Starkweather et al. May 2004 B2
6740075 Lebel et al. May 2004 B2
6741148 Killen et al. May 2004 B2
6742249 DeRochemont et al. Jun 2004 B2
6743744 Kim et al. Jun 2004 B1
6744350 Blomquist Jun 2004 B2
6749587 Flaherty Jun 2004 B2
6750740 Killen et al. Jun 2004 B2
6750820 Killen et al. Jun 2004 B2
6751490 Esenaliev et al. Jun 2004 B2
6752785 Van et al. Jun 2004 B2
6752787 Causey et al. Jun 2004 B1
6753745 Killen et al. Jun 2004 B2
6753814 Killen et al. Jun 2004 B2
6758810 Lebel et al. Jul 2004 B2
6758835 Close et al. Jul 2004 B2
6761286 Py et al. Jul 2004 B2
6762237 Glatkowski et al. Jul 2004 B2
6768425 Flaherty et al. Jul 2004 B2
6780156 Haueter et al. Aug 2004 B2
6786246 Ohms et al. Sep 2004 B2
6786890 Preuthun et al. Sep 2004 B2
6787181 Uchiyama et al. Sep 2004 B2
6791496 Killen et al. Sep 2004 B1
6796957 Carpenter et al. Sep 2004 B2
6796970 Klitmose et al. Sep 2004 B1
6799149 Hartlaub Sep 2004 B2
6809653 Mann et al. Oct 2004 B1
6810290 Lebel et al. Oct 2004 B2
6811533 Lebel et al. Nov 2004 B2
6811534 Bowman et al. Nov 2004 B2
6813519 Ebel et al. Nov 2004 B2
6826031 Nagai et al. Nov 2004 B2
6827702 Lebel et al. Dec 2004 B2
6830558 Flaherty et al. Dec 2004 B2
6830623 Hayashi et al. Dec 2004 B2
6837858 Cunningham et al. Jan 2005 B2
6837988 Leong et al. Jan 2005 B2
6846288 Nagar et al. Jan 2005 B2
6852104 Blomquist Feb 2005 B2
6853288 Ahn et al. Feb 2005 B2
6854620 Ramey Feb 2005 B2
6854653 Eilersen Feb 2005 B2
6855129 Jensen et al. Feb 2005 B2
6858892 Yamagata Feb 2005 B2
6862534 Sterling et al. Mar 2005 B2
6864848 Sievenpiper Mar 2005 B2
6865408 Abbink et al. Mar 2005 B1
6871396 Sugaya et al. Mar 2005 B2
6872200 Mann et al. Mar 2005 B2
6873268 Lebel et al. Mar 2005 B2
6878132 Kipfer Apr 2005 B2
6878871 Scher et al. Apr 2005 B2
6883778 Newton et al. Apr 2005 B1
6890291 Robinson et al. May 2005 B2
6893415 Madsen et al. May 2005 B2
6899695 Herrera May 2005 B2
6899699 Enggaard May 2005 B2
6905989 Ellis et al. Jun 2005 B2
6906674 McKinzie et al. Jun 2005 B2
6914566 Beard Jul 2005 B2
6919119 Kalkan et al. Jul 2005 B2
6922590 Whitehurst Jul 2005 B1
6923763 Kovatchev et al. Aug 2005 B1
6925393 Kalatz et al. Aug 2005 B1
6928298 Furutani et al. Aug 2005 B2
6936006 Sabra Aug 2005 B2
6936029 Mann et al. Aug 2005 B2
6943430 Kwon Sep 2005 B2
6943731 Killen et al. Sep 2005 B2
6945961 Miller et al. Sep 2005 B2
6949081 Chance Sep 2005 B1
6950708 Bowman et al. Sep 2005 B2
6958809 Sterling et al. Oct 2005 B2
6960192 Flaherty et al. Nov 2005 B1
6963259 Killen et al. Nov 2005 B2
6979326 Mann et al. Dec 2005 B2
6989891 Braig et al. Jan 2006 B2
6990366 Say et al. Jan 2006 B2
6997911 Klitmose Feb 2006 B2
6997920 Mann et al. Feb 2006 B2
7002436 Ma et al. Feb 2006 B2
7005078 Van et al. Feb 2006 B2
7008399 Larsen et al. Mar 2006 B2
7008404 Nakajima Mar 2006 B2
7009180 Sterling et al. Mar 2006 B2
7014625 Bengtsson Mar 2006 B2
7016713 Gardner et al. Mar 2006 B2
7018360 Flaherty et al. Mar 2006 B2
7025743 Mann et al. Apr 2006 B2
7025744 Utterberg et al. Apr 2006 B2
7027848 Robinson et al. Apr 2006 B2
7029455 Flaherty Apr 2006 B2
7043288 Davis et al. May 2006 B2
7047637 Derochemont et al. May 2006 B2
7054836 Christensen et al. May 2006 B2
7060059 Keith et al. Jun 2006 B2
7060350 Takaya et al. Jun 2006 B2
7061593 Braig et al. Jun 2006 B2
7066910 Bauhahn et al. Jun 2006 B2
7070580 Nielsen Jul 2006 B2
7096124 Sterling et al. Aug 2006 B2
7098803 Mann et al. Aug 2006 B2
7104972 Moller et al. Sep 2006 B2
7109878 Mann et al. Sep 2006 B2
7115205 Robinson et al. Oct 2006 B2
7116949 Irie et al. Oct 2006 B2
7123964 Betzold et al. Oct 2006 B2
7133329 Skyggebjerg et al. Nov 2006 B2
7137694 Ferran et al. Nov 2006 B2
7139593 Kavak et al. Nov 2006 B2
7139598 Hull et al. Nov 2006 B2
7144384 Gorman et al. Dec 2006 B2
7160272 Eyal et al. Jan 2007 B1
7171252 Scarantino et al. Jan 2007 B1
7172572 Diamond et al. Feb 2007 B2
7179226 Crothall et al. Feb 2007 B2
7190988 Say et al. Mar 2007 B2
7204823 Estes et al. Apr 2007 B2
7220240 Struys et al. May 2007 B2
7230316 Yamazaki et al. Jun 2007 B2
7232423 Mernoee Jun 2007 B2
7248912 Gough et al. Jul 2007 B2
7267665 Steil et al. Sep 2007 B2
7271912 Sterling et al. Sep 2007 B2
7278983 Ireland et al. Oct 2007 B2
7291107 Hellwig et al. Nov 2007 B2
7291497 Holmes et al. Nov 2007 B2
7291782 Sager et al. Nov 2007 B2
7303549 Flaherty et al. Dec 2007 B2
7303622 Loch et al. Dec 2007 B2
7303922 Jeng et al. Dec 2007 B2
7354420 Steil et al. Apr 2008 B2
7388202 Sterling et al. Jun 2008 B2
7402153 Steil et al. Jul 2008 B2
7404796 Ginsberg Jul 2008 B2
7405698 De Rochemont Jul 2008 B2
7429255 Thompson Sep 2008 B2
7460130 Salganicoff Dec 2008 B2
7481787 Gable et al. Jan 2009 B2
7491187 Van et al. Feb 2009 B2
7494481 Moberg et al. Feb 2009 B2
7500949 Gottlieb et al. Mar 2009 B2
7509156 Flanders Mar 2009 B2
D590415 Ball et al. Apr 2009 S
7522124 Smith et al. Apr 2009 B2
7547281 Hayes et al. Jun 2009 B2
7553281 Hellwig et al. Jun 2009 B2
7553512 Kodas et al. Jun 2009 B2
7564887 Wang et al. Jul 2009 B2
7569030 Lebel et al. Aug 2009 B2
7569050 Moberg et al. Aug 2009 B2
7570980 Ginsberg Aug 2009 B2
7591801 Brauker et al. Sep 2009 B2
7595623 Bennett Sep 2009 B2
7597682 Moberg Oct 2009 B2
7608042 Goldberger et al. Oct 2009 B2
7641649 Moberg et al. Jan 2010 B2
7651845 Doyle et al. Jan 2010 B2
7652901 Kirchmeier et al. Jan 2010 B2
7654982 Carlisle et al. Feb 2010 B2
7670288 Sher Mar 2010 B2
7680529 Kroll Mar 2010 B2
D614634 Nilsen Apr 2010 S
7708717 Estes et al. May 2010 B2
7714794 Tavassoli Hozouri May 2010 B2
7734323 Blomquist et al. Jun 2010 B2
7763917 De Rochemont Jul 2010 B2
7766829 Sloan et al. Aug 2010 B2
7771391 Carter Aug 2010 B2
7785258 Braig et al. Aug 2010 B2
7785313 Mastrototaro Aug 2010 B2
7789859 Estes et al. Sep 2010 B2
7794426 Briones et al. Sep 2010 B2
7806853 Wittmann et al. Oct 2010 B2
7806854 Damiano et al. Oct 2010 B2
7812774 Friman et al. Oct 2010 B2
7815602 Mann et al. Oct 2010 B2
7819843 Mann et al. Oct 2010 B2
7828528 Estes et al. Nov 2010 B2
7850641 Lebel et al. Dec 2010 B2
7904061 Zaffino et al. Mar 2011 B1
7918825 O'Connor et al. Apr 2011 B2
7938797 Estes May 2011 B2
7938801 Hawkins et al. May 2011 B2
7946985 Mastrototaro et al. May 2011 B2
D640269 Chen Jun 2011 S
7959598 Estes Jun 2011 B2
7967812 Jasperson et al. Jun 2011 B2
7972296 Braig et al. Jul 2011 B2
7976492 Brauker et al. Jul 2011 B2
8029459 Rush et al. Oct 2011 B2
8057436 Causey et al. Nov 2011 B2
8062249 Wilinska et al. Nov 2011 B2
8065096 Moberg Nov 2011 B2
8066805 Zuercher et al. Nov 2011 B2
8069690 DeSantolo et al. Dec 2011 B2
8105268 Lebel et al. Jan 2012 B2
8114023 Ward et al. Feb 2012 B2
8114489 Nemat-Nasser et al. Feb 2012 B2
8152789 Starkweather et al. Apr 2012 B2
8178457 De Rochemont May 2012 B2
8182461 Pope May 2012 B2
8193873 Kato et al. Jun 2012 B2
8206296 Jennewine Jun 2012 B2
8206350 Mann et al. Jun 2012 B2
8208984 Blomquist et al. Jun 2012 B2
8221345 Blomquist Jul 2012 B2
8221385 Estes Jul 2012 B2
8226556 Hayes et al. Jul 2012 B2
8246540 Ginsberg Aug 2012 B2
8251907 Sterling et al. Aug 2012 B2
8262616 Grant et al. Sep 2012 B2
8267893 Moberg et al. Sep 2012 B2
8267921 Yodfat et al. Sep 2012 B2
8273052 Damiano et al. Sep 2012 B2
D669165 Sims et al. Oct 2012 S
8282626 Wenger et al. Oct 2012 B2
8287487 Estes Oct 2012 B2
8318154 Frost et al. Nov 2012 B2
8348844 Kunjan et al. Jan 2013 B2
8348886 Kanderian et al. Jan 2013 B2
8348923 Kanderian et al. Jan 2013 B2
8350657 Derochemont Jan 2013 B2
8352011 Van et al. Jan 2013 B2
8354294 De et al. Jan 2013 B2
8372039 Mernoe et al. Feb 2013 B2
D677685 Simmons et al. Mar 2013 S
8409142 Causey et al. Apr 2013 B2
8417311 Rule Apr 2013 B2
8430847 Mernoe et al. Apr 2013 B2
8439834 Schmelzeisen-Redeker et al. May 2013 B2
8439897 Yodfat et al. May 2013 B2
8449524 Braig et al. May 2013 B2
8452359 Rebec et al. May 2013 B2
8454510 Yodfat et al. Jun 2013 B2
8454576 Mastrototaro et al. Jun 2013 B2
8460231 Brauker et al. Jun 2013 B2
8467972 Rush Jun 2013 B2
8467980 Campbell et al. Jun 2013 B2
8475409 Tsoukalis Jul 2013 B2
8478557 Hayter et al. Jul 2013 B2
8480655 Jasperson et al. Jul 2013 B2
D688686 Rhee et al. Aug 2013 S
8547239 Peatfield et al. Oct 2013 B2
8548544 Kircher et al. Oct 2013 B2
8548552 Tsoukalis Oct 2013 B2
8551045 Sie et al. Oct 2013 B2
8560082 Wei Oct 2013 B2
8560131 Haueter et al. Oct 2013 B2
8562558 Kamath et al. Oct 2013 B2
8562587 Kovatchev et al. Oct 2013 B2
8568713 Frost et al. Oct 2013 B2
D693837 Bouchier Nov 2013 S
8579854 Budiman et al. Nov 2013 B2
8579879 Palerm et al. Nov 2013 B2
8585591 Sloan et al. Nov 2013 B2
8585593 Kovatchev et al. Nov 2013 B2
8585637 Wilinska et al. Nov 2013 B2
8585638 Blomquist Nov 2013 B2
8593819 De Rochemont Nov 2013 B2
D695757 Ray et al. Dec 2013 S
8597274 Sloan et al. Dec 2013 B2
8615366 Galley et al. Dec 2013 B2
8622988 Hayter Jan 2014 B2
8679016 Mastrototaro et al. Mar 2014 B2
8679060 Mernoe et al. Mar 2014 B2
8690820 Cinar et al. Apr 2014 B2
8694115 Goetz et al. Apr 2014 B2
8706691 McDaniel et al. Apr 2014 B2
8715839 De Rochemont May 2014 B2
8718949 Blomquist et al. May 2014 B2
8721585 Brauker et al. May 2014 B2
8727982 Jennewine May 2014 B2
8734422 Hayter May 2014 B2
8734428 Blomquist May 2014 B2
8747315 Brauker et al. Jun 2014 B2
8762070 Doyle et al. Jun 2014 B2
8771222 Kanderian et al. Jul 2014 B2
8777896 Starkweather et al. Jul 2014 B2
8777924 Kanderian et al. Jul 2014 B2
8784364 Kamen et al. Jul 2014 B2
8784369 Starkweather et al. Jul 2014 B2
8784370 Lebel et al. Jul 2014 B2
8790294 Estes Jul 2014 B2
D710879 Elston et al. Aug 2014 S
8795224 Starkweather et al. Aug 2014 B2
8795252 Hayter Aug 2014 B2
8808230 Rotstein Aug 2014 B2
8810394 Kalpin Aug 2014 B2
D714822 Capua et al. Oct 2014 S
D715315 Wood Oct 2014 S
D715815 Bortman et al. Oct 2014 S
8852141 Mhatre et al. Oct 2014 B2
8876755 Taub et al. Nov 2014 B2
8882741 Brauker et al. Nov 2014 B2
D718779 Hang et al. Dec 2014 S
D720366 Hiltunen et al. Dec 2014 S
8903501 Perryman Dec 2014 B2
8919180 Gottlieb et al. Dec 2014 B2
8920401 Brauker et al. Dec 2014 B2
D720765 Xie et al. Jan 2015 S
8926585 Brauker et al. Jan 2015 B2
8939935 O'Connor et al. Jan 2015 B2
8945094 Nordh Feb 2015 B2
8956291 Valk et al. Feb 2015 B2
8956321 DeJournett Feb 2015 B2
8977504 Hovorka Mar 2015 B2
8992475 Mann et al. Mar 2015 B2
D726760 Yokota et al. Apr 2015 S
D727928 Allison et al. Apr 2015 S
D730378 Xiong et al. May 2015 S
9034323 Frost et al. May 2015 B2
D733175 Bae Jun 2015 S
9050413 Brauker et al. Jun 2015 B2
9056165 Steil et al. Jun 2015 B2
9056168 Kircher et al. Jun 2015 B2
9061097 Holt et al. Jun 2015 B2
D734356 Xiong et al. Jul 2015 S
9078963 Estes Jul 2015 B2
9089305 Hovorka Jul 2015 B2
D736811 Teichner et al. Aug 2015 S
D737305 Scazafavo et al. Aug 2015 S
D737831 Lee Sep 2015 S
D737832 Lim et al. Sep 2015 S
D738901 Amin Sep 2015 S
D740301 Soegiono et al. Oct 2015 S
D740308 Kim et al. Oct 2015 S
D740311 Drozd et al. Oct 2015 S
D741354 Lee et al. Oct 2015 S
D741359 Ji-Hye et al. Oct 2015 S
9149233 Kamath et al. Oct 2015 B2
9155843 Brauker et al. Oct 2015 B2
9171343 Fischell et al. Oct 2015 B1
D743431 Pal et al. Nov 2015 S
D743991 Pal et al. Nov 2015 S
9180224 Moseley et al. Nov 2015 B2
9180244 Anderson et al. Nov 2015 B2
9192716 Jugl et al. Nov 2015 B2
D744514 Shin et al. Dec 2015 S
D744517 Pal et al. Dec 2015 S
D745032 Pal et al. Dec 2015 S
D745034 Pal et al. Dec 2015 S
D745035 Pal et al. Dec 2015 S
D746827 Jung et al. Jan 2016 S
D746828 Arai et al. Jan 2016 S
D747352 Lee et al. Jan 2016 S
9233204 Booth et al. Jan 2016 B2
D749097 Zou et al. Feb 2016 S
D749118 Wang Feb 2016 S
9247901 Kamath et al. Feb 2016 B2
D751100 Lindn et al. Mar 2016 S
D752604 Zhang Mar 2016 S
D753134 Vazquez Apr 2016 S
D754718 Zhou Apr 2016 S
9314566 Wenger et al. Apr 2016 B2
9320471 Hayes et al. Apr 2016 B2
D755193 Sun et al. May 2016 S
D755799 Finnis et al. May 2016 S
D755820 Wang May 2016 S
D756387 Chang et al. May 2016 S
D757032 Sabia et al. May 2016 S
D757035 Raskin et al. May 2016 S
9333298 Kim et al. May 2016 B2
D758391 Suarez Jun 2016 S
D758422 Zhao Jun 2016 S
D759032 Amin et al. Jun 2016 S
D759078 Iwamoto Jun 2016 S
D759678 Jung et al. Jun 2016 S
D759687 Chang et al. Jun 2016 S
D761812 Motamedi Jul 2016 S
D763308 Wang et al. Aug 2016 S
D763868 Lee et al. Aug 2016 S
D765110 Liang Aug 2016 S
D765124 Minks-Brown et al. Aug 2016 S
9402950 Dilanni et al. Aug 2016 B2
9415157 Mann et al. Aug 2016 B2
D765707 Gomez Sep 2016 S
D766286 Lee et al. Sep 2016 S
D767586 Kwon et al. Sep 2016 S
D768154 Kim et al. Oct 2016 S
D768188 Li et al. Oct 2016 S
D768660 Wielgosz Oct 2016 S
D768685 Lee et al. Oct 2016 S
D769315 Scotti Oct 2016 S
9474855 McCann et al. Oct 2016 B2
D770507 Umezawa et al. Nov 2016 S
D770515 Cho et al. Nov 2016 S
D771073 Choi et al. Nov 2016 S
D771076 Butcher et al. Nov 2016 S
D771690 Yin et al. Nov 2016 S
D772911 Lee et al. Nov 2016 S
9480796 Starkweather et al. Nov 2016 B2
9486172 Cobelli et al. Nov 2016 B2
9486571 Rosinko Nov 2016 B2
9486578 Finan et al. Nov 2016 B2
D773531 Toth et al. Dec 2016 S
D775184 Song et al. Dec 2016 S
D775196 Huang et al. Dec 2016 S
9520649 De Rochemont Dec 2016 B2
D775658 Luo et al. Jan 2017 S
D776126 Lai et al. Jan 2017 S
D776687 Wick et al. Jan 2017 S
D777191 Polimeni Jan 2017 S
D777758 Kisselev et al. Jan 2017 S
9561324 Estes Feb 2017 B2
9579456 Budiman et al. Feb 2017 B2
D781323 Green et al. Mar 2017 S
D781781 Schimmoeller, Jr. Mar 2017 S
D781877 Ko et al. Mar 2017 S
D781878 Butcher et al. Mar 2017 S
D781879 Butcher et al. Mar 2017 S
D781903 Reichle et al. Mar 2017 S
D781905 Nakaguchi et al. Mar 2017 S
D782506 Kim et al. Mar 2017 S
D783672 Rajasankar et al. Apr 2017 S
D785010 Bachman et al. Apr 2017 S
D785656 Bramer et al. May 2017 S
D786278 Motamedi May 2017 S
D786898 Hall May 2017 S
D788126 Evnin et al. May 2017 S
9656017 Greene May 2017 B2
D788621 Shallice et al. Jun 2017 S
D788652 Mutsuro et al. Jun 2017 S
D789402 Dye et al. Jun 2017 S
D789967 Kaplan et al. Jun 2017 S
D789982 Christiana et al. Jun 2017 S
D790560 Inose et al. Jun 2017 S
D791781 Donarski et al. Jul 2017 S
D791805 Segars Jul 2017 S
D791812 Bistoni et al. Jul 2017 S
D793412 Chaudhri et al. Aug 2017 S
D795886 Ng et al. Aug 2017 S
D795891 Kohan et al. Aug 2017 S
D795900 Bischoff et al. Aug 2017 S
D795906 Butrick Aug 2017 S
D795927 Bischoff et al. Aug 2017 S
9743224 San et al. Aug 2017 B2
D796530 McMillan et al. Sep 2017 S
D796540 McLean et al. Sep 2017 S
D797116 Chapman et al. Sep 2017 S
D797763 Kim et al. Sep 2017 S
D797774 Park et al. Sep 2017 S
D797797 Gandhi et al. Sep 2017 S
D798310 Golden et al. Sep 2017 S
D798311 Golden et al. Sep 2017 S
D799536 Eder Oct 2017 S
D800765 Stoksik Oct 2017 S
D800769 Hennessy et al. Oct 2017 S
D801383 Park et al. Oct 2017 S
D802011 Friedman et al. Nov 2017 S
D802088 Bos et al. Nov 2017 S
D803232 Leigh et al. Nov 2017 S
D803242 Mizono et al. Nov 2017 S
D804502 Amini et al. Dec 2017 S
D805525 Dascola et al. Dec 2017 S
D806716 Pahwa et al. Jan 2018 S
D807376 Mizono et al. Jan 2018 S
D807400 LaGreca Jan 2018 S
D807910 Graham et al. Jan 2018 S
D807918 Cohen et al. Jan 2018 S
D807919 Cohen et al. Jan 2018 S
D808423 Jiang et al. Jan 2018 S
D808974 Chiappone et al. Jan 2018 S
D808983 Narinedhat et al. Jan 2018 S
9857090 Golden et al. Jan 2018 B2
9878097 Estes Jan 2018 B2
D810116 McLean et al. Feb 2018 S
D810771 Gandhi et al. Feb 2018 S
9889254 Haenggi Feb 2018 B2
9907515 Doyle et al. Mar 2018 B2
D815131 Thompson et al. Apr 2018 S
D816090 Stonecipher et al. Apr 2018 S
D817339 Nanjappan et al. May 2018 S
D818491 Timmer et al. May 2018 S
D819057 Huang May 2018 S
D819059 O'Toole May 2018 S
9968729 Estes May 2018 B2
9980140 Spencer et al. May 2018 B1
9984773 Gondhalekar et al. May 2018 B2
D820311 Cabrera et al. Jun 2018 S
D820862 Alfonzo et al. Jun 2018 S
D822034 Clymer et al. Jul 2018 S
D822677 Weaver et al. Jul 2018 S
D822684 Clausen-Stuck et al. Jul 2018 S
D822692 Loychik et al. Jul 2018 S
D823862 Chung et al. Jul 2018 S
D824400 Chang et al. Jul 2018 S
D824951 Kolbrener et al. Aug 2018 S
D826956 Pillalamarri et al. Aug 2018 S
D826957 Pillalamarri et al. Aug 2018 S
D828381 Lee et al. Sep 2018 S
D829732 Jeffrey et al. Oct 2018 S
D830374 Leonard et al. Oct 2018 S
D830384 Lepine et al. Oct 2018 S
D830385 Lepine et al. Oct 2018 S
D830407 Kisielius et al. Oct 2018 S
D831033 Leonard et al. Oct 2018 S
D833469 Coleman et al. Nov 2018 S
D834601 Felt Nov 2018 S
D835132 Ito et al. Dec 2018 S
D835145 Cashner et al. Dec 2018 S
D835147 Kisielius et al. Dec 2018 S
D835651 Bao Dec 2018 S
D835666 Saleh et al. Dec 2018 S
D836123 Pillalamarri et al. Dec 2018 S
D837807 Baber et al. Jan 2019 S
D838731 Pillalamarri et al. Jan 2019 S
D840418 Saad et al. Feb 2019 S
D840419 Saad et al. Feb 2019 S
D844022 Amin Mar 2019 S
D845317 Wellmeier et al. Apr 2019 S
10248839 Levy et al. Apr 2019 B2
D848459 Li May 2019 S
D851099 Uppala et al. Jun 2019 S
D851658 Pillalamarri et al. Jun 2019 S
10335464 Michelich et al. Jul 2019 B1
10449294 Estes Oct 2019 B1
D865795 Koo Nov 2019 S
D872746 LaBorde Jan 2020 S
10545132 Guthrie Jan 2020 B2
D874471 Pillalamarri et al. Feb 2020 S
D875114 Clediere Feb 2020 S
10569015 Estes Feb 2020 B2
10583250 Mazlish et al. Mar 2020 B2
D880498 Shahidi et al. Apr 2020 S
D888070 Yusupov et al. Jun 2020 S
10737015 Estes Aug 2020 B2
10737024 Schmid Aug 2020 B2
D904426 Paul Dec 2020 S
D911353 Sanchez et al. Feb 2021 S
D914031 Ding et al. Mar 2021 S
D916729 Gabriel et al. Apr 2021 S
D916870 Hemsley Apr 2021 S
D916878 Kim et al. Apr 2021 S
10987468 Mazlish et al. Apr 2021 B2
D918261 Ramamurthy et al. May 2021 S
D920351 Zhang May 2021 S
D923033 Smith et al. Jun 2021 S
D927533 Clymer Aug 2021 S
11147914 Estes Oct 2021 B2
D938447 Holland Dec 2021 S
11197964 Sjolund et al. Dec 2021 B2
11260169 Estes Mar 2022 B2
D954078 Rahate et al. Jun 2022 S
20010003542 Kita Jun 2001 A1
20010021803 Blank et al. Sep 2001 A1
20010034023 Stanton et al. Oct 2001 A1
20010034502 Moberg et al. Oct 2001 A1
20010041869 Causey et al. Nov 2001 A1
20010048969 Constantino et al. Dec 2001 A1
20010051377 Hammer et al. Dec 2001 A1
20010053895 Vaillancourt Dec 2001 A1
20010056258 Evans Dec 2001 A1
20010056262 Cabiri et al. Dec 2001 A1
20020010401 Bushmakin et al. Jan 2002 A1
20020010423 Gross et al. Jan 2002 A1
20020013784 Swanson Jan 2002 A1
20020016534 Trepagnier et al. Feb 2002 A1
20020016568 Lebel et al. Feb 2002 A1
20020032402 Daoud et al. Mar 2002 A1
20020040208 Flaherty et al. Apr 2002 A1
20020046315 Miller et al. Apr 2002 A1
20020047768 Duffy Apr 2002 A1
20020055845 Ueda et al. May 2002 A1
20020070983 Kozub et al. Jun 2002 A1
20020072720 Hague et al. Jun 2002 A1
20020123740 Flaherty et al. Sep 2002 A1
20020128543 Leonhardt Sep 2002 A1
20020147423 Burbank et al. Oct 2002 A1
20020155425 Han et al. Oct 2002 A1
20020156462 Stultz Oct 2002 A1
20020161288 Shin et al. Oct 2002 A1
20020164973 Janik et al. Nov 2002 A1
20020173769 Gray et al. Nov 2002 A1
20020190818 Endou et al. Dec 2002 A1
20030023148 Lorenz et al. Jan 2003 A1
20030023152 Abbink et al. Jan 2003 A1
20030034124 Sugaya et al. Feb 2003 A1
20030040715 D'Antonio et al. Feb 2003 A1
20030050621 Lebel et al. Mar 2003 A1
20030055380 Flaherty Mar 2003 A1
20030060692 L. Ruchti et al. Mar 2003 A1
20030065308 Lebel et al. Apr 2003 A1
20030086073 Braig et al. May 2003 A1
20030086074 Braig et al. May 2003 A1
20030086075 Braig et al. May 2003 A1
20030088238 Poulsen et al. May 2003 A1
20030090649 Sterling et al. May 2003 A1
20030100040 Bonnecaze et al. May 2003 A1
20030104982 Wittmann et al. Jun 2003 A1
20030121055 Kaminski et al. Jun 2003 A1
20030122647 Ou Jul 2003 A1
20030125672 Adair et al. Jul 2003 A1
20030135388 Martucci et al. Jul 2003 A1
20030144582 Cohen et al. Jul 2003 A1
20030148024 Kodas et al. Aug 2003 A1
20030161744 Vilks et al. Aug 2003 A1
20030163097 Fleury et al. Aug 2003 A1
20030170436 Sumi et al. Sep 2003 A1
20030175806 Rule et al. Sep 2003 A1
20030195404 Knobbe et al. Oct 2003 A1
20030198558 Nason et al. Oct 2003 A1
20030208113 Mault et al. Nov 2003 A1
20030208154 Close et al. Nov 2003 A1
20030212379 Bylund et al. Nov 2003 A1
20030216627 Lorenz et al. Nov 2003 A1
20030216683 Shekalim Nov 2003 A1
20030216686 Lynch et al. Nov 2003 A1
20030220605 Bowman et al. Nov 2003 A1
20030221621 Pokharna et al. Dec 2003 A1
20030236498 Gross et al. Dec 2003 A1
20040001027 Killen et al. Jan 2004 A1
20040006316 Patton Jan 2004 A1
20040010207 Flaherty et al. Jan 2004 A1
20040019325 Shekalim Jan 2004 A1
20040034295 Salganicoff Feb 2004 A1
20040045879 Shults et al. Mar 2004 A1
20040051368 Caputo et al. Mar 2004 A1
20040064088 Gorman et al. Apr 2004 A1
20040064096 Flaherty et al. Apr 2004 A1
20040064259 Haaland et al. Apr 2004 A1
20040068224 Couvillon et al. Apr 2004 A1
20040068230 Estes et al. Apr 2004 A1
20040069004 Gist et al. Apr 2004 A1
20040069044 Lavi et al. Apr 2004 A1
20040078028 Flaherty et al. Apr 2004 A1
20040087894 Flaherty May 2004 A1
20040087904 Langley et al. May 2004 A1
20040092865 Flaherty et al. May 2004 A1
20040092878 Flaherty May 2004 A1
20040097796 Berman et al. May 2004 A1
20040115068 Hansen et al. Jun 2004 A1
20040116847 Wall Jun 2004 A1
20040116866 Gorman et al. Jun 2004 A1
20040122353 Shahmirian et al. Jun 2004 A1
20040127844 Flaherty Jul 2004 A1
20040133166 Moberg et al. Jul 2004 A1
20040147034 Gore et al. Jul 2004 A1
20040153032 Garribotto et al. Aug 2004 A1
20040158207 Hunn et al. Aug 2004 A1
20040171983 Sparks et al. Sep 2004 A1
20040176720 Kipfer Sep 2004 A1
20040176727 Shekalim Sep 2004 A1
20040187952 Jones Sep 2004 A1
20040203357 Nassimi Oct 2004 A1
20040204673 Flaherty Oct 2004 A1
20040204744 Penner et al. Oct 2004 A1
20040204868 Maynard et al. Oct 2004 A1
20040215492 Choi Oct 2004 A1
20040220551 Flaherty et al. Nov 2004 A1
20040235446 Flaherty et al. Nov 2004 A1
20040241736 Hendee et al. Dec 2004 A1
20040249308 Forssell Dec 2004 A1
20040260233 Garibotto et al. Dec 2004 A1
20050003470 Nelson et al. Jan 2005 A1
20050010165 Hickle Jan 2005 A1
20050020980 Inoue et al. Jan 2005 A1
20050021005 Flaherty et al. Jan 2005 A1
20050021104 DiLorenzo Jan 2005 A1
20050022274 Campbell et al. Jan 2005 A1
20050033148 Haueter et al. Feb 2005 A1
20050038332 Saidara et al. Feb 2005 A1
20050049179 Davidson et al. Mar 2005 A1
20050065464 Talbot et al. Mar 2005 A1
20050065760 Murtfeldt et al. Mar 2005 A1
20050075624 Miesel Apr 2005 A1
20050090808 Malave et al. Apr 2005 A1
20050090851 Devlin Apr 2005 A1
20050095063 Fathallah et al. May 2005 A1
20050101933 Marrs et al. May 2005 A1
20050105095 Pesach et al. May 2005 A1
20050107743 Fangrow May 2005 A1
20050113745 Stultz May 2005 A1
20050124866 Elaz et al. Jun 2005 A1
20050134609 Yu Jun 2005 A1
20050137530 Campbell et al. Jun 2005 A1
20050137573 McLaughlin Jun 2005 A1
20050160858 Mernoe Jul 2005 A1
20050171503 Van et al. Aug 2005 A1
20050171512 Flaherty Aug 2005 A1
20050182306 Sloan Aug 2005 A1
20050182366 Vogt et al. Aug 2005 A1
20050192494 Ginsberg Sep 2005 A1
20050192557 Brauker et al. Sep 2005 A1
20050197621 Poulsen et al. Sep 2005 A1
20050203360 Brauker et al. Sep 2005 A1
20050203461 Flaherty et al. Sep 2005 A1
20050215982 Malave et al. Sep 2005 A1
20050222645 Malave et al. Oct 2005 A1
20050234404 Vilks et al. Oct 2005 A1
20050238507 Diianni et al. Oct 2005 A1
20050240544 Kil et al. Oct 2005 A1
20050245878 Mernoe et al. Nov 2005 A1
20050251097 Mernoe Nov 2005 A1
20050261660 Choi Nov 2005 A1
20050262451 Remignanti et al. Nov 2005 A1
20050267402 Stewart et al. Dec 2005 A1
20050272640 Doyle et al. Dec 2005 A1
20050273059 Mernoe et al. Dec 2005 A1
20050277890 Stewart et al. Dec 2005 A1
20050277912 John Dec 2005 A1
20060009727 O'Mahony et al. Jan 2006 A1
20060036214 Mogensen et al. Feb 2006 A1
20060041229 Garibotto et al. Feb 2006 A1
20060042633 Bishop et al. Mar 2006 A1
20060064053 Bollish et al. Mar 2006 A1
20060069351 Safabash et al. Mar 2006 A9
20060069382 Pedersen Mar 2006 A1
20060074381 Malave et al. Apr 2006 A1
20060075269 Liong et al. Apr 2006 A1
20060079765 Neer et al. Apr 2006 A1
20060079809 Goldberger et al. Apr 2006 A1
20060086994 Mefers et al. Apr 2006 A1
20060095014 Ethelfeld May 2006 A1
20060100494 Kroll May 2006 A1
20060125654 Liao et al. Jun 2006 A1
20060134323 O'Brien Jun 2006 A1
20060134491 Hilchenko et al. Jun 2006 A1
20060135913 Ethelfeld Jun 2006 A1
20060142698 Ethelfeld Jun 2006 A1
20060151545 Imhof et al. Jul 2006 A1
20060167350 Monfre et al. Jul 2006 A1
20060173410 Moberg et al. Aug 2006 A1
20060178633 Garibotto et al. Aug 2006 A1
20060184104 Cheney et al. Aug 2006 A1
20060184119 Remde et al. Aug 2006 A1
20060189925 Gable et al. Aug 2006 A1
20060189926 Hall et al. Aug 2006 A1
20060197015 Sterling et al. Sep 2006 A1
20060200070 Callicoat et al. Sep 2006 A1
20060200073 Radmer et al. Sep 2006 A1
20060204535 Johnson Sep 2006 A1
20060206054 Shekalim Sep 2006 A1
20060214511 Dayan Sep 2006 A1
20060229531 Goldberger et al. Oct 2006 A1
20060247574 Maule et al. Nov 2006 A1
20060247581 Pedersen et al. Nov 2006 A1
20060253085 Geismar et al. Nov 2006 A1
20060253086 Moberg et al. Nov 2006 A1
20060258973 Volt Nov 2006 A1
20060258976 Shturman et al. Nov 2006 A1
20060264835 Nielsen et al. Nov 2006 A1
20060264890 Moberg et al. Nov 2006 A1
20060264894 Moberg et al. Nov 2006 A1
20060264895 Flanders Nov 2006 A1
20060270983 Lord et al. Nov 2006 A1
20060276771 Galley et al. Dec 2006 A1
20060282290 Flaherty et al. Dec 2006 A1
20070016127 Staib et al. Jan 2007 A1
20070060796 Kim Mar 2007 A1
20070060869 Tolle et al. Mar 2007 A1
20070060870 Tolle et al. Mar 2007 A1
20070060872 Hall et al. Mar 2007 A1
20070073228 Mernoe et al. Mar 2007 A1
20070073235 Estes et al. Mar 2007 A1
20070073236 Mernoe et al. Mar 2007 A1
20070078818 Zivitz et al. Apr 2007 A1
20070079836 Reghabi et al. Apr 2007 A1
20070083160 Hall et al. Apr 2007 A1
20070088271 Richards Apr 2007 A1
20070093750 Jan et al. Apr 2007 A1
20070093786 Goldsmith et al. Apr 2007 A1
20070100222 Mastrototaro et al. May 2007 A1
20070100635 Mahajan et al. May 2007 A1
20070106135 Sloan et al. May 2007 A1
20070106218 Yodfat et al. May 2007 A1
20070112298 Mueller et al. May 2007 A1
20070116601 Patton May 2007 A1
20070118364 Wise et al. May 2007 A1
20070118405 Campbell et al. May 2007 A1
20070123819 Mernoe et al. May 2007 A1
20070124002 Estes et al. May 2007 A1
20070129690 Rosenblatt et al. Jun 2007 A1
20070142720 Ridder et al. Jun 2007 A1
20070142776 Kovelman et al. Jun 2007 A9
20070155307 Ng et al. Jul 2007 A1
20070156092 Estes et al. Jul 2007 A1
20070156094 Safabash et al. Jul 2007 A1
20070166170 Nason et al. Jul 2007 A1
20070166453 Van et al. Jul 2007 A1
20070167905 Estes et al. Jul 2007 A1
20070169607 Keller et al. Jul 2007 A1
20070173761 Kanderian et al. Jul 2007 A1
20070173974 Lin Jul 2007 A1
20070179352 Randlov et al. Aug 2007 A1
20070191702 Yodfat et al. Aug 2007 A1
20070191716 Goldberger et al. Aug 2007 A1
20070197163 Robertson Aug 2007 A1
20070219432 Thompson Sep 2007 A1
20070219480 Kamen et al. Sep 2007 A1
20070225675 Robinson et al. Sep 2007 A1
20070233521 Wehba et al. Oct 2007 A1
20070239116 Follman et al. Oct 2007 A1
20070244381 Robinson et al. Oct 2007 A1
20070248238 Abreu Oct 2007 A1
20070249007 Rosero Oct 2007 A1
20070252774 Ql et al. Nov 2007 A1
20070255250 Moberg et al. Nov 2007 A1
20070259768 Kear et al. Nov 2007 A1
20070264707 Liederman et al. Nov 2007 A1
20070282269 Carter et al. Dec 2007 A1
20070282299 Hellwig Dec 2007 A1
20070287931 Dilorenzo Dec 2007 A1
20070287985 Estes et al. Dec 2007 A1
20070293843 Ireland et al. Dec 2007 A1
20080009824 Moberg et al. Jan 2008 A1
20080015422 Wessel Jan 2008 A1
20080027574 Thomas Jan 2008 A1
20080031481 Warren et al. Feb 2008 A1
20080033272 Gough et al. Feb 2008 A1
20080033320 Racchini et al. Feb 2008 A1
20080045891 Maule et al. Feb 2008 A1
20080051697 Mounce et al. Feb 2008 A1
20080051698 Mounce et al. Feb 2008 A1
20080051714 Moberg et al. Feb 2008 A1
20080051716 Stutz Feb 2008 A1
20080051730 Bikovsky Feb 2008 A1
20080051738 Griffin Feb 2008 A1
20080051764 Dent et al. Feb 2008 A1
20080058625 McGarraugh et al. Mar 2008 A1
20080065050 Sparks et al. Mar 2008 A1
20080071157 McGarraugh et al. Mar 2008 A1
20080071158 McGarraugh et al. Mar 2008 A1
20080077081 Mounce et al. Mar 2008 A1
20080078400 Martens et al. Apr 2008 A1
20080097289 Steil et al. Apr 2008 A1
20080097326 Moberg et al. Apr 2008 A1
20080097375 Bikovsky Apr 2008 A1
20080097381 Moberg et al. Apr 2008 A1
20080103022 Dvorak et al. May 2008 A1
20080109050 John May 2008 A1
20080114304 Nalesso et al. May 2008 A1
20080125700 Moberg et al. May 2008 A1
20080125701 Moberg et al. May 2008 A1
20080129535 Thompson et al. Jun 2008 A1
20080132880 Buchman Jun 2008 A1
20080160492 Campbell et al. Jul 2008 A1
20080161664 Mastrototaro et al. Jul 2008 A1
20080172026 Blomquist Jul 2008 A1
20080172027 Blomquist Jul 2008 A1
20080172028 Blomquist Jul 2008 A1
20080172029 Blomquist Jul 2008 A1
20080177149 Weinert et al. Jul 2008 A1
20080183060 Steil et al. Jul 2008 A1
20080188796 Steil et al. Aug 2008 A1
20080198012 Kamen Aug 2008 A1
20080200838 Goldberger et al. Aug 2008 A1
20080201325 Doniger et al. Aug 2008 A1
20080206067 De et al. Aug 2008 A1
20080208113 Damiano et al. Aug 2008 A1
20080208627 Skyggebjerg Aug 2008 A1
20080214919 Harmon et al. Sep 2008 A1
20080215035 Yodfat et al. Sep 2008 A1
20080228056 Blomquist et al. Sep 2008 A1
20080234630 Iddan et al. Sep 2008 A1
20080249386 Besterman et al. Oct 2008 A1
20080255516 Yodfat et al. Oct 2008 A1
20080269585 Ginsberg Oct 2008 A1
20080269683 Bikovsky Oct 2008 A1
20080269687 Chong et al. Oct 2008 A1
20080269714 Mastrototaro et al. Oct 2008 A1
20080269723 Mastrototaro et al. Oct 2008 A1
20080287906 Burkholz et al. Nov 2008 A1
20080294094 Mhatre et al. Nov 2008 A1
20080294109 Estes et al. Nov 2008 A1
20080294142 Patel et al. Nov 2008 A1
20080300572 Rankers et al. Dec 2008 A1
20080306434 Dobbles et al. Dec 2008 A1
20080306444 Brister et al. Dec 2008 A1
20080312512 Brukalo et al. Dec 2008 A1
20080312634 Helmerson et al. Dec 2008 A1
20080319381 Yodfat et al. Dec 2008 A1
20080319383 Byland et al. Dec 2008 A1
20080319384 Yodfat et al. Dec 2008 A1
20080319394 Yodfat et al. Dec 2008 A1
20080319414 Yodfat et al. Dec 2008 A1
20080319416 Yodfat et al. Dec 2008 A1
20090006061 Thukral et al. Jan 2009 A1
20090018406 Yodfat et al. Jan 2009 A1
20090030398 Yodfat et al. Jan 2009 A1
20090036753 King Feb 2009 A1
20090036760 Hayter Feb 2009 A1
20090036870 Mounce et al. Feb 2009 A1
20090043240 Robinson et al. Feb 2009 A1
20090043291 Thompson Feb 2009 A1
20090048584 Thompson Feb 2009 A1
20090054753 Robinson et al. Feb 2009 A1
20090069743 Krishnamoorthy et al. Mar 2009 A1
20090069745 Estes et al. Mar 2009 A1
20090069746 Miller et al. Mar 2009 A1
20090069749 Miller et al. Mar 2009 A1
20090069784 Estes et al. Mar 2009 A1
20090069785 Miller et al. Mar 2009 A1
20090069787 Estes et al. Mar 2009 A1
20090076453 Mejlhede et al. Mar 2009 A1
20090076849 Diller Mar 2009 A1
20090082728 Bikovsky Mar 2009 A1
20090093756 Minaie et al. Apr 2009 A1
20090099507 Koops Apr 2009 A1
20090099521 Gravesen et al. Apr 2009 A1
20090105573 Malecha Apr 2009 A1
20090105636 Hayter et al. Apr 2009 A1
20090112333 Sahai Apr 2009 A1
20090118664 Estes et al. May 2009 A1
20090131861 Braig et al. May 2009 A1
20090143916 Boll et al. Jun 2009 A1
20090156922 Goldberger et al. Jun 2009 A1
20090156924 Shariati et al. Jun 2009 A1
20090156990 Wenger et al. Jun 2009 A1
20090163781 Say et al. Jun 2009 A1
20090164190 Hayter Jun 2009 A1
20090177142 Blomquist et al. Jul 2009 A1
20090177154 Blomquist Jul 2009 A1
20090192722 Shariati et al. Jul 2009 A1
20090198191 Chong et al. Aug 2009 A1
20090198215 Chong et al. Aug 2009 A1
20090198350 Thiele Aug 2009 A1
20090212966 Panduro Aug 2009 A1
20090221890 Saffer et al. Sep 2009 A1
20090228214 Say et al. Sep 2009 A1
20090275887 Estes Nov 2009 A1
20090318791 Kaastrup Dec 2009 A1
20090326343 Gable et al. Dec 2009 A1
20090326472 Carter et al. Dec 2009 A1
20100010330 Rankers et al. Jan 2010 A1
20100017141 Campbell et al. Jan 2010 A1
20100036326 Matusch Feb 2010 A1
20100057040 Hayter Mar 2010 A1
20100057041 Hayter Mar 2010 A1
20100064243 Buck et al. Mar 2010 A1
20100077198 Buck et al. Mar 2010 A1
20100094078 Weston Apr 2010 A1
20100114026 Karratt et al. May 2010 A1
20100121167 McGarraugh May 2010 A1
20100137784 Cefai et al. Jun 2010 A1
20100145272 Cefai et al. Jun 2010 A1
20100152658 Hanson et al. Jun 2010 A1
20100165795 Elder et al. Jul 2010 A1
20100168538 Keenan et al. Jul 2010 A1
20100168820 Maniak et al. Jul 2010 A1
20100174228 Buckingham et al. Jul 2010 A1
20100174229 Hsu et al. Jul 2010 A1
20100174266 Estes Jul 2010 A1
20100179409 Kamath et al. Jul 2010 A1
20100185183 Alme et al. Jul 2010 A1
20100211003 Sundar et al. Aug 2010 A1
20100211005 Edwards et al. Aug 2010 A1
20100241066 Hansen et al. Sep 2010 A1
20100249530 Rankers et al. Sep 2010 A1
20100262117 Magni et al. Oct 2010 A1
20100262434 Shaya Oct 2010 A1
20100273738 Valcke et al. Oct 2010 A1
20100286601 Yodfat et al. Nov 2010 A1
20100286653 Kubel et al. Nov 2010 A1
20100298685 Hayter et al. Nov 2010 A1
20100298765 Budiman et al. Nov 2010 A1
20100324382 Cantwell et al. Dec 2010 A1
20100324977 Dragt Dec 2010 A1
20100325864 Briones et al. Dec 2010 A1
20110009813 Rankers Jan 2011 A1
20110015511 Bousamra et al. Jan 2011 A1
20110021584 Berggren et al. Jan 2011 A1
20110028817 Jin et al. Feb 2011 A1
20110040247 Mandro et al. Feb 2011 A1
20110049394 De Rochemont Mar 2011 A1
20110054390 Searle et al. Mar 2011 A1
20110054399 Chong et al. Mar 2011 A1
20110065224 Bollman et al. Mar 2011 A1
20110071464 Palerm Mar 2011 A1
20110071765 Yodfat et al. Mar 2011 A1
20110098637 Hill Apr 2011 A1
20110098674 Vicente et al. Apr 2011 A1
20110105955 Yudovsky et al. May 2011 A1
20110106050 Yodfat et al. May 2011 A1
20110118699 Yodfat et al. May 2011 A1
20110124996 Reinke et al. May 2011 A1
20110130716 Estes et al. Jun 2011 A1
20110144586 Michaud et al. Jun 2011 A1
20110160652 Yodfat et al. Jun 2011 A1
20110163880 Halff et al. Jul 2011 A1
20110178472 Cabiri Jul 2011 A1
20110190694 Lanier et al. Aug 2011 A1
20110199194 Waldock et al. Aug 2011 A1
20110202005 Yodfat et al. Aug 2011 A1
20110218495 Remde Sep 2011 A1
20110224523 Budiman Sep 2011 A1
20110230833 Landman et al. Sep 2011 A1
20110251509 Beyhan et al. Oct 2011 A1
20110313390 Roy et al. Dec 2011 A1
20110313680 Doyle et al. Dec 2011 A1
20110316562 Cefai et al. Dec 2011 A1
20110319813 Kamen et al. Dec 2011 A1
20120003935 Lydon et al. Jan 2012 A1
20120010594 Holt et al. Jan 2012 A1
20120016304 Patel et al. Jan 2012 A1
20120029468 Diperna et al. Feb 2012 A1
20120030393 Ganesh et al. Feb 2012 A1
20120046606 Arefieg Feb 2012 A1
20120053556 Lee Mar 2012 A1
20120065894 Tubb et al. Mar 2012 A1
20120078067 Kovatchev et al. Mar 2012 A1
20120078161 Masterson et al. Mar 2012 A1
20120078181 Smith et al. Mar 2012 A1
20120101451 Boit et al. Apr 2012 A1
20120123234 Atlas et al. May 2012 A1
20120124521 Guo May 2012 A1
20120150446 Chang et al. Jun 2012 A1
20120150556 Galasso et al. Jun 2012 A1
20120172694 Desborough et al. Jul 2012 A1
20120172802 Blomquist Jul 2012 A1
20120185267 Kamen et al. Jul 2012 A1
20120190955 Rao et al. Jul 2012 A1
20120197207 Stefanski Aug 2012 A1
20120203085 Rebec Aug 2012 A1
20120203178 Tverskoy Aug 2012 A1
20120203467 Kamath et al. Aug 2012 A1
20120209208 Stefanski Aug 2012 A1
20120215087 Cobelli et al. Aug 2012 A1
20120225134 Komorowski Sep 2012 A1
20120226259 Yodfat et al. Sep 2012 A1
20120227737 Mastrototaro et al. Sep 2012 A1
20120232520 Sloan et al. Sep 2012 A1
20120238851 Kamen et al. Sep 2012 A1
20120238853 Arefieg Sep 2012 A1
20120238999 Estes et al. Sep 2012 A1
20120245448 Shariati et al. Sep 2012 A1
20120245556 Kovatchev et al. Sep 2012 A1
20120245855 Kamath et al. Sep 2012 A1
20120246106 Atlas et al. Sep 2012 A1
20120250449 Nakano Oct 2012 A1
20120259191 Shariati et al. Oct 2012 A1
20120271655 Knobel et al. Oct 2012 A1
20120277668 Chawla Nov 2012 A1
20120277723 Skladnev et al. Nov 2012 A1
20120282111 Nip et al. Nov 2012 A1
20120283694 Yodfat et al. Nov 2012 A1
20120289931 Robinson et al. Nov 2012 A1
20120295550 Wilson et al. Nov 2012 A1
20120302991 Blomquist et al. Nov 2012 A1
20120323590 Udani Dec 2012 A1
20120330270 Colton Dec 2012 A1
20130030358 Yodfat et al. Jan 2013 A1
20130046281 Javitt Feb 2013 A1
20130053818 Estes Feb 2013 A1
20130053819 Estes Feb 2013 A1
20130053820 Estes et al. Feb 2013 A1
20130102867 Desborough et al. Apr 2013 A1
20130116649 Breton et al. May 2013 A1
20130138205 Kushwaha et al. May 2013 A1
20130158503 Kanderian et al. Jun 2013 A1
20130159456 Daoud et al. Jun 2013 A1
20130165041 Bukovjan et al. Jun 2013 A1
20130172695 Nielsen et al. Jul 2013 A1
20130172710 Mears et al. Jul 2013 A1
20130178791 Javitt Jul 2013 A1
20130204186 Moore et al. Aug 2013 A1
20130204202 Trombly et al. Aug 2013 A1
20130218126 Hayter et al. Aug 2013 A1
20130231642 Doyle et al. Sep 2013 A1
20130237932 Thueer et al. Sep 2013 A1
20130245545 Arnold et al. Sep 2013 A1
20130245563 Mercer et al. Sep 2013 A1
20130245604 Kouyoumjian et al. Sep 2013 A1
20130253284 Fraier et al. Sep 2013 A1
20130253418 Kamath et al. Sep 2013 A1
20130253472 Cabiri Sep 2013 A1
20130261406 Rebec et al. Oct 2013 A1
20130275139 Coleman Oct 2013 A1
20130281965 Kamen et al. Oct 2013 A1
20130296792 Cabiri Nov 2013 A1
20130296823 Melker et al. Nov 2013 A1
20130297334 Galasso et al. Nov 2013 A1
20130298080 Griffin et al. Nov 2013 A1
20130317753 Kamen et al. Nov 2013 A1
20130332874 Rosinko et al. Dec 2013 A1
20130338576 O'Connor et al. Dec 2013 A1
20130338629 Agrawal et al. Dec 2013 A1
20130338630 Agrawal et al. Dec 2013 A1
20130345663 Agrawal et al. Dec 2013 A1
20130346858 Neyrinck Dec 2013 A1
20140005633 Finan Jan 2014 A1
20140018730 Stephan Jan 2014 A1
20140025015 Cross et al. Jan 2014 A1
20140031759 Kouyoumjian et al. Jan 2014 A1
20140032549 McDaniel et al. Jan 2014 A1
20140039383 Dobbles et al. Feb 2014 A1
20140052091 Dobbles et al. Feb 2014 A1
20140052092 Dobbles et al. Feb 2014 A1
20140052093 Dobbles et al. Feb 2014 A1
20140052094 Dobbles et al. Feb 2014 A1
20140052095 Dobbles et al. Feb 2014 A1
20140066859 Ogawa et al. Mar 2014 A1
20140066884 Keenan et al. Mar 2014 A1
20140066885 Keenan et al. Mar 2014 A1
20140066886 Roy et al. Mar 2014 A1
20140066887 Mastrototaro et al. Mar 2014 A1
20140066888 Parikh et al. Mar 2014 A1
20140066889 Grosman et al. Mar 2014 A1
20140066890 Sloan et al. Mar 2014 A1
20140066892 Keenan et al. Mar 2014 A1
20140074033 Sonderegger et al. Mar 2014 A1
20140088428 Yang et al. Mar 2014 A1
20140088557 Mernoe et al. Mar 2014 A1
20140094766 Estes et al. Apr 2014 A1
20140107607 Estes Apr 2014 A1
20140108046 Echeverria et al. Apr 2014 A1
20140114278 Dobbles et al. Apr 2014 A1
20140121635 Hayter May 2014 A1
20140127048 Diianni et al. May 2014 A1
20140128705 Mazlish May 2014 A1
20140128803 Dobbles et al. May 2014 A1
20140128839 Diianni et al. May 2014 A1
20140129951 Amin et al. May 2014 A1
20140135880 Baumgartner et al. May 2014 A1
20140142508 Diianni et al. May 2014 A1
20140146202 Boss et al. May 2014 A1
20140171901 Langsdorf et al. Jun 2014 A1
20140180203 Budiman et al. Jun 2014 A1
20140180240 Finan et al. Jun 2014 A1
20140200426 Taub et al. Jul 2014 A1
20140200559 Doyle et al. Jul 2014 A1
20140228627 Soffer et al. Aug 2014 A1
20140228668 Wakizaka et al. Aug 2014 A1
20140230021 Birtwhistle et al. Aug 2014 A1
20140235981 Hayter Aug 2014 A1
20140249500 Estes Sep 2014 A1
20140276553 Rosinko et al. Sep 2014 A1
20140276554 Finan et al. Sep 2014 A1
20140276555 Morales Sep 2014 A1
20140276556 Saint et al. Sep 2014 A1
20140276583 Chen et al. Sep 2014 A1
20140278123 Prodhom et al. Sep 2014 A1
20140309615 Mazlish Oct 2014 A1
20140316379 Sonderegger et al. Oct 2014 A1
20140323959 Lebel et al. Oct 2014 A1
20140325065 Birtwhistle et al. Oct 2014 A1
20150018633 Kovachev et al. Jan 2015 A1
20150025329 Amarasingham et al. Jan 2015 A1
20150025471 Enggaard Jan 2015 A1
20150025495 Peyser Jan 2015 A1
20150025503 Searle et al. Jan 2015 A1
20150030641 Anderson et al. Jan 2015 A1
20150041498 Kakiuchi et al. Feb 2015 A1
20150045737 Stefanski Feb 2015 A1
20150073337 Saint et al. Mar 2015 A1
20150080789 Estes et al. Mar 2015 A1
20150120317 Mayou et al. Apr 2015 A1
20150120323 Galasso et al. Apr 2015 A1
20150134265 Kohlbrecher et al. May 2015 A1
20150134353 Ferrell et al. May 2015 A1
20150136336 Huang et al. May 2015 A1
20150148774 Yao May 2015 A1
20150157794 Roy et al. Jun 2015 A1
20150164414 Matthews Jun 2015 A1
20150165119 Palerm et al. Jun 2015 A1
20150173674 Hayes et al. Jun 2015 A1
20150193585 Sunna Jul 2015 A1
20150202386 Brady et al. Jul 2015 A1
20150205509 Scriven et al. Jul 2015 A1
20150205511 Vinna et al. Jul 2015 A1
20150213217 Amarasingham et al. Jul 2015 A1
20150217051 Mastrototaro et al. Aug 2015 A1
20150217052 Keenan et al. Aug 2015 A1
20150217053 Booth et al. Aug 2015 A1
20150265767 Vazquez et al. Sep 2015 A1
20150265768 Vazquez et al. Sep 2015 A1
20150301691 Qin Oct 2015 A1
20150306314 Doyle et al. Oct 2015 A1
20150314062 Blomquist et al. Nov 2015 A1
20150320933 Estes Nov 2015 A1
20150328402 Nogueira et al. Nov 2015 A1
20150331995 Zhao et al. Nov 2015 A1
20150351671 Vanslyke et al. Dec 2015 A1
20150351672 Vanslyke et al. Dec 2015 A1
20150351683 Brauker et al. Dec 2015 A1
20150352282 Mazlish Dec 2015 A1
20150352283 Galasso Dec 2015 A1
20150356250 Polimeni Dec 2015 A1
20150366945 Greene Dec 2015 A1
20160000998 Estes Jan 2016 A1
20160015891 Papiorek Jan 2016 A1
20160019352 Cohen et al. Jan 2016 A1
20160030669 Harris et al. Feb 2016 A1
20160038673 Morales Feb 2016 A1
20160038689 Lee et al. Feb 2016 A1
20160051749 Istoc Feb 2016 A1
20160082187 Schaible et al. Mar 2016 A1
20160082188 Blomquist et al. Mar 2016 A1
20160089494 Guerrini Mar 2016 A1
20160158438 Monirabbasi et al. Jun 2016 A1
20160162662 Monirabbasi et al. Jun 2016 A1
20160175520 Palerm et al. Jun 2016 A1
20160213841 Geismar et al. Jul 2016 A1
20160220181 Rigoard et al. Aug 2016 A1
20160228641 Gescheit et al. Aug 2016 A1
20160243318 Despa et al. Aug 2016 A1
20160256087 Doyle et al. Sep 2016 A1
20160256629 Grosman et al. Sep 2016 A1
20160259889 Murtha et al. Sep 2016 A1
20160287512 Cooper et al. Oct 2016 A1
20160302054 Kimura et al. Oct 2016 A1
20160331310 Kovatchev Nov 2016 A1
20160354543 Cinar et al. Dec 2016 A1
20170007882 Werner Jan 2017 A1
20170021096 Cole et al. Jan 2017 A1
20170049386 Abraham et al. Feb 2017 A1
20170131887 Kim et al. May 2017 A1
20170143899 Gondhalekar et al. May 2017 A1
20170143900 Rioux et al. May 2017 A1
20170156682 Doyle et al. Jun 2017 A1
20170173261 O'Connor et al. Jun 2017 A1
20170182248 Rosinko Jun 2017 A1
20170188943 Braig et al. Jul 2017 A1
20170189614 Mazlish et al. Jul 2017 A1
20170189625 Cirillo et al. Jul 2017 A1
20170203036 Mazlish et al. Jul 2017 A1
20170216524 Haider et al. Aug 2017 A1
20170239415 Hwang et al. Aug 2017 A1
20170258987 Caspers Sep 2017 A1
20170281877 Marlin et al. Oct 2017 A1
20170296746 Chen et al. Oct 2017 A1
20170311903 Davis et al. Nov 2017 A1
20170347971 Davis et al. Dec 2017 A1
20170348482 Duke et al. Dec 2017 A1
20180036495 Searle et al. Feb 2018 A1
20180040255 Freeman et al. Feb 2018 A1
20180075200 Davis et al. Mar 2018 A1
20180075201 Davis et al. Mar 2018 A1
20180075202 Davis et al. Mar 2018 A1
20180092576 Ambrsio Apr 2018 A1
20180126073 Wu et al. May 2018 A1
20180169334 Grosman et al. Jun 2018 A1
20180200434 Mazlish et al. Jul 2018 A1
20180200438 Mazlish et al. Jul 2018 A1
20180200441 Desborough et al. Jul 2018 A1
20180204636 Edwards et al. Jul 2018 A1
20180277253 Gondhalekar et al. Sep 2018 A1
20180289891 Finan et al. Oct 2018 A1
20180296757 Finan et al. Oct 2018 A1
20180307515 Meller et al. Oct 2018 A1
20180342317 Skirble et al. Nov 2018 A1
20180369479 Hayter et al. Dec 2018 A1
20190076600 Grosman et al. Mar 2019 A1
20190095052 De et al. Mar 2019 A1
20190132801 Kamath et al. May 2019 A1
20190184091 Sjolund et al. Jun 2019 A1
20190240403 Palerm et al. Aug 2019 A1
20190290844 Monirabbasi et al. Sep 2019 A1
20190321545 Saint Oct 2019 A1
20190336683 O'Connor et al. Nov 2019 A1
20190336684 O'Connor et al. Nov 2019 A1
20190348157 Booth et al. Nov 2019 A1
20190374714 Rioux et al. Dec 2019 A1
20200001006 Pizzochero et al. Jan 2020 A1
20200046268 Patek et al. Feb 2020 A1
20200101222 Lintereur et al. Apr 2020 A1
20200101223 Lintereur et al. Apr 2020 A1
20200101225 O'Connor et al. Apr 2020 A1
20200113515 O'Connor et al. Apr 2020 A1
20200219625 Kahlbaugh Jul 2020 A1
20200342974 Chen et al. Oct 2020 A1
20210050085 Hayter et al. Feb 2021 A1
20210098105 Lee et al. Apr 2021 A1
20220023536 Graham et al. Jan 2022 A1
20220105270 Doyle et al. Apr 2022 A1
20220126027 Narayanaswami Apr 2022 A1
Foreign Referenced Citations (249)
Number Date Country
2015200834 Mar 2015 AU
2015301146 Mar 2017 AU
1040271 Oct 1978 CA
2543545 May 2005 CA
3026851 Feb 2020 CA
1297140 May 2001 CN
1859943 Nov 2006 CN
101208699 Jun 2008 CN
4200595 Jul 1993 DE
19627619 Jan 1998 DE
19756872 Jul 1999 DE
19912459 Sep 2000 DE
10236669 Feb 2004 DE
202005012358 Oct 2005 DE
200401893 Dec 2004 DK
0026056 Apr 1981 EP
0062974 Oct 1982 EP
0098592 Jan 1984 EP
0275213 Jul 1988 EP
0341049 Nov 1989 EP
0496141 Jul 1992 EP
0496305 Jul 1992 EP
0549341 Jun 1993 EP
0580723 Feb 1994 EP
0612004 Aug 1994 EP
0721358 Jul 1996 EP
0867196 Sep 1998 EP
0939451 Sep 1999 EP
1045146 Oct 2000 EP
1136698 Sep 2001 EP
1376759 Jan 2004 EP
1177802 Sep 2004 EP
1491144 Dec 2004 EP
1495775 Jan 2005 EP
1527792 May 2005 EP
1571582 Sep 2005 EP
0801578 Jul 2006 EP
1754498 Feb 2007 EP
1818664 Aug 2007 EP
1824536 Aug 2007 EP
1951340 Aug 2008 EP
2139382 Jan 2010 EP
2397181 Dec 2011 EP
2468338 Jun 2012 EP
2666520 Nov 2013 EP
2695573 Feb 2014 EP
2703024 Mar 2014 EP
2764881 Aug 2014 EP
2830499 Feb 2015 EP
2897071 Jul 2015 EP
2943149 Nov 2015 EP
3177344 Jun 2017 EP
3193979 Jul 2017 EP
3314548 May 2018 EP
3607985 Feb 2020 EP
2096275 Feb 1972 FR
2585252 Jan 1987 FR
0747701 Apr 1956 GB
1125897 Sep 1968 GB
2218831 Nov 1989 GB
2443261 Apr 2008 GB
51-125993 Nov 1976 JP
02-131777 May 1990 JP
09-504974 May 1997 JP
11-010036 Jan 1999 JP
2000-513974 Oct 2000 JP
2002-085556 Mar 2002 JP
2002-507459 Mar 2002 JP
2002-523149 Jul 2002 JP
2003-531691 Oct 2003 JP
2004-283378 Oct 2004 JP
2005-326943 Nov 2005 JP
2007-525276 Sep 2007 JP
2008-513142 May 2008 JP
2010-502361 Jan 2010 JP
2010-524639 Jul 2010 JP
2012-527981 Nov 2012 JP
2017-516548 Jun 2017 JP
2017-525451 Sep 2017 JP
2018-153569 Oct 2018 JP
2019-525276 Sep 2019 JP
200740148 Oct 2007 TW
M452390 May 2013 TW
8606796 Nov 1986 WO
9015928 Dec 1990 WO
9509021 Apr 1995 WO
9721457 Jun 1997 WO
9800193 Jan 1998 WO
9804301 Feb 1998 WO
9811927 Mar 1998 WO
9855073 Dec 1998 WO
9857683 Dec 1998 WO
9907425 Feb 1999 WO
9910040 Mar 1999 WO
9910049 Mar 1999 WO
9921596 May 1999 WO
9939118 Aug 1999 WO
9948546 Sep 1999 WO
9956803 Nov 1999 WO
9962576 Dec 1999 WO
0030705 Jun 2000 WO
0032258 Jun 2000 WO
0048112 Aug 2000 WO
0154753 Aug 2001 WO
0172354 Oct 2001 WO
0172360 Oct 2001 WO
0178812 Oct 2001 WO
0191822 Dec 2001 WO
0191833 Dec 2001 WO
0215954 Feb 2002 WO
0226282 Apr 2002 WO
0240083 May 2002 WO
0243866 Jun 2002 WO
0257627 Jul 2002 WO
0268015 Sep 2002 WO
0276535 Oct 2002 WO
0281012 Oct 2002 WO
0282990 Oct 2002 WO
0284336 Oct 2002 WO
2002100469 Dec 2002 WO
0316882 Feb 2003 WO
0323728 Mar 2003 WO
0326728 Mar 2003 WO
0326726 Apr 2003 WO
0339362 May 2003 WO
0345233 Jun 2003 WO
0397133 Nov 2003 WO
2003103763 Dec 2003 WO
2004041330 May 2004 WO
2004043250 May 2004 WO
2004056412 Jul 2004 WO
2004092715 Oct 2004 WO
2004093648 Nov 2004 WO
2004110526 Dec 2004 WO
2005002652 Jan 2005 WO
2005011779 Feb 2005 WO
2005011799 Feb 2005 WO
2005039673 May 2005 WO
2005051170 Jun 2005 WO
2005072794 Aug 2005 WO
2005072795 Aug 2005 WO
2005082436 Sep 2005 WO
2005110601 Nov 2005 WO
2005113036 Dec 2005 WO
2006053007 May 2006 WO
2006061354 Jun 2006 WO
2006067217 Jun 2006 WO
2006075016 Jul 2006 WO
2006097453 Sep 2006 WO
2006105792 Oct 2006 WO
2006105793 Oct 2006 WO
2006105794 Oct 2006 WO
2007005219 Jan 2007 WO
2007056247 May 2007 WO
2007056504 May 2007 WO
2007056592 May 2007 WO
2007064835 Jun 2007 WO
2007066152 Jun 2007 WO
2007071255 Jun 2007 WO
2007078937 Jul 2007 WO
2007078992 Jul 2007 WO
2007141786 Dec 2007 WO
2008016621 Feb 2008 WO
2008024810 Feb 2008 WO
2008029403 Mar 2008 WO
2008073609 Jun 2008 WO
2008089184 Jul 2008 WO
2008103175 Aug 2008 WO
2008133702 Nov 2008 WO
2008134146 Nov 2008 WO
2009032402 Mar 2009 WO
2009035759 Mar 2009 WO
2009039203 Mar 2009 WO
2009045462 Apr 2009 WO
2009049252 Apr 2009 WO
2009066287 May 2009 WO
2009066288 May 2009 WO
2009098648 Aug 2009 WO
2009134380 Nov 2009 WO
2010022069 Feb 2010 WO
2010045460 Apr 2010 WO
2010053702 May 2010 WO
2010077279 Jul 2010 WO
2010097796 Sep 2010 WO
2010132077 Nov 2010 WO
2010138848 Dec 2010 WO
2010139793 Dec 2010 WO
2010147659 Dec 2010 WO
2011031458 Mar 2011 WO
2011075042 Jun 2011 WO
2011095483 Aug 2011 WO
2011133823 Oct 2011 WO
2012045667 Apr 2012 WO
2012073032 Jun 2012 WO
2012108959 Aug 2012 WO
2012134588 Oct 2012 WO
2012177353 Dec 2012 WO
2012178134 Dec 2012 WO
2013050535 Apr 2013 WO
2013078200 May 2013 WO
2013134486 Sep 2013 WO
2013149186 Oct 2013 WO
2013177565 Nov 2013 WO
2013182321 Dec 2013 WO
2014029416 Feb 2014 WO
2014035672 Mar 2014 WO
2014062399 Apr 2014 WO
2014074476 May 2014 WO
2014109898 Jul 2014 WO
2014110538 Jul 2014 WO
2014134459 Sep 2014 WO
2014149357 Sep 2014 WO
2014172467 Oct 2014 WO
2014179774 Nov 2014 WO
2014194183 Dec 2014 WO
2015056259 Apr 2015 WO
2015061493 Apr 2015 WO
2015073211 May 2015 WO
2015081337 Jun 2015 WO
2015117082 Aug 2015 WO
2015117854 Aug 2015 WO
2015167201 Nov 2015 WO
2015177082 Nov 2015 WO
2015187366 Dec 2015 WO
2015191459 Dec 2015 WO
2016004088 Jan 2016 WO
2016004210 Jan 2016 WO
2016022650 Feb 2016 WO
2016041873 Mar 2016 WO
2016089702 Jun 2016 WO
2016141082 Sep 2016 WO
2016161254 Oct 2016 WO
2017004278 Jan 2017 WO
2017091624 Jun 2017 WO
2017105600 Jun 2017 WO
2017184988 Oct 2017 WO
2017187177 Nov 2017 WO
2017205816 Nov 2017 WO
2018009614 Jan 2018 WO
2018067748 Apr 2018 WO
2018120104 Jul 2018 WO
2018136799 Jul 2018 WO
2018204568 Nov 2018 WO
2019077482 Apr 2019 WO
2019094440 May 2019 WO
2019213493 Nov 2019 WO
2019246381 Dec 2019 WO
2020081393 Apr 2020 WO
2021011738 Jan 2021 WO
Non-Patent Literature Citations (51)
Entry
US 5,954,699 A, 09/1999, Jost et al. (withdrawn)
International Preliminary Report on Patentability in Application No. PCT/US2017/013112, dated Jul. 26, 2018, 6 pages.
International Search Report and Written Opinion in Application No. PCT/US2017/013112, dated May 15, 2017, 9 pages.
Percival et al., “Closed-Loop Control and Advisory Mode Evaluation of an Artificial Pancreatic B Cell: Use of Proportional-Integral-Derivative Equivalent Model-Based Controllers,” J Diabetes Sci Tech 2(4):636-644, Jul. 2008.
European Examination Report from European Application No. 17701779.5, dated Sep. 30, 2021, 8 pages.
Decision to grant received for European Patent Application No. 14826694.3, mailed on Apr. 4, 2019, 2 pages.
European Communication pursuant to Article 94(3) EPC for European Application No. 14826694.3, dated Oct. 12, 2017, 4 pages.
Intention to grant received for European Patent Application No. 14826694.3, mailed on Mar. 20, 2019, 4 pages.
Intention to grant received for European Patent Application No. 14826694.3, mailed on Oct. 2, 2018, 6 pages.
Supplementary European Extended Search Report and Opinion for European Application No. 14826694.3., dated Jul. 1, 2016, 7 pages.
“Minimed Inc. Introduces 407C Infusion Pump for General Medication Use” [online]. Business Wire, AllBusiness.com, Aug. 10, 1999 [retrieved on Feb. 28, 2011]. Retrieved from the Internet: <URL: http://www.allbusiness.com/company-activities-management/product-management/6734565-1.html>.
“Using the Deltec Cozmo Insulin Pump Correction Bolus Feature” believed to be publicly available before May 5, 2008, pp. 36-41.
“Which Insulin Pump is Right for Me?”, Albany Medical Center, Goodman Diabetes Service, Jan. 2006, 4 pages.
Accu-Chek Spirit, “Pump Therapy Made for You,” Roche, 2006, 6 pages.
Animas Corporation, IR1200 User Guide Manual, pp. 29-31, revised Sep. 2006.
Asante Solutions Pearl User Manual, Asante Inc., 2012, 180 pages.
Brown et al., “CGM, Pumps, and SMBG.” American Diabetes Association—71st Scientific Sessions, San Diego, CA, Jun. 24-28, 2011, 38 pages.
Collins and Lee, “Microfluidic flow transducer based on the measurement of electrical admittance,” Lab Chip, 2004, 4:7-10.
Copp et al., “Simultaneous Model Predictive Control and Moving Horizon Estimation for Blood Glucose Regulation in Type 1 Diabetes,” Optim. Control Appl. Meth. 2016, 15 pages.
Cox et al. “Prediction of Severe Hypoglycemia.” Diabetes Care, vol. 30, No. 6, Jun. 2007, 4 pages.
Dassau et al., “12-Week 24/7 Ambulatory Artificial Pancreas With Weekly Adaptation of Insulin Delivery Settings: Effect on Hemoglobin Alc and Hypoglycemia” Diabetes Care, Dec. 1, 2017, 40(12):1719-26.
Debiotech SA; Debiotech reveals its new miniaturized Disposable Insulin Nanopump} for Diabetes therapy (news release); retrieved from the internet: (http://web.archive.org/web/20060822033820/http://www.debiotech.com/news/nw_159.html); 3 pgs.; Apr. 24, 2006.
DOCNews; The latest in high-tech and convenient devices; American Diabetes Assoc.; 2(7); retrieved from the internet: (http://web.archive.org/web/20080526162751/http://docnews.diabetesjournals.org/cgi/content/full/2/7/13?); 3 pgs.; Jul. 1, 2005.
Duden Deutsches Universaiworterbuch, Dudenveriag, Mannheim, 1989, p. 822.
Dumont, “Feedback control for clinicians,” Journal of clinical monitoring and computing, Feb. 1, 2014, 28(1):5-11.
Fischer et al., “In Vivo Comparison of Different Algorithms for the Artificial Beta-Cell,” Artificial organs, May 1, 1985, 9(2):173-9.
Guarnieri et al.; Flexible versus rigid catheters for chronic administration of exogenous agents into central nervous system tissues (abstract only); J Neurosc Meth; 144(2); pp. 147-152; Jun. 2005.
Honan, Matthew. “Apple unveils iPhone” Jan. 9, 2007. MacCentral. Accessed Dec. 29, 2011. 2 pages.
Insulet Corporation; Innovative New System for Managing Diabetes Receives FDA Clearance; The OmniPod (Registered) Insulin Management System (press release); retrieved from the internet: (http://phx.corporate-ir.net/phoenix.zhtml? c=209336&p=irol-newsArticle_pf&ID=988708&highlight=); 2 pg .; Feb. 1, 2005.
Insulet Corporation; OmniPod (Registered) Insulin Management System (quick-start guide); 2 pgs.; (Copyright) 2008.
Keith Hynes et al., “DiAs User Interface: A Patient-Centric Interface for Mobile Artificial Pancreas Systems,” J Diabetes Sci Tech 7(6):1416-1426, Nov. 2013.
Kovatchev et al., “Safety of Outpatient Closed-Loop Control: First Randomized Crossover Trials of a Wearable Artificial Pancreas,” Diabetes Care 37(7):1789-1796, Jul. 2014.
Medtronic News Release, “Medtronic Receives FDA Approval for World's First Insulin Pump with Real-time Continuous Glucose Monitoring,” Apr. 13, 2006, 3 pages.
OmniPod Insulin Management System—Investor Relations—Press Release, Feb. 1, 2005, http://investors.insulet.com/phoenix.zhtml?c=209336&p=irol-newsA- rticle&ID=988708&highlight= 1 page.
OmniPod Quick Start Guide, 2007, 2 pages.
Oxford Advanced Learners Dictionary, 4th Ed., Oxford University Press, Oxford, 1989, p. 178.
Patent Abstracts of Japan, vol. 1999, No. 4, and JP 11 010036 , Apr. 30, 1999 and Jan. 19, 1999, Toray Ind. Inc.
Salzsieder et al., “Estimation of individually adapted control parameters for an artificial beta cell,” Biomed. Biochim. Acta, Jan. 1, 1984, 43(5):585-596.
Shiavon et al., “Quantitative Estimation of Insulin Sensitivity in Type 1 Diabetic Subjects Wearing a Sensor-Augmented Insulin Pump,” Diabetes care, May 1, 2014, 37(5):1216-23.
The Content of Investigational Device Exemption (IDE) and Premarket Approval (PMA) Application for Low Glucose Suspend (LGS) Device System. Rockville, MD, Food and Drug Administration, 2011, 59 pages.
The Medtronic Diabetes Connection, 2006, 6 pages.
Vozeh et al., “Feedback Control Methods for Drug Dosage Optimisation, Concepts, Classifications and Clinical Application,” Clinical pharmacokinetics, Nov. 1, 1985, 10(6):457-76.
Walsh et al., “Guidelines for Insulin Dosing in Continuous Subcutaneous Insulin Infusion Using New Formulas from a Retrospective Study of Individuals with Optimal Glucose Levels”, J. Diabetes Science and Technology, vol. 4 Issue 5, Sep. 2010 (8 pages).
Walsh et al., “Guidelines for Optimal Bolus Calculator Settings in Adults”, J. Diabetes Science and Technology; vol. 5 Issue 1; Jan. 2011 (7 pages).
Xilas Temp Touch, “The latest in high-tech and convenient devices,” DOCNews, vol. 2, No. 7, Jul. 1, 2005, http://docnews.diabetesioumals.ord/cgi/content/full/2/7/13, 3 pages.
International Search Report from International Application No. PCT/US06/43599, mailed Mar. 20, 2007, 4 pages.
International Written Opinion from International Application No. PCT/US06/43599, mailed Mar. 20, 2007, 6 pages.
Invitation to Pay Additional Fee received for PCT Patent Application No. PCT/US14/19441, mailed on May 21, 2014, 2 pages.
Examination report No. 1 of Australian Application No. 2023203536, mailed Mar. 8, 2024, 3 pages.
First Office Action and Search Report of Chinese Patent Application No. 202111284422.2, issued Apr. 25, 2024, 16 pages with English translation.
Examination Report of Canadian Patent Application No. 3,009,409, issued Jun. 26, 2024, 3 pages.
Related Publications (1)
Number Date Country
20200206421 A1 Jul 2020 US
Provisional Applications (1)
Number Date Country
62278974 Jan 2016 US
Divisions (1)
Number Date Country
Parent 15404442 Jan 2017 US
Child 16802753 US