Bahmni Standard 1.0.0 Release Notes

Bahmni Standard 1.0.0 is the first release of standard on docker with upgraded OpenMRS version, enhanced In-Patient features, support for Odoo 16 LTS, SNOMED Integration and enhanced security.

On this page

1 Bahmni Standard v1.0.0 Major Features
2 Individual Artifact Versions
3 Getting Started for new Implementers
4 Migration for existing Implementers

Bahmni Standard v1.0.0 Major Features

This release of Bahmni Standard includes the following features:

Dockerized: Bahmni is now fully dockerized, simplifying installation and operation across major operating systems like Linux, Windows, and Mac OS. Docker containers isolate applications, ensuring that all dependencies and configurations are included in the package, making deployment consistent and reliable. Read about the setup guide here.
Cloud Ready: Bahmni is optimized for secure cloud deployment, allowing healthcare providers to deploy easily in any cloud environments like AWS, Azure, or Google Cloud etc.
Security: Significant security upgrades, including critical fixes to vulnerabilities, ensure Bahmni is more resilient against cyber threats, particularly when deployed in cloud or multi-user environments. There are security scanners configured in Bahmni build workflows which scans the artifacts before getting published.
Pre-configured Medical Dictionary: Bahmni now ships with the CIEL dictionary, which includes over 56,000 medical terms, with mappings to SNOMED, LOINC, and ICD-10. It also comes pre-loaded with clinical forms, the India Essential Drug List, and reporting tools. This helps save time on initial setup, requiring minimal configuration and supports accurate medical coding for better reporting and interoperability. Read more about this on this Wiki Page.
Support for Initializer Module: Bahmni OpenMRS distro now bundles the initializer module which allows maintaining the metadata in the form of CSV files and version control it within the implementation specific configuration. Read the module’s documentation here to know the list of domains supported.
New In-Patient Features: A new set of In-Patient features: Inpatient Dashboard, Care View (Ward) dashboard, and the ability to manage inpatient medication and non-medication tasks, offering healthcare providers better visibility into patient care. Refer to this feature guide for more details.
FHIR Support: In addition to basic FHIR compatibility, Bahmni now supports anonymized data retrieval and integration with the FHIR Terminology Service, enabling advanced interoperability. This feature facilitates secure data exchange across healthcare systems and makes Bahmni more compliant with modern healthcare data standards, improving system integration
Teleconsultation Support: Bahmni now supports teleconsultation using Jitsi, allowing healthcare providers to conduct virtual consultations. It also includes ad-hoc tele-consultation features for more flexible use. Refer to feature guide and setup guide for more details.
SMS/WhatsApp/Email Support: Bahmni enables notifications via SMS, WhatsApp, and email for sending prescriptions and appointment reminders, registration notifications thus improving communication between healthcare providers and patients.
Odoo 16 LTS: Bahmni now ships with Odoo 16 LTS, upgrading from the previously used Odoo v10. This ensures Bahmni is equipped with a modern, supported and secure ERP system for managing billing, inventory and accounting functions. Odoo 16 also comes out of the box with additional reports. Read more about it here about the setup and migration.
Metabase: Comes out-of-the-box with Metabase analytics/reporting tool connected to OpenMRS DB and Mart DB for easier report creation. Read more and see the demo video here: Bahmni Metabase/Mart.
Integration with SNOMED-CT Terminology Server: Integrates with SNOMED-CT Terminology Server for conditions/diagnoses and drug-related CDSS. Provides support for connecting with an external terminology server or host an on-premise lightweight server. Using SNOMED-CT terminology server integration should be an informed decision. Refer to this Wiki Page for more details.
Enhancements in Appointments: The appointments module has been revamped with an improved user interface and added support for waitlisted appointments, improves overall scheduling efficiency by providing a side panel for scheduling appointments.
Enhancements in OT Module: Operation Theatre module has been enhanced to support Provider view, show OT notes.
Enhanced Login Screen to allow restricted access by location: The login screen has been updated to allow restricted access based on user location. Users can only log in from a list of assigned locations, improving access control.
Quick Logout and Context-Based Relogin: Allows users to log out swiftly using Cmd/Ctrl + Esc and redirects them to their previous page if they log back in within the configured time frame.
Improved Locale Support Across Languages: Lots of fixes for i18n, also ships with translations across various languages.
Upgraded OpenMRS version: Bahmni now runs on OpenMRS 2.5.12, a significant upgrade from previous versions using OpenMRS 2.1.x. This provides improved performance, stability, and access to new features and also enhances compatibility with the latest OpenMRS modules, plugins and security fixes.
Allergies Capture and Display Control: Embedded allergies display control in the patient dashboard which allows capturing of allergies from the dashboard without redirection and display of allergies.
MySQL 8.0 Upgrade: Bahmni now uses MySQL 8.0 as the default database for OpenMRS and reporting services, ensuring better database performance and modern features. This also helps implementers running on cloud as most cloud providers support a minimum of MySQL 8.0. Learn more about this here.
Monitoring and Centralized Logging: Bahmni now includes an out-of-the-box observability stack powered by Prometheus and Grafana, allowing implementers to monitor system performance and infrastructure health in real-time. This stack collects, stores, and helps visualize metrics such as CPU usage, memory consumption, disk I/O, network activity, and application performance. The PLG stack collects logs from all Bahmni services (OpenMRS, Odoo, MySQL, etc.) in one central place, making it easy to monitor system behavior, debug issues, and trace errors. Read the setup guide here.

Individual Artifact Versions

Bahmni Standard v1.0.0 comes with the following artifacts tagged and released. These values can also be referenced from the .env file in the bahmni-docker/bahmni-standard

S.No	Artifact Name (Docker Image)	Version

S.No	Artifact Name (Docker Image)	Version
	bahmni/proxy	1.1.0
	bahmni/standard-config	1.0.0
	bahmni/openmrs	1.1.1
	bahmni/bahmni-web	1.1.0
	bahmni/appointments	1.1.1
	bahmni/implementer-interface	1.1.1
	bahmni/patient-documents	1.1.1
	bahmni/sms-service	1.1.0
	bahmni/microfrontend-ipd	1.0.0
	bahmni/reports	1.1.0
	bahmni/openelis	1.0.0
	bahmni/odoo-16	1.0.0
	bahmni/odoo-connect	1.0.0
	bahmni/odoo-10 (Only for backward compatibility)	1.0.0
	bahmni/dcm4chee	1.0.0
	bahmni/pacs-integration	1.0.0
	bahmni/bahmni-mart	1.1.0
	bahmni/metabase	1.2.0
	bahmni/cdss	1.1.0
	snomedinternational/snowstorm-lite	1.4.1-beta

The versions of OpenMRS modules bundled can be referred from the OpenMRS → Administration → Manage Modules page.

Getting Started for new Implementers

If you are new to Bahmni and want to get started, follow the instructions below:

git clone https://github.com/Bahmni/bahmni-docker.git

cd bahmni-docker

git checkout tags/1.0.0-standard

cd bahmni-standard

# Using docker compose

docker compose --profile bahmni-standard up -d

# Or use the bash script

./run-bahmni.sh .env

Migration for existing Implementers

If you are currently running Bahmni on CentOS (v0.91, v0.92 or v0.93), migrating to Bahmni Standard 1.0.0 requires careful planning and execution. We recommend implementers to thoroughly review the migration guide to understand the steps involved in migration.

Reference Links:

Migration Guide

Bahmni Upgrade Training Recordings

Community Session on Bahmni Upgrade

If you are already running on docker, then we highly recommend you to update the IMAGE_TAG variables in the .env file with the artifact versions mentioned above.