What is the OpenMRS Technical Roadmap?

The Technical OpenMRS Roadmap is a set of milestones for our Platform, Reference Application, community-sponsored modules, and related tasks that help us meet the needs of our implementations.

For information about how the roadmap milestones are chosen and prioritized, see the Technical Roadmap Planning page.


Platform 2.3 ( June 2019)

Release Manager:   Nathan Ruhanga  Release Mentor: Samuel Male

Operational Strategic Stretch Goal: Commence discussions on how to include decision support ; Output being a strategy paper with possible options




Point of Contact



REST resource for Creating Order Group

Need to ask product owner if they are still interested in continuing @ Yusuf Akhond


Upgrade our libraries

 Review of the palm file to better understand which libraries need upgrading; i.e. what libraries do we have and what is the latest for that version.

We could write a maven command that can generate a report with libraries that need updating. From there we can determine what level of effort will be required to upgrade the library.


Bundle addon manager owa

Need dev to do final testing. If we can find dev in the community, great; otherwise, Daniel will do.


7Adopting OpenJDK

May need to get feedback from the community on whether they have used OpenJDK and whether it is stable enough

Review the CI build to determine if it can run on OpenJDK

8Support for alternate authentication schemes

  • To include in the release notes . Already merged but should be noted.
9Use of the new Implementation ID server URL, and support for redirects & https in the custom HttpClient class

Release Manager:  TBD
Platform 2.4 ( TBD 2019)

Operational Strategic Goal: Commence discussions on how to include decision support ; Output being a strategy paper with possible options




Point of Contact


Order Templates


Jonathan Dick

Reference Application 2.10 (TBD 2019)

Ongoing talk post for roadmap planning

Optional Features for consideration in Ref 2.10:




Point of Contact



Offline Capability


Developing an upward/backward migration path


Reference Application 2.9 (April 2019)

Release Manager:  Reuben Varghese




Point of Contact


Reference Application

Stephen Senkomago Musoke

  • These issues have had their respective PRs merged.

  • They need to be tested thoroughly before being marked as complete.

  • Instructions for testing will be posted soon.

Platform 2.2 (March 2019)

Release Manager: Samuel Male and Irene Nyakate




Point of Contact



Mike Seaton / Mark Goodrich

IDGEN-42 was being worked on by Daniel Kayiwa, but he is busy with multitasking, so we need to find someone to take this on.

tendo kiiza Martyn picked it up and is working on this Issue

Samuel Male planning to help Tendo finish the ticket after exams (tomorrow)

Encounter Diagnosis


Daniel Kayiwa closed this ticket after all work on it was done.

Provider Roles

Mark Goodrich

Finished by Wyclif Luyima and a followup ticket created as RA-1174 for the remaining work in the reference application.

Creatable, Changeable interfaces

Wyclif Luyima

Program Enrollment Attributes

Daniel Kayiwa, Steven Musoke

Daniel Kayiwa made a followup commit for the remaining minor issues.

Bundle addon manager owa

Daniel Kayiwa

Need dev to do final testing. If we can find dev in the community, great; otherwise, Daniel will do.

Reference Application Someday




Point of Contact


Add Order Entry UI

Add some sort of user interface for doing order entry.

Daniel Kayiwa

We could polish up the orderentryui module, or do an OWA from scratch. Whichever we find easier.

Add Patient Flags Module

Still under development

Responsive ability to the clinician facing dashboard

Core and modules to advertise capabilities that can be configured and manipulated

Not started

MPI enhancements to Registration App and Registration Core

Production quality integration with OpenEMPI using HL7 v3 PIX/PDQ messaging standards

Nathaelf Hyppolite

Discussion on talk.

Pre-built Reporting Tools

This includes the ability to do several things.

  1. Run a report for a patient directly form the patient dashboard.

Mike Seaton

Patient summary module does not provide adequate configuration and doesn't work in Ref App.

27-March: We could include Reporting REST documentation that Darius Jazayeri and the Andela team have done.

OCL subscription module

Using KenyaEMR as a use case, create a tool for subscribing an OpenMRS instance to a dictionary (e.g. the CIEL dictionary)

Nicholas Ingosi and Rafa? Korytkowski

Retrospective data entry

Basic support for retrospective data entry within the Reference Application

Needs a user centric story - add to existing ticket

OpenMRS Web Framework

From discussions in #MOZ15, we would like for the OpenMRS Platform to evolve toward providing a web framework that allows developers to add functionality using standard development tools (e.g., HTML5 + JavaScript against REST services, AngularJS apps, OWA , ...).

Burke Mamlin

Ranking REST tickets on 5 Aug design call.

Burke Mamlin and Darius Jazayeri discussed 24-July-2015 and Darius will make a Talk topic to move this forward.

Bahmni technical deep dive scheduled for 4 June Developers Forum.

17 June design forum will discuss progress (coordinating various efforts). As well as look at how to make REST services more robust. Darius still working w/ Bahmni on fundamental pieces of their web framework to pull into OpenMRS (will talk about this on future call).

25 June dev forum on REST web services: how to substantially improve them W/ Burke Mamlin & Darius Jazayeri

Vertical Packaging

OpenMRS has a lot of flexibility and extensibility with a central concept dictionary, RBAC, forms, reports, modules, and apps; however, it's not always easy to know which metadata goes with which functionality. The goal of vertical packaging is to define best practices for managing and relating all of the components (metadata & behavior) that work together to solve a particular problem within OpenMRS. Eventually, we envision a way that someone could easily add the MDRTB package to their OpenMRS implementation to begin treating MDRTB patients... or upgrade their Oncology package, etc.

Rafal Korytkowski

Need to look at the design we had and see if we can get it in 2.3

Burke Mamlin to share first draft of metadata mapping design on Talk.

First step will be to add ability to map metadata, 22 June design forum

Discussed on 20 May design forum.

Condition List

Manage & view patient problems (e.g., on the patient dashboard and integrated with diagnosis capture)

See also:

see Condition List board

Daniel Kayiwa

Ravinder Kumar

Daniel took a look at condition list to see what we need to do to get the API in 2.3 and believes if we do not get volunteers on admin sprint then condition list will not be ready.,

13 April WIP given on design call

1 June design forum to define how encounter diagnoses should work with conditions (and condition list).

Talked w/ Bahmni BA (Saranya) about use cases and requirements on 15 June design forum

Basic Order Entry for meds and tests

Basic ordering of meds and tests "out of the box" in Reference Application.

Ad Hoc Analysis tool (v1)

 Incorporate new cohort definition tool.


Concept Management Improvements

Allow for concept merging and easier browsing through concepts and references terms without losing frame of reference.

Improvements to Permissions (technical implementation)

Avoid giving all API privileges to users

Burke Mamlin

Needs discussion and design

Would like input from implementations, PIH (Mark, Mike, David) AMPATH, Kenya EMR, BAMI/JSS

Need to reach out for inputs!

Kiran has started helping with this

Provider Management

Would include provider types and ability to retire the old provider management module. Will remove UI library module once provider management is in the core.

Platform Someday





Multiple concept classes per concept

Anonymous Patients

Support for unnamed John Doe patients

Test Patients

Support for tagging & recognizing test/fake patients, so they can be ignored within reports.

Decision Support (v1)

The first trivial example of providing decision-support feedback (includes significant design and back-end discussions)

Clinical Encounter

Record the entire clinical transaction piece-by-piece as part of a Session, as opposed to via a Form.

Patient Lists

e.g. "My Patients", "Inpatients on Service XYZ", etc. (Related to RA-202.)

Program Enrollments

v1: capturing this data; v2: drive available forms/actions based on program state