A Usability Study of a Mobile Health Application for Rural Ghanaian Midwives
Bibliographic record
Abstract
INTRODUCTION: Midwives in rural Ghana work at the frontline of the health care system, where they have access to essential data about the patient population. However, current methods of data capture, primarily pen and paper, make the data neither accessible nor usable for monitoring patient care or program evaluation. Electronic health (eHealth) systems present a potential mechanism for enhancing the roles of midwives by providing tools for collecting, exchanging, and viewing patient data as well as offering midwives the possibility for receiving information and decision support. Introducing such technology in low-resource settings has been challenging because of low levels of user acceptance, software design that does not match the end-user environment, and/or unforeseen challenges such as irregular power availability. These challenges are often attributable to a lack of understanding by the software developers of the end users' needs and work environment. METHODS: A mobile health (mHealth) application known as mClinic was designed to support midwife access to the Millennium Village-Global Network, an eHealth delivery platform that captures data for managing patient care as well as program evaluation and monitoring, decision making, and management. We conducted a descriptive usability study composed of 3 phases to evaluate an mClinic prototype: 1) hybrid lab-live software evaluation of mClinic to identify usability issues; 2) completion of a usability questionnaire; and 3) interviews that included low-fidelity prototyping of new functionality proposed by midwives. RESULTS: The heuristic evaluation identified usability problems related to 4 of 8 usability categories. Analysis of usability questionnaire data indicated that the midwives perceived mClinic as useful but were more neutral about the ease of use. Analysis of midwives' reactions to low-fidelity prototypes during the interview process supported the applicability of mClinic to midwives' work and identified the need for additional functionality. DISCUSSION: User acceptance is essential for the success of any mHealth implementation. Usability testing identified mClinic development flaws and needed software enhancements.
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.015 | 0.034 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.003 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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".