MétaCan
Menu
Back to cohort
Record W4382401163 · doi:10.2196/45694

Sustainable Development for Mobile Health Apps Using the Human-Centered Design Process

2023· article· en· W4382401163 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 Formative Research · 2023
Typearticle
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsnot available
Fundersnot available
KeywordsmHealthSociotechnical systemHealth careKnowledge managementBusinessInternet privacyProcess managementComputer scienceMedicineNursingPsychological interventionPolitical science

Abstract

fetched live from OpenAlex

Well-documented scientific evidence indicates that mobile health (mHealth) apps can improve the quality of life, relieve symptoms, and restore health for patients. In addition to improving patients' health outcomes, mHealth apps reduce health care use and the cost burdens associated with disease management. Currently, patients and health care providers have a wide variety of choices among commercially available mHealth apps. However, due to the high resource costs and low user adoption of mHealth apps, the cost-benefit relationship remains controversial. When compared to traditional expert-driven approaches, applying human-centered design (HCD) may result in more useable, acceptable, and effective mHealth apps. In this paper, we summarize current HCD practices in mHealth development studies and make recommendations to improve the sustainability of mHealth. These recommendations include consideration of factors regarding culture norms, iterative evaluations on HCD practice, use of novelty in mHealth app, and consideration of privacy and reliability across the entire HCD process. Additionally, we suggest a sociotechnical lens toward HCD practices to promote the sustainability of mHealth apps. Future research should consider standardizing the HCD practice to help mHealth researchers and developers avoid barriers associated with inadequate HCD practices.

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.013
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.213
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0130.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.002
Science and technology studies0.0130.000
Scholarly communication0.0000.000
Open science0.0010.000
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.359
GPT teacher head0.609
Teacher spread0.250 · 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