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 | Description | Timelines | Links | Status | Project Leads | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|
1 | 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. |
| ACTIVE | |||||||
2 | Bahmni on Cloud | 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. |
| ACTIVE | |||||||
3 | Lab Lite (using Bahmni@next) | 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. |
| ACTIVE | |||||||
4 | Performance & Capacity Plan for Bahmni | Perform Performance/Load testing of Bahmni to publish a whitepaper on Bahmni performance. See this document. |
| ACTIVE | |||||||
5 | Payments-Lite | Lightweight alternative to Odoo for invoicing & billing (using opensource Crater). See this document. | ACTIVE | ||||||||
6 | Upgrade to OpenMRS 2.5 | Upgrade Bahmni to the latest version of OpenMRS platform. This has many benefits including: Support for higher versions of Java, Synergy with OpenMRS development, Support for PostgreSQL (besides mysql), new APIs with FHIR support, stability and bug fixes. Read more here: https://talk.openmrs.org/t/bahmni-openmrs-platform-upgrade-from-2-1-6-to-2-5-0/36063 |
| ACTIVE | |||||||
7 | Security hardening | Features to harden the overall security for Bahmni. This includes
| ACTIVE | ||||||||
8 | 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. |
| COMPLETED-P1 ACTIVE-P2 | Ruchika Bhargava (ThoughtWorks) | ||||||
9 | Bahmni Covid-19 Starter Kit | Extend Bahmni Capabilities for Covid19 Pandemic information in order to provide quality care to patients, reduce risk for front line workers and provide government compliant reports and state Programs , Forms , Reports built for
|
| RELEASED - 1.0 | Ruchika Bhargava (ThoughtWorks) @Ati | ||||||
10 | Tele-consulting using Bahmni as EMR | 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. |
| COMPLETED | Ruchika Bhargava (ThoughtWorks) | ||||||
11 | Bahmni Dockerization | Dockerize Bahmni. See discussion here. The current milestone is focussed on Bahmni EMR UI + OpenMRS. See Mekom solutions docker-for-bahmni here. |
| M1 -COMPLETED | Team: docker squad | ||||||
12 | Bahmni v0.93 | Bahmni V0.93 release work. Lots of new features. See this. |
|
| COMPLETED | ||||||
13 | Integration with SENAITE (BikaLIMS) | Adopt the HL7-based integration of Bahmni with SENAITE (Lab System). See this discussion. |
| PLANNED FOR 2022 | Johannes Heinzl Albion Shala Akhil Malhotra | ||||||
14 | OCR in Bahmni | Use OCR to extract coded data from uploaded patient documents (like Lab Results from 3rd party labs) - to display them on Bahmni Patient dashboard. | ON-HOLD | IIT Mumbai/KCDH Venkatapathy Subramanian | |||||||
15 | Bahmni@next |
|
| MERGED: LAB LITE | Team: Bahmni@next squad | ||||||
16 | Speech to Text Recognition | Integrate Bahmni with a Speech-to-text engine (like Vakyansh) for reducing the effort & time taken by clinicians to record data in Bahmni. | PLANNED FOR 2022 | ||||||||
17 | Upgrade to Latest version of Log4j | Upgrade Bahmni Log1.x and Log2.x to latest version of Log2.x, for enhanced security. | Milestone: |
| COMPLETED | Nouman Memon Rohit Yawalkar (Deactivated) Deepthi Mantena Himabindu Thungathurty | |||||
18 | Odoo Upgrade to latest version | Bahmni is packaged with v10 of Odoo, whereas the latest version is v15. Need to upgrade and dockerize Odoo. This will also require some modifications to Bahmni Odoo modules. | PLANNED FOR 2022 | ||||||||
19 | Centralized Metadata Management | 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. |
| PLANNED FOR 2022 | Centralized Metadata Management | 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. |
| PLANNED FOR 2022 | Beehyv & Thoughtworks |