The goal is to provide support to the implementers in configuring Bahmni across various use cases. This can be achieved by creating a self-learning module which guides the implementers across various commonly used workflows in Hospital and Lab management.
Bahmni is an easy to use, complete, open-source Hospital Information System (HIS) and Electronic Medical Record (EMR) that has been built in the Global South to meet the needs of low resource environments. Bahmni is a distribution of the OpenMRS medical record platform, with a user interface built from the ground up. It also supports Odoo (formerly OpenERP), OpenELIS, and dcm4chee, providing an integrated robust solution that manages patient information in a flexible fashion through the care cycle, including registration, various points-of-care, investigations, lab orders and results management, PACS and billing.
BeeHyv will use the investment to facilitate the resources needed towards shipping the proposed solution to the community. This will generally cover the development and administrative costs related to the project.
Bahmni has a low-code configuration driven architecture to support various use cases in hospital and lab management, the latest implementation guide is from 2017 and the plan is to create a learning module which guides the implementers configure commonly used scenarios. This could also be extended to support end user training since Bahmni doesn't come with a user guide.
BeeHyv comes with both being a preferred technology partner for non-profits on several low resource settings and for startups in defining and implementing DevOps strategies. Our expertise in both open-source technologies and DevOps technologies while working on past projects would ensure that the set goals of the proposed solution are met.
The Bahmni project was started by Thoughtworks in January 2013, and in January 2018 Bahmni coalition was formed to own the Bahmni project. At present, the Bahmni Coalition includes 11 organizations, including BeeHyv.
BeeHyv will undertake the development activities and will work closely with of Bahmni coalition and other relevant communities to achieve the project goals
The user guides are not available for end-users even though Bahmni is a highly configurable system. Besides, the implementers guide available are also not up-to-date and are not easy to use for new implementers.
We propose to develop learning modules supporting the following use cases:
Basic Clinical Implementation: Data Entry: In this setup, Bahmni is used for managing hospital operations and for clinical data entry at the end of the visit. The setup involves using Bahmni for Registration, Laboratory, Pharmacy and / or Billing and Reporting. Clinical information is captured in post facto data entry mode.
Complete Implementation: In this setup, Bahmni is used for Clinical activities as well as for managing hospital operations. The setup involves using Bahmni for Registration, Clinical (OPD & IPD), Laboratory, Pharmacy and / or Billing and Reporting.
Program Specific Implementation: In this setup, Bahmni is used for capturing disease specific program data. The setup involves using Bahmni for Registration and capturing program specific Clinical data and Reporting. This typically involves installing Bahmni with only OpenMRS.
The plan is not to create new training materials, but to provide a self-learning module using moodle ( or other opensource). The users can go through the relevant scenarios in moodle which would support creating effective and safe implementation.
Monitoring and Evaluation approach:
We propose to follow the Agile development model with 2-week sprints, with daily stand-ups. A project management tool like Trello or JIRA would be used to assign work to the team and track progress. A status report will be published to the Digital Square team before the monthly sync-up (proposed) to set the agenda for the call. It will contain the following information:
Activities completed during the reporting period / planned during the reporting period but not completed (Slipped activities will be reported in bold).
Activities scheduled for the next reporting period.
Blockers, dependencies, and queries.
Cumulative progress report for the sprint.
The diagram given below explains the model at a very high level.
BeeHyv will provide the following deliverables: code and documentation detailing the tasks accomplished to achieve the codes.
The status and outputs of the deliverables will be provided in the following reports
1. Regular Status reports - These reports will document updates of the activity plans to be submitted regularly at agreed-upon intervals.
2. Interim report - This report will have a summary of the project and a brief description of the progress at an agreed-upon interval through the project execution.
3. Final project report - This report will provide a detailed description of the final results of the project and will be presented during the closure of the project.
Project Gantt Chart
It is critical that the scenarios for all implementations are considered while developing the learning module and any failure in this regard will lead to adoption risks. To mitigate this risk, we plan to have periodic discussions with the Bahmni coalition and incorporate their inputs into the solution development process.