Constant Fluid Removal Associates With Greater Risk of Elevated High‐Sensitivity Troponin I Than Downward Sloping Profile Among Maintenance Dialysis Patients With High Ultrafiltration
Bibliographic record
Abstract
INTRODUCTION: High ultrafiltration rate is a common clinical problem in those undergoing maintenance dialysis and is associated with myocardial injury and increased mortality. The safety of the downward sloping profile of ultrafiltration in those with high ultrafiltration rates is currently unknown. The aim of the present study is to compare mean arterial pressure trends and dialysis-associated high-sensitivity Troponin I changes among patients with high ultrafiltration rates undergoing constant and profiled ultrafiltration. METHODS: The enrolled study participants were patients on maintenance dialysis thrice weekly with ultrafiltration rates > 13 mL/kg/h and without known cardiac disease. During the study month, they received six sessions with constant ultrafiltration and six sessions with downward sloping profiled ultrafiltration. Pre-to-post HD hs TnI change, blood pressures, and intradialytic hypotension episodes were measured during all 12 sessions. FINDINGS: A total of 42 study participants with 504 dialysis sessions were analyzed. The mean age of study participants was 41.3 (±12.1) years, two-thirds were male, and up to 17% had diabetes mellitus. The mean ultrafiltration volume was 17.4 (±3.2) mL/kg/h. Mean arterial pressures and intradialytic hypotension did not differ significantly between constant and profiled sessions, except for trends toward higher pressures at the post-HD timepoint in profiled UF (p = 0.08). Upon comparing Δ Post-Pre-HD hs Tn I of constant versus profiled ultrafiltration, constant sessions showed a median rise of troponin, ranging from 8 to 21 ng/mL from pre- to post-HD, and profiled sessions showed a median fall, ranging from 11 to 21 ng/mL from pre- to post-HD during profiled UF sessions (p < 0.001). Multivariate logistic regression analysis showed that constant UF type was associated with 27 times greater odds of developing a 10% rise in high-sensitivity troponin. CONCLUSION: In maintenance dialysis patients with high ultrafiltration, constant fluid removal is associated with a rise in hs Tn I, and a downward sloping profile may be safer than constant fluid removal. TRIAL REGISTRATION: Clinical Trials Registry of India (CTRI): CTRI/2023/02/049618.
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.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 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".