A PHP Error was encountered

Severity: Warning

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

Randomized assessment of ticagrelor versus prasugrel antiplatelet effects in patients with ST-segment-elevation myocardial infarction. | LitMetric

AI Article Synopsis

Article Abstract

Background: Ticagrelor and prasugrel provide stronger platelet inhibition compared with clopidogrel. Direct pharmacodynamic comparison between them has not yet been reported in ST-segment-elevation myocardial infarction patients.

Methods And Results: In a prospective, single-center, single-blind study, 55 out of 117 (47%) screened consecutive ST-segment-elevation myocardial infarction patients undergoing primary percutaneous coronary intervention were randomized to either ticagrelor 180 mg loading followed by 90 mg bid, or prasugrel 60 mg loading followed by 10 mg od for 5 days. Platelet reactivity (PR) was assessed with the VerifyNow P2Y12 function assay and the Multiplate Analyzer at 0, 1, 2, 6, 24 hours, and 5 days postrandomization. The primary end point, PR with VerifyNow at hour 1, did not differ significantly between patients randomized to ticagrelor versus prasugrel (257.3 P2Y12 reaction unit [PRU], 95% CI 230.8-283.8 versus 231.3 PRU, 95% CI 205.3-257.4; P=0.2). PR did not differ at 2, 6, and 24 hours, although at day 5 it was lower with ticagrelor than prasugrel (25.6 PRU, 95% CI 12.3-38.9 versus 50.3 PRU, 95% CI 36.4-64.1; P=0.01). At hour 2, high on-treatment PR rates (cutoff 208 PRU) were 46.2% and 34.6% for ticagrelor and prasugrel, respectively, decreased significantly thereafter, whereas did not differ significantly between the 2 agents at all the time points of the study.

Conclusions: In patients with ST-segment-elevation myocardial infarction undergoing primary percutaneous coronary intervention, both ticagrelor and prasugrel exhibit an initial delay in the onset of their antiplatelet action. Ticagrelor did not appear superior to prasugrel in reducing PR during the first 24 hours of ST-segment-elevation myocardial infarction.

Clinical Trial Registration: URL: http://www.clinicaltrials.gov. Unique identifier: NCT01463163.

Download full-text PDF

Source
http://dx.doi.org/10.1161/CIRCINTERVENTIONS.112.972323DOI Listing

Publication Analysis

Top Keywords

st-segment-elevation myocardial
20
myocardial infarction
16
ticagrelor prasugrel
16
pru 95%
12
ticagrelor
8
ticagrelor versus
8
prasugrel
8
versus prasugrel
8
patients st-segment-elevation
8
undergoing primary
8

Similar Publications

Background: The peak incidence of cardiovascular diseases (CVD) usually occurs in the morning. This study aimed to investigate the exact distribution pattern of peak incidence of ST-segment elevation myocardial infarction (STEMI) in the Chinese population, and to explore whether it is associated with the prognosis.

Methods: This study included 7,805 patients with STEMI from the multicenter, prospective AMI cohort in China, for whom had a definite time of symptom onset.

View Article and Find Full Text PDF

Background: In patients with ST-segment elevation myocardial infarction (STEMI) and multivessel coronary artery disease, the optimal management strategy for non-culprit lesions is a subject of ongoing debate. There has been an increasing use of physiology-guidance to assess the extent of occlusion in non-culprit lesions, and hence the need for stenting. Fractional flow reserve (FFR) is commonly used as a technique.

View Article and Find Full Text PDF

Background: In this study, we aimed to investigate the prognostic implications of lead aVR ST-segment elevation in an initial electrocardiogram (ECG) in patients diagnosed with acute coronary syndrome (ACS). Furthermore, we evaluated the association between electrocardiographic changes in lead aVR and objective measures such as angiographic findings and Syntax score.

Methods: This retrospective cohort study, conducted as a pilot study, encompassing both a retrospective cross-sectional analysis and a longitudinal follow-up, took place at Chamran Hospital from November 2017 to October 2019.

View Article and Find Full Text PDF

This comprehensive analysis by Saeed and Faeq investigates the impact of primary percutaneous coronary intervention (pPCI) on mortality among patients with ST-segment elevation myocardial infarction (STEMI) at the Erbil Cardiac Center. Analyzing data from 96 consecutive STEMI patients, the study identified significant predictors of in-hospital mortality, emphasizing the critical impact of time of hospital arrival post-symptom onset on overall prognosis. Findings indicate that factors such as atypical presentation, cardiogenic shock, chronic kidney disease, and specific coronary complications are associated with higher mortality rates.

View Article and Find Full Text PDF

Background: Primary percutaneous coronary intervention (PCI) is crucial in managing acute ST-segment elevation myocardial infarction (STEMI), emphasizing the importance of optimal myocardial reperfusion.

Objective: The goal of this research was to determine how loading doses of rosuvastatin and atorvastatin affected the flow rate of thrombolysis in myocardial infarction (TIMI) immediately post-perfusion thrombolysis in patients undergoing primary PCI.

Methodology: This prospective, comparative study was carried out over a one-year period (January 2023 to December 2023) in Pakistan.

View Article and Find Full Text PDF

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!