Real time management of data relating to physiological control of glucose levels

Description

TECHNICAL FIELD

The present invention relates generally to an integrated diabetes management system, and more particularly, to the use of exogenous data to predict alarms and to manage glucose levels.

BACKGROUND

Glucose monitoring systems for patients afflicted with diabetes may incorporate various functionalities, including a capability to project or predict alarms to warn patients and/or provide information related to expected glucose levels, for example. Various factors may affect glucose levels; however, glucose monitoring systems generally only have access to certain types of information and factors (i.e., the monitored information). Thus, the projected alarms generated by such glucose monitoring systems are based on limited data and, although quite helpful, may be less reliable than if additional relevant information and factors were taken into account in projecting the alarms.

In a continuous glucose management (“CGM”) system, it is possible to predict if the glucose level is going to cross a hypoglycemic or hyperglycemic threshold in the future by using the CGM data. One way to do this is to estimate the rate-of-change of the glucose and project from the latest glucose point to some time in the future. While this projected alarm is helpful, there can be a significant number of false alarms and misdetections. These often occur when the glucose level of the patient changes direction, which often occurs. These changes are caused by physiological effects (the body's production of insulin), insulin boluses, meal intake, exercise, and other causes.

In the past, continuous glucose monitoring and continuous insulin delivery are accomplished by different pieces of hardware devices that do not share data. Each device provides real time management tools for diabetes and insulin delivery respectively. With the convergence of continuous glucose monitoring and insulin pumps, real-time management tools could be developed that will enhance the existing tools and provide new real-time management functionalities that did not exist before.

For example, the FreeStyle Navigator® system from Abbott Diabetes Care Inc, Alameda, Calif., a continuous glucose monitor, provides a projected low glucose (hypoglycemia) alarm function using the trend of the glucose profile and the rate of change of glucose to predict when the glucose reading would fall below the low threshold that can be set by the user. The user can set the alarm sensitivity to receive a warning of up to thirty minutes prior to the low glucose event. With the addition of insulin delivery data, for example, the “insulin on board” information from the insulin pump, then we would be able to enhance the reliability of the projected low glucose alarm to be provided earlier and provide a tool for the user to figure out the amount of carbohydrates to take to prevent the low blood glucose from occurring.

As used herein, the term “exogenous” data is meant to encompass measurements other than glucose measurements.

On the other hand, many therapy parameters that govern the real time bolus decision using the insulin pump can be better adjusted and refined with the availability of the continuous glucose information. For example, many smart pumps today provide a way to calculate the amount of insulin to cover a food or meal event through the use of the carbohydrate ratio (also referred to as “carb ratio” herein) and the bolus calculator. However, the precise carbohydrate ratio to use is an empirically derived number. With the continuous glucose data available, the “accuracy” of the carbohydrate ratio used for a food bolus calculation may be assessed in real time to provide adjustment guidance for refining the carbohydrate ratio for use in the subsequent food or meal event.

Hence those of skill in the art have recognized a need for increased reliability of projected glucose alarms. Those skilled in the art have also recognized the need for the instant or near-instant incorporation of exogenous data to further increase the reliability and effectiveness of projected alarms. A further need has been recognized for providing tools to more accurately control glucose levels; and further, those skilled in the art have identified a need for the use of exogenous data in fine-tuning the management of a diabetic patient's glucose control. The present invention fulfills these needs and others.

SUMMARY OF THE INVENTION

Briefly and in general terms, the invention is directed to a system and method for processing glucose level measurement data with exogenous data to result in more reliable projected alarms and to enable tuning of patient-specific insulin data.

In accordance with the invention, there is provided an integrated glucose monitoring system, comprising a memory configured to store data relating to at least two measurements of a physiological glucose level in a patient, wherein the two measurements are taken at different time points t1 and t2, a safe range of glucose for the patient; and at least one other medically relevant patient-specific data point of exogenous data, a user interface comprising a visual display, and a processor comprising computer-executable instructions to determine a rate of change between the at least two glucose level measurements and based on the determined rate of change, further determine a glucose level at a future time t3, process the glucose level determined for time t3 with the stored exogenous data to result in an integrated glucose level for time t3, and provide an alarm at the user interface if the projected integrated glucose level for time t3 is outside the safe range.

In accordance with more detailed aspects, the exogenous data is selected from the group of insulin on board, insulin sensitivity, prior carbohydrate intake, basal rate, and available insulin bolus. The processor comprises a further computer-executable instruction to determine a recommended change to one or more of the medically relevant data points, the change comprising a therapeutic response. The recommended therapeutic response comprises one or more of an insulin bolus, intake of a particular level of carbohydrates, and temporary change to a basal insulin rate. The processor comprises a further computer-executable instruction to display the recommended therapeutic response on the visual display. The user interface comprises a graphical user interface on the visual display and an input device for communicating data and instructions from a patient to the processor, and wherein the alarm comprises a visual alarm provided on the graphical user interface.

In other aspects, the integrated glucose monitoring system further comprises a communication module configured to communicate with an insulin delivery pump engaged with the patient to acquire patient-specific insulin delivery data including insulin on board, wherein the processor processes the glucose level determined for time t3 from the rate of change data as a function of the insulin delivery data received from the delivery pump to result in the integrated glucose level for time t3. Additionally, a communication module is configured to communicate an alarm to a remote location wirelessly or by wired connection. The processor also comprises a further computer-executable instruction to control the communication module to communicate measured glucose level data, and alarms to a remote location.

In accordance with a method, there is provided a method of integrated glucose monitoring, comprising storing data relating to at least two measurements of a physiological glucose level in a patient, wherein the two measurements are taken at different time points t1 and t2, storing a safe range of glucose for the patient, storing at least one other medically relevant patient-specific data point of exogenous data, determining a rate of change between the stored at least two glucose level measurements and based on the determined rate of change, further determining a glucose level at a future time t3, processing the glucose level determined for time t3 with the stored exogenous data to result in an integrated glucose level for time t3, and providing an alarm if the projected integrated glucose level for time t3 is outside the stored safe range.

In further method aspects, the invention is directed to a method for reducing false alarms in managing projected alarms related to glucose levels, comprising determining a rate of change between at least two glucose level measurements taken at different time points t1 and t2, identifying whether an expected glucose level at a future time point t3 is above or below a target glucose level, determining a recommended change to one or more medically relevant data points comprising determining a therapeutic response if a difference between the expected glucose level and the target glucose level exceeds a preset warning value, and identifying whether the recommended change to one or more of the medically relevant data points has been performed at a predetermined time point t4 before future time point t3 has been reached, wherein an alarm is provided only where the recommended change to one or more of the medically relevant data points has not been performed at the predetermined time point t4, thereby reducing false alarms. In additional aspects, the expected glucose level is a function of the rate of change between the at least two glucose level measurements and at least one or more of the medically relevant data points. The one or more medically relevant data points is selected from the group of insulin on board, insulin sensitivity, prior carbohydrate intake, basal insulin, available insulin bolus; projection time, insulin action time, carbohydrate ratio, carbohydrate uptake time.

In yet a further detailed aspect, the recommended therapeutic response comprises one or more of a particular insulin bolus, intake of a particular level of carbohydrates, and temporary change to a basal insulin level.

An integrated glucose management system for tuning patient-specific insulin data, comprises a memory configured to record and store data representing measurements of physiological glucose levels in a patient, and to store exogenous data in the form of attributes tagged to the stored glucose measurement data, a user interface comprising a visual display and an input device configured to receive and communicate user input data and instructions, and a processor comprising computer-executable instructions to record multiple series of glucose level measurement data into the memory during defined time periods, tag each of the recorded series of glucose level measurement data with exogenous attributes including a profile name, wherein the name of the profile is selected to identify the data recording as belonging to a particular category of patient conditions, access the memory to retrieve a plurality of profiles having the same profile name, compare the recorded data of the plurality of retrieved profiles to detect a persistent pattern of undesirable measured glucose levels existing in the plurality of profiles, provide an alarm at the user interface if a persistent pattern is detected in the data of the retrieved plurality of profiles, and provide a recommended change to be made to tune the patient-specific insulin data as a result of the detected persistent pattern, and display the recommended change on the user interface.

In more detailed aspects of the integrated glucose management system, the computer-executable instructions include an excess insulin manager configured to provide a plurality of alternative recommended changes to the patient-specific insulin data. The excess insulin manager is further configured to prioritize a recommended increase in carbohydrate intake lower than recommended changes to insulin delivery. The exogenous patient-specific insulin data comprises basal rate, carb ratio, and insulin sensitivity. The profiles include a skip-meal profile, a meal test profile, and a correction bolus test profile. The processor comprises a further computer-executable instruction to require that a minimum number of profiles must be outside the safe range before a recommendation will be provided. The processor comprises a further computer-executable instruction to require that all profiles retrieved for comparison must have been recorded within a selected time period. The processor comprises a further computer-executable instruction to require that a recommendation for change of basal rate, carb ratio, and insulin sensitivity cannot exceed a predetermined amount.

In further detailed aspects, the integrated glucose management system includes a communication module permitting wireless or wired communication to and from the system to a remote location for alarms, recommended changes, patient-specific insulin data, and other data. A health care provider at a remote location may override limitations on recommended changes. Patient glucose measurements and other medical data may be stored remotely for access by the patient's health care providers or other authorized personnel.

BRIEF DESCRIPTION OF THE DRAWINGS

Various features and advantages of the disclosure will become more apparent by the following detailed description of several embodiments thereof with reference to the attached drawings, of which:

FIG. 1 is a graph providing the change in patient glucose resulting from changes in basal rate over time showing in particular the increase in glucose with a lowered basal rate and a decrease in glucose with a higher basal rate;

FIG. 2 is a graph that displays patient glucose versus time related to changes in carb ratio and carbohydrate bolus, according to an embodiment;

FIG. 3 is a graph that displays the effect of more accurate projected alarms when an unexpected rise in glucose occurs taking the glucose to a hyperglycemic state, showing the effect that early insulin delivery can have;

FIG. 4 is a graph of glucose versus time that illustrates the result of the delivery of a correction bolus when insulin sensitivity is considered;

FIG. 5 illustrates a block diagram of an integrated continuous glucose monitoring and insulin pump system, according to an embodiment in which more reliable projected alarms are provided and in which profiles of continuous glucose monitoring data are produced for tuning of exogenous patient-specific insulin data for more accurate control over a patient's glucose levels;

FIG. 6 is a flow chart illustrating a method for managing glucose levels, projections, and alarms related to glucose levels, according to an embodiment; and

FIG. 7 is a flow chart showing a profile recording feature in accordance with aspects of the invention in which profiles are formed of continuous glucose data of the patient and are used to determine fine-tuning of patient-specific insulin values to achieve better control over a patient's glucose levels.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Reference will now be made in detail to various embodiments of the invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to like or corresponding elements throughout. While the embodiments are described with detailed construction and elements to assist in a comprehensive understanding of the various applications and advantages of the embodiments, it should be apparent however that the embodiments can be carried out without those specifically detailed particulars. Also, well-known functions or constructions will not be described in detail so as to avoid obscuring the description with unnecessary detail. It should be also noted that in the drawings, the dimensions of the features are not intended to be to true scale and may be exaggerated for the sake of allowing greater understanding.

An integrated continuous glucose monitoring (CGM) and medication delivery system, such as an insulin pump, is highly advantageous as two types of information (i.e., continuous glucose monitoring information (e.g., glucose trend and profile information) and continuous insulin delivery information from the medication delivery system) may be combined for various calculations, predictions, and analyses useful in managing a person's diabetes. Examples of the calculations, predictions, and analyses include, but are not limited to: a projected alarm for providing a warning for insulin excess and carbohydrate requirements; a temporary basal manager for managing basal rate reduction through temporary basal control; a basal rate tuner for adjusting basal rate using continuous glucose information; a carbohydrate ratio tuner for adjusting carbohydrate ratio used in a bolus calculator for administering food bolus; and a correction factor tuner for adjusting insulin sensitivity in a bolus calculator for administering a correction bolus.

As used herein, the term “project” or “projected” is synonymous with “predict” or “predicted” and “forecast” or “forecasted.”

As noted above, information related to meals and insulin delivery may affect a projected alarm. For example, if a projected hyperglycemia alarm were about to occur, but information related to a recent insulin bolus delivery were provided, then the projected alarm may be desirably delayed as it may be unnecessary due to the effect that the recent bolus delivery will have.

More specifically, a CGM system may predict if a glucose level is going to cross a hypoglycemic or hyperglycemic threshold based upon monitored glucose data, such as rate-of-change and the projected glucose level. However, the glucose level may change direction due to, for example, physiological effects (e.g., production of insulin), bolus, meal intake, exercise, and other factors. The change in direction may have the effect of the glucose level not crossing a threshold, thus making a projected alarm unnecessary. Thus, taking into account the factors noted above (e.g., physiological effects (e.g., production of insulin), bolus, meal intake, exercise, and other factors), it can then be determined if a projected alarm is indeed necessary, thereby increasing the efficacy of the projected alarm in its predictive capability features.

Examples of the increased reliability of the predictive capability features when insulin delivery and meal information are taken into account include the following: (i) if the projected alarm feature indicates that the hyperglycemic event was going to happen soon, but a bolus occurred ten minutes prior, the projected alarm may be cancelled; (ii) if a projected low glucose alarm was about to occur but a meal event was recently entered, the projected alarm may be cancelled; (iii) if a projected low glucose alarm was about to occur but an insulin bolus was recently given, then the projected alarm may be initiated immediately instead of waiting for the previously scheduled time; and (iv) if the presence of “exogenous” data, such as insulin on board (IOB), suggests that the patient is in an “insulin excess” state, then the projected alarm may be initiated when in the absence of the IOB information, such projected alarm would not be indicated.

To implement a projected alarm that provides a warning for insulin excess and to provide carbohydrate requirements, the following factors may by utilized to determine when a patient's glucose level will fall below an acceptable limit: current glucose level, insulin on board (“IOB”), insulin sensitivity, carbohydrate ratio, and duration of insulin action. Other factors may also be taken into account. As used herein, the “carbohydrate ratio” refers to the amount of carbohydrates required for each unit of insulin.

The two scenarios in Table 1 below may be used to illustrate the projected alarm feature, according to an embodiment, in which a patient's current glucose level is 173 mg/dL. A response in each scenario may differ depending on the availability of IOB information. The presence of IOB information can enhance the time horizon of a low glucose (hypoglycemia) projected alarm over one that is based solely on using glucose rate of change information.

TABLE 1

Scenario 1
Scenario 2

Current glucose
173 mg/dL
173 mg/dL

Insulin on board (IOB)
NO IOB information
4.6 units

Carb ratio
12 grams
12 grams

Target glucose level
100 mg/dL
100 mg/dL

Insulin sensitivity
45.6 mg/L
45.6 mg/L

Alarm information
No alarm is indicated.
Indicate projected low glucose

alarm. Glucose level will fall

below low threshold of 70 mg/dL

in about 2.5 hours.

This calculation is based on

insulin action profile, insulin

action time, and insulin

sensitivity.

In this example, glucose will

fall below 70 mg/dL when

2.26 units of insulin are used

up. Assume a linear insulin

action profile for the purpose

of the illustration; this is about

(~49% of current insulin on

board amount) 2.5 hours if

time of insulin action is set at

5 hours.

Possible Recommendation
Patient needs 1.6 units of
In addition to initiating a

insulin bolus.
projected low glucose alarm,

provide a potential avoidance

strategy: needs 36 g of

carbohydrates to cover the

excess insulin.

With scenario 2 illustrated above in Table 1, an enhanced projected hypoglycemic alarm based on the use of the exogenous insulin on board, and with the availability of personalized therapy parameters like insulin sensitivity, carb ratio, and target BG, may signal to the patient that within approximately 2.5 hours, a low glucose level will be reached.

According to another embodiment, an “excess insulin manager” can provide a recommendation to avoid the future low glucose level depending on the type of information available to the system. For example, in Table 1, Scenario 2, with the availability of the particular patient's carb ratio, the excess insulin manager can provide the recommendation to take 36 g of carbohydrates now.

A temporary basal approach, according to another embodiment, operates to determine a basal reduction necessary to compensate for excess insulin on board, when additional access and control of the insulin delivery rates are available. With the same example in Scenario 2 of Table 1, the “excess insulin manager” can provide a different option to deal with excess insulin by reducing the future basal insulin delivery by programming a temporary basal insulin reduction. This alternative may be preferred because the user would not need to eat additional carbohydrates, which tend to add weight to the patient. Furthermore, the “excess insulin manager” could provide the means for the user to take both options to offset the excess insulin; i.e., take additional carbohydrates and make a temporary basal reduction.

Table 2 below shows that multiple recommendations may be possible after the initiation of the low alarm depending on access to insulin delivery information and control. In Table 2, Scenario 2 is the same as Scenario 2 in Table 1 except for the “possible recommendation” in that in Table 2, multiple recommendations are provided due to the presence of the basal rate information.

TABLE 2

Scenario 2
Scenario 3

Current glucose
173 mg/dL
173 mg/dL

Insulin on board (IOB)
4.6 units
4.6 units

Carb ratio
12 grams
12 grams

Target glucose level
100 mg/dL
100 mg/dL

Insulin sensitivity
45.6 mg/L
45.6 mg/dL

Basal insulin delivery rate

Alarm information
Indicate projected low glucose
Indicate projected low glucose

alarm. Glucose level will fall
alarm. Glucose level will fall

below low threshold of 70 mg/dL
below low threshold of 70 mg/dL

in about 2.5 hours.
in about 2.5 hours.

This calculation is based on
This calculation is based on

insulin action profile, insulin
insulin action profile, insulin

action time, and insulin
action time, and insulin

sensitivity.
sensitivity.

In this example, glucose will
In this example, glucose will

fall below 70 mg/dL
fall below 70 mg/dL

when 2.26 units of insulin is
when 2.26 units of insulin is

used up. Assume a linear
used up. Assume a linear

insulin action profile for the
insulin action profile for the

purpose of the illustration; this
purpose of the illustration; this

is about (~49% of current
is about (~49% of current

insulin on board amount) ~2.5
insulin on board amount) ~2.5

hours if time of insulin action
hours if time of insulin action

is set at 5 hours.
is set at 5 hours.

Recommendation
No specific insulin rate
With additional basal rate

information:
information:

Needs 36 g of carbohydrates
a) needs 36 g of carbohydrates

