| Info |
|---|
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. |
| Info |
|---|
See the Roadmap Goals/themes for Bahmni for 2022-23 here: Bahmni Roadmap |
Initiative / Project | Description | Timelines | Links | Status | Project Leads | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Completed in 2021 | |||||||||||
| 2 | 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
|
|
| Ruchika Bhargava (ThoughtWorks) @Ati | |||||||
| 3 | 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. |
|
|
Team Trello Board (restricted)
Github: bahmni-hip-service
|
|
|
Ruchika Bhargava (ThoughtWorks)
| ||||||||||||
| 4 | Tele-consultation Appointment | 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. |
|
| Ruchika Bhargava (ThoughtWorks) |
| 5 | Bahmni |
v0.93 |
Bahmni V0.93 release work. |
Lots of new features. See this. |
|
|
| |||||||||||||||||
| 6 | Completed in 2022 | |||||||||||||||||||
| 7 | Upgrade to Latest version of Log4j | Upgrade Bahmni Log1.x and Log2.x to latest version of Log2.x, for enhanced security. | Milestone: |
|
| Nouman Memon Rohit Yawalkar (Deactivated) Deepthi Mantena Himabindu Thungathurty | ||||||||||||||
| 8 | Bahmni Dockerization | Dockerize Bahmni. See discussion here. This will help in easy packaging of dependencies, easy install & upgrades, better security, allow for multiple OS support (besides CentOS), and make it Kubernetes/Cloud ready. |
| |||||||||||||||||
|
|
| Team: docker squad |
Bahmni v0.93
Bahmni V0.93 release work. Lots of new features. See this.
Release on:
Slack: #bahmni-93
| 9 | 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. |
|
| Angshuman Sarkar Nouman Memon Mohankumar Thangavel Mradul Jain | |||||||||||||
| 10 | Lab Lite
(using O3 design styles) | 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. |
|
| ||||||||||||||
| 11 | Payments-Lite
| Lightweight alternative to Odoo for invoicing & billing (using opensource Crater). See this document. |
| |||||||||||||||
| 12 | Bahmni Lite for India
| A lightweight version of Bahmni for clinics and small hospitals, ready for India (with India Master Data) + CIEL dictionary, ready for Cloud/AWS/Kubernetes. Read more here. |
|
| Akhil Malhotra Gurpreet Luthra Nouman Memon Himabindu Akkinepalli | |||||||||||||
| 13 | Bahmni@next |
|
|
| Team: Bahmni@next squad | |||||||||||||
| 14 | 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 |
|
|
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.
Slack: OpenMRS (#ocl)
| Status | ||||
|---|---|---|---|---|
|
| 15 | 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. |
|
| ||||||||||||||||||||
| 16 | Performance & Capacity Plan for Bahmni
| Perform Performance/Load testing of Bahmni to publish a whitepaper on Bahmni performance. See this document. |
|
|
| |||||||||||||||||||
| 17 | Security hardening | Features to harden the overall security for Bahmni. This includes
|
|
| ||||||||||||||||||||
| 18 | Tele-consulting using Bahmni as EMR (Adhoc) | 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. |
|
| Ruchika Bhargava (ThoughtWorks) | |||||||||||||||||||
| 19 | Speech to Text Recognition (Part1) | Integrate Bahmni with a Speech-to-text engine (like Vakyansh) for reducing the effort & time taken by clinicians to record data in Bahmni. |
| |||||||||||||||||||||
| 20 | Upgrade to MySQL v8 | Upgrade to latest version of MySQL for better security, reliability and performance. | - |
| ||||||||||||||||||||
| 21 | Make Bahmni Mobile/Tablet Responsive for Clinical Use cases
| Make current web version of Bahmni usable for Tablet/Mobile resolution for clinicians, so that on-the-go within a hospital, doctors can quickly view/edit patient records. | Milestone1: |
|
| Aditya Karle, Krishna Kiran | ||||||||||||||||||
| 22 | Bahmni Analytics out of the Box (with Mart & Metabase) | Make it easy & powerful to perform Bahmni Reporting/Analytics using OpenSource Metabase & Bahmni Mart. This is now available out-of-the-box with Bahmni docker. | Milestone1 MVP: Package Metabase & MART completed on |
|
| |||||||||||||||||||
| 23 | 2023 | |||||||||||||||||||||||
| 24 | Multi-tenancy for Bahmni/OpenMRS (Research ONLY)
| OpenMRS currently is single tenant (with dedicated DB per facility). This makes it costly for SaaS providers to host one instance of OpenMRS per clinic. With Multi-tenancy, the same OpenMRS/Bahmni instance should be able to support multiple clinics (20x), which will reduce operational overhead and bring down hardware costs. |
| |||||||||||||||||||||
| 25 | SNOMED CT Integration as FHIR Terminology Server
| In collaboration with SNOMED, the Bahmni team is working to show case best-practices of how EMRs should record clinical data in SNOMED, and integrate in real-time with SNOMED Terminology Server over FHIR. | Milestone1: Milestone2: |
|
| Ketan Goenka Vijay Anand Shanmughadass Siva Reddy Pathuri Kai Kewley | ||||||||||||||||||
| 26 | Incremental UX rewrite for Consultation App |
| Milestone1: (this work is happening as part of the IPD re-write initiative) |
|
| Aditya Karle (UX), Krishna Kiran Abhinab Bharali Himabindu Thungathurty | ||||||||||||||||||
| 27 | Odoo Upgrade to latest version
| Bahmni is packaged with v10 of Odoo, whereas the latest version is v16. Need to upgrade and dockerize Odoo. This will also require some modifications to Bahmni Odoo modules. | Milestone1: |
|
| Angshuman Sarkar Gurpreet Luthra (Coordinating with KGISL) | ||||||||||||||||||
| 28 | Avni Integration for Offline data recording (called Bahmni Outreach app)
| Ability to capture data remotely in non-Internet locations by Community Health workers using opensource Avni app. | Milestone1: Milestone2: |
| Mohankumar Thangavel Gokul Kuppan[GoK Team] | |||||||||||||||||||
| 29 | Integration with SENAITE (BikaLIMS) | Adopt the HL7-based integration of Bahmni with SENAITE (Lab System). See this discussion. |
|
| ||||||||||||||||||||
|
| Johannes Heinzl Albion Shala Akhil Malhotra |
| 30 | In-Patient Features (IPD)
| In-Patient features in Bahmni, to record and manage patient data from Admission to Discharge, e.g. Drug Chart (MAR), Ward View, Nurse Dashboard, Discharge Summary, etc. All this work is being done in React/Carbon UI. | Milestone1: |
|
| Himabindu Akkinepalli Abhinab Bharali Aditya Karle[UX] Amit Sil | ||||||||||||
| 31 | Bahmni Standard V1.0 | Release Bahmni Standard for Hospitals with updated OpenMRS, Odoo, Lab, DCM4chee, etc, to provide for an upgrade path to customers who are on V0.93. Also make it docker-compose and AWS/Kubernetes ready |
| |||||||||||||||
| 32 | Upgrade to Java11 | Java8 will reach End-Of-Life soon. See this discussion. | - |
| - | |||||||||||||
| 33 | Support for Allergies | Bahmni UI to provide support for recording Patient Allergies (OpenMRS already has backend support for this) | - |
| - | |||||||||||||
| 34 | Stronger IDP for Login Security | Provide a stronger Identity Provider for User AuthX and AuthZ (support it for OpenMRS, Crater, Lab, ERP, Dcm4chee). | - |
| - | |||||||||||||
| 35 | ON HOLD | |||||||||||||||||
| 36 | 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. |
|
| ||||||||||||||
| 37 | 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. |
| |||||||||||||||
|
TBD
Bahmni@next
Facelift Bahmni and migrate out of AngularJS.
Start: Nov-2021
End:
Releases:
Medication: TBD
Documentation
Slack:
Channel: #bahmni-next
JIRA: Kanban Board
GitHub:
| Status | ||||
|---|---|---|---|---|
|
| IIT Mumbai/KCDH Venkatapathy Subramanian | |||||||||
| 38 | 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. |
|
| Centralized Metadata Management |