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

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

BAH-939 Bahmni installation fails due to upgraded systemd

BAH-956 Ward list layout is not seen in In-Patient module

BAH-958 ODOO Receipt printing of Partial Payment

BAH-978 ERP feed service fails because of missing dependencies

BAH-965 Refund of discounted invoice does not consider the discount

Operation System - CentOS 7.5, 7.6 and 7.7. We would advise starting with a "minimal" distro. 

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.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.

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

BAH-772 - Enhancement of Patient Queues/List

BAH-705 - Validate backup and restore mechanism on Centos 7

BAH-840 - Upgrade implementer-interface dependencies

BAH-847 - "Default" implementation installation shows an existing customer and an order associated 

BAH-487/BAH-632 - Upgrade Apache Httpd to v2.4

BAH-487/BAH-633 - Upgrade Postgresql to v9.6

BAH-487/BAH-630 - Upgrade MySQL to 5.7

BAH-736 - Update API url for 2FA plugin bahmni-sms-plugin 

BAH-775 - Patient document - Viewing patient images requires scrolling

BAH-763 - “bahmni-erp-connect” application properties not getting overridden by system or env properties. 

BAH-738 - Camera not working after chrome upgrade

BAH-661 - Not possible to create Bed Layout without mentioning all bed details

BAH-844 - Bahmni-erp-connect: Integration between MRS-ERP fails if Lab Component is not installed

BAH-648 - Atomfeed Console API leaks out internal system credentials 

BAH-780 - Pip upgrade during bahmni-installer re-run fails

BAH-726 - Auto upgrade Bahmni emr

BAH-383 - Bahmni Installer needs python “ez_setup” dependency to be installed first

BAH-626 - Ward Management Admin Console does not work if there are too many locations to load    

BAH-774 - bahmni install-certs command failing because of the old agreement file

BAH-664 - Missing privileges for Bed Management

BAH-814 - Non-default configuration install results in missing scheduler entries

BAH-845 - Liquibase precondition fails for openerp-atomfeed-service because of missing table "event_records”

BAH-851 - Lab Results do not appear on Bahmni Clinical (e.g. Dashboards) against the order 

BAH-870 - Change URL for Radiology in Bahmni Landing Page

Operation System - CentOS 7.5, 7.6. We would advise starting with a "minimal" distro. 

Please see system requirements here

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

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

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.

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. 

> service bahmni-erp-connect restart

> service bahmni-lab restart

service or 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

BAH-772 Enhancing Performance of Program queues with debouncing.

BAH-661 - Unable to set a layout in ward management admin console

BAH-738 - Camera is not working on the registration page with latest Chrome browser

BAH 763 -  bahmni-erp-connect application properties not getting overridden by system or env properties

BAH-578 -  [0.91 bug bash] Do not mandate to enter "0" in the "Age" field when "month" or "days" field has data

BAH-758 -  Upgrade WebServices REST Module to 2.24

BAH-771 -  [Appt. Scheduling] Appointment Times Problem

BAH-775 -  Patient document - Viewing patient images requires scrolling

BAH-626 -  Ward Management Admin Console does not work if the number of locations are a lot

BAH-648 -  Atomfeed Console api is compromised

BAH-664 -  Add missing privileges for Bed Management

BAH-785 -  Implementer interface, bahmniapps has latest bahmni-form-controls npm version

BAH-787 -  Change the java version from jre1.8.0_101 to jre1.8.0_131 in Bahmni-Package

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

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.

BAH-310 - Enhancements to Diagnosis Search. You can search Diagnosis by a code if you have mapped your diagnosis concepts to a coding system like ICD10 or SNOMED. See here for details.

BAH-399 - Ability to search patient relationship by name

BAH-404 - Only providers marked for “Available for Appointments” should be listed  while creating appointment.

BAH-491 - Display of Units for lab tests in Investigation chart, Lab Results details

BAH-497 - Prompt while navigating away from Patient Registration

BAH-511 - Navigation configuration for “Go to IPD Dashboard”

BAH-414 - Display section names in OpenELIS dashboards for “Samples to collect” and  “Samples collected” queue for “Today” and “Backlog”

BAH-567 - Bahmni Reports Integration with Bahmni-mart

BAH-608 - Enable concatenated reports for Bahmni-mart reports

BAH-598 - Feed Events for BM tags

BAH-314 - Enable Bahmni Apps Reports app to handle 'date range' reports from the Reporting module

BAH-403 - Ability to upload Concepts in CSV files with specified UUID

BAH-447 - Hide empty empty rows and columns in obs-to-obs-flow-sheet control

BAH-385 - internationalization gaps in modules - admin, adt, appointments, clinical, messages, Forms 1.0, display controls, patient search, registration, document upload, home screen, orders, reports

BAH-387 - Inpatient report with diagnosis - Diagnosis made during course of admission, should show up in inpatient report

BAH-341 - Unable to stop/discontinue a drug with current date as the stop date for a drug started in past encounter.

BAH-398 - Unexpected token in JSON when login is done from login screen for an invalidated user session.

BAH-311 - internationalization gaps have been fixed in “Observation Graph”, Diagnosis tab, treatment tab, drug order history, registration page.

BAH-376 - Patient Identifier prefix with NULL should not be shown in registration

BAH-382 - Audit Log tables headers are hardcoded to english

BAH-407 - Bottom banner shrinks on responsive screens

BAH-415, BAH-490 - Forms 1.0, conceptSetUI based forms with mandatory boolean concepts throw error on save.

BAH-426 - Appointments List View should wrap texts to display texts appropriately

BAH-435 - Date picker date in appointment list/calendar view can be cleared with the delete button

BAH-439 - Registration search page displays Attributes which are concepts as numbers

BAH-446 - Forms 1.0, conceptSetUI based forms with Image marked as mandatory throws error on save

BAH-451 - Patient assignment to bed fails for event errors

BAH-453 - During bahmni-connect installation, offline-config from default-config repo should be copied to bahmni_config folder.

BAH-456 - Truncate audit log on fresh install with default demo database

BAH-459 - Slow performance in Appointment Scheduling module

BAH-461 - Special characters (e.g è) are not shown property in reports

BAH-462 - Should not call API to fetch appointments while shifting views list ⇔ calendar

BAH-463 - Memory leak when uploading videos

BAH-465 - Patient Document Upload should allow specific file types

BAH-469 - Adding 2018 as accounting fiscal year in ERP default database.

BAH-470 - OpenELIS lab dashboard searches not working in ‘Samples to Collect => backlog’ for ‘Source’.

BAH-482 - Appropriate error message for date validation

BAH-498 - Order of tests in results page and validation page is different

BAH-510 - Program Context is being lost during navigation resulting the data captured not being in program context

BAH-512 - Disposition type dropdown shows empty lines when standard dispositions like 'Admit Patient', 'Discharge Patient', 'Transfer Disposition' are removed.

BAH-514 - Data captured through Forms2.0 in Bahmni Connect are lost if and when a form data is edited offline.

BAH-495 - Scroll issues in Lab Investigation chart

BAH-522 - Blocked Admin action to clear out ELIS database

BAH-523 - OpenELIS LoginList page shows the user's passwords in clear text

BAH-524 - Unable to view audit log messages even with required privileges

BAH-526 - Duplicate appointments while editing an appointment in operation theatre module

BAH-528, BAH-537 - Error is thrown when deselecting concepts in a form with multiple levels of form conditions

BAH-529 - Program state change throws error if date of enrollment is passed with time details