to cover the excess insulin.
to cover the excess insulin

b) reduces future basal

delivery to offset the excess

insulin (2.34 units). Specific

temp basal rate and time can

be provided to facilitate quick

setting of the rate on an

integrate pump.

c) combination of both -

wizard like process can guide

the user through determining

how much carbs to take and

how much reduction in basal

to make into the future.

According to another embodiment, the “excess insulin manager” could be initiated by the user, instead of being initiated by the occurrence of a projected hypoglycemia alarm. The user may choose to turn off the projected alarm and use the “excess insulin manager” features on-demand. An example would be where the user wants to check for excess insulin right before going to bed so that he or she can take appropriate measures to avoid nocturnal hypoglycemia.

The production of continuous glucose data by a CGM system offers the ability to fine-tune various glucose management factors to permit more accurate control of a patient's glucose levels. For patients having an insulin pump, a basal rate of insulin delivery is typically assigned for the purpose of maintaining constant control over the patient's glucose level. Additionally, a carb ratio, mentioned above, is determined for each patient based on that patient's characteristics, which is used to determine the amount of carbohydrates that will cover, or neutralize, one unit of insulin in that particular patient. Insulin amounts and calculations of carbohydrate amounts for this patient are determined by his or her carb ratio. Also, the individual patient's sensitivity to insulin or “correction factor” is determined and is used to calculate the speed with which insulin affects the patient, also a factor in determining when and how much insulin to deliver to that patient. To provide further control over the patient's glucose, a profile recording feature is provided.

The “profile recording feature” that can be enabled by the user to record the glucose data from the CGM system as a particular “profile.” User action may be used to set the start and end times of the profile recording or the user may “tag” an event in which case the processor will initiate and terminate the data recording and label that recorded data as a particular user profile. For example, the profile recording may require user input of the start time and the end time. The start time could be manually entered, or automatically entered if it corresponds to the time of certain user or device action, such as the start of a meal bolus, the start of a correction bolus, etc. The end time could be manually entered by the user or it could correspond to the completion of certain user or device action. These profiles can be categorized by the type of user actions, analyzed, and displayed in reports for use in fine-tuning glucose management factors. A specific rule engine can be implemented to provide actionable recommendations to the user based on the output of the recorded profiles.

Some examples of rules that may be implemented are: 1) rule for persistent/recurring profile, e.g., require a minimum number of profiles, N, all of which must be greater than the target or all of which must be less than the target by a certain amount X before a recommendation for a change in a factor can be given; 2) rule for usable profile for analysis; e.g., only a test measured within the last two weeks can be used for analysis for an insulin recommendation; data that is too old could be irrelevant now; 3) rule for refreshing the profile queue; more profiles must be entered into the queue after every insulin change that has taken place, or after X amount of time has elapsed since the first recording; and 4) rule for safety, that is, only allow an increase in basal insulin of ten percent at a time and set the maximum incremental change possible for the carb ratio and the correction factor.

The above rule engine settings can be set by the user or by the health care provider (“HCP”) depending on the sophistication of the user. Also, the user's diabetes management devices may have possible security and lock out features so that only the HCP can set the rules without allowing the user to change them.

According to one embodiment, a “skip-meal test” feature is provided to the user to allow the user to mark the CGM data during the meal that is skipped for the purpose of fine-tuning the basal rate. Upon a user's initiating the “skip-meal test,” the user will be given a chance to choose the start time of the skip-meal test (either the time when the “skip-meal test” is initiated on the user's interface (“UI”), or the user will be given the means to set a time prior to when the “skip-meal test” is initiated). The system will then record the CGM data starting from the user-indicated start time to form a skip-meal test profile. The recording of this CGM profile will end upon a certain user indication through the device UI, a spike in the CGM signal, or a certain device event (e.g., a meal bolus).

A “skip meal profile” report similar to FIG. 1 may be used to analyze and visualize the recorded “skip-meal” profiles. With reference to FIG. 1 (“Basal Rate Tuner”), a graph 200 is provided to help the user decide whether a basal rate adjustment may be needed based on the recorded “skip meal profiles.” The left vertical axis provides the glucose level in mg/dL in this embodiment while the bottom horizontal axis provides time, starting with the start time of the individual profile recording. The 120 mg/dL line 206 indicates the target glucose level. The dashed line 208 above that level indicates a higher glucose level than target, which may indicate that an increase in basal rate should be affected. The dashed line 210 below target 206 indicates a low glucose and that perhaps the basal rate should be lowered. If persistent pattern is observed in the skip-meal profiles over a certain time, an appropriate action can be recommended by the “basal rate tuner” to fine-tune the basal rate to get it closer to the target level 206. However, if a persistent pattern is not observed over time, such a recommendation may not be made since the data does not clearly indicate that a continuous problem exists.

A “carb tuner” is also provided in which a “meal test” feature is provided to the user. With this feature, the meal test allows the user to start recording the CGM data to form a meal test profile after a “meal event,” that profile representing the glucose response for that meal. Typically, a patient takes an insulin bolus prior to the start of a meal to manage the likely increasing spike in glucose level that eating a meal causes. That meal bolus for the patient is calculated using the patient's carb ratio. The meal test feature permits the patient to ascertain whether his or her carb ratio needs tuning.

The start of the recording of CGM data is based on a user prompt, a user entered meal event, or a device-driven event such as a meal bolus. The end of the recording of CGM data for that profile is based on user prompt or a pump device related parameter, such as the insulin action time. Appropriate meal bolus parameters such as the carb ratio will be saved as an attribute that will be associated with the profile. Additional user-entered or device related-tags, such as food description and meal type (breakfast, lunch, dinner, snack, etc.) can also be added as attributes that can be associated with the recorded profile.

A “meal test” report, similar to that shown in FIG. 2, may be used to analyze and visualize the recorded “meal test” profiles for the purpose of fine-tuning the user's carbohydrate ratio used in a bolus calculator for recommending food bolus amounts at meal times in an integrated CGM and insulin pump system.

With further reference to FIG. 2 (“Carbohydrate Ratio Tuner”), a graph 220 provides information related to the user's carbohydrate ratio. The left vertical axis provides the user's glucose level while the bottom horizontal axis provides time. The graph illustrates when to increase the patient's carbohydrate ratio (and decrease the carbohydrate bolus) and when to decrease the patient's carbohydrate ratio (and increase the carbohydrate bolus). The 100 mg/dL solid line glucose level 226 is the target glucose level and the effects of a meal, taken at 6 pm are seen with the three representative lines. A correct carb ratio is shown with the middle dashed line 228 showing a modest increase in glucose following the mean with a drop back to near target glucose level at about 9 pm. However, the upper dashed line 230 shows an undesirable increase in glucose indicating a carb ratio that is too high. The line 230 may indicate that a decrease in the carb ratio should be determined for this patient, depending on whether a persistent pattern exists over time.

The lower dashed line 232 indicates that the glucose level dropped much lower than desired after the meal thus indicating that the carb ratio is too low and should be raised. As with the highest glucose line on the figure, i.e., line 230, a change in the carb ratio for this patient may be needed depending on whether a persistent pattern appears over a period of time. Such a persistent pattern in glucose levels, as determined by the integrated CGM and insulin pump system, is utilized to calculate a change recommendation in carb ratio for the patient. Additional data labels can be used to show the various profile attributes to interpretation.

In another embodiment, a collection of “meal test profiles” may be accessed by the patient prior to meal bolus events. A “meal bolus profile” queue may be implemented as part of the carb ratio selector during a meal bolus calculation process, in which the patient can select the carb ratio based on the previously recorded profile. The queue may indicate a carb ratio to use for meal bolus events. The results in the queue may be standardized, according to an embodiment, to group together multiple meal bolus events so that a general modification recommendation may be generated. Such collected profiles may be characterized by a particular meal, such as breakfast or other, and may be further characterized by the type of food to be eaten for that meal. The patient may then want to select the profile that provided the best glucose control for that prior event and have that previous carb ratio applied to the present meal event.

Moreover, the “meal test profile” and “carbohydrate ratio tuner” features may provide the means to add a warning mechanism for an under-bolus alarm in which under-dosing of food bolus insulin occurs if the food bolus profile deviates from an expected pattern based on the selected recorded “meal test profile”. For example and with reference to FIG. 3 (“Carbohydrate Ratio Tuner—Early Warning” with glucose level at the vertical left axis and time at the bottom horizontal axis), a graph 240 is provided that indicates an expected glucose level 246, as well as possible ranges of the expected glucose level based on previously recorded profiles. A meal is consumed at 0 minutes with a glucose level of 120 mg/dL. A possible range is shown with an upper solid line 248 and the lower dashed line 250. The expected glucose level 246 is shown with the dotted line. The under-bolus alarm may be generated to indicate a need for patient intervention even if a hyperglycemia alarm is not triggered.

A third tuner is the insulin sensitivity factor or correction factor. A “correction bolus test” feature is provided to allow the user to record the CGM data profile after a correction bolus delivery for the purpose of fine-tuning the insulin sensitivity factor that may be implemented in the integrated CGM and insulin pump system. The start of the recording is based on a user prompt, a user entered correction bolus event, or a device-driven event such as a correction bolus. The end of the recording is based on a user prompt or a pump-device related parameter, such as the insulin action time. Appropriate correction bolus parameters, such as the insulin sensitivity factor, will be saved as an attribute that will be associated with the correction bolus profile. Additional user-entered or device-related tags (e.g., time of day) can also be added to the stored data as attributes that can be associated with the recorded profile.

A “correction bolus test” report, similar to FIG. 4, may be used to analyze and visualize the recorded “meal test” profiles for the purpose of tuning the carbohydrate ratio used in a bolus calculator for recommending food bolus amounts in an integrated CGM and insulin pump system.

With reference to FIG. 4 (“Insulin Sensitivity Tuner”), correction bolus information is displayed in graph 260, indicating a need to either increase insulin sensitivity (decrease correction bolus) or decrease insulin sensitivity (increase correction bolus). The glucose level is shown as the vertical left axis while once again time is shown as the bottom horizontal axis. In this case, all the “correction test profiles” with an insulin bolus delivery at 6 pm are plotted in a representative plot to illustrate the possible action based on the representative pattern of the profiles. The correct insulin sensitivity is shown as the middle dashed line 266. If the “correction test profiles” show a persistent pattern in regard to the upper dashed line 268 or the lower dashed line 270, appropriate actionable recommendations can be suggested to the user.

In yet another embodiment, these “correction bolus test” profiles related to insulin sensitivity adjustments may conveniently be provided prior to correction bolus events. The previously recorded profiles may be placed in a “correction bolus profile” queue for access by a patient. The results of the queue may be standardized, according to an embodiment, to group together multiple bolus results for a general modification recommendation for an upcoming correction bolus event. Should the patient experience a situation identical or similar to one of the profiles, he or she may select a profile from the queue for use of that sensitivity with the present situation.

With reference now to FIG. 5, a block diagram of an integrated CGM and insulin pump system 600, according to an embodiment, is illustrated. The integrated CGM and insulin pump system 600 may operate to manage alarm projections and alarms related to glucose levels. The system is also configured and programmed to produce profiles from CGM data to be used in tuning certain glucose management factors, as discussed above.

The system 600 may include, according to an embodiment, a glucose monitoring and management portion as well as an insulin infusion pump that stores or otherwise acts upon data relating to glucose measurements, carbohydrate intake values, and other data of interest in diabetes management.

The system 600 may include a glucose sensor 601, a transmitter unit 602 coupled to the sensor 601, and a primary receiver unit 604 which is configured to communicate with the transmitter unit 602 via a communication link 603. Those of ordinary skill in the art will readily recognize that the sensor represented as element 601 may include a drug delivery device, such as an insulin infusion system which includes a transmitter and, if so, that the principles of data preservation and transfer disclosed herein would apply as well to such a system. Therefore, system 600 as depicted in FIG. 5 will be understood to be representative rather than limiting of the arrangements of medical data receivers and transmitters with which the present invention may be used.

The primary receiver unit 604 may be configured to receive data from the transmitter unit 602 and may be further configured to transmit data to a data processing terminal/infusion section 605 for evaluating the data received by the primary receiver unit 604. Moreover, the data processing terminal/infusion section 605 in one embodiment may be configured to receive data directly from the transmitter unit 602 via a communication link 607 which may optionally be configured for bi-directional communication.

Also shown in FIG. 5 is a secondary receiver unit 606 which is operatively coupled to the communication link 603 and configured to receive data transmitted from the transmitter unit 602. Moreover, as shown in FIG. 5, the secondary receiver unit 606 is configured to communicate with the primary receiver unit 604 as well as the data processing terminal/infusion section 605. The secondary receiver unit 606 may be configured for bi-directional wireless communication with each of the primary receiver unit 604 and the data processing terminal/infusion section 605. As discussed in further detail below, in one embodiment, the secondary receiver unit 606 may be configured to include a limited number of functions and features as compared with the primary receiver unit 604. As such, the secondary receiver unit 606 may be configured substantially in a smaller compact housing, for example. Alternatively, the secondary receiver unit 606 may be configured with the same or substantially similar functionality as the primary receiver unit 604 and may be configured to be used in conjunction with a docking cradle unit for placement by bedside, for night time monitoring, for example, and/or a bi-directional communication device.

Only one sensor 601, transmitter unit 602, and data processing terminal/infusion section 605 are shown in the integrated CGM and insulin pump system 600 illustrated in FIG. 5. However, the system 600 may include one or more sensors 601, transmitter units 602, and data processing terminal/infusion sections 605. In a multi-component environment, each device is configured to be uniquely identified by each of the other devices in the system so that communication conflict is readily resolved between the various components within the system 600.

In an embodiment, the sensor 601 is physically positioned in or on the body of a user whose analyte (e.g., glucose) level is being monitored. The sensor 601 may be configured to continuously sample the analyte level of the user and convert the sampled analyte level into a corresponding data signal for transmission by the transmitter unit 602. In one embodiment, the transmitter unit 602 is physically coupled to the sensor 601 so that both devices are positioned on the user's body, with at least a portion of the analyte sensor 601 positioned transcutaneously under the skin layer of the user. The transmitter unit 602 performs data processing such as filtering and encoding on data signals, each of which corresponds to a sampled analyte level of the user, for transmission to the primary receiver unit 604 via the communication link 603.

In an embodiment, the system 600 is configured as a one-way RF communication path from the transmitter unit 602 to the primary receiver unit 604. In such embodiment, the transmitter unit 602 transmits the sampled data signals received from the sensor 601 without acknowledgement from the primary receiver unit 604 that the transmitted sampled data signals have been received. For example, the transmitter unit 602 may be configured to transmit the encoded sampled data signals at a fixed rate (e.g., at one minute intervals) after the completion of the initial power on procedure. Likewise, the primary receiver unit 604 may be configured to detect such transmitted encoded sampled data signals at predetermined time intervals. Alternatively, the integrated CGM and insulin pump system 600 may be configured with a bi-directional RF (or otherwise) communication between the transmitter unit 602 and the primary receiver unit 604.

