This invention relates generally to implantable medical devices which deliver a therapeutic drug to a body site at flow rates and times specified by a drug delivery profile and, more particularly, to such devices and methods of operation for automatically modifying a Current Profile to accommodate changes in the drug formulation being delivered.
Various implantable drug delivery devices are known in the art which can be programmed to deliver a drug to a body site for infusion at flow rates and times dictated by a stored drug delivery profile. Such delivery devices typically include a refillable reservoir for storing a fluid drug and a controllable fluid transfer device (e.g., a pump or valve) for transferring fluid from the reservoir to a catheter for delivery to the body site. The drug delivery profile comprises a data set specifying a schedule of flow rates for a periodic cycle, or period, of a certain duration. For example, the duration of a period can be one day, one week, or one month, etc. The particular profile used to control drug delivery is typically specified by the patient's clinician and depends upon several factors including the particular drug formulation being delivered, the patients condition, the therapy being administered, etc.
Most modern drug delivery devices permit a clinician to modify a patient's drug therapy by modifying a stored delivery profile, and/or replacing the current, or old, drug with a new drug. As used herein, the term “new” drug refers to a change in formulation and is intended to include a change in concentration and/or a change in active components. Regardless, if an old drug is replaced by a new drug, then a Current Profile must also be changed to assure that the new drug is properly delivered with regard to safety and efficacy.
Modern implantable drug delivery devices generally permit a clinician to evacuate the volume of old drug from the reservoir prior to introducing a new drug. Although the reservoir can be evacuated, a certain amount of old drug generally remains in the system, typically in the pump (i.e., pump clearance space) and catheter (i.e., catheter clearance space). Any old drug remaining in the system is typically cleared by delivery to the patient's body site. Although, it is generally desired to clear the old drug rapidly in order to promptly initiate the new therapy, the delivery rate must not be so rapid as to jeopardize the patient's health or safety. In any event, the delivery profile for the old drug is generally different than the profile for the new drug. Traditionally, the transition from an old drug to a new drug is typically handled by the clinician calculating a “bridge bolus” to rapidly clear the old drug. Calculation of this bridge bolus and the associated bolus rate is generally time consuming for the clinician and represents an opportunity for human error.
The present invention relates to an implantable drug delivery device which includes a fluid drug reservoir, a catheter, a controllable fluid transfer device, e.g., a pump or valve, and a drug delivery control means. The control means in accordance with the invention is configured to initially clear a first, or old, drug from the device based on the content of the Current Profile data containing a first, or old, delivery profile. After the old drug is cleared, then the control means automatically modifies the Current Profile data to match a second, or new, delivery profile for controlling delivery of a second, or new, drug.
In accordance with a preferred embodiment of the invention, the drug delivery control means comprises a controller, e.g., a microprocessor or microcontroller, programmed to defer adoption of a new delivery profile, as the Current Profile, until a remaining, or “clearance”, volume of the old drug has been cleared from the device. More particularly, the controller, upon receipt of a new profile, determines the Clearance Volume, i.e., the volume of the old drug which remains to be cleared. The controller then monitors the subsequent delivery of the old drug to the patient to determine when the remaining old drug has been cleared from the device. Thereafter, the controller adopts the new profile as the Current Profile.
In accordance with the preferred embodiment, after a new drug has been introduced into the reservoir and a new profile has been loaded into the controller, the controller retains the new profile in a Next Profile storage location. The contents of the Next Profile storage location is then used as the Current Profile data after the old drug has been cleared from the device.
In accordance with a significant aspect of the invention, the quantity of remaining old drug delivered subsequent to receipt of a new delivery profile is preferably determined by monitoring the activity of the fluid transfer device. This technique assures that any delivery of the old drug, whether attributable to the old delivery profile and/or a bolus administered by a clinician or the patient, will be taken into account.
Attention is initially directed to
As depicted in
Communication device 16 is shown as including a CD programmer 34, e.g., a microprocessor or microcontroller, which operates in conjunction with memory 36 which stores programs and/or data. The device 16 optionally includes a CD user input device 38, e.g., a keyboard, and a CD user output device 40, e.g., a display. The communication device 16 further includes aforementioned CD telemetry subsystem 19 configured to transmit signals to or receive signals from the MD telemetry subsystem 18. The communication device 16 further includes an internal power source 44 which can comprise a battery or any other suitable conventional power source.
In a typical system 10, the communication device 16 is capable of sending messages to the medical device 14 for use by its controller 22 to affect the operation of its therapeutic administration subsystem 26. Additionally, the medical device 14 is typically capable of sending messages to the communication device 16 to report various conditions, e.g., battery status, drug reservoir status, etc. These respective messages sent by the communication device 16 and medical device 14 are handled by the respective telemetry subsystems 19 and 18, each of which is able to transmit and receive RF telemetry signals. Typically, these RF telemetry signals comprise bit streams carried by an RF carrier signal of specified frequency.
In typical use, a hypodermic needle (not shown) is used, via fill port 38, to fill the reservoir 36 with a first drug. The fluid transfer device 40 is controlled by controller 50 in accordance with Current Profile data, containing data appropriate to the first drug, drug delivery profile to deliver the drug to the catheter proximal end. The drug delivery profile data which specifies a schedule of drug flow rates over a certain period, or cycle, e.g., having a duration of one day or one week or one month.
Attention is now directed to
In accordance with the present invention, as represented in
Attention is now directed to
The flow chart of
Based on the known pump and catheter data, the microprocessor 22, in block 124, calculates the quantity of old drug which must still be cleared from the delivery device in accordance with the old delivery profile. After the remaining old drug volume to be cleared is calculated in block 124, blocks 125 and 126 are executed. Block 125 introduces a wait interval. Block 126 indicates that the current drug delivery rate of the pump is still controlled by the CurrentProfile data based on the old delivery profile. Consequently, the fluid transfer device or pump continues to deliver the old drug at the rate specified by the old profile stored in the CurrentProfile register.
Block 128 develops a DrugAccumulator value based on the delivery profile stored in the Current Profile register. Once the DrugAccumulator value is greater than one pump stroke, then decision block 130 provides a “yes” output and operation proceeds to block 132. On the other hand, if block 130 produces a “no” response, then operation loops back to block 125 which iteratively enableS the DrugAccumulator value to increase to one stroke.
Block 132 occurs when the DrugAccumulator value exceeds one stroke meaning that the fluid transfer device or pump should be actuated to deliver a unit quantity of the old drug via the catheter to the patient's body site. In block 134 a previously calculated VolumeToClear value is decremented by the volume of drug moved by the pump stroke. Decision block 136 compares the decremented VolumeToClear value with zero. If the VolumeToClear value has not yet decremented to zero, then operation loops back to block 125 to continue clearance of the old drug. On the other hand, if block 136 produces a “yes” result (meaning that the old drug has been fully cleared), then operation proceeds to block 138 which adopts the new drug delivery profile, stored in the NextProfile register in block 122, as the CurrentProfile. Then, operation continues based on the new delivery profile to cause the fluid transfer device to thereafter deliver the new drug according with the new profile, as was demonstrated in
After block 136′ recognizes that the old drug has been cleared, operation proceeds to block 137′ which scales the CurrentProfile by the ConcentrationRatio received from the programmer (block 120′). Then normal delivery is resumed in block 140′.
From the foregoing, it should be understood that a method and apparatus has been disclosed herein for automatically bridging the delivery profiles respectively associated with a first or old drug and a second or new drug. The method and apparatus described herein relieves the clinician of the task of determining a bolus rate which is frequently time consuming and represents an opportunity for human error. An apparatus operating in accordance with the present invention operates to more smoothly bridge the delivery rates respectively associated with different first and second drugs.
It is pointed out that the term drug delivery profile has been used herein to generally refer to a set of data describing a schedule of flow rates.
A drug delivery profile typically refers to a single period or cycle of certain duration, e.g., 24 hours, or one week, or one month, etc. The drug delivery profile data can be organized in any of various ways, all consistent with the teachings of the present invention. For example, the drug delivery data can be consistent with any of the following approaches or any combination thereof:
It is, of course, recognized that a system in accordance with the invention that automatically switches delivery profiles relies on accurate VolumeToClear and DrugAccumulator data. If the mechanism cannot deliver accurately, then it might switch profiles either early or late. This, in turn, could result in an over-delivery situation. To mitigate this potential safety issue, it is sometimes prudent to intentionally deliver the drug at the slower rate during the period of uncertainty; i.e., during the period when either drug could be delivered from the tip of the catheter.
It is possible to assert that the implantable drug-delivery pump does not really need to know if the concentration of the drug increases or decreases at a refill. When the pump is done bridging, it will switch from one basal-rate profile to another. If only a single basal rate were delivered for each profile, then the pump could switch from a high rate to a low rate earlier than from a low rate to a high rate. This would avoid the delivery of a high concentration drug at a high rate. This idea can be extended to a basal-rate profile with multiple basal rates by averaging the rates across the entire profile duration. In the case of a daily profile, this would be the total amount of drug that is delivered in twenty four hours. If the daily delivery rate decreases with a refill, the pump should begin using the new profile after the minimum clearance volume has been delivered.
Another solution to the problem of selecting the minimum or maximum bridge volume is to simply have the clinician specify which to use. Bridging in this manner is performed by tracking the amount of drug that has been delivered after a drug change. Therefore, it accounts for both basal and bolus delivery. However, if the rates, duration, or limits to patient-requested boluses are changed by the clinician, these changes should take effect at the end of the bridging period (i.e., when the new drug is being delivered from the tip of the catheter)
The programmer is preferably configured to also allow the clinician to specify the type of procedure (e.g., refill, drug formulation change, or drug concentration change). The programmer will then signal the implanted pump to start a bridging operation. If a simple drug concentration change is performed, the programmer will compute the ratio between the two drugs and then send this information to the pump. In this manner, the bridging would be programmed by the clinician specifying the type of operation rather than explicitly specifying that a bridge is desired.
This application is a continuation of U.S. application Ser. No. 11/069,573, filed Feb. 28, 2005, now U.S. Pat. No. 7,347,854, which claims the benefit of U.S. Provisional application Ser. No. 60/549,474, filed Mar. 2, 2004.
Number | Name | Date | Kind |
---|---|---|---|
4146029 | Ellinwood, Jr. | Mar 1979 | A |
4373527 | Fischell | Feb 1983 | A |
4494950 | Fischell | Jan 1985 | A |
4559037 | Franetzki et al. | Dec 1985 | A |
5527307 | Srisathapat et al. | Jun 1996 | A |
5527407 | Gartland et al. | Jun 1996 | A |
5814014 | Elsberry et al. | Sep 1998 | A |
5836935 | Ashtom et al. | Nov 1998 | A |
6269340 | Ford et al. | Jul 2001 | B1 |
6537268 | Gibson et al. | Mar 2003 | B1 |
6562001 | Lebel et al. | May 2003 | B2 |
6571128 | Lebel et al. | May 2003 | B2 |
6572583 | Olsen et al. | Jun 2003 | B1 |
6577899 | Lebel et al. | Jun 2003 | B2 |
6579280 | Kovach et al. | Jun 2003 | B1 |
6585644 | Lebel et al. | Jul 2003 | B2 |
6605072 | Struys et al. | Aug 2003 | B2 |
6648821 | Lebel et al. | Nov 2003 | B2 |
6668196 | Villegas et al. | Dec 2003 | B1 |
6687546 | Lebel et al. | Feb 2004 | B2 |
6740075 | Lebel et al. | May 2004 | B2 |
6810290 | Lebel et al. | Oct 2004 | B2 |
7347854 | Shelton et al. | Mar 2008 | B2 |
8128616 | Junker | Mar 2012 | B2 |
20010044620 | Krulevitch et al. | Nov 2001 | A1 |
20020019606 | Lebel et al. | Feb 2002 | A1 |
20030045858 | Struys et al. | Mar 2003 | A1 |
20030060753 | Starkweather et al. | Mar 2003 | A1 |
20030216682 | Junker | Nov 2003 | A1 |
Number | Date | Country |
---|---|---|
WO 03082380 | Oct 2003 | WO |
Number | Date | Country | |
---|---|---|---|
20080177254 A1 | Jul 2008 | US |
Number | Date | Country | |
---|---|---|---|
60549474 | Mar 2004 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11069573 | Feb 2005 | US |
Child | 11927174 | US |