I. Inventory and Documentation

Summary of tools/technologies used:

Database: PostgreSQL

Backend: Python, Django, graphQL

Frontend: React JS

Dockerized Exteranal Components:

• https://github.com/openimis/openimis-dist_dkr/tree/coremisSetup

• openFN lightning (GitHub - openimis/openimis-lightning_dkr: Dockerized instance of Lightning with demo workflow for openIMIS Individual ETL )

• OpenSearch

• OpenSearch Dashboards

Summary of the documentation:

Assembly Modules

• Backend Assembly: GitHub - openimis/openimis-be_py at coreMIS

• Frontend Assembly: GitHub - openimis/openimis-fe_js at coreMIS

CoreMIS Modules

Developers documentation:

Database

• GitHub - openimis/openimis-dist_dkr: The "all in one" packaged openIMIS (docker-compose) - PostgreSQL container (db)

Dockerized Distribution

• GitHub - openimis/openimis-dist_dkr: The "all in one" packaged openIMIS (docker-compose)

Documentation on Confluence page

• http://README.md sections of all modules presented in coreMIS package

• Developers documentation:

• Task based update - technical details (CORE-MIS) - tasks management module maker-checker logic

• Payment Funcionality migration strategy - payment modules design

• Module mapping module mapping

User guides

• User Guides (CORE-MIS modules):

II. Access Details

Transfer critical system/application logins.

a) coreMIS demo server - no production data

• URL https://coremis.s1.openimis.org/front/

• Login: Admin

• Password: admin123

b) coreMIS demo lightning credential - no production data

• URL https://coremis-etl.s1.openimis.org/users/log_in

• Login: IMISUser@openimis.com

• Password:  IMISUserPassword

c) OpenSearch Dashboard demo server

• coremis.s1.openimis.org/opensearch/

• NOTE: You have to log into openIMIS to access OpenSearch due to the nginx configuration.

Update access list post-handover.

• N/A

Ensure secure credential transfer.

• N/A

III. Ongoing tasks and responsibilities

List of the created but not addressed task is also available under this link https://openimis.atlassian.net/jira/software/projects/CM/boards/45/backlog

IV. Environment Details

Environments:

coreMIS demo server - no production data

• URL

• Login: Admin

• Password: admin123

coreMIS demo lightning credential - no production data

• URL https://coremis-etl.s1.openimis.org/users/log_in

• Login: IMISUser@openimis.com

• Password:  IMISUserPassword

OpenSearch Dashboard demo server

• coremis.s1.openimis.org/opensearch/

• NOTE: you have to log into openIMIS to access openSearch

Differences

Configuration of the social-proteciton page can be based on the coreMIS branches in assembly modules GitHub - openimis/openimis-be_py at coreMIS and GitHub - openimis/openimis-fe_js at coreMIS

The frontend has additional configurations that change the position of the menu and redirect links when clicking the help icon. Here https://github.com/openimis/openimis-fe-core_js#configurations-options you can find more details how to change it (menuLeft, redirectToCoreMISConfluenceUrl).

coreMIS frontend nginx.conf (openimis.conf) - here, there are additional directives for OpenSearch Dashboards.

Deployments

• In every module, there is a GitHub workflow (example: https://github.com/openimis/openimis-be-social_protection_py/blob/develop/.github/workflows/core-mis-test-server-deploy.yml ) to execute deployment to the test server once a PR is merged into the develop branch.

• You can manually rebuild it on the GitHub Actions page, as shown in the screenshot below (see bold 'CoreMIS Server Deployment job' option):

Access to server and release process

• The server is maintained by the SwissTPH team.

• The openIMIS has biannual releases, occurring in April and October each year

• The release process involves creating branches related to the release (release/<month-year>). Once all the necessary preparations are complete, this branch is merged into the main branch, and the packages for Python and React are created with the appropriate version tags.

• The team responsible for maintaining the project is in charge of handling the releases.

V. Feedback Mechanism

For any feedback or concerns, please contact our Project Manager Artur Lebiedziński via email at alebiedzinski@soldevelo.com . This ensures all feedback is tracked and addressed promptly.

VI. Data Models of Entities Relevant For the Project

Social Protection Module:

Open

Grievance Module:

Open

Individual Module:

OpenSearch Reports Module:

Payer Module:

Payment Cycle Module:

Payment Module:

Payroll Module:

Tasks Management Module:

Contribution Plan Module: