Bibliographic record
Abstract
Introduction: there is a paucity of literature regarding the incidence of long-term urethral complications after prostate cancer treatment.our objective was to assess the long-term incidence of urethral complications after different treatment modalities for prostate cancer.Methods: All men with a diagnosis of prostate cancer from 2002-2021 from the Alberta Cancer registry were included.the discharge Abstract data (dAd) and the national Ambulatory Care reporting system (nACrs) were searched for different treatment modalities and urologic diagnosis/procedures. patients were allocated into six different groups: radical prostatectomy (rp), radiotherapy (rt), cryotherapy (Cryo), medical treatment/observation (mt/o), rp+rt, or Cryo+rt.Urethral complication was defined as development of stenosis, fistula, or a urethral/ bladder neck procedure >30 days after treatment (excluding tUrp, diagnostic procedures, and incontinence).We compared the incidence of urethral complications among different groups using Cox regression Results: A total of 47 387 patients with prostate cancer diagnosis were identified, with a median age of 66 years (IQr 60-74); 3140 patients developed a urethral complication at a median followup of 76 months.table 1 shows the cumulative incidence of urethral complications.on Kaplan-meier analysis (Figure 1), urethral complication rate was different among groups (p<0,001).on multivariable Coxregression analysis including age (p<0.001) and stage p=0.002) at diagnosis, all treatment modalities (except for cryotherapy) were associated with development of urethral complications compared to mt/o.In particular, combined modalities such as rp+rt (Hr 2.9, p<0,001) and rt+Cryo (Hr 3.6, p<0.001) showed the highest risk.Complications after rp reached a plateau at 10 years, whereas other modalities continued to accumulate complications over the long-term.Conclusions: patients undergoing prostate cancer treatment are at risk for developing urethral complications in the long-term regardless of treatment type.specifically, combined modalities pose a heightened risk.
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.002 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.003 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.609 | 0.296 |
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; the direct Gemma label and the distilled Codex classifier agree on what is shown here.
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".