Device and method for automatic data acquisition and/or detection

Abstract
Methods and devices for providing diabetes management including automatic time acquisition protocol is provided.
Description
BACKGROUND

In diabetes management, there exist devices which allow diabetic patients to measure the blood glucose levels. One such device is a hand-held electronic meter such as blood glucose meters such as Freestyle® blood glucose monitoring system available from Abbott Diabetes Care, Inc., of Alameda, Calif. which receives blood samples via enzyme-based test strips. Typically, the patient lances a finger or alternate body site to obtain a blood sample, applies the drawn blood sample to the test strip, and the strip is inserted into a test strip opening or port in the meter housing. The blood glucose meter converts a current generated by the enzymatic reaction in the test strip to a corresponding blood glucose value which is displayed or otherwise provided to the patient to show the level of glucose at the time of testing.


Such periodic discrete glucose testing helps diabetic patients to take any necessary corrective actions to better manage diabetic conditions. Presently available glucose meters have limited functionalities (for example, providing the glucose value measured using the test strip and storing the data for subsequent recall or display) and do not provide any additional information or capability to assist patients in managing diabetes.


SUMMARY

In accordance with the various embodiments of the present disclosure, there are provided methods and devices for detecting a predefined parameter associated with an operational condition of an analyte monitoring device, transmitting a request for time information in response to the predefined parameter detection, and receiving time information in response to the transmitted request.


These and other objects, features and advantages of the present disclosure will become more fully apparent from the following detailed description of the embodiments, the appended claims and the accompanying drawings.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram illustrating a therapy management system for practicing one embodiment of the present disclosure;



FIG. 2 is a block diagram of an fluid delivery device of FIG. 1 in one embodiment of the present disclosure;



FIG. 3 is a flowchart illustrating the time zone detection procedure in the therapy management system in one embodiment of the present disclosure;



FIG. 4 is a flowchart illustrating the time zone detection procedure in the therapy management system in another embodiment of the present disclosure;



FIG. 5 is a flowchart illustrating the device synchronization procedure in the therapy management system in one embodiment of the present disclosure;



FIG. 6 is a flowchart illustrating device condition notification function in the therapy management system in one embodiment of the present disclosure;



FIG. 7 is a flowchart illustrating automatic time information detection function incorporated in a medical device such as a blood glucose meter in one embodiment of the present disclosure;



FIG. 8 is a flowchart illustrating automatic time information detection function incorporated in a medical device such as a blood glucose meter in another embodiment of the present disclosure; and



FIGS. 9A-9C illustrate embodiments of automatic expiration detection function on blood glucose meter test strips in accordance with one embodiment of the present disclosure.





DETAILED DESCRIPTION

As described below, within the scope of the present disclosure, there are provided user interface features associated with the operation of the various components or devices in a therapy management system such as automatic time change based functions, automatic expiration date detection on test strips, for example, synchronization of the components in the therapy management system, user interface changes based on the user configuration, notification functions for programmable events associated with the therapy management, and voice enabled communication between devices in the therapy management system.



FIG. 1 is a block diagram illustrating a therapy management system for practicing one embodiment of the present disclosure. Referring to FIG. 1, the therapy management system 100 includes an analyte monitoring system 110 operatively coupled to a fluid delivery device 120, which may be in turn, operatively coupled to a remote terminal 140. As shown in the Figure, the analyte monitoring system 110 is, in one embodiment, coupled to the patient 130 so as to monitor or measure the analyte levels of the patient. Moreover, the fluid delivery device 120 is coupled to the patient using, for example, an infusion set and tubing connected to a cannula (not shown) that is placed transcutaneously through the skin of the patient so as to infuse medication such as, for example, insulin, to the patient.


Referring to FIG. 1, the analyte monitoring system 110 in one embodiment may include one or more analyte sensors subcutaneously positioned such that at least a portion of the analyte sensors are maintained in fluid contact with the patient's analytes. The analyte sensors may include, but are not limited to short term subcutaneous analyte sensors or transdermal analyte sensors, for example, which are configured to detect analyte levels of a patient over a predetermined time period, and after which, a replacement of the sensors is necessary.


The one or more analyte sensors of the analyte monitoring system 110 is coupled to a respective one or more of a data transmitter unit which is configured to receive one or more signals from the respective analyte sensors corresponding to the detected analyte levels of the patient, and to transmit the information corresponding to the detected analyte levels to a receiver device, and/or fluid delivery device 120. That is, over a communication link, the transmitter units may be configured to transmit data associated with the detected analyte levels periodically, and/or intermittently and repeatedly to one or more other devices such as the fluid delivery device 120 and/or the remote terminal 140 for further data processing and analysis.


In one aspect, each of the one or more receiver devices of the analyte monitoring system 110 and the fluid delivery device 120 includes a user interface unit which may include a display unit, an audio output unit such as, for example, a speaker, or any other suitable user interface mechanism for displaying or informing the user of such devices.


The transmitter units of the analyte monitoring system 110 may in one embodiment be configured to transmit the analyte related data substantially in real time to the fluid delivery device 120 and/or the remote terminal 140 after receiving it from the corresponding analyte sensors such that the analyte level such as glucose level of the patient 130 may be monitored in real time. In one aspect, the analyte levels of the patient may be obtained using one or more of discrete blood glucose testing devices such as blood glucose meters that employ glucose test strips, or continuous analyte monitoring systems such as continuous glucose monitoring systems. In a further embodiment, the analyte monitoring system 110 may include a blood glucose meter such as Freestyle® and Precision meters available from Abbott Diabetes Care Inc., of Alameda Calif. The blood glucose meter may be used to calibrate the sensors in the analyte monitoring system 110. Exemplary analyte systems that may be employed are described in, for example, U.S. Pat. Nos. 6,134,461, 6,175,752, 6,121,611, 6,560,471, 6,746,582, and elsewhere, the disclosures of which are herein incorporated by reference.


Analytes that may be monitored, determined or detected in the analyte monitoring system 110 include, for example, acetyl choline, amylase, amyln, bilirubin, cholesterol, chorionic gonadotropin, creatine kinase (e.g., CK-MB), creatine, DNA, fructosamine, glucose, glutamine, growth hormones, hormones, ketones, lactate, measures for oxidative stress (such as 8-iso PGF2gamma), peroxide, prostate-specific antigen, prothrombin, RNA, thyroid stimulating hormone, and troponin. The concentration of drugs, such as, for example, antibiotics (e.g., gentamicin, vancomycin, and the like), biguanides, digitoxin, digoxin, drugs of abuse, GLP-1, insulin, PPAR agonists, sulfonylureas, theophylline, thiazolidinediones, and warfarin, may also be determined.


