Usability of UgandaEMR+ among health workers in Uganda: adaptation and evaluation of the System Usability Scale in a low- resource EMR environment
This study adapted the System Usability Scale to evaluate UgandaEMR+ across four Ugandan facilities, revealing moderate overall usability hindered primarily by operational friction such as cumbersome workflows, complexity, and inconsistency caused by infrastructure and support challenges rather than core software functionality.
Original paper licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine Uganda's healthcare system is trying to upgrade from a giant, messy filing cabinet (paper records) to a sleek, modern digital library (the UgandaEMR+ system). The government has installed this digital library in over 1,000 hospitals and clinics, hoping it will make doctors' and nurses' jobs easier. But, there's a problem: many health workers are still sticking to their old paper notebooks, or they are using the new system only half-heartedly.
This research paper is like a "customer satisfaction survey" for that digital library. The researchers wanted to know: Is the system actually easy to use, or is it frustrating?
Here is the story of what they found, explained simply:
The "Report Card"
The researchers asked 302 health workers (doctors, nurses, lab techs) to grade the system using a standard "usability report card" called the System Usability Scale (SUS). Think of this like a Yelp review for software.
- The Overall Grade: The system got a "C" (Moderate). It's not broken, and it's not terrible, but it's not "A-list" either.
- The Split: About 28% of workers hated it (Low usability), 44% thought it was just okay (Moderate), and 28% thought it was great (High usability).
The Real Problem: It's Not the Car, It's the Road
The most interesting part of the study is why people gave it a "C."
The researchers broke down the survey into specific questions. They found that the workers didn't think the software itself was too hard to understand or too complicated to learn. Instead, they felt the system was cumbersome (clunky), inconsistent (unreliable), and hard to learn because of the environment around it.
Here are the metaphors for what the paper actually found:
The "Power Outage" Analogy:
Imagine trying to drive a brand-new, high-tech electric car, but every few miles, the electricity grid fails, and you have to jump out and push the car while it's still in gear.- What the paper says: The health workers said the system feels "cumbersome" not because the buttons are confusing, but because the electricity and internet keep cutting out. When the power dies, they have to switch back to paper, then switch back to the computer when power returns. This "hybrid" dance makes the whole process feel slow and clunky.
The "Broken Elevator" Analogy:
Imagine you are in a building with a new elevator. The elevator works fine, but if it gets stuck, no one comes to fix it for three days. You start to feel like the elevator is "inconsistent" or "broken," even though the machine itself is fine.- What the paper says: Workers felt the system was "inconsistent" because when a bug or error happened, there was no clear way to get help. The IT support was missing or slow, so small problems turned into big frustrations.
The "Wrong Map" Analogy:
Imagine you are used to walking a specific path to work. Suddenly, someone gives you a new map that forces you to walk a completely different route, even though the destination is the same. You feel like the new map is "hard to learn," but really, you just aren't used to the new path yet.- What the paper says: The system felt like it had a "high learning demand" not because the software was too smart, but because it didn't match how doctors and nurses actually do their daily work. They were trained on paper, and the digital system asked them to do things in a different order.
The Surprise Finding: Training Didn't Help Much
The researchers expected that if they gave workers more training, they would use the system more.
- The Result: They found no link between formal training and actually using the system.
- The Metaphor: Giving someone a manual on how to drive a car doesn't help if the road is full of potholes and the gas station is closed. The paper suggests that training alone isn't enough; you have to fix the "road" (the workflow and infrastructure) first.
The Bottom Line
The paper concludes that UgandaEMR+ is a decent tool, but it is being held back by its surroundings.
To make health workers love the system, you don't necessarily need to redesign the software interface (the "car"). Instead, you need to:
- Fix the power and internet (so the car can actually drive).
- Fix the IT support (so the elevator gets fixed quickly).
- Align the digital system with real-life workflows (so the map makes sense).
The researchers also proved that their "Report Card" (the adapted SUS survey) works well in these low-resource settings, meaning it can be used as a regular tool to check if the system is getting better or worse over time.
In short: The software isn't the villain; the environment (power, internet, and support) is making the software feel clumsy. Fix the environment, and the usability will improve.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.