Development and Validation of Nine Deprescribing Algorithms for Patients on Hemodialysis to Decrease Polypharmacy
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
BACKGROUND: Polypharmacy is ubiquitous in patients on hemodialysis (HD), and increases risk of adverse events, medication interactions, nonadherence, and mortality. Appropriately applied deprescribing can potentially minimize polypharmacy risks. Existing guidelines are unsuitable for nephrology clinicians as they lack specific instructions on how to deprescribe and which safety parameters to monitor. OBJECTIVE: To develop and validate deprescribing algorithms for nine medication classes to decrease polypharmacy in patients on HD. DESIGN: Questionnaires and materials sent electronically. PARTICIPANTS: Nephrology practitioners across Canada (nephrologists, nurse practitioners, renal pharmacists). METHODS: A literature search was performed to develop the initial algorithms via Lynn's method for development of content-valid clinical tools. Content and face validity of the algorithms was evaluated over three interview rounds using Lynn's method for determining content validity. Canadian nephrology clinicians each evaluated three algorithms (15 clinicians per round, 45 clinicians in total) by rating each algorithm component on a four-point Likert scale for relevance; face validity was rated on a five-point scale. After each round, content validity index of each component was calculated and revisions made based on feedback. If content validity was not achieved after three rounds, additional rounds were completed until content validity was achieved. RESULTS: After three rounds of validation, six algorithms achieved content validity. After an additional round, the remaining three algorithms achieved content validity. The proportion of clinicians rating each face validity statement as "Agree" or "Strongly Agree" ranged from 84% to 95% (average of all five questions, across three rounds). LIMITATIONS: Algorithm development was guided by existing deprescribing protocols intended for the general population and the expert opinions of our study team, due to a lack of background literature on HD-specific deprescribing protocols. There is no universally accepted method for the validation of clinical decision-making tools. CONCLUSIONS: Nine medication-specific deprescribing algorithms for patients on HD were developed and validated by clinician review. Our algorithms are the first medication-specific, patient-centric deprescribing guidelines developed and validated for patients on HD.
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.
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.000 | 0.032 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| 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.000 | 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 it