Streptococcal PD peritonitis--a 10-year review of one centre's experience
Bibliographic record
Abstract
BACKGROUND: Detailed descriptive studies focusing on streptococcal peritonitis in patients on peritoneal dialysis are lacking. Most of the current information is available through isolated case reports. METHODS: We conducted a retrospective analysis of our peritoneal dialysis (PD) peritonitis database over the last decade to study the clinical profile and treatment outcomes of streptococcal peritonitis. RESULTS: A total of 68 patients (age: 57.12 +/- 16.6 years; male: 58.7%) with 104 episodes of streptococcal peritonitis (11.7% of total peritonitis) were identified. Of the patients, 18 (26.4%) were considered immunocompromised [failed renal transplant, systemic lupus erythematosus (SLE)] and 28 (41.1%) had diabetes. Streptococcus viridans accounted for the majority (94 episodes: 90.3%) of the streptococcal peritonitis. One patient developed S. viridans peritonitis after dental cleaning without antibiotic prophylaxis. Two (1.9%) infections with S. agalactiae and S. bovis each and seven (6.7%) with non-haemolytic Streptococcus were noted. Three patients had hospital-acquired infection. Twenty-six (25%) episodes needed 8 +/- 5.9 days of hospitalization. Concurrent infection with two organisms accounted for 17 (16.3%) episodes. Cefazolin (71) and vancomycin (29) were the primary antibiotics used for the treatment. Five episodes needed two antibiotics and one patient required antifungal treatment. A third of the patients (33.3%) had peritonitis that resolved slowly, although the majority of those (94%) did ultimately resolve with antibiotics alone. Five (4.8%) episodes required removal of the PD catheter. Three of them were associated with dual infections (one each with yeast, Stenotrophomonas and Enterococcus). Relapse occurred in eight (7.6%) episodes, and 11 (10.5%) recurred over the period from 4 weeks to 6 months after treatment. CONCLUSIONS: Streptococci remain a significant cause of PD peritonitis. Viridans strep is the primary subtype responsible. Isolated infections with these organisms are associated with slower response, good outcome and higher rates of recurrence.
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.001 | 0.005 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.005 | 0.008 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| 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; 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".