Is routine post-procedural anticoagulation warranted after primary percutaneous coronary intervention in ST-segment elevation myocardial infarction? Insights from the HORIZONS-AMI trial
Bibliographic record
Abstract
AIM: Post-procedural anticoagulation (AC) for routine prophylaxis may be administered after primary percutaneous coronary intervention (PCI) in ST-segment elevation myocardial infarction (STEMI), but the risks and benefits of this practice are uncertain. We therefore sought to assess the utility of routine post-procedural AC after primary PCI. METHODS AND RESULTS: Patients undergoing primary PCI in the Harmonizing Outcomes with Revascularization and Stents in Acute Myocardial Infarction (HORIZONS-AMI) trial were grouped according to whether they received post-PCI AC for routine prophylaxis. Outcomes were assessed using propensity-adjusted multivariable analysis. Among 2932 patients in whom primary PCI for STEMI was performed, 869 (29.6%) received post-PCI AC for routine prophylaxis (median duration four days) and 2063 (70.4%) received no post-PCI AC. Time from PCI to ambulation was similar in both groups (median 0.9 vs 1.0 days, p=0.40), although hospitalization was prolonged in patients receiving AC for routine prophylaxis (median 6.0 vs 4.0 days, p<0.0001). After propensity-adjustment, patients who received and did not receive AC for routine prophylaxis after PCI experienced similar rates of 30-day adverse ischemic and major bleeding events. Deep venous thrombosis or pulmonary emboli developed rarely (0.3%) within 30 days, and were not significantly reduced by use of post-PCI AC for routine prophylaxis. CONCLUSIONS: In this large-scale prospective study, use of post-procedural AC for routine prophylaxis was relatively common, and was not associated with improved clinical outcomes, although the duration of hospitalization was prolonged. These data suggest that post-PCI AC for routine prophylaxis may not provide benefit after successful primary PCI in patients in whom early ambulation is likely.
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.005 | 0.015 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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".