MétaCan
Menu
Back to cohort
Record W3094844007 · doi:10.1136/bmjopen-2020-038339

Are you really doing ‘codesign’? Critical reflections when working with vulnerable populations

2020· article· en· W3094844007 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueBMJ Open · 2020
Typearticle
Languageen
FieldHealth Professions
TopicMental Health and Patient Involvement
Canadian institutionsCanadian Centre on Disability StudiesOntario College of Art and DesignMcMaster University
FundersMcMaster University
KeywordsCoproductionCLARITYReflexivityMedicineProcess (computing)Health careCritical reflectionService (business)Public relationsEngineering ethicsProcess managementSociologyComputer sciencePolitical science

Abstract

fetched live from OpenAlex

'Codesign' and associated terms such as 'coproduction' or 'patient engagement', are increasingly common in the health research literature, due to an increased emphasis on the importance of ensuring that research related to service/systems development is meaningful to end-users. However, there continues to be a lack of clarity regarding the key principles and practices of codesign, and wide variation in the extent to which service users are meaningfully engaged in the process. These issues are particularly acute when end-users include populations who have significant health and healthcare disparities that are linked to a range of intersecting vulnerabilities (eg, poverty, language barriers, age, disability, minority status, stigmatised conditions). The purpose of this paper is to prompt critical reflection on the nature of codesign research with vulnerable populations, including key issues to consider in the initial planning phases, the implementation process, and final outputs. Risks and tensions will be identified in each phase of the process, followed by a tool to foster reflexivity in codesign processes to address these issues.

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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies, Insufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.756
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0030.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0010.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.757
GPT teacher head0.581
Teacher spread0.176 · 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