MétaCan
Menu
Back to cohort

A propensity score case‐control comparison of aprotinin and tranexamic acid in high‐transfusion‐risk cardiac surgery

2006· article· en· W1978691495 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

VenueTransfusion · 2006
Typearticle
Languageen
FieldMedicine
TopicBlood transfusion and management
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsTranexamic acidAprotininMedicineAntifibrinolyticAnesthesiaCardiac surgeryPerioperativePropensity score matchingCardiopulmonary bypassBlood transfusionSurgeryBlood productHemostasisBlood loss

Abstract

fetched live from OpenAlex

BACKGROUND: Cardiac surgery with cardiopulmonary bypass may result in excessive fibrinolysis and platelet (PLT) dysfunction, resulting in impaired hemostasis and excessive blood loss. Prophylactic use of the antifibrinolytic drugs aprotinin and tranexamic acid is thought to prevent these hemostatic defects. Their relative clinical utility and safety in high-transfusion-risk cardiac surgery, however, is not known. STUDY DESIGN AND METHODS: Using propensity scores, 449 patients who received aprotinin for high-transfusion-risk cardiac surgery were matched to 449 patients who received tranexamic acid from a pool of 10,870 consecutive patients who underwent cardiac surgery at a single center, 586 of whom received aprotinin and the remainder of whom received tranexamic acid. RESULTS: The two matched groups were well balanced in terms of measured perioperative variables. Blood product transfusion rates were similar in the aprotinin and tranexamic acid groups: red blood cells, 79 percent versus 76 percent (p = 0.3); PLTs, 56 percent versus 50 percent (p = 0.06); and plasma, 66 percent versus 61 percent (p = 0.1). Adverse events rates were comparable in the two groups, except for renal dysfunction (defined as a greater than 50% increase in creatinine concentration during the first postoperative week to >100 micromol/L in women and >110 micromol/L in men or a new requirement for dialysis support), which occurred in 24 percent (107/449) of aprotinin patients and 17 percent (75/449) of tranexamic acid patients (p = 0.01). CONCLUSIONS: Aprotinin and tranexamic acid have similar hemostatic effectiveness in high-transfusion-risk cardiac surgery. Within the confines of propensity score matching, our results suggest that aprotinin may be associated with renal dysfunction.

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.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.106
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.025
GPT teacher head0.242
Teacher spread0.217 · 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