Why Local Innovation Matters in Digital Health
Good digital care starts with the setting in which it will be used. Language, everyday constraints and the work of local teams belong in the design from the beginning.
A service can look clear in a demonstration and still be difficult to use in an ordinary day. Local innovation begins by understanding that day: who needs help, which decisions they face, what resources are available and who carries the work when something goes wrong. It is less about where a product was coded than about whose reality shapes it.
Begin with a journey, not a feature list
Consider a fictional appointment journey. A person receives joining instructions on a shared phone, changes a work shift to attend and needs a relative’s help reading the message. A design review that asks only whether the booking button works misses much of the experience. Useful questions include whether the time is clear, the next step is understandable and the person has a safe way to ask for help.
The same exercise belongs with staff. A new alert may look helpful to a patient while adding another inbox for a team with no agreed responsibility to monitor it. Before designing another notification, establish who receives it, when they can respond and how unresolved work is recognised.
Language is part of access
Translation needs more than a language menu. Instructions, errors, consent explanations and follow-up information all need to make sense. An apparently small word such as ‘submitted’ can be mistaken for ‘accepted’. Testing comprehension matters as much as translating the label.
English and French content can widen a website’s usefulness, but neither covers every language preference in Southern Africa. Accessible text, clear structure and a route to ask about support are practical starting points. They should not be presented as proof that every language or accommodation is available in a clinical service.
Invite disagreement early
A useful design discussion gives people permission to say that a process does not fit. Ask someone to explain what they think will happen after each step, rather than asking whether they like the screen. Include people who need support, people using older devices and staff responsible for the less visible administrative work.
For example, a team might discover that a confirmation message is clear to its authors but confusing when read out loud. Changing the wording is worthwhile before adding more features. Such examples describe a method of working; they are not reports of completed AfriMed community research.
Connect local insight with evidence
Africa CDC’s Digital Transformation Strategy places governance, workforce skills and interoperability alongside digital tools. For a local design team, that points to a practical question: what support and shared rules would make the tool useful here? A promising interface still needs evaluation in the setting where people will use it.
Sources: Africa CDC — Digital Transformation Strategy (2023)
What this means for AfriMed
AfriMed’s regional ambition needs to be informed by the people and organisations who would use it. The starting conversation should identify a concrete coordination problem, the people responsible and the constraints a solution must respect. It should also establish what success would look like and how difficulties would be reported.
We do not assume that a workflow demonstrated in one setting is ready for every country or institution. Local innovation is an ongoing practice of listening, adapting and checking. A credible invitation is therefore specific: tell us where information or responsibility becomes unclear in your work, and we can discuss whether the existing capabilities fit.
