What is the OpenMRS Technical Road Map?

The Technical OpenMRS Road Map 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 road map milestones are chosen and prioritized, see the Technical Road Map Planning page.


Milestones

Reference Application 2.8 (April 2018)

Release Manager: Juliet Wamalwa

FeatureDescriptionStatusPoint of ContactComments
Condition ListsSupport for condition lists in the reference application

See this Talk thread
Program Dashboards

Mark GoodrichSee this Talk thread.

Platform 2.2 ( June 2018)

Release Manager: Samuel Male and Irene Nyakate

FeatureDescriptionStatusPoint of ContactComments
Idgen

Mike Seaton / Mark Goodrich

2018-01-22: Design Forum discussion on 2017-08-21.

2018-02-05: IDGEN-33 getting close. Daniel will assign Andela dev for IDGEN-42.

Encounter Diagnosis

 2018-01-22: Waiting for developer.

2018-02-05: Daniel planning on breaking task down into smaller tasks for Andela, assuming DHIS2 sprint is not yet ready. Also has been proposed for GSoC 2018 as backup.

Provider Roles

Darius Jazayeri

Mark Goodrich

2018-01-22: Assigned to Denis Wokanya, but no recent activity in JIRA. Daniel will check on status.

2018-02-05: Daniel planning on breaking task down into smaller tasks for Andela

Creatable, Changeable interfaces

Wyclif Luyima


Program Enrollment Attributes

Daniel Kayiwa, Steven Musoke

2018-02-05 : Brian Njenga working on this. Almost done.
Bundle addon manager owa

Rafal, Daniel2018-02-05: Being actively worked on by Andela.

Reference Application Someday

FeatureDescriptionStatusPoint of ContactComments
Add Order Entry UIAdd some sort of user interface for doing order entry.
Wyclif LuyimaWe 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 CoreProduction quality integration with OpenEMPI using HL7 v3 PIX/PDQ messaging standards
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.

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)

 

 

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 , ...).

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.

 

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:

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 testsBasic ordering of meds and tests "out of the box" in Reference Application.

 

Ad Hoc Analysis tool (v1)

 Incorporate new cohort definition tool.

 

 

 
Concept Management ImprovementsAllow 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

 

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 ManagementWould 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

FeatureDescriptionStatusComments
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 EncounterRecord the entire clinical transaction piece-by-piece as part of a Session, as opposed to via a Form.  
Patient Listse.g. "My Patients", "Inpatients on Service XYZ", etc. (Related to RA-202.)  
Program Enrollmentsv1: capturing this data; v2: drive available forms/actions based on program state