Relationship of Platelet Reactivity With Bleeding Outcomes During Long‐Term Treatment With Dual Antiplatelet Therapy for Medically Managed Patients With Non‐ST‐Segment Elevation Acute Coronary Syndromes
Bibliographic record
Abstract
BACKGROUND: The relationship between "on-treatment" low platelet reactivity and longitudinal risks of major bleeding dual antiplatelet therapy following acute coronary syndromes remains uncertain, especially for patients who do not undergo percutaneous coronary intervention. METHODS AND RESULTS: reaction units; PRUs) and were randomized to aspirin+prasugrel versus aspirin+clopidogrel for up to 30 months. Contal's method was used to determine whether a cut point for steady-state PRU values could distinguish high versus low bleeding risk using 2-level composites: Global Use of Strategies to Open Occluded Coronary Arteries (GUSTO) severe/life-threatening or moderate bleeding unrelated to coronary artery bypass grafting (CABG) and non-CABG Thrombolysis In Myocardial Infarction (TIMI) major or minor bleeding. Exploratory analyses used 3-level composites that incorporated mild and minimal GUSTO and TIMI events. Continuous measures of PRUs (per 10-unit decrease) were not independently associated with the 2-level GUSTO (adjusted hazard ratio [HR], 1.01; 95% CI, 0.96-1.06) or TIMI composites (1.02; 0.98-1.07). Furthermore, no PRU cut point could significantly distinguish bleeding risk using the 2-level composites. However, the PRU cut point of 75 differentiated bleeding risk with the 3-level composites of GUSTO (26.5% vs 12.6%; adjusted HR, 2.28; 95% CI, 1.77-2.94; P<0.001) and TIMI bleeding events (25.9% vs 12.2%; adjusted HR, 2.30; 95% CI, 1.78-2.97; P<0.001). CONCLUSIONS: Among medically managed non-ST-segment elevation acute coronary syndromes patients receiving prolonged dual antiplatelet therapy, PRU values were not significantly associated with the long-term risk of major bleeding events, suggesting that low on-treatment platelet reactivity does not independently predict serious bleeding risk. CLINICAL TRIAL REGISTRATION: URL: http://www.clinicaltrials.gov. Unique identifier: NCT00699998.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.005 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".