Individualized treatment with sunitinib versus standard dosing with sunitinib or pazopanib in patients with metastatic renal cell carcinoma (mRCC): Results from the Canadian Kidney Cancer information system (CKCis).
Bibliographic record
Abstract
468 Background: Recent analysis using CKCis, a prospective database, showed that mRCC patients receiving first-line sunitinib (S) had better survival than patients receiving pazopanib (P) and greater than expected absolute survival in the real world setting. We conducted further analyses to see if an individualized approach (treatment starting at standard dose/schedule with subsequent schedule/dose alterations based on toxicity) using S results in better outcomes in mRCC patients. Methods: Patients within CKCis diagnosed with clear cell mRCC treated with first-line S or P between January 2011 to December 2015 were analyzed by three treatment groups: 1) S as per individualized approach (SI), 2) S as per product monograph (SS), or 3) P as per product monograph (PS). Overall survival (OS) and time-to-treatment failure (TTF) were calculated. Cox regression analysis allowed for adjustment of International Metastatic RCC Database Consortium (IMDC) criteria with age as a continuous variable. Results: A total of 573 patients were identified, 261 patients in SI, 201 patients in SS, and 111 patients in PS. Differences in baseline characteristics were noted (Table). Median OS was improved in SI vs. SS (40.8 vs. 22.6 months (m), p<0.001) and SI vs. PS (40.8 vs. 20.3 m, p<0.001). TTF was better in SI vs. SS (16.6 vs. 5.4 m, p<0.001) and SI vs. PS (16.6 vs. 7.0 m, p<0.001). SS vs. PS showed no difference in median OS (22.6 vs. 20.3 m, p=0.76) or TTF (5.4 vs. 7.0 m, p=0.11). Adjusted hazard ratio showed significance in SS vs. SI (OS 1.81, p=0.004 TTF 2.42, p<0.001) and PS vs. SI (OS 3.16, p<0.001; TTF 2.03, p<0.001). Conclusions: Significant improvement in OS and TTF is seen using an individualized approach to mRCC patients, further supporting the growing body of evidence endorsing this practice. Further prospective validation awaits from the NCT01499121 study. [Table: see text]
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.002 | 0.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.002 |
| 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.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".