User interface for diabetes management system

Description

TECHNICAL FIELD

This document relates a diabetes management system including a pump for dispensing a medicant and a control device for controlling the pump, the control device having a user interface for controlling functions of the pump and providing information related to operation of the pump and other information. For example, the control device can be a mobile computing device in wireless communication with one or more glucose sensors and/or insulin delivery devices and the user interface can be an application running on the mobile computing device.

BACKGROUND

Diabetes mellitus is a chronic metabolic disorder caused by an inability of a person's pancreas to produce sufficient amounts of the hormone, insulin, such that the person's metabolism is unable to provide for the proper absorption of sugar and starch. This failure leads to hyperglycemia, i.e., the presence of an excessive amount of analyte within the blood plasma. Persistent hyperglycemia has been associated with a variety of serious symptoms and life threatening long-term complications such as dehydration, ketoacidosis, diabetic coma, cardiovascular diseases, chronic renal failure, retinal damage and nerve damages with the risk of amputation of extremities. Because healing is not yet possible, a permanent therapy is necessary that provides constant glycemic control in order to constantly maintain the level of blood analyte within normal limits. Such glycemic control is achieved by regularly supplying external drugs to the body of the patient to thereby reduce the elevated levels of blood analyte.

Conventionally, an external biologically effective drug (e.g., insulin or its analog) is commonly administered by means of multiple, daily injections of a mixture of rapid and intermediate acting drug via a hypodermic syringe. While this treatment does not require the frequent estimation of blood analyte, it has been found that the degree of glycemic control achievable in this way is suboptimal because the delivery is unlike physiological hormone production, according to which, hormones enter the bloodstream at a lower rate and over a more extended period of time.

Improved glycemic control may be achieved by the so-called intensive drug therapy which is based on multiple daily injections, including one or two injections per day of a long acting drug for providing a basal level of drug and additional injections of a rapidly acting drug before each meal in an amount proportional to the size of the meal. Although traditional syringes have at least partly been replaced by drug pens, the frequent injections are nevertheless very inconvenient for the patient, particularly those who are incapable of reliably self-administering injections.

Substantial improvements in diabetes therapy have been achieved by the development of other drug delivery devices, such as insulin pumps, relieving the patient of the need for syringes or drug pens and the administration of multiple, daily injections. Insulin pumps allow for the delivery of insulin in a manner that bears greater similarity to the naturally occurring physiological processes and can be controlled to follow standard or individually modified protocols to give the patient better glycemic control. In some circumstances, an insulin pump device can store (via input from a clinician or a user) a number of settings (e.g., dosage parameters or other settings) that are customized by the physician for the particular user. In one example, an infusion pump device can be programmed to store a user's insulin sensitivity (e.g., in units of mg/dL/insulin unit), which can be employed by the infusion pump system when calculating a correction bolus dosage for that particular user. In another example, an infusion pump device can be programmed to store a user's carbohydrate ratio (e.g., in units of g/insulin unit), which can be employed by the infusion pump system when calculating meal bolus dosage for that particular user. In many cases, these user-specific settings are manually input into the infusion pump device via user interface buttons on the infusion pump device. If any of these settings are erroneously input into the infusion pump system (e.g., due to a transcribing error or other error when manually inputting the data), the resulting consequences could lead to improper bolus dosage calculations resulting in blood glucose levels that are unnecessarily too high or too low.

In addition, delivery directly into the intraperitoneal space or intravenously can be achieved by drug delivery devices. Drug delivery devices can be constructed as an implantable device for subcutaneous arrangement or can be constructed as an external device with an infusion set for subcutaneous infusion to the patient via the transcutaneous insertion of a catheter, cannula or a transdermal drug transport such as through a patch. External drug delivery devices are mounted on clothing, hidden beneath or inside clothing, or mounted on the body and are generally controlled via a user interface built-in to the device or on a separate remote device.

Drug delivery devices have been utilized to assist in the management of diabetes by infusing drug or a suitable biologically effective material into the diabetic patient at a basal rate with additional drug or “bolus” to account for meals or high analyte values, levels, or concentrations. The drug delivery device typically is connected to an infuser, better known as an infusion set, by a flexible hose. The infuser typically has a subcutaneous cannula, and an adhesive backed mount on which the cannula is attached. The cannula may include a quick disconnect to allow the cannula and mount to remain in place on the skin surface of the user while the flexible tubing is disconnected from the infuser. Regardless of the type of drug delivery device, blood analyte monitoring is typically required to achieve acceptable glycemic control. For example, delivery of suitable amounts of drug by the drug delivery device requires that the patient frequently determine his or her blood analyte level and manually input this value into a user interface for the external drug delivery device, which then may calculate a suitable modification to the default or currently in-use drug delivery protocol, i.e., dosage and timing, and subsequently communicates with the drug delivery device to adjust its operation accordingly. The determination of blood analyte concentration is typically performed by means of an episodic measuring device such as a hand-held electronic meter, which receives blood samples via enzyme-based test strips and calculates the blood analyte value based on the enzymatic reaction. In recent years, continuous analyte monitoring has also been utilized with drug delivery devices to allow for greater control of the drug(s) being infused into the diabetic patients.

People with diabetes and their health care provider (HCP) bear a great deal of cognitive burden in managing intensive drug therapy. Delivering the correct amount of the drug at the correct time is an extremely challenging endeavor. It requires the patient to make dosing determinations multiple times per day and it requires a combination of the patient and the HCP to re-calibrate the therapeutic parameters of the therapy on an episodic time frame that varies from individual to individual.

In light of the many deficiencies and problems associated with current systems and methods for maintaining proper glycemic control, enormous resources have been put into finding better solutions. Developing workable solutions to the problem that are simple, safe, reliable and able to gain regulatory approval has, however, proved to be elusive. For years, researchers have contemplated coupling a continuous glucose monitoring system with an insulin delivery device to provide an “artificial pancreas” to assist people living with diabetes. Their efforts have yet to result in a commercial product. What has been needed is a system and method that provides a level of automatic control of drug delivery devices for improved drug delivery and glycemic control that is simple, safe, and reliable in a real world setting.

SUMMARY

User interfaces provided herein can simplify the management of diabetes, reduce the cognitive burden on users, and reassure the user that the diabetes management system is acting appropriately to manage the disease. User interfaces provided herein can be designed to highlight actionable information so that an ordinary user can quickly determine an appropriate corrective action. In some cases, user interfaces provided herein can be used to deliver mealtime boluses and/or input therapeutically relevant information. In some cases, user interfaces provided herein can display blood glucose data and project future blood glucose values. In some cases, user interfaces provided herein can display medication delivery information. In some cases, user interfaces provided herein can inform a user about upcoming predicted system maintenance activities and detected problems with the system that require maintenance.

In general, one innovative aspect of the subject matter described in this specification can be embodied in a medical infusion pump system that includes a portable housing defining a space to receive a supply of insulin; a pump drive system to dispense insulin from the portable housing when the supply of insulin is received in the space; control circuitry that electrically communicates with the pump drive system to control dispensation of the insulin from the portable housing when the supply of insulin is received in the space; a blood glucose detection device comprising at least one of a continuous glucose monitor or a blood glucose meter; a user interface device including a display screen and being configured to receive user input and present one or more outputs on the display screen based on information received from the blood glucose detection device. The user interface device is in communication with the control circuitry and provides a graphic user interface on the display screen that includes a first chart depicting a series of blood glucose values received from the blood glucose detection device aligned over a first axis to reflect the times that the blood glucose values were measured by the blood glucose detection device; and a second chart depicting a series of insulin bolus amounts administered by the pump drive system aligned over a second axis to reflect the times that the insulin bolus amounts were administered; wherein the first axis of the first chart and the second axis of the second chart are time-aligned.

These and other embodiments can each optionally include one or more of the following features. The user interface device can be a mobile computing device in wireless communication with the control circuitry. The mobile computing device can be in direct wireless communication with the blood glucose detection device. The mobile computing device can be in indirect wireless communication with the blood glucose detection device via the control circuitry. The medical infusion pump system can include a second blood glucose detection device; wherein the first blood glucose detection device comprises a continuous glucose monitor; wherein the second blood glucose detection device comprises a blood glucose meter; and wherein the first chart depicts a series of blood glucose values received from the continuous glucose monitor aligned over the first axis to reflect the times that the blood glucose values were measured by the continuous glucose monitor, and a series of blood glucose values received from the blood glucose meter aligned over the first axis to reflect the times that the blood glucose values were measured by the blood glucose meter.

The blood glucose values received from the continuous glucose monitor can be depicted using a first symbol and the blood glucose values received from the blood glucose meter can be depicted using a second symbol, the second symbol being larger than the first symbol. The graphic user interface can further include a current time line that passes through the first axis of the first chart and the second axis of the second chart to identify a current time with respect to the first and second charts; wherein the first chart further depicts a projection of future blood glucose values on a right side of the current time line. The graphic user interface can further includes a third chart depicting a step graph of a plurality of basal insulin delivery rates reflecting rates of basil insulin delivery by the pump drive system aligned over a third axis to reflect times of the basal insulin delivery rates; wherein the third axis of the third chart is time-aligned with the first axis of the first chart and the second axis of the second chart.

The graphic user interface can further include a current time line that passes through the first axis of the first chart, the second axis of the second chart, and the third axis of the third chart to identify a current time with respect to the first, second, and third charts; wherein the first chart further depicts a projection of future blood glucose values on a right side of the current time line; and wherein the third chart further depicts a projected basil insulin delivery rate on the right side of the current time line. The graphic user interface can further include a projected blood glucose value and a time for the projected blood glucose value, wherein the time for the projected blood glucose value is between 15 minutes and 4 hours after a most recent blood glucose measurement. The graphic user interface can further include an arrow indicating a projected profile of how blood glucose values are expected to change over a future time period, the time period being a length of time between 30 minutes and 4 hours.

In general, one innovative aspect of the subject matter described in this specification can be embodied in methods that include the actions of: receiving, at a mobile computing device, a plurality of blood glucose measurement values and corresponding measurement times for each of the blood glucose measurement values from a blood glucose detection device, the blood glucose detection device comprising at least one of a continuous glucose monitor or a blood glucose meter; receiving, at the mobile computing device, information indicating a plurality of insulin bolus dosage values for insulin bolus dosages administered by a pump device of the medical infusion pump system and corresponding bolus administration times for each of the insulin bolus dosage values; displaying, by the mobile computing device, a first graphic user interface having a first selectable input; receiving, by the mobile computing device, user selection of the first selectable input of the first graphic user interface; displaying, by the mobile computing device and in response to receiving the selection of the first selectable input, a second graphic user interface, the second graphic user interface including: a first chart depicting the plurality of blood glucose values received from the blood glucose detection device plotted over a first time axis according to the corresponding measurement times for each of the blood glucose measurement values; and a second chart depicting the plurality of insulin bolus dosage values for insulin bolus dosages administered by the pump device plotted over a second time axis according to the corresponding bolus administration times for each of the insulin bolus dosage values; wherein the first time axis of the first chart and the second time axis of the second chart are time-aligned.

