Magnesium carbonate for phosphate control in patients on hemodialysis. A randomized controlled trial
Bibliographic record
Abstract
BACKGROUND: Magnesium salts bind dietary phosphorus, but their use in renal patients is limited due to their potential for causing side effects. The aim of this study was to evaluate the efficacy and safety of magnesium carbonate (MgCO(3)) as a phosphate-binder in hemodialysis patients. METHODS: Forty-six stable hemodialysis patients were randomly allocated to receive either MgCO(3) (n=25) or calcium carbonate (CaCO(3)), (n=21) for 6 months. The concentration of Mg in the dialysate bath was 0.30 mmol/l in the MgCO(3) group and 0.48 mmol/l in the CaCO(3) group. RESULTS: Only two of 25 patients (8%) discontinued ingestion of MgCO(3) due to complications: one (4%) because of persistent diarrhea, and the other (4%) because of recurrent hypermagnesemia. In the MgCO(3) and CaCO(3) groups, respectively, time-averaged (months 1-6) serum concentrations were: phosphate (P), 5.47 vs. 5.29 mg/dl, P=ns; Ca, 9.13 vs. 9.60 mg/dl, P<0.001; Ca x P product, 50.35 vs. 50.70 (mg/dl)(2), P=ns; Mg, 2.57 vs. 2.41 mg/dl, P=ns; intact parathyroid hormone (iPTH), 285 vs. 235 pg/ml, P<0.01. At month 6, iPTH levels did not differ between groups: 251 vs. 212 pg/ml, P=ns. At month 6 the percentages of patients with serum levels of phosphate, Ca x P product and iPTH that fell within the Kidney Disease Outcomes Quality Initiative (K/DOQI) guidelines were similar in both groups, whereas more patients in the MgCO(3) group (17/23; 73.91%) than in the CaCO(3) group (5/20, 25%) had serum Ca levels that fell within these guidelines, with the difference being significant at P<0.01. CONCLUSION: Our study shows that MgCO(3) administered for a period of 6 months is an effective and inexpensive agent to control serum phosphate levels in hemodialysis patients. The administration of MgCO(3) in combination with a low dialysate Mg concentration avoids the risk of severe hypermagnesemia.
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.003 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.004 | 0.003 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.003 | 0.002 |
| Insufficient payload (model declined to judge) | 0.007 | 0.001 |
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".