User Preferences and Design Recommendations for an mHealth App to Promote Cystic Fibrosis Self-Management
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: mHealth apps hold potential to provide automated, tailored support for treatment adherence among individuals with chronic medical conditions. Yet relatively little empirical research has guided app development and end users are infrequently involved in designing the app features or functions that would best suit their needs. Self-management apps may be particularly useful for people with chronic conditions like cystic fibrosis (CF) that have complex, demanding regimens. OBJECTIVE: The aim of this mixed-methods study was to involve individuals with CF in guiding the development of engaging, effective, user-friendly adherence promotion apps that meet their preferences and self-management needs. METHODS: Adults with CF (n=16, aged 21-48 years, 50% male) provided quantitative data via a secure Web survey and qualitative data via semi-structured telephone interviews regarding previous experiences using apps in general and for health, and preferred and unwanted features of potential future apps to support CF self-management. RESULTS: Participants were smartphone users who reported sending or receiving text messages (93%, 14/15) or emails (80%, 12/15) on their smartphone or device every day, and 87% (13/15) said it would be somewhat or very hard to give up their smartphone. Approximately one-half (53%, 8/15) reported having health apps, all diet/weight-related, yet many reported that existing nutrition apps were not well-suited for CF management. Participants wanted apps to support CF self-management with characteristics such as having multiple rather than single functions (eg, simple alarms), being specific to CF, and minimizing user burden. Common themes for desired CF app features were having information at one's fingertips, automation of disease management activities such as pharmacy refills, integration with smartphones' technological capabilities, enhancing communication with health care team, and facilitating socialization within the CF community. Opinions were mixed regarding gamification and earning rewards or prizes. Participants emphasized the need for customization options to meet individual preferences and disease management goals. CONCLUSIONS: Unique capabilities of emerging smartphone technologies (eg, social networking integration, movement and location detection, integrated sensors, or electronic monitors) make many of these requests possible. Involving end users in all stages of mHealth app development and collaborating with technology experts and the health care system may result in apps that maintain engagement, improve integration and automation, and ultimately impact self-management and health outcomes.
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.000 | 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