Release Notes

1. Dockerized: Fully dockerized version of Bahmni, to install and run Bahmni easily on an OS (Linux/Windows/Mac).
2. Cloud Ready: AWS & Kubernetes ready, with terraform automation to deploy Bahmni Lite v1.0.0 on the cloud, in a secure fashion. Read more here.
3. Security: Significant security upgrades and fixes! Also see the new Security Guide.
4. Lightweight: Contains Bahmni EMR (running on OpenMRS latest version 2.5.9), Reports, and Crater for billing & invoicing.
5. Pre-configured: Pre-configured with CIEL dictionary containing 50,000+ medical terms with SNOMED, LOINC and ICD-10 mappings, Clinical forms, India Essential Drug List and Reports, so that it is ready out-of-the-box for demos and requires minimal configuration to roll out.
6. Mobile Responsive: Bahmni EMR UI is now mobile responsive for the Clinical module, so clinicians on the move can use Bahmni from their mobile/tablets.
7. Lab Report Upload Module: Comprises a new Lab Report upload module (written in React). See screenshot here.
8. FHIR Support: Provides FHIR APIs to pull data from Bahmni / OpenMRS. Read more about Bahmni Interop support for Global standards here.
9. Tele-consultation support using Jitsi.
10. SMS / Whatsapp / Email support for sending prescriptions or informing patients about Appointments, etc.
11. Metabase: Comes out-of-box with Metabase analytics / reporting tool connected to OpenMRS DB and Mart DB (for easier report creation). Read more and see demo video here: Bahmni Metabase / Mart

Docker and docker compose needs to be installed for bahmni lite setup.  

For installing docker, docker compose and other docker commands please refer to Running Bahmni on Docker wiki page.

Installing Bahmni Lite using docker

git clone https://github.com/Bahmni/bahmni-docker.git && cd bahmni-docker
git checkout tags/1.0.0-lite
cd bahmni-lite
# Using docker compose
docker compose --profile bahmni-lite up -d
# Or use the bash script
./run-bahmni.sh

As Bahmni docker ships with default credentials, make sure that these are changed to ensure Bahmni setup is safe. Refer to the steps involved here.

To be noted that Bahmni comes with an out-of-the-box demo database. The demo database contains a location (Bahmni Clinic) and with some users created for login. One can also perform an installation with a fresh schema. Refer to this document. Also you can run your own version of Bahmni-Config by following the steps mentioned here.

This release includes fixing the vulnerabilities with struts-core.jar dependency

Please see system requirements here

Before you go through the installation process, please upgrade "zlib" packages. 

$ yum install -y https://kojipkgs.fedoraproject.org//packages/zlib/1.2.11/19.fc30/x86_64/zlib-1.2.11-19.fc30.x86_64.rpm

Please refer to the documentation on Installation, Upgrade and/or Advanced Installation for version 0.93

Please also refer Installing and Configuring Bahmni Connect for Bahmni Connect Setup

You can refer to All Releases page for further details on RPM versions

Briefly:

# install dependencies
> yum install -y https://kojipkgs.fedoraproject.org//packages/zlib/1.2.11/19.fc30/x86_64/zlib-1.2.11-19.fc30.x86_64.rpm

> yum install -y epel-release

> pip install --upgrade pip

> pip install babel==v1.0 python-stdnum urllib3==1.21.1 idna==2.5 chardet==3.0.2 certifi==2017.4.17 qrcode pyserial pypdf python-chart psycogreen passlib ofxparse requests

# install bahmni command line installer
> yum install -y https://repo.mybahmni.org/releases/bahmni-installer-0.93-219.noarch.rpm


# download the postgres repo rpm. 
> rm -f /opt/pgdg-redhat-repo-*

> cd /opt && wget https://yum.postgresql.org/common/redhat/rhel-7-x86_64/pgdg-redhat-repo-42.0-23.noarch.rpm --no-check-certificate

# if the filee /etc/bahmni-installer/setup.yml is not there, you can get a sample
> curl -L https://tinyurl.com/yyoj98df >> /etc/bahmni-installer/setup.yml

# configure your implementation specific settings, set repo URL
> vi /etc/bahmni-installer/setup.yml

# configure components you require
> vi /etc/bahmni-installer/local

# run the installer
> bahmni -i local install

