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: Late gadolinium-enhanced cardiovascular magnetic resonance imaging overestimates infarct size and underestimates recovery of dysfunctional segments acutely post ST-segment-elevation myocardial infarction. We assessed whether cardiovascular magnetic resonance imaging-derived segmental myocardial strain and markers of myocardial injury could improve the accuracy of late gadolinium-enhancement in predicting functional recovery after ST-segment-elevation myocardial infarction.
Methods And Results: A total of 164 ST-segment-elevation myocardial infarction patients underwent acute (median 3 days) and follow-up (median 9.4 months) cardiovascular magnetic resonance imaging. Wall-motion scoring, feature tracking-derived circumferential strain (Ecc), segmental area of late gadolinium-enhancement (SEE), microvascular obstruction, intramyocardial hemorrhage, and salvage index (MSI) were assessed in 2624 segments. We used logistic regression analysis to identify markers that predict segmental recovery. At acute CMR 32% of segments were dysfunctional, and at follow-up CMR 19% were dysfunctional. Segmental function at acute imaging and odds ratio (OR) for functional recovery decreased with increasing SEE, although 33% of dysfunctional segments with SEE 76% to 100% improved. SEE was a strong predictor of functional improvement and normalization (area under the curve [AUC], 0.840 [95% confidence interval {CI}, 0.814-0.867]; OR, 0.97 [95% CI, 0.97-0.98] per +1% SEE for improvement and AUC, 0.887 [95% CI, 0.865-0.909]; OR, 0.95 [95% CI, 0.94-0.96] per +1% SEE for normalization). Its predictive accuracy for improvement, as assessed by areas under the receiver operator curves, was similar to that of MSI (AUC, 0.840 [95% CI, 0.809-0.872]; OR, 1.03 [95% CI, 1.02-1.03] per +1% MSI for improvement and AUC, 0.862 [0.832-0.891]; OR, 1.04 [95% CI, 1.03-1.04] per +1% SEE for normalization) and Ecc (AUC, 0.834 [95% CI, 0.807-0.862]; OR, 1.05 [95% CI, 1.03-1.07] per +1% MSI for improvement and AUC, 0.844 [95% CI, 0.818-0.871]; OR, 1.07 [95% CI, 1.05-1.10] per +1% SEE for normalization), and for normalization was greater than the other predictors. MSI and Ecc remained as significant after adjustment for SEE but provided no significant increase in predictive accuracy for improvement and normalization compared with SEE alone. MSI had similar predictive accuracy to SEE for functional recovery but was not assessable in 25% of patients. Microvascular obstruction provided no incremental predictive accuracy above SEE.
Conclusions: This multicenter study confirms that SEE is a strong predictor of functional improvement post ST-segment-elevation myocardial infarction, but recovery occurs in a substantial proportion of dysfunctional segments with SEE >75%. Feature tracking-derived Ecc and MSI provide minimal incremental benefit to SEE in predicting segmental recovery.
Clinical Trial Registration: URL: http://www.isrctn.com. Unique identifier: ISRCTN70913605.
Download full-text PDF |
Source |
---|---|
http://dx.doi.org/10.1161/CIRCIMAGING.115.003457 | DOI Listing |
Enter search terms and have AI summaries delivered each week - change queries or unsubscribe any time!