Why the study?
Does continuous oral warfarin throughout pregnancy improve safety and efficacy compared to subcutaneous heparin in the 1st trimester followed by warfarin in pregnant women with mechanical heart valves?
Does continuous oral warfarin throughout pregnancy improve safety and efficacy compared to subcutaneous heparin in the 1st trimester followed by warfarin in pregnant women with mechanical heart valves?
Answers are grounded in this paper and cite their sources.
Continuous oral warfarin throughout pregnancy in women with mechanical heart valves appears safe with no observed coumarin-induced fetal malformations, suggesting that switching to heparin in the first trimester may not be mandatory.
Mechanical valve thrombosis is a life-threatening event, while pregnancy is associated with a hypercoagulable state. Thus, in pregnant women with mechanical valves, adequate anticoagulation becomes even more critical. This prospective study was conducted to establish a uniform anticoagulation regimen for these women. A total of 250 pregnancies in 245 women with mechanical heart valves were evaluated. The patients were divided into 2 groups: group 1 (n = 150) took oral warfarin throughout pregnancy and group 2 (n = 100) received subcutaneous heparin in the 1(st) trimester and oral warfarin for the other trimesters. Both groups received heparin at the time of delivery. There were no coumarin-induced fetal malformations. Minor thromboembolic episodes took place in 5 women in group 1 and 3 in group 2. Valve thrombosis occurred in 1 woman in group 2 and led to 1 maternal death in this series. The incidence of spontaneous abortion was similar between the groups. We conclude that warfarin is safe and convenient to use during pregnancy. The teratogenic effects of warfarin during the 1(st) trimester are overstated, and switching to heparin is not mandatory.
No takes yet. Share an insight, caveat, or question.
Geelani et al. (2005) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: