There are usually two or more Active Initiatives (or Projects) at any time in Bahmni – running in different locations at their own cadence. These are independently managed and you may reach out mentioned project leads for details and/or collaboration. The Bahmni core group provides guidance and approves PRs in situations where the core Bahmni product codebase is affected. Volunteers with requisite capabilities, bandwidth and commitment are welcome! Listed below are Active, Completed and Planned initiatives.
Initiative / Project
Initiative / Project
OCL for central metadata management
Use a shared concept dictionary managed in the cloud for metadata & terminology management. Leverage the work done by MSF. See this.
Make it ultra easy to deploy Bahmni on cloud, with automated Infra-as-code, starter kits, docker-images, pre-seeded data, centralized master data / configuration management – so that spinning up a Bahmni instance, or upgrading is easy. Cloud provider yet to be decided – AWS likely to be prioritized first.
A lightweight Lab Result Upload/Entry screen within Bahmni EMR UI. This is helpful in clinics/small hospitals who do not have a full lab, and would just wish to enter (or upload) Lab results into Bahmni (no OpenELIS). Note: This is being developed using the latest OpenMRS3 Micro-frontend architecture in React.
Bahmni as Health Information Provider [HIP]for NDHM Compatibility
Bahmni will function as Health Information Provider (HIP) integrated with India's Federated Health Record system, where users can have access to a longitudinal view of their health data across all providers. Personal Health Record [PHR] architecture also allows for safe and secure exchange of consented health information.
Patients’ ability to consult (COVID or otherwise) is hampered because of physical distancing / restricted people movement. In many cases, healthcare service provisioning during pandemic situations can be achieved through alternative channels like Tele-consulting, which we think will ensure continuity of care, and make healthcare accessible. We want to ensure that for legitimate scenarios, healthcare services are no longer a function of distance. See discussion here.
For multi-instance, cloud deployments of Bahmni, there is a need to have a centrally managed metadata/config, so that all master data and configurations can be managed in one place, and tramitted to all Bahmni servers connected to that central instance. This will make maintenance, standardization, roll-outs and upgrades easier for “blueprint” or “templatized” hospitals – which have similar needs, or belong to a single organisation.