Skip to main content

Welcome to Afiax FHIR

Platform architecture

Understand the broader Afiax platform model, delivery layers, and governance model.

Read more

Enterprise platform

Review the clinical core, interoperability layer, digital services, and deployment models.

Read more

Canonical FHIR model

See how Afiax keeps the shared model country-neutral while country packs bind local requirements.

Read more

Country packs

Learn how national integrations are packaged without turning the core into a country-specific fork.

Read more

Integration boundaries

See what belongs in Afiax FHIR, what belongs in country packs, and what belongs in adjacent services.

Read more

Developer stack

Run the platform locally, extend it with Bots and operations, and prepare for sovereign deployment.

Read more

What is Afiax FHIR?​

Afiax FHIR is the FHIR-native clinical core used inside Afiax Enterprise, the broader connected-healthcare offering under Afiax Connected Healthcare.

Afiax Enterprise combines:

  • Clinical core: canonical FHIR resources, access control, subscriptions, Bots, operations, and shared domain services
  • Digital service layers: provider workflows, patient engagement, telehealth, analytics, remote care, and partner APIs
  • Country packs: national terminology, registries, payer rails, claims, and exchange connectors
  • Tenant overlays: customer-specific configuration, workflow toggles, and deployment choices
  • Delivery models: SaaS, managed PaaS, and infrastructure patterns aligned to local sovereignty and scale needs

Platform scope​

  • Cloud-based electronic health record and clinical operations foundation
  • Interoperability and national exchange services built on HL7/FHIR
  • Telemedicine, remote-care, and patient engagement services
  • Financial and administrative enablement around the clinical core
  • Analytics and AI-driven decision support
  • Developer and partner platform capabilities via APIs, Bots, and country-pack contracts
  • Shared SaaS, dedicated runtime, and managed deployment options depending on market and customer needs

How the docs are organized​

  1. Start with the architecture overview for the broad Afiax platform model.
  2. Use the enterprise platform and canonical FHIR model docs to define the shared core.
  3. Open country packs when you are ready to localize the platform for a market.
  4. Use the active pack docs under country packs when you need country-specific implementation details.
  5. Use Bots, FHIR operations, and the FHIR datastore to deliver auditable workflows.

Core principles​

  • Country-neutral core, country-specific overlays
  • FHIR-native source of truth in canonical resources
  • No direct national API calls from UI applications
  • Sovereign deployment for identifiable clinical data
  • Audit, provenance, and reconciliation before production go-live

Country-pack note​

The general docs stay pan-African in scope. Country-specific implementation details live under the relevant country-pack docs, with Kenya documented as the current first active pack.

Platform foundation​

Afiax FHIR is built on Medplum open-source software and extended with Afiax-specific branding, country-pack support, and enterprise integration boundaries. See Platform foundation.

Building blocks​

Learn more​

Learn more about the broader company and market-facing platform at www.afiax.africa.

Reference material​