MétaCan
Menu
← Back to cohort
Record W4247110261 · doi:10.5489/cuaj.14

Should peritoneal dialysis catheters be removed at the time of kidney transplantation?

2012· article· en· W4247110261 on OpenAlexaffvenue
Jeff Warren, Emily Jones, Alp Şener, Martin Drage, Ali Taqi, Siân Griffin, Christopher J.E. Watson, Patrick Luke

Bibliographic record

VenueCanadian Urological Association Journal · 2012
Typearticle
Languageen
FieldMedicine
TopicDialysis and Renal Disease Management
Canadian institutionsLondon Health Sciences CentreWestern University
Fundersnot available
KeywordsMedicinePeritoneal dialysisPeritonitisCatheterSurgeryLaparotomyDialysisTransplantationComplicationKidney transplantationDialysis catheterUrology

Abstract

fetched live from OpenAlex

Background: Delayed graft function (DGF) following transplantationnecessitates support in the form of hemodialyis (HD) orperitoneal dialysis (PD). However, post-transplant PD-related complicationand failure rates are unknown.Methods: We studies patients who were on PD at the time of kidneytransplantation over a 4-year period at two separate institutions.Results: Of the 137 PD patients, 19 had their catheters removedat the time of transplant. Of the remaining 118 patients, 89% hadimmediate graft function. PD-related complications in this groupincluded peritonitis (n=5), catheter-related infections (n=2) andemergency laparotomy (n=1). Of the 15 patients requiring posttransplantPD, 33% developed peritonitis and 20% had fluid-leaksnecessitating HD. Overall, leaving a PD catheter in situ post- transplantationis associated with 7% rate of peritonitis versus 0% ifremoved (p < 0.05).Conclusions: PD catheter removal should be considered at thetime of renal transplantation, as postoperative PD-related failure/complication rates are high.

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 imitation

Not 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.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.014
Version: metacan-v3-hybrid-931329e0061cValidation 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.002
Threshold uncertainty score0.008

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.014
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0010.001
Scholarly communication0.0010.001
Open science0.0010.000
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.0020.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.016
GPT teacher head0.238
Teacher spread0.222 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designObservational
Domainnot available
GenreEmpirical

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".

Quick stats

Citations2
Published2012
Admission routes2
Has abstractyes

Explore more

Same venueCanadian Urological Association Journal→Same topicDialysis and Renal Disease Management→French-language works237,207→