A PHP Error was encountered

Severity: Warning

Message: fopen(/var/lib/php/sessions/ci_session2dpur1jdr7oqkfd5qbtfrv3jjvi3p7ir): 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

A PHP Error was encountered

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

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: 3098
Function: getPubMedXML

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

A PHP Error was encountered

Severity: Warning

Message: Attempt to read property "Count" on bool

Filename: helpers/my_audit_helper.php

Line Number: 3100

Backtrace:

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 3100
Function: _error_handler

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

Treatment effectiveness of alemtuzumab compared with natalizumab, fingolimod, and interferon beta in relapsing-remitting multiple sclerosis: a cohort study. | LitMetric

AI Article Synopsis

Article Abstract

Background: Alemtuzumab, an anti-CD52 antibody, is proven to be more efficacious than interferon beta-1a in the treatment of relapsing-remitting multiple sclerosis, but its efficacy relative to more potent immunotherapies is unknown. We compared the effectiveness of alemtuzumab with natalizumab, fingolimod, and interferon beta in patients with relapsing-remitting multiple sclerosis treated for up to 5 years.

Methods: In this international cohort study, we used data from propensity-matched patients with relapsing-remitting multiple sclerosis from the MSBase and six other cohorts. Longitudinal clinical data were obtained from 71 MSBase centres in 21 countries and from six non-MSBase centres in the UK and Germany between Nov 1, 2015, and June 30, 2016. Key inclusion criteria were a diagnosis of definite relapsing-remitting multiple sclerosis, exposure to one of the study therapies (alemtuzumab, interferon beta, fingolimod, or natalizumab), age 65 years or younger, Expanded Disability Status Scale (EDSS) score 6·5 or lower, and no more than 10 years since the first multiple sclerosis symptom. The primary endpoint was annualised relapse rate. The secondary endpoints were cumulative hazards of relapses, disability accumulation, and disability improvement events. We compared relapse rates with negative binomial models, and estimated cumulative hazards with conditional proportional hazards models.

Findings: Patients were treated between Aug 1, 1994, and June 30, 2016. The cohorts consisted of 189 patients given alemtuzumab, 2155 patients given interferon beta, 828 patients given fingolimod, and 1160 patients given natalizumab. Alemtuzumab was associated with a lower annualised relapse rate than interferon beta (0·19 [95% CI 0·14-0·23] vs 0·53 [0·46-0·61], p<0·0001) and fingolimod (0·15 [0·10-0·20] vs 0·34 [0·26-0·41], p<0·0001), and was associated with a similar annualised relapse rate as natalizumab (0·20 [0·14-0·26] vs 0·19 [0·15-0·23], p=0·78). For the disability outcomes, alemtuzumab was associated with similar probabilities of disability accumulation as interferon beta (hazard ratio [HR] 0·66 [95% CI 0·36-1·22], p=0·37), fingolimod (1·27 [0·60-2·70], p=0·67), and natalizumab (0·81 [0·47-1·39], p=0·60). Alemtuzumab was associated with similar probabilities of disability improvement as interferon beta (0·98 [0·65-1·49], p=0·93) and fingolimod (0·50 [0·25-1·01], p=0·18), and a lower probability of disability improvement than natalizumab (0·35 [0·20-0·59], p=0·0006).

Interpretation: Alemtuzumab and natalizumab seem to have similar effects on annualised relapse rates in relapsing-remitting multiple sclerosis. Alemtuzumab seems superior to fingolimod and interferon beta in mitigating relapse activity. Natalizumab seems superior to alemtuzumab in enabling recovery from disability. Both natalizumab and alemtuzumab seem highly effective and viable immunotherapies for multiple sclerosis. Treatment decisions between alemtuzumab and natalizumab should be primarily governed by their safety profiles.

Funding: National Health and Medical Research Council, and the University of Melbourne.

Download full-text PDF

Source
http://dx.doi.org/10.1016/S1474-4422(17)30007-8DOI Listing

Publication Analysis

Top Keywords

multiple sclerosis
24
interferon beta
20
relapsing-remitting multiple
20
effectiveness alemtuzumab
8
natalizumab fingolimod
8
fingolimod interferon
8
cohort study
8
patients relapsing-remitting
8
june 2016
8
annualised relapse
8

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!