MétaCan
Menu
Back to cohort
Record W3042851801 · doi:10.1111/hex.13099

How to identify, incorporate and report patient preferences in clinical guidelines: A scoping review

2020· review· en· W3042851801 on OpenAlex

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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueHealth Expectations · 2020
Typereview
Languageen
FieldHealth Professions
TopicPatient-Provider Communication in Healthcare
Canadian institutionsUniversity of TorontoUniversity Health Network
Fundersnot available
KeywordsCINAHLMEDLINEGuidelineScopusMedicineData extractionPsychologyNursingPsychological intervention

Abstract

fetched live from OpenAlex

BACKGROUND: Clinical guidelines optimize care delivery and outcomes. Guidelines support patient engagement and adherence if they reflect patient preferences for treatment options, risks and benefits. Many guidelines do not address patient preferences. Developers require insight on how to develop such guidelines. OBJECTIVE: To conduct a scoping review on how to identify, incorporate and report patient preferences in guidelines. SEARCH: We searched MEDLINE, EMBASE, Scopus, CINAHL, OpenGrey and GreyLit from 2010 to November 2019. ELIGIBILITY: We included English language studies describing patient preferences and guidelines. DATA EXTRACTION AND SYNTHESIS: We reported approaches for and determinants and impacts of identifying patient preferences using summary statistics and text, and interpreted findings using a conceptual framework of patient engagement in guideline development. RESULTS: Sixteen studies were included: 2 consulted patients and providers about patient engagement approaches, and 14 identified patient preferences (42.9%) or methods for doing so (71.4%). Studies employed single (57.1%) or multiple (42.9%) methods for identifying preferences. Eight (57.1%) incorporated preferences in one aspect of guideline development, while 6 (42.9%) incorporated preferences in multiple ways, most commonly to identify questions, benefits or harms, and generate recommendations. Studies did not address patient engagement in many guideline development steps. Included studies were too few to establish the best approaches for identifying or incorporating preferences. Fewer than half of the studies (7, 43.8%) explored barriers. None examined reporting preferences in guidelines. CONCLUSIONS: Research is needed to establish the single or multiple approaches that result in incorporating and reporting preferences in all guideline development steps.

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 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.001
metaresearch head score (Gemma)0.016
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Meta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Systematic review · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.649
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.016
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0040.000
Bibliometrics0.0010.002
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0010.001
Research integrity0.0000.002
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.732
GPT teacher head0.645
Teacher spread0.087 · 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