Abstract 16418: Reinitiation of Antithrombotic Therapy After Emergency Procedures or After an Uncontrolled or Life Threatening Bleeding Event. Initial Experience From the Re-verse Ad Trial
Bibliographic record
Abstract
Background: In AF patients, oral anticoagulation is effective for stroke risk reduction, but there is uncertainty on how to manage re-initiation of anticoagulation after a bleeding complication. Ideally, therapy would be stopped immediately and reinitiated as soon as possible after the bleeding has resolved. In clinical trials comparing dabigatran to warfarin, urgent interventions were linked to higher rates of both bleeding and thromboembolic events than elective interventions. Idarucizumab immediately reverses the anticoagulant effects of dabigatran without prothrombotic effect. Due to idarucizumab’s specificity to dabigatran, other drug-drug interaction is not expected, allowing the clinician flexibility in managing antithrombotic therapy during and after the event. Methods: In the ongoing phase III RE-VERSE AD study, dabigatran-treated patients with uncontrolled bleeding (Group A) or who require emergency surgery (Group B) are given 5 g of idarucizumab IV. The primary endpoint was median maximum reversal of the anticoagulant effect of dabigatran, based on dilute thrombin time (dTT) or ecarin clotting time (ECT) within 4 h of study drug infusion. Data collection on re-initiation of antithrombotic therapy was studied as a secondary endpoint. Results: In the interim analysis of 90 patients, median maximum reversal of the anticoagulant effect of dabigatran was 100%. For antithrombotic re-initiation data, see Table. Conclusions: Idarucizumab is an immediate-acting, specific reversal agent for dabigatran. Preliminary results from RE-VERSE AD suggest that idarucizumab facilitates the periprocedural management of dabigatran-treated patients. Of note is that after an acute event, alternative antithrombotic therapy can be initiated at any time after idarucizumab application. Reintroduction of dabigatran was possible as early as 24 h after idarucizumab treatment. This is desirable to protect patients from their underlying thromboembolic risk.
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.004 | 0.003 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.002 | 0.002 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.001 | 0.003 |
| Insufficient payload (model declined to judge) | 0.004 | 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".