MétaCan
Menu
Back to cohort
Record W2577836407 · doi:10.1186/s12911-016-0399-8

Involving members of vulnerable populations in the development of patient decision aids: a mixed methods sequential explanatory study

2017· article· en· W2577836407 on OpenAlex
Michèle Dugas, Marie-Ève Trottier, Selma Chipenda Dansokho, Gratianne Vaisson, Thierry Provencher, Heather Colquhoun, Maman Joyce Dogba, Sophie Dupéré, Angela Fagerlin, Anik Giguère, Lynne Haslett, Aubri Hoffman, Noah Ivers, France Légaré, Jean Légaré, Carrie A. Levin, Matthew Menear, Jean-Sébastien Renaud, Dawn Stacey, Robert J. Volk, Holly O. Witteman

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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueBMC Medical Informatics and Decision Making · 2017
Typearticle
Languageen
FieldHealth Professions
TopicPatient-Provider Communication in Healthcare
Canadian institutionsUniversity of OttawaWomen's College HospitalUniversity of TorontoUniversité LavalRegent Park Community Health CentreHôpital du Saint-SacrementOttawa HospitalCentre hospitalier universitaire de Québec
FundersDepartment of Family and Community Medicine, University of TorontoUniversity of TorontoCanadian Institutes of Health ResearchUniversity of OttawaNational Institute on AgingPatient-Centered Outcomes Research Institute
KeywordsHealth informaticsDecision aidsMedicineFamily medicineComputer sciencePublic healthNursingAlternative medicinePathology

Abstract

fetched live from OpenAlex

BACKGROUND: Patient decision aids aim to present evidence relevant to a health decision in understandable ways to support patients through the process of making evidence-informed, values-congruent health decisions. It is recommended that, when developing these tools, teams involve people who may ultimately use them. However, there is little empirical evidence about how best to undertake this involvement, particularly for specific populations of users such as vulnerable populations. METHODS: To describe and compare the development practices of research teams that did and did not specifically involve members of vulnerable populations in the development of patient decision aids, we conducted a secondary analysis of data from a systematic review about the development processes of patient decision aids. Then, to further explain our quantitative results, we conducted semi-structured telephone interviews with 10 teams: 6 that had specifically involved members of vulnerable populations and 4 that had not. Two independent analysts thematically coded transcribed interviews. RESULTS: Out of a total of 187 decision aid development projects, 30 (16%) specifically involved members of vulnerable populations. The specific involvement of members of vulnerable populations in the development process was associated with conducting informal needs assessment activities (73% vs. 40%, OR 2.96, 95% CI 1.18-7.99, P = .02) and recruiting participants through community-based organizations (40% vs. 11%, OR 3.48, 95% CI 1.23-9.83, P = .02). In interviews, all developers highlighted the importance, value and challenges of involving potential users. Interviews with developers whose projects had involved members of vulnerable populations suggested that informal needs assessment activities served to center the decision aid around users' needs, to better avoid stigma, and to ensure that the topic truly matters to the community. Partnering with community-based organizations may facilitate relationships of trust and may also provide a non-threatening and accessible location for research activities. CONCLUSIONS: There are a small number of key differences in the development processes for patient decision aids in which members of vulnerable populations were or were not specifically involved. Some of these practices may require additional time or resources. To address health inequities, researchers, communities and funders may need to increase awareness of these approaches and plan accordingly.

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.007
metaresearch head score (Gemma)0.010
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Science and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.634
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0070.010
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0020.000
Scholarly communication0.0000.000
Open science0.0010.001
Research integrity0.0000.001
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.395
GPT teacher head0.542
Teacher spread0.147 · 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