MétaCan
Menu
Back to cohort
Record W2959096163 · doi:10.1001/jamaoncol.2019.1588

Durvalumab With or Without Tremelimumab for Patients With Metastatic Pancreatic Ductal Adenocarcinoma

2019· article· en· W2959096163 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueJAMA Oncology · 2019
Typearticle
Languageen
FieldMedicine
TopicPancreatic and Hepatic Oncology Research
Canadian institutionsPrincess Margaret Cancer Centre
FundersNational Cancer InstituteAstraZeneca
KeywordsDurvalumabMedicineTremelimumabGemcitabineInternal medicinePopulationCombination therapyOncologySurgeryCancerImmunotherapyIpilimumabNivolumab

Abstract

fetched live from OpenAlex

IMPORTANCE: New therapeutic options for patients with metastatic pancreatic ductal adenocarcinoma (mPDAC) are needed. This study evaluated dual checkpoint combination therapy in patients with mPDAC. OBJECTIVE: To evaluate the safety and efficacy of the anti-PD-L1 (programmed death-ligand 1) antibody using either durvalumab monotherapy or in combination with the anticytotoxic T-lymphocyte antigen 4 antibody using durvalumab plus tremelimumab therapy in patients with mPDAC. DESIGN, SETTING, AND PARTICIPANTS: Part A of this multicenter, 2-part, phase 2 randomized clinical trial was a lead-in safety, open-label study with planned expansion to part B pending an efficacy signal from part A. Between November 26, 2015, and March 23, 2017, 65 patients with mPDAC who had previously received only 1 first-line fluorouracil-based or gemcitabine-based treatment were enrolled at 21 sites in 6 countries. Efficacy analysis included the intent-to-treat population; safety analysis included patients who received at least 1 dose of study treatment and for whom any postdose data were available. INTERVENTIONS: Patients received durvalumab (1500 mg every 4 weeks) plus tremelimumab (75 mg every 4 weeks) combination therapy for 4 cycles followed by durvalumab therapy (1500 mg every 4 weeks) or durvalumab monotherapy (1500 mg every 4 weeks) for up to 12 months or until the onset of progressive disease or unacceptable toxic effects. MAIN OUTCOMES AND MEASURES: Safety and efficacy were measured by objective response rate, which was used to determine study expansion to part B. The threshold for expansion was an objective response rate of 10% for either treatment arm. RESULTS: Among 65 randomized patients, 34 (52%) were men and median age was 61 (95% CI, 37-81) years. Grade 3 or higher treatment-related adverse events occurred in 7 of 32 patients (22%) receiving combination therapy and in 2 of 32 patients (6%) receiving monotherapy; 1 patient randomized to the monotherapy arm did not receive treatment owing to worsened disease. Fatigue, diarrhea, and pruritus were the most common adverse events in both arms. Overall, 4 of 64 patients (6%) discontinued treatment owing to treatment-related adverse events. Objective response rate was 3.1% (95% CI, 0.08-16.22) for patients receiving combination therapy and 0% (95% CI, 0.00-10.58) for patients receiving monotherapy. Low patient numbers limited observation of the associations between treatment response and PD-L1 expression or microsatellite instability status. CONCLUSION AND RELEVANCE: Treatment was well tolerated, and the efficacy of durvalumab plus tremelimumab therapy and durvalumab monotherapy reflected a population of patients with mPDAC who had poor prognoses and rapidly progressing disease. Patients were not enrolled in part B because the threshold for efficacy was not met in part A. TRIAL REGISTRATION: ClinicalTrials.gov identifier: NCT02558894.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.091
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0020.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.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.

Opus teacher head0.031
GPT teacher head0.337
Teacher spread0.306 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it