BAH-531 - Missing foreign key constraint in bed_location_map table

BAH-550 - Filter duplicates in patient relationship search

BAH-570 - Cancel/Postpone Surgical Block functionality in OT app is not working

BAH-571 - Inpatient report should not show inactive diagnosis

BAH-574 - Unique constraint for surgical appointment attribute types in OT scheduling

BAH-578 - Do not mandate value in year field when month and day fields have value

BAH-594 - Performance improvement for Observation Display Control

BAH-597 - Unable to show multiple images in obsToObsFlowSheet control

BAH-599 - Unable to move up appointments in OT schedule block

BAH-605 - Bahmni Connect sync fails during initial patient data download

BAH-485 - Show/Hide Visit start button based on configuration

BAH-639 - Installation with base Database fails due to migrations in OT and Appointments module

Install EPEL repo

You may down the installer here. http://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm

Data Quality for Bed Management

As mentioned in [Known Issues].1, there are a few not-Null, Foreign Key constraints added on Bed Management database tables to ensure data integrity. Please resolve the issues first, without which the feature behaviour may be impacted. 

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

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.

Set 'bed_location_map.bed_id' columns as nullable in 'openmrs': This is required for the "Ward Management" admin console to create a bed layout. 

> mysql -uroot -p openmrs
> ALTER TABLE bed_location_map MODIFY bed_id INTEGER null;

Setuptools error

During installation, If you get the following error:

ImportError: No module named importlib

warning: %post(bahmni-installer-0:0.90-291.noarch) scriptlet failed, exit status 1

Non-fatal POSTIN scriptlet failure in rpm package bahmni-installer-0.90-291.noarch

Please follow these steps

wget https://bitbucket.org/pypa/setuptools/raw/0.7.2/ez_setup.py

python ez_setup.py --user

Undefined period error during quotation confirmation in OpenERP

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 the 2018 with the default ERP database, if you are going to be installing in 2019, you may still face this error.

Please follow the steps as mentioned in this page -  OpenERP error "There is no period defined" while confirming a sale quotation

Following are minor product enhancements with their JIRA card Links: 

1. Enhancements to CSV Imports
1. Ability to read special characters in CSV Imports - #BAH-344
2. Ability to Import Person Attribute of Type ‘Date’ - #BAH-365  
2. Registration
1. Upload an existing photograph as patient profile pic - #BAH-238
2. Make Last name a Configuration and non Mandatory - #BAH-293
3. White labelling
1. Extending the config for a  bottom banner on the login page - #BAH287
4. Order sets
1. Order Sets Rules engine must take latest Height/Weight on calculations  - #BAH-247
5. Conditions List
1. Hide Conditions list from UI  - #BAH-236
6. Programs
1. Support obsIgnoreList in Programs Dashboard - #BAH-307
2. Hide specific Program Attributes based on selected Program - #BAH-296
7. Replace copy task with synchronize for implementation config - #BAH-297
8. Pass the 'patient' object to formConditions - #BAH-276
9. Capture thumbnail for videos on patient dashboard - #BAH-308
10. Translate “location” on various screens in the app- #BAH-275
11. Make delimiter in obsToObsFlowsheet configurable - #BAH131

1. Error is thrown when Orders are saved after collapsing the Lab or Radiology Tab #BAH-285
2. Fixed missing mx dependency issue with ERP installation - #BAH-40
3. "Privilege: Get Forms" is shown for registration and clinical pages- #BAH-54

• Remove Java 7 dependency for DCM4CHEE Installation -  #BAH-244
• Adding patient attribute fields in openerp model fails by throwing error - #BAH-305
• Incorrect address variable name in bahmni ui apps - #BAH-268
• Unable to view patient's visit information in openMRS - #BAH-263
• “PatientInformation” display control is not configured in General tab of visit.json- #BAH-352
• Visit dates should not be mandated if encounter dates are provided for "Encounter csv" upload - #BAH-144
• Encounter upload fails for login location with parenthesis  - #BAH-230
• Link to Open uploaded Pdf in new tab is not visible -  #BAH-233
• Patient Dashboard can be seen for provider without Clinical access - #BAH-239
• Multiple Visits can be opened from the same location using Patient Doc Upload - #BAH-250
• Timezone Mismatch warning doesn't work for timezones with spaces in their names - #BAH-289
• Non-Date Range Reports throws exception on the UI - #BAH-65

• Post 0.90 upgrade, to support Lucene search it's essential to run search indexes from the OpenMRS UI. Without this, Patient, Drug and Concept search won't work in openmrs and bahmni.

  Run the indexes: OpenMRS -> Navigate to Administration → Search Index and Run Rebuild Search Index.

  Related Bahmni talk thread for the same - https://talk.openmrs.org/t/help-us-test-the-bahmni-0-90-second-release-candidate/14124/3

• Upgrade Instructions to access Appointment scheduling :

To start using Appointment scheduling, please add one or more of the following privileges to your user roles from OpenMRS Admin Console

• Appointments:FullAccess
• Appointments:ReadOnly
• Appointments:ManageAppointments

You will find more information about user roles and privileges here.

Bahmni Connect on chrome is now a Progressive Web App (PWA):

PWA takes advantage of new features supported by modern browsers, including Service Workers and Web App Manifests and allows the users to work offline.

Also, Google will be discontinuing its support for Chrome Apps, so Bahmni Connect has been ported to a Progressive Web App and use Service Workers for offline support.

More details here - Bahmni Connect - Client

Faster Initial Sync :

Initial patient sync used to sync patients 'one at a time' and took more time if the no. of patients was huge. This initial sync is redesigned to sync all relevant patients at once, resulting in much faster initial sync on both Chrome and Android app. 

More details here - Initial Sync Improvements

What is built:

Form builder shall be the tool using which the implementers shall design the forms for each implementation. The current processes will be changed in that there will not be a compulsory need to create a "concept set" and adding the set to a "concept set of sets" Also the current process of creating a JSON configuration to control the behaviour of concepts could be handled through the form builder.

In 0.88 release, form-builder alpha version was introduced which contained the ability to create new forms Label, ObsControl (text, boolean, coded and numeric obs concepts), Obs Group Control and sections which are visual groupings. Basic form control properties like mandatory and allow decimal (for numeric) had been introduced. The forms were available to be used in the consultation tab.

For more details, visit this page.

Now in 0.89 release, the following new features and enhancements have been introduced:

• Refactor Architecture，for more details, please visit this Doc - Mingle Card #3296
• Automated function test: To make sure form builder works well after refactoring, we setup automation function test to test functionality of form in Bahmni App which created by form builder and these tests are already added into implementer interface CI pipeline - Mingle Card #3297
• Add more: user should be able to add "add more" for the concept and concept set. we add the "add more"control property for obs and obsGroup control in form builder, then implementer can decide to turn on or turn off "add more" when design form - Mingle Cards #3254, #3263, #3042, #2258
• Removing a control from the form: when implementer design a form in form builder, they may put controls into form canvas by mistake, deleting control provide a way for implmenter to correct their design - Mingle Card #2296
• Form Event Handling(form conditions): form builder provide this feature to enable user to capture "onValueChange", "onFormInitial" event, and get/set value of controls. By these basic event and get/set APIs, user can create their own logic freely.  - Mingle Cards #3407, #3406, #3402, #3405, #3152, #3154, #3397, #3129, #3404, #3153 ,#3398

As part of this release, we upgraded OpenMRS to version 2.1. This was a minor release upgrade and there are not many new user visible features. The ability to implement Lucene indexing for patient search was one of the compelling reasons to upgrade to 2.1.

