This page provides a high-level (introduction) view of the OpenIMIS openIMIS targeted (modular) architecture.

The transition (transformation) plan from current (2018) OpenIMIS openIMIS implementation to this architecture is described in a separated page: Modular Transformation.

...

At Solution level, the roadmap clearly position OpenIMIS openIMIS as a component of OpenHIE platform.

...

• conforming to the OpenHIE platform standards (enforced via the OpenHIE Integration Layer)
• adopting the FHIR existing standards to expose OpenIMIS openIMIS - managed concepts

Software Component & Entity levels

Software Component and Entity levels modularity are fully in the scope (controlled by) of OpenIMISopenIMIS.

OpenIMIS openIMIS is built modular "from the core on": even low level features (like login,...) and central features (like Insurance Scheme management,...) are built as a plugins of a core platform.

...

• Frontend(s) layer
• Backend layer
• Database layer

Although OpenIMIS openIMIS is an assembly of components (themselves assemblies of plugins), deployments of OpenIMIS openIMIS doesn't impose a distributed deployment.

...

Within a project, scaling up by distributing components as the load increases is a very standard (and easy) operation:

...

openIMIS is NOT

• multi-tenant: while database table will receive a tenant-discriminant (index) column, being multi-tenant requires several precautions we are not going to address in early project phases (like computing/ IO resources sharing, forced coordinated upgrades,...)