Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 120 Current »


2019 OpenMRS Community RoadMap V1


Jan2019FebMarAprMayJunJulAugSepOctNovDec2.9.12.2.1
Ref App 2.9.x
Platform 2.2.x
PM/Operational
OMRS V3.0

Testing & Release

2.9 Official Launch

Feature review and confirmation for next release

Development of Features

Testing & Release

2.9.1 Official Launch

Complete Dev Commence Testing

2.2 Official Launch

Development of Features

Testing & Release

Feature review and confirmation for next release

2.2.1 Official Launch

Testing & Release

Define Requirements Gathering Process

Identify New Tickets for Dev

Establish a Design Team

Establish and Formalise PAT

Identify Release Managers

Identify a way to do Automated Testing

Identify a QA Team

Confirm and Ensure Documentation of Previous Release Process

Identify a way to harvest modules into RefApp

Greater Support for Implementation

Update & Improve Documentation

Easier installation and updates.

Common application that is built for scale

Broadened functionality and new technologies



We're playing with a new format for the road map... so don't believe anything you see here.  Use the Road Map page instead.


The OpenMRS Road Map is a set of milestones not only for the core OpenMRS platform, but also for core and sponsored modules as well as 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 Roadmap Planning page.

For information about ongoing development tasks, see the Sprint Schedule page.

 

Milestones

Work needed during quarter

2013 Q1

 


2013 Q2

 

 

2013 Q3

OpenMRS 1.10 (June 2013)

  • Order Entry API
  • ...


2013 Q4

OpenMRS 2.0 (Oct 2012)

  • A new UI!
  • ...

 

2014 Q1

 

 

2014 Q2


 

OpenMRS Someday

Features planned for the future.  Once these have been designed, they will be attached to a milestone

Feature

Status 

Completion Status

Sessions (Encounter Transactions)IN DESIGN

Metadata Mapping (Design Page)

 

 

 

Common or Centralized Approach to Tagging

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

 

 

[ARCHIVED] Handling Observation Exceptions (Design Page)  

Concept Class Hierarchy

 

 

 

Support for DME Supplies  

Cohort-level Encounters and Observations

 

Improved State Machinery (Design Page)

TRUNK-2995 - A Program work flow should provide the transition order of its states Closed

Episodes of Care and Protocols

IN DESIGN

Support for Care Settings 

 

 

Form Model improvements

 

Support for person_identifier

 

Separating organizational from privilege-related roles

 

Contact Information On Persons


Support for Clustering

TRUNK-314 - Investigate about support for Servlet Container Clustering Closed
Support for Drug Formularies Unable to locate Jira server for this macro. It may be due to Application Link configuration.

 

 

Support external master registries of Patient, Location, Provider, Concept, and other metadata

TRUNK-1991 - Support external master registries of Patient, Location, Provider, Concept and other metadata Closed

Centralized Auditing (Design Page)

 

 

 

Support for Structured Numerics

TRUNK-413 - Implement the Structured Numeric datatype Closed

Event Bus for OpenMRS (enterprise-quality event messaging)

 

  • No labels