Venous thromboembolism incidence associated with pegylated asparaginase (ASP) compared to the native L‐ASP: A retrospective analysis with an ASP‐based protocol in adult patients <scp>with acute lymphoblastic leukaemia</scp>
Bibliographic record
Abstract
Venous thromboembolism (VTE) is a well-known complication in patients with acute lymphoblastic leukaemia (ALL) receiving asparaginase (ASP)-based chemotherapy, including the ASP-intensive Dana-Farber Cancer Institute (DFCI) 91-01 protocol for adults. Since 2019, native L-ASP is no longer available in Canada and was replaced by pegylated (PEG)-ASP. To determine whether the incidence of VTE has changed since switching from L-ASP to PEG-ASP, we conducted a single-centred retrospective cohort study. We included 245 adult patients with Philadelphia chromosome negative ALL between 2011 and 2021, with 175 from the L-ASP group (2011-2019) and 70 from the PEG-ASP group (2018-2021). During Induction, 10.29% (18/175) of patients who received L-ASP developed VTE, whereas 28.57% (20/70) of patients who received PEG-ASP developed VTE (p = 0.0035; odds ratio [OR] 3.35, 95% confidence interval [CI] 1.51-7.39), after adjusting for line type, gender, history of VTE, platelets at diagnosis. Similarly, during Intensification, 13.64% (18/132) of patients had VTE on L-ASP while 34.37% (11/32) of patients on PEG-ASP developed VTE (p = 0.0096; OR 3.96, 95% CI 1.57-9.96 with multivariable analysis). We found that PEG-ASP is associated with a higher incidence of VTE compared to L-ASP, both during Induction and Intensification, despite the administration of prophylactic anticoagulation. Further VTE mitigation strategies are needed in particular for adult patients with ALL receiving PEG-ASP.
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.004 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 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.000 | 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".