Dialysis system having adaptive prescription management

Information

  • Patent Grant
  • 11918721
  • Patent Number
    11,918,721
  • Date Filed
    Friday, April 22, 2022
    2 years ago
  • Date Issued
    Tuesday, March 5, 2024
    2 months ago
Abstract
An example peritoneal dialysis system is disclosed. The example peritoneal dialysis system includes at least one pump and a memory device configured to store therapy prescriptions including a low ultrafiltration (“UF”) therapy prescription, a first standard UF therapy prescription with a longer duration and a lower dextrose concentration, and a second standard UF therapy prescription with a shorter duration and a higher dextrose concentration. The memory device also stores a schedule indicative as to which of the therapy prescriptions are to be performed on specified dates. The system further includes a logic implementer configured to determine or identify a current date, use the schedule stored in the memory device to select the therapy prescription based on the current date, and control the at least one pump based on the selected therapy prescription to perform a peritoneal dialysis therapy.
Description
BACKGROUND

The proportion of patients performing automated peritoneal dialysis (“APD”) is increasing worldwide, which is due in part to the ability of APD to be adapted to the patient's particular needs regarding the patient's private life and the patient's therapy needs. The two primary goals of dialysis, solute clearance and ultrafiltration (“UF”) depend on the modality or type of APD performed (e.g., nocturnal intermittent peritoneal dialysis (“NIPD”), continuous cycling peritoneal dialysis (“CCPD”) and hi-dose CCPD, solution type, therapy time and fill volume. Prescribing an APD therapy constitutes selecting one of each of these. Thus there are many combinations and possibilities from which to choose.


APD devices typically do not have the capability to provide feedback to the patient regarding the effectiveness of his/her recent therapies. Also, APD devices typically run open loop such that they do not adjust therapy parameters (e.g., modality, solution type, therapy time and fill volume) based on the actual measured daily clearance and UF. Accordingly, some patients underachieve their targets and develop adverse conditions such as fluid overload and in some cases hypertension. Current methods for adjusting treatment typically involve the patient reporting to a center every so often to be evaluated. These methods place the burden of therapy adjustment solely on the doctor or clinician and do not occur frequently enough to adjust properly to the patient's weekly, monthly, seasonal or other lifestyle change.


The systems and methods of the present disclosure attempt to remedy the above problems.


SUMMARY

The system of the present disclosure includes a plurality of prescription optimization modules. One of the modules is an advanced peritoneal equilibration test or (“PET”). The PET allows the patient to perform an ultrafiltration (“UF”) portion of the PET at home automatically using the patient's automated peritoneal dialysis (“APD”) machine. The automated test collects more UF data point samples than in the past, which helps to establish a more accurate UF patient-characteristic curve. The UF samples and blood work are then used to generate physiological data for the patient.


A second module of the prescription optimization system of the present disclosure is to use the above patient physiological data in continuation with specified therapy targets (e.g., UF, clearance) and ranges of therapy inputs (e.g., number of exchanges, cycle times, solution choices) to calculate or deliver all possible regimens that fit within the provided ranges.


A third aspect or module of the present disclosure is to use one or more filter specifying a patient's preference or doctor's performance requirement to narrow the number of regimens to a manageable few. The doctor or patient agree upon a certain number of the regimens, e.g. three to five regimens, to be prescribed by the doctor for treatment.


Another feature of the present disclosure is an inventory tracking module that tracks different solutions and other supplies used over a delivery cycle in performing the different prescriptions selected by the patient. The APD machine has the ability to mix dialysis solutions of different dextrose levels to produce hybrid dextrose dialysate blends, which further enables the patient's treatment to be optimized. The inventory tracking feature records dextrose levels used and replaces the associated dialysate concentrations consumed.


A fifth module of the present disclosure is a trending of the prescriptions that the patients are performing. The trends can track any one or more of UF removed, body weight blood pressure and prescription used. A sixth module controls how the different prescriptions are recalled for use and adjusted or replaced if needed. The trends can also trend and show averages such as a seven day moving average UF and/or a thirty day moving average.


In one embodiment, the patient at the beginning of treatment weighs himself/herself (e.g. after initial drain) and takes the patient's blood pressure. As discussed in detail herein, the present system includes a scale and blood pressure taker that output weight and blood pressure information, respectively, wirelessly to the APD machine using a wireless technology such as Bluetooth™, WiFi™, Zigbee™ technology. The wireless link is provided via radio frequency transmission in one embodiment. In an alternative embodiment, the weight and blood pressure information are provided via a wired connection between the scale and blood pressure taker and the APD machine. The patient alternatively types in the weight and blood data.


The APD machine provides multiple therapy prescriptions from which either the patient or the APD machine chooses one for that day's treatment. For example, the APD machine can provide five physician-approved prescriptions for the patient, one of which is chosen based on the patient's weight, blood pressure and UF removed over the last twenty-four hours. The prescription does not need to be selected before the initial drain (initial drain is done in any of the possible treatments), so that the patient or machine can obtain the final UF information from the previous day's treatment before determining which prescription to select. The machine in one embodiment provides prompts at the beginning of treatment to remind the patient to obtain the patient's weight and blood pressure.


The five possible prescriptions are determined analytically. One possibility is to develop and store an algorithm either in the APD machine itself or in a server computer that communicates with the APD machine, e.g., via an internet connection. The algorithm can employ a three-pore model, for example, which adds predicted clearances across three different sized pores in the patient's peritoneal membrane. Flow of toxins through large pores, small pores and micro-pores in the blood vessels of the peritoneal membrane are summed. Urea and creatinine for example are removed from the patient's blood through the small pores. The large pores allow larger protein molecules to pass from the patient's blood to the dialysate. In each case, an osmotic gradient drives the toxins from the patient's blood to the dialysate. Using the predicted clearances and the three-pore model, the system of the present disclosure outputs a plurality of acceptable regimens for the patient. From these regimens five prescriptions can be selected, for example. The algorithm alternatively uses a two-pool model as discussed in detail below.


In one embodiment, the regimen generation portion of the system is stored and used at a dialysis center or nephrologist's office. The patient enters the office or center, and the doctor or clinician examines the patient, enters patient data into regimen generation software located at the office or center, which outputs suitable regimens from which, e.g., five, different prescriptions are selected. These different prescriptions are expected to address the patient's varying APD needs for the foreseeable future, e.g., over the next six months to a year. New patients may have residual renal function (“RRF”), such that their kidneys are partially functional. These patients do not need treatments that are as aggressive as do patient's with no kidney function. The need for adjustment for these patients may be greater however as RRF degrades. Here, the plurality of prescriptions may need to be upgraded more frequently, e.g., every three months.


The three-pore model is very good at predicting clearance values, such as urea removed, Kt/V, pKt/V, creatinine removed, CCr, pCCr, glucose absorption and total effluent. The system of the present disclosure also uses an advanced peritoneal effectiveness test (“PET”) to help predict UF removal accurately. The advanced PET also includes blood samples and chemical analysis performed on dialysate samples to accurately predict the patient's clearances for urea removed, Kt/V, pKt/v, creatinine removed, CCr, pCCr, glucose absorption and total effluent even better.


Regarding the advanced PET module of the present disclosure, the advanced PET includes samples taken over two therapies. In the first therapy, for example, UF is measured after a thirty minute dwell, sixty minute dwell, 120 minute dwell and 240 minute dwell, totaling 7.5 hours. In the second therapy, UF is measured after an eight hour dwell, providing a total of five data points. At each time interval, the patient is drained completely to determine UF accurately. The UF can be measured by the APD machine or alternatively or additionally via a weight scale if more accuracy is desired. Because the patient has to refill after draining completely each time, the actual UF time periods may differ slightly from the intended UF time periods. For example, the two hour UF time period may actually consume two hours and ten minutes. The system of the present invention records the actual time period and uses the actual time as an input to the kinetic modeling.


The blood and dialysate samples can be taken at certain intervals wherever and whenever blood can be drawn. The first and second therapies can be performed consecutively or over two nights. In one embodiment, the patient performs the half hour, one hour, and four hour fills/dwells/drains at night before bed. The patient then performs a last fill, sleeps and is awakened in time to perform the eight hour drain. UF and actual dwell times are recorded for each dwell period. The data can be recorded on a data card that the patient beings the next day to the lab or center. The data is transferred to the lab or center alternatively via an internet using a data communications module discussed herein.


The patient then travels to a dialysis center. The patient is filled an additional time. Blood and dialysate samples are taken at two hours and four hours, for example. A second four-hour drain UF data point can be taken and compared to the first four-hour drain UF data point for additional accuracy.


The five data UF points, blood testing and dialysate testing data are obtained using a particular dialysate concentrate, such as 2.5 percent dextrose. The data points are used to estimate kinetic parameters consisting of solute mass transfer area coefficients (“MTAC”) and ultrafiltration parameters (a hydraulic permeability coefficient and a fluid absorption rate) and also to classify the patient's transport and UF characteristics. Based on the estimated kinetic parameters, kinetic modeling using a modified three-pore model can then be applied physiologically to other types of dialysate concentrate, such as 1.5 percent dextrose and Extraneal® dialysate.


Regarding the regimen generation module of the present disclosure, the prediction algorithms use the above calculated patient transport and UF characteristics, target information and other therapy input information to generate the regimens. The target and other therapy information include for example: (i) clinical targets such as (a) minimum urea clearance, (b) minimum urea Kt/V, (c) minimum creatinine clearance, (d) maximum glucose absorption, and (e) target UF; and (ii) therapy parameters such as (a) therapy time, (b) therapy volume, (c) fill volume, (d) percent dextrose, and (e) solution type; and (iii) available solutions. Many of these inputs are expressed in ranges, leading to many possible regimen outcomes. The software using the three-pore or two-pool model equations generates, in one embodiment, every possible regimen using (i) each input in each range and (ii) the patient's transport and UF characteristics, which meets the above-described target and therapy information.


Regarding the prescription filtering module, the system allows the user to specify certain filtering information to pair the regimen combinations down to a manageable number of combinations from which to select and approve as set of prescriptions. The filtering information can include for example filtering out all regimens with aKt/V, creatinine clearance and UF below a certain value, and a glucose absorbed above a certain value. The clinician and patient then agree on a few of the paired down prescription possibilities to be stored as prescriptions on the patient's APD machine or alternatively on a server computer having a communications link to the APD machine.


The prescriptions can be stored on the patient's data card and loaded physically into the APD machine when the patient returns home. Alternatively, a dialysis center downloads the prescriptions to the APD machine via a interne or other data communications network. One set of prescriptions can include for example: (i) a standard UF prescription; (ii) a high UF prescription; and (iii) a low UF prescription. If the patient is capable, the APD system can be set to allow the patient to run a prescription tailored to the day's activities. If the patient exercises heavily on certain days, losing large amounts of body fluids via sweat, the patient can run a lower UF treatment that evening, perhaps saving the patient from having to perform a day exchange the next day. If the patient is out to dinner on a given night and consumes more liquids than normal, the patient can run the high UF treatment. On all other days the patient runs the standard UF prescription.


One corollary component to the instant system is the inventory distribution and tracking module. If the selected prescriptions require different types of dialysate concentrates, the different dialysate types need to be delivered in the right quantity. In the present system, either the APD machine or the clinician's server tracks the patient's current inventory and ensures that a needed supply of the appropriate solutions is delivered to the patient's home.


As discussed herein, one of the therapy parameters is percent dextrose of the solution, which affects the amount of UF removed and the amount of calories absorbed by the patient. More dextrose results in more UF removed, which is generally desirable. More dextrose, however, results in more caloric intake and weight gain by the patient, which is not desirable. Dextrose profiling is therefore an important factor in selecting the patient's possible therapies. The different solutions are provided in different dextrose percentages, such as 1.5%, 2.5% and 4.25% dextrose. The APD machine described in connection with the present system has the ability to connect to multiple solution bags having different glucose percentages and pull solution from the different bags to form a mixed or blended solution, e.g., in a warmer bag or in the patient's peritoneum if inline heating is used, having a desired glucose percentage different from the rated percentages, e.g., 2.0%, 2.88%, 3.38% and 3.81% dextrose. If mixed in a warmer bag, the warmer bag can be fitted with one or more conductive strip, which allows a temperature compensated conductivity reading of the mixed solution to be taken to ensure that the solutions have been mixed properly.


In one embodiment, the APD machine tracks the different bags used during treatment over the course of a delivery cycle. Before the delivery person arrives with new solution bags, the inventory used is sent to the solution distribution facility. This inventory is subtracted from the patient's total home inventory, so that the solution distribution facility knows how much of which solution(s) to deliver to the patient's home. In one embodiment, when the delivery person arrives at the patient's home, the delivery person scans in the patient's remaining inventory for comparison with what is expected to be remaining. The APD machine does not automatically account for solution bags that are destroyed, lost or otherwise not used for treatment. It is contemplated however to allow the patient to enter a lost or destroyed bag amount (or actual total amount of bags remaining) into the APD machine tracking system if such procedure is found to provide more accurate advance inventory information. The delivery person's scan of the remaining product in any case resets the patient's inventory at each delivery so that errors do not accumulate.


Regarding the trending and alert generation module, the APD system of the present disclosure tracks or trends certain therapy parameters, such as daily UF, blood pressure and body weight. The trends in one embodiment can be seen on the display device of the APD machine between therapies, for example at the beginning of a therapy. The trends can also be viewed by the clinician and/or doctor. The patient at the beginning of therapy can for example view the patient's weight, blood pressure and UF removed over the last twenty-four hours. The patient can learn of a previous day's UF after the patient's initial drain, which is from the last fill of the previous night's therapy. That is, the end of a first initial drain to the end of a second initial drain sets a UF cycle that is recorded. The patient after the initial drain weighs himself/herself, providing data that is entered into the machine via cable or wirelessly or, alternatively, via patient entry. The trend data in combination with a set of filters or criterion are used to either allow treatment to be performed under a current set of prescriptions or to be run via a new prescription(s). The machine in one embodiment automatically alerts the clinician if an alarm condition occurs or if a prescription change is needed.


The trend screens can show for example a daily UF trend, a seven day moving average trend and a thirty day moving average trend. The moving average trends smooth the daily highs and lows and more readily indicate UF up and down trends. When the actual UF removed falls below a low threshold UF removed, e.g., over a predefined period of time, or in combination with the patient running a high UF prescription to avoid underperforming UF, the system of the present disclosure causes the APD machine to send an alarm or alert signal to the dialysis center and/or doctor. Different methods or algorithms are discussed herein for preventing the system from overreaction or being too sensitive. Besides the rolling UF averages, the system also uses algorithms that accumulate error and look for other physiological patient parameters, such as weight and blood pressure in an attempt to view the patient more generally instead of just looking at UF removal.


Regarding the prescription recall and adjustment module, the clinician or doctor responds to the prescription alarm in an appropriate manner, such as by calling the patient into the clinic, making suggestions via phone or email regarding the use of the currently existing prescriptions, ordering a new PET, and/or changing the patient's prescriptions. The system is thus configured to remove the burden of detecting a poor performing prescription(s) from the clinician or doctor and to alert of such poor performing prescription as soon as reasonably possible without overreacting to one or more underachieving day.


If an alert condition occurs and the APD machine is not able to communicate the alert condition to the clinic or center, e.g., no internet service is available or accessible, the system is configured to have the APD machine prompt the patient to contact the clinic or center. To that end, the system includes a handshaking procedure in which the clinician's server sends an electronic receipt-confirmed message to the APD machine, so that the APD knows that the alert has been received.


The APD system can be set to respond in a closed-loop manner to a consistent underperforming therapy. Here the APD machine stores a database of acceptable prescriptions, e.g., the five prescriptions prescribed above by the doctor. The machine automatically selects a prescription approved by the doctor in an attempt to improve results. For example, the machine could select a higher UF prescription if the patient's UF has been underperforming. Or, the machine presents a number of prescription options to the patient, who selects one or more prescription approval by the doctor. It should be appreciated that in one embodiment, the system only allows the patient to run a prescription approved by a doctor.


In another alternative embodiment, the plurality of, e.g., five, approved prescriptions are loaded onto the patient's APD machine but only a subset, e.g., three of five, prescriptions is enabled. When the enabled treatments are found to be underperforming, a doctor or clinician enables a previously non-enabled therapy that is, for example, capable of increasing the patient's UF. In this way, the doctor or clinician can select from a pre-approved set of prescriptions and not have to rerun the regimen generation and prescription filtering prescription sequence described above. The system can also provide the above-described alert responses for blood pressure and body weight alert conditions.


The system can respond to alerts in other ways besides changing the patient's prescription. The trends show which prescriptions have been run on which days, so the doctor or clinician can look to see if the patient is running enough therapies and/or the right therapies. The trends also show patient weight, allowing the doctor or clinician to recommend that the patient reduce his/her food and drink intake if the patient has gained too much weight. Patient blood pressure can also be trended and considered upon an alert. Discussed herein are a plurality of algorithms and examples illustrating possible repercussions from a patient alert.


When the patient's therapy is functioning properly, the system can operate to allow the patient to select a prescription to run on a given day. The machine or system can alternatively select the daily prescriptions to run, or some combination thereof. Discussed herein are a number of prescription adjustment algorithms or methods that attempt to balance patient flexibility and lifestyle concerns with therapy performance concerns.


It is accordingly an advantage of the present disclosure to provide an APD system that analyzes patient treatment data and communicates results to the doctor or clinician, who can then spend more time talking to the patient rather than performing the analysis manually.


It is another advantage of the present disclosure to provide a peritoneal dialysis system that attempts to optimize a therapy prescription for the patient.


Still further, it is an advantage of the system of the present disclosure to track or trend various patient PD physiological parameters, to provide rolling averages of same, and to react quickly but not overreact to an apparent underperforming therapy.


It is a further advantage of the system of the present disclosure to provide a closed-loop PD system that responds to underperforming UF, patient weight gain and/or high blood pressure.


It is yet another advantage of the system of the present disclosure to provide a system that tracks patient solution use to deliver multiple needed solutions to the patient efficiently.


It is still a further advantage of the system of the present disclosure to provide a dialysis system that mixes standard dextrose solutions to achieve a desired, blended dextrose level dialysate.


It is yet a further advantage of the system of the present disclosure to provide a dialysis system having a plurality of approved prescriptions from which the patient can choose to fit a patient's daily needs.


It is still another advantage of the system of the present disclosure to provide a dialysis system that uses a more accurate peritoneal equilibration test.


Additional features and advantages are described herein, and will be apparent from, the following Detailed Description and the figures.





BRIEF DESCRIPTION OF THE FIGURES


FIG. 1 is a schematic view of one embodiment of the prescription optimization system of the present disclosure including an improved peritoneal equilibration test (“PET”) module, regimen generation module, prescription filtering and selection module, dialysis fluid inventory management module, communications module, data input module, trending and alert generation module, and a prescription recall and adjustment module.



FIG. 2A is a perspective view of a peritoneal blood vessel showing the different sizes of pores used in a three-pore model for predicting peritoneal dialysis therapy results.



FIG. 2B is a schematic view of the kinetic transport properties of a two-pool model used for predicting peritoneal dialysis therapy results.



FIG. 3 illustrates a sample plot of UF removed versus dwell time from data collected by the dialysis instrument at home for use with an improved peritoneal equilibration test (“PET”) of the present disclosure.



FIGS. 4A to 4D are sample screens displayed on a clinician's or doctor's computer as part of the system of the present disclosure, illustrating additional data associated with the improved PET module.



FIG. 5 is a sample screen displayed on a clinician's or doctor's computer as part of the system of the present disclosure, illustrating data associated with the regimen generation module.



FIGS. 6A to 6C are sample screens displayed on a clinician's or doctor's computer as part of the system of the present disclosure, illustrating filtering criteria used to filter the generated regimens into possible prescriptions for therapy.



FIGS. 7A and 7B are sample screens displayed on a clinician's or doctor's computer as part of the system of the present disclosure, illustrating the selection of prescriptions from the list of filtered regimens.



FIGS. 8A to 8C are sample screens displayed on a clinician's or doctor's computer as part of the system of the present disclosure, illustrating the agreed upon high UF, standard UF and low UF prescriptions, respectively.



FIGS. 9A to 9E illustrate another example of a filtering process according to the present disclosure, which results in a final filter of three prescribed regimes for the patient.



FIGS. 10 to 13 are sample screens displayed on a clinician's or doctor's computer as part of the system of the present disclosure, illustrating one embodiment of an inventory management module.



FIG. 14 is a perspective view of one embodiment of a dialysis instrument and disposable pumping cassette illustrating one suitable apparatus for performing dextrose mixing used with the prescription optimization system of the present disclosure.



FIGS. 15A and 15B are schematic views illustrating embodiments for wireless and wired communications modules, respectively, for the prescription optimization system of the present disclosure.



FIG. 16A is a schematic view illustrating another embodiment for a communications module and an embodiment of the data collection module, which includes wireless weight and blood pressure data entry for the prescription optimization system of the present disclosure.



FIG. 16B is a schematic view illustrating a further embodiment for a communications module, in which a central clinical server is located at or associated with a particular dialysis center.



FIGS. 17 to 21 are sample screens displayed on a patient's dialysis instrument illustrating various trending data available to the patient.



FIGS. 22 and 23 are sample screens displayed on a patient's dialysis instrument or a clinician's and/or doctor's computer as part of the trending module of the present disclosure, illustrating various trending data including moving UF averages, target UF, daily UF, UF limits and prescription used.



FIG. 24 is a schematic diagram illustrating one possible alert generation algorithm for the trending and alert generation module of the prescription optimization system of the present disclosure.



FIG. 25 is a logic flow diagram illustrating another possible alert generation/prescription modification algorithm for the trending and alert generation module of the prescription optimization system of the present disclosure.



FIG. 26 is a sample screen displayed on a patient's dialysis instrument or a clinician's and/or doctor's computer as part of the system of the present disclosure, illustrating various trending data including moving UF averages and UF limits determined via statistical process control.



FIG. 27 is a sample screen displayed on a patient's dialysis instrument or a clinician's and/or doctor's computer as part of the system of the present disclosure, illustrating various trending data including moving UF averages, target UF, prescription used and UF limits determined via statistical process control.



FIG. 28 is a schematic view of one embodiment of a transfer function used for the prescription recall and adjustment module of the prescription optimization system of the present disclosure.



FIG. 29 is a sample screen displayed on a patient's dialysis instrument illustrating one possible prescription recall embodiment of the prescription recall and adjustment module of the prescription optimization system of the present disclosure.





DETAILED DESCRIPTION

Referring now to the drawings and in particular to FIG. 1, a schematic view of peritoneal dialysis (“PD”) system 10 having an automated peritoneal dialysis (“APD”) machine 104 is illustrated. System 10 provides and uses an improved peritoneal equilibration test (“PET”) 12, which samples and employs multiple data points for determining the patient's ultrafiltration (“UF”) curve over the course of treatment. PET 12 improves UF prediction used to characterize an individual's response to PD therapies and helps the clinician to generate optimized prescriptions for patients. In one embodiment, PET 12 is performed as a fixed therapy using the APD machine 104 at home. PET 12 also requires lab testing and analysis as set forth below.


System 10 also performs automated regimen generation 14. Known regimen generation is performed manually by a physician 110 or clinician 120 using a hit or miss type strategy, which is time consuming and relies on scientific guessing by the nurse or physician. Automated regimen generation feature 14 uses the results of PET 12, therapy input parameters and inputted therapy target parameters to generate regimens for the physician 110 or clinician 120, which saves time and increases the likelihood that one or more regimen is generated that meets the therapy targets for clearance and UF, minimizes glucose exposure, and meets lifestyle needs.


System 10 further includes a prescription filtering module 16, which reduces the many regimens generated by automated regimen generation feature 14 to a manageable number of prescriptions, which are then selected by the patient and doctor/clinician to provide a set of approved prescriptions that are loaded onto the patient's APD machine 104 at home. In one embodiment, the APD machine 104 supports up to five prescriptions that are transferred to the APD machine 104 via a data card, the interne or other type of data communication. The different prescriptions can include for example: two primary (or standard) prescriptions, one volume depleted (low UF) prescription, and two fluid overloaded (high UF) prescriptions, totaling five. Not all of the prescriptions have to be enabled by the physician. However, once enabled by physician, the multiple prescriptions provide flexibility to the patient and allow the APD machine 104 and therapy to better fit the patient's life style needs, while providing a proper therapy.


Prescription filtering 16 naturally leads to an inventory tracking feature or module 18. Different prescriptions can require the patient to store different types of PD solutions at home. For example, one type of solution may be used for nighttime exchanges, while a second type of solution is used for a last fill or day exchange. Also, the same type of solution can be provided in different dextrose quantities. System 10 determines what types and varieties of type of solutions are needed, quantities of such types and varieties, and what related disposable components are needed to carry out the enabled prescriptions. The APD machine 104 tracks how many of which type and variety of solutions are used over the course of a delivery cycle and communicates the usage to the clinician's server. The clinician's server then determines how much of which supplies need to be delivered to the patient for the next delivery cycle. When the delivery person arrives at the patient's house, he or she can scan the patient's actual remaining inventory to compare against the clinician server's expected remaining inventory. The patient's delivery can be adjusted if needed. Here, the patient's post delivery inventory is known and sent to the clinician's server. Communication is performed using a communications module discussed below.


System 10 as mentioned includes a prescription download and therapy data upload communications module 20 that transfers data between the APD software and doctor/clinician's software, e.g., via any one or more of the internet, modem and cell phone. The dialysis center could use communications module 20 for example to send updated prescriptions to the patient's APD machine. Therapy data, logs and trending data can be uploaded to the doctor/clinician's data center, so that the physician or clinician can access patient information at any time and from anywhere.


System 10 also includes an automated, e.g., twenty-four hour UF, blood pressure and body weight data collection feature 22. The APD machine determines patient twenty-four hour UF, and obtains blood pressure and body weight daily and automatically in one embodiment. A remote exchange system (“RES”) collects the patient's mid-day exchange data and feeds such data to the APD machine daily, e.g., via bluetooth or other wireless communication. Blood pressure and body weight devices can also communicate the patient's blood pressure and body weight to the APD machine, e.g., daily and wirelessly. Data collection feature 22 also includes the collection and input of therapy ranges and target information, e.g., into regimen generation feature 14.


System 10 further includes a trending and alert generation feature 24. The APD machine provides, for example, up to ninety days of trending of twenty-four hour UF, blood pressure, heart rate, body weight and prescription used. The patient, clinician and/or doctor can view these curves on the display of the APD machine, clinician computer or doctor's computer. The APD machine obtains the data necessary for the trends, sends the data to a server computer, which in turn generates and monitors the trends. The APD machine and/or clinical software monitors the patient therapy trending data and generates alerts when any of the vital parameters falls outside a physician's preset range (or outside of the range in combination with other alert filtering criteria described herein).


System 10 further includes a prescription recall and modification feature 26. Based on the data the from trend feature 24, patient 102, doctor 110 and/or dialysis center 120 may recall one approved prescription for daily use over another. For example, if the patient's UF results for the past few days have been less than expected, the patient 102, doctor 110 and/or dialysis center 120 may decide to use a higher UF prescription as opposed to a standard UF prescription. System 10 for example can store three or five different prescriptions, which have all been doctor approved. The five prescriptions may include, for example, (i) low UF, (ii) standard UF with shorter duration and higher dextrose, (iii) standard UF with longer duration and lower dextrose, (iv) high UF with shorter duration and higher dextrose, and (v) high UF with longer duration and lower dextrose.


If the patient 102, doctor 110 and/or dialysis center 120 knows that the patient has gained weight of late, a lower dextrose prescription may be selected to reduce the caloric input from the treatment. Otherwise the patient may wish to run a shorter therapy or one without a mid-day exchange for life style reasons. System 10 can be configured such that the patient chooses which prescription to run on a given day. Alternatively, the dialysis instrument 104 runs a prescription downloaded from the dialysis center 120. Further alternatively, the dialysis instrument 104 runs a prescription downloaded from the doctor 110. System 10 can run a hybrid control, which for example allows the patient to choose which prescription to run on a given day as long as the patient is making responsible choices, and if the patient does not make responsible choices, system 10 switches so that the prescription to run is set by the machine for the patient. Alternatively, if the patient does not make responsible choices, system 10 can, e.g., remove less aggressive options from the list of possible prescriptions but still allow the patient to choose from the remaining prescriptions.


Many PD patients lose residual renal function (“RRF”) over time, so that the PD therapy needs to remove more UF. Also, the patient's transport characteristics may diminish due to a loss of RRF. When trending function 24 indicates that the patient's UF is underperforming no matter which prescription the patient runs, the patient is gaining too much weight, the patient's blood pressure is too high, or a combination of these conditions occurs, system 10 according to module 26 will automatically alert that the patient's prescriptions likely need to be modified. Discussed herein are a number of measures taken so that system 10 is not oversensitive and allows for natural fluctuations in patient UF, due for example to instrument error and residual volume of fluid left in the patient's peritoneum. However, when the patient shows a pattern of underperformance sufficient to indicate that it is not a result of normal fluctuation, system 10 institutes a number of procedures to improve the patient's PD performance. For example, system 10 can call for a new PET to be performed, new regimens to be generated accordingly, and new prescriptions to be filtered from the regimens generated. Or, perhaps as an initial attempt, system 10 calls for a new set of filtering criteria (e.g., more stringent therapy criteria) to be applied to the previously generated regimens to filter out a new set of prescriptions. The new prescriptions are downloaded to the patient's dialysis instrument 104 via either a data memory card or via an internet link from the doctor's office 110 or the dialysis clinic 120.


Peritoneal Equilibration Test (“PET”)

Referring now to FIG. 2A, a cross-section from a peritoneal blood vessel illustrates the three-pores of the vessel. The three-pores each have their own toxin and UF clearance, leading to one kinetic model called the three-pore model. The three-pore model is a mathematical model that describes, correlates and predicts relationships among the time-course of solution removal, fluid transfer, treatment variables and physiological properties. The three-pore model is a predictive model that can be used for different types of dialysate, such as Dianeal®, Physioneal®, Nutrineal®, and Extraneal® dialysates marketed by the assignee of the present disclosure.


The three-pore model is based on an algorithm, which is described as follows:








d


V
D



d

t


=


J

V
C


+

J

V
S


+

J

V
L


-
L






in which:


VD is the peritoneal fluid volume;


JVC is the flow of fluid through transcellular pores or aquaporins shown in FIG. 2A;


JVS is the flow of fluid through small pores shown in FIG. 2A;


JVL is the flow of fluid through large pores shown in FIG. 2A; and


L is the peritoneal lymph flow.


Research has shown the three-pore model and a modified two-pool model are essentially equivalent in terms of UF and small solute clearance. The modified two-pool model is easier to implement than the three-pore model because it requires less computation, and thus less computer time. Research also has shown that the correlation between predicted results derived from the prediction software versus actual results measured from actual therapies have, for the most part, good correlation. Table 1 below shows results of one study (E. Vonesh et al., 1999). Correlations (rc) are accurate for urea removed, weekly urea clearance (pKt/V), total urea clearance (Kt/V), creatinine removed, weekly creatinnine clearance (pCCr), total creatinine clearance (CCr), glucose absorption and total effluent (drain volume). The UF correlation however is not as accurate due possibly to: APD device OF volumetric accuracy, residual solution volume in the patient, variation of patient's transport characteristics, and limited input points for estimating key kinetic parameters.









TABLE 1







Correlation Between Kinetic Software Model And Actual Measured Results









Three-Pore Model (PD Adequest 2.0 with APD, n = 63)










Measured
Predicted












Outcome measure
Mean
SD
Mean
SD
rc















Urea removed (g/day)
5.33
1.86
5.35
1.88
0.93


Kt/V
2.25
0.44
2.23
0.49
0.83


pKt/V
1.93
0.56
1.94
0.59
0.89


Creatinine removed (g/day)
0.72
0.31
0.72
0.31
0.93


CCr (L/week/1.73 m2)
62.89
16.11
61.64
16.26
0.87


pCCr (L/week/1.73 m2)
47.38
15.56
47.32
15.03
0.86


Glucose absorption (g/day)
103.1
61.57
105.9
54.05
0.9


Total effluent (L/day)
14.47
4.83
14.57
0.509
0.98


Net ultrafiltration (L/day)
0.983
0.672
1.09
0.784
0.23









It has been found that the certain APD devices can measure fill and drain fluid volumes very accurately. For example, the HomeChoice®/HomeChoicePRO® APD machine provided by the assignee of the present disclosure has a reported total fill and drain volume accuracy of 1% or +/−10 mL. An APD machine employing multiple exchange cycles increases the data points needed to estimate key kinetic parameters, and at the same time, reduces the possibility of introducing errors due to the residual solution volume in the patient. A new PET is accordingly proposed to improve the UF prediction accuracy, while maintaining or improving the current good prediction of small solutes (or toxins).



FIG. 2B illustrates an alternative (two-pool PD) kinetic model that system 10 can use for PET 12. The two-pool PD kinetic model of FIG. 2B, like that of FIG. 2A, is used to predict fluid and solute removal in PD to: (i) aid clinicians in the care and management of patients; (ii) assist clinicians in the understanding of the physiological mechanisms that govern peritoneal transport; and (iii) simulate a therapy outcome. A set of differential equations that collectively describe both diffusive and convective mass transport in both the body and dialysate compartments for an “equivalent” membrane core are as follows:


Body Compartment





d(VBCB)/dt=g−KPA(CB−CD)−QUsC−KRCB


Dialysate Compartment





d(VDCD)/dt=KPA(CB−CD)+QUsC


The diffusive mass transfer rate is the product of the mass transfer area coefficient, KPA, and the concentrate gradient, (CB−CD). KPA is in turn equal to the product of the solute membrane permeability (p) and transfer area (A). The convective mass transfer rate is the product of the net water removal (UF) rate, QU, the solute sieving coefficient, s, and the mean membrane solute concentration, C. KR is the renal residual function coefficient.


Using an approximation to the above equations, an analytical solution was obtained for the ultrafiltration rate, Qu, which in turn was solved analytically for the dialysis volume, VD, at time t as follows:


Dialysate Volume






V
D

=


V
D
1




{

1
+

1.5


L

P

A








i
=
1

m





K
i

*

-
1





(

1
-

s
i


)




(


C

D
,
i

1

-

C

B
,
i

1


)



(

e


-

K
i
*




t
/

V
D
1




)





}


2
/
3




e


-

Q
L
0




t
/

V
D
1










in which (i) VD1 is the dialysate volume immediately after infusion (mL); (ii) LPA′ is the hydraulic permeability transport rate (mL/min/mmol/L); (iii) Ki* is the ith solute's value of mass transfer area coefficient (mL/min); minus 1.5 QL0 (iv) si is the ith solute's sieving coefficient; (v) CD,i1 is the ith solutes dialysate concentration immediately after infusion (mmol/L); (vi) CB,i1 is the ith solutes blood concentration immediately after infusion (mmol/L); (vii) t is the time (min); and (viii) QL0 is the lymphatic absorption (ml/min). UF can accordingly be calculated from the above equation knowing infusion volume, solution concentration and dwell time. The above equations were all based initially on the Pyle-Popovich two-pool model (Vonesh et al., 1991) and were later modified by Vonesh et al. (1999) to incorporate key aspects of the three-pore model resulting in a modified two-pool model which is also referred to as a modified three-pore model (Vonesh et al., 1999). All subsequent references to a two-pool model or three-pore model refer to the modified model described by Vonesh et al. (1999).


To estimate hydraulic permeability (LPA, mL/min/mmol/L) and lymphatic flow rate, (QL, mL/min) for the modified version of the above equation, two VD values at corresponding dwell time t1, and t2 are needed. The VD (fill volume+UF) value is difficult to measure due to the incomplete drain (cycler) and resulting UF measurement errors. PET 12 as shown in FIG. 3 uses multiple, e.g., five, dwell volume (VD) measurements at multiple (five) different corresponding dwell times, e.g., overnight, four-hour, two-hour, one-hour and half-hour, to improve the accuracy of LPA and QL estimation and thus improve the UF prediction accuracy.


In one embodiment, the PET 12 of the present disclosure begins with a UF versus dwell time evaluation performed over the course of two treatments (e.g., two evenings or back to back) by directly estimating the patient's fluid transport parameters and correlating the measured parameters with other PET results. UF removed for a particular type of dialysate is measured by filling the patient with fresh dialysate, allowing the solution to dwell within the patient's peritoneum for a prescribed time, draining the patient, and subtracting the fill volume from the drain volume to determine a UF volume for that particular dwell time.


In one implementation, on a first night, using a standard dialysate, such as a 2.5% dextrose Dianeal® dialysate, the APD machine runs four separate two liter fill/drain cycles: a first cycle at a thirty minute dwell; second cycle at a sixty minute (one hour) dwell; third cycle at a 120 minute (two hour) dwell; and a fourth cycle at a 240 minute (four hour) dwell. Total of all dwell times is about seven hours, thirty minutes, which including the time needed for filling and draining consumes about a typical nine and one-half hour total therapy time. The APD machine records fill volume, drain volume and actual dwell time for each cycle. The fill volume may be slightly less or more than two liters depending for example on how much fresh dialysate is actually existing initially in the bag and how empty the APD machine is able to make the bag. In any case, the fill and drain volumes are recorded accurately so that the resulting calculated UF is also accurate.


In an alternative embodiment, to increase accuracy the patient weighs the dialysate bag before fill and after drain. The weight values can be sent wirelessly from the scale to the APD machine (as discussed in detail below). The patient alternatively enters weight data manually. The APD machine subtracts the pre-fill weight from the post-drain weight to accurately determine a UF value, which is matched with the actual dwell time.


The dwell time can be: (i) the time between the end of a fill and the beginning of the corresponding drain; (ii) the time between the beginning of a fill and the end of the corresponding drain; and (iii) in one preferred embodiment the time between the end of a fill and the end of the corresponding drain. In any of the scenarios, the actual dwell time will likely be slightly more or less than the prescribed dwell time. For example, in scenarios (ii) and (iii), a kinked line during drain will lengthen drain time and thus recorded dwell time. In scenario (ii) a kinked line during fill will lengthen fill time and thus recorded dwell time. The APD machine records the actual dwell times for use as shown below. The actual, not the prescribed times, are used so that any difference between actual and prescribed dwell times does not introduce error into the UF predictive model.


On the next or second night, using the standard (e.g., 2.5% dextrose Dianeal®) dialysate, the APD machine patient runs a single fill volume with a 480 minute or eight hour dwell. The APD machine records actual dwell time (according to any of the scenarios (i) to (iii) above) and matches the actual dwell time with the actual UF recorded (e.g., via the APD or weigh scale) in the APD machine.


At the end of two days, the APD machine has recorded five UF/dwell time data points (more or less data points could be achieved, however, the above five dwell times are acceptable and achievable over two standard eight hour therapies). In one embodiment, the APD machine sends the UF/dwell time data points to a server computer located at a dialysis clinic 120 or doctor's office 110 (FIGS. 15A, 15B, 16A and 16B) at which the remainder of the PET 12 is performed. Various embodiments for linking the APD machine to a server computer are shown herein, for example, an electronic mail link can be used to transport data. In another embodiment, the APD machine records the five (or other number) data points onto a patient data card that the patient inserts into the APD machine. The patient then brings the data card and accompanying data to the dialysis center 120 or doctor's office 110 to complete PET 12.


The patient then travels to the dialysis center or doctor's office, e.g., the next day. The patient is filled an additional time and drained typically after four hours. Blood and dialysate samples are taken for example at two hours and four hours. A second four-hour dwell UF data point can be taken and compared to the first four-hour dwell UF data point for additional accuracy. Alternatively, the second blood sample is taken at four hours but the patient is drained at, e.g., five hours, providing an additional UF dwell data point.



FIG. 3 illustrates a plot of the UF data points for the different actual dwell times. The server computer, or other clinical software computer is programmed to fit a curve 30 to the five data points. Curve 30 fills the gaps between the different recorded dwell periods (e.g., at 0.5 hour, one hour, two hours, four hours and eight hours) and thus predicts the UF that will be removed for any dwell period within the eight hour range and beyond, and for the particular dialysate and dextrose level used.


The osmotic gradient created by the dextrose in the dialysis solution decreases with time as dextrose is absorbed by the body. The patient's ultrafiltration rate accordingly begins at a high level and decreases over time to a point at which the rate actually becomes negative, such that the patient's body begins to reabsorb fluid. Thus UF volume as shown in the graph can actually decrease after a certain dwell time. One of the goals of the present disclosure is to learn the patient's optimal UF dwell time, which may be dextrose level dependent, and incorporate the optimal dwell time(s) into the prescriptions discussed in detail below.


In the illustrated embodiment, curve 30 predicts UF removed for 2.5 percent dextrose. Once the curve is fitted for a particular patient, the curve can then be calculated using the kinetic model to predict UF/dwell time values for other dialysates and other dextrose levels, e.g., for 1.5 percent and 4.25 percent dextrose levels. As shown in FIG. 3, for 2.5 percent dextrose, curve 30 has a maximum UF removed dwell time of about three hundred minutes or five hours. Five hours is likely too long a dwell time, however, UF for a dwell time of two hours or 2.5 hours comes fairly close to the maximum UF dwell time. A dwell time of two hours comes much closer to the maximum for 1.5 percent dextrose. 4.25 percent dextrose lends itself to longer dwells as seen in FIG. 3. For example, a single day exchange is a good application for 4.25 percent dextrose.


Besides predicting optimal UF, the five or six UF data points, blood testing and dialysate testing data are taken using a particular dialysate, such as 2.5 percent dextrose Dianeal® dialysate. Each of the UF, blood and dialysate the data are used to generate mass transfer area coefficient (“MTAC”) data and hydraulic permeability data to classify the patient's transport and UF characteristics. The MTAC data and hydraulic permeability data can then also be applied physiologically to other types of dialysates, such as 1.5 or 4.5 percent dextrose solutions and for different formulations, such as Extraneal® and Nutrineal® dialysates provided by the assignee of the present disclosure. That is, curve 30 is shown for one concentration. However, once the kinetic model and LPA and QL (from PET test results) are known, system 10 could calculate the VD according to the algorithm above, for each the solution type, dextrose concentration, dwell time, and fill volume. An LPA value of 1.0 (mL/min/mmol/L) and a QL value of 0.8 ml/min were used in the simulation for curve 30 (2.5% dextrose) and the curves for 1.5% dextrose and 4.25% dextrose in FIG. 3.


A kinetic modeling simulation was conducted using the above algorithm for dialysate volume VD, and the following data shown in Table 2 was generated, which shows a comparison of UF estimation and associated error using a known PET and PET 12. Data showed that the PET 12 improved the UF prediction accuracy significantly compared with a known PET.









TABLE 2







UF Prediction Accuracy Using PET 12













True UF with
UF Prediction
UF Prediction
UF Prediction
UF Prediction


Dwell Time
Dextrose of 2.5%
Using Known PET
Error Using
Using PET 12
Error Using


(min)
(mL)
(mL)
Known PET
(mL)
PET 12















30
86.73
158.81
83.1%
111.48
28.5%


60
158.74
281.52
77.3%
201.28
26.8%


90
217.88
374.37
71.8%
272.49
25.1%


120
265.71
442.21
66.4%
327.68
23.3%


150
303.61
488.92
61.0%
368.98
21.5%


180
332.76
517.70
55.6%
398.25
19.7%


210
354.20
531.24
50.0%
417.04
17.7%


240
368.86
531.79
44.2%
426.72
15.7%


270
377.54
521.28
38.1%
428.48
13.5%


300
380.95
501.35
31.6%
423.35
11.1%


330
379.73
473.44
24.7%
412.23
8.6%


360
374.42
438.79
17.2%
395.92
5.7%


390
365.53
398.44
9.0%
375.11
2.6%


420
353.49
353.34
0.0%
350.42
−0.9%


450
338.69
304.29
−10.2%
322.39
−4.8%


480
321.48
252.00
−21.6%
291.49
−9.3%


510
302.16
197.07
−34.8%
258.15
−14.6%


540
281.00
140.03
−50.2%
222.73
−20.7%









Automated Regimen Generation

As seen in FIG. 1, present system 10 includes a therapy regimen generation module 14. Regimen generation module 14 includes a plurality of prediction algorithms. The prediction algorithms use the above calculated patient transport and UF characteristics from PET 12, target information and other therapy input information to generate the regimens. Regimen generation module 14 in one embodiment generates all of the possible therapy regimens that meet entered target requirements using the therapy input information and calculated patient transport and UF characteristics. The regimens generated are many as shown below. The prescription generation module 16 then filters the regimens generated at module 14 to yield a finite number of optimized prescriptions that can be performed on the APD machine for the particular patient.



FIG. 4A shows one data entry screen for regimen generation module 14. Data entered into the screen of FIG. 4A is obtained from PET 12. FIG. 4A provides PET 12 data inputs for the dialysis center clinical nurse. The data includes the dialysate UF measurement, dialysate lab test results (urea, creatinine and glucose), and blood test results (serum urea, creatinine and glucose). Specifically, an “Overnight Exchange” module of FIG. 4A provides overnight exchange data input, including: (i) % dextrose, (ii) solution type, (iii) volume of solution infused, (iv) volume of solution drained, (v) dwell time(s), (vi) dialysate urea concentration (lab test result from drained dialysate), and (vii) dialysate creatinine concentration (lab test results from drained dialysate). A “Four-Hour Equilibration” module of FIG. 4A provides four-hour exchange data input, which is normally obtained from a patient blood sample taken in a clinic, the data including: (i) % dextrose, (ii) solution type, (iii) volume of solution infused, (iv) volume of solution drained, (v) infusion time, and (vi) drain time. A “Data” module of FIG. 4A provides four-hour exchange data input, including: (i) serum #1 sample time (normally 120 minutes after infusion of the dialysate), urea, creatinine, and glucose concentration, which are the clinician's inputs, “Corrected Crt” is a corrected creatinine concentration that the software algorithm calculates; (ii), (iii) and (iv) for dialysate #1, #2 and #3, sample time, urea, creatinine, and glucose concentration, which are clinician's inputs, “Corrected Crt” and “CRT D/P” (dialysate creatinine/plasma creatinine) which are calculated by software.


In FIG. 4B, the “serum concentration” module involves a blood test that is typically performed after the regular APD therapy, preferably in the morning, leading to result sent to the lab for analysis of creatinine, urea, glucose, and albumin. Serum concentration (sometimes called plasma concentration) is the lab test results of blood urea, creatinine and glucose concentration. A patient with end-stage kidney disease has blood urea and creatinine levels that are much higher than for people with functioning kidneys. The glucose concentration is important because it measures how much glucose the patient's body absorbs when using a dextrose-based solution. The “24-hour dialysate and urine collection” module of FIG. 4B shows that the patient has no residual renal function, thus produces no urine. The overnight collection data is used for patient residual renal function (“RRF”) calculation, APD therapy results (fill, drain and lab test results), and for measuring the patient height and weight to calculate the patient's body surface area (“BSA”). As seen in the example for the second day of PET 12, (eight hour dwell), 8000 milliliters of dialysate was infused into the patient, 8950 milliliters of dialysate was removed from the patient, yielding a net UF volume of 950 milliliters. The dialysate is sent to the lab for analysis of urea, creatinine, and glucose. A “weekly clearances” module calculates the weekly Urea Kt/V and weekly creatinine clearance (“CCL”), which are parameters that doctors use to analyze if patient has adequate clearance.



FIG. 4C of regimen generation feature 14 shows a sample screen in which system 10 calculates mass transfer coefficients (“MTAC's”) and water transport parameters using the data of screens 4A and 4B and stored algorithms. RenalSoft™ software provided by the assignee of the present invention is one known software for calculating the data shown in FIG. 4C from the input data of FIGS. 4A and 4B. Some of the data calculated and shown in FIG. 4C is used in an algorithm for regimen generation feature 14. Specifically, the regimen generation algorithm uses the MTAC's for urea, creatinine and glucose, and the hydraulic permeability to generate the regimens



FIG. 4D of regimen generation feature 14 shows the clinician or doctor the predicted drain volumes determined based on the hydraulic permeability of FIG. 4C versus the actual UF measured from PET 12. The results are shown for an overnight exchange (e.g., night one or night two of PET 12) and the four-hour dwell test performed at the dialysis center 120 or doctor's office 110. The difference between actual drain volume UF and predicted drain volume is calculated so that the clinician or doctor can view the accuracy of PET 12 and the prediction routines of FIGS. 4A to 4D for drain volume and UF. To generate the predicted drain volumes, the operator enters a fluid absorption index. The machine also calculates a fluid absorption value used in the prediction of drain volume. As seen in FIG. 4D, the software of system 10 has calculated the fluid absorption rate to be 0.1 ml/min based on values entered from the patient's PET. As seen at the top of FIG. 4D, the actual versus predicted drain volume for the overnight exchange was 2200 ml versus 2184 ml. The four hour (day) predicted drain versus the actual drain was 2179 ml versus 2186 ml. The bottom of FIG. 4D shows the actual versus predicted drain values for a more common fluid absorption rate of 1.0 ml/min, which are not as close to one another as those for the 0.1 ml/min fluid absorption rate. The system can then ask the clinician to enter a fluid absorption rate that he/she would like to use for this patient when predicting UF, which is normally somewhere between and including 0.1 ml/min and 1.0 ml/min.



FIG. 5 illustrates one possible regimen calculation input table for regimen generation feature 14. The regimen calculation input table inputs Clinical Targets data including (a) minimum urea clearance, (b) minimum urea Kt/V, (c) minimum creatinine clearance, (d) maximum glucose absorption, and (e) target UF (e.g., over twenty-four hours).


The table of FIG. 5 also inputs Night Therapy Parameters data, such as (i) therapy time, (ii) total therapy volume, (iii) fill volume, (iv) percent dextrose for the chosen solution type, and possibly (v) solution type. Here, dwell times and number of exchanges are calculated from (ii) and (iii). Dwell time can alternatively be set according to the results of PET 12 as discussed above, which can be used in combination with at least one other input, such as, total time, total volume and fill volume to calculate the remainder of total time, total volume and fill volume inputs. For example, if dwell time, total volume and total time are set, system 10 can calculate the fill volume per exchange and the number of exchanges. The Night Therapy Parameters input also includes last fill inputs, such as (i) dwell time, (ii) last fill volume, and (iii) percent dextrose for the chosen solution type.


The table of FIG. 5 also inputs Day Therapy Parameters data, such as (i) therapy time, (ii) day fill volume, (iii) number of cycles, (iv) percent dextrose for the chosen solution type, and possibly (v) solution type. Day exchanges may or may not be performed.


Solution type for the night and day therapies is chosen from a Solutions portion of the input table of FIG. 5, which inputs available dextrose levels, solution formulation (e.g., Dianeal®, Physioneal®, Nutrineal®, and Extraneal® dialysates marketed by the assignee of the present disclosure) and bag size. Bag size can be a weight concern especially for elderly patients. Smaller bags may be needed for regimens that use a different last fill and/or day exchange solution or dextrose level. Smaller bags may also be needed for regimens that call for a dextrose level that requires a mix from two or more bags of standard dextrose level (e.g., dextrose level of 2.0%, 2.88%, 3.38%, or 3.81%) listed under the Solutions portion of the table of FIG. 5. Mixing to produce customized dextrose level is discussed below in connection with FIG. 14. Solution bag inventory management is also discussed below in connection with FIGS. 10 to 13.


The regimen calculation input table of FIG. 5 also illustrates that many of the inputs have ranges, such as plus/minus ranges for the Clinical Targets data and minimum/maximum/increment ranges for certain Night Therapy Parameters data and Day Therapy Parameters data. Once the clinician or doctor starts to complete the table of FIG. 5, system 10 automatically places suggested values in many of the other cells, minimizing the amount of entries. For example, the solutions available under Solutions data can be filled automatically based upon the solutions that have been indicated as available by the dialysis center, which is further based the available solution portfolio approved for a specific country. In another example, system 10 can adjust the fill volume increments for Night Therapy Parameters data automatically to use all of the available solutions (e.g., when a twelve liter therapy is being evaluated, the number of cycles and the fill volumes can range as follows: four-3000 mL fills, five-2400 mL fills, six-2000 mL fills, and seven-1710 mL fills). System 10 allows the operator to change any of the suggested values if desired.


The software of system 10 calculates the predicted outcomes for all of the possible combinations of parameters based upon the ranges that are entered for each parameter. As seen in FIG. 5, some regimens will have “adequate” predicted outcomes for urea clearance, creatinine clearance and UF that meet or exceed the minimum criteria selected by the clinician. Others will not. Selecting “Only Display Adequate Regimens” speeds the regimen generation process. Some patients may have hundreds of regimens that are adequate. Others may have only few, or possibly even none. When none are adequate, it may be necessary to display all regimens so that the regimens that are close to meeting the target requirements can be identified for filtering. Filtering when starting with all regimens displayed provides the clinician/doctor the most flexibility when trying to find the best prescription for the patient.


System 10 feeds all of the therapy combinations into outcome prediction software and tabulates the results in a table that system 10 can then filter through as shown below in connection with prescription filtering module 16. One suitable software is RenalSoft™ software provided by the assignee of the present disclosure. The combinations take into account the different ranges entered above in the regimen calculation input table of FIG. 5.


Table 3 below shows the first ten results (of a total of 270 results) for one set of data inputted into system software. Here, a 1.5% night dextrose solution is chosen. No day exchange is allowed. Results are shown generated for a standard PD therapy but could alternatively or additionally be generated for other types of PD therapies, such as a tidal therapy. FIG. 5 has check boxes that allow either one or both of continuous cycling peritoneal dialysis (“CCPD”) or tidal therapies (both APD therapies) to be included in the regimen generation process.









TABLE 3







APD Therapy





















Night
Night
Night
Number


Last Fill
Number


Day Fill



Night
Ther
Ther
Fill
of Night
Last Fill
Last Fill
Dwell
of Day
Day Fill
Day Fill
Dwell



Dex
Time
Volume
Volume
Exch
Volume
Solution
Time
Exch
Volume
Solution
Time






















1
1.5
7
8
2
4
0
0
0
0
0
0
0


2
1.5
7
8
2.2
3
0
0
0
0
0
0
0


3
1.5
7
8
2.4
3
0
0
0
0
0
0
0


4
1.5
7
8
2.6
3
0
0
0
0
0
0
0


5
1.5
7
8
2.8
3
0
0
0
0
0
0
0


6
1.5
7
8
3
2
0
0
0
0
0
0
0


7
1.5
7
9
2
4
0
0
0
0
0
0
0


8
1.5
7
9
2.2
4
0
0
0
0
0
0
0


9
1.5
7
9
2.4
3
0
0
0
0
0
0
0


10
1.5
7
9
2.6
3
0
0
0
0
0
0
0









As stated, Table 3 illustrates ten of two-hundred seventy valid combinations possible with a 1.5% night dextrose level. The same two-hundred seventy combinations will also exist for 2% dextrose level, 2.5%, etc., night dextrose level. An equal number of valid combinations is created for each possible dextrose level when a day fill is added. Further, the last fill dwell time can be varied to create even more valid combinations.


Prescription Filtering

As shown above, system 10 allows the doctor/clinician to prescribe values for clinical targets and therapy inputs, such as patient fill volume, total therapy volume, total therapy time, etc., and generates a table, such as Table 3, containing all therapies that meet all of the clinical requirements. The table of therapies that meet all of the clinical requirements can then be automatically filtered and sorted based upon parameters such as total night therapy time, therapy solution cost, therapy weight, etc.


The software uses one or more algorithm in combination with the therapy combinations (e.g., of Table 3) and the patient physiologic data generated via PET 12 as shown in connection with FIGS. 4A to 4D to determine predicted therapy results. Therapy combinations (e.g., of Table 3) that meet the Clinical Targets of FIG. 5 are filtered and presented to the clinician, nurse or doctor as candidates to become prescribed regimens.



FIGS. 6A and 6B illustrate examples of filters that the doctor or clinician can use to eliminate regimens. In FIG. 6A, minimum Urea Kt/V removal is increased from 1.5 in FIG. 5 to 1.7 in FIG. 6A. In one embodiment, the range of +0 to −0.2 in FIG. 5 is applied automatically to the new minimum value set in FIG. 6A. Alternatively, system 10 prompts the user to enter a new range or keep the same range. A Boolean “And” operator is applied to the new minimum Urea Kt/V to specify that the value must be met, subject to the applied range, in combination with the other clinical targets.


In FIG. 6B, minimum twenty-four hour UF removal is increased from 1.0 in FIG. 5 to 1.5 in FIG. 6B. In one embodiment, the range of +0 to −0.2 in FIG. 5 is again applied automatically to the new minimum value set in FIG. 6B. Alternatively, system 10 prompts the user to enter a new daily UF range or keep the same UF range. Again, a Boolean “And” operator is applied to the new minimum twenty-four hour UF to specify that the value must be met, subject to the applied range, in combination with the other clinical targets. The clinician and patient are free to impose additional, clinical and non clinical requirements, such as: solution cost, solution bag weight, glucose absorbed, night therapy time, day fill volume, night fill volume.


Referring now to FIG. 7A, the regimens that meet the Clinical Targets and other inputs of FIG. 5 and the additional filtering of FIGS. 6A and 6B are shown. As seen, each of the regimens is predicted to remove at least 1.5 liters of UF per day and has a minimum Urea Kt/V removal of greater than 1.5.


Regimen 36 is highlighted because it has the smallest day fill volume (patient comfort), the lowest solution weight (patient convenience), and the next to lowest glucose absorption value (least dietary impact). Thus, regimen 36 is chosen and prescribed by a doctor as a standard UF regimen.


The patient, clinician and/or doctor can also pick one or more additional prescription for approval that also meets with a patient's lifestyle needs. Suppose for example that the patient is a member of a bowling team during the winter months that competes in a Saturday night league. He drinks a little more than normal while socializing. The patient and his doctor/clinician agree that a therapy regimen that removes about 20% more UF should therefore be performed on Saturday nights. Also, on bowling nights, the patient only has seven hours to perform therapy rather a standard eight hour therapy. Filtered potential prescription 34 highlighted in FIG. 7A is accordingly approved as a higher UF prescription, which uses a higher dextrose concentration to remove the extra UF and does so in the required seven hours.


Further, suppose that the patient lives in a southern state and does yard work on the weekends during the summer months (no bowling league) and accordingly loses a substantial amount of body fluid due to perspiration. The doctor/clinician and patient agree that less than 1.5 liters of UF needs to be removed on such days. Because FIG. 7A only shows regimens that remove at or over 1.5 liters of UF, further filtering is used to provide low UF regimens for possible selection as a low UF prescription.


The doctor or clinician uses an additional filtering of the twenty-four hour UF screen of FIG. 6C to restrict the prior range of daily UF that the regimes must meet. Here, the doctor/clinician looks for regimes having daily UF removals of greater than or equal to 1.1 liter and less than or equal to 1.3 liters. The Boolean “And” operator is selected such that the therapy meets all of the other clinical requirements of FIGS. 5 and 6A.


Referring now to FIG. 7B, the regimens that meet the Clinical Targets and other inputs of FIG. 5 and the additional filtering of FIGS. 6A and 6C are shown. As seen, each of the regimens is predicted to remove at or between 1.1 and 1.3 liters of UF per day, while meeting the minimum Urea Kt/V removal of greater than 1.5 and other clinical targets. The doctor/clinician and patient then decide on a tidal therapy regimen 58 (highlighted), which does not require a day exchange, and requires the shortest night therapy time. The doctor then prescribes the therapy.


Referring now to FIGS. 8A to 8C, the three agreed-upon high UF, standard UF and low UF prescriptions are illustrated, respectively. The prescriptions are named (see upper-right corner), so that they are easily recognizable by the patient 102, doctor 110 and clinician 120. While three prescriptions are shown in this example, system 10 can store other suitable numbers of prescriptions as discussed herein. System 10 downloads the prescription parameters onto a data card in one embodiment, which is then inserted in the APD machine 104, transferring the prescriptions to the non-volatile memory of the APD machine. Alternatively, the prescriptions are transferred to APD machine 104 via a wired data communications link, such as via the internet. In one embodiment, the patient is free to choose which prescription is performed on any given day. In an alternative embodiment, the data card or data link transfer of the prescriptions is entered into the memory of the dialysis instrument, such that the instrument runs a prescribed treatment each day automatically. These embodiments are discussed in detail below in connection with the prescription recall and adjustment module 26. In any case, when the patient starts any of the therapies, system 10 provides instructions on which solution bags to connect to a disposable cassette for pumping since the therapies may use different solutions.



FIGS. 9A to 9E illustrate another filtering example for module 16. FIG. 9A illustrates filtered settings on the left and corresponding results on the right, which yield 223 possible regimens. In FIG. 9B, the clinician further filters to regimens by limiting the day fill volume (patient comfort) to 1.5 liters. Such filtering reduces the possible regimens to 59. In FIG. 9C, the clinical software further filters the regimens by decreasing the regimens to 19. In FIG. 9D, the clinical further filters the available regimens by reducing the glucose absorbed to 500 Kcal/day. Such action reduces the available regimens to three.



FIG. 9E shows the three filtered regimens that can either be prescribed by the physician or discarded to enable another filtering exercise to be performed. The exercise of FIGS. 9A to 9D shows that prescription optimization is made convenient once the patient's physiological characteristics are known. FIGS. 9A to 9D also show suitable lists of possible filtering criteria.


Inventory Tracking

Referring now to FIGS. 10 to 13, one embodiment for an inventory tracking subsystem or module 18 of system 10 is illustrated. As discussed herein, system 10 generates agreed-upon prescriptions, such as high UF, standard UF and low UF prescriptions as shown in connection with FIGS. 8A to 8C. The different prescriptions require different solutions as seen in FIG. 10. FIG. 10 shows that the standard UF prescription uses twelve liters of 1.5% Dianeal® dialysate and two liters of Extraneal® dialysate. The high UF prescription uses fifteen to eighteen (depending on alternate dialysis used) liters of 1.5% Dianeal® dialysate and two liters of Extraneal® dialysate. The low UF prescription uses twelve liters of 1.5% Dianeal® dialysate and three liters of 2.5% Dianeal® dialysate.



FIG. 11 shows an example screen that a server in a dialysis center 120 can display for a patient having the above three prescriptions. The screen of FIG. 11 shows the minimum base supply inventory needed for the three prescriptions over a delivery cycle. The screen of FIG. 11 shows that the patient is to be supplied the solutions needed to perform thirty-two standard UF prescription therapies. The patient is to be supplied the solutions needed to perform six high UF prescription therapies. The patient is also to be supplied the solutions needed to perform six low UF prescription therapies. The patient is further to be provided one “ultrabag” case (six 2.5 liter bags). The stem of a Y-shaped ultrabag tubing set can connect to the patient's transfer set. An empty bag is attached to the one leg of the Y and a full bag is pre-attached to the other leg of the Y. The ultrabag is used to perform CAPD exchanges if the APD machine breaks, if power is lost and the APD machine cannot operate, or if the patient is traveling and his/her supplies do not arrive on time.


Additionally, the patient is also to be provided with forty-five disposable sets (one used for each treatment), which includes a disposable pumping cassette, bag line, patient line, drain line, heater bag and associated clamps and connectors. The patient is provided with low (1.5%), medium (2.5%) and high (4.25%) dextrose concentration dialysis solutions, so that the patient can remove more or less fluid by switching which dextrose level is used. Prescription flexibility (including mixing) could increase the total number of bags needed for a given month to about forty-five days worth of solutions.


The patient is also to be provided forty-five caps or flexicaps, which are used to cap the patient's transfer set when the patient is not connected to the cycler. The flexicaps contain a small amount of povidone iodine to minimize the potential for bacterial growth due to touch contamination.



FIG. 12 shows an example screen that the dialysis center 120 can display for a patient having the above three prescriptions. The screen of FIG. 12 shows the expected actual patient inventory at the time a new delivery of inventory is to be made. That is, the screen of FIG. 12 shows what inventory the server computer thinks will be at the patient's home when the delivery person arrives. In the example, the server computer expects that when the delivery person arrives at the patient's home, the patient will already have: (i) five cases (two bags per case) of 1.5% Dianeal® dialysate containing six liter bags, (ii) one case (four bags per case) of 2.5% Dianeal® dialysate containing three liter bags, (iii) one case (six bags per case) of Extraneal® dialysate containing two liter bags, (iv) twenty-four (out of a case of thirty) disposable sets, each including the apparatuses described above, (v) two 1.5%, 2.5 liter Ultrabags of dialysate (out of a case of 6), and six caps or flexicaps (out of a case of thirty).



FIG. 13 shows an example screen that the server of dialysis center 120 can display for a patient having the above three prescriptions. The screen of FIG. 13 shows the actual inventory that will be delivered to the patient. That is, the screen of FIG. 13 shows the inventory difference between what the patient is supposed to have at the start of the inventory cycle and what the server computer thinks will be at the patient's home when the delivery person arrives. In the example, the patient needs: (i) eighty-eight, six liter bags of 1.5% Dianeal® dialysate, has ten at home, reducing the need to seventy-eight bags or thirty-nine cases (two bags per case); (ii) six, three liter bags of 2.5% Dianeal® dialysate, has four at home, reducing the need to two bags or one case (four bags per case, resulting in two extra delivered); (iii) thirty-eight, two liter bags of Extraneal® dialysate, has six at home, reducing the need to thirty-two bags or six cases (six bags per case, resulting in four extra delivered); (iv) forty-five disposable sets, has twenty-four at home, reducing the need to twenty-one or one case (thirty per case, resulting in nine extra disposable sets delivered); (v) six, 2.5 liter 1.5% Ultrabags, has two at home, reducing the need to four bags or one case (six bags per case, resulting in two extra ultrabags delivered); and (vi) forty-five flexicaps, has thirty-six at home, reducing the need to nine or one case (thirty-six per case, resulting in twenty-seven extra flexicaps delivered).


In one embodiment, the dialysis center server database of the inventory tracking module 18 maintains and knows: (a) how much of each dialysate and other supplies the patient is supposed to have at the beginning of a delivery cycle; (b) the patient's different prescriptions, solutions used with each, and the number of times each prescription is to be used over the delivery cycle; and (c) accordingly how much of each dialysate the patient is supposed to use over a delivery cycle. Knowing the above, the inventory tracking server can calculate how much of each solution and other supplies needs to be delivered at the next delivery date. Chances are the patient has consumed more or less of one or more solution or other item than expected. For example, the patient may have punctured a solution bag, which then had to be discarded. The patient may misplace a solution bag or other item. Both instances result in more inventory being consumed than expected. On the other hand, the patient may skip one or more treatment over the course of the delivery cycle, resulting in less inventory being consumed than expected.


In one embodiment, the inventory tracking module or subsystem 18 of system 10 expects that the estimated amount of solutions and other supplies is close to the actual amount needed. If too much inventory is delivered (patient used less than prescribed), the delivery person can deliver the extra inventory to the patient and scan or otherwise note the additional inventory, so that it can be saved into the inventory server memory. For the next cycle, system 10 updates (e.g., increases) (a) above, namely, how much of each dialysate and other supplies the patient is supposed to have at the beginning of a delivery cycle. Alternatively, the delivery person only delivers the needed amount of inventory, so as to make the patient's actual inventory at the beginning of the delivery cycle equal to the expected inventory at (a) above. If not enough inventory is scheduled for delivery (patient lost or damaged solution or related supplies for example), the delivery person brings extra inventory so as to make the patient's actual inventory at the beginning of the delivery cycle equal to the expected inventory at (a) above.


The inventory subsystem 18 of system 10 in one embodiment maintains additional information such as the individual cost of the supplies, the weight of the supplies, alternatives for the required supplies if the patient depletes the required supplies during the delivery cycle. As shown above in FIGS. 7A and 7B, the regimen generation software in one embodiment uses or generates the weight and cost data as a factor or potential factor in determining which regimes to be selected as prescriptions. The server of the dialysis center 120 downloads (or transfers via data card) the alternative solution data to the patient's APD Cycler. In one implementation, when a patient starts a therapy, the patient is notified of the particular solution bag(s) needed for that day's particular prescription. If the patient runs outs of one type of solution, the system can provide an alternative based upon the solutions held in current inventory.


Dextrose Mixing

As shown above in FIG. 5, system 10 contemplates using a plurality of different dextrose levels for each of the different brands or types of dialysates available, which increases the doctor/clinician's options in optimizing prescriptions for the patient. The tradeoff with dextrose is generally that higher levels of dextrose remove more UF but have higher caloric input, making weight control for the patient more difficult. The converse is also true. Dialysate (at least certain types) is provided in different standard dextrose levels including 0.5%, 1.5%, 2.5% and 4.25%. As seen in FIG. 6, night dextrose, last fill dextrose and day dextrose can be chosen to have any of the above standard percentages or to have a blended dextrose level of 2.0%, 2.88%, 3.38% or 3.81%. System 10 uses the dialysis instrument 104 to mix the standard percentages to create the blended percentages. It is believed that since each of the standard dextrose level dialysates has been approved by the Federal Drug Administration (“FDA”) and that the blended dextrose levels are within approved levels, that such mixing would meet readily with FDA approval.









TABLE 4







Glucose-Based Solutions Mixing Ratios and Concentrations.













Available




Dextrose
Solutions of


Dextrose

Concentration (%)
Dextrose


Concentration (%)
Mixing Ratio
after mixing
Concentration (%)





1.5 and 2.5
1 to 1
2.00
1.5


1.5 and 4.25
1 to 1
2.88
2.0


2.5 and 4.25
1 to 1
3.38
2.5


2.5 and 4.25
1 to 3
3.81
2.88





3.38





3.81





4.25









Using 1:1 or 1:3 mixing shown in Table 4 generates more dextrose solutions, providing more therapy options for clinicians. At the same time, these mixing ratios will use all the solution in a container, resulting in no waste.


Referring now to FIG. 14, dialysis instrument 104 illustrates one apparatus capable of producing the blended dextrose level dialysates. Dialysis instrument 104 is illustrated as being a HomeChoice® dialysis instrument, marketed by the assignee of the present disclosure. The operation of the HomeChoice® dialysis instrument is described in many patents including U.S. Pat. No. 5,350,357 (“the '357 patent”), the entire contents of which are incorporated herein by reference. Generally, the HomeChoice® dialysis instrument accepts a disposable fluid cassette 50, which includes pump chambers, valve chambers and fluid flow pathways that interconnect and communicate fluidly with various tubes, such as a to/from heater bag tube 52, a drain tube 54, a patient tube 56 and dialysate supply tubes 58a and 58b. While FIG. 14 shows two supply tubes 58a and 58b, dialysis instrument 104 and cassette 50 can support three or more supply tubes and thus three or more supply bags. Further, as seen in the '357 patent, one or both supply tubes 58a and 58b can Y-connect to two supply bags if more supply bags are needed.


In one embodiment, system 10 pumps fluid from a supply bag (not shown), through one of supply tubes 58a or 58b, cassette 50, to a warmer bag (not shown) located on a heater tray of APD 104. The warmer bag provides an area for the solutions to mix before being delivered to the patient. In such a case, the warmer bag can be fitted with one or more conductive strip, which allows a temperature compensated conductivity reading of the mixed solution to be taken to ensure that the solutions have been mixed properly. Alternatively, APD 104 uses inline heating in which case the mixing is done in the tubing and the patients peritoneum.


To operate with cassette 50, the cassette is compressed between a cassette actuation plate 60 and a door 62. The '357 patent describes a flow management system (“FMS”), in which the volume of fluid pumped from each pump chamber (cassette 50 includes two in one embodiment), after each pump stroke is calculated. The system adds the individual volumes determined via the FMS to calculate a total amount of fluid delivered to and removed from the patient.


System 10 contemplates proportioning the pump strokes from different standard dextrose supplies using FMS to achieve a desired blended dextrose. As seen at Table 4 above, a 1.5% standard dextrose supply bag can be connected to supply line 58a, while a 4.25% standard dextrose supply bag is connected to supply line 58b. Dialysis machine 104 and cassette 50 pump dialysate from each supply bag in a 50/50 ratio using FMS to achieve the 2.88% blended dextrose ratio. In another example, a 2.5% standard dextrose supply bag is connected to supply line 58a, while a 4.25% standard dextrose supply bag is connected to supply line 58b. Dialysis machine 104 and cassette 50 pump dialysate from each supply bag in a 50/50 ratio using FMS to achieve the 3.38% blended dextrose ratio. In a further example, a 2.5% standard dextrose supply bag (e.g. 2 L bag) is connected to supply line 58a, while a 4.25% standard dextrose supply bag (e.g. 6 L bag) is connected to supply line 58b. Dialysis machine 104 and cassette 50 pump dialysate from each supply bag in a 25/75 (2.5% to 4.25%) ratio using FMS to achieve the 3.81% blended dextrose ratio.


The first two examples can include a connection of a six liter bag of dialysate to each of lines 58a and 58b. In the third example, a three liter 2.5% standard dextrose supply bag is connected to supply line 58a, while a three liter 4.25% supply bag is Y-connected to a six liter 4.25% supply bag, which are both in turn connected to supply line 58b. Dialysis machine 104 and cassette 50 pump dialysate from each supply bag to a heater bag in one embodiment, which allows the two different dextrose dialysates to fully mix before being pumped from the heater bag to the patient. Accordingly, system 10 can achieve the blended dialysate ratios shown in FIG. 6 and others by pumping different standard dextrose levels at different ratios using FMS. Dialysis instrument 104 in one embodiment is configured to read bag identifiers to ensure that the patient connects the proper dialysates and proper amounts of the dialysate. Systems and methods for automatically identifying the type and quantity of dialysate in a supply bag are set forth in U.S. patent application Ser. No. 11/773,822 (“the '822 Application”), entitled “Radio-Frequency Auto-Identification System For Dialysis Systems”, filed Jul. 5, 2007, now U.S. Pat. No. 8,330,579, issue date, Dec. 11, 2012, assigned to the assignee of the present disclosure, the entire contents of which are incorporated herein by reference. The '822 application discloses one suitable system and method for ensuring that the proper supply bags are connected to the proper ports of cassette 50. System 10 can alternatively use a barcode reader that reads a barcode placed on the bag or container for solution type/volume identification. In the case in which Y-connections are needed, APD machine 104 can prompt the patient to confirm that the Y-connection(s) to an additional bag(s) has been made.


U.S. Pat. No. 6,814,547 (“the '547 patent”) assigned to the assignee of the present disclosure, discloses a pumping mechanism and volumetric control system in connection with FIGS. 17A and 17B and associated written description, incorporated herein by reference, which uses a combination of pneumatic and mechanical actuation. Here, volume control is based on precise control of a stepper motor actuator and a known volume pump chamber. It is contemplated to use this system instead of the FMS of the '357 patent to achieve the above blended dextrose levels.


Prescription Download and Therapy Data Upload Communication Module

Referring now to FIG. 15A, network 100a illustrates one wireless network or communication module 20 (FIG. 1) for communicating the PET, regimen generation, prescription filtering, inventory tracking, trending and prescription modification information (below) between patient 102, doctor 110 and dialysis center 120. Here, the patient 102 operates a dialysis instrument 104, which communicates wirelessly with a router 106a, which is in wired communication with a modem 108a. The doctor 110 operates the doctor's (or nurse's) computer 112a (which could also be connected to a doctor's network server), which communicates wirelessly with a router 106b, which is in wired communication with a modem 108b. The dialysis center 120 includes a plurality of clinician's computers 112b to 112d, which are connected to a clinician's network server 114, which communicates wirelessly with a router 106c, which is in wired communication with a modem 108c. Modems 108a to 108c communicate with each other via an internet 116, wide area network (“WAN”) or local area network (“LAN”).



FIG. 15B illustrates an alternative wired network 100b or communication module 20 (FIG. 1) for communicating the PET, regimen generation, prescription filtering, inventory tracking, trending and prescription modification information (below) between patient 102, doctor 110 and dialysis center 120. Here, the patient 102 includes a dialysis instrument 104, which is in wired communication with modem 108a. The doctor 110 operates the doctor's (or nurse's) computer 112a (which could also be connected to a network server), which is in wired communication with a modem 108b. The dialysis center 120 includes a plurality of clinician's computers 112b to 112d, which are in wired communication with a modem 108c. Modems 108a to 108c again communicate with each other via an internet 116, WAN or LAN.


In one embodiment, the data points for curve 30 of FIG. 3 are generated at instrument 104 and sent to either the doctor 110 or the dialysis center 120 (most likely dialysis center 102), which houses the software to fit curve 30 to the data points. The patient then travels to the dialysis center 120 to have the blood work performed and to complete the PET as discussed herein. The software configured to run the PET and regimen generation screens of FIGS. 4A, 4B, 5A, 5B and 6 can be stored on clinician's server 114 (or individual computers 112b to 112d) of clinic 120 or computers 112a of doctor 110 (most likely clinic 120) of system 100a or 100b. Likewise, software configured to run the filtering and prescription optimization screens of FIGS. 6A to 6C, 7A, 7B, 8A to 8C and 9A to 9E can be stored on server 114 (or individual computers 112b to 112d) of clinic 120 or computers 112a of doctor 110 of system 100a and 100b.


In one embodiment, dialysis center 120 runs the PET, generates the regimens and filters the prescriptions. Dialysis center 120 via network 100 (referring to either or both networks 100a and 100b) sends the prescriptions to doctor 110. The filtering can be performed with input from the patient via either network 100, telephone or personal visit. The doctor reviews the prescriptions to approve or disapprove. If the doctor disapproves, the doctor can send additional or alternative filtering criteria via network 100 back to dialysis center 120 to perform additional filtering to optimize a new set of prescriptions. Eventually, either dialysis center 120 or doctor 110 sends approved prescriptions to instrument 104 of patient 102 via network 100. Alternatively, dialysis center 120 or doctor 110 stores the approved prescriptions and instrument 104 and on a given day queries dialysis center 120 or doctor 110 over network 100 to determine which prescription to run. The prescriptions can further alternatively be transferred via a data card.


In an alternative embodiment, dialysis center 120 runs the PET and generates the regimens. Dialysis center 120 via network 100 sends the regimens to doctor 110. The doctor reviews the regimens and filters same until arriving at a set of prescriptions to approve or disapprove. The filtering can again be performed with input from the patient via either network 100, telephone or personal visit. If the doctor disapproves, the doctor can perform additional filtering to optimize a new set of prescriptions. Here, doctor 110 sends approved prescriptions to instrument 104 and of patient 102 via network 100. Alternatively, doctor 110 stores the approved prescriptions and instrument 104 on a given day queries doctor 110 over network 100 to determine which prescription to run. Further alternatively, doctor 110 sends the approved prescriptions to dialysis center 120 over network 100, the dialysis center stores the approved prescriptions, and instrument 104 on a given day queries dialysis center 120 over network 100 to determine which prescription to run.


As discussed above, dialysis center 120 is likely in a better position to handle the inventory tracking module or software 18 than is doctor 110. In one embodiment therefore, dialysis center 120 stores the software configured to run the inventory tracking screens of FIGS. 10 to 13. Dialysis center 120 communicates with dialysis instrument 104 and patient 102 via network 100 to control the inventory for the patient's approved prescriptions.


Referring now to FIG. 16A, network 100c illustrates a further alternative network or communication module 20 (FIG. 1). Network 100c also illustrates the patient data collection module 22 of FIG. 1. It should be appreciated that the patient data collection principles discussed in connection with network 100c are also applicable to networks 100a and 100b. Network 100c includes a central clinical server 118, which could be stored in one of the dialysis centers 120, one of the doctor's offices 110 or at a separate location, such as at a facility run by the provider of system 10. Each of patients 102a and 102b, doctors 110a and 110b and dialysis centers 120a and 120b communicates with clinical server 118, e.g., via internet 116. Clinical server 118 stores and runs the software associated with any of the PET, regimen generation, prescription filtering, inventory tracking, trending and prescription modification (below) modules and facilitates communication between patients 102a/102b, doctors 110a/110b and dialysis centers 120a/120b.


Clinical server 118 in one embodiment receives the PET data from one of the dialysis centers 120 (referring to either of centers 120a or 120b) and sends it to clinical server 118. The UF data points of FIG. 3 can be sent to clinical server 118 either directly from patient 102 (referring to either of patients 102a or 102b) or from dialysis center 120 via patient 102. Clinical server 118 fits curve 30 (FIG. 3) to the data points and generates the regimens and either (i) filters the regimens (perhaps with patient input) into optimized prescriptions for the doctor 110 (referring to either of doctors 110a or 110b) to approve or disapprove or (ii) sends the regimens to doctor 110 to filter into optimized prescriptions (perhaps with patient input).


In either case, the approved prescriptions may or may not be sent to an associated dialysis center 120. For example, if the associated dialysis center 120 runs inventory tracking module 18 of system 10, the dialysis center 120 needs to know the prescriptions to know which solutions and supplies are needed. Also, if system 10 is operated such that the patient's dialysis instrument 104 (referring to either instrument 104a or 104b) queries the dialysis center 120 on a given day for which prescription to run, the dialysis center 120 needs to know the prescriptions. Alternatively, the patient's dialysis instrument 104 queries clinical server 118 daily for which prescription to run. It is also possible for clinical server 118 to run inventory tracking module 18 of system 10, in which case the associated dialysis center 120 can be relegated to obtaining the PET data.


Clinical server 118 can be a single server, e.g., a national server, which is a logical geographical boundary because different countries have different sets of approved dialysis solutions. If two or more countries have the same approved set of dialysis solutions and a common language, however, clinical server 118 could service the two or more countries. Clinical server 118 can be a single server or have spoke and hub links between multiple servers.


Referring now to FIG. 16B, network 100d includes a central clinical server 118, which is housed at or close to one of the dialysis centers 120. The dialysis center 120 houses a doctor's office 110 and a patient service area 90, each including one or more computer 112a to 112d. Patient service area 90 includes a server computer 114, which communicates with clinical server 118 in one embodiment via a local area network (“LAN”) 92 for the dialysis center 120. Clinical server 118 in turn includes a clinical web server that communicates with internet 116 and LAN 92, a clinical data server that communicates with LAN 92 and a clinical database that interfaces with the clinical data server.


Each of patients 102a and 102b communicates with clinical server 118, e.g., via internet 116. Clinical server 118 stores and runs the software associated with any of the PET, regimen generation, prescription filtering, inventory tracking, trending and prescription modification (below) modules and facilitates communication between patients 102a/102b, doctors 110 and dialysis centers 120. Other dialysis centers 120 can communicate with center-based clinical server 118 with internet 116. Any of systems 100a to 100d can also communicate with an APD machine manufacturer's service center 94, which can include for example a service database, a database server and a web server. Manufacturer's service center 94 tracks machine problems, delivers new equipment, and the like.


Data Collection Feature

PET module 12, regimen generation module 14 and prescription optimization or filtering module 16 output data that networks 100 (referring now additionally to networks 100c and 100d) use to run dialysis therapies. In this regard, the networks 114 and 118 of system 10 use results from analysis that have already been performed. As seen with network 100c, system 10 also generates real-time daily patient data, which is fed to a server 114 (of a center 120) or 118 for tracking and analysis. This real-time data, along with therapy parameter inputs and therapy target inputs make up the data collection module 22 (FIG. 1) of system 10.


Each dialysis machine 104 (referring to either or both machines 104a and 104b) includes a receiver 122 as illustrated in FIG. 16A. Each receiver 122 is coded with an address and a personal identification number (“PIN”). The patient is equipped with a blood pressure monitor 124 and a weigh scale 126. Blood pressure monitor 124 and weigh scale 126 are each provided with a transmitter, which sends patient blood pressure data and patient weight data, respectively, wirelessly to receiver 122 of dialysis machine 104.


The address and PIN ensure that the information from blood pressure monitor 124 and weigh scale 126 reaches the proper dialysis machine 104. That is, if machines 104a and 104b and associated blood pressure monitors 124 and weigh scales 126 are within range of each other, the addresses and PIN's ensure that the dialysis machine 104a receives information from the blood pressure monitor 124 and weigh scale 126 associated with dialysis machine 104a, while dialysis machine 104b receives information from the blood pressure monitor 124 and weigh scale 126 associated with dialysis machine 104b. The address and PIN also ensure that dialysis machines 104 do not receive extraneous data from unwanted sources. That is, if data from an unwanted source is somehow transmitted using the same frequency, data rate, and communication protocol of receiver 122, but the data cannot supply the correct device address and/or PIN, receiver 122 will not accept the data.


The wireless link between blood pressure monitor 124, weigh scale 126 and dialysis machine 104 allows the devices to be located conveniently with respect to each other in the patient's room or house. That is, they are not tied to each other via cords or cables. Or, blood pressure and weight data are entered into instrument 104 manually. The wireless link however also ensures that the blood pressure data and weight data, when taken, are transferred automatically to the dialysis machine 104. It is contemplated that the patient takes his/her blood pressure and weighs himself/herself before (during or directly after) each treatment to provide a blood pressure and weight data point for each treatment. Data collection module 22 is configured alternatively to have a wired connection between one or more of blood pressure monitor 124 and instrument 104 and weight scale 126 and instrument 104.


Another data point that is generated for each treatment is the amount of ultrafiltration (“UF”) removed from the patient. All three data points, blood pressure, patient weight and UF removed, for each treatment can be stored in the memory of the dialysis machine 104, on a data card and/or be sent to a remote server 114 or 118. The data points are used to produce performance trends as described next.


Any one or combination of the processing and memory associated with any of the dialysis instrument 104, doctor's (or nurse's) computer 112, clinician's server 114, clinical web server 118 or manufacturer's service center 94 may be termed a “logic implementer”.


Trending And Alert Generation

The trending analysis and statistics module 24 (FIG. 1) of system 10 as seen herein calculates short term and long term moving averages of daily UF and other patient data shown below. Monitoring actual measured daily UF, only, produces too much noise due to residual volume and measurement error of the dialysis instrument 104. The trending regimes of module or feature 24 therefore look at and trend daily data as well as data that is averaged over one or more period of time.


Trending and Alert Generation Using Multiple Patient Parameters

Trending module 24 in one embodiment uses the following equation to form the short term and long term moving averages: UFma(n)=1/k*(UF(n)+UF (n−1)+UF (n−2) . . . +UF (n−k)). For the short term moving average, typical values for k can be, e.g., three to fourteen days, such as seven days. For the long term moving average, typical values for k can be, e.g., fifteen to forty-five days, such as twenty-eight days.


The difference between target UF and actual measured UF is set forth as:

ΔUF=UFtarget−UFma.

UFtarget is the physician prescribed UF, and UFma is the moving average value of actual daily UF measured (either daily measured value or two to three days for short term moving average). ΔUF can be either positive or negative. When the absolute value of ΔUF/UFtarget exceeds the alert threshold preset by physician, system 10 (either at the machine 104 level or via server 114/118) alerts the patient and the physician 110 and/or clinician 120, which can trigger prescription adjustment or other response as discussed below.


The alert threshold can account for UF anomalies so as not to make system 10 false trigger or be oversensitive to daily UF fluctuations, which can inherently be significant (e.g., due to measurement error and residual volume). The following equation illustrates an example in which system 10 requires a number of days of a certain UF deviation:

δ(alert generated)=ΔUF/UFtarget|>X% for Y days.

X % can be preset by the physician or clinician, and a typical value may be thirty to fifty percent. Y can also be preset by either the physician or clinician, and a typical value may be three to seven days.


The next equation addresses the possibility of a patient skipping dialysis or the patient's UF being consistently much lower than the target UF:









If





δ

=





i
=
1

q



δ
i


=




i
=
1

q





Δ






UF
/

UF
target











P





%





for





Q





days





P % can be preset by the physician or clinician, and a typical value may be 150% to 250%. Q can also be preset by the physician or clinician, and a typical value can be two to three days. The above equation calculates a difference between the daily measured UF and the target UF and expresses the difference as a percentage of the target UF to determine an error in the percentage. Then the error percentage is accumulated over several days, e.g., two to three (Q) days. If the accumulated errors exceeds the threshold (P %), system 10 will generate UF alerts. The following examples illustrate the above algorithm:


Example #1





    • P=150%, Q=3 days


      Day #1, patient skipped therapy, UF error=100%; Day #2, patient skipped therapy, UF error=100%; Day #3, patient performed therapy, UF error=10%; accumulated UF error=210%>150%, then it will generate alarm.





Example #2





    • P=150%, Q=3 days


      Day #1, patient skipped therapy, UF error=100%; Day #2, patient performed therapy, UF error=20%; Day #3, patient performed therapy, UF error=10%; accumulated UF error=130%<150%, no alarm will be generated.






FIGS. 17 to 21 show trending screens 128, 132, 134, 136 and 138, respectively, which can be displayed to the patient on a display device 130 of the dialysis instrument 104 and/or on a computer monitor at doctor 110 or dialysis center 120. It is contemplated to generate the trends at any of these locations as needed. The main trending screen 128 of FIG. 17 allows the patient for example to select to see: (i) pulse and pressure trends; (ii) recent therapy statistics; (iii) UF trends; and (iv) weight trends. The patient can access any of the screens via a touch screen input, via a membrane or other type of switch associated with each selection, or via knob or other selector that allows one of the selections to be highlighted, after which the patient presses a “select” button.


When the patient selects the pulse and pressure trends selection of the main trending screen 128, display device 130 displays the pulse and pressure trends screen 132 of FIG. 18. Pulse (heart rate, line with ●'s), systolic pressure (line with ▴'s), and diastolic pressure (line with ▪'s) are shown for a one month time period in units of mmHg. Selection options on the pulse and pressure trends screen 132 include (i) returning to the main trending screen 128, (ii) seeing weekly trends for pulse, systolic pressure, and diastolic pressure instead and (iii) advancing to the next trending screen 134. The one or more therapy performed during the trend period, namely, therapy number 1 (e.g., standard UF), is also shown.


When the patient selects the next trending selection of the pulse and pressure trends screen 132, display device 130 displays a recent therapy trends or statistics screen 134 as seen in FIG. 19. FIG. 19 shows actual values for UF removed (in milliliters, including total UF and breakout UF's for day and night exchanges), cumulative dwell time (in hours, seconds, including total dwell and breakout dwells for day and night exchanges), drain volume (in milliliters, including total volume and breakout volumes for day and night exchanges), and filled volume (in milliliters, including total volume and breakout volumes for day and night exchanges). The recent therapy trends or statistics screen 134 as seen in FIG. 19 in one embodiment shows statistics from the previous therapy. Screen 134 alternatively includes a logs option that enables the patient to view the same information for prior therapies, e.g., therapies up to a month ago or since the download of the last set of prescriptions. Selection options displayed on the recent therapy trends or statistics screen 134 include (i) returning to the main trending screen 128, (ii) returning to the previous trending screen 132 and (iii) advancing to the next trending screen 136.


When the patient selects the next trending selection of the recent therapy trends or statistics screen 134, display device 130 displays a UF trends screen 136 as seen in FIG. 20. UF trends screen 136 shows a target UF line and a measured UF line for a one month time period in units of milliliters. Selection options on the UF trend screen include (i) returning to the main trending screen 128, (ii) seeing weekly trends for UF, monthly trends for UF or even three month trends for UF as long as the data is available, and (iii) advancing to the next trending screen 138. The therapy performed during the UF trending period is also shown.


When the patient selects the next trending selection of the recent UF trends screen 136, display device 130 displays a patient weight trends screen 138 as seen in FIG. 21. Patient weight trends screen 138 shows a measured body weight (“BW”) line for a one month time period in units of pounds. Selection options on the patient weight trend screen 138 include (i) returning to the main trending screen 128 and (ii) advancing to a next screen. The therapy performed during the BW trending period is also shown.


Alternative trending charts of FIGS. 22 and 23 display actual days on the x-axis. These trends could be reserved for the doctor 110 and/or dialysis center 120 or be accessible additionally by the patient, meaning that the alerts can be generated from the APD device 104 to the doctor and/or clinician or from a server computer to the doctor, clinician and/or patient. The trending charts of FIGS. 22 and 23 show the expected UF value or UF target for the patient based upon the patient's last PET results. If the difference between expected PET UF and the actual UF increases beyond a value that the doctor or clinician determines is significant, the clinician can order a new PET with or without lab work. That is, the patient can perform the UF portion of the PET as described in connection with FIGS. 2 and 3 and bring the drain volumes to the dialysis center 120. U.S. patent application Ser. No. 12/128,385, entitled “Dialysis System Having Automated Effluent Sampling And Peritoneal Equilibration Test”, filed May 28, 2008, now U.S. Pat. No. 8,449,495, issue date, May 28, 2013, the entire contents of which are incorporated herein by reference, discloses an automated PET, which results in effluent samples that the patient can bring to the dialysis center 120 so that the samples can be analyzed for urea clearance, creatinine clearance, etc.


The trending charts of FIGS. 22 and 23 also show which therapy prescription was used on a given day, as seen at the right side of the figures (assuming for example that therapy prescription Zero is low UF, therapy prescription One is standard UF and therapy prescription Two is high UF). As seen in FIGS. 22 and 23, the standard UF prescription is performed on all but two days in which the high UF prescription is performed. In FIG. 22, the thirty day moving average (line with ●'s) in particular shows that, generally, the patient's treatment is meeting the UF goal. In FIG. 23, the thirty day moving average (line with ●'s) shows that after about Oct. 2, 2006, the patient's treatment started to not meet the UF goal and became progressively worse. Moreover, the entire thirty day trend line for October, 2006 slopes towards less and less UF removal. A skilled clinician here will see such trend as potentially being due to a loss of the patient's renal function and either (in conjunction with a doctor) order a new PET, provide new prescriptions or put the patient's UF performance on a close watch to see if the trend continues. The clinician/doctor could alternatively prescribe that the high UF prescription be performed more frequently in an attempt to reverse the negative-going UF trend.


As alluded to above, the doctor or clinician likely does not want to be notified when a single day falls below the lower limit. The UF data therefore needs to be filtered. The filter for example considers all three of daily UF values, the seven day rolling average UF (line with ▾'s) and the thirty day rolling average (line with ●'s) in an algorithm to determine if the patient's prescription needs to be modified. The filter can also consider which therapies are being performed. For example, alert notification can occur sooner if the patient runs a high percentage of High UF therapies and is still failing to meet standard therapy UF targets.


One specific example of an alert algorithm is: the thirty day rolling average UF (line with ●'s) has fallen by ten percent, and the actual UF (base line) has been below the lower limit for three of the past seven days while performing either the standard UF prescription or the high UF prescription. Another specific example of an alert algorithm is: the thirty day rolling average UF (line with ●'s) has fallen by ten percent and the seven day rolling average UF (line with ▾'s) has fallen below the lower limit LCL, while performing either the standard UF of the high UF therapies.


The alert algorithm can also take into account daily weight and blood pressure data. For example, when the UF deviation, daily blood pressure and body weight each exceed a respective safety threshold, an alert is triggered. In one specific example, system 10 alerts if (i) UF deviates from the target UF; and (ii) short term moving average (e.g., three to seven days) body weight (“BW”) is greater than a threshold; and (iii) short term moving average (e.g., three to seven days) systolic/diastolic blood pressure (“BP”) is greater than a threshold. BP and BW thresholds are preset by physician 110.


Further, body weight data alone can trigger an alarm when for example the patient is gaining weight at a certain rate or gains a certain amount of weight. Here, system 10 can notify the doctor 110 and/or clinician 120, prompting a call or electronic mail to the patient asking for an explanation for the weight gain. If the weight gain is not due to diet, it could be due to an excessive amount of dextrose in the patient's prescription, such that a new lower dextrose prescription or set of such prescriptions may need to be prescribed. For example, clinician 120 can set the patient's target body weight, and if the daily measured body weight is off by Xw pounds for Yw days in a seven day period, body weight gain is considered excessive and an alert is triggered:

ΔBW=BWm−BWtarget>Xw for Yw days, where

BWm is the measured daily body weight, BWtarget is the target body weight (set by doctor 110 or clinician 120), Xw is a limit of body weight exceeding the target (set by doctor 110 or clinician 120), and Yw is the number of days (set by doctor 110 or clinician 120).


Likewise, an increase in blood pressure alone could prompt a communication from the doctor 110 and/or clinician 120 for an explanation from the patient. It is further contemplated to trend the patient's daily bio-impedance, especially as such sensing comes of age. A bio-impedance sensor can for example be integrated into a blood pressure cuff (for wired or wireless communication with dialysis instrument 104), so that such sensing does not inconvenience the patient. System 10 uses bio-impedance in one embodiment to monitor the dialysate patient hydration state by estimating the patient's intra and extra-cellular water. Such data aids the patient and clinician in selecting a therapy (e.g., high UF when patient is over hydrated and low UF patient is dehydrated). Bio-impedance can thereby help to control the patient's fluid balance and blood pressure.


The clinician in the main is concerned about two factors: therapy effectiveness and patient compliance. Patients whose UF is below target because they are running a low UF therapy too often, or are skipping therapies, need to be told in a timely manner to change their behavior. Patients whose UF is below target but who are fully compliant and may even be performing high UF therapies to obtain their target UF may need to have their prescription(s) changed in a timely manner. The trends of FIGS. 22 and 23 provide all such information to the clinician.


System 10 knows accordingly if the lower than expected UF is due to compliance issues or potential therapy prescription issues. In an embodiment in which the patient chooses to pick which prescription to run on a given day, the dialysis instrument 104 can be programmed to provide a warning to the patient when the patient runs the low UF prescription too often (low UF prescription may be less demanding than standard UF prescription). The programming can be configured to escalate the warnings if the patient continues with this behavior, let the patient know that the dialysis center 120 is being notified, and notify the dialysis center accordingly. The instrument 104 can likewise be programmed to warn the patient if the patient skips too many treatments and notify the dialysis center 120 if the missed treatments continue. Here, the warning and notification can be made regardless of whether the patient picks the prescription to run or the machine 104/clinic 120 chooses the prescriptions on a given day.



FIG. 24 summarizes the options available for setting simple or complex alert generation logics. The parameters that could be monitored include (on the top row): (i) daily UF deviation limit, (ii) UF deviation accumulation limit, (iii) body weight target and (iv) blood pressure limit. The middle logic operators show that using one or more of (a) measured daily UF, (b) measured daily body weight, and (c) measured daily blood pressure, the limits of the top row can be combined in different combinations using “AND” logic “OR” Boolean logic to determine when to send an alert to the patient, doctor or clinician. The illustrated, alerts are based on (i) UF and BW or (ii) UF, BW and BP. An alert can be based on UF alone, however.


Referring now to FIG. 25, algorithm or action flow diagram 140 shows one alternative alert sequence for system 10. Upon starting at oval 142, system 10 collects daily UF, BP, and BW data at block 144. At block 146, deviation analysis is performed, e.g., based on doctor/clinician settings and rolling averages for UF, BP and BW. At diamond 148, method or algorithm 140 of system 10 determines whether any of UF, BP, and BW is exceeding limits. If not, method or algorithm 140 waits for another day, as seen at block 150, and then returns to the collection step of block 144. If one or a combination of limits is exceeded at diamond 148, an alert is sent to the patient, clinician and/or doctor, as seen at block 152. Deviation and accumulated values are reset.


A hold or watch period is then started at diamond 154, e.g., for seven days, to see if the alert condition persists. During this period, it is contemplated that system 10 communicates between patient 104, doctor 110 and/or clinician 120 daily or otherwise regularly until the low UF trend is reversed. The clinician may make suggestions during this period, e.g., to try the high UF prescription or modify the patient's diet. As discussed, dialysis center 120 also receives trending data for patient weight and blood pressure in addition to the UF trending data. The mean arterial pressure (“MAP”) may be the most appropriate value to trend relative to blood pressure. The clinicians evaluate the weight and MAP data concurrently during the low UF periods.


If the alert condition persists for a period, e.g., seven days as seen at diamond 154, method 140 and system 10 order a new PET and/or change the patient's prescription, as seen at block 156. Afterwards, method 140 ends as seen at oval 158.


Patient Case Studies

Patient A started peritoneal dialysis treatment just two months ago and still has residual renal function (“RRF”). His UF target is 800 mL/per day. The doctor set the alert watch to look at daily UF deviation, UF deviation accumulation and target body weight. Here, a deviation limit X was chosen to be 30%, for a period Y equal to four out of seven days. A three-day UF deviation accumulated error was chosen to be 150%. Target body weight was selected to be 240 pounds with a safety limit delta of +five pounds in seven days. The following table is an example of the measured daily twenty-four hour UF, BP and BW for a seven day period.









TABLE 5







Patient A measured parameters














Parameters
Sun
Mon
Tue
Wed
Thur
Fri
Sat

















Daily UF (mL)
600
650
700
600
550
750
730


Daily Systolic/Diastolic
150/90
148/95
160/97
153/88
165/98
170/95
160/92


Pressure (mmHg)









Daily Body Weight
242.5
243.3
243.5
244.7
243.1
245.4
245.8


(LB)









Daily UF Deviation
25%
19%
13%
25%

custom character

 6%
 9%


From Target UF









Daily UF Deviation


57%
57%
69%
62%
46%


Accumulated Error









Daily Body Weight
2.5
3.3
3.5
4.7
3.1

custom character


custom character



Deviation from Target









(LB)









In the week of therapy shown above for Patient A, only Thursday's daily UF falls below the 30% lower limit threshold. The three-day accumulated UF deviation does not exceed 150%. The patient's body weight stays under limit (+five pounds) in all but the last two days. Here, system 10 does not generate an alert.


Patient B has been on PD for over two years. She is very compliant with her therapy and follows clinician's instructions strictly. She does not have any RRF and her daily UF target is 1.0 L. Here, the doctor 110 and/or clinician 120 set alert conditions as follows. A deviation limit X was chosen to be 20%, for a period Y equal to four out of seven days. A three-day UF deviation accumulated error was chosen to be 150%. Target body weight was selected to be 140 pounds with a safety limit delta of +five pounds in seven days. The following table is an example of the measured daily twenty-four hour UF, BP and BW for a seven day period.









TABLE 6







Patient B measured parameters















Sun
Mon
Tue
Wed
Thur
Fri
Sat

















Daily UF (mL)
880
850
920
870
910
950
930


Daily Systolic/Diastolic
150/93
142/86
147/92
153/86
155/90
173/90
166/87


Pressure (mmHg)









Daily Body Weight (LB)
143.5
144.3
143.8
144.3
143.1
144.6
144.8


Daily UF Deviation From
12%
15%
 8%
13%
 9%
 5%
 7%


Target UF









Daily UF Deviation


35%
36%
30%
27%
21%


Accumulated Error









Daily Body Weight
3.5
3.3
3.8
4.3
3.1
4.6
4.8


Deviation from Target (LB)
















In the week of therapy shown above for Patient B, none of the daily 24-hour UF values falls below the 20% lower limit threshold. The 3-day accumulated UF deviation does not exceed 150% on any day. The patient's weight never exceeds the threshold of +five pounds. Accordingly, system 10 does not generate a trending alert this week.


Patient C has been on PD for over a year. The patient sometimes over-eats/drinks and skips a therapy from time to time. He does not have any RRF and his daily UF target is 1.0 L. Here, the doctor 110 and/or clinician 120 set alert conditions as follows. A deviation limit X was chosen to be 25%, for a period Y equal to four out of seven days. A three-day UF deviation accumulated error was chosen to be 150%. Target body weight was selected to be 220 pounds with a safety limit delta of +five pounds in seven days. The following table is an example of his measured daily 24-hour UF, BP and WE for a seven day period.









TABLE 7







Patient C measured parameters















Sun
Mon
Tue
Wed
Thur
Fri
Sat

















Daily UF (mL)
880
700
840
900
0
700
500


Daily Systolic/Diastolic
167/97
156/88
177/96
163/96
165/90
166/90
178/89


Pressure (mmHg)









Daily Body Weight (LB)
223.5
225.3
223.8
224.3
225.1
225.6
225.8


Daily UF Deviation From
12%

custom character

16%
10%

custom character


custom character


custom character



Target UF









Daily UF Deviation


58%
56%
126%
140%

custom character



Accumulated Error









Daily Body Weight
3.5

custom character

3.8
4.3

custom character


custom character


custom character



Deviation from Target









(LB)









In the week of therapy shown above for Patient C, the patient's daily UF fell below the 25% threshold on Monday, Thursday, Friday and Saturday, as highlighted. The three-day accumulated UF deviation exceeded the 150% limit after Saturday's therapy. The patient also exceeds his +five pound weight limit four times, namely, on Monday, Thursday, Friday and Saturday. System 10 accordingly sends a trending alert after this week.


Trending and Alert Generation Using Statistical Process Control

It is also contemplated to use statistical process control (“SPC”) to identify instability and unusual circumstances. Referring now to FIG. 26, one example moving average or trend is shown, which shows a five-day average UF (dots) and an average UF for the previous thirty days (base middle line). A range is calculated to be the difference between the lowest and the highest UF values over the past thirty days. An upper control limit (“UCL”, line with X's through it) for a given day is calculated to be:

UCL=(the moving average for the given day)+(a constant, e.g., 0.577,*the range for the given day)


and the lower control limit (“LCL”, line with /'s through it) is calculated to be

LCL=(the moving average for the given day)−(the constant, e.g., 0.577,*the range for the given day).



FIG. 26 shows a UF trend created for a patient, e.g., from August 2003 through June 2004 using SPC. In December of 2003 and in April of 2004, the five day moving average UF (dots) fell below the LCL. System 10 could be configured to monitor the five day average and alert the patient, clinic and/or doctor when the five day moving average UF (dots) falls below the LCL (or falls below the LCL for a number of days in a row). The software configured to generate the trends can be located at the dialysis instrument 104 or at either server computer 114 or 118. In various embodiments, any one or more or all of the patient 102, dialysis center 120 or doctor 110 can access and view the trends. The trend data is generated whether or not the trend is actually viewed by anyone. The alerts are auto-generated in one embodiment, enabling system 10 to monitor patient 102 automatically for the dialysis center 120 and doctor 110.



FIG. 27 shows a second trend for the same patient after changes have been made to the patient's prescription (line with ●'s). Here, the patient's daytime exchange has been changed from Nutrineal® dialysate to Extraneal® dialysate. FIG. 27 shows the difference a new prescription (line with ●'s) had on the patient's UF starting in September of 2004 and again in November of 2004 when the patient's residual renal function tapered off.


The statistical process control alert algorithm can also take into account body weight (“BW”) and/or blood pressure (“BP”). If UF has a normal distribution having a mean value of μ and standard deviation of σ calculated based on time and population, and wherein C is an empirically determined constant. In most processes that are controlled using Statistical Process Control (SPC), at each time point, multiple measurements or observations are made (e.g. measure the room temperature multiple times at 8:00 AM), however in one embodiment of system 10, the SPC only one measurement is made at each time point, e.g., one UF measurement, one pressure and weight reading per day. System 10 could then alert if: (i) short term moving average (e.g., three to seven days) UF is outside the upper control limit (UCLUF=UFtarget□±Cσ) or lower control limit (LCLUF=UFtarget□−Cσ); or (ii) short term moving average (three to seven days) body weight >BW threshold; and/or (iii) short term moving average (three to seven days) systolic/diastolic BP >BP threshold.



FIG. 27 shows that the SPC trending charts can also display the expected UF value (line with ▴'s) for the patient based upon his/her last PET results. The thirty-day average line shows that actual UF, while lagging slightly behind expected UF (which is to be expected for a thirty day average) eventually aligns itself with the expected UF results. Here, the patient is not underperforming, he/she is able to meet target. The patient may be losing RRF, however, meaning the patient's prescription needs to be more aggressive for UF because the patient has increasing less ability to remove waste and excess water himself/herself. On the other hand, if the difference between expected UF and the actual UF increases beyond a value that the doctor/clinician determines is significant, e.g., below LCL for one or more day, the clinician/doctor can order a new PET as discussed above.


Prescription Recall and Modification

System 10 also includes a prescription recall and modification feature 26 shown and described above in connection with FIG. 1. Referring now to FIG. 28, prescription recall and adjustment feature or module 26 is illustrated in more detail. Prescription recall and adjustment feature or module 26 relies on and interfaces with other features of system 10, such as the improved PET feature 12, regimen generation feature 14, prescription filtering feature 16, and trending an alert generation feature 24. As seen in FIG. 28, one aspect of prescription recall and adjustment feature or module 26 is the selection of one of the approved prescriptions for treatment.


Referring now to FIG. 29, a screen 160 of display device 130 of dialysis machine 104 illustrates one patient selection screen that allows the patient to select one of the approved prescriptions (standard, high and low UF) for the day's treatment. The type of input can be via membrane keys or here via a touch screen overlay, for which areas 162, 164 and 166 have been mapped into memory as standard UF prescription, high UF prescription and low UF prescription selections, respectively. System 10 in the illustrated embodiment allows the patient to select a prescription for each day's treatment. For example, if the patient has consumed more fluids than normal on a given day, the patient can run the high UF prescription. If the patient has worked out, been in the sun, or for whatever reason perspired a great deal during the day, the patient may choose to run the low UF prescription.


If the patient viewing the therapy trend screens 134 and 136 above notices a drop in UF running the standard UF prescription, the patient may be empowered to choose to run the high UF prescription for a few days to see how the patient reacts to the prescription change. Presumably, daily UF will increase. But it should also be appreciated that the patient, clinician or doctor should check to see if the actual increased UF meets the increased expected UF due to the use of the high UF prescription. If the patient is underperforming for both prescriptions, it may be time for a new PET and possibly a new set of prescriptions.


Allowing the patient to adjust his/her therapy as described above is likely done only when the doctor or clinician has a comfort level with the patient that the patient is compliant in terms of lifestyle and adherence to treatment. Also, the doctor/clinician may wish to make sure that the patient has enough experience with the treatment and the dialysis instrument 104 to be able to accurately gauge when the patient needs a high, versus a low, versus a standard UF treatment. Even though the patient is making the prescription decisions in this embodiment, the data for trending as shown above is being sent to the dialysis center 120 and/or doctor 110, so that if the patient is making poor decisions as to which prescriptions to run, the dialysis center 120 and/or doctor 110 can detect the situation in short order and correct it. For example, system 10 enables the dialysis center 120 and/or doctor 110 to remove prescriptions from possible selection or to set the dialysis instrument 104 such that it automatically selects a prescription set at either machine 104 or a server computer 114 or 118.


It is believed, given the importance of a dialysis treatment, that most people will be responsible and that a conscientious and thoughtful patient will best be able to gauge when the patient may need a more aggressive or less aggressive prescription, knowing that even the less aggressive prescriptions have been approved and will remove a certain amount of UF. It is contemplated to provide more than three prescriptions. For example, the patient can have two high UF prescriptions, one that requires a longer night therapy and the other that requires a higher dextrose level. Assuming the patient knows that he/she needs to run a high UF prescription after a relatively large liquid intake day, the patient may choose the longer night therapy high UF prescription knowing that he/she has gained weight of late and is better off staying away from the higher caloric intake of the higher dextrose prescription. System 10 attempts to accommodate the patient's lifestyle, while ensuring that a proper therapy is performed, while also gathering therapy data over time to establish a thorough patient history that enables physiologic changes of the patient to be detected relatively quickly and accurately.


In another embodiment, dialysis instrument 104 selects which prescription the patient is to run based on the patient's daily body weight and possibly the patient's blood pressure. The patient weighs himself/herself, a weight signal is transmitted, e.g., wirelessly to dialysis instrument 104, which uses the weight signal to determine how much UF the patient has accumulated and accordingly which prescription to run. In one embodiment, the patient weighs himself/herself just prior to the last nighttime fill or just prior to a mid-day fill to establish a localized “dry weight”. The patient then weighs himself/herself at night, just after the last fill drain, to establish a localized “wet weight”. The difference between the localized “wet weight” and the localized “dry weight” determines a UF amount. The UF amount is fitted into one of a low UF range, standard UF range and high UF range. Dialysis instrument 104 then picks a corresponding low UF prescription, standard UF prescription or a high UF prescription to run. Alternatively, dialysis instrument 104 provides alternative prescriptions for a particular range, e.g., two high UF prescriptions, allowing the patient to pick one of the two high UF prescriptions. As discussed above, dialysis instrument 104 is configured in one embodiment to read bag identifiers to ensure that the patient connects the proper dialysate(s) and proper amount(s) of dialysate(s).


In a further alternative embodiment, the doctor 110 or dialysis center 120 chooses or pre-approves the prescriptions to be run on a given day, such that the patient does not have the ability to run a different prescription. Here, fill, dwell, and/or drain times can be preset, and the dialysis instrument 104 can also be configured to read bag identifiers to ensure that the patient connects the proper dialysate(s) and proper amount(s) of dialysate(s).


It is further contemplated to allow the patient to have input into which prescriptions are run, but wherein the doctor 110 or dialysis center 120 ultimately approves of a prescription selection or selection plan before the prescriptions are downloaded into dialysis instrument 104. For example, it is contemplated that the dialysis center 120 send an auto-generated email to the patient 102, e.g., each month one week prior to the start of the next month. The email includes a calendar, each day of the calendar shows all available prescriptions, e.g., (i) lowUF, (ii) midUFlowDEX, (iii) midUFhighDEX, (iv) highUFlowDEX and (v) highUFhighDEX. The patient clicks on one of the prescriptions for each day and sends the completed calendar to clinician 120 for approval. For example, the patient may choose to run one of the high UF prescriptions on the weekends and one of the middle or standard prescriptions during the week. Perhaps the patient attends physically demanding workout classes after work on Mondays and Wednesdays and selects the low UF prescription for those days.


It is contemplated to allow the patient to type notes in the days to explain why a particular prescription has been proposed. For example, the patient could select the lowUF prescription and type “spin class” in that calendar day. Or the patient could select the highUFhighDEX prescription and type “birthday party, up early next day” in that calendar day.


When the clinician receives the completed, proposed calendar from the patient, the clinician can either approve of the proposed calendar, call or email the patient with questions as to why one or more prescription was chosen for a particular day, forward the calendar to the doctor's office 110 if the clinician is concerned or has questions regarding the proposed calendar, or modify the selections in the calendar and send the modified calendar back to the patient. The clinician can review the patient's trend data when evaluating the proposed prescription calendar. For example, if the patient has been gaining weight and has selected the high dextrose standard UF for many or all of the days of the month, the clinician can call or email the patient and suggest switching to the low dextrose standard UF prescription in an attempt to control the patient's weight gain.


Eventually, the clinician and the patient reach a consensus. The doctor may or may not need to be consulted. It is expected that the patient's calendars will look similar from month to month and may change naturally based on season, vacations, and holidays. When a more radical change is presented, e.g., the patient intends to start a vigorous workout or training routine and wants to introduce more low UF days, the clinician can seek doctor approval.


In one embodiment, dialysis instrument 104 confirms that the patient wants to run a non-standard treatment on a particular day. The dialysis instrument 104 also enables the patient to switch to a standard therapy if the patient desires. For example, if the patient has Mondays and Wednesdays approved for a low UF prescription because the patient expects to have vigorous workouts those days, but the patient skips a workout, the patient can choose to run a standard UF prescription instead. Or, if the patient is slated to run a high UF prescription because he/she is supposed to attend a party on a given day, but misses the party, the patient can choose to run a standard UF prescription instead.


Dialysis instrument 104 could also be configured to provide the patient with a limited amount of prescription changes from a standard UF prescription to a low or high UF prescription. For example, if the patient decides to workout Thursday instead of Wednesday, the patient could switch the prescription from standard UF to low UF on Thursday. System 10 could be configured to allow for one such standard to non-standard prescription change per week, for example.


In another example, dialysis instrument 104 allows the patient to increase the UF removal at any time, that is, switch from low UF prescription to a standard or high UF prescription, or switch from a standard UF prescription to a high UF prescription at any time. If the patient chooses this option a certain number of times during the month, dialysis instrument 104 can be configured to send an alert to the doctor 110 or clinician 120.


The approved calendar in one embodiment is integrated with the inventory tracking feature 18. The approved calendar tells the inventory tracking feature 18 what is needed for the next delivery cycle, which can be a month to month cycle. If the patient can plan and gain approval for multiple months, the delivery cycle can be for the multiple months. In any case, the patient can be delivered extra solution if needed to allow for switches from the planned prescriptions.


In a further alternative embodiment, the patient and clinician and/or doctor agree that for each week the patient will run a certain number of standard, low and high prescriptions, e.g., five standard, one low and one high. The patient then chooses which days during the week to run the various prescriptions. The weekly allotment does not have to include any low UF or high UF allotments. The patient could have seven standard UF allotments with four low dextrose standard and three high dextrose standard prescriptions, for example. Here too, dialysis instrument 104 can be configured to let the patient change prescriptions in certain instances as described above.


In still a further alternative embodiment, dialysis instrument 104 or one of the server computers 114 or 118 picks one of the approved prescriptions for the patient for each therapy. The pick can be based on any of the trending data above and/or based on a series of questions answered by the patient such as: (i) Was your fluid intake today low, moderate, average, high or very high? (ii) Was your food intake today low, moderate, average, high or very high? (iii) Was your carbohydrate intake today low, moderate, average, high or very high? (iv) Was your sugar intake today low, moderate, average, high or very high? (v) Was your activity level today low, moderate, average, high or very high? System 10 then picks one of the approved prescriptions for the patient. Inventory management for this embodiment can be based on average usages over the past X number of delivery cycles. In any of the above regimes, dialysis instrument 104 can also read bag identifiers to ensure that the patient connects the proper dialysate(s) and proper amount(s) of dialysate(s).


As seen in FIG. 28, the selected daily prescriptions are fed into a switch mechanism for prescription recall and modification feature 26. The switch mechanism is activated when the applied alert generation algorithm of feature 24 computes an error that is greater than the threshold(s) of the applied alert generation algorithm. As seen in FIG. 28, when the applied alert generation algorithm of feature 24 computes an error that is not greater than the threshold, feature 26 maintains the current set of prescriptions and whichever prescription recall regime is being employed. Accordingly, the switch mechanism does not switch to a new prescription or set of prescriptions.


When a prescription is used for a treatment, the prescription carries with it a predicted UF, which is generated via regimen generation feature 14 and selected via prescription filtering feature 16.


Actual UF data is obtained from the short term and long term moving averages as discussed above in connection with trending and alert generation feature 24, which are in turn developed from measured UF data generated at dialysis instrument 104. Actual UF values area function of the patient's transport characteristics as has been described herein but also account for environmental factors, such as regimen deviation by the patient. Actual UF values are subtracted from the predicted UF values at difference generator 66a and fed into the alert generation algorithm at diamond 24. The actual UF values are also fed into a difference generator 66b, which are used to adjust target UF values used to generate the regimens in connection with feature 14. Other target values include target urea removal, target creatinine removal and target glucose absorption as discussed above.


As seen at diamond 24, once system 10 determines an alarm condition, system 10 triggers prescription adjustment switch mechanism. That does not necessarily mean that the patient's prescriptions will be adjusted. The doctor 110 ultimately makes the call based on the data of UF, patient daily weight, daily blood pressure, or estimated dry weight using a bio-impedance sensor. When it appears prescription adjustment is needed, system 10 via communications module 20 communicates with the patient, e.g., via wireless communication between APD system to modem through a router. Based on the received data, the nephrologist 110 at switch mechanism 26 could make following decisions: (i) continue with current prescriptions and come to office visit as previously planned; (ii) continue with current prescriptions but visit office sooner for possible prescription adjustment; (iii) switch to a different routine using current prescriptions, visit office soon, e.g., within two weeks, receive trending data on new routine; (iv) warn the patient that he/she is not being compliant with treatment and maintain current prescription(s); (v) warn the patient that he/she is running a low UF prescription(s) too often and maintain current prescription(s); (vi) continue with the current therapy and monitoring, but lower the UF target to A and lower the UF limit to B; and (vii) perform a new APD PET to evaluate the change of PD membrane transport characteristics and provide the center with updated therapy suggestions based upon this PET.


If the patient is fully compliant and the low UF is as a result of transport characteristic changes as verified by the new PET, doctor 110 can order a new one or prescription be generated, including a change in one or more standard UF prescription. To do so, regimen generation module 14 and prescription filtering module 16 are used again to develop the new prescription(s). The doctor agrees to the new prescriptions and switch mechanism 26 changes to the new prescription(s) as seen in FIG. 28.


It should be understood that various changes and modifications to the presently preferred embodiments described herein will be apparent to those skilled in the art. Such changes and modifications can be made without departing from the spirit and scope of the present subject matter and without diminishing its intended advantages. It is therefore intended that such changes and modifications be covered by the appended claims.

Claims
  • 1. A peritoneal dialysis system comprising: at least one pump; a memory device configured to store: ultrafiltration (“UF”) therapy prescriptions including a first UF therapy prescription, a second UF therapy prescription with a longer duration and a lower dextrose concentration compared to the first UF therapy prescription, and a third UF therapy prescription with a shorter duration and a higher dextrose concentration compared to the first UF therapy prescription,a schedule indicative as to which of the first, second, or third UF therapy prescriptions are to be performed on specified dates, anda limit of possible permissible UF therapy prescription changes for a given week; anda logic implementer communicatively coupled to the memory device and configured to: determine or identify a current date;use the schedule stored in the memory device to select one of the first, second, or third UF therapy prescription based on the current date;receive an input from a patient regarding a selection of one of the first, second, or third UF therapy prescription for the current date that is changed from the UF therapy prescription specified by the schedule:increment a counter regarding a number of times that the patient selected UF therapy prescription was used to perform a peritoneal dialysis therapy instead of the UF therapy prescription specified by the schedule for a current week:determine whether the counter is below the limit of permissible UF therapy prescription changes; andwhen the counter is below the limit, control the at least one pump based on the patient selected UF therapy prescription instead of the UF therapy prescription specified by the schedule to perform a peritoneal dialysis therapy.
  • 2. The peritoneal dialysis system of claim 1, wherein the logic implementer is communicatively coupled to a network and further configured to: receive the schedule from a clinician computer or a server via the network; andstore the schedule to the memory device.
  • 3. The peritoneal dialysis system of claim 1, further comprising a user interface device configured to: receive a first calendar input from the patient regarding a selection of one of the UF therapy prescriptions for certain dates;receive a second calendar input from the patient regarding a reason for the selection of the UF therapy prescription for each of the certain dates; andtransmit the first and second calendar inputs to a clinician computer or a server via a network.
  • 4. The peritoneal dialysis system of claim 3, wherein the logic implementer is further configured to: receive the schedule from the clinician computer or the server via the network after the clinician computer or the server (a) receives an approval of the first and second calendar inputs, or (b) receives a modification to the selected UF therapy prescription for at least one of the dates of the first calendar input; andstore the schedule to the memory device.
  • 5. The peritoneal dialysis system of claim 3, wherein the user interface device is communicatively coupled to the logic implementer.
  • 6. The peritoneal dialysis system of claim 1, wherein the logic implementer is further configured to: determine whether the counter is meets or exceeds the limit of permissible UF therapy prescription changes; andwhen the counter meets or exceeds the limit, control the at least one pump based on the UF therapy prescription specified by the schedule to perform the peritoneal dialysis therapy instead of using the patient selected UF therapy prescription.
  • 7. The peritoneal dialysis system of claim 1, wherein the limit includes more than one UF therapy prescription change per week.
  • 8. A peritoneal dialysis system comprising: at least one pump;a memory device configured to store: ultrafiltration (“UF”) therapy prescriptions including a first UF therapy prescription, a second UF therapy prescription with a longer duration and a lower dextrose concentration compared to the first UF therapy prescription, and a third UF therapy prescription with a shorter duration and a higher dextrose concentration compared to the first UF therapy prescription,a schedule indicative as to which of the first, second, or third UF therapy prescriptions are to be performed on specified dates, andan alarm threshold of permissible UF therapy prescription changes for a given week or month; anda logic implementer communicatively coupled to the memory device and configured to: determine or identify a current date;use the schedule stored in the memory device to select one of the first, second, or third UF therapy prescription based on the current date:receive an input from a patient regarding a selection of one of the first, second, or third UF therapy prescription for the current date that is changed from the UF therapy prescription specified by the schedule;control the at least one pump based on the patient selected UF therapy prescription instead of the UF therapy prescription specified by the schedule to perform a peritoneal dialysis therapy;increment a counter regarding a number of times the patient selected UF therapy prescription was used instead of the UF therapy prescription specified by the schedule for a current week or month;determine whether the counter meets or exceeds the alarm threshold; andwhen the counter meets or exceeds the alarm threshold, transmit an alarm message via a network to a clinician computer or a server, the alarm message indicative of the alarm threshold being met or exceeded.
  • 9. The peritoneal dialysis system of claim 8, wherein the logic implementer is further configured to increment the counter only when the patient selects the second UF therapy prescription or the third UF therapy prescription.
  • 10. The peritoneal dialysis system of claim 8, wherein the UF therapy prescriptions additionally include a fourth UF therapy prescription with a shorter duration and a higher dextrose concentration compared to the first UF therapy prescription, and a fifth UF therapy prescription with a shorter duration and a higher dextrose concentration compared to the first UF therapy prescription.
  • 11. The peritoneal dialysis system of claim 8, wherein the peritoneal dialysis therapy includes at least one of a tidal dialysis therapy or a continuous cycling peritoneal dialysis therapy (“CCPD”).
  • 12. A peritoneal dialysis system comprising: at least one pump;a memory device configured to store: ultrafiltration (“UF”) therapy prescriptions including a first UF therapy prescription, second UF therapy prescription, and a third UF therapy prescription,a schedule indicative as to which of the UF therapy prescription performed on specified dates, and
  • 13. The peritoneal dialysis system of claim 12, further comprising a user interface device configured to: receive calendar inputs from the patient regarding selections of the UF therapy prescriptions for certain dates; andtransmit the calendar inputs to a clinician computer or a server via a network.
  • 14. The peritoneal dialysis system of claim 13, wherein the logic implementer is further configured to: receive the schedule from the clinician computer or the server via the network after the clinician computer or the server (a) receives an approval of the calendar inputs, or (b) receives a modification to the selected UF therapy prescription for at least one of the dates; andstore the schedule to the memory device.
  • 15. The peritoneal dialysis system of claim 13, wherein the user interface device is communicatively coupled to the logic implementer.
  • 16. The peritoneal dialysis system of claim 13, wherein the schedule is integrated with an inventory tracking feature at the server for determining when fluid containers for performing subsequent peritoneal dialysis therapies are to be mailed to the patient.
  • 17. A peritoneal dialysis system comprising: at least one pump;a memory device configured to store:ultrafiltration (“UF”) therapy prescriptions including a first UF therapy prescription, second UF therapy prescription, and a third UF therapy prescription,a schedule indicative as to which of the UF therapy prescriptions are to be performed on specified dates, anda limit of permissible UF therapy prescription changes for a given week; anda logic implementer communicatively coupled to the memory device and configured to:determine or identify a current date;use the schedule stored in the memory device to select one of the first, second, or third UF therapy prescription based on the current date:receive an input from a patient regarding a selection of one of the first, second or third UF therapy prescription for the current date that is changed from the UF therapy prescription specified by the schedule;increment a counter regarding a number of times that the patient selected UF therapy prescription was used to perform a peritoneal dialysis therapy instead of the UF therapy prescription specified by the schedule for a current week;determine whether the counter is below the limit of permissible UF therapy prescription changes; andwhen the counter is below the limit, control the at least one pump based on the patient selected UF therapy prescription instead of the UF therapy prescription specified by the schedule to perform a peritoneal dialysis therapy.
  • 18. The peritoneal dialysis system of claim 17, wherein the logic implementer is further configured to: determine whether the counter meets or exceeds the limit of permissible UF therapy prescription changes; and when the counter meets or exceeds the limit, control the at least one pump based on the UF therapy prescription specified by the schedule to perform the peritoneal dialysis therapy instead of using the patient selected UF therapy prescription.
PRIORITY CLAIM

This application claims priority to and the benefit as a continuation application of U.S. Patent Application entitled “Dialysis System Having Adaptive Prescription Generation”, Ser. No. 16/871,558, filed May 11, 2020, now U.S. Pat. No. 11,311,658, issued date Apr. 26, 2022, which is a continuation application of U.S. Patent Application entitled “Dialysis System and Disposable Set”, Ser. No. 16/141,353, filed Sep. 25, 2018, now U.S. Pat. No. 10,646,634, issue date May 12, 2020, which is a divisional application of U.S. Patent Application entitled, “Dialysis Method Including Wireless Patient Data”, Ser. No. 14/518,274, filed Oct. 20, 2014, now U.S. Pat. No. 10,307,524, issue date, Jun. 4, 2019, which is a continuation of U.S. Patent Application entitled, “Dialysis Method Including Wireless Patient Data”, Ser. No. 13/679,525, filed Nov. 16, 2012, now U.S. Pat. No. 8,871,095, issue date Oct. 28, 2014, which is a continuation of U.S. Patent Application entitled, “Dialysis System Including Wireless Patient Data and Trending And Alert Generation”, Ser. No. 13/274,012, filed Oct. 14, 2011, now U.S. Pat. No. 8,313,642, issue date, Nov. 20, 2012, which is a continuation of U.S. Patent Application entitled, “Dialysis Systems Having Trending and Alert Generation”, Ser. No. 12/170,220, filed Jul. 9, 2008, now U.S. Pat. No. 8,057,679, issue date, Nov. 15, 2011, the entire contents each of which are incorporated herein by reference and relied upon.

US Referenced Citations (1532)
Number Name Date Kind
250868 Abbott Dec 1881 A
927476 Barker Jul 1909 A
1505050 Lauritsen Aug 1924 A
2292007 Morgan Aug 1942 A
2736332 Simmons Feb 1956 A
3044236 Bearden et al. Jul 1962 A
3074645 Main Jan 1963 A
3095062 Neely Jun 1963 A
3229445 Kraft Jan 1966 A
3287885 Sommer Nov 1966 A
3295297 Collins Jan 1967 A
3342019 Smythe Sep 1967 A
3412760 Franck Nov 1968 A
3426150 Tygart Feb 1969 A
3527572 Urkiewicz Sep 1970 A
3540477 Hogel Nov 1970 A
3563381 Edelson et al. Feb 1971 A
3581464 Bhuta et al. Jun 1971 A
3598727 Wilock Aug 1971 A
3677710 Hirsch Jul 1972 A
3685680 Tenckhoff et al. Aug 1972 A
3739943 Williamsen et al. Jun 1973 A
3742938 Stern Jul 1973 A
3744492 Leibinsohn Jul 1973 A
3744636 Commarmot Jul 1973 A
3756234 Kopp Sep 1973 A
3756752 Stenner Sep 1973 A
3769207 Baer Oct 1973 A
3771288 Wisman et al. Nov 1973 A
3774762 Lichtenstein Nov 1973 A
3786190 Pori Jan 1974 A
3795088 Esmond Mar 1974 A
3809871 Howard et al. May 1974 A
3810102 Parks, III et al. May 1974 A
3814249 Eaton Jun 1974 A
3827561 Serfass et al. Aug 1974 A
3830234 Kopp Aug 1974 A
3834386 Sisley Sep 1974 A
3848112 Weichselbaum et al. Nov 1974 A
3849071 Kayser Nov 1974 A
3858574 Page Jan 1975 A
3878095 Frasier et al. Apr 1975 A
3908653 Kettering Sep 1975 A
3910257 Fletcher et al. Oct 1975 A
3915802 Kominek Oct 1975 A
3910260 Sarnoff et al. Nov 1975 A
3921196 Patterson Nov 1975 A
3946731 Lichtenstein Mar 1976 A
3964479 Boag et al. Jun 1976 A
3971000 Cromwell Jul 1976 A
3976311 Spendlove Aug 1976 A
3985134 Lissot et al. Oct 1976 A
3996027 Schnell et al. Dec 1976 A
3998103 Bjorklund et al. Dec 1976 A
4031891 Jess Jun 1977 A
4032908 Rice et al. Jun 1977 A
4038190 Baudet et al. Jul 1977 A
4047563 Kurata Sep 1977 A
4048995 Mittleman Sep 1977 A
4054522 Pinkerton Oct 1977 A
4060485 Eaton Nov 1977 A
4061031 Grimsrud Dec 1977 A
4067803 Quentin Jan 1978 A
4078562 Friedman Mar 1978 A
4102655 Jeffrey et al. Jul 1978 A
4137160 Ebing et al. Jan 1979 A
4144496 Cunningham et al. Mar 1979 A
4149860 Kulik Apr 1979 A
4151088 Wolf, Jr. et al. Apr 1979 A
4151407 McBride et al. Apr 1979 A
4156867 Bench et al. May 1979 A
4164320 Irazoqui et al. Aug 1979 A
4173971 Karz Nov 1979 A
4181245 Garrett et al. Jan 1980 A
4191182 Popovich et al. Mar 1980 A
4199307 Jassawalla Apr 1980 A
4200095 Reti Apr 1980 A
4209402 Gentles Jun 1980 A
4244816 Vogler et al. Jan 1981 A
4270532 Franetzki et al. Jun 1981 A
4273121 Jassawalla Jun 1981 A
4282872 Franetzki et al. Aug 1981 A
4293413 Schnell Oct 1981 A
4303376 Siekmann Dec 1981 A
4304670 Watanabe et al. Dec 1981 A
4308866 Jelliffe et al. Jan 1982 A
4311137 Gerard Jan 1982 A
4319338 Grudowski et al. Mar 1982 A
4320757 Whitney et al. Mar 1982 A
4325715 Bowman et al. Apr 1982 A
4332264 Gortz Jun 1982 A
4344777 Siposs Aug 1982 A
4345919 Wilkinson et al. Aug 1982 A
4345999 Sigdell et al. Aug 1982 A
4348280 George et al. Sep 1982 A
4353368 Slovak et al. Oct 1982 A
4354252 Lamb et al. Oct 1982 A
4360323 Anderson Nov 1982 A
4363641 Finn, III Dec 1982 A
4368118 Siposs Jan 1983 A
4369780 Sakai Jan 1983 A
4370983 Lichtenstein Feb 1983 A
4373527 Fischell Feb 1983 A
4381776 Latham, Jr. May 1983 A
4385630 Gilcher et al. May 1983 A
4386634 Stasz et al. Jun 1983 A
4398289 Schoate Aug 1983 A
4398908 Siposs Aug 1983 A
4416654 Schoendorfer et al. Nov 1983 A
4425114 Schoendorfer et al. Jan 1984 A
4427009 Wells et al. Jan 1984 A
4428381 Hepp Jan 1984 A
4433971 Lindsay et al. Feb 1984 A
4443216 Chappell Apr 1984 A
4447224 DeCant, Jr. et al. May 1984 A
4449538 Corbitt et al. May 1984 A
4451255 Bujan et al. May 1984 A
4457750 Hill Jul 1984 A
4458693 Badzinski et al. Jul 1984 A
4460358 Somerville et al. Jul 1984 A
4464172 Lichtenstein Aug 1984 A
4469481 Kobayashi Sep 1984 A
4475901 Kraegen et al. Oct 1984 A
4476381 Rubin Oct 1984 A
4477342 Allan et al. Oct 1984 A
4480751 Lueptow Nov 1984 A
4481670 Freeburg Nov 1984 A
4487604 Iwatschenko et al. Dec 1984 A
4490798 Franks et al. Dec 1984 A
4493705 Gordon et al. Jan 1985 A
4496351 Hillel et al. Jan 1985 A
4511352 Theeuwes et al. Apr 1985 A
4512163 Wells et al. Apr 1985 A
4525861 Freeburg Jun 1985 A
4529401 Leslie et al. Jul 1985 A
4531527 Reinhold, Jr. et al. Jul 1985 A
4531937 Yates Jul 1985 A
4538138 Harvey et al. Aug 1985 A
4545071 Freeburg Oct 1985 A
4551133 Zegers de Beyl et al. Nov 1985 A
4559038 Berg et al. Dec 1985 A
4560979 Rosskopf Dec 1985 A
4561443 Hogrefe et al. Dec 1985 A
4562751 Nason Jan 1986 A
4568333 Sawyer et al. Feb 1986 A
4583981 Urquhart et al. Apr 1986 A
4586925 Carlsson et al. May 1986 A
4590473 Burke et al. May 1986 A
4602249 Abbott Jul 1986 A
4619653 Fischell Oct 1986 A
4622032 Katsura et al. Nov 1986 A
4622979 Katchis et al. Nov 1986 A
4624661 Arimond Nov 1986 A
4636950 Caswell Jan 1987 A
4637817 Archibald et al. Jan 1987 A
4643713 Viitala Feb 1987 A
4643715 Isono et al. Feb 1987 A
4650458 Dahlberg et al. Mar 1987 A
4650469 Berg et al. Mar 1987 A
4652262 Veracchi Mar 1987 A
4655941 Suzuki Apr 1987 A
4657490 Abbott Apr 1987 A
4664891 Cosentino et al. May 1987 A
4666598 Heath et al. May 1987 A
4676776 Howson Jun 1987 A
4681563 Deckert et al. Jul 1987 A
4681606 Swan, Jr. et al. Jul 1987 A
4684460 Issautier Aug 1987 A
4688167 Agarwal Aug 1987 A
4691580 Fosslien Sep 1987 A
4695954 Rose et al. Sep 1987 A
4696671 Epstein et al. Sep 1987 A
4697928 Csongor Oct 1987 A
4702595 Mutschler et al. Oct 1987 A
4702829 Polaschegg et al. Oct 1987 A
4705506 Archibald Nov 1987 A
4708802 Rath et al. Nov 1987 A
4714462 DiComenico Dec 1987 A
4717042 McLaughlin Jan 1988 A
4718576 Tamura et al. Jan 1988 A
4722224 Scheller et al. Feb 1988 A
4722349 Baumberg Feb 1988 A
4722725 Sawyer et al. Feb 1988 A
4722731 Vailancourt Feb 1988 A
4722734 Kolln Feb 1988 A
4730849 Siegel Mar 1988 A
4731058 Doan Mar 1988 A
4732411 Siegel Mar 1988 A
4734198 Harm et al. Mar 1988 A
4734269 Clarke et al. Mar 1988 A
4741732 Crankshaw et al. May 1988 A
4741736 Brown May 1988 A
4756706 Kerns et al. Jul 1988 A
4759756 Forman Jul 1988 A
4767399 Bollish Aug 1988 A
4778449 Weber et al. Oct 1988 A
4778451 Kamen Oct 1988 A
4779626 Peel et al. Oct 1988 A
4784645 Fischell Nov 1988 A
4785799 Schoon et al. Nov 1988 A
4785969 McLaughlin Nov 1988 A
4796644 Polaschegg Jan 1989 A
4797840 Fraden Jan 1989 A
4803625 Fu et al. Feb 1989 A
4806135 Siposs Feb 1989 A
4810090 Boucher Mar 1989 A
4810243 Howson Mar 1989 A
4811844 Moulding, Jr. et al. Mar 1989 A
4816208 Woods et al. Mar 1989 A
4817044 Ogren Mar 1989 A
4828543 Weiss et al. May 1989 A
4828545 Epstein et al. May 1989 A
4830018 Treach May 1989 A
4831562 McIntosh et al. May 1989 A
4832033 Maher et al. May 1989 A
4835372 Beard et al. May 1989 A
4835521 Andrejasich et al. May 1989 A
4838275 Lee Jun 1989 A
4838865 Flank et al. Jun 1989 A
4839806 Goldfischer et al. Jun 1989 A
4845644 Anthias et al. Jul 1989 A
4847764 Halvorson Jul 1989 A
4850009 Zook et al. Jul 1989 A
4850972 Schulman et al. Jul 1989 A
4853521 Claeys et al. Aug 1989 A
4854324 Hirschman et al. Aug 1989 A
4857713 Brown Aug 1989 A
4857716 Gombrich et al. Aug 1989 A
4865584 Epstein et al. Sep 1989 A
4871351 Feingold Oct 1989 A
4878175 Norden-Paul et al. Oct 1989 A
4889132 Hutcheson et al. Dec 1989 A
4889134 Greenwold et al. Dec 1989 A
4893270 Beck et al. Jan 1990 A
4897777 Janke et al. Jan 1990 A
4898576 Philip Feb 1990 A
4898578 Rubalcaba, Jr. Feb 1990 A
4901728 Hutchison Feb 1990 A
4908017 Howson et al. Mar 1990 A
4912623 Rantala et al. Mar 1990 A
4916441 Gombrich et al. Apr 1990 A
4922922 Pollock et al. May 1990 A
4923612 Trivett et al. May 1990 A
4925444 Orkin et al. May 1990 A
4932987 Molina Jun 1990 A
4933843 Scheller et al. Jun 1990 A
4937777 Flood et al. Jun 1990 A
4941808 Qureshi et al. Jul 1990 A
4941875 Brennan Jul 1990 A
4943279 Samiotes et al. Jul 1990 A
4946439 Eggers Aug 1990 A
4949274 Hollander et al. Aug 1990 A
4952928 Carroll et al. Aug 1990 A
4953074 Kametani et al. Aug 1990 A
4955508 Capanna et al. Sep 1990 A
D311061 Vrana et al. Oct 1990 S
4960230 Marelli Oct 1990 A
4966579 Polaschegg Oct 1990 A
4967928 Carter Nov 1990 A
4968295 Neumann Nov 1990 A
4976683 Gauthier et al. Dec 1990 A
4976685 Block, Jr. Dec 1990 A
4977590 Milovancevic Dec 1990 A
4978335 Arthur Dec 1990 A
4991091 Allen Feb 1991 A
4992926 Janke et al. Feb 1991 A
4993068 Piosenka et al. Feb 1991 A
4997464 Kopf Mar 1991 A
4998249 Bennett et al. Mar 1991 A
5002055 Merki et al. Mar 1991 A
5002471 Perlov Mar 1991 A
5003296 Lee Mar 1991 A
5006699 Felkner et al. Apr 1991 A
5007429 Treatch et al. Apr 1991 A
5011607 Shinzato Apr 1991 A
5012402 Akiyama Apr 1991 A
5012411 Policastro et al. Apr 1991 A
5014875 McLaughlin et al. May 1991 A
5016172 Dessertine May 1991 A
5023770 Siverling Jun 1991 A
5025374 Roizen et al. Jun 1991 A
5032265 Jha et al. Jul 1991 A
5036852 Leishman Aug 1991 A
5038800 Oba Aug 1991 A
5041086 Koenig et al. Aug 1991 A
5045048 Kaleskas et al. Sep 1991 A
5047147 Chevallet et al. Sep 1991 A
5047959 Phillips et al. Sep 1991 A
5049492 Sauer et al. Sep 1991 A
5053031 Borsanyi Oct 1991 A
5053990 Kreifels et al. Oct 1991 A
5055001 Natwick et al. Oct 1991 A
5057076 Polaschegg Oct 1991 A
5059173 Sacco Oct 1991 A
5061236 Sutherland et al. Oct 1991 A
5061243 Winchell et al. Oct 1991 A
5061365 Utterberg Oct 1991 A
5062774 Kramer et al. Nov 1991 A
5072356 Watt et al. Dec 1991 A
5072383 Brimm et al. Dec 1991 A
5072412 Henderson, Jr. et al. Dec 1991 A
5078683 Sancoff et al. Jan 1992 A
5084828 Kaufman et al. Jan 1992 A
5087245 Doan Feb 1992 A
5088515 Kamen Feb 1992 A
5088904 Okada Feb 1992 A
5088981 Howson et al. Feb 1992 A
5088990 Hivale et al. Feb 1992 A
5091094 Veech Feb 1992 A
5096385 Georgi et al. Mar 1992 A
5098377 Borsanyi et al. Mar 1992 A
5100380 Adaniya et al. Mar 1992 A
5104374 Bishko et al. Apr 1992 A
5108363 Tuttle et al. Apr 1992 A
5108367 Epstein et al. Apr 1992 A
5108372 Swenson Apr 1992 A
5109487 Ohgomori et al. Apr 1992 A
5109849 Goodman et al. May 1992 A
5112319 Lai May 1992 A
5112480 Hukasawa May 1992 A
5114580 Ahmad et al. May 1992 A
5116203 Natwick et al. May 1992 A
5116312 Blankenship et al. May 1992 A
5120303 Hombrouckx Jun 1992 A
5122516 Watanabe et al. Jun 1992 A
5131092 Sackmann et al. Jul 1992 A
5134574 Beaverstock et al. Jul 1992 A
5135500 Zdeb Aug 1992 A
5137023 Mendelson et al. Aug 1992 A
5151978 Bronikowski et al. Sep 1992 A
5152296 Simons Oct 1992 A
5153416 Neeley Oct 1992 A
5153827 Coutre et al. Oct 1992 A
5155693 Altmayer et al. Oct 1992 A
5157595 Lovrenich Oct 1992 A
5158091 Butterfield et al. Oct 1992 A
5159673 Sackmann et al. Oct 1992 A
5160320 Yum et al. Nov 1992 A
5161211 Taguchi et al. Nov 1992 A
5167235 Seacord et al. Dec 1992 A
5167921 Gordon Dec 1992 A
5172698 Stanko Dec 1992 A
5173125 Felding Dec 1992 A
5176004 Gaudet Jan 1993 A
5178763 Delaunay Jan 1993 A
5179569 Sawyer Jan 1993 A
5179700 Aihara et al. Jan 1993 A
5181910 Scanlon Jan 1993 A
5190185 Blechl Mar 1993 A
5190522 Wojcicki et al. Mar 1993 A
5191891 Righter Mar 1993 A
5204000 Steadman et al. Apr 1993 A
5208907 Shelton et al. May 1993 A
5211849 Kitaevich et al. May 1993 A
5213099 Tripp, Jr. May 1993 A
5213232 Kraft et al. May 1993 A
5213568 Lattin et al. May 1993 A
5219330 Bollish et al. Jun 1993 A
5219331 Vanderveen Jun 1993 A
5221267 Folden Jun 1993 A
5225974 Mathews et al. Jul 1993 A
5226425 Righter Jul 1993 A
5228450 Sellers Jul 1993 A
5228889 Cortial et al. Jul 1993 A
5231990 Gauglitz Aug 1993 A
5234404 Tuttle et al. Aug 1993 A
5235510 Yamada et al. Aug 1993 A
5236416 McDaniel et al. Aug 1993 A
5236476 Klick Aug 1993 A
5238001 Gallant et al. Aug 1993 A
5240007 Pytel et al. Aug 1993 A
5244463 Cordner, Jr. et al. Sep 1993 A
5245704 Weber et al. Sep 1993 A
5246560 Nekoksa et al. Sep 1993 A
5254096 Rondelet et al. Oct 1993 A
5256156 Kern et al. Oct 1993 A
5256157 Samiotes et al. Oct 1993 A
5256371 Pippert Oct 1993 A
5259954 Taylor Nov 1993 A
5259961 Eigendorf Nov 1993 A
5265010 Evans-Paganelli et al. Nov 1993 A
5265431 Gaudet et al. Nov 1993 A
5267174 Kaufman et al. Nov 1993 A
5268077 Bubik et al. Dec 1993 A
5271405 Boyer et al. Dec 1993 A
5272318 Gorman Dec 1993 A
5272321 Otsuka et al. Dec 1993 A
5273517 Barone et al. Dec 1993 A
5274434 Morioka et al. Dec 1993 A
5277188 Selker Jan 1994 A
5283861 Dangler et al. Feb 1994 A
5284150 Butterfield et al. Feb 1994 A
5286252 Tuttle et al. Feb 1994 A
5292029 Pearson Mar 1994 A
5295505 Polaschegg et al. Mar 1994 A
5297257 Struger et al. Mar 1994 A
5298021 Sherer Mar 1994 A
5304126 Epstein et al. Apr 1994 A
5307263 Brown Apr 1994 A
5307372 Sawyer et al. Apr 1994 A
5307463 Hyatt et al. Apr 1994 A
5311908 Barone et al. May 1994 A
5314243 McDonald et al. May 1994 A
5315505 Pratt et al. May 1994 A
5317506 Coutre et al. May 1994 A
5318750 Lascombes Jun 1994 A
5319543 Wilhelm Jun 1994 A
5321618 Gessman Jun 1994 A
5321829 Zifferer Jun 1994 A
5325478 Shelton et al. Jun 1994 A
5326473 Lascombes et al. Jul 1994 A
5327341 Whalen et al. Jul 1994 A
5330420 Lee Jul 1994 A
5331549 Crawford, Jr. Jul 1994 A
5336165 Twardowski Aug 1994 A
5336245 Adams et al. Aug 1994 A
5337230 Baumgartner et al. Aug 1994 A
5338157 Blomquist Aug 1994 A
5339821 Fujimoto Aug 1994 A
5341291 Roizen et al. Aug 1994 A
5341412 Ramot et al. Aug 1994 A
D350822 Lanigan Sep 1994 S
D350823 Lanigan Sep 1994 S
5348008 Bornn et al. Sep 1994 A
5348539 Herskowitz Sep 1994 A
5349675 Fitzgerald et al. Sep 1994 A
5350357 Kamen et al. Sep 1994 A
5356376 Milijasevic et al. Oct 1994 A
5356378 Doan Oct 1994 A
5358481 Todd et al. Oct 1994 A
5361202 Doue Nov 1994 A
5361758 Hall et al. Nov 1994 A
5366896 Margrey et al. Nov 1994 A
5366904 Qureshi et al. Nov 1994 A
5367555 Isoyama Nov 1994 A
5368555 Sussman et al. Nov 1994 A
5368562 Blomquist et al. Nov 1994 A
5370612 Maeda et al. Dec 1994 A
5371687 Holmes, II et al. Dec 1994 A
5374251 Smith Dec 1994 A
5374813 Shipp Dec 1994 A
5374965 Kanno Dec 1994 A
5375604 Kelly et al. Dec 1994 A
5376070 Colman et al. Dec 1994 A
5376263 Fischel Dec 1994 A
5377864 Blechl et al. Jan 1995 A
5378231 Johnson et al. Jan 1995 A
5379214 Arbuckle et al. Jan 1995 A
5385564 Slater et al. Jan 1995 A
5389078 Zalesky et al. Feb 1995 A
5390238 Kirk et al. Feb 1995 A
5392951 Gardner et al. Feb 1995 A
5394732 Johnson et al. Mar 1995 A
5395320 Padda et al. Mar 1995 A
5395321 Kawahara et al. Mar 1995 A
5398336 Tantry et al. Mar 1995 A
5401059 Ferrario Mar 1995 A
5401238 Pirazzoli Mar 1995 A
5401342 Vincent et al. Mar 1995 A
D357312 Riquier et al. Apr 1995 S
5404292 Hendrickson Apr 1995 A
5404384 Colburn et al. Apr 1995 A
5406473 Yoshikura et al. Apr 1995 A
5411472 Steg, Jr. et al. May 1995 A
5411705 Thor et al. May 1995 A
5412715 Volpe May 1995 A
5415167 Wilk May 1995 A
5416695 Miller et al. May 1995 A
5417222 Dempsey et al. May 1995 A
5420977 Sztipanovits et al. May 1995 A
5421343 Feng Jun 1995 A
5421815 Noguchi et al. Jun 1995 A
5423746 Burkett et al. Jun 1995 A
5429595 Wright, Jr. et al. Jul 1995 A
5429602 Hauser Jul 1995 A
5431299 Brewer et al. Jul 1995 A
5431627 Pastrone et al. Jul 1995 A
5433736 Nilsson Jul 1995 A
5438607 Przygoda, Jr. et al. Aug 1995 A
5440699 Farrand et al. Aug 1995 A
5441047 David et al. Aug 1995 A
5441636 Chevallet et al. Aug 1995 A
5445294 Gardner et al. Aug 1995 A
5445621 Poli et al. Aug 1995 A
5446868 Gardea, II et al. Aug 1995 A
5453098 Botts et al. Sep 1995 A
5455851 Chaco et al. Oct 1995 A
5458123 Unger Oct 1995 A
5460294 Williams Oct 1995 A
5460605 Tuttle et al. Oct 1995 A
5461665 Shur et al. Oct 1995 A
5462051 Oka et al. Oct 1995 A
5464392 Epstein et al. Nov 1995 A
5465286 Clare et al. Nov 1995 A
5467773 Bergelson et al. Nov 1995 A
5468110 McDonald et al. Nov 1995 A
5468388 Goddard et al. Nov 1995 A
5469855 Pompei et al. Nov 1995 A
5471382 Tallman et al. Nov 1995 A
5470483 Bene et al. Dec 1995 A
5474552 Palti Dec 1995 A
5482043 Zulauf Jan 1996 A
5482446 Williamson et al. Jan 1996 A
5484397 Twardowski Jan 1996 A
5485408 Blomquist Jan 1996 A
5489385 Raabe et al. Feb 1996 A
5490610 Pearson Feb 1996 A
5490925 Eigendorf Feb 1996 A
5494592 Latham, Jr. et al. Feb 1996 A
5496265 Langley et al. Mar 1996 A
5496273 Pastrone et al. Mar 1996 A
5498338 Kruger et al. Mar 1996 A
5502944 Kraft et al. Apr 1996 A
5503801 Brugger Apr 1996 A
5507412 Ebert et al. Apr 1996 A
5508912 Schneiderman Apr 1996 A
5509422 Fukami Apr 1996 A
5509895 Noguchi et al. Apr 1996 A
5513957 O'Leary May 1996 A
5514088 Zakko May 1996 A
5514095 Brightbill et al. May 1996 A
5515426 Yacenda et al. May 1996 A
5520450 Colson, Jr. et al. May 1996 A
5520637 Pager et al. May 1996 A
5520640 Utterberg May 1996 A
5522396 Langer et al. Jun 1996 A
5522798 Johnson et al. Jun 1996 A
5526428 Arnold Jun 1996 A
5528503 Moore et al. Jun 1996 A
5529063 Hill Jun 1996 A
5531680 Dumas et al. Jul 1996 A
5531697 Olsen et al. Jul 1996 A
5531698 Olsen Jul 1996 A
5533079 Colburn et al. Jul 1996 A
5533981 Mandro et al. Jul 1996 A
5534691 Holdaway et al. Jul 1996 A
5536084 Curtis et al. Jul 1996 A
5537313 Pirelli Jul 1996 A
5537853 Finburgh et al. Jul 1996 A
5540808 Vincent et al. Jul 1996 A
5540842 Aoyama et al. Jul 1996 A
5542420 Goldman et al. Aug 1996 A
5544649 David et al. Aug 1996 A
5544651 Wilk Aug 1996 A
5544661 Davis et al. Aug 1996 A
5545131 Davankov Aug 1996 A
5545140 Conero et al. Aug 1996 A
5546580 Seliger et al. Aug 1996 A
5547470 Johnson et al. Aug 1996 A
5549117 Tacklind et al. Aug 1996 A
5549460 O'Leary Aug 1996 A
5553609 Chen et al. Sep 1996 A
5558638 Evers et al. Sep 1996 A
5558640 Pfeiler et al. Sep 1996 A
5560352 Heim et al. Oct 1996 A
5562232 Pearson Oct 1996 A
5562621 Claude et al. Oct 1996 A
5563347 Martin et al. Oct 1996 A
5564803 McDonald et al. Oct 1996 A
5568912 Minami et al. Oct 1996 A
5569186 Lord et al. Oct 1996 A
5569187 Kaiser Oct 1996 A
5570026 Buffaloe, IV et al. Oct 1996 A
5571258 Pearson Nov 1996 A
5573502 LeCocq et al. Nov 1996 A
5573506 Vasko Nov 1996 A
5575632 Morris et al. Nov 1996 A
5576952 Stutman et al. Nov 1996 A
5578070 Utterberg Nov 1996 A
5579001 Dempsey et al. Nov 1996 A
5579378 Arlinghaus, Jr. Nov 1996 A
5581369 Righter et al. Dec 1996 A
5581687 Lyle et al. Dec 1996 A
5582593 Hultman Dec 1996 A
5583758 McIlroy et al. Dec 1996 A
5588815 Zaleski, II Dec 1996 A
5588816 Abbott et al. Dec 1996 A
5589932 Garcia-Rubio et al. Dec 1996 A
5590648 Mitchell et al. Jan 1997 A
5591251 Brugger Jan 1997 A
5591344 Kenley et al. Jan 1997 A
5593267 McDonald et al. Jan 1997 A
5594637 Eisenberg et al. Jan 1997 A
5594786 Chaco et al. Jan 1997 A
5597995 Williams et al. Jan 1997 A
5598536 Slaughter, III et al. Jan 1997 A
5601445 Schipper et al. Feb 1997 A
5605540 Utterberg Feb 1997 A
5609572 Lang Mar 1997 A
5609575 Larson et al. Mar 1997 A
5609576 Voss et al. Mar 1997 A
5613115 Gihl et al. Mar 1997 A
5614677 Wansiedler et al. Mar 1997 A
5616248 Schal Apr 1997 A
5619428 Lee et al. Apr 1997 A
5619991 Sloane Apr 1997 A
5623652 Vora et al. Apr 1997 A
5623925 Swenson et al. Apr 1997 A
5626144 Tacklind et al. May 1997 A
5628619 Wilson May 1997 A
5628908 Kamen May 1997 A
5630710 Tune et al. May 1997 A
5631844 Margrey et al. May 1997 A
5633910 Cohen May 1997 A
D380260 Hyman Jun 1997 S
5634893 Rishton Jun 1997 A
5637081 Noguchi et al. Jun 1997 A
5637082 Pages et al. Jun 1997 A
5637093 Hyman et al. Jun 1997 A
5640301 Roecher et al. Jun 1997 A
5640953 Bishop et al. Jun 1997 A
5640995 Packard et al. Jun 1997 A
5641628 Bianchi Jun 1997 A
5643193 Papillon et al. Jul 1997 A
5643212 Coutre et al. Jul 1997 A
5643250 Utterberg Jul 1997 A
5647853 Feldmann et al. Jul 1997 A
5647854 Olsen et al. Jul 1997 A
5650071 Brugger et al. Jul 1997 A
5651775 Walker et al. Jul 1997 A
5652566 Lambert Jul 1997 A
5658240 Urdahl et al. Aug 1997 A
5658250 Blomquist et al. Aug 1997 A
5658456 Kenley et al. Aug 1997 A
5661978 Holmes et al. Sep 1997 A
5664270 Bell et al. Sep 1997 A
5666404 Ciccotelli et al. Sep 1997 A
5674199 Brugger Oct 1997 A
5678562 Sellers Oct 1997 A
5678568 Uchikubo et al. Oct 1997 A
5681285 Ford et al. Oct 1997 A
5681294 Osborne et al. Oct 1997 A
5682526 Smokoff et al. Oct 1997 A
5683355 Fini et al. Nov 1997 A
5683367 Jordan et al. Nov 1997 A
5685844 Marttila Nov 1997 A
5685988 Malchesky Nov 1997 A
5687717 Halpern Nov 1997 A
5687734 Dempsey et al. Nov 1997 A
5690831 Kenley et al. Nov 1997 A
5695473 Olsen Dec 1997 A
5697951 Harpstead Dec 1997 A
5700998 Palti Dec 1997 A
5701894 Cherry et al. Dec 1997 A
5702597 Chevallet et al. Dec 1997 A
5702606 Peter, Jr. et al. Dec 1997 A
5704351 Mortara et al. Jan 1998 A
5704364 Saltzstein et al. Jan 1998 A
5704366 Tacklind et al. Jan 1998 A
5712798 Langley et al. Jan 1998 A
5712912 Tomko et al. Jan 1998 A
5713485 Liff et al. Feb 1998 A
5713856 Eggers et al. Feb 1998 A
5715823 Wood et al. Feb 1998 A
5716114 Holmes et al. Feb 1998 A
5716194 Butterfield et al. Feb 1998 A
5718562 Lawless et al. Feb 1998 A
5719761 Gatti et al. Feb 1998 A
RE35743 Pearson Mar 1998 E
5722947 Jeppsson et al. Mar 1998 A
5724025 Tavori Mar 1998 A
5724580 Levin et al. Mar 1998 A
5725776 Kenley et al. Mar 1998 A
5730712 Falkvall et al. Mar 1998 A
5730730 Darling, Jr. Mar 1998 A
5732709 Tacklind et al. Mar 1998 A
5733259 Valcke et al. Mar 1998 A
5735887 Barreras, Sr. et al. Apr 1998 A
5737539 Edelson et al. Apr 1998 A
5740185 Bosse Apr 1998 A
5740800 Hendrickson et al. Apr 1998 A
5745366 Higham et al. Apr 1998 A
5745378 Barker et al. Apr 1998 A
5752917 Fuchs May 1998 A
5752976 Duffin et al. May 1998 A
5755563 Clegg et al. May 1998 A
5762782 Kenley et al. Jun 1998 A
5763266 Palsson et al. Jun 1998 A
5764923 Tallman et al. Jun 1998 A
5766155 Hyman et al. Jun 1998 A
5769811 Stacey et al. Jun 1998 A
5771657 Lasher et al. Jun 1998 A
5772585 Lavin et al. Jun 1998 A
5772586 Heinonen et al. Jun 1998 A
5772635 Dastur Jun 1998 A
5772637 Heinzmann et al. Jun 1998 A
5776057 Swenson et al. Jul 1998 A
5776091 Brugger et al. Jul 1998 A
5776345 Truitt et al. Jul 1998 A
5778345 McCartney Jul 1998 A
5778882 Raymond et al. Jul 1998 A
5781442 Chamberlain et al. Jul 1998 A
5782575 Vincent et al. Jul 1998 A
5782805 Meinzer et al. Jul 1998 A
5782878 Morgan et al. Jul 1998 A
5785650 Akasaka et al. Jul 1998 A
5788669 Peterson Aug 1998 A
5790409 Fedor et al. Aug 1998 A
5791342 Woodard Aug 1998 A
5791880 Wilson Aug 1998 A
5793861 Haigh Aug 1998 A
5793969 Kamentsky et al. Aug 1998 A
5795317 Brierton et al. Aug 1998 A
5795327 Wilson et al. Aug 1998 A
5797515 Liff et al. Aug 1998 A
5800387 Duffy et al. Sep 1998 A
5803906 Pratt et al. Sep 1998 A
5805442 Crater et al. Sep 1998 A
5805456 Higham et al. Sep 1998 A
5805505 Zheng et al. Sep 1998 A
5807321 Stoker et al. Sep 1998 A
5807322 Lindsey et al. Sep 1998 A
5807336 Chen et al. Sep 1998 A
5810747 Brudny et al. Sep 1998 A
5814015 Cowen et al. Sep 1998 A
5815566 Ramot et al. Sep 1998 A
5822418 Yacenda et al. Oct 1998 A
5822544 Chaco et al. Oct 1998 A
5823949 Goltra Oct 1998 A
5826237 Macrae et al. Oct 1998 A
5829438 Gibbs et al. Nov 1998 A
5830185 Block, Jr. Nov 1998 A
5832448 Brown Nov 1998 A
5832450 Myers et al. Nov 1998 A
5833599 Schrier et al. Nov 1998 A
5836908 Beden et al. Nov 1998 A
5841975 Layne et al. Nov 1998 A
5842841 Danby et al. Dec 1998 A
5842976 Williamson Dec 1998 A
5845253 Rensimer et al. Dec 1998 A
5846419 Nederlof Dec 1998 A
5848593 McGrady et al. Dec 1998 A
5849065 Wojke Dec 1998 A
5851186 Wood et al. Dec 1998 A
5851202 Carlsson Dec 1998 A
5852590 De La Huerga Dec 1998 A
5853387 Clegg et al. Dec 1998 A
5855550 Buyan et al. Jan 1999 A
5857967 Frid et al. Jan 1999 A
5858239 Kenley et al. Jan 1999 A
5859972 Subramaniam et al. Jan 1999 A
5863421 Peter, Jr. et al. Jan 1999 A
5865745 Schmitt et al. Feb 1999 A
5865786 Sibalis et al. Feb 1999 A
5866880 Seitz et al. Feb 1999 A
5867821 Ballantyne et al. Feb 1999 A
5871465 Vasko Feb 1999 A
5871694 Beden et al. Feb 1999 A
5876926 Beecham Mar 1999 A
5880443 McDonald et al. Mar 1999 A
5882338 Gray Mar 1999 A
5883370 Walker et al. Mar 1999 A
5883576 De La Huerga Mar 1999 A
5885245 Lynch et al. Mar 1999 A
5891035 Wood et al. Apr 1999 A
5891734 Gill et al. Apr 1999 A
5893697 Zimi et al. Apr 1999 A
5894273 Meador et al. Apr 1999 A
5895368 Utterberg Apr 1999 A
5895371 Jordan et al. Apr 1999 A
5895578 Simard et al. Apr 1999 A
5897493 Brown Apr 1999 A
5897530 Jackson Apr 1999 A
5897989 Beecham Apr 1999 A
5899665 Makino et al. May 1999 A
5899855 Brown May 1999 A
5901150 Dupouy et al. May 1999 A
5902476 Twardowski May 1999 A
5904668 Hyman et al. May 1999 A
5905653 Higham et al. May 1999 A
5907291 Chen et al. May 1999 A
5908027 Butterfield et al. Jun 1999 A
5910107 Iliff Jun 1999 A
5910252 Truitt et al. Jun 1999 A
5911132 Sloane Jun 1999 A
5911687 Sano et al. Jun 1999 A
5912818 McGrady et al. Jun 1999 A
5913197 Kameda Jun 1999 A
5913310 Brown Jun 1999 A
5915240 Karpf Jun 1999 A
5919154 Toavs et al. Jul 1999 A
5919369 Ash Jul 1999 A
5921938 Aoyama et al. Jul 1999 A
5923018 Kameda et al. Jul 1999 A
5924074 Evans Jul 1999 A
5924103 Ahmed et al. Jul 1999 A
5925011 Faict et al. Jul 1999 A
5927540 Godlewski Jul 1999 A
5928744 Heilmann et al. Jul 1999 A
5928889 Bakich et al. Jul 1999 A
5931791 Saltzstein et al. Aug 1999 A
5931990 Andrews Aug 1999 A
5932103 Kenley et al. Aug 1999 A
5932110 Shah Aug 1999 A
5935060 Iliff Aug 1999 A
5935099 Peterson et al. Aug 1999 A
5935106 Olsen Aug 1999 A
5938413 Makino et al. Aug 1999 A
5939326 Chupp et al. Aug 1999 A
5939699 Perttunen et al. Aug 1999 A
5940306 Gardner et al. Aug 1999 A
5940802 Hildebrand et al. Aug 1999 A
5941829 Saltzstein et al. Aug 1999 A
5942986 Shabot et al. Aug 1999 A
5943423 Muftic Aug 1999 A
5943633 Wilson et al. Aug 1999 A
5944659 Flach et al. Aug 1999 A
5945651 Chorosinski et al. Aug 1999 A
5946083 Melendez et al. Aug 1999 A
5946659 Lancelot et al. Aug 1999 A
5948251 Brugger Sep 1999 A
5950006 Crater et al. Sep 1999 A
5951300 Brown Sep 1999 A
5951510 Barak Sep 1999 A
5951870 Utterberg Sep 1999 A
5954640 Szabo Sep 1999 A
5954885 Bollish et al. Sep 1999 A
5954958 Folden Sep 1999 A
5954971 Pages et al. Sep 1999 A
5956023 Lyle et al. Sep 1999 A
5957153 Frey et al. Sep 1999 A
5957885 Bollish et al. Sep 1999 A
5959529 Kail, IV Sep 1999 A
5960085 De La Huerga Sep 1999 A
5960403 Brown Sep 1999 A
5960991 Ophardt Oct 1999 A
5961446 Beller et al. Oct 1999 A
5961448 Swenson et al. Oct 1999 A
5961487 Davis Oct 1999 A
5964700 Tallman et al. Oct 1999 A
5966304 Cook et al. Oct 1999 A
5967975 Ridgeway Oct 1999 A
5970423 Langley et al. Oct 1999 A
5971593 McGrady Oct 1999 A
5971921 Timbel Oct 1999 A
5971948 Pages et al. Oct 1999 A
5974124 Schlueter, Jr. et al. Oct 1999 A
5975737 Crater et al. Nov 1999 A
5980490 Tsoukalis Nov 1999 A
5980741 Schnell et al. Nov 1999 A
5983193 Heinonen et al. Nov 1999 A
5983947 Utterberg Nov 1999 A
5987519 Peifer et al. Nov 1999 A
5989318 Schroll Nov 1999 A
5989423 Kamen et al. Nov 1999 A
5991731 Colon et al. Nov 1999 A
5993046 McGrady et al. Nov 1999 A
5993420 Hyman et al. Nov 1999 A
5995077 Wilcox et al. Nov 1999 A
5995965 Experton Nov 1999 A
5997167 Crater et al. Dec 1999 A
5997476 Brown Dec 1999 A
6001201 Vincent et al. Dec 1999 A
6003006 Colella et al. Dec 1999 A
6004020 Bartur Dec 1999 A
6004276 Wright et al. Dec 1999 A
6004311 Heilmann et al. Dec 1999 A
6009333 Chaco Dec 1999 A
6010454 Arieff et al. Jan 2000 A
6010623 Schnell et al. Jan 2000 A
6011858 Stock et al. Jan 2000 A
6011999 Holmes Jan 2000 A
6012034 Hamparian et al. Jan 2000 A
6013057 Danby et al. Jan 2000 A
6014631 Teagarden et al. Jan 2000 A
6016444 John Jan 2000 A
6017318 Gauthier et al. Jan 2000 A
6018713 Coli et al. Jan 2000 A
6019745 Gray Feb 2000 A
6019824 Schnell Feb 2000 A
6021392 Lester et al. Feb 2000 A
6022315 Iliff Feb 2000 A
6023522 Draganoff et al. Feb 2000 A
6024539 Blomquist Feb 2000 A
6024699 Allen et al. Feb 2000 A
6027217 McClure et al. Feb 2000 A
6029138 Khorasani et al. Feb 2000 A
6032119 Brown et al. Feb 2000 A
6032155 de la Huerga Feb 2000 A
6033076 Braeuning et al. Mar 2000 A
6039251 Crone et al. Mar 2000 A
6039467 Holmes Mar 2000 A
6046806 Thompson Apr 2000 A
6047259 Campbell et al. Apr 2000 A
6050940 Braun et al. Apr 2000 A
6051134 Schnell et al. Apr 2000 A
6053967 Heilmann et al. Apr 2000 A
6055487 Margery et al. Apr 2000 A
6057758 Dempsey et al. May 2000 A
6059736 Tapper May 2000 A
6061603 Papadopoulos et al. May 2000 A
6061941 Verret May 2000 A
6065819 Holmes et al. May 2000 A
6066111 Brockhoff May 2000 A
6068153 Young et al. May 2000 A
6071269 Schnell et al. Jun 2000 A
6073046 Patel et al. Jun 2000 A
6074345 van Oostrom et al. Jun 2000 A
6079621 Vardanyan et al. Jun 2000 A
6080106 Lloyd et al. Jun 2000 A
6081048 Bergmann et al. Jun 2000 A
6082776 Feinberg Jul 2000 A
6083206 Molko Jul 2000 A
6093146 Filangeri Jul 2000 A
6095985 Raymond et al. Aug 2000 A
6101407 Groezinger Aug 2000 A
6101478 Brown Aug 2000 A
6102856 Groff et al. Aug 2000 A
6108399 Hernandez-Guerra et al. Aug 2000 A
6108588 McGrady Aug 2000 A
6109774 Holmes et al. Aug 2000 A
6112224 Peifer et al. Aug 2000 A
RE36871 Epstein et al. Sep 2000 E
6113554 Gilcher et al. Sep 2000 A
6116461 Broadfield et al. Sep 2000 A
6117342 Schnell et al. Sep 2000 A
6117940 Mjalli Sep 2000 A
6123524 Danby et al. Sep 2000 A
6125350 Dirbas Sep 2000 A
6129517 Danby et al. Oct 2000 A
6132371 Dempsey et al. Oct 2000 A
6132616 Twardowski et al. Oct 2000 A
6134504 Douglas et al. Oct 2000 A
6135949 Russo et al. Oct 2000 A
6139495 De La Huerga Oct 2000 A
6139748 Ericson et al. Oct 2000 A
6139754 Hartranft Oct 2000 A
6139757 Ohmura Oct 2000 A
6144922 Douglas et al. Nov 2000 A
6145695 Garrigues Nov 2000 A
6146523 Barrett et al. Nov 2000 A
6146536 Twardowski Nov 2000 A
6148297 Swor et al. Nov 2000 A
6149063 Reynolds et al. Nov 2000 A
6151536 Arnold et al. Nov 2000 A
6152364 Schoonen et al. Nov 2000 A
6154668 Pedersen et al. Nov 2000 A
6154726 Rensimer et al. Nov 2000 A
6157914 Seto et al. Dec 2000 A
6158965 Butterfield et al. Dec 2000 A
6160478 Jacobsen et al. Dec 2000 A
6161095 Brown Dec 2000 A
6163737 Fedor et al. Dec 2000 A
6165154 Gray et al. Dec 2000 A
6168563 Brown Jan 2001 B1
6170007 Venkatraman et al. Jan 2001 B1
6170746 Brook et al. Jan 2001 B1
6171112 Clark et al. Jan 2001 B1
6171237 Boaz et al. Jan 2001 B1
6171264 Bader Jan 2001 B1
6171484 Schnell et al. Jan 2001 B1
6173198 Schulze et al. Jan 2001 B1
6175779 Barrett Jan 2001 B1
6175977 Schumacher et al. Jan 2001 B1
6176903 Wamsiedler Jan 2001 B1
6182047 Dirbas Jan 2001 B1
6183417 Geheb et al. Feb 2001 B1
6186145 Brown Feb 2001 B1
6187198 Utterberg Feb 2001 B1
6188988 Barry et al. Feb 2001 B1
6192320 Margrey et al. Feb 2001 B1
6193480 Butterfield Feb 2001 B1
6195887 Danby et al. Mar 2001 B1
6198394 Jacobsen et al. Mar 2001 B1
6200264 Satherley et al. Mar 2001 B1
6200289 Hochman et al. Mar 2001 B1
6203495 Bardy Mar 2001 B1
6203528 Deckert et al. Mar 2001 B1
6206238 Ophardt Mar 2001 B1
6206829 Iliff Mar 2001 B1
6206954 Schnell et al. Mar 2001 B1
6210361 Kamen et al. Apr 2001 B1
6213391 Lewis Apr 2001 B1
6213738 Danby et al. Apr 2001 B1
6219439 Burger Apr 2001 B1
6219587 Ahlin et al. Apr 2001 B1
6221011 Bardy Apr 2001 B1
6221012 Maschke et al. Apr 2001 B1
6222619 Herron et al. Apr 2001 B1
6224549 Van Drongelen May 2001 B1
6225901 Kail, IV May 2001 B1
6226564 Stuart May 2001 B1
6228047 Dadson May 2001 B1
6230927 Schoonen et al. May 2001 B1
6234997 Kamen et al. May 2001 B1
6245013 Minoz et al. Jun 2001 B1
6246473 Smith, Jr. et al. Jun 2001 B1
6248063 Barnhill et al. Jun 2001 B1
6248065 Brown Jun 2001 B1
6251167 Berson Jun 2001 B1
6251279 Peterson et al. Jun 2001 B1
6254567 Treu et al. Jul 2001 B1
6255951 De La Huerga Jul 2001 B1
6256643 Cork et al. Jul 2001 B1
6256967 Hebron et al. Jul 2001 B1
6259355 Chaco et al. Jul 2001 B1
6259654 De La Huerga Jul 2001 B1
6260715 Simard et al. Jul 2001 B1
6266645 Simpson Jul 2001 B1
6269340 Ford et al. Jul 2001 B1
D446854 Cheney, II et al. Aug 2001 S
6270455 Brown Aug 2001 B1
6270457 Bardy Aug 2001 B1
6272394 Lipps Aug 2001 B1
6272505 De La Huerga Aug 2001 B1
6274034 Nikaido et al. Aug 2001 B1
6274103 Taylor Aug 2001 B1
6277072 Bardy Aug 2001 B1
6280632 Polaschegg Aug 2001 B1
6280634 Shah et al. Aug 2001 B1
6283322 Liff et al. Sep 2001 B1
6283944 McMullen et al. Sep 2001 B1
6287516 Matson et al. Sep 2001 B1
6290646 Cosentino Sep 2001 B1
6290650 Butterfield et al. Sep 2001 B1
6294999 Yarin et al. Sep 2001 B1
6295506 Heinonen Sep 2001 B1
6304788 Eady et al. Oct 2001 B1
6306088 Krausman et al. Oct 2001 B1
6307956 Black Oct 2001 B1
6308171 De La Huerga Oct 2001 B1
6309673 Duponchelle Oct 2001 B1
6311163 Sheehan et al. Oct 2001 B1
6312227 Davis Nov 2001 B1
6312378 Bardy Nov 2001 B1
6312414 Brockhoff et al. Nov 2001 B1
6314384 Goetz Nov 2001 B1
6315895 Summerton et al. Nov 2001 B1
6317719 Schrier et al. Nov 2001 B1
6319200 Lai Nov 2001 B1
6321203 Kameda Nov 2001 B1
6322504 Kirshner Nov 2001 B1
6322515 Goor et al. Nov 2001 B1
6322551 Brugger Nov 2001 B1
6331252 El Sayyid et al. Dec 2001 B1
RE37531 Chaco et al. Jan 2002 E
6337631 Pai Jan 2002 B1
6338007 Broadfield et al. Jan 2002 B1
6339732 Phoon et al. Jan 2002 B1
6344139 Utterberg Feb 2002 B1
6345260 Cummings, Jr. et al. Feb 2002 B1
6346886 De La Huerga Feb 2002 B1
6348162 Ash Feb 2002 B1
6352200 Schoonen et al. Mar 2002 B1
6353817 Jacobs et al. Mar 2002 B1
6357600 Scagliarini Mar 2002 B1
6358225 Butterfield Mar 2002 B1
6358237 Paukovits Mar 2002 B1
6361201 Russell et al. Mar 2002 B1
6361263 Dewey et al. Mar 2002 B1
6362591 Moberg Mar 2002 B1
6363282 Nichols et al. Mar 2002 B1
6363290 Lyle et al. Mar 2002 B1
6366282 Nichols et al. Mar 2002 B1
6364143 Knierbein Apr 2002 B1
6364834 Reuss et al. Apr 2002 B1
6364857 Gray et al. Apr 2002 B1
6368273 Brown Apr 2002 B1
6370841 Chudy et al. Apr 2002 B1
6381577 Brown Apr 2002 B1
6382923 Gray May 2002 B1
6385505 Lipps May 2002 B1
6391541 Petersen et al. May 2002 B1
6391638 Shaaltiel May 2002 B1
6393369 Carr May 2002 B1
6397190 Goetz May 2002 B1
6402702 Gilcher et al. Jun 2002 B1
6406426 Reuss et al. Jun 2002 B1
6406631 Collins et al. Jun 2002 B1
6407335 Franklin-Lees et al. Jun 2002 B1
6408330 De La Huerga Jun 2002 B1
6416293 Bouchard et al. Jul 2002 B1
6416471 Kumar et al. Jul 2002 B1
6421650 Goetz et al. Jul 2002 B1
6426056 Taylor Jul 2002 B2
6427088 Bowman, IV et al. Jul 2002 B1
6434531 Lancelot et al. Aug 2002 B1
6434569 Tomlinson et al. Aug 2002 B1
6449927 Hebron et al. Sep 2002 B2
6450956 Rappaport et al. Sep 2002 B1
6458102 Mann et al. Oct 2002 B1
6464977 Kai et al. Oct 2002 B2
6468242 Wilson et al. Oct 2002 B1
6470234 McGrady Oct 2002 B1
6471089 Liff et al. Oct 2002 B2
6471645 Warkentin et al. Oct 2002 B1
6475146 Frelburger et al. Nov 2002 B1
6475148 Jackson et al. Nov 2002 B1
6475180 Peterson et al. Nov 2002 B2
6478737 Bardy Nov 2002 B2
6485465 Moberg et al. Nov 2002 B2
6489301 Kobira et al. Dec 2002 B1
6511138 Gardner et al. Jan 2003 B1
6519569 White et al. Feb 2003 B1
6537244 Paukovits Mar 2003 B2
6542902 Dulong et al. Apr 2003 B2
6542910 Cork et al. Apr 2003 B2
6544174 West et al. Apr 2003 B2
6544228 Heitmeier Apr 2003 B1
6551243 Bocionek et al. Apr 2003 B2
6551276 Mann et al. Apr 2003 B1
6554791 Cartledge et al. Apr 2003 B1
6554798 Mann et al. Apr 2003 B1
6555986 Moberg Apr 2003 B2
6558321 Burd et al. May 2003 B1
6561975 Pool et al. May 2003 B1
6562001 Lebel et al. May 2003 B2
6564104 Nelson et al. May 2003 B2
6564105 Starkweather et al. May 2003 B2
6571128 Lebel et al. May 2003 B2
6575900 Zweig et al. Jun 2003 B1
6577899 Lebel et al. Jun 2003 B2
6579232 Sakamaki et al. Jun 2003 B2
6581069 Robinson et al. Jun 2003 B1
6582385 Burbank et al. Jun 2003 B2
6584336 Ali et al. Jun 2003 B1
6585157 Brandt et al. Jul 2003 B2
6585644 Lebel et al. Jul 2003 B2
6585675 O'Mahony et al. Jul 2003 B1
6592551 Cobb Jul 2003 B1
6593528 Franklin-Lees et al. Jul 2003 B2
6595944 Balschat et al. Jul 2003 B2
6607485 Bardy Aug 2003 B2
6613009 Bainbridge et al. Sep 2003 B1
6623709 Taylor Sep 2003 B2
6635014 Starkweather et al. Oct 2003 B2
6648821 Lebel et al. Nov 2003 B2
6656355 Sano Dec 2003 B2
6659948 Lebel et al. Dec 2003 B2
6664893 Eveland et al. Dec 2003 B1
6668196 Villegas et al. Dec 2003 B1
6673314 Burbank et al. Jan 2004 B1
6673376 Knerr et al. Jan 2004 B1
6685831 Donig et al. Feb 2004 B2
6687546 Lebel et al. Feb 2004 B2
6689091 Bui et al. Feb 2004 B2
6694191 Starkweather et al. Feb 2004 B2
6694334 Dulong et al. Feb 2004 B2
6733446 Lebel et al. May 2004 B2
6733447 Lai et al. May 2004 B2
6740075 Lebel et al. May 2004 B2
6745903 Grandics Jun 2004 B2
6746398 Hervy et al. Jun 2004 B2
6749818 Sano et al. Jun 2004 B2
6752928 Pfeil et al. Jun 2004 B2
6758810 Lebel et al. Jul 2004 B2
6758975 Peabody et al. Jul 2004 B2
6768425 Flaherty et al. Jul 2004 B2
6787032 Kurome et al. Sep 2004 B2
6790198 White et al. Sep 2004 B1
6804656 Rosenfeld et al. Oct 2004 B1
6810290 Lebel et al. Oct 2004 B2
6811533 Lebel et al. Nov 2004 B2
6811534 Bowman, IV et al. Nov 2004 B2
6811707 Rovatti et al. Nov 2004 B2
6813519 Lebel et al. Nov 2004 B2
6820093 De La Huerga Nov 2004 B2
6854088 Massengale et al. Feb 2005 B2
6861033 Mullins et al. Mar 2005 B2
6871211 Labounty et al. Mar 2005 B2
6873268 Lebel et al. Mar 2005 B2
6880034 Manke et al. Apr 2005 B2
6885288 Pincus Apr 2005 B2
6902670 Ho Jun 2005 B2
6908546 Smith Jun 2005 B2
6912549 Rotter et al. Jun 2005 B2
6913590 Sorenson et al. Jul 2005 B2
6923987 Kai et al. Aug 2005 B2
6928452 De La Huerga Aug 2005 B2
6950708 Bowman IV et al. Sep 2005 B2
6958705 Lebel et al. Oct 2005 B2
6974437 Lebel et al. Dec 2005 B2
6976628 Krupa Dec 2005 B2
6979306 Moll Dec 2005 B2
6980958 Surwit et al. Dec 2005 B1
6986872 Taylor Jan 2006 B2
7024245 Lebel et al. Apr 2006 B2
7039878 Auer et al. May 2006 B2
7044927 Mueller et al. May 2006 B2
7045061 Nishimura et al. May 2006 B2
7051002 Keresman, III et al. May 2006 B2
7061831 De La Huerga Jun 2006 B2
7072769 Fletcher-Haynes et al. Jul 2006 B2
7076520 Nelson et al. Jul 2006 B2
7077956 Rovatti Jul 2006 B2
7089780 Sunshine et al. Aug 2006 B2
7092796 Vanderveen Aug 2006 B2
7096072 Engleson et al. Aug 2006 B2
7108790 Collins et al. Sep 2006 B2
7117239 Hansen Oct 2006 B1
7122210 Elisabettini Oct 2006 B2
7156808 Quy Jan 2007 B2
7161484 Tsoukalis Jan 2007 B2
7165221 Monteleone et al. Jan 2007 B2
7171274 Starkweather et al. Jan 2007 B2
7188151 Kumar et al. Mar 2007 B2
7194336 DeGianfilippo et al. Mar 2007 B2
7208092 Micheli Apr 2007 B2
7216802 De La Huerga May 2007 B1
7231263 Choi Jun 2007 B2
7238156 Adamczyk Jul 2007 B1
7250619 Taylor et al. Jul 2007 B2
7251610 Alban et al. Jul 2007 B2
7264148 Tachibana Sep 2007 B2
7274799 Cohen et al. Sep 2007 B2
7275220 Brummel et al. Sep 2007 B2
7290680 Henry et al. Nov 2007 B2
7292141 Staats et al. Nov 2007 B2
7300418 Zaleski Nov 2007 B2
7304582 Robert et al. Dec 2007 B2
7306736 Collins et al. Dec 2007 B2
7308894 Hickle Dec 2007 B2
7309323 Gura et al. Dec 2007 B2
7315825 Rosenfeld et al. Jan 2008 B2
7316648 Kelly et al. Jan 2008 B2
7316662 Delnevo et al. Jan 2008 B2
7317967 DiGianfilippo et al. Jan 2008 B2
7319386 Collins, Jr. et al. Jan 2008 B2
7321862 Rosenfeld et al. Jan 2008 B2
7343224 DiGianfilippo et al. Mar 2008 B2
7347819 Lebel et al. Mar 2008 B2
7356382 Vanderveen Apr 2008 B2
7369913 Heminway et al. May 2008 B2
7383196 Tang et al. Jun 2008 B1
7384410 Eggers et al. Jun 2008 B2
7419587 Valbjoern et al. Sep 2008 B2
7419597 Brugger et al. Sep 2008 B2
7544300 Brugger et al. Jun 2009 B2
7749393 Brugger et al. Jul 2010 B2
7890341 McNally Feb 2011 B2
7892423 Rohde et al. Feb 2011 B2
7976711 Brugger et al. Jul 2011 B2
7981281 Yu Jul 2011 B2
8057679 Yu Nov 2011 B2
8062513 Yu Nov 2011 B2
8071055 Newcombe Dec 2011 B2
8177977 Gaignet May 2012 B2
8192387 Brugger et al. Jun 2012 B2
8216452 Rohde et al. Jul 2012 B2
8257582 Yu Sep 2012 B2
8313642 Yu Nov 2012 B2
8354029 Hank Jan 2013 B2
8425767 Fava et al. Apr 2013 B2
8512554 Yu Aug 2013 B2
8871095 Yu Oct 2014 B2
9078971 Scarpaci Jul 2015 B2
9697334 Yu Jul 2017 B2
9860302 Wittner et al. Jan 2018 B2
10307524 Yu Jun 2019 B2
10646634 Yu May 2020 B2
11311658 Yu Apr 2022 B2
20010001237 Stroda et al. May 2001 A1
20010003177 Schena et al. Jun 2001 A1
20010007053 Bardy Jul 2001 A1
20010007932 Kamen et al. Jul 2001 A1
20010011153 Bardy Aug 2001 A1
20010016699 Burbank et al. Aug 2001 A1
20010017817 De La Huerga Aug 2001 A1
20010021801 Bardy Sep 2001 A1
20010021817 Brugger et al. Sep 2001 A1
20010025138 Bardy Sep 2001 A1
20010025156 Bui et al. Sep 2001 A1
20010027634 Hebron et al. Oct 2001 A1
20010028308 De La Huerga Oct 2001 A1
20010030234 Wiklof Oct 2001 A1
20010031944 Peterson et al. Oct 2001 A1
20010032101 Statius Muller Oct 2001 A1
20010034502 Moberg et al. Oct 2001 A1
20010034616 Giannini Oct 2001 A1
20010037057 Bardy Nov 2001 A1
20010037079 Burbank et al. Nov 2001 A1
20010037083 Hartlaub et al. Nov 2001 A1
20010037217 Abensour et al. Nov 2001 A1
20010037220 Merry et al. Nov 2001 A1
20010041920 Starkweather et al. Nov 2001 A1
20010042441 Purdom et al. Nov 2001 A1
20010044588 Mault Nov 2001 A1
20010044731 Coffman et al. Nov 2001 A1
20010051764 Bardy Dec 2001 A1
20010053885 Gielen et al. Dec 2001 A1
20020002326 Causey, III et al. Jan 2002 A1
20020002473 Schrier et al. Jan 2002 A1
20020004645 Carlisle et al. Jan 2002 A1
20020010568 Rubbert et al. Jan 2002 A1
20020013612 Whitehurst Jan 2002 A1
20020016567 Hochman et al. Feb 2002 A1
20020016568 Lebel et al. Feb 2002 A1
20020016719 Nemeth et al. Feb 2002 A1
20020016722 Kameda Feb 2002 A1
20020019606 Lebel et al. Feb 2002 A1
20020019748 Brown Feb 2002 A1
20020022776 Bardy Feb 2002 A1
20020025796 Taylor et al. Feb 2002 A1
20020026104 Bardy Feb 2002 A1
20020029157 Marchosky Mar 2002 A1
20020029776 Blomquist Mar 2002 A1
20020032602 Lanzillo, Jr. et al. Mar 2002 A1
20020038392 De La Huerga Mar 2002 A1
20020040208 Flaherty et al. Apr 2002 A1
20020044043 Chaco et al. Apr 2002 A1
20020046062 Kameda Apr 2002 A1
20020046185 Villart et al. Apr 2002 A1
20020046346 Evans Apr 2002 A1
20020052539 Haller et al. May 2002 A1
20020052542 Bardy May 2002 A1
20020052574 Hochman et al. May 2002 A1
20020065540 Lebel et al. May 2002 A1
20020067273 Jaques et al. Jun 2002 A1
20020068015 Polaschegg et al. Jun 2002 A1
20020072718 Brugger et al. Jun 2002 A1
20020072733 Flaherty Jun 2002 A1
20020077852 Ford et al. Jun 2002 A1
20020077865 Sullivan Jun 2002 A1
20020082480 Riff et al. Jun 2002 A1
20020082865 Bianco et al. Jun 2002 A1
20020082868 Pories et al. Jun 2002 A1
20020084904 De La Huerga Jul 2002 A1
20020087120 Rogers et al. Jul 2002 A1
20020099283 Christ et al. Jul 2002 A1
20020099301 Bardy Jul 2002 A1
20020100762 Liff et al. Aug 2002 A1
20020107476 Mann et al. Aug 2002 A1
20020107707 Naparstek et al. Aug 2002 A1
20020116509 De La Huerga Aug 2002 A1
20020128606 Cowan et al. Sep 2002 A1
20020128871 Adamson et al. Sep 2002 A1
20020128880 Kunikiyo Sep 2002 A1
20020131332 Kaelin Sep 2002 A1
20020133377 Brown Sep 2002 A1
20020140675 Ali et al. Oct 2002 A1
20020143254 Maruyama Oct 2002 A1
20020156462 Stultz Oct 2002 A1
20020158128 Ashiuro Oct 2002 A1
20020162778 Peabody et al. Nov 2002 A1
20020165491 Reilly Nov 2002 A1
20020169636 Eggers et al. Nov 2002 A1
20020198513 Lebel et al. Dec 2002 A1
20030011646 Levine Jan 2003 A1
20030023177 Bardy Jan 2003 A1
20030036783 Bauhahn et al. Feb 2003 A1
20030050621 Lebel et al. Mar 2003 A1
20030052787 Zerhusen Mar 2003 A1
20030060753 Starkweather et al. Mar 2003 A1
20030060754 Reilly Mar 2003 A1
20030060765 Campbell et al. Mar 2003 A1
20030060768 Kiyatake Mar 2003 A1
20030065287 Spohn et al. Apr 2003 A1
20030078534 Hochman et al. Apr 2003 A1
20030083901 Bosch et al. May 2003 A1
20030088238 Poulsen et al. May 2003 A1
20030097092 Flaherty May 2003 A1
20030114836 Estes et al. Jun 2003 A1
20030125611 Bardy Jul 2003 A1
20030135250 Lauman et al. Jul 2003 A1
20030139701 White et al. Jul 2003 A1
20030140929 Wilkes et al. Jul 2003 A1
20030141368 Pascual et al. Jul 2003 A1
20030144878 Wilkes et al. Jul 2003 A1
20030144880 Talachian et al. Jul 2003 A1
20030144881 Talachian et al. Jul 2003 A1
20030144882 Talachian et al. Jul 2003 A1
20030154108 Fletcher-Haynes et al. Aug 2003 A1
20030160683 Blomquist Aug 2003 A1
20030163088 Blomquist Aug 2003 A1
20030163223 Blomquist Aug 2003 A1
20030163789 Blomquist Aug 2003 A1
20030167035 Flaherty et al. Sep 2003 A1
20030176933 Lebel et al. Sep 2003 A1
20030181851 Mann et al. Sep 2003 A1
20030182164 Shabot et al. Sep 2003 A1
20030195397 Bardy Oct 2003 A1
20030201697 Richardson Oct 2003 A1
20030204414 Wilkes et al. Oct 2003 A1
20030204416 Radpay et al. Oct 2003 A1
20030204419 Wilkes et al. Oct 2003 A1
20030204420 Wilkes et al. Oct 2003 A1
20030212379 Bylund et al. Nov 2003 A1
20030220605 Bowman et al. Nov 2003 A1
20030225596 Richardson et al. Dec 2003 A1
20030225728 Moura Dec 2003 A1
20040010425 Wilkes et al. Jan 2004 A1
20040039260 Bardy Feb 2004 A1
20040039264 Bardy Feb 2004 A1
20040051368 Caputo et al. Mar 2004 A1
20040088374 Webb et al. May 2004 A1
20040111293 Firanek et al. Jun 2004 A1
20040116862 Ray Jun 2004 A1
20040117215 Marchosky Jun 2004 A1
20040121767 Simpson et al. Jun 2004 A1
20040167465 Mihai et al. Aug 2004 A1
20040172283 Vanderveen et al. Sep 2004 A1
20040172300 Mihai et al. Sep 2004 A1
20040172301 Mihai et al. Sep 2004 A1
20040172302 Martucci et al. Sep 2004 A1
20040176667 Mihai et al. Sep 2004 A1
20040193328 Zaitsu et al. Sep 2004 A1
20040204673 Flaherty Oct 2004 A1
20040215490 Duchon et al. Oct 2004 A1
20040220829 Baharav et al. Nov 2004 A1
20040235446 Flaherty et al. Nov 2004 A1
20040260233 Garibotto et al. Dec 2004 A1
20050038680 McMahon Feb 2005 A1
20050054923 Pan Mar 2005 A1
20050065817 Mihai et al. Mar 2005 A1
20050070767 Maschke Mar 2005 A1
20050071194 Bormann et al. Mar 2005 A1
20050080651 Morrison et al. Apr 2005 A1
20050177096 Bollish et al. Apr 2005 A1
20050102167 Kapoor May 2005 A1
20050131340 Sorenson et al. Jun 2005 A1
20050131741 Tang et al. Jun 2005 A1
20050133449 Sternby Jun 2005 A1
20050135306 McAllen et al. Jun 2005 A1
20050137573 McLaughlin Jun 2005 A1
20050139651 Lim et al. Jun 2005 A1
20050143671 Hastings et al. Jun 2005 A1
20050148890 Hastings Jul 2005 A1
20050171815 Vanderveen Aug 2005 A1
20050177395 Blomquist Aug 2005 A1
20050201345 Williamson Sep 2005 A1
20050228693 Webb et al. Oct 2005 A1
20050231374 Diem et al. Oct 2005 A1
20050234381 Niemetz et al. Oct 2005 A1
20050246416 Blomquist Nov 2005 A1
20050267780 Ray et al. Dec 2005 A1
20050278194 Holland et al. Dec 2005 A1
20050283385 Hunkeler et al. Dec 2005 A1
20060015015 Kawamoto et al. Jan 2006 A1
20060167722 Struys et al. Jan 2006 A1
20060064020 Burnes et al. Mar 2006 A1
20060064053 Bollish et al. Mar 2006 A1
20060065713 Kingery Mar 2006 A1
20060089539 Miodownik et al. Apr 2006 A1
20060089854 Holland et al. Apr 2006 A1
20060089855 Holland et al. Apr 2006 A1
20060100907 Holland et al. May 2006 A1
20060106647 Brummel et al. May 2006 A1
20060106649 Eggers et al. May 2006 A1
20060116639 Russell Jun 2006 A1
20060143051 Eggers et al. Jun 2006 A1
20060149591 Hanf et al. Jul 2006 A1
20060173713 Petro et al. Aug 2006 A1
20060190302 Eggers et al. Aug 2006 A1
20060200369 Batch et al. Sep 2006 A1
20060206356 Vanderveen Sep 2006 A1
20060211994 Roman et al. Sep 2006 A1
20060229551 Martinez et al. Oct 2006 A1
20060247606 Batch Nov 2006 A1
20060253301 Simms et al. Nov 2006 A1
20060258985 Russell Nov 2006 A1
20060259327 Hoag Nov 2006 A1
20060277070 Hungerford et al. Dec 2006 A1
20070033073 Tajaliawal Feb 2007 A1
20070073266 Chmiel et al. Mar 2007 A1
20070083386 Chuang et al. Apr 2007 A1
20070083390 Gorup et al. Apr 2007 A1
20070088578 Hoffman et al. Apr 2007 A1
20070124002 Estes et al. May 2007 A1
20070129983 Scherpbier et al. Jun 2007 A1
20070135866 Baker et al. Jun 2007 A1
20070156452 Batch Jul 2007 A1
20070158268 DeComo Jul 2007 A1
20070163965 Wolfe Jul 2007 A1
20070179807 Nessinger et al. Aug 2007 A1
20070185738 Anuszewski et al. Aug 2007 A1
20070197878 Shklarski Aug 2007 A1
20070198293 Ash et al. Aug 2007 A1
20070203753 Hasan et al. Aug 2007 A1
20070214003 Holland et al. Sep 2007 A1
20070233035 Wehba et al. Oct 2007 A1
20070233049 Wehba et al. Oct 2007 A1
20070233050 Wehba et al. Oct 2007 A1
20070233281 Wehba et al. Oct 2007 A1
20070233520 Wehba et al. Oct 2007 A1
20070233521 Wehba et al. Oct 2007 A1
20070255126 Moberg et al. Nov 2007 A1
20070265879 Charlson et al. Nov 2007 A1
20070276869 Charlson et al. Nov 2007 A1
20070278155 Lo et al. Dec 2007 A1
20070293817 Feng et al. Dec 2007 A1
20080015895 Charlson et al. Jan 2008 A1
20080021741 Holla et al. Jan 2008 A1
20080033360 Evans et al. Feb 2008 A1
20080033749 Blomquist Feb 2008 A1
20080034323 Blomquist Feb 2008 A1
20080045877 Levin et al. Feb 2008 A1
20080045932 Beau et al. Feb 2008 A1
20080052317 Francis et al. Feb 2008 A1
20080059239 Gerst et al. Mar 2008 A1
20080076969 Kraft et al. Mar 2008 A1
20080077436 Muradia Mar 2008 A1
20080091466 Butler et al. Apr 2008 A1
20080097912 Dicks et al. Apr 2008 A1
20080097913 Dicks et al. Apr 2008 A1
20080097914 Dicks et al. Apr 2008 A1
20080103554 Dicks et al. May 2008 A1
20080114292 Rasch-Menges et al. May 2008 A1
20080125693 Gavin May 2008 A1
20080126969 Blomquist May 2008 A1
20080133265 Silkaitis et al. Jun 2008 A1
20080143515 Wood et al. Jun 2008 A1
20080161751 Plahey Jul 2008 A1
20080161754 Marano-Ford Jul 2008 A1
20080203023 Burbank et al. Aug 2008 A1
20080208111 Kamen Aug 2008 A1
20080210606 Burbank Sep 2008 A1
20080230450 Burbank et al. Sep 2008 A1
20090008306 Cicchello Jan 2009 A1
20090008318 Anes et al. Jan 2009 A1
20090008331 Wilt et al. Jan 2009 A1
20090012655 Kienman et al. Jan 2009 A1
20090045121 Kabayama et al. Feb 2009 A1
20090218285 Hank Sep 2009 A1
20100016776 Roher Jan 2010 A1
20100018923 Rohde et al. Jan 2010 A1
20100051546 Vuong et al. Mar 2010 A1
20100078092 Weilhoefer et al. Apr 2010 A1
20100137693 Porras et al. Jun 2010 A1
20100192686 Kamen Aug 2010 A1
20100326916 Wrazel et al. Dec 2010 A1
20100332149 Scholpp Dec 2010 A1
20110072422 Brauer Mar 2011 A1
20110100913 Minami et al. May 2011 A1
20110131058 McNally Jun 2011 A1
20110180480 Kloeffel et al. Jul 2011 A1
20110186521 Burbank et al. Aug 2011 A1
20110192796 Smejtek et al. Aug 2011 A1
20110315611 Fulkerson et al. Dec 2011 A1
20130008854 Wallace et al. Jan 2013 A1
20130062265 Balschat et al. Mar 2013 A1
20140238912 Vincent Aug 2014 A1
20170203022 Burbank et al. Jul 2017 A1
Foreign Referenced Citations (96)
Number Date Country
296007 Jan 1954 CH
1806654 May 1970 DE
20 02 033 Aug 1970 DE
29 01 628 Jul 1980 DE
31 22 756 Jun 1982 DE
33 07 830 Jun 1984 DE
34 42 744 Jun 1986 DE
40 03 452 Aug 1991 DE
42 08 054 Oct 1992 DE
41 22 754 Jan 1993 DE
198 14 695 Oct 1999 DE
198 54 338 Jun 2000 DE
0 058 325 Aug 1982 EP
0 064 393 Oct 1982 EP
0 106 026 Apr 1984 EP
0 143 340 Jun 1985 EP
0 143 341 Jun 1985 EP
0 171 550 Feb 1986 EP
0 233 848 Aug 1987 EP
0 318 993 Jun 1989 EP
0 350 675 Jan 1990 EP
0 373 455 Jun 1990 EP
0 222 709 May 1991 EP
0 490 212 Jun 1992 EP
0 501 144 Sep 1992 EP
0 560 368 Sep 1993 EP
0 587 251 Mar 1994 EP
0 720 856 Jul 1996 EP
0 722 744 Jul 1996 EP
0 749 328 Dec 1996 EP
0 776 222 Jun 1997 EP
0 826 383 Mar 1998 EP
0 826 384 Mar 1998 EP
0 659 091 Dec 2000 EP
1 097 724 May 2001 EP
1 277 485 Jan 2003 EP
1614437 Jan 2006 EP
2180908 May 2010 EP
2 397 197 Feb 1979 FR
2 585 251 Jan 1987 FR
1 408 319 Oct 1975 GB
2 014 060 Aug 1979 GB
1 554 810 Oct 1979 GB
2 061 755 May 1981 GB
2 212 739 Aug 1989 GB
3 026 703 Jul 1998 GR
55-32384 Mar 1980 JP
55-45437 Mar 1980 JP
57161511 Oct 1982 JP
S61143074 Jun 1986 JP
4-2060 Jan 1992 JP
4-348757 Dec 1992 JP
7-299455 Nov 1995 JP
8-29224 Feb 1996 JP
9-327511 Dec 1997 JP
H1085324 Apr 1998 JP
11-137672 May 1999 JP
2000-217908 Aug 2000 JP
2000-296318 Oct 2000 JP
2001-270856 Oct 2001 JP
2003047657 Feb 2003 JP
2003-513714 Apr 2003 JP
20020008145 Jan 2002 KR
1001945 Mar 1983 SU
1992 018048 Oct 1992 WO
9415099 Jul 1994 WO
9517597 Jun 1995 WO
9625214 Aug 1996 WO
9640318 Dec 1996 WO
9709074 Mar 1997 WO
9822165 May 1998 WO
9823353 Jun 1998 WO
9832477 Jul 1998 WO
9942150 Aug 1999 WO
0009182 Feb 2000 WO
0031967 Jun 2000 WO
0057925 Oct 2000 WO
0057926 Oct 2000 WO
0057927 Oct 2000 WO
0064510 Nov 2000 WO
0137786 May 2001 WO
0137894 May 2001 WO
0137895 May 2001 WO
0137900 May 2001 WO
0141831 Jun 2001 WO
0141832 Jun 2001 WO
0141833 Jun 2001 WO
0142758 Jun 2001 WO
0145769 Jun 2001 WO
0147576 Jul 2001 WO
2007118235 Oct 2007 WO
WO2007130491 Nov 2007 WO
2008138311 Nov 2008 WO
2011069110 Jun 2011 WO
2012120078 Sep 2012 WO
2012129501 Sep 2012 WO
Non-Patent Literature Citations (18)
Entry
Translation of Publication KR 20020008145A, published Jan. 2002 (Year: 2002).
Notice of Reasons for Rejection dated Dec. 5, 2017 in corresponding JP Application No. 2013-257132.
European Search Report—EP Application No. 16176496 dated Mar. 21, 2017—13 pages.
European Communication—EP Application No. 09710209.9 dated Mar. 20, 2015—6 pages.
Search and Examination Report dated Jul. 29, 2014 for related GB Appl. No. 1322331.8.
Office Action for Mexican Patent Application No. MX/a/2010/008961 received Apr. 22, 2013.
International Search Report for PCT/US2017/031405 dated May 5, 2017—7 pages.
Written Opinion of the International Searching Authority for PCT/US2017/031405 dated May 5, 2017—13 pages.
International Search Report for PCT/US2017/031400 dated Sep. 25, 2017—7 pages.
Written Opinion of the International Search Authority for PCT/US2017/031400 dated Sep. 25, 2017—14 pages.
International Search Report for PCT/US2017/031396 dated Jul. 27, 2017—6 pages.
Written Opinion of the International Search Authority for PCT/US2017/031396 dated Jul. 27, 2017—7 pages.
U.S. Appl. No. 15/195,801, filed Jun. 28, 2016.
International Search Report for corresponding International Application PCT/US2009/031809 dated Oct. 19, 2009.
Written Opinion for corresponding International Application PCT/US2009/031809 dated Oct. 19, 2009.
Japanese Office Action dated Dec. 14, 2012 for related Application No. 2011-100145—corresponding communication indicates no references cited in Japanese OA (1 page).
Fresenius 90/2 Peritoneal Therapy Cycler, Article, written by Fresenius USA, dated Jul. 1993—6 pages.
Japanese Office Action Application No. 2020-017331 dated Mar. 2, 2021—3 pages.
Related Publications (1)
Number Date Country
20220241482 A1 Aug 2022 US
Divisions (1)
Number Date Country
Parent 14518274 Oct 2014 US
Child 16141353 US
Continuations (5)
Number Date Country
Parent 16871558 May 2020 US
Child 17727334 US
Parent 16141353 Sep 2018 US
Child 16871558 US
Parent 13679525 Nov 2012 US
Child 14518274 US
Parent 13274012 Oct 2011 US
Child 13679525 US
Parent 12170220 Jul 2008 US
Child 13274012 US