How dwb-ehealth/bangladesh-config works
Project type and purpose
• This is a DevOps/configuration-management repository for deploying the “Bangladesh” implementation of Bahmni (an OpenMRS-based EMR).
• It bundles:
– Ansible playbooks and roles for provisioning servers
– Bahmni installer configuration (in /etc/bahmni-installer)
– OpenMRS modules and offline assets
– Data-warehouse (Bahmni-Mart) ETL scripts and Metabase dumps
– Clinical form definitions and translations
File-structure analysis
• Top-level directories:
– playbooks/… : Ansible roles and playbooks (appointment-frontend, openmrs, bahmni-mart, etc.)
– etc/bahmni-installer & etc/bahmni-mart-playbook : installer and mart-ETL config
– openmrs/… & offline/openmrs/… : JSON and Groovy modules, UIs for OpenMRS and offline clients
– bahmni-mart/… : JSON mapping and SQL views for the data-warehouse
– clinical_forms/… : form definitions + translations
– database-snapshots/… : initial DB dumps, anonymization scripts, migration archives
– configuration/… : CSVs for locations, person attributes, appointments definitions
• Key indicators:
– Ansible for orchestration,
– JSON + SQL for metadata & ETL,
– Groovy/.omod for OpenMRS extensions,
– Offline PWA assets for field use,
– Separate inventories for EMR, EMR-DB, reports, reports-DB
Insights from README
• Describes step-by-step deployment: install dependencies, fetch configs, run bahmni -i prod install, then Ansible playbooks (playbooks/all.yml) against an inventory with roles:
– bahmni-emr (Tomcat + OpenMRS)
– bahmni-emr-db (MySQL)
– bahmni-reports (Bahmni-Mart + Metabase)
– bahmni-reports-db (MySQL)
Main components and their interactions
a. Ansible Control Machine
– Runs playbooks and roles, pushes configs and packages to all hosts
b. Application Tier – bahmni-emr
– Apache HTTPD / Tomcat
– OpenMRS core + modules (clinical, adt, registration, etc.) loaded from openmrs/apps and offline/openmrs/apps
– Configuration symlinked from /var/www/bahmni_config/configuration
c. Data Tier – bahmni-emr-db
– MySQL storing OpenMRS patient, encounter, concept data
– Initialized via database-snapshots/latest-openmrs_backup.sql
d. Reporting Tier
– Extraction & transformation (“Bahmni-Mart”) using bahmni-mart JSON mappings and SQL views
– Loads into Reporting DB (bahmni-reports-db MySQL)
– Metabase BI server (bahmni-reports) connects to Reporting DB, serves dashboards
e. External actors
– Clinical users via browser (HTTP/HTTPS) to bahmni-emr
– Field/offline clients fetching offline assets from bahmni-emr or dedicated static host
– Operators/DevOps via SSH to Ansible controller and target hosts
Architectural patterns and design principles
• Infrastructure as Code (Ansible) – idempotent provisioning
• Multi-tier separation – app, DB, reporting
• Modular config – roles, playbooks, reusable JSON/SQL artifacts
• Offline-first PWA support – pre-bundled assets under offline/
Essential details to capture
• Inventory-based host grouping (role assignment)
• SQL dump initialization step for EMR DB
• Symlink of /var/www/bahmni_config/configuration into OpenMRS
• Offline assets provisioning under offline/openmrs/apps
• ETL mapping files in bahmni-mart (JSON + viewSql/*.sql)
• Playbook orchestration flow (all.yml → per-role tasks)