Precision blood fluid removal therapy based on patient monitoring

Description

FIELD

The present disclosure relates generally to devices, systems and methods for monitoring parameters of patients that receive blood fluid removal therapy.

BACKGROUND

Patients who undergo hemodialysis or other procedures that remove fluid from blood often die of cardiac complications. Many factors may contribute to such death, including stress placed on the heart due to increased blood fluid volume in these patients. Increased fluid concentrations and inability to appropriately remove waste products from the blood can also contribute to electrolyte and pH imbalance that can affect cardiac contractility and efficiency. Further, rapid changes in fluid volume or pH or electrolyte concentration of the blood during hemodialysis or other fluid removal processes may place additional stress on the heart and may contribute to the high rate of morbidity for patients who undergo blood fluid removal procedures.

When a patient reaches a point where routine blood fluid removal procedures are prescribed, the patient undergoes periodic examinations that allow a healthcare provider to set various parameters of the blood fluid removal procedures, such as the profile of fluid removal, the composition of dialysate or replacement fluid employed, and the like. These examinations typically occur once a month in accordance with current standards of care.

While such monthly examinations somewhat provide for blood fluid removal sessions tailored according to the patient's needs, it may be desirable to provide a more systematic evaluation of the patient and the blood fluid removal session parameters to achieve a more patient-specific therapy.

SUMMARY

This disclosure, among other things, describes devices, systems and methods for monitoring patient parameters and blood fluid removal system parameters and identifying those system parameters that result in improved (more effective) patient parameters or in worsened (less effective) patent parameters. By comparing the patient's past responses to system parameters or changes in system parameters, a blood fluid removal system may be able to avoid future use of parameters that may harm the patient and may be able to learn which parameters are likely to be most effective in treating the patient in a blood fluid removal session. Further, by monitoring the patient's response between sessions, those system parameters that result in lasting improvement or worsening of patient variables may be tracked so that future blood fluid removal sessions may be appropriately tailored to effectuate good lasting outcomes for the patient. In addition or alternatively, tracking patient variables leading up to a blood fluid session may allow proper conditions to be set for the upcoming session based on patient response to prior system parameters when the patient presented with similar variables.

In various embodiments described herein, a method includes (i) storing system parameters from a first blood fluid removal session in memory; (ii) acquiring a first set of data regarding one or more patient parameters following the first session but before a second session; (iii) storing the first data set in a “most effective to date” data set memory; (iv) associating the first system parameters in an increased effectiveness lookup table with the first data set; (v) storing system parameters from the second blood fluid removal session in memory; (vi) acquiring a second set of data regarding the one or more patient parameters following the second session; and (vii) if at least one value of the second data set is closer to the target value than a corresponding at least one value of the first data set: replacing the first data set in the most effective to date data set memory with the second data set; storing in the increased effectiveness lookup table data regarding the second data set; and associating data regarding the second system parameters with the second data set.

In embodiments, a method includes (i) acquiring data regarding one or more of one or more patient physiological parameters and time since last blood fluid removal session; (ii) acquiring data regarding one or more target outcomes of a blood fluid removal session; (iii) comparing the data regarding at least one of the one or more target outcomes of the blood fluid removal session to corresponding data regarding at least one prior target outcome stored in a lookup table, wherein the lookup table comprises data regarding system parameters used in one or more prior blood fluid removal sessions of the patient and comprises patient data prior to the previous session regarding one or more of the one or more patient physiological parameters and the time since last blood fluid removal session; (iv) comparing the data regarding the one or more of the one or more patient physiological parameters and the time since last blood fluid removal session to corresponding patient data prior to the previous session stored in the lookup table; and (v) initiating a blood fluid removal session employing the system parameters used for the prior blood fluid removal session if the at least one of the one or more target outcomes is within a predetermined range of the corresponding data regarding the at least one prior target outcome stored in the lookup table and the data regarding the one or more of the one or more patient physiological parameters and the time since last blood fluid removal session is within a predetermined range of the corresponding patient data prior to the previous session stored in the lookup table.

Blood fluid removal systems configured to carry out the methods described herein are also presented, as are computer readable medium that, when executed, cause a blood fluid removal system to carry out the methods described herein.

One or more embodiments of the systems, devices and methods described herein may provide one or more advantages over prior systems, devices and methods for blood fluid removal in patients. Such advantages will be apparent to those skilled in the art upon reading the following detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated into and form a part of the specification, illustrate several embodiments of the present disclosure and, together with the description, serve to explain the principles of the disclosure. The drawings are only for the purpose of illustrating embodiments of the disclosure and are not to be construed as limiting the disclosure.

FIGS. 1-7 are flow diagrams illustrating methods in accordance with various embodiments described herein.

FIG. 8 is a schematic graphical representation of monitored data (not actual data) shown for purposes of illustration.

FIGS. 9-11 are schematic block diagrams showing interaction of blood fluid removal devices with a patient showing flow of blood (dashed arrows) and fluid (solid arrows), which blood fluid removal devices may be used in various embodiments described herein.

FIG. 12 is a schematic block diagram showing flow paths and some control mechanisms for controlling flow of concentrate into fluid for use in a blood fluid removal process.

FIGS. 13-14 are schematic block diagrams of some components of blood fluid removal devices that are configured to various system parameters.

The schematic drawings presented herein are not necessarily to scale. Like numbers used in the figures refer to like components, steps and the like. However, it will be understood that the use of a number to refer to a component in a given figure is not intended to limit the component in another figure labeled with the same number. In addition, the use of different numbers to refer to components is not intended to indicate that the different numbered components cannot be the same or similar.

DETAILED DESCRIPTION

In the following detailed description, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration several embodiments of devices, systems and methods. It is to be understood that other embodiments are contemplated and may be made without departing from the scope or spirit of the present disclosure. The following detailed description, therefore, is not to be taken in a limiting sense.

All scientific and technical terms used herein have meanings commonly used in the art unless otherwise specified. The definitions provided herein are to facilitate understanding of certain terms used frequently herein and are not meant to limit the scope of the present disclosure.

As used in this specification and the appended claims, the singular forms “a”, “an”, and “the” encompass embodiments having plural referents, unless the content clearly dictates otherwise.

As used in this specification and the appended claims, the term “or” is generally employed in its sense including “and/or” unless the content clearly dictates otherwise.

As used herein, “have”, “having”, “include”, “including”, “comprise”, “comprising” or the like are used in their open ended sense, and generally mean “including, but not limited to.”

As used herein, a “patient for which a blood fluid removal session is indicated” is a patient that has undergone, is undergoing, or is likely to undergo at least one blood fluid removal session. In general, such patients are fluid overloaded patients, such as patients suffering from heart failure, chronic kidney disease, or acute kidney failure. Often such patients are stage 3 to stage 5 chronic kidney disease patients, are unresponsive or under-responsive to diuretics, or the like.

As used herein, a “blood fluid removal process,” or the like, refers to a process from which fluid is removed from blood of a patient and the blood is returned to the patient. In most cases, the blood is also cleaned; i.e., waste products are removed from the blood and cleaned blood is returned to the patient. Examples of blood fluid removal processes include ultrafiltration, hemofiltration, hemodialysis, hemodiafiltration, peritoneal dialysis and the like. Any patient for which blood fluid removal is indicated may benefit from the devices, systems and methods described herein.

As used herein, “effective” or the like, as it relates to patient parameters, refers to the how close one or more patient parameters are to one or more target for the one or more parameters. Thus, a “most effective” patient parameter to date is a patient parameter at a given time that is closer to the target than the same parameter measured at any previous time. A “more effective” patient parameter is a parameter measured at a given time that is closer to the target than the same parameter measured at another time. A “least effective” patient parameter to date is a patient parameter at a given time that is farther from the target than the same parameter measured at any previous time. A “less effective” patient parameter is a parameter measured or observed at a given time that is farther from the target than the same parameter measured at another time.

This disclosure, among other things, describes devices, systems and methods for monitoring patient physiological parameters and blood fluid removal system parameters and identifying those system parameters that result in improved physiological parameters or in worsened physiological parameters. By comparing the patient's past responses to system parameters or changes in system parameters, a blood fluid removal system may be able to avoid future use of parameters that may harm the patient and may be able to learn which parameters are likely to be most effective in treating the patient in a blood fluid removal session.

U.S. Provisional Patent Application No. 61/480,539, entitled ADAPTIVE SYSTEM FOR BLOOD FLUID REMOVAL, filed on Apr. 29, 2011, is incorporated herein by reference in its entirety to the extent that it does not conflict with the present disclosure. While the present disclosure includes much of the discussion and drawings presented in U.S. Provisional Patent Application No. 61/480,539, the present application enhances the disclosure with regard to inter-session parameters and learning.

Referring to FIG. 1, a high level schematic overview of embodiments of the present disclosure is shown. As shown in FIG. 1, a learning algorithm 520 is employed to determine what system parameters work well to produce desired patient physiological results based on input. Any suitable input variable 500 may be considered by the algorithm 520 in the learning process. For example, variables such as how long it has been since the patient's last blood removal session may be input. Such input could be important as patients undergoing, for example, hemodialysis on a Monday, Wednesday, Friday schedule are more likely to suffer an adverse cardiac event just before, during or after the Monday blood fluid removal session. Accordingly, the algorithm 520 may consider whether a different set of system parameters should be employed when the patient has not undergone a session in 72 hours relative to when the patient has not undergone a session in 48 hours. Input variables 500 may also include whether the patient has limited time to undergo a blood fluid removal session. The algorithm 520 can determine whether a faster fluid removal rate should be used or whether a partial session at a reduced fluid removal rate would likely be more effective based on the patient's history of response to fast fluid removal rates. Alternatively, the patient may have additional time to undergo a blood fluid removal session, and the algorithm 520 can take such input 500 into account to determine whether there may be an advantage to slower fluid removal rates or slower adjustment of a concentration of an electrolyte based on the patient's history. Of course, it will be understood that any other suitable input variables 500 may be entered regarding target outcomes (e.g., quick session, long session, etc.), patient history (e.g., time since last session), or the like. In embodiments, input that takes into account future patient behavior or needs may be entered into the system. For example, if a patient knows that they will miss a session or the time until their next session will be delayed from normal, time until next session may be entered, which may affect the system parameters (e.g., may remove additional fluid, etc.). By way of another example, if the patient knows that they will eat or drink an amount more than optimal before the session, expected consumption levels may be input in the system.

As shown in FIG. 1, the algorithm 520, based on input variables 500, and patient physiological variables 510 may determine appropriate system variables 530 to employ based on the patient's history with blood fluid sessions under the algorithm. During a blood fluid session, system variables 530 may be changed and the patient physiological response may be monitored in response to the changed system variables. If one or more of the patient's physiological variables 510 improve, the algorithm 530 can associate the changed system variables 530 with the improved patient outcome so that the changed system variables 530 may be used later in the session or in a future session when the patient has a similar set of physiological variables 510. If one or more of the patient's physiological variables 510 worsen, the algorithm 530 can associate the changed system variables 530 with a worsened patient outcome so that the changed system variables 530 may be avoided later in the session or in a future session when the patient has a similar set of physiological variables 510.

In embodiments, the input variables 500 include patient physiological variables that have occurred in a time period preceding a blood fluid removal session. For example, the time period may be a period of time (e.g., all or one or more portions of time) since the patient's last session. In embodiments, the input variables include input indicating (i) how long favorable patient variables 510 (e.g., above or below a predetermined threshold) were observed after the last session; (ii) the rate of change of patient variables 510 following the last session, (iii) etc., all of which may be compared against system parameters 530 used in the previous session. If the patient physiological 510 or other variables (e.g. patient input regarding how the patient has felt), were favorable since the last session, the system may employ similar variables in future sessions. It may also or alternatively be desirable to monitor patient physiological or other variables in a time period leading up to a session and input such variables into the algorithm 520 or system before the session. The system or algorithm 520 can then determine whether the patient has presented with similar symptoms or parameters in previous sessions and employ system variables 530 to which the patient responded favorably, either in the session, after the session, or both in the session and after the session. Accordingly, the system or algorithm 520 may monitor patient well-being, which may be derived from patient physiological variable 510 or input variables 500, within a session and between sessions to determine which system variables should be employed and changed based on the patient response to previous sessions. As indicated by the dashed lines and arrows in FIG. 1, patient physiological variables 510 obtained between sessions and system variables 530 used in a prior session may be input variables 500 in a current or upcoming session.

In embodiments, the physiological variables 510 are monitored by sensors that feed data regarding the variables directly into the algorithm 520 or electronics running the algorithm. The sensors may monitor fluid volume in the patient's blood; fluid volume in the patient's tissue; concentrations of electrolytes in the patient's blood; pH of the patient's blood; one or more cardiovascular parameter of the patient, such as blood pressure, heart rhythm, heart rate; or combinations or indicators thereof. The sensors may monitor the patient physiological parameters before, during or after a blood fluid removal session.

Any suitable sensor may be employed. Examples of sensors and systems that may be employed with regard to blood fluid volumes and tissue fluid volumes are discussed in U.S. Provisional Patent Application No. 61/480,528, filed on Apr. 29, 2011, entitled FLUID VOLUME MONITORING FOR PATIENTS WITH RENAL DISEASE; and U.S. Provisional Patent Application No. 61/480,530, filed on Apr. 29, 2011, entitled MONITORING FLUID VOLUME FOR PATIENTS WITH RENAL DISEASE, which applications are hereby incorporated herein by reference in their respective entireties to the extent that they do not conflict with the present disclosure. Sensors for monitoring tissue fluid volume, blood fluid volume, fluid flow or volume diverted from blood and the like typically monitor fluid indirectly, and directly monitor an indicator of fluid volume, flow or the like. For example, a sensor may indirectly monitor hematocrit (the portion of the blood volume that is occupied by red blood cells). Any suitable hematocrit sensor, such as a CRIT-LINE monitor from HEMA METRICS (see, HEMA METRICS, CRIT-LINE hematocrit accuracy, Vol. 1, Techn Note No. 11 (Rev. D) Feb. 24, 2003), may be used and may serve as an indicator of blood fluid volume. A sensor configured to monitor hemoglobin levels may also be used as an indicator of blood fluid volume, as hemoglobin concentration is typically proportional to red blood cell concentration. Thus, lower the hemoglobin concentrations may be indicative of higher blood fluid volume. Any suitable sensor may be used to measure hemoglobin concentration, such as sensors used in pulse oximeters which measure adsorption of red and infrared light to determine concentration of oxygenated hemoglobin and deoxyhemoglobin, respectfully. The sensors (which may include the associated light source(s)) may be placed in any suitable location, such as around tubing that carries blood from the patient to the blood fluid removal device or from the blood fluid removal device to the patient, within the blood fluid removal device, or the like. In addition or alternatively, a sensor may be implanted in a patient and disposed about a blood vessel to measure hemoglobin levels, and thus hematocrit and blood fluid levels. By way of further example, total blood protein or albumin concentrations and blood pressure, alone or in combination, can be used to evaluate blood volume. High blood pressure combined with low hematocrit or low blood protein may indicate a higher possibility of blood fluid overloading. Alternatively or additionally, blood viscosity may be used as an indicator of blood fluid volume and may be measured by pressure or flow. Impedance, capacitance, or dialectic constant sensors may be employed to monitor fluid volume. For example, impedance may be monitored between two electrodes. The electrodes may be operably coupled to control and processing electronics via leads. The electronics are configured to generate a voltage differential between the electrodes, current may be measured, and impedance calculated. The measurement may be done in either DC or AC mode. Impedance or phase angle may be correlated to tissue fluid volume. Tissue impedance sensing for purposes of monitoring tissue fluid volume has been well documented. One example of a well studied system that may be used or modified for use herein is Medtronic, Inc.'s OptiVol® fluid status monitoring system. Such a system, or other similar systems, have well-documented procedures for determining acceptable ranges of tissue impedance and thus fluid volume. See, e.g., (i) Siegenthalar, et al. Journal of Clinical Monitoring and Computing (2010): 24:449-451, and (ii) Wang, Am. J. Cardiology, 99 (Suppl):3G-1-G, May 21, 2007. Alternatively or in addition, tissue impedance may be monitored for a suitable period of time to establish as suitable baseline, and patient markers or clinician input may be used to instruct whether the patient is fluid overloaded or under-loaded. The data acquired by impedance sensor and input data regarding fluid status of the patient at the time the sensor data is acquired may be used to establish suitable ranges for impedance values.

Examples of sensors and systems for monitoring pH and electrolyte concentration are disclosed in U.S. Provisional Patent Application No. 61/480,532, filed on Apr. 29, 2011, entitled ELECTROLYTE AND pH MONITORING FOR FLUID REMOVAL PROCESSES, which application is hereby incorporated herein by reference in its entirety to the extent that it does not conflict with the present disclosure. Of course, any suitable sensor or systems for monitoring pH and electrolyte concentration may be used. For example, a transducer may be employed to detect pH or electrolytes. Suitable transducers may include an ion selective electrode configured to detect H⁺ ions, K⁺ ions, Na⁺ ions, Ca²⁺ ions, Cl⁻ ions, phosphate ions, magnesium ions, acetate ions, amino acids ions, or the like. Such electrodes, and components of sensors employing such electrodes, are known in the art and may be employed, or modified to be employed, for use in the monitoring described herein. One or more sensors may be employed to detect one or more ions to gauge pH or electrolytes in the blood. In some embodiments, a sensor may have more than one transducer, even if leadless, that may monitor more than one ionic species. By measuring more than one ionic species, a more detailed understanding of the levels of various electrolytes or blood components may be had. For example, in some patients in some situations, one electrolyte may be at elevated levels while another may be at reduced levels. In some embodiments, more than one sensor for the same ion is employed for purposes of result confirmation and redundancy, which can improve reliability and accuracy. In some embodiments, sensors for the same ion may be configured to accurately detect different ranges of concentrations of the ion. In embodiments, more than one transducer is present in a single unit. This allows for convenient data collection and circuitry, as all the data may be collected in one place at the same time. Further, the multiple transducers may share the same fluid collection mechanism (e.g., a microdialyzer in the case of an implant), and if needed or desired, may share the same data processing and memory storage components. A sensor (or transducer) for detecting pH, electrolyte concentration, or the like may be placed at any suitable location for purposes of monitoring electrolytes or pH. For example, the sensor may be implanted in the patient, located external to the patient an upstream of a blood fluid removal device, located external to the patient and downstream of the blood fluid removal device, or the like.

