Severity: Warning
Message: fopen(/var/lib/php/sessions/ci_sessionlf75r5unl5pj5h07c3j2gmtb3sm60d4i): 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: 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
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
Patients with triple-class refractory (TCR) multiple myeloma (MM) have limited treatment options and poor prognoses. This high unmet need has prompted the development of new therapies allowing for improved outcomes for these patients. Recently, new targeted therapies for the treatment of patients with relapsed or refractory MM have been approved based on single-arm clinical trial results. Real-world (RW) data enable a better understanding of the effectiveness of new therapies in clinical practice and provide external controls for single-arm studies. However, using RW data to identify patients with TCR MM is challenging and subject to limitations. In this retrospective cohort study of an analysis of the COTA electronic health record (EHR) database, we used four algorithms to define refractory status and created four groups of patients with TCR MM initiating post-TCR therapy. Each algorithm relied on slightly different criteria to identify TCR patients, but all were based on the International Myeloma Working Group (IMWG)-derived and/or healthcare provider (HCP)-reported progressions within the database. A total of 3815 patients with newly diagnosed MM met the eligibility criteria for this study. The choice of the algorithm did not impact the characteristics of identified patients with TCR MM (Algorithm 1 [ = 404], Algorithm 2 [ = 123], Algorithm 3 [ = 404], and Algorithm 4 [ = 375]), including their demographic and disease characteristics, MM treatment history, or treatment patterns received after becoming TCR. However, identifying TCR MM using a combination of IMWG-derived and HCP-reported progressions allowed up to a 70% increase in the size of the identified group of patients compared with using only IMWG-derived progressions. In RW settings, progressions from both IMWG-derived data and physician reports may be used to identify patients with TCR MM.
Download full-text PDF |
Source |
---|---|
http://dx.doi.org/10.1080/03007995.2024.2333439 | DOI Listing |
Enter search terms and have AI summaries delivered each week - change queries or unsubscribe any time!