Long‐term efficacy and safety of sucroferric oxyhydroxide in African American dialysis patients
Bibliographic record
Abstract
INTRODUCTION: Sucroferric oxyhydroxide (SFOH) is a non-calcium, iron-based phosphate binder that demonstrated sustained serum phosphorus (sP) control, good tolerability, and lower pill burden, vs. sevelamer carbonate ("sevelamer"), in a Phase 3 study conducted in dialysis patients with hyperphosphatemia. This analysis evaluates the efficacy and safety of SFOH and sevelamer among African American (AA) patients participating in the trial. METHODS: Post hoc analysis of a 24-week, Phase 3, open-label trial (NCT01324128) and its 28-week extension study (NCT01464190). Patients were randomized 2:1 to SFOH (1.0-3.0 g/day) or sevelamer (2.4-14.4 g/day) for up to 52 weeks. FINDINGS: Of 549 patients who completed the Phase 3 study and extension, 100 (18.2%) AA patients were eligible for efficacy analysis (SFOH, n = 48; sevelamer, n = 52). sP concentrations decreased rapidly and comparably with both treatments by Week 8 (mean ± standard deviation change from baseline: -1.9 ± 1.9 mg/dL for SFOH and -2.2 ± 1.8 mg/dL for sevelamer). These reductions were maintained for 52 weeks (-2.1 ± 2.6 and -2.1 ± 1.6 mg/dL) and achieved with a lower mean pill burden (3.4 ± 1.4 vs. 7.6 ± 2.9 tablets/day) with SFOH vs. sevelamer. Treatment adherence rates (adherence within 70%-120% of expected medication intake) were 79.2% with SFOH and 59.6% with sevelamer. The proportion of patients reporting serious adverse events (AEs) was 27.7% with SFOH and 30.7% with sevelamer. More patients withdrew due to treatment-emergent AEs with SFOH vs. sevelamer (18.5% vs. 8.0%). The most common AEs with both treatments were gastrointestinal-related: diarrhea and discolored feces with SFOH, and nausea, vomiting, and constipation with sevelamer. DISCUSSION: SFOH is an efficacious and well-tolerated treatment for hyperphosphatemia in AA dialysis patients, with a lower pill burden and an improved adherence rate vs. sevelamer. These findings were consistent with the wider US patient population and the overall study population.
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.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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".