Moreover, within the scope of the present disclosure, the transmitter units of the analyte monitoring system 110 may be configured to directly communicate with one or more of the remote terminal 140 or the fluid delivery device 120. Furthermore, within the scope of the present disclosure, additional devices may be provided for communication in the analyte monitoring system 110 including additional receiver/data processing units, remote terminals (such as a physician's terminal and/or a bedside terminal in a hospital environment, for example).


In addition, within the scope of the present disclosure, one or more of the analyte monitoring system 110, the fluid delivery device 120 and the remote terminal 140 may be configured to communicate over a wireless data communication link such as, but not limited to radio frequency (RF) communication link, Bluetooth® communication link, infrared communication link, or any other type of suitable wireless communication connection between two or more electronic devices, which may further be uni-directional or bi-directional communication between the two or more devices. Alternatively, the data communication link may include wired cable connection such as, for example, but not limited to RS232 connection, USB connection, or serial cable connection.


The fluid delivery device 120 may include in one embodiment, but not limited to, an external infusion device such as an external insulin infusion pump, an implantable pump, a pen-type insulin injector device, a patch pump, an inhalable infusion device for nasal insulin delivery, or any other type of suitable delivery system. In addition, the remote terminal 140 in one embodiment may include for example, a desktop computer terminal, a data communication enabled kiosk, a laptop computer, a handheld computing device such as a personal digital assistant (PDAs), or a data communication enabled mobile telephone.


Referring back to FIG. 1, in one embodiment, the analyte monitoring system 110 includes a strip port configured to receive a test strip for capillary blood glucose testing. In one aspect, the glucose level measured using the test strip may in addition, be configured to provide periodic calibration of the analyte sensors of the analyte monitoring system 110 to assure and improve the accuracy of the analyte levels detected by the analyte sensors.


Referring yet again to FIG. 1, in one embodiment of the present disclosure, the fluid delivery device 120 may be configured to include a voice signal activation/generation unit for voice communication with the remote terminal 140 configured as a voice device such as a mobile telephone, a voice enabled personal digital assistant, a Blackberry device, or the like. For example, in one embodiment, the communication between the fluid delivery device 120 and the remote terminal 140 may be voice based such that the information or data output to the user from the fluid delivery device 120 is configured to be transmitted to the user's telephone. In turn, the fluid delivery device 120 may additionally be configured to receive voice commands from the remote terminal 140 configured as a telephone or any other voice signal communication device (such as personal computers or PDAs with voice signal capabilities).


In this manner, in one embodiment, the user interface of the fluid delivery device 120 may be configured with the voice signal activation/generation unit such that, output information for the user is converted into a voice signal and transmitted to the voice signal enabled remote terminal 140. For example, when the fluid delivery device 120 detects an alarm condition, the fluid delivery device 120 is configured to initiate a telephone call to the user's telephone (remote terminal 140), and when the user picks up the telephone line, the user is provided with a voice signal representing the alarm condition.


In a further embodiment, for certain predetermined patient conditions, the fluid delivery device 120 may be configured to initiate a telephone call directly to a preprogrammed telephone number of a health care physician, a local hospital, or emergency medical care facilities, in addition to or instead of initiating a telephone call to the user of the fluid delivery device 120.


In addition, within the scope of the present disclosure, interaction and programming of the fluid delivery device 120 may be exclusively or partially exclusively performed over the user's telephone in voice communication with the fluid delivery device 120. That is, when the user wishes to calculate a carbohydrate bolus in the fluid delivery device 120, the user may dial a predetermined number using the user's telephone (remote terminal 140) to connect with the fluid delivery device 120, and the user may provide voice commands to the fluid delivery device 120 via the telephone connection between the user's telephone (remote terminal 140) and the fluid delivery device 120.



FIG. 2 is a block diagram of an fluid delivery device of FIG. 1 in one embodiment of the present disclosure. Referring to FIG. 2, the fluid delivery device 120 in one embodiment includes a processor 210 operatively coupled to a memory unit 240, an input unit 220, a display unit 230, an output unit 260, and a fluid delivery unit 250. In one embodiment, the processor 210 includes a microprocessor that is configured to and capable of controlling the functions of the fluid delivery device 120 by controlling and/or accessing each of the various components of the fluid delivery device 120. In one embodiment, multiple processors may be provided as safety measure and to provide redundancy in case of a single processor failure. Moreover, processing capabilities may be shared between multiple processor units within the fluid delivery device 120 such that pump functions and/or control may be performed faster and more accurately.


Referring back to FIG. 2, the input unit 220 operatively coupled to the processor 210 may include a jog dial key pad buttons, a touch pad screen, or any other suitable input mechanism for providing input commands to the fluid delivery device 120. More specifically, in case of a jog dial input device, or a touch pad screen, for example, the patient or user of the fluid delivery device 120 will manipulate the respective jog dial or touch pad in conjunction with the display unit 230 which performs as both a data input and output unit. The display unit 230 may include a touch sensitive screen, an LCD screen, or any other types of suitable display unit for the fluid delivery device 120 that is configured to display alphanumeric data as well as pictorial information such as icons associated with one or more predefined states of the fluid delivery device 120, or graphical representation of data such as trend charts and graphs associated with the insulin infusion rates, trend data of monitored glucose levels over a period of time, or textual notification to the patients.


In one embodiment, the alphanumeric representation displayed on the display unit 230 may be configured to be modified by the user of the fluid delivery device such that the size of the displayed number or character may be adjusted to suit the user's visual needs. For example, in one embodiment, the user may apply font size adjustment request via the input unit 220 to instruct the processor 210 to modify the size of the displayed number or character on the display unit 230. In one aspect, the font size may be increased or decreased for each character, value or word displayed on the display unit 230. Alternatively, the font size adjustment may be applied globally to all output settings, for example, under the control of the processor 210 such that the user setting of the size adjustment may be configured to apply to substantially all displayed values or characters on the display unit 230 of the fluid delivery device 120 (FIG. 1).


Moreover, referring back to FIG. 2, in a further aspect of the present disclosure, the relative size adjustment of the displayed character or value may be determined by the processor 210 so that the relative size adjustment may be implemented to the output display on the display unit 230. In this manner, depending upon the type or configuration of the display unit 230 (whether bit map or icon type display), in one embodiment, the display size adjustment may be implemented within the predetermined size restrictions for the respective value or character. For example, a 10% relative increase in the font size for display area designated for insulin dosage level may correspond to a 5% relative increase in the size of the display area designated for the insulin delivery time display. In one embodiment, the processor 210 may be configured to determine the relative size modification for each area of the display unit 230 based on the user inputted size adjustment values to appropriately apply the relative size differential adjustment.


In a further aspect, the processor 210 may be configured to temporarily increase the font size displayed on the display unit 230 based on the user input commands such that the user requested size modification on the display unit 230 may be implemented only for the displayed screen at the time the user input commands for size adjustment is received by the processor 210. In this manner, the processor may be configured to revert to the previously programmed display size settings for the display unit 230 when the user is no longer viewing the particular displayed screen from which the user has requested font size adjustment.


In addition, the user interface of the receiver unit of the analyte monitoring system 110 (FIG. 1) may be configured with similar size adjustment capabilities so as to allow the user to instruct the controller or processor of the analyte monitoring system 110 to appropriately adjust the size of the displayed character or value on the display unit of the analyte monitoring system 110.


In a further embodiment, the display unit 230 may be configured to display an indication or marker for the type of insulin or other medication being used by the fluid delivery device 120 such as, for example, Symlin and Byetta. Such a marker may, in one embodiment, be associated with a predefined icon or character for display on the display unit 230. In addition, within the scope of the present disclosure, the information associated with the displayed marker or indication may be stored in the memory unit 240 so that the user may retrieve this information as desired. In addition, an indication or a marker for shift work may be programmed in the fluid delivery device 120 (FIG. 1) such that shift workers using the fluid delivery device 120 may align days and nights upon command based on the markers.


For example, if a user worked nightshifts on Mondays and Tuesdays and dayshifts on Thursdays and Fridays, this daily work pattern information may be stored, identified or marked in the fluid delivery device 120 to provide additional data management functionalities and a more robust therapy analysis. For example, meal times such as breakfasts, for example, at 8 pm on Monday and 9 pm on Tuesday (during the nightshifts) may be aligned with the breakfasts at 7 am on Thursday and 8 am on Friday. In this manner, the user may conveniently access meal (e.g., breakfast) related data and associated therapy information in conjunction with the operation of the fluid delivery device 120. This may assist the user in improving upon the user's diet such as the daily food intake.


Referring to FIG. 2, the output unit 260 operatively coupled to the processor 210 may include an audible alarm or alarms including one or more tones and/or preprogrammed or programmable tunes or audio clips, or vibratory alert features having one or more pre-programmed or programmable vibratory alert levels.


In addition, in one embodiment of the present disclosure, each alert event or alarm event may be programmed with combined notification features such that, depending upon the level of importance associated with each alert or alarm, a combination of vibratory, audible, or displayed indications may be provided to the user using the display unit 230 in combination with the output unit 260.


For example, the processor 210 may be configured to provide combined vibratory and increasingly audible alerts on the output unit 260 in addition to intermittently flashing background light on the display unit 230 for one or more predetermined alarms that require immediate user attention. An example may include unexpected pressure increase in the infusion tubing which may indicate an occlusion or other undesirable condition that the user should be immediately notified. The processor 210 may be configured such that the alarm or alert may be automatically reasserted within a predetermined time period in the event the associated alarm or alert condition has not been cleared by the user. In addition, each alert/alarm feature may be individually programmed to include a wide selection of tones, audible levels, vibratory strength, and intensity of visual display.


In a further aspect, the fluid delivery device 120 may be configured to provide an alarm or alert indication associated with a change in temperature. That is, when the fluid delivery device 120 which contains the insulin (for example, in a reservoir) experiences a rise or drop in temperature, such change in the temperature may have adverse effect on the insulin contained within the device 120. Accordingly, a temperature sensor may be coupled to the processor 210 of the fluid delivery device 120 to detect the operating condition of the fluid delivery device 120 and to notify the user of changes in the temperature, when, for example, the temperature change reaches a predetermined threshold level that may potentially have adverse impact upon the efficacy of the insulin being delivered.


Also shown in FIG. 2 is the fluid delivery unit 250 which is operatively coupled to the processor 210 and configured to deliver the insulin doses or amounts to the patient from the insulin reservoir or any other types of suitable containment for insulin to be delivered (not shown) in the fluid delivery device 120 via an infusion set coupled to a subcutaneously positioned cannula under the skin of the patient.


Referring yet again to FIG. 2, the memory unit 240 may include one or more of a random access memory (RAM), read only memory (ROM), or any other type of data storage unit that is configured to store data as well as program instructions for access by the processor 210 and execution to control the fluid delivery device 120 and/or to perform data processing based on data received from the analyte monitoring system 110, the remote terminal 140, the patient 130 or any other data input source.



FIG. 3 is a flowchart illustrating the time zone detection procedure in the therapy management system in one embodiment of the present disclosure. Referring to FIG. 3, the fluid delivery device 120 (FIG. 1) may be configured to transmit a location position request (310) to for example, a global positioning system (GPS). Thereafter, the location information is received (320) by the processor 210 of the fluid delivery device 120. The processor 210 is further configured to determine whether the location information has changed (330). That is, the processor 210 in one embodiment is configured to compare the receive location information which may include a current time zone information associated with the location of the fluid delivery device 120, with the previously stored and operating time zone information in the fluid delivery device 120 in operation.


Referring back, if it is determined that the location information has not changed, then the routine terminates. On the other hand, if it is determined that the fluid delivery device location information has changed, then, the location change information is output (340) to the user on the display unit 230, for example. Thereafter, the processor 210 may be configured to generate a user prompt or notification to modify the time zone information (350) of the fluid delivery device 120 such that it is updated to the new location where the fluid delivery device 120 is operating.


For example, when the fluid delivery device 120 is programmed with predetermined basal profiles and/or bolus functions that are time based and associated with an internal clock of the fluid delivery device 120, it may be desired to modify some or all of the time based insulin delivery profiles programmed in the fluid delivery device 120 so as to correspond to the location of the fluid delivery device 120. More specifically, if a user is traveling from a first location to a second location in which one or more time zones are traversed, e.g., by way of example from San Francisco to Paris, given the time difference, the meal times, and sleep times, for example, will change. In this case, it may be desirable to modify the preprogrammed time based insulin delivery profiles so that they are synchronized with the user events such as meals and sleep times.


Referring back to FIG. 3, in one embodiment, the user responds to the time based programming change prompt provided by the processor 210, then the processor 210 may be configured in one embodiment, to propagate the time change associated with the preprogrammed insulin delivery profile and notify the user to confirm the changes, prior to implementing the modification to the delivery profiles and any associated alerts or notifications. For example, in the case where the user has programmed to be alerted at a particular time of day, e.g., noon each day, for a bolus determination prior to lunch, the processor 210 in one embodiment is configured to either modify the internal clock of the fluid delivery device 120 or alternatively, modify the programmed alert for bolus determination so as to correspond to the new location of the user and the fluid delivery device 120.


In another embodiment, the fluid delivery device 120 may be configured to include a time zone detection unit, such as for example, the processor 210 may be configured to communicate with a geographical location change detection mechanism (e.g., an atomic clock) operatively coupled to the processor 210 for performing the time zone detection procedure as described above in conjunction with FIG. 3. In addition, the analyte monitoring system 110 may be configured to include a time zone detection unit as described above to automatically or based on a preprogrammed procedure, detect any location change associated with the analyte monitoring system 110. In this manner, the analyte monitoring system 110 may be configured to automatically or based on a preprogrammed procedure, implement modifications to functions associated with the operation of the analyte monitoring system 110 that are temporally associated with the time of day information.



FIG. 4 is a flowchart illustrating the time zone detection procedure in the therapy management system in another embodiment of the present disclosure. Referring to FIG. 4, the fluid delivery device 120 (FIG. 1) may be configured to transmit a location position request (410) to for example, a global positioning system (GPS). Thereafter, the location information is received (420) by the processor 210 of the fluid delivery device 120. The processor 210 is further configured to determine whether the location information has changed (430). That is, the processor 210 in one embodiment is configured to compare the receive location information which may include a current time zone information associated with the location of the fluid delivery device 120, with the previously stored and operating time zone information in the fluid delivery device 120 in operation.


Referring back, if it is determined that the location information has not changed, then the routine terminates. On the other hand, if it is determined that the fluid delivery device 330 location information has changed, then, the processor 210 in one embodiment is configured to retrieve one or more time based programmed functions (440) from the memory unit 240 of the fluid delivery device 120, for example.


Thereafter, the processor 210 may be further configured to modify the retrieved time based preprogrammed functions in accordance with the location change information received (450). Then, the modified retrieved functions are provided to the user (460) on the display unit 230, for example, to request confirmation of the time based adjustments, prior to the processor 210 executing the modified retrieved functions.


In addition, in one embodiment of the present disclosure, the fluid delivery device 120 may be configured to detect for daylight savings time and the processor 210 may be configured to either automatically execute the time change in the internal clock of the fluid delivery device, and/or provide a user notification to accept such time based change so that the operation of the fluid delivery device 120 performing time based programs are updated with any time based change in the insulin delivery system 120 operating environment.


Within the scope of the present disclosure, the fluid delivery device 120 may be configured to receive location information from any positioning system which provides updated time information based on location. The fluid delivery device 120 may be configured with a positioning transceiver that is configured to transmit location information request to a satellite network, for example, and to receive the location information therefrom.


Alternatively, the fluid delivery device 120 may be configured to update its location information locally upon synchronization with another device operating in the local (or at the new location). This may include a host computer terminal connectable to the fluid delivery device 120 such as, for example, the remote terminal 140 (FIG. 1), the analyte monitoring system 110, or any other electronic device operating in the new location with communication capabilities with the fluid delivery device 120 such as a cellular telephone, a personal digital assistant, and the like.


In addition, within the scope of the present disclosure, the procedure and processes described in conjunction with FIGS. 3-4 associated with location change information and corresponding modification to the time based preprogrammed functions in the fluid delivery device 120 may be provided to the analyte monitoring system 110 such that the analyte monitoring system 110 is also configured to receive new location information and correspondingly perform modifications to any time based preprogrammed functions.



FIG. 5 is a flowchart illustrating the device synchronization procedure in the therapy management system in one embodiment of the present disclosure. Referring to FIG. 5, in one embodiment the fluid delivery device 120 (FIG. 1) may be configured to detect a synchronization request (510) from another device such as the remote terminal 140 or the analyte monitoring system 110 (FIG. 1). Thereafter, data communication connection is established (520) between the fluid delivery device 120 and the synchronization requesting device. In one embodiment, the fluid delivery device 120 is configured to verify the authenticity or identity of the device requesting synchronization, and upon synchronization approval, the fluid delivery device 120 is configured to establish communication with the synchronization requesting device.


In addition, within the scope of the present disclosure, the fluid delivery device 120 may be configured to periodically or at a predetermined time interval, establish communication connection with another device for synchronization. Alternatively, the fluid delivery device may be configured to attempt communication connection when another device for synchronization is detected within a predefined distance from the location of the fluid delivery device 120.


Referring back to FIG. 5, the fluid delivery device 120 is configured in one embodiment to transmit its programmed and operating settings to the connected device (530), and the connected device is configured to update and store the data received from the fluid delivery device 120 based on predetermined conditions (540). For example, the predetermined conditions may include a predefined set of rules associated with the type of data from the fluid delivery device 120 to be updated such as historical infusion related information, programmed functions in the fluid delivery device 120 such as bolus calculations, temporarily basal profiles, programmed basal profiles, insulin usage level, and any other information that is associated with the user.


In this manner, in one embodiment of the present disclosure, periodic synchronization of the fluid delivery device 120 settings and functions may be synchronized to another device so that when the user replaces the fluid delivery device 120, the new or upgrade fluid delivery device may be easily and readily programmed to the user's specification. The synchronization described above may be configured to be performed periodically at a regular interval such as, once a week, once per day, when certain predefined criteria are met such as when the devices are within a predetermined distance from each other, and/or upon user command.


In addition, within the scope of the present disclosure, the fluid delivery device 120 may be configured with any communication protocol which would allow data transfer between the fluid delivery device 120 and the synchronizing device. This may include, wired or wireless communication including for example, Bluetooth® protocol, 802.1x protocol, USB cable connection and the like.



FIG. 6 is a flowchart illustrating device condition notification function in the therapy management system in one embodiment of the present disclosure. Referring to FIG. 6 the fluid delivery device 120 may be configured to detect a notification condition (610). For example, the processor 210 may be configured to detect such notification conditions at a preprogrammed time interval (such as about every 24 hours, for example). Thereafter, the programmed profile associated with the condition is retrieved (620). An example of the programmed profile associated with the condition includes a reminder to start an overnight fast for the user.


Referring back to FIG. 6, the processor 210 in one embodiment is further configured to generate a message associated with the notification condition and/or the retrieved programmed profile (630), and, the generated message is provided to the user (640) on one or more of the display unit 230 or the output unit 260. In this manner, in one embodiment of the present disclosure, the fluid delivery device 120 may be programmed with automatic reminders for conditions to assist the user to improve insulin therapy management.


In one embodiment, the notification condition detection may be skipped and the processor 210 may be configured to retrieve the appropriate programmed profile associated with notification conditions based on the user programming of the fluid delivery device 120. Additionally, while a reminder for overnight fast is described as an example, any other therapy related reminders or device operating condition reminders may be programmed for execution by the processor 210 to remind the user. Examples of such reminders include, but are not limited to, infusion set replacement reminder, battery replacement reminder, data synchronization reminder, insulin replenishment reminder, glucose testing reminder, and the like. In addition, within the scope of the present disclosure, the procedure described in conjunction with FIG. 6 may be incorporated in the analyte monitoring system 110 for programming suitable automatic reminders such as, for example, sensor replacement reminder, sensor calibration reminder, and the like.



FIG. 7 is a flowchart illustrating automatic time information detection function incorporated in a medical device such as a blood glucose meter of the analyte monitoring system 110 in one embodiment of the present disclosure. Referring to FIG. 7, when the medical device active state is detected (710) for example, by the user initiated power on procedure of the medical device such as a blood glucose meter, a routine is called by the processor of the medical device to automatically initiate time acquisition protocol. That is, upon power on of the medical device, the device is automatically configured to perform time acquisition protocol to, among others, transmit request for time and/or date information to available communication channels, and upon receiving the information, to store, update and/or otherwise set and/or display the received or acquired time/date information in the medical device (720-740).


Referring back to FIG. 7, in one embodiment, the time information is received at step 730, and thereafter, the received time information is stored and/or displayed on a display unit of the medical device. In one aspect, the medical device is configured to update all previously stored time associated data (for example, blood glucose readings taken at certain times of the day (or week, month, or any other time period)). More specifically, in one embodiment, when the medical device such as the blood glucose meter is activated by the user, the processor or controller of the glucose meter is configured to enable or activate time/date receiver (for example, a communication component such as a radio frequency transceiver coupled to the processor of the glucose meter). The time/date receiver in one embodiment is configured to seek or acquire automatically, upon activation, time and date information from one or more available communication networks within range. For example, the time/date receiver may be configured to detect the time/date information from one or more radio frequencies on public, government, or private airwaves using AM band short frequency or FM band long wave frequency. Alternatively, as discussed above, current local time/date information may be received from global positioning satellites, as well as cellular telephone networks such as GSM, CDMA, AMPS, and the like within range of the time/date receiver in the medical device. Additionally, WiFi network may be used to receive the time/data information, if available and within range.


In this manner, in one embodiment, the medical device such as a blood glucose meter, may be configured to automatically acquire time information that is continuously broadcast on frequency which antenna and the receiver of the blood glucose meter is configured to operate. Upon obtaining and verifying the time and date information, the internal clock function or component is updated or adjusted with the acquired time/date information and displayed to the user, for example.


In a further embodiment, the medical device such as a blood glucose meter may be configured to use GMT time as the reference time for all log entry (for example, for each blood glucose test performed) timestamps associated with each data stored in the medical device. Thereafter, the medical device may be configured to convert the stored GMT based time information for each log entry stored in the medical device to the local time based on the location of the medical device.



FIG. 8 is a flowchart illustrating automatic time information detection function incorporated in a medical device such as a blood glucose meter in another embodiment of the present disclosure. Referring to FIG. 8, in one embodiment, the automatic time acquisition protocol is initiated based on a detection of one or more changed or preconfigured parameters associated with the medical device and/or the user of the medical device (810). For example, the device parameter may include a preconfigured time for periodically checking for time and date information (such as every 24 hours, 48 hours, or based on a programmed calendar such as to compensate for daylight savings time change).


Alternatively, the device parameter may include an environmental condition change associated with the medical device or the user, such as a detection of the medical device location such as during travel by air or a vehicle. That is, in one embodiment, the medical device may be configured to include an altimeter which is coupled to the processor of the medical device to detect a change in altitude of the medical device location for example, when the user of the medical device is traveling by air. In such a case, the medical device may be configured to initiate the time acquisition protocol to confirm or verify the time and date information of the medical device (820-840).


Further, the medical device may include an accelerometer which may be configured to initiate the automatic time acquisition protocol on the medical device when a predetermined threshold level of acceleration force is reached. Within the scope of the present disclosure, other parameters may be used in conjunction with the medical device to trigger the automatic time acquisition protocol on the medical device (820-840) such that, without user intervention, prompting, or initiating, the medical device is configured to automatically initiate time and date information acquisition routine. In addition, the functionality of the automatic time and date information acquisition may be incorporated in other medical devices such as infusion pumps, continuous glucose monitoring devices, heart rate monitors, and the like that are configured to maintain a time associated log of physiological data (such as glucose levels, insulin infusion rates, cardiac signal levels and so on) of a patient or a user.



FIGS. 9A-9C illustrate embodiments of automatic expiration detection function on blood glucose meter test strips in accordance with one embodiment of the present disclosure. Presently, test strips for use with blood glucose meters are sold or made available in containers that include the expiration date information of the test strips contained therein. For diabetic patients or healthcare providers using glucose meters, it is important to check the expiration information of the test strip before testing for glucose levels so that the obtained results are accurate.


Referring to FIGS. 9A-9C, in one embodiment, test strips may be configured with predefined parameters to allow automatic expiration date detection of the test strip. In one aspect, resistance values are provided on the test strips such that when the test strip is inserted into the strip port of the blood glucose meter, the meter is configured to compare the detected resistance value to a stored value of resistance, and determine whether the inserted test strip has expired or not. More specifically, in one embodiment, using the resistance value on the test strip, the expiration date information may be coded, and the meter may be configured to detect the resistance value of the test strip and determine whether the test strip has expired.


In one aspect, the resistance value on the test strip may be controlled with the ink formulation on the wake up bar and/or patterns provided thereon. Silver, gold, carbon or any other suitable conductive material may be used to increase the resistance as may be desired. The blood glucose meter may be configured such that the strip port includes a current connector and predetermined control lines that may be configured to measure the resistance values coded on the test strips. More specifically, in one embodiment, the expiration dates may be coded using the resistance value on the wake-up bar in a logical sequence such as follows:
















Resistance Value
Expiration Date









300-310 kOhm
Q1 of odd year



315-320 kOhm
Q2 of odd year



. . .



350-360 kOhm
Q1 of even year










Referring to FIGS. 9A-9C, it can be seen that the wavy lines may increase in thickness or length to change the resistance on the test strip. Furthermore, the pads on the test strip are shown to make contact with the wake-up bar on the strip port. By way of an example, FIG. 9A illustrates 300 KOhm trace width, FIG. 9B illustrates 315 KOhm trace width, and FIG. 9C illustrates 350 KOhm trace width, each associated with a predefined expiration date as described above.


In this manner, in one embodiment of the present disclosure, expiration date of test strips may be automatically detected so that the user is notified of expired date of a given test strip before it used to test for blood glucose levels. Moreover, while the automatic expiration detection is described in conjunction with test strip and blood glucose meters, within the scope of the present disclosure, other medical device or comsumable items with expiration dates may benefit from the technique described herein.


Accordingly, a method in one aspect of the present disclosure includes detecting a predefined parameter associated with an operational condition of a medical device such as, for example, but not limited to a blood glucose meter, an analyte monitoring device such as continuous glucose monitoring device, or an infusion pump, transmitting a request for time information in response to the predefined parameter detection, and receiving time information in response to the transmitted request.


The method in one aspect may include storing the received time information.


In a further aspect, the method may include updating one or more stored data based on the received time information.


In still another aspect, the method may include retrieving one or more stored data associated with stored time related information, and updating the retrieved one or more stored data based on the received time information, and further, storing the updated retrieved one or more stored data.


The retrieved one or more stored data may include one or more of a blood glucose measurement value, monitored analyte level data, calibration schedule data, or analyte sensor insertion time data.


Further, transmitting the request for time information may be automatically performed in response to the predefined parameter detection.


In still another aspect, the method may include displaying the received time information.


The method may also include receiving confirmation of the received time information.


The time information may include one or more of a time of day information and date information, or other temporal and/or geographical information such as time zone information, location information, GMT data, and the like.


A medical device in accordance with another aspect of the present disclosure includes one or more processing units, and a memory for storing instructions which, when executed by the one or more processing units, causes the one or more processing units to detect a predefined parameter associated with an operational condition of the medical device, to transmit a request for time information in response to the predefined parameter detection, and to receive time information in response to the transmitted request.


The memory for storing instructions which, when executed by the one or more processing units, may cause the one or more processing units to store the received time information.


The memory for storing instructions which, when executed by the one or more processing units, may cause the one or more processing units to update one or more stored data based on the received time information.


The memory for storing instructions which, when executed by the one or more processing units, may cause the one or more processing units to retrieve one or more stored data associated with stored time related information, and to update the retrieved one or more stored data based on the received time information.


Also, the memory for storing instructions which, when executed by the one or more processing units, may cause the one or more processing units to store the updated retrieved one or more stored data.


In one embodiment, the medical device may include an analyte monitoring device, such as a blood glucose meter, a continuous glucose monitoring device, an integrated continuous glucose monitoring device and blood glucose meter, or a controller unit in communication with one or more of the blood glucose meter, the continuous glucose monitoring device or the integrated continuous glucose monitoring device and blood glucose meter.


For example, in one aspect, the medical device may include an in vitro blood glucose meter. Alternatively, the medical device may include a receiver unit or a controller unit in a continuous glucose monitoring system 110 (FIG. 1), which may additionally incorporate a strip port and the corresponding electronic circuitry for processing blood samples from an in vitro test strip.


In still another aspect, the medical device may include an infusion device for infusing medication such as insulin, for example an external infusion pump, an implantable infusion pump, an inhalable medication dispensing unit, or a medication injection device.


The retrieved one or more stored data includes one or more of a blood glucose measurement value, monitored analyte level data, calibration schedule data, or analyte sensor insertion time data, or any other time associated data such as, for example, a medication delivery schedule such as programmed basal profiles in infusion pumps.


Also, the memory for storing instructions which, when executed by the one or more processing units, may the one or more processing units to automatically transmit the request for time information in response to the predefined parameter detection.


The device may include a display unit operatively coupled to the one or more processing units, to display the received time information.


The memory for storing instructions which, when executed by the one or more processing units, may cause the one or more processing units to receive confirmation of the received time information.


The one or more of the processing units may include a communication unit configured to transmit the request for time information or to receive time information in response to the transmitted request, or both.


The communication unit may be configured to transmit or receive information using one or more of a Bluetooth communication protocol, an RF communication protocol, an infrared communication protocol, a Zigbee communication protocol, an 802.1× communication protocol, or a wireless personal area network protocol.


A medical device in yet another embodiment may include means for detecting a predefined parameter associated with an operational condition of a medical device, means for transmitting a request for time information in response to the predefined parameter detection, and means for receiving time information in response to the transmitted request.


A therapy management system in one embodiment of the present disclosure includes an infusion device including a processing unit configured to perform data processing, and a user interface unit operatively coupled to a processing unit, where the processing unit is configured to detect a location information associated with the infusion device for output to the user interface unit.


The location information in one embodiment is time based.


In one aspect, the location information is associated with a local time information based on the location of the infusion device, where the location information may be received from a global positioning system (GPS) or from another device, such as a mobile telephone, a GPS enabled personal digital assistant, which has received that information from a global positioning system.


In one aspect, a clock unit may be operatively coupled to the processing unit, where the clock unit is configured to dynamically adjust the location information based on the location of the infusion device.


In a further embodiment, the clock unit may include an atomic clock.


The processor unit may be configured to generate a notification associated with the detected location information for output to the user interface unit, where the notification may be output to the user interface unit as one or more of a date information and time information associated with the location of the infusion device.


The processing unit may be configured to retrieve one or more programmed procedures associated with time, where the one or more programmed procedures may include one or more basal profiles, a programmed bolus determination schedule, a time based condition alert.


The time based condition alert may include one or more of a time based reminder associated with the operation of the infusion device. Further, the time based condition alert may include one or more of a time based reminder associated with the condition of the infusion device user.


In a further aspect, the processor unit may be configured to automatically adjust one or more time based functions associated with the operation of the infusion device based on the detected location information.


A method in accordance with another embodiment includes detecting a change in the location information of a therapy management device, comparing the detected change with a stored location information, and executing one or more processes associated with the operation of the therapy management device based on the detected change.


The detected change in the location information may include one of a time zone change, a time standard change, a date change, or combinations thereof.


The one or more processes may include generating a notification associated with the detected change in the location information.


Further, the one or more processes may include modifying one or more programmed time based functions of the therapy management device and which may include one or more of a programmed time based alert, a programmed time based fluid delivery determination; a programmed time based fluid delivery profile, or a programmed time based operational condition of the therapy management device.


In still another aspect, the therapy management device may include one or more of an infusion device or an analyte monitoring unit.


A therapy management system in accordance with still another embodiment of the present disclosure includes an infusion device, and a communication unit operatively coupled to the infusion device over a wireless data network, the communication device configured to transmit a request for synchronization to the infusion device, where the infusion device may be configured to transmit one or more data to the communication unit in response to the received synchronization request.


The wireless data network may be based on one or more of a Bluetooth communication protocol, an RF communication protocol, an infrared communication protocol, a Zigbee communication protocol, an 802.1x communication protocol, or a wireless personal area network such as ANT protocol.


In a further aspect, the wireless data network may include one or more of a wireless local area network, or a WiFi network.


The communication unit may be configured to periodically transmit the synchronization request at a predetermined time interval.


Further, the infusion device may be configured to verify the received synchronization request before transmitting the one or more data to the communication unit.


The transmitted one or more data to the communication unit may be encrypted, and also, the communication unit may be configured to decrypt the received one or more encrypted data.


The transmitted one or more data may include one or more information associated with the stored user profile of the infusion device, an operating parameter of the infusion device, or infusion delivery information.


The communication unit may include one or more of an analyte monitoring unit, a personal digital assistant, a mobile telephone, a computer terminal, a server terminal or an additional infusion device.


A system for communicating with an infusion device in still another embodiment of the present disclosure includes a voice enabled device and an infusion device configured to communicate with the voice enabled device using one or more voice signals.


In one aspect, the voice enabled device may include one or more of a telephone set, a mobile telephone, a voice of IP (Internet Protocol) telephone, a voice enabled computing device, or a voice enabled computer terminal.


The infusion device may be configured to initiate a voice enabled communication to the voice enabled device. For example, the infusion device may be integrated with mobile telephone components.


In one aspect, the voice enabled communication may include a telephone call.


The infusion device may be configured to receive one or more voice commands from the voice enabled device, where the infusion device may be configured to process the one or more voice commands to execute one or more associated functions of the infusion device operation.


The one or more associated functions include a bolus dosage determination, a programmable notification, or a temporarily basal dosage determination.


A method in accordance with yet still another embodiment of the present disclosure includes initiating a voice signal based communication from an infusion device, and transmitting a voice signal associated with the operation of the infusion device.


The method may also include receiving a voice signal based request over a communication network, and executing one or more functions associated with the operation of the infusion device based on the received voice signal based request.


The voice signal based communication may include a telephone call.


A therapy management kit in accordance with still yet another embodiment includes an infusion device including a processing unit configured to perform data processing, and a user interface unit operatively coupled to a processing unit, where the processing unit is configured to detect a location information associated with the infusion device for output to the user interface unit.


The kit may further include a clock unit operatively coupled to the processing unit, where the clock unit is configured to dynamically adjust the location information based on the location of the infusion device.


The clock unit may include an atomic clock.


In a further aspect, the kit may also include a voice enabled device, where the infusion device may be further configured to communicate with the voice enabled device using one or more voice signals.


In one aspect, the voice enabled device may include one or more of a telephone set, a mobile telephone, a voice of IP (Internet Protocol) telephone, a voice enabled computing device, or a voice enabled computer terminal.


The various processes described above including the processes performed by the processor 210 in the software application execution environment in the fluid delivery device 120 as well as any other suitable or similar processing units embodied in the analyte monitoring system 120 and the remote terminal 140, including the processes and routines described in conjunction with FIGS. 3-8, may be embodied as computer programs developed using an object oriented language that allows the modeling of complex systems with modular objects to create abstractions that are representative of real world, physical objects and their interrelationships. The software required to carry out the inventive process, which may be stored in the memory unit 240 (or similar storage devices in the analyte monitoring system 110 or the remote terminal 140) of the processor 210, may be developed by a person of ordinary skill in the art and may include one or more computer program products.


In addition, all references cited above herein, in addition to the background and summary of the invention sections, are hereby incorporated by reference into the detailed description of the preferred embodiments as disclosing alternative embodiments and components.


Various other modifications and alterations in the structure and method of operation of this invention will be apparent to those skilled in the art without departing from the scope and spirit of the invention. Although the invention has been described in connection with specific preferred embodiments, it should be understood that the invention as claimed should not be unduly limited to such specific embodiments. It is intended that the following claims define the scope of the present disclosure and that structures and methods within the scope of these claims and their equivalents be covered thereby.

Claims
  • 1. A method, comprising: transmitting, from a medical device, a request for time information over a communication channel;receiving, at the medical device, a time information in response to the transmitted request;updating data stored in the medical device based on the received time information;measuring, with one or more processors, a resistance value of a medical component associated with the medical device;matching, with the one or more processors, the measured resistance value to a corresponding stored resistance value, the stored resistance value associated with an expiration date of the medical component;determining, with the processor, the expiration date of the medical component based on the received time information and the measured resistance value; andgenerating, with the processor, an output signal based on the determination of the predetermined expiration date.
  • 2. The method of claim 1 wherein the updated stored data includes one or more of a blood glucose measurement value, monitored analyte level data, calibration schedule data, or analyte sensor insertion time data.
  • 3. The method of claim 1 wherein transmitting the request for time information includes automatically transmitting the request for time information upon detection of a time zone change associated with the medical device.
  • 4. The method of claim 1 including receiving confirmation of the received time information.
  • 5. The method of claim 1 wherein the time information includes one or more of a time of day information or date information.
  • 6. The method of claim 1 wherein transmitting the request for time information includes automatically transmitting the request upon detection of an operational condition, said operational condition corresponding to one or more of measuring an analyte level of a patient, monitoring an analyte level of the patient, delivering a medication to the patient, transferring data from the medical device to a secondary device, and powering on the medical device.
  • 7. The method of claim 1, further comprising modifying a preprogrammed time based medication delivery profile based on the received time information.
  • 8. The method of claim 7, further comprising obtaining confirmation of the modification prior to implementing the modification to the preprogrammed time based insulin delivery profile.
  • 9. The method of claim 1 wherein the medical component includes one or more of a blood glucose test strip, an analyte sensor, or an infusion set.
  • 10. The method of claim 1, further comprising: initiating local synchronization between the medical device and a secondary device;verifying the identity of the secondary device;approving synchronization between the medical device and the secondary device; andsynchronizing the medical device with the secondary device.
  • 11. A medical device, comprising: one or more processing units; anda memory for storing instructions which, when executed by the one or more processing units, causes the one or more processing units to transmit a request for time information over a communication channel, receive a time information in response to the transmitted request, update data stored in the medical device based on the received time information, measure a resistance value of a medical component associated with the medical device, match the measured resistance value to a corresponding stored resistance value, the stored resistance value associated with an expiration date of the medical component, determine the expiration date of the medical component based on the received time information and the measured resistance value, and generate an output signal based on the determination of the predetermined expiration date.
  • 12. The medical device of claim 11 wherein the updated stored data includes one or more of a blood glucose measurement value, monitored analyte level data, calibration schedule data, or analyte sensor insertion time data.
  • 13. The medical device of claim 11 wherein the instructions to transmit the request for time information includes instructions to automatically transmit the request for time information upon detection of a time zone change associated with the medical device.
  • 14. The medical device of claim 11 including instructions which, when executed by the one or more processing units, causes the one or more processing units to receive confirmation of the received time information.
  • 15. The medical device of claim 11 wherein the time information includes one or more of a time of day information or date information.
  • 16. The medical device of claim 11 wherein the instructions to transmit the request for time information includes instructions to automatically transmit the request upon detection of an operational condition, said operational condition corresponding to one or more of measuring an analyte level of a patient, monitoring an analyte level of the patient, delivering a medication to the patient, transferring data from the medical device to a secondary device, and powering on the medical device.
  • 17. The medical device of claim 11, further comprising instructions which, when executed by the one or more processing units, causes the one or more processing units to modify a preprogrammed time based medication delivery profile based on the received time information.
  • 18. The medical device of claim 17, further comprising instructions which, when executed by the one or more processing units, causes the one or more processing units to obtain confirmation of the modification prior to implementing the modification to the preprogrammed time based insulin delivery profile.
  • 19. The medical device of claim 11 wherein the medical component includes one or more of a blood glucose test strip, an analyte sensor, or an infusion set.
  • 20. The medical device of claim 11, further comprising instructions which, when executed by the one or more processing units, causes the one or more processing units to initiate local synchronization between the medical device and a secondary device, verify the identity of the secondary device, approve synchronization between the medical device and the secondary device, and synchronize the medical device with the secondary device.
RELATED APPLICATIONS

The present application is a continuation of U.S. patent application Ser. No. 12/031,664 filed Feb. 14, 2008, which claims priority under §35 U.S.C. 119(e) to U.S. provisional patent application No. 60/890,154 filed Feb. 15, 2007, entitled “Device And Method For Automatic Data Acquisition And/Or Detection”, the disclosure of which is incorporated herein by reference for all purposes.

US Referenced Citations (578)
Number Name Date Kind
3581062 Aston May 1971 A
3926760 Allen et al. Dec 1975 A
3949388 Fuller Apr 1976 A
4036749 Anderson Jul 1977 A
4055175 Clemens et al. Oct 1977 A
4129128 McFarlane Dec 1978 A
4245634 Albisser et al. Jan 1981 A
4327725 Cortese et al. May 1982 A
4344438 Schultz Aug 1982 A
4349728 Phillips et al. Sep 1982 A
4373527 Fischell Feb 1983 A
4392849 Petre et al. Jul 1983 A
4425920 Bourland et al. Jan 1984 A
4478976 Goertz et al. Oct 1984 A
4494950 Fischell Jan 1985 A
4509531 Ward Apr 1985 A
4527240 Kvitash Jul 1985 A
4538616 Rogoff Sep 1985 A
4619793 Lee Oct 1986 A
4671288 Gough Jun 1987 A
4703756 Gough et al. Nov 1987 A
4731726 Allen, III Mar 1988 A
4749985 Corsberg Jun 1988 A
4757022 Shults et al. Jul 1988 A
4777953 Ash et al. Oct 1988 A
4779618 Mund et al. Oct 1988 A
4854322 Ash et al. Aug 1989 A
4871351 Feingold Oct 1989 A
4890620 Gough Jan 1990 A
4925268 Iyer et al. May 1990 A
4953552 DeMarzo Sep 1990 A
4986271 Wilkins Jan 1991 A
4995402 Smith et al. Feb 1991 A
5000180 Kuypers et al. Mar 1991 A
5002054 Ash et al. Mar 1991 A
5019974 Beckers May 1991 A
5050612 Matsumura Sep 1991 A
5055171 Peck Oct 1991 A
5068536 Rosenthal Nov 1991 A
5082550 Rishpon et al. Jan 1992 A
5106365 Hernandez Apr 1992 A
5122925 Inpyn Jun 1992 A
5165407 Wilson et al. Nov 1992 A
5246867 Lakowicz et al. Sep 1993 A
5262035 Gregg et al. Nov 1993 A
5262305 Heller et al. Nov 1993 A
5264104 Gregg et al. Nov 1993 A
5264105 Gregg et al. Nov 1993 A
5279294 Anderson et al. Jan 1994 A
5285792 Sjoquist et al. Feb 1994 A
5293877 O'Hara et al. Mar 1994 A
5299571 Mastrototaro Apr 1994 A
5320725 Gregg et al. Jun 1994 A
5322063 Allen et al. Jun 1994 A
5340722 Wolfbeis et al. Aug 1994 A
5342789 Chick et al. Aug 1994 A
5356786 Heller et al. Oct 1994 A
5360404 Novacek et al. Nov 1994 A
5372427 Padovani et al. Dec 1994 A
5379238 Stark Jan 1995 A
5390671 Lord et al. Feb 1995 A
5391250 Cheney, II et al. Feb 1995 A
5408999 Singh et al. Apr 1995 A
5411647 Johnson et al. May 1995 A
5425868 Pedersen Jun 1995 A
5431160 Wilkins Jul 1995 A
5431921 Thombre Jul 1995 A
5462645 Albery et al. Oct 1995 A
5489414 Schreiber et al. Feb 1996 A
5497772 Schulman et al. Mar 1996 A
5507288 Bocker et al. Apr 1996 A
5509410 Hill et al. Apr 1996 A
5514718 Lewis et al. May 1996 A
5531878 Vadgama et al. Jul 1996 A
5568806 Cheney, II et al. Oct 1996 A
5569186 Lord et al. Oct 1996 A
5582184 Erickson et al. Dec 1996 A
5586553 Halili et al. Dec 1996 A
5593852 Heller et al. Jan 1997 A
5609575 Larson et al. Mar 1997 A
5628310 Rao et al. May 1997 A
5653239 Pompei et al. Aug 1997 A
5665222 Heller et al. Sep 1997 A
5673322 Pepe et al. Sep 1997 A
5711001 Bussan et al. Jan 1998 A
5711861 Ward et al. Jan 1998 A
5733259 Valcke et al. Mar 1998 A
5772586 Heinonen et al. Jun 1998 A
5791344 Schulman et al. Aug 1998 A
5899855 Brown May 1999 A
5925021 Castellano et al. Jul 1999 A
5935224 Svancarek et al. Aug 1999 A
5942979 Luppino Aug 1999 A
5957854 Besson et al. Sep 1999 A
5964993 Blubaugh, Jr. et al. Oct 1999 A
5965380 Heller et al. Oct 1999 A
5971922 Arita et al. Oct 1999 A
5995860 Sun et al. Nov 1999 A
6001067 Shults et al. Dec 1999 A
6024699 Surwit et al. Feb 2000 A
6032064 Devlin et al. Feb 2000 A
6049727 Crothall Apr 2000 A
6083710 Heller et al. Jul 2000 A
6088608 Schulman et al. Jul 2000 A
6091976 Pfeiffer et al. Jul 2000 A
6093172 Funderburk et al. Jul 2000 A
6103033 Say et al. Aug 2000 A
6117290 Say et al. Sep 2000 A
6119028 Schulman et al. Sep 2000 A
6120676 Heller et al. Sep 2000 A
6121009 Heller et al. Sep 2000 A
6121611 Lindsay et al. Sep 2000 A
6122351 Schlueter, Jr. et al. Sep 2000 A
6134461 Say et al. Oct 2000 A
6144922 Douglas et al. Nov 2000 A
6162611 Heller et al. Dec 2000 A
6175752 Say et al. Jan 2001 B1
6200265 Walsh et al. Mar 2001 B1
6212416 Ward et al. Apr 2001 B1
6213972 Butterfield et al. Apr 2001 B1
6219574 Cormier et al. Apr 2001 B1
6233471 Berner et al. May 2001 B1
6248067 Causey, III et al. Jun 2001 B1
6275717 Gross et al. Aug 2001 B1
6284478 Heller et al. Sep 2001 B1
6293925 Safabash et al. Sep 2001 B1
6295506 Heinonen et al. Sep 2001 B1
6306104 Cunningham et al. Oct 2001 B1
6309884 Cooper et al. Oct 2001 B1
6329161 Heller et al. Dec 2001 B1
6360888 McIvor et al. Mar 2002 B1
6366794 Moussy et al. Apr 2002 B1
6377828 Chaiken et al. Apr 2002 B1
6379301 Worthington et al. Apr 2002 B1
6424847 Mastrototaro et al. Jul 2002 B1
6427088 Bowman, IV et al. Jul 2002 B1
6440068 Brown et al. Aug 2002 B1
6478736 Mault Nov 2002 B1
6484046 Say et al. Nov 2002 B1
6514718 Heller et al. Feb 2003 B2
6544212 Galley et al. Apr 2003 B2
6551494 Heller et al. Apr 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 Say et al. May 2003 B2
6565509 Say et al. May 2003 B1
6571128 Lebel et al. May 2003 B2
6576101 Heller et al. Jun 2003 B1
6577899 Lebel et al. Jun 2003 B2
6579690 Bonnecaze et al. Jun 2003 B1
6585644 Lebel et al. Jul 2003 B2
6591125 Buse et al. Jul 2003 B1
6595919 Berner et al. Jul 2003 B2
6605200 Mao et al. Aug 2003 B1
6605201 Mao et al. Aug 2003 B1
6607509 Bobroff et al. Aug 2003 B2
6610012 Mault Aug 2003 B2
6633772 Ford et al. Oct 2003 B2
6635014 Starkweather et al. Oct 2003 B2
6648821 Lebel et al. Nov 2003 B2
6654625 Say et al. Nov 2003 B1
6659948 Lebel et al. Dec 2003 B2
6668196 Villegas et al. Dec 2003 B1
6687546 Lebel et al. Feb 2004 B2
6689056 Kilcoyne et al. Feb 2004 B1
6694191 Starkweather et al. Feb 2004 B2
6695860 Ward et al. Feb 2004 B1
6698269 Baber et al. Mar 2004 B2
6702857 Brauker et al. Mar 2004 B2
6733446 Lebel et al. May 2004 B2
6740075 Lebel et al. May 2004 B2
6741877 Shults et al. May 2004 B1
6743635 Neel et al. Jun 2004 B2
6746582 Heller et al. Jun 2004 B2
6758810 Lebel et al. Jul 2004 B2
6770030 Schaupp et al. Aug 2004 B1
6790178 Mault et al. Sep 2004 B1
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
6814844 Bhullar et al. Nov 2004 B2
6862465 Shults et al. Mar 2005 B2
6873268 Lebel et al. Mar 2005 B2
6881551 Heller et al. Apr 2005 B2
6892085 McIvor et al. May 2005 B2
6895263 Shin et al. May 2005 B2
6895265 Silver May 2005 B2
6925393 Kalatz et al. Aug 2005 B1
6931327 Goode, Jr. et al. Aug 2005 B2
6932894 Mao et al. Aug 2005 B2
6936006 Sabra Aug 2005 B2
6950708 Bowman, IV et al. Sep 2005 B2
6958705 Lebel et al. Oct 2005 B2
6968294 Gutta et al. Nov 2005 B2
6971274 Olin Dec 2005 B2
6974437 Lebel et al. Dec 2005 B2
6990366 Say et al. Jan 2006 B2
6997907 Safabash et al. Feb 2006 B2
6998247 Monfre et al. Feb 2006 B2
7003336 Holker et al. Feb 2006 B2
7003340 Say et al. Feb 2006 B2
7003341 Say et al. Feb 2006 B2
7022072 Fox et al. Apr 2006 B2
7024245 Lebel et al. Apr 2006 B2
7025774 Freeman et al. Apr 2006 B2
7029444 Shin et al. Apr 2006 B2
7041068 Freeman et al. May 2006 B2
7052483 Wojcik May 2006 B2
7056302 Douglas Jun 2006 B2
7074307 Simpson et al. Jul 2006 B2
7081195 Simpson et al. Jul 2006 B2
7098803 Mann et al. Aug 2006 B2
7108778 Simpson et al. Sep 2006 B2
7110803 Shults et al. Sep 2006 B2
7113821 Sun et al. Sep 2006 B1
7118667 Lee Oct 2006 B2
7134999 Brauker et al. Nov 2006 B2
7136689 Shults et al. Nov 2006 B2
7171274 Starkweather et al. Jan 2007 B2
7190988 Say et al. Mar 2007 B2
7192450 Brauker et al. Mar 2007 B2
7198606 Boecker et al. Apr 2007 B2
7225535 Feldman et al. Jun 2007 B2
7226978 Tapsak et al. Jun 2007 B2
7267665 Steil et al. Sep 2007 B2
7276029 Goode, Jr. et al. Oct 2007 B2
7299082 Feldman et al. Nov 2007 B2
7310544 Brister et al. Dec 2007 B2
7335294 Heller et al. Feb 2008 B2
7354420 Steil et al. Apr 2008 B2
7364592 Carr-Brendel et al. Apr 2008 B2
7366556 Brister et al. Apr 2008 B2
7379765 Petisce et al. May 2008 B2
7402153 Steil et al. Jul 2008 B2
7424318 Brister et al. Sep 2008 B2
7448996 Khanuja et al. Nov 2008 B2
7460898 Brister et al. Dec 2008 B2
7467003 Brister et al. Dec 2008 B2
7471972 Rhodes et al. Dec 2008 B2
7476827 Bhullar et al. Jan 2009 B1
7494465 Brister et al. Feb 2009 B2
7497827 Brister et al. Mar 2009 B2
7519408 Rasdal et al. Apr 2009 B2
7547281 Hayes et al. Jun 2009 B2
7569030 Lebel et al. Aug 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
7613491 Boock et al. Nov 2009 B2
7615007 Shults et al. Nov 2009 B2
7618369 Hayter et al. Nov 2009 B2
7632228 Brauker 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
7654956 Brister et al. Feb 2010 B2
7657297 Simpson et al. Feb 2010 B2
7711402 Shults et al. May 2010 B2
7713574 Brister et al. May 2010 B2
7715893 Kamath et al. May 2010 B2
20020019022 Dunn et al. Feb 2002 A1
20020042090 Heller et al. Apr 2002 A1
20020053523 Liamos et al. May 2002 A1
20020103499 Perez et al. Aug 2002 A1
20020106709 Potts et al. Aug 2002 A1
20020128594 Das et al. Sep 2002 A1
20020161288 Shin et al. Oct 2002 A1
20020169635 Shillingburg Nov 2002 A1
20030004403 Drinan et al. Jan 2003 A1
20030023317 Brauker et al. Jan 2003 A1
20030032874 Rhodes et al. Feb 2003 A1
20030042137 Mao et al. Mar 2003 A1
20030065308 Lebel et al. Apr 2003 A1
20030100821 Heller et al. May 2003 A1
20030125612 Fox et al. Jul 2003 A1
20030130616 Steil et al. Jul 2003 A1
20030134347 Heller et al. Jul 2003 A1
20030168338 Gao et al. Sep 2003 A1
20030176933 Lebel et al. Sep 2003 A1
20030187338 Say et al. Oct 2003 A1
20030199790 Boecker et al. Oct 2003 A1
20030208113 Mault et al. Nov 2003 A1
20030212317 Kovatchev et al. Nov 2003 A1
20030212379 Bylund et al. Nov 2003 A1
20030216630 Jersey-Willuhn et al. Nov 2003 A1
20030217966 Tapsak et al. Nov 2003 A1
20040010207 Flaherty et al. Jan 2004 A1
20040011671 Shults et al. Jan 2004 A1
20040039298 Abreu Feb 2004 A1
20040040840 Mao et al. Mar 2004 A1
20040045879 Shults et al. Mar 2004 A1
20040064068 DeNuzzio et al. Apr 2004 A1
20040073266 Haefner et al. Apr 2004 A1
20040106858 Say et al. Jun 2004 A1
20040122353 Shahmirian et al. Jun 2004 A1
20040133164 Funderburk et al. Jul 2004 A1
20040138588 Saikley et al. Jul 2004 A1
20040146909 Duong et al. Jul 2004 A1
20040152622 Keith et al. Aug 2004 A1
20040167801 Say et al. Aug 2004 A1
20040171921 Say et al. Sep 2004 A1
20040176672 Silver 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
20040197846 Hockersmith et al. Oct 2004 A1
20040199059 Brauker et al. Oct 2004 A1
20040204687 Mogensen et al. Oct 2004 A1
20040225338 Lebel et al. Nov 2004 A1
20040236200 Say et al. Nov 2004 A1
20040254433 Bandis et al. Dec 2004 A1
20040267300 Mace Dec 2004 A1
20050004439 Shin et al. Jan 2005 A1
20050004494 Perez et al. Jan 2005 A1
20050010269 Lebel et al. Jan 2005 A1
20050027177 Shin et al. Feb 2005 A1
20050031689 Shults et al. Feb 2005 A1
20050038332 Saidara et al. Feb 2005 A1
20050038680 McMahon Feb 2005 A1
20050043598 Goode, Jr. et al. Feb 2005 A1
20050090607 Tapsak et al. Apr 2005 A1
20050096511 Fox et al. May 2005 A1
20050096512 Fox et al. May 2005 A1
20050112169 Brauker et al. May 2005 A1
20050113653 Fox et al. May 2005 A1
20050114068 Chey et al. May 2005 A1
20050121322 Say et al. Jun 2005 A1
20050131346 Douglas Jun 2005 A1
20050143635 Kamath et al. Jun 2005 A1
20050176136 Burd et al. Aug 2005 A1
20050177398 Watanabe et al. Aug 2005 A1
20050182306 Sloan Aug 2005 A1
20050187720 Goode, Jr. et al. Aug 2005 A1
20050192494 Ginsberg Sep 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
20050239154 Feldman et al. Oct 2005 A1
20050241957 Mao et al. Nov 2005 A1
20050245795 Goode, Jr. et al. Nov 2005 A1
20050245799 Brauker et al. Nov 2005 A1
20050245839 Stivoric et al. Nov 2005 A1
20050245904 Estes et al. Nov 2005 A1
20050287620 Heller et al. Dec 2005 A1
20060001538 Kraft et al. Jan 2006 A1
20060004270 Bedard 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
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
20060029177 Cranford, Jr. 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
20060155180 Brister et al. Jul 2006 A1
20060166629 Reggiardo Jul 2006 A1
20060173260 Gaoni et al. Aug 2006 A1
20060173406 Hayes et al. Aug 2006 A1
20060173444 Choy et al. Aug 2006 A1
20060183985 Brister et al. Aug 2006 A1
20060189863 Peyser et al. Aug 2006 A1
20060222566 Brauker et al. Oct 2006 A1
20060224109 Steil et al. Oct 2006 A1
20060229512 Petisce et al. Oct 2006 A1
20060247508 Fennell Nov 2006 A1
20060272652 Stocker et al. Dec 2006 A1
20070016381 Kamath et al. Jan 2007 A1
20070027381 Stafford Feb 2007 A1
20070033074 Nitzan et al. Feb 2007 A1
20070060814 Stafford Mar 2007 A1
20070066873 Kamath et al. Mar 2007 A1
20070071681 Gadkar et al. Mar 2007 A1
20070073129 Shah et al. Mar 2007 A1
20070078320 Stafford Apr 2007 A1
20070078321 Mazza et al. Apr 2007 A1
20070078322 Stafford Apr 2007 A1
20070078323 Reggiardo et al. Apr 2007 A1
20070106135 Sloan et al. May 2007 A1
20070124002 Estes et al. May 2007 A1
20070149875 Ouyang et al. Jun 2007 A1
20070163880 Woo et al. Jul 2007 A1
20070168224 Letzt et al. Jul 2007 A1
20070173706 Neinast et al. Jul 2007 A1
20070173761 Kanderian et al. Jul 2007 A1
20070179349 Hoyme et al. Aug 2007 A1
20070179352 Randlov et al. Aug 2007 A1
20070191701 Feldman et al. Aug 2007 A1
20070203407 Hoss et al. Aug 2007 A1
20070203966 Brauker et al. Aug 2007 A1
20070235331 Simpson et al. Oct 2007 A1
20070249922 Peyser et al. Oct 2007 A1
20080009692 Stafford Jan 2008 A1
20080017522 Heller et al. Jan 2008 A1
20080021666 Goode, Jr. et al. Jan 2008 A1
20080029391 Mao et al. Feb 2008 A1
20080033254 Kamath et al. Feb 2008 A1
20080039702 Hayter et al. Feb 2008 A1
20080045824 Tapsak et al. Feb 2008 A1
20080058625 McGarraugh et al. Mar 2008 A1
20080064937 McGarraugh et al. Mar 2008 A1
20080071156 Brister et al. Mar 2008 A1
20080071157 McGarraugh et al. Mar 2008 A1
20080071158 McGarraugh et al. Mar 2008 A1
20080081977 Hayter et al. Apr 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
20080097289 Steil et al. Apr 2008 A1
20080108942 Brister et al. May 2008 A1
20080154513 Kovatchev et al. Jun 2008 A1
20080167543 Say et al. Jul 2008 A1
20080172205 Breton et al. Jul 2008 A1
20080183060 Steil 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
20080188796 Steil et al. Aug 2008 A1
20080189051 Goode 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
20080208025 Shults et al. Aug 2008 A1
20080208113 Damiano et al. Aug 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
20080242961 Brister et al. Oct 2008 A1
20080255434 Hayter et al. Oct 2008 A1
20080255437 Hayter Oct 2008 A1
20080255808 Hayter Oct 2008 A1
20080256048 Hayter Oct 2008 A1
20080262469 Brister et al. Oct 2008 A1
20080275313 Brister et al. Nov 2008 A1
20080287761 Hayter Nov 2008 A1
20080287762 Hayter Nov 2008 A1
20080287763 Hayter 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
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
20080312841 Hayter Dec 2008 A1
20080312842 Hayter Dec 2008 A1
20080312844 Hayter et al. Dec 2008 A1
20080312845 Hayter et al. Dec 2008 A1
20090005665 Hayter et al. Jan 2009 A1
20090006034 Hayter et al. Jan 2009 A1
20090012379 Goode et al. Jan 2009 A1
20090018424 Kamath et al. Jan 2009 A1
20090018425 Ouyang 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
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
20090055149 Hayter et al. Feb 2009 A1
20090062633 Brauker et al. Mar 2009 A1
20090062635 Brauker et al. Mar 2009 A1
20090062767 VanAntwerp et al. Mar 2009 A1
20090063402 Hayter Mar 2009 A1
20090076356 Simpson et al. Mar 2009 A1
20090076360 Brister et al. Mar 2009 A1
20090076361 Kamath et al. Mar 2009 A1
20090099436 Brister 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
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
20090198118 Hayter et al. Aug 2009 A1
20090203981 Brauker et al. Aug 2009 A1
20090204341 Brauker et al. Aug 2009 A1
20090216103 Brister et al. Aug 2009 A1
20090240120 Mensinger et al. Sep 2009 A1
20090240128 Mensinger et al. Sep 2009 A1
20090240193 Mensinger 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
20090287073 Boock et al. Nov 2009 A1
20090287074 Shults et al. Nov 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
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
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
20100119693 Tapsak et al. May 2010 A1
20100121169 Petisce et al. May 2010 A1
20100219250 Wang Sep 2010 A1
Foreign Referenced Citations (23)
Number Date Country
2399887 Aug 2006 CA
2268483 Jan 2007 CA
0127958 Dec 1984 EP
0320109 Jun 1989 EP
0353328 Feb 1990 EP
0390390 Oct 1990 EP
0396788 Nov 1990 EP
0286118 Jan 1995 EP
1048264 Nov 2000 EP
1669020 Jun 2006 EP
1729128 Dec 2006 EP
1288653 Jun 2011 EP
WO-9625089 Aug 1996 WO
WO-9635370 Nov 1996 WO
WO-0049940 Aug 2000 WO
WO-0059370 Oct 2000 WO
WO-0152935 Jul 2001 WO
WO-0154753 Aug 2001 WO
WO-0216905 Feb 2002 WO
WO-03076893 Sep 2003 WO
WO-03082091 Oct 2003 WO
WO-2006026741 Mar 2006 WO
WO-2006086423 Aug 2006 WO
Non-Patent Literature Citations (24)
Entry
Bennion, N., et al., “Alternate Site Glucose Testing: A Crossover Design”, Diabetes Technology & Therapeutics, vol. 4, No. 1, 2002, pp. 25-33.
Isermann, R., “Supervision, Fault-Detection and Fault-Diagnosis Methods—An Introduction”, Control Engineering Practice, vol. 5, No. 5, 1997, pp. 639-652.
Isermann, R., et al., “Trends in the Application of Model-Based Fault Detection and Diagnosis of Technical Processes”, Control Engineering Practice, vol. 5, No. 5, 1997, pp. 709-719.
Jungheim, K., et al., “Risky Delay of Hypoglycemia Detection by Glucose Monitoring at the Arm”, Diabetes Care, vol. 24, No. 7, 2001, pp. 1303-1304.
Kaplan, S. M., “Wiley Electrical and Electronics Engineering Dictionary”, IEEE Press, 2004, pp. 141, 142, 548, 549.
Lortz, J., et al., “What is Bluetooth? We Explain the Newest Short-Range Connectivity Technology”, Smart Computing Learning Series, Wireless Computing, vol. 8, Issue 5, 2002, pp. 72-74.
McKean, B. D., et al., “A Telemetry-Instrumentation System for Chronically Implanted Glucose and Oxygen Sensors”, IEEE Transactions on Biomedical Engineering, vol. 35, No. 7, 1988, pp. 526-532.
Salehi, C., et al., “A Telemetry-Instrumentation System for Long-Term Implantable Glucose and Oxygen Sensors”, Analytical Letters, vol. 29, No. 13, 1996, pp. 2289-2308.
Shaw, G. W., et al., “In Vitro Testing of a Simply Constructed, Highly Stable Glucose Sensor Suitable for Implantation in Diabetic Patients”, Biosensors & Bioelectronics, vol. 6, 1991, pp. 401-406.
Shichiri, M., et al., “Telemetry Glucose Monitoring Device With Needle-Type Glucose Sensor: A Useful Tool for Blood Glucose Monitoring in Diabetic Individuals”, Diabetes Care, vol. 9, No. 3, 1986, pp. 298-301.
Shults, M. C., et al., “A Telemetry-Instrumentation System for Monitoring Multiple Subcutaneously Implanted Glucose Sensors”, IEEE Transactions on Biomedical Engineering, vol. 41, No. 10, 1994, pp. 937-942.
Updike, S. J., et al., “Principles of Long-Term Fully Implanted Sensors with Emphasis on Radiotelemetric Monitoring of Blood Glucose from Inside a Subcutaneous Foreign Body Capsule (FBC)”, Biosensors in the Body: Continuous in vivo Monitoring, Chapter 4, 1997, pp. 117-137.
Velho, G., et al., “Strategies for Calibrating a Subcutaneous Glucose Sensor”, Biomedica Biochimica Acta, vol. 48, 1989, pp. 957-964.
Chinese Patent Application No. 200880005149.1, Original Language and English Translation of Office Action mailed Jul. 29, 2010.
Chinese Patent Application No. 200880005149.1, Original Language and English Translation of Office Action maled Aug. 17, 2011.
Chinese Patent Application No. 200880005149.1, Original Language and English Translation of Office Action maled Feb. 16, 2012.
PCT Application No. PCT/US2008/054165, International Preliminary Report on Patentability and Written Opinion of the International Searching Authority mailed Aug. 27, 2009.
PCT Application No. PCT/US2008/054165, International Search Report and Written Opinion of the International Searching Authority mailed Jun. 5, 2008.
Russian Patent Application No. 2009134334, Original Language and English Translation of Office Action mailed Feb. 7, 2012.
U.S. Appl. No. 12/031,664, Advisory Action mailed Oct. 19, 2010.
U.S. Appl. No. 12/031,664, Notice of Allowance Oct. 24, 2011.
U.S. Appl. No. 12/031,664, Office Action mailed Aug. 2, 2010.
U.S. Appl. No. 12/031,664, Office Action mailed Feb. 19, 2010.
U.S. Appl. No. 12/031,664, Office Action mailed Mar. 18, 2011.
Related Publications (1)
Number Date Country
20120150556 A1 Jun 2012 US
Provisional Applications (1)
Number Date Country
60890154 Feb 2007 US
Continuations (1)
Number Date Country
Parent 12031664 Feb 2008 US
Child 13400026 US