Prior statin use and the incidence of in-hospital arrhythmia in acute coronary syndrome: A systematic review and meta-analysis
Bibliographic record
Abstract
The benefit of prior statin use to reduce the incidence of arrhythmia in acute coronary syndrome (ACS) is still a matter of debate. Statins have multiple pleiotropic effects, which may reduce the incidence of in-hospital arrhythmia. A systematic review and meta-analysis were performed to evaluate prior statin use and the incidence of in-hospital arrhythmia in ACS. This systematic review was conducted as per the Preferred Reporting Items for Systematic Reviews and Meta-analyses (PRISMA). We performed a literature search through Pubmed, Proquest, EBSCOhost, and Clinicaltrial.gov. A random-effect model was used due to moderate heterogeneity. Quality assessment was performed using Newcastle Ottawa Scale. Sensitivity analysis was performed by using leave one or two out method. PROSPERO registration number: CRD42022336402. Nine eligible studies consisting of 86,795 patients were included. A total of 22,130 (25.5%) patients were in statin use before the index ACS event. The prevalence of old myocardial infarction, heart failure, hypertension, diabetes mellitus, and chronic renal failure and concomitant treatment with aspirin, clopidogrel, and beta blocker was higher in the prior statin group compared to no previous statin. Overall, prior statin use was associated with a significantly lower incidence of in-hospital arrhythmia during ACS compared to no previous statin (OR 0.60; 95% CI 0.49–0.72; P < 0.00001; I2 = 54%, P-heterogeneity = 0.03). In subgroup analysis, previous statin use reduced the incidence of atrial fibrillation or atrial flutter (OR 0.64; 95% CI 0.43–0.95; P = 0.03; I2 = 73%, P-heterogeneity = 0.01) and ventricular tachycardia or ventricular fibrillation (OR 0.57; 95% CI 0.49–0.65; P < 0.00001; I2 = 8%, P-heterogeneity = 0.35). Based on aggregate patient data, prior statin use may reduce the incidence of in-hospital arrhythmia during ACS, particularly atrial fibrillation or atrial flutter and ventricular tachycardia or ventricular fibrillation.
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.013 | 0.034 |
| Meta-epidemiology (narrow) | 0.002 | 0.002 |
| Meta-epidemiology (broad) | 0.018 | 0.039 |
| Bibliometrics | 0.005 | 0.007 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.003 | 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".