Wiki Spaces

Documentation
Projects
Resources

Get Help from Others

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

Documentation

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

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.

Table of Contents

Milestones

Platform 2.4 (Fall 2020) - Theme: Upgrading the stack

Lots of under-the-hood updates to have more modern tech stack. 

Release Manager:  CLIFF GITA, with mentorship from Kaweesi Joseph and Nathan Ruhanga, and support from Herbert Yiga

Feature

Description

Status

Point of Contact

Comments

Upgrade FHIR

Replace original fhir module with fhir2 module with support for FHIR R4

IN PROGRESS


Upgrade SpringUpgrade to Spring 5.2.7

DONE


Upgrade HibernateUpgrade to Hibernate 5.4.18

DONE


Support Java 8 - 14Add support for Java 9, 10, 11, 12, 13, 14 while not losing support for Java 8

DONE


Upgrade Liquibase

Upgrade to Liquibase 3.10.1 and Avoid running legacy liquibase changesets

DONE


Upgrade Other LibrariesUpgrade a number of other underlying libraries. e.g Log4j 2, JUnit 5, etc

DONE


Support PostgreSQLAdd support for PostgreSQL versions 8.2 up to the latest 12

IN PROGRESS


Support MySQL 5.6 - 8.0Add support for all MySQL versions from 5.6 to the latest 8.0

DONE


Reference Application 2.11 (Fall 2020 - date TBD) - Theme: TBD

Release Manager: Sharif Magembe, with mentorship from tendo kiiza Martyn and Moses Mutesasira (TBD, to have additional mentors/support as with platform release above)

High-level goals: Updating modules, bug fixes, incorporation of micro frontend module (without production implications)

Important note: must be backwards compatible, so only module versions that are compatible with >=2.3.

Feature

Description

Status

Point of Contact

Comments






Release Calendar

How to update this calendar

List View

  1. EDIT THE CALENDAR

    Customise the different types of events you'd like to manage in this calendar.

    #legIndex/#totalLegs
  2. RESTRICT THE CALENDAR

    Optionally, restrict who can view or add events to the team calendar.

    #legIndex/#totalLegs
  3. SHARE WITH YOUR TEAM

    Grab the calendar's URL and email it to your team, or paste it on a page to embed the calendar.

    #legIndex/#totalLegs
  4. ADD AN EVENT

    The calendar is ready to go! Click any day on the calendar to add an event or use the Add event button.

    #legIndex/#totalLegs
  5. SUBSCRIBE

    Subscribe to calendars using your favourite calendar client.

    #legIndex/#totalLegs

Calendar View

  1. EDIT THE CALENDAR

    Customise the different types of events you'd like to manage in this calendar.

    #legIndex/#totalLegs
  2. RESTRICT THE CALENDAR

    Optionally, restrict who can view or add events to the team calendar.

    #legIndex/#totalLegs
  3. SHARE WITH YOUR TEAM

    Grab the calendar's URL and email it to your team, or paste it on a page to embed the calendar.

    #legIndex/#totalLegs
  4. ADD AN EVENT

    The calendar is ready to go! Click any day on the calendar to add an event or use the Add event button.

    #legIndex/#totalLegs
  5. SUBSCRIBE

    Subscribe to calendars using your favourite calendar client.

    #legIndex/#totalLegs

Someday

Reference Application Someday

Feature

Description

Status

Point of Contact

Comments

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


NOT DONE


Still under development

Responsive ability to the clinician facing dashboard

RA-1285 - Getting issue details... STATUS

Accepted



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

RA-1292 - Getting issue details... STATUS

NOT DONE


Not started

MPI enhancements to Registration App and Registration Core

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

IN PROGRESS

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. RA-381 - Getting issue details... STATUS

IN PROGRESS

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)

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



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

IN DESIGN

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.

IN DESIGN

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)

EA-40 - Getting issue details... STATUS

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

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

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.

STALLED



Ad Hoc Analysis tool (v1)

 Incorporate new cohort definition tool.

RA-261 - Getting issue details... STATUS

 STALLED




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

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

NOT DONE



Platform Someday

Feature

Description

Status

Comments

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