MétaCan
Menu
Back to cohort
Record W4404591097 · doi:10.1136/spcare-2024-hunc.84

P-65 The use of RUN-PC triage tool for community palliative care service

2024· article· en· W4404591097 on OpenAlexaboutno aff
Patrick J. McGrath

Bibliographic record

VenuePoster presentations · 2024
Typearticle
Languageen
FieldHealth Professions
TopicDisaster Response and Management
Canadian institutionsnot available
Fundersnot available
KeywordsTriageService (business)Palliative careMedical emergencyComputer scienceNursingMedicineBusiness

Abstract

fetched live from OpenAlex

<h3>Background</h3> There is no doubting that health care providers face increasing challenges to meet the needs of the population whilst dealing with gaps in funding. Teams need to be innovative in their approach which allows for a more proactive and targeted service (Antonacci, Barrie, Baxter, et al. J Aging Res. 2020:3921245). Our hospice applies its own triage tool which has overtime created ‘front door’ pressures on the team with over 50% of all referrals viewed as amber/72 hour response. The RUN-PC tool is an evidence based triage tool which allows services to allocate resources based on complexity (Russell, Philip, Wawryk, et al. Palliat Med. 2021;35(4):759–767). It ensures equitable, efficient and transparent access to clinical services whilst managing increasing caseloads and waiting lists (Russell, Sundararajan, Hennesy-Anderson, et al. Palliat Med. 2018;32(7):1246–1254). <h3>Aim</h3> To apply the RUN-PC Triage Tool to community referrals. <h3>Method</h3> The team performed a retrospective application of the RUN score on 37 amber patients. Following the results it was proposed to have an initial trial over Quarter 1 and Quarter 2. <h3>Results</h3> The tool provided a greater breakdown of complexity of service users and allowing for the most urgent patients to be prioritised in a timely manner. Out of 37 analysed: 7 Red 24 hours. 10 amber 72 hours. 18 Green 1 week. 2 Green 2 week. <h3>Conclusion</h3> The RUN-PC was shown to provide further breakdown of patient need and the timeframes for services to respond. The initial scope reduced the number of patients needing to be seen within 72 hours by 20 which potentially frees up services to prioritise those in greatest need. Further application of the tool in Q1 and Q2 will allow further data collection and analysis.

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 imitation

Not 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.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.554
Threshold uncertainty score0.541

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.343
GPT teacher head0.501
Teacher spread0.158 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designQualitative
Domainnot available
GenreEmpirical

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".

Quick stats

Citations0
Published2024
Admission routes1
Has abstractyes

Explore more

Same venuePoster presentationsSame topicDisaster Response and ManagementFrench-language works237,207