Minimise data entry | Set targets for speed and usability, for example, less than 80 s for new patient registration and initial clinical visit and less than 20 s for follow-up patient visits Resist temptation to add features or data requirements unless speed and ease-of-entry targets can be maintained
|
Offline-first | Faster and more reliable, with less chance of patients not being registered or follow-up information not updated because of slow or absent connectivity Minimise data elements to be stored and avoid large data components, for example, photos or scans, to ensure capacity for storing data offline on mobile devices
|
Use QR codes for patient identification | |
Maximise usability | Design screens and interfaces based on actual user testing, not what programme experts or engineers think staff will want Use straightforward information design to provide providers and programme managers with visualisation of the most important indicators of programme progress The design and accessibility for Simple follow best-in-class standards, such as the US Digital.gov guidelines (https://digital.gov/resources) Prioritise usability for front-line staff over interoperability across different platforms
|
Easy to train in clinic | |
Data governance and security | A local or national government agency (eg, Ministry of Health) owns the data The system must have clear and ethical data governance from an early stage and address ownership transparently, such as through Memorandum of Understanding agreements outlining governance with each country’s Ministry of Health Mobile device data are encrypted both in transit and at rest using industry-standard security best practices Patients should have control of their own data, allowing them to monitor and improve their health, and must opt in at enrolment to consent to have their data collected
|
Enable mobile device use | |
Enable patient registers for recall to care | |
Build for scale | |