The effect of blood flow rate on dialysis recovery time in patients undergoing maintenance hemodialysis: A prospective, parallel‐group, randomized controlled trial
Bibliographic record
Abstract
INTRODUCTION: A majority of patients with end-stage renal disease (ESRD) on in-center hemodialysis (HD) require several hours to recover from an HD session. Patients and caregivers identify fatigue as a high priority for improvement. However, evidence for practical interventions to improve recovery time from conventional in-center HD is lacking. The effect of blood flow rate reduction on dialysis recovery time (DRT) is unknown. METHODS: Multicenter, single-blinded, randomized, parallel-design controlled trial of blood flow rate reduction vs. usual care. One-hundred two patients with ESRD undergoing maintenance HD in 18 centers with baseline DRT of greater than 6 hours were included as subjects. The intervention was a blood flow rate reduction of 100 mL/min, to a minimum of 300 mL/min. The primary outcome was the between-group difference in change in DRT. Secondary outcomes were changes in London Evaluation of Illness (LEVIL) survey responses from baseline. FINDINGS: Baseline median DRT was 720 (IQR 360-1013) minutes in controls and 720 (IQR 360-1106) minutes in the intervention group. DRT decreased in both groups. Mean change from baseline (95% confidence interval) at Week 4 in the study was -324 (-473, -175) minutes in the control group and -120 (-329, 90) minutes in the intervention group. The change from baseline was more profound in the control group (P = 0.05). Secondary outcomes of measures of quality of life reported on the LEVIL survey showed more improvement in patients' feelings of general well-being in the control group (P = 0.01). Differences between groups in pain, feeling washed out or drained, sleep quality, shortness of breath, and appetite were not statistically significant. DISCUSSION: Blood flow rate reduction did not improve DRT over usual care. Though more work needs to be done to address patient-reported fatigue, a significant positive impact may not be achieved without substantial changes in dialysis prescription.
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.005 | 0.006 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.005 | 0.003 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.003 | 0.003 |
| Insufficient payload (model declined to judge) | 0.005 | 0.001 |
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".