Role of thromboprophylaxis during neoadjuvant chemotherapy before radical cystectomy in patients with bladder cancer: Results of a multicenter retrospective cohort study.
Bibliographic record
Abstract
598 Background: Patients undergoing radical cystectomy are at risk of developing venous thromboembolic events (VTE), with most VTEs occurring during neoadjuvant chemotherapy. The ASCO Clinical Practice Guideline Update recommends thromboprophylaxis in cancer patients with a high risk of VTE and a low risk of bleeding. However, the risks of VTE and bleeding with or without thromboprophylaxis in bladder cancer patients scheduled for radical cystectomy have not been well evaluated. Methods: We conducted a retrospective cohort study of patients with non-metastatic bladder cancer undergoing cystectomy across 28 centers in 13 countries between 1990 and 2021. Inverse probability weighting analyses were performed to estimate the effect of thromboprophylaxis during neoadjuvant chemotherapy on VTE and bleeding. Results: Of 4886 patients, 4631 (95%) received neither thromboprophylaxis nor anticoagulation during chemotherapy. Thromboprophylaxis during neoadjuvant chemotherapy was prescribed in 151 (3%) patients mainly being enoxaparin (80%) with a median duration of 94 (range 38 to 104) days. In inverse probability weighting analyses, patients with thromboprophylaxis compared to patients without thromboprophylaxis during chemotherapy had not only a lower VTE (HR 0.32 [95% CI, 0.12 to 0.81], p-value = 0.016) but also a lower bleeding risk (HR 0.03 [95% CI, 0.09 to 0.12], p-value: <0.0001). Conclusions: In this retrospective analysis, the benefit of thromboprophylaxis during neoadjuvant chemotherapy before cystectomy is in line with data from randomized trials in other malignancies. Our data suggests thromboprophylaxis seems protective against VTEs during neoadjuvant chemotherapy in bladder cancer patients planned for cystectomy. The ASCO guidelines recommending thromboprophylaxis during chemotherapy should therefore also be regarded as a standard of care in patients treated with neoadjuvant chemotherapy before cystectomy.
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.003 | 0.006 |
| 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.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| 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".