1. Rebuild Search Index: It's required to rebuild search indexes from the OpenMRS UI. Without this, Patient, Drug and Concept searches won't work in Bahmni or OpenMRS. Please rebuild the indexes post install/upgrade: OpenMRS => Navigate to Administration => Search Index => Run Rebuild Search Index.
2. Duplicate Scheduler Tasks: We have noticed that there are sometimes duplicate schedulers for OpenElis Patient Atom Feed Task and OpenMRS event publisher Task running. Having such duplicate entries relevant to Feed and Events can result in unforeseen and unpredictable synchronization issues between components of Bahmni. This was fixed as part of Bahmni-0.91 release for the default demo and clean databases. However, existing installations trying to upgrade Bahmni should manually delete the entries from database. You can do this either from OpenMRS Administration console or updating database directly. You can verify by running this SQL on mysql “openmrs” database.

   select schedulable_class, count(*) from scheduler_task_config group by schedulable_class;

   If any of the rows, show as more than 1, then you should delete the duplicate entries to ensure only one scheduler job exists and is being run.

3. Tag a Location with ‘Operation Theatre’ : To create a surgical block in OT scheduling module, we should have at least one location tagged as "Operation Theatre". If you are not using default config, or have forked from default config previously, you must tag your OT location with ‘Operation Theatre’ tag. Without this setup, OT scheduling app will throw an error.
4. Oviyam Viewer URL : You may need to update the configuration for Oviyam DICOM viewer URL in app config for clinical dashboard, if you are migrating from older version. Please edit file /var/www/bahmni_config/openmrs/apps/clinical/dashboard.json for the “pacsImageUrl” attribute like in the example here.
5. Odoo Setup: If you are going to use Billing/Pharmacy/Inventory functions from ERP, you need to configure Odoo for your requirements appropriately. Please see WIKI documentation for guide. 
6. Odoo - Undefined period error during quotation confirmation : While confirming a quotation, if there is no period defined an error is thrown "There is no Period defined". While this has been fixed for 2018 with the default ERP database, if you are going to be installing in 2021, you may still face this error. 
   Workaround:  Please follow the steps as mentioned in this page -  OpenERP error "There is no period defined" while confirming a sale quotation 
7. Change default passwords: You should change the user passwords for OpenMRS (superman, admin), OpenELIS (admin), Odoo (admin),  Dcm4Chee (admin)

Information don’t sync to Odoo, or published lab results don’t sync to OpenMRS: We have noticed that sometimes post installation (with bahmi-lab, bahmni-erp-connect services running) information don’t sync to Odoo (from OpenMRS) or to OpenMRS (from lab), while the front end applications seem to be working fine. If you would check the log files, you will probably see connection lost, or C3PO connection pool errors. Restarting the services seem to resolve the errors. 

> systemctl restart bahmni-erp-connect

> systemctl restart bahmni-lab

systemctl commands throwing error: 

Authorization not available. Check if polkit service is running or see debug message for more information. Failed to restart odoo.service: Connection timed out
See system logs and ‘systemctl status odoo.service’ for details.

We have noticed this error coming up infrequently. Follow the instructions provided below for resolution

https://access.redhat.com/solutions/1543343

running services in debug mode:

• If you want to run a particular service in debug mode, you can still continue to use the “service <bahmni service-name> debug” command. However, few things you need to keep in mind
• Always run the service in debug mode, as root user. 
• After stopping the service, ensure that you delete the /var/run/<bahmni-service-name> and /var/log/<bahmni-service-name> directories. 

generate "LetsEncrypt" certs:

• If you want to generate “LetsEncypt” certs from the same server machine, you will have to manually install zlib-devel package. Please see this thread for information

Can not start opnmrs service using "systemctl": 

• Openmrs service fails to start with “systemctl start openmrs” after the usage of “service openmrs start”: 
  
  1. mv /opt/openmrs/log /opt/openmrs/log-backup
  2. rm /var/log/openmrs (without ‘/’ at the end, we want to remove only the symlink)
  3. rm /var/run/openmrs (without ‘/’ at the end, we want to remove only the symlink)
  4. mkdir /opt/openmrs/log
  5. chown bahmni:bahmni /opt/openmrs/log
  6. ln -s /opt/openmrs/log /var/log/openmrs
  7. chown -R bahmni:bahmni /var/log/openmrs

