Alcohol Intake and Cardiovascular Outcomes in Patients With Atrial Fibrillation: <scp>RE</scp>‐<scp>LY AF</scp> Registry Analysis
Bibliographic record
Abstract
BACKGROUND: Alcohol intake increases recurrence of atrial fibrillation (AF), but its relationship with cardiovascular outcomes is less well characterized. We aimed to study the association between different levels of alcohol intake and cardiovascular outcomes in a global cohort of patients with AF. METHODS: This is a cross-sectional analysis of the RE-LY AF registry, including 15,400 patients with AF who visited emergency departments in 47 countries. Patients were categorized into abstainers, light (< 7 standard drinks [SD]/week), moderate (7-13 SD/week), and heavy drinkers (≥ 14 SD/week). Outcomes were stroke/systemic embolism, heart failure (HF) hospitalization, and major bleeding at 1-year follow-up. Logistic mixed-effects regression models were used to calculate multivariable-adjusted odds ratios (aOR) with a 95% confidence interval (CI). RESULTS: In total,14,058 patients (mean age = 65.9 ± 14.7 years, 48.0% women) with available alcohol intake level data were included. This consisted of 12,091 (86.0%) abstainers, 1150 (8.2%) light, 458 (3.3%) moderate, and 359 (2.6%) heavy drinkers. The odds of stroke/systemic embolism were not significantly different in light (aOR = 0.88, 95% CI: 0.60-1.28), moderate (aOR = 0.91, 95% CI: 0.53-1.57) or heavy drinkers (aOR = 0.79, 95% CI: 0.41-1.54) compared to abstainers. Major bleedings were numerically, but not statistically significantly, higher among heavy drinkers (aOR = 1.52, 95% CI: 0.82-2.80). Compared to abstainers, alcohol intake was associated with fewer HF hospitalizations (light: aOR = 0.73, 95% CI: 0.58-0.92; moderate: aOR = 0.53, 95% CI: 0.35-0.78; heavy: aOR = 0.63, 95% CI: 0.41-0.98). However, this protective association was observed only in upper-middle and high-income countries (p-interaction < 0.001). CONCLUSION: Alcohol drinking is unlikely to be associated with increased thromboembolic events in patients with AF, but may be associated with a lower risk of HF hospitalizations.
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.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| 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".