...
The following sections will specify the changes and enhancements brought by this project to the two components from each WP.
1 openIMIS FHIR Module
1.1 FHIR release four (R4) integration
| Expand | |||||
|---|---|---|---|---|---|
| |||||
|
| Expand | |||||
|---|---|---|---|---|---|
| |||||
|
1.2 FHIR R4 extensions development
1.3 FHIR Authentication and Authorisation
FHIR Authentication
The objective is to manage User authentication directly from the FHIR module. The JWT authentication mechanism is used. FHIR module is using the authentication services so the token can be used in both FHIR REST API and GraphQL queries.
...
1.4 openIMIS FHIR Quality Assurance
To come
1.5 openIMIS FHIR module documentation
...
openIMIS FHIR Quality Assurance
To come.
2 Packaging and Installation
2.1 Docker package improvement
Enhancement of openIMIS dockerization
...
For better distribution, docker can be used to facilitate the installation of openIMIS. The repository https://github.com/openimis/openimis-dist_dkr/tree/develop was updated to let users provide their own configuration using local files. Here For this, the user has to provide the normally called “openimis.json” openimis.json file locally using the appropriate environmental variable, two . Two files can be provided for the backend and frontend configuration (from the README.MD):
...
https://github.com/openimis/openimis-dist_dkr/blob/develop/README.md):
| Code Block |
|---|
BE_CONF_PATH=<the path to your config file, has to be local>
FE_CONF_PATH=<the path to your config file, has to be local> |
...
For even easier installation, the different repositories will be built on the fly directly from GitHub (repository previously provided), the . The user might can change the branch if need using the variables:
| Code Block |
|---|
BE_BRANCH=<branch of the backend repository to be used> FE_BRANCH=<branch of the frontend repository to be used> DB_BRANCH=<branch of the database repository to be used> GW_BRANCH=<branch of the gateway repository to be used> |
...
openIMIS integrated with Instant OpenHIE
A package to include not only openIMIS, but also services that could be required by an user, as e.g. a mediator (OpenHIM) or a FHIR server (Hapi), was developed. For this purpose, we extend the work of the OpenHIE, so called instant Instant OpenHIE (https://github.com/openhie/instant) to include openIMIS as a service (https://github.com/openimis/openimis-dist_instant_openhie/tree/develop).
There were To satisfy the Instant OpenHIE requirements, some alterations of the in the previous section mentioned repository to achieve thiswere necessary to the openIMIS docker package. The manual steps for the installation of the database were eliminated, so that the only command the user would be required to use requires is:
./deploy.sh init core openimis-db_dkr openimis-dist_dkr -c="./openimis-db_dkr" -c="./openimis-dist_dkr"
To clean up the project you'd use destroy instead of init. The commands up and down known from docker-compose are also allowed.
This is extendable by any service the user may want, given Given that the service is in a directory that follows instant Instant OpenHIE structure, and this implementation is extendable with any service the user may want by adding the package ID then to the previous command with the corresponding path.
The variables for both services are now in the docker/compose.sh files of each service as opposed of the .env file as in the previous repository.
...