The safety of antithrombotic therapy during pregnancy
Bibliographic record
Abstract
A number of clinical conditions can require the use of antithrombotic drugs during pregnancy. These mainly include prevention of venous thromboembolism (VTE) and fetal complications in high-risk patients, treatment of VTE and prevention of arterial emboli in patients with mechanical heart valve prostheses. However, there are several problems when using antithrombotic drugs during pregnancy. Warfarin, as well as the other coumarin compounds, crosses the placenta and has the potential to cause both bleeding in the fetus and teratogenicity, therefore its use is not recommended during the first trimester and during the perinatal period. Unfractionated heparin (UFH) and low molecular weight heparin (LMWH) do not cross the placenta and are safe for the fetus, but long-term treatment with UFH is problematic because of its inconvenient administration, the need to monitor anticoagulant activity and because of its potential side effects, such as heparin-induced thrombocytopenia and osteoporosis. LMWH is the drug of choice in the prevention and treatment of VTE during pregnancy because of its practical advantages over UFH and because of a lower risk of side effects. Patients with mechanical heart valve prostheses represent a major clinical challenge. Warfarin, the drug of choice in non-pregnant women, can be administered between the 12th and 36th week. Full-dose UFH is recommended in the first trimester and after week 36. The use of LMWH as an alternative to UFH is still a matter of debate, because inadequate data are available.
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.002 | 0.008 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.003 | 0.002 |
| Insufficient payload (model declined to judge) | 0.005 | 0.002 |
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".