Configurations: What goes where?

Owned by Shruthi Pitta (Deactivated)
Last updated: Jan 23, 2018 by Darius Jazayeri

There are different levels at which Bahmni is configurable:

  • Installation Configurations
  • UI / Client side 
  • Server Side


  • Configurations in Installation: As Bahmni has a micro service architecture, one could choose the components to install/ upgrade. This can be done through the inventory file. It is located in /etc/bahmni-installer/local. This is the default inventory file shipped with product. Also there are a set of installation variables (like timezone, implementation name, bahmni_repo_url ....)  which can be set in /etc/bahmni-installer/setup.yml. For more information please visit this page.
  • UI / Client side Configurations: Bahmni UI is configurable to a large extent. Configurations like which apps should appear in Bahmni EMR home page, display controls etc. are present in the folder /var/www/bahmni_config (in the server). Implementations can have their specific folder deployed in this path during installation. The default config which gets shipped as part of the product can be found here. For more details about the structure and variables visit Bahmni App Configuration.
  • Server side configurations: The metadata for data in Bahmni EMR is set up through OpenMRS attributes such as users, patient attriibutes, locations, drugs, concepts and concept sets, etc. Apart from these, we also have Global Properties, when a OpenMRS module code needs to refer to a value that's unique to a particular installation, such as a concept ID number or a file path.These are required for every installation of Bahmni. Most OpenMRS configuration can be done using the OpenMRS Administration UI. For further details visit OpenMRS Configuration.



The Bahmni documentation is licensed under Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)