Abstract

Serum calcium/phosphate ratio (Ca/P) has been recently proposed as an additional tool to identify primary hyperparathyroidism (PHPT), especially in patients with subclinical presentation, with a proposed cut-off of 3.3 when both values are expressed in mg/dL. No data are available on the relationship between Ca/P and the clinical presentation of PHPT. We thus evaluated this relationship in a large, single-center, unselected series. 515 consecutive PHPT patients (mean age 65 ± 13.15years, 77.1% females) were retrospectively evaluated at diagnosis. Mean Ca/P was 4.54 ± 1.5 (range 2.36-13.9), being higher than 3.3 in 88.5% of patients. Ca/P was significantly higher in (1) males, (2) symptomatic PHPT, (3) patients with 25-hydroxy vitamin D levels lower than 20μg/L, (4) patients with osteitis fibrosa cystica, (5) patients with T score < - 2.5 at the radial site. In a multivariate regression analysis, Ca/P resulted significantly associated with PTH levels. After the exclusion of 57 patients with asymptomatic PHPT (aPHPT) patients and serum Ca higher than 1mg/dL above the upper limit of normal range, no differences were found in Ca/P between aPHPT meeting or not surgical criteria. In PHPT Ca/P ratio is associated with increased biochemical and clinical severity of disease and represents a direct indicator of clinical bone damage. However, it does not seem an additional tool to identify aPHPT patients reaching surgical indication.

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.