Nationwide Standardized Peritonitis Reporting: Updated Results From the Optimizing the Prevention of Peritoneal Dialysis Associated Peritonitis in the United States (OPPUS) Study
Bibliographic record
Abstract
Background: Peritoneal Dialysis (PD) associated peritonitis is a common complication of PD and is the leading cause of transfer to hemodialysis in the US. No formal mechanism or surveillance system exists for nationwide peritonitis reporting. Our primary aim was to develop a uniform widescale peritonitis reporting mechanism and evaluate its implementation in the Optimizing Prevention of PD-associated Peritonitis in US (OPPUS) study. Methods: Following literature review, stakeholder consultation, and ISPD guidelines review, a web-based peritonitis tracker tool (OPPUS-Link) was developed. Pilot sites for one-year data collection were selected based on geography and reported peritonitis rates, including 3 medium-large dialysis organizations. We provided formal training, central data review, and adjudication of all peritonitis episodes and outcomes. Data collection began in October 2020 and is ongoing. Results: Initial data for 53 participating facilities with a median follow-up time of 31 patient-years includes 350 peritonitis episodes (rate of 0.24 episodes/year). Permanent transfer to HD, PD catheter removal, and hospitalization occurred in 14%, 15%, and 41% of episodes respectively, with 6% of episodes resulting in death. Only 1.5% of peritonitis episodes occurred following PD catheter insertion but prior to PD at home. Ongoing challenges include high prevalence of culture-negative peritonitis (22% of episodes) and high percentage of peritonitis acquired in hospital (15%). Conclusions: Standardized, uniform peritonitis reporting is feasible, a first step in national PD-peritonitis surveillance, allowing for benchmarking, outbreak identification, and quality improvement initiative implementation. Further data validation is necessary and integrating routine peritonitis reporting in electronic health records with an overall goal of peritonitis reduction and improved outcomes for PD patients. Funding: Other NIH Support - AHRQ
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.045 | 0.066 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.006 | 0.010 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.002 | 0.003 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.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.
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".