The Diabetes App Challenge: User-Led Development and Piloting of Internet Applications Enabling Young People With Diabetes to Set the Focus for Their Diabetes Consultations
Notice bibliographique
Résumé
BACKGROUND: Traditionally, some teenagers and young adults with diabetes have not engaged well at diabetes appointments, giving rise to concerns about long-term health risks. We considered that apps might help this group of patients to improve preparation for, and therefore engagement at their appointments. Although there are already many apps for young people with type 1 diabetes (YPD), we thought that by supporting YPD themselves to develop apps, the resulting products would have greater "authenticity" and relevance. OBJECTIVE: To test the feasibility of an online competition to (1) recruit and support YPD to develop apps (mobile or Internet based) to help prepare for clinic appointments, and (2) for these apps to be tested and rated by YPD. METHODS: The "Diabetes App Challenge" was a United Kingdom (UK) national competition, run between June and October 2012 for teams including at least one YPD (aged 16-25) to pilot the design and development of apps for use by other YPD prior to clinic appointments. The competition was advertised by social media, email, AdWords and postings on the Diabetes UK website. Registrants for the competition were supported via email and discussion forum. After app development, other YPD were invited (November 2012-February 2013) to trial the apps, choose and use one prior to a clinic appointment, and review their experiences. RESULTS: Of 56 people (including 28 YPD) who expressed interest in the competition, 6 teams (14 people) developed and submitted an app. Two apps aimed to facilitate agenda setting in clinic consultations, 2 enabled data logging and 2 helped insulin dose calculation. Of 135 YPD who registered to trial the apps, 83 (61.5%) took part (mean age 18.98, 37/83 male). Agenda setting apps were considered most useful for preparing for and setting the focus of clinic appointments (P=.02). Just over half (46/83, 55%) said they would use their chosen app again and 4/5 (67/83, 81%) would recommend it to a friend. CONCLUSIONS: This competition to engage YPD in developing and reviewing apps proved successful. App designers and testers saw a need for a range of functions. However, this may, in part, reflect a lack of detailed knowledge of all existing apps and be limited by the technical skills of YPD. App competitions appear worth applying to other patient groups, but future competitions should include a review stage and perhaps focus on ideas for app design for subsequent professional implementation.
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.
Comment cette classification a été obtenuedéplier
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,003 | 0,001 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,000 | 0,000 |
| Études des sciences et des technologies | 0,002 | 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écouleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule tête enseignante, pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».