Roadmap Planning Process

How is the Roadmap created?

The Bahmni Roadmap process happens once a year and starts at the beginning of every calendar year, typical in January. We try to publish a one-year roadmap by April. 

We receive feedback/feature requests when you add feature requests in Trello, you post a request in our discussion forum, report an issue in JIRA, and also when we talk to different stakeholders all year round. Based on the inputs we receive we create a high-level product goals wishlist which is discussed and prioritised by the Bahmni Coalition.  

What if I have a feature request after the roadmap has been published?  

At any point, anyone may propose an enhancement to the Bahmni product by submitting a feature request. 

We provide a template that can help organize relevant details for a requested product enhancement, in a way that facilitates review.

The template is made available via both a word document and a Trello card.  

Can I influence a change in the Roadmap?

Yes, you definitely can. We take our community's inputs very seriously. If we feel your requirement is critical for patient care, we will try to accommodate your needs. It would help enormously if your team can contribute to the development as well.   

Can I build a feature and which is not in the Roadmap and contribute it?

Definitely.  When you contribute features, the entire community benefits. We are there to help you and your team through the process

What is the Roadmap Prioritization Criteria?

The prioritization process of the feature will be based on some key metrics listed below.

Disclaimer: The order of the criteria is a general guideline. We will always aim to build a mix of new kinds of improvements.

Proposed roadmap items that come with a commitment to development resources will have the highest priority (assuming good product fit).

Beyond that:

  • The feature is targeted on increasing implementation and adoption of Bahmni within implementations in the community.
    • Requirements from Bahmni systems running in production and those hindering new implementations will be prioritized.
    • Critical issues affecting production operation will have priority.
    • Robustness of the product relating to improvement in the performance, reliability, security and operational aspects of Bahmni will have priority.
  • Ongoing improvements of existing features that can be implemented efficiently (with less up-front development time and low maintenance cost) will have priority. These can include:
    • Feature enhancements to support different healthcare settings
    • New configuration settings to handle different scenarios
    • Changes to accommodate different workflows
  • New features - new features will be prioritized based on
    • The potential extent of the use of that feature in the Bahmni community.
    • Linked to health impact and improvement in inpatient care.
    • Operational improvement in the facility
    • Economically feasible to implement for almost any hospital or health facility.
    • Contributions from implementation teams/ organizations - in part or full.

The Bahmni documentation is licensed under Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)