Improvements in phosphate control with short daily in-center hemodialysis
Bibliographic record
Abstract
BACKGROUND: Hyperphosphatemia is an independent risk factor for mortality in hemodialysis (HD) patients. The relative importance of HD frequency and duration for phosphate removal is not clear. Short daily hemodialysis (SDHD) is a form of HD which offers increased treatment frequency. SDHD studies have not been shown to normalize serum phosphate. METHODS: Twenty-one patients were converted from conventional thrice weekly HD (CHD, 4 h/session) to SDHD (2 - 3.75 h/session, 5 - 6 sessions per week). The primary endpoint was the change in predialysis serum phosphate levels after conversion from CHD to SDHD. Changes in serum calcium levels, phosphate binder and vitamin D analogue usage, and serum parathyroid hormone (PTH) levels were measured as secondary endpoints. RESULTS: Mean duration of SDHD was 17.7 +/- 1.9 months. Mean treatment time was 2.63 +/- 0.10 h, and mean frequency was 5.3 +/- 0.1 sessions per week. Predialysis serum phosphate decreased from 1.99 +/- 0.12 mM at three months pre conversion to 1.27 +/- 0.10 mM at six months post conversion to SDHD (p = 0.002). Serum phosphate remained stable between six and 12 months post conversion (1.27 +/- 0.10 mM to 1.38 +/- 0.14 mM, p = 0.8). When patients were grouped according to SDHD sessional frequency (five sessions/week versus six sessions/week) and compared, no significant differences were found in predialysis serum phosphate levels at six or 12 months post conversion. There were no changes in serum calcium. Overall phosphate binder usage did not change pre and post conversion to SDHD. Serum PTH tended to decrease after one year of SDHD (44.2 +/- 13.4 pM to 21.4 +/- 5.9 pM, p = 0.07). CONCLUSION: Conversion to SDHD significantly decreased serum phosphate. There may be a minimum hemodialysis duration below which increases in frequency are not able to compensate to achieve normal phosphate levels. Future studies are necessary to better characterize the relationship between HD duration and frequency with respect to phosphate removal.
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".