Go to the main page
Search
Downloads

DHIS2 Software Development Roadmap Process

On this page, you can get an overview of the prioritization and development process and schedule for DHIS2 software, including how you can share your input on new features

Jump to a section on this page

    Overview: DHIS2 software roadmap and prioritization

    A dedicated team at the HISP Centre, University of Oslo (HISP UiO) leads the development and maintenance of the DHIS2 software platform. Development of new DHIS2 features is based on input from the HISP network and complemented with the global user community. Priority is given to generic improvements that can have an impact across implementations, rather than those that are specific to one place. DHIS2 software is developed in 12-month cycles of backend releases, plus periodic patch releases and continuous app releases, according to a collaboratively planned roadmap.

    The annual prioritization process for this roadmap is an iterative, flexible, and continuously evolving process that broadly follows the following steps:

    1. Define strategic priorities: Strategic priorities reflect mid-long term goals for DHIS2 that can be advanced substantially over a period of ~3 years. They are in line with HISP UiO’s overall strategy and are not intended to change dramatically year over year. These priorities are informed by a process of gathering inputs within HISP UiO and the HISP Network.
    2. Define Objectives: Objectives specifically target high-level platform improvements that can be achieved in 1-2 years. They are refined through negotiation and prioritization, bringing in implementation, engineering, and product perspectives and taking into account day-to-day challenges and interactions with the overall DHIS2 community, and based on available resources, level of effort, and impact.
    3. Define Initiatives: Initiatives are time-bound, typically between 3 months and one release cycle. They have a finite scope and are the key operational level for making progress against one or more objectives. Initiatives are typically — but not always — composed of a multidisciplinary working group (implementation, product, and engineering). Initiatives result in features, performance improvements, implementation references, interoperability improvements. They are what defines the roadmap and where we get the work done!

    See the sections below for an overview of the DHIS2 software release cycle, a link to the current software roadmap, and guidance on how to contribute your input.

    DHIS2 software release cycle

    New versions of the core DHIS2 software are currently released on an annual cycle, while new versions of the Android application are released twice per year. Patch releases for supported versions are released on a periodic basis. In addition, feature updates to several core DHIS2 applications are released on a monthly basis through continuous delivery, allowing you to update these apps to the latest versions independently of the core software release cycle.

    Current roadmap for upcoming DHIS2 software releases

    Visit the Software Roadmap page for an interactive diagram showing the software features planned for upcoming DHIS2 core and Android software releases.

    Browse the Roadmap

    Share input and explore the software roadmap in more detail

    The DHIS2 software development team uses Jira to manage the DHIS2 roadmap and development process. Starting in 2024, we launched a new Jira project called DHIS2 roadmap where we aim to compile all the ideas submitted by the DHIS2 community, in a format that is separate from our traditional Jira features. We review and triage these ideas regularly, and use them as a source for building the roadmap when we are in phase 2 and 3 of the annual prioritization process (defining objectives and initiatives) as described above.

    In the DHIS2 roadmap project you can explore all proposed ideas in different views before submitting your own:

    You can also follow up the progress of the roadmap by exploring the prioritized ideas. Once a Roadmap idea is prioritized, we create the Jira features for development and link them to the related Roadmap ideas.

    Explore & Share Input

     

    Reporting of software bugs is handled through our old process. We ask that you first post a description and explanation of the bug on the DHIS2 Community of Practice, where the UiO team and other developers can review and provide feedback before you write the bug ticket on Jira.