Enoxaparin and percutaneous coronary intervention: a Canadian perspective.
Bibliographic record
Abstract
BACKGROUND: The low molecular weight heparin enoxaparin is commonly used in the management of patients with non-ST segment elevation acute coronary syndromes (ACS). It is perceived that there is variable acceptance of the use of enoxaparin in patients with ACS in conjunction with percutaneous coronary intervention (PCI) by Canadian interventional cardiologists, as well as diverse approaches to the procedural (ie, PCI) management of anticoagulation. METHODS AND RESULTS: A survey assessing physician and centre demographics, as well as the opinion and approach to the use of enoxaparin in patients undergoing PCI, was developed. All 141 interventional cardiologists performing PCI in Canada were sent the survey, with a 52% response rate. The majority (64%) of respondents were comfortable performing PCI during enoxaparin treatment, but almost one-half (46.5%) stated a preference to have a point-of-care measurement of the anticoagulation level during the procedure. Various 'top-up' protocols are used across the country, including fixed-dose intravenous (IV) enoxaparin, weight-adjusted IV enoxaparin, fixed-dose IV unfractionated heparin, weight-adjusted IV unfractionated heparin and IV unfractionated heparin titrated to a target activated clotting time. Although the median time threshold for administering a 'top-up' dose of anticoagulation matched current recommendations, there was a wide variation ranging from 2 h to 10 h (median 8 h). CONCLUSIONS: Although the majority of Canadian interventional cardiologists were comfortable performing PCI in patients treated with enoxaparin, the survey demonstrated various levels of confidence and a diverse range of 'top-up' anticoagulation procedures. Nationwide guidelines for the management of anticoagulation in patients with ACS undergoing PCI with enoxaparin should be developed from the best available clinical and research evidence to limit potential patient risk of inadequate or excessive anticoagulation. This is especially relevant in view of the association between switching among anticoagulant therapies and an increased bleeding risk in patients undergoing early cardiac catheterization and PCI that was found in the recently reported Superior Yield of the New Strategy of Enoxaparin, Revascularization and Glycoprotein IIb/IIIa Inhibitors (SYNERGY) trial.
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.002 | 0.005 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.006 |
| Science and technology studies | 0.004 | 0.003 |
| Scholarly communication | 0.004 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.004 | 0.004 |
| Insufficient payload (model declined to judge) | 0.011 | 0.001 |
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".