MétaCan
Menu
Back to cohort
Record W3204460798 · doi:10.2196/31985

Toward the Value Sensitive Design of eHealth Technologies to Support Self-management of Cardiovascular Diseases: Content Analysis

2021· article· en· W3204460798 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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueJMIR Cardio · 2021
Typearticle
Languageen
FieldMedicine
TopicDiabetes Management and Education
Canadian institutionsnot available
FundersConsejo Nacional de Ciencia y Tecnología
KeywordseHealthComputer scienceSet (abstract data type)Knowledge managementValue (mathematics)Data scienceHealth care

Abstract

fetched live from OpenAlex

BACKGROUND: eHealth can revolutionize the way self-management support is offered to chronically ill individuals such as those with a cardiovascular disease (CVD). However, patients' fluctuating motivation to actually perform self-management is an important factor for which to account. Tailoring and personalizing eHealth to fit with the values of individuals promises to be an effective motivational strategy. Nevertheless, how specific eHealth technologies and design features could potentially contribute to values of individuals with a CVD has not been explicitly studied before. OBJECTIVE: This study sought to connect a set of empirically validated, health-related values of individuals with a CVD with existing eHealth technologies and their design features. The study searched for potential connections between design features and values with the goal to advance knowledge about how eHealth technologies can actually be more meaningful and motivating for end users. METHODS: Undertaking a technical investigation that fits with the value sensitive design framework, a content analysis of existing eHealth technologies was conducted. We matched 11 empirically validated values of CVD patients with 70 design features from 10 eHealth technologies that were previously identified in a systematic review. The analysis consisted mainly of a deductive coding stage performed independently by 3 members of the study team. In addition, researchers and developers of 6 of the 10 reviewed technologies provided input about potential feature-value connections. RESULTS: In total, 98 connections were made between eHealth design features and patient values. This meant that some design features could contribute to multiple values. Importantly, some values were more often addressed than others. CVD patients' values most often addressed were related to (1) having or maintaining a healthy lifestyle, (2) having an overview of personal health data, (3) having reliable information and advice, (4) having extrinsic motivators to accomplish goals or health-related activities, and (5) receiving personalized care. In contrast, values less often addressed concerned (6) perceiving low thresholds to access health care, (7) receiving social support, (8) preserving a sense of autonomy over life, and (9) not feeling fear, anxiety, or insecurity about health. Last, 2 largely unaddressed values were related to (10) having confidence and self-efficacy in the treatment or ability to achieve goals and (11) desiring to be seen as a person rather than a patient. CONCLUSIONS: Positively, existing eHealth technologies could be connected with CVD patients' values, largely through design features that relate to educational support, self-monitoring support, behavior change support, feedback, and motivational incentives. Other design features such as reminders, prompts or cues, peer-based or expert-based human support, and general system personalization were also connected with values but in narrower ways. In future studies, the inferred feature-value connections must be validated with empirical data from individuals with a CVD or similar chronic conditions.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.566
Threshold uncertainty score0.406

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
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.044
GPT teacher head0.291
Teacher spread0.247 · 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