MétaCan
Menu
Back to cohort
Record W2514447137 · doi:10.2196/resprot.5906

Patient Insights Into the Design of Technology to Support a Strengths-Based Approach to Health Care

2016· article· en· W2514447137 on OpenAlexvenueno aff
Jelena Mirković, Ólöf Birna Kristjánsdóttir, Una Stenberg, Tonje Krogseth, Kurt C. Stange, Cornelia M. Ruland

Bibliographic record

VenueJMIR Research Protocols · 2016
Typearticle
Languageen
FieldPsychology
TopicDigital Mental Health Interventions
Canadian institutionsnot available
FundersNorges ForskningsrådPatient-Centered Outcomes Research Institute
KeywordsStrengths and weaknessesHealth carePsychologyMedicineNursingKnowledge managementMedical educationComputer scienceSocial psychology

Abstract

fetched live from OpenAlex

BACKGROUND: An increasing number of research studies in the psychological and biobehavioral sciences support incorporating patients' personal strengths into illness management as a way to empower and activate the patients, thus improving their health and well-being. However, lack of attention to patients' personal strengths is still reported in patient-provider communication. Information technology (IT) has great potential to support strengths-based patient-provider communication and collaboration, but knowledge about the users' requirements and preferences is inadequate. OBJECTIVE: This study explored the aspirations and requirements of patients with chronic conditions concerning IT tools that could help increase their awareness of their own personal strengths and resources, and support discussion of these assets in consultations with health care providers. METHODS: We included patients with different chronic conditions (chronic pain, morbid obesity, and chronic obstructive pulmonary disease) and used various participatory research methods to gain insight into the participants' needs, values, and opinions, and the contexts in which they felt strengths-based IT tools could be used. RESULTS: Participants were positive toward using technology to support them in identifying and discussing their personal strengths in clinical consultation, but also underlined the importance of fitting it to their specific requirements and the right contexts of use. Participants recommended that technology be designed for use in preconsultation settings (eg, at home) and felt that it should support them in both identifying strengths and in finding out new ways how strengths can be used to attain personal health-related goals. Participants advocated use of technology to support advance preparation for consultations and empower them to take a more active role. IT tools were suggested to be potentially useful in specific contexts, including individual or group consultations with health care providers (physician, nurse, specialist, care team) in clinical consultations but also outside health care settings (eg, as a part of a self-management program). Participants' requirements for functionality and design include, among others: providing examples of strengths reported by other patients with chronic conditions, along with an option to extend the list with personal examples; giving an option to briefly summarize health-related history; using intuitive, easy-to-use but also engaging user interface design. Additionally, the findings are exemplified with a description of a low-fidelity paper prototype of a strengths-based tool, developed with participants in this study. CONCLUSIONS: Users requirements for IT support of a strengths-based approach to health care appear feasible. The presented findings reflect patients' values and lists potential contexts where they feel that technology could facilitate meaningful patient-provider communication that focuses not just on symptoms and problems, but also takes into account patients' strengths and resources. The findings can be used to inform further development of IT tools for use in clinical consultations.

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.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Protocol · Consensus signal: Protocol
Teacher disagreement score0.886
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.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.001

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.215
GPT teacher head0.585
Teacher spread0.370 · 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.

Study designNot applicable
Domainnot available
GenreProtocol

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

Citations39
Published2016
Admission routes1
Has abstractyes

Explore more

Same venueJMIR Research ProtocolsSame topicDigital Mental Health InterventionsFrench-language works237,207