Certificate: Digital Health Systems & Telemedicine

Telemedicine and mHealth are the reach technologies of African digital health: the tools that move scarce expertise to where patients are and meet people on the phones already in their pockets. This Level II certificate course takes clinicians, health managers, service designers, and students from first principles to deployable practice across eight weeks and 15 contact hours.

You will learn to select the right telemedicine model, synchronous consultation, asynchronous tele-expertise, remote monitoring, or tele-education, for a given clinical problem, bandwidth reality, and specialist supply. You will match mHealth channels (SMS, USSD, voice, or app) to a user's literacy and devices, map health journeys into requirements, and design for low bandwidth, offline use, and local language. Drawing on exemplars like MomConnect and national instruments such as Ethiopia's 2020 telehealth guideline, you will establish clinical governance, integrate referrals that close the loop, and build financing that escapes the donor cliff.

Course glossary

• Digital health — The field of knowledge and practice associated with developing and using digital technologies to improve health (WHO); the umbrella over eHealth, mHealth, telehealth, and health informatics.
• Telemedicine — Delivery of healthcare services, where distance is a critical factor, using ICT for diagnosis, treatment, prevention, research, evaluation, and continuing education; client-to-provider or provider-to-provider.
• mHealth — Health practice supported by mobile devices; in Africa, prominently including SMS, USSD, and voice channels usable on feature phones, not only smartphone apps.
• Client-to-provider / provider-to-provider — The two ends-of-the-line configurations of telemedicine: patient-to-clinician, and clinician-to-clinician (e.g., frontline worker to specialist).
• Synchronous consultation — Real-time video or voice communication requiring simultaneous connectivity and scheduling.
• Asynchronous / store-and-forward tele-expertise — Capture-and-forward review of images or cases with a delayed specialist reply; tolerant of intermittent connectivity and the highest-yield model where bandwidth and specialist time are scarce.
• Remote patient monitoring (RPM) — Sensor-based tracking of patient physiology between visits, transmitted to a care team that acts on threshold breaches.
• Tele-education and supervision — Remote teaching, case review, and CPD for health workers; often the largest real use of telemedicine and a direct workforce multiplier.
• SMS / USSD / IVR — mHealth channels: SMS for universal text messaging on any phone; USSD for interactive *123# menu sessions without a data plan; IVR/voice for low-literacy users via recorded prompts in local language.
• Targeted client communication — A digital health intervention delivering tailored health messages to clients (e.g., MomConnect's maternal messages).
• Digital health platform (DHP) / infostructure — Shared, reusable information infrastructure (registries, shared health record, terminology, interoperability layer) on which applications run.
• Client registry / Master Patient Index — The platform component assigning each person a unique cross-system identity, the foundation of longitudinal records.
• Interoperability layer / HIE — The mediator through which systems exchange data, increasingly using FHIR, while enforcing standards, security, and audit.
• Clinical governance (telemedicine) — Defined scope, escalation rules, and documentation standards that make remote care safe and accountable.
• Telehealth guideline — A national instrument (e.g., Ethiopia 2020) defining permitted modalities, clinical/documentation expectations, and safeguards; regulation acting as enabling infrastructure.
• Readiness (access, training, attitude) — The measurable preconditions determining whether clinicians can practise telemedicine safely.
• Referral integration / closing the loop — Wiring tele-advice into the referral system so it changes patient flow, with a counter-referral that returns the outcome to the originating clinician.
• Loss to follow-up — A health-system challenge in which a person does not return for care or does not receive a needed follow-up.
• MomConnect — South Africa's national maternal mHealth service (2014); the book's exemplar of durability (government ownership, simplest tech first, integration with routine services).
• Low-bandwidth / offline-first design — Context-honest design treating offline operation, shared devices, local language, low literacy, and battery reality as explicit requirements.
• Principles for Digital Development — A field discipline codifying user-centred, context-aware, sustainable digital design.
• DHIS2 / OpenMRS — Open-source digital public goods: DHIS2 for aggregate routine reporting; the OpenMRS family for patient records — the backbone open stack of African digital health.
• eLMIS — Electronic logistics management information system, giving supply-chain stock visibility and reducing expiry and stockouts.
• Zipline — Rwanda's drone-delivery service, a model of contracting for outcomes (paying per delivery against a performance spec).
• Donor cliff — The collapse of a service when grants end and no domestic financing absorbs its recurrent costs; a design failure of unscheduled domestication.
• Total cost of ownership (TCO) — Full-lifecycle costing capturing the recurrent operating costs that dominate a system's lifetime bill.
• Domestication / institutionalization — Migrating core operating costs onto durable domestic instruments and transferring every life function from project to government institution.

---

Frequently asked questions

Q: I'm a clinician, not an IT specialist. Why do I need to understand platforms and infostructure? A: Because the quality and safety of the care you give remotely depend on it. A teleconsultation that cannot find your patient's prior records (no client registry), cannot return a result to the referring clinic (no interoperability), or stores notes nowhere others can read them (no shared health record) is unsafe and unconnected — however good your clinical judgement. You do not need to build platforms, but you do need to ask whether a service plugs into one. This is part of the clinical informatics competency the framework expects of every digitally fluent clinician.

Q: Which telemedicine model should I start with if resources are tight? A: Usually asynchronous store-and-forward tele-expertise (provider-to-provider). It tolerates intermittent connectivity, time-shifts scarce specialist time so one specialist clears a queue, documents the case by default, and — when paired with tele-education — steadily raises frontline capability. Teledermatology and teleradiology are proven African starting points. Reserve synchronous (live) care for cases that genuinely need real-time presence, and treat tele-education as the foundation under everything.

Q: How do I choose between SMS, USSD, IVR, and a smartphone app for a public-facing service? A: Start from the target user's real device, literacy, language, and social context — not from what feels modern. SMS and USSD reach almost any phone with no data plan; IVR/voice serves low-literacy users in local language; smartphone apps fit health workers with institutional devices but exclude many of the public, especially women on the wrong side of the gender digital divide. Pick the simplest channel that reaches everyone you need, and layer richer channels in later (as MomConnect migrated from SMS/USSD toward WhatsApp).

Q: What makes a telemedicine service legal and safe to run? A: Clinical governance: a defined scope (what may be done remotely, for which conditions), escalation rules (how to exit to in-person or emergency care), documentation standards (the same medico-legal record as an in-person visit, with consent), and paid, scheduled specialist time. Operate within your national instrument — Ethiopia's 2020 telehealth guideline, South Africa's HPCSA telehealth rules, Kenya's 2023 Digital Health Act — and ensure clinician readiness in access, training, and attitude. The WHO Consolidated Telemedicine Implementation Guide is the international reference.

Q: Our tele-advice is excellent but nothing seems to change for patients. What's wrong? A: Almost certainly missing referral integration. If the advice lives outside the referral system, patient flow does not change and the opinion is orphaned. Map the health journey, find where the loop is open (the referral may not arrive; the outcome never returns), and build the requirement that closes it — for example, "alert the health post when a referred mother delivers." A working service changes what happens to the patient and returns the outcome (counter-referral) to the originating clinician.

Q: Why does low-bandwidth design matter if 4G is spreading and smartphones are getting cheaper? A: Because connectivity and power remain intermittent for most of the people a health programme most needs to reach, and because designing for offline operation, local language, low literacy, shared devices, and battery reality is simply good design — it reaches the underserved and survives real conditions. The Ethiopia Blueprint names language as a critical barrier to adoption. Designing for the best case excludes the very populations digital health is meant to serve and produces another entry in the pilot graveyard.

Q: What is the "donor cliff," and how do I avoid it? A: It is the collapse of a well-performing telemedicine or mHealth service when grant funding ends in year three and no domestic budget line or reimbursement exists to absorb its recurrent costs. Avoid it by scheduling domestication from the start: do a full total-cost-of-ownership analysis (recurrent costs dominate), then move core costs onto durable instruments — government budget integration, transition-pointed donor financing, health-financing/reimbursement (make the teleconsultation reimbursable), and disciplined blended models. The transition plan belongs in the funding proposal, not the exit report.

Q: How does my country's context change my strategy? A: It shapes which path to scale is realistic. In a public-flagship context like South Africa (and largely Ethiopia), national scale runs through strong public institutions and a ministry budget line — with recurrent financing as the chief risk. In a mobile-market context like Kenya, private rails (M-PESA, M-TIBA) accelerate reach and statute catches up to govern it. In a scale-against-constraint context like Nigeria, innovation concentrates in enterprises (Helium Health, LifeBank) and governance catch-up is the binding agenda. Read your country against these patterns to find where your opportunities and constraints actually lie.