Rivaroxaban for Thromboprophylaxis in Patients Undergoing Major Orthopedic Surgery
Bibliographic record
Abstract
OBJECTIVE: To review the pharmacology, pharmacokinetics, and clinical efficacy/safety profile of rivaroxaban to inform health-care professionals of this new agent for the prevention of venous thromboembolism (VTE) in patients undergoing major orthopedic surgery. DATA SOURCES: A literature search was performed in PubMed/MEDLINE (1966-March 2010), International Pharmaceutical Abstracts (1970-March 2010), and EMBASE (1990-March 2010), limited to publications in English, using the search terms BAY 59-7939, rivaroxaban, factor Xa inhibitor, hip replacement, and/or knee replacement to identify literature sources. References from retrieved articles were evaluated to identify relevant literature. Unpublished Phase 3 clinical trials in progress (using www.clinicaltrials.gov) were also reviewed. The Food and Drug Administration, European Medicines Agency, and Health Canada Web sites were used to retrieve product monographs, regulatory guidance, and advisory committee briefing packets. STUDY SELECTION AND DATA EXTRACTION: All available studies relevant to the pharmacology, pharmacokinetics, and clinical safety/efficacy of rivaroxaban for the prevention of VTE in patients undergoing major orthopedic surgery were included, with preference for clinical data. DATA SYNTHESIS: Rivaroxaban use was significantly more effective for thromboprophylaxis in patients undergoing total knee replacement (TKR) or total hip replacement (THR), compared to enoxaparin for the composite incidence of deep vein thrombosis, nonfatal pulmonary embolism, all-cause mortality, and the rate of major VTE; bleeding events occurred at statistically similar rates. In Phase 3 studies, rivaroxaban 10 mg was administered orally 6-8 hours post-surgery and post-hemostasis. Thereafter, administration was once daily for 35 days in THR and 10-14 days in TKR. CONCLUSIONS: Rivaroxaban has demonstrated comparable safety and superior efficacy to the commonly used low-molecular-weight heparin, enoxaparin. Ongoing and future clinical trials will allow clinicians to further assess the efficacy, safety, and pharmacoeconomics of rivaroxaban.
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.019 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.003 | 0.002 |
| Bibliometrics | 0.004 | 0.003 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| 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".