These and other embodiments can each optionally include one or more of the following features. The mobile computing device can be in wireless communication with control circuitry in electrical communication with a pump drive system of the pump device to control dispensation of medicine from the pump device and wherein the bolus dosages administered by the pump device are administered in response to control signals communicated from the mobile computing device to the control circuitry. Receiving the plurality of blood glucose measurement values can include receiving a first plurality of blood glucose measurement values from a continuous glucose monitor and receiving a second plurality of blood glucose measurements from a blood glucose meter. The first chart can depict the first plurality of blood glucose measurement values received from the continuous glucose monitor aligned over the first time axis to reflect the times that each of the first plurality of blood glucose measurement values were measured by the continuous glucose monitor, and the second plurality of blood glucose measurement values received from the blood glucose meter aligned over the first time axis to reflect the times that each of the second plurality of blood glucose measurement values were measured by the blood glucose meter. The blood glucose measurement values received from the continuous glucose monitor can be depicted using a first symbol and the blood glucose measurement values received from the blood glucose meter are depicted using a second symbol, the second symbol being larger than the first symbol.

The second graphic user interface can further includes a current time line that passes through the first time axis of the first chart and the second time axis of the second chart to identify a current time with respect to the first and second charts; wherein the first chart further depicts a projection of future blood glucose values on a right side of the current time line. The second graphic user interface can further include a third chart depicting a step graph of a plurality of basal insulin delivery rates reflecting rates of basil insulin delivery by the pump device aligned over a third time axis to reflect times of the basal insulin delivery rates; wherein the third time axis of the third chart is time-aligned with the first time axis of the first chart and the second time axis of the second chart. The second graphic user interface can further include a current time line that passes through the first time axis of the first chart, the second time axis of the second chart, and the third time axis of the third chart to identify a current time with respect to the first, second, and third charts; wherein the first chart further depicts a projection of future blood glucose values on a right side of the current time line; and wherein the third chart further depicts a projected basil insulin delivery rate on the right side of the current time line.

The second graphic user interface can further include a projected blood glucose value and a time for the projected blood glucose value, wherein the time for the projected blood glucose value is between 15 minutes and 4 hours after a most recent blood glucose measurement. The second graphic user interface can further include an arrow indicating a projected profile of how blood glucose values are expected to change over a future time period, the time period being a length of time between 30 minutes and 4 hours.

The details of one or more implementations of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

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

FIG. 1B depicts details of components of an exemplary insulin pump.

FIG. 1C depicts details of components of an exemplary insulin pump controller.

FIG. 2 is an example home screen of a mobile computing application for a diabetes management system.

FIG. 3A is an example history chart for a diabetes management system.

FIG. 3B is an example history log for a diabetes management system.

FIGS. 4A-4H illustrate various user interface screens of an example bolus calculator for a diabetes management system.

FIG. 5 illustrates an example user interface for entering a blood glucose value.

FIG. 6 illustrates an example user interface for reporting outside insulin.

FIGS. 7A-7D illustrate example user interface screens for system maintenance.

FIG. 8 depicts an example user interface alarm screen.

FIG. 9A depicts an example alternative user interface dashboard.

FIG. 9B depicts an alternative example slide-out navigation screen.

Like reference symbols in the various drawings may indicate like elements.

DETAILED DESCRIPTION

Diabetes management systems provided herein can provide a user experience that reduces the cognitive burden on a person with diabetes (PWD) and their caregivers as they treat the disease. The user experience can be improved by providing a user interface that provides the user with actionable and easy to understand information. In some cases, the user interface can be provided on a mobile computing device (e.g., a smart phone or tablet device), which can be in wireless communication with an insulin pump, a continuous glucose monitor, a blood glucose monitor, and/or other components. Diabetes management systems 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. 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.

Diabetes Management System Overview

FIGS. 1A and 1B provide examples of a diabetes management system (DMS) 10 including an insulin pump assembly 15, a mobile computing device 60, a continuous glucose monitor 50, and a blood glucose monitor 70. FIG. 1C depicts the details of an exemplary pump controller, which can be used with DMS 10. Pump assembly 15 includes an infusion set 146 adapted to deliver insulin to an infusion set 146. In some cases, DMS 10 can include an insulin pen 80 or other insulin delivery device that can also be used to deliver insulin to a user. As shown, mobile computing device 60 is in wireless communication with insulin pump assembly 15. 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, continuous glucose monitor 50 can wirelessly communicate directly with mobile computing device 60. As shown, insulin pump assembly 15 is in wireless communication with blood glucose monitor 70 and data from blood glucose monitor 70 can be transferred to the mobile computing device 60 via insulin pump assembly 15. In some cases, blood glucose monitor 70 can wirelessly communicate directly with mobile computing device 60. In some cases, blood glucose monitor 70 can be unconnected from the insulin delivery system 10 and a user can manually input a blood glucose monitor reading into mobile computing device 60 (or into insulin pump assembly 15), either with or without a user prompt. In some cases, a blood glucose monitor 70 can be in wireless communication with continuous glucose monitor 50.

The features that are described herein can be extended to DMSs 10 that use alternative insulin delivery devices (e.g., insulin pens, patch pumps, syringes) and/or devices delivering other medicines (e.g., glucagon). In some cases, insulin pen 80 can be in wireless communication with mobile computing device 60. In some cases, user interfaces provided herein can be adapted to allow a user to manually input a bolus delivered using insulin pen 80. User interfaces described herein can also be used with any suitable insulin pump device, including patch pumps and/or other commercially available pumps. In some cases, an insulin pump assembly used in DMS 10 can have a unitary construction and have a reservoir adapted to be filled with insulin.

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.

Mobile computing device 60 can serve as the user interface of DMS 10. As shown, mobile computing device 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, user interfaces provided herein are all present on mobile computing device 60 and are not present on a pump assembly 15, which can eliminate a need for a dedicated display and user input device on pump assembly 15, reducing costs and energy expenditure for pump assembly 15. In some cases, pump assembly 15 can include between zero and five LED indicators adapted to light to inform the user of certain conditions. In some cases, pump assembly 15 lacks a graphical display. In some cases, pump assembly 15 can provide audible, visual, and/or tactile (vibration) alarms to alert a user to a need to access mobile computing device 60 to monitor DMS 10. In some cases, pump assembly 15 lacks any user selectable buttons or icons, but can optionally use an accelerometer to detect motion of the pump assembly 15 for receiving user inputs to the pump assembly 15. In some cases, pump assembly 15 includes between zero and two user actionable buttons or icons. By placing most or all of the user interface on mobile computing device 60 (e.g., a smart phone or tablet device), a user can avoid attracting unwanted attention when inputting data into the DMS. Moreover, smart phones typically have more robust graphical displays, which can improve the user experience as compared to the types of displays typically added to insulin pump devices. In some cases, however, user interfaces provided herein can be present on pump assembly 15, on a web portal, on a continuous glucose monitor controller, on blood glucose meter 70, or another part of a DMS system.

User Interface

FIG. 2 depicts an exemplary home screen 300 for DMS 10, which can appear on a mobile computing device 60 when a user selects an icon for the DMS application. If the user is already logged in, home screen 300 can pop up whenever the user selects an icon for the DMS control application. If the user is not logged in, a log-in screen can appear for the user to enter secure identifying information (e.g., a user name and password, a thumb print, an iris scan, etc.). Moreover, as discussed below, the DMS control application can also prompt a user to pair one or more insulin delivery devices, continuous glucose monitors, and/or blood glucose monitors during an initial log in and/or if mobile computing device 60 fails to find a paired insulin delivery device, continuous glucose monitors, and/or blood glucose monitors.

Home screen 300 can provide the user with a simplified view of the DMS status to help the user quickly understand whether the DMS system is operating appropriately and promote routine activities, while also allowing the user to access additional data if the user is interested in more detailed system information. As shown, home screen 300 includes a header 310, which can include mobile and Wi-Fi-signal strength indicators 311, a mobile computing device power display 312, a logo 313, a time display 314, and a user name 315. Header 310 can provide the user with comfort about the system status of the mobile computing device 60 and assure the user that the mobile computing device 60 is their personal mobile computing device 60.

Home screen 300 includes a most recent glucose measurement field 320 that includes a most recent glucose measurement 321 which can be displayed as the most prominent number, along with a time display 322 of the timing of glucose measurement field 320, an identification of the glucose measurement device 323, and the units 324 for glucose measurement 321. In some cases, the most recent glucose measurement 321 can be from a continuous glucose monitor (CGM). In some cases, the most recent glucose measurement 321 can be from a blood glucose meter (BGM). In some cases, the most recent glucose measurement 321 will always display the most recent glucose measurement regardless of the measurement device. Glucose measurement 321 can be the most prominent number because it is typically the number that a person with diabetes (PWD) or a caregiver is most concerned about monitoring to ensure the diabetes is being treated appropriately. Accordingly, a very prominent display of the most recent blood glucose measurement 321 can help assure a user that the DMS is acting appropriately. In some cases, the most recent glucose measurement field 320 can include a trend arrow 325, which can indicate the slope of the recent blood glucose measurements from a continuous glucose monitor.

Home screen 300 can, in some cases, also include a projected condition display 330 indicating how glucose levels are expected to change going forward, which is distinct from the typical display of blood glucose trend indicators, such as trend arrow 325. As shown, home screen 300 displays a numerical projected glucose level 331 along with a future time 332 for which that glucose value is projected and the units 334. In some cases, future time 332 for projected glucose value 331 is between 15 minutes and two hours in advance of the time of the most recent blood glucose value 320. In some cases, future time 332 is between 30 minutes and 1 hour in advance of the time of most recent blood glucose value 320.

In some cases, projected condition display 330 can include a prediction arrow 335 that can indicate the direction and/or rate of projected change. As shown, prediction arrow 335 can have a different slope than trend arrow 325, which is because the trend arrow is based on a plot of past glucose data alone. In some cases, prediction arrow 335 is depicted with projected glucose value 331. In some cases, prediction arrow 335 can be present without a projected glucose value 331. In some cases, prediction arrow 335 can be straight to indicate that the glucose values are projected to steadily increase, decrease, or remain relatively static over the next one, two, three, or four hours. In some cases, a slope of prediction arrow 335 can indicate the approximate expected rate of change. In contrast to trend arrow 325, prediction arrow 335 can display the trajectory of projected glucose values, not just the trajectory of previously recorded glucose values. In some cases, prediction arrow 335 can be curved to indicate that projected glucose levels are expected to rise then fall (e.g., after a meal and bolus) or fall then rise (e.g., after the system has detected a projected low and reduced basal delivery rates). In some cases, projected condition display 330 can include a text string with or without prediction arrow 335 and/or projected glucose value 331 to indicate how the DMS 10 expects glucose values to change over the next 15 minutes to 4 hours. Exemplary text strings could include the following: “Glucose values expected to remain with 20 mg/dL of target over the next two hours”; “Glucose values expected to rise over the next hour, but return within 20 mg/dL of target within three hours”; “Glucose values expected to fall over the next 30 minutes to be within 20 mg/dL of target”; “Glucose values projected to continue to rise, DMS recommends a correction bolus”; and “Glucose values projected to fall quickly, DMS recommends that you eat sugar or inject glucagon.” In the case that the DMS projects a high or low that cannot be corrected with an adjustment to a basal rate using a closed loop algorithm, the DMS system can provide an alarm (for example, on the mobile computing device 60, pump assembly 15, or a combination thereof) to get the user's attention, thus the typical display of projected glucose values should reassure the user that the DMS 10 is acting appropriately to manage the PWD's diabetes. For example, the DMS 10 can perform an analysis to determine if a projected high or low BGL can be corrected with an adjustment to a basal rate. If the DMS 10 determines that the BGL cannot be corrected with an adjustment to the basal rate, the DMS 10 provides an audio, visual, and/or tactile alarm to alert the user to the projected high or low. An example alarm is depicted in FIG. 8, discussed below. An advantage of a projected glucose value 331, a prediction arrow 335 depicting how glucose values are expected to change, and/or a text string explaining how glucose values are expected to change over the next few hours is that the user does not need to conduct a self-evaluation that considers trends in the glucose data, amounts of food consumed, and amounts of recently insulin delivered to evaluate whether the DMS is operating appropriately.

