Page tree
Skip to end of metadata
Go to start of metadata

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.7 (November 2017)

Release Manager: tendo kiiza Martyn

FeatureDescriptionStatusPoint of ContactComments
Google Summer of Code Projects
  1. Prebuilt Reference Application Reports - https://talk.openmrs.org/t/gsoc-2017-built-in-reports-for-reference-application-final-presentation/13079?source_topic_id=13309
  2. Metadata managament in AdminUI - https://talk.openmrs.org/t/gsoc-2017-more-metadata-management-in-admin-ui-final-presentation/13065?source_topic_id=13309
  Pending SDK upgrade to enable addition of OWAs to a distribution package
SDK Deploy of OWAsEnable SDK to deploy OWAs that are not included in modules SDK-225 - Getting issue details... STATUS IN PROGRESSRafal Korytkowski 
Add OWAs for Ref App
RA-1427 - Getting issue details... STATUS
IN PROGRESSRafal Korytkowskiwith support from Daniel Kayiwa
Biometrics Support in Registration App RA-1406 - Getting issue details... STATUS RA-1407 - Getting issue details... STATUS RA-1391 - Getting issue details... STATUS RA-1395 - Getting issue details... STATUS RA-1397 - Getting issue details... STATUS IN PROGRESSMike Seaton 
Sticky Note on the Patient Dashboard RA-1287 - Getting issue details... STATUS IN PROGRESSRomain Buisson 
Ability to edit implementation formsEnable users to edit their custom forms. RA-435 - Getting issue details... STATUS DONEBurke Mamlin and Daniel Kayiwa

Product owner  James Arbaugh.

xForms module currently provides this feature.

Pre-built Reporting Tools

This includes the ability to do several things.

  1. Pre-built reports for Ref App. RA-1257 - Getting issue details... STATUS see GSoc Project
  2. Ref App - Configurable dashboards out of the box. RA-1258 - Getting issue details... STATUS
DONEMike Seaton

 

Platform 2.2 (December 2017)

Release Manager: Irene Nyakate

FeatureDescriptionStatusPoint of ContactComments
Idgen

IDGEN-33 - Getting issue details... STATUS

IDGEN-42 - Getting issue details... STATUS

IN PROGRESSMike Seaton 
Encounter Diagnosis TRUNK-5015 - Getting issue details... STATUS IN PROGRESSDarius Jazayeri 
Add-On ManagementIncorporating module and OWA management into the PlatformIN PROGRESSDaniel Kayiwa 

Reference Application 2.8 (April 2018)

Release Manager: TBD

FeatureDescriptionStatusPoint of ContactComments
Responsive ability to the clinician facing dashboard RA-1285 - Getting issue details... STATUS NOT DONE  
Core and modules to advertise capabilities that can be configured and manipulated RA-1292 - Getting issue details... STATUS NOT DONE Not started
Pre-built Reporting Tools

This includes the ability to do several things.

  1. Run a report for a patient directly form the patient dashboard. RA-381 - Getting issue details... STATUS
IN PROGRESSMike 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.

Add Patient Flags Module NOT DONE Still under development
MPI enhancements to Registration App and Registration CoreProduction quality integration with OpenEMPI using HL7 v3 PIX/PDQ messaging standardsIN PROGRESSCraig A 

Reference Application Someday

FeatureDescriptionStatusPoint of ContactComments
     
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)

BETA

 

Nicholas Ingosi and Rafał Korytkowski

OCLM-24 - Getting issue details... STATUS

 

Retrospective data entry

Basic support for retrospective data entry within the Reference Application

RA-68 - Getting issue details... STATUS


NOT STARTED

 

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

IN DESIGNBurke 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.

IN DESIGNRafal 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)

EA-40 - Getting issue details... STATUS

See also: RA-209 - Getting issue details... STATUS

  • RA-580 - Getting issue details... STATUS

IN PROGRESS

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

 

Ad Hoc Analysis tool (v1)

 Incorporate new cohort definition tool.

RA-261 - Getting issue details... STATUS

 STALLED

 

Darius Jazayeri 
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

RA-341 - Getting issue details... STATUS

NOT DONE

 

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 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.NOT DONE  

Platform Someday

FeatureDescriptionStatusComments
Multiple concept classes per concept TRUNK-4540 - Getting issue details... STATUS

NOT DONE

 
Anonymous Patients

Support for unnamed John Doe patients

RA-62 - Getting issue details... STATUS

NOT DONE

 

 
Test Patients

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

RA-65 - Getting issue details... STATUS

 

NOT DONE

 

 
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