Late Peritoneal Dialysis Exit-Site Leak: A Case Report
Bibliographic record
Abstract
Peritoneal dialysis (PD) pericatheter exit-site leaks most commonly occur early, within 30 days of catheter insertion. Late exit-site leaks are rare. The distinction between early and late exit-site leaks is important because the causes and subsequent management strategies may be different. Early leaks can often be first treated by delaying or holding PD therapy, allowing the prolongation of the healing time because fibrous tissue continues to form around the deep cuff. Late leaks are less likely to heal with cessation of PD alone and often require PD catheter replacement. In this case report, we provide an overview of the diagnosis and management of PD catheter exit-site leaks while highlighting a case of a late presenting exit-site leak resulting from a unique cause of PD catheter trauma. Peritoneal dialysis (PD) pericatheter exit-site leaks most commonly occur early, within 30 days of catheter insertion. Late exit-site leaks are rare. The distinction between early and late exit-site leaks is important because the causes and subsequent management strategies may be different. Early leaks can often be first treated by delaying or holding PD therapy, allowing the prolongation of the healing time because fibrous tissue continues to form around the deep cuff. Late leaks are less likely to heal with cessation of PD alone and often require PD catheter replacement. In this case report, we provide an overview of the diagnosis and management of PD catheter exit-site leaks while highlighting a case of a late presenting exit-site leak resulting from a unique cause of PD catheter trauma.
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 distilled prediction
Teacher imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
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; both teacher heads 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".