The aim of this phase is to achieve a running version of openIMIS where:
The database in use at the en of this phase is still the current MSSQL instance, with no (or only minor) changes in the data structure. Finally, this phase is accomplished in iterations, module per module. Each iteration identifies the modules to be re-engineered and delivers a production-ready assembly of legacy and re-engineered modules, covering the current openIMIS functional scope. |
The very first iteration of of openIMIS will be a "all proxy" implementation where every (functional) feature is a proxy in the (web) frontend layer to existing openIMIS implementation:
...
Next iterations will will be planned to replace chosen proxy(ies) to their target implementation.
The core components (FE, BE,...) of openIMIS will be built (enhanced) along the proxy replacements.
The choice (order of) proxy replacement will thus be based on:
what is needed from the core components, and its availability
what has the most value (business wise)
Proxy replacement by own implementation
...
An iteration may target the Payers FE proxy replacement by implementing a BE proxy, targeting current openIMIS API (WebServices):
...
Depending on the identified workload, the iteration may even skip the BE proxy and connect the actual Payers BE plugins (Online and Batch) implementation:
...
Proxy replacement by delegation
...
the actual hierarchy management, facility description, grouping,... can be delegated to DHIS2:
...