Nurses’ Roles in mHealth App Development: Scoping Review
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
BACKGROUND: Although mobile health (mHealth) apps for both health consumers and health care providers are increasingly common, their implementation is frequently unsuccessful when there is a misalignment between the needs of the user and the app's functionality. Nurses are well positioned to help address this challenge. However, nurses' engagement in mHealth app development remains unclear. OBJECTIVE: This scoping review aims to determine the extent of the evidence of the role of nurses in app development, delineate developmental phases in which nurses are involved, and to characterize the type of mHealth apps nurses are involved in developing. METHODS: We conducted a scoping review following the 6-stage methodology. We searched 14 databases to identify publications on the role of nurses in mHealth app development and hand searched the reference lists of relevant publications. Two independent researchers performed all screening and data extraction, and a third reviewer resolved any discrepancies. Data were synthesized and grouped by the Software Development Life Cycle phase, and the app functionality was described using the IMS Institute for Healthcare Informatics functionality scoring system. RESULTS: The screening process resulted in 157 publications being included in our analysis. Nurses were involved in mHealth app development across all stages of the Software Development Life Cycle but most frequently participated in design and prototyping, requirements gathering, and testing. Nurses most often played the role of evaluators, followed by subject matter experts. Nurses infrequently participated in software development or planning, and participation as patient advocates, research experts, or nurse informaticists was rare. CONCLUSIONS: Although nurses were represented throughout the preimplementation development process, nurses' involvement was concentrated in specific phases and roles.
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.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.000 | 0.002 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it