A conservative, traceable, neuraxial-aware planner that surfaces stop/restart timing, renal considerations, and clear source citations for peri-procedure anticoagulation.
We do not invent new clinical rules. Where MDACC or ASRA-derived summaries are silent, the tool presents a conservative warning and advises consultation with Hematology/Anesthesia.
This tool supports, not replaces, clinical judgment. Always confirm local policy and current ASRA guidance for neuraxial catheters. Do not enter patient identifiers. The calculator is for planning logic, not patient data storage. Use is at the clinician’s discretion, contingent on secure hemostasis and individual patient factors.
Independence notice: This is an independent project that is not affiliated with, sponsored by, or endorsed by MD Anderson Cancer Center. It implements their published guidance for clarity and ease of use and cites the relevant tables/appendices so users can verify each step.
Apixaban, rivaroxaban, edoxaban, dabigatran: hold/restart intervals follow MDACC tables/appendices with renal-tier handling (especially for dabigatran) and neuraxial hard stops. No DOAC dosing while a neuraxial catheter is in place; restart on the later of baseline timing or catheter-removal gap per ASRA/Stanford guidance. Governance: Do not bridge DOACs. Very-high risk adds Appendix I p.31 advisory; no auto-bridging schedule.
Standard 5-day pre-procedure hold; restart windows by bleeding risk. INR governance: check INR pre-procedure; target <1.5; correct or delay if ≥1.5 within 24–48 h. Bridging appears only for high/very-high thrombosis risk and respects renal function (UFH preference if CrCl <30).
Pre-procedure stops and post-procedure restarts per MDACC. Neuraxial catheter gating applies: no dosing while a catheter is in place; restart on the later of baseline timing or removal gap; verify aPTT normalization for UFH.
The calculator runs client-side and does not store patient identifiers. We may use aggregate, privacy-friendly analytics (e.g., page views) to guide improvements—no PHI is collected. If you submit feedback with contact details, we will use it only to respond to your message or improve the tool.