Sevelamer hydrochloride: A novel treatment of hyperphosphatemia associated with tumor lysis syndrome in children
Bibliographic record
Abstract
BACKGROUND: Sevelamer is a phosphate-binder used effectively for the treatment of hyperphosphatemia in patients treated with dialysis. OBJECTIVES: To describe the safety of sevelamer in children with hyperphosphatemia secondary to tumor lysis syndrome and the serum phosphate concentrations observed following its administration. PROCEDURE: A retrospective chart review of all children with leukemia/lymphoma diagnosed between November 2002 and April 2004 who received sevelamer during their initial admission was conducted. We monitored the effects of sevelamer on serum phosphate concentration, calcium/phosphate product and renal function at hours 24, 48, and 72 from sevelamer initiation. RESULTS: Thirteen patients received sevelamer during the study period. Their median age was 13 years (range 2.7-17.9) and eight were boys. Nine children had acute lymphoblastic leukemia, one had acute myeloid leukemia and 3 had non-Hodgkin's lymphoma. The most frequently used dose of sevelamer was 400 mg orally twice daily. The median duration of sevelamer therapy was 2 days (range 1-7). Two children were excluded from the efficacy analysis due to concurrent use of dialysis. Mean serum phosphate levels decreased after sevelamer administration, in eleven patients, from a baseline 2.2 mmol/L +/- 0.4 (95% CI, 1.7-3.1) to 1.1 mmol/L +/- 0.2 at hour 72 (95%CI, 0.6-1.5). The only toxicity attributed to sevelamer was mild vomiting in three patients. CONCLUSIONS: Sevelamer appears to be effective and tolerable for the treatment of hyperphosphatemia associated with tumor lysis syndrome.
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.000 |
| 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".