Social, Organizational, and Technological Factors Impacting Clinicians’ Adoption of Mobile Health Tools: Systematic Literature Review
Bibliographic record
Abstract
BACKGROUND: There is a growing body of evidence highlighting the potential of mobile health (mHealth) in reducing health care costs, enhancing access, and improving the quality of patient care. However, user acceptance and adoption are key prerequisites to harness this potential; hence, a deeper understanding of the factors impacting this adoption is crucial for its success. OBJECTIVE: The aim of this review was to systematically explore relevant published literature to synthesize the current understanding of the factors impacting clinicians' adoption of mHealth tools, not only from a technological perspective but also from social and organizational perspectives. METHODS: A structured search was carried out of MEDLINE, PubMed, the Cochrane Library, and the SAGE database for studies published between January 2008 and July 2018 in the English language, yielding 4993 results, of which 171 met the inclusion criteria. The Preferred Reporting Items for Systematic Review and Meta-Analysis guidelines and the Cochrane handbook were followed to ensure a systematic process. RESULTS: The technological factors impacting clinicians' adoption of mHealth tools were categorized into eight key themes: usefulness, ease of use, design, compatibility, technical issues, content, personalization, and convenience, which were in turn divided into 14 subthemes altogether. Social and organizational factors were much more prevalent and were categorized into eight key themes: workflow related, patient related, policy and regulations, culture or attitude or social influence, monetary factors, evidence base, awareness, and user engagement. These were divided into 41 subthemes, highlighting the importance of considering these factors when addressing potential barriers to mHealth adoption and how to overcome them. CONCLUSIONS: The study results can help inform mHealth providers and policymakers regarding the key factors impacting mHealth adoption, guiding them into making educated decisions to foster this adoption and harness the potential benefits.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.021 | 0.103 |
| Meta-epidemiology (narrow) | 0.002 | 0.002 |
| Meta-epidemiology (broad) | 0.008 | 0.009 |
| Bibliometrics | 0.019 | 0.019 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.004 | 0.004 |
| Open science | 0.002 | 0.003 |
| Research integrity | 0.003 | 0.002 |
| Insufficient payload (model declined to judge) | 0.004 | 0.000 |
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 itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".