Is rivaroxaban associated with lower inpatient costs compared to warfarin among patients with non-valvular atrial fibrillation?
Bibliographic record
Abstract
BACKGROUND: Warfarin has been the mainstay treatment used by patients with a moderate-to-high risk of stroke due to non-valvular atrial fibrillation (NVAF). Unlike rivaroxaban, laboratory monitoring to allow the attainment of the prothrombin time international normalized ratio goal is required with warfarin, thereby potentially increasing a patient's hospitalization costs. OBJECTIVE: To compare hospitalization costs between hospitalized NVAF patients using rivaroxaban versus warfarin in a real-world setting. METHODS: A retrospective claims analysis was conducted using the Premier Perspective Comparative Hospital Database from November 2010 to September 2012. The study included adult patients hospitalized for NVAF after November 2011. Patients using rivaroxaban during hospitalization were matched with up to four warfarin users by propensity score analyses. Hospitalization costs were compared between the matched cohorts using generalized estimating equations. A sub-analysis was performed for patients who were first administered their treatment on day three or later of their hospital stay. Sensitivity analyses were conducted on matched cohorts with a primary diagnosis of AF. RESULTS: The matched cohorts' (2809 rivaroxaban and 11,085 warfarin users) characteristics were well balanced. The mean age of cohorts was 71 years and 49% of patients were female. The average hospitalization cost of rivaroxaban users was $11,993 compared to $13,255 for warfarin users. The cost difference was significantly lower by $1284 (P < 0.001). Patients who were administered rivaroxaban treatment on day three or after incurred significantly lower hospitalization costs (cost difference: $4350; P < 0.001) compared to warfarin users. Rivaroxaban users with a primary diagnosis of AF also had significantly lower costs compared to warfarin users. LIMITATIONS: These included possible inaccuracies or omissions in diagnoses, completeness of baseline characteristics, and a study population that included patients newly initiated on and patients who continued anticoagulant therapy. CONCLUSION: Hospitalization costs for rivaroxaban were significantly lower than those for warfarin in NVAF patients treated with 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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
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 teacher head, 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".