Examples of sensors and systems for monitoring cardiovascular parameters are disclosed in U.S. Provisional Patent Application No. 61/480,535, filed on Apr. 29, 2011, entitled CARDIOVASCULAR MONITORING FOR FLUID REMOVAL PROCESSES, which application is hereby incorporated herein by reference in its entirety to the extent that it does not conflict with the present disclosure. Of course, any suitable sensor for monitoring cardiovascular parameters may be used. In embodiments, pH or electrolyte sensors; e.g., as described above, may be used to monitor cardiovascular parameters. Sensors for monitoring heart rate or heart rhythm may be used. One suitable implantable sensor device that is configured to monitor a patient's ECG signals is a Medtronic, Inc.'s Reveal® series insertable cardiac monitor. In embodiments, the sensor device may be a suitably equipped pacemaker or defibrillator already implanted in the patient. Monitored cardiac signals from such a device may be transmitted to a blood fluid removal device or intermediate device for use in the blood fluid removal session or for setting the prescription for the blood fluid removal session. Blood pressure monitors, which may be external or implantable (such as Medtronic Inc.'s active leadless pressure sensor (ALPS), which generally takes the form of a stent to anchor the device within a vessel, may be employed. Such a device may be placed in any suitable blood vessel location, such as in a femoral artery or pulmonary artery. A wearable sensor system, such as a Holter sensor system, may be used to monitor ECG activity of the patient. Regardless of whether the sensor or sensor system employed, or components thereof, is implantable, wearable, part of a larger stand-alone device, or part of a blood fluid monitoring device, the sensor may monitor any suitable cardiovascular parameter of a patient. In various embodiments, the sensors or monitoring systems are configured to monitor one or more of heart rate, heart rhythm or a variable thereof, or blood pressure. Examples of variables of heart rhythm that may be measured are heart rate variability (HRV), heart rate turbulence (HRT), T-wave alternans (TWA), P-wave dispersion, T-wave dispersion, Q-T interval, ventricular premature depolarization (VPD), or the like.

As indicated above, sensors for monitoring patient physiological parameters may be, or may have components that are, implantable or wearable. In embodiments, multiple sensors may be connected via telemetry, body bus, or the like. The connected sensors may be of the same or different type (e.g., pH or impedance). Such connected sensors may be placed (e.g., internal or external) for purposes of monitoring at various locations of the patient's body.

Monitoring may occur during a blood removal session or between blood removal sessions. In embodiments, blood fluid removal is chronically performed, such as when a blood fluid removal device or a component thereof is wearable or implantable, and monitoring is chronically performed. Chronic monitoring in association with blood fluid removal is described in U.S. Provisional Patent Application No. 61/480,544, filed on Apr. 29, 2011, entitled CHRONIC pH OR ELECTROLYTE MONITORING, which application is hereby incorporated herein by reference in its entirety to the extent that it does not conflict with the present disclosure.

Monitoring may alternatively or additionally include receiving patient or physician feedback regarding the patient's state. For example, the patient may indicate a point in time when cramping begins, which often happens when too much fluid is removed. The blood fluid monitoring device may include an input, such as a keyboard or touch screen display for entering such data. Alternatively, a separate device such as a patient programmer, laptop computer, tablet computer, personal data assistance, smart phone or the like may be used to input the data; or the like.

Any suitable system variable 530 may be adjusted. FIGS. 10-15, and the associated text below, describe some suitable blood fluid removal systems and variables that may be adjusted. In many cases, fluid removal rate, blood flow rate, or concentration of electrolyte or composition of pH buffer in replacement fluid or dialysate may be adjusted. It may be desirable to monitor blood fluid removal system parameters to ensure that the system is performing in an expected manner. For example, it may be desirable to monitor fluid rate removal rather than merely adjusting a system variable related to fluid removal rate to ensure that the adjusted system variable actually adjusted the fluid removal rate in the expected manner. Any suitable system and method may be employed to monitor such system performance.

Examples of systems and methods for monitoring system performance are described in U.S. Provisional Patent Application No. 61/480,541, filed on Apr. 29, 2011, entitled BLOOD FLUID REMOVAL SYSTEM PERFORMANCE MONITORING, which application is hereby incorporated herein by reference in its entirety to the extent that it does not conflict with the present disclosure. For example, flow sensors such as an acoustic Doppler velocimeter, an optical flow meter, a thermal flow meter, a Venturi meter, in-fluid paddle type meter, or the like may be used upstream or downstream of blood fluid removal device to monitor system performance. Sensors configured to monitor an indicator of a compound in blood or in fluid removed from the blood may be used to monitor system performance. The sensors may be configured to monitor components of blood that are configured to be removed during some blood fluid removal processes, such as hemodialysis. Examples of such compounds include urea, creatinine, sulfate, phosphate, β-2-microglobulin, or the like. Sensors capable of measuring such compounds are known in the art and can be readily adapted for used herein. For example, Nova Biomedical manufactures a variety of sensors capable of detecting components in blood such as creatinine, phosphate, urea and the like, which sensors can be employed or adapted for use herein. Other urea sensor detection technology that may be employed or adapted for used herein is described by Zhong et al., Clin. J. Biotechnol. 1992; 8(1):57-65. β-2-microglobulin sensor detection technology that may be employed or adapted for used herein is described by Brynda et al., Biosens Bioelectron. 1999; 14(4):363-8 and by Nedelkov et al., Proteomics. 2002; 2(4):441-6. Of course, any suitable sensor technology may be employed. By way of further example, pressure sensors may be employed to monitor pressure differential across a blood fluid removal membrane to monitor system performance.

Referring now to FIG. 2, a high level flow diagram of a method is described. The method includes providing input (600), such as input variables discussed above with regard to FIG. 1, to a blood fluid removal system. The method also includes initiating or starting (700) a blood fluid removal session, and learning (800) from the session. The learning (800) may be as discussed above with regard to FIG. 1 with system parameters being varied and patient physiological parameters being monitored to determine which system parameter adjustments result in desirable patient physiologic outcomes. The learning may also occur over multiple sessions by monitoring patient variables within the sessions or by monitoring patient variables between sessions to determine how well the patient responded prior sessions to predict how well a patient will respond to future sessions (or to set initial parameters for future sessions based on prior experiences).

For example and with reference to FIG. 3A, additional detail regarding an embodiment of a learning process that may occur during a blood fluid removal session is shown. The blood fluid removal session is started (700) and the patient is monitored (810). Monitored patient parameters, such as patient physiological variables as discussed above, are stored (820); e.g., in memory of the blood fluid removal system. The system parameters, such as system variables described above, which may include rate of fluid removal from the blood or electrolyte concentration of a dialysate or replacement fluid, are adjusted (830) and the system parameters are stored (840); e.g., in memory of the blood fluid removal system, and patient monitoring (810) continues. The set of stored patient parameters (820) are associated (850A) with a set of stored system parameters (840) so that the system may recall particular system parameters that were employed at the time the patient had a given set of parameters. The data regarding the stored patient parameters (820) and the stored system parameters (840) may be tagged with, for example, a time event to associate the two sets of data. Of course any other suitable method or mechanism for associating the data sets may be employed. In some embodiments, the associated data, or a portion thereof, is placed in a lookup table tracking the patient's history of physiological response to changing system parameters (860A).

Referring now to FIG. 3B, an overview of a learning process that may occur with monitoring between blood fluid removal sessions is shown. Before, during or after a blood fluid removal session is ended (899), system parameters used in the session are stored (840). The system parameters, such as system variables described above, which may include rate of fluid removal from the blood or electrolyte concentration of a dialysate or replacement fluid, as well as any adjustments made during the session that has just ended may be stored in memory and associated with the patient. During one or more time periods between the end of the session (899) and the start of the next session (700), the patient is monitored (810). Monitored patient parameters, such as patient physiological variables as discussed above, are stored (820); e.g., in memory of the blood fluid removal system or in memory of a device capable of communicating with, or a part of, the blood fluid removal system. For example, if monitoring (810), or a portion thereof, occurs via an implanted device, the implantable monitoring device may be configured to wirelessly communicate with a blood fluid removal system or a device capable of communicating with the blood fluid removal system. If monitoring includes assays or other diagnostic procedures for which data is presented to a user, such as a health care provider, the data may be entered into a blood fluid removal system or device in communication with the blood fluid removal system. The set of stored system parameters (840) are associated (850B) with a set of patient system parameters (820) so that the system may recall particular system parameters that were employed in prior sessions that resulted in a given set of patient parameters. The data regarding the stored patient parameters (820) and the stored system parameters (840) may be tagged with, for example, a time event to associate the two sets of data. Of course any other suitable method or mechanism for associating the data sets may be employed. In some embodiments, the associated data, or a portion thereof, is placed in a lookup table tracking the patient's history of physiological response to system parameters (860B). Depending on the patient's response (patient monitoring 810) to the prior sessions, the system parameters may be adjusted (830) prior to beginning the next session (700). The patient's responses between sessions may also affect changes made during a session.

Referring now to FIG. 3C, an overview of a learning process that accounts for both inter-session and intra-session patient monitoring is shown. The process depicted in FIG. 3C is mainly a composite of the processes depicted and described above with regard to FIGS. 3A-B. As depicted in FIG. 3C, the process or algorithm may include associating (850A) system parameters (840), and adjustments thereof (830), that result in good or bad outcomes with regard to patient parameters (820) and may recall those associations for later use, e.g. in the form of a lookup table (860A) for purposes of making future adjustments to system parameters (830) based on patient response (810) within a session. Prior patient responses occurring between prior sessions (i.e., between end of session 899 and beginning of session 700) may also be taken into account (e.g., associated parameters (850B) that include patient parameters obtained between sessions) by, for example, referring to lookup table 860B. If, for example, changes in systems parameters (830) within a session are associated with good (effective) or bad (ineffective) patient responses (810) between sessions, similar changes may be made or avoided, as relevant, within a session. In addition, the patient response (810) to a prior session or the patient's condition (810) before a session may warrant adjustment of system parameters (830) prior to beginning a session (700). The patient response (810) within prior sessions may also be taken into account (e.g., by reference to history table 860A) in making system adjustments prior to beginning a session.

A more detailed embodiment of a within-session learning algorithm, or method is presented in FIG. 4A. In the embodiment depicted in FIG. 4A, patient is monitored (810) during a blood fluid removal session. It may be desirable to determine whether data acquired from patient monitoring is out of range (813). As used herein, “out of range” means that a value of a monitored parameter exceeds (ie., is above or below) a predetermined range of values. The predetermined range of values may be indicative of a patient safety concern. If the data is out of range, an alert may be issued (815) or the session may be stopped (817). In some cases, it may be desirable to continue with the session, even if the monitored data, or some aspect thereof is out of range. In the depicted embodiment, if the session is continued, (e.g., due to choice or to the monitored data not being out of range), data regarding the monitored patient parameters is stored (820) and is compared to stored patient data previously obtained (e.g., in a prior session or earlier in the session). A determination may be made as to whether the present patient parameter data is less effective (823) than stored patient parameter data resulting from system parameter adjustments (830) that occurred just prior to the current set of system parameters. If the data is determined to be less effective (823), the stored current patient parameters (820) may be associated (851) with stored current system parameters (840); e.g., as discussed above. In some cases, it may be desirable to determine whether the current patient parameter data, or a portion or aspect thereof, is the least effective that has been detected in the patient in a current or previous blood fluid removal session (825); e.g. by comparing the current patient data to a history of collected patient data. If the current patient data is the least effective observed (825) to date, the stored current patient parameters (820) may be associated (851) with stored current system parameters (840). In this way, only the “least effective” patient conditions are tracked, as opposed to all patient conditions, which can save on memory and processing power. In any case, once the patient and system parameter data is associated (851), the system parameters may be adjusted (830) and the process repeated.

If the present patient parameter data is determined to not be less effective than stored patient parameter data resulting from system parameter adjustments that occurred just prior to the current set of system parameters, a determination may be made as to whether the present patient parameter data is more effective (833) than stored patient parameter data resulting from system parameter adjustments (830) that occurred just prior to the current set of system parameters. If the data is determined to be more effective (833), the stored current patient parameters (820) may be associated (852) with stored current system parameters (840); e.g., as discussed above. In some cases, it may be desirable to determine whether the current patient parameter data, or a portion or aspect thereof, is the most effective that has been detected in the patient in a current or previous blood fluid removal session (835); e.g. by comparing the current patient data to a history of collected patient data (e.g., “history table” in FIG. 3). If the current patient data is the most effective observed (835) to date, the stored current patient parameters (820) may be associated (852) with stored current system parameters (840). In this way, only the “most effective” patient conditions are tracked, as opposed to all patient conditions, which can save on memory and processing power. In any case, once the patient and system parameter data is associated (852), the system parameters may be adjusted (830) and the process repeated.

A more detailed embodiment of a between-session learning algorithm, or method is presented in FIG. 4B. In the embodiment depicted in FIG. 4B, patient is monitored (810) between a blood fluid removal sessions. It may be desirable to determine whether data acquired from patient monitoring (810) is out of range (813). If the data is out of range, an alert may be issued (815) prompting the patient to seek medical attention or prompting a health care or an implanted system or device to take action. In some cases, a new session may be begun (700) if patient conditions warrant. If a new session is not initiated, the inter-session process may continue. In the depicted embodiment, if the process is continued, data regarding the monitored patient parameters is stored (820) and is compared to stored patient data previously obtained (e.g., between prior sessions). A determination may be made as to whether the present patient parameter data is less effective (823) than stored patient parameter data obtained between previous sessions. If the data is determined to be less effective (823), the stored current patient parameters (820) may be associated (851) with stored system parameters (840) from the previous session that had ended (899). In some cases, it may be desirable to determine whether the current patient parameter data, or a portion or aspect thereof, is the least effective that has been detected in the patient between blood fluid removal sessions (825); e.g. by comparing the current patient data to a history of collected patient data. If the current patient data is the least effective observed (825) to date, the stored current patient parameters (820) may be associated (851) with stored system parameters (840) from the previous session that had ended (899). In this way, only the “least effective” patient conditions are tracked, as opposed to all patient conditions, which can save on memory and processing power. In any case, once the patient and system parameter data is associated (851), a recommendation as to system parameters to be used in the next session may be made (e.g., the system parameters for the future session may be set 830 based on the patient response or prior patient responses) may be adjusted (830) and the process repeated until the next session begins 700.

If the present patient parameter data is determined to not be less effective than stored patient parameter data obtained from time periods between prior sessions, a determination may be made as to whether the present patient parameter data is more effective (833) than stored patient parameter data obtained from between prior sessions. If the data is determined to be more effective (833), the stored current patient parameters (820) may be associated (852) with stored current parameters (840) from the previous session that had ended (899). In some cases, it may be desirable to determine whether the current patient parameter data, or a portion or aspect thereof, is the most effective that has been detected in the patient in a time between sessions (835); e.g. by comparing the current patient data to a history of collected patient data (e.g., “history table” in FIG. 3). If the current patient data is the most effective observed (835) to date, the stored current patient parameters (820) may be associated (852) with stored system parameters (840) from the previous session that had ended (899). In this way, only the “most effective” patient conditions are tracked, as opposed to all patient conditions, which can save on memory and processing power. In any case, once the patient and system parameter data is associated (852), recommendation system parameters may set (830) based on the patient response or prior patient responses, and the process repeated until the next session begins 700.

It will be understood that the processes or algorithms depicted in, and discussed above with regard to, FIGS. 4A-B may be combined (e.g., in a manner similar to the combination of FIGS. 3A and 3B into FIG. 3C). In this way, setting of system parameters for an upcoming session may take into account how a patient responded to such parameters within prior sessions, or altering of system parameters within a session may take into account how a patient responded to such alterations between prior sessions.

Referring now to FIG. 5A, an embodiment of a method where more than one patient parameter variable is evaluated in a manner similar to that described with regard to FIG. 4A. In the embodiment depicted in FIG. 5A, two patient parameter variables are evaluated. However, it will be understood that any number of patient parameter variables may be evaluated by employing a method as depicted in FIG. 5A or using any other suitable method. In the embodiment depicted in FIG. 5A, the variables are labeled “primary” and “secondary”, as it may be desirable to prioritize patient parameter variables. For example, in some cases it may be desirable to monitor blood pressure and attempt to achieve a stable blood pressure at or near a target range throughout the session because hypotension is one of the most common side effects of blood fluid removal sessions. That is, as long as other patient parameters are not out of a pre-determined range, the system may attempt to keep blood pressure in check and make adjustments to that end. However, in some cases, reducing arrhythmias is the primary goal, as many patients for which a blood fluid removal process is indicated dire from complications due to arrhythmias. If arrhythmias are determined to be the primary patient parameter, the blood fluid removal system may attempt to keep arrhythmias in check and make adjustments to this effect without regard to other patient parameters, e.g., as long as the other patient parameters remain within acceptable limits.

The method depicted FIG. 5A includes monitoring patient parameters (810) (at least a primary and secondary patient parameter), storing patient parameter data (820), and determining whether a parameter, or aspect thereof, is out of a predetermined range (813). If the parameter is out of range, an alert may be issued (815), the blood fluid removal session may be stopped (817) or the session may continue. If the parameters are determined to not be out of range (813), the system parameters may be adjusted (843) and stored (840). A determination may then be made as to whether the primary patient parameter is less effective (843), e.g. by comparing current patient parameter data to stored patient parameter data resulting from system parameter adjustments that occurred just prior to the current set of system parameters. If the primary patient parameter is determined to be less effective (843), the current stored patient parameter data may be associated (853) with the current stored system parameters. Alternatively or in addition, a determination may be made as to whether the current patient parameter data regarding the primary parameter is the least effective that has been detected in the patient in a current or previous blood fluid removal session (845); e.g., as discussed above with regard to FIG. 4A. If it is the least effective, the current stored patient parameter data may be associated (853) with the current stored system parameters as described above with regard to FIG. 4A. Similarly determinations as to whether the primary patent parameter data is more effective (853) or the most effective to date (855) may be made and stored system and patient parameters may be associated (854). Similar determinations regarding whether the secondary patient parameter, or a value associated therewith, is less effective (863), the least effective (865), more effective (873), the most effective (875) and appropriate associations (855, 856) may be made. In this manner, the system may identify and learn how system parameters may affect individually monitored patient parameters, such as blood pressure, heart rate, fluid volume, and electrolyte concentration. Based on this information, the system may make choices as to which system parameters may be employed to produce results that are likely to be favorable to the patient.

Referring now to FIG. 5B, an embodiment of a method where more than one patient parameter variable is evaluated between blood fluid removal sessions in a manner similar to that described with regard to FIG. 4B. In the embodiment depicted in FIG. 5B, two patient parameter variables are evaluated. However, it will be understood that any number of patient parameter variables may be evaluated by employing a method as depicted in FIG. 5B or using any other suitable method. In the embodiment depicted in FIG. 5B, the variables are labeled “1°” and “2°”. However, such labeling does not necessarily imply that one variable is more important than another. While one variable may, in some circumstances be considered more important, the labeling of “primary” and “secondary” may merely imply that the variables being monitored and tracked are different from one another.

The method depicted FIG. 5B includes ending a blood fluid removal session (899) and storing system parameters (840) from the ended session, which may be done during the session or after the session has ended (as depicted). The method also includes monitoring patient parameters (810) (at least a primary and secondary patient parameter), storing patient parameter data (820), and determining whether a parameter, or aspect thereof, is out of a predetermined range (813). If the parameter is out of range, an alert may be issued (815), prompting the patient to seek medical attention or prompting a healthcare provider or system or device to take action. In some cases, a blood fluid removal process may be initiated (700), e.g. if warranted or desired. If the parameters are determined to not be out of range (813) or if a blood fluid session is not initiated, a determination may be made as to whether the primary patient parameter is less effective (843), e.g. by comparing current patient parameter data to stored patient parameter data resulting from system parameters used in the previous session. If the primary patient parameter is determined to be less effective (843), the current stored patient parameter data may be associated (853) with the stored system parameters from the previous session. Alternatively or in addition, a determination may be made as to whether the current patient parameter data regarding the primary parameter is the least effective that has been detected in the patient between blood fluid removal sessions (845); e.g., as discussed above with regard to FIG. 4B. If it is the least effective, the current stored patient parameter data may be associated (853) with the stored system parameters as described above with regard to FIG. 4B. Similarly determinations as to whether the primary patent parameter data is more effective (853) or the most effective to date (855) may be made and stored system and patient parameters may be associated (854). Similar determinations regarding whether the secondary patient parameter, or a value associated therewith, is less effective (863), the least effective (865), more effective (873), the most effective (875) and appropriate associations (855, 856) may be made. In this manner, the system may identify and learn how system parameters employed in previous sessions may affect individually monitored patient parameters, such as blood pressure, heart rate, fluid volume, and electrolyte concentration. Based on this information, the system may make choices as to which system parameters may be employed in future sessions to produce results that are likely to be favorable to the patient.

As depicted in FIG. 5B, recommended system parameters may be set (830) based on how the patient responded to the prior session or the patient's condition prior to the upcoming session. The recommended system parameters may be adjusted or set (830) more than once during the process of monitoring the patient between sessions or at the end of the inter-session monitoring before initiating the next blood fluid removal session (700).

It will be understood that the processes or algorithms depicted in, and discussed above with regard to, FIGS. 5A-B may be combined (e.g., in a manner similar to the combination of FIGS. 3A and 3B into FIG. 3C). In this way, setting of system parameters for an upcoming session may take into account how a patient responded to such parameters within prior sessions, or altering of system parameters within a session may take into account how a patient responded to such alterations between prior sessions.

Referring now to FIG. 6A, a flow diagram depicting a process where the combined response of two or more patient parameters to changes in system parameters (830) is tracked within a session. For the purposes of convenience some of the steps depicted and described above with regard to FIGS. 4A and 5A are omitted from FIG. 6A. However, it will be understood that the same or similar steps may be employed with regard to the method depicted in FIG. 6A. In the depicted embodiment, patient parameters and system parameters are stored (857, 858) only when both the primary and secondary patient parameters are determined to become less effective (843, 863) or more effective (853,873). In this manner, the system may identify or learn which system parameters result in desirable (or undesirable) changes in multiple patient parameters.

Referring now to FIG. 6B, a flow diagram depicting a process where the combined response of two or more patient parameters to changes in system parameters (830) is tracked between sessions. For the purposes of convenience some of the steps depicted and described above with regard to FIGS. 4B and 5B are omitted from FIG. 6B. However, it will be understood that the same or similar steps may be employed with regard to the method depicted in FIG. 6B. In the depicted embodiment, patient parameters are stored (857, 858) only when both the primary and secondary patient parameters are determined to become less effective (843, 863) or more effective (853,873) and may be associated with stored system parameters (840) for the previously ended session (899). In this manner, the system may identify or learn which system parameters result in desirable (or undesirable) changes in multiple patient parameters.

Through the association of patient parameter data and system parameter data as shown in FIGS. 3-6 and discussed above, a history of patient responses, within sessions or between sessions, to changing system parameters may be obtained. This history, which may be in the form of one or more lookup table, may be consulted prior to or during a blood fluid removal session to determine which system parameters, given the patient's physiological parameters at a given point in time, are more likely to cause the patient to respond favorably and which system parameters are more likely to cause the patient to respond negatively. Accordingly, the system may respond by adjusting or setting parameters to those that are more likely to cause the patient to respond favorably.

For example and with reference to FIG. 7, a flow diagram is shown that depicts and embodiment of how stored and associated data (e.g., as discussed above with regard to FIGS. 3-6) may be used to determine which system parameters to use at a given time in or before a blood fluid removal session. The method includes monitoring patient parameters (810), within a blood fluid removal session or between sessions, and consulting history lookup table (880), which may be generated by associating system parameters and patient parameters as described above with regard to FIGS. 3-6. Monitoring the patient (810) may include monitoring physiological variables or receiving input from the patient, a healthcare provider, or the like. A value associated with the current patient parameter data (obtained from monitoring 810) is compared to data regarding a corresponding value in the lookup table, and a determination is made as to whether the current patient parameter is similar to prior patient parameter data stored in the history table (882). By way of example, a value of a current patient parameter data set may be determined to be similar to a corresponding value in the lookup table if the values are within 10%. The system may consult the lookup table to identify the closest corresponding value, if more than one corresponding value is within the predetermined cutoff for being considered similar (e.g., within 10%). As used herein, a “corresponding” value is a value of the same parameter obtained at different times. The value may be a magnitude, a rate of change, an average, or the like. The parameter may be blood pressure, heart rate, fluid volume, concentration of electrolyte, or the like.

If more than one parameter or value of a parameter is compared to data in the lookup table, the system may determine whether each value for each parameter is within the predetermined cutoff for being considered similar and identify a prior patient parameter data set as being most similar by prioritizing or weighting parameters or by summing the percent differences between all of the current values and the corresponding values in the lookup table. Regardless of how the system determines whether a current patient parameter data set is similar, or most similar, to a prior patient data set stored in the history table, a determination may be made as to whether the patient's response to the system parameters associated with the stored patient parameter data table was a favorable response (884); e.g., was “more effective” or “most effective” as discussed above with regard to FIGS. 4-6. If the prior patient response was determined to be a good response, the system parameters may be set or adjusted according to the parameters stored in the lookup table (892). If the prior patient response was considered to not to be similar (882) or good (884), a default table may be consulted (888) which contains non-patient specific system parameters that would generally be considered suitable in general circumstances or that would be considered suitable for a patient presenting with the current physiological parameters. The system parameters may then be set or adjusted according to the parameters stored in the default table (890).

It will be understood that prior patient negative responses (e.g., “less effective”, “least effective to date”) may be stored in a lookup table, accessed and used in a similar manner to that described with regard to the “good” responses in FIG. 7. In some embodiments, separate lookup tables are maintained for “more effective” responses (e.g., an “increased effectiveness” data table) and for “less effective responses” (e.g., a “decreased effectiveness” data table). In some embodiments, the “increased effectiveness” lookup table and the “decreased effectiveness” lookup table are the same data table, which stores patient parameters and associated system parameters that resulted in “more effective”, “most effective”, “less effective” or “least effective” patient parameters. As discussed above, lookup tables may include information regarding patient data obtained within a session or between sessions.

For purposes of example and to provide some clarity with regard to how one (or a blood fluid removal system) may determine whether patient parameter data is “out of range”, “more effective”, “less effective”, and the like (e.g., as discussed above with regard to FIGS. 4-6), graphical schematic data is presented in FIG. 8 showing representations of monitored data (not actual data) for blood pressure (BP), heart rate (HR), and potassium concentration in the patient's blood ([K⁺]). In the schematic illustration, a blood fluid removal session is initiated at T1 and is ended at T4. System parameters are changed at times T2 and T3. The patient parameters (BP, HR, [K⁺]) are shown as changing in response to the changes in blood fluid removal system parameters and continuing to change after the session ends. As shown, not all patient parameters will respond similarly (e.g., more effective or less effective) in response to a system parameter change or session. In the depicted schematic illustrations, a desired target value is shown for each patient parameter. If the monitored data value achieves or approaches the target, a determination may be made that the change in system parameter or an overall session resulted in an increased effectiveness or “more effective” state for that parameter. If the monitored data value deviates from the target, a determination may be made that the change in system parameter or overall session parameters resulted in a decreased effectiveness or “less effective” state for that parameter. It will be understood that the timing of the patient parameter response to a change in system parameters may vary greatly from patient parameter to patient parameter. In some cases, changes in a patient parameter may be observed within seconds or minutes of a change in a system parameter. In other cases, a change in a patient parameter in response to a change in a system parameter may take hours or more to be fully appreciated or observed.

In the graphical depictions of the represented monitored data presented in FIG. 8, a lower threshold value and an upper threshold value are depicted by horizontal dashed lines. If the monitored data for a patient parameter exceeds the upper threshold value or crosses below the lower threshold value, a determination may be made that the value for that parameter is “out of range.”

It will be understood that the condition of a patient may deteriorate with time, which is typical of patients having chronic kidney disease. Accordingly, the targets and upper and lower thresholds may vary with time. These targets and thresholds may be modified by input from, for example, a healthcare provider from time to time based on, e.g., the patient's health or status of patient parameters. Alternatively, the system may automatically adjust target or threshold values over time based on population data or based on data of a particular patient indicative of a generally deteriorating condition. If the target or thresholds are adjusted to or near predetermined cutoff values, an alert may be issued to that effect.

Further, target and threshold values for one or more parameters may be modified on a session-by-session basis. For example, if the patient is excessively fluid overloaded prior to a given session, the target or threshold tissue fluid levels may be adjusted upward for the next or current session. The negative consequences of too much fluid removal in one session or at too fast of a rate may outweigh the negative consequences of higher fluid levels remaining in the patient. Additional or more frequent fluid removal sessions may be employed to return the patient to more desirable fluid levels.

As shown in the examples presented in FIG. 8, the patient parameters change over time. In embodiments, values of one or more patient parameters are averaged over a period of time to account for fluctuations that may occur. The averaged value may be compared to the target and thresholds for determining whether a patient is improving. By averaging values over time, the effect of an anomalous value that may deviate significantly from the target value or may be out of bounds may be diminished. Of course, thresholds may be set for single occurrences, for example if the values of those occurrences may present an imminent health concern to the patient. In embodiments, the presence a single occurrence that deviates significantly from other recent occurrences may result in activation of a subroutine or monitoring method for detecting similar subsequent deviations. In embodiments, consecutive significant deviations, a percent of significant deviations within a given number of samples, or the like, may result in activation or an alert or alarm.

In embodiments, patient parameters are measured or monitored within discrete windows of time rather than continuously. Such time sampling may be valuable for implantable systems or systems having implantable components as the power and processing requirements may be reduced relative to continuous monitoring.

It will be understood that the processes, and components thereof, described above with regard to FIGS. 1-7, as well as the illustrative examples presented in and described above with regard to FIG. 8, are provided for purposes of illustration and not limitation. Process steps other than those described herein, or derivations of the steps or components to carry out the steps, may be employed. Further, process steps depicted and discussed above may be interchanged, substituted, added to, or omitted from processes of alternative embodiments, as appropriate.

The processes described above may be employed with any suitable device or system for removing fluid, or fluid and contaminants, from blood. The devices, or components thereof, may be traditional large counsel-type, wearable, or implantable.

Block diagrams of some example devices and systems are shown in FIGS. 9-11. As shown in FIG. 9, blood may be removed from a patient 10 and fluid may be removed via a blood fluid removal device 100 and returned to the patient 10. Removed fluid may be diverted. In some embodiments where the blood fluid removal device 100 or system, or components thereof, are implanted, the removed fluid may be diverted to the patient's bladder. Examples of blood fluid removal devices 100 that may operate as depicted in FIG. 9 are ultrafiltration and hemofiltration devices. Examples of such devices and components thereof that may be employed in accordance with the teachings presented herein are well known in the art. With some of such devices, replacement fluid may be introduced into the patient's blood if fluid is removed from the blood by the device 100 at too great of a rate or amount. The replacement fluid may be added to the original blood before fluid removal or may be added to the blood after initial fluid removal and prior to return to the patient's cardiovascular system. Preferably, the replacement fluid is added after initial fluid removal. The pH and electrolyte concentration of the replacement fluid may be set or adjusted, e.g. as described in more detail below.

As shown in the embodiment depicted in FIG. 10, the blood fluid removal device 100 may employ dialysate to assist in removal of contaminants from the patient's blood and in maintaining proper pH and electrolyte balance. The pH or electrolyte concentration of the dialysate may be set or adjusted, e.g. as described in more detail below. Used dialysate and fluid removed from the blood may be diverted. In some embodiments, particularly where the blood fluid removal device 100 or system or components thereof are wearable or implantable, the used dialysate and removed fluid, or a portion thereof, may be regenerated (indicated by dashed lined regeneration system 150) to produce fresh dialysate for re-use in the blood fluid removal process. One system for regeneration of dialysate is the REDY system, such as described in Roberts, M, “The regenerative dialysis (REDY) sorbent system,” Nephrology 4:275-278, 1998, which system may be employed or readily modified for use in embodiments described herein. As shown in FIG. 10, a concentrate may be added to the regenerated dialysate to adjust the pH and electrolytes of the regenerated dialysate to an amount suitable for re-use as fresh dialysate.

Regardless of whether the dialysate is regenerated, systems and devices that operate in a manner shown in the embodiment of FIG. 10 include hemodialysis and hemodiafiltration systems. Examples of such devices and components thereof that may be employed in accordance with the teachings presented herein are well known in the art. It will be understood that peritoneal dialysis, where the dialysate is introduced into peritoneal cavity may also be employed.

As shown in FIG. 11, in cases where the blood fluid removal device 100 of FIG. 10 removes fluid from the blood at too high of a rate, replacement fluid may be introduced into the patient's blood, upstream or downstream of fluid removal, e.g. as described above with regard to FIG. 9.

Regardless of the device or blood fluid removal process employed, system parameters such as rate of fluid removal, blood flow rate or electrolyte or pH buffer component or concentration may be controlled. Some schematic block diagrams for controlling electrolyte or pH of a dialysate or replacement fluid (and thus of blood) are shown in FIG. 12, in which representative components of an example of a closed-loop system for adjusting pH and electrolyte concentrations of fluid are shown.

With reference to FIG. 12, input data 600 (e.g. input 600 as discussed above with regard to FIG. 2) or “learned” parameters may be presented to, or processed within, control electronics 495, which are configured to control flow control elements 415, 425, 435, such as valves. The electronically controllable flow control elements 415, 425, 435 are in fluid communication with supplies of concentrated electrolyte or buffer solutions 410, 420, 430 and with fluid line 440, which may be a catheter for carrying fresh dialysate or a catheter for carrying replacement fluid. The electronically controllable flow control elements 415, 425, 435, via control electronics 495, control the rate at which the concentrates 410, 420, 430 flow into the fluid line 440. The concentrates 410, 420, 430 are added to bulk fluid 400 to adjust the concentration of electrolytes or the pH of the bulk fluid (and thus the blood).

Any number of suitable concentrates may be used. For example, one concentrate may be sufficient with higher amounts being added when the electrolytes are determined to be low in the patient's blood, and smaller amounts being added when the electrolytes are determined to be high in the patient's blood. More than one concentrate may be used when it is desired to, for example, control pH and electrolyte concentration independently or to control concentration of different electrolytes independently.

Control elements 415, 425, 435, as depicted in FIG. 12 and discussed above, may be any suitable control element, such as electronically controllable valves, electronically controllable pump mechanisms, or the like.

Any suitable system may be configured as depicted in FIG. 12 to provide control of adjustment of pH or electrolytes based on input data 600 or “learned” parameters. By way of example, selected components of two example systems are illustrated in FIGS. 13-14.

Referring now to FIG. 13, the depicted device 100 includes a fluid pathway for adding replacement fluid to blood before it is returned to the patient. The device 100 includes an inlet 110 for receiving blood from the patient and an outlet 140 for returning blood to the patient. In the flow path between the inlet 110 and outlet 140 are a blood flow control element 120 and a medium for removing fluid and contaminants from the blood. The blood flow control element 120 is operably coupled to control electronics 150 which provide instructions to control the rate at which blood is passed through medium 130. Fluids and contaminants removed from the blood by the medium 130 may exit via outlet 180.

The device 100 depicted in FIG. 13 also includes an inlet 197 for receiving bulk replacement fluid and a replacement fluid flow control element 195 in communication with the inlet and configured to control the rate at which the replacement fluid is added to the blood. The control electronics 150 are operably coupled to the replacement fluid flow control element 195 and are configured to control the rate at which replacement fluid flow control element 195 adds fluid to the blood. The device 100 also includes (i) an inlet 401 for receiving a concentrate for adjusting the pH or electrolyte concentration of the bulk replacement fluid, and (ii) a concentrate flow control element 415 in communication with the inlet 401 and configured to control the rate at which the concentrate is added to the replacement fluid or blood before the blood is returned to the patient. Preferably, the concentrate is added to the replacement fluid prior to the replacement fluid being added to the blood (as depicted) so that the concentrate may be mixed or diluted prior to being added to the blood. The device may include a mixer (not shown) to mix the concentrate and bulk replacement fluid prior to adding to the blood.

In the device depicted in FIG. 13, the control electronics 150 are operably coupled to the concentrate flow control element 415 and are configured to control the rate at which the concentrate flow control element 415 adds fluid to the replacement fluid or blood. By controlling the rate at which the concentrate is introduced into replacement fluid or blood, the concentration or pH (or buffering capacity) of the returned blood can be controlled.

Referring now to FIG. 14, in which components that are numbered the same as in FIG. 13 refer to the same or similar components, a schematic block diagram of selected components of a blood fluid removal device 100 is shown. In the embodiment depicted in FIG. 14, the device has in inlet 110 for receiving blood from a patient, a blood flow control element 120 in communication with the inlet 110 and configured to control the rate at which blood flows through medium 130 for removing fluid and contaminates from the blood. The device also includes an outlet 140 in communication with the medium 130 for returning blood to the patient. In the depicted embodiment, the medium 130 includes a semipermeable filter 135, such as a hemodialysis or hemodiafiltration filter. The membrane separates a blood flow compartment from a dialysis flow compartment of the medium component 130.

In the embodiment depicted in FIG. 14, used dialysate is regenerated by passing through dialysate regeneration medium 402 or components, such REDY regeneration medium and components, or the like, to regenerate bulk dialysate. The device also has an outlet 180 in communication with the medium 130 for diverting fluid removed from the blood out of the device. A flow regulator element 700, such as a valve, is operably coupled to control electronics 150 and is disposed in the flow path between the medium 130 and the outlet 180 to control the amount of fluid that exits the device (as a portion of the fluid is regenerated). Often, the regeneration media or components (402) remove much of the pH buffer or electrolytes from the dialysate. Accordingly, a concentrate containing concentrated electrolytes and pH buffers is added to the regenerated dialysate before the dialysate re-enters the medium 130. In some embodiments, a sensor 299 is positioned downstream of the regeneration medium 402 to monitor a level of a component of the regenerated dialysate. The sensor 299 may be a pH or electrolyte sensor and data acquired from sensor 299 may be used in determining how much concentrate to add to the regenerated fluid (which data may be provided to control electronics 150). The sensor 299 may be a sensor that monitors a blood waste product, such as urea, to determine whether the regeneration media 402 is properly functioning. Increased or detectable levels of a waste product may indicate that the regeneration media 402 or components may need replacement or regeneration.

In the depicted embodiment, the concentrate 410 is stored in a reservoir 410, having an inlet 401 that allows the concentrate supply in the reservoir 410 to be replenished from time to time. The rate at which the concentrate is added to the regenerated dialysate is controlled by concentrate flow control element 415, which is operably coupled to control electronics 150, and may be based on input data 600 or “learned” parameters as described above.

The device 100 in FIG. 14 also has a dialysis flow control element 170 for controlling the rate at which dialysis is introduced into the dialysis flow compartment of the medium 130.

In the depicted embodiment, the device 100 also includes a negative pressure control element 190 in communication with the dialysate compartment of the medium component 130. The negative pressure control element 190, which may include a vacuum pump or the like, may be used to generate or change a pressure differential across the membrane to control the rate at which fluid is removed from blood that passes though the medium component 130.

The control electronics 150, which may include a processor, memory, etc., are operably coupled to, and configured to control, the blood flow control element 120, the dialysis flow control element 170, and the negative pressure control element 190. By controlling these elements in a coordinated manner, the rate at which fluid is removed from blood may be controlled. It will be understood that a device 100 need not have all of the controllable elements (120, 170, 190) depicted in FIG. 14 to effectively control rate of fluid removal from blood.

Any suitable control element may be used for the various control elements (120, 150, 170, 195, 415) depicted in FIGS. 13-14. For example, a variable or adjustable rate pump may be employed. Alternatively or in addition, a series of electronically controllable valves may be employed. In some embodiments, the valves are in communication flow paths having differing flow resistances.

While FIGS. 13-14 depict components as being within a single unit, it will be understood that one or more of the components may be housed in separate units. For example, the control electronics, or a portion thereof, may be housed in a separate device, such as a computer, tablet, physician programmer, or the like. The computer, tablet, etc. may receive input from sensors, determine appropriate action to take, and instruct appropriate components of a blood fluid removal device to take the appropriate action.

It will be understood that the blood fluid removal devices and systems, and components thereof, described herein are presented for purposes of illustration and not limitation. Components, devices and systems other than those described herein, or derivations of the components, devices and systems described herein, may be employed. Further, components of the devices depicted and discussed above may be interchanged, substituted or added to components of alternative embodiments, as appropriate. Further, it will be understood that, while many of the blood fluid removal devices depicted in a variety of the figures, such as FIGS. 9-11, are shown as external to the patient, the teachings presented herein apply if the device, or components thereof, were implanted in the patient.

The devices and systems described above, or components thereof, may be used to carry out the methods depicted in FIGS. 1-7, or portions thereof. Of course, any suitable device or system may be employed to carry out the methods, or portions thereof, described above.

The methods described herein, including the methods depicted in FIGS. 1-7, may be carried out by blood fluid removal devices or systems, or other devices in communication with blood fluid removal devices or systems. These methods may be algorithms or instructions programmed into memory of such devices, which may be carried out by processors or other control electronics of the devices. Preferably, the processor is in communication with appropriate control elements of the devices and is configured to control such elements in a manner such that the programmed instructions are carried out by the appropriate device. It will be understood that a computer readable medium programmed with instructions that cause a sensor device, blood fluid removal device, or other suitable device to carry out a method, or a portion thereof, as described herein are contemplated. The computer readable medium may be non-transitory, i.e. lasting for more than a fleeting instant or seconds. The medium may be memory, such as RAM or ROM, a cd or dvd, flash memory, or the like.

Various aspects of methods, devices, systems, computer-readable media, and the like are described herein. A summary of some of selected aspects described herein is presented below.

In a 1^staspect, a method carried out by a blood fluid removal system, comprises (i) initiating a blood fluid removal session with initial system parameters; (ii) acquiring a first set of data regarding one or more patient physiological parameters; (iii) storing the first data set in a “most effective to date” data set memory; (iv) associating the initial system parameters in an increased effectiveness lookup table with the first data set; (v) adjusting at least one parameter of the blood fluid removal session to arrive at adjusted system parameters; (vi) acquiring a second set of data regarding the one or more patient physiological parameters after the at least one parameter of the blood fluid removal session has been adjusted; and (vii) if at least one value of the second data set is closer to the target value than a corresponding at least one value of the first data set: replacing the first data set in the most effective to date data set memory with the second data set; storing in the increased effectiveness lookup table data regarding the second data set; and associating data regarding the adjusted system parameters with the second data set.

A 2^ndaspect is a method of the 1^staspect, further comprising: (i) storing the first data set in a least effective to date data set memory; (ii) associating the initial system parameters in a becoming less effective lookup table with the first data set prior to adjusting the at least one parameter of the blood fluid removal session; and (iii) if the at least one value of the second data set is not closer to the target value than the corresponding at least one value of the first data set: replacing the first data set in the least effective to date data set memory with the second data set; storing in the becoming less effective lookup table data regarding the second data set; and associating data regarding the adjusted system parameters with the second data set.

A 3^rdaspect is a method of the 1^stor 2^ndaspect, further comprising: (i) further adjusting at least one parameter of the blood fluid removal session to arrive at further adjusted system parameters; (ii) acquiring a third set of data regarding the one or more patient physiological parameters after the at least one parameter of the blood fluid removal session has been further adjusted; and (iii) if at least one value of the third data set is closer to the target value than a corresponding at least one value stored in the most effective to date data set memory: replacing the data set in the most effective to date data set memory with the third data set; and storing in the increased effectiveness lookup table data regarding the third data set and associating data regarding the further adjusted system parameters with the third data set.

A 4^thaspect is a method of the 2^ndaspect, further comprising: (i) further adjusting at least one parameter of the blood fluid removal session to arrive at further adjusted system parameters; (ii) acquiring a fourth set of data regarding the one or more patient physiological parameters after the at least one parameter of the blood fluid removal session has been further adjusted; and (iii) if at least one value of the fourth data set is not closer to the target value than a corresponding at least one value stored in the least effective to date data set memory: replacing the data set in the least effective to date data set memory with the fourth data set; and storing in the becoming less effective lookup table data regarding the fourth data set and associating data regarding the further adjusted system parameters with the fourth data set.

A 5^thaspect is a method of any of aspects 1-4, further comprising: (i) acquiring a fifth set of data regarding one or more patient physiological parameters; (ii) comparing the fifth data set to the increased effectiveness lookup table; and (iii) adjusting the system parameters the system parameters associated with the data set stored in the increased effectiveness lookup table if at least one parameter of the data set stored in the improvement lookup table is within a predetermined range of at least one corresponding parameter of the fifth data set.

A 6^thaspect is a method of any of aspects 1-5, further comprising: (i) stopping the blood fluid removal session; (ii) acquiring a sixth set of data regarding one or more patient physiological parameters; (iii) comparing the sixth data set to the increased effectiveness lookup table; and (iv) initiating a second blood fluid removal session with the system parameters associated with the data set stored in the increased effectiveness lookup table if at least one parameter of the data set stored in the increased effectiveness lookup table is within a predetermined range of at least one corresponding parameter of the sixth data set.

A 7^thaspect is a method of any of aspects 1-6, wherein the at least one of the one or more patient parameters are selected from the group consisting of blood pressure, heart rate, pH and concentration of an electrolyte.

An 8^thaspect is method of the 7^thaspect, wherein the electrolyte is potassium.

A 9^thaspect is a method of any of aspects 1-8, wherein the system parameters comprise one or more of fluid removal rate and concentration of one or more electrolyte.

A 10^thaspect is a blood fluid removal system, comprising: (a) a blood fluid removal medium configured to remove blood from a patient, wherein blood enters the medium, fluid is removed from the blood, and blood exits the medium; (b) one or more control elements configured to control (i) the rate at which the medium removed fluid from the blood or (ii) the concentration of electrolytes or pH in the blood that exits the medium; (c) one or more sensors configured monitor one or more physiological parameter of the patient; and (d) control electronics comprising memory and a processor, wherein the control electronics are in operable communication with the one or more sensors and are operably coupled to the one or more control elements, wherein the control electronics are configured to carry out a method according to any of aspects 1-9.

An 11^thaspect is a system of the 10^thaspect, wherein the blood fluid removal medium and the control electronics are housed within a blood fluid removal device.

A 12^thaspect is a system of the 10^thor 11^thaspect, further comprising a computer readable, wherein the computer readable medium comprises instructions that cause the control electronics to carry out the method according to any of aspects 1-9.

A 13^thaspect is a blood fluid removal system comprising: (a) a blood fluid removal medium configured to remove blood from a patient, wherein blood enters the medium, fluid is removed from the blood, and blood exits the medium; (b) one or more control elements configured to control (i) the rate at which the medium removed fluid from the blood or (ii) the concentration of electrolytes or pH in the blood that exits the medium; (c) one or more sensors configured monitor one or more physiological parameter of the patient; and (d) control electronics comprising memory and a processor, wherein the control electronics are in operable communication with the one or more sensors and are operably coupled to the one or more control elements, wherein the control electronics are configured to (i) initiate a blood fluid removal session with initial system parameters; (ii) acquire a first set of data regarding one or more patient physiological parameters; (iii) store the first data set in a most effective to date data set memory; (iv) associate the initial system parameters in an increased effectiveness lookup table with the first data set; (v) adjust at least one parameter of the blood fluid removal session to arrive at adjusted system parameters; (vi) acquire a second set of data regarding the one or more patient physiological parameters after the at least one parameter of the blood fluid removal session has been adjusted; and (vii) if at least one value of the second data set is closer to a target value than a corresponding at least one value of the first data set: replace the first data set in the most effective to date data set memory with the second data set; store in the increased effectiveness lookup table data regarding the second data set; and associate data regarding the adjusted system parameters with the second data set.

A 14^thaspect is a computer-readable medium comprising instructions that, when executed by a blood fluid removal device, cause the device to (i) initiate a blood fluid removal session with initial system parameters; (ii) acquire a first set of data regarding one or more patient physiological parameters; store the first data set in a most effective to date data set memory; (iii) associate the initial system parameters in an increased effectiveness lookup table with the first data set; (iv) adjust at least one parameter of the blood fluid removal session to arrive at adjusted system parameters; (v) acquire a second set of data regarding the one or more patient physiological parameters after the at least one parameter of the blood fluid removal session has been adjusted; and (vi) if at least one value of the second data set is closer to a target value than a corresponding at least one value of the first data set: replace the first data set in the most effective to date data set memory with the second data set; store in the increased effectiveness lookup table data regarding the second data set; and associate data regarding the adjusted system parameters with the second data set.

A 15^thaspect is a method carried out by a blood fluid removal system, comprising: (a) acquiring data regarding one or more of: (i) one or more patient physiological parameters; and (ii) time since last blood fluid removal session; (b) acquiring data regarding one or more target outcomes of a blood fluid removal session; (c) comparing the data regarding at least one of the one or more target outcomes of the blood fluid session to corresponding data regarding at least one prior patient outcome stored in a lookup table, wherein the lookup table comprises data regarding system parameters used in one or more prior blood fluid removal sessions of the patient and comprises patient data prior to the previous session regarding one or more of (i) one or more patient physiological parameters; and (ii) time since last blood fluid removal session; (d) comparing the data regarding the one or more of (i) one or more patient physiological parameters; and (ii) time since last blood fluid removal session to corresponding patient data prior to the previous session stored in the lookup table; and (e) initiating a blood fluid removal session employing the system parameters used the prior blood fluid removal session if the at least one of the one or more target outcomes is within a predetermined range of the corresponding data regarding the at least one prior patient outcome stored in the lookup table and the data regarding the one or more of (i) one or more patient physiological parameters; and (ii) time since last blood fluid removal session is within a predetermined range of the corresponding patient data prior to the previous session stored in the lookup table.

A 16^thaspect is a method of the 15 h aspect, wherein the at least one of the one or more patient parameters are selected from the group consisting of blood pressure, heart rate, pH and concentration of an electrolyte.

A 17^thaspect is method of the 16^thaspect, wherein the electrolyte is potassium.

An 18^thaspect is a method of any of aspects 15-17, wherein the system parameters comprise one or more of fluid removal rate and concentration of one or more electrolyte.

A 19^thaspect is a blood fluid removal system, comprising: (a) a blood fluid removal medium configured to remove blood from a patient, wherein blood enters the medium, fluid is removed from the blood, and blood exits the medium; (b) one or more control elements configured to control (i) the rate at which the medium removed fluid from the blood or (ii) the concentration of electrolytes or pH in the blood that exits the medium; (c) one or more sensors configured monitor one or more physiological parameter of the patient; (d) an input configured to allow entry of data regarding patient or system parameters; and (e) control electronics comprising memory and a processor, wherein the control electronics are in operable communication with the one or more sensors and are operably coupled to the one or more control elements and the input, wherein the control electronics are configured to carry out a method according to any of aspects 15-18.

A 20^thaspect is a system of the 19^thaspect, wherein the blood fluid removal medium and the control electronics are housed within a blood fluid removal device.

A 21^staspect is a system of the 19^thor 20^thaspect, further comprising a computer readable, wherein the computer readable medium comprises instructions that cause the control electronics to carry out the method according to any of aspects 15-18.

A 22^ndaspect is a blood fluid removal system comprising: (a) a blood fluid removal medium configured to remove blood from a patient, wherein blood enters the medium, fluid is removed from the blood, and blood exits the medium; (b) one or more control elements configured to control (i) the rate at which the medium removed fluid from the blood or (ii) the concentration of electrolytes or pH in the blood that exits the medium; (c) one or more sensors configured monitor one or more physiological parameter of the patient; (d) an input configured to allow entry of data regarding patient or system parameters; and (e) control electronics comprising memory and a processor, wherein the control electronics are in operable communication with the one or more sensors and are operably coupled to the one or more control elements and the input, wherein the control electronics are configured to: (i) acquire data regarding one or more of: one or more patient physiological parameters; and time since last blood fluid removal session; (ii) acquire data regarding one or more target outcomes of a blood fluid removal session; (iii) compare the data regarding at least one of the one or more target outcomes to corresponding data regarding at least one prior patient outcome stored in a lookup table, wherein the lookup table comprises data regarding system parameters used in one or more prior blood fluid removal sessions of the patient and comprises patient data prior to the previous session regarding one or more of (i) one or more patient physiological parameters; and (ii) time since last blood fluid removal session; (iv) compare the data regarding the one or more of (i) one or more patient physiological parameters; and (ii) time since last blood fluid removal session to corresponding patient data prior to the previous session stored in the lookup table; and (v) initiate a blood fluid removal session employing the system parameters used in the prior blood fluid removal session if the at least one of the one or more target outcomes is within a predetermined range of the corresponding data regarding the at least one prior patient outcome stored in the lookup table and the data regarding the one or more of (i) one or more patient physiological parameters; and (ii) time since last blood fluid removal session is within a predetermined range of the corresponding patient data prior to the previous session stored in the lookup table.

A 23^rdaspect is a computer-readable medium comprising instructions that, when executed by a blood fluid removal device, cause the device to (i) acquire data regarding one or more of: one or more patient physiological parameters; and time since last blood fluid removal session; (ii) acquire data regarding one or more target outcomes of a blood fluid removal session; (iii) compare the data regarding the at least one of the one or more target outcomes to corresponding data regarding at least one prior patient outcome stored in a lookup table, wherein the lookup table comprises data regarding system parameters used in one or more prior blood fluid removal sessions of the patient and comprises patient data prior to the previous session regarding one or more of one or more patient physiological parameters and time since last blood fluid removal session; (iv) compare the data regarding the one or more of (i) one or more patient physiological parameters; and (ii) time since last blood fluid removal session to corresponding patient data prior to the previous session stored in the lookup table; and (v) initiate a blood fluid removal session employing the system parameters used in the prior blood fluid removal session if the at least one of the one or more target outcomes is within a predetermined range of the corresponding data regarding the at least one prior patient outcome stored in the lookup table and the data regarding the one or more of (i) one or more patient physiological parameters; and (ii) time since last blood fluid removal session is within a predetermined range of the corresponding patient data prior to the previous session stored in the lookup table.

A 24^thaspect is a method carried out by a blood fluid removal system, comprising: (i) collecting first data regarding a patient, the data including one or more of a physiological parameter and time since last blood fluid removal session; (ii) collecting second data regarding system parameters employed in blood fluid removal sessions of the patient; (iii) determining, based on the first and second collected data, whether at least one physiological parameter of the patient became more effective as a result of the system parameters employed; (iv) determining whether a value of current patient data is within a predetermined range of a corresponding value of first collected data; and (v) employing the system parameters that resulted in increased effectiveness, if such parameters are determined to exist and if the current patient data is determined to be within the predetermined range.

A 25^thaspect is a blood fluid removal system, comprising: (a) a blood fluid removal medium configured to remove blood from a patient, wherein blood enters the medium, fluid is removed from the blood, and blood exits the medium; (b) one or more control elements configured to control (i) the rate at which the medium removed fluid from the blood or (ii) the concentration of electrolytes or pH in the blood that exits the medium; (c) one or more sensors configured monitor one or more physiological parameter of the patient; (d) an input configured to allow entry of data regarding patient or system parameters; and (e) control electronics comprising memory and a processor, wherein the control electronics are in operable communication with the one or more sensors and are operably coupled to the one or more control elements and the input, wherein the control electronics are configured to carry out a method according to aspect 24.

A 26^thaspect is a system of the 25^thaspect, wherein the blood fluid removal medium and the control electronics are housed within a blood fluid removal device.

A 27^thaspect is a system of the 25^thor 26^thaspect, further comprising a computer readable, wherein the computer readable medium comprises instructions that cause the control electronics to carry out the method according to the 24^thaspect.

A 28^thaspect is a blood fluid removal system comprising: (a) a blood fluid removal medium configured to remove blood from a patient, wherein blood enters the medium, fluid is removed from the blood, and blood exits the medium; (b) one or more control elements configured to control (i) the rate at which the medium removed fluid from the blood or (ii) the concentration of electrolytes or pH in the blood that exits the medium; (c) one or more sensors configured monitor one or more physiological parameter of the patient; (d) an input configured to allow entry of data regarding patient or system parameters; and (e) control electronics comprising memory and a processor, wherein the control electronics are in operable communication with the one or more sensors and are operably coupled to the one or more control elements and the input, wherein the control electronics are configured to: (i) collect first data regarding a patient, the data including one or more of a physiological parameter and time since last blood fluid removal session; (ii) collect second data regarding system parameters employed in blood fluid removal sessions of the patient; (iii) determine, based on the first and second collected data, whether at least one physiological parameter of the patient became more effective as a result of the system parameters employed; (iv) determine whether a value of current patient data is within a predetermined range of a corresponding value of first collected data; and (v) employ the system parameters that resulted in increased effectiveness, if such parameters are determined to exist and if the current patient data is determined to be within the predetermined range.

A 29^thaspect is a computer-readable medium comprising instructions that, when executed by a blood fluid removal device, cause the device to (i) collect first data regarding a patient, the data including one or more of a physiological parameter and time since last blood fluid removal session; (ii) collect second data regarding system parameters employed in blood fluid removal sessions of the patient; (iii) determine, based on the first and second collected data, whether at least one physiological parameter of the patient became more effective as a result of the system parameters employed; (iv) determine whether a value of current patient data is within a predetermined range of a corresponding value of first collected data; and (v) employ the system parameters that resulted in increased effectiveness, if such parameters are determined to exist and if the current patient data is determined to be within the predetermined range.

A 30^thaspect is a method comprising: (i) storing system parameters from a first blood fluid removal session in memory; (ii) acquiring a first set of data regarding one or more patient parameters following the first session but before a second session; (iii) storing the first data set in a most effective to date data set memory; (iv) associating the first system parameters in an increased effectiveness lookup table with the first data set; (v) storing system parameters from the second blood fluid removal session in memory; (vi) acquiring a second set of data regarding the one or more patient parameters following the second session; (vii) determining whether at least one value of the second data set is closer to a target value than at least one corresponding value of the first data set; and (viii) if the at least one value of the second data set is determined to be closer to the target value than the corresponding at least one value of the first data set: replacing the first data set in the most effective to date data set memory with the second data set; storing in the increased effectiveness lookup table data regarding the second data set; and associating data regarding the second system parameters with the second data set.

A 31^staspect is a method of the 30^thaspect, further comprising: (i) storing the first data set in a least effective to date data set memory; (ii) associating the first system parameters in a decreased effectiveness lookup table with the first data set; and (iii) if the at least one value of the second data set is determined not to be closer to the target value than the corresponding at least one value of the first data set: replacing the first data set in the least effective to date data set memory with the second data set; storing in the decreased effectiveness lookup table data regarding the second data set; and associating data regarding the second system parameters with the second data set.

A 32^ndaspect is a method of the 30^thor 31^staspect, further comprising: (i) storing system parameters for a third blood fluid removal session in memory; (ii) acquiring a third set of data regarding the one or more patient parameters following the third session; (iii) determining whether at least one value of the third data set is closer to a target value than at least one corresponding value stored in the most effective to date data set memory; and (iv) if the at least one value of the third data set is determined to be closer to the target value than the corresponding at least one value stored in the most effective to date data set memory: replacing the data set in the most effective to date data set memory with the third data set; and storing in the increased effectiveness lookup table data regarding the third data set and associating data regarding the third system parameters with the third data set.

A 33^rdaspect is a method of the 30^thor 31^staspect, further comprising: (i) storing system parameters from a fourth blood fluid removal session in memory; (ii) acquiring a fourth set of data regarding the one or more patient parameters following the fourth session; (iii) determining whether at least one value of the fourth data set is further from a target value than at least one corresponding value stored in the least effective to date data set memory; and (iv) if the at least one value of the fourth data set is determined not to be closer to the target value than the corresponding at least one value stored in the least effective to date data set memory: replacing the data set in the least effective to date data set memory with the fourth data set; and storing in the decreased effectiveness lookup table data regarding the fourth data set and associating data regarding the fourth system parameters with the fourth data set.

A 34^thaspect is a method of any of aspects 30-33, further comprising: (i) acquiring a fifth set of data regarding one or more patient parameters; (ii) consulting the increased effectiveness lookup table to determine whether at least one parameter of a data set stored in the increased effectiveness lookup table is within a predetermined range of the fifth data set; and (iii) setting system parameters for a next blood fluid removal session to the system parameters associated with the data set stored in the increased effectiveness lookup table.

A 35^thaspect is a method of any of aspects 30-35, wherein the at least one of the one or more patient parameters are selected from the group consisting of blood pressure, heart rate, pH and concentration of an electrolyte.

A 36^thaspect is a method of the 35^thaspect, wherein the electrolyte is potassium.

A 37^thaspect is a method of any of aspects 30-36, wherein the system parameters comprise one or more of fluid removal rate and concentration of one or more electrolyte.

A 38^thaspect is a method of any of aspects 30-37, wherein the method is carried out by a blood fluid removal system.

A 39^thaspect is a blood fluid removal system, comprising: (a) a blood fluid removal medium configured to remove blood from a patient, wherein blood enters the medium, fluid is removed from the blood, and blood exits the medium; (b) one or more control elements configured to control (i) the rate at which the medium removed fluid from the blood or (ii) the concentration of electrolytes or pH in the blood that exits the medium; (c) one or more sensors configured monitor one or more physiological parameter of the patient; and (d) control electronics comprising memory and a processor, wherein the control electronics are in operable communication with the one or more sensors and are operably coupled to the one or more control elements, wherein the control electronics are configured to carry out a method according to any of aspects 30-38.

A 40^thaspect is a system of the 39^thaspect, wherein the blood fluid removal medium and the control electronics are housed within a blood fluid removal device.

A 41^staspect is a system of the 39^thor 40^thaspects, further comprising a computer readable, wherein the computer readable medium comprises instructions that cause the control electronics to carry out the method according to any of aspects 30-38.

A 42^ndaspect is a blood fluid removal system comprising: (a) a blood fluid removal medium configured to remove blood from a patient, wherein blood enters the medium, fluid is removed from the blood, and blood exits the medium; (b) one or more control elements configured to control (i) the rate at which the medium removed fluid from the blood or (ii) the concentration of electrolytes or pH in the blood that exits the medium; (c) one or more sensors configured monitor one or more physiological parameter of the patient; and (d) control electronics comprising memory and a processor, wherein the control electronics are in operable communication with the one or more sensors and are operably coupled to the one or more control elements, wherein the control electronics are configured to (i) store system parameters from a first blood fluid removal session in memory; (ii) acquire a first set of data regarding one or more patient parameters following the first session but before a second session; (iii) store the first data set in a most effective to date data set memory; (iv) associate the first system parameters in an increased effectiveness lookup table with the first data set; (v) store system parameters from the second blood fluid removal session in memory; (vi) acquire a second set of data regarding the one or more patient parameters following the second session; (vii) determine whether at least one value of the second data set is closer to a target value than at least one corresponding value of the first data set; and (viii) if the at least one value of the second data set is determined to be closer to the target value than the corresponding at least one value of the first data set: replace the first data set in the most effective to date data set memory with the second data set; store in the increased effectiveness lookup table data regarding the second data set; and associate data regarding the second system parameters with the second data set.

A 43^rdaspect is a computer-readable medium comprising instructions that, when executed by a blood fluid removal device, cause the device to (i) store system parameters from a first blood fluid removal session in memory; (ii) acquire a first set of data regarding one or more patient parameters following the first session but before a second session; (iii) store the first data set in a most effective to date data set memory; (iv) associate the first system parameters in an increased effectiveness lookup table with the first data set; (v) store system parameters from the second blood fluid removal session in memory; (vi) acquire a second set of data regarding the one or more patient parameters following the second session; (vii) determine whether at least one value of the second data set is closer to a target value than at least one corresponding value of the first data set; and (viii) if the at least one value of the second data set is determined to be closer to the target value than the corresponding at least one value of the first data set: replace the first data set in the most effective to date data set memory with the second data set; store in the increased effectiveness lookup table data regarding the second data set; and associate data regarding the second system parameters with the second data set.

Thus, systems, devices and methods for INTERSESSION MONITORING FOR BLOOD FLUID REMOVAL THERAPY are described. Those skilled in the art will recognize that the preferred embodiments described herein may be altered or amended without departing from the true spirit and scope of the disclosure, as defined in the accompanying claims.

In the claims that follow and the preceding aspects, the designators “first”, “second”, “third” and the like are used for purposes of distinguishing between elements and not for purposes of enumerating the elements or for defining a sequence of the elements. For example, a “third” data set does not necessarily imply that there are three data sets but rather that the “third” data set is distinct from the “first” data set. By way of further example, a “third” data set need not be obtained after a “first” data set.

Claims

1. A non-transitory computer-readable storage medium with an executable program stored thereon comprising instructions that, when executed by one or more programmable computer systems incorporated into a blood fluid removal device, cause the blood fluid removal device to execute the following steps: acquire first patient data of a first blood fluid removal session regarding one or more of (i) one or more patient physiological parameters; and (ii) time since a last blood fluid removal session before an upcoming blood fluid removal session;acquire data regarding one or more target outcomes of each blood fluid removal session;compare the data regarding the at least one of the target outcomes of each blood fluid removal session to corresponding data regarding at least one prior patient outcome stored in a lookup table; wherein the lookup table comprises data regarding system parameters used in the one or more prior blood fluid removal sessions of the patient and comprises prior patient data prior to a first session regarding one or more of (i) one or more patient physiological parameters and (ii) time since the prior blood fluid removal session before a corresponding upcoming blood fluid removal session;compare the first patient data to the corresponding prior patient data stored in the lookup table;initiate the upcoming blood fluid removal session employing the system parameters used in the prior blood fluid removal session if the at least one of the one or more target outcomes is within a predetermined range of the corresponding data regarding the at least one prior patient outcome stored in the lookup table and the patient data is within a predetermined range of the corresponding prior patient data.
2. A method carried out by a blood fluid removal system, wherein the blood fluid removal system comprises:(a) a blood fluid removal medium to remove blood from the patient, wherein the blood enters the medium, a fluid contained in the blood is removed from the blood, and the blood exits the medium;(b) one or more control elements to control (i) a rate at which the medium removes fluid from the blood or (ii) concentration of electrolytes or pH in the blood that exits the medium;(c) one or more sensors to monitor one or more physiological parameters of the patient wherein the physiological parameters are one or more selected from the group consisting of blood pressure, heart rate, pH, and electrolyte concentration, the one or more sensors sensing signals from one or more of the blood and a tissue of the patient; and(d) control electronics comprising memory and a processor, wherein the control electronics are in operable communication with the one or more sensors and are operably coupled to the one or more control elements,wherein the control electronics are programmed to carry out the method, comprising:acquiring first patient data of a first blood fluid removal session regarding one or more of: (i) the one or more patient physiological parameters; and (ii) time since a last blood fluid removal session before an upcoming blood fluid removal session;acquiring data regarding one or more target outcomes of each blood fluid removal session;comparing the data regarding at least one of the one or more target outcomes of each blood fluid removal session to corresponding data regarding at least one prior patient outcome stored in a lookup table, wherein the lookup table comprises data regarding system parameters used in the one or more prior blood fluid removal sessions of the patient and comprises prior patient data prior to the first session regarding one or more of (i) one or more patient physiological parameters; and (ii) time since the prior blood fluid removal session before a corresponding upcoming blood fluid removal session;comparing the first patient data to the corresponding prior patient data stored in the lookup table;initiating the upcoming blood fluid removal session employing the system parameters used in the prior blood fluid removal session if the at least one of the one or more target outcomes is within a predetermined range of the corresponding data regarding the at least one prior patient outcome stored in the lookup table and the patient data is within a predetermined range of the corresponding prior patient data stored in the lookup table.
3. The method of claim 2, wherein the at least one of the one or more patient parameters comprise the concentration of an electrolyte.
4. The method of claim 3, wherein the electrolyte is potassium.
5. The method of claim 2, wherein the system parameters comprise one or more of fluid removal rate and concentration of one or more electrolyte.
6. A blood fluid removal system, comprising: a blood fluid removal medium configured to remove blood from a patient, wherein blood enters the medium, fluid is removed from the blood, and blood exits the medium;one or more control elements configured to control (i) the rate at which the medium removed fluid from the blood or (ii) the concentration of electrolytes or pH in the blood that exits the medium;one or more sensors configured monitor one or more physiological parameter of the patient;an input configured to allow entry of data regarding patient or system parameters; andcontrol electronics comprising memory and a processor, wherein the control electronics are in operable communication with the one or more sensors and are operably coupled to the one or more control elements and the input,wherein the control electronics are programmed to carry out a method according to claim 2.
7. The system of claim 6, wherein the blood fluid removal medium and the control electronics are housed within a blood fluid removal device.
8. The system of claim 6, further comprising a computer readable, wherein the computer readable medium comprises instructions that cause the control electronics to carry out the method according claim 2.
9. A blood fluid removal system comprising: a blood fluid removal medium configured to remove blood from a patient, wherein blood enters the medium, fluid is removed from the blood, and blood exits the medium;one or more control elements configured to control (i) the rate at which the medium removed fluid from the blood or (ii) the concentration of electrolytes or pH in the blood that exits the medium;one or more sensors configured monitor one or more physiological parameter of the patient;an input configured to allow entry of data regarding patient or system parameters; andcontrol electronics comprising memory and a processor, wherein the control electronics are in operable communication with the one or more sensors and are operably coupled to the one or more control elements and the input,wherein the control electronics are programmed to: acquire data regarding one or more of: one or more patient physiological parameters; and time since last blood fluid removal session;acquire data regarding one or more target outcomes of a blood fluid removal session;compare the data regarding at least one of the one or more target outcomes of the blood fluid removal session to corresponding data regarding at least one prior patient outcome stored in a lookup table, wherein the lookup table comprises data regarding system parameters used in one or more prior blood fluid removal sessions of the patient and comprises patient data prior to the previous session regarding one or more of (i) one or more patient physiological parameters; and (ii) time since last blood fluid removal session;compare the data regarding the one or more of (i) one or more patient physiological parameters; and (ii) time since last blood fluid removal session to corresponding patient data prior to the previous session stored in the lookup table; andinitiate a blood fluid removal session employing the system parameters used the prior blood fluid removal session if the at least one of the one or more target outcomes is within a predetermined range of the corresponding data regarding the at least one prior target outcome stored in the lookup table and the data regarding the one or more of (i) one or more patient physiological parameters; and (ii) time since last blood fluid removal session is within a predetermined range of the corresponding patient data prior to the previous session stored in the lookup table.
10. A non-transitory computer-readable storage medium with an executable program stored thereon comprising instructions that, when executed by one or more programmable computer systems incorporated into a blood fluid removal device, cause the blood fluid removal device to execute the following steps: acquire first patient data of a first blood fluid removal session regarding one or more of: (i) one or more patient physiological parameters; and (ii) time since last blood fluid removal session;acquire data regarding one or more target outcomes of each blood fluid removal session;compare the data regarding at least one of the one or more target outcomes of each blood fluid removal session to corresponding data regarding at least one prior patient outcome stored in a lookup table, wherein the lookup table comprises data regarding system parameters used in the one or more prior blood fluid removal sessions of the patient and comprises prior patient data prior to the first session regarding one or more of (i) one or more patient physiological parameters; and (ii) time since the prior blood fluid removal session;compare the first patient data to the corresponding prior patient data stored in the lookup table; andinitiate the upcoming blood fluid removal session employing the system parameters used in the prior blood fluid removal session if the at least one of the one or more target outcomes is within a predetermined range of the corresponding data regarding the at least one prior target outcome stored in the lookup table and the patient data is within a predetermined range of the corresponding prior patient data stored in the lookup table.

RELATED APPLICATION

This application is a divisional of U.S. patent application Ser. No. 13/424,429 filed Mar. 20, 2012, which claims priority to U.S. Provisional Application No. 61/480,539, U.S. Provisional Application No. 61/480,544, U.S. Provisional Application No. 61/480,541, U.S. Provisional Application No. 61/480,535, U.S. Provisional Application No. 61/480,532, U.S. Provisional Application No. 61/480,530, and U.S. Provisional Application No. 61/480,528, wherein each priority application was filed Apr. 29, 2011, wherein each priority application is hereby incorporated by reference in its entirety to the extent that it does not conflict with the disclosure presented herein.

US Referenced Citations (268)

Number	Name	Date	Kind
3608729	Haselden	Sep 1971	A
3669878	Marantz	Jun 1972	A
3669880	Marantz	Jun 1972	A
3850835	Marantz	Nov 1974	A
3884808	Scott	May 1975	A
3989622	Marantz	Nov 1976	A
4060485	Eaton	Nov 1977	A
4371385	Johnson	Feb 1983	A
4374382	Markowitz	Feb 1983	A
4381999	Boucher	May 1983	A
4460555	Thompson	Jul 1984	A
4556063	Thompson	Dec 1985	A
4562751	Nason	Jan 1986	A
4581141	Ash	Apr 1986	A
4650587	Polak	Mar 1987	A
4678408	Mason	Jul 1987	A
4685903	Cable	Aug 1987	A
4750494	King	Jun 1988	A
4826663	Alberti	May 1989	A
4828693	Lindsay	May 1989	A
5080653	Voss	Jan 1992	A
5092886	Dobos-Hardy	Mar 1992	A
5097122	Coiman	Mar 1992	A
5127404	Wyborny	Jul 1992	A
5284470	Beltz	Feb 1994	A
5302288	Meidl	Apr 1994	A
5305745	Zacouto	Apr 1994	A
5318750	Lascombes	Jun 1994	A
5468388	Goddard	Nov 1995	A
5507723	Keshaviah	Apr 1996	A
5651893	Kenley	Jul 1997	A
5683432	Goedeke	Nov 1997	A
5744031	Bene	Apr 1998	A
5762782	Kenley	Jun 1998	A
5902336	Mishkin	May 1999	A
5944684	Roberts	Aug 1999	A
6048732	Anslyn	Apr 2000	A
6052622	Holmstrom	Apr 2000	A
6058331	King	May 2000	A
6156002	Polaschegg	Dec 2000	A
6230059	Duffin	May 2001	B1
6248093	Moberg	Jun 2001	B1
6254567	Treu	Jul 2001	B1
6321101	Holmstrom	Nov 2001	B1
6362591	Moberg	Mar 2002	B1
6363279	Ben-Haim	Mar 2002	B1
6505075	Weiner	Jan 2003	B1
6554798	Mann	Apr 2003	B1
6555986	Moberg	Apr 2003	B2
6589229	Connelly	Jul 2003	B1
6602399	Fromherz	Aug 2003	B1
6627164	Wong	Sep 2003	B1
6676608	Keren	Jan 2004	B1
6689083	Gelfand	Feb 2004	B1
6706007	Gelfand	Mar 2004	B2
6711439	Bradley	Mar 2004	B1
6726647	Sternby	Apr 2004	B1
6780322	Bissler	Aug 2004	B1
6818196	Wong	Nov 2004	B2
6878283	Thompson	Apr 2005	B2
6887214	Levin	May 2005	B1
6890315	Levin	May 2005	B1
6960179	Gura	Nov 2005	B2
7074332	Summerton	Jul 2006	B2
7077819	Goldau	Jul 2006	B1
7131956	Pirazzoli	Nov 2006	B1
7175809	Gelfand	Feb 2007	B2
7208092	Micheli	Apr 2007	B2
7276042	Polaschegg	Oct 2007	B2
7399289	Gelfand	Jul 2008	B2
7500958	Asbrink	Mar 2009	B2
7566432	Wong	Jul 2009	B2
7575564	Childers	Aug 2009	B2
7674231	McCombie	Mar 2010	B2
7704361	Garde	Apr 2010	B2
7736507	Wong	Jun 2010	B2
7744553	Kelly	Jun 2010	B2
7754852	Burnett	Jul 2010	B2
7756572	Fard	Jul 2010	B1
7775983	Zhang	Aug 2010	B2
7776210	Rosenbaum	Aug 2010	B2
7785463	Bissler	Aug 2010	B2
7794141	Perry	Sep 2010	B2
7850635	Polaschegg	Dec 2010	B2
7857976	Bissler	Dec 2010	B2
7867214	Childers	Jan 2011	B2
7896831	Sternby	Mar 2011	B2
7922686	Childers	Apr 2011	B2
7922911	Micheli	Apr 2011	B2
7947179	Rosenbaum	May 2011	B2
7955291	Sternby	Jun 2011	B2
7967022	Grant	Jun 2011	B2
7981082	Wang	Jul 2011	B2
8000000	Greenberg	Aug 2011	B2
8034161	Gura	Oct 2011	B2
8070709	Childers	Dec 2011	B2
8096969	Roberts	Jan 2012	B2
8105260	Tonelli	Jan 2012	B2
8183046	Lu	May 2012	B2
8187250	Roberts	May 2012	B2
8197439	Wang	Jun 2012	B2
8202241	Karakama	Jun 2012	B2
8246826	Wilt	Aug 2012	B2
8273049	Demers	Sep 2012	B2
8282828	Wallenas	Oct 2012	B2
8292594	Tracey	Oct 2012	B2
8313642	Yu	Nov 2012	B2
8317492	Demers	Nov 2012	B2
8357113	Childers	Jan 2013	B2
8366316	Kamen	Feb 2013	B2
8366655	Kamen	Feb 2013	B2
8404091	Ding	Mar 2013	B2
8409441	Wilt	Apr 2013	B2
8496809	Roger	Jul 2013	B2
8499780	Wilt	Aug 2013	B2
8500676	Jansson	Aug 2013	B2
8512271	Moissl	Aug 2013	B2
8518260	Raimann	Aug 2013	B2
8521482	Akonur	Aug 2013	B2
8535525	Heyes	Sep 2013	B2
8560510	Brueggerhoff	Oct 2013	B2
8580112	Updyke	Nov 2013	B2
8597227	Childers	Dec 2013	B2
8696626	Kirsch	Apr 2014	B2
8903492	Soykan	Dec 2014	B2
8926542	Gerber	Jan 2015	B2
9561316	Gerber	Feb 2017	B2
20020042561	Schulman	Apr 2002	A1
20020112609	Wong	Aug 2002	A1
20030080059	Peterson	May 2003	A1
20030097086	Gura	May 2003	A1
20030105435	Taylor	Jun 2003	A1
20030114787	Gura	Jun 2003	A1
20040019312	Childers	Jan 2004	A1
20040068219	Summerton	Apr 2004	A1
20040099593	DePaolis	May 2004	A1
20040147900	Polaschegg	Jul 2004	A1
20040168969	Sternby	Sep 2004	A1
20040215090	Erkkila	Oct 2004	A1
20050065760	Murtfeldt	Mar 2005	A1
20050113796	Taylor	May 2005	A1
20050126961	Bissler	Jun 2005	A1
20050131331	Kelly	Jun 2005	A1
20050126998	Childers	Jul 2005	A1
20050150832	Tsukamoto	Jul 2005	A1
20050234381	Niemetz	Oct 2005	A1
20050236330	Nier	Oct 2005	A1
20050274658	Rosenbaum	Dec 2005	A1
20060025661	Sweeney	Feb 2006	A1
20060217771	Soykan	Feb 2006	A1
20060058731	Burnett	Mar 2006	A1
20060195064	Plahey	Aug 2006	A1
20060226079	Mori	Oct 2006	A1
20060241709	Soykan	Oct 2006	A1
20060264894	Moberg	Nov 2006	A1
20070007208	Brugger	Jan 2007	A1
20070066928	Lannoy	Mar 2007	A1
20070138011	Hofmann	Jun 2007	A1
20070175827	Wariar	Aug 2007	A1
20070179431	Roberts	Aug 2007	A1
20070213653	Childers	Sep 2007	A1
20070215545	Bissler	Sep 2007	A1
20070255250	Moberg	Nov 2007	A1
20080006570	Gura	Jan 2008	A1
20080021337	Li	Jan 2008	A1
20080053905	Brugger	Mar 2008	A9
20080067132	Ross	Mar 2008	A1
20080093276	Roger	Apr 2008	A1
20080215247	Tonelli	Sep 2008	A1
20080253427	Kamen	Oct 2008	A1
20090020471	Tsukamoto	Jan 2009	A1
20090101577	Fulkerson	Apr 2009	A1
20090124963	Hogard	May 2009	A1
20090127193	Updyke	May 2009	A1
20090171261	Sternby	Jul 2009	A1
20090264776	Vardy	Oct 2009	A1
20090275849	Stewart	Nov 2009	A1
20090275883	Chapman	Nov 2009	A1
20090281484	Childers	Nov 2009	A1
20090282980	Gura	Nov 2009	A1
20090314063	Sternby	Dec 2009	A1
20100004588	Yeh	Jan 2010	A1
20100010429	Childers	Jan 2010	A1
20100042035	Moissl	Feb 2010	A1
20100076398	Scheurer	Mar 2010	A1
20100078381	Merchant	Apr 2010	A1
20100078387	Wong	Apr 2010	A1
20100084330	Wong	Apr 2010	A1
20100087771	Karakama	Apr 2010	A1
20100094158	Solem	Apr 2010	A1
20100113891	Barrett	May 2010	A1
20100114012	Sandford	May 2010	A1
20100137693	Porras	Jun 2010	A1
20100137782	Jansson	Jun 2010	A1
20100168546	Kamath	Jul 2010	A1
20100217180	Akonur	Aug 2010	A1
20100217181	Roberts	Aug 2010	A1
20100224492	Ding	Sep 2010	A1
20100234795	Wallenas	Sep 2010	A1
20100241045	Kelly	Sep 2010	A1
20100264086	Noack	Oct 2010	A1
20110017665	Updyke	Jan 2011	A1
20110048949	Ding et al.	Mar 2011	A1
20110066043	Banet	Mar 2011	A1
20110071465	Wang	Mar 2011	A1
20110077574	Sigg	Mar 2011	A1
20110079558	Raimann	Apr 2011	A1
20110087187	Beck	Apr 2011	A1
20110100909	Stange	May 2011	A1
20110106003	Childers	May 2011	A1
20110130666	Dong	Jun 2011	A1
20110144570	Childers	Jun 2011	A1
20110163034	Castellarnau	Jul 2011	A1
20110184340	Tan	Jul 2011	A1
20110208105	Brandl	Aug 2011	A1
20110272337	Palmer	Nov 2011	A1
20110301447	Park	Dec 2011	A1
20120016228	Kroh	Jan 2012	A1
20120083729	Childers	Apr 2012	A1
20120085707	Beiriger	Apr 2012	A1
20120115248	Ansyln	May 2012	A1
20120220528	VanAntwerp	Aug 2012	A1
20120258546	Marran	Oct 2012	A1
20120259276	Childers	Oct 2012	A1
20120273415	Gerber	Nov 2012	A1
20120273420	Gerber	Nov 2012	A1
20120277546	Soykan	Nov 2012	A1
20120277551	Gerber	Nov 2012	A1
20120277552	Gerber	Nov 2012	A1
20120277604	Gerber	Nov 2012	A1
20120277650	Gerber	Nov 2012	A1
20120277655	Gerber	Nov 2012	A1
20120277722	Gerber	Nov 2012	A1
20130037465	Heyes	Feb 2013	A1
20130062265	Balschat	Mar 2013	A1
20130193073	Hogard	Aug 2013	A1
20130199998	Kelly	Aug 2013	A1
20130211730	Wolff	Aug 2013	A1
20130213890	Kelly	Aug 2013	A1
20130228517	Roger	Sep 2013	A1
20130231607	Roger	Sep 2013	A1
20130248426	Pouchoulin	Sep 2013	A1
20130274642	Soykan	Oct 2013	A1
20130324915	(Krensky)Britton	Dec 2013	A1
20130330208	Ly	Dec 2013	A1
20130331774	Farrell	Dec 2013	A1
20140018728	Plahey	Jan 2014	A1
20140042092	Akonur	Feb 2014	A1
20140065950	Mendelsohn	Mar 2014	A1
20140088442	Soykan	Mar 2014	A1
20140110340	White	Apr 2014	A1
20140110341	White	Apr 2014	A1
20140158538	Collier	Jun 2014	A1
20140158588	Pudil	Jun 2014	A1
20140158623	Pudil	Jun 2014	A1
20140190876	Meyer	Jul 2014	A1
20140217028	Pudil	Aug 2014	A1
20140217030	Meyer	Aug 2014	A1
20140220699	Pudil	Aug 2014	A1
20150032023	Soykan	Jan 2015	A1
20150080682	Gerber	Mar 2015	A1
20150088047	Gerber	Mar 2015	A1
20150144539	Pudil	May 2015	A1
20150250427	Soykan	Sep 2015	A1
20150352269	Gerber	Dec 2015	A1
20150367054	Gerber	Dec 2015	A1
20160206801	Gerber	Jul 2016	A1
20160331884	Sigg	Nov 2016	A1

Foreign Referenced Citations (110)

Number	Date	Country
101193667	Jun 2008	CN
103037917	Apr 2013	CN
266795	Nov 1987	EP
0272414	Oct 1991	EP
0330892	Jul 1994	EP
1124599	May 2000	EP
1175238	Nov 2000	EP
2308526	Oct 2003	EP
1364666	Nov 2003	EP
1523347	Jan 2004	EP
1523350	Jan 2004	EP
0906768	Feb 2004	EP
1691863	Apr 2005	EP
2116269	Feb 2008	EP
1450879	Oct 2008	EP
1514562	Apr 2009	EP
2219703	May 2009	EP
1592494	Jun 2009	EP
2100553	Sep 2009	EP
2398529	Nov 2010	EP
2575827	Dec 2010	EP
2100553	Aug 2011	EP
2576453	Dec 2011	EP
2701580	Nov 2012	EP
2701595	Nov 2012	EP
1345856	Mar 2013	EP
2344220	Apr 2013	EP
1351756	Jul 2013	EP
2190498	Jul 2013	EP
2701596	Mar 2014	EP
1582226	Jan 2016	EP
S551980138462	Oct 1980	JP
2002542900	Dec 2002	JP
2003235965	Aug 2003	JP
5099464	Oct 2012	JP
1995003839	Feb 1995	WO
9937342	Jul 1999	WO
0057935	Oct 2000	WO
200066197	Nov 2000	WO
2000066197	Nov 2000	WO
200170307	Sep 2001	WO
2001085295	Sep 2001	WO
0185295	Nov 2001	WO
1085295	Nov 2001	WO
2002013691	Feb 2002	WO
2003043677	May 2003	WO
2003043680	May 2003	WO
2003051422	Jun 2003	WO
2004008826	Jan 2004	WO
2004009156	Jan 2004	WO
2004009158	Jan 2004	WO
2004030716	Apr 2004	WO
2004030717	Apr 2004	WO
2004064616	Aug 2004	WO
2005061026	Jul 2005	WO
2005123230	Dec 2005	WO
2006011009	Feb 2006	WO
2006017446	Feb 2006	WO
2007038347	Apr 2007	WO
2007089855	Aug 2007	WO
2008037410	Apr 2008	WO
2009026603	Dec 2008	WO
2009024566	Feb 2009	WO
2009026603	Mar 2009	WO
2009061608	May 2009	WO
2009094184	Jul 2009	WO
2009157877	Dec 2009	WO
2009157878	Dec 2009	WO
2010024963	Mar 2010	WO
2010028860	Mar 2010	WO
2010028860	Mar 2010	WO
2010033314	Mar 2010	WO
2010033699	Mar 2010	WO
2010077851	Jul 2010	WO
2010096659	Oct 2010	WO
2010121820	Oct 2010	WO
2011025705	Mar 2011	WO
2011026645	Mar 2011	WO
2011137693	Nov 2011	WO
2012042323	Apr 2012	WO
2012050781	Apr 2012	WO
2012051996	Apr 2012	WO
2012073420	Jul 2012	WO
2012148781	Nov 2012	WO
2012148786	Nov 2012	WO
2012148787	Nov 2012	WO
2012148789	Nov 2012	WO
2012162515	Nov 2012	WO
2012172398	Dec 2012	WO
2013019179	Feb 2013	WO
2013019994	Feb 2013	WO
2013025844	Feb 2013	WO
2013028809	Feb 2013	WO
2013101292	Jul 2013	WO
2013103607	Jul 2013	WO
2013103906	Jul 2013	WO
2013110906	Aug 2013	WO
2013110919	Aug 2013	WO
2013114063	Aug 2013	WO
2013121162	Aug 2013	WO
2013140346	Sep 2013	WO
2013141896	Sep 2013	WO
2013101292	Oct 2013	WO
14066254	May 2014	WO
14066255	May 2014	WO
14077082	May 2014	WO
2014121162	Aug 2014	WO
2014121163	Aug 2014	WO
2014121167	Aug 2014	WO
2014121169	Aug 2014	WO

Non-Patent Literature Citations (83)

Entry
Wang, Fundamentals of intrathoracic impedance monitoring in heart failure, Am. J. Cardiology, 2007, 3G-10G: Suppl.
Weissman, S., et al., “Hydroxyurea-induced hepatitis in human immunodeficiency virus-positive patients.” Clin. Infec. Dis, (Jul. 29, 1999): 223-224.
Brynda, et al., The detection of toman 2-microglcbuiin by grating coupler immunosensor with three dimensional antibody networks. Biosensors & Bioelectronics, 1999, 363-368, 14(4).
Hemametrics, Crit-Line Hematocrit Accuracy, 2003, 1-5, vol. 1, Tech Note No. 11 (Rev. D).
Nedelkov, et al., Design of buffer exchange surfaces and sensor chips for biosensor chip mass spectrometry, Proteomics, 2002, 441-446, 2(4).
PCT/US/2012/034327, International Search Report, dated Aug. 13, 2013.
PCT/US/2012/034329, International Search Report, dated Dec. 3, 2012.
PCT/US2012/034331, International Search Report and Written Opinion dated Jul. 9, 2012.
PCT/US2012/034334, International Search Report, dated Jul. 6, 2012.
PCT/US2012/034335, International Search Report, dated Sep. 5, 2012.
Roberts M, The regenerative dialysis (REDY) sorbent system. Nephrology, 1998, 275-278:4.
Siegenthaler, et al., Pulmonary fluid status monitoring with intrathoracic impedance, Journal of Clinical Monitoring and Computing, 24:449-451, 2010.
U.S. Appl. No. 61/480,528.
U.S. Appl. No. 61/480,530.
U.S. Appl. No. 61/480,532.
U.S. Appl. No. 61/480,535.
U.S. Appl. No. 61/480,539.
U.S. Appl. No. 61/480,541.
U.S. Appl. No. 61/480,544.
Zhong, et. al., Miniature urea sensor based on H(+)-ion sensitive field effect transistor and its application in clinical analysis, Chin. J. Biotechnol., 1992, 57-65. 8(1).
Wheaton, et al., Dowex Ion Exchange Resins—Fundamentals of Ion Exchange; Jun. 2000, pp. 1-9. http://www.dow.com/scripts/litorder.asp?filepath=liquidseps/pdfs/noreg/177-01837.pdf.
Lima, et. al., An electrochemical sensor based on nanostructure hollsndite-type manganese oxide for detection of potassium ion, Sensors, 2009, 6613-8625, 9.
MacLean, et, al., Effects of hindlimb contraction on pressor and muscle interstitial metabolite responses in the cat, J. App. Physiol., 1998, 1583-1592, 85(4).
Overgaard, et. al., Activity-induced recovery of excitability in K+-depressed rat soieus muscle, Am. J. P.
Overgaard. et. al., Relations between excitability and contractility in rate soleus'muscle: role of the NA+-K+ pump and NA+-K-S gradients. Journal of Physiology, 1999, 215-225, 518(1).
PCT/US2012/034332, International Search Report, dated Jul. 5, 2012.
U.S. Appl. No. 13/368,225.
Redfield, et. al, Restoration of renal response to atrial natriuretic factor in experimental low-output heat failure, Am. J. Physiol., 1989, R917-923:257.
Rogoza, et. al., Validation of A&D UA-767 device for the self-measurement of blood pressure, Blood Pressure Monitoring, 2000, 227-231, 5(4).
Ronco et al. 2008, ‘Cardiorenal Syndrome,’ Journal American College Cardiology, 52:1527-1539, Abstract.
Secemsky, et. al, High prevalence of cardiac autonomic dysfunction and T-wave alternans in dialysis patients. Heart Rhythm, Apr. 2011, 592-598 : vol. 8, No. 4.
U.S. Appl. No. 13/424,533.
U.S. Appl. No. 13/424,467.
U.S. Appl. No. 13/424,429.
U.S. Appl. No. 13/424,454.
U.S. Appl. No. 13/424,479.
U.S. Appl. No. 13/424,490.
U.S. Appl. No. 13/424,517.
U.S. Appl. No. 13/424,525.
Wei, et. al., Fullerene-cryptand coated piezoelectric crystal urea sensor based on urease, Analytica Chimica Acta, 2001,77-85:437.
PCT/US2014/067650 International Search Report Written Opinion dated Mar. 9, 2015.
PCT/US2012/034335, International Preliminary Report on Patentability, dated Nov. 7, 2013.
Gambro AK 96 Dialysis Machine Operator's Manual, Dec. 2012.
PCT/US2012/034329, International Preliminary Report on Patentability, dated Oct. 29, 2013.
U.S. Appl. No. 13/757,794, filed Feb. 2, 2013.
U.S. Appl. No. 13/757,722, filed Feb. 1, 2013.
U.S. Appl. No. 13/837,287, filed Mar. 15, 2013.
U.S. Appl. No. 13/757,792, filed Feb. 2, 2013.
U.S. Appl. No. 13/791,755, filed Mar. 8, 2013.
PCT/US2014/014357 International Search Report and Written Opinion dated May 19, 2014.
Leifer et al., ‘A Study on the Temperature Variation of Rise Velocity for Large Clean Bubbles,’ J. Atmospheric & Oceanic Tech., vol. 17, pp. 1392-1402.
Culleton, BF et al. Effect of Frequent Nocturnal Hemodialysis vs. Conventional Hemodialysis on Left Ventricular Mass and Quality of Life. 2007 Journal of the American Medical Association 298 (11), 1291-1299.
Talaia, ‘Terminal Velocity of a Bubble Rise in a Liquid Column,’ World Acad. of Sci., Engineering & Tech., vol. 28, pp. 264-268.
The FHN Trial Group. In-Center. Hemodialysis Six Times per Week versus Three Times per Week, New England Journal of Medicine, 2010 Abstract.
U.S. Appl. No. 13/757,693, filed Feb. 1, 2013.
Coast, et al. 1990, An approach to Cardiac Arrhythmia analysis Using Hidden Markov Models, IEEE Transactions on Biomedical Engineering. 1990, 37(9):826-835.
PCT/US2012/034330, International Preliminary Report on Patentability, dated Oct. 29, 2013.
PCT Application, PCT/US20013/020404, filed Jan. 4, 2013.
U.S. Appl. No. 13/836,973, filed Mar. 15, 2013.
U.S. Appl. No. 14/259,655, filed Apr. 23, 2014.
U.S. Appl. No. 14/259,589, filed Apr. 23, 2014.
PCT/US2012/034333, International Preliminary Report on Patentability, dated Oct. 29, 2013.
PCT/US2012/034333, International Search Report, dated Aug. 29, 2012.
U.S. Appl. No. 13/757,794, filed Feb. 2, 2012.
Bleyer, et. al., Sudden and cardiac death rated in hemodialysis patients, Kidney International. 1999, 1553-1559: 55.
Weiner, et. al., Article: Cardiac Function and Cardiovascular Disease in Chronic Kidney Disease, Book: Primer on Kidney Diseases (Author: Greenberg, et al), 2009,499-505, 5th Ed., Saunders Elsevier, Philadelphia, PA.
U.S. Appl. No. 13/424,517 IDS, filed Aug. 2, 2012.
U.S. Appl. No. 13/424,517, IDS filed Dec. 2, 2013.
PCT/US2012/034332, Internatonal Preliminary Report on Patentability, dated Oct. 29, 2013.
PCT/US2012/034303, Internationa Search Report, dated Jul. 6, 2013.
PCT/US2012/034327, International Preliminary Report on Patentability, dated Oct. 29, 2013.
Zoccali, Pulmonary Congestion Predicts Cardiac Events and Mortality in ESRD, Clinical Epidemiology, J. Am Soc Nephrol 24:639-646, 2013.
Velasco, Optimal Fluid Control can Normalize Cardiovascular Risk Markers and Limit Left Ventricular Hypertrophy in Thrice Weekly Dialysis Patients, Hemodialysis Intenational, 16:465-472, 2012.
Whitman, CKD and Sudden Cardiac Death: Epidemiology, Mechanisms, and Therapeutic Approaches, J Am Soc Nephrol, 23:1929-1939, 2012.
Hall, Hospitalization for Congestive Heart Failure: United States, 2000-2010, NCHS Data Brief, No. 108, Oct. 2012.
Albert, Fluid Management Strategies in Heart Failure, Critical Care Nurse, 32:20-32, 2012.
PCT/US2014/065201 International Search Report dated May 26, 2015.
John Wm Agar: “Review: Understanding sorbent dialysis systems,” Nephrology, vol. 15, No. 4, Jun. 1, 2010, pp. 406-411.
Office Action in Chinese Application No. 201510511657.9 dated May 10, 2017.
Office Action in European Application No. EP 12717021.5 dated Feb. 3, 2017.
Office Action in Chinese Application No. 201510593695.3 dated Jul. 12, 2017.
Office Action in European Application No. EP 12719170.8 dated Jan. 14, 2015.
Office Action in Japanese Application No. JP 2014-508437 dated Dec. 8, 2014.

Related Publications (1)

	Number	Date	Country
	20170100529 A1	Apr 2017	US

Provisional Applications (7)

Number	Date	Country
61480541	Apr 2011	US
61480539	Apr 2011	US
61480544	Apr 2011	US
61480528	Apr 2011	US
61480532	Apr 2011	US
61480535	Apr 2011	US
61480530	Apr 2011	US

Divisions (1)

	Number	Date	Country
Parent	13424429	Mar 2012	US
Child	15384912		US

Precision blood fluid removal therapy based on patient monitoring

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications

Disclaimer

Abstract