We have observed performance issues in patient search when the number of patient records is high. OpenMRS added Lucene index support for Patient and Patient Identifier. Leveraging this we have built implemented Lucene indexing for patient search in Bahmni, which has improved the search performance.

In 0.89, we have implemented Lucene only for Patient search by Identifier in the Registration app.

Audit logs are records of all the actions performed within an EMR system. In any EMR, it is vital that we know not only what data has been captured and the alterations made to the data, but also who is responsible for these.The function of audit logs is to essentially provide a timeline of all such actions.Audit trails are important from both regulatory and legal standpoints. They will make the EMR more reliable and discourage the misuse of confidential data. 

From 0.89 Bahmni has introduced Audit Logs. The audit log feature can be found inside the 'Admin' module on the home dashboard.For the current release we are tracking user navigations to different pages in the clinical app. We will be defining more such events to have a more comprehensive audit trail.

Mingle Card #3369. (Documentation)

White labelling of Bahmni will provide the various implementations, the ability to brand Bahmni as applicable to them. The implementors will now be able to configure Logos and Text, specific to their implementations, on the landing page and the Bahmni login pages.

More information on White Labelling of Bahmni can be found here and here.

Conditions is the most important clinical information of a patient. Bahmni now provides the ability to capture and edit conditions for patients on the diagnoses tab inside clinical consultation. Clinicians can use this feature to capture conditions of patients and manage their old conditions. In the database these conditions can be mapped to ICD-10 codes for reporting purposes.

There is also an ability to associate encounters with one or more conditions to mark the purpose/reason of the visit as “Follow-up” to those conditions. (Documentation)

• Ability to Upload Multiple Documents - Mingle Card #3089
  • Multiple documents now can be uploaded at once.
  • This is supported in both Patient documents upload and Radiology Uploads module.
• UX enhancement to the Patient image upload through Observation Forms - Mingle epic #3290
  • The UI of image upload through forms and their display on dashboard has been enhanced.

Bug Fix: The error message when unsupported formats are uploaded has been enhanced.

The implementers can Show/Hide display controls on the dashboard based on whether there is data in it or not. - Mingle Card #3092

When the dashboard contains a lot of information, it fails to display in a single page and requires the user to scroll through the page to get to the information they want to see. So hiding controls that have no data is convenient. However in some cases empty display controls may serve as reminders to users to enter data. In which case showing the display controls is more intuitive (Documentation).

Earlier if a single visit is configured, the registration second page can be configured to appear or not. From this release onwards, users can configure registration second page availability even when multiple visits are configured. (Documentation)

When large amount of information is captured, the forms grow in size, the user would need to do significant amount of scrolling to get to relevant fields where data is to be entered. It is now possible to show/hide fields in the form based on form conditions.  (Documentation)

We have replaced the two letter codes for locales for which internationalisation is supported, with names of languages to make it more intuitive to the user. E.g français for 'fr'; Espanol for 'es'

Mingle Card #3422

It is now possible to show/hide the left navigation panel on the Observations tab. This has been introduced in devices like iPad to make data entry easier.

Mingle Card #3376

From this release onwards, users need not specify the inventory file each time we run bahmni command. Instead users can specify the file name in environment variable "BAHMNI_INVENTORY". (Documentation)

Mingle Card #2956

It was observed that there was a problem in syncing the drug orders to ERP because MRP of some drugs was less than the sales price. It was causing failed events and thus sync was failing. So we have put in checks to make sure that for new incoming batches of products, MRP is either equal to or more than sales price.

Mingle Card #3447

Post the upgrade to 0.89 is done, to support Lucene search it's essential to run search indexes from the OpenMRS UI. Without this, Patient, Drug and Concept search won't work in openmrs and bahmni.

Run the indexes: OpenMRS -> Navigate to Administration → Search Index and Run Rebuild Search Index.

Note: While indexes are running, there's an error on the UI. Ignore the error as it doesn't impact the index rebuilding.

To track the indexes are done, keep looking at the size of the index files here: /opt/openmrs/lucene/indexes. Indexing is considered done, when the size of the files are no more changing.

Bahmni v0.89 still uses Java 7 for PACS (Dcm4Che). If you intend to use PACS, you will need to download Java 7 (1.7.0_79) in advance. The default lookup location for Java 7 rpm is "/opt". You may also specify the file location using "java_file_url" variable in "setup.yml". If you do want to use higher versions of Java 7 (e.g java 1.7.0_80), then you will need to modify the startup script of Dcm4Che, (“/etc/init.d/dcm4chee”) for JAVA_HOME. Next version of Bahmni will use only Java 8.

Mingle Epic #2731 (Documentation)

Bahmni being an EMR has lot of important patient related information collected over a period of time. In addition there are lot of configurations and setup done customized to hospital needs where Bahmni is installed. In case of any untoward incidents (hardware failure/network issues/manual errors etc...) there is a need to set up an alternative machine or need to set up Bahmni again on the same machine. Hence Bahmni as a product should provide an unified mechanism to perform regular backup and restore the required artifacts so that business continues as usual at the earliest with minimal loss of any data.

In addition, thus far Bahmni only supported full DB backup/restore however starting this release incremental backup and point in time restore of DB’s is supported.

This backup mechanism takes care the following items.

1. Patient images

2. Document images

3. Uploaded files

4. Uploaded lab results

5. PACS images

6. Report module generated files by Queue feature

7. MySQL databases

8. Postgres databases

Implementations can configure the frequency at which backups needs to be taken. It's recommended that the backups be taken in some external devices like an external hard drive and stored securely (preferably outside the hospital premises). For more details on how to backup/restore artefacts, please refer the documentation.

Mingle Card #2940

Until now, ELIS supported only one location to be configured & synced back to EMR. Starting this release, there is support for configuring sample source to location mapping & syncing this information back to EMR. This will ensure samples from different sample source are associated with the corresponding visits for that patient.

Sample source in ELIS will be used to map the source location (documentation)

1. ELIS to EMR sync:

• Users have to manually select a sample source while adding sample details in ELIS  which will be used to sync the information to  a corresponding visit in EMR.

• There is a configuration to set a default value for sample source in Administration tab under site information (documentation).  Users would also be able to select one from the list while while adding a sample in ELIS. Once a sample details is saved, the sample source can not be edited.

2. EMR to ELIS sync:

• In Elis, sample source will automatically take the encounter location when lab orders are placed from EMR. This will be non editable while editing sample collection details in ELIS.
  
  
  

Known Issues:

• When we login to OpenELIS and if we print the lab reports of the patient from Lab Dashboard its throwing “Failed to load PDF Document” error. It is an issue with the 0.88 version.
• To solve this manually copy *.jasper files which are located in /opt/bahmni-lab/bahmni-lab/WEB-INF/reports from any previous versions of bahmni to this 0.88 version in the same path.
  

 Mingle Card #2249 (Documentation)

Mingle Epic #2962

• The disposition tab in bahmni (Consultation module) allows providers to decide on the next course of action for a patient esp w.r.t admitting/discharging a patient.

  • The values listed in the disposition drop down is now made context sensitive based on the patient's admission status. Mingle card #2905.

• Rename & change radiology order options configuration - Mingle card #2820
       a. As part of this story Urgency and Needs print options, played in earlier release, user could enable some of the radiology order options. Some cleanup has been done around this
           to have a better naming convention & an efficient way for users to provide only the needed configuration.
  

