Lack of Adoption of a Mobile App to Support Patient Self-Management of Diabetes and Hypertension in a Federally Qualified Health Center: Interview Analysis of Staff and Patients in a Failed Randomized Trial
Pourquoi ce travail est dans la base
Une base qui oublie comment elle a trouvé un travail ne peut pas être vérifiée. Voici les voies qui ont admis celui-ci.
Notice bibliographique
Résumé
BACKGROUND: Thousands of mobile health (mHealth) apps have been developed to support patients' management of their health, but the effectiveness of many of the apps remains unclear. While mHealth apps appear to hold promise for improving the self-management of chronic conditions across populations, failure to balance the system demands of the app with the needs, interests, or resources of the end users can undermine consumers' adoption of these technologies. OBJECTIVE: The original aim of this study was to evaluate the effectiveness of a commercial mHealth app in improving clinical outcomes for adult patients in a Federally Qualified Health Center (FQHC) with uncontrolled diabetes and/or hypertension. Patients entered clinical data into the app, which also supported messaging between patients and providers. After a 4-month period of vigorous recruitment, the trial was suspended due to low enrollment and inconsistent use of the app by enrolled patients. The project aim was changed to understanding why the trial was unsuccessful. METHODS: We used the user-task-context (eUTC) usability framework to develop a set of interview questions for patients and staff who were involved in the trial. All interviews were done by phone and lasted 20 to 30 minutes. Interviews were not recorded. RESULTS: There was a poor fit between the app, end users, and recruitment and treatment approaches in our setting. Usability testing might have revealed this prior to launch but was not an option. There was not sufficient time during routine care for clinical staff to familiarize patients with the app or to check clinical data and messages, which are unreimbursed activities. Some patients did not use the app appropriately. The lack of integration with the electronic health record (EHR) was cited as a problem for both patients and staff who also said the app was just one more thing to attend to. CONCLUSIONS: This brief trial underscores the pitfalls in the utilization of mHealth apps. Effective use of mHealth tools requires a good fit between the app, the users' electronic health (eHealth) literacy, the treatment approach, staff time, and reimbursement for services. The last 3 are contextual factors of the setting that affected the adoption of the app and context is an important factor in implementation science. We recommend that researchers address contextual factors in the trial and adoption of mHealth technologies.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,002 | 0,000 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,002 | 0,000 |
| Bibliométrie | 0,001 | 0,000 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,000 | 0,000 |
| Science ouverte | 0,000 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,000 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découle