Implementation Patterns
Afiax Enterprise uses Afiax FHIR as the clinical core for a broader pan-African platform. These reference patterns describe the kinds of solutions the platform is intended to support.
Reference patterns
Digital services and AI
Afiax should expose clean clinical and operational APIs so AI services, patient engagement tools, and workforce applications can interact with the platform without owning the source record.
Provider and specialty workflows
Provider portals, custom EHR workflows, scheduling, documentation, referrals, and care coordination should be delivered on top of the shared Afiax FHIR core.
Diagnostics and devices
Laboratories, imaging partners, and device ecosystems should integrate through normalized workflows that keep orders, results, attachments, and audit events consistent.
Country and national interoperability
Country packs, Bots, and custom operations allow Afiax to publish regulated outputs to registries, payers, and national platforms without turning those external payloads into the primary clinical model.
Kenya as the first reference pack
Kenya should prove the packaging model: canonical core first, country-specific exchange logic second, and tenant-specific rollout third. That makes the next country an extension problem instead of a rewrite.
Provider operations
Custom EHR workflows, provider portals, and care coordination should all use the same canonical resource model.
Diagnostics
Diagnostics workflows should integrate analyzers, partner labs, and reference systems through a governed interoperability layer.
Country packs
National logic should live under dedicated packaging and documentation rather than being spread across the entire product story.
Patient-facing services
Patient portals and digital front doors should reuse the same identity, consent, and longitudinal record patterns as provider-facing workflows.
Interoperability spine
External systems should connect through subscriptions, Bots, custom operations, and normalized return paths into the clinical core.
Architecture guardrails
The platform should keep clinical state in Afiax FHIR and let ERP, mobile, AI, and national systems remain integration peers.