Low-Molecular-Weight Heparin as Bridging Anticoagulation During Interruption of Warfarin
Bibliographic record
Abstract
BACKGROUND: The treatment of patients at increased risk for arterial thromboembolism who require temporary interruption of warfarin sodium therapy is a common clinical problem. We investigated the efficacy and safety of a standardized periprocedural anticoagulation regimen with low-molecular-weight heparin. METHODS: We studied 650 consecutive patients with a mechanical heart valve, chronic atrial fibrillation, or embolic stroke who required interruption of warfarin therapy because of an invasive procedure. Warfarin was stopped 5 or 6 days before the procedure, and patients received subcutaneous dalteparin sodium, 100 IU/kg twice daily, starting 3 days before the procedure. The risk of postprocedural bleeding determined postprocedural anticoagulant management. In patients undergoing a non-high-bleeding-risk procedure who had adequate postprocedural hemostasis, warfarin was resumed on the evening of the procedure, and dalteparin sodium, 100 IU/kg twice daily, was resumed on the next day and continued until the international normalized ratio was 2.0 or more. If postprocedural hemostasis was not secured, the resumption of dalteparin was delayed. In patients undergoing a high-bleeding-risk procedure, warfarin was resumed on the evening of the procedure, but dalteparin was not given after the procedure. RESULTS: Patients were followed up during the preprocedural and postprocedural period for a mean of 13.8 days (range, 10-18 days). In 542 patients who underwent a non-high-bleeding-risk procedure, there were 2 thromboembolic events (0.4%), 4 major bleeding episodes (0.7%), and 32 episodes of increased wound-related blood loss that precluded postprocedural dalteparin administration (5.9%). In 108 patients who underwent a high-bleeding-risk procedure, there were 2 deaths (1.8%) possibly due to thromboembolism and 2 major bleeding episodes (1.8%). CONCLUSIONS: In patients at increased risk for arterial thromboembolism who require temporary interruption of warfarin therapy, a standardized periprocedural anticoagulant regimen with low-molecular-weight heparin is associated with a low risk of thromboembolic and major bleeding complications.
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.000 |
| 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.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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".