Bibliographic record
Abstract
This study helps to shed light on a long-standing dilemma in renal transplant surgery: whether to remove the peritoneal dialysis (PD) catheter at the time of transplant surgery or to leave it in place until established renal allograft function down the road.1 The potential benefits to removing the PD catheter at the time of surgery are that you eliminate the need for a second procedure, as well as avoid the potential complications fraught with having a PD catheter (e.g., infection, peritonitis) as highlighted in this study.1 On the other hand, in the face of delayed graft function (DGF) having PD catheter in place postoperatively leaves the potential to use that catheter for temporizing peritoneal dialysis while waiting for the allograft to recover function.2 However, as pointed out in several studies including this one, peritoneal dialysis in the post-transplant setting is also fraught with a high risk of potential complications, including fluid leakage from the incision if the peritoneum is violated during the transplant surgery.3–5 Therefore, the overall benefit to leaving a PD catheter in place seems to be minimal, especially in the live-donor population of transplants where the DGF rate is exceedingly low. In Winnipeg, we have had a very similar experience with our perioperative PD catheter situations; our new policy is to remove PD catheters on all transplant patients. As pointed out by the authors in this study,1 in the setting of DGF temporary dialysis can be facilitated by a central catheter which is very easy to place and remove and is associated with a low complication rate. In fact, most transplant recipients already have a central line in place at the time of surgery for central venous pressure monitoring and drug administration, so utilizing this line or switching it over to a dialysis line is very convenient. Despite the need for future prospective studies, the evidence points to an overall benefit of PD catheter removal at the time of kidney transplantation. This seems to outweigh the benefits of leaving in the PD catheter. Obviously, every patient and clinical scenario is different and there may be situations were this rule does not apply. Warren and colleagues make a strong case for PD catheter removal at the time of surgery.1
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.004 | 0.029 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.004 | 0.004 |
| Scholarly communication | 0.006 | 0.007 |
| Open science | 0.002 | 0.004 |
| Research integrity | 0.006 | 0.011 |
| Insufficient payload (model declined to judge) | 0.012 | 0.003 |
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".