MétaCan
Menu
Back to cohort
Record W2889893184 · doi:10.1038/s41746-018-0053-1

Agile research to complement agile development: a proposal for an mHealth research lifecycle

2018· review· en· W2889893184 on OpenAlexafffund
Kumanan Wilson, Cameron Bell, Lindsay Wilson, Holly O. Witteman

Bibliographic record

Venuenpj Digital Medicine · 2018
Typereview
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsOttawa HospitalUniversité LavalUniversity of Ottawa
FundersCanadian Institutes of Health ResearchHealth CanadaPublic Health AgencyPublic Health Agency of CanadaSanofi
KeywordsmHealthAgile software developmentProcess managementNew product developmentProduct lifecycleComputer scienceScrumKnowledge managementSystems engineeringRisk analysis (engineering)EngineeringHealth careMedicineBusinessSoftware developmentSoftware engineeringSoftwareMarketing

Abstract

fetched live from OpenAlex

Mobile health (mHealth) technology is increasingly being used, but academic evaluations supporting its use are not keeping pace. This is partly due to the disconnect between the traditional pharmaceutical approach to product evaluation, with its incremental approach, and the flexible way in which mHealth products are developed. An important step to addressing these problems lies in establishing agile research methods that complement the agile development methodologies used to create modern digital health applications. We describe an mHealth research model that mirrors traditional clinical research methods in its attention to safety and efficacy, while also accommodating the rapid and iterative development and evaluation required to produce effective, evidence-based, and sustainable digital products. This approach consists of a project identification stage followed by four phases of clinical evaluation: Phase 1: User Experience Design, Development, & Alpha Testing; Phase 2: Beta testing; Phase 3: Clinical Trial Evaluation; and Phase 4: Post-Market Surveillance. These phases include sample gating questions and are adapted to accommodate the unique nature of digital product development.

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.154
metaresearch head score (Gemma)0.088
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
Consensus categoriesnone
DomainCandidate signal: Methods · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Review · Consensus signal: none
Teacher disagreement score0.846
Threshold uncertainty score0.813

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.1540.088
Meta-epidemiology (narrow)0.0020.002
Meta-epidemiology (broad)0.0020.004
Bibliometrics0.0080.008
Science and technology studies0.0040.026
Scholarly communication0.0210.034
Open science0.0060.020
Research integrity0.0120.023
Insufficient payload (model declined to judge)0.0060.003

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.683
GPT teacher head0.691
Teacher spread0.008 · 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.

Study designTheoretical or conceptual
DomainMethods
GenreReview

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

Citations121
Published2018
Admission routes2
Has abstractyes

Explore more

Same venuenpj Digital MedicineSame topicMobile Health and mHealth ApplicationsFrench-language works237,207