Announcing - Bahmni 0.93 -Alpha Release.

Hello All,

Bahmni 0.93 alpha is available at our QA environments.

We have installed the 0.93 related changes in the following link for you to do QA

Login credentials:

EMR : superman/Admin123

ELIS (Lab): admin/adminADMIN!

dcm4chee: admin/admin

odoo: admin/admin

Features Released: Role-based access for forms based on the department

Internationalization of Registration and Clinical Modules


Role-based access for reports

Appointment Module - Migration from AngularJS to React.

Recurring Appointments

Multiple Provider

Conflict Management for patient and service

OT scheduling

Form Builder Enhancements

Anything sellable can be synchronized as an Order to ERP.

UI enhancements in Elis

Upgrade node version and dependencies in BahmniApps

Whats not included in alpha and will be taken up in beta?

Bahmni Connect - upgrade

Known Issues which the core team is working on:

Openelis to Openmrs sync

Bahmni connect


In case you need an rpm to install and test the same please use

Local Bahmni Setup: Steps to be followed

If you would want to run and try Bahmni locally, please follow the steps. The same will be updated in WIKI too.

yum install

sudo yum install python-pip [If not already present]

sudo yum install epel-release [If not already present]

sudo yum install python-pip [If not already present]

sudo pip install pip==v19.0

sudo uninstall click

sudo pip install click==v7.0

pip install beautifulsoup4

Download latest bahmni installer (check the thread below for notification on latest installer availability)


Install bahmni installer

yum install


sudo yum install bahmni-installer-0.93-37.noarch.rpm

Create setup.yml configuration file.

curl -L >> /etc/bahmni-installer/setup.yml>> /etc/bahmni-installer/setup.yml

Point the bahmni_base_url to amazon s3. You need to add line below in setup.yml for this


Source the local file:

echo “export BAHMNI_INVENTORY=local” >> ~/.bashrc

source ~/.bashrc

Modify the inventory file if needed and run the installer

bahmni -i local install

Let Core team know if any feedback through following channels -

  1. Talk thread : We will use this thread for anything posting relevant to the release - Updates and notifications from the release team, reporting new issues (new JIRA cards only) etc

  2. Slack : #community channel for regular discussions. Please see here for details

Kindly reach out to us, incase you find any issues related to installation or any feature released. We would be very happy to help you out.


@ajeenckya, @angshuonline, @arjun, @darius, @ivange94, @krishnanspace, @mksd, @mksrom, @pramidat, @ramashish, @ramses, @shilpa, @vmalini @ajeenckya @arjun @mksrom @pramidat @ramashish @shivarachakonda @binduak @swetha184 @laxman @anandpatel @sushilp @sushmit @vmalini @akhilmalhotra @dipakthapa @ramashish @pradipta @mddubey @rrameshbtech @mddubey @iadksd @angshuonline @mwelazek @michaelbontyes @buvaneswariarun @praveenad @sanjayap @florianrappl @apaule @mwelazek @som.bhattacharyya @tejakancherla @rabbott @grace @sandeepe @apaule


Environment: 0.93 QA server -

OpenElis lab results are not syncing with Bahmni.

  1. Created a new patient and OPD visit
  2. Placed 3 lab orders
  3. Patient got synced with OpenElis
  4. Entered and validated results in OpenElis
  5. Results are not syncing with Bahmni even after multiple refresh and waiting for a min.


Thanks for bringing this up. This has been identified and fixed in the beta release. Beta will be out on monday

1 Like

Hello @buvaneswariarun could you kindly provide the link of 0.93 beta if it is out for testing, Thanks Apuda

Hi, Please go through the following link for BETA release.


Thanks so much for availing me the link,

i get this error

whenever i try any procedure request… which list of procedures can we test… Thanks

@apuda - Can you try this please

Yes, this error is because there is no mapping between the newly created order type and the concept class id for which you will have to execute the following insert statements.

insert into order_type (name, description, creator, date_created, retired, uuid, java_class_name) values(<new order type>,<description of new order type>, <user id of creator say 1>, now(), 0, uuid(), 'org.openmrs.Order');
insert into order_type_class_map (order_type_id, concept_class_id) values(<newly created order_type_id above>, <concept class id used for the new order type>);

@ramashish thanks for pointing out this challenge i was facing.i believe this will be fixed by the core team i was testing the procedure orders which by default were to show off when searched or displayed like the Radiology or Lab orders. Thanks

Hi @apuda - it is the expectation from the implementer that, I case there is a new order type introduced, then we need to take care of adding these two entries in the db manually. If there is a requirement for an interface to do the same, we dont have that feature right now and you can raise this concern in our PAT calls or discuss about the same in the slack channel or talk thread.

1 Like

@buvaneswariarun, Thanks so much for the clarity that i have understood to my best,for testing purposes of 0.93-73 beta,i had expected you avail us with a few procedure cases we do testing since we dont have access to EMR module to manually add any procedure test. take a look at a sample procedure test we do

. Thanks once again for the response. Regards Apuda