Enhancing User Experience Through User Study: Design of an mHealth Tool for Self-Management and Care Engagement of Cardiovascular Disease Patients
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.
Bibliographic record
Abstract
BACKGROUND: As patient communication, engagement, personal health data tracking, and up-to-date information became more efficient through mobile health (mHealth), cardiovascular diseases (CVD) and other diseases that require behavioral improvements in daily life are now capable of being managed and prevented more effectively. However, to increase patient engagement through mHealth, it is important for the initial design to consider functionality and usability factors and accurately assess user demands during the developmental process so that the app can be used continuously. OBJECTIVE: The purpose of the study was to provide insightful information for developing mHealth service for patients with CVD based on user research to help enhance communication between patients and doctors. METHODS: To drive the mobile functions and services needed to manage diseases in CVD patients, user research was conducted on patients and doctors at a tertiary general university hospital located in the Seoul metropolitan area of South Korea. Interviews and a survey were performed on patients (35 participants) and a focus group interview was conducted with doctors (5 participants). A mock-up mobile app was developed based on the user survey results, and a usability test was then conducted (8 participants) to identify factors that should be considered to improve usability. RESULTS: The majority of patients showed a positive response in terms of their interest or intent to use an app for managing CVD. Functional features, such as communication with doctors, self-risk assessment, exercise, tailored education, blood pressure management, and health status recording had a score of 4.0 or higher on a 5-point Likert scale, showing that these functions were perceived to be useful to patients. The results of the mock-up usability test showed that inputting and visualizing blood pressure and other health conditions was required to be easier. The doctors requested a function that offered a comprehensive view of the patient's daily health status by linking the mHealth app data with the hospital's electronic health record system. CONCLUSIONS: Insights derived from a user study for developing an mHealth tool for CVD management, such as self-assessment and a communication channel between patients and doctors, may be helpful to improve patient engagement in care.
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 imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it