Meta‐analysis of retroperitoneal vs transperitoneal laparoscopic and robot‐assisted pyeloplasty for the management of pelvi‐ureteric junction obstruction
Bibliographic record
Abstract
OBJECTIVE: To determine differences in perioperative outcomes between retroperitoneal and transperitoneal approaches for laparoscopic pyeloplasty (LP) to manage pelvi-ureteric junction obstruction (PUJO) through a meta-analysis of comparative studies. METHODS: A systematic search was performed in January 2020. Comparative studies were evaluated according to Cochrane Collaboration recommendations. Assessed outcomes included success and complication rates, conversion to open surgery, operative time (OT), length of hospital stay (LOS), estimated blood loss (EBL), analgesic requirements, regular diet resumption, and drain duration. Relative risk (RR) and standardised mean difference (SMD) with 95% confidence intervals (CIs) were extrapolated. Subgroup analyses were performed according to study design and techniques. International Prospective Register of Systematic Reviews (PROSPERO) number: CRD42020163303. RESULTS: A total of 18 studies describing 2007 cases were included. Overall pooled effect estimates did not show statistically significant differences between the approaches with regards to success rate (RR 0.99; 95% CI 0.97, 1.01), complications (RR 1.09; 95% CI 0.82, 1.45), OT (SMD 0.61; 95% CI -0.04, 1.26), LOS (SMD -0.30; 95% CI -0.63, 0.04), EBL (SMD -0.53; 95% CI -1.26, 0.21), or analgesic requirements (SMD -0.51; 95% CI -1.23, 0.21). Compared to the transperitoneal approach, retroperitoneal LP had a higher conversion rate (RR 2.40; 95% CI 1.23, 4.66); however, patients resumed diets earlier (SMD -2.49; 95% CI -4.17, -0.82) and had shorter drain duration (SMD -0.31; 95% CI -0.57, -0.05). CONCLUSION: The evidence suggests that there are no significant differences in success rate, OT and complications between transperitoneal and retroperitoneal LP. Conversion rates are higher with the retroperitoneal approach; however, return to diet occurs faster and drain duration is shorter when compared to the transperitoneal approach.
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.022 |
| Meta-epidemiology (narrow) | 0.003 | 0.001 |
| Meta-epidemiology (broad) | 0.020 | 0.048 |
| Bibliometrics | 0.005 | 0.005 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.004 | 0.002 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.003 | 0.002 |
| Insufficient payload (model declined to judge) | 0.004 | 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".