• Improvements around pivot table display- Mingle card #2906

  • Some display controls like the Observation & disease template display control's can be configured to show data in a pivot table in the expanded view. The order of data displayed in this table is now in the ascending order instead of the earlier descending order. There is also an option for the user to quickly scroll to the extreme right of the table to view the latest results.
    

Mingle card #2904

Few of the queries used in patient listing queues configured in diff apps like Clinical, ADT  have been optimized to enhance performance.

As part of the previous release, we had UX changes on the observation tab. Few minor improvements have been done around this in this release. #2947 (Documentation).

Some of these include:

1. Maintaining the order in which the forms are added on the left panel.

2. Have the first form in the left panel auto expanded when users access the Obs tab for the first time.

3. Keep the last selected form open after user saves information.
   

Form builder is a tool using which the implementers can design the forms for each implementation. The current processes will be changed in that there will not be a compulsory need to create a "concept set" and adding the set to a "concept set of sets" Also the current process of creating a JSON configuration to control the behaviorb of concepts could be handled through the form builder.

With form builder, users will be able to create forms in Bahmni through a user interface by doing drag and drop of various components required by them on the form and changing the control properties. (Documentation)

The following controls are supported: (Documentation)

• Obs Control

• Obs Group Control

• Label Control

• Section Control
  

Following data types are supported for controls:

• Boolean

• Coded

• Date

• DateTime

• Numeric

• Text

The forms support “Form Status” and “Versioning”. The concept of "Form Status" means that the form will have "Draft" status till the form is WIP (working in progress) and user will be able to "Publish" the form after which it will start showing up on Bahmni apps and will be ready for use. Once the form is published, it will be given a version number. For details on Form Status and Versioning, please visit this documentation page on Wiki.

Some of the functionalities that are not yet supported:

• Add more

• Media data type is not supported yet

• Form Conditions

• Removing a control from the form

• Form Preview before publishing

The installation steps for the form builder app can be found here.

In the earlier release of connect, Bahmni was only supporting one location per connect app. From this release onwards, Connect can be made configurable to support more than one location. This will make the connect application usable in scenarios where multiple locations are covered by a user in a single tour using a single Bahmni Connect application. Default behaviour will still be to support one location per Connect application.

The following features are NOT supported for now:

1. Deleting a previously synced location

2. Highlighting synced locations on Bahmni Connect

3. Migration of existing application data

In addition, Bahmni Connect now validates a manually entered patient identifier on the client side in an offline setting and displays error incase of duplicate patient ID entry.

The installation steps for Bahmni Connect can be found here.

• As part of the multiple locations support for sample source in Elis, Mingle Card #2940,
  
  a. It is required that all values listed under sample source must be linked to a valid location in OpenMRS which in turn should be associated to a visit location in order to sync information to EMR. The information flow will fail if this setup is not proper.
  
  b. Lab Location field under site information in Administration tab in ELIS is removed and will no longer be used.

Known Issues:

• This issue occurs intermittently - "peer not authenticated" error while running reports.  https://bahmni.mingle.thoughtworks.com/projects/bahmni_emr/cards/2721
  

             Workaround: Restart reports service (service bahmni-reports restart)

•     For some known issues/limitations on bahmni connect, please refer this page

• Error is thrown when Orders are saved after collapsing the Lab or Radiology Tab.

  Workaround: The order gets synced inspite of the error. One can acknowledge the error and proceed. This bug will be fixed as a part of 0.90 release.

  JIRA Card BAH-285

As part of this release, we upgraded OpenMRS to version 2.0.2. While version 2.0.2 is a major upgrade in terms of features for core OpenMRS users, this is not much of a difference for existing Bahmni users.

Technically, Bahmni now runs on Java 8, and enjoys a 3x improvement in its throughput because of the upgrade. This means that users can experience a similar performance in Bahmni even if you triple the number of people using the system.

Some insight to the performance tests results can be found here

 Mingle Card #2798 (Documentation)

Bahmni has improved user experience on Observation tab as part of this release. Some of pain points and feedback's on the previous UI have been addressed in the new approach. Some enhancements & benefits include:

• The work space is now divided into two panels. Left side panel will display all the added/selected forms and right side panel will display the expanded form. This helps users to focus on one form at a time without the need to scroll.
• Form validation errors are clearly indicated on the left panel against the specific forms.
• User can now search for a form to be added from the forms list.
• Easy way to  ‘Add more’ of some forms for which the configuration is enabled. This will be useful in filling up multiple follow-up forms.
• Forms shown enabled/disabled in the forms list, differentiates from those that can be added more than once.
• Option to pin forms enables user to quickly access some of the most used forms as these are always displayed on the left panel.  User could choose to unpin at any point in time.
• Delete form option can be used to remove a form that might have been either added by mistake or no longer needed for capturing data.

(Detailed documentation) (Installation Instructions for Bahmni Connect)

Bahmni connect client is specifically designed for CHWs (Community Health Workers) traveling to work in areas (satellite areas) where there is no internet connection. The offline application helps the CHWs to record ramped down medical information about patients. The information collected in the offline application gets synced with the Bahmni online server (mother location) when the device gets internet connectivity. This helps in two ways:

1. Allows patient information from remote areas to reside at a central location to help in clinical decisions, epidemiology, etc.

2. Makes the work of CHWs visible to the clinicians to help in better healthcare in remote and resource constrained areas

The below figure illustrates the user workflow supported by Bahmni Connect Client. Please note that Bahmni Connect is primarily designed as a single user application.

Features supported:

Bahmni Connect currently supports a subset of Bahmni online features. Some of these are

• Works offline. Syncs two way data to server

• Register Patient / Search Patient

• View Patient dashboard and information related to
  

• Observations

• Visits

• Treatments

• Lab orders

• Diagnosis

• Capture observations in forms and enter consultation notes

Please note that this is still in alpha stage. We are working on some of the limitations and performance enhancements. Please do try out and provide feedback.

The installation steps for Bahmni Connect can be found here.

Mingle Card #2643 (Documentation)

An implementer can configure different forms to capture observations. Bahmni now offers a report solution to extract data from the forms in the form of one row per encounter.
This also addresses the scenario wherein a concept/concept set is part of multiple forms and the need is to get a report based on data captured as part of specific forms.

There are different configuration options available to filter and/or include additional columns in the report.
Please refer the documentation for complete configuration details.

Mingle Card #2724

• Pacs archive directory is now made configurable (Documentation)

• Ansible version is now made available in bahmni repo. This would be default used during bahmni installation. In addition, user can also specify the ansible rpm url in the bahmni command during installation.

OpenMRS Upgrade:

Some manual tasks to be taken care of before upgrading to Openmrs 2.0.2:

• Since Openmrs 2.0, any of the child/leaf obs value which does not have a value cannot be persisted in database. Any reference to such obs would result in error.
  Implementations should take care of handling all such obs before the upgrade to prevent any errors that could occur due to this.
  

  The concepts corresponding to these obs will have to be looked at to understand the type of these & the value should be set accordingly.
  To get the count of such obs the following query can be used.

  Count of obs with null values

  select count(*) from obs parent where coalesce(value_coded,value_drug,value_coded_name_id,value_datetime,value_numeric,value_modifier,value_text,value_complex) is null and voided = 0 and (select count(*) from obs child where child.obs_group_id= parent.obs_id and voided = 0)=0;

   One approach to fix this is to "void" these obs. If obs is of value_text type, then you could also choose to set it to empty string.
  
  

