Problem statement: 

Currently, Bahmni can be installed and configured for a hospital one at a time.  

• This installation involves numerous manual steps, which lead to error prone installations. 

• Besides being a time consuming installation, the Bahmni installations depend on a specific operation system (Cento OS).  

• Also, the scaling support based on services is not available for Bahmni installations. 

Technical approach: 

The Bahmni deployment involves setting up software in CentOS machines - for which currently dockerization support is being added. To add to that, we would like to create Kubernetes pods so that Bahmni can be scaled at component level based on the specific use case. The various steps involved are 

1. Each instance of Bahmini will be deployed in a namespace in Kubernetes.  

2. Each namespace will consist of the following components 

• Bahmani web  

• OpenMRS(Tomcat)  

• OpenElis(Tomcat)  

• OpenMRS(MySQL)  

• Odoo(Python)  

• Odoo-connect  

• DCM4CHEE(Jboss)  

• OpenElis(Postgres) /DCM4CHEE(Postgres)/Odoo(Postgres) 

3. Following components will be a stateful deployment since the data needs to be persisted  

•   openelisdbdata  

•   odoodbdata  

•   odooappdata  

•   openmrs-data  

•   openmrsdbdata  

4. Kubernetes deployment yaml along with service for OCL in a common namespace will be created. This will be used by all the Bahmani instances.  

5. LoadBalancer will be created using the Kubernetes service object and will point to the Bahmni web pod.  

Tasks required (To be achieved) 

• Creation of helm chart for Bahmini and deployment file for OCL  

• Pipeline for building of the docker images 

• Setup of monitoring and logging 

• Pipeline for deploying the helm chart and OCL  

 Monitoring and Evaluation approach: 

We propose to follow the Agile development model with 2-week sprints, with daily stand-ups. A project management tool like Trello or JIRA would be used to assign work to the team and track progress. A status report will be published to the Digital Square team before the monthly sync-up (proposed) to set the agenda for the call. It will contain the following information:  

• Activities completed during the reporting period / planned during the reporting period but not completed (Slipped activities will be reported in bold).  

• Activities scheduled for the next reporting period.  

• Blockers, dependencies, and queries.  

• Cumulative progress report for the sprint.  

The diagram given below explains the model at a very high level.  

 Project Deliverables 

BeeHyv will provide the following deliverables: code and documentation detailing the tasks accomplished to achieve the codes. 

 The status and outputs of the deliverables will be provided in the following reports 

1. Regular Status reports - These reports will document updates of the activity plans to be submitted regularly at agreed-upon intervals.  

2. Interim report - This report will have a summary of the project and a brief description of the progress at an agreed-upon interval through the project execution. 

3. Final project report - This report will provide a detailed description of the final results of the project and will be presented during the closure of the project. 

Project Gantt Chart  

  

Risk Mitigation: 

It is critical that the scenarios for all implementations are considered while designing the solution and any failure in this regard will lead to adoption risks. To mitigate this risk, we plan to have periodic discussions with the Bahmni coalition and incorporate their inputs into the solution development process.