Fibroblast growth factor 23 is associated with fractional excretion of sodium in patients with chronic kidney disease
Bibliographic record
Abstract
BACKGROUND: Recent studies suggest that the phosphaturic hormone fibroblast growth factor 23 (FGF23) is involved in regulation of renal sodium excretion and blood pressure. There is evidence of both direct effects via regulation of the sodium-chloride symporter (NCC) in the distal tubule, and indirect effects through interactions with the renin-angiotensin-aldosterone system. However, clinical data on the association between FGF23 and renal sodium regulation is lacking. Herein, we investigated the associations of FGF23 with renal sodium handling and blood pressure in non-dialysis CKD patients. METHODS: This was a cross-sectional study encompassing 180 CKD patients Stage 1-5, undergoing renal biopsy. Plasma intact FGF23, 24-h urinary sodium excretion, fractional excretion of sodium (FENa) and blood pressure were measured at baseline. The association between FGF23 and renal sodium handling was explored by multivariate regression analysis. RESULTS: The median age was 52.8 years, 60.6% were men and the median estimated glomerular filtration rate (eGFR) was 50.6 mL/min/1.73 m2. In univariate analysis, FGF23 was positively associated with FENa (Spearman's rho = 0.47; P < 0.001) and systolic blood pressure (rho = 0.17, P < 0.05), but not with plasma sodium, 24-h urinary sodium excretion or mean arterial blood pressure. The association between FGF23 and FENa remained significant after adjustment for potential confounders (multivariable adjusted β coefficient 0.60, P < 0.001). This association was stronger among the 107 individuals with eGFR <60 mL/min/1.73 m2 (β = 0.47, P = 0.04) and in the 73 individuals on any diuretics (β = 0.88, P < 0.001). Adjustment for measured GFR instead of eGFR did not alter the relationship. CONCLUSIONS: FGF23 is independently associated with increased FENa in non-dialysis CKD patients. These data do not support the notion that FGF23 causes clinically significant sodium retention. Further studies are warranted to explore the mechanism underlying this association.
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.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 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".