MétaCan
Menu
Back to cohort
Record W1990743482 · doi:10.1186/1471-2490-8-3

CT scanning for diagnosing blunt ureteral and ureteropelvic junction injuries

2008· article· en· W1990743482 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueBMC Urology · 2008
Typearticle
Languageen
FieldMedicine
TopicUreteral procedures and complications
Canadian institutionsHealth Sciences CentreSunnybrook Health Science Centre
Fundersnot available
KeywordsMedicineBluntAdipose capsule of kidneyBlunt traumaLaparotomyRadiologyUreteropelvic junctionSurgeryEmergency departmentUrinomaUreterHydronephrosisUrinary systemAnatomyKidneyInternal medicine

Abstract

fetched live from OpenAlex

BACKGROUND: Blunt ureteral and ureteropelvic (UPJ) injuries are extremely rare and very difficult to diagnose. Many of these injuries are missed by the initial trauma evaluation. METHODS: Trauma registry data was used to identify all blunt trauma patients with ureteral or UPJ injuries, from 1 April 2001 to 30 November 2006. Demographics, injury information and outcomes were determined. Chart review was then performed to record initial clinical and all CT findings. RESULTS: Eight patients had ureteral or UPJ injuries. Subtle findings such as perinephric stranding and hematomas, and low density retroperitoneal fluid were evident on all initial scans, and prompted delayed excretory scans in 7/8 cases. As a result, ureteral and UPJ injuries were diagnosed immediately for these seven patients. These findings were initially missed in the eighth patient because significant associated visceral findings mandated emergency laparotomy. All ureteral and UPJ injuries have completely healed except for the case with the delay in diagnosis. CONCLUSION: Most blunt ureteral and UPJ injuries can be identified if delayed excretory CT scans are performed based on initial CT findings of perinephric stranding and hematomas, or the finding of low density retroperitoneal fluid.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.027
Threshold uncertainty score0.358

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.042
GPT teacher head0.288
Teacher spread0.246 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it