The impact of perioperative red blood cell transfusions in patients undergoing liver resection: a systematic review protocol
Bibliographic record
Abstract
BACKGROUND: Liver resection is commonly performed for malignant and benign disease and is associated with frequent use of intraoperative and postoperative blood transfusions. Blood transfusions are potentially life-saving, but they have many adverse effects; some well understood, and others less so. Some of the poorly understood side effects include increased risk of postoperative complications and possibly worse oncologic outcomes. The objective of this systematic review is to provide estimates of transfusion prevalence and the effects of perioperative blood transfusion on postoperative mortality and morbidity and long-term cancer outcomes in patients undergoing liver resection. METHODS/DESIGN: The Cochrane, Medline, and EMBASE databases will be searched for any randomized controlled trial or observational cohort study comparing liver resection patients that received intraoperative or postoperative allogeneic red blood cell transfusions to those who did not. Outcomes include postoperative mortality, postoperative morbidity (infectious, liver failure, renal failure, cardiovascular/cerebrovascular events, and thromboembolic events), and long-term disease-free and overall survival. Only studies with adult, human patients (>18 years old) undergoing liver resection, in which the primary intervention of interest is blood transfusion will be included. Data will be extracted by two reviewers in duplicate and synthesized into a narrative review. Risk of bias will be assessed. When clinically and methodologically appropriate, meta-analysis will be performed. DISCUSSION: Our review will synthesize the literature pertaining to the potential beneficial and detrimental effects of red blood cell transfusion in patients undergoing liver resection. It will be an important step in the development of guidelines for the appropriate use of blood transfusions in patients undergoing liver resection. SYSTEMATIC REVIEW REGISTRATION: PROSPERO CRD42015026132.
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.039 | 0.056 |
| Meta-epidemiology (narrow) | 0.004 | 0.004 |
| Meta-epidemiology (broad) | 0.017 | 0.013 |
| Bibliometrics | 0.012 | 0.011 |
| Science and technology studies | 0.003 | 0.004 |
| Scholarly communication | 0.006 | 0.006 |
| Open science | 0.005 | 0.004 |
| Research integrity | 0.006 | 0.004 |
| Insufficient payload (model declined to judge) | 0.033 | 0.003 |
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".