A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

A PHP Error was encountered

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

Exploratory clinical efficacy and patient-reported outcomes from NOVA: A randomized controlled study of intravenous natalizumab 6-week dosing versus continued 4-week dosing for relapsing-remitting multiple sclerosis. | LitMetric

AI Article Synopsis

Article Abstract

Background: Natalizumab (TYSABRI®) 300 mg administered intravenously every-4-weeks (Q4W) is approved for treatment of relapsing-remitting multiple sclerosis but is associated with increased risk of progressive multifocal leukoencephalopathy (PML). Extended natalizumab dosing intervals of approximately every-6-weeks (Q6W) are associated with a lower risk of PML. Primary and secondary clinical outcomes from the NOVA randomized clinical trial (NCT03689972) suggest that effective disease control is maintained in patients who were stable during treatment with natalizumab Q4W for ≥12 months and who then switched to Q6W dosing. We compared additional exploratory clinical and patient-reported outcomes (PROs) from NOVA to assess the efficacy of Q6W dosing.

Methods: Prespecified exploratory clinical efficacy endpoints in NOVA included change from baseline in Expanded Disability Status Scale (EDSS) score, Timed 25-Foot Walk (T25FW), dominant- and nondominant-hand 9-Hole Peg Test (9HPT), and Symbol Digit Modalities Test (SDMT). Exploratory patient-reported outcome (PRO) efficacy endpoints included change from baseline in the Treatment Satisfaction Questionnaire for Medication (TSQM), Neuro-QoL fatigue questionnaire, Multiple Sclerosis Impact Scale (MSIS-29), EuroQol 5 Dimensions (EQ-5D-5 L) index score, Clinical Global Impression (CGI)-Improvement (patient- and clinician-assessed) and CGI-Severity (clinician-assessed) rating scales. Estimated proportions of patients with confirmed EDSS improvement were based on Kaplan-Meier methods. Estimates of mean treatment differences for Q6W versus Q4W in other outcomes were assessed by least squares mean (LSM) and analyzed using a linear mixed model of repeated measures or ordinal logistic regression (CGI-scale).

Results: Exploratory clinical and patient-reported outcomes were assessed in patients who received ≥1 dose of randomly assigned study treatment and had ≥1 postbaseline efficacy assessment (Q6W group, n = 247, and Q4W group, n = 242). Estimated proportions of patients with EDSS improvement at week 72 were similar for Q6W and Q4W groups (11.7% [19/163] vs 10.8% [17/158]; HR 1.02 [95% confidence interval [CI], 0.53-1.98]; P = 0.9501). At week 72, there were no significant differences between Q6W and Q4W groups in LSM change from baseline for T25FW (0.00, P = 0.975), 9HPT (dominant [0.22, P = 0.533] or nondominant [0.09, P = 0.862] hand), or SDMT (-1.03, P = 0.194). Similarly, there were no significant differences between Q6W and Q4W groups in LSM change from baseline for any PRO (TSQM, -1.00, P = 0.410; Neuro-QoL fatigue, 0.52, P = 0.292; MSIS-29 Psychological, 0.67, P = 0.572; MSIS-29 Physical, 0.74, P = 0.429; EQ-5D-5 L, 0.00, P = 0.978). For the EQ-5D-5 L, a higher proportion of Q6W patients than Q4W patients demonstrated worsening (≥0.5 standard deviation increase in the EQ-5D-5 L index score; P = 0.0475). From baseline to week 72 for Q6W versus Q4W, odds ratio (ORs) of LSM change in CGI scores did not show meaningful differences between groups (CGI-Improvement [patient]: OR [95% CI] 1.2 [0.80-1.73]; CGI-Improvement [physician]: 0.8 [0.47-1.36]; CGI-Severity [physician]: 1.0 [0.71-1.54]).

Conclusions: No significant differences were observed in change from baseline to week 72 between natalizumab Q6W and Q4W groups for all exploratory clinical or PRO-related endpoints assessed. For the EQ-5D-5 L, a higher proportion of Q6W than Q4W patients demonstrated worsening.

Download full-text PDF

Source
http://dx.doi.org/10.1016/j.msard.2023.104561DOI Listing

Publication Analysis

Top Keywords

exploratory clinical
20
change baseline
20
q6w q4w
20
q4w groups
16
patient-reported outcomes
12
multiple sclerosis
12
q6w
12
differences q6w
12
lsm change
12
q4w
11

Similar Publications

Want AI Summaries of new PubMed Abstracts delivered to your In-box?

Enter search terms and have AI summaries delivered each week - change queries or unsubscribe any time!

A PHP Error was encountered

Severity: Notice

Message: fwrite(): Write of 34 bytes failed with errno=28 No space left on device

Filename: drivers/Session_files_driver.php

Line Number: 272

Backtrace:

A PHP Error was encountered

Severity: Warning

Message: session_write_close(): Failed to write session data using user defined save handler. (session.save_path: /var/lib/php/sessions)

Filename: Unknown

Line Number: 0

Backtrace: