US 7,901,394 B2Grant
Physiological monitoring device for controlling a medication infusion device
Issue Date:2011-03-08
•16 Claims
•7 Drawing Sheets
Abstract
Methods and apparatuses for calculating and transmitting medication dosage or bolus information are provided. A blood glucose meter receives a test strip with a sample of the user's blood and measures the user's blood glucose level with a sensor. The meter then calculates a bolus amount that is transmitted to a medication infusion pump using a radio frequency transmitter or transceiver. The infusion pump receives the bolus amount data and then delivers a bolus of medication to the user based on the calculated bolus estimate. The meter may also transmit commands to, and be used to remotely control, the infusion pump.
Metadata
Assignee
- Medtronic Minimed, Inc.
Inventors
- Jeffrey R. Ireland
- Cary D. Talbot
- Mark C. Estes
Application Information
Application Number:US 11/849,141
Filing Date:2007-08-31
Priority Date:2002-07-24
Art Unit:3763
Classifications
IPC:
A61M31/00
Patent Drawings (7 sheets)
Description
Cross Reference to Related Applications
[0001] This application claims priority from U.S. Provisional Application No. 60/398,213, filed Jul. 24, 2002. This application is a continuation application of pending U.S. application Ser. No. 10/624,177, filed Jul. 22, 2003, which is incorporated by reference in its entirety.
Field of the Invention
[0002] This invention relates generally to improvements in medical devices, such as patient physiological monitoring systems and medication infusion systems that are used for controlled delivery of medication to a user. More specifically, this invention relates to improved methods and apparatuses for calculating and communicating the quantity or bolus of medication that is to be delivered to the user.
Background
[0003] People with Type 1 diabetes and some with Type 2 diabetes use insulin to control their blood glucose (BG) level. Typically, if a person's BG level is too high, he or she can inject a “bolus” (dose) of insulin to lower his/her BG level to a desired target level. Furthermore, he or she may inject a bolus of insulin in anticipation of ingesting carbohydrates, thus heading off a sharp rise in BG level.
[0004] Various calculations can be used to determine the amount of insulin to inject, and bolus estimation software is available for performing such calculations. These software programs can be used on an electronic computing device, such as a computer, the Internet, a personal digital assistant (PDA), or an insulin delivery device. Insulin delivery devices include infusion pumps, injection pens, and IV meters.
[0005] Some bolus estimation software takes into account an individual's current BG level. Presently, blood glucose can be measured using devices such as a test strip meter, a continuous glucose measurement system, a hospital hemocue, or an automated intermittent blood glucose measurement system. BG measurement devices use various methods, such as a sample of blood, a sensor in contact with a bodily fluid, an optical sensor, an enzymatic sensor, or a fluorescent sensor.
[0006] When the BG measurement device has generated a measurement, it is displayed on the device. Then the user may visually read the BG measurement and physically enter it into an electronic computing device to calculate a bolus estimate. Finally, once the bolus estimate is calculated, the user can inject the insulin bolus, or can program an insulin delivery device to deliver the bolus into his/her body.
[0007] Unfortunately, this process can be cumbersome and subject to transcribing errors—for example, the user may not accurately enter the BG measurement that is displayed on the BG measurement device into the electronic computing device. Thus if the BG measurement is not entered correctly, the bolus estimate may not be accurate. Furthermore, once the bolus estimation calculation is complete, the user may not accurately enter the bolus amount into a programmable infusion device, or the user may read the bolus amount incorrectly and inject the wrong amount of medication.
Summary of the Illustrated Embodiments
[0008] A physiological monitoring device that conducts a bolus estimation calculation is provided. In one aspect, the monitoring device communicates a bolus amount resulting from the bolus estimation calculation to a medication infusion device, which delivers a bolus of medication to a user based on the communication from the monitoring device. The medication infusion device delivers the medication automatically after receiving the communication from the monitoring device.
[0009] In another aspect, the monitoring device comprises a processor and a sensor coupled to the processor and adapted to provide an output signal as a function of a concentration of an analyte in the user. A communication circuit is coupled to the processor. The processor is adapted to calculate an amount of the medication or fluid to be infused into the user's body based upon the sensor output signal, and to cause the monitoring device communication circuit to transmit a set of data indicative of the amount of the fluid to be infused.
[0010] An indicator is coupled to the monitoring device processor and adapted to provide a notification of the following events: the measuring of the output signal produced by the sensor, the calculating of the amount of the fluid, and the transmitting of the set of data by the first communication circuit.
[0011] The medication infusion device comprises a processor and a drive mechanism coupled to the processor and adapted to infuse the fluid into the user's body. A communication circuit is coupled to the processor and adapted to receive the set of data from the monitoring device communication circuit. The processor is adapted to cause the drive mechanism to automatically infuse the fluid into the user in accordance with the set of data.
[0012] In another aspect, the monitoring device communication circuit is a transmitter or a transceiver, and the infusion device communication circuit is a receiver or a transceiver.
[0013] In an alternative embodiment, the monitoring device further comprises a user input device for inputting commands. The monitoring device communication circuit transmits the first set of data in response to a command from the input device.
[0014] In another aspect, the monitoring device processor is further adapted to determine a first amount of time that has elapsed since the sensor provided the output signal and to cause the monitoring device communication circuit to transmit the first set of data if the first amount of time does not exceed a predetermined amount of time.
[0015] In yet another embodiment, the monitoring device further comprises an indicator coupled to the monitoring device processor and adapted to provide a display of the amount of the fluid and a user input device for inputting commands. The monitoring device processor is further adapted to cause the monitoring device communication circuit to transmit the first set of data in response to a first command from the input device.
[0016] In another aspect, the infusion device further comprises a user input device for inputting commands and an indicator coupled to the infusion device processor and adapted to provide a display of the amount of the fluid. An infusion device memory is coupled to the infusion device processor and adapted to store at least two fluid infusion parameters. The infusion device processor is further adapted to retrieve one of the fluid infusion parameters from the memory in response to a command from the input device associated with a selection by the user. The infusion device processor further causes the drive mechanism to infuse the fluid into the user's body in accordance with the first or second fluid infusion parameter.
[0017] In an alternative embodiment, the monitoring device processor is further adapted to cause the monitoring device communication circuit to transmit a first command repeatedly for a plurality of transmissions and the infusion device communication circuit is further adapted to receive the first command. The infusion device processor is further adapted to cause power to the infusion device communication circuit to be cycled whereby the power is removed from the infusion device communication circuit for a first time period and is restored to the infusion device communication circuit for a second time period. The infusion device processor causes the power to the infusion device communication circuit to be restored and the power cycling to be discontinued if the first command has been received.
[0018] In yet another embodiment, the monitoring device sensor is coupled to the monitoring device processor and adapted to provide first and second output signals as a function of first and second quantities of an analyte in the user. The monitoring device processor is adapted to calculate a first amount of the fluid to be infused into the user's body based upon the first output signal and generate a first code associated with the first amount of the fluid. The processor then causes the monitoring device telemetry circuit to transmit a first plurality of transmissions wherein each of the first plurality of transmissions is comprised of a first set of data and the first code, the first set of data being indicative of the first amount of the fluid.
[0019] The monitoring device processor then calculates a second amount of the fluid to be infused into the user's body based upon the second output signal and generates a second code associated with the second amount of the fluid. The processor next causes the monitoring device telemetry circuit to transmit a second plurality of transmissions wherein each of said second plurality of transmissions is comprised of a second set of data and the second code, the second set of data being indicative of the second amount of the fluid.
[0020] The infusion device telemetry circuit is adapted to receive the first and second plurality of transmissions from the monitoring device telemetry circuit. The infusion device processor is adapted to store a first received code, said first received code being the first code or the second code as received from one of the first or second plurality of transmissions. The processor then compares a second received code with the first received code, where the second received code is another of the first or second codes as received from another of the first or second plurality of transmissions. The processor then causes the drive mechanism to apply pressure to the fluid in accordance with the second set of data if the second received code does not equal the first received code.
[0021] In one aspect, the first code is generated by incrementing a counter to provide a first counter value and the second code is generated by incrementing the counter to provide a second counter value. In another aspect, the first code corresponds to a first date and time and the second code corresponds to a second date and time.
[0022] There are additional aspects to the present inventions. It should therefore be understood that the preceding is merely a brief summary of some embodiments and aspects of the present inventions. Additional embodiments and aspects of the present inventions are referenced below. It should further be understood that numerous changes to the disclosed embodiments can be made without departing from the spirit or scope of the inventions. The preceding summary therefore is not meant to limit the scope of the inventions. Rather, the scope of the inventions is to be determined by appended claims and their equivalents.
Brief Description of the Drawings
[0023] FIG. 1 is a perspective view of a blood glucose monitor and an infusion pump in accordance with an embodiment of the present invention.
[0024] FIG. 2 is a simplified block diagram of an infusion pump in accordance with an embodiment of the present invention.
[0025] FIG. 3 a is a block diagram of an RF communication system in the infusion pump in accordance with an embodiment of the present invention.
[0026] FIG. 3 b is a block diagram of an RF communication system in the infusion pump in accordance with another embodiment of the present invention.
[0027] FIG. 4 a is a simplified block diagram of a blood glucose monitor in accordance with an embodiment of the present invention.
[0028] FIG. 4 b is a simplified block diagram of a blood glucose monitor in accordance with another embodiment of the present invention.
[0029] FIG. 5 is a simplified block diagram of a blood glucose monitor in accordance with still another embodiment of the present invention.
Detailed Description of the Preferred Embodiments
[0030] In the following description, reference is made to the accompanying drawings which form a part hereof and which illustrate several embodiments of the present invention. It is understood that other embodiments may be used and structural and operational changes may be made without departing from the scope of the present invention.
[0031] A physiological monitoring device that conducts a bolus estimation calculation is provided. In one aspect, the monitoring device communicates a bolus amount resulting from the bolus estimation calculation to a medication infusion device, which then delivers a bolus of medication to a user based on the communication from the monitoring device. The monitoring device may also be used to control other functions of the medication infusion device based on communications from the monitoring device.
[0032] Referring to FIGS. 1 and 4 a, the monitoring device is a BG test strip meter 10 and the medication infusion device is a medication infusion pump 50, such as for example, an insulin infusion pump. The BG meter 10 receives a test strip 12 with a sample 14 of the user's blood and measures the user's BG level with a sensor. The BG meter 10 then calculates a bolus amount that is transmitted to the infusion pump 50, for example, using a radio frequency (RF) transmitter or transceiver. The infusion pump 50 then delivers a bolus of medication to the user based on the bolus amount data received from the BG meter 10. Transmission of the bolus amount from the BG meter 10 to the infusion pump 50 may eliminate user transcription errors and simplify the use of a bolus estimator.
[0033] In particular embodiments, the physiological monitoring device is the BG meter 10 which includes a test strip receptacle or port 11 for receiving and analyzing the test strip 12 with the sample 14 of the user's blood to obtain a BG measurement. In alternative embodiments, the monitoring device may be a continuous glucose measurement system, a hospital hemocue, or an automated intermittent blood glucose measurement system. For example, the monitoring device may generally be of the type or include features disclosed in U.S. Pat. No. 6,558,320, U.S. Patent Application Publication No. 20020002326, published on Jan. 3, 2003, and U.S. patent application Ser. No. 09/377,472 filed Aug. 19, 1999 and entitled “Telemetered Characteristic Monitor System and Method of Using the Same,” and Ser. No. 09/334,996 filed Jun. 17, 1999 and entitled “Characteristic Monitor with a Characteristic Meter and Method of Using the Same,” which are herein incorporated by reference. Moreover, the monitoring device may use other methods or sensors for measuring the user's BG level, such as a sensor in contact with a body fluid, an optical sensor, an enzymatic sensor, a fluorescent sensor, or a blood sample placed in a receptacle. Some monitoring devices are adapted to be carried by a user during his or her daily activities, and thus, may be implanted within the body of the user, or may be external to the user's body and hand-held, or held in a clothing pocket or attached to the body or clothing by straps, adhesives, fasteners, etc.
[0034] In further alternative embodiments, the monitoring device may use samples from body fluids other than blood, such as interstitial fluid, spinal fluid, saliva, urine, tears, or sweat. Other physiological determining or measuring devices may be used to determine or measure the concentrations or quantities of other characteristics, analytes, or agents in the user, such as hormones, cholesterol, medication concentrations, viral loads (e.g., HIV), lactose, oxygen, pH, heart rate, respiratory rate, etc. which may be used in a bolus estimation algorithm or may be used to identify an alarm condition or record an event.
[0035] Referring again to FIGS. 1 and 4 a, the BG meter 10 includes a bolus estimator 64 that is comprised of software algorithms. Once the BG meter 10 obtains a BG measurement, the bolus estimator 64 uses the measurement data to calculate a bolus amount. The bolus amount data is transmitted to the infusion pump 50 using a radio frequency (RF) transmitter 15, as will be described below. Alternatively, the RF transmitter 15 may be replaced with an RF transceiver 19 (as shown in FIG. 4 b) or 36 (as shown in FIG. 5 ), and the bolus data may be transmitted to the infusion pump 50 using the RF transceiver 19 or 36.
[0036] In the illustrated embodiment, the test strip port 11 and RF transmitter 15 are coupled to a processor 17, which executes programs (including the bolus estimator 64) and controls the BG meter 10. The processor 17 is also connected to a memory 30 for storing programs, history data, user defined information and parameters. The BG meter 10 also includes an indicator or display 16 for providing notifications to the user of the BG measurement, bolus amount information, and messages, such as status, alarms or error messages. In particular embodiments, the display 16 includes a backlight for reading the display 16 in the dark.
[0037] The BG meter 10 includes user input devices comprising one or more housing buttons 18 and 20 for control of the meter 10, such as turning it on or off, reviewing previous BG measurements or bolus amounts, transmitting bolus data to the infusion pump 50, and turning off the transmitter 15 (or transceiver 19 (shown in FIG. 4 b) or 36 (shown in FIG. 5 )) in the BG meter 10 so that it does not send bolus data to the infusion pump 50.
[0038] The BG meter 10 further includes an additional user input device comprising a keypad 28 with one or more keypad buttons 22, 24, and 26 that are dedicated to remotely controlling the infusion pump 50, for example, via the RF transmitter 15 (or RF transceiver 19 (as shown in FIG. 4 b) or 36 (as shown in FIG. 5)), as will be described below. The keypad buttons 22, 24, and 26 may also be used to transmit bolus data to the infusion pump 50 and are labeled ‘S’ for “suspend”, ‘B’ for “bolus”, and ‘ACT’ for “activate.”
[0039] In alternative embodiments, other quantities and arrangements of buttons may be included on the meter 10, and the buttons may be labeled other than as illustrated in FIG. 1 . Alternatively, the keypad buttons 22, 24, and 26 may be omitted, and the housing buttons 18 and 20 may be used to remotely control the infusion pump 50. On the other hand, the housing buttons 18 and 20 may be omitted, and the keypad buttons 22, 24, and 26 may be used to operate the BG meter 10. Additionally, the user may use other methods to input commands with the BG meter 10, such as selecting a menu item, using the display 16 as a touch screen, or pressing multi-function keys.
[0040] In addition to transmitting the bolus amount data to the infusion pump 50, the BG meter 10 also stores the BG measurement and bolus data in the memory 30 of the BG meter 10 for subsequent analysis and review. A history of alarms or error messages generated by the BG meter 10, as well as remote control commands sent to or information received from the infusion pump 50, may also be stored in the memory 30. Further, the user may periodically cause the BG meter 10 to download the stored data through a communication circuit (such as the RF transmitter 15 (or RF transceiver 19 (as shown in FIG. 4 b) or 36 (as shown in FIG. 5)), a cable, or a communication station), directly to a computer 34, or alternatively, over the Internet to a remote server for storage. For example, a connector 32 may be inserted into the test strip port 11 to provide a wired connection to a USB, serial, or other port of the computer 34, and data may be downloaded from the BG meter 10 through the connector 32 to the computer 34. The user or a caregiver (e.g., the user's parent, health care professional, educator) can evaluate the user's therapy by accessing the historical BG measurements or bolus data downloaded from the meter 10.
[0041] Referring now to FIGS. 1 and 2 , the infusion pump 50 regulates the flow of fluid from the pump, through flexible tubing 54, and into an infusion set 56 that is adhered to the user. Infusion sets that may be used as part of an infusion device are described in, but not limited to, U.S. Pat. Nos. 4,723,947; 4,755,173; 5,176,662; 5,584,813; and 6,056,718, which are herein incorporated by reference. The infusion pump 50 may be of the type described in U.S. Pat. Nos. 4,562,751; 4,685,903; 5,080,653; 5,097,122; 5,505,709; 6,248,093; and 6,554,798, which are herein incorporated by reference. Some infusion pumps are adapted to be carried by a user during his or her daily activities, and thus, may be implanted within the body of the user, or may be external to the body of the user and hand-held or held in a clothing pocket or attached to the body or clothing by straps, adhesives, fasteners, etc.
[0042] In alternative embodiments, other devices may be used for delivery or infusion of fluid into a user's body, such as for example, an implantable insulin infusion pump or a system that uses a combination of implantable and external components, an injection pen, an IV meter, etc.
[0043] Referring still to FIGS. 1 and 2 , the infusion pump 50 includes an RF communication system 60 that in turn includes an RF receiver 80, as shown in FIG. 3 a. This allows one-way communication from the BG meter 10 (or other external devices such as a remote programmer) to the infusion pump 50. Alternatively, the RF communication system 60′ may include an RF transceiver 81, as shown in FIG. 3 b, which allows two-way communication between the BG meter 10 and the infusion pump 50.
[0044] The RF communication system 60 communicates with a processor 64 contained in a housing 52 of the infusion pump 50. The processor 64 is used to execute programs and control the infusion pump 50, and is connected to an internal memory device 66 that stores programs, history data, user defined information and parameters. The memory device 66 is a ROM and DRAM, but alternatively, the memory device 66 may include other memory storage devices, such as RAM, EPROM, dynamic storage such as flash memory, energy efficient hard-drive, etc.
[0045] The infusion pump 50 is preferably programmed through a user input device comprising a keypad 58 on the housing 52, or alternatively, by commands received from an RF programmer (not shown) through the RF communication system 60. The infusion pump 50 may also be programmed by commands that are input using the keypad 28 on the BG meter 10 and received from the BG meter 10, for example, through the RF communication system 60, as will be described below. Feedback by the infusion pump 50 on status or programming changes is shown on a display 68, is provided tactilely with a vibration alarm 78 or audibly through a speaker 70 or other sound generation device. The infusion pump 50 may also provide the user with either an audible alarm or a vibration alarm for notification of a low medication reservoir condition or low battery charge. Alarms may start out at a low decibel or vibration level and escalate until acknowledged by the user. In alternative embodiments, the keypad 58 may include other quantities and arrangements of keys than those illustrated in FIG. 1 . Alternatively, the keypad 58 may be omitted, and the display 68 may be used as a touch screen input device. In further alternative embodiments, the keypad 58, display 68, and/or speaker 70 may be omitted, and some or all programming and data transfer may be handled through a communication circuit, i.e. the RF communication system 60.
[0046] The processor 64 is also coupled to a drive mechanism 72 that is connected to a fluid reservoir 74 containing fluid. The processor 64 causes the drive mechanism 72 to deliver the fluid through an outlet 76 in the reservoir 74 and housing 52, and then into the user's body through the tubing 54 and the infusion set 56.
[0047] In particular embodiments, one-way communication is provided from the BG meter 10 to the infusion pump 50. The BG meter 10 includes the RF transmitter 15 (shown in FIG. 4 a), and the infusion pump 50 includes an RF receiver 80 (shown in FIG. 3 a). Alternatively, two-way communication may be provided between the BG meter 10 and the infusion pump 50. The RF transmitter 15 in the BG meter 10 is replaced with an RF transceiver 19 (shown in FIG. 4 b) or 36 (shown in FIG. 5 ), and the RF receiver 80 in the infusion pump 50 is replaced with an RF transceiver 81 (shown in FIG. 3 b).
[0048] The infusion pump 50 provides several programming options, including remote and on-device programming. The infusion pump 50 also can be configured through a communication circuit, such as a cable or communication station, using a computer. Additionally, the infusion pump 50 allows the user to download information in the memory 66 through the communication circuit directly to a computer, or alternatively, over the Internet to a remote server for storage. Further description of a communication station of this general type may be found in U.S. Pat. No. 5,376,070, which is incorporated herein by reference. The user or a caregiver (e.g., the user's parent, health care professional, educator) can evaluate the user's therapy by accessing the historical BG measurements or bolus data downloaded from the BG meter 10 and insulin delivery information downloaded from the pump 50.
[0049] Information may also be downloaded from the infusion pump 50 through the RF communication system 60. Referring to FIG. 3 b, the RF communication system 60′ may include a RF transceiver 81 for transmitting information to and receiving information from external devices. In particular embodiments, an external communication link (not shown) may be connected to a serial, USB, or other port of a computer. Information may be transmitted from the RF transceiver 81 in the infusion pump 50 to an RF transceiver in the external communication link (not shown), which then downloads the information through a wired connection to the computer. During the download process, the communication link may draw power from the computer through the serial, USB, or other port.
[0050] In other embodiments, the connector 32 may be inserted into the test strip port 11′ of the BG meter 10′ to provide a wired connection to a USB, serial, or other port of the computer 34, as shown in FIG. 4 b. Information may be transmitted from the RF transceiver 81 in the infusion pump 50 to the RF transceiver 19 in the BG meter 10′, and may then be downloaded through the connector 32 to the computer 34. The BG meter 10′ merely functions as a “pass through” connection between the infusion pump 50 and the computer 34. During the download process, power may be drawn from a power supply (not shown) for the BG meter 10′ (e.g., a battery), or alternatively, from the USB, serial, or other port of the computer 34.
[0051] Alternatively, information may be transmitted from the RF transceiver 81 in the infusion pump 50 to the RF transceiver 36 in the BG meter 10″, as shown in FIG. 5 . The information may be transmitted from the infusion pump 50 to the BG meter 10″ at a rate higher than can be handled by the meter processor 17″. Accordingly, the BG meter 10″ includes a communications microcontroller or processor 38 with a higher processing speed (e.g., 10 MHz) than the meter processor 17″ with a lower processing speed (e.g., 1-4 MHz). The transmitted information is first processed by the communications processor 38, then processed by the meter processor 17″, and finally downloaded through the connector 32 to the computer 34. Again, the BG meter 10″ merely functions as a “pass through” connection between the infusion pump 50 and the computer 34. In alternative embodiments, information may be transmitted from the infusion pump 50 and stored in the memory 30′ or 30″ of the BG meter 10′ or 10″ for subsequent downloading from the BG meter 10′ or 10″ to the computer 34. In further alternative embodiments, information may be transmitted from the infusion pump 50 through the BG meter to the computer 34 using other modes of communication, such as infrared, cable, ultrasonic, sonic, optical, etc.
[0052] As previously stated, the BG meter 10 analyzes the blood sample 14 on the test strip 12 to calculate a BG measurement. The BG meter 10 next calculates a bolus amount and communicates the bolus amount to the infusion pump 50. The pump 50 then delivers a bolus of the medication into the user based on the bolus amount data received from the BG meter 10. In particular embodiments, the BG meter 10 automatically communicates the bolus amount data to the pump 50 once the BG meter 10 calculates the bolus amount. Alternatively, the BG meter 10 communicates the bolus amount to the pump 50 upon removal of the test strip 12 from the BG meter 10, or in response to an action by the user.
[0053] The BG meter 10 provides notification to the user of several events, including when it is analyzing a blood sample, calculating a bolus amount, and communicating with the pump 50. In particular embodiments, the notification is provided as a status on the display 16. In alternative embodiments, the status is communicated to the user in other ways, such as using one or more light emitting diodes, a vibrator or other tactile device, or one or more audible tones (generated by a speaker, a piezoelectric sound generator or other sound generating device). However, when the BG meter 10 provides continuous or automatic BG measurements, the user is not constantly notified of the status of the calculations and transmissions.
[0054] Optionally, the user can direct the BG meter 10 to calculate a bolus estimate amount and/or provide bolus data to the infusion pump 50. User input devices and methods for inputting commands to cause a bolus estimation calculation to be conducted and to transmit bolus data to the infusion pump 50 include: pressing a button, activating a user interface, touching a screen, selecting a menu item, and entering information about a meal such as carbohydrates to be ingested. The BG meter 10 may also re-transmit the bolus amount data to the pump 50 in response to a user action such as pressing a button, selecting a menu item, holding down a button, aligning the BG meter 10 and infusion pump 50, etc. Alternatively, the BG meter 10 may be notified by the infusion pump 50 to re-transmit the bolus amount data.
[0055] In particular embodiments, the BG meter 10 increments a counter each time a new bolus amount is calculated and communicated to the pump 50. If a previously calculated and transmitted bolus amount is re-transmitted, then the BG meter 10 does not increment the counter. Each transmission from the BG meter 10 to the infusion pump 50 includes the bolus amount and the counter value. When the infusion pump 50 receives the transmission from the BG meter 10, the pump compares the counter in the new transmission to the counter in a previous transmission. If the counter has not incremented, the infusion pump 50 will ignore the new transmission since it is a duplicate of a previously-received communication. Thus, the infusion pump 50 will activate an insulin delivery only once for each calculated bolus amount.
[0056] In alternative embodiments, the BG meter 10 generates a unique code associated with each bolus amount that is communicated to the pump 50. Each transmission from the BG meter 10 to the pump 50 includes the bolus amount and the unique code. The infusion pump 50 stores each code received and ignores any later transmission containing a code that was previously received. In one aspect, the BG meter 10 includes a clock circuit adapted to provide a date and time that may be used to generate the code, or alternatively, the date and time may be used as a counter.
[0057] In some embodiments, the BG meter 10 keeps track of the elapsed time between the point when a BG measurement is obtained and when a bolus amount is communicated to the infusion pump 50. The infusion pump 50 includes a clock circuit adapted to provide a date and time, and thus the pump 50 only delivers medication in a bolus amount received from the BG meter 10 if the BG measurement used in the bolus estimation calculation is sufficiently recent in time. Bolus estimations can be at least partially dependent on the difference between the user's present blood glucose level and a desired target blood glucose level. Since a user's BG level varies over time, using a bolus estimation based on an old BG measurement might be inappropriate for the user.
[0058] A bolus estimation is expired (and will not be used for delivering medication to a user) when the BG measurement is too old to be considered representative of the user's present BG level. Thus the BG meter 10 will not transmit a bolus amount to the infusion pump 50 if 10 minutes or more have elapsed since the BG measurement was taken. Alternative shorter or longer time delays may be used, however, such as 7 minutes, 5 minutes, 4 minutes, 3 minutes, or 2 minutes, etc., as well as 12 minutes, 15 minutes, 20 minutes, 30 minutes, 1 hour, 1½ hour, 2 hours, 2½ hours, 3 hours, 3½ hours, 4 hours, etc. Alternatively, the time required for a BG measurement to expire may be set by the user, a caregiver, a physician, a parent, a guardian, etc. For example, a child's BG level may change more quickly than that of a heavy adult, so the BG meter 10 may be programmed so that BG measurements older than 5 minutes cannot be transmitted to another device. On the other hand, an adult might program the BG meter 10 so that BG measurements expire after 12 minutes.
[0059] Alternatively, the infusion pump 50 is programmed to not use a bolus amount if the BG measurement used in the bolus estimation calculation has expired. The infusion pump 50 keeps track of the elapsed time between the point when a new bolus amount is received from the BG meter 10 and when the bolus amount is used to activate an insulin delivery. For example, the infusion pump 50 may be provided the age of the bolus amount it receives. In other words, the elapsed time between when a BG measurement is collected and when the bolus amount is communicated to the infusion pump 50 is transmitted along with each set of bolus data. The pump then can calculate the current age of the bolus amount by adding the age of the bolus amount at the time it was communicated to the time that has passed since the bolus amount was received. Thus, since the infusion pump 50 knows the age of the bolus amount, the infusion pump 50 can reject bolus amounts that are expired. Alternatively, the infusion pump 50 notifies the user if a bolus amount has been received but is expired, before the bolus amount is used to activate a medication delivery. The user may then choose to suspend or activate the bolus delivery.
[0060] In particular embodiments, the infusion pump processor 64 causes the drive mechanism 72 to deliver or infuse the fluid into the body of the user according to fluid infusion parameters. For example, the pump can deliver the medication in virtually a single dose, i.e., a “normal bolus.” Several minutes may be required to deliver the entire bolus amount depending on other fluid infusion parameters, such as the present basal rate that medication is being delivered, the size of the bolus amount, the delivery location on or in the body, and the maximum rate that the infusion pump 50 can deliver the medication, etc.
[0061] The user alternatively may program a bolus type other than a normal bolus. Other delivery profiles or bolus types can include a SQUARE WAVE™ bolus and a DUAL WAVE™ bolus. When a SQUARE WAVE™ bolus is used, the delivery of the bolus is spread at a constant rate over a time period. When a DUAL WAVE™ bolus is used, the user specifies a portion of the bolus amount to be delivered as a normal bolus, and the remaining portion to be delivered as a SQUARE WAVE™ bolus. Other bolus types or profiles can also be used to deliver the bolus amount.
[0062] Preferably, the infusion pump 50 automatically activates an insulin delivery almost immediately upon receiving a bolus amount communicated from the BG meter 10, assuming the bolus amount has not expired. Alternatively, the bolus amount can be approved by the user before it is used. The bolus amount is displayed, and the user responds by pressing a button, selecting a menu item, touching a screen, etc., before the bolus amount is used for medication delivery. For example, the bolus amount may be displayed on the display 16 of the BG meter 10 and approved by the user before it is transmitted to the infusion pump 50. Alternatively, the bolus amount may be displayed on the display 68 of the infusion pump 50 and approved by the user before the medication is delivered. Additionally, the user may indicate the bolus type before the bolus is delivered. For example, the user may employ the user input devices on the BG meter 10 to indicate the bolus type and any associated parameters (such as the bolus amount, the bolus delivery duration period, the portion of the bolus amount that is to be delivered immediately, the portion of the bolus amount that is to be delivered over the extended bolus delivery duration period, etc.) along with other parameters that are transmitted to the infusion pump 50 when a bolus amount is to be delivered. Alternatively, the user may use the infusion pump 50 to indicate the bolus type and any associated parameters. The bolus amount may be sent from the BG meter 10 to the infusion pump 50 automatically, whereupon the user input device on the pump 50 may be used to select a bolus type before the bolus is delivered. Additionally, the user can specify a default bolus type.
[0063] In some embodiments, the BG meter 10 transmits a bolus amount to the infusion pump 50 using radio frequency (RF) communication. Alternatively, other communication circuits are used, such as infrared (IR), wired, ultrasonic, sonic, optical, etc. Transmissions between the BG meter 10 and the infusion pump 50 may contain unique identifying information associated with the identity of the BG meter 10 and/or the infusion pump 50, such as the BG meter's and/or the infusion pump's serial number, identification number, a password, a code, etc. The identification information may be used to discern between communications that are intended for the respective device (i.e., the BG meter 10 or the pump 50), and those that are not. Alternative identification information or codes can include a password, a bit sequence, a special frequency, timing between communications, etc.
[0064] Preferably, the communication system in the BG meter 10 may be deactivated either automatically or by the user, whereupon the meter will not attempt to communicate with other devices. Thus when a new BG measurement is available, the BG meter 10 will not communicate a bolus amount to another device. For example, the RF transmitter 15 (FIG. 4 a) or the RF transceiver 19 (FIG. 4 b) or 36 (FIG. 5 ) can be deactivated and reactivated by the user. This can be useful, for example, if the BG meter 10 transmits at frequencies that might disrupt an airplane during take-off or landing. In alternative embodiments, other devices may be used to deactivate and reactivate the BG meter 10 communication system. For example, the infusion pump 50 can be used to deactivate the BG meter's communication system.
[0065] Additionally, the BG meter 10 can be programmed to reactivate the communication system after a pre-set duration. When the user deactivates the BG meter's communication system, the user is prompted to enter a duration of time for the communication system to remain deactivated. The communication system will automatically become active at the end of the time period. Alternatively, the user may specify a time of day for the communication system to become active. The user is alerted to review any bolus amounts that were generated while the communication system was deactivated. Then the user can request that they be sent to the infusion pump 50 if desired.
[0066] In accordance with one embodiment, two-way communication is used between the BG meter 10 and the infusion pump 50. The infusion pump 50 sends an acknowledge (ACK) message to the BG meter 10 when it receives a transmission. In particular embodiments, the BG meter 10 will not re-transmit (even if requested by the user) if the BG meter 10 has received an ACK from the infusion pump 50. Alternatively, the infusion pump 50 echoes the bolus amount back to the BG meter 10 and waits for a confirmation from the BG meter 10 before delivering the bolus amount. The user is alerted when communication between the BG meter 10 and infusion pump 50 is activated but not functioning properly.
[0067] The infusion pump 50 preferably uses power cycling to periodically supply power to its communication system 60. The power cycle is the time period that the communication system 60 is off plus the time period that the communication system is on. In some embodiments, the power cycle is 8 seconds in length. Alternatively, shorter or longer power cycles may be used, such as 4 seconds, 2 seconds, or 1 second, etc., as well as 12 seconds, 15 seconds or 20 seconds, etc.
[0068] Additionally, the time period that the communication system 60 is on during each power cycle is preferably 48 milliseconds (ms). Alternatively, the period that the communication system is on during each power cycle can be greater or less than 48 ms, depending on the length of the message to be received, the communication frequency, the speed of the communication system electronics, etc. The BG meter 10 sends repeated signals to the infusion pump 50 for a period longer than the power cycle. Each signal sent from the BG meter 10 to the infusion pump 50 includes a command. The command is preferably short enough to be captured during the on-time of the infusion pump's 50 communication system 60. In accordance with one embodiment, the command is short enough to be captured twice during the infusion pump's 50 communication system 60 on-time.
[0069] The time that the infusion pump's 50 communication system 60 must be on to capture the command from the BG meter 10 is short compared to the power cycle, or alternatively is short compared to a string of information. When the infusion pump 50 receives the command, the pump 50 stops power cycling its communication system 60 and turns the system 60 on continuously. Thus short commands may be used to activate the infusion pump's 50 communication system 60 so that one or more longer strings of information may be received by the pump 50.
[0070] The infusion pump 50 prepares to receive a string of information that is longer than a command and includes a bolus amount. The string of information may further include an elapsed time since the BG measurement was taken, a bolus type, bolus parameters, a counter, a unique identification code, a date, a time, a serial number, and the time elapsed since the bolus amount was calculated, etc.
[0071] The BG meter 10 may transmit a date and time to the infusion pump 50 so that the pump 50 can determine the difference between the BG meter 10 date and time and the pump 50 date and time. Moreover, the pump 50 can reset its clock to correspond to the BG meter 10 clock. Alternatively, the BG meter 10 can use the infusion pump 50 date and time to reset the BG meter 10 clock. In particular embodiments, when the pump 50 acknowledges receipt of information from the BG meter 10, the pump 50 will communicate its current time and date to the meter 10. The meter 10 then resets its clock, if necessary, to correspond to the pump's clock.
[0072] The infusion pump 50 preferably returns to power cycling the communication system 60 after information has been received from the BG meter 10. For example, power cycling may be restored after the pump 50 receives a complete signal containing a bolus amount from the BG meter 10. Alternatively, the infusion pump 50 returns to power cycling at a predetermined period after the signal from the BG meter 10 has stopped, or after the commencement of a signal from the BG meter 10.
[0073] In alternative embodiments there is no longer string of information that follows a command. Rather, the command itself includes all of the information to be sent to the pump, such as the bolus amount, the bolus type and/or a time parameter, serial number, BG meter counter, etc. Thus the pump does not change from its power cycling routine.
[0074] The BG meter 10 is preferably used to control one or more functions of the infusion pump 50. These functions include: bolus delivery (bolus amount, start time, bolus type, duration, maximum bolus amount limit, etc.), basal delivery (profiles, delivery rates, time of day when rates change, maximum basal rate limit, etc.), alarms, user interfaces (turning on or off sound generating devices, vibrator, display, or light, etc.), selection of devices that can communicate with the infusion pump 50, lock-out controls, reservoir seating, reservoir priming, and data download.
[0075] Alternative embodiments of a BG meter 10 include one or more indicators and user input devices, such as audible alarms, vibrators, displays (liquid crystal display (LCD), light emitting diodes (LEDs), touch screen, etc.), sound generation devices, keypads, keyboards, buttons, and voice activated controls, etc. In addition to the pump 50, the BG meter 10 can communicate with other devices, such as a computer, PDA, telephone, central server, Internet hardware device, relay, remote alarm or notification device, and a remote controller, etc. The BG meter 10 uses one or more communication circuits or methods to communicate with these other devices, such as RF, infrared (IR), bluetooth, optical, sound, ultrasonic, and wired, etc.
[0076] The infusion pump 50 indicates its present function or activity, so that a user can monitor the pump's reaction to commands that it has received, for example, from the BG meter 10. Also, the user may override commands that the infusion pump 50 has received from another device. Alternatively, the infusion pump 50 only communicates with a user through another device, such as via the BG meter 10. Examples of functions/activities indicated to the user include: the delivery of a certain basal profile, the completion of delivery to the user of a certain portion of a bolus, the time period remaining for completing a bolus delivery, the suspension of pump 50 operations, the priming or seating of the pump 50, etc. In one embodiment, the infusion pump 50 communicates to the BG meter 10 the pump status or alarms, such as a fluid path occlusion, an electrostatic discharge alarm, a low battery power level, a low reservoir level, etc.
[0077] The user accesses and implements commands using the BG meter 10 through a menu structure shown on the display 16 and navigated by the keypad 28. Alternatively, input devices or other methods are used such as pressing dedicated keys, scribing a command on a screen, touching a touch screen, voice activated commands, etc. Each keystroke on the BG meter 10 is communicated to the infusion pump 50. Alternatively, the BG meter 10 only communicates actionable commands to the infusion pump 50. Thus, the user may press many keystrokes on the BG meter 10 before the BG meter 10 transmits to the pump 50.
[0078] For example, the BG meter 10 does not communicate to the infusion pump 50 until the user has stopped pressing keys that might influence the infusion pump 50 function. Thus for example, the user might conduct a programming session on the BG meter 10 to implement a new basal delivery pattern, enter a new serial number of a new device that the infusion pump 50 should respond to, and program a bolus amount. The BG meter 10 would not initiate a transmission to the infusion pump 50 until the user has completed the programming session.
[0079] The BG meter 10 identifies the end of a programming session when the user inputs a completion command indicating that the session is complete or commanding the BG meter 10 to initiate the transmission. Alternatively, the BG meter 10 communicates at the end of each actionable command. Alternatively still, the BG meter 10 communicates to the infusion pump 50 whenever the user returns to the main menu, or the BG meter 10 waits a specified delay period after the last keystroke to determine that the user has completed the programming session. The specified delay period may be programmable, or may be a preset period such as 10 seconds, 15 seconds, 30 seconds, 1 minute, etc. The BG meter 10 nevertheless will communicate some commands immediately, such as for example, a suspend command (to stop medication delivery), responses to alarms, or starting a new bolus delivery.
[0080] In an alternative embodiment, the meter has a review feature so that the user may scroll through programming steps that are about to be sent to the pump. The user may choose to modify the commands or accept the commands before the meter initiates a transmission to the pump.
[0081] As described above, the infusion pump 50 communicates with various external devices, such as the BG meter 10, using RF communication. Additionally, the infusion pump 50 uses power cycling to periodically supply power to its communication system 60. Referring to FIGS. 3 a and 3b, to facilitate one-way RF communication, the infusion pump 50 includes a processor 64, a RF receiver 80, a RF microcontroller (or RF programmable integrated circuit—(RF PIC)) 82, and an application specific integrated circuit (ASIC) 84. Alternatively, to facilitate two-way RF communication, the RF receiver 80 may be replaced with an RF transceiver 81, as shown in FIG. 3 b. The RF PIC 82 holds a 7-byte word, although in alternative embodiments, it may hold other lengths of data. The processor communicates with the RF PIC 82 and the ASIC 84 using synchronous peripheral interfaces (SPI interfaces).
[0082] The RF receiver 80 or RF transceiver 81 receives and demodulates RF signals, extracts a data packet from the RF signal, and passes the data packet to the RF PIC 82. The RF PIC 82 accepts and decodes the data packet and checks for format. If the format of the data packet is valid, the RF PIC 82 sends an interrupt signal to the ASIC 84. When the ASIC 84 receives the interrupt signal from the RF PIC 82, the ASIC 84 sends an interrupt to the processor 64, triggering the processor 64 to notify the RF PIC 82 to pass the contents of its buffer to the processor 64.
[0083] The processor 64 acquires the decoded data packet from the RF PIC 82 and evaluates the content, which may include a command or information to be stored. In response to some data packets, the processor 64 may send a command to the ASIC 84 to change the power conditions on the RF receiver 80 or RF transceiver 81. The processor 64 also processes the commands and data received from the BG meter 10, which may result in controlling functions on the infusion pump 50. One of the main tasks for the ASIC 84 is to enable and disable power on the RF receiver 80 or RF transceiver 81. Generally, the ASIC 84 cycles the power on the RF receiver 80 or the RF transceiver 81 to save energy. If commanded by the processor 64, however, the ASIC 84 will enable the RF receiver 80 or the RF transceiver 81 to be powered continuously.
[0084] Each RF transmission sent to the infusion pump 50 preferably includes an RF signal header followed by a command packet or an information packet. Since the infusion pump's RF receiver 80 or RF transceiver 81 is likely to wake up in the middle of a command packet, the RF signal header at the start of each transmission helps the infusion pump 50 to synchronize its data sampling and identify the first byte of a new command packet or information packet. The RF signal header is preferably the same for each transmission, and is transmitted at the start of each RF transmission.
[0085] The RF signal header may include two parts: a preamble and a start signature. The preamble is a series of pulses used to train the infusion pump's digital signal sampling, and allows the infusion pump 50 to synchronize its pulse sampling with the pulse bits in the new transmission. The start signature notifies the RF PIC 82 when the first byte of a new packet is starting. Alternatively, the RF signal header may include other data, or the RF signal header may be omitted.
[0086] The command packets are 7 bytes in length, and information packets are 71 bytes in length. Alternative embodiments incorporate command packets and information packets of different lengths. The last byte of every command or information packet is an 8-bit cyclic redundancy check (CRC) calculated on all the preceding bytes in the packet. Before a command or information packet is transmitted to the infusion pump 50, it is preferably encoded by the BG meter 10 using a DC balanced encoding scheme, which translates 4 bits of data into 6 for transmission as follows:
[0087]
| HEX | DC | |
|---|---|---|
| 0 | 010101 | |
| 1 | 110001 | |
| 2 | 110010 | |
| 3 | 100011 | |
| 4 | 110100 | |
| 5 | 100101 | |
| 6 | 100110 | |
| 7 | 010110 | |
| 8 | 011010 | |
| 9 | 011001 | |
| A | 101010 | |
| B | 001011 | |
| C | 101100 | |
| D | 001101 | |
| E | 001110 | |
| F | 011100 | |
[0088] The result of the encoding is that the 7-byte command packets require transmission of 11 bytes and the 71-byte information packets require transmission of 107 bytes. Upon receipt of the 1-byte or 107-byte packets from the BG meter 10, the RF PIC 82 in the infusion pump 50 decodes the packet into the 7-byte command packet or the 71-byte information packet. The processor 64 checks all packets for valid identification of the infusion pump 50 (e.g., identification or serial number) and CRC. If the infusion pump 50 identification is not valid, the packet is ignored. If the CRC of the first command packet is not valid, the command is ignored. Otherwise, the processor 64 may send a negative acknowledge (NAK) response to any packet with an invalid CRC.
[0089] Information packets (71 bytes) are much larger than command packets (7 bytes), and cannot be stored in the RF PIC 82, and thus, cannot be used to “wake up” the pump. Instead, a command packet must be sent to the infusion pump 50 to turn on the pump's RF receiver 80 or RF transceiver 81 and prepare the pump 50 to receive an information packet. While power to the pump's RF receiver 80 or RF transceiver 81 is being cycled, a command packet is repeatedly transmitted from the meter 10 to the pump 50 to activate the pump's RF receiver 80 or RF transceiver 81. If an RF signal (i.e. including the first command packet) is present when the pump's RF receiver 80 or RF transceiver 81 comes on, the pump 50 will attempt to store the contents of the signal in the RF PIC 82.
[0090] The processor 64 will verify whether the content of the signal is a valid command packet. If the command packet is valid, then the infusion pump 50 will stop power cycling and power the RF receiver 80 and RF transceiver 81 continuously. Only the first command packet must be transmitted repeatedly. After the RF receiver 80 or RF transceiver 81 is on full-time, other command packets or an information packet can be sent to the infusion pump 50.
[0091] The pump 50 preferably recognizes two categories of command packets: remote control or normal bolus commands and bolus estimation or amount commands. Remote control or normal bolus commands directly control the pump's insulin bolus delivery. Bolus estimation or amount commands prepare the pump 50 to receive an information packet containing a new bolus estimate amount.
[0092] The pump 50 may receive a normal bolus command from the BG meter 10 or a remote programmer associated with the pump 50. The bolus command preferably includes a type code indicating the type of device transmitting the message (e.g., the BG meter 10 or the remote programmer), unique identifying information about the pump 50 (e.g., serial number, identification number, password, or the like), a key code indicating which bolus command button has been pressed (e.g., button “S” 22, button “B” 24, or button “ACT” 26 on the BG meter 10), and a counter indicating the number of times that the button has been pressed. In alternative embodiments, the bolus command may include other information and/or omit some of this data. When the pump 50 receives the bolus command, the processor 64 filters the command to discern the counter value so that the pump 50 can respond to the number of times the user has pressed the button to adjust a bolus.
[0093] The pump 50 may also receive a bolus estimation command from the BG meter 10. The bolus estimation command is transmitted to the pump 50 to prepare the pump 50 to receive an information packet containing a new bolus estimate amount from the BG meter 10. The bolus estimation command preferably includes a type code indicating the type of device transmitting the message (e.g., the BG meter 10), unique identifying information about the pump 50 (e.g., serial number, identification number, password, or the like), and a key code indicating that a new bolus estimate amount is about to be transmitted. In alternative embodiments, the bolus estimation command may include other information and/or omit some of this data.
[0094] In response to RF transmissions, the pump 50 typically sends an acknowledge (ACK) response. However, in particular embodiments, the BG meter 10 does not include an RF receiver, and the pump 50 does not include an RF transmitter, and thus, the pump 50 does not send an ACK response if the type code in the command (e.g., bolus or BG measurement command) indicates that the device transmitting the message is the BG meter 10. In alternative embodiments, both the BG meter 10 and the pump 50 may include an RF transceiver (i.e. transceiver 19 (shown in FIG. 4( b)) or 36 (shown in FIG. 5) in the BG meter 10′ or 10″, and transceiver 81 (shown in FIG. 3( b)) in the infusion pump 50), and thus, the pump 50 may send an ACK response to the BG meter 10.
[0095] When the infusion pump 50 receives a command packet from the BG meter 10, the processor 64 will send a data packet through the ASIC 84, commanding the RF receiver 80 or RF transceiver 81 to remain on full-time for a specified number of minutes, to receive other command packets or an information packet. The RF receiver 80 or RF transceiver 81 may return to power cycling after the information packet has been received, a certain period of time after receiving a command (in the event that the anticipated information packet does not arrive), or after the battery in the infusion pump 50 has been removed and replaced.
[0096] In an alternative embodiment, the BG meter 10 transmits only normal bolus commands and does not transmit the bolus estimation or amount commands. However, the BG meter 10 transmits the normal bolus commands as a series of commands over a predetermined time period, and this collectively approximates a bolus estimation or amount. The BG meter 10 accomplishes this by converting bolus estimation data into the series of normal bolus commands. Thus by doing so, for example, the SQUARE WAVE™ bolus can be approximated by a series of normal bolus commands transmitted over a predetermined time period that corresponds to the SQUARE WAVE™ bolus time period.
[0097] Generally, the infusion pump's RF PIC 82 remains in receive mode unless it has received a command from the processor 64 to transmit, in which case it switches to transmit mode until the transmission is complete. Once the data has been transmitted, the RF PIC 82 automatically returns to receive mode.
[0098] Thus according to certain embodiments, there are disclosed methods and apparatuses relating to a physiological monitoring device that conducts a bolus estimation calculation. The monitoring device communicates a bolus amount resulting from the bolus estimation calculation to a medication infusion device, which delivers a bolus of medication to a user based on the communication from the monitoring device. The monitoring device may also be used to control other functions of the medication infusion device based on communications from the monitoring device.
[0099] While the description above refers to particular embodiments of the present invention, it will be understood that many modifications may be made without departing from the spirit thereof. The claims are intended to cover such modifications as would fall within the true scope and spirit of the present invention. The presently disclosed embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the claims rather than the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.
Claims
What is claimed is:
1. A method of infusing a fluid into a body of a user comprising:
operating a physiological monitoring device carried on the exterior of the body of the user, to perform the operations of:
measuring an output signal produced by a sensor, the output signal being a function of a concentration of an analyte in the user;
determining a first amount of time that has elapsed since the sensor provided the output signal;
determining whether the first amount of time exceeds a predetermined amount of time; and, if the first amount of time does not exceed the predetermined amount of time,
calculating an amount of the fluid to be infused into the user's body based upon the output signal; and
transmitting a first set of data with a first communication circuit enclosed within a first housing of the physiological monitoring device, the first set of data being indicative of the amount of the fluid to be infused, the first set of data further including an identifier associated with the amount of fluid to be infused;
wherein the amount of fluid to be infused into the user's body based upon the output signal is not calculated if the first amount of time exceeds the predetermined amount of time; and
operating a medication infusion device carried on the exterior of the body of the user, to perform the operations of:
receiving the first set of data with a second communication circuit enclosed within a second housing of the medication infusion device carried on the exterior of the body of the user;
verifying the identifier to ensure the amount of fluid to be infused has not already been administered; and
activating a drive mechanism to infuse the fluid in accordance with the first set of data.
2. The method of claim 1, wherein the drive mechanism is activated automatically after receipt of the first set of data by the second communication circuit.
3. The method of claim 1, wherein the sensor of the physiological monitoring device is a blood glucose test strip meter, wherein said measuring includes analyzing a test strip exposed to a discrete sample of the analyte of the user to prove a discrete measurement of the analyte in the user, and wherein the drive mechanism is an insulin infusion pump drive mechanism.
4. The method of claim 3, wherein the first communication circuit includes one of a transmitter and a transceiver and wherein the second communication circuit includes one of a receiver and a transceiver.
5. The method of claim 1 further comprising operating the physiological monitoring device to perform the operation of providing a notification of at least one event of the group consisting of: the measuring of the output signal produced by the sensor, the calculating of the amount of the fluid, and the transmitting of the first set of data by the first communication circuit.
6. The method of claim 5 wherein the notification is provided using at least one of a vibration alarm, a sound generation device, a panel adapted to display text, and a LED.
7. The method of claim 1 further comprising operating the physiological monitoring device to perform the operation of providing a notification of the completion of at least one event of the group consisting of: the measuring of the output signal produced by the sensor, the calculating of the amount of the fluid, and the transmitting of the first set of data by the first communication circuit.
8. The method of claim 1 further comprising operating the physiological monitoring device to perform the operation of inputting a command with a user input device, wherein the first set of data is transmitted in response to the command.
9. The method of claim 1 further comprising operating the physiological monitoring device to perform the operation of inputting a command with a user input device, wherein the drive mechanism is activated to infuse the fluid in accordance with the first set of data in response to the command.
10. The method of claim 1 wherein the first set of data is further indicative of at least one of a medication delivery profile, an elapsed time since the output signal was provided, and an identification value associated with the identification of the infusion device.
11. The method of claim 1 further comprising: operating the physiological monitoring device to perform the operations of: inputting a command with a user input device; and transmitting the command with the first communication circuit enclosed within the first housing of the physiological monitoring device; and operating the medication infusion device to perform the operations of: receiving the command with the second communication circuit enclosed within the second housing of the medication infusion device; and controlling the medication infusion device in accordance with the command.
12. The method of claim 11 wherein the command for controlling the medication infusion device comprises one of a medication delivery start time, a medication delivery profile, a medication delivery rate, a medication delivery amount, a cessation of a medication delivery, an activation of an alarm, a cessation of an alarm, a display of a text message, and a download of data.
13. The method of claim 1 further comprising: operating the medication infusion device to perform the operation of transmitting a second set of data indicative of an infusion device status; and operating the physiological monitoring device to perform the operations of: receiving the second set of data with the first communication circuit enclosed within the first housing of the physiological monitoring device; and displaying the infusion device status in accordance with the second set of data.
14. The method of claim 1, wherein the identifier is based on a counter, the counter being incremented for each calculation of an amount of fluid to be infused, the medication infusion device comparing a received counter with a previous transmission counter to ensure an amount of fluid is not administered a second time.
15. The method of claim 1, wherein the identifier of the first set of data is a unique code, the medication infusion device storing the unique code so stored unique codes can be compared to subsequently received unique codes to ensure an amount of fluid is not administered a second time.
16. The method of claim 15, wherein the unique code is generated based on a date and time.
Patent Citations (284)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3631847(A) | 1972-01-01 | Hobbs, II | Applicant |
| US4270532(A) | 1981-06-01 | Franetzki et al. | Applicant |
| US4282872(A) | 1981-08-01 | Franetzki et al. | Applicant |
| US4373527(A) | 1983-02-01 | Fischell | Applicant |
| US4392849(A) | 1983-07-01 | Petre et al. | Applicant |
| US4395259(A) | 1983-07-01 | Prestele et al. | Applicant |
| US4433072(A) | 1984-02-01 | Pusineri et al. | Applicant |
| US4443218(A) | 1984-04-01 | DeCant, Jr. et al. | Applicant |
| US4469481(A) | 1984-09-01 | Kobayashi | Applicant |
| US4475901(A) | 1984-10-01 | Kraegen et al. | Applicant |
| US4494950(A) | 1985-01-01 | Fischell | Applicant |
| US4529401(A) | 1985-07-01 | Leslie et al. | Applicant |
| US4542532(A) | 1985-09-01 | McQuilkin | Applicant |
| US4550731(A) | 1985-11-01 | Batina et al. | Applicant |
| US4559037(A) | 1985-12-01 | Franetzki et al. | Applicant |
| US4562751(A) | 1986-01-01 | Nason et al. | Applicant |
| US4671288(A) | 1987-06-01 | Gough | Applicant |
| US4678408(A) | 1987-07-01 | Nason et al. | Applicant |
| US4685903(A) | 1987-08-01 | Cable et al. | Applicant |
| US4696671(A) | 1987-09-01 | Epstein et al. | Applicant |
| US4703756(A) | 1987-11-01 | Gough et al. | Examiner |
| US4731051(A) | 1988-03-01 | Fischell | Applicant |
| US4731726(A) | 1988-03-01 | Allen, III | Applicant |
| US4781798(A) | 1988-11-01 | Gough | Applicant |
| US4803625(A) | 1989-02-01 | Fu et al. | Applicant |
| US4809697(A) | 1989-03-01 | Causey, III et al. | Applicant |
| US4826810(A) | 1989-05-01 | Aoki | Applicant |
| US4865584(A) | 1989-09-01 | Epstein et al. | Applicant |
| US4871351(A) | 1989-10-01 | Feingold | Examiner |
| US4898578(A) | 1990-02-01 | Rubalcaba, Jr. | Applicant |
| US4935105(A) | 1990-06-01 | Churchouse | Applicant |
| US4953552(A) | 1990-09-01 | DeMarzo | Applicant |
| US5019974(A) | 1991-05-01 | Beckers | Applicant |
| US5034004(A) | 1991-07-01 | Crankshaw | Applicant |
| US5050612(A) | 1991-09-01 | Matsumura | Applicant |
| US5078683(A) | 1992-01-01 | Sancoff et al. | Applicant |
| US5080653(A) | 1992-01-01 | Voss et al. | Applicant |
| US5097122(A) | 1992-03-01 | Colman et al. | Applicant |
| US5100380(A) | 1992-03-01 | Epstein et al. | Applicant |
| US5101814(A) | 1992-04-01 | Palti | Applicant |
| US5108819(A) | 1992-04-01 | Heller et al. | Applicant |
| US5113869(A) | 1992-05-01 | Nappholz et al. | Applicant |
| US5153827(A) | 1992-10-01 | Coutre et al. | Applicant |
| US5165407(A) | 1992-11-01 | Wilson et al. | Applicant |
| US5211626(A) | 1993-05-01 | Frank et al. | Applicant |
| US5216597(A) | 1993-06-01 | Beckers | Applicant |
| US5262035(A) | 1993-11-01 | Gregg et al. | Applicant |
| US5262305(A) | 1993-11-01 | Heller et al. | Applicant |
| US5264104(A) | 1993-11-01 | Gregg et al. | Applicant |
| US5264105(A) | 1993-11-01 | Gregg et al. | Applicant |
| US5266013(A) | 1993-11-01 | Aubert et al. | Applicant |
| US5284140(A) | 1994-02-01 | Allen et al. | Applicant |
| US5299571(A) | 1994-04-01 | Mastrototaro | Applicant |
| US5307263(A) | 1994-04-01 | Brown | Applicant |
| US5317506(A) | 1994-05-01 | Coutre et al. | Applicant |
| US5319363(A) | 1994-06-01 | Welch et al. | Applicant |
| US5320725(A) | 1994-06-01 | Gregg et al. | Applicant |
| US5322063(A) | 1994-06-01 | Allen et al. | Applicant |
| US5338157(A) | 1994-08-01 | Blomquist | Applicant |
| US5339821(A) | 1994-08-01 | Fujimoto | Applicant |
| US5341291(A) | 1994-08-01 | Roizen et al. | Applicant |
| US5350411(A) | 1994-09-01 | Ryan et al. | Applicant |
| US5356786(A) | 1994-10-01 | Heller et al. | Applicant |
| US5357427(A) | 1994-10-01 | Langen et al. | Applicant |
| US5364346(A) | 1994-11-01 | Schrezenmeir | Applicant |
| US5368562(A) | 1994-11-01 | Blomquist et al. | Applicant |
| US5370622(A) | 1994-12-01 | Livingston | Applicant |
| US5371687(A) | 1994-12-01 | Holmes, II et al. | Applicant |
| US5376070(A) | 1994-12-01 | Purvis et al. | Applicant |
| US5390671(A) | 1995-02-01 | Lord et al. | Applicant |
| US5391250(A) | 1995-02-01 | Cheney, II et al. | Applicant |
| US5403700(A) | 1995-04-01 | Heller et al. | Applicant |
| US5411647(A) | 1995-05-01 | Johnson et al. | Applicant |
| US5417222(A) | 1995-05-01 | Dempsey et al. | Applicant |
| US5429602(A) | 1995-07-01 | Hauser | Applicant |
| US5437634(A) | 1995-08-01 | Amano | Applicant |
| US5464392(A) | 1995-11-01 | Epstein et al. | Applicant |
| US5472317(A) | 1995-12-01 | Field et al. | Applicant |
| US5478211(A) | 1995-12-01 | Dominiak et al. | Applicant |
| US5482446(A) | 1996-01-01 | Williamson et al. | Applicant |
| US5482473(A) | 1996-01-01 | Lord et al. | Applicant |
| US5485408(A) | 1996-01-01 | Blomquist et al. | Applicant |
| US5497772(A) | 1996-03-01 | Schulman et al. | Applicant |
| US5499243(A) | 1996-03-01 | Hall | Applicant |
| US5507288(A) | 1996-04-01 | Bocker et al. | Applicant |
| US5543326(A) | 1996-08-01 | Heller et al. | Applicant |
| US5545191(A) | 1996-08-01 | Mann et al. | Applicant |
| US5558640(A) | 1996-09-01 | Pfeiler et al. | Applicant |
| US5569186(A) | 1996-10-01 | Lord et al. | Applicant |
| US5569187(A) | 1996-10-01 | Kaiser | Applicant |
| US5573506(A) | 1996-11-01 | Vasko | Applicant |
| US5582593(A) | 1996-12-01 | Hultman | Applicant |
| US5584814(A) | 1996-12-01 | Schuster et al. | Applicant |
| US5586553(A) | 1996-12-01 | Halili et al. | Applicant |
| US5593390(A) | 1997-01-01 | Castellano et al. | Applicant |
| US5593852(A) | 1997-01-01 | Heller et al. | Applicant |
| US5594638(A) | 1997-01-01 | Iliff | Applicant |
| US5609060(A) | 1997-03-01 | Dent | Applicant |
| US5609575(A) | 1997-03-01 | Larson et al. | Applicant |
| US5616124(A) | 1997-04-01 | Hague et al. | Applicant |
| US5620312(A) | 1997-04-01 | Hyman et al. | Applicant |
| US5626144(A) | 1997-05-01 | Tackland et al. | Applicant |
| US5630710(A) | 1997-05-01 | Tune et al. | Applicant |
| US5643212(A) | 1997-07-01 | Coutre et al. | Applicant |
| US5647853(A) | 1997-07-01 | Feldmann et al. | Applicant |
| US5660163(A) | 1997-08-01 | Schulman et al. | Applicant |
| US5660176(A) | 1997-08-01 | Iliff | Applicant |
| US5665065(A) | 1997-09-01 | Colman et al. | Applicant |
| US5665222(A) | 1997-09-01 | Heller et al. | Applicant |
| US5681285(A) | 1997-10-01 | Ford et al. | Applicant |
| US5685844(A) | 1997-11-01 | Marttila | Applicant |
| US5687734(A) | 1997-11-01 | Dempsey et al. | Applicant |
| US5704366(A) | 1998-01-01 | Tacklind et al. | Applicant |
| US5713856(A) | 1998-02-01 | Eggers et al. | Applicant |
| US5748103(A) | 1998-05-01 | Flach et al. | Applicant |
| US5750926(A) | 1998-05-01 | Schulman et al. | Applicant |
| US5764159(A) | 1998-06-01 | Neftel | Applicant |
| US5772635(A) | 1998-06-01 | Dastur et al. | Applicant |
| US5777060(A) | 1998-07-01 | Van Antwerp | Applicant |
| US5779665(A) | 1998-07-01 | Mastrototaro et al. | Applicant |
| US5786439(A) | 1998-07-01 | Van Antwerp et al. | Applicant |
| US5788669(A) | 1998-08-01 | Peterson | Applicant |
| US5791344(A) | 1998-08-01 | Schulman et al. | Applicant |
| US5807336(A) | 1998-09-01 | Russo et al. | Applicant |
| US5814015(A) | 1998-09-01 | Gargano et al. | Applicant |
| US5832448(A) | 1998-11-01 | Brown | Applicant |
| US5840020(A) | 1998-11-01 | Heinonen et al. | Applicant |
| US5840026(A) | 1998-11-01 | Uber, III et al. | Applicant |
| US5861018(A) | 1999-01-01 | Feierbach | Applicant |
| US5868669(A) | 1999-02-01 | Iliff | Applicant |
| US5871465(A) | 1999-02-01 | Vasko | Applicant |
| US5879163(A) | 1999-03-01 | Brown et al. | Applicant |
| US5885245(A) | 1999-03-01 | Lynch et al. | Applicant |
| US5897493(A) | 1999-04-01 | Brown | Applicant |
| US5899855(A) | 1999-05-01 | Brown et al. | Applicant |
| US5904708(A) | 1999-05-01 | Goedeke | Applicant |
| US5913310(A) | 1999-06-01 | Brown | Applicant |
| US5917346(A) | 1999-06-01 | Gord et al. | Applicant |
| US5918603(A) | 1999-07-01 | Brown | Applicant |
| US5925021(A) | 1999-07-01 | Castellano et al. | Applicant |
| US5933136(A) | 1999-08-01 | Brown | Applicant |
| US5935099(A) | 1999-08-01 | Peterson et al. | Applicant |
| US5940801(A) | 1999-08-01 | Brown | Applicant |
| US5951521(A) | 1999-09-01 | Mastrototaro et al. | Applicant |
| US5956501(A) | 1999-09-01 | Brown | Applicant |
| US5960403(A) | 1999-09-01 | Brown | Applicant |
| US5961451(A) | 1999-10-01 | Reber et al. | Applicant |
| US5965380(A) | 1999-10-01 | Heller et al. | Applicant |
| US5972199(A) | 1999-10-01 | Heller et al. | Applicant |
| US5997476(A) | 1999-12-01 | Brown | Applicant |
| US5999848(A) | 1999-12-01 | Gord et al. | Applicant |
| US5999849(A) | 1999-12-01 | Gord et al. | Applicant |
| US6009339(A) | 1999-12-01 | Bentsen et al. | Applicant |
| US6032119(A) | 2000-02-01 | Brown et al. | Applicant |
| US6043437(A) | 2000-03-01 | Schulman et al. | Applicant |
| US6067474(A) | 2000-05-01 | Schulman et al. | Applicant |
| US6081736(A) | 2000-06-01 | Colvin et al. | Applicant |
| US6083710(A) | 2000-07-01 | Heller et al. | Applicant |
| US6088608(A) | 2000-07-01 | Schulman et al. | Applicant |
| US6101478(A) | 2000-08-01 | Brown | Applicant |
| US6103033(A) | 2000-08-01 | Say et al. | Applicant |
| US6119028(A) | 2000-09-01 | Schulman et al. | Applicant |
| US6120676(A) | 2000-09-01 | Heller et al. | Applicant |
| US6121009(A) | 2000-09-01 | Heller et al. | Applicant |
| US6134461(A) | 2000-10-01 | Say et al. | Applicant |
| US6135949(A) | 2000-10-01 | Russo et al. | Applicant |
| US6142008(A) | 2000-11-01 | Cole et al. | Applicant |
| US6143164(A) | 2000-11-01 | Heller et al. | Applicant |
| US6162611(A) | 2000-12-01 | Heller et al. | Applicant |
| US6171276(B1) | 2001-01-01 | Lippe et al. | Applicant |
| US6175752(B1) | 2001-01-01 | Say et al. | Applicant |
| US6246992(B1) | 2001-06-01 | Brown | Applicant |
| US6248067(B1) | 2001-06-01 | Causey et al. | Applicant |
| US6250309(B1) | 2001-06-01 | Krichen et al. | Applicant |
| US6254586(B1) | 2001-07-01 | Mann et al. | Applicant |
| US6259937(B1) | 2001-07-01 | Schulman et al. | Applicant |
| US6269340(B1) | 2001-07-01 | Ford et al. | Applicant |
| US6270478(B1) | 2001-08-01 | Mernoe | Applicant |
| US6270481(B1) | 2001-08-01 | Mason et al. | Applicant |
| US6295506(B1) | 2001-09-01 | Heinonen et al. | Applicant |
| US6329161(B1) | 2001-12-01 | Heller et al. | Applicant |
| US6355018(B1) | 2002-03-01 | Vasko | Applicant |
| US6461331(B1) | 2002-10-01 | Van Antwerp | Applicant |
| US6472122(B1) | 2002-10-01 | Schulman et al. | Applicant |
| US6484046(B1) | 2002-11-01 | Say et al. | Applicant |
| US6503381(B1) | 2003-01-01 | Gotoh et al. | Applicant |
| US6514718(B2) | 2003-02-01 | Heller et al. | Applicant |
| US6551276(B1) | 2003-04-01 | Mann et al. | Applicant |
| US6554798(B1) | 2003-04-01 | Mann et al. | Applicant |
| US6556963(B1) | 2003-04-01 | Tetzlaff | Applicant |
| US6558320(B1) | 2003-05-01 | Causey, III et al. | Applicant |
| US6560471(B1) | 2003-05-01 | Heller et al. | Applicant |
| US6565509(B1) | 2003-05-01 | Say et al. | Applicant |
| US6577899(B2) | 2003-06-01 | Lebel et al. | Examiner |
| US6579690(B1) | 2003-06-01 | Bonnecaze et al. | Applicant |
| US6591125(B1) | 2003-07-01 | Buse et al. | Applicant |
| US6592745(B1) | 2003-07-01 | Feldman et al. | Applicant |
| US6605200(B1) | 2003-08-01 | Mao et al. | Applicant |
| US6605201(B1) | 2003-08-01 | Mao et al. | Applicant |
| US6607658(B1) | 2003-08-01 | Heller et al. | Applicant |
| US6616819(B1) | 2003-09-01 | Liamos et al. | Applicant |
| US6618934(B1) | 2003-09-01 | Feldman et al. | Applicant |
| US6623501(B2) | 2003-09-01 | Heller et al. | Applicant |
| US6641533(B2) | 2003-11-01 | Causey, III et al. | Applicant |
| US6654625(B1) | 2003-11-01 | Say et al. | Applicant |
| US6671554(B2) | 2003-12-01 | Gibson et al. | Applicant |
| US6676816(B2) | 2004-01-01 | Mao et al. | Applicant |
| US6689091(B2) | 2004-02-01 | Bui et al. | Applicant |
| US6689265(B2) | 2004-02-01 | Heller et al. | Applicant |
| US6733471(B1) | 2004-05-01 | Ericson et al. | Applicant |
| US6746582(B2) | 2004-06-01 | Heller et al. | Applicant |
| US6749740(B2) | 2004-06-01 | Liamos et al. | Applicant |
| US6809653(B1) | 2004-10-01 | Mann et al. | Applicant |
| US6872200(B2) | 2005-03-01 | Mann et al. | Applicant |
| US6881551(B2) | 2005-04-01 | Heller et al. | Applicant |
| US6893545(B2) | 2005-05-01 | Gotoh et al. | Applicant |
| US6916159(B2) | 2005-07-01 | Rush et al. | Applicant |
| US6932584(B2) | 2005-08-01 | Gray et al. | Applicant |
| US6932894(B2) | 2005-08-01 | Mao et al. | Applicant |
| US6936029(B2) | 2005-08-01 | Mann et al. | Applicant |
| US6942518(B2) | 2005-09-01 | Liamos et al. | Applicant |
| US6945760(B2) | 2005-09-01 | Gray et al. | Applicant |
| US6979326(B2) | 2005-12-01 | Mann et al. | Applicant |
| US6997920(B2) | 2006-02-01 | Mann et al. | Applicant |
| US7025743(B2) | 2006-04-01 | Mann et al. | Applicant |
| US2002/0019606(A1) | 2002-02-01 | Lebel et al. | Applicant |
| US2002/0082665(A1) | 2002-06-01 | Haller et al. | Applicant |
| US2002/0161288(A1) | 2002-10-01 | Shin et al. | Applicant |
| US2003/0078560(A1) | 2003-04-01 | Miller et al. | Applicant |
| US2003/0088166(A1) | 2003-05-01 | Say et al. | Applicant |
| US2003/0152823(A1) | 2003-08-01 | Heller et al. | Applicant |
| US2003/0168338(A1) | 2003-09-01 | Gao | Applicant |
| US2003/0176183(A1) | 2003-09-01 | Drucker et al. | Applicant |
| US2003/0188427(A1) | 2003-10-01 | Say et al. | Applicant |
| US2003/0199744(A1) | 2003-10-01 | Buse et al. | Applicant |
| US2003/0220552(A1) | 2003-11-01 | Reghabi et al. | Applicant |
| US2004/0061232(A1) | 2004-04-01 | Shah et al. | Applicant |
| US2004/0061234(A1) | 2004-04-01 | Shah et al. | Applicant |
| US2004/0064133(A1) | 2004-04-01 | Miller et al. | Applicant |
| US2004/0064156(A1) | 2004-04-01 | Shah et al. | Applicant |
| US2004/0074785(A1) | 2004-04-01 | Holker et al. | Applicant |
| US2004/0093167(A1) | 2004-05-01 | Braig et al. | Applicant |
| US2004/0111017(A1) | 2004-06-01 | Say et al. | Applicant |
| US2005/0214585(A1) | 2005-09-01 | Li | Applicant |
| DE4329229 | 1995-03-01 | Applicant | |
| EP98592 | 1984-01-01 | Applicant | |
| EP680727 | 1995-11-01 | Applicant | |
| EP806738 | 1997-11-01 | Applicant | |
| EP880936 | 1998-12-01 | Applicant | |
| EP1048264 | 2000-11-01 | Applicant | |
| EP1338295 | 2003-08-01 | Applicant | |
| GB2218831 | 1989-11-01 | Applicant | |
| WO9528878 | 1995-11-01 | Applicant | |
| WO9620745 | 1996-07-01 | Applicant | |
| WO9636389 | 1996-11-01 | Applicant | |
| WO9637246 | 1996-11-01 | Applicant | |
| WO9721456 | 1997-06-01 | Applicant | |
| WO9728736 | 1997-08-01 | Applicant | |
| WO9800056 | 1998-01-01 | Applicant | |
| WO9820439 | 1998-05-01 | Applicant | |
| WO9824358 | 1998-06-01 | Applicant | |
| WO9842407 | 1998-10-01 | Applicant | |
| WO9849659 | 1998-11-01 | Applicant | |
| WO9856293 | 1998-12-01 | Applicant | |
| WO9859487 | 1998-12-01 | Applicant | |
| WO9908183 | 1999-02-01 | Applicant | |
| WO9910801 | 1999-03-01 | Applicant | |
| WO9918532 | 1999-04-01 | Applicant | |
| WO9922236 | 1999-05-01 | Applicant | |
| WO9945375 | 1999-09-01 | Applicant | |
| WO9945387 | 1999-09-01 | Applicant | |
| WO9956613 | 1999-11-01 | Applicant | |
| WO10628 | 2000-03-01 | Applicant | |
| WO19887 | 2000-04-01 | Applicant | |
| WO29047 | 2000-05-01 | Applicant | |
| WO47109 | 2000-08-01 | Applicant | |
| WO78210 | 2000-12-01 | Applicant | |
| WO128416 | 2001-04-01 | Applicant | |
| WO128495 | 2001-04-01 | Applicant | |
| WO139089 | 2001-05-01 | Applicant | |
| WO152718 | 2001-07-01 | Applicant | |
| WO152727 | 2001-07-01 | Applicant | |
| WO156454 | 2001-08-01 | Applicant | |
| WO2058537 | 2002-08-01 | Applicant |
Non-Patent Literature (38)
- Abel, P. et al., “Experience with an Implantable Glucose Sensor as a Prerequisite of an Artificial Beta Cell”, Biomed. Biochim.,1984, Acta 43, 5, pp. 577-584.Applicant
- Banks, P. (Ed.), “Insulin Infusion Pump Therapy”, Intensive Diabetes Management, 1995, pp. 66-78.Applicant
- Bode, B.W. et al., “Reduction in Severe Hypoglycemia with Long-Term Continuous Subcutaneous Insulin Infusion in Type I Diabetes”, Diabetes Care, vol. 19, No. 4, 1996, 324-327.Applicant
- Boland, E., “Teens Pumping it Up! Insulin Pump Therapy Guide for Adolescents”, 2nd Edition, 1998, 60 pp.Applicant
- Brackenridge, B.P., “Carbohydrate Gram Counting: A Key to Accurate Mealtime Boluses in Intensive Diabetes Therapy”, Practical Diabetology, vol. 11, No. 2, 1992, pp. 22-28.Applicant
- Brackenridge, B.P. et al., “Counting Carbohydrates: How to Zero in on Good Control using the MiniMed insulin Pump”, MiniMed Technologies Inc.,1995, 26 pp.Applicant
- Farkas-Hirsch, R. et al., “Continuous Subcutaneous Insulin Infusion: A Review of the Past and Its Implementation for the Future”, Diabetes Spectrum From Research to Practice, vol. 7, No. 2, 1994, pp. 80-84 and 136-138.Applicant
- Fredrickson, L. (Ed.), “The Insulin Pump Therapy Book: Insights from the Experts”, MiniMed Technologies, 1995, 172 pp.Applicant
- Hirsch, I.B. et al., “Intensive Insulin Therapy for Treatment of Type I Diabetes”, Diabetes Care, vol. 13, No. 12, 1990, pp. 1265-1283.Applicant
- Kawamori, R. et al., “Perfect Normalization of Excessive Glucagon Responses to Intravenous Arginine in Human Diabetes Mellitus with the Artificial Beta-Cell”, Rapid Publication from Diabetes, vol. 29, Sep. 1980, pp. 762-765.Applicant
- Kulkarni, K. et al., “Carbohydrate Counting: A Primer for Insulin Pump Users to Zero in on Good Control”, MiniMed Inc., 1999, pp. 1-50.Applicant
- Marcus, A.O. et al., “Insulin Pump Therapy: Acceptable Alternative to Injection Therapy”, Postgraduate Medicine, vol. 99, No. 3, 1996, pp. 125-143.Applicant
- Mastrototaro, J.J. et al., “An Electroenzymatic Sensor Capable of 72 Hour Continuous Monitoring of Subcutaneous Glucose”, Presentation given at the 14th International Diabetes Federation Congress in Washington, D. C., Jun. 1991, 19 pp.Applicant
- McKean, B., et al., “A Telemetry-Instrumentation System for Chronically Implanted Glucose and Oxygen Sensors”, IEEE Transactions on Biomedical Engineering, vol. 35, No. 7, Jul. 1988, pp. 526-532.Applicant
- MiniMed, Inc., “MiniMed 508 Insulin Pump Flipchart: Guide to Insulin Pump Therapy”, Dec. 1999, 35 pp.Applicant
- MiniMed, Inc., “MiniMed 508 Insulin Pump User's Guide”, Sep. 2001, pp. 1-145.Applicant
- MiniMed, Inc., “MiniMed Dosage Calculator”, 1994, 4 pp.Applicant
- MiniMed, Inc., “Now I Can: Correction Bolus Calculator and Meal Bolus Calculator”, Jul. 2000, 2 pp.Applicant
- MiniMed, Inc., “Medtronic MiniMed Meal Bolus Calculator and Correction Bolus Calculator”, International Version, Feb. 2002, 4 pp.Applicant
- MiniMed, Inc., “Now I Can: MiniMed Pump Therapy Brochure”, Sep. 2000, 10 pp.Applicant
- MiniMed, Inc., “Now I Can: MiniMed Diabetes Management Packet”, Sep. 2000, 46 pp.Applicant
- MiniMed, Inc., “Paradigm Infusion Pump: Model MMT-511 User Guide”, Jan. 2002, 83 pp.Applicant
- Monroe, D. et al., “Novel implantable glucose sensors”, ACL, Dec. 1989, pp. 8-16.Applicant
- Nishida, K. et al., “Clinical applications of the wearable artificial endocrine pancreas with the newly designed needle-type glucose sensor”, Elsevier Science B.V., 1994, pp. 353-358.Applicant
- PCT International Search Report, Nov. 11, 2003, for International Application No. PCT/US03/23018, 10 pp.Applicant
- Reed, J, “Living with Diabetes”, Voice of the Diabetic, vol. 11, No. 3, 1996, pp. 1-38.Applicant
- Shichiri, M. et al., “A Needle-Type Glucose Sensor—A Valuable Tool Not Only for a Self-Blood Glucose Monitoring But for a Wearable Artificial Pancreas-”, Life Support Systems, Proceedings XI Annual Meeting ESAO, Sep. 1984, vol. 2, Supplement 1, pp. 7-9.Applicant
- Shichiri, M. et al., “An Artificial Endocrine Pancreas—Problems Awaiting Solution for Long-Term Clinical Applications of a Glucose Sensor”, Frontiers Med. Biol. Engng, VSP, vol. 3, No. 4, 1991, pp. 283-292.Applicant
- Shichiri, M. et al., “Closed-Loop Glycemic Control with a Wearable Artificial Endocrine Pancreas Variations in Daily Insulin Requirements to Glycemic Response”, Rapid Publication from Diabetes, vol. 33, Dec. 1984, pp. 1200-1202.Applicant
- Shichiri, M. et al., “Glycaemic Control in Pancreatectomized Dogs with a Wearable Artificial Endocrine Pancreas”, Diabetologia 24, 1983, pp. 179-184.Applicant
- 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, May-Jun. 1986, pp. 298-301.Applicant
- Shichiri, M. et al., “The Wearable Artificial Endocrine Pancreas with a Needle-Type Glkucose Sensor: Perfect Glycemic Control in Ambulatory Diabetics”, Acta Paediatr Jpn 26, 1984, pp. 359-370.Applicant
- Shichiri, M. et al., “Wearable Artificial Endocrine Pancreas with Needle-Type Glucose Sensor”, The Lancet, Nov. 20, 1982, pp. 1129-1131.Applicant
- 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.Applicant
- Skyler, J.S., “Continuous Subcutaneous Insulin Infusion [CSII] With External Devices: Current Status”, Update in Drug Delivery Systems, Futura Publishing Company, Chapter 13, 1989, pp. 163-183.Applicant
- Strowig, S.M., “Initiation and Management of Insulin Pump Therapy”, The Diabetes Educator, vol. 19, No. 1, 1993, pp. 50-60.Applicant
- Walsh, J. et al., “Pumping Insulin: The Art of Using an Insulin Pump”, MiniMed Technologies, 1989, 149 pp.Applicant
- Wang, J. et al., “Needle-Type Dual Microsensor for the Simultaneous Monitoring of Glucose and Insulin”, Analytical Chemistry, vol. 73, No. 4, Feb. 15, 2001, pp. 844-847.Applicant