Long‐term neurotoxicity effects of oxaliplatin added to fluorouracil and leucovorin as adjuvant therapy for colon cancer: Results from National Surgical Adjuvant Breast and Bowel Project trials C‐07 and LTS‐01
Bibliographic record
Abstract
BACKGROUND: Neurotoxicity from adjuvant treatment with oxaliplatin has been studied in patients with colorectal carcinoma in short-term studies, but, to the authors' knowledge, the current article is the first long-term assessment which reports the National Surgical Adjuvant Breast and Bowel Project (NSABP) investigation of whether excess neurotoxicity persists beyond 4 years. METHODS: As part of a colorectal cancer long-term survivor study (LTS-01), long-term neurotoxicity was assessed in 353 patients on NSABP Protocol C-07 (cross-sectional sample). Ninety-two of these patients from LTS-01 also had longitudinal data and were reassessed 5 to 8 years (median, 7 years) after random assignment (longitudinal sample). Contingency tables compared cohorts, a mixed model compared neurotoxicity between treatments over time, and a Wilcoxon rank-sum test compared neurotoxicity between treatments (cross-sectional sample). RESULTS: In the cross-sectional sample, the increase in mean total neurotoxicity scores of 1.8 with oxaliplatin was statistically significant (P = .005), but not clinically significant (a minimally important difference of 4 was reported at the long-term assessment). Patients who received oxaliplatin had increased odds of numbness and tingling in hands (odds ratio, 2.00; P = .015) and feet (odds ratio, 2.78; P < .001) versus patients who did not receive oxaliplatin. The magnitude of the oxaliplatin effect varied with time (P < .001) in the longitudinal sample, such that the oxaliplatin-treated group did not have significantly greater total neurotoxicity scores by 7 years. CONCLUSIONS: At the long-term endpoint, there was no clinically significant increase in total neurotoxicity scores for patients who received oxaliplatin, but the specific neurotoxicities of numbness and tingling of the hands and feet remained significantly elevated for oxaliplatin-treated patients.
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.008 | 0.009 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.001 |
| 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".