Systematic Review and Meta-Analysis on the Effectiveness of Tranexamic Acid in Controlling Bleeding During Transurethral Benign Prostatic Hyperplasia Surgery
Bibliographic record
Abstract
Background: Benign prostatic hyperplasia (BPH) is a frequent condition in ageing men. Surgery is recommended for severe BPH symptoms and BPH-related complications. TURP is the reference standard for BPH surgery, but carries a risk of bleeding, which can lead to significant perioperative morbidity and mortality. To reduce bleeding during TURP, antifibrinolytic agents like tranexamic acid (TXA) have been studied. We aim to review the current evidence regarding TXA use during transurethral BPH surgery. Objective: This review aims to assess the efficacy and safety of tranexamic acid in reducing bleeding during transurethral benign prostatic hyperplasia surgery. Methods: Major clinical research databases such as PubMed, Cochrane Central Register of Controlled Trials, EBSCO, Scopus, Google Scholar, and Web of Science were searched from 2012 to 2022 for randomised controlled trials (RCTs) comparing the use of TXA to placebo in transurethral BPH surgery using the PICOS format. We included RCTs without language restrictions that assessed intraoperative blood loss, transfusion rates, haemoglobin levels, length of hospital stay, postoperative thromboembolic events, and 30-day perioperative mortality as outcomes. The quality assessment of the included studies was performed using the Cochrane risk-of-bias tool, RoB 2, for randomised studies. Results: A total of six RCTs, which included 456 patients, were eventually included in the meta-analysis. The results showed that tranexamic acid is beneficial in reducing blood loss and minimising changes in haemoglobin levels during transurethral resection of the prostate. However, it does not lessen the need for blood transfusions or shorten the hospital stay. Conclusions: Tranexamic acid is useful in decreasing blood loss and reducing changes in haemoglobin in patients undergoing transurethral resection of the prostate. Its utility during BPH surgery in low-resource settings where the latest haemostatic enucleation techniques, such as holmium and GreenLight laser enucleation, may not be readily available needs further evaluation.
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.011 | 0.032 |
| Meta-epidemiology (narrow) | 0.003 | 0.001 |
| Meta-epidemiology (broad) | 0.022 | 0.042 |
| Bibliometrics | 0.006 | 0.007 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.003 | 0.002 |
| Insufficient payload (model declined to judge) | 0.005 | 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 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".