MétaCan
Menu
← Back to cohort
Record W2945476588 · doi:10.2196/14124

Technical Guidance for Clinicians Interested in Partnering With Engineers in Mobile Health Development and Evaluation

2019· article· en· W2945476588 on OpenAlexvenueno aff
Lochan M. Shah, William Yang, Ryan Demo, Matthias Lee, Daniel Weng, Rongzi Shan, Shannon Wongvibulsin, Erin M. Spaulding, Françoise A. Marvel, Seth S. Martin

Bibliographic record

VenueJMIR mhealth and uhealth · 2019
Typearticle
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsnot available
FundersNational Institute of Nursing ResearchNational Heart, Lung, and Blood Institute
KeywordsmHealthContext (archaeology)BluetoothPsychological interventionHealth careInternet privacyIntervention (counseling)Process (computing)Computer scienceTelemedicinePopulationMedicineKnowledge managementNursingWirelessTelecommunications

Abstract

fetched live from OpenAlex

The explosion of mobile health (mHealth) interventions has prompted significant investment and exploration that has extended past industry into academia. Although research in this space is emerging, it focuses on the clinical and population level impact across different populations. To realize the full potential of mHealth, an intimate understanding of how mHealth is being used by patients and potential differences in usage between various demographic groups must also be prioritized. In this viewpoint, we use our experiences in building an mHealth intervention that incorporates an iOS app, Bluetooth-enabled blood pressure cuff, and Apple Watch to share knowledge on (1) how user interaction data can be tracked in the context of health care privacy laws, (2) what is required for effective, nuanced communication between clinicians and engineers to design mHealth interventions that are patient-centered and have high clinical impact, and (3) how to handle and set up a process to handle user interaction data efficiently.

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.027
metaresearch head score (Gemma)0.126
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Other · Consensus signal: none
Teacher disagreement score0.220
Threshold uncertainty score0.735

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0270.126
Meta-epidemiology (narrow)0.0020.002
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0040.002
Science and technology studies0.0020.002
Scholarly communication0.0050.006
Open science0.0020.006
Research integrity0.0060.005
Insufficient payload (model declined to judge)0.2200.164

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.115
GPT teacher head0.509
Teacher spread0.394 · 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 designNot applicable
Domainnot available
GenreOther

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

Citations10
Published2019
Admission routes1
Has abstractyes

Explore more

Same venueJMIR mhealth and uhealth→Same topicMobile Health and mHealth Applications→French-language works237,207→