Evaluation of a score for identifying hospital stays that trigger a pharmacist intervention: integration into a clinical decision support system
Bibliographic record
Abstract
Objectives: The objective of the study was to determine, after medication review, the patient risk score threshold that would distinguish between stays with prescriptions triggering pharmacist intervention (PI) and stays with prescriptions not triggering PI. Materials and Methods: The study was retrospective and observational, conducted in the clinical pharmacy team. The patient risk score was adapted from a Canadian score and was integrated in the clinical decision support system (CDSS). For each hospital stay, the score was calculated at the beginning of hospitalization and we retrospectively showed if a medication review and a PI were conducted. Then, the optimal patient risk score threshold was determined to help pharmacist in optimizing medication review. Results: During the study, 973 (56.7%) medication reviews were performed and 248 (25.5%) led to a PI. After analyzing sensitivity, specificity, and positive predictive value of different thresholds, the threshold of 4 was deemed discriminating to identify hospital stays likely to lead to a PI following a medication review. At this threshold, 600 hospital stays would have been detected (33.3% of the latter led to a PI), and 5.0% of stays with a medication review would not have been detected even though they were hospital stays that had triggered a PI. Discussion and Conclusion: Integration of a patient risk score in a CDSS can help clinical pharmacist to target hospital stays likely to trigger a PI. However, an optimal threshold is difficult to determine. Constructing and using a score in practice should be organized with the local clinical pharmacy team, in order to understand the tool's limitations and maximize its use in detecting at-risk drug prescriptions.
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.009 | 0.030 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.002 | 0.001 |
| Bibliometrics | 0.004 | 0.003 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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".