In some commercial devices, an amount of insulin on board (IOB) is calculated to tell a user an estimate of how much insulin has been delivered but not yet acted, which some diabetics use to adjust treatment. In some cases, home screen 300 can display an indication of an amount of insulin on board (IOB) in order to reassure users that are accustomed to seeing an IOB. In some cases, home screen 300 can eliminate an IOB display due to the presence of a projected glucose value, a projected glucose trajectory, or a textual string. In some cases, a user can set an option regarding whether to see an IOB value on home screen 300. For example, a setup screen can provide a control that allows the user to elect to display an IOB value on the home screen or on another screen.

Referring back to FIG. 2, home screen 300 includes a history field 350 configured to indicate to the user the most recent relevant event, which can typically be a bolus amount 352 along with the timing 353 of the bolus. History field 350 can ensure that a user can quickly confirm that a recent bolus (e.g., for a recent meal) was delivered. Bolus history field 350 is a more intuitive way for a user, especially users new to the management of diabetes, to understand the currently enacted treatment. If a user clicks on history field 350, a history user interface can appear, such as those discussed below in relationship to FIGS. 3A and 3B.

History User Interfaces

When a user clicks on the history field 350 on home screen 300, the user can arrive at one of the history screens 420 or 440 depicted in FIGS. 3A and 3B. As shown, screens 420 and 440 both include headers 310 similar to the header on home screen 300, but having a title 317 and a back button 316. Back button 316 can bring the user back to home screen 300. A toggle field 430, below header 310, allows a user to toggle between history screens 420 and 440 by clicking on chart control 432 for history chart screen 420 and by clicking on log control 434 for history log screen 440.

History chart screen 420 provides time-aligned graphical charts 450, 460, and 470. Glucose value chart 450 shows both continuous glucose monitor glucose values 452 and blood glucose meter glucose values 454 plotted along a time x-axis 453 and a glucose value y-axis 455. As shown, blood glucose meter and continuous glucose meter values are visually distinct (e.g., different color, different size, etc.). In some cases, data 454 from a blood glucose meter is more prominent because blood glucose meter data is more accurate and less frequent. In some cases, data 454 from a blood glucose meter can display the numerical value of the reading to make it clear that the data point is more accurate. A current time indicator line 456 extends down the screen and a time indicator 458 indicates the current time. The data to the left of time indicator line 456 is historical data, while the data to the right of the indicator line 456 can be blank, can project one or more predicted glucose values (for example, in a different color or using a different dash pattern), or can project a range of possible glucose values. As shown, the data to the right of indicator line 456 can include prediction arrow 335 having a shape and/or slope as discussed above. In some cases, projected glucose values can appear like a shaded triangle to indicate a range of possibilities. Beneath glucose value chart 450, charts 460 and 470 depict the basal delivery rates 462 over time and a history of bolus deliveries over time, respectively. Basal dosage chart 460 indicates the basal delivery rates, which DMS 10 automatically adjusts based on data from a continuous glucose monitor, blood glucose meter, and/or recent insulin deliveries. The y-axis 465 of basal dosage chart 460 includes basal delivery rates per hour. On the right side of time indicator 456 basal dosage chart can be blank or display the currently scheduled basal delivery rate 467. Although actual basal insulin may be delivered as discrete units at regular or irregular intervals based on the specifics of the insulin pump, chart 460 depicts the basal delivery as a step graph 462 showing a continuous insulin delivery as a rate over time. Bolus dosage chart 470 depicts a history of larger dosages of insulin 472 along the time x-axis 473 as bars 472 on a graph with units of insulin along the y-axis 475. Each bar can include a numerical display 474 of units delivered. In some cases, charts 460 and 470 are separate due to the different y-axis units. In some cases, charts 460 and 470 can overlie each other and each bolus bar labeled to indicate the amount of the bolus, such as depicted in the alternative user interface depicted in FIG. 9A. The history screen 420 can typically display 4 hours of data, but a user can click on 436 to change the amount of time displayed.

History log screen 440 can provide a log 480 of all glucose readings 482 and 483 (both from a continuous glucose monitor and a blood glucose meter, respectively) and insulin delivery tasks 484 and 485 (e.g., bolus deliveries and/or changes to basal insulin rates) as separate entries, each with a time, a label, and a summary. A filter 438 can be used to select the types of data displayed in log 480.

After a user has gained confidence in the DMS, a user might not typically access history screens 420 and 440. Nonetheless, the presence of history screens 420 and 440 can allow a user to gain trust in the DMS by allowing the user to see all activates. Moreover, users might access history screens 420 and 440 if the user believes that the system is acting unusually. Additionally, clinicians and other care providers can use history screens to monitor the DMS to determine if the DMS is acting appropriately.

Bolus Entry

Referring back to FIG. 2, in some cases home screen 300 also prominently displays a bolus entry user actionable display 340, including an icon 341 that allows a user to enter carbohydrates and/or units of insulin to properly dose insulin in response to a meal. The button for bolus entry user actionable display 340 is prominently displayed because it is expected to be the most common action of a user using a closed-loop diabetes management system. For example, the button for bolus entry can be displayed as larger than any other single control on the home screen 300. Home screen 300 can additionally include additional user selectable icons that allow the user to provide additional data to DMS 10, but less routine tasks (e.g., recording outside insulin) can be deemphasized as compared to more routine tasks (e.g., inputting a mealtime bolus). As shown in FIG. 2, navigation row 390 can include additional user selectable icons.

When a user selects the bolus entry user actionable display 340 or icon 341, a user can be delivered to a bolus calculator screen, such as screen 500A as depicted in FIG. 4A. The bolus calculator thus minimizes the amount of information that the user must comprehend when considering a mealtime bolus. FIGS. 4A-4G depict how a bolus calculator can be used. Again, the bolus calculator screens include a header 310 that can include a title 317 and a back button 316, which can be clicked to return to home screen 300. Beneath header 310, a toggle field 510 allows a user to switch between entering carbs consumed and units of insulin by selecting carbs control 511 or units control 512. As shown in FIG. 4A, the carbs control 511 is selected. If the units control is selected, the user will be delivered to screen 500C as depicted in FIG. 4G. The toggle between carbs and units of insulin allows for different users to use the bolus calculator, as some users may think about meals in terms of the number of carbohydrates consumed while others think about meals in terms of units of insulin needed for the meal.

In screen 500A, a user first scrolls down to a number of carbs 523A using scroll wheel 522A to estimate a number of carbs for the meal, changing the screen to appear similar to screen 501A depicted in FIG. 4B. The units 524A for the scroll wheel 522A are clearly displayed to avoid user confusion about the data being entered. As the grams of carbs 523A is adjusted using scroll wheel 522A, the user interface dynamically updates a conversion of the carbs 523A to units of insulin 526A for the user, which can be based on the user's carbohydrate to insulin ratio. Screens 500A and 501A further depict a total dose field 530A that includes an adjusted total dose 532A of insulin delivery that displays a calculated correction of the dose. Text string 534A can indicate that the DMS recommends the calculated correction of the dose. An information button 536 can be clicked on to explain to a user how this is calculated. An example of the information that can be included on the screen when clicking information button 536 is shown in screen 537A in FIG. 4F, discussed below. When the user first arrives at the bolus calculator screen and the carbs scroll wheel 522A initially has the selected value of carbs 523A set to zero, the total dose 532A will indicate the amount of the adjustment, so a user can see how much of an adjustment the DMS is making. This adjustment can be based on factors such as the amount of insulin on board, current glucose values and/or trends, and/or additional information about the user.

Once the user has entered the number of carbs (which can be left at zero), the user can select continue button 540 to go to screen 502A as depicted in FIG. 4C. In some cases, the text of continue button 540 can instead recite “Adjust Insulin.” After selecting continue button 540, the fields 520A and 530A change to fields 520B and 530B as shown in FIG. 4C. In field 520B, the user selected number of carbs 523A is displayed as the selected number of carbs 523B without any scroll wheel to indicate that this value is set. Field 520B also displays the units 524B and the conversion to units of insulin 526B so that the user can remember the amount of units being delivered due to the consumption of food. If the user wishes to change the number of carbs entered, the user can click on field 520B to have the screen revert to screen 501A. Field 530B then allows the user to make a personal adjustment using a scrolling wheel 535 to the total dose. The recommended total dose 532A from screen 501A can appear at the bottom of field 530B and/or have a distinct appearance in the scrolling wheel 535 to remind a user what the DMS has calculated for the total dose. Screen 502A allows the user to adjust the number of units so that the user has ultimate control over the bolus amount. For example, a user may want to adjust the bolus amount from the DMS calculated amount if the user is feeling sick or if the user is about to exercise. Being able to adjust the number of units for the total dose 537 can be useful when a user is building trust in the system. Once the user has selected the total dose 537 on scrolling wheel 535, the user can hit continue button 550 to bring up screen 503. In screen 503, depicted in FIG. 4D, a confirmation box 574 pops up to inform the user that the pump is about to deliver a certain number of units of insulin to the user and has the user click on selectable button 576 to deliver the insulin. The display of box 574 results in the reminder of the screen being shaded 572. FIG. 4E depicts a screen 504 indicating an announcement that insulin has been delivered successfully. In some cases, a screen can appear showing the progress of the bolus. For example, a user interface can show a progress bar.

FIG. 4F displays a bolus information box that can be displayed when a user selections information icon 336 in any of FIGS. 4A-4C, 4G, and 4F. Screen 537 explains how the recommended dose is based on an insulin to carb ratio and blood glucose readings 538A and explain that a user can manually adjust the total 538B. The box can be over a shaded background 572. A user can select an “OK” button 539 to exit the information box.

