OpenMRS Worldwide Summit is fast approaching!

#OMRS15, the 1st OpenMRS Worldwide Summit, is 8-14 December. Registration is open & session ideas are being accepted. More information:

Wiki Spaces


Get Help from Others

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


Skip to end of metadata
Go to start of metadata

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 Road Map Planning page.

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



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



Completion Status

Sessions (Encounter Transactions)IN DESIGN      
Handling Observation Exceptions  
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 Ready for Work


Episodes of Care



Form Model improvements



Support for person_identifier

In early design


Separating organizational from privilege-related roles



Contact Information On Persons

Project described


Metadata Mapping (Design Page)



Support for Clustering

TRUNK-314 - Investigate about support for Servlet Container Clustering Closed       

Centralized Auditing (Design Page)



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 Design       

Support for Structured Numerics

TRUNK-413 - Implement the Structured Numeric datatype Design       

Event Bus for OpenMRS (enterprise-quality event messaging)



Common or Centralized Approach to Tagging

TRUNK-2284 - Common tagging mechanism for openmrs objects Design       

Concept Class Hierarchy


Support for Care Settings       
Support for Drug Formularies TRUNK-4535 - Support formulary status for drugs Ready for Work       
  • No labels