• Openmrs stores boolean obs values in ‘value_coded’ column of the table ‘obs’ since previous versions. In version 2.0, Openmrs removed the column ‘value_boolean’ from the table ‘obs’. If any of the custom views added for the implementation references the column ‘value_boolean’ in its view definition, it has to be fixed before starting the upgrade.
  
  One of the views that references the column ‘value_boolean’ is ‘obs_view’.
  Following sql should be executed before the upgrade to fix ‘obs_view’ :
  
  

  obs_view without value_boolean reference

  create or replace view obs_view as
  select
  concept_view.*,
  obs.obs_id as obs_id,
  obs.value_text as value_text,
  obs.value_datetime as value_datetime,
  obs.value_numeric as value_numeric,
  obs.value_coded as value_coded,
  obs.obs_group_id as obs_group_id,
  obs.person_id as person_id,
  obs.encounter_id as encounter_id,
  obs.obs_datetime as obs_datetime,
  obs.voided as voided
  from obs, concept_view
  where
  obs.concept_id = concept_view.concept_id;

  
  
  

• Since Hibernate 4.x, error is thrown when ‘limit’ clause is used in HQL. If any of the groovy files in config uses limit clause, it has to replaced with usage of ‘setMaxResults’ as done in the following commit:
  https://github.com/Bahmni/default-config/commit/8dcd2fc7bb92b4d893340da7a2bd261bf7020005

Changes to Bahmni Command

• A new option is available in the bahmni command to specify the Ansible rpm url  bahmni -i <inventory> -aru <ansible_rpm_url> install. By default bahmni uses the rpm url http://repo.mybahmni.org/releases/ansible-2.2.0.0-3.el6.noarch.rpm. If the rpm file is in your filesystem, give its full path to the -aru option.

Bahmni Connect

• Some performance testing results can be found here.
• There are some observations which were captured during the testing phase. Some of the limitations that are currently present are being worked on.
  Please refer to the Observations/recomendations sections to know more on these.

Known Issues:

• This issue occurs intermittently - "peer not authenticated" error while running reports.  https://bahmni.mingle.thoughtworks.com/projects/bahmni_emr/cards/2721
  

             Workaround: Restart reports service (service bahmni-reports restart)

•     For some known issues/limitations on bahmni connect, please refer this page

Mingle Card #2571 (Documentation)

• For faster look up of patients in registration module, barcode could be generated during the patient registration process which can then be used during patient search.
  

  The card print template in Bahmni is configurable, one can add a barcode generation script to the print template. The barcode image can be generated using the patient identifier which is unique for each patient. During subsequent patient visits, the barcode on the card can be scanned directly without the need of manually entering the identifier on the screen.
  

 Mingle Card #2284 (Documentation)

• While ordering radiology orders during consultation, user can now add an urgency flag and provide instructions for printing which can be comunicated to the radiologist if Pacs integration is setup.
  

(Documentation)

• Report Queuing feature introduced in 0.85 release was useful in getting long running reports. All report requests would be sent to a queue which would then be available for download once the report is ready. 
  
  A feature toggle option has been introduced which lets implementations choose the way report generation happens..either run a report and have it downloaded immediately or switch to report queue option. By default, the report queue option is not enabled.
  

Mingle epic #2484

• Provide ability to configure OpenERP to use https - Mingle Card #2493 (Documentation)
  If you have a domain name that can be mapped to the OpenERP server, drop the url to openerp_url in setup.yml, and start using OpenERP with https.

• Add authentication for OpenELIS atom feed - Mingle Card #2374 (Documentation)
  The content urls in the atom feed of OpenElis has been brought behind authentication. A user (atomfeed) has been created in OpenElis for feeds to work. Please refer to documentation (openelis_username and openelis_password) to change the values.
  

• Built-in roles within Bahmni have been cleaned up, giving proper naming conventions and ensuring all the required privileges for the new features/modules are part of a given role. This is to make it easier to create users with the right roles. Refer the documentation for more information.

Mingle Epic #2541(Documentation)

• Ability to sequence / configure the report columns - Mingle Card #2361
  1. Generic reports output contains default and optional columns for patient details, visit attributes, address etc. Implementers now have an ability to mention the sequence of columns to be displayed in the output as per the need.
     

• Ability to sort columns in generic reports - Mingle Card #2357

Mingle Epic #2477

• Introduction of bahmni install-certs command. The install-certs command can be used to create certificates using letsencrypt, if you have a domain name. More documentation can be found at Documentation
• Introduction of the new UI to visualize atom feed issues (atomfeed-console)
  1. Atomfeed-console can be enabled from your inventory file by adding the ip address of the machine to the [atomfeed-console] group. By default, it has 'localhost'. It can be accessed via the url <ip>/atomfeed-console. Consider adding a new app to the home page.
     
     

