Interested is participating in the Google Summer of Code program? Please see the GSOC wiki page.

Wiki Spaces

Documentation
Projects
Resources

Get Help from Others

Q&A: Ask OpenMRS »
Discussion: OpenMRS Talk »
Real-Time: IRC Chat

Documentation

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

Platform 2.1 (March 2017) 

Release Manager: Darius Jazayeri

Questions: Talk thread about whether this will be a non-LTS release

FeatureDescriptionStatusPoint of ContactComments
 Lucene Patient Search TRUNK-425 - Use Hibernate Search with Apache Lucene for Patient Searches Closed COMPLETED  
Additions to Lucene Patient Search TRUNK-5012 - Ability to limit lucene patient search by identifier to a particular identifier type Closed IN PROGRESS  
Various other features

Open: 11 issues

Resolved: 112 issues

IN PROGRESS  

Reference Application 2.6 (April 2017)

Release Manager: Collin Grimm

FeatureDescriptionStatusPoint of ContactComments
Add more Configurable Sections on the Clinical Facing Dashboard RA-1286 - Enable the creation of new sections on the Clinician Facing Dashboard In Backlog and RA-1258 - Support configurable dashboards out of the box In Backlog IN PROGRESSRafal Korytkowskihttps://issues.openmrs.org/secure/RapidBoard.jspa?rapidView=103&sprint=127
Responsive ability to the clinician facing dashboard RA-1285 - Make the clinician facing dashboard responsive using Twitter bootstrap Waiting for Analysis NOT DONE  
Ability to edit implementation formsEnable users to edit their custom forms. RA-435 - Need way to edit implementation custom forms In Development IN PROGRESSBurke 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. Run a report for a patient directly form the patient dashboard. RA-381 - Implementation-defined patient reports should be available through the RA user interface In Backlog
  2. Pre-built reports for Ref App. RA-1257 - Include Demo Reports with demo data In Backlog
  3. Ref App - Configurable dashboards out of the box. RA-1258 - Support configurable dashboards out of the box In Backlog
NOT DONEMike SeatonPatient summary module does not provide adequate configuration and doesn't work in Ref App.
Include more translations

Start automatically importing community-sourced translations from Transifex into all the Reference Application modules

RA-1000 - Automatically pull translations into modules as part of their release process Waiting for Test

IN PROGRESSDarius Jazayeri 
Enable visitless encounters: not requiring a visit to be created before an encounter can be entered EA-116 - Enable Encounters to be created without an existing visit Code Review (Post-Commit) COMPLETEDStephen Senkomago Musoke 
Sticky Note on the Patient Dashboard RA-1287 - Enable the ability to add a sticky note to the patient dashboard In Development NOT DONERomain Buisson 

 

Reference Application 2.7 (October 2017)

Release Manager: TBD

FeatureDescriptionStatusPoint of ContactComments
Core and modules to advertise capabilities that can be configured and manipulated RA-1292 - Enable modules and openmrs-core to advertise capability or functionality In Backlog NOT DONE Not started

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 - Support paging when fetching updates Ready for Work

 

Retrospective data entry

Basic support for retrospective data entry within the Reference Application

RA-68 - Retrospective data entry Waiting for Analysis


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 - Condition List V1 Ready for Work

See also: RA-209 - Condition List Waiting for Dev

  • RA-580 - Demonstrate condition lists working within OpenMRS 2.2 Waiting for Dev

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 - Ad Hoc Analysis tool (v1) Waiting for Dev

 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 - Avoid giving all API privileges to users In Backlog

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 - Support multiple classes per concept Ready for Work

NOT DONE

 
Anonymous Patients

Support for unnamed John Doe patients

RA-62 - Anonymous Patients In Backlog

NOT DONE

 

 
Test Patients

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

RA-65 - Test Patients In Backlog

 

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