Wiki Spaces

Documentation
Projects
Resources

Get Help from Others

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

Documentation

Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

What is the OpenMRS Technical Road Map?

Excerpt

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.

Table of Contents

Milestones

Platform 1.11.4 (maintenance release to support Reference Application 2.3 in September 2015)
Release Manager: Daniel Kayiwa

FeatureDescriptionStatusPoint of ContactComments
REST Module and other module upgrades

Latest version of web services module(s).

Status
colourGreen
titledone
  


Reference Application 2.3 (September 2015)
Release Manager: Unknown User (tharunya)

FeatureDescriptionStatusPoint of ContactComments
Administrative functions

Basic administrative functions should be added to the OpenMRS 2.x UI.

Jira
serverOpenMRS JIRA
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyRA-61

Open tickets labeled as "adminui" in JIRA:

Jira
serverOpenMRS JIRA
jqlQuerylabels = adminui and status not in (Closed, Accepted, Cancelled)
counttrue
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95

Status
colourGreen
titledone
Wyclif Luyima

Admin UI module will be released by 16 September.

Support for MariaDB

Our CI system should be testing against MariaDB as well as MySQL.

Jira
serverOpenMRS JIRA
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyTRUNK-4689

Status
colourYellow
titlein progress
 

Unknown User (lluismf) and Cintia Del Rio are discussing how to get CI set up, Talk discussion here.

Platform 2.0 (Q4 2015)
Release Manager: Unknown User (maany)

FeatureDescriptionStatusPoint of ContactComments
Java 8 support

Starting with OpenMRS 2.3, OpenMRS will be built against Java 8 and begin using Java 8 language features, which means that OpenMRS 2.3+ will require Java 8+ to run.

Jira
serverOpenMRS JIRA
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyTRUNK-4550

 

Status
colourGreen
titleDONE
Wyclif Luyima 
Upgrade Underlying Technologies

Upgrade to the latest version of underlying technologies

  • Spring 4.x
    Jira
    serverOpenMRS JIRA
    serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
    keyTRUNK-4584
  • Hibernate 4.x
    Jira
    serverOpenMRS JIRA
    serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
    keyTRUNK-4364
Status
colourGreen
titledone
Unknown User (raff)

Spring 4 changes have been merged into master.

22 June design forum Unknown User (raff) and Unknown User (kristopherschmidt) joined to discuss Hibernate upgrade.

Will plan sprint to help module authors with preparing for Platform 2.0 following the Reference Application 2.3 release.

FHIR Support

FHIR web services should be added to the platform to run alongside the OpenMRS REST web services.

See OpenMRS FHIR Module

Status
colourGreen
titledone

 

Unknown User (surangak)

Version 0.9.1 released.

May include toggle for diagnostic reports by the time Platform 2.0 is released.

Remove Legacy UI

The legacy UI should be moved to a module.

See Migration of Legacy UI to the module

Status
colourYellow
titlein progress
Unknown User (tharunya)

Planning on migrating Legacy UI to OpenMRS org and changes into core.

Plan a sprint after Ref App 2.3 has been released and the dust settles.

Allergies in core

Allergies were introduced with Reference Application 2.2. We will bring them into the core platform with 2.0 (and remove the old, largely unused allergy support).

Jira
serverOpenMRS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyTRUNK-4747
Status
colourYellow
titlein progress
Unknown User (jdegraft)Aiming to include in alpha release if possible (i.e., by 15 Oct)
Remove problem lists

Problem lists will eventually be replaced with condition lists (likely initially introduced via a module and later migrated to core), so the old "active lists" design needs to be removed from core.

Jira
TRUNK-4749
TRUNK-4749

Status
colourYellow
titlein progress
Daniel Kayiwa 
Remove deprecated methodsMoving to Platform 2.0 is an opportunity to clean house and remove deprecated methods.
Status
colourRed
titlenot started
TBD

We will choose an owner for this over the next week. See this Talk topic.

Reference Application 2.4+

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

Status
colourYellow
titleIN DESIGN
Burke Mamlin

Ranking REST tickets on 5 Aug design call.

Burke Mamlin and Unknown User (darius) 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

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)

Status
colourYellow
titleBETA

 

Unknown User (ningosi) and Rafał Korytkowski

Jira
serverOpenMRS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyOCLM-24

 

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.

Status
colourYellow
titleIN DESIGN
Unknown User (raff)

 

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)

Jira
EA-40
EA-40

See also:

Jira
serverOpenMRS JIRA
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyRA-209

  • Jira
    RA-580
    RA-580

Status
colourYellow
titlein progress

see Condition List board

Daniel Kayiwa

Unknown User (ravinder)

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.
Status
colourYellow
titleIN DESIGN
Unknown User (darius)

 

Integrating Multiple ServersMany of our implementations are struggling with the problem of coordinating data and workflow across multiple OpenMRS servers (e.g., sharing data, patient transfers, remote management, supporting an external MPI).  PIH will be working on this, so we'd like to maximize the extent to which that effort can benefit everyone.
Status
colourYellow
titlein design
 

Discussed with PIH and Unknown User (rcrichton) on 14-Jan design call. Ryan sent some links. PIH is considering options.

Ad Hoc Analysis tool (v1)

 Incorporate new cohort definition tool.

Jira
serverOpenMRS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyRA-261

 

Status
colourYellow
titleIn Progress

 

Unknown User (darius) 
Reporting Improvements    
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

Jira
serverOpenMRS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyRA-341

Status
colourRed
titleNOT 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

 

Retrospective data entry

Basic support for retrospective data entry within the Reference Application

Jira
serverOpenMRS JIRA
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyRA-68


Status
colourRed
titlenot started

 

Unknown User (darius) Needs a user centric story - add to existing ticket

Account Manager

Manage your users & providers, including roles & privileges, disable accounts, etc.

Jira
serverOpenMRS JIRA
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyRA-61

Status
colourRed
titleNot started

 

 Implemented in Mirebalais. Needs design review and porting to RefApp codebase

Someday

FeatureDescriptionStatusComments
Multiple concept classes per concept
Jira
serverOpenMRS JIRA
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyTRUNK-4540

Status
colourRed
titlenot done

 
Anonymous Patients

Support for unnamed John Doe patients

Jira
serverOpenMRS JIRA
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyRA-62

Status
colourRed
titlenot done

 

 
Clinician Facing Patient Dashboard (v2)

Patient summary and dashboard designed for doctors and nurses

Jira
serverOpenMRS JIRA
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyRA-212

Status
colourRed
titlenot done

 

 
Merge Patients

Merge duplicate patient records into one.

Jira
serverOpenMRS JIRA
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyRA-63

 

Status
colourRed
titlenot done

 

 
Test Patients

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

Jira
serverOpenMRS JIRA
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyRA-65

 

Status
colourRed
titlenot done

 

 
Patient Lookup (v2)

Search for a patient by name or ID

Jira
serverOpenMRS JIRA
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyRA-224

Status
colourRed
titlenot done

 

 
Simple Dispensing

A form to record medication dispensing events within the patient record

Jira
serverOpenMRS JIRA
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyRA-87

Status
colourYellow
titlein design

 

 
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  
Easy Chart Review / FlowsheetsReviewing the patient's whole electronic record for data points of interest (also has been called "Chart Search")