Continuous Blood Volume Monitoring and Ultrafiltration Control
Bibliographic record
Abstract
Continuous blood volume monitoring (CBVM) is believed to be a promising method for making the determination of patients' "dry weight" more objective, and ultrafiltration (UF) control more appropriate. Although blood volume response to UF and the interrelation between blood volume changes and changes in hemodynamic parameters are highly individual, certain principles of this response and interrelation can be identified and exploited for effective use of CBVM. The present work summarizes the authors' findings from practical CBVM application over the past 5 years and their opinions on the future development of this method. Four distinct types of blood volume response to constant UF rate were identified: Type 1, flat line throughout the whole session; Type 2, flat line during the first part of dialysis, followed by a linear decrease during the remaining time; Type 3, linear decrease right from dialysis start; and Type 4, linear decrease first, followed by a flat line during the remaining time. The possibility of a shift from one type to the other was verified. Blood volume reduction due to UF was found to have a static and a dynamic component. The most important factors affecting both components were found to be, by sensitivity analysis of a three-pool kinetic model, degree of overhydration, vascular system compliance, and UF volume (for the static component); and UF coefficient of the capillary wall and UF rate (for the dynamic component). Type 3 response, induced by more vigorous UF, was found to significantly decrease the volume of residual daily diuresis on the first postdialysis day. If confirmed, this finding may serve as a basis for the response type choice in patients with still significant residual renal function. Exploitation of the existence of dynamic blood volume reduction component for the first generation of automated biofeedback UF controllers may be complemented by automated identification of patient's plasma refilling capacity and/or position of his/her point on the Guytonian pressure/volume characteristics curves, and thus may more advanced "intelligent" UF controllers be constructed in the future.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.005 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".