Redirecting service commands to systemctl:

• With the release of Bahmni version 0.92, Bahmni’s services uses systemd unit files as opposed to the older init.d files. Using service commands to start/stop Bahmni services are not supported and only systemcl commands are advised. To prevent use of “service” command, we can run the optional step below that sets up a “service” function to redirect service command to call “systemctl” instead:

  1. vi ~/.bash_profile
  2. Add the following line:
  
  service() { local first=$1; local second=$2; echo “Redirecting to systemctl from Bahmni, to unset this run ‘unset -f service’“; systemctl $second $first;}
  
  3. Save and close the file
  4. source ~/.bash_profile

  To remove the above function, modify the same file and remove the service function.

1. Patient Identifier Extension : registration module now allows for lookup and association of other system identifiers (eg Interacing with a National ID system) by means of custom extension.

This release includes an up-gradation of the log4j version to the latest (2.17.1) to overcome the vulnerabilities, please refer to the below talk thread for more details, https://talk.openmrs.org/t/log4j-security-vulnerability-impact-on-bahmni-cve-2021-44228/35367

Please see system requirements here

Before you go through the installation process, please upgrade "zlib" packages. 

$ yum install -y https://kojipkgs.fedoraproject.org//packages/zlib/1.2.11/19.fc30/x86_64/zlib-1.2.11-19.fc30.x86_64.rpm

Please refer to the documentation on Installation, Upgrade and/or Advanced Installation for version 0.93

Please also refer Installing and Configuring Bahmni Connect for Bahmni Connect Setup

You can refer to All Releases page for further details on RPM versions

Briefly:

# install dependencies
> yum install -y https://kojipkgs.fedoraproject.org//packages/zlib/1.2.11/19.fc30/x86_64/zlib-1.2.11-19.fc30.x86_64.rpm

> yum install -y epel-release


# install bahmni command line installer
yum install -y https://repo.mybahmni.org/releases/bahmni-installer-0.93-215.noarch.rpm



# download the postgres repo rpm. 
> rm -f /opt/pgdg-redhat-repo-latest.noarch.rpm
> rm -f /opt/pgdg-redhat-repo-42.0-23.noarch.rpm
> cd /opt && wget https://yum.postgresql.org/common/redhat/rhel-7-x86_64/pgdg-redhat-repo-42.0-23.noarch.rpm --no-check-certificate

# if the filee /etc/bahmni-installer/setup.yml is not there, you can get a sample
> curl -L https://tinyurl.com/yyoj98df >> /etc/bahmni-installer/setup.yml

# configure your implementation specific settings, set repo URL
> vi /etc/bahmni-installer/setup.yml

# configure components you require
> vi /etc/bahmni-installer/local

# run the installer
> bahmni -i local install

1. Rebuild Search Index: It's required to rebuild search indexes from the OpenMRS UI. Without this, Patient, Drug and Concept searches won't work in Bahmni or OpenMRS. Please rebuild the indexes post install/upgrade: OpenMRS => Navigate to Administration => Search Index => Run Rebuild Search Index.
2. Duplicate Scheduler Tasks: We have noticed that there are sometimes duplicate schedulers for OpenElis Patient Atom Feed Task and OpenMRS event publisher Task running. Having such duplicate entries relevant to Feed and Events can result in unforeseen and unpredictable synchronization issues between components of Bahmni. This was fixed as part of Bahmni-0.91 release for the default demo and clean databases. However, existing installations trying to upgrade Bahmni should manually delete the entries from database. You can do this either from OpenMRS Administration console or updating database directly. You can verify by running this SQL on mysql “openmrs” database.

   select schedulable_class, count(*) from scheduler_task_config group by schedulable_class;

   If any of the rows, show as more than 1, then you should delete the duplicate entries to ensure only one scheduler job exists and is being run.

