Severity: Warning
Message: fopen(/var/lib/php/sessions/ci_sessionl1raitrcomgdvmbohu21jvb6rcka3dr9): Failed to open stream: No space left on device
Filename: drivers/Session_files_driver.php
Line Number: 177
Backtrace:
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: session_start(): Failed to read session data: user (path: /var/lib/php/sessions)
Filename: Session/Session.php
Line Number: 137
Backtrace:
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Undefined array key "choices"
Filename: controllers/Detail.php
Line Number: 249
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 249
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 249
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 249
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: 8192
Message: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated
Filename: models/Detail_model.php
Line Number: 71
Backtrace:
File: /var/www/html/application/models/Detail_model.php
Line: 71
Function: strpos
File: /var/www/html/application/controllers/Detail.php
Line: 252
Function: insertAPISummary
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: 8192
Message: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated
Filename: helpers/my_audit_helper.php
Line Number: 8919
Backtrace:
File: /var/www/html/application/helpers/my_audit_helper.php
Line: 8919
Function: str_replace
File: /var/www/html/application/controllers/Detail.php
Line: 255
Function: formatAIDetailSummary
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Undefined array key "choices"
Filename: controllers/Detail.php
Line Number: 256
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 256
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 256
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Undefined array key "usage"
Filename: controllers/Detail.php
Line Number: 257
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 257
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 257
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 257
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Undefined array key "usage"
Filename: controllers/Detail.php
Line Number: 258
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 258
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 258
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 258
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Undefined array key "usage"
Filename: controllers/Detail.php
Line Number: 259
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 259
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 259
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 259
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Undefined array key "usage"
Filename: controllers/Detail.php
Line Number: 260
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 260
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 260
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: file_get_contents(https://...@gmail.com&api_key=61f08fa0b96a73de8c900d749fcb997acc09): Failed to open stream: HTTP request failed! HTTP/1.1 429 Too Many Requests
Filename: helpers/my_audit_helper.php
Line Number: 143
Backtrace:
File: /var/www/html/application/helpers/my_audit_helper.php
Line: 143
Function: file_get_contents
File: /var/www/html/application/helpers/my_audit_helper.php
Line: 209
Function: simplexml_load_file_from_url
File: /var/www/html/application/helpers/my_audit_helper.php
Line: 994
Function: getPubMedXML
File: /var/www/html/application/helpers/my_audit_helper.php
Line: 3134
Function: GetPubMedArticleOutput_2016
File: /var/www/html/application/controllers/Detail.php
Line: 574
Function: pubMedSearch_Global
File: /var/www/html/application/controllers/Detail.php
Line: 488
Function: pubMedGetRelatedKeyword
File: /var/www/html/index.php
Line: 316
Function: require_once
Background: Although most patients with epithelial ovarian cancer respond to frontline platinum-based chemotherapy, around 70% will relapse within 3 years. The phase 3 JAVELIN Ovarian 100 trial compared avelumab (anti-PD-L1 monoclonal antibody) in combination with chemotherapy followed by avelumab maintenance, or chemotherapy followed by avelumab maintenance, versus chemotherapy alone in patients with treatment-naive epithelial ovarian cancer.
Methods: JAVELIN Ovarian 100 was a global, open-label, three-arm, parallel, randomised, phase 3 trial run at 159 hospitals and cancer treatment centres in 25 countries. Eligible women were aged 18 years and older with stage III-IV epithelial ovarian, fallopian tube, or peritoneal cancer (following debulking surgery, or candidates for neoadjuvant chemotherapy), and had an Eastern Cooperative Oncology Group performance status of 0 or 1. Patients were randomly assigned (1:1:1) via interactive response technology to receive chemotherapy (six cycles; carboplatin dosed at an area under the serum-concentration-time curve of 5 or 6 intravenously every 3 weeks plus paclitaxel 175 mg/m every 3 weeks or 80 mg/m once a week [investigators' choice]) followed by avelumab maintenance (10 mg/kg intravenously every 2 weeks; avelumab maintenance group); chemotherapy plus avelumab (10 mg/kg intravenously every 3 weeks) followed by avelumab maintenance (avelumab combination group); or chemotherapy followed by observation (control group). Randomisation was in permuted blocks of size six and stratified by paclitaxel regimen and resection status. Patients and investigators were masked to assignment to the two chemotherapy groups without avelumab at the time of randomisation until completion of the chemotherapy phase. The primary endpoint was progression-free survival assessed by blinded independent central review in all randomly assigned patients (analysed by intention to treat). Safety was analysed in all patients who received at least one dose of study treatment. This trial is registered with ClinicalTrials.gov, NCT02718417. The trial was fully enrolled and terminated at interim analysis due to futility, and efficacy is no longer being assessed.
Findings: Between May 19, 2016 and Jan 23, 2018, 998 patients were randomly assigned (avelumab maintenance n=332, avelumab combination n=331, and control n=335). At the planned interim analysis (data cutoff Sept 7, 2018), prespecified futility boundaries were crossed for the progression-free survival analysis, and the trial was stopped as recommended by the independent data monitoring committee and endorsed by the protocol steering committee. Median follow-up for progression-free survival for all patients was 10·8 months (IQR 7·1-14·9); 11·1 months (7·0-15·3) for the avelumab maintenance group, 11·0 months (7·4-14·5) for the avelumab combination group, and 10·2 months (6·7-14·0) for the control group. Median progression-free survival was 16·8 months (95% CI 13·5-not estimable [NE]) with avelumab maintenance, 18·1 months (14·8-NE) with avelumab combination treatment, and NE (18·2 months-NE) with control treatment. The stratified hazard ratio for progression-free survival was 1·43 (95% CI 1·05-1·95; one-sided p=0·99) with the avelumab maintenance regimen and 1·14 (0·83-1·56; one-sided p=0·79) with the avelumab combination regimen, versus control treatment. The most common grade 3-4 adverse events were anaemia (69 [21%] patients in the avelumab maintenance group, 63 [19%] in the avelumab combination group, and 53 [16%] in the control group), neutropenia (91 [28%], 99 [30%], and 88 [26%]), and neutrophil count decrease (49 [15%], 45 [14%], and 59 [18%]). Serious adverse events of any grade occurred in 92 (28%) patients in the avelumab maintenance group, 118 (36%) in the avelumab combination group, and 64 (19%) in the control group. Treatment-related deaths occurred in one (<1%) patient in the avelumab maintenance group (due to atrial fibrillation) and one (<1%) patient in the avelumab combination group (due to disease progression).
Interpretation: Although no new safety signals were observed, results do not support the use of avelumab in the frontline treatment setting. Alternative treatment regimens are needed to improve outcomes in patients with advanced epithelial ovarian cancer.
Funding: Pfizer and Merck KGaA, Darmstadt, Germany.
Download full-text PDF |
Source |
---|---|
http://dx.doi.org/10.1016/S1470-2045(21)00342-9 | DOI Listing |
Enter search terms and have AI summaries delivered each week - change queries or unsubscribe any time!