MétaCan
Menu
Back to cohort

Thrombosis and anticoagulation in the setting of renal or liver disease

2016· review· en· W2559241462 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueHematology · 2016
Typereview
Languageen
FieldMedicine
TopicVenous Thromboembolism Diagnosis and Management
Canadian institutionsMcMaster UniversitySt. Joseph’s Healthcare Hamilton
Fundersnot available
KeywordsMedicineLiver diseaseAnticoagulantDiseaseThrombosisRenal functionKidney diseaseVenous thrombosisInternal medicineIntensive care medicineGastroenterology

Abstract

fetched live from OpenAlex

Thrombosis and bleeding are among the most common causes of morbidity and mortality in patients with renal disease or liver disease. The pathophysiology underlying the increased risk for venous thromboembolism and bleeding in these 2 populations is distinct, as are considerations for anticoagulation. Anticoagulation in patients with kidney or liver disease increases the risk of bleeding; this risk is correlated with the degree of impairment of anticoagulant elimination by the kidneys and/or liver. Despite being in the same pharmacologic category, anticoagulant agents may have varied degrees of renal and liver metabolism. Therefore, specific anticoagulants may require dose reductions or be contraindicated in renal impairment and liver disease, whereas other drugs in the same class may not be subject to such restrictions. To minimize the risk of bleeding, while ensuring an adequate therapeutic effect, both appropriate anticoagulant drug choices and dose reductions are necessary. Renal and hepatic function may fluctuate, further complicating anticoagulation in these high-risk patient groups.

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.

Full frame distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.887
Threshold uncertainty score0.315

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.089
GPT teacher head0.384
Teacher spread0.295 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it