Afiax FHIR is the FHIR-native clinical core for Afiax Enterprise, the broader pan-African digital healthcare platform.
The platform combines clinical interoperability, digital service layers, and modular country packs so national requirements stay local while the broader platform remains reusable.
Core: Afiax FHIR services, policies, subscriptions, Bots, and internal operations.
Digital services: provider workflows, patient engagement, analytics, telemedicine, and partner APIs built on the same core.
Localization: country packs and tenant overlays carry national rules, deployment choices, and customer-specific workflow constraints.
Afiax is designed so clinical data, digital services, and national interoperability can evolve together without forcing country-specific logic into the core platform.
Clinical source-of-truth data lives in canonical FHIR resources, not in national submission payloads.
National registries, terminology, payer workflows, and exchange connectors are packaged as modular overlays.
Provider workflows, patient engagement, telemedicine, and partner-facing services can share the same canonical platform.
Identifiable clinical data can remain in-country while non-sovereign tooling is isolated by policy.
Bots and FHIR operations coordinate auditable automation without pushing national API logic into the UI.
Each customer can inherit the shared platform while keeping tenant-specific workflow, secrets, and policies separate.
The business and technical platform includes clinical systems, remote care, analytics, and developer infrastructure, with country packs localizing that platform for each market.
Build identity, encounters, referrals, documents, and coverage workflows on top of a shared data model.
Support virtual care, patient engagement, and remote-care experiences without fragmenting the data layer.
Add dashboards, predictive services, and operational insight on top of normalized clinical data.
Expose APIs, Bots, and reusable contracts so partners and internal teams can extend the platform safely.
Operate the same platform as shared SaaS, dedicated runtimes, or managed in-country infrastructure.
Scale across providers, counties, payers, and future markets without forking the architecture.
Kenya is the first reference implementation used to validate the country-pack SDK and localization model.
Profiles, terminology, mappings, connectors, Bots, and compliance artifacts define the localization contract.
Kenya implements registries, eligibility, SHR publishing, and claims behind generic internal operations.
Future markets should inherit the same core model, SDK contracts, and tenant architecture instead of redefining the platform.
Use the architecture docs to define Afiax FHIR and its role in Afiax Enterprise, then open the country-pack section when you are ready to localize Kenya or the next market.