The effect of cisplatin-based neoadjuvant chemotherapy on the renal function of patients undergoing radical cystectomy
Bibliographic record
Abstract
INTRODUCTION: Cisplatin-based neoadjuvant chemotherapy (NAC) is the standard of care for patients with muscle-invasive bladder cancer (MIBC) undergoing radical cystectomy (RC). Cisplatin, however, can induce renal toxicity. Furthermore, RC is an independent risk factor for renal injury, with decreases in estimated glomerular filtration rate (eGFR) of up to 6 mL/min/1.73 m2 reported at one year postoperatively. Our objective was to evaluate the effect of cisplatin-based NAC and RC on the renal function of patients undergoing both. METHODS: We analyzed a multicenter database of patients with MIBC, all of whom received cisplatin-based NAC prior to RC. eGFR values were collected at time points T1 (before NAC), T2 (after NAC but before RC), and T3 (one year post-RC). eGFR and proportion of patients with eGFR <60 ml/min/1.73m2 (chronic kidney disease [CKD] stage ≥3) were compared between these time points. As all patients in this dataset had received NAC, we identified a retrospective cohort of patients from one institution who had undergone RC during the same time period without NAC for context. RESULTS: We identified 234 patients with available renal function data. From T1 to T3, there was a mean decline in eGFR of 17% (13 mL/min/1.73 m2) in the NAC cohort and an increase in proportion of patients with stage ≥3 CKD from 27% to 50%. The parallel cohort of patients who did not receive NAC was comprised of 236 patients. The mean baseline eGFR in this cohort was lower than in the NAC cohort (66 vs. 75 mL/min/1.73 m2). The mean eGFR decline in this non-NAC cohort from T1 to T3 was 6% (4 mL/ min/1.73 m2), and the proportion of those with stage ≥3 CKD increased from 37% to 51%. CONCLUSIONS: Administration of NAC prior to RC was associated with a 17% decline in eGFR and a nearly doubled incidence of stage ≥3 CKD at one year after RC. Patients who underwent RC without NAC had a higher rate of stage ≥3 CKD at baseline but appeared to have less renal function loss at one year.
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.004 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 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".