| Literature DB >> 24555733 |
Clara B Aranda-Jan, Neo Mohutsiwa-Dibe, Svetla Loukanova1.
Abstract
BACKGROUND: Access to mobile phone technology has rapidly expanded in developing countries. In Africa, mHealth is a relatively new concept and questions arise regarding reliability of the technology used for health outcomes. This review documents strengths, weaknesses, opportunities, and threats (SWOT) of mHealth projects in Africa.Entities:
Mesh:
Year: 2014 PMID: 24555733 PMCID: PMC3942265 DOI: 10.1186/1471-2458-14-188
Source DB: PubMed Journal: BMC Public Health ISSN: 1471-2458 Impact factor: 3.295
SWOT analysis of included studies
| -Potential to enhance timeliness in reporting health and stock data in rural and remote areas [ | -High facility workload and staff/patient/user illiteracy [ | |||
| -Improved patient-health worker and clinic staff-health worker communication [ | -Results are variable depending on the duration of the intervention and may be overestimated [ | -Lack of stock management resulting in patients untreated [ | -Limited knowledge on the effects of mHealth on patient health outcomes in low-resource settings [ | |
| -Difficult to monitor text messages content [ | -mHealth projects are regarded as innovative and current data collection methods tend to have poor quality [ | -Use of mobile technology for research is recent [ | ||
| -Higher rate and more efficient patient follow-up [ | -Reported patient anxiety due receiving information [ | -Dependency in donor funding and limited funding opportunities may limit long-term sustainability [ | ||
| -Supports efficient stock management, local drug distribution, counting and ordering accuracy, and supply chain monitoring [ | -mHealth results are dependant of external factors (e.g. long duration of patient treatment may reduce adherence and motivation to participate) [ | |||
| | ||||
| -Allows delivery of lab text results [ | ||||
| -Overcome logistical and distance barriers [ | ||||
| -Provide health education [ | ||||
| -Support patient management [ | -Unclear roles, responsibilities, actions, boundaries and responses needed at different levels of healthcare system (government) for project implementation and scale-up [ | -Existing communication gap between health workers, managers and patients [ | -Political crisis may hindered project implementation and results [ | |
| -Intervention flexible to be adapted to local context and language [ | -Project results depend on training and clinical practice of health workers [ | -Weak routine health, logistics, and surveillance data reporting systems [ | -Current care delivery processes will need to be redesigned (e.g. change to electronic records and data) [ | |
| -Allows focusing efforts of clinical staff in areas not covered by the intervention (e.g. remote areas with no mobile phone coverage) [ | -Most pilot projects are started by implementing organisations themselves rather than integrated to the health system [ | -Monitoring and evaluation of programmes may be done with collection of electronic information[ | -Costs of mHealth implementation may affect patient treatment costs [ | |
| -Public-private partnerships proved to work effectively in these projects [ | -mHealth projects are unlikely to prove effective in poorly performing systems [ | -Improved adherence to clinical guidelines by health workers is required [ | -Unknown health systems complexities for large scale implementation of mHealth projects [ | |
| -High government commitment, existing governmental eHealth strategy [ | -Lack of cultural and organisational capacity to manage digital health information [ | |||
| -Availability of local private providers willing to set up the mHealth system [ | ||||
| -Increased participation of local health staff in active case detection in surveillance systems (e.g. malaria) [ | ||||
| -Places rural health centres in direct communication with the MoH and other stakeholders [ | -Underutilise community health workforce (e.g. health workers) [ | |||
| -Difficult to collect and disseminate health data in remote areas [ | ||||
| -Support provision of user and staff training [ | -Low patient motivation to participate (e.g. reply messages or calls) [ | -Implementation needs to become multidisciplinary [ | -Challenge of management of mHealth projects remain underestimated [ | |
| -Minimal human resources and training are required [ | -Small sample size of pilot projects provide limited or biased results [ | -Available funding from larger programmes (e.g. PEPFAR mobile clinic) [ | ||
| -Financial incentive (e.g. airtime credit) allows high response rate to the project [ | -Costs and logistics affect text messaging responding on time [ | -Reporting transparency for donors and stakeholders [ | ||
| -Allows real-time supervision and monitoring work rate, attendance, and staff working hours [ | -Occasional staff shortages during project implementation [ | -Low capacity and administrative challenges for data collection [ | ||
| -Research is needed to optimize project delivery and intervention targets [ | ||||
| -Coded information contributes to data security and confidentiality [ | -Privacy concerns raised when using mobile phones, particularly if not owned by the patient [ | Not mentioned | -No minimum number of critical surveillance parameters to be reported has been established [ | |
| -Integration of SMS guidelines into healthcare process delivery [ | -Security measures (e.g. PIN) may be confusing to users when unfamiliar and poorly understood [ | -Lack of published data on feasibility and acceptability of confidentiality methods [ | ||
| -Unknown standards for monitoring and evaluation of mHealth programmes [ | ||||
| -Limited text capacity of mobile phones and text messages (e.g. up to 160 char.) [ | -High phone theft and limited electricity to charge phones [ | |||
| -Staff are not always able to use or act promptly to the text messaging requests, or do not have the skills required [ | -Potential of SMSs to influence uptake of healthcare technologies [ | -Technical or expert knowledge for development, maintenance and platforms (software and hardware) may be limited [ | ||
| -Variable access to mobile phones (e.g. not all patients own a personal phone, phones are often shared, cost of service) [ | -SMS-based software and delivery systems can be updated and review for future developments [ | |||
| -Mobile phones are not easily broken and less subject to thief than other technologies [ | -The lack of other communication technologies (e.g. internet) offers opportunities to mobile phones [ | |||
| -Use of similar technologies may not have similar results [ | ||||
| -Staff may not use the mobile phones appropriately or handle them with care [ | -Receptiveness of the technology is limited by socioeconomic and sociocultural factors, geographic barriers and quality of care [ | |||
| -Software may not be adaptable or flexible, and are still subject to human error [ | ||||
| -Allows monitoring and impact assessment prior to scaling-up [ | -No assessment has been performed to know if an effective implementation for one disease works for other diseases [ | |||
| -Feasible to be implemented in remote and resource-limited areas [ | -High upfront set-up costs [ | -Innovations for automated text messaging and partnerships with mobile technology developers may improve scalability [ | - Lack of a mechanism to use data collected at district and national levels [ | |
| -Open source programmes may support implementation of mHealth in low-resource settings [ | -MoH guidance and policies, and government financial support are lacking and are required for scaling-up [ | |||
| -Little existing evidence on efficacy and effectiveness of mHealth interventions [ |
The table below summarizes and compiles findings of the studies included in the review. The SWOT analysis methodology was used in five areas related to implementation of mHealth projects: project sustainability and mid/long-term results, integration of the project to the health system, technology and infrastructure, project management process, scale-up and replication, and legal, regulatory and standardization aspects. When more than 3 studies were found to be referring to the same issues, these were embolden to highlight their relevance according to appearance in the studies.
Figure 1Inclusion/exclusion flowchart.
Figure 2Main considerations for an effective mHealth project in the African context. Good project design (adapted to the local context, promotion, education and awareness of the project, etc.), Technology and resources (use local resources, capacity building, availability and maintenance), Involvement of stakeholders (strong public-private partnership, multidisciplinary teams, MoH, political leadership, local champion) and Government e-health/m-health department (program monitoring and evaluation, research, etc.).