Persistent need for ongoing medical or surgical therapy despite UroLift
Bibliographic record
Abstract
INTRODUCTION: The prostatic urethral lift (PUL) is a popular surgical option for benign prostatic hyperplasia (BPH) with lower urinary tract symptoms (LUTS). Prior 5-year data from the multicenter L.I.F.T. trial suggested durability and a surgical retreatment rate of 13.6% at five years. We assessed the proportion of patients who had ongoing medical or surgical BPH management following PUL. METHODS: With institutional review board approval, cases of PUL performed from 2015-2020 at our academic institution were retrospectively reviewed for management of BPH following PUL. RESULTS: A total of 209 men were identified, with followup available for 198 (95%). Mean age was 68.9 years and mean followup was 18.5 months. Mean prostate size was 43 g. Patients were discharged from recovery in 97% of cases, with 29% discharged with indwelling or intermittent catheterization. The rate of 30-day complications was 18%, with 89% graded Clavien I-II. Postoperatively, mean improvements in International Prostate Symptom Score (IPSS) and quality of life subscore (QoL) were 5.3 and 1.1 points, respectively. Unplanned emergency room or clinic visits within 30 days of the procedure occurred in 14% and 17% of men, respectively, with 4% requiring hospital readmission. In followup, α-blockers and/or 5α-reductase inhibitors were continued or initiated postoperatively for 44% of men; 20% of men required repeat surgical intervention at a mean of 19.2 months (1.4-56.4), consisting of repeat PUL (30%), transurethral resection of prostate (28%), or thulium laser enucleation (18%). Overall, 53% of men needed medication and/or repeat surgery for BPH following PUL, and this was independent of age, race, prostate volume, intravesical prostate protrusion, baseline IPSS and QOL, stricture, number of implants used, or a history of urinary retention (p>0.05). CONCLUSIONS: Most men undergoing PUL require ongoing medical and/or surgical management for BPH. Patients should be counseled as to the likelihood of failure as a unimodal therapy long-term.
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.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| 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".