3. Tag a Location with ‘Operation Theatre’ : To create a surgical block in OT scheduling module, we should have at least one location tagged as "Operation Theatre". If you are not using default config, or have forked from default config previously, you must tag your OT location with ‘Operation Theatre’ tag. Without this setup, OT scheduling app will throw an error.
4. Oviyam Viewer URL : You may need to update the configuration for Oviyam DICOM viewer URL in app config for clinical dashboard, if you are migrating from older version. Please edit file /var/www/bahmni_config/openmrs/apps/clinical/dashboard.json for the “pacsImageUrl” attribute like in the example here.
5. Odoo Setup: If you are going to use Billing/Pharmacy/Inventory functions from ERP, you need to configure Odoo for your requirements appropriately. Please see WIKI documentation for guide. 
6. Odoo - Undefined period error during quotation confirmation : While confirming a quotation, if there is no period defined an error is thrown "There is no Period defined". While this has been fixed for 2018 with the default ERP database, if you are going to be installing in 2021, you may still face this error. 
   Workaround:  Please follow the steps as mentioned in this page -  OpenERP error "There is no period defined" while confirming a sale quotation 
7. Change default passwords: You should change the user passwords for OpenMRS (superman, admin), OpenELIS (admin), Odoo (admin),  Dcm4Chee (admin)

Information don’t sync to Odoo, or published lab results don’t sync to OpenMRS: We have noticed that sometimes post installation (with bahmi-lab, bahmni-erp-connect services running) information don’t sync to Odoo (from OpenMRS) or to OpenMRS (from lab), while the front end applications seem to be working fine. If you would check the log files, you will probably see connection lost, or C3PO connection pool errors. Restarting the services seem to resolve the errors. 

> systemctl restart bahmni-erp-connect

> systemctl restart bahmni-lab

systemctl commands throwing error: 

Authorization not available. Check if polkit service is running or see debug message for more information. Failed to restart odoo.service: Connection timed out
See system logs and ‘systemctl status odoo.service’ for details.

We have noticed this error coming up infrequently. Follow the instructions provided below for resolution

https://access.redhat.com/solutions/1543343

running services in debug mode:

• If you want to run a particular service in debug mode, you can still continue to use the “service <bahmni service-name> debug” command. However, few things you need to keep in mind
• Always run the service in debug mode, as root user. 
• After stopping the service, ensure that you delete the /var/run/<bahmni-service-name> and /var/log/<bahmni-service-name> directories. 

generate "LetsEncrypt" certs:

• If you want to generate “LetsEncypt” certs from the same server machine, you will have to manually install zlib-devel package. Please see this thread for information

Can not start opnmrs service using "systemctl": 

• Openmrs service fails to start with “systemctl start openmrs” after the usage of “service openmrs start”: 
  
  1. mv /opt/openmrs/log /opt/openmrs/log-backup
  2. rm /var/log/openmrs (without ‘/’ at the end, we want to remove only the symlink)
  3. rm /var/run/openmrs (without ‘/’ at the end, we want to remove only the symlink)
  4. mkdir /opt/openmrs/log
  5. chown bahmni:bahmni /opt/openmrs/log
  6. ln -s /opt/openmrs/log /var/log/openmrs
  7. chown -R bahmni:bahmni /var/log/openmrs

Redirecting service commands to systemctl:

• With the release of Bahmni version 0.92, Bahmni’s services uses systemd unit files as opposed to the older init.d files. Using service commands to start/stop Bahmni services are not supported and only systemcl commands are advised. To prevent use of “service” command, we can run the optional step below that sets up a “service” function to redirect service command to call “systemctl” instead:

  1. vi ~/.bash_profile
  2. Add the following line:
  
  service() { local first=$1; local second=$2; echo “Redirecting to systemctl from Bahmni, to unset this run ‘unset -f service’“; systemctl $second $first;}
  
  3. Save and close the file
  4. source ~/.bash_profile

  To remove the above function, modify the same file and remove the service function.

1. Localization - While Bahmni was designed for internationalization, there remain certain gaps and challenges towards completely localizing a specific Bahmni implementation. In this release, gaps primarily in Registration and Clinical modules have been fixed. For concepts, if you have the metadata properly set up for other languages, it would reflect so once you have logged on to a specific locale.
2. Appointment module - new features include ability to schedule for multiple providers for an appointment, conflict management for patients and services, ability to schedule recurring appointments etc
3. Forms 2 - Forms now have additional events like onSave which allows you to do validation at form level. Form builder UI now provides a JavaScript editor with basic validations, help etc. It also provides a “preview” mode to test out your form and its behavior. Also a new table control has been introduced.
4. Access Control - Reports and forms can now be made accessible to users with specified privileges.
5. OT Scheduling - Weekly view is now provided for OT schedules.
6. Additional orderables -  you may mark a concept as “sellable” and configure such concepts in the orders tab, so that on order they appear on Odoo quotations. For example - procedures, counselling, physiotherapy etc
7. Lab Improvements - result entry for referred out tests can be marked as done, test status configuration, test method management, sample printout with barcode,  
8. Security Improvements - security enhancements towards XSS, CSRF, Domain whitelisting, Injections Attacks etc
9. Teleconsultation - (Preview feature only) - It's also possible to schedule a tele consultation appointment, built on top of Jitsi, allowing Doctor-patient interactions over video. Note, while the teleconsultation feature is fully functional, there are some missing features you should be aware of before using on production.
10. Oviyam Viewer Upgrade - Oviyam Dicom Viewer has been upgraded to v.2.8.1.

This release includes a preview of a new feature that we expect to officially include in the Bahmni 0.94 release. There is no official support for these previews, and no guarantee that configurations created now will be compatible with the official release.

Teleconsultation: With this release, it's possible to schedule a tele consultation appointment. Note, while the teleconsultation feature is fully functional, there are some missing features you should be aware of before using on production.

1. Bahmni-mart : A simplified database used for analytics wherein hierarchical structures have been flattened and pivoted and many other entities denormalized. You may plugin data visualization tools Metabase, Superset etc on top of this database. NOTE: Bahmni-mart is not part of the default distribution and packaging of Bahmni 0.93. Please follow the steps here if you would like to try this out. 
2. Integration with OpenMRS Reporting : This Open Web App (OWA) is useful to execute Reports defined in the OpenMRS reporting module.  Please see here for documentation

Please see system requirements here

Before you go through the installation process, please upgrade "zlib" packages. 

$ yum install -y https://kojipkgs.fedoraproject.org//packages/zlib/1.2.11/19.fc30/x86_64/zlib-1.2.11-19.fc30.x86_64.rpm

Please refer to the documentation on Installation, Upgrade and/or Advanced Installation for version 0.93

Please also refer Installing and Configuring Bahmni Connect for Bahmni Connect Setup

You can refer to All Releases page for further details on RPM versions

Briefly:

# install dependencies
> yum install -y https://kojipkgs.fedoraproject.org//packages/zlib/1.2.11/19.fc30/x86_64/zlib-1.2.11-19.fc30.x86_64.rpm

> yum install -y epel-release


# install bahmni command line installer
yum install -y https://repo.mybahmni.org/releases/bahmni-installer-0.93-197.noarch.rpm



# download the postgres repo rpm. 
> rm -f /opt/pgdg-redhat-repo-latest.noarch.rpm
> curl https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/pgdg-redhat-repo-latest.noarch.rpm --output /opt/pgdg-redhat-repo-latest.noarch.rpm


# if the filee /etc/bahmni-installer/setup.yml is not there, you can get a sample
> curl -L https://tinyurl.com/yyoj98df >> /etc/bahmni-installer/setup.yml

# configure your implementation specific settings, set repo URL
> vi /etc/bahmni-installer/setup.yml

# configure components you require
> vi /etc/bahmni-installer/local

# run the installer
> bahmni -i local install

1. Rebuild Search Index: It's required to rebuild search indexes from the OpenMRS UI. Without this, Patient, Drug and Concept searches won't work in Bahmni or OpenMRS. Please rebuild the indexes post install/upgrade: OpenMRS => Navigate to Administration => Search Index => Run Rebuild Search Index.
2. Duplicate Scheduler Tasks: We have noticed that there are sometimes duplicate schedulers for OpenElis Patient Atom Feed Task and OpenMRS event publisher Task running. Having such duplicate entries relevant to Feed and Events can result in unforeseen and unpredictable synchronization issues between components of Bahmni. This was fixed as part of Bahmni-0.91 release for the default demo and clean databases. However, existing installations trying to upgrade Bahmni should manually delete the entries from database. You can do this either from OpenMRS Administration console or updating database directly. You can verify by running this SQL on mysql “openmrs” database.

   select schedulable_class, count(*) from scheduler_task_config group by schedulable_class;

   If any of the rows, show as more than 1, then you should delete the duplicate entries to ensure only one scheduler job exists and is being run.