FIGS. 4G and 4H illustrate how the bolus calculator works if the user clicks on units control 512 to arrive at screen 500C and enters units 523C using a scroll wheel 522C. A conversion of the units 523C into a number of carbs 526C dynamically updates. Again, the units 524C is clearly displayed so that a user knows what is being entered. A total dose recommendation field 530C is also dynamically updated to display a calculated total dose 532C. Once a user hits continue button 540, the user is brought to a screen similar to screen 502A, as depicted in FIG. 4C, to allow the user to manually adjust and deliver an amount of insulin using similar functionality. In some cases, an alarm is scheduled for a predetermined number of minutes (e.g., 5 minutes) in the future as soon as the bolus screen is activated, and cleared upon the delivery of the insulin so that a user that inadvertently fails to deliver the bolus can be reminded that they may have intended to deliver a bolus. For example, this could be useful if the application is interrupted and the user is unsure if the bolus instruction was delivered to the insulin pump and/or forgets to finish to bolus delivery process. In some cases, the alarm can be set on pump controller.

DMS Operating Information

Referring back to FIG. 2, home screen 300 can include a CGM monitor field 360 and an insulin pump field 370 to display relevant information about whether these devices are properly connected and/or the mode of operation. For example, in order for a closed loop system to be in operation, the system requires proper access to the continuous glucose monitor (CGM) data, thus, indicating that the CGM Monitor is “ON” will assure the user that the DMS 10 is operating appropriately. If the user clicks on the CGM monitor field 360, the user can go to a screen where the user can adjust the continuous glucose monitor settings. In some cases, condition display 330 is only displayed in response to the CGM monitor being on. In some cases, when the CGM monitor is off, the system will display a warning in condition display 330 that the system cannot predict future glucose values because the CGM monitor is not operating.

In some cases, a user can select CGM monitor field 360 to make changes to the settings or to tell the DMS to stop using data from a paired continuous glucose monitor. For example, if a user suspects that the data from a paired continuous glucose monitor is inaccurate, a user can turn the CGM indicator to “OFF” so that the DMS will stop using glucose values from the continuous glucose monitor, which will stop any adjustments to basal insulin delivery rates from predetermined basal delivery rates. In some cases, the CGM monitor field 360 will be turned “OFF” during a warmup period after a new continuous glucose monitor sensor has been placed on the user.

Displaying the status of the insulin pump in field 370 is also useful to assure the user that the system is operating appropriately. In some cases, DMS can have a plurality of operating modes depending on the data available. For example, some modes may automate basal delivery rates based on CGM data in order to provide a closed loop system. Accordingly, displaying that automation is on for the insulin pump can assure the user that the DMS will automatically adjust basal delivery rates in order to control blood glucose levels.

Additional Data Entry Field

Referring again to FIG. 2, home screen 300 can also include navigation row 390 along the bottom of the device, which can display other user-selectable icons for less routine tasks. As discussed above, these tasks may be less frequent than mealtime boluses because they represent information that can be collected via wireless connections between a blood glucose meter 70, the pump assembly 15, and the continuous glucose monitor 50. As shown in FIG. 2, in some cases navigation row 390 can include a recording BG icon 392, recording outside insulin icon 394, and settings icon 396. Additional possible icons could include icons, for example, that allow a user to indicate exercise, sickness, sleep, and/or additional states that could impact blood glucose levels.

When a user selects icon 392 to input a blood glucose meter reading, a screen similar to screen 600, as depicted in FIG. 5, can appear. Screen 600 can include a header 310 similar to those discussed above, but also include a submit button 610. Screen 600 can include a warning about when the reading must have been taken 620, and an input field 630 for the blood glucose meter value. Screen 600 clearly includes a label 634 identifying the field as being for blood glucose and provides the units 632. In some cases, blood glucose measurement can be used to calibrate the continuous glucose monitor of the DMS. When a user clicks on field 630, a numerical keypad can appear to allow the user to enter a number and hit return. In some cases, screen 600 can pop up as part of completing the bolus calculator. As discussed above, DMS systems provided herein can include blood glucose meters in wireless communication with an insulin pump and/or a mobile computing device, thus the manual entry of blood glucose values may not be a typical action of a user.

When a user selects icon 394 to enter outside insulin, a screen similar to screen 660, as depicted in FIG. 6, can appear. Screen 660 can include a header 310 similar to those discussed above with a submit button 610, a warning about the insulin being insulin taken outside of the DMS system 625, and an input field 670 for entering a number of units 672 of outside insulin. Field 670 is clearly labeled as being insulin 674. Screen 660 also includes a time scrolling wheel 680 for a user to enter the time that the insulin was administered. In some cases, screens similar to screen 660 can allow for entry of different types of medication (e.g., glucagon), different types of insulin (e.g., slow acting insulin), and/or other information about how the medication was delivered.

When a user selects icon 396 (FIG. 2) to adjust settings, the user can adjust a number of other user settings, such as insulin sensitivity factors, carbohydrate to insulin ratios, baseline basal insulin delivery rates, and target glucose levels.

Maintenance Field

Home screen 300 also includes a maintenance field 380 adapted to indicate to a user if the user will be expected to conduct any maintenance tasks in the near future (e.g., in the next 24 hours) and/or whether the DMS has detected any need for immediate maintenance. For example, maintenance field 380 can indicate when an infusion set is due for replacement, when an infusion set should be changed, when disposable parts of a pumping assembly need to be replaced and/or when an insulin reservoir needs to be refilled, when the continuous glucose monitor sensor needs to be changed or moved to a new location on the body, or when a blood glucose measurement should be made to calibrate the continuous glucose monitor. In some cases, static indicators can indicate the approximate deadline for conducting routine maintenance, optionally with color indicators indicating the urgency of each maintenance task (e.g., red, yellow and green to indicate high, medium, and low urgency respectively). In some cases, maintenance field 380 can indicate that no maintenance tasks are required. In the cases that immediate maintenance is required, DMS 10 can provide an alarm (e.g., on the mobile computing device 60, pump assembly 15, or a combination thereof) to get the user to look at the user interface to learn about the required maintenance task. Maintenance field 380 is configured to reassure a user that system maintenance tasks are up-to-date, thus again reducing the cognitive burden on the user.

FIGS. 7A-7D depict pump maintenance user interfaces 701-704, which can be used when conducting pump maintenance. User interface 701 allows a user to select between conducting cannula fill operations and tube priming operations. User interface 702 confirms a cannula fill. User interface 703 provides options for a tubing prime operation. User interface 704 provides a warning that the tubing is about to be primed including a confirmation text box 774 over a shaded background 772.

Alarm Screen

FIG. 8 depicts an alarm screen 800 that includes a header 310 similar to those discussed above, and an alert field 810 and a text field 820. Alert field can be colored to indicate that an immediate action is needed. For example, field 810 can have a red background. Text field 820 can inform the user, potentially by name, that the DMS is taking a limited action but that the user may want to take additional action. An “OK” or “Okay” bottom can be present at the bottom of screen 800 for the user to acknowledge the alarm.

Alternative Home Screen and Navigation

FIGS. 9A and 9B depict an alternative dashboard having slide-out navigation to access various tasks. Dashboard 900 includes a graphical history display similar to that shown in FIG. 3A, discussed above, but uses this graphical display as part of a home screen. Dashboard 900 includes a header 910, similar to header 310 discussed above, that includes mobile computing device connection information, a mobile computing device power indicator, and a time of day. Beneath header 910, dashboard displays an estimate of the insulin on board (IOB) 930 and a most recent glucose measurement 932, and an arrow 933 showing a prediction of how blood glucose levels will change, similar to prediction arrow 335 discussed above. In some cases, dashboard 900 can include an alert icon 920 that appears if there is an alarm condition, which the user can select to learn details about the alert. Dashboard 900 further indicates when the most recent blood glucose measurement was taken. Chart 940 is similar to glucose value chart 450 discussed above, but can use different colors. Chart 950 is similar to charts 460 and 470 discussed above, but can include an overlay of the bars representing bolus deliveries and the step graph showing the basal rate. User-selectable icons along a bottom row 960 can allow a user to input a blood glucose measurement, icon 962, enter a meal for a bolus calculation, icon 962, and look at user settings, icon 964. Clicking on icon 962 can bring the user to the user interface of FIG. 5. Clicking on icon 964 can bring the user to the bolus calculator discussed above in relationship to FIGS. 4A-4G.

By clicking on navigation icon 970 in the upper left corner, a slide-out menu can appear, as shown as screen 901 in FIG. 9B. The navigation slide-out can include icons for recording outside insulin, changing device pairings, editing configurations, preforming insulin pump maintenance, preforming insulin infusion set maintenance, starting insulin delivery, starting a continuous glucose monitor sensor, changing the automation mode, and viewing the event history.

Exemplary Mobile Computing Device

Referring again to FIGS. 1, 1B, and 1C, mobile computing device 60 can communicate with the controller device 200 through a wireless and/or wired connection with the controller device 200 (e.g., via a Bluetooth wireless communication connection in this particular implementations). In some cases, mobile computing device 60 communicates wirelessly with other elements of the insulin delivery system 10. 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 where there is no computing device 200 that is part of a pump, the mobile computing device 60 can receive and log data from the other elements of insulin delivery system 10. In some cases, a user can input relevant data into mobile computing device 60. In some cases where a pump assembly 15 includes controller device 200, the mobile computing device 60 can receive and log data that is collected by the controller device 200, such as blood glucose readings, dosage delivery information, and also can receive user inputs (e.g., user-selected parameters to be stored on the controller device 200, user-confirmation of bolus dosages (described below), and others). 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

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 continuous glucose monitor 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 continuous glucose monitor 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 continuous glucose monitor 50 can be in communication with the controller device 200 or another computing device via a wired connection.

Blood Glucose Meter

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.

External Insulin Delivery Devices

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.

Pump Assembly

Referring again to FIG. 1, 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. Additional details about the particularly depicted pump assembly 15 are described in more detail below in connection with FIGS. 1B and 1C.

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 tube 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 220.

Referring now to FIG. 1B, 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 in FIG. 5) 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 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 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 structure 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).

Still referring to FIG. 1B, 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 cartridge 120. In some cases, the drive system incrementally advances a piston rod (not shown) longitudinally into the 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 tube 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 infusion cannula 149 in fluid communication with the tissue or vasculature of the user so that the medicine dispensed through the tube 147 passes through the cannula 149 and into the user's body. The cap device 130 can provide fluid communication between the output end 122 (FIG. 5) of the fluid cartridge 120 and the tube 147 of the infusion set 146.

Referring now to FIG. 1C, the controller device 200 (shown in an exploded view) houses a number of components that can be reused with a series of successive pump devices 100. In particular, the controller device 200 can include control circuitry 240 and a rechargeable battery pack 245, each arranged in the controller housing 210. The rechargeable battery pack 245 may provide electrical energy to components of the control circuitry 240, other components of the controller device (e.g., the display device 222 and other user interface components, sensors, or the like), or to components of the pump device 100. The control circuitry 240 may be configured to communicate control or power signals to the drive system of the pump device 100, or to receive power or feedback signals from the pump device 100.

The control circuitry 240 of the controller device 200 can include one or more microprocessors 241 configured to execute computer-readable instructions stored on one or more memory devices 242 so as to achieve any of the control operations described herein. At least one memory device 242 of the control circuitry may be configured to store a number of user-specific dosage parameters. Various user-specific dosage parameters can be automatically determined and/or updated by control operations implemented by the control circuitry 240 of the controller device 200. Additionally, the control circuitry 240 can cause the controller device 200 to periodically communicate the user-specific dosage parameters to the mobile computing device 60 for future use during operations by the mobile computing device 60 or for subsequent communication to cloud-based computer network.

