About Afiax Connected Healthcare
Afiax is building pan-African digital health infrastructure on top of Afiax FHIR, a FHIR-native clinical core.
The platform uses Medplum as an upstream foundation, then adds country packs, enterprise architecture, and delivery patterns for real-world health systems.
What Afiax is building
Afiax is not just a country implementation. It is a broader platform strategy that combines a canonical clinical core, country-specific overlays, and tenant-level operational configuration. Kenya is the first reference pack, not the definition of the whole platform.
Clinical core
Afiax FHIR remains the system of record for canonical FHIR resources, access control, audit, provenance, subscriptions, Bots, and controlled workflows.
Country packs
Country packs carry profiles, terminology, mappings, regulatory rules, and connector contracts without hard-coding country logic into the shared platform.
Connected platform
Afiax is designed to interoperate with registries, payers, ERP platforms, commerce systems, mobile apps, and partner services while preserving a normalized clinical source of truth.
Our values
Build deliberately
Afiax is intended for regulated healthcare operations, so we prefer explicit boundaries, phased delivery, and traceable decisions over fast but fragile complexity.
Keep the core consistent
The shared platform should stay country-neutral wherever possible. Country packs and tenant overlays should extend the core, not fragment it.
Design for ecosystems
Ministries, provider networks, labs, payers, pharmacies, and digital services all need to collaborate on the same healthcare fabric. Afiax is built for that shared operating environment.
Use engineering as leverage
We use open standards, disciplined APIs, automation, and documentation to make complex health system delivery reproducible across countries and implementations.
Operating model
Afiax uses a layered model so the platform can grow country by country without forcing a rewrite of the clinical core.
Pan-African core
Shared FHIR semantics, shared security primitives, and shared platform patterns create the base that every country pack and solution can inherit.
Country packs
Kenya is the first reference implementation. Additional markets should plug into the same model through profiles, mappings, terminology, and connector packages.
Tenant overlays
Networks, hospitals, insurers, and digital providers should be able to configure workflows, access, and integrations without forking the platform.