Abstract

Background Lanthanum carbonate is widely used to manage serum phosphate and calcium levels in end-stage kidney disease (ESKD) patients, yet comprehensive long-term safety data are lacking. This study leverages the FDA Adverse Event Reporting System (FAERS) to assess the extended safety profile of lanthanum carbonate. Research design and methods We analyzed FAERS data (2004-2022) to study the association between lanthanum carbonate and adverse events (AEs). Using MedDRA v25.0, we identified risk signals through System Organ Classes (SOCs) and Preferred Terms (PTs). Disproportionality analyses quantified lanthanum carbonate-associated AE signals. Results Among 3,284 reports, 2,466 were primary suspected AEs linked to lanthanum carbonate. Males reported AEs more frequently than females. Patients aged over 64 represented the majority. Median onset time for lanthanum carbonate-related AEs was 146 days. Gastrointestinal disorders were prevalent. We identified 16 new signals, including stress, abnormal hepatic function, cholelithiasis, bile duct stone, gastric cancer, and adenocarcinoma gastric. Stress was notable, particularly in male patients over 65 and those with lower weight. Conclusions This study affirms lanthanum carbonate’s long-term safety for reducing elevated blood phosphorus levels. While gastrointestinal disorders were common, attention must focus on emerging AEs, particularly stress, especially in elderly patients.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.