In some cases, the control circuitry 240 can receive input data or other information from the mobile computing device 60 (e.g., via user input at the mobile computing device 60) and thereby cause the controller device 200 to output information to the mobile computing device 60 for display on the screen of the mobile computing device 60, such as settings and data (e.g., review data that shows the medicine dispensing rate, the total amount of medicine dispensed in a given time period, the amount of medicine scheduled to be dispensed at a particular time or date, the approximate amount of medicine remaining the cartridge 120, the amount of battery life remaining, or the like). The control circuitry 240 can be programmable to cause the control circuitry 240 to change any one of a number of settings or modes of operation for the insulin delivery system 10. In some cases, the control circuitry 240 can include a cable connector (e.g., a USB connection port or another data cable port) that is accessible on an external portion of the controller housing 210. As such, a cable can be connected to the control circuitry 240 to upload or download data or program settings to the control circuitry.

A number of implementations 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 implementations are within the scope of the following claims.

Claims

1. A mobile computing device for controlling a medical infusion pump system, the computing device comprising: a display screen of a smart phone or a tablet computer;one or more input controls manipulable by a user;one or more processors;a memory to store computer-readable instructions that, when executed by the one or more processors, enable the computing device to perform actions comprising: communicating with a controller of a medical infusion pump system to cause the medical infusion pump system to dispense medicine to a patient;receiving blood glucose level information for the patient, wherein the blood glucose level information is associated with one or more blood glucose measurement times;providing a graphic user interface formatted for the display screen of the smart phone or the tablet computer, wherein the graphical user interface includes: a blood glucose level chart presented at a first region of the graphical user interface, the blood glucose level chart depicting a series of blood glucose values included in the received blood glucose level information, the series of blood glucose values being aligned adjacent a first vertical axis and over a first time axis to reflect the times that the blood glucose values were measured; andan insulin delivery chart presented at a second region of the graphical user interface, the insulin delivery chart depicting (1) a first graph, presented at a first sub-region of the second region, showing a continuous line indicating basal delivery rates administered by the infusion pump system over time aligned adjacent a second vertical axis, and (2) a second graph, presented at a second sub-region of the second region, showing a series of insulin bolus indicators indicating times that insulin bolus deliveries were administered aligned adjacent a third vertical axis, respective areas defined by borders of bolus indicators representative of amounts of insulin bolus deliveries, wherein the first graph showing the continuous line indicating basal delivery rates and the second graph showing the series of insulin bolus indicators are aligned over a second time axis, wherein the first graph and the second graph presented at the first and second sub-regions, respectively, do not overlap, wherein the first and third vertical axis are aligned over the same portion of the second time axis,wherein the second time axis is distinct from the first time axis,wherein there is no spatial overlap between the blood glucose level chart and the insulin delivery chart,a current time; anda vertical line segment that intersects the first time axis and the second time axis respectively at points corresponding to the current time.
2. The computing device of claim 1, wherein the first time axis of the blood glucose level chart is positioned above the first graph showing the line indicating basal delivery rates and the second time axis of the insulin delivery chart is positioned below the graph showing the line indicating basal delivery rates.
3. The computing device of claim 1, wherein the first time axis of the blood glucose level chart is positioned above the series of insulin bolus indicators and the second time axis of the insulin delivery chart is positioned below at least a portion of each of the series of insulin bolus indicators.
4. The computing device of claim 1, wherein the first time axis of the blood glucose level chart is positioned above the insulin delivery chart.
5. The computing device of claim 1, wherein the first time axis of the blood glucose level chart and the second time axis of the insulin delivery chart are time-aligned within the graphic user interface.
6. The computing device of claim 5, wherein the graphic user interface further includes a current time line that passes through the first time axis of the blood glucose level chart and the second time axis of the insulin delivery chart to identify a current time with respect to the blood glucose level chart and the insulin delivery chart.
7. The computing device of claim 6, wherein the blood glucose level chart depicts a projection of future blood glucose values on a right side of the current time line; and wherein the insulin delivery chart depicts a scheduled future basal delivery rate on the right side of the current time line.
8. The computing device of claim 1, wherein: the received blood glucose level information comprises blood glucose level information measured by a continuous glucose monitor and blood glucose level information measured by a blood glucose meter; andthe blood glucose level chart depicts a first series of blood glucose values measured by the continuous glucose monitor aligned over the first time axis to reflect the times that the blood glucose values in the first series of blood glucose values were measured by the continuous glucose monitor, and a second series of blood glucose values measured by the blood glucose meter aligned over the first time axis to reflect the times that the blood glucose values in the second series of blood glucose values were measured by the blood glucose meter.
9. The computing device of claim 8, wherein the first series of blood glucose values measured by the continuous glucose monitor are depicted using a first symbol and the second series of blood glucose values measured by the blood glucose meter are depicted using a second symbol, the second symbol being larger than the first symbol.
10. The computing device of claim 8, wherein the first series of blood glucose values measured by the continuous glucose monitor are depicted are depicted at a higher sampling rate than the second series of blood glucose values measured by the blood glucose meter.
11. The computing device of claim 8, wherein the first series of blood glucose values includes more blood glucose values than the second series of blood glucose values.
12. The computing device of claim 1, wherein the graphic user interface further comprises a display of a most recent glucose measurement that is distinct from the blood glucose level chart.
13. The computing device of claim 1, wherein the graphic user interface further comprises a display of an active insulin on board value.
14. The computing device of claim 1, wherein the graphic user interface further comprises an interactive control that allows the user to select an amount of time represented by the first time axis and the second time axis.
15. The computing device of claim 1, wherein the graphic user interface further comprises an indication of a current time.
16. A computer-implemented method, comprising: communicating with a controller of a medical infusion pump system to cause the medical infusion pump system to dispense medicine to a patient;receiving blood glucose level information for the patient, wherein the blood glucose level information is associated with one or more blood glucose measurement times;providing a graphic user interface formatted for the display screen of a smart phone or a tablet computer, the graphic user interface including: a blood glucose level chart, presented at a first region of the graphical user interface, the blood glucose level chart depicting a series of blood glucose values included in the received blood glucose level information, the series of blood glucose values being aligned adjacent a first vertical axis and over a first time axis to reflect the times that the blood glucose values were measured; andan insulin delivery chart, presented at a second region of the graphical user interface, the insulin delivery chart, depicting (1) a graph, presented at a first sub-region of the second region, showing a continuous line indicating basal delivery rates administered by the infusion pump system over time aligned adjacent a second vertical axis, and (2) a second graph, presented at second sub-region of the second region, showing a series of insulin bolus indicators indicating times that insulin bolus deliveries were administered aligned adjacent a third vertical axis, respective areas defined by borders of bolus indicators representative of amounts of insulin bolus deliveries, wherein the first graph and the second graph presented at the first and second sub-regions, respectively, do not overlap, wherein the first and third vertical axis are aligned over the same portion of a second time axis,wherein the graph showing the basal delivery rates and the series of insulin bolus indicators are aligned over the second time axis, wherein the second time axis is distinct from the first time axis,wherein there is no overlap between the blood glucose level chart and the insulin delivery chart,a current time; anda vertical line segment that intersects the first time axis and the second time axis respectively at points corresponding to the current time.
17. The method of claim 16, wherein the first time axis of the blood glucose level chart is positioned above the first graph showing the continuous line indicating basal delivery rates and the second time axis of the insulin delivery chart is positioned below the graph showing basal delivery rates.
18. The method of claim 16, wherein the first time axis of the blood glucose level chart is positioned above the insulin delivery chart.
19. The method of claim 16, wherein the graphic user interface further includes a current time line that passes through the first time axis of the blood glucose level chart and the second time axis of the insulin delivery chart to identify a current time with respect to the blood glucose level chart and the insulin delivery chart; and wherein the blood glucose level chart depicts a projection of future blood glucose values on a right side of the current time line; and wherein the insulin delivery chart depicts a scheduled future basal delivery rate on the right side of the current time line.
20. The method of claim 16, wherein: the received blood glucose level information comprises blood glucose level information measured by a continuous glucose monitor and blood glucose level information measured by a blood glucose meter; andthe blood glucose level chart depicts a first series of blood glucose values measured by the continuous glucose monitor aligned over the first time axis to reflect the times that the blood glucose values in the first series of blood glucose values were measured by the continuous glucose monitor, and a second series of blood glucose values measured by the blood glucose meter aligned over the first time axis to reflect the times that the blood glucose values in the second series of blood glucose values were measured by the blood glucose meter.
21. The method of claim 16, wherein the graphic user interface further comprises a display of a most recent glucose measurement that is distinct from the blood glucose level chart.
22. A non-transitory computer-readable medium including instructions that, when executed by at least one processor, cause performance of operations that comprise: communicating with a controller of a medical infusion pump system to cause the medical infusion pump system to dispense medicine to a patient;receiving blood glucose level information for the patient, wherein the blood glucose level information is associated with one or more blood glucose measurement times;providing a graphic user interface formatted for a display screen of a smart phone or tablet computer, the graphic user interface including: a blood glucose level chart, presented at a first region of the graphical user interface, the blood glucose level chart, depicting a series of blood glucose values included in the received blood glucose level information, the series of blood glucose values being aligned adjacent a first vertical axis and over a first time axis to reflect the times that the blood glucose values were measured; andan insulin delivery chart, presented at a second region of the graphical user interface, the insulin delivery chart, depicting (1) a graph, presented at a first sub-region of the second region, showing a continuous line indicating basal delivery rates administered by the infusion pump system over time aligned adjacent a second vertical axis, and (2) a second graph, presented at a second sub-region of the second region, showing a series of insulin bolus indicators indicating times that insulin bolus deliveries were administered aligned adjacent a third vertical axis, respective areas defined by borders of bolus indicators representative of amounts of insulin bolus deliveries, wherein the first graph showing the continuous line indicating basal delivery rates and the second graph showing the series of insulin bolus indicators are aligned over a second time axis, wherein the first graph and the second graph presented at the first and second sub-regions, respectively, do not overlap, wherein the first and third vertical axis are aligned over the same portion of the second time axis,wherein the graph showing the basal delivery rates and the series of insulin bolus indicators are aligned over the second time axis, wherein the second time axis is distinct from the first time axis,wherein there is no overlap between the blood glucose level chart and the insulin delivery chart,a current time; anda vertical line segment that intersects the first time axis and the second time axis respectively at points corresponding to the current time.
23. The non-transitory computer-readable medium of claim 22, wherein the first time axis of the blood glucose level chart is positioned above the first graph showing the continuous line indicating basal delivery rates and the second time axis of the insulin delivery chart is positioned below the graph showing basal delivery rates.
24. The non-transitory computer-readable medium of claim 22, wherein the first time axis of the blood glucose level chart is positioned above the insulin delivery chart.
25. The non-transitory computer-readable medium of claim 22, wherein the graphic user interface further includes a current time line that passes through the first time axis of the blood glucose level chart and the second time axis of the insulin delivery chart to identify a current time with respect to the blood glucose level chart and the insulin delivery chart; and wherein the blood glucose level chart depicts a projection of future blood glucose values on a right side of the current time line; and wherein the insulin delivery chart depicts a scheduled future basal delivery rate on the right side of the current time line.
26. The non-transitory computer-readable medium of claim 22, wherein: the received blood glucose level information comprises blood glucose level information measured by a continuous glucose monitor and blood glucose level information measured by a blood glucose meter; andthe blood glucose level chart depicts a first series of blood glucose values measured by the continuous glucose monitor aligned over the first time axis to reflect the times that the blood glucose values in the first series of blood glucose values were measured by the continuous glucose monitor, and a second series of blood glucose values measured by the blood glucose meter aligned over the first time axis to reflect the times that the blood glucose values in the second series of blood glucose values were measured by the blood glucose meter.
27. The non-transitory computer-readable medium of claim 22, wherein the graphic user interface further comprises a display of a most recent glucose measurement that is distinct from the blood glucose level chart.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 15/402,493, filed Jan. 10, 2017, now U.S. Pat. No. 10,275,573, issued Apr. 30, 2019, which claims priority to U.S. Application Ser. No. 62/278,231, filed on Jan. 13, 2016.

