<scp>ECLIPSES</scp>: Early initiation of sodium glucose <scp>cotransporter</scp>‐2 inhibitors for <scp>cardiovascular</scp> protection in patients with type 2 diabetes following acute coronary syndrome and <scp>subsequent</scp> coronary artery bypass graft surgery
Bibliographic record
Abstract
INTRODUCTION: There is a paucity of data evaluating early initiation of sodium-glucose cotransporter-2 inhibitors (SGLT2i) in patients with diabetes following acute coronary syndrome (ACS) and coronary artery bypass graft surgery (CABG). OBJECTIVES: To describe the efficacy and safety of SGLT2i initiated early after CABG in patients with type 2 diabetes who experienced ACS. METHODS: This is a retrospective cohort study of patients with type 2 diabetes (T2DM) who experienced ACS and subsequent CABG with follow up at 3 and 12 months. Patients who filled a SGLT2i prescription within 14 days of discharge were allocated to the SGLT2i group and those who did not were included in the no SGLT2i group. The primary efficacy end point was first occurrence of a 4-point Major Adverse Cardiovascular Event (MACE), and the primary safety end point was a composite of hypoglycemia, hypotension, diabetic ketoacidosis, acute kidney injury, and urinary tract infection. Secondary end points included a comparative analysis of the primary outcome, 30-day readmission rates, and subgroup analyses of key populations. RESULTS: A total of 1629 patients were included: 226 received a SGLT2i within 14 days of discharge and 1403 did not. At 12 months, 8.9% and 15.3% of patients experienced MACE in the SGLT2i and no SGLT2i groups, respectively (adjusted Hazard Ratio [aHR] 0.65, 95% confidence interval [CI] 0.41-1.04). The primary safety outcome occurred in 12.0% of the SGLT2i group and 19.1% of the no SGLT2i group at 12 months (aHR 0.68, 95% CI 0.45-1.01). CONCLUSION: Early initiation of SGLT2i use was not associated with a reduction in MACE in patients with T2DM who experienced ACS and underwent subsequent CABG surgery. However, no apparent safety concerns were identified. Adequately powered trials are required to confirm this finding.
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.001 | 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.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".