Efficacy and safety of sucroferric oxyhydroxide versus sevelamer carbonate: A systematic review and meta‐analysis
Bibliographic record
Abstract
INTRODUCTION: Phosphate binders are commonly used in patients receiving kidney replacement therapy (KRT), aiming to reduce and maintain serum phosphorus. Chronic kidney disease-mineral and bone disorder has been linked to reduced lifespan and worsened quality of life. This study aims to examine the efficacy and safety of sucroferric oxyhydroxide versus sevelamer carbonate in patients receiving KRT. METHODS: The data sources examined were MEDLINE (PubMed), Scopus, and the Cochrane Central Register of Controlled Clinical Trials with a search deadline of October 2023. We examined randomized controlled trials that compared sucroferric oxyhydroxide versus sevelamer carbonate in the adult population receiving KRT. We performed a meta-analysis combining the data from trials, using R-studio. FINDINGS: Inclusion criteria were met by five randomized trials. There was no statistically significant difference in the reduction of serum phosphorus between the two groups (MD: -0.07 mmol/L, 95% CI-random effects: -0.15 to 0.02). In the same line, a non-statistically significant difference was observed in serum i-PTH reduction between the two drugs (MD = -1.53 mg/dL, 95% CI = (-4.45, 1.4), p = 0.26, random effects model). No statistically significant difference was observed in all adverse events between the two groups (odds ratio: 1.11, 95% CI: 0.65-1.88, random effects model). Further analysis of gastrointestinal adverse events revealed that sevelamer carbonate increases gastrointestinal adverse events by up to 60% (odds ratio: 1.60, 95% CI: 1.31-1.97, common (fixed) effect model). DISCUSSION: This meta-analysis of randomized trials showed that both drugs, sucroferric oxyhydroxide and sevelamer equally and effectively controlled serum phosphorus levels, whereas sucroferric oxyhydroxide revealed a better profile in terms of gastrointestinal adverse events. Sucroferric oxyhydroxide is a valuable option for patients receiving KRT when sevelamer carbonate is more difficult to tolerate.
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.013 | 0.025 |
| Meta-epidemiology (narrow) | 0.003 | 0.001 |
| Meta-epidemiology (broad) | 0.022 | 0.038 |
| Bibliometrics | 0.006 | 0.006 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.004 | 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".