Selecting, implementing and evaluating patient-reported outcome measures for routine clinical use in cancer: the Cancer Care Ontario approach
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: The use of Patient-Reported Outcome Measures (PROMs) in routine clinical care can help ensure symptoms are identified, acknowledged and addressed. In 2007, the provincial cancer agency, Cancer Care Ontario, began to implement routine symptom screening with the Edmonton Symptom Assessment System (ESAS) for ambulatory cancer patients. Having had a decade of experience with ESAS, the program developed a strategic interest in implementing new and/or additional measures. This article describes the development of a streamlined PROM selection and implementation evaluation process with core considerations. METHODS: Development of the PROM selection and implementation evaluation process involved analysis of quantitative and qualitative data as well as consensus building through a multi-stakeholder workshop. Core PROM selection considerations were developed through a literature scan, review and refinement by a panel of methodological experts and patient advisors, and testing via a test case. Core PROM implementation evaluation considerations were developed through analysis of PROM evaluation frameworks, and review and refinement by a committee of provincial implementation leads. RESULTS: Core PROM selection considerations were identified under three overarching themes: symptom coverage, usability and psychometric properties. The symptom coverage category assesses each PROM to determine how well the PROM items address the most prevalent and burdensome symptoms in the target patient population. The usability category aims to assess each measure on characteristics key to successful implementation in the clinical setting. The psychometric properties category assesses each PROM to ensure the data collected is credible, meaningful and interpretable. A scoring system was developed to rate PROM performance by assigning a grade of "weak", "average" or "good" for each category. The process results in a summary matrix which illustrates the overall assessment of each PROM. Implementation evaluation considerations were identified under three overarching concepts: acceptability, outcomes, and sustainability. A consensus building exercise resulted in the further identification of patient, provider, and clinic specific indicators for each consideration. CONCLUSION: To address the need for a systematic, evidence-based approach to selection, implementation and evaluation of PROMs in the clinical setting, Cancer Care Ontario defined a process with embedded core considerations to facilitate decision-making and encourage standardization.
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.002 | 0.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| 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.001 |
| 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