MétaCan
Menu
Back to cohort
Record W2346705182 · doi:10.1159/000445068

Scores for Prediction of Fistula after Pancreatoduodenectomy: A Systematic Review

2016· review· en· W2346705182 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

VenueDigestive Surgery · 2016
Typereview
Languageen
FieldMedicine
TopicPancreatic and Hepatic Oncology Research
Canadian institutionsPancreas Centre (Canada)
Fundersnot available
KeywordsMedicinePancreatic fistulaPancreaticoduodenectomyScoring systemRetrospective cohort studyGeneral surgeryRadiologySurgeryPancreasInternal medicine

Abstract

fetched live from OpenAlex

BACKGROUND/AIM: Different scoring systems to predict the occurrence of postoperative pancreatic fistula (POPF) after pancreatoduodenectomy have been described, but the considered risk factors often suffer subjective scaling. The aim of this review is to evaluate and compare all published risk metrics predictive of POPF. METHODS: All existing scores were retrieved by literature web search. Inclusion criteria were ISGPF classification of POPF and the development of a risk score metric. RESULTS: From a total of 286 publications, 10 studies were selected. Most of them were retrospective and single center. The models considered a median number of 3 items (range from 2 to 5); in 5 of 10 trials only pre or intraoperative variables were included. The median number of patients/study was 186 (IQR 111.1-229.0). External validation was performed in 6 of 10 studies. The most recurrent items were abdominal fat (4/10), main pancreatic duct diameter (in 4/10), and pancreatic texture (3/10). CONCLUSION: POPF risk estimation should be easy, accurate, and objective. It should consider preoperative patient-related and gland-related features, and intraoperative events. None of the published systems completely adhere to these principles. Large heterogeneous multicentric validations should be endorsed, to account for the case-mix and evaluate the reproducibility of each scoring system.

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.002
metaresearch head score (Gemma)0.007
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Systematic review · Consensus signal: Systematic review
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.106
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.007
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0090.002
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.081
GPT teacher head0.383
Teacher spread0.302 · 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