Dialysis technology based on relative blood volume
The dialysis system is controlled through a computer system and the ultrafiltration rate is managed based on the relative blood volume and PI process, which solves the problem of fluid volume control in dialysis, reduces complications, improves efficacy and treatment safety.
Patent Information
- Application Number
- CN202411256428.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2018-09-19
- Filing Date
- 2019-09-18
- Publication Date
- 2024-11-12
AI Technical Summary
In dialysis treatment, the prior art is difficult to effectively control the fluid volume, resulting in complications such as fluid overload and hypotension within dialysis, and conventional dialysis systems lack the ability to respond to physiological changes of patients.
The patient's relative blood volume (RBV) value is determined through a computer system, and the ultrafiltration rate (UFR) is controlled based on the RBV target information and proportional integral (PI) process to maintain the RBV within the target range, and the operation of the UF pump is adjusted to achieve UFR. Dynamic management.
Effectively reduce dialysis complications, improve patient efficacy, realize automatic and feedback-based control of the dialysis process, and improve the accuracy and safety of treatment.
Smart Images

Figure CN118942664A_ABST
Abstract
Description
[0001] This application is a divisional application of an invention patent application with an application date of September 18, 2019, application number 201980061808.1 (PCT / US2019 / 051715), and invention name “Dialysis technology based on relative blood volume”.
[0002] CROSS-REFERENCE TO RELATED APPLICATIONS
[0003] This application claims priority to U.S. Provisional Patent Application No. 62 / 733,485, filed on September 19, 2018, entitled “Ultrafiltration Control Via Blood Volume Targets,” the contents of which are incorporated herein by reference in their entirety. Technical Field
[0004] The present disclosure relates generally to a dialysis system and, more particularly, to techniques for controlling aspects of a dialysis process, such as ultrafiltration rate, based on relative blood volume. Background Art
[0005] Dialysis can be used in the treatment of kidney disease. The three main dialysis methods are hemodialysis (HD), hemodiafiltration (HDF), and peritoneal dialysis (PD). During dialysis treatment, various undesirable substances can be removed from the patient's blood, including waste products (e.g., urea), toxins, and foreign substances (e.g., prescribed drug molecules).
[0006] Proper fluid volume control is one of the main challenges of dialysis. For example, most HD patients are fluid overloaded. To avoid the long-term consequences of fluid overload, such as congestive heart failure, ventricular hypertrophy or inflammation, fluid removal via ultrafiltration is essential. However, correct management of dialysis fluid removal is required to avoid intradialytic complications, such as deleterious effects on vital organs or intradialytic hypotension (IDH). Therefore, one goal of dialysis is to achieve a fluid removal plan in which the dialysis treatment sufficiently removes undesirable interstitial fluid while avoiding removing too much fluid, thereby improving the patient's therapeutic efficacy. Summary of the invention
[0007] This Summary is provided to introduce some concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be an aid in determining the scope of the claimed subject matter.
[0008] According to various aspects of the described embodiments, there is provided an apparatus comprising at least one processor and a memory coupled to the at least one processor. The memory comprises instructions that, when executed by the at least one processor, cause the at least one processor to determine a relative blood volume (RBV) value of a patient during a dialysis process, determine ultrafiltration (UF) information based on the RBV value and RBV target information, and provide UF information to control a UF pump during the dialysis process.
[0009] In some embodiments of the device, the RBV target information includes population-based dialysis data of actual patient outcomes for a patient population associated with the patient. In various embodiments of the device, the instructions, when executed by the at least one processor, cause the at least one processor to present a graphical user interface (GUI) for performing at least one of: displaying RBV and UF information for a dialysis treatment or receiving a UF deviation range for the dialysis treatment from a user.
[0010] In some embodiments of the apparatus, the instructions, when executed by the at least one processor, cause the at least one processor to determine the UF information to maintain the RBV value within a target RBV range defined by the RBV target information. In an exemplary embodiment of the apparatus, the UF information includes one of a UF rate (UFR) or a UF target (UFG).
[0011] In various embodiments of the apparatus, the instructions, when executed by the at least one processor, cause the at least one processor to determine the UF information based on a proportional-integral (PI) process, the process variables of the PI process comprising a RBV value. In some embodiments of the apparatus, the control variables of the PI process comprise the UF information.
[0012] In an exemplary embodiment of the device, the UF information comprises a UF rate (UFR). In various embodiments of the device, the RBV target information comprises a plurality of RBV time values, each of the plurality of RBV time values comprising a target RBV range for a defined time interval during the dialysis process.
[0013] In some embodiments of the device, the instructions, when executed by the at least one processor, cause the at least one processor to determine the UF information based on at least one constraint, the at least one constraint comprising at least one of: maximum UF rate (UFR) variation, blood oxygen saturation, blood pressure, or IDH prediction. In various embodiments of the device, the instructions, when executed by the at least one processor, cause the at least one processor to provide the UF information to a UF pump controller to adjust the operation of the UF pump to achieve the UF rate (UFR).
[0014] According to various aspects of the described embodiments, a computer-implemented method is provided, comprising: determining, via a processor of a computing device, a relative blood volume (RBV) value of a patient during a dialysis process performed via a dialysis machine operably coupled to the computing device, determining ultrafiltration (UF) information based on the RBV value and RBV target information, and providing the UF information to control a UF pump during the dialysis process.
[0015] In an exemplary embodiment of the method, the RBV target information includes population-based dialysis data of actual patient outcomes for a patient population associated with the patient. In some embodiments of the method, the method includes determining the UF information to maintain the RBV value within a target RBV range defined by the RBV target information. In various embodiments of the method, the UF information includes one of a UF rate (UFR) or a UF target (UFG).
[0016] In some embodiments of the method, the RBV target information includes a plurality of RBV time values, each of the plurality of RBV time values including a target RBV range for a defined time interval during the dialysis process. In various embodiments of the method, the method includes determining the UF information based on at least one constraint, the at least one constraint including at least one of: maximum UF rate (UFR) change, blood oxygen saturation, blood pressure, or IDH prediction.
[0017] According to various aspects of the described embodiments, there is provided a computer-implemented method for performing a dialysis process using relative blood volume (RBV) based ultrafiltration (UF) control, the method comprising: receiving, via a processor of a computing device operably coupled to a dialysis machine performing the dialysis process, RBV target information including population-based dialysis data of actual patient outcomes for a patient population associated with a patient, determining an RBV value for the patient during the dialysis process, comparing the RBV value to the RBV target information, and determining UF information to control a UF pump of the dialysis machine to maintain the RBV value within a target RBV range defined by the RBV target information.
[0018] In some embodiments of the method, controlling the pump includes adjusting the operation of the UF pump to achieve a UF rate (UFR). In some embodiments of the method, the method includes determining UF information to maintain the RBV value within a target RBV range defined by the RBV target information. In various embodiments of the method, the UF information includes a UF target (UFG). In some embodiments of the method, the RBV target information includes a plurality of RBV time values, each of the plurality of RBV time values including a target RBV range for a defined time interval during a dialysis process.
[0019] According to various aspects of the described embodiments, a computer-implemented method of performing a dialysis treatment is provided, the method comprising: determining, via a processor of a computing device, a relative blood volume (RBV) value of a patient during the dialysis treatment, comparing the RBV value to RBV target information, and adjusting an ultrafiltration rate (UFR) of the dialysis treatment to maintain future RBV values of the patient within a RBV target range during the dialysis treatment.
[0020] In some embodiments of the method, wherein the RBV target information includes population-based dialysis data of actual patient outcomes for a patient population associated with the patient. In various embodiments of the method, wherein adjusting the UFR includes adjusting the rate of a UF pump used to perform the dialysis treatment. In some embodiments of the method, wherein adjusting the UFR includes increasing the UFR. In an exemplary embodiment of the method, wherein adjusting the UFR includes decreasing the UFR. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] By way of example, specific embodiments of the disclosed machine will now be described with reference to the accompanying drawings, in which:
[0022] Figure 1 An example of a first operating environment that may be representative of some embodiments of the present disclosure is shown.
[0023] Figure 2 Target relative blood volume (RBV) information is shown in accordance with some embodiments.
[0024] Figure 3 Target relative blood volume (RBV) information is shown in accordance with some embodiments.
[0025] Figure 4 A proportional-integral (PI) control element is shown in accordance with some embodiments.
[0026] Figure 5 Target relative blood volume (RBV) information is shown in accordance with some embodiments.
[0027] Fig. 6A and6B Depicted is a RBV-based ultrafiltration (UF) controller graphical user interface (GUI) according to some embodiments.
[0028] Figure 7 Depicted is a RBV based UF control display GUI according to some embodiments.
[0029] Figure 8 A first logic flow is shown according to some embodiments.
[0030] Fig. 9 A second logic flow is shown according to some embodiments.
[0031] Figure 10-29 Graphic information from the Intradialytic RBV All-Cause Mortality Study is depicted.
[0032] Figures 30A-30C Graphical information depicting an In-Silico case study.
[0033] Figures 31A-31D Graphic information depicting clinical pilot studies.
[0034] Fig.32 An example hemodialysis system is shown.
[0035] Fig.33 One embodiment of a computing architecture according to the present disclosure is shown. DETAILED DESCRIPTION
[0036] The present embodiment will now be described more fully below with reference to the accompanying drawings, in which a plurality of exemplary embodiments are shown. However, the subject matter of the present disclosure can be implemented in many different forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided so that the present disclosure will be thorough and complete, and it is intended that the scope of the present subject matter be conveyed to those skilled in the art. In the accompanying drawings, identical or similar reference numerals always represent identical or similar elements.
[0037] Fluid management is one of the main functions of hemodialysis, but the progressive increase in the average age and comorbidities of patients receiving this therapy is associated with a reduced clinical condition and tolerance to treatment. The short duration of each HD session leads to the risk of intradialytic morbid events and ultimately to inadequate achievement of fluid removal. For example, in most HD sessions, the ultrafiltration rate (UFR) exceeds the refilling rate of fluid from the interstitium to the vascular space, resulting in a decrease in blood volume, potentially exacerbating intradialytic hypotension (IDH) and reduced refilling of vital organs. During conventional HD treatment, 20-50% of patients with end-stage renal disease (ESRD) are affected by symptomatic IDH. This is directly reflected in morbidity, as many patients leave treatment due to persistent fluid overload, which ultimately translates into hypertension, left ventricular hypertrophy, pulmonary congestion, inflammation and premature death.
[0038] Clinical assessment has been the basis for deciding how much fluid to remove during each treatment, but this approach is widely considered to be suboptimal. A variety of techniques have been proposed for objectively assessing fluid status, including measurement of relative blood volume (RBV). RBV devices measure changes in the intravascular fluid status of blood passing through the dialysis line by monitoring the concentration of whole blood components, such as hemoglobin or hematocrit. These blood concentration markers can effectively monitor real-time relative changes in blood water concentration, providing the possibility of preventing IDH and improving fluid management. RBV decreases with increasing ultrafiltration (UF), and the higher the UF rate, the greater the rate of decline of the RBV curve.
[0039] Thus, various embodiments may generally be directed to systems, methods, and / or apparatus for performing a dialysis process in which patient fluid may be removed based at least in part on RBV. In some embodiments, UF characteristics such as UF rate (UFR), UF target (UFG), and / or similar characteristics may be determined at various time periods during the dialysis process to maintain the patient's RBV at a target RBV value or range during treatment. As described in more detail in this specific embodiment, a patient's intradialytic RBV may be associated with the morbidity of dialysis patients (e.g., see Case Study 1: Intradialytic RBV All-Cause Mortality Study). For example, a specific intradialytic RBV range may be associated with all-cause mortality in HD patients (e.g., see Case Study 1: Intradialytic RBV All-Cause Mortality Study). Therefore, maintaining the intradialytic RBV at a target RBV value or range at different time periods during dialysis treatment according to various embodiments can reduce or even eliminate certain dialysis complications, thereby improving patient outcomes.
[0040] For example, in some embodiments, UF rate feedback controller device software has been developed that uses the Fresenius 2008T hemodialysis machine and The device provides information in real time to identify the appropriate relative blood volume (RBV) trajectory for each patient (input), thereby directing the UF rate (output) to a beneficial target within a range of RBV. These ranges are based on previously observed data.
[0041] For example, as described in more detail below in Case Study 1: Intradialysis RBV All-Cause Mortality Study, a range of RBV associated with significantly improved survival can be determined. In Case Study 1, a retrospective (January 2012 to December 2016) multicenter (17 clinics of the National Kidney Research Institute) cohort study of prevalent chronic HD patients was conducted (e.g., see Case Study 1: Intradialysis RBV All-Cause Mortality Study). After a 6-month baseline period, patients were followed up until the end of the study period. A Crit-Line monitor (CRM), which provides hematocrit (Hct) readings every minute and is the standard of care at the RRI clinic, was used to obtain RBV readings. RBV was calculated based on the change in Hct according to RBV(t)[%] = 100·Hct(0) / Hct(t) (where Hct(0) is the initial Hct and Hct(t) is the current Hct). RBV levels at 1, 2, and 3 hours after treatment were defined as the mean RBV between 50 and 70 minutes, 110 to 130 minutes, and 170 to 190 minutes, respectively. The relationship between all-cause mortality and RBV was analyzed using a Cox proportional hazards model with spline terms for RBV at these three hourly time points, which enabled the identification of hourly RBV ranges associated with significantly improved survival.
[0042] Conventional dialysis systems typically use static UFR and / or UFG. For example, a standard dialysis system may use a UFR variation characteristic that is set at the beginning of treatment to deliver UFR without considering any physiological feedback. Therefore, conventional systems lack the ability to automatically respond to physiological changes in patients during the dialysis process, such as plasma refilling and hemodynamic changes. In addition, alternative conventional dialysis methods are not configured to control UFR and / or UFG based on RBV, particularly a target RBV range that has been shown to provide improved patient efficacy.
[0043] Thus, the described embodiments may provide a variety of technical features and advantages over conventional systems, including improvements in computing technology. A non-limiting example of a technical advantage may include providing automatic, feedback-based control of dialysis UF, such as UFR and / or UFG, for the dialysis process based on physiological characteristics of the patient, including intra-dialytic RBV. For example, a logic device configured to manage the dialysis process may be a controller or may include a controller that can be used to receive a patient's RBV information during a time period of dialysis treatment and determine UFR and / or UFG to achieve a specific patient RBV. Another non-limiting example of a technical advantage may include controlling UF based on RBV information derived from population-based dialysis data of real patient outcomes during dialysis treatment, thereby improving patient dialysis treatment outcomes (e.g., see Figure 2 and 3 ). In this manner, embodiments may provide additional non-limiting technical advantages of performing dialysis via delivery of UF that allows for removal of prescribed UF volumes while minimizing intradialytic complications and maximizing long-term patient outcomes in a more efficient and accurate process than is achievable with conventional methods.
[0044] In this specification, many specific details such as components and system configurations may be set forth in order to provide a more thorough understanding of the described embodiments. However, those skilled in the art will recognize that the described embodiments may be practiced without such specific details. In addition, some well-known structures, elements, and other features are not shown in detail to avoid unnecessarily obscuring the described embodiments.
[0045] In the following description, references to "one embodiment," "an embodiment," "example embodiment," "various embodiments," etc., indicate that one or more embodiments of the technology described thus may include a particular feature, structure, or characteristic, but more than one embodiment may, and not every embodiment necessarily, include the particular feature, structure, or characteristic. Furthermore, some embodiments may have some, all, or none of the features described for other embodiments.
[0046] As used in this specification and the claims, unless otherwise stated, the use of ordinal adjectives "first", "second", "third", etc. to describe elements merely indicates that specific instances of the elements or different instances of similar elements are being referenced, and does not mean that the elements so described must be in a specific order in time, space, sequence, or in any other manner.
[0047] Figure 1 An example of an operating environment 100 that may represent some embodiments is shown. Figure 1As shown, the operating environment 100 may include a dialysis system 105 associated with a dialysis machine 170. In some embodiments, the dialysis machine 170 may include various components, such as a UF pump 172. In various embodiments, the dialysis machine 170 may be or may include an HD dialysis system. For example, the dialysis machine 170 may be or may include a Fresenius 2008T HD machine available from Fresenius Medical Care, Inc. of Waltham, Massachusetts, United States of America. Although HD is used in the examples in this specific embodiment, the embodiments are not limited thereto, as other types of dialysis systems and treatments that can be performed according to some embodiments are contemplated herein.
[0048] In various embodiments, the dialysis system 105 may include a computing device 110 communicatively coupled to a dialysis machine 170. The computing device 110 may be configured to manage operational aspects of the dialysis machine 170, for example, to perform dialysis treatment on a patient. Figure 1 Only one computing device 110 and dialysis machine 170 are depicted in the figure, but the embodiments are not limited in this regard. In various embodiments, the functions, operations, configurations, data storage functions, applications, logic units, and / or the like described in conjunction with the computing device 110 may be executed and / or stored in one or more other computing devices (not shown) coupled to the computing device 110, for example, via the network 150 (e.g., network nodes 152a-n). A single computing device 110 and dialysis machine 170 are depicted for illustrative purposes only to simplify the drawings. For example, the computing device 110 may be operable to partially or fully operate a dialysis process of multiple dialysis machines 170 coupled to the computing device 110, for example, via the network 150. The embodiments are not limited in this regard.
[0049] The computing device 110 may include a transceiver 140, a display 142, an input device 144, and / or a processor circuit 120 communicatively coupled to a memory unit 130. According to some embodiments, the processor circuit 120 may be, may include, and / or may have access to various logic units for performing processes. For example, the processor circuit 120 may include and / or may have access to a dialysis logic unit 122 and / or a RBV-based UF control logic unit 124. The processing circuit 120, the dialysis logic unit 122, and / or the RBV-based UF control logic unit 124, and / or portions thereof may be implemented in hardware, software, or a combination thereof. As used in this application, the terms "logic unit," "component," "layer," "system," "circuit," "decoder," "encoder," "control loop," and / or "module" are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution, examples of which are provided by the exemplary computing architecture 3300. For example, a logic unit, circuit, or module may be and / or may include, but is not limited to, a process running on a processor, a processor, a hard drive, multiple storage drives (of optical and / or magnetic storage media), an object, an executable file, an execution thread, a program, a computer, a hardware circuit, an integrated circuit, an application specific integrated circuit (ASIC), a programmable logic device (PLD), a digital signal processor (DSP), a field programmable gate array (FPGA), a system on a chip (SoC), a memory cell, a logic gate, a register, a semiconductor device, a chip, a microchip, a chipset, a software component, a program, an application, firmware, a software module, computer code, a control loop, a proportional integral derivative (PID) controller, a combination of any of the foregoing, and / or the like.
[0050] Despite Figure 1 In the embodiment, the dialysis logic unit 122 and the RBV-based UF control logic unit 124 are depicted as being within the processor circuit 120, but the embodiments are not limited thereto. For example, the dialysis logic unit 122, the RBV-based UF control logic unit 124, and / or any of its components may be located within an accelerator, a processor core, an interface, a separate processor chip, which is fully implemented as a software application (e.g., a dialysis application 136), and / or the like. In some embodiments, the computing device 110 and / or its components may be an embedded or integrated component of a dialysis machine. For example, the processor circuit 120, the dialysis logic unit 122, the RBV-based UF control logic unit 124, and / or portions thereof may be arranged in a dialysis machine 170 or otherwise integrated into the dialysis machine 170.
[0051] The memory unit 130 may include various types of computer-readable storage media and / or systems in the form of one or more higher speed memory cells, such as read-only memory (ROM), random access memory (RAM), dynamic RAM (DRAM), double data rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, polymer memory, such as ferroelectric polymer memory, austenite memory, phase change or ferroelectric memory, silicon oxide-nitride-oxide, etc. The memory unit 130 may include a silicon-on-silicon (SONOS) memory, a magnetic card or an optical card, an array device such as a redundant array of independent disks (RAID) drive, a solid-state memory device (e.g., a USB memory, a solid-state drive (SSD), and any other type of storage medium suitable for storing information. In addition, the memory unit 130 may include various types of computer-readable storage media in the form of one or more low-speed memory units, including an internal (or external) hard disk drive (HDD), a magnetic floppy disk drive (FDD), and an optical disk drive for reading or writing from a removable optical disk (e.g., a CD-ROM or DVD), a solid-state drive (SSD), and / or the like.
[0052] The memory unit 130 can store dialysis information 132 and / or RBV information 134. In some embodiments, the dialysis information 132 may include information generated during the dialysis process, including operating information and / or patient physiological information of the dialysis machine 170. The operating information may include UFR, UFG, treatment time, operating parameters, and / or the like. The patient physiological information may include temperature, heart rate, RBV, blood oxygen saturation, blood pressure, intradialytic hypotension (IDH) information (e.g., predicted IDH information), and / or the like. Embodiments are not limited thereto.
[0053] In various embodiments, the dialysis machine 170 may be operably coupled to various patient monitoring devices 174a-n for monitoring various physiological characteristics of a patient undergoing dialysis treatment. For example, the monitoring devices 174a-n may be or may include blood volume (BV) monitoring devices and / or Crit-1® monitors such as those available from Fresenius Medical Care, Inc. of Waltham, Massachusetts, United States of America. In some embodiments, the monitoring devices 174a-n may include a hematocrit measurement device of a monitor (CLM). Typically, the CLM may be an online monitor for measuring changes in hematocrit, blood oxygen saturation, and / or blood volume during dialysis treatment. Although a CLM may be used in some examples, the embodiments are not limited thereto as any technology, device, apparatus, system, process, and / or the like for measuring and / or predicting a patient's physiological characteristics such as BV and / or RBV that is capable of operating in accordance with some embodiments is contemplated herein. In various embodiments, the monitoring devices 174a-n may include a fluid management monitoring tool, such as available from Fresenius Medical Care, Inc. of Waltham, Massachusetts, United States of America. device. The devices may non-invasively measure certain patient physiological characteristics, such as absolute hematocrit and continuous oxygen saturation. Thus, in some embodiments, the information monitored by one or more of the monitoring devices 174a-n may be or may be used to determine the RBV and / or other physiological characteristics of the patient during dialysis treatment.
[0054] In some embodiments, the target RBV information 134 may include an expected RBV value for a particular patient during a dialysis treatment. In some embodiments, the target RBV information 134 may be or may include population-based RBV information. In various embodiments, the population-based RBV information may be or may include a RBV range for improving patient outcomes based on various factors, including but not limited to hazard ratios (HR), morbidity, mortality, complication rates, and / or the like. In various embodiments, the target RBV information may include a target RBV range for a time period of a dialysis process.
[0055] refer to Figure 2 , which depicts a graph 205 of illustrative target RBV information in the form of a RBV curve 210. Figure 2 As shown, the RBV curve 210 may include target RBV ranges 212a-f, one for each time period 214a-f. Although the time periods 214a-f are in half-hour increments, according to some embodiments, the time periods 214a-f may have any duration, including but not limited to 10 seconds, 30 seconds, 1 minute, 5 minutes, 10 minutes, 15 minutes, 20 minutes, 30 minutes, 45 minutes, 1 hour, 1 hour and 30 minutes, 2 hours, and any value or range between any two of these values (including the endpoints).
[0056] In various embodiments, the target RBV ranges 212a-f may include favorable RBV ranges determined from a patient population, for example, in one or more clinical trials. In some embodiments, the target RBV ranges 212a-f may include RBV values for a patient population having an improved HR, for example, an HR below a threshold, such as an HR of all-cause mortality <1.0.
[0057] refer to Figure 3 , which depicts a graph 305 of illustrative target RBV information. Figure 3 As shown, a target RBV range, such as target RBV ranges 212a-f, can be used to generate a target region or "pipe of good fortune" 310 by connecting the top of the range 212a-f and the bottom of the range. In some embodiments, target RBV curve 312 can be determined, for example, as a straight line or substantially straight line through the range of target region 310, or otherwise fit to a median or average value through the range of target region 310.
[0058] The population used to generate the target RBV information 134 may have various characteristics, such as age, gender, disease state, fluid removal, complications, and / or the like. In various embodiments, the target RBV information 134 may include, for example, multiple RBV curves and / or ranges, each of which is associated with a specific set of population characteristics. Therefore, in some embodiments, patients undergoing dialysis treatment according to some embodiments may use target RBV information associated with their individual characteristics, subgroups, and / or the like. For example, a 60-year-old female patient may use an RBV curve 312 determined for a female patient between the ages of 50 and 60. The embodiment is not limited thereto. In various embodiments, the RBV-based UF control logic unit 124 may receive patient information (e.g., physical information, disease information, historical treatment information, and / or the like), and determine one or more optimal target RBV curves, ranges, or other structures to be used for RBV-based UF control during patient treatment. In general, according to some embodiments, the RBV-based UF control logic unit 124 may operate as a feedback controller designed to steer the patient's RBV curve into a predefined target range during dialysis treatment.
[0059] In various embodiments, the dialysis logic unit 122 can be operated to perform a dialysis process, such as HD treatment, on a patient via a dialysis machine 170, for example, via a dialysis application 136. For example, the dialysis logic unit 122 can receive dialysis treatment information such as patient characteristics, dialysis prescription information, and / or the like to perform a dialysis process on the patient. The RBV-based UF control logic unit 124 can be operated to perform computer-assisted UF control by managing UF characteristics during dialysis treatment based on the patient's RBV value and target RBV information. The UF characteristics can include UFR and / or UFG. In some embodiments, the RBV-based UF control logic unit 124 can be operated, for example, via a dialysis application 136 to control the UF pump 172 to achieve the target UF characteristics.
[0060] In some embodiments, the UF control logic unit 124 may be or may include a control element, such as a PID control loop. Figure 4 PI control loop information according to some embodiments is depicted. In various embodiments, the PI control loop may determine UFR at time t(u(t)) according to equation 402, which has a proportional gain term 404 graphically depicted in graph 405 and an integral gain term 406 graphically depicted in graph 410. Embodiments are not limited in this regard.
[0061] The PID controller can continuously acquire an error value (the deviation of the (measured) process variable from the desired value) to adjust the control variable so that the process variable follows the desired value. In some embodiments, the PID controller can operate as a PI controller (e.g., a PID controller with the derivative (D) term set to zero). In some embodiments, the process variable is the patient's RBV level (e.g., calculated based on the patient's hematocrit value (physiological variable)) and the adjusted control variable is the UF rate. Typically, a PI controller operates in such a way that if the process variable decreases when the control variable increases, then if the process variable is greater than the desired value, the control variable will increase, and vice versa. The PI controller has two terms to calculate the size of the adjustment: the proportional term 404 only considers the error value at the current point in time, while the integral term 406 considers the history of errors by summing all previously measured errors. Both terms have gains (proportional gain and integral gain) to adjust performance.
[0062] Therefore, in some embodiments, the RBV-based UF control logic unit 124 can operate a closed-loop controller with the patient's RBV value as a feedback variable. For example, the RBV-based UF control logic unit 124 can set the UFR for the UF pump 172 (e.g., starting from an initial value). The patient's RBV value can be continuously monitored and provided to the RBV-based UF control logic unit (e.g., a PID or PI control loop) and compared with the target RBV information. The RBV-based UF control logic unit 124 can adjust the UFR to set or maintain the patient's RBV within the target RBV range within a specific time period.
[0063] In some embodiments, the RBV-based UF control logic 124 may fully automate UF control. In various embodiments, operator assistance may be used to confirm or change the UFR and / or UFG values determined by the RBV-based UF control logic 124. For example, the RBV-based UF control logic 124 may determine at the 1 hour mark that the UFR should be increased from x to y. A graphical user interface (GUI) prompt, alarm, message, or other signal may be used to prompt a nurse or other operator to verify the increase (e.g., see Fig. 6A , 6B and 7). Alternatively, the operator may input a specific UFR range or other operating parameters, such as a UFR change threshold, a UFG range, and / or the like.
[0064] In various embodiments, the RBV-based UF control logic unit 124 may operate under various constraints, such as PID controller constraints, to reduce or even eliminate the negative consequences of changing the UFR. Non-limiting examples of constraints may include UF boundaries (e.g., see Figure 5 ), UFR change threshold, blood oxygen saturation, blood pressure and / or (predicted) IDH. In some embodiments, the UFR change threshold may include a maximum relative change in UFR (e.g., + / - 75% of the prescribed UFR) and / or a maximum allowed change in UFR (e.g., maximum ml / hour change). Figure 5 Depicted is a graph 505 showing illustrative UFR variation limits or boundaries for advantageous tube 520 relative to a prescribed UFR within advantageous tube 510 and outside advantageous tube 515 according to some embodiments. Table 1 depicts the information of graph 505 in tabular form:
[0065]
[0066] Table 1
[0067] As long as the patient's RBV remains within the favorable tube 310, the patient's RBV will pass through the RBV target range. Therefore, if the RBV is inside the favorable tube 310, the controller (e.g., the RBV-based UF control logic unit 124) can be configured to be able to make only minor adjustments to the UF rate. The maximum allowable change in UFR can be defined as a percentage of a specified UFR and / or absolute UFR increase / decrease. For example, outside the favorable tube 310, larger adjustments may be allowed because these may be necessary to get the patient's RBV into the favorable tube. Based on relative limits, the controller can be programmed to observe the parameters defined in Table 1.
[0068] Thus, in some embodiments, the maximum allowed UFR variation may be reduced as treatment progresses. For example, in the final stages of treatment (>180 minutes), the controller may only increase the UFR by a maximum of 5%. However, a substantial reduction in the RBV at a UF rate below the target line (up to 35%) is permitted in order to place the RBV within the desired range, since a reduction in the UFR is associated with improved hemodynamic stability and may pose little or no risk to the patient.
[0069] In some embodiments, the dialysis information 132 may include constraint information for the treatment process, such as which constraints are in effect, thresholds, constraint actions, and / or the like. For example, the dialysis information 132 may indicate Figure 5 The UFR change limits depicted in are effective, and if the UFR change is determined by the RBV-based UF control logic unit 124 to be beyond the allowable range, one or more constraint actions are to be taken. For example, the constraint action can be to maintain the previous UFR, reach the maximum / minimum UFR within the allowed threshold (for example, if the threshold UFR change is +20%, and the determined UFR change is +30%, then perform a maximum 20% change), trigger an alarm, a combination thereof, and / or the like. The embodiment is not limited to this.
[0070] For example, for blood oxygen saturation constraints, the RBV-based UF control logic unit 124 can prevent the UFR from being increased in the event of low (e.g., below an absolute threshold) and / or declining blood oxygen saturation levels (e.g., a percentage change over a specified duration). For example, for catheter-based central venous oxygen saturation, an absolute threshold of approximately 44% over 5 minutes and a relative threshold of 7% can be used. In another example, for AVF arterial oxygen saturation, an absolute threshold of approximately 86% over 5 minutes and a relative threshold of 5% can be used. The embodiments are not limited to this. Generally, arterial oxygen saturation below 86% and central venous oxygen saturation below 44% for at least 5 minutes can be considered "low", and a decrease in blood oxygen saturation of more than 5 percentage points (for central venous oxygen saturation) or more than 7 percentage points (for arterial oxygen saturation) over the previous 5 minutes can be considered "declining".
[0071] In another example, for blood pressure constraints, the RBV-based UF control logic unit 124 can constrain changes in UFR based on absolute blood pressure values and / or blood pressure trends (e.g., changes over a period of time). For example, the RBV-based UF control logic unit 124 can allow UFR adjustments that are otherwise allowed within a specified threshold blood pressure range. Outside the specified threshold blood pressure range, the RBV-based UF control logic unit 124 can allow an increase in UFR, but not a decrease in UFR.
[0072] In another example, an IDH constraint may be used based on a predicted IDH (e.g., an IDH predicted at a specific time interval such as every 1 minute to 30 minutes). In various embodiments, the RBV-based UF control logic unit 124 may reduce the UF rate in response to a (predicted) IDH value being outside a threshold.
[0073] In some embodiments, the RBV-based UF control logic unit 124 may perform various validations on all user-supplied inputs to ensure that they are reasonable. Any UF rate suggested by the controller may be within the initially defined hard limits (UFR and UFG deviation). In some embodiments, if the prescribed UFG violates an internal UFR upper limit, such as 13 mL / kg / hour, the RBV-based UF control logic unit 124 may be disabled or suspended.
[0074] In various embodiments, the RBV-based UF control logic unit 124 may perform internal checks on its operation. If an initial UFR recommendation cannot be calculated (e.g., due to insufficient data availability), or if any calculation fails these internal checks, then no UFR recommendation may be generated and the RBV-based UF control logic unit 124 may automatically enter a fallback mode. In the fallback mode, the RBV-based UF control logic unit 124 may recommend continuing treatment with the current UFG settings.
[0075] For example, data received from patient monitoring devices 174a-n, such as The data is pre-processed so that no UFG or UFR recommendations are based on erroneous or questionable data. In some embodiments, the RBV-based UF control logic unit 124 may not recommend any changes in the UF rate if the required input data is insufficient. In addition, there is an option to prevent the controller from recommending an increase in the UF rate in the event of a low or declining blood oxygen saturation level. The nurse can turn this option on or off in the GUI. Other constraints described herein may also limit or disable changes to UFG and / or UFR.
[0076] In various embodiments, the dialysis application 136, alone or in conjunction with the dialysis logic unit 122 and / or the RBV-based UF control logic unit 124, may provide various GUI interfaces for presenting and / or receiving information related to RBV-based UF control of dialysis treatments. Fig. 6A and 6B Depicted is a UF controller input GUI interface 605 according to some embodiments. Fig. 6A and 6B As shown, the UF controller input GUI interface 605 may include objects for receiving treatment parameters, such as ultrafiltration (e.g., UFG) deviation value 620, weight 622, update interval 624, and / or the like. Fig. 6A and 6B , this is because an input / data object that receives and / or displays any type of information for RBV-based UF control of dialysis treatments may be presented via the UF controller input GUI interface 605. Figure 7Depicted is a RBV-based UF control GUI interface 705 according to some embodiments. The RBV-based UF control GUI interface 705 may be configured to be capable of presenting information associated with RBV-based UF control during dialysis treatment, such as a graph 710 of RBV versus time, an original UF target 720, a suggested UF target (e.g., determined by the RBV-based UF control logic unit 1240), an original UF time 724, an actual UF time 726, a suggested UFR 727, and an actual UFR 730. In this manner, an operator, such as a nurse, may view and manage RBV-based UF control in real time or substantially in real time.
[0077] Included herein are one or more logic flows representing exemplary methods for executing novel aspects of the disclosed architecture. Although one or more methods herein are shown and described as a series of actions for the purpose of simplicity of explanation, it will be understood and appreciated by those skilled in the art that these methods are not limited by the order of actions. Accordingly, some actions may occur in a different order and / or simultaneously with other actions than those shown and described herein. For example, it will be understood and appreciated by those skilled in the art that methods may alternatively be represented as a series of interrelated states or events, such as in a state diagram. In addition, for novel implementations, all of the behaviors shown in the method may not be required. The blocks designated by dashed lines may be optional blocks of the logic flow.
[0078] The logic flow may be implemented in software, firmware, hardware, or any combination thereof. In software and firmware embodiments, the logic flow may be implemented by computer executable instructions stored on a non-transitory computer readable medium or machine readable medium. The embodiments are not limited thereto.
[0079] Figure 8 One embodiment of a logic flow 800 is shown. The logic flow 800 may represent some or all of the operations performed by one or more embodiments described herein, such as the computing device 110 and / or its components. In some embodiments, the logic flow 800 may represent some or all of the operations of determining RBV variation characteristics for a patient according to some embodiments.
[0080] At block 802, the logic flow 800 may determine population-based RBV information 802. In some embodiments, the population-based RBV information 802 may be or may include target RBV information for a particular population determined based on one or more analyses, such as the target RBV curve 312. In some embodiments, the analyses may include real-world clinical trials (e.g., see Case Study 1: In-dialysis RBV All-Cause Mortality Study), In-Silico clinical trials (e.g., see Case Study 2: In-Silico Case Study), combinations thereof, and / or the like. For example, a clinical trial of RBV ranges and patient efficacy may be performed to determine one or more target RBV curves for a population, subgroups, and / or the like. The subgroups may include any type of groupable grouping of the clinical trial population, such as age, gender, comorbidities (e.g., congestive heart failure, diabetes, UFG, and / or the like). Thus, in some embodiments, the target RBV information 132 may include a library of target RBV ranges or curves that may be associated with individual patients based on the patient's physical characteristics, treatment regimen, and / or the like. In some embodiments, the RBV information 132 may be stored locally, for example, in the memory 130 of the computing device 110. In other embodiments, the RBV information 132 may be accessed via a network, cloud, or other storage environment. In this manner, a patient being treated at a particular location may be able to be treated using a wide range of RBV target structures to determine the best match for that patient.
[0081] At block 804 , the logic flow 800 may determine dialysis information. For example, dialysis information 132 such as patient characteristics, dialysis prescription information, treatment parameters, RBV-based UF control parameters, constraint information, and / or the like may be accessed by the RBV-based UF control logic unit 124 .
[0082] At block 806, the logic flow 800 may determine RBV variation characteristics. For example, the RBV-based UF control logic unit 124 may determine an RBV target curve 312 corresponding to the patient from the target RBV information library. For example, an RBV target curve 312 may be determined that matches or substantially matches the patient characteristics or patient subgroup characteristics.
[0083] At block 808, the logic flow 800 may perform dialysis using RBV-based UF control based on the RBV variation characteristics. For example, the dialysis application 136 may perform dialysis operations via the dialysis machine 170, wherein the RBV-based UF control operations are used to maintain the patient RBV value within the range specified by the target RBV curve determined in block 808. In this manner, patients may receive dialysis treatment using RBV-based UF control optimized for their individual or subgroup characteristics.
[0084] Fig. 9 One embodiment of a logic flow 900 is shown. The logic flow 900 may represent some or all of the operations performed by one or more embodiments described herein, such as the computing device 110, the dialysis machine 170, and / or component parts thereof. In some embodiments, the logic flow 900 may represent some or all of the operations of performing a dialysis treatment according to some embodiments.
[0085] At box 902, a dialysis treatment can be started by the logic flow 900. For example, the dialysis logic unit 122 can start a dialysis treatment process for a patient using the dialysis machine 170 via the dialysis application 136. The dialysis process can start with an initial UFG and UFR. In some embodiments, RBV-based UF control can be initialized on the computing device 110. Various dialysis information 132 can be provided to the computing device, for example, at specific time intervals (e.g., every 0.5 seconds to 10 minutes) or frequencies (e.g., 0.5Hz to 5.0Hz). Non-limiting examples of dialysis information 132 from the dialysis machine 170 can include HD machine timestamp, HD machine ID, patient ID, UF rate, cumulative UF volume, UF target, amount of blood processed, blood pressure (BP), remaining dialysis time, remaining UF time and / or the like. It can also be obtained from devices such as CLM and / or The patient monitoring devices 174a-n of the apparatus receive the dialysis information 132. Illustrative and non-limiting examples of the dialysis information from the patient monitoring devices 174a-n may include timestamps, counters, hematocrit, hemoglobin concentration, oxygen saturation, blood volume information, vital sign information, and / or the like. In some embodiments, the dialysis information 132 from the dialysis machine 170 and the patient monitoring devices may be processed by the RBV-based UF control logic unit 124 to calculate a recommended UFG and / or UFR to guide the patient's RBV into a target RBV range.
[0086] The prescribed UFR is the prescribed UFG or UF volume divided by the total treatment time. In some embodiments, the dialysis information 132 may include the patient's previous post-treatment HD weight, and optionally the maximum allowed deviation (+ / -) in the prescribed UFG (e.g., per clinic policy, + / - approximately 1000 mL).
[0087] At box 904, the logic flow 900 can determine whether the evaluation period has expired. For example, the patient RBV can be checked at discrete time intervals, such as every minute to every 20 minutes. In some embodiments, the evaluation period can be approximately 10 minutes. In some embodiments, the evaluation period can be different based on the stage or duration of the dialysis treatment. For example, the first evaluation period can be approximately 15 minutes, followed by 10 minute intervals for the remaining dialysis treatments. The embodiments are not limited to this.
[0088] At block 906, the logic flow 900 may determine the patient RBV value. For example, the RBV-based UF control logic unit 124 may determine the patient RBV value based on, for example, dialysis information obtained from the patient monitoring devices 174a-n. In some embodiments, the patient RBV value may be determined based on, for example, The RBV value may be determined by a patient's hematocrit value determined by a PCR or similar device. The patient's RBV value may include the patient's RBV at a specific time interval.
[0089] At block 908, the logic flow 900 may determine UF information. For example, the RBV-based UF control logic unit 124 may determine a recommended UFG, for example, via a PI control loop. The RBV-based UF control logic unit 124 may determine the recommended UFG based on the target RBV information 134 (such as the target RBV curve 312) so that the patient RBV is within the target RBV range at a specific time interval.
[0090] In some embodiments, the logic flow 900 may consider one or more constraints when determining the UF information. For example, based on the patient's RBV value, the RBV-based UF control logic unit 124 may determine to increase the UFG by 10%. However, if, for example, the patient's blood pressure is outside of a threshold, a blood pressure constraint may prevent the increase. If a constraint is triggered, a recommended UFG may be generated based on a constraint action, which may include maintaining the current UFG.
[0091] At block 910, the logic flow 900 may change the UFR to achieve the UFG determined in block 908. In some embodiments, the recommended UFR may be determined based on the recommended UFG and the remaining time of the dialysis treatment (e.g., the UFR required to meet the recommended UFG within the remaining time). For example, the RBV-based UF control logic unit 124 may change the operation of the UF pump 172 alone or in combination with the dialysis application 136 to change the UFR. In some embodiments, due to constraints and / or the recommended UFR change being outside of a maximum change threshold (e.g., see Tables 1 and 2), the recommended UFR may be changed. Figure 5 ), the change in UFR can be rejected.
[0092] In some embodiments, operator intervention may be required to change the UFR or other UF operating parameters. In such embodiments, the operator may be reminded that a change in a UF operating parameter, such as the UFR, is being recommended. For example, from 60 seconds before each scheduled update time point (or evaluation period) to 60 seconds after, the "Update Controller" button on the GUI may be accompanied by an acoustic signal flashing to remind the operator (e.g., dialysis nurse) that the controller is ready to attempt to generate a UF rate recommendation for evaluation and (if applicable) implementation. When the operator selects the "Update Controller" button, the GUI displays the updated UFR and the corresponding UFG (based on the remaining UF time). The operator then decides whether to implement the recommendation. In order to implement the controller's recommendation, in some embodiments, the operator can enter the recommended UFG (rather than the UFR) into the HD machine (e.g., via GUI 605) (changing the UFR on the machine may cause the treatment time to be adjusted while maintaining the UFG, which is not desirable). Changing the UFG always keeps the remaining treatment time unchanged and adjusts the UF rate, which is a desired change.
[0093] Rather than entering the controller's recommendation, the operator may also decide to enter a different UFG or UFR or make no changes at all. If the operator misses pressing the "Update Controller" button during the allowed time period, the UF rate will remain unchanged (again, unless the nurse decides to implement a change) and the controller will generate a new UF rate recommendation at the next regularly scheduled update time point.
[0094] Thus, if the operator accepts the recommended UF target at block 912, the logic flow may change the UFR to achieve the UFG at block 910. Otherwise, at block 914, the logic flow may maintain the previous UFR (and UFG).
[0095] Case Study 1: All-cause mortality study of intradialytic RBV
[0096] The Intradialytic RBV All-Cause Mortality Study was conducted to determine the association between intradialytic RBV and mortality.
[0097] In the Intradialytic RBV All-Cause Mortality Study, RBV was recorded every minute during a 6-month baseline period; all-cause mortality was recorded during the follow-up period. RBV at 1, 2, and 3 hours (h) into HD served as a predictor of all-cause mortality during the follow-up period. Specifically, 842 patients were studied. During the follow-up period (median 30.8 months), 249 patients (29.6%) died. The following hourly RBV ranges were associated with improved survival: first hour, 93-96% (hazard ratio (HR) 0.58 (95% confidence interval (CI) 0.42-0.79)); second hour, 89-94% (HR 0.54 (95% CI 0.39-0.75)); third hour, 86-92% (HR 0.46 (95% CI 0.33-0.65)). In approximately one-third of patients, RBV was within these ranges, while two-thirds were outside these ranges. By median age ( < / >61 years), sex, race (white / non-white), predialysis systolic blood pressure (SBP) ( < / >130 mmHg) and median interdialytic weight gain ( < Subgroup analysis of patients with 3-h RBV between 86% and 92% showed comparable favorable RBV ranges. When compared with patients with RBV>92%, patients with 3-h RBV between 86% and 92% were younger, had higher ultrafiltration volumes and rates, similar intradialytic mean and nadir SBP and hypotension rates, lower postdialytic SBP, and lower incidence of congestive heart failure. In multivariable Cox analysis, RBV range remained an independent and significant predictor of efficacy.
[0098] In general, all-cause mortality studies on intradialytic RBV have concluded that a specific intradialytic RBV range per hour is associated with lower all-cause mortality in chronic HD patients.
[0099] The Intradialytic RBV All-Cause Mortality Study was a multicenter observational retrospective study of maintenance HD patients from 17 institutions at the Renal Research Institute (RRI) in New York, NY, USA. CLM was deployed to RRI dialysis clinics on a rolling basis and was the standard of care. A 6-month baseline period and a follow-up period of up to 54 months were defined at the patient level (see Fig.10 , which depicts the baseline and follow-up periods). The first treatment with eligible CLM data was taken as the start date of the baseline period. All patients with at least 10 eligible CLM records during the baseline period were included in the study. Treatment duration <200 minutes was the only exclusion criterion. Patient characteristics were assessed during the baseline period. All-cause mortality was recorded during the follow-up period.
[0100] The RBV at time t (expressed as a percentage of the blood volume at the start of dialysis) is calculated as follows:
[0101] RBV (%) at time t = 100 × HCT0 / HCTt.
[0102] HCT0 and HCT t are the hematocrit at the beginning of the HD period and at a given time t, respectively. Hematocrit was measured quasi-continuously using CLM, and RBV was reported every minute. RBV was calculated for each patient for each treatment, then the RBV for all treatments was averaged for each patient, and then the RBV for each patient was averaged again. RBV at 1, 2, and 3 hours of the HD period was used as a predictor of efficacy. For this purpose, RBV data were averaged between 50 and 70 minutes, 110 and 130 minutes, and 170 and 190 minutes, respectively.
[0103] In the Intradialytic RBV All-Cause Mortality Study, blood pressure was measured automatically every 30 minutes using the oscillometric method. Mean predialytic, postdialytic, and intradialytic systolic blood pressure (SBP) were calculated, and the lowest SBP and IDH rate were reported; IDH was defined as intradialytic SBP <90 mmHg. Intradialytic SBP during the baseline period was available for 181 treatments in 219 patients.
[0104] Congestive heart failure (CHF), diabetes mellitus (DM), and chronic obstructive pulmonary disease (COPD) were recorded using International Classification of Diseases, Ninth Revision, codes in the patients' electronic health records.
[0105] Descriptive statistics included means (+ / - standard deviations) for continuous variables and percentages for categorical variables. To explore the association between all-cause mortality and RBV at 1, 2, and 3 hours, the Intradialytic RBV All-Cause Mortality Study used a Cox proportional hazards model with spline terms, allowing for modeling of the nonlinear effects of RBV as a continuous variable and its relationship to all-cause mortality at these three hourly time points. This spline analysis allowed for the identification of hourly RBV ranges associated with hazard ratios (HRs) that were significantly <1 (“favorable”) or >1 (“unfavorable”), respectively.
[0106] For additional analyses, patients were stratified into two groups, those within or outside the "favorable" 3-h RBV range. Survival characteristics were compared using Kaplan-Meier plots, log-rank tests, and Cox proportional hazards models. Minimally and fully adjusted Cox models supplemented the original survival analysis. The minimally adjusted model included age, sex, CHF, and COPD. In addition, the fully adjusted model included serum albumin and hemoglobin, neutrophil:lymphocyte ratio (NLR; inflammatory marker), UFR, predialysis SBP, diabetes, and race. Patients were censored or deleted at the time of kidney transplantation, transfer to a non-RRI institution, change in dialysis treatment modality, or end of follow-up.
[0107] Baseline descriptive statistics for group differences and 95% confidence intervals for patients within or outside the “favorable” 3-h RBV range, respectively, are also reported. To further explore these findings and account for possible bias from considering only 3 h instead of the entire treatment time, the association between all-cause mortality and relative elapsed treatment time (where total treatment time was defined as 100%) and RBV was also examined. All-cause mortality by intradialytic RBV was investigated using 25%, 50%, 75%, and 100% of elapsed treatment time by averaging RBV between 21–30, 46–55, 71–80, and 91–100% of total treatment time, respectively. In addition, the association between RBV slope and all-cause mortality was examined. RBV slope was calculated using simple linear regression with an intercept of 100% RBV (by definition, initial RBV). Sensitivity analyses excluding patients with RBV below the favorable hourly RBV range were also performed.
[0108] The Intradialytic RBV All-Cause Mortality Study studied 842 patients with a total of 28,119 dialysis sessions with eligible RBV records during a 6-month baseline period, resulting in 33.4 ± 13.8 eligible dialysis sessions per patient (see Fig.11 Table 1105). Age was 61±14.8 years, dialysis years were 3.9±4.1 years, 50.6% were white, 62.1% were male, 55.8% had diabetes, 24% had CHF, and 9.4% had COPD. Intradialytic RBV was 97.9±1.9%, 94.8±2.6, and 93.1±3.3% after 1, 2, and 3 hours, respectively.
[0109] During a median follow-up of 30.8 months, 249 patients (29.6%) died. The HRs for all-cause mortality were significantly <1.0 for patients with a 1-h RBV of 93-96%, a 2-h RBV of 89-94%, and a 3-h RBV of 86-92%. Approximately 65% of patients achieved an RBV above these RBV ranges, 32% achieved an RBV within these RBV ranges, and approximately 2.5% achieved an RBV below these RBV ranges (see Table 2). Fig.12 1205). The RBV ranges associated with HR significantly > 1.0 were 97-100% (1 h), 95-99% (2 h), and 93-99% (3 h) (see Fig.13 Figures 1310, 1312 and 1314 and Fig.14 1405). Fig.13 , which depicts HR and Cis for RBV levels achieved after 1 hour (graph 1310), 2 hours (graph 1312), and 3 hours (graph 1314), with tick marks on the x-axis representing individual patients. Fig.14 Graph 1405 depicts the range of intradialytic hourly RBV with a HR significantly < 1.0 for all-cause mortality.
[0110] exist Fig.15 In Figure 1505 of FIG. 1506 , the half-hour favorable RBV range is shown as supplemental data. Multivariate Cox analysis confirmed that those patients whose RBV fell within these RBV ranges had a lower HR for all-cause mortality (see Fig.16 1605). Analysis by percentage of treatment time elapsed rather than by hours showed essentially the same results (see Fig.17 Figure 1705). By median age ( < / >61 years), race (white, non-white), sex, pre-dialysis SBP ( < / >130 mmHg) and interdialytic weight gain (IDWG) ( < / >2.3 kg) showed a comparable favorable RBV range (see Fig.18 Table 1805).
[0111] Kaplan-Meier analysis and Cox proportional hazards models showed that patients with a 3-h RBV of 86-92% had significantly better survival than those outside this range (see Fig.19 The charts of 1905 and Fig. 20 2005).
[0112] Analysis of RBV slope and all-cause mortality showed that significantly increased HRs had slopes ranging from 2.47 to 0.34% / h and significantly decreased HRs had slopes from 5.18 to 3.04% / h (see Fig.21 Figure 2105).
[0113] The Intradialytic RBV All-Cause Mortality Study compared clinical, laboratory, and treatment variables between patients who did and did not achieve a 3-h RBV of 86-92% (see Fig.11 Table 1105 of the literature). 273 patients (32.5%) had RBV within this 3-h RBV range, 554 patients (65.8%) had RBV >92%, and 15 patients (1.8%) had RBV <86%. Patients outside the 3-h RBV range of 86–92% were older (63.6+ / -15.9 years vs. 55.7+ / -14.1 years; P < .001), had more frequent CHF (26.2% vs. 19.4%; P = .03), had lower IDWG (2.2+ / -0.8 vs. 2.7+ / -0.8 kg; P < .001), lower standardized UFR (7.1+ / -2.5 vs. 8.8+ / -2.7 mL / kg / h; P < .001), and had lower mean The patients had an increased normalized protein catabolism rate (enPCR; 0.9+ / -0.2 vs. 1.0+ / -0.2 g / day / kg; P<0.001), lower albumin levels (3.9+ / -0.4 vs. 4.0+ / -0.3 g / dL; P=0.003), lower transferrin saturation (32.4+ / -9.0 vs. 34.1+ / -8.5%; P=0.007), and higher NLR (4.0+ / -2.3 vs. 3.3+ / -1.7; P<0.001).
[0114] Mean predialysis, postdialysis, intradialytic, and nadir SBP were 146.3 ± 20.1, 136.6 ± 18.5, 135.3 ± 19.0, and 116.2 ± 19.0 mmHg, respectively. Predialysis and intradialytic SBP did not differ between patients who did or did not achieve a 3-h RBV of 86–92%. Postdialysis SBP was significantly higher in patients with an RBV outside this range (see Table 1). Fig.11 Table 1105 and Fig. 22 Figure 2205).
[0115] To investigate whether intradialytic SBP characteristics are associated with specific RBV levels, the Intradialytic RBV All-Cause Mortality Study stratified patients based on their intradialytic SBP change (post-hemodialysis SBP, pre-hemodialysis SBP). Hourly RBV levels were comparable in all groups with respect to intradialytic SBP change (see Fig.23 Table 2305).
[0116] The association between RBV and intradialytic SBP patterns was examined by analyzing the 219 patients with available intradialytic RBV and SPB data. Seventy-six patients (34.7%) were within the favorable 3-h RBV range, and 143 patients (65.3%) were outside the favorable 3-h RBV range. There were no differences in intradialytic mean SBP, nadir SBP, and 10 IDH rate between the two groups (see Fig.24 Table 2405 and Fig.25 2505). The hourly RBV at treatment level was comparable between the phases with and without IDH (see Fig.26 Table 2605).
[0117] Recognizing the possible effect of fluid administration on RBV, hourly RBV levels during documented fluid administration treatments were examined; hourly RBV levels were essentially the same (see Fig. 27 In addition, there were no differences between patients in the fluid administration rate and in the presence of IDH within or outside the range of 86-92% 3-h RBV (see Table 2705). Fig.25 Table 2505).
[0118] To explore the effect of RBV levels below the favorable RBV range on efficacy, the HR for all-cause mortality was calculated after excluding patients with RBV below the lower limit of the favorable RBV range per hour. This sensitivity analysis showed essentially the same results (see Fig.28 Table 2805 and Fig.29 Figure 2905).
[0119] To further explore the effect of intradialytic fluid administration on the association between RBV and all-cause mortality, sensitivity analyses were performed for patients with available intradialytic data. Cox proportional hazards models excluding fluid administration treatment (crude minimal and fully adjusted models) showed essentially identical results.
[0120] The Intradialytic RBV All-Cause Mortality Study investigated the association between hourly intradialytic RBV levels and all-cause mortality in a large and diverse cohort of chronic HD patients. The main finding was that specific intradialytic RBV ranges were associated with a significant reduction in all-cause mortality. Furthermore, in the Intradialytic RBV All-Cause Mortality Study, patients who achieved a favorable 3-h RBV range did not have an increased IDH rate despite a higher UFR.
[0121] In a study of intradialytic RBV all-cause mortality, approximately two-thirds of patients achieved RBV above the favorable range, whereas < 3% of patients fell below the favorable range. Patients with 3-h RBV above the upper limit of the favorable range developed clinical signs of fluid overload, such as higher postdialysis SBP and a higher prevalence of CHF (see Fig.11 Table 1105 of the literature). Patients with RBV outside the favorable range were older, had a higher prevalence of CHF, lower enPCR, and lower UFR than those with RBV within the favorable range. In conclusion, the intradialytic RBV all-cause mortality study showed that specific intradialytic RBV ranges are associated with all-cause mortality in HD patients.
[0122] Case Study 2: In-Silico Case Study
[0123] According to some embodiments, an In-Silico case study was performed using a patient avatar (or "fluid avatar") undergoing a simulated dialysis treatment with RBV-based UF control. Figures 30A-30C Depicts the data generated during the In-Silico case study. For example, Fig. 30A Graphs 3005 and 3010 are shown, respectively, depicting RBV versus time and UFR versus time for a first patient avatar having a prescribed UF target of 2800 mL and a UFR of 960 mL / hour (line 3012 of graph 3010) and an actual UF removal of 2120 mL. The first patient avatar has a TBV of -14.6%, a PV of -2.1%, and an ECV / TBW of 22.5 / 53.5 = 0.42.
[0124] Fig. 30B A graph 3015 of RBV versus time and a graph 3020 of UFR versus time are depicted for a second patient avatar having a prescribed UF target of 3000 mL and a UFR of 800 mL / hour (line 3014 of curve 3020) and an actual UF removal of 4000 mL. The second patient avatar has a TBV of -18.7%, a PV of +40.8%, and an ECV / TBW of 22.5 / 56.8 = 0.45.
[0125] Fig. 30C Depicted are a graph 3025 of RBV versus time, a graph 3030 of UFR versus time, and a graph 3035 of blood oxygen saturation versus time for a third patient avatar. For the third patient avatar, RBV-based ultrafiltration control with blood oxygen saturation constraints was examined.
[0126] Case Study 3: Clinical Pilot Study
[0127] According to some embodiments, a clinical pilot study was conducted to characterize RBV-based UF control as a feedback controller designed to guide a patient's RBV curve into a predefined target range during hemodialysis treatment. The clinical pilot study was a single-arm, prospective, interventional pilot study conducted on HD patients. The clinical pilot study included 16 patients with a total of 37 study visits. Figures 31A-31D Graphs 3105, 3110, 3115, and 3120 depict data generated during a clinical pilot study. For example, reference Fig.31A , which depicts a graph 3105 showing RBV 3112 managed within RBV target range 3114. In general, Fig.31B and 31C Further shown is the relationship between the RBV [%] measured during treatment and the corresponding adjustment to the UFR to return the patient's RBV to the "tube of good fortune".
[0128] Fig.32 A diagram of an exemplary embodiment of a dialysis system 3200 according to the present disclosure is shown. The dialysis system 3200 can be configured to provide hemodialysis (HD) treatment for a patient 3201. A fluid reservoir 3202 can deliver fresh dialysate to a dialyzer 3204 via a tube 3203, and a reservoir 3206 can receive used dialysate via a tube 3205 once the fresh dialysate has passed through the dialyzer 3204. A hemodialysis operation can filter particles and / or contaminants from the patient's blood by, for example, a patient-external filtration device of the dialyzer 3204. When the dialysate passes through the dialyzer 3204, unfiltered patient blood also enters the dialyzer 3204 via a tube 3207, and the filtered blood is returned to the patient 3201 via a tube 3205. Arterial pressure can be monitored via a pressure sensor 3210, inflow pressure is monitored via a sensor 3218, and venous pressure is monitored via a pressure sensor 3214. An air trap and detector 3216 can ensure that air is not introduced into the patient's blood as the blood is filtered and returned to the patient 3201. The flow of blood and the flow of dialysate can be rotated via corresponding pumps including a blood pump 3212 and a fluid pump 3220. Heparin 3222, a blood thinner, can be used in conjunction with saline 3224 to ensure that blood clots do not form or block blood flow through the system.
[0129] In some embodiments, the dialysis system 3200 may include a controller 3250, which may be similar to the computing device 110 and / or its components (e.g., the processor circuit 420). The controller 3250 may be configured to monitor fluid pressure readings to identify fluctuations in patient parameters such as heart rate and / or respiratory rate. In some embodiments, the patient's heart rate and / or respiratory rate may be determined by the fluid pressure in the fluid flow line and fluid bag. Although the controller 3250 may use any available data about the patient's biological function or other patient parameters, the controller 3250 may also be operably connected to and / or communicate with additional sensors or sensor systems, devices, and / or the like. For example, according to some embodiments, the controller 3250 may send patient data to the computing device 110 to perform some processes.
[0130] Fig.33 An embodiment of an exemplary computing architecture 3300 suitable for implementing various embodiments as described above is shown. In various embodiments, the computing architecture 3300 may include or be implemented as part of an electronic device. In some embodiments, the computing architecture 3300 may represent, for example, a computing device 3302 and / or its components. The embodiments are not limited thereto.
[0131] As used in this application, the terms "system" and "component" and "module" mean an entity related to a computer, either hardware, a combination of hardware and software, software, or software in execution, examples of which are provided by the exemplary computing architecture 3300. For example, a component can be, but is not limited to, a process running on a processor, a processor, a hard drive, multiple storage drives (optical and / or magnetic storage media), an object, an executable file, an execution thread, a program, and / or a computer. As an illustration, both an application running on a server and a server can be a component. One or more components can reside within a process and / or an execution thread, and a component can be located on a computer and / or distributed between two or more computers. In addition, components can be communicatively coupled to each other through various types of communication media to coordinate operations. Coordination can involve a unidirectional or bidirectional exchange of information. For example, a component can communicate information in the form of a signal communicated on a communication medium. The information can be implemented as a signal assigned to various signal lines. In such an assignment, each message is a signal. However, other embodiments may alternatively employ data messages. Such data messages can be sent through various connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces.
[0132] The computing architecture 3300 includes various common computing elements such as one or more processors, multi-core processors, coprocessors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input / output (I / O) components, power supplies, etc. However, the embodiments are not limited to implementation by the computing architecture 3300.
[0133] like Fig.33 As shown, computing architecture 3300 includes processing unit 3304, system memory 3306, and system bus 3308. Processing unit 3304 can be any of a variety of commercially available processors, including but not limited to and processor; Application, embedded and security processors; and and Processors; IBM and Cell processor; Core(2) and processor; and similar processors. Dual microprocessors, multi-core processors, and other multi-processor architectures can also be used as the processing unit 3304.
[0134] The system bus 3308 provides an interface for system components, including but not limited to the interface of the system memory 3306 to the processing unit 3304. The system bus 3308 can be any of a variety of types of bus structures that can be further interconnected to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. Interface adapters can be connected to the system bus 3308 via a slot architecture. Example slot architectures can include but are not limited to accelerated graphics port (AGP), card bus, (extended) industry standard architecture ((E)ISA), micro channel architecture (MCA), NuBus, peripheral component interconnect (extended) (PCI (X)), PCI Express, personal computer memory card international association (PCMCIA), etc.
[0135] The system memory 3306 may include various types of computer-readable storage media in the form of one or more higher speed memory cells, such as read-only memory (ROM), random access memory (RAM), dynamic RAM (DRAM), double data rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, polymer memory, such as ferroelectric polymer memory, austenite memory, phase change or ferroelectric memory, silicon oxide-nitride-oxide-silicon (SONOS) memory, magnetic or optical cards, array devices such as redundant array of independent disks (RAID) drives, solid-state memory devices (e.g., USB memory, solid-state drive (SSD), and any other type of storage medium suitable for storing information. Fig.33 In the illustrative embodiment shown, system memory 3306 can include non-volatile memory 3310 and / or volatile memory 3312. A basic input / output system (BIOS) can be stored in non-volatile memory 3310.
[0136] The computer 3302 may include various types of computer-readable storage media in the form of one or more lower speed memory units, including an internal (or external) hard disk drive (HDD) 3314, a magnetic floppy disk drive (FDD) 3316 that reads or writes from a removable magnetic disk 3318, and an optical drive 3320 that reads or writes from a removable optical disk 3322 (e.g., a CD-ROM or DVD). The HDD 3314, FDD 3316, and optical drive 3320 may be connected to the system bus 3308 via a HDD interface 3324, a FDD interface 3326, and an optical drive interface 3329, respectively. The HDD interface 3324 for external drive implementations may include at least one or both of Universal Serial Bus (USB) and IEEE 1384 interface technologies.
[0137] The drives and associated computer-readable media provide volatile and / or nonvolatile storage of data, data structures, computer-executable instructions, etc. For example, a number of program modules may be stored in the drives and memory units 3310, 3312, including an operating system 3330, one or more application programs 3332, other program modules 3334, and program data 3336. In one embodiment, the one or more application programs 3332, other program modules 3334, and program data 3336 may include, for example, various applications and / or components of the computing device 110.
[0138] A user may enter commands and information into the computer 3302 through one or more wired / wireless input devices, such as a keyboard 3338 and a pointing device such as a mouse 3340. Other input devices may include a microphone, an infrared (IR) remote control, a radio frequency (RF) remote control, a game pad, a stylus, a card reader, a dongle, a fingerprint reader, a glove, a graphics tablet, a joystick, a keyboard, a retina reader, a touch screen (e.g., capacitive, resistive, etc.), a trackball, a trackpad, a sensor, a stylus, etc. These and other input devices are typically connected to the processing unit 3304 through an input device interface 3342 coupled to the system bus 3308, but may also be connected through other interfaces such as a parallel port, an IEEE 994 serial port, a game port, a USB port, an IR port, etc.
[0139] A monitor 3344 or other type of display device is also connected to the system bus 3308 via an interface such as a video adapter 3346. The monitor 3344 may be internal or external to the computer 3302. In addition to the monitor 3344, computers typically include other peripheral output devices such as speakers, printers, and the like.
[0140] The computer 3302 can operate in a network environment using logic units via wired and / or wireless communications to one or more remote computers, such as remote computer 3349. The remote computer 3349 can be a workstation, server computer, router, personal computer, portable computer, microprocessor-based entertainment device, peer device or other public network node, and typically includes many or all of the elements described for the computer 3302, but only a memory / storage device 3350 is shown for simplicity. The depicted logical connections include wired / wireless connections to a local area network (LAN) 3352 and / or a larger network, such as a wide area network (WAN) 3354. Such LAN and WAN network environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can be connected to a global communication network, such as the Internet.
[0141] When used in a LAN networking environment, the computer 3302 is connected to the LAN 3352 through a wired and / or wireless communication network interface or adapter 3356. The adapter 3356 can facilitate wired and / or wireless communication to the LAN 3352, which can also include a wireless access point disposed thereon for communicating with the wireless functionality of the adapter 3356.
[0142] When used in a WAN networking environment, the computer 3302 may include a modem 3358, or be connected to a communications server on the WAN 3354, or have other means for establishing communications over the WAN 3354, such as over the Internet. The modem 3359, which may be internal or external and may be a wired and / or wireless device, may be connected to the system bus 3308 via the input device interface 3342. In a networked environment, program modules depicted for the computer 3302, or portions thereof, may be stored in the remote memory / storage device 3350. It should be appreciated that the network connections shown are exemplary and other methods of establishing a communications link between the computers may be used.
[0143] The computer 3302 is operable to communicate with wired and wireless devices or entities using the IEEE 802 family of standards, such as wireless devices operatively arranged in wireless communications (e.g., IEEE 802.16 over-the-air modulation techniques). This includes at least Wi-Fi (or Wireless Fidelity), WiMax, and Bluetooth. TM Wireless technology. Therefore, the communication can be a predefined structure like a conventional network, or just a simple and self-organizing communication between at least two devices. Wi-Fi networks use radio technology called IEEE802.11x (a, b, g, n, etc.) to provide secure, reliable, and fast wireless connections. Wi-Fi networks can be used to connect computers to each other, to the Internet, and to wired networks (which use the media and functions associated with IEEE 802.3).
[0144] Many specific details have been set forth herein to provide a thorough understanding of the embodiments. However, those skilled in the art will appreciate that the embodiments may be practiced without these specific details. In other cases, well-known operations, components, and circuits are not described in detail to avoid confusing the embodiments. It is understood that the specific structural and functional details disclosed herein may be representative and do not necessarily limit the scope of the embodiments.
[0145] Some embodiments may be described using the expressions "coupled" and "connected" and their derivatives. These terms are not intended to be synonymous with each other. For example, some embodiments may be described using the terms "connected" and / or "coupled" to indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" may also mean that two or more elements are not in direct contact with each other, but still cooperate or interact with each other.
[0146] Unless otherwise expressly stated, it is understood that terms such as "processing", "computing", "calculating", "determining", etc. refer to actions and / or processes of a computer or computing system or similar electronic computing device that manipulate and / or transform data represented as physical quantities (e.g., electronic) in registers and / or memories of the computing system into other data similarly represented as physical quantities within the memory, registers, or other such information storage, transmission, or display device of the computing system. The embodiments are not limited thereto.
[0147] It should be noted that the methods described herein do not have to be executed in the order described or in any particular order. In addition, various activities described with respect to the methods identified herein can be executed in serial or parallel manner.
[0148] Although specific embodiments have been shown and described herein, it should be understood that any arrangement calculated to achieve the same purpose can replace the specific embodiments shown. The present disclosure is intended to cover any and all modifications or variations of the various embodiments. It should be understood that the above description is made in an illustrative manner and not restrictive. Upon reviewing the above description, the above embodiments and other embodiments not specifically described herein will be apparent to those skilled in the art. Therefore, the scope of the various embodiments includes any other application in which the above-mentioned compositions, structures and methods are used.
[0149] Although the subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
1. A device comprising: at least one processor; as well as A memory coupled to the at least one processor, the memory comprising instructions that, when executed by the at least one processor, cause the at least one processor to: selecting a target RBV curve for the patient from a target RBV information library, the target RBV information library comprising a plurality of RBV curves, each of the plurality of RBV curves being associated with improved patient outcomes for a patient population having at least one population characteristic, the target RBV curve being based on at least one characteristic of the patient corresponding to the at least one population characteristic of the patient population associated with the target RBV curve; receiving a measurement of a relative blood volume (RBV) value of the patient during a dialysis procedure; calculating an ultrafiltration (UF) rate based on the measured RBV value of the patient and a target RBV curve; and The UF rate is used to control the UF pump during the dialysis process.
2. The device according to claim 1, wherein: The at least one characteristic and the at least one population characteristic include at least one of age, gender, disease state, fluid removal, and complications.
3. The device according to claim 1, wherein: The RBV target curve includes a plurality of RBV time values, each of the plurality of RBV time values including a target RBV range for a defined time interval during the dialysis procedure.
4. The device according to claim 1, wherein: The instructions, when executed by the at least one processor, cause the at least one processor to calculate a UF rate to maintain a future RBV value of the patient within a target RBV curve during a dialysis procedure.
5. The device according to claim 1, wherein: The instructions, when executed by the at least one processor, cause the at least one processor to determine a UF rate based on at least one constraint, the at least one constraint comprising at least one of: a maximum UF rate change constraint, a blood oxygen saturation constraint, and an intradialytic hypotension (IDH) prediction constraint.
6. The device according to claim 1, wherein: The improved patient outcomes for the multiple RBV curves were based on hazard ratios (HR) for all-cause mortality for the patient population.
7. The device according to claim 1, wherein: The instructions, when executed by the at least one processor, cause the at least one processor to execute a proportional-integral (PI) control loop to calculate a UF rate based on a measured value of a patient's RBV value and a target RBV curve, wherein the PI control loop operates using a process variable based on the measured value of the patient's RBV value and a control variable based on a previous UF rate.
8. A computer-implemented method for ultrafiltration (UF) control based on relative blood volume (RBV), the method comprising executing, via a processor of a computing device: receiving at least one characteristic of the patient; and RBV target information is determined, the RBV target information comprising a target RBV curve, the target RBV curve being generated based on clinical trial dialysis data of real patient efficacy for a patient population whose population characteristics correspond to the at least one characteristic of the patient, the RBV target information being configured as a target RBV range for patients at defined time intervals of a dialysis process, the target RBV range of the target RBV curve comprising an RBV value determined based on a hazard ratio (HR) threshold for the patient population.
9. The computer-implemented method of claim 8, wherein: Clinical trial dialysis data on real patient outcomes include improved patient outcomes based on HR thresholds.
10. The computer-implemented method of claim 9, wherein: HR thresholds were based on all-cause mortality for the patient population.
11. The computer-implemented method of claim 8, wherein: The at least one characteristic and the at least one population characteristic include at least one of age, gender, disease state, fluid removal, and complications.
12. The computer-implemented method of claim 8, wherein: The method further comprises: Receive the patient's RBV value; Determine the current time interval; determining UF information so as to maintain a future RBV value of the patient within a target RBV range for a defined time interval corresponding to a current time interval; and The UF pump of the dialysis machine is controlled based on the UF information.
13. The computer-implemented method of claim 12, wherein: The UF information includes one of a UF rate and a UF target.
14. The computer-implemented method of claim 8, wherein: The method includes determining a future RBV value based on at least one constraint, the at least one constraint including at least one of: a maximum UF rate change constraint, a blood oxygen saturation constraint, and an intradialytic hypotension (IDH) prediction constraint.
15. A computer-implemented method for performing a dialysis treatment, the method comprising executing, via a processor of a computing device: Receive the patient's relative blood volume (RBV) value during dialysis treatment; comparing the RBV value to RBV target information determined using clinical trial dialysis data for a patient population having a population characteristic corresponding to at least one characteristic of the patient, the RBV target information comprising a curve of an expected RBV range for the patient during a dialysis procedure; and Adjusting an ultrafiltration (UF) rate during dialysis treatment to maintain a patient's future RBV value within a desired RBV target range during dialysis treatment, the UF rate being adjusted based on at least one constraint, the at least one constraint comprising one of: a maximum UF rate change constraint, a blood oxygen saturation constraint, and an intradialytic hypotension (IDH) prediction constraint.
16. The computer-implemented method of claim 15, wherein: The blood oxygen saturation constraint is configured to prevent an increase in the UF rate in response to the patient's blood oxygen saturation level falling below a threshold.
17. The computer-implemented method of claim 15, wherein: The IDH prediction constraint is configured to reduce the UF rate in response to the patient's predicted IDH being outside of a predicted IDH range threshold.
18. The computer-implemented method of claim 15, wherein: The maximum UF rate change constraint is configured to be based on a UF rate threshold that is calculated based on whether the RBV value is within or outside the desired RBV range curve.
19. The computer-implemented method of claim 15, wherein: The maximum UF rate change constraint is configured to be based on a UF rate threshold value calculated based on the elapsed time of the dialysis treatment.
20. The computer-implemented method of claim 15, wherein: The at least one constraint includes a blood pressure constraint configured to prevent a reduction in the UF rate in response to the patient's blood pressure exceeding a threshold blood pressure range.
