MétaCan
Menu
Back to cohort
Record W4200589373 · doi:10.2196/29197

A Mobile App to Support Self-management of Chronic Kidney Disease: Development Study

2021· article· en· W4200589373 on OpenAlexvenueno aff
Talar Markossian, Jason Boyda, Jennifer Taylor, Bella Etingen, François Modave, Ron Price, Holly Kramer

Bibliographic record

VenueJMIR Human Factors · 2021
Typearticle
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsnot available
FundersLoyola University Chicago
KeywordsKidney diseaseFocus groupSelf-managementMedicineDisease managementNephrologyFamily medicineNursingDiseaseInternal medicineBusinessComputer science

Abstract

fetched live from OpenAlex

BACKGROUND: Chronic kidney disease (CKD) is a common and costly condition that is usually accompanied by multiple comorbidities including type 2 diabetes, hypertension, and obesity. Proper management of CKD can delay or prevent kidney failure and help mitigate cardiovascular disease risk, which increases as kidney function declines. Smart device apps hold potential to enhance patient self-management of chronic conditions including CKD. OBJECTIVE: The objective of this study was to develop a mobile app to facilitate self-management of nondialysis-dependent CKD. METHODS: Our stakeholder team included 4 patients with stage 3-4 nondialysis-dependent CKD; a kidney transplant recipient; a caretaker; CKD care providers (pharmacists, a nurse, primary care physicians, a nephrologist, and a cardiologist); 2 health services and CKD researchers; a researcher in biomedical informatics, nutrition, and obesity; a system developer; and 2 programmers. Focus groups and in-person interviews with the patients and providers were conducted using a focus group and interview guide based on existing literature on CKD self-management and the mobile app quality criteria from the Mobile App Rating Scale. Qualitative analytic methods including the constant comparative method were used to analyze the focus group and interview data. RESULTS: Patients and providers identified and discussed a list of requirements and preferences regarding the content, features, and technical aspects of the mobile app, which are unique for CKD self-management. Requirements and preferences centered along themes of communication between patients and caregivers, partnership in care, self-care activities, adherence to treatment regimens, and self-care self-efficacy. These identified themes informed the features and content of our mobile app. The mobile app user can enter health data including blood pressure, weight, and blood glucose levels. Symptoms and their severity can also be entered, and users are prompted to contact a physician as indicated by the symptom and its severity. Next, mobile app users can select biweekly goals from a set of predetermined goals with the option to enter customized goals. The user can also keep a list of medications and track medication use. Our app includes feedback mechanisms where in-range values for health data are depicted in green and out-of-range values are depicted in red. We ensured that data entered by patients could be downloaded into a user-friendly report, which could be emailed or uploaded to an electronic health record. The mobile app also includes a mechanism that allows either group or individualized video chat meetings with a provider to facilitate either group support, education, or even virtual clinic visits. The CKD app also includes educational material on CKD and its symptoms. CONCLUSIONS: Patients with CKD and CKD care providers believe that a mobile app can enhance CKD self-management by facilitating patient-provider communication and enabling self-care activities including treatment adherence.

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.006
metaresearch head score (Gemma)0.010
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.006
Threshold uncertainty score0.031

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0060.010
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0010.000
Science and technology studies0.0010.000
Scholarly communication0.0010.001
Open science0.0010.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0030.001

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.045
GPT teacher head0.432
Teacher spread0.387 · 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 designBench or experimental
Domainnot available
GenreMethods

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

Citations31
Published2021
Admission routes1
Has abstractyes

Explore more

Same venueJMIR Human FactorsSame topicMobile Health and mHealth ApplicationsFrench-language works237,207