MétaCan
Menu
Back to cohort
Record W3169589642 · doi:10.2196/14466

Using Goal-Directed Design to Create a Mobile Health App to Improve Patient Compliance With Hypertension Self-Management: Development and Deployment

2019· article· en· W3169589642 on OpenAlexvenueno aff
Huilong Duan, Zheyu Wang, Yumeng Ji, Li Ma, Fang Liu, Mingwei Chi, Ning Deng, Jiye An

Bibliographic record

VenueJMIR mhealth and uhealth · 2019
Typearticle
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsnot available
Fundersnot available
KeywordsSelf-managementFocus groupMedicinemHealthGoal settingSoftware deploymentProcess managementComputer sciencePsychologyNursingPsychological interventionEngineeringBusiness

Abstract

fetched live from OpenAlex

BACKGROUND: Hypertension is a lifestyle-induced chronic disease that threatens the lives of patients. Control of hypertension requires patients to follow self-management regimes; unfortunately, however, patient compliance with hypertension self-management is low, especially in developing countries. Improvement of patient compliance is premised on meeting patient needs. Mobile health apps are becoming increasingly popular for self-management of chronic diseases. However, few mobile apps have been designed to meet patient needs for hypertension self-management. OBJECTIVE: The goal of this study was to develop a mobile health app to improve patient compliance with hypertension self-management and evaluate the effectiveness of the app in terms of patient compliance. METHODS: The goal-directed design method was applied to guide study design. We divided the study into 4 stages. Stages 1 to 3 comprised the development process. To improve the applicability of the goal-directed design method to chronic disease management, we extracted elements of user models concerned with patient compliance and defined a concrete process for user modeling. In stage 1, personas of hypertensive patients were built using qualitative and quantitative methods. Clustering methods based on questionnaire responses were used to group patients. Qualitative interviews were conducted to identify the needs of different groups. In stage 2, several functional modules were designed to meet the needs of different groups based on the results from stage 1. In stage 3, prototypes of functional modules were designed and implemented as a real app. Stage 4 was the deployment process, in which we conducted a pilot study to investigate patient compliance after using the app. Patient compliance was calculated through the frequency with which they took blood pressure measurements. In addition, qualitative interviews were conducted to learn the underlying reasons for the compliance results. RESULTS: In stage 1, patients were divided into 3 groups based on 82 valid questionnaire responses. Eighteen patients from the different groups (7, 5, and 6 patients) were interviewed, and the needs of the groups were summarized as follows: improve self-management ability, enhance self-management motivation, and receive self-management support. In stages 2 and 3, 6 functional modules were designed and implemented based on specified needs, and the usability of the app was improved through usability tests. In stage 4, 143 patients were recruited to use different versions of the app for 2 months. Results show that patient compliance improved as functional modules were added (P<.001) and was maintained at a high level (rate of 0.73). Interview results from 32 patients show that the design of the app met different needs; thus, patients were more compliant with it. CONCLUSIONS: This study developed a mobile health app for hypertension self-management using the goal-directed design method. The app proved to be effective for improving patient compliance with hypertension self-management.

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.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Science and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.884
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.001
Science and technology studies0.0020.000
Scholarly communication0.0000.000
Open science0.0000.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.088
GPT teacher head0.407
Teacher spread0.319 · 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 designOther design
Domainnot available
GenreEmpirical

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

Citations91
Published2019
Admission routes1
Has abstractyes

Explore more

Same venueJMIR mhealth and uhealthSame topicMobile Health and mHealth ApplicationsFrench-language works237,207