Phosphate Binder Choice Against a Rising Coronary Calcium Score
A hemodialysis patient whose phosphate keeps climbing despite genuine dietary effort, and whose own coronary calcium score may be telling the group which binder class is actually safe for him.
Walter T., a 58-year-old man, has taught high-school metal shop for over two decades and still runs the after-school welding club twice a week, though the fatigue that brought him to dialysis four years ago has made standing at the forge longer than an hour something he now has to plan around. His diabetic nephropathy progressed to end-stage kidney disease gradually enough that he'd already adjusted his classroom routines around dialysis days before his creatinine ever forced the conversation. He has never missed a session and, unusually, has completed two separate dietary phosphate counseling visits this year with a food diary a dietitian confirmed as genuinely accurate — which makes tonight's number harder to explain away as noncompliance.
His phosphate has climbed to 6.8 mg/dL, up from 5.9 six weeks ago, on the same binder regimen and the same diet a dietitian just verified — a rise that reads as a dosing or binder-choice problem, not a new lapse in effort. His PTH has followed the same upward line over three months. The number that actually reframes the decision, though, sits outside the metabolic panel: a repeat coronary CT ordered for an unrelated pre-transplant-eligibility workup came back with a calcium score of 850, up from 610 a year earlier — real, measurable progression of vascular calcification, in the same window his phosphate control has been slipping, and not an incidental finding either: a coronary calcium score this high and still climbing is itself a factor his transplant center will weigh when it reviews his candidacy next year, which turns tonight's binder decision into something with a deadline attached, not an open-ended preference. Treat-to-Goal, the trial that first put numbers behind the worry that calcium-based binders accelerate exactly this process, followed dialysis patients randomized to calcium acetate or sevelamer for one year and found significantly less coronary calcium progression in the sevelamer arm. Walter's own scan, unprompted by that trial, is now showing the same trajectory in a patient who has spent four years on a calcium-containing binder. His decade of type 2 diabetes offers a competing explanation, and it is a good one for why a 58-year-old carries a score of 850 at all — but it is a poor one for why that score moved 240 points in twelve months on an unchanged regimen. The absolute number is his diabetes. The slope is the argument.
At the binder review, four years in
The calcium score is the finding I'd act on first. Treat-to-Goal randomized dialysis patients to calcium acetate or sevelamer and found significantly less coronary calcification progression on sevelamer over one year — a controlled comparison, not an observation. Walter's own scan just reproduced that finding in real life: 610 to 850 over the same year his phosphate crept up on a calcium-containing binder. I don't think we need to wait for a mortality trial to act on a signal this direct in this specific patient.
If his calcium score had been flat, I would not be pushing this nearly as hard — the argument is about his own measured trajectory, not a blanket rule against calcium-based binders for everyone on dialysis.
I'll grant the trajectory is real and worth responding to. But DCOR, the largest RCT actually powered for mortality, found no significant difference between sevelamer and calcium-based binders on the outcome that matters most. I'll be straight about the Cochrane update rather than lean on it harder than it holds: Natale and colleagues' 2025 revision does report that sevelamer may reduce all-cause death compared with calcium-based binders, which cuts against me. What it also reports is that binders as a class show no clinically important benefit over placebo or usual care on cardiovascular death or on calcium score itself — the very endpoint we're about to reorganize his regimen around. A calcification score is a real, worrying number, but it's still a surrogate, and switching a patient whose adherence has been unusually good onto a pricier, harder-tolerated regimen isn't free.
And the Treat-to-Goal comparison she's citing measured one year of surrogate progression in a trial not designed or powered to show whether that translates into fewer deaths or cardiovascular events — which is exactly the gap DCOR was built to close, and didn't. CARE-2 is the sharper problem for her: when both arms got atorvastatin and ended at the same LDL, the calcification difference between calcium acetate and sevelamer disappeared.
There's a version of this that doesn't require resolving the calcification-versus-mortality argument today. His hemoglobin is 9.8 on ESA and ongoing IV iron — also failing target. Ferric citrate binds phosphate the same way sevelamer avoids calcium load, and in Lewis and colleagues' 52-week dialysis trial patients on it needed roughly half the IV iron (median 12.9 versus 26.9 mg/week) and less ESA than those on sevelamer or calcium acetate, while holding phosphate. It doesn't settle whether calcification progression changes his mortality risk, but it removes the calcium load either way and treats a second active problem with the same prescription.
The honest caveat is that ferric citrate's own outcome evidence is no stronger than sevelamer's — this is a reasonable choice given his whole picture, not a trump card over either position above.
Agreed: start ferric citrate in place of calcium acetate, recheck phosphate and iron studies in four weeks, and repeat the coronary calcium score at the twelve-month mark to see whether progression has actually slowed.
Not agreed: whether the calcification data should carry this much weight going forward if adherence ever becomes the bigger threat instead. The evidence-and-adherence voice stayed on record that calcium acetate remains a reasonable fallback if cost or tolerability ever put ferric citrate out of reach for him — a position the group left open rather than resolved.