US Referenced Citations (1129)

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
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
3812843	Wootten et al.	May 1974	A
3841328	Jensen	Oct 1974	A
3885662	Schaefer	May 1975	A
3963380	Thomas et al.	Jun 1976	A
3983077	Fuller et al.	Sep 1976	A
4055175	Clemens et al.	Oct 1977	A
4108177	Pistor	Aug 1978	A
4146029	Ellinwood, Jr.	Mar 1979	A
4151845	Clemens	May 1979	A
4245634	Albisser et al.	Jan 1981	A
4268150	Chen	May 1981	A
4295176	Wittwer	Oct 1981	A
4313439	Babb et al.	Feb 1982	A
4368980	Aldred et al.	Jan 1983	A
4373527	Fischell	Feb 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
4464170	Clemens et al.	Aug 1984	A
4469481	Kobayashi	Sep 1984	A
4475901	Kraegen et al.	Oct 1984	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
4559033	Stephen et al.	Dec 1985	A
4559037	Franetzki et al.	Dec 1985	A
4562751	Nason et al.	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
4657529	Prince et al.	Apr 1987	A
4678408	Nason et al.	Jul 1987	A
4684368	Kenyon	Aug 1987	A
4685903	Cable et al.	Aug 1987	A
4731726	Allen, III	Mar 1988	A
4743243	Vaillancourt	May 1988	A
4755169	Sarnoff et al.	Jul 1988	A
4755173	Konopka et al.	Jul 1988	A
4759120	Bernstein	Jul 1988	A
4781688	Thoma et al.	Nov 1988	A
4781693	Martinez et al.	Nov 1988	A
4808161	Kamen	Feb 1989	A
4854170	Brimhall et al.	Aug 1989	A
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
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
5061424	Karimi et al.	Oct 1991	A
5062841	Siegel	Nov 1991	A
5084749	Losee et al.	Jan 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
5176662	Bartholomew et al.	Jan 1993	A
5178609	Ishikawa	Jan 1993	A
5189609	Tivig et al.	Feb 1993	A
5198824	Poradish	Mar 1993	A
5205819	Ross et al.	Apr 1993	A
5207642	Orkin 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
5232439	Campbell et al.	Aug 1993	A
5237993	Skrabal	Aug 1993	A
5244463	Cordner et al.	Sep 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
5342298	Michaels et al.	Aug 1994	A
5346476	Elson	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
5403797	Ohtani et al.	Apr 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
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
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
5635433	Sengupta	Jun 1997	A
5637095	Nason et al.	Jun 1997	A
5665065	Colman et al.	Sep 1997	A
5665070	McPhee	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
5722397	Eppstein	Mar 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
5771567	Pierce 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
5817007	Fodgaard et al.	Oct 1998	A
5820622	Gross 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
5854608	Leisten	Dec 1998	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
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
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
5919167	Mulhauser 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
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
5993423	Choi	Nov 1999	A
5997501	Gross et al.	Dec 1999	A
6005151	Herrmann et al.	Dec 1999	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
6036924	Simons et al.	Mar 2000	A
6040578	Malin et al.	Mar 2000	A
6040805	Huynh et al.	Mar 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
6058934	Sullivan	May 2000	A
6066103	Duchon et al.	May 2000	A
6071292	Makower et al.	Jun 2000	A
6072180	Kramer et al.	Jun 2000	A
6077055	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
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
6126637	Kriesel et al.	Oct 2000	A
6128519	Say	Oct 2000	A
6142939	Eppstein et al.	Nov 2000	A
6143164	Heller et al.	Nov 2000	A
6143432	De et al.	Nov 2000	A
6154176	Fathy et al.	Nov 2000	A
6157041	Thomas et al.	Dec 2000	A
6161028	Braig et al.	Dec 2000	A
6162639	Douglas	Dec 2000	A
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
6244776	Wiley	Jun 2001	B1
6261065	Nayak et al.	Jul 2001	B1
6262798	Shepherd et al.	Jul 2001	B1
6266020	Chang	Jul 2001	B1
6270455	Brown	Aug 2001	B1
6271045	Douglas et al.	Aug 2001	B1
6280381	Malin et al.	Aug 2001	B1
6285448	Kuenstner	Sep 2001	B1
6300894	Lynch et al.	Oct 2001	B1
6309370	Ben-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
6375627	Mauze et al.	Apr 2002	B1
6375638	Nason et al.	Apr 2002	B2
6379301	Worthington et al.	Apr 2002	B1
6402689	Scarantino et al.	Jun 2002	B1
6413244	Bestetti et al.	Jul 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
6492949	Breglia et al.	Dec 2002	B1
6496149	Birnbaum et al.	Dec 2002	B1
6501415	Viana et al.	Dec 2002	B1
6512937	Blank et al.	Jan 2003	B2
6520936	Mann	Feb 2003	B1
6525509	Petersson et al.	Feb 2003	B1
6527744	Kriesel et al.	Mar 2003	B1
6528809	Thomas et al.	Mar 2003	B1
6537249	Kriesell et al.	Mar 2003	B2
6540260	Tan	Apr 2003	B1
6540672	Simonsen et al.	Apr 2003	B1
6541820	Bol	Apr 2003	B1
6544212	Galley et al.	Apr 2003	B2
6546268	Ishikawa et al.	Apr 2003	B1
6546269	Kurnik	Apr 2003	B1
6552693	Leisten	Apr 2003	B1
6553841	Blouch	Apr 2003	B1
6554798	Mann et al.	Apr 2003	B1
6556850	Braig et al.	Apr 2003	B1
D474778	Barnes	May 2003	S
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
6562014	Lin et al.	May 2003	B2
6569115	Barker et al.	May 2003	B1
6569125	Jepson et al.	May 2003	B2
6572542	Houben et al.	Jun 2003	B1
6572545	Knobbe et al.	Jun 2003	B2
6574490	Abbink et al.	Jun 2003	B2
6575905	Knobbe et al.	Jun 2003	B2
6580934	Braig et al.	Jun 2003	B1
6583699	Yokoyama	Jun 2003	B2
6595956	Gross et al.	Jul 2003	B1
6611419	Chakravorty	Aug 2003	B1
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
6642908	Pleva et al.	Nov 2003	B2
6645142	Braig et al.	Nov 2003	B2
6650303	Kim et al.	Nov 2003	B2
6653091	Dunn et al.	Nov 2003	B1
6656158	Mahoney et al.	Dec 2003	B2
6662030	Khalil et al.	Dec 2003	B2
6669663	Thompson	Dec 2003	B1
6670497	Tashino et al.	Dec 2003	B2
6678542	Braig et al.	Jan 2004	B2
6680700	Hilgers	Jan 2004	B2
6683576	Achim	Jan 2004	B2
6686406	Tomomatsu et al.	Feb 2004	B2
6690336	Leisten et al.	Feb 2004	B1
6697605	Atokawa et al.	Feb 2004	B1
6699218	Flaherty et al.	Mar 2004	B2
6699221	Vaillancourt	Mar 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
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
6733890	Imanaka et al.	May 2004	B2
6740059	Flaherty	May 2004	B2
6740072	Starkweather 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
6750740	Killen et al.	Jun 2004	B2
6750820	Killen et al.	Jun 2004	B2
6751490	Esenaliev et al.	Jun 2004	B2
6753745	Killen et al.	Jun 2004	B2
6753814	Killen et al.	Jun 2004	B2
6758835	Close et al.	Jul 2004	B2
6762237	Glatkowski et al.	Jul 2004	B2
6780156	Haueter et al.	Aug 2004	B2
6787181	Uchiyama et al.	Sep 2004	B2
6791496	Killen et al.	Sep 2004	B1
6810290	Lebel et al.	Oct 2004	B2
6826031	Nagai et al.	Nov 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
6853288	Ahn 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
6878871	Scher et al.	Apr 2005	B2
6883778	Newton et al.	Apr 2005	B1
6890291	Robinson et al.	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
6928298	Furutani et al.	Aug 2005	B2
6936029	Mann et al.	Aug 2005	B2
6943430	Kwon	Sep 2005	B2
6943731	Killen et al.	Sep 2005	B2
6949081	Chance	Sep 2005	B1
6958809	Sterling et al.	Oct 2005	B2
6963259	Killen et al.	Nov 2005	B2
6989891	Braig et al.	Jan 2006	B2
6990366	Say et al.	Jan 2006	B2
7002436	Ma et al.	Feb 2006	B2
7008404	Nakajima	Mar 2006	B2
7009180	Sterling et al.	Mar 2006	B2
7016713	Gardner et al.	Mar 2006	B2
7018360	Flaherty et al.	Mar 2006	B2
7025743	Mann et al.	Apr 2006	B2
7025744	Utterberg et al.	Apr 2006	B2
7027848	Robinson et al.	Apr 2006	B2
7043288	Davis et al.	May 2006	B2
7047637	Derochemont 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
7096124	Sterling et al.	Aug 2006	B2
7115205	Robinson et al.	Oct 2006	B2
7116949	Irie et al.	Oct 2006	B2
7128727	Flaherty et al.	Oct 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
7190988	Say et al.	Mar 2007	B2
7204823	Estes et al.	Apr 2007	B2
7230316	Yamazaki et al.	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
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
7553512	Kodas et al.	Jun 2009	B2
7564887	Wang et al.	Jul 2009	B2
7569030	Lebel et al.	Aug 2009	B2
7595623	Bennett	Sep 2009	B2
7608042	Goldberger et al.	Oct 2009	B2
7651845	Doyle et al.	Jan 2010	B2
7652901	Kirchmeier et al.	Jan 2010	B2
7680529	Kroll	Mar 2010	B2
D614634	Nilsen	Apr 2010	S
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
7806854	Damiano et al.	Oct 2010	B2
7806886	Kanderian et al.	Oct 2010	B2
7812774	Friman et al.	Oct 2010	B2
7918825	O'Connor et al.	Apr 2011	B2
7946985	Mastrototaro et al.	May 2011	B2
D640269	Chen	Jun 2011	S
7972296	Braig et al.	Jul 2011	B2
8066805	Zuercher et al.	Nov 2011	B2
8069690	Desantolo et al.	Dec 2011	B2
8114489	Nemat-Nasser et al.	Feb 2012	B2
8178457	De Rochemont	May 2012	B2
8193873	Kato et al.	Jun 2012	B2
8221345	Blomquist	Jul 2012	B2
8251907	Sterling et al.	Aug 2012	B2
8267921	Yodfat et al.	Sep 2012	B2
8350657	Derochemont	Jan 2013	B2
8354294	De et al.	Jan 2013	B2
D677685	Simmons et al.	Mar 2013	S
8417312	Kamath	Apr 2013	B2
8449524	Braig et al.	May 2013	B2
8452359	Rebec et al.	May 2013	B2
8454576	Mastrototaro et al.	Jun 2013	B2
8467980	Campbell et al.	Jun 2013	B2
8478557	Hayter et al.	Jul 2013	B2
D688686	Rhee et al.	Aug 2013	S
8547239	Peatfield et al.	Oct 2013	B2
D693837	Bouchier	Nov 2013	S
8593819	De Rochemont	Nov 2013	B2
D695757	Ray et al.	Dec 2013	S
8597274	Sloan et al.	Dec 2013	B2
8622988	Hayter	Jan 2014	B2
8715839	De Rochemont	May 2014	B2
D710879	Elston et al.	Aug 2014	S
8810394	Kalpin	Aug 2014	B2
D714822	Capua et al.	Oct 2014	S
D715315	Wood	Oct 2014	S
D715815	Bortman et al.	Oct 2014	S
D718779	Hang et al.	Dec 2014	S
D720366	Hiltunen et al.	Dec 2014	S
D720765	Xie et al.	Jan 2015	S
8939935	O'Connor et al.	Jan 2015	B2
D726760	Yokota et al.	Apr 2015	S
D727928	Allison et al.	Apr 2015	S
D730378	Xiong et al.	May 2015	S
D733175	Bae	Jun 2015	S
9061097	Holt et al.	Jun 2015	B2
D734356	Xiong et al.	Jul 2015	S
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
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
D751100	Lindn et al.	Mar 2016	S
D752604	Zhang	Mar 2016	S
D753134	Vazquez	Apr 2016	S
D754718	Zhou	Apr 2016	S
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
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
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
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
9486571	Rosinko	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
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
D810116	McLean et al.	Feb 2018	S
D810771	Gandhi et al.	Feb 2018	S
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
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
D865795	Koo	Nov 2019	S
D872746	Laborde	Jan 2020	S
D874471	Pillalamarri et al.	Feb 2020	S
D875114	Clediere	Feb 2020	S
10583250	Mazlish et al.	Mar 2020	B2
D880498	Shahidi et al.	Apr 2020	S
D888070	Yusupov et al.	Jun 2020	S
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
D938447	Holland	Dec 2021	S
11197964	Sjolund et al.	Dec 2021	B2
11260169	Estes	Mar 2022	B2
D954078	Rahate et al.	Jun 2022	S
20010021803	Blank et al.	Sep 2001	A1
20010034023	Stanton et al.	Oct 2001	A1
20010034502	Moberg et al.	Oct 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
20020010401	Bushmakin et al.	Jan 2002	A1
20020010423	Gross et al.	Jan 2002	A1
20020016568	Lebel et al.	Feb 2002	A1
20020040208	Flaherty et al.	Apr 2002	A1
20020047768	Duffy	Apr 2002	A1
20020070983	Kozub 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
20020161288	Shin et al.	Oct 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
20030060692	Ruchti et al.	Mar 2003	A1
20030086073	Braig et al.	May 2003	A1
20030086074	Braig et al.	May 2003	A1
20030086075	Braig et al.	May 2003	A1
20030090649	Sterling et al.	May 2003	A1
20030100040	Bonnecaze et al.	May 2003	A1
20030122647	Ou	Jul 2003	A1
20030130616	Steil 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
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
20030208113	Mault et al.	Nov 2003	A1
20030208154	Close et al.	Nov 2003	A1
20030212379	Bylund et al.	Nov 2003	A1
20030216627	Lorenz et al.	Nov 2003	A1
20030220605	Bowman et al.	Nov 2003	A1
20030221621	Pokharna et al.	Dec 2003	A1
20040001027	Killen et al.	Jan 2004	A1
20040010207	Flaherty et al.	Jan 2004	A1
20040034295	Salganicoff	Feb 2004	A1
20040045879	Shults et al.	Mar 2004	A1
20040051368	Caputo et al.	Mar 2004	A1
20040064088	Gorman et al.	Apr 2004	A1
20040064259	Haaland et al.	Apr 2004	A1
20040068224	Couvillon et al.	Apr 2004	A1
20040069004	Gist et al.	Apr 2004	A1
20040069044	Lavi et al.	Apr 2004	A1
20040087904	Langley et al.	May 2004	A1
20040097796	Berman et al.	May 2004	A1
20040116847	Wall	Jun 2004	A1
20040122353	Shahmirian et al.	Jun 2004	A1
20040133166	Moberg et al.	Jul 2004	A1
20040147034	Gore et al.	Jul 2004	A1
20040171983	Sparks et al.	Sep 2004	A1
20040203357	Nassimi	Oct 2004	A1
20040204868	Maynard et al.	Oct 2004	A1
20040215492	Choi	Oct 2004	A1
20040220517	Starkweather et al.	Nov 2004	A1
20040241736	Hendee et al.	Dec 2004	A1
20040249308	Forssell	Dec 2004	A1
20050003470	Nelson et al.	Jan 2005	A1
20050020980	Inoue et al.	Jan 2005	A1
20050022274	Campbell et al.	Jan 2005	A1
20050033148	Haueter et al.	Feb 2005	A1
20050049179	Davidson et al.	Mar 2005	A1
20050065464	Talbot et al.	Mar 2005	A1
20050065465	Lebel et al.	Mar 2005	A1
20050075624	Miesel	Apr 2005	A1
20050105095	Pesach et al.	May 2005	A1
20050134609	Yu	Jun 2005	A1
20050137573	McLaughlin	Jun 2005	A1
20050171503	Van et al.	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
20050238507	Diianni et al.	Oct 2005	A1
20050261660	Choi	Nov 2005	A1
20050262451	Remignanti et al.	Nov 2005	A1
20050272640	Doyle et al.	Dec 2005	A1
20050277912	John	Dec 2005	A1
20060009727	O'Mahony et al.	Jan 2006	A1
20060041229	Garibotto et al.	Feb 2006	A1
20060064053	Bollish et al.	Mar 2006	A1
20060079765	Neer et al.	Apr 2006	A1
20060079809	Goldberger et al.	Apr 2006	A1
20060086994	Viefers et al.	Apr 2006	A1
20060100494	Kroll	May 2006	A1
20060134323	O'Brien	Jun 2006	A1
20060134491	Hilchenko et al.	Jun 2006	A1
20060167350	Monfre et al.	Jul 2006	A1
20060173406	Hayes et al.	Aug 2006	A1
20060178633	Garibotto et al.	Aug 2006	A1
20060189925	Gable et al.	Aug 2006	A1
20060189926	Hall et al.	Aug 2006	A1
20060197015	Sterling et al.	Sep 2006	A1
20060200070	Callicoat et al.	Sep 2006	A1
20060204535	Johnson	Sep 2006	A1
20060229531	Goldberger et al.	Oct 2006	A1
20060253085	Geismar et al.	Nov 2006	A1
20060264895	Flanders	Nov 2006	A1
20060270983	Lord et al.	Nov 2006	A1
20060272652	Stocker et al.	Dec 2006	A1
20060276771	Galley et al.	Dec 2006	A1
20060282290	Flaherty et al.	Dec 2006	A1
20070016127	Staib et al.	Jan 2007	A1
20070060796	Kim	Mar 2007	A1
20070060869	Tolle et al.	Mar 2007	A1
20070060872	Hall et al.	Mar 2007	A1
20070083160	Hall et al.	Apr 2007	A1
20070100635	Mahajan et al.	May 2007	A1
20070106135	Sloan et al.	May 2007	A1
20070116601	Patton	May 2007	A1
20070118405	Campbell et al.	May 2007	A1
20070129690	Rosenblatt et al.	Jun 2007	A1
20070142720	Ridder et al.	Jun 2007	A1
20070166453	Van et al.	Jul 2007	A1
20070173761	Kanderian et al.	Jul 2007	A1
20070173974	Lin	Jul 2007	A1
20070179352	Randlov et al.	Aug 2007	A1
20070191716	Goldberger et al.	Aug 2007	A1
20070197163	Robertson	Aug 2007	A1
20070225675	Robinson et al.	Sep 2007	A1
20070244381	Robinson et al.	Oct 2007	A1
20070249007	Rosero	Oct 2007	A1
20070259768	Kear et al.	Nov 2007	A1
20070264707	Liederman et al.	Nov 2007	A1
20070282269	Carter et al.	Dec 2007	A1
20070287985	Estes et al.	Dec 2007	A1
20070293843	Ireland et al.	Dec 2007	A1
20080033272	Gough et al.	Feb 2008	A1
20080033320	Racchini et al.	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
20080071580	Marcus	Mar 2008	A1
20080078400	Martens et al.	Apr 2008	A1
20080097289	Steil et al.	Apr 2008	A1
20080114304	Nalesso et al.	May 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
20080172028	Blomquist	Jul 2008	A1
20080177165	Blomquist et al.	Jul 2008	A1
20080188796	Steil et al.	Aug 2008	A1
20080200838	Goldberger et al.	Aug 2008	A1
20080206067	De et al.	Aug 2008	A1
20080208113	Damiano et al.	Aug 2008	A1
20080214919	Harmon et al.	Sep 2008	A1
20080228056	Blomquist et al.	Sep 2008	A1
20080249386	Besterman et al.	Oct 2008	A1
20080269585	Ginsberg	Oct 2008	A1
20080269714	Mastrototaro et al.	Oct 2008	A1
20080269723	Mastrototaro et al.	Oct 2008	A1
20080287906	Burkholz et al.	Nov 2008	A1
20090006061	Thukral et al.	Jan 2009	A1
20090018406	Yodfat et al.	Jan 2009	A1
20090030398	Yodfat et al.	Jan 2009	A1
20090036753	King	Feb 2009	A1
20090043240	Robinson et al.	Feb 2009	A1
20090054753	Robinson et al.	Feb 2009	A1
20090069743	Krishnamoorthy et al.	Mar 2009	A1
20090069745	Estes et al.	Mar 2009	A1
20090069787	Estes et al.	Mar 2009	A1
20090099521	Gravesen et al.	Apr 2009	A1
20090105573	Malecha	Apr 2009	A1
20090131861	Braig et al.	May 2009	A1
20090156922	Goldberger et al.	Jun 2009	A1
20090156924	Shariati et al.	Jun 2009	A1
20090163781	Say et al.	Jun 2009	A1
20090198350	Thiele	Aug 2009	A1
20090212966	Panduro	Aug 2009	A1
20090221890	Saffer et al.	Sep 2009	A1
20090228214	Say et al.	Sep 2009	A1
20090318791	Kaastrup	Dec 2009	A1
20090326343	Gable et al.	Dec 2009	A1
20090326472	Carter et al.	Dec 2009	A1
20100017141	Campbell et al.	Jan 2010	A1
20100036326	Matusch	Feb 2010	A1
20100057042	Hayter	Mar 2010	A1
20100064243	Buck et al.	Mar 2010	A1
20100077198	Buck et al.	Mar 2010	A1
20100114026	Karratt et al.	May 2010	A1
20100121170	Rule	May 2010	A1
20100137784	Cefai et al.	Jun 2010	A1
20100145272	Cefai et al.	Jun 2010	A1
20100152658	Hanson et al.	Jun 2010	A1
20100174228	Buckingham et al.	Jul 2010	A1
20100185183	Alme et al.	Jul 2010	A1
20100211003	Sundar et al.	Aug 2010	A1
20100228110	Tsoukalis	Sep 2010	A1
20100241066	Hansen et al.	Sep 2010	A1
20100262117	Magni et al.	Oct 2010	A1
20100262434	Shaya	Oct 2010	A1
20100295686	Sloan et al.	Nov 2010	A1
20100298765	Budiman et al.	Nov 2010	A1
20100305965	Benjamin	Dec 2010	A1
20110021584	Berggren et al.	Jan 2011	A1
20110028817	Jin 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
20110071765	Yodfat et al.	Mar 2011	A1
20110124996	Reinke et al.	May 2011	A1
20110144586	Michaud et al.	Jun 2011	A1
20110160652	Yodfat et al.	Jun 2011	A1
20110178472	Cabiri	Jul 2011	A1
20110190694	Lanier et al.	Aug 2011	A1
20110202005	Yodfat et al.	Aug 2011	A1
20110218495	Remde	Sep 2011	A1
20110230833	Landman et al.	Sep 2011	A1
20110251509	Beyhan et al.	Oct 2011	A1
20110313680	Doyle et al.	Dec 2011	A1
20110316562	Cefai et al.	Dec 2011	A1
20120003935	Lydon et al.	Jan 2012	A1
20120010594	Holt et al.	Jan 2012	A1
20120030393	Ganesh et al.	Feb 2012	A1
20120053556	Lee	Mar 2012	A1
20120078067	Kovatchev et al.	Mar 2012	A1
20120078161	Masterson et al.	Mar 2012	A1
20120078181	Smith et al.	Mar 2012	A1
20120101451	Boit et al.	Apr 2012	A1
20120123234	Atlas et al.	May 2012	A1
20120124521	Guo	May 2012	A1
20120136336	Mastrototaro et al.	May 2012	A1
20120150446	Chang et al.	Jun 2012	A1
20120190955	Rao et al.	Jul 2012	A1
20120203085	Rebec	Aug 2012	A1
20120203178	Tverskoy	Aug 2012	A1
20120215087	Cobelli et al.	Aug 2012	A1
20120225134	Komorowski	Sep 2012	A1
20120226259	Yodfat et al.	Sep 2012	A1
20120232520	Sloan et al.	Sep 2012	A1
20120238851	Kamen et al.	Sep 2012	A1
20120250449	Nakano	Oct 2012	A1
20120271655	Knobel et al.	Oct 2012	A1
20120277668	Chawla	Nov 2012	A1
20120282111	Nip et al.	Nov 2012	A1
20120295550	Wilson et al.	Nov 2012	A1
20130030358	Yodfat et al.	Jan 2013	A1
20130158503	Kanderian et al.	Jun 2013	A1
20130172695	Nielsen et al.	Jul 2013	A1
20130172710	Mears	Jul 2013	A1
20130178791	Javitt	Jul 2013	A1
20130231642	Doyle et al.	Sep 2013	A1
20130245545	Arnold et al.	Sep 2013	A1
20130253472	Cabiri	Sep 2013	A1
20130261406	Rebec et al.	Oct 2013	A1
20130296792	Cabiri	Nov 2013	A1
20130296823	Melker 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
20130346858	Neyrinck	Dec 2013	A1
20140005633	Finan	Jan 2014	A1
20140018730	Mueller-Pathle	Jan 2014	A1
20140032549	McDaniel et al.	Jan 2014	A1
20140066859	Ogawa et al.	Mar 2014	A1
20140066886	Roy et al.	Mar 2014	A1
20140074033	Sonderegger et al.	Mar 2014	A1
20140088428	Yang et al.	Mar 2014	A1
20140108046	Echeverria et al.	Apr 2014	A1
20140121635	Hayter	May 2014	A1
20140127048	Diianni et al.	May 2014	A1
20140128705	Mazlish	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	Jul 2014	A1
20140200559	Doyle et al.	Jul 2014	A1
20140230021	Birtwhistle et al.	Aug 2014	A1
20140276554	Finan et al.	Sep 2014	A1
20140276556	Saint et al.	Sep 2014	A1
20140278123	Prodhom et al.	Sep 2014	A1
20140309615	Mazlish	Oct 2014	A1
20140316379	Sonderegger et al.	Oct 2014	A1
20140325065	Birtwhistle et al.	Oct 2014	A1
20150018633	Kovachev et al.	Jan 2015	A1
20150025329	Amarasingham et al.	Jan 2015	A1
20150025495	Peyser	Jan 2015	A1
20150025503	Searle et al.	Jan 2015	A1
20150041498	Kakiuchi et al.	Feb 2015	A1
20150120317	Mayou et al.	Apr 2015	A1
20150134265	Kohlbrecher et al.	May 2015	A1
20150134353	Ferrell et al.	May 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
20150217052	Keenan et al.	Aug 2015	A1
20150217053	Booth et al.	Aug 2015	A1
20150265767	Vazquez et al.	Sep 2015	A1
20150301691	Qin	Oct 2015	A1
20150306314	Doyle et al.	Oct 2015	A1
20150331995	Zhao et al.	Nov 2015	A1
20150351671	Vanslyke et al.	Dec 2015	A1
20150351672	Vanslyke et al.	Dec 2015	A1
20150356250	Polimeni	Dec 2015	A1
20150366945	Greene	Dec 2015	A1
20160015891	Papiorek	Jan 2016	A1
20160019352	Cohen et al.	Jan 2016	A1
20160038673	Morales	Feb 2016	A1
20160038689	Lee et al.	Feb 2016	A1
20160051749	Istoc	Feb 2016	A1
20160082187	Schaible et al.	Mar 2016	A1
20160089494	Guerrini	Mar 2016	A1
20160175520	Palerm et al.	Jun 2016	A1
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
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
20170188943	Braig et al.	Jul 2017	A1
20170189625	Cirillo 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	Afonso	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

