We use a few cookies

Essential cookies keep the library working. With your permission, we'd also like to use analytics to see what's useful and improve the experience. Read our Privacy Policy or Cookie Policy.

Skip to main content
Home/e-Resources/Life Sciences/A framework for managing severe DOAC-related bleeding: Recognize, Reverse, Resume, Reduce
PeriodicalsLife Sciences

A framework for managing severe DOAC-related bleeding: Recognize, Reverse, Resume, Reduce

Checking your access to this record.

Abstract & Overview

Bleeding is the main complication of treatment with anticoagulants, the most common adverse drug event that leads to emergency department visits, hospital admission, and death. While direct oral anticoagulants (DOACs) reduce the risk of major, fatal and intracranial bleeding compared to vitamin K antagonists, DOAC-associated bleeding is associated with substantial short-term mortality rates. To optimize management and improve outcomes, a standardized approach to managing severe bleeding includes rapid recognition, provision of treatments to reverse anticoagulation or enhance hemostasis, resumption of anticoagulation safety after bleed cessation and attention to secondary prevention measures and long-term monitoring. This narrative review outlines a pragmatic multimodal framework for severe DOAC bleed management with case examples to illustrate key principles.

Cite this record

Stephane Cormier, Deborah M. Siegal (2024). A framework for managing severe DOAC-related bleeding: Recognize, Reverse, Resume, Reduce. Thrombosis Update, 15, 100165–100165. https://doi.org/10.1016/j.tru.2024.100165

Copy in another style

Cormier, S., & Siegal, D. M. (2024). A framework for managing severe DOAC-related bleeding: Recognize, Reverse, Resume, Reduce. Thrombosis Update, 15, 100165–100165. https://doi.org/10.1016/j.tru.2024.100165
Author names are used as deposited, so check their order before you submit.

Metadata is harvested from open-access indexes and can be incomplete. Check a citation against the published version before relying on it — see our open access & attribution policy.