3. Tag a Location with ‘Operation Theatre’ : To create a surgical block in OT scheduling module, we should have at least one location tagged as "Operation Theatre". If you are not using default config, or have forked from default config previously, you must tag your OT location with ‘Operation Theatre’ tag. Without this setup, OT scheduling app will throw an error.
4. Oviyam Viewer URL : You may need to update the configuration for Oviyam DICOM viewer URL in app config for clinical dashboard, if you are migrating from older version. Please edit file /var/www/bahmni_config/openmrs/apps/clinical/dashboard.json for the “pacsImageUrl” attribute like in the example here.
5. Odoo Setup: If you are going to use Billing/Pharmacy/Inventory functions from ERP, you need to configure Odoo for your requirements appropriately. Please see WIKI documentation for guide. 
6. Odoo - Undefined period error during quotation confirmation : While confirming a quotation, if there is no period defined an error is thrown "There is no Period defined". While this has been fixed for 2018 with the default ERP database, if you are going to be installing in 2021, you may still face this error. 
   Workaround:  Please follow the steps as mentioned in this page -  OpenERP error "There is no period defined" while confirming a sale quotation 
7. Change default passwords: You should change the user passwords for OpenMRS (superman, admin), OpenELIS (admin), Odoo (admin),  Dcm4Chee (admin)

Information don’t sync to Odoo, or published lab results don’t sync to OpenMRS: We have noticed that sometimes post installation (with bahmi-lab, bahmni-erp-connect services running) information don’t sync to Odoo (from OpenMRS) or to OpenMRS (from lab), while the front end applications seem to be working fine. If you would check the log files, you will probably see connection lost, or C3PO connection pool errors. Restarting the services seem to resolve the errors. 

> systemctl restart bahmni-erp-connect

> systemctl restart bahmni-lab

systemctl commands throwing error: 

Authorization not available. Check if polkit service is running or see debug message for more information. Failed to restart odoo.service: Connection timed out
See system logs and ‘systemctl status odoo.service’ for details.

We have noticed this error coming up infrequently. Follow the instructions provided below for resolution

https://access.redhat.com/solutions/1543343

running services in debug mode:

• If you want to run a particular service in debug mode, you can still continue to use the “service <bahmni service-name> debug” command. However, few things you need to keep in mind
• Always run the service in debug mode, as root user. 
• After stopping the service, ensure that you delete the /var/run/<bahmni-service-name> and /var/log/<bahmni-service-name> directories. 

generate "LetsEncrypt" certs:

• If you want to generate “LetsEncypt” certs from the same server machine, you will have to manually install zlib-devel package. Please see this thread for information

Can not start opnmrs service using "systemctl": 

• Openmrs service fails to start with “systemctl start openmrs” after the usage of “service openmrs start”: 
  
  1. mv /opt/openmrs/log /opt/openmrs/log-backup
  2. rm /var/log/openmrs (without ‘/’ at the end, we want to remove only the symlink)
  3. rm /var/run/openmrs (without ‘/’ at the end, we want to remove only the symlink)
  4. mkdir /opt/openmrs/log
  5. chown bahmni:bahmni /opt/openmrs/log
  6. ln -s /opt/openmrs/log /var/log/openmrs
  7. chown -R bahmni:bahmni /var/log/openmrs

Redirecting service commands to systemctl:

• With the release of Bahmni version 0.92, Bahmni’s services uses systemd unit files as opposed to the older init.d files. Using service commands to start/stop Bahmni services are not supported and only systemcl commands are advised. To prevent use of “service” command, we can run the optional step below that sets up a “service” function to redirect service command to call “systemctl” instead:

  1. vi ~/.bash_profile
  2. Add the following line:
  
  service() { local first=$1; local second=$2; echo “Redirecting to systemctl from Bahmni, to unset this run ‘unset -f service’“; systemctl $second $first;}
  
  3. Save and close the file
  4. source ~/.bash_profile

  To remove the above function, modify the same file and remove the service function.

BAH-1051 Add support to MySql 5.6 for bahmni installation 0.92

BAH-1037 Installation of Bahmni 0.92, fails because of non- availability of postgres rpm

BAH-1038 Installation of Bahmni 0.92, fails because of non-availability of ansible

BAH-1049 Not able to start Odoo after bahmni installation 0.92

Please see system requirements here

Before you go through the installation process, please upgrade "zlib" packages. 