In operation, upon completing a power-on procedure, the primary receiver unit 604 is configured to detect the presence of the transmitter unit 602 within its range based on, for example, the strength of the detected data signals received from the transmitter unit 602 or a predetermined transmitter identification information. Upon successful synchronization with the corresponding transmitter unit 602, the primary receiver unit 604 is configured to begin receiving from the transmitter unit 602 data signals corresponding to the user's analyte level as detected by the sensor 601. More specifically, the primary receiver unit 604 in an embodiment is configured to perform synchronized time hopping with the corresponding synchronized transmitter unit 602 via the communication link 603 to obtain the user's detected analyte level.

Referring again to FIG. 5, the data processing terminal/infusion section 605 may include, as examples, a personal computer, a portable computer such as a laptop or a handheld device (e.g., personal digital assistants (PDAs)), and the like, each of which may be configured for data communication with the receiver via a wired or a wireless connection. The data processing terminal/infusion section 605 includes a processor that includes computer-executable instructions for performing various functions and processing related to, for example, data transmitted and received within the system 600. Additionally, the data processing terminal/infusion section 605 may further be connected to a data network 620 for storing, retrieving, and updating data corresponding to the detected analyte level of the user, for example. Other types of data and information may also be stored, retrieved, and updated.

The data processing terminal/infusion section 605 may include an infusion device such as an insulin infusion pump or the like, which may be configured to administer insulin to a patient 622, and which may be configured to communicate with the receiver unit 604 for receiving, among others, the measured analyte level. Alternatively, the receiver unit 604 may be configured to integrate an infusion device therein so that the receiver unit 604 is configured to administer insulin therapy to patients, for example, for administering and modifying basal profiles, as well as for determining appropriate boluses for administration based on, among others, the detected analyte levels received from the sensor 601 through the transmitter unit 602.

Additionally, the transmitter unit 602, the primary receiver unit 604, and the data processing terminal/infusion section 605 may each be configured for bi-directional wireless communication such that each of the transmitter unit 602, the primary receiver unit 604, and the data processing terminal/infusion section 605 may be configured to communicate (that is, transmit data to and receive data from) with each other via the wireless communication link 603. More specifically, the data processing terminal/infusion section 605 may in an embodiment be configured to receive data directly from the transmitter unit 602 via the communication link 607, where the communication link 607, as described above, may be configured for bi-directional communication.

The data processing terminal/infusion section 605 which may include an insulin pump, may be configured to receive the analyte signals from the sensor 601 through the transmitter unit 602, and thus, incorporate the functions of the receiver unit 604 including data processing for managing the patient's insulin therapy and analyte monitoring. In an embodiment, the communication link 603 may include one or more of an RF communication protocol, an infrared communication protocol, a Bluetooth® enabled communication protocol, an 802.11x wireless communication protocol, or an equivalent wireless communication protocol which would allow secure, wireless communication of several units (for example, per HIPAA requirements) while avoiding potential data collision and interference.

Additional detailed description of a continuous analyte monitoring system and its various components including the functional descriptions of the transmitter are provided in U.S. Pat. No. 6,175,752 issued Jan. 16, 2001 entitled “Analyte Monitoring Device and Methods of Use,” in U.S. application Ser. No. 10/745,878 filed Dec. 26, 2003, now U.S. Pat. No. 7,811,231, entitled “Continuous Glucose Monitoring System and Methods of Use,” and in U.S. application Ser. No. 12/024,101 filed Jan. 31, 2008, now U.S. Pat. No. 8,140,312, entitled “Method and System for Determining Analyte Levels,” each of which is assigned to the Assignee of the present application, and each of which is incorporated herein by reference.

With further reference to FIG. 5, a display 608 is provided as part of the integrated CGM and insulin pump system 600. According to an embodiment, the display 608 may be part of the data processing terminal/infusion section 605. For example, the display 608 may be a monitor of the data processing terminal/infusion section 605, which may be a personal computer or a portable computer. Alternatively, the display 608 may be a separate component coupled to the transmitter unit 602 and/or the data processing terminal/infusion section 605 respectively via communication links 609 and 610. The communication links 609 and 610, similar to the link 603 described above, may incorporate a wireless communication protocol for secure, wireless communication. Or, the communication links 609 and 610 may be directly or indirectly wired.

The display 608 may include a graphical user interface for displaying received and/or processed information to a patient or other user. The received and/or processed information may come from various and multiple sources, such as the sensor 601, the transmitter unit 602, and/or the data processing terminal/infusion section 605. For example, as described above, the transmitter unit 602 may be configured to receive data from the sensor 601, while the primary receiver unit 604 may be configured to receive data from the transmitter unit 602 and may be further configured to transmit data to the data processing terminal/infusion section 605 for evaluating the data received by the primary receiver unit 604. The evaluated data, as processed by the data processing terminal/infusion section 605, may then be displayed on the graphical user interface of the display 608, for example.

The evaluated data may be displayed in various forms and/or representations, such as charts, graphs, and/or tables. The evaluated data may simply be presented as a list or bulleted items on the display 608. According to an embodiment, the evaluated data may include graphs 200, 220, 240, and 260 as described above and as processed by the data processing terminal/infusion section 605 with both data from the sensor 601 and the insulin pump incorporated in the data processing terminal/infusion section 605.

With further reference to FIG. 5, the integrated CGM and insulin pump system 600 includes one or more memory components 611 configured to store various data and/or datasets. The one or more memory components 611 may be part of the data processing terminal/infusion section 605, and/or the one or more memory components 611 may be separate components residing, for example, in an external server or data network 620.

According to an embodiment, the memory component 611 stores data related at least to the following: measurements of a physiological glucose level in a patient (endogenous data); a target glucose level for the patient (exogenous data); and one or more medically relevant data points (exogenous data), such as insulin on board, insulin sensitivity, prior carbohydrate intake, basal rate of insulin, carb ratio, available insulin bolus, profiles of CGM data, and other. The exogenous data of a patient's basal rate, carb ratio, and insulin sensitivity are patient-specific and are related to insulin. These may also be referred to as exogenous patient-specific insulin values.

The measurements of a physiological glucose level in a patient may include two measurements taken at different time points t1 and t2, for example. The measurements may be taken from the sensor 601 at predetermined time points t1 and t2 as established by the patient or another, such as a clinician, or other health care provider. The time points t1 and t2 may be provided to the system 600 through use of the graphical user interface on the display 608. Alternatively, the time points t1 and t2 may be randomly selected by the data processing terminal/infusion section 605 based upon monitored and/or processed criteria, for example. As an example, the physiological glucose level of the patient may be continuously monitored and processed, and the data processing terminal/infusion section 605 may select two or more of the monitored levels.

The target glucose level for the patient, also stored in the memory component 611, may be established by the patient or a clinician or other healthcare professional. The target glucose level may be provided to the system 600 through use of the graphical user interface on the display 608. Alternatively, the target glucose level may be sent to the system 600 from a remote server or data network 620.

The other medically relevant data points stored in the memory component 611 may be data that is monitored and/or otherwise processed by the integrated glucose monitoring and insulin pump system 600. For example, and as described in further detail above with respect to FIGS. 1-5, the data may be exogenous and related to insulin delivery and meal information and may include, but is not limited to, insulin on board, insulin sensitivity, prior carbohydrate intake, carb ratio, basal insulin rate, and available insulin bolus. Such exogenous data, along with the target glucose level may be input to the memory 611, processor 605 and other parts of the system through various means, one of which includes a keyboard that is connected with the memory 611 or the processor 605. Such data may also be received from a remote source through the network 620 which may be in wired or wireless contact with other sources.

The computer-executable instructions of the data processing terminal/infusion section 605 may operate to process data stored in the memory component 611. For example, the instructions may operate to determine a rate of change between the glucose level measurements and an expected glucose level at a future time point t3. According to an embodiment, the time point t3 may be up to thirty minutes after the time point t2, for example. The computer-executable instructions may be further configured to identify whether this expected glucose level is above or below the target glucose level established for the patient. According to an embodiment, the expected glucose level may be a function of the rate of change between the two glucose level measurements as well as the medically relevant data point or points.

The computer-executable instructions may be further configured to provide an alarm if a difference between the expected glucose level and the target glucose level exceeds a preset warning value. The preset warning value may be established by the patient, a clinician, or other health care provider and may be provided to the system 600 through a graphical user interface of the display 608 or through other means as discussed above. The alarm may be in various forms, such as a sound alarm that serves to be audibly delivered to the patient, a visual alarm provided via the display 608 through the graphical user interface, a vibratory alarm, an email or other message delivered to a device of the patient, or a combination thereof.

The data processing terminal/infusion section 605, through the computer-executable instructions, may be further configured to determine and provide a recommended change to one or more of the medically relevant data point or points or factors. Such a recommended change may include, for example, a therapeutic response, such as a particular insulin bolus, intake of a particular level of carbohydrates, and/or a change or changes to exogenous data factors, such as the basal insulin level, the carb ratio, or the insulin sensitivity. The recommended therapeutic response may be displayed on the display 608 for ease in recognition by the patient.

The alarm and/or the recommended change may take the form of, for example, the graphs 200, 220, 240, and 260 (FIGS. 1, 2, 3, and 4). Additionally, the alarm and/or recommended change may be in the form of tables, such as Table 1 and Table 2 provided above. Profiles of CGM data may also be provided for review and selection by the patient, as discussed above. The patient may review the profiles, the comparisons of the profiles that show a persistent pattern and may retune one of more of the exogenous data in accordance with a processor's analysis of those profiles. For example, the patient may lower his or her basal rate to be consistent with the results of the profiles of the basal test by making the change on a keyboard through programming of the processor 605 or by use of a different user interface, such as the graphical user interface provided on the display 608. On the other hand, a patient may select a stored profile similar to the present conditions and command the processor to apply the stored profile's attributes to management of the patient's diabetes presently. Further, the processor may perform the safety checks of any exogenous data changes at this time to be sure that requested data changes are not inconsistent with the safety rules.

With reference to FIG. 6, a flow chart illustrates a method for managing projections and alarms related to glucose levels.

At 701, a rate of change between at least two glucose level measurements of a patient taken at different time points t1 and t2 is determined.

At 702, an expected glucose level at a future time point t3 is determined, which may be a function of the rate of change between the at least two glucose level measurements and a function of at least one other medically relevant data point selected from exogenous data, such as the group of insulin on board, insulin sensitivity, prior carbohydrate intake, basal insulin, and available insulin bolus, for example. According to an embodiment, the time point t3 may be up to thirty minutes after the time point t2. Other time intervals may be used, however, and the time point t3 may be any amount of time following the time point t1 and the time point t2.

At 703, a determination is made as to whether the expected glucose level at the time point t3, as determined at 702, is above or below a target glucose level established for the patient. If the expected glucose level is equal to the target glucose level or within a safe range, the process may continue back to 701 to determine a new rate of change between at least two glucose level measurements of the patient.

If it is determined at 703 that the expected glucose level is above or below the target glucose level or outside a safe range, a determination is made as to whether the difference between the expected glucose level and the target glucose level exceeds a preset warning value at 704, as may be established depending upon the patient and other factors. If the difference does not exceed the preset warning value, the process may continue back to 701 to determine a new rate of change between at least two glucose level measurements of the patient.

However, if the difference exceeds the preset warning value, an alarm is provided at 705 to warn the patient and/or clinician of the expected glucose level. The alarm may be one or more of a visual alarm, an audible alarm, a vibratory alarm, and a message sent to the patient and/or clinician. If the alarm is a visual alarm, the alarm may be provided on the graphical user interface of the display 608, for example.

At 706, a recommended change to one or more of the medically relevant data points is determined. The determination of the recommended change may include, for example, determining a therapeutic response, which may, include a particular insulin bolus, intake of a particular level of carbohydrates, temporary change to a basal insulin level, change carb ratio, or change insulin sensitivity. Other therapeutic or tuning responses may also be established and used.

At 707, the recommended change is displayed on a visual display, which may include a graphical user interface. For example, the recommended change may be provided on the graphical user interface.

An automatic response to an alarm may also be provided. For example, if an alarm is provided that is indicative of a very low glucose level, provision of an insulin bolus may be locked out at insulin pump system 600; e.g., by operation of a switch triggered in response to the alarm, preferably subject to manual override to ensure the availability of an insulin bolus if medically necessary.

According to embodiments of the present invention, methods are provided to increase reliability of projected alarms and reduce false alarms, which is highly desirable for improving the management of the user's medical condition. For example, in one embodiment a hyperglycemic projected alarm is provided in which false alarms are reduced. The method is provided as follows:

- a) for every measurement of physiological glucose level in a patient performed by the CGM, the projected glucose is calculated based on the latest glucose reading, latest glucose trend estimate and projection time, which is generally a predetermined amount of time (e.g., 20 minutes), for example: projected glucose=current glucose+trend*projected time;
- b) if the projected glucose exceeds a predetermined hyperglycemic threshold (e.g., 300 mg/dL), then proceed to (c); and
- c) if an insulin bolus greater than a predetermined amount (e.g., 1 Unit) has not been delivered within a predetermined time (e.g., 20 minutes), then assert the projected alarm; otherwise, do not assert the projected alarm.

In another embodiment, a hypoglycemic projected alarm is provided in which reliability is increased and false alarms are reduced. For example, the method is provided as follows:

- a) for every measurement of physiological glucose level in a patient performed by the CGM, the projected glucose is calculated based on the latest glucose reading, latest glucose trend estimate and projection time, which is generally a predetermined amount of time (e.g., 20 minutes), for example: projected glucose=current glucose+trend*projected time;
- b) if the projected glucose falls below a predetermined hypoglycemic threshold (e.g., 60 mg/dL), then proceed to (c); and
- c) if a meal event greater than a predetermined amount (e.g., 1 Carb) has not been delivered within a predetermined time (e.g., 20 minutes), then assert the projected alarm; otherwise do not assert the projected alarm.

In related embodiments, hyperglycemic and hypoglycemic alarms similar to those described above are contemplated in which (a) and (b) compare the current glucose level in a patient to a predetermined threshold. In other related embodiments, (c) of the above hyperglycemic and hypoglycemic alarms may be modified such that even if the event (e.g., meal or insulin bolus event) occurs within the predetermined time, if the projected glucose level exceeds a second, more extreme threshold, the alarm is asserted. One of skill in the art would understand that all predetermined parameters (e.g., predetermined amounts and times) may be selectable by the patient or user:

Varying degrees of complexity are contemplated, for the above projected hyperglycemic and hypoglycemic alarms including elaborate model-based projected alarm as described further below. Accordingly, in yet another embodiment of the present invention, a model-based projected alarm is provided in which reliability is increased and false alarms are reduced. The method is provided as follows:

- a) for every measurement of physiological glucose level in a patient performed by the CGM, the projected glucose is calculated based on one or more glucose readings; projection time (predetermined, e.g., 20 minutes); an exogenous parameter or parameters, for example one or more insulin/meal/exercise information parameters (e.g., bolus or meal amount and relative time of occurrence); and/or model parameters such as insulin sensitivity, insulin action time, carbohydrate ratio, carb uptake time, basal rate, or the like; and
- b) if the projected glucose exceeds a predetermined hyperglycemic alarm threshold (e.g., 300 mg/dL), or falls below the hypoglycemic alarm threshold (e.g., 60 mg/dL), then the appropriate projected alarm is asserted.

In addition to potentially reducing the incidence of false alarms and thereby making projected alarms more reliable, the projected alarm may actually become more responsive with the additional inputs of meals and insulin; that is, the alarm may occur sooner than if these additional inputs were absent. For example, a patient's glucose may be at 100 mg/dL and trending downward, but not fast enough to alone trip the projected hypoglycemic alarm at this point in time. However, if a bolus occurs and is included in the projected alarm computation, the model may predict a more accurate projected glucose that will trip the projected alarm at this point in time. As discussed above, one of skill in the art would understand that all predetermined parameters described may be defined by the patient or user.

Turning now to FIG. 7, there is shown a flow chart of the process of forming and analyzing profiles of CGM data for “tuning” patient-specific insulin data values, such as the patient's basal delivery rate of insulin, the patient's insulin sensitivity, and the patient's carb ratio, all of which are used by the patient in the delivery of carbohydrates and insulin to control the patient's glucose levels. These tuners are discussed above.

Referring in detail to FIG. 7, the first step is one in which the recording of CGM data is started during a test or other selected time period 720, such as a basal test, skip-meal test, meal-test, or other. The means of starting the recording of the data may be a manual start signal from the patient or an automatic start control as discussed above. At the end of the test period or when sufficient CGM data has been collected, the recording feature is ended 722 either manually by the patient, such as by entering a stop signal at a keyboard, or by an automatic end recording feature, as discussed above. In certain cases, attributes are added to the recorded data file 724. As discussed above, such attributes may be varied but in one example, they may take the form of tagging the recorded CGM data as being “breakfast” data, or “high fat meal” data, or “post-prandial” data or others. Such data tagging can be highly useful in locating profiles of CGM data of similar past events that are stored in the memory 611 (FIG. 5) 726. For example when a patient intends to consume a meal similar to one recently consumed, and in which the patient's glucose was successfully controlled to the desired safe range, the patient may desire to locate the stored CGM profile for that previous meal. That stored CGM profile would include not only recorded glucose data for that meal, but would also include patient-specific insulin data values, such as the patient's basal rate, the patient's insulin sensitivity, and the patient's carb ratio. In accordance with a feature on the invention, the previously-stored similar profiles may be made available to the patient from the memory 611 on the display 608 or in printing, so that the patient may study them and select one, if desired. The patient may choose to assign those patient specific insulin values to determining the pre-meal insulin bolus for this new meal by selecting one of these stored profiles by a keyboard stroke, or by a visual touch panel stroke, or by other user interface means. Other exogenous patient data is also considered, such as insulin-on-board, in calculating the pre-meal bolus.

