The Target (modular) Architecture of openIMIS foresee several deployment possibilities and is installed "aside" a legacy installation. Aside may mean:
- on the same server, but as a separated (set of) process (listening to distinct ports)
- or on separated servers connected to each others behind a 'gateway' in order to look like a single one for the users
Today, the new openIMIS platform is installed in the following configurations:
NEPALI "TEST" Platform:
frontend modules versions:
- openimis/fe-core@0.0.15
- openimis/fe-home@0.0.7
- openimis/fe-location@0.0.5
- openimis/fe-insuree@0.0.10
- openimis/fe-medical@0.0.5
- openimis/fe-policy@0.0.8
- openimis/fe-claim@0.0.12
- openimis/fe-admin@0.0.11
- openimis/fe-tools@0.0.9
- openimis/fe-profile@0.0.9
ibackend modules versions:
- openimis-be-core==0.0.12
- openimis-be-location==0.0.4
- openimis-be-medical==0.0.5
- openimis-be-product==0.0.1
- openimis-be-insuree==0.0.6
- openimis-be-policy==0.0.7
- openimis-be-contribution==0.0.1
- openimis-be-claim==0.0.10
- openimis-be-api_fhir==0.0.4
backend modules versions:
- openimis-be-core==0.0.11
- openimis-be-location==0.0.3
- openimis-be-medical==0.0.3
- openimis-be-product==0.0.1
- openimis-be-insuree==0.0.4
- openimis-be-policy==0.0.6
- openimis-be-contribution==0.0.1
- openimis-be-claim==0.0.7
- openimis-be-api_fhir==0.0.4
NEPALI QA Platform
//TODO