MétaCan
Menu
Back to cohort
Record W2952464649 · doi:10.2196/13608

Mobile Apps for Medication Management: Review and Analysis

2019· review· en· W2952464649 on OpenAlex
Katarína Tabi, Abnashi Singh Randhawa, Fiona Choi, Zamina Mithani, Friederike Albers, Mohammadali Nikoo, Daniel Vigo, Kerry L. Jang, Regina Demlová, Michael Krausz

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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
venuePublished in a venue whose home country is Canada.

Bibliographic record

VenueJMIR mhealth and uhealth · 2019
Typereview
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsSimon Fraser UniversityCentre for Advancing Health OutcomesSt. Paul's HospitalUniversity of British Columbia
FundersLékařská fakulta, Masarykova univerzitaMasarykova Univerzita
KeywordsApp storeAndroid (operating system)Mobile phonemHealthInternet privacyPsychological interventionMobile deviceMobile appsMedicineWorld Wide WebPillContext (archaeology)Computer scienceNursing

Abstract

fetched live from OpenAlex

BACKGROUND: Pharmacotherapy remains one of the major interventional strategies in medicine. However, patients from all age groups and conditions face challenges when taking medications, such as integrating them into the daily routine, understanding their effects and side effects, and monitoring outcomes. In this context, a reliable medication management tool adaptable to the patient's needs becomes critical. As most people have a mobile phone, mobile apps offer a platform for such a personalized support tool available on the go. OBJECTIVE: This study aimed to provide an overview of available mobile apps, focusing on those that help patients understand and take their medications. We reviewed the existing apps and provided suggestions for future development based on the concept understand and manage, instead of the conventional adhere to medication. This concept aims to engage and empower patients to be in charge of their health, as well as see medication as part of a broader clinical approach, working simultaneously with other types of interventions or lifestyle changes, to achieve optimal outcomes. METHODS: We performed a Web search in the iOS Apple App Store and Android Google Play Store, using 4 search terms: medication management, pill reminder, medication health monitor, and medication helper. We extracted information from the app store descriptions for each eligible app and categorized into the following characteristics: features, author affiliation, specialty, user interface, cost, and user rating. In addition, we conducted Google searches to obtain more information about the author affiliation. RESULTS: A total of 328 apps (175 Android and 153 iOS) were categorized. The majority of the apps were developed by the software industry (73%, 11/15), a minority of them were codeveloped by health care professionals (15%, 3/20) or academia (2.1%; 7/328). The most prevalent specialty was diabetes (23 apps). Only 7 apps focused on mental health, but their content was highly comprehensive in terms of features and had the highest prevalence of the education component. The most prevalent features were reminder, symptom tracker, and ability to share data with a family member or doctor. In addition, we highlighted the features considered innovative and listed practical suggestions for future development and innovations. CONCLUSIONS: We identified detailed characteristics of the existing apps, with the aim of informing future app development. Ultimately, the goal was to provide users with effective mobile health solutions, which can be expected to improve their engagement in the treatment process and long-term well-being. This study also highlighted the need for improved standards for reporting on app stores. Furthermore, it underlined the need for a platform to offer health app users an ongoing evaluation of apps by health professionals in addition to other users and to provide them with tools to easily select an appropriate and trustworthy app.

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 imitation

Not 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.

metaresearch head score (Codex)0.004
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Science and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.937
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.000
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0050.000
Bibliometrics0.0010.002
Science and technology studies0.0020.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.150
GPT teacher head0.545
Teacher spread0.395 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it