Foreign Referenced Citations (152)

Number	Date	Country
2015200834	Mar 2015	AU
2015301146	Mar 2017	AU
1040271	Oct 1978	CA
3026851	Feb 2020	CA
1297140	May 2001	CN
101208699	Jun 2008	CN
4200595	Sep 1993	DE
19756872	Jul 1999	DE
0026056	Apr 1981	EP
0341049	Nov 1989	EP
0496305	Jul 1992	EP
0549341	Jun 1993	EP
0867196	Sep 1998	EP
0939451	Sep 1999	EP
1376759	Apr 2001	EP
1177802	Sep 2004	EP
1491144	Dec 2004	EP
1571582	Sep 2005	EP
0801578	Jul 2006	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
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
1125897	Sep 1968	GB
2443261	Apr 2008	GB
51-125993	Nov 1976	JP
02-131777	May 1990	JP
2004-283378	Oct 2004	JP
2005-326943	Nov 2005	JP
2007-525276	Sep 2007	JP
2008-513142	May 2008	JP
2018-153569	Oct 2008	JP
2012-527981	Nov 2012	JP
2017-516548	Jun 2017	JP
2017-525451	Sep 2017	JP
2019-525276	Sep 2019	JP
2004740148	Oct 2007	TW
M452390	May 2013	TW
8606796	Nov 1986	WO
9800193	Jan 1998	WO
9855073	Dec 1998	WO
9910040	Mar 1999	WO
9910049	Mar 1999	WO
9956803	Nov 1999	WO
9962576	Dec 1999	WO
0030705	Jun 2000	WO
0032258	Jun 2000	WO
0048112	Aug 2000	WO
0172354	Oct 2001	WO
0178812	Oct 2001	WO
0215954	Feb 2002	WO
0226282	Apr 2002	WO
0243866	Jun 2002	WO
0276535	Oct 2002	WO
0282990	Oct 2002	WO
0316882	Feb 2003	WO
0339362	May 2003	WO
0345233	Jun 2003	WO
0397133	Nov 2003	WO
2004043250	May 2004	WO
2004092715	Oct 2004	WO
2005051170	Aug 2005	WO
2005082436	Sep 2005	WO
2005110601	Nov 2005	WO
2005113036	Dec 2005	WO
2006053007	Dec 2005	WO
2007064385	Jun 2007	WO
2007066152	Jun 2007	WO
2007078937	Jul 2007	WO
2008024810	Feb 2008	WO
2008029403	Mar 2008	WO
WO 2008048584	Apr 2008	WO
2008133702	Nov 2008	WO
2009039203	Mar 2009	WO
2009045462	Apr 2009	WO
2009049252	Apr 2009	WO
2009066287	May 2009	WO
2009098648	Aug 2009	WO
2009134380	Nov 2009	WO
2010022069	Feb 2010	WO
2010053702	May 2010	WO
2010077279	Jul 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
WO 2013097929	Jul 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
2014109898	Jul 2014	WO
2014110538	Jul 2014	WO
2014149357	Sep 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
2016004088	Jan 2016	WO
2016022650	Feb 2016	WO
2016041873	Mar 2016	WO
2016089702	Jun 2016	WO
2016141082	Sep 2016	WO
2016161254	Oct 2016	WO
2017004278	Jan 2017	WO
2017091624	Jun 2017	WO
2017105600	Jun 2017	WO
2017184988	Oct 2017	WO
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 (4)

Entry
US 5,954,699 A, 09/1999, Jost et al. (withdrawn)
International Preliminary Report on Patentability in Application No. PCTUS/2017/012806, dated Jul. 26, 2018, 9 pages.
International Search Report and Written Opinion in Application No. PCTUS/2017/012806, dated Apr. 5, 2017, 14 pages.
Percival et al., “Closed-Loop Control and Advisory Mode Evaluation of an Artificial Pancreatic β Cell: Use of Proportional-Integral-Derivative Equivalent Model-Based Controllers,” J Diabetes Sci Tech 2(4):636-644, Jul. 2008.

Related Publications (1)

	Number	Date	Country
	20190221307 A1	Jul 2019	US

Provisional Applications (1)

	Number	Date	Country
	62278231	Jan 2016	US

Continuations (1)

	Number	Date	Country
Parent	15402493	Jan 2017	US
Child	16360751		US

User interface for diabetes management system

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Disclaimer

Abstract