$ yum install -y https://kojipkgs.fedoraproject.org//packages/zlib/1.2.11/19.fc30/x86_64/zlib-1.2.11-19.fc30.x86_64.rpm
$ sudo yum install epel-release
$ sudo yum install python-pip
$ sudo pip install pip==v19.0
$ sudo uninstall click
$ sudo pip install click==v7.0
$ sudo pip install pyusb
$ sudo pip install babel==v0.9.6
$ sudo pip install decorator==v3.4.0
$ sudo pip install beautifulsoup4

Please refer to the documentation on Installation, Upgrade and/or Advanced Installation for version 0.92

Please also refer Installing and Configuring Bahmni Connect for Bahmni Connect Setup

You can refer to All Releases page for further details on RPM versions

Rebuild Search Index: It's mandatory to rebuild search indexes from the OpenMRS UI. Without this, Patient, Drug and Concept searches won't work in Bahmni or OpenMRS. Please rebuild the indexes post install/upgrade: OpenMRS => Navigate to Administration => Search Index => Run Rebuild Search Index. 

Duplicate Scheduler Tasks: We have noticed that there are sometimes duplicate schedulers for OpenElis Patient Atom Feed Task and OpenMRS event publisher Task running. Having such duplicate entries relevant to Feed and Events can result in unforeseen and unpredictable synchronization issues between components of Bahmni. This is fixed as part of latest Bahmni-0.91 release for the default demo and clean databases. However, existing installations trying to upgrade Bahmni should manually delete the entries from database. You can do this either from OpenMRS Administration console or updating database directly. You can verify by running this SQL on mysql “openmrs” database.

select schedulable_class, count(*) from scheduler_task_config group by schedulable_class;

If any of the rows, show as more than 1, then you should delete the duplicate entries to ensure only one scheduler job exists and is being run.

Tag a Location with ‘Operation Theatre’ : To create a surgical block in OT scheduling module, we should have at least one location tagged as "Operation Theatre". If you are not using default config, or have forked from default config previously, you must tag your OT location with ‘Operation Theatre’ tag. Without this setup, OT scheduling app will throw an error.

Odoo Setup: If you are going to use Billing/Pharmacy/Inventory functions from ERP, you need to configure Odoo for your requirements appropriately. Please see WIKI documentation for guide.

Change default passwords: You should change the user passwords for OpenMRS (superman, admin), OpenELIS (admin), Odoo (admin),  Dcm4Chee (admin)

MySQL admin password: From 0.92, we are using MySQL version 5.7, and the password policy is stricter and set to MEDIUM, which is a combination of “Length; numeric, lowercase/uppercase, and special characters”. If you are changing the admin user (root) password, you need to set password appropriately. Check MySQL documentation here for more information.

Ansible preferred version: Default ansible version supported is 2.4.6. Bahmni command line option -aru has been reintroduced to enable users to provide repo-url of ansible package (incase of non availability of ansible package) while installing Bahmni.

MySQL version configuration: Default MySQL version supported is 5.7.30. A new configuration parameter mysql_version has been introduced to override MySQL version.

Information don’t sync to Odoo, or published lab results don’t sync to OpenMRS: We have noticed that sometimes post installation (with bahmi-lab, bahmni-erp-connect services running) information don’t sync to Odoo (from OpenMRS) or to OpenMRS (from lab), while the front end applications seem to be working fine. If you would check the log files, you will probably see connection lost, or C3PO connection pool errors. Restarting the services seem to resolve the errors. 

> systemctl restart bahmni-erp-connect

> systemctl restart bahmni-lab

systemctl commands throwing error: 

Authorization not available. Check if polkit service is running or see debug message for more information. Failed to restart odoo.service: Connection timed out
See system logs and ‘systemctl status odoo.service’ for details.

We have noticed this error coming up infrequently. Follow the instructions provided below for resolution

https://access.redhat.com/solutions/1543343

running services in debug mode:

• If you want to run a particular service in debug mode, you can still continue to use the “service <bahmni service-name> debug” command. However, few things you need to keep in mind
• Always run the service in debug mode, as root user. 
• After stopping the service, ensure that you delete the /var/run/<bahmni-service-name> and /var/log/<bahmni-service-name> directories. 

generate "LetsEncrypt" certs:

• If you want to generate “LetsEncypt” certs from the same server machine, you will have to manually install zlib-devel package. Please see this thread for information