• Please use the command bahmni -i <inventory> -av 2.2.0.0 install to install bahmni. The available ansible version is 2.2.0.0.
• Currently Bahmni uses Ansible 2.1.2.0. There is a known issue with epel repo that hosts Ansible rpms. They might remove the current rpm if they release a new rpm. For this reason, we have included an option to explicitly specify the version of Ansible to use. You can run the command bahmni -i <inventory> -av 2.3.4 install. -av is the short option for --ansible-version. To find out the latest available version of Ansible, visit https://dl.fedoraproject.org/pub/epel/6/x86_64/ and search for ansible.
• As part of the story - Cleanup of bahmni in-built roles(Mingle Card #2241), there are new roles created. Some of the roles should not be assigned to users directly as it is only for internal use. Please refer the notes column here.
• For any implementation, upgrading to this release or later
  1. New roles will be added and the existing roles will be unchanged. Existing users will not be affected and can continue using the system as is.
  2. If new roles are to be used, configs would have to be updated & and the roles have to be assigned to users accordingly, as there has been changes around some of the priveliges around tabs in clinical. Refer this table for details.

• Please change password for the "atomfeed" user in bahmni-lab and update installation variables (/etc/bahmni-installer/setup.yml) to the new password.
  
  

Known Issues:

• This issue occurs intermittently - "peer not authenticated" error while running reports.  https://bahmni.mingle.thoughtworks.com/projects/bahmni_emr/cards/2721
  

             Workaround: Restart reports service (service bahmni-reports restart)

Mingle Epic #1686 (Documentation)

• This feature gives the ability to get results on large data sets. Let's say, to get list of observations recorded for all patients in the past year or six months. This is a huge data set and surely you can't run it using instant reports. So, the approach for report running has been changed. Any report request will be queued and the user can go to 'My Reports' tab/page to see the status of the request and can download once the processing is complete. The running of report requests are moved as background jobs.

 Mingle Epic #2236 (Documentation)

• 1. Observations

     1. Replaced ‘short’ with ‘shorNamePreferred’

     2. Replaced fully_specified with fullySpecifiedName (to make it consistence)

     1. An ability to apply date range by obsCreatedDate

     2. Replaced programDatetime with programDate (to make it consistence)

     3. Replaced obsDatetime with obsDate (to make it consistence)

  1. Changes in conceptNameDisplayFormat option

  2. Changes in applyDateRangeFor option

  3. New option conceptValuesToFilter has been added. This option gives ability to filter by values

  2. Visits

  1. An ability to filter records by ‘Date of Admission’ or ‘Date of Discharge’

  2. Column to indicate New patient visit

  3. Lab Results

  1. An ability to filter out ‘Referred Out’ tests. When showing lab results there will be column for Referred Out

  2. When file attached for lab results in OpenElis then there is a column to indicate whether file attached or not

Mingle epic #2007

• Delinking Action Buttons on Patient Dashboard From Display Controls - Mingle story #2330 & #2442
  As part of this feature, display of navigation links on the patient dashboard is made independent of the patient dashboard page load. Each display control in Bahmni now spins by itself and this allows the user to navigate away without having to wait for the complete page load. This is helpful esp incase user intends to access consultation quickly.

• Performance improvements - Mingle story #2308
  Queries used for display of diagnosis on patient dashboard and visit pages have been optimized to improve performance.
  
  
• Validation on Resend OTP - Mingle Story #2273 (Documentation)
  Bahmni provides Two Factor Authentication (2FA) feature which has a Resend OTP option. This story covers couple of more scenarios around handling multiple valid OTP’s at the time of user login.
  
  
• Community - Some of the feature enhancements developed by community has also been merged in this release. Mingle epic #2319 

Mingle epic #2328

As part of this epic, couple of scripts are provided which could be used over the default and the clean empty databases for proper data setup. 

• Provide a way to delete all transactional data from the default database (Documentation)
  User can use this script to delete the demo/transactional data whichis provided as part of the default database.

• Provide a way to add minimal data to a clean empty db to get bahmni working.(Documentation)
  Incase of a fresh bahmni installation a clean db is created for OpenMRS, OpenElis and Odoo. But the data in this is not good enough for Bahmni to start functioning. The script provided would help in setting up the basic necessary data/config so as to get the app up and running.

• Void a patient program (Documentation)

  Users can now void a program enrollment. After voiding the program, it will be removed from the patient’s dashboard. But, there will be a database entry to keep an audit trail.

• Ability to configure multiple prints on Patient Dashboard (Documentation)

  There is now an ability to configure multiple printouts (eg.- visit summary, discharge summary) from patient dashboard including latest visit summary. The prints will appear as a dropdown on the patient dashboard
  
  
• Enhancements in OpenERP

  • • Item category is now visible onPurchase Order print. It is displayed next to the item.

      
      
      
      

  • 
    

    • Receipt date is now displayed on GRN print

      
      
      
      
      
      

    • There is now an ability to mention discount on Supplier Invoice. The discount can be mentioned either in percentage or lump-sum cash discount
      
      
      

    
    

    • Display grand total of expenses in Purchase history
      

      

• Mingle epic #2306 (Documentation)

  We have made improvements so that each of the components can be independently provisioned and deployed. This also solves an upgrade issue, where if one has skipped a specific component (e.g. Lab) during upgrade, the configuration (ssl and postgres) would get removed and thus rendering the component unusable.

  
  

Known Issues:

This issue only happens if you install Bahmni using only RPMs (like https://github.com/Bahmni/bahmni-docker/blob/master/base.sh). You will not face this issue if you usebahmni-installer (ansible) to do the installation.

https://bahmni.mingle.thoughtworks.com/projects/bahmni_emr/cards/2633

Fix for the issue: Execute these steps before doing installation to solve the above mentioned issue

1. Create the file "/etc/bahmni-installer/bahmni.conf"

2. Add the following variables in the file

   OPENMRS_DB_SERVER=localhost
   OPENMRS_DB_USERNAME=openmrs-user
   OPENMRS_DB_PASSWORD=password
   REPORTS_DB_SERVER=localhost
   REPORTS_DB_PASSWORD=password
   REPORTS_DB_USERNAME=reports-user

Mingle epic #1601 (Documentation)

• OpenMRS supports multiple identifiers for a patient. This means that we could capture different identifier types (eg: Hospital ID, National ID, Driving License etc) for a patient. Till now, Bahmni supported only one identifier type and other IDs were to be captured as person attributes. This new enhancement enables Bahmni to support multiple identifiers for a patient.

  Please make sure to change the prints in registration which includes patient identifier

  change patient.identifier to patient.primaryIdentifier.identifier

  
  
  

Mingle epic #1861 (Documentation)

• Generic Lab Results Report
• Ability to get aggregation by row group. The column group is made optional
• Enhanced with age group support in the aggregation either in row group or in column group
• Showing total in aggregation report added as an option. We can configure ‘Total’ column
• Ability to exclude columns in a report
• Obs Report Specific:
  • An option introduced to ignore empty obs values
  • Introduced different formats for concept name display

Mingle epic #1505

• • Ability to write specific rules for Order Sets in the Rules Engine - Mingle Story #1772 (Documentation)

     In certain diseases such as Diabetes, Tuberculosis, etc. paediatric dosing(weight based or BSA based) conflicts with adult dosing (block dosing based). Hence “Custom Rule” has been introduced in Order Sets whereby an implementation can specify rules and the order set will be populated accordingly in the medication tab for the patient so that the clinician’s drudgery is mitigated.

• • Ability to filter out display of specific lab test results in Bahmni - Mingle Story #1516 (Documentation).

    In cases such as cross panel orders, certain tests within the panel must be viewed in Bahmni and some must be filtered to be not viewed. These tests must be created in OpenELIS only, and must be accordingly mentioned in a groovy script so as not to be consumed by OpenMRS.
    
    

  • Address Hierarchy strict entry changes - Mingle Story #1865 (Documentation)

    Configuration has been introduced to make address level fields follow strict autocomplete from  certain address level in both top-down and bottom-up address hierarchies.
     

  • Displaying the Short-name of a Concept if Present in the Diagnosis Tab - Mingle Story #1514 (Documentation)
    

    Diagnosis tab has been enhanced to display the English short-name, if configured, as pointing to the fully specified name in the autocomplete list. Also if a short-name is configured, only it will be displayed against diagnosis across Bahmni.
    
    

  • Disabling Bacteriology Tab in Retrospective Mode - Mingle Story #1698 (Documentation)
    

    In retrospective mode bacteriology tab has been disabled. This is because Bacteriology is not used retrospectively
    
    

  • Remove Health Center from OpenELIS - Mingle Story ##1778 (Documentation)
    

    Health centre has been removed from OpenELIS. However existing features such as sync from OpenMRS to ELIS, patient creation in ELIS, ELIS reports and flow-back of lab results have not been interrupted and continue to function as such.
     
    

Resolved Issues:

• #2002 During upgrade of Dcm4Che component, a variable ‘suid-prefix’ which is specific for an implementation would get reset. Now you can define a parameter ‘dcm4che_study_uid’ in ‘setup.yml’ can be set, which would ensure that the right variable is set in ‘orm2dcm_bahmni.xsl’.
• #2117 Fixed Pacs integration startup error because of an conflicting library dependency.

• As part of this story:  Address Hierarchy strict entry changes - Mingle Story #1865 (Documentation),
  New config 'strictAutocompleteFromLevel' for configuring address fields is introduced. It is used to specify the level from which the address fields should have strictautocomplete.

  As part of this, we are decommissioning the older config 'freeTextAddressFields' (to make address fields accept freeText). From now on by default all address fields will accept free text and autocomplete for both 'topDown' and 'BottomUp' approach.

  All the implementations using 'freeTextAddressFields' config should change to new config 'strictAutocompleteFromLevel' and update the address data accordingly.

  
  

• Using the feature - Support for additional identifiers, Mingle epic #1601 (Documentation)

Known issue:

Mingle epic #1653 (Documentation)

• • • 2FA is additional security mechanism to protect the user from fraudulent act. Bahmni using basic authentication (username, password) from OpenMRS so far. We are introducing 2FA in Bahmni to enhance the security. This feature only covers login through the Bahmni application. It doesn't apply to direct login through OpenMRS or OpenELIS or OpenERP. This feature is optional for an implementation. When this feature is enabled then user will be authenticated with username and password first and on success, the user will get SMS with OTP (One Time Password) in his/her registered mobile. The user has to authenticate with OTP before proceed to use the system.

Mingle epic #1628

• • • Bahmni provides generic reports which will be used to extract data from the system so that implementer can apply macros to get different statistics. To further simplify that, we have enhanced the generic reports so that now an implementer can configure pivot/aggregate and get the desired result. This is available for Observation, Visits and Programs generic reports. (Documentation)
       

    • Since an implementer can apply macros on the output, we have enhanced the report module with concatenate reports so that one can configure more than one report in this report type and will get the output. This feature can be used in HMIS kind of report where multiple reports combined together. (Documentation)
       

    • The report module now can output the result in ODF (Open-Office) format as well.

Mingle epic #1707 (Documentation)

• • • Till v0.83, we were not persisting visit location, only encounter locations were stored. Now we also store location with visit. Now onwards visits will be associated with a location. We have also provided ability to have more than one visit open as long as they are associated with different locations. This is done so that in cases where facilities have multiple ‘visit locations’. This caters to scenarios like facilities looking at different departments like Cardiology or Dental as different visits, or for facilities having outreach programs having subcenters to be treated differently.

Mingle epic #1672 (Documentation)

• • • Earlier, the primary identifier type was hard-coded in Bahmni. Now an implementation can select the primary identifier type they want to use for their implementation. It has been made configurable.

Mingle epic #1976 (Documentation)

• • • Atomfeed has been enhanced to:

      • Raise events in a program specific feed (from OpenMRS) for program enrollment

      • Update OpenMRS feed for create/update patient to include patient relationship info

A configuration has been added to switch on/off raising these events. (Documentation)

Mingle epic #1594

• • • #1968 - Earlier when the drug dose was calculated based on BSA or weight, it used to show up in exact decimal points. Now, it is rounded off to the next whole number if decimals are .50 or above and if decimals are below .50, it is rounded off to the previous whole number.
       

    • #1842 - Earlier all the order sets that are configured in the implementation used to appear on the medication screen. Now an order set search box has been introduced on the medication screen. Users can now search for the order sets based on name and description.
      
      
      
      

    • #1618 - On the order sets authoring page, a new field has been added for “Additional Instructions”. This will provide the ability to have pre-written additional instructions in the order sets as well.
      

Mingle epic #1692

• • • • #1431 - Now, doctors can search active patients and navigate to their dashboard from the dashboard or consultation tab of current patient without going to the patient queues page.
        
        
        
        

    • #1557 - OpenELIS: Running the “Test status by patients” report, the report generated was sequenced by accession number which was making it difficult to search through it for report from a specific date. Now the report is sorted by ascending order of “date of order” making it easier to locate the report from a certain date.
       

    • #1608 - A Validation has been added for variable dosage on medication screen to make dose as a mandatory field.
       

    • #1688 - Observation and diagnosis display controls can now be configured on the prints on the patient registration page
       

    • #1783 - Bahmni now supports ability to select multiple values in autocomplete fields.
      
      
      
      

    • #1993 - Patient information is now displayed on the header on Radiology and Patient Document upload pages.
      
      

    • Community - Some of the feature enhancements developed by community has also been merged in this release.
      Mingle epic  - #1980
      
      

• • • #1843 - Return codes for services

      service <name> status now returns 0 (program is running) or 1 (program is dead).

• • • #1828 - Bahmni installer on other machines

      So far, we had bahmni installer was installed only on the control machine, where from the bahmni deployment is initialized. This installed ‘bahmni command line util’ - using which we can perform various tasks like taking a db backup. From now onwards, bahmni command line util is now available in other nodes as well. Note, this does not copy the ‘inventory’ file (which specifies what services and databases are installed in which machines) or the setup.yml file (which specifies users, password etc) - because the inventory and setup files are to be secured for installations. This means before running the bahmni utility commands, you will have to copy these files onto another node. This is only meant as a backup option in case the control machine crashed for unexpected reason.

• • • #1791 - Individual database import during installation

      Till now, we could only import entire postgres dbms during installation, and not individual database dumps. We can now import individual OpenELIS database or OpenERP database dumps/backups.

• • • #1788 - Bahmni Installed component versions

      Now you can find out installed service versions using bahmni command line utility.
      “bahmni --version”
      Also Bahmni homepage has a link which will display the installed service versions.

• • • #1785 - Security enhancements

      All services runs with “bahmni” user, which has strictly a nologin user now. Shell access for “bahmni” is denied.
      Firewall rules have been tightened. Only essential ports like 80,443, 22 and 8069 (openerp) are open and all other incoming and forwarded ports are being dropped.
      Incorrect ssl conf in passive machine which used to point to active machines (in multi machine setup) has been fixed.

• • • #1637 - Copy all implementation omods during installation from external directory

      While earlier version allowed installation of additional omod (each had to be specified), we now install installation of all omods present in external modules directory (/etc/bahmni-installer/deployment-artifacts/module).

• • • #1638 - Select right version of the OMOD provided by implementation

      Bahmni deployment script is now smart enough to override an existing version of a module with an upgraded one. For example, in the omod directory, if you have “idgen-webservices-1.0.omod” & “idgen-webservices-1.1.omod”, the deployment script will pick the later version. For more information please refer to discussion on OpenMRS Talk.

1.Visit Location

 Mingle epic #490 (Documentation)

In addition to the existing canned reports, in this release, a completely generic reporting solution has been provided for the following-

• • • Visits

    • Patient Programs

    • Observations

These generic reports contain comprehensive information about (Visits or Programs or Observations) and we can apply filters and macros on them to suit implementation specific needs.

Mingle Epic #1440

#1786 - The deployment process now allows setup of dcm4chee application and database on two different systems.

#1651 - Provisioning of the downloadable vagrant box for the release now happens via Ansible. This ensures that all the subsystems are setup properly with the latest release and in sync with each other in the provisioned vagrant box.

#1646 - OpenMRS rpm versioning was previously done as "openmrs-<version>-<build_number>". However the build number (Go cd build number) is reset for every release. This can result in yum install command pulling in an older rpm. The rpm has been renamed to "bahmni-openmrs-<release_version>-<build_number>" (e.g. bahmni-openmrs-0.81-230)

#1604 - During deployment or upgrade, accessing any bahmni service will now result apache showing a "Down for maintenance" page.

Mingle Epic #1232

#1249 - We have upgraded webservices.rest module to v2.14. Till v0.81 we were bundling a version that was forked from openmrs, so that we could work on REST resources for OrderSet during the test period. Since then OrderSet has been merged to master and hence upgrade to v2.14.

 Mingle Epic #1285

#1334 - Earlier, registration encounter was created as soon as the visit was opened from the first page of registration. Now the registration encounter will be created when the registration desk user enters some observations (height, weight etc) in the second page of registration and saves them.

#1363 - In the referred out page of OpenELIS all the tests were sorted in descending order of date-time when they were referred out. Now, in addition to descending order, all the tests which have same accession ID will be grouped together and ordered in the same order as defined in the All Lab Tests set defined in OpenMRS.

#1286 - The application now remembers the tab which was active in the patient listing page when the user navigates to patient dashboard. And, when the user navigates back to the patient listing page after viewing details of the selected patient, the respective tab is made active.

#1186 - The columns shown in registration search results have been made configurable. There are few columns which are fixed (ID, name, age, gender, registration date). On top of this, up to five more columns (person and address attributes) have been made configurable.(Documentation)

#999 - All the options in the location widget are now tied to specific privileges for access (retrospective date, location selection, data entry on behalf of another user). Based on the privileges of the logged in user, corresponding options will be provided. (Documentation)

#113 - While uploading the csv, an extra validation has been added to prevent cycles in concept set definitions. This helps in preventing any looped concepts from getting uploaded.

#1487 - Allow decimal field for numeric concepts now works with concept creation through csv upload (Documentation)

#522 - In OpenELIS, when a patient is searched for and the the test results are asked for, the search query used to take 10-15+ secs to fetch results. A performance optimization fix has been done for this query.

Current Development notes (0.90)

Mingle epics #89 and #570 (Documentation)

Order sets provide the ability to create sets of orders on the orders page, that can be used to improve physician time for ordering, and reduce errors in ordering drug. Currently, order sets can be created by a hospital administrator and used by anyone who can access the Medications screen. Here is how we can define order sets.

Mingle Epics #706, #572 (Documentation)

Installation and provisioning of Bahmni machines have changed. All installers are now packaged as rpms instead of the usual bin-shell style installers. For new installations of Bahmni, please follow this documentation, and for upgrades, please follow this migration document. There are also significant changes in the way Bahmni is setup. For example

• • • All application logs are under /var/log

    • The usual tomcat installation under /home/bahmni has been replaced. Every application uses an embedded tomcat container, and runs as a different service under its own port

    • New bahmni_support user created that helps with installation

    • All executables are under /opt

Mingle Epic#506

• • • Search for lab tests from your Orders tab during consultation

• • • Configuration to make the dose and dose units non-mandatory based on the route specified for a drug. (Documentation)

    • On Bacteriology tab, ability to add multiple samples at a time using the “Add Sample” button.

• • • Option to configure a field as dropdown on the registration page. (Documentation)

    • FreeTextAutoComplete control is now merged with AutoComplete. AutoComplete now supports both coded & non-coded answers. (Documentation)

    • In OpenERP, order-type to shop mapping is made non-mandatory. User can now configure the order types for which quotation needs to be created without having to map to any shop. In such case, the quotation is created against the first one from the list of available shops configured in ERP.

    • Program enrolment now has a separate role. Anyone user who has been assigned with this role only will have access to program enrolment page. (Documentation)

    • Ability to filter orders on the order fulfilment page to display only those ordered from within the facility. (Documentation)

Mingle Epic #1129 (Documentation)

• • • Provides mechanism to dispense drugs from doctor’s location or pharmacy and handle inventory management appropriately. In OpenERP, user has the option to configure the order type -> shop mapping to track the dispensed drugs separately.

    • There is also a configuration to automatically convert quotations to sale orders for drugs dispensed from a given location. The location information is also available in quotation and sale orders listing page.

Mingle epic #1406 (Documentation)

There is now a configuration to specify a macro file for reports in custom excel format. Once a file has been specified for a particular report, when that report is run, the system picks up that file and generates the report accordingly.

Mingle epic #1458 (Documentation)

Using a custom display control it is possible to have the day wise drug intake indication on the treatment chart displayed based on the corresponding drug frequency . For ex:  If the user configures the drug frequency as say Monday, Wednesday, Friday and saves the drug order, the day wise indication (right tick marks)in the treatment chart can be configured to be shown only on those cells which correspond to Monday/Wednesday/Friday.

Mingle epic #614

Few of the queries used for selecting patient in Bahmni and displaying dashboard in OpenELIS have been optimized to enhance performance.

Mingle epic #1478

In OpenERP, couple of custom filters have been added to filter out Quotations/Sales based on duration.

• • • Program Display Control is enhanced to display Program specific information (Documentation).

    • Search functionality on the Registration app is enhanced to support searching patients by Program Attributes (Documentation).

    • Program enrollment page has a redesigned UI.

• • • There is now an ability to edit the start date of active programs.

    • Program attributes now supports coded concepts and numeric values as data-types (Documentation).

Mingle Epic #989

• • • Improved data export for Program Enrollments that displays all the Program Attributes for enrollments over a specified time-range. (Documentation)

• • • Bahmni now does not get affected by pre-installed Java versions on a computer. A compatible version of Java is installed automatically when Bahmni is installed on a machine.

Mingle Epics #1123, #940 and #662

• • • • Provider name now syncs to OpenERP and is saved on the quotation. This can also be used in the bill printout.

      • “Tax” column is displayed in the sale order line items in OpenERP and tax is calculated automatically and added to the total sales amount.

      • In OpenERP, following validations have been added (Documentation)

      • Validation to check if batch number added is correct.

      • Price in the sale order cannot exceed the MRP of the product.

    • Column size for identity_data in OpenELIS is increased to 255 characters from 50 characters.

    • Currently user credentials (username and password) for the reports module is stored in the reports properties file. Any implementation where this user is not created will not able to run reports from the system. Hence a migration script has been added to create an OpenMRS user for reports during implementations where this user is not created.

    • A check has been added in install script to avoid errors. The script checks if BAHMNI_VERSION variable is not set. If yes, then the install script gives an appropriate error message, and fails immediately, to notify the implementer of the need to set the variable. 

    • Bahmni now has an ability to treat multiple versions of the same form as individual forms if they are saved in the same encounter.

    • Support to have an "Add More" button for a form (Documentation).

• • • Implementers can now specify the report formats to be used by the implementation. (Documentation).

    • Custom display controls can now be configured on Patient Dashboard. (Documentation)

    • Displaying the “Abnormal” button is now configurable. (Documentation)

    • Patient summary now shows the current month of treatment as calculated from treatment start date (Documentation)

    • On the Medication page, there are improvements to: (Documentation)

  • • • Enable deletion of a drug order.

      • Internationalization support for headers of the columns in the custom control to display drug history.

      • The Drug Name and Refill and action buttons are fixed and displayed at all times. The rest of the columns can be made scrollable, if required.

• • • Form header is now fixed at the top of the layover screen when editing a form. It does not scroll with the form

• • • Patient information is displayed on top of the page while in consultation (Documentation)

    • Configuration for the forms display to show obs date time or only date for each form (Documentation)

    • A new view button for each form on the forms display control. It opens the form in a view-only mode.

• • • Multiple forms display controls can now be configured on the patient dashboard. This helps in displaying logically grouped forms separately in different display controls. (Documentation)

    • Implementers can specify reference terms for concepts in OpenMRS which can be configured to be displayed in display controls (Documentation)

    • Display controls can now be configured to take 25%, 50%, 75% and 100% as the page width. (Documentation)

Mingle epic #1051

• • • Episodes of Care is introduced to link all the encounters related to a program.

    • Following display controls are enhanced to display program specific information

  • • • Drug order details display control

      • Chronic treatment chart

      • Obs vs obs display control

      • Obs display control

      • Bacteriology display

      • Forms display control

      • Drug order section display control on the Treatment tab

      • Month calculation files have also been updated to pick program specific data

    • There is a new Program Specific Drug Order Report that will only consider the active programs within a date range, for drug orders and export all data for the active programs. (Documentation)

    • A new Program Specific ObsTemplate report that will only consider the ACTIVE programs within a date range, for an obs group (form) and export all data for the ACTIVE programs. (Documentation)

    • Delete patient data script has been updated to take care of Episodes of Care

    • A migration script is available for creating episodes for existing implementations that use programs.