Bibliographic record
Abstract
BACKGROUND: There is no therapy known to reduce the risk of complications or death after coronary bypass surgery. Because platelet activation constitutes a pivotal mechanism for injury in patients with atherosclerosis, we assessed whether early treatment with aspirin could improve survival after coronary bypass surgery. METHODS: At 70 centers in 17 countries, we prospectively studied 5065 patients undergoing coronary bypass surgery, of whom 5022 survived the first 48 hours after surgery. We gathered data on 7500 variables per patient and adjudicated outcomes centrally. The primary focus was to discern the relation between early aspirin use and fatal and nonfatal outcomes. RESULTS: During hospitalization, 164 patients died (3.2 percent), and 812 others (16.0 percent) had nonfatal cardiac, cerebral, renal, or gastrointestinal ischemic complications. Among patients who received aspirin (up to 650 mg) within 48 hours after revascularization, subsequent mortality was 1.3 percent (40 of 2999 patients), as compared with 4.0 percent among those who did not receive aspirin during this period (81 of 2023, P<0.001). Aspirin therapy was associated with a 48 percent reduction in the incidence of myocardial infarction (2.8 percent vs. 5.4 percent, P<0.001), a 50 percent reduction in the incidence of stroke (1.3 percent vs. 2.6 percent, P=0.01), a 74 percent reduction in the incidence of renal failure (0.9 percent vs. 3.4 percent, P<0.001), and a 62 percent reduction in the incidence of bowel infarction (0.3 percent vs. 0.8 percent, P=0.01). Multivariate analysis showed that no other factor or medication was independently associated with reduced rates of these outcomes and that the risk of hemorrhage, gastritis, infection, or impaired wound healing was not increased with aspirin use (odds ratio for these adverse events, 0.63; 95 percent confidence interval, 0.54 to 0.74). CONCLUSIONS: Early use of aspirin after coronary bypass surgery is safe and is associated with a reduced risk of death and ischemic complications involving the heart, brain, kidneys, and gastrointestinal tract.
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.000 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 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".