Stored profiles of previous events of this type are retrieved by the processor 728 from the memory 611 (FIG. 5). For example, the patient may retrieve all stored breakfast profiles. The processor then compares the stored profiles to one another to attempt to identify any persistent pattern 730. Such a pattern, as an example, may be seen in FIG. 2 in dashed line 232. Should the processor identify that in all stored profiles, or in a certain number of them, the patient's glucose level follows line 232 of FIG. 2, the processor may indicate that a persistent pattern exists in which the patient's glucose falls too low after consuming a meal. In this case, the processor would indicate in box 732 that a persistent pattern has been identified and would proceed to box 734 in which a change in the pre-meal insulin bolus is recommended so that a glucose level line more resembling 228 could be obtained. Such finding of a persistent pattern and recommended change in pre-meal insulin bolus may be presented to the patient by the display 608, it may also be stored in memory 611, it may be communicated to the patient's physician over a network 620 for storage and review by the physician or other health care provider, and/or may be printed for the patient.

The patient then has the option in this embodiment to accept the recommended exogenous data value change 736. If the change is accepted at box 736, such as a basal rate change, that change in the patient-specific insulin basal rate delivery will be implemented and the process begins again at box 720. However, if the comparison of multiple stored profiles 730 did not find a persistent pattern 738, no changes are recommended to the patient's exogenous insulin data and the process begins again at box 720.

While the disclosure has been particularly shown and described with reference to several embodiments thereof with particular details, it will be apparent to one of ordinary skill in the art that various changes may be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined in the following claims and their equivalents.

Claims

1. An integrated glucose management system for treating diabetes of a patient, the system comprising: a controller comprising: a memory configured to store glucose measurement data wirelessly received from a continuous glucose monitoring sensor, and to store exogenous data including attributes tagged to the stored glucose measurement data; anda processor configured to execute computer-executable instructions to: automatically enable a profile recording feature to generate a first profile of a first profile type, the automatic enablement based on a first detected system-driven event;store glucose measurement data into the memory during a first defined time period to generate the first profile;automatically enable the profile recording feature to generate a plurality of subsequent profiles of subsequent profile types, the automatic enablement based on a plurality of subsequent detected system-driven events;store glucose measurement data into memory during a plurality of subsequent defined time periods to generate each of the plurality of subsequent profiles, wherein the first profile type and the subsequent profile types are selected from the group consisting of a skip-meal profile, a meal test profile, a correction bolus profile, a basal test profile, and an insulin action profile;tag one or more of the first profile and the plurality of subsequent profiles with an exogenous attribute; determine whether a persistent pattern of measured glucose levels exists among a minimum number of the first profile and the plurality of subsequent profiles of a same profile type, wherein the persistent pattern exists if the minimum number of the first profile and the plurality of subsequent profiles of the same profile type includes respective measured glucose levels outside of a glucose level target associated with the profile type; andoutput to a display a recommended change to medication data if the persistent pattern exists for a user to manage glucose levels within the glucose level target.
2. The integrated glucose management system of claim 1, wherein the medication data comprises one or more of a basal rate, a carb ratio, or an insulin sensitivity.
3. The integrated glucose management system of claim 1, wherein the processor comprises a computer-executable instruction to determine whether the persistent pattern exists among the minimum number of the first profile and the plurality of subsequent profiles of the same profile type within a selected time period.
4. The integrated glucose management system of claim 1, wherein the processor comprises a computer-executable instruction to determine that the recommended change to medication data does not exceed a predetermined amount, and wherein the medication data comprises one or more of a basal rate, a carb ratio, or an insulin sensitivity.
5. The integrated glucose management system of claim 1, wherein the exogenous attribute tag includes at least one of meal data, breakfast data, high-fat meal data, or post-prandial data.
6. A method of treating diabetes, comprising: automatically enabling a profile recording feature to generate a first profile of a first profile type, the automatic enablement based on a first detected system-driven event;storing glucose measurement data received wirelessly from a continuous glucose monitoring sensor during a first defined time period to generate the first profile;automatically enabling the profile recording feature to generate a plurality of subsequent profiles of subsequent profile types, the automatic enablement based on plurality of subsequent detected system-driven events;storing glucose measurement data received wirelessly from the continuous glucose monitoring sensor during a plurality of subsequent defined time periods to generate the plurality of subsequent profiles, wherein the first profile type and the subsequent profile types are selected from the group consisting of a skip-meal profile, a meal test profile, a correction bolus profile, a basal test profile, and an insulin action profile;tagging one or more of the first profile and the plurality of subsequent profiles with an exogenous attribute;determining whether a persistent pattern of measured glucose levels exists among a minimum number of the first profile and the plurality of subsequent profiles of a same profile type, wherein the persistent pattern exists if the minimum number of the first profile and the plurality of subsequent profiles of the same profile type includes respective measured glucose levels outside of a glucose level target associated with the profile type; andoutputting to a display a recommended change to medication data if the persistent pattern exists for a user to manage glucose levels within the glucose level target.
7. The method of claim 6, wherein the medication data comprises one or more of a basal rate, a carb ratio, or an insulin sensitivity.
8. The method of claim 6, wherein the minimum number of the first profile and the plurality of subsequent profiles of the same profile type are each within a selected time period for determining whether the persistent pattern exists.
9. The method of claim 6, further including determining that the recommended change to medication data does not exceed a predetermined amount, and wherein the medication data comprises one or more of a basal rate, a carb ratio, or an insulin sensitivity.
10. The method of claim 6, wherein the exogenous attribute tag includes at least one of meal data, breakfast data, high-fat meal data, or post-prandial data.
11. The integrated glucose management system of claim 1, wherein the processor comprises a computer-executable instructions to modify the medication data.
12. The integrated glucose management system of claim 1, further comprising a drug delivery device, wherein the drug delivery device is configured to deliver insulin based on the recommended change to the medication data.
13. The method of claim 6, further comprising modifying the medication data.
14. The method of claim 6, further comprising delivering insulin based on the recommended change to the medication data using a drug delivery device.
15. The integrated glucose management system of claim 1, wherein the processor comprises a computer-executable instruction to prioritize a recommended increase in carbohydrate intake lower than a recommended modification to medication delivery.
16. The method of claim 6, further comprising prioritizing a recommended increase in carbohydrate intake lower than a recommended modification to medication delivery.
17. The integrated glucose management system of claim 1, wherein the controller is in wireless communication with drug delivery device, and wherein the first detected system-driven event and the plurality of subsequent detected system-driven events are received from the drug delivery device.
18. An integrated glucose management system for treating diabetes of a patient, the system comprising: a controller comprising: a memory configured to store glucose measurement data wirelessly received from a continuous glucose monitoring sensor, and to store exogenous data including attributes tagged to the stored glucose measurement data; anda processor configured to execute computer-executable instructions to: enable a profile recording feature to generate a first profile of a first profile type;store glucose measurement data into the memory during a first time period to generate the first profile;automatically end the profile recording feature after the first time period based on a first detected system-driven event;enable the profile recording feature to generate a plurality of subsequent profiles of subsequent profile types;store glucose measurement data into memory during a plurality of subsequent time periods to generate each of the plurality of subsequent profiles;automatically end the profile recording feature after the plurality of subsequent time periods based on a plurality of subsequent detected system-driven events, wherein the first profile type and the subsequent profile types are selected from the group consisting of a skip-meal profile, a meal test profile, a correction bolus profile, a basal test profile, and an insulin action profile;tag one or more of the first profile and the plurality of subsequent profiles with an exogenous attribute; determine whether a persistent pattern of measured glucose levels exists among a minimum number of the first profile and the plurality of subsequent profiles of a same profile type, wherein the persistent pattern exists if the minimum number of the first profile and the plurality of subsequent profiles of the same profile type includes respective measured glucose levels outside of a glucose level target associated with the profile type; andoutput to a display a recommended change to medication data if the persistent pattern exists for a user to manage glucose levels within the glucose level target.
19. The integrated glucose management system of claim 18, wherein the first detected system-driven event and the plurality of subsequent detected system-driven events are received from continuous glucose monitoring sensor.
20. The integrated glucose management system of claim 18, wherein the controller is in wireless communication with drug delivery device, and wherein the first detected system-driven event and the plurality of subsequent detected system-driven events are received from the drug delivery device.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 12/842,838 filed Jul. 23, 2010, now U.S. Pat. No. 8,798,934, which claims the benefit of U.S. Application No. 61/228,101, filed Jul. 23, 2009, the disclosures of each of which are incorporated herein by reference in their entirety.

US Referenced Citations (1284)

Number	Name	Date	Kind
2915579	Mendelsohn	Dec 1959	A
3374337	Burley	Mar 1968	A
3510747	Petrides	May 1970	A
3606592	Madurski et al.	Sep 1971	A
3750687	Williams	Aug 1973	A
3843455	Bier	Oct 1974	A
3923060	Elinwood	Dec 1975	A
3930493	Williamson	Jan 1976	A
3994799	Yao et al.	Nov 1976	A
4018547	Rogen	Apr 1977	A
4048551	Bosik	Sep 1977	A
4121282	Ohsawa	Oct 1978	A
4146029	Elinwood	Mar 1979	A
4193397	Tucker et al.	Mar 1980	A
4268173	Barnard et al.	May 1981	A
4288793	Lotscher	Sep 1981	A
4362052	Heath et al.	Dec 1982	A
4401122	Clark, Jr.	Aug 1983	A
4439197	Honda et al.	Mar 1984	A
4441968	Emmer et al.	Apr 1984	A
4447224	DeCant, Jr. et al.	May 1984	A
4458686	Clark, Jr.	Jul 1984	A
4464170	Clemens et al.	Aug 1984	A
4467811	Clark, Jr.	Aug 1984	A
4472113	Rogen	Sep 1984	A
4494950	Fischell	Jan 1985	A
4512348	Uchigaki et al.	Apr 1985	A
4524343	Morgan et al.	Jun 1985	A
4529401	Leslie et al.	Jul 1985	A
4531235	Brusen	Jul 1985	A
4562751	Nason et al.	Jan 1986	A
4563249	Hale	Jan 1986	A
4570492	Walsh	Feb 1986	A
4573994	Fischell et al.	Mar 1986	A
4633878	Bombardieri	Jan 1987	A
4678408	Nason et al.	Jul 1987	A
4685903	Cable et al.	Aug 1987	A
4686624	Blum et al.	Aug 1987	A
4736748	Nakamura et al.	Apr 1988	A
4755173	Konopka et al.	Jul 1988	A
4811564	Palmer	Mar 1989	A
4847785	Stephens	Jul 1989	A
4850959	Findl	Jul 1989	A
4851827	Nicholas	Jul 1989	A
4866396	Tamura	Sep 1989	A
4890621	Hakky	Jan 1990	A
4953552	DeMarzo	Sep 1990	A
4976590	Baldwin	Dec 1990	A
4979509	Hakky	Dec 1990	A
4984581	Stice	Jan 1991	A
5004532	Hale et al.	Apr 1991	A
5012667	Kruse	May 1991	A
5019974	Beckers	May 1991	A
5036861	Sembrowich et al.	Aug 1991	A
5051688	Murase et al.	Sep 1991	A
5051880	Harm et al.	Sep 1991	A
5061914	Bush et al.	Oct 1991	A
5068536	Rosenthal	Nov 1991	A
5079920	Whitehead et al.	Jan 1992	A
5081421	Miller et al.	Jan 1992	A
5101814	Palti	Apr 1992	A
5124661	Zelin et al.	Jun 1992	A
5135004	Adams et al.	Aug 1992	A
5139023	Stanley et al.	Aug 1992	A
5155695	Stein	Oct 1992	A
5190041	Palti	Mar 1993	A
5202261	Musho et al.	Apr 1993	A
5205819	Ross et al.	Apr 1993	A
5207666	Idriss et al.	May 1993	A
5210778	Massart	May 1993	A
5211371	Coffee	May 1993	A
5211626	Frank et al.	May 1993	A
5223822	Stommes et al.	Jun 1993	A
5228449	Christ et al.	Jul 1993	A
5231988	Wernicke et al.	Aug 1993	A
5251126	Kahn et al.	Oct 1993	A
5262305	Heller et al.	Nov 1993	A
5267026	Kawahara et al.	Nov 1993	A
5278997	Martin	Jan 1994	A
5284423	Holdsworth et al.	Feb 1994	A
5291614	Baker et al.	Mar 1994	A
5291887	Stanley et al.	Mar 1994	A
5324599	Oyama et al.	Jun 1994	A
5325280	Tortola et al.	Jun 1994	A
5330634	Wong et al.	Jul 1994	A
5349852	Kamen et al.	Sep 1994	A
5356786	Heller et al.	Oct 1994	A
5366292	Voss	Nov 1994	A
5368028	Palti	Nov 1994	A
5371687	Holmes, II et al.	Dec 1994	A
5372133	Hogen Esch	Dec 1994	A
5376070	Purvis et al.	Dec 1994	A
5382331	Banks	Jan 1995	A
5384547	Lynk et al.	Jan 1995	A
5390671	Lord et al.	Feb 1995	A
5391250	Cheney, II et al.	Feb 1995	A
5398681	Kuperschmidt	Mar 1995	A
5404585	Vimpari et al.	Apr 1995	A
5406301	Ravid	Apr 1995	A
5410326	Goldstein	Apr 1995	A
5429602	Hauser	Jul 1995	A
5445611	Eppstein et al.	Aug 1995	A
5448992	Kuperschmidt	Sep 1995	A
5458140	Eppstein et al.	Oct 1995	A
5469025	Kanemori et al.	Nov 1995	A
5479486	Saji	Dec 1995	A
5494562	Maley et al.	Feb 1996	A
5497772	Schulman et al.	Mar 1996	A
5505713	Van Antwerp	Apr 1996	A
5505828	Wong et al.	Apr 1996	A
5507288	Bocker et al.	Apr 1996	A
5517434	Hanson et al.	May 1996	A
5526844	Kamen et al.	Jun 1996	A
5533389	Kamen et al.	Jul 1996	A
5543678	Hoiberg	Aug 1996	A
5552997	Massart	Sep 1996	A
5559528	Ravid	Sep 1996	A
5568400	Stark et al.	Oct 1996	A
5568806	Cheney, II et al.	Oct 1996	A
5575770	Melsky et al.	Nov 1996	A
5576535	Oosterwijk et al.	Nov 1996	A
5586553	Halili et al.	Dec 1996	A
5593852	Heller et al.	Jan 1997	A
5594906	Holmes, II et al.	Jan 1997	A
5601435	Quy	Feb 1997	A
5604404	Sahara	Feb 1997	A
5609575	Larson et al.	Mar 1997	A
5615671	Schoonen et al.	Apr 1997	A
5622413	Kim et al.	Apr 1997	A
5622482	Lee	Apr 1997	A
5628324	Sarbach	May 1997	A
5640954	Pfeiffer et al.	Jun 1997	A
5645709	Birch et al.	Jul 1997	A
5660163	Schulman et al.	Aug 1997	A
5661643	Blakely et al.	Aug 1997	A
5662461	Ono	Sep 1997	A
5671301	Kuperschmidt	Sep 1997	A
5685844	Marttila	Nov 1997	A
5695949	Galen et al.	Dec 1997	A
5703928	Galloway et al.	Dec 1997	A
5707502	McCaffrey et al.	Jan 1998	A
5708247	McAleer et al.	Jan 1998	A
5711861	Ward et al.	Jan 1998	A
5711868	Maley et al.	Jan 1998	A
5722397	Eppstein	Mar 1998	A
5726646	Bane et al.	Mar 1998	A
5741211	Renirie et al.	Apr 1998	A
5748103	Flach et al.	May 1998	A
5748872	Norman	May 1998	A
5759510	Pillai	Jun 1998	A
5771890	Tamada	Jun 1998	A
5774254	Berlin	Jun 1998	A
5786439	Van Antwerp et al.	Jul 1998	A
5790297	Berlin	Aug 1998	A
5791344	Schulman et al.	Aug 1998	A
5814599	Mitragotri et al.	Sep 1998	A
5815303	Berlin	Sep 1998	A
5822715	Worthington et al.	Oct 1998	A
5825488	Kohl et al.	Oct 1998	A
5833603	Kovacs et al.	Nov 1998	A
5842189	Keeler et al.	Nov 1998	A
5848990	Cirelli et al.	Dec 1998	A
5851197	Marano et al.	Dec 1998	A
5873026	Reames	Feb 1999	A
5875417	Golden	Feb 1999	A
5885211	Eppstein et al.	Mar 1999	A
5899855	Brown	May 1999	A
5913833	Elstrom et al.	Jun 1999	A
5918603	Brown	Jul 1999	A
5923512	Brownlow et al.	Jul 1999	A
5947921	Johnson et al.	Sep 1999	A
5948512	Kubota et al.	Sep 1999	A
5951582	Thorne et al.	Sep 1999	A
5951836	McAleer et al.	Sep 1999	A
5954643	Van Antwerp et al.	Sep 1999	A
5965380	Heller et al.	Oct 1999	A
5968011	Larsen et al.	Oct 1999	A
5971922	Arita et al.	Oct 1999	A
5980708	Champagne et al.	Nov 1999	A
6001067	Shults et al.	Dec 1999	A
6002961	Mitragotri et al.	Dec 1999	A
6011486	Casey	Jan 2000	A
6014577	Henning et al.	Jan 2000	A
6017328	Fischell et al.	Jan 2000	A
6018678	Mitragotri et al.	Jan 2000	A
6023629	Tamada	Feb 2000	A
6024539	Blomquist et al.	Feb 2000	A
6026320	Carlson et al.	Feb 2000	A
6027459	Shain et al.	Feb 2000	A
6027496	Loomis et al.	Feb 2000	A
6027692	Galen et al.	Feb 2000	A
6028413	Brockmann	Feb 2000	A
6032059	Henning et al.	Feb 2000	A
6041253	Kost et al.	Mar 2000	A
6041665	Hussain	Mar 2000	A
6052565	Ishikura et al.	Apr 2000	A
6059546	Brenan et al.	May 2000	A
6063039	Cunningham et al.	May 2000	A
6064368	Kang	May 2000	A
6066243	Anderson et al.	May 2000	A
6067017	Stewart et al.	May 2000	A
6067463	Jeng et al.	May 2000	A
6071249	Cunningham et al.	Jun 2000	A
6071251	Cunningham et al.	Jun 2000	A
6073031	Helstab et al.	Jun 2000	A
6077660	Wong et al.	Jun 2000	A
6081104	Kern	Jun 2000	A
6083710	Heller et al.	Jul 2000	A
6085871	Karamata	Jul 2000	A
6086575	Mejslov	Jul 2000	A
6091975	Daddona et al.	Jul 2000	A
6093156	Cunningham et al.	Jul 2000	A
6093172	Funderburk et al.	Jul 2000	A
6096364	Bok et al.	Aug 2000	A
6121009	Heller et al.	Sep 2000	A
6129823	Hughes et al.	Oct 2000	A
6132371	Dempsey et al.	Oct 2000	A
6141573	Kurnik et al.	Oct 2000	A
6142939	Eppstein et al.	Nov 2000	A
6143164	Heller et al.	Nov 2000	A
6144303	Federman	Nov 2000	A
6144869	Berner et al.	Nov 2000	A
6144922	Douglas et al.	Nov 2000	A
6147342	Kucher	Nov 2000	A
6154855	Norman	Nov 2000	A
6155992	Henning et al.	Dec 2000	A
6157442	Raskas	Dec 2000	A
6160449	Klomsdorf et al.	Dec 2000	A
6162202	Sicurelli et al.	Dec 2000	A
6162611	Heller et al.	Dec 2000	A
6164284	Schulman et al.	Dec 2000	A
6173160	Liimatainen	Jan 2001	B1
6175752	Say et al.	Jan 2001	B1
6180416	Kurnik et al.	Jan 2001	B1
6185452	Schulman et al.	Feb 2001	B1
6200265	Walsh et al.	Mar 2001	B1
6201980	Darrow et al.	Mar 2001	B1
6206841	Cunningham et al.	Mar 2001	B1
6208894	Schulman et al.	Mar 2001	B1
6212416	Ward et al.	Apr 2001	B1
6215206	Chitayat	Apr 2001	B1
6222514	DeLuca	Apr 2001	B1
6228100	Schraga	May 2001	B1
6232370	Kubota et al.	May 2001	B1
6233471	Berner et al.	May 2001	B1
6233539	Brown	May 2001	B1
6242961	Liu et al.	Jun 2001	B1
6245060	Loomis et al.	Jun 2001	B1
6248067	Causey, III et al.	Jun 2001	B1
6262708	Chu	Jul 2001	B1
6270455	Brown	Aug 2001	B1
6272364	Kurnik	Aug 2001	B1
6278425	DeLuca	Aug 2001	B1
6280587	Matsumoto	Aug 2001	B1
6283926	Cunningham et al.	Sep 2001	B1
6284478	Heller et al.	Sep 2001	B1
6288653	Shih	Sep 2001	B1
6293925	Safabash et al.	Sep 2001	B1
6295506	Heinonen et al.	Sep 2001	B1
6298254	Tamada	Oct 2001	B2
6298255	Cordero et al.	Oct 2001	B1
6299347	Pompei	Oct 2001	B1
6299578	Kurnik et al.	Oct 2001	B1
6301499	Carlson et al.	Oct 2001	B1
6306104	Cunningham et al.	Oct 2001	B1
6309351	Kurnik et al.	Oct 2001	B1
6309884	Cooper et al.	Oct 2001	B1
6312888	Wong et al.	Nov 2001	B1
6314317	Willis	Nov 2001	B1
6315721	Schulman et al.	Nov 2001	B2
6326160	Dunn et al.	Dec 2001	B1
6329161	Heller et al.	Dec 2001	B1
6341232	Conn et al.	Jan 2002	B1
6356776	Berner et al.	Mar 2002	B1
6359270	Bridson	Mar 2002	B1
6360888	McIvor et al.	Mar 2002	B1
6366793	Bell et al.	Apr 2002	B1
6366794	Moussy et al.	Apr 2002	B1
6368141	Van Antwerp et al.	Apr 2002	B1
6368274	Van Antwerp et al.	Apr 2002	B1
6372371	Iarochenko et al.	Apr 2002	B1
6375344	Hanson et al.	Apr 2002	B1
6375638	Nason et al.	Apr 2002	B2
6377828	Chaiken et al.	Apr 2002	B1
6377894	Deweese et al.	Apr 2002	B1
6379301	Worthington et al.	Apr 2002	B1
6381496	Meadows et al.	Apr 2002	B1
6387048	Schulman et al.	May 2002	B1
6393318	Conn et al.	May 2002	B1
6403944	MacKenzie et al.	Jun 2002	B1
6405066	Essenpreis et al.	Jun 2002	B1
6408402	Norman	Jun 2002	B1
6417074	Kopley et al.	Jul 2002	B2
6419642	Marchitto et al.	Jul 2002	B1
6424847	Mastrototaro et al.	Jul 2002	B1
6425829	Julien	Jul 2002	B1
6427088	Bowman, IV et al.	Jul 2002	B1
6432585	Kawakami et al.	Aug 2002	B1
6437379	Kopley et al.	Aug 2002	B2
6438385	Heinonen et al.	Aug 2002	B1
6438414	Conn et al.	Aug 2002	B1
6440068	Brown et al.	Aug 2002	B1
6442413	Silver	Aug 2002	B1
6461329	Van Antwerp et al.	Oct 2002	B1
6462162	Van Antwerp et al.	Oct 2002	B2
6464848	Matsumoto	Oct 2002	B1
6466807	Dobson et al.	Oct 2002	B1
6466810	Ward et al.	Oct 2002	B1
6468222	Mault et al.	Oct 2002	B1
6471689	Joseph et al.	Oct 2002	B1
6471980	Sirhan et al.	Oct 2002	B2
6472991	Schulman et al.	Oct 2002	B1
6475196	Vachon	Nov 2002	B1
6478736	Mault	Nov 2002	B1
6480730	Darrow et al.	Nov 2002	B2
6482158	Mault	Nov 2002	B2
6484045	Holker et al.	Nov 2002	B1
6484046	Say et al.	Nov 2002	B1
6485138	Kubota et al.	Nov 2002	B1
6485461	Mason et al.	Nov 2002	B1
6492180	Brown et al.	Dec 2002	B2
6493069	Nagashimada et al.	Dec 2002	B1
6498043	Schulman et al.	Dec 2002	B1
6506168	Fathallah et al.	Jan 2003	B1
6513532	Mault et al.	Feb 2003	B2
6514460	Fendrock	Feb 2003	B1
6514689	Han et al.	Feb 2003	B2
6514718	Heller et al.	Feb 2003	B2
6522530	Bang	Feb 2003	B2
6525330	Paolini et al.	Feb 2003	B2
6526298	Khalil et al.	Feb 2003	B1
6529772	Carlson et al.	Mar 2003	B2
6530915	Eppstein et al.	Mar 2003	B1
6535753	Raskas	Mar 2003	B1
6537243	Henning et al.	Mar 2003	B1
6540675	Aceti et al.	Apr 2003	B2
6540891	Stewart et al.	Apr 2003	B1
6543224	Barooah	Apr 2003	B1
6544212	Galley et al.	Apr 2003	B2
6546268	Ishikawa et al.	Apr 2003	B1
6546269	Kurnik	Apr 2003	B1
6549796	Sohrab	Apr 2003	B2
6551276	Mann et al.	Apr 2003	B1
6554798	Mann et al.	Apr 2003	B1
6558320	Causey, III et al.	May 2003	B1
6558321	Burd et al.	May 2003	B1
6558351	Steil et al.	May 2003	B1
6560471	Heller et al.	May 2003	B1
6561978	Conn et al.	May 2003	B1
6562001	Lebel et al.	May 2003	B2
6564105	Starkweather et al.	May 2003	B2
6564807	Schulman et al.	May 2003	B1
6565509	Say et al.	May 2003	B1
6565738	Henning et al.	May 2003	B1
6569157	Shain et al.	May 2003	B1
6571128	Lebel et al.	May 2003	B2
6571200	Mault	May 2003	B1
6572545	Knobbe et al.	Jun 2003	B2
6576117	Iketaki et al.	Jun 2003	B1
6577899	Lebel et al.	Jun 2003	B2
6579498	Eglise	Jun 2003	B1
6579690	Bonnacaze et al.	Jun 2003	B1
6582393	Sage, Jr.	Jun 2003	B2
6585644	Lebel et al.	Jul 2003	B2
6586971	Naffziger et al.	Jul 2003	B1
6587705	Kim et al.	Jul 2003	B1
6589229	Connelly et al.	Jul 2003	B1
6594514	Berner et al.	Jul 2003	B2
6595919	Berner et al.	Jul 2003	B2
6596016	Vreman et al.	Jul 2003	B1
6600997	Deweese et al.	Jul 2003	B2
6602469	Maus et al.	Aug 2003	B1
6607509	Bobroff et al.	Aug 2003	B2
6610012	Mault	Aug 2003	B2
6612306	Mault	Sep 2003	B1
6615061	Khalil et al.	Sep 2003	B1
6615074	Mickle et al.	Sep 2003	B2
6618603	Varalli et al.	Sep 2003	B2
6620106	Mault	Sep 2003	B2
6623501	Heller et al.	Sep 2003	B2
6629934	Mault et al.	Oct 2003	B2
6633095	Swope et al.	Oct 2003	B1
6633772	Ford et al.	Oct 2003	B2
6635014	Starkweather et al.	Oct 2003	B2
6641533	Causey, III et al.	Nov 2003	B2
6645142	Braig et al.	Nov 2003	B2
6648821	Lebel et al.	Nov 2003	B2
6650064	Guthrie et al.	Nov 2003	B2
6653091	Dunn et al.	Nov 2003	B1
6656114	Poulson et al.	Dec 2003	B1
6656158	Mahoney et al.	Dec 2003	B2
6656159	Flaherty	Dec 2003	B2
6658396	Tang et al.	Dec 2003	B1
6659948	Lebel et al.	Dec 2003	B2
6668196	Villegas et al.	Dec 2003	B1
6669663	Thompson	Dec 2003	B1
6669669	Flaherty et al.	Dec 2003	B2
6670806	Wendt et al.	Dec 2003	B2
6675030	Ciuczak et al.	Jan 2004	B2
6676816	Mao et al.	Jan 2004	B2
6679841	Bojan et al.	Jan 2004	B2
6687522	Tamada	Feb 2004	B2
6687546	Lebel et al.	Feb 2004	B2
6692457	Flaherty	Feb 2004	B2
6694191	Starkweather et al.	Feb 2004	B2
6695885	Schulman et al.	Feb 2004	B2
6699218	Flaherty et al.	Mar 2004	B2
6702857	Brauker et al.	Mar 2004	B2
6723072	Flaherty et al.	Apr 2004	B2
6728560	Kollias et al.	Apr 2004	B2
6730200	Stewart et al.	May 2004	B1
6731976	Penn et al.	May 2004	B2
6733446	Lebel et al.	May 2004	B2
6736777	Kim et al.	May 2004	B2
6736797	Larsen et al.	May 2004	B1
6738654	Sohrab	May 2004	B2
6740059	Flaherty	May 2004	B2
6740075	Lebel et al.	May 2004	B2
6740518	Duong et al.	May 2004	B1
6741877	Shults et al.	May 2004	B1
6743635	Neel et al.	Jun 2004	B2
6749587	Flaherty	Jun 2004	B2
6752787	Causey, III et al.	Jun 2004	B1
6758810	Lebel et al.	Jul 2004	B2
6764581	Forrow et al.	Jul 2004	B1
6768425	Flaherty et al.	Jul 2004	B2
6770030	Schaupp et al.	Aug 2004	B1
6770729	Van Antwerp	Aug 2004	B2
6773563	Matsumoto	Aug 2004	B2
6779984	Lilie et al.	Aug 2004	B2
6789195	Prihoda et al.	Sep 2004	B1
6790178	Mault et al.	Sep 2004	B1
6794195	Colvin, Jr.	Sep 2004	B2
6799861	Naghi et al.	Oct 2004	B2
6809653	Mann et al.	Oct 2004	B1
6810290	Lebel et al.	Oct 2004	B2
6811533	Lebel et al.	Nov 2004	B2
6811534	Bowman, IV et al.	Nov 2004	B2
6813519	Lebel et al.	Nov 2004	B2
6816742	Kim et al.	Nov 2004	B2
6818348	Venkatesan et al.	Nov 2004	B1
6830558	Flaherty et al.	Dec 2004	B2
6832114	Whitehurst et al.	Dec 2004	B1
6833540	MacKenzie et al.	Dec 2004	B2
6835553	Han et al.	Dec 2004	B2
6837858	Cunningham et al.	Jan 2005	B2
6839596	Nelson et al.	Jan 2005	B2
6840912	Kloepfer et al.	Jan 2005	B2
6849237	Housefield et al.	Feb 2005	B2
6850790	Berner et al.	Feb 2005	B2
6859831	Gelvin et al.	Feb 2005	B1
6862465	Shults et al.	Mar 2005	B2
6865407	Kimball et al.	Mar 2005	B2
6872200	Mann et al.	Mar 2005	B2
6873268	Lebel et al.	Mar 2005	B2
6881551	Heller et al.	Apr 2005	B2
6882940	Potts et al.	Apr 2005	B2
6892085	McIvor et al.	May 2005	B2
6893396	Schulze et al.	May 2005	B2
6895263	Shin et al.	May 2005	B2
6895265	Silver	May 2005	B2
6898451	Wuori	May 2005	B2
6899683	Mault et al.	May 2005	B2
6899684	Mault et al.	May 2005	B2
6904301	Raskas	Jun 2005	B2
6907127	Kravitz et al.	Jun 2005	B1
6908535	Rankin et al.	Jun 2005	B2
6916159	Rush et al.	Jul 2005	B2
6918874	Hatch et al.	Jul 2005	B1
6922576	Raskas	Jul 2005	B2
6922578	Eppstein et al.	Jul 2005	B2
6923763	Kovatchev et al.	Aug 2005	B1
6923764	Aceti et al.	Aug 2005	B2
6931327	Goode, Jr. et al.	Aug 2005	B2
6936029	Mann et al.	Aug 2005	B2
6949816	Brown et al.	Sep 2005	B2
6950708	Bowman, IV et al.	Sep 2005	B2
6952603	Gerber et al.	Oct 2005	B2
6955650	Mault et al.	Oct 2005	B2
6958129	Galen et al.	Oct 2005	B2
6958705	Lebel et al.	Oct 2005	B2
6960192	Flaherty et al.	Nov 2005	B1
6974437	Lebel et al.	Dec 2005	B2
6979326	Mann et al.	Dec 2005	B2
6983176	Gardner et al.	Jan 2006	B2
6990366	Say et al.	Jan 2006	B2
6990372	Perron et al.	Jan 2006	B2
6997911	Klitmose	Feb 2006	B2
6997920	Mann et al.	Feb 2006	B2
6999810	Berner et al.	Feb 2006	B2
7003340	Say et al.	Feb 2006	B2
7003341	Say et al.	Feb 2006	B2
7005857	Stiene et al.	Feb 2006	B2
7006858	Silver et al.	Feb 2006	B2
7010356	Jog et al.	Mar 2006	B2
7011630	Desai et al.	Mar 2006	B2
7015817	Copley et al.	Mar 2006	B2
7016713	Gardner et al.	Mar 2006	B2
7018360	Flaherty et al.	Mar 2006	B2
7020508	Stirovic et al.	Mar 2006	B2
7024245	Lebel et al.	Apr 2006	B2
7024249	Weisner et al.	Apr 2006	B2
7025425	Kovatchev et al.	Apr 2006	B2
7025743	Mann et al.	Apr 2006	B2
7027848	Robinson et al.	Apr 2006	B2
7027931	Jones et al.	Apr 2006	B1
7029444	Shin et al.	Apr 2006	B2
7029455	Flaherty	Apr 2006	B2
7034677	Steinthal et al.	Apr 2006	B2
7041468	Drucker et al.	May 2006	B2
7043287	Khalil et al.	May 2006	B1
7046153	Oja et al.	May 2006	B2
7052251	Nason et al.	May 2006	B2
7067498	Wolf et al.	Jun 2006	B2
7070591	Adams et al.	Jul 2006	B2
7072738	Bonney et al.	Jul 2006	B2
7074307	Simpson et al.	Jul 2006	B2
7077328	Krishnaswamy et al.	Jul 2006	B2
7079901	Loftin et al.	Jul 2006	B1
7081195	Simpson et al.	Jul 2006	B2
7083593	Stultz	Aug 2006	B2
7086277	Tess et al.	Aug 2006	B2
7092762	Loftin et al.	Aug 2006	B1
7092891	Maus et al.	Aug 2006	B2
7097983	Markovsky et al.	Aug 2006	B2
7098803	Mann et al.	Aug 2006	B2
7108711	Vogel et al.	Sep 2006	B2
7108778	Simpson et al.	Sep 2006	B2
7110803	Shults et al.	Sep 2006	B2
7114502	Schulman et al.	Oct 2006	B2
7123206	Hess et al.	Oct 2006	B2
7133710	Acosta et al.	Nov 2006	B2
7134999	Brauker et al.	Nov 2006	B2
7136689	Shults et al.	Nov 2006	B2
7136704	Schulman	Nov 2006	B2
7137964	Flaherty	Nov 2006	B2
7144384	Goiman et al.	Dec 2006	B2
7149581	Goedeke	Dec 2006	B2
7153212	Karten et al.	Dec 2006	B1
7153265	Vachon	Dec 2006	B2
7154398	Chen et al.	Dec 2006	B2
7155290	Von Arx et al.	Dec 2006	B2
7163511	Conn et al.	Jan 2007	B2
7167818	Brown	Jan 2007	B2
7171274	Starkweather et al.	Jan 2007	B2
7174199	Berner et al.	Feb 2007	B2
7181261	Silver et al.	Feb 2007	B2
7186566	Qian	Mar 2007	B2
7186791	Bruno et al.	Mar 2007	B2
7192450	Brauker et al.	Mar 2007	B2
7198603	Penner et al.	Apr 2007	B2
7202734	Raab	Apr 2007	B1
7205409	Pei et al.	Apr 2007	B2
7207974	Safabash et al.	Apr 2007	B2
7208119	Kurtock et al.	Apr 2007	B1
7211048	Najafi et al.	May 2007	B1
7218017	Chitayet et al.	May 2007	B1
7225535	Feldman et al.	Jun 2007	B2
7226278	Nason et al.	Jun 2007	B2
7226442	Sheppard, Jr. et al.	Jun 2007	B2
7226978	Tapsak et al.	Jun 2007	B2
7258666	Brown	Aug 2007	B2
7258673	Racchini et al.	Aug 2007	B2
7266400	Fine et al.	Sep 2007	B2
7276029	Goode, Jr. et al.	Oct 2007	B2
7278983	Ireland et al.	Oct 2007	B2
7283867	Strother et al.	Oct 2007	B2
7286894	Grant et al.	Oct 2007	B1
7299080	Acosta et al.	Nov 2007	B2
7303549	Flaherty et al.	Dec 2007	B2
7310544	Brister et al.	Dec 2007	B2
7317938	Lorenz et al.	Jan 2008	B2
7323091	Gillette et al.	Jan 2008	B1
7324949	Bristol et al.	Jan 2008	B2
7364592	Carr-Brendel et al.	Apr 2008	B2
7366556	Brister et al.	Apr 2008	B2
7379765	Petisce et al.	May 2008	B2
7404796	Ginsberg	Jul 2008	B2
7424318	Brister et al.	Sep 2008	B2
7436511	Ruchti et al.	Oct 2008	B2
7460898	Brister et al.	Dec 2008	B2
7467003	Brister et al.	Dec 2008	B2
7471972	Rhodes et al.	Dec 2008	B2
7474992	Ariyur	Jan 2009	B2
7480138	Kogan et al.	Jan 2009	B2
7494465	Brister et al.	Feb 2009	B2
7497827	Brister et al.	Mar 2009	B2
7510526	Merry et al.	Mar 2009	B2
7519408	Rasdal et al.	Apr 2009	B2
7583190	Reggiardo et al.	Sep 2009	B2
7583990	Goode, Jr. et al.	Sep 2009	B2
7591801	Brauker et al.	Sep 2009	B2
7599726	Goode, Jr. et al.	Oct 2009	B2
7602310	Mann et al.	Oct 2009	B2
7613491	Boock et al.	Nov 2009	B2
7615007	Shults et al.	Nov 2009	B2
7620437	Reggiardo	Nov 2009	B2
7630748	Budiman	Dec 2009	B2
7632228	Brauker et al.	Dec 2009	B2
7635594	Holmes et al.	Dec 2009	B2
7637868	Saint et al.	Dec 2009	B2
7640048	Dobbles et al.	Dec 2009	B2
7651596	Petisce et al.	Jan 2010	B2
7651845	Doyle, III et al.	Jan 2010	B2
7654956	Brister et al.	Feb 2010	B2
7657297	Simpson et al.	Feb 2010	B2
7699775	Desai et al.	Apr 2010	B2
7699964	Feldman et al.	Apr 2010	B2
7711402	Shults et al.	May 2010	B2
7713574	Brister et al.	May 2010	B2
7715893	Kamath et al.	May 2010	B2
7736310	Taub et al.	Jun 2010	B2
7766829	Sloan et al.	Aug 2010	B2
7768386	Hayter et al.	Aug 2010	B2
7768387	Fennell et al.	Aug 2010	B2
7771352	Shults et al.	Aug 2010	B2
7775444	DeRocco et al.	Aug 2010	B2
7778680	Goode et al.	Aug 2010	B2
7783333	Brister et al.	Aug 2010	B2
7792562	Shults et al.	Sep 2010	B2
7811231	Jin et al.	Oct 2010	B2
7813809	Strother et al.	Oct 2010	B2
7826382	Sicurello et al.	Nov 2010	B2
7826981	Goode, Jr. et al.	Nov 2010	B2
7889069	Fifolt et al.	Feb 2011	B2
7899511	Shults et al.	Mar 2011	B2
7899545	John	Mar 2011	B2
7905833	Brister et al.	Mar 2011	B2
7914450	Goode, Jr. et al.	Mar 2011	B2
7920906	Goode et al.	Apr 2011	B2
7928850	Hayter et al.	Apr 2011	B2
7938797	Estes	May 2011	B2
7941200	Weinert et al.	May 2011	B2
7946985	Mastrototaro et al.	May 2011	B2
7970448	Shults et al.	Jun 2011	B2
7972296	Braig et al.	Jul 2011	B2
7974672	Shults et al.	Jul 2011	B2
7976466	Ward et al.	Jul 2011	B2
7978063	Baldus et al.	Jul 2011	B2
8010174	Goode et al.	Aug 2011	B2
8010256	Oowada	Aug 2011	B2
8160900	Taub et al.	Apr 2012	B2
8192394	Estes et al.	Jun 2012	B2
8216138	McGarraugh et al.	Jul 2012	B1
8282549	Brauker et al.	Oct 2012	B2
8461985	Fennell et al.	Jun 2013	B2
8478557	Hayter et al.	Jul 2013	B2
20010016682	Berner et al.	Aug 2001	A1
20010016683	Darrow et al.	Aug 2001	A1
20010016710	Nason et al.	Aug 2001	A1
20010020124	Tamada	Sep 2001	A1
20010023095	Kopley et al.	Sep 2001	A1
20010024864	Kopley et al.	Sep 2001	A1
20010029340	Mault et al.	Oct 2001	A1
20010034502	Moberg et al.	Oct 2001	A1
20010037060	Thompson et al.	Nov 2001	A1
20010037069	Carlson et al.	Nov 2001	A1
20010037366	Webb et al.	Nov 2001	A1
20010041830	Varalli et al.	Nov 2001	A1
20010044581	Mault	Nov 2001	A1
20010044588	Mault	Nov 2001	A1
20010049470	Mault et al.	Dec 2001	A1
20010053891	Ackley	Dec 2001	A1
20010056255	Kost et al.	Dec 2001	A1
20020002326	Causey, III et al.	Jan 2002	A1
20020002328	Tamada	Jan 2002	A1
20020004640	Conn et al.	Jan 2002	A1
20020010414	Coston et al.	Jan 2002	A1
20020019022	Dunn et al.	Feb 2002	A1
20020026937	Mault	Mar 2002	A1
20020027164	Mault et al.	Mar 2002	A1
20020028995	Mault	Mar 2002	A1
20020032374	Holker et al.	Mar 2002	A1
20020040208	Flaherty et al.	Apr 2002	A1
20020042090	Heller et al.	Apr 2002	A1
20020047867	Mault et al.	Apr 2002	A1
20020053637	Conn et al.	May 2002	A1
20020054320	Ogino	May 2002	A1
20020062069	Mault	May 2002	A1
20020068858	Braig et al.	Jun 2002	A1
20020068860	Clark	Jun 2002	A1
20020077765	Mault	Jun 2002	A1
20020077766	Mault	Jun 2002	A1
20020087056	Aceti et al.	Jul 2002	A1
20020091312	Berner et al.	Jul 2002	A1
20020091454	Vasko	Jul 2002	A1
20020095076	Krausman et al.	Jul 2002	A1
20020103425	Mault	Aug 2002	A1
20020107433	Mault	Aug 2002	A1
20020107476	Mann et al.	Aug 2002	A1
20020109600	Mault et al.	Aug 2002	A1
20020118090	Park et al.	Aug 2002	A1
20020119711	Van Antwerp et al.	Aug 2002	A1
20020124017	Mault	Sep 2002	A1
20020133378	Mault et al.	Sep 2002	A1
20020147135	Schnell	Oct 2002	A1
20020161286	Gerber et al.	Oct 2002	A1
20020161288	Shin et al.	Oct 2002	A1
20020169394	Eppstein et al.	Nov 2002	A1
20020169439	Flaherty et al.	Nov 2002	A1
20020169635	Shillingburg	Nov 2002	A1
20020177764	Sohrab	Nov 2002	A1
20020193679	Malave et al.	Dec 2002	A1
20030009133	Ramey	Jan 2003	A1
20030023182	Mault et al.	Jan 2003	A1
20030023317	Brauker et al.	Jan 2003	A1
20030028089	Galley et al.	Feb 2003	A1
20030028120	Mault et al.	Feb 2003	A1
20030032868	Graskov et al.	Feb 2003	A1
20030032874	Rhodes et al.	Feb 2003	A1
20030040683	Rule et al.	Feb 2003	A1
20030050546	Desai et al.	Mar 2003	A1
20030050575	Diermann et al.	Mar 2003	A1
20030060692	Ruchti et al.	Mar 2003	A1
20030060753	Starkweather et al.	Mar 2003	A1
20030060765	Campbell et al.	Mar 2003	A1
20030065257	Mault et al.	Apr 2003	A1
20030065273	Mault et al.	Apr 2003	A1
20030065274	Mault et al.	Apr 2003	A1
20030065275	Mault et al.	Apr 2003	A1
20030065308	Lebel et al.	Apr 2003	A1
20030078560	Miller et al.	Apr 2003	A1
20030100040	Bonnacaze et al.	May 2003	A1
20030100821	Heller et al.	May 2003	A1
20030105407	Pearce, Jr. et al.	Jun 2003	A1
20030107487	Korman et al.	Jun 2003	A1
20030108976	Braig et al.	Jun 2003	A1
20030114897	Von Arx et al.	Jun 2003	A1
20030118460	Lilie et al.	Jun 2003	A1
20030125612	Fox et al.	Jul 2003	A1
20030130616	Steil et al.	Jul 2003	A1
20030134347	Heller et al.	Jul 2003	A1
20030135100	Kim et al.	Jul 2003	A1
20030135333	Aceti et al.	Jul 2003	A1
20030147515	Kai et al.	Aug 2003	A1
20030153820	Berner et al.	Aug 2003	A1
20030153821	Berner et al.	Aug 2003	A1
20030158472	Sohrab	Aug 2003	A1
20030158707	Doi	Aug 2003	A1
20030175806	Rule et al.	Sep 2003	A1
20030176933	Lebel et al.	Sep 2003	A1
20030181851	Mann et al.	Sep 2003	A1
20030181852	Mann et al.	Sep 2003	A1
20030187338	Say et al.	Oct 2003	A1
20030187525	Mann et al.	Oct 2003	A1
20030191376	Samuels et al.	Oct 2003	A1
20030191377	Robinson et al.	Oct 2003	A1
20030191431	Mann et al.	Oct 2003	A1
20030195403	Berner et al.	Oct 2003	A1
20030195462	Mann et al.	Oct 2003	A1
20030198558	Nason et al.	Oct 2003	A1
20030199825	Flaherty	Oct 2003	A1
20030199837	Vachon	Oct 2003	A1
20030208110	Mault et al.	Nov 2003	A1
20030208113	Mault et al.	Nov 2003	A1
20030208133	Mault	Nov 2003	A1
20030208154	Close et al.	Nov 2003	A1
20030208409	Mault	Nov 2003	A1
20030212346	Yuzhakov et al.	Nov 2003	A1
20030212364	Mann et al.	Nov 2003	A1
20030212379	Bylund et al.	Nov 2003	A1
20030217966	Tapsak et al.	Nov 2003	A1
20030225360	Eppstein et al.	Dec 2003	A1
20030225361	Sabra	Dec 2003	A1
20030226695	Mault	Dec 2003	A1
20030232370	Trifiro	Dec 2003	A1
20030235817	Bartkowiak et al.	Dec 2003	A1
20040010186	Kimball et al.	Jan 2004	A1
20040010207	Flaherty et al.	Jan 2004	A1
20040011671	Shults et al.	Jan 2004	A1
20040015131	Flaherty et al.	Jan 2004	A1
20040018486	Dunn et al.	Jan 2004	A1
20040019321	Sage et al.	Jan 2004	A1
20040024553	Monfre et al.	Feb 2004	A1
20040027253	Marsh et al.	Feb 2004	A1
20040034289	Teller et al.	Feb 2004	A1
20040039256	Kawatahara et al.	Feb 2004	A1
20040041749	Dixon	Mar 2004	A1
20040045879	Shults et al.	Mar 2004	A1
20040054263	Moerman et al.	Mar 2004	A1
20040059201	Ginsberg	Mar 2004	A1
20040063435	Sakamoto et al.	Apr 2004	A1
20040064088	Gorman et al.	Apr 2004	A1
20040064096	Flaherty et al.	Apr 2004	A1
20040064133	Miller et al.	Apr 2004	A1
20040072357	Stiene et al.	Apr 2004	A1
20040073095	Causey, III et al.	Apr 2004	A1
20040085215	Moberg et al.	May 2004	A1
20040096959	Stiene et al.	May 2004	A1
20040099529	Mao et al.	May 2004	A1
20040100376	Lye et al.	May 2004	A1
20040106858	Say et al.	Jun 2004	A1
20040106859	Say et al.	Jun 2004	A1
20040106860	Say et al.	Jun 2004	A1
20040108226	Polychronakos et al.	Jun 2004	A1
20040115067	Rush et al.	Jun 2004	A1
20040122353	Shahmirian et al.	Jun 2004	A1
20040132220	Fish	Jul 2004	A1
20040133092	Kain	Jul 2004	A1
20040133390	Osorio et al.	Jul 2004	A1
20040147872	Thompson	Jul 2004	A1
20040152622	Keith et al.	Aug 2004	A1
20040158137	Eppstein et al.	Aug 2004	A1
20040162473	Sohrab	Aug 2004	A1
20040164961	Bal et al.	Aug 2004	A1
20040167383	Kim et al.	Aug 2004	A1
20040167464	Ireland et al.	Aug 2004	A1
20040167801	Say et al.	Aug 2004	A1
20040171921	Say et al.	Sep 2004	A1
20040176913	Kawatahara et al.	Sep 2004	A1
20040186362	Brauker et al.	Sep 2004	A1
20040186365	Jin et al.	Sep 2004	A1
20040193025	Steil et al.	Sep 2004	A1
20040193090	Lebel et al.	Sep 2004	A1
20040199056	Husemann et al.	Oct 2004	A1
20040199059	Brauker et al.	Oct 2004	A1
20040202576	Aceti et al.	Oct 2004	A1
20040204868	Maynard et al.	Oct 2004	A1
20040207054	Brown et al.	Oct 2004	A1
20040208780	Faries, Jr. et al.	Oct 2004	A1
20040210184	Kost et al.	Oct 2004	A1
20040219664	Heller et al.	Nov 2004	A1
20040225338	Lebel et al.	Nov 2004	A1
20040236200	Say et al.	Nov 2004	A1
20040248204	Moerman	Dec 2004	A1
20040249250	McGee et al.	Dec 2004	A1
20040249253	Racchini et al.	Dec 2004	A1
20040249254	Racchini et al.	Dec 2004	A1
20040249999	Connolly et al.	Dec 2004	A1
20040253736	Stout et al.	Dec 2004	A1
20040254429	Yang	Dec 2004	A1
20040254434	Goodnow et al.	Dec 2004	A1
20040260478	Schwamm	Dec 2004	A1
20040263354	Mann et al.	Dec 2004	A1
20040264396	Ginzburg et al.	Dec 2004	A1
20050001024	Kusaka et al.	Jan 2005	A1
20050003470	Nelson et al.	Jan 2005	A1
20050009126	Andrews et al.	Jan 2005	A1
20050010269	Lebel et al.	Jan 2005	A1
20050016276	Guan et al.	Jan 2005	A1
20050017864	Tsoukalis	Jan 2005	A1
20050027179	Berner et al.	Feb 2005	A1
20050027180	Goode, Jr. et al.	Feb 2005	A1
20050027181	Goode, Jr. et al.	Feb 2005	A1
20050027462	Goode, Jr. et al.	Feb 2005	A1
20050027463	Goode, Jr. et al.	Feb 2005	A1
20050031689	Shults et al.	Feb 2005	A1
20050033132	Shults et al.	Feb 2005	A1
20050038680	McMahon	Feb 2005	A1
20050043598	Goode, Jr. et al.	Feb 2005	A1
20050043894	Fernandez	Feb 2005	A1
20050045476	Neel et al.	Mar 2005	A1
20050049179	Davidson et al.	Mar 2005	A1
20050049473	Desai et al.	Mar 2005	A1
20050051580	Ramey	Mar 2005	A1
20050053365	Adams et al.	Mar 2005	A1
20050054909	Petisce et al.	Mar 2005	A1
20050059926	Sage, Jr. et al.	Mar 2005	A1
20050065464	Talbot et al.	Mar 2005	A1
20050070774	Addison et al.	Mar 2005	A1
20050070777	Cho et al.	Mar 2005	A1
20050090607	Tapsak et al.	Apr 2005	A1
20050090808	Malave et al.	Apr 2005	A1
20050096516	Soykan et al.	May 2005	A1
20050112169	Brauker et al.	May 2005	A1
20050113657	Alarcon et al.	May 2005	A1
20050113658	Jacobson et al.	May 2005	A1
20050113886	Fischell et al.	May 2005	A1
20050116683	Cheng et al.	Jun 2005	A1
20050118726	Scultz et al.	Jun 2005	A1
20050121322	Say et al.	Jun 2005	A1
20050124873	Shults et al.	Jun 2005	A1
20050137471	Haar et al.	Jun 2005	A1
20050137530	Campbell et al.	Jun 2005	A1
20050143635	Kamath et al.	Jun 2005	A1
20050143636	Zhang et al.	Jun 2005	A1
20050148003	Keith et al.	Jul 2005	A1
20050154271	Rasdal et al.	Jul 2005	A1
20050161346	Simpson et al.	Jul 2005	A1
20050171503	Van Den Berghe et al.	Aug 2005	A1
20050171512	Flaherty	Aug 2005	A1
20050171513	Mann et al.	Aug 2005	A1
20050173245	Feldman et al.	Aug 2005	A1
20050176136	Burd et al.	Aug 2005	A1
20050177036	Shults et al.	Aug 2005	A1
20050181012	Saint et al.	Aug 2005	A1
20050182306	Sloan	Aug 2005	A1
20050182358	Veit et al.	Aug 2005	A1
20050182366	Vogt et al.	Aug 2005	A1
20050182451	Griffin et al.	Aug 2005	A1
20050187442	Cho et al.	Aug 2005	A1
20050187720	Goode, Jr. et al.	Aug 2005	A1
20050192557	Brauker et al.	Sep 2005	A1
20050195930	Spital et al.	Sep 2005	A1
20050199494	Say et al.	Sep 2005	A1
20050203360	Brauker et al.	Sep 2005	A1
20050203461	Flaherty et al.	Sep 2005	A1
20050204134	Von Arx et al.	Sep 2005	A1
20050214892	Kovatchev et al.	Sep 2005	A1
20050215871	Feldman et al.	Sep 2005	A1
20050215872	Berner et al.	Sep 2005	A1
20050235732	Rush	Oct 2005	A1
20050236361	Ufer et al.	Oct 2005	A1
20050238503	Rush et al.	Oct 2005	A1
20050238507	Dilanni et al.	Oct 2005	A1
20050239154	Feldman et al.	Oct 2005	A1
20050239518	D'Agostino et al.	Oct 2005	A1
20050245795	Goode, Jr. et al.	Nov 2005	A1
20050245799	Brauker et al.	Nov 2005	A1
20050245839	Stivoric et al.	Nov 2005	A1
20050249506	Fuse	Nov 2005	A1
20050249606	Rush	Nov 2005	A1
20050251033	Scarantino et al.	Nov 2005	A1
20050251083	Carr-Brendel et al.	Nov 2005	A1
20050261660	Choi	Nov 2005	A1
20050267550	Hess et al.	Dec 2005	A1
20050267780	Ray et al.	Dec 2005	A1
20050271546	Gerber et al.	Dec 2005	A1
20050271547	Gerber et al.	Dec 2005	A1
20050272640	Doyle, III et al.	Dec 2005	A1
20050272985	Kotulla et al.	Dec 2005	A1
20050277844	Strother et al.	Dec 2005	A1
20050277912	John	Dec 2005	A1
20050287620	Heller et al.	Dec 2005	A1
20060001538	Kraft et al.	Jan 2006	A1
20060001550	Mann et al.	Jan 2006	A1
20060001551	Kraft et al.	Jan 2006	A1
20060003398	Heller et al.	Jan 2006	A1
20060004271	Peyser et al.	Jan 2006	A1
20060004603	Peterka et al.	Jan 2006	A1
20060007017	Mann et al.	Jan 2006	A1
20060015020	Neale et al.	Jan 2006	A1
20060015024	Brister et al.	Jan 2006	A1
20060016700	Brister et al.	Jan 2006	A1
20060017923	Ruchti et al.	Jan 2006	A1
20060019327	Brister et al.	Jan 2006	A1
20060020186	Brister et al.	Jan 2006	A1
20060020187	Brister et al.	Jan 2006	A1
20060020188	Kamath et al.	Jan 2006	A1
20060020189	Brister et al.	Jan 2006	A1
20060020190	Kamath et al.	Jan 2006	A1
20060020191	Brister et al.	Jan 2006	A1
20060020192	Brister et al.	Jan 2006	A1
20060020300	Nghiem et al.	Jan 2006	A1
20060025663	Talbot et al.	Feb 2006	A1
20060031094	Cohen et al.	Feb 2006	A1
20060036139	Brister et al.	Feb 2006	A1
20060036140	Brister et al.	Feb 2006	A1
20060036141	Kamath et al.	Feb 2006	A1
20060036142	Brister et al.	Feb 2006	A1
20060036143	Brister et al.	Feb 2006	A1
20060036144	Brister et al.	Feb 2006	A1
20060036145	Brister et al.	Feb 2006	A1
20060036187	Vos et al.	Feb 2006	A1
20060040402	Brauker et al.	Feb 2006	A1
20060041229	Garibotto et al.	Feb 2006	A1
20060052679	Kotulla et al.	Mar 2006	A1
20060058588	Zdeblick	Mar 2006	A1
20060058602	Kwiatkowski et al.	Mar 2006	A1
20060058627	Flaherty et al.	Mar 2006	A1
20060063218	Bartowiak et al.	Mar 2006	A1
20060074564	Bartkowiak et al.	Apr 2006	A1
20060079740	Silver et al.	Apr 2006	A1
20060091006	Wang et al.	May 2006	A1
20060094986	Neel et al.	May 2006	A1
20060142651	Brister et al.	Jun 2006	A1
20060154642	Scannell	Jul 2006	A1
20060156796	Burke et al.	Jul 2006	A1
20060161078	Schraga	Jul 2006	A1
20060166629	Reggiardo	Jul 2006	A1
20060173259	Flaherty et al.	Aug 2006	A1
20060173444	Choy et al.	Aug 2006	A1
20060173712	Joubert	Aug 2006	A1
20060178633	Garibotto et al.	Aug 2006	A1
20060189863	Peyser et al.	Aug 2006	A1
20060193375	Lee et al.	Aug 2006	A1
20060202805	Schulman et al.	Sep 2006	A1
20060211072	Ryan et al.	Sep 2006	A1
20060222566	Brauker et al.	Oct 2006	A1
20060224141	Rush et al.	Oct 2006	A1
20060240403	List et al.	Oct 2006	A1
20060247508	Fennell	Nov 2006	A1
20060247985	Liamos et al.	Nov 2006	A1
20060253085	Geismar et al.	Nov 2006	A1
20060253296	Liisberg et al.	Nov 2006	A1
20060258929	Goode et al.	Nov 2006	A1
20060273759	Reggiardo	Dec 2006	A1
20060281985	Ward et al.	Dec 2006	A1
20060282290	Flaherty et al.	Dec 2006	A1
20060290496	Peeters et al.	Dec 2006	A1
20060293577	Morrison et al.	Dec 2006	A1
20060293607	Alt et al.	Dec 2006	A1
20070007133	Mang et al.	Jan 2007	A1
20070010950	Abensour et al.	Jan 2007	A1
20070016381	Kamath et al.	Jan 2007	A1
20070017983	Frank et al.	Jan 2007	A1
20070032706	Kamath et al.	Feb 2007	A1
20070032717	Brister et al.	Feb 2007	A1
20070038044	Dobbles et al.	Feb 2007	A1
20070060803	Liljeryd et al.	Mar 2007	A1
20070060869	Tolle et al.	Mar 2007	A1
20070060979	Strother et al.	Mar 2007	A1
20070066956	Finkel	Mar 2007	A1
20070078314	Grounsell et al.	Apr 2007	A1
20070078323	Reggiardo et al.	Apr 2007	A1
20070078818	Zvitz et al.	Apr 2007	A1
20070093786	Goldsmith et al.	Apr 2007	A1
20070094216	Mathias et al.	Apr 2007	A1
20070100222	Mastrototaro et al.	May 2007	A1
20070106135	Sloan et al.	May 2007	A1
20070118405	Campbell et al.	May 2007	A1
20070135697	Reggiardo	Jun 2007	A1
20070153705	Rosar et al.	Jul 2007	A1
20070156094	Safabash et al.	Jul 2007	A1
20070163880	Woo et al.	Jul 2007	A1
20070173711	Shah et al.	Jul 2007	A1
20070173761	Kanderian, Jr. et al.	Jul 2007	A1
20070176867	Reggiardo et al.	Aug 2007	A1
20070191702	Yodfat et al.	Aug 2007	A1
20070203407	Hoss et al.	Aug 2007	A1
20070203966	Brauker et al.	Aug 2007	A1
20070208246	Brauker et al.	Sep 2007	A1
20070213657	Jennewine et al.	Sep 2007	A1
20070219480	Kamen et al.	Sep 2007	A1
20070219597	Kamen et al.	Sep 2007	A1
20070228071	Kamen et al.	Oct 2007	A1
20070235331	Simpson et al.	Oct 2007	A1
20070255321	Gerber et al.	Nov 2007	A1
20070255348	Holtzclaw	Nov 2007	A1
20070271285	Eichorn et al.	Nov 2007	A1
20070282299	Hellwig	Dec 2007	A1
20070299617	Willis	Dec 2007	A1
20080004515	Jennewine et al.	Jan 2008	A1
20080004601	Jennewine et al.	Jan 2008	A1
20080021436	Wolpert et al.	Jan 2008	A1
20080021666	Goode, Jr. et al.	Jan 2008	A1
20080033254	Kamath et al.	Feb 2008	A1
20080045824	Tapsak et al.	Feb 2008	A1
20080057484	Miyata et al.	Mar 2008	A1
20080058626	Miyata et al.	Mar 2008	A1
20080058678	Miyata et al.	Mar 2008	A1
20080058773	John	Mar 2008	A1
20080060955	Goodnow	Mar 2008	A1
20080061961	John	Mar 2008	A1
20080064941	Funderburk et al.	Mar 2008	A1
20080071156	Brister et al.	Mar 2008	A1
20080083617	Simpson et al.	Apr 2008	A1
20080086042	Brister et al.	Apr 2008	A1
20080086044	Brister et al.	Apr 2008	A1
20080086273	Shults et al.	Apr 2008	A1
20080092638	Brenneman et al.	Apr 2008	A1
20080103447	Reggiardo et al.	May 2008	A1
20080108942	Brister et al.	May 2008	A1
20080114215	Ward et al.	May 2008	A1
20080114228	McCluskey et al.	May 2008	A1
20080119708	Budiman	May 2008	A1
20080139910	Mastrototaro et al.	Jun 2008	A1
20080161666	Feldman et al.	Jul 2008	A1
20080177149	Weinert et al.	Jul 2008	A1
20080182537	Manku et al.	Jul 2008	A1
20080183061	Goode et al.	Jul 2008	A1
20080183399	Goode et al.	Jul 2008	A1
20080188731	Brister et al.	Aug 2008	A1
20080189051	Goode et al.	Aug 2008	A1
20080194934	Ray et al.	Aug 2008	A1
20080194935	Brister et al.	Aug 2008	A1
20080194936	Goode et al.	Aug 2008	A1
20080194937	Goode et al.	Aug 2008	A1
20080194938	Brister et al.	Aug 2008	A1
20080195232	Carr-Brendel et al.	Aug 2008	A1
20080195967	Goode et al.	Aug 2008	A1
20080197024	Simpson et al.	Aug 2008	A1
20080200788	Brister et al.	Aug 2008	A1
20080200789	Brister et al.	Aug 2008	A1
20080200791	Simpson et al.	Aug 2008	A1
20080200838	Goldberger et al.	Aug 2008	A1
20080201325	Doniger et al.	Aug 2008	A1
20080208025	Shults et al.	Aug 2008	A1
20080208026	Noujaim et al.	Aug 2008	A1
20080214900	Fennell et al.	Sep 2008	A1
20080214915	Brister et al.	Sep 2008	A1
20080214918	Brister et al.	Sep 2008	A1
20080228051	Shults et al.	Sep 2008	A1
20080228054	Shults et al.	Sep 2008	A1
20080228055	Sher	Sep 2008	A1
20080234663	Yodfat et al.	Sep 2008	A1
20080234943	Ray et al.	Sep 2008	A1
20080242961	Brister et al.	Oct 2008	A1
20080242963	Essenpreis et al.	Oct 2008	A1
20080254544	Modzelewski et al.	Oct 2008	A1
20080262469	Brister et al.	Oct 2008	A1
20080269714	Mastrototaro et al.	Oct 2008	A1
20080269723	Mastrototaro et al.	Oct 2008	A1
20080275313	Brister et al.	Nov 2008	A1
20080287764	Rasdal et al.	Nov 2008	A1
20080287765	Rasdal et al.	Nov 2008	A1
20080287766	Rasdal et al.	Nov 2008	A1
20080288180	Hayter	Nov 2008	A1
20080288204	Hayter et al.	Nov 2008	A1
20080296155	Shults et al.	Dec 2008	A1
20080300572	Rankers et al.	Dec 2008	A1
20080306368	Goode et al.	Dec 2008	A1
20080306434	Dobbles et al.	Dec 2008	A1
20080306435	Kamath et al.	Dec 2008	A1
20080306444	Brister et al.	Dec 2008	A1
20080314395	Kovatchev et al.	Dec 2008	A1
20080319085	Wright et al.	Dec 2008	A1
20080319279	Ramsay et al.	Dec 2008	A1
20080319295	Bernstein et al.	Dec 2008	A1
20080319296	Bernstein et al.	Dec 2008	A1
20090005665	Hayter et al.	Jan 2009	A1
20090005666	Shin et al.	Jan 2009	A1
20090006034	Hayter et al.	Jan 2009	A1
20090006061	Thukral et al.	Jan 2009	A1
20090006133	Weinert et al.	Jan 2009	A1
20090012379	Goode et al.	Jan 2009	A1
20090018424	Kamath et al.	Jan 2009	A1
20090030294	Petisce et al.	Jan 2009	A1
20090033482	Hayter et al.	Feb 2009	A1
20090036747	Hayter et al.	Feb 2009	A1
20090036758	Brauker et al.	Feb 2009	A1
20090036760	Hayter	Feb 2009	A1
20090036763	Brauker et al.	Feb 2009	A1
20090040022	Finkenzeller	Feb 2009	A1
20090043181	Brauker et al.	Feb 2009	A1
20090043182	Brauker et al.	Feb 2009	A1
20090043525	Brauker et al.	Feb 2009	A1
20090043541	Brauker et al.	Feb 2009	A1
20090043542	Brauker et al.	Feb 2009	A1
20090045055	Rhodes et al.	Feb 2009	A1
20090048503	Dalal et al.	Feb 2009	A1
20090054745	Jennewine et al.	Feb 2009	A1
20090054747	Fennell	Feb 2009	A1
20090054748	Feldman et al.	Feb 2009	A1
20090055149	Hayter et al.	Feb 2009	A1
20090062633	Brauker et al.	Mar 2009	A1
20090062635	Brauker et al.	Mar 2009	A1
20090063402	Hayter	Mar 2009	A1
20090068954	Reggiardo et al.	Mar 2009	A1
20090076356	Simpson et al.	Mar 2009	A1
20090076358	Reggiardo et al.	Mar 2009	A1
20090076360	Brister et al.	Mar 2009	A1
20090076361	Kamath et al.	Mar 2009	A1
20090082693	Stafford	Mar 2009	A1
20090083003	Reggiardo et al.	Mar 2009	A1
20090085873	Betts et al.	Apr 2009	A1
20090088614	Taub et al.	Apr 2009	A1
20090093687	Telfort et al.	Apr 2009	A1
20090099436	Brister et al.	Apr 2009	A1
20090105560	Solomon	Apr 2009	A1
20090105570	Sloan et al.	Apr 2009	A1
20090105571	Fennell et al.	Apr 2009	A1
20090105636	Hayter et al.	Apr 2009	A1
20090124877	Goode et al.	May 2009	A1
20090124878	Goode et al.	May 2009	A1
20090124879	Brister et al.	May 2009	A1
20090124964	Leach et al.	May 2009	A1
20090131768	Simpson et al.	May 2009	A1
20090131769	Leach et al.	May 2009	A1
20090131776	Simpson et al.	May 2009	A1
20090131777	Simpson et al.	May 2009	A1
20090137886	Shariati et al.	May 2009	A1
20090137887	Shariati et al.	May 2009	A1
20090143659	Li et al.	Jun 2009	A1
20090143660	Brister et al.	Jun 2009	A1
20090156919	Brister et al.	Jun 2009	A1
20090156924	Shariati et al.	Jun 2009	A1
20090163790	Brister et al.	Jun 2009	A1
20090163791	Brister et al.	Jun 2009	A1
20090164190	Hayter	Jun 2009	A1
20090164239	Hayter et al.	Jun 2009	A1
20090164251	Hayter	Jun 2009	A1
20090177147	Blomquist et al.	Jul 2009	A1
20090178459	Li et al.	Jul 2009	A1
20090182217	Li et al.	Jul 2009	A1
20090192366	Mensinger et al.	Jul 2009	A1
20090192380	Shariati et al.	Jul 2009	A1
20090192722	Shariati et al.	Jul 2009	A1
20090192724	Brauker et al.	Jul 2009	A1
20090192745	Kamath et al.	Jul 2009	A1
20090192751	Kamath et al.	Jul 2009	A1
20090203981	Brauker et al.	Aug 2009	A1
20090204341	Brauker et al.	Aug 2009	A1
20090216100	Ebner et al.	Aug 2009	A1
20090216103	Brister et al.	Aug 2009	A1
20090227855	Hill et al.	Sep 2009	A1
20090240120	Mensinger et al.	Sep 2009	A1
20090240128	Mensinger et al.	Sep 2009	A1
20090240193	Mensinger et al.	Sep 2009	A1
20090240440	Shurabura et al.	Sep 2009	A1
20090242399	Kamath et al.	Oct 2009	A1
20090242425	Kamath et al.	Oct 2009	A1
20090247855	Boock et al.	Oct 2009	A1
20090247856	Boock et al.	Oct 2009	A1
20090247857	Harper et al.	Oct 2009	A1
20090247931	Damgaard-Sorensen	Oct 2009	A1
20090253973	Bashan et al.	Oct 2009	A1
20090259118	Feldman et al.	Oct 2009	A1
20090287073	Boock et al.	Nov 2009	A1
20090287074	Shults et al.	Nov 2009	A1
20090292188	Hoss et al.	Nov 2009	A1
20090296742	Sicurello et al.	Dec 2009	A1
20090298182	Schulat et al.	Dec 2009	A1
20090299155	Yang et al.	Dec 2009	A1
20090299156	Simpson et al.	Dec 2009	A1
20090299162	Brauker et al.	Dec 2009	A1
20090299276	Brauker et al.	Dec 2009	A1
20100010324	Brauker et al.	Jan 2010	A1
20100010329	Taub et al.	Jan 2010	A1
20100010331	Brauker et al.	Jan 2010	A1
20100010332	Brauker et al.	Jan 2010	A1
20100016687	Brauker et al.	Jan 2010	A1
20100016698	Rasdal et al.	Jan 2010	A1
20100022855	Brauker et al.	Jan 2010	A1
20100030038	Brauker et al.	Feb 2010	A1
20100030053	Goode, Jr. et al.	Feb 2010	A1
20100030484	Brauker et al.	Feb 2010	A1
20100030485	Brauker et al.	Feb 2010	A1
20100036215	Goode, Jr. et al.	Feb 2010	A1
20100036216	Goode, Jr. et al.	Feb 2010	A1
20100036222	Goode, Jr. et al.	Feb 2010	A1
20100036223	Goode, Jr. et al.	Feb 2010	A1
20100036225	Goode, Jr. et al.	Feb 2010	A1
20100041971	Goode, Jr. et al.	Feb 2010	A1
20100045465	Brauker et al.	Feb 2010	A1
20100049024	Saint et al.	Feb 2010	A1
20100063373	Kamath et al.	Mar 2010	A1
20100076283	Simpson et al.	Mar 2010	A1
20100081906	Hayter et al.	Apr 2010	A1
20100081908	Dobbles et al.	Apr 2010	A1
20100081910	Brister et al.	Apr 2010	A1
20100087724	Brauker et al.	Apr 2010	A1
20100096259	Zhang et al.	Apr 2010	A1
20100099970	Shults et al.	Apr 2010	A1
20100099971	Shults et al.	Apr 2010	A1
20100105999	Dixon et al.	Apr 2010	A1
20100119693	Tapsak et al.	May 2010	A1
20100121169	Petisce et al.	May 2010	A1
20100141656	Krieftewirth	Jun 2010	A1
20100152554	Steine et al.	Jun 2010	A1
20100160759	Celentano et al.	Jun 2010	A1
20100168538	Keenan et al.	Jul 2010	A1
20100168546	Kamath et al.	Jul 2010	A1
20100174266	Estes	Jul 2010	A1
20100185175	Kamen et al.	Jul 2010	A1
20100191082	Brister et al.	Jul 2010	A1
20100191085	Budiman	Jul 2010	A1
20100191472	Doniger et al.	Jul 2010	A1
20100198034	Thomas et al.	Aug 2010	A1
20100198142	Sloan et al.	Aug 2010	A1
20100198196	Wei	Aug 2010	A1
20100198314	Wei	Aug 2010	A1
20100204557	Kiaie et al.	Aug 2010	A1
20100213080	Celentano et al.	Aug 2010	A1
20100234710	Budiman et al.	Sep 2010	A1
20100240975	Goode et al.	Sep 2010	A1
20100274111	Say et al.	Oct 2010	A1
20100274515	Hoss et al.	Oct 2010	A1
20100275108	Sloan et al.	Oct 2010	A1
20100312176	Lauer et al.	Dec 2010	A1
20100313105	Nekoomaram et al.	Dec 2010	A1
20110024043	Boock et al.	Feb 2011	A1
20110024307	Simpson et al.	Feb 2011	A1
20110027127	Simpson et al.	Feb 2011	A1
20110027453	Boock et al.	Feb 2011	A1
20110027458	Boock et al.	Feb 2011	A1
20110028815	Simpson et al.	Feb 2011	A1
20110028816	Simpson et al.	Feb 2011	A1
20110029269	Hayter et al.	Feb 2011	A1
20110031986	Bhat et al.	Feb 2011	A1
20110077490	Simpson et al.	Mar 2011	A1
20110148905	Simmons et al.	Jun 2011	A1
20110208027	Wagner et al.	Aug 2011	A1
20110257895	Brauker et al.	Oct 2011	A1
20110287528	Fern et al.	Nov 2011	A1
20110320130	Valdes et al.	Dec 2011	A1
20120078071	Bohm et al.	Mar 2012	A1
20120108934	Valdes et al.	May 2012	A1
20120165626	Irina et al.	Jun 2012	A1
20120165640	Galley et al.	Jun 2012	A1
20120173200	Breton et al.	Jul 2012	A1
20120190989	Kaiser et al.	Jul 2012	A1
20130035575	Mayou et al.	Feb 2013	A1
20130235166	Jones et al.	Sep 2013	A1

Foreign Referenced Citations (44)

Number	Date	Country
2003259741	Feb 2004	AU
2495648	Feb 2004	CA
2498682	Sep 2005	CA
2555749	Sep 2005	CA
2632709	Jun 2007	CA
2615575	Jun 2008	CA
2701374	Apr 2009	CA
0455455	Nov 1991	EP
0518524	Dec 1992	EP
0878707	Nov 1998	EP
0543916	Jul 2001	EP
1130638	Sep 2001	EP
1755443	Nov 2005	EP
1783536	May 2007	EP
1956371	Aug 2008	EP
2260757	Dec 2010	EP
2001-177423	Jun 2001	JP
2001-056673	Nov 2001	JP
WO-1996014026	May 1996	WO
WO-1999022236	May 1999	WO
WO-2001052727	Jul 2001	WO
WO-2001071186	Sep 2001	WO
WO-2002039086	May 2002	WO
WO-2002084860	Oct 2002	WO
WO-2002100263	Dec 2002	WO
WO-2002100469	Dec 2002	WO
WO-2003006091	Jan 2003	WO
WO-2004015539	Feb 2004	WO
WO-2004028337	Apr 2004	WO
WO-2004032994	Apr 2004	WO
WO-2004061420	Jul 2004	WO
WO-2005089103	Sep 2005	WO
WO-2005101994	Nov 2005	WO
WO-2006003919	Jan 2006	WO
WO-2006079114	Jul 2006	WO
WO-2006086701	Aug 2006	WO
2007005170	Jan 2007	WO
2007051139	May 2007	WO
WO-2007065285	Jun 2007	WO
WO-2007149319	Dec 2007	WO
WO-2008001366	Jan 2008	WO
WO-2008151452	Dec 2008	WO
WO-2009049252	Apr 2009	WO
WO-2011104616	Sep 2011	WO

Non-Patent Literature Citations (26)

Entry
Al-Tabakha et al. Recent Challenges in Insulin Delivery systems: A Review Indian Journal of Pharmaceutical Sciences pp. 278-286 May-Jun. 2008 (Year: 2008).
Freckmann et al. Continuous Glucose Profiles in Healthy Subjects under Everyday Life Conditions and after Different Meals Journal of Diabetes Science and Technology vol. 1, pp. 695-703 (Year: 2007).
European Patent Application No. 10739770.5, Examination Report dated Sep. 22, 2014.
“An Electrochemical Slow Flow Meter”, http://gore.ocean.washington.edu/research/slow_flow_meter.html, 2005, 3 pages.
Barbosa, R. M., et al., “Electrochemical Studies of Zinc in Zinc-Insulin Solution”, Journal of the Royal Society of Chemistry, Analyst, vol. 121, No. 12, 1996, pp. 1789-1793.
Bard, A. J., et al., “Methods Involving Forced Convection—Hydrodynamic Methods”, Electrochemical Methods—Fundamentals and Applications, 2001, pp. 331-367.
Bremer, T. M., et al., “Benchmark Data from the Literature for Evaluation of New Glucose Sensing Technologies”, Diabetes Technology & Therapeutics, vol. 3, No. 3, 2001, pp. 409-418.
Cheyne, E. H., et al., “Perfoimance of a Continuous Glucose Monitoring System During Controlled Hypoglycaemia in Healthy Volunteers”, Diabetes Technology & Therapeutics, vol. 4, No. 5, 2002, pp. 607-613.
Diem, P., et al., “Clinical Performance of a Continuous Viscometric Affinity Sensor for Glucose”, Diabetes Technology & Therapeutics, vol. 6, 2004, pp. 790-799.
El-Khatib, F. H, et al., “Adaptive Closed-Loop Control Provides Blood-Glucose Regulation Using Subcutaneous Insulin and Glucagon Infusion in Diabetic Swine”, Journal of Diabetes Science and Technology, vol. 1, No. 2, 2007, pp. 181-192.
Garg, S., et al., “Improvement in Glycemic Excursions with a Transcutaneous, Real-Time Continuous Glucose Sensor”, Diabetes Care, vol. 29, No. 1, 2006, pp. 44-50.
Kissinger, P. T., “Introduction to Analog Instrumentation”, Laboratory Techniques in Electroanalytical Chemistry, Second Edition, Revised and Expanded, 1996, pp. 165-194.
Kondepati, V., et al., “Recent Progress in Analytical Instrumentation for Glycemic Control in Diabetic and Critically Ill Patients”, Analytical Bioanalytical Chemistry, vol. 388, 2007, pp. 545-563.
Li, Y., et al., “In Vivo Release From a Drug Delivery MEMS Device”, Journal of Controlled Release, vol. 100, 2004, 99. 211-219.
Lodwig, V., et al., “Continuous Glucose Monitoring with Glucose Sensors: Calibration and Assessment Criteria”, Diabetes Technology & Therapeutics, vol. 5, No. 4, 2003, pp. 573-587.
Morbiducci, U, et al., “Improved Usability of the Minimal Model of Insulin Sensitivity Based on an Automated Approach and Genetic Algorithms for Parameter Estimation”, Clinical Science, vol. 112, 2007, pp. 257-263.
Mougiakakou, et al., “A Real Time Simulation Model of Glucose-Insulin Metabolism for Type 1 Diabetes Patients”, Proceedings of the 2005 IEEE, 2005, pp. 298-301.
Panteleon, A. E., et al., “The Role of the Independent Variable to Glucose Sensor Calibration”, Diabetes Technology & Therapeutics, vol. 5, No. 3, 2003, pp. 401-410.
Parker, R., et al., “Robust H∞ Glucose Control in Diabetes Using a Physiological Model”, AIChE Journal, vol. 46, No. 12, 2000, pp. 2537-2549.
Ursino, M, et al., “A Mathematical Model of Cerebral Blood Flow Chemical Regulation—Part I: Diffusion Processes”, IEEE Transactions on Biomedical Engineering, vol. 36, No. 2, 1989, pp. 183-191.
European Patent Application No. 10739770.5, Examination Report dated Apr. 30, 2013.
PCT Application No. PCT/US2010/043132, International Preliminary Report on Patentability and Written Opinion of the International Searching Authority dated Feb. 2, 2012.
PCT Application No. PCT/US2010/043132, International Search Report dated Jan. 27, 2011.
U.S. Appl. No. 12/842,838, Notice of Allowance dated Jun. 11, 2014.
U.S. Appl. No. 12/842,838, Office Action dated Dec. 6, 2013.
European Patent Application No. 10739770.5, Examination Report dated May 13, 2015.

Related Publications (1)

	Number	Date	Country
	20140344280 A1	Nov 2014	US

Provisional Applications (1)

	Number	Date	Country
	61228101	Jul 2009	US

Continuations (1)

	Number	Date	Country
Parent	12842838	Jul 2010	US
Child	14449691		US

Real time management of data relating to physiological control of glucose levels

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

International Classifications

Disclaimer

Term Extension

Abstract