Why it exists
Africa has no shortage of health and education apps. What it has lacked is a common foundation that lets these tools work together without custom integration every time.
Global standards such as FHIR and xAPI were designed for reliable connectivity and English-first metadata. DatAfri does not replace them. It adds the layer that African deployments need.
Problems it solves
Identity offline
Unique record identity across devices that are rarely online at the same time.
Sync and conflicts
Reliable sync and conflict resolution in low-connectivity settings.
Privacy
Privacy handling aligned with the African Union Malabo Convention.
Reliable deletion
Deletion that a late-syncing device cannot reverse.
How it is structured
DatAfri Base is the foundation that every record follows. DatAfri Domain Protocols sit on top and define what goes inside records for a specific use. The first published domain is DatAfri Health.
Reference implementations
| Application | Description |
|---|---|
| Asibi | Offline-first community health triage |
| EpiRadar | Outbreak intelligence dashboard |
| EpiSitRep AI | AI-assisted situation report generator |
Designed to be adopted
The base layer is deliberately small. An intermediate developer can produce a valid DatAfri record within fifteen minutes of first reading the specification.
