...

Proxy plugins will be developed in the various layers and will be replaced once the new implementation is ready.

Transformation methodology

The very first iteration of OpenIMIS will thus be a "all proxy" implementation where every (functional) feature is a proxy in the (web) frontend layer to existing OpenIMIS implementation:

...

• what is needed from the core components, and its availability
• what has the most value (business wise)

Proxy replacement by own implementation

Proxy may be replaced by the target implementation, moving horizontally (in a layer) or vertically (cross layers)

Example, should we identify the Payers-related features as interesting to migrate first.

...

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

Proxy replacement does not necessary mean full features re-implementation of existing features.

OpenIMIS will indeed rely on other Software components out of OpenHIE, a proxy may be replaced by a delegated implementation.

Example, should HFR target an interface to DHIS2 (Organisation Units). Not all HFR features (like manage facilities hierarchy,...) must be re-implemented in the OpenIMIS.

OpenIMIS will still need search for facilities, reference them in the services (price lists,...)