MétaCan
Menu
Back to cohort
Record W2796817098 · doi:10.2196/mhealth.9620

Managing Patient-Generated Health Data Through Mobile Personal Health Records: Analysis of Usage Data

2018· article· en· W2796817098 on OpenAlexvenueno aff
Yu Rang Park, Yura Lee, Ji Young Kim, Jeong Hoon Kim, Hae Reong Kim, Young‐Hak Kim, Woo Sung Kim, Jae‐Ho Lee

Bibliographic record

VenueJMIR mhealth and uhealth · 2018
Typearticle
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsnot available
Fundersnot available
KeywordsMedical recordMedicinemHealthDiseaseDiabetes mellitusObesityHealth recordsMedical emergencyFamily medicineHealth careInternal medicineNursing

Abstract

fetched live from OpenAlex

BACKGROUND: Personal health records (PHRs) and mHealth apps are considered essential tools for patient engagement. Mobile PHRs (mPHRs) can be a platform to integrate patient-generated health data (PGHD) and patients' medical information. However, in previous studies, actual usage data and PGHD from mPHRs have not been able to adequately represent patient engagement. OBJECTIVE: By analyzing 5 years' PGHD from an mPHR system developed by a tertiary hospital in South Korea, we aimed to evaluate how PGHD were managed and identify issues in PGHD management based on actual usage data. Additionally, we analyzed how to improve patient engagement with mPHRs by analyzing the actively used services and long-term usage patterns. METHODS: We gathered 5 years (December 2010 to December 2015) of log data from both hospital patients and general users of the app. We gathered data from users who entered PGHD on body weight, blood pressure (BP), blood glucose levels, 10-year cardiovascular disease (CVD) risk, metabolic syndrome risk, medication schedule, insulin, and allergy. We classified users according to whether they were patients or general users based on factors related to continuous use (≥28 days for weight, BP, and blood glucose, and ≥180 days for CVD and metabolic syndrome), and analyzed the patients' characteristics. We compared PGHD entry counts and the proportion of continuous users for each PGHD by user type. RESULTS: The total number of mPHR users was 18,265 (patients: n=16,729, 91.59%) with 3620 users having entered weight, followed by BP (n=1625), blood glucose (n=1374), CVD (n=764), metabolic syndrome (n=685), medication (n=252), insulin (n=72), and allergy (n=61). Of those 18,256 users, 3812 users had at least one PGHD measurement, of whom 175 used the PGHD functions continuously (patients: n=142, 81.14%); less than 1% of the users had used it for more than 4 years. Except for weight, BP, blood glucose, CVD, and metabolic syndrome, the number of PGHD records declined. General users' continuous use of PGHD was significantly higher than that of patients in the blood glucose (P<.001) and BP (P=.03) functions. Continuous use of PGHD in health management (BP, blood glucose, and weight) was significantly greater among older users (P<.001) and men (P<.001). In health management (BP, weight, and blood glucose), overall chronic disease and continuous use of PGHD were not statistically related (P=.08), but diabetes (P<.001) and cerebrovascular diseases (P=.03) were significant. CONCLUSIONS: Although a small portion of users managed PGHD continuously, PGHD has the potential to be useful in monitoring patient health. To realize the potential, specific groups of continuous users must be identified, and the PGHD service must target them. Further evaluations for the clinical application of PGHD, feedback regarding user interfaces, and connections with wearable devices are needed.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.005
metaresearch head score (Gemma)0.020
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.005
Threshold uncertainty score0.026

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0050.020
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0040.006
Science and technology studies0.0000.000
Scholarly communication0.0010.002
Open science0.0010.001
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0010.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.211
GPT teacher head0.509
Teacher spread0.298 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designObservational
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations64
Published2018
Admission routes1
Has abstractyes

Explore more

Same venueJMIR mhealth and uhealthSame topicMobile Health and mHealth ApplicationsFrench-language works237,207