Pricing and engagement
Afiax Enterprise pricing depends on the shape of the implementation. Engagements combine Afiax FHIR, the country-pack layer, integration work, and optional managed operations, so the right commercial model depends on what you are actually deploying.
For commercial discussions, contact info@afiax.africa or visit www.afiax.africa.
How Afiax is typically scoped
Most Afiax work is priced as a platform engagement rather than a generic self-service plan. Scope usually starts with Afiax FHIR, then adds the first country pack, production connectors, and tenant- or program-specific rollout requirements.
Platform foundation
Covers Afiax FHIR, the canonical data model, access control, auditability, and administrative tooling needed to stand up the shared platform.
Country-pack delivery
Covers country-specific profiles, terminology, mappings, connector contracts, and documentation. Kenya is the first reference pack in this model.
Managed operations
Covers hosting model, observability, support expectations, release management, and operational governance for production deployments.
Deployment model
Sovereign hosting, managed cloud, or self-hosted enterprise environments materially change scope and support requirements.
Integration breadth
The number and complexity of payer, registry, ERP, diagnostics, and partner integrations are major pricing drivers.
Workflow complexity
Country-pack rollout, approvals, automation, referrals, and multi-tenant configuration all affect the level of implementation work required.
Assurance and support
Audit needs, reconciliation tooling, delivery timelines, and support SLAs should be agreed explicitly as part of the engagement.
Best fit for early deployments
Start with one country, one high-value operational spine, and a small set of production-grade integrations. That approach proves the platform before expanding into broader enterprise services.
Best fit for enterprise rollouts
Larger health systems, insurers, ministries, and regional delivery networks generally need a phased program covering platform setup, country-pack implementation, rollout support, and long-term operations.
Best next step
Share the target country, deployment model, integration list, and operational goals. That is enough to turn the architecture into a realistic commercial scope.