MétaCan
Menu
Back to cohort
Record W2942276329 · doi:10.2196/13963

Development and Implementation of a Mobile Phone–Based Prevention of Mother-To-Child Transmission of HIV Cascade Analysis Tool: Usability and Feasibility Testing in Kenya and Mozambique

2019· article· en· W2942276329 on OpenAlexvenueno aff
Nami Kawakyu, Ruth Nduati, Khátia Munguambe, Joana Coutinho, Nancy Mburu, Georgina DeCastro, Celso Inguane, Andrew Zunt, Neil Abburi, Kenneth Sherr, Sarah Gimbel

Bibliographic record

VenueJMIR mhealth and uhealth · 2019
Typearticle
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsnot available
FundersNational Institute of Allergy and Infectious Diseases
KeywordsUsabilityFocus groupNursingMedicineHealth facilityHealth careLikert scalemHealthQualitative researchPsychologyPsychological interventionComputer sciencePopulationEnvironmental healthBusiness

Abstract

fetched live from OpenAlex

BACKGROUND: Prevention of mother-to-child HIV transmission (PMTCT) care cascade failures drive pediatric HIV infections in sub-Saharan Africa. As nurses' clinical and management role in PMTCT expand, decision-support tools for nurses are needed to facilitate identification of cascade inefficiencies and solutions. The mobile phone-based PMTCT cascade analysis tool (mPCAT) provides health facility staff a quick summary of the number of patients and percentage drop-off at each step of the PMCTC care cascade, as well as how many women-infant pairs would be retained if a step was optimized. OBJECTIVE: The objective of this study was to understand and improve the mPCAT's core usability factors and assess the health workers' experience with using the mPCAT. METHODS: Overall, 2 rounds of usability testing were conducted with health workers from 4 clinics and leading experts in maternal and child health in Kenya and Mozambique using videotaped think aloud assessment techniques. Semistructured group interviews gauged the understanding of mPCAT's core usability factors, based on the Nielsen Usability Framework, followed by development of cognitive demand tables describing the needed mPCAT updates. Post adaptation, feasibility was assessed in 3 high volume clinics over 12 weeks. Participants completed a 5-point Likert questionnaire designed to measure ease of use, convenience of integration into work, and future intention to use the mPCAT. Focus group discussions with nurse participants at each facility and in-depth interviews with nurse managers were also conducted to assess the acceptability, use, and recommendations for adaptations of the mPCAT. RESULTS: Usability testing with software engineers enabled real-time feedback to build a tool following empathic design principles. The revised mPCAT had improved navigation and simplified data entry interface, with only 1 data entry field per page. Improvements to the results page included a data visualization feature and the ability to share results through WhatsApp. Coding was simplified to enable future revisions by nontechnical staff-critical for context-specific adaptations for scale-up. Health care workers and facility managers found the tool easy to use (mean=4.3), used the tool very often (mean=4.1), and definitely intended to continue to use the tool (mean=4.8). Ease of use was the most common theme identified, with emphasis on how the tool readily informed system improvement decision making. CONCLUSIONS: The mPCAT was well accepted by frontline health workers and facility managers. The collaborative process between software developer and user led to the development of a more user-friendly, context-specific tool that could be easily integrated into routine clinical practice and workflow. The mPCAT gave frontline health workers and facility managers an immediate, direct, and tangible way to use their clinical documentation and routinely reported data for decision making for their own clinical practice and facility-level improvements.

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.017
metaresearch head score (Gemma)0.020
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.017
Threshold uncertainty score0.091

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0170.020
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.001
Science and technology studies0.0010.001
Scholarly communication0.0010.001
Open science0.0010.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0010.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.

Opus teacher head0.066
GPT teacher head0.455
Teacher spread0.389 · 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.

The models applied no category: nothing in the taxonomy fit this work.
Study designObservational
Domainnot available
GenreEmpirical

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

Citations19
Published2019
Admission routes1
Has abstractyes

Explore more

Same venueJMIR mhealth and uhealthSame topicMobile Health and mHealth ApplicationsFrench-language works237,207