-
JMIR mHealth and uHealth · Feb 2020
Medication Management Apps for Diabetes: Systematic Assessment of the Transparency and Reliability of Health Information Dissemination.
- Zhilian Huang, Elaine Lum, and Josip Car.
- Centre for Population Health Sciences, Lee Kong Chian School of Medicine, Nanyang Technological University, Singapore, Singapore.
- JMIR Mhealth Uhealth. 2020 Feb 19; 8 (2): e15364.
BackgroundSmartphone apps are increasingly used for diabetes self-management because of their ubiquity and ability to help users to personalize health care management. The number of diabetes apps has proliferated in recent years, but only a small subset of apps that pose a higher risk are regulated by governmental agencies. The transparency and reliability of information sources are unclear for apps that provide health care advice and are not regulated by governmental agencies.ObjectiveThis study aimed to assess the transparency and reliability of information disseminated via diabetes apps against 8 criteria adapted from the Health On the Net code of conduct (HONcode) principles.MethodsEnglish-language diabetes-related terms were searched on a market explorer (42matters) on June 12, 2018. Apps with medication and blood glucose management features were downloaded and evaluated against the App-HONcode criteria adapted from the 8 HONcode principles: authoritative, complementarity, privacy, attribution, justifiability, transparency, financial disclosure, and advertising policy. Apps were profiled by operating platforms (ie, Android and iOS) and the number of downloads (ie, Android only: ≥100,000 downloads and <100,000 downloads).ResultsA total of 143 apps (81 Android and 62 iOS) were downloaded and assessed against the adapted App-HONcode criteria. Most of the apps on the Android and iOS platforms fulfilled between 2 and 6 criteria, but few (20/143, 14.0%) apps mentioned the qualifications of individuals who contributed to app development. Less than half (59/143, 39.2%) of the apps disclaimed that the information provided or app functions do not replace the advice of the health care provider. A higher proportion of iOS apps fulfilled 5 or more App-HONcode criteria compared with Android apps. However, Android apps were more likely to have the developer's email listed on the app store (Android: 75/81, 98%; and iOS: 52/62, 84%; P=.005) compared with iOS apps. Of the Android apps assessed, a significantly higher proportion of highly downloaded apps had a privacy and confidentiality clause (high downloads: 15/17, 88%; and low downloads: 33/64, 52%; P=.006) and were more likely to discuss their financial sources (high downloads: 14/17, 82%; and low downloads: 32/64, 50%; P=.03) compared with apps with a low number of downloads.ConclusionsGaps in the disclosure of the developer's qualification, funding source, and the complementary role of the app in disease management were identified. App stores, developers, and medical providers should collaborate to close these gaps and provide more transparency and reliability to app users. Future work can further examine the consent-seeking process for data collection, data management policies, the appropriateness of advertising content, and clarity of privacy clause of these apps.©Zhilian Huang, Elaine Lum, Josip Car. Originally published in JMIR mHealth and uHealth (http://mhealth.jmir.org), 19.02.2020.
Notes
Knowledge, pearl, summary or comment to share?You can also include formatting, links, images and footnotes in your notes
- Simple formatting can be added to notes, such as
*italics*
,_underline_
or**bold**
. - Superscript can be denoted by
<sup>text</sup>
and subscript<sub>text</sub>
. - Numbered or bulleted lists can be created using either numbered lines
1. 2. 3.
, hyphens-
or asterisks*
. - Links can be included with:
[my link to pubmed](http://pubmed.com)
- Images can be included with:
![alt text](https://bestmedicaljournal.com/study_graph.jpg "Image Title Text")
- For footnotes use
[^1](This is a footnote.)
inline. - Or use an inline reference
[^1]
to refer to a longer footnote elseweher in the document[^1]: This is a long footnote.
.