MétaCan
Menu
← Back to cohort
Record W2980707842 · doi:10.2196/16247

Mobile Health Projects in a High-Complexity Reference Hospital: Case Study

2019· article· en· W2980707842 on OpenAlexvenueno aff
Imma Grau, Margarida Jansà, Pau Gascon, Raimundo Lozano-Rubí, Percy Efrain Pantoja, Daría Roca, Valentín Aragunde Miguens, Diego Hidalgo‐Mazzei, Joan Escarrabill

Bibliographic record

VenueJMIR mhealth and uhealth · 2019
Typearticle
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsnot available
Fundersnot available
KeywordsmHealthTelemedicineContext (archaeology)Wearable computerHealth careSnowball samplingNursingMedicineWearable technologyMedical educationPsychological interventionComputer scienceGeography

Abstract

fetched live from OpenAlex

BACKGROUND: The widespread adoption of mobile and wearable devices and apps makes it essential to assess their possible impact on the management of health and diseases. Health care providers (HCPs) find themselves faced with a new situation in their setting with the proliferation of mobile health (mHealth) intervention tests. Few studies have addressed the development of mHealth and the methodologies to manage these apps in a tertiary hospital. OBJECTIVE: The aim of this study was to evaluate the mHealth projects implemented in the Hospital Clínic of Barcelona to increase awareness of the context in which they are used and to develop policies for the development of good practice in mHealth innovation. METHODS: A prospective, descriptive cross-sectional study was conducted in a highly specialized university hospital with 850 beds for adults and a reference population of 520,000 inhabitants. A specific questionnaire was developed based on the Mobile Health 5 Dimensions European (MOHE 5D-EU) theoretical model to find mHealth projects. Apps, telemedicine, and wearable devices were included in the systematic search. For that purpose, a vertical (top-down) email-based snowball process was conducted. Data were collected from February to December 2018 by conducting personal interviews with HCPs using a structured questionnaire. RESULTS: During the study period, 45 interviews were conducted; 35 mHealth initiatives were found, with 25 targeted to patients and 10 to health professionals. Most mHealth initiatives (34/35, 97%) were related to the software field (apps and telemedicine initiatives), and one was related to wearable devices. Among the projects, 68% (24/35) were classified as medical devices or developments at the edge (developments susceptible to limitations depending on the intended use). In relation to data protection, 27 initiatives managing personal data (27/35, 77%) considered data protection legislation. Only 9% (3/35) of the initiatives had foreseen the use of interconnectivity standards. Most of the initiatives were funded by grants (14/35, 40%), sponsorships (5/35, 14%), or the hospital itself (5/35, 14%). In terms of clinical management, most projects were developed in the field of research, followed by professional tools, clinical information, and therapeutic education. Only 6 projects were involved with health care; all were led by either the industry or small and medium enterprises. CONCLUSIONS: This study helped create the design of a map of the mHealth projects conducted in our hospital that showed the stages of development of the different ongoing projects. This will allow monitoring of mHealth projects and construction of tools to reinforce areas with detected deficiencies. Our theoretical approach using a modified MOHE 5D-EU model was found to be useful for analyzing the characteristics of mHealth projects.

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.002
metaresearch head score (Gemma)0.007
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: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.008
Threshold uncertainty score0.031

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.007
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0020.002
Science and technology studies0.0060.002
Scholarly communication0.0020.001
Open science0.0020.004
Research integrity0.0040.002
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.144
GPT teacher head0.491
Teacher spread0.347 · 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

Citations0
Published2019
Admission routes1
Has abstractyes

Explore more

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