Release Notes 2.0

On this page:

Introducing OpenMRS 2.0

Release date: 26 February 2014

Today, our community is excited to announce the release of OpenMRS 2.0. This is quite a milestone for us, and we’d like to explain what it means:

  • We’re more than just a platform. OpenMRS 2.0 release brings a new focus to OpenMRS. Instead of just releasing a generic enterprise-grade platform and leaving it up to each implementation to configure, OpenMRS 2.0 includes more functionality “out of the box” that should help you be more productive, faster.
  • Patient Summary view for clinicians.
  • Visit view for data clerks.
  • Vital Signs capture, including support for a standalone vitals workstation.
  • Diagnosis capture, supporting coded/non-coded, confirmed/presumed, and primary/secondary diagnoses.
  • Outpatient vs. Inpatient statuses.
  • Multiple wards/services in a facility.

What hasn’t changed: OpenMRS 2.0 is still built on our familiar OpenMRS Platform, including OpenMRS API 1.9.7 and REST web services. We’re building on a decade of experience and effort from around the world to make sure our software is reliable and has a wide and deep support system.

What HAS changed: OpenMRS 2.0 features a completely new and modern user interface, built from scratch to be much more user friendly. Our new UI is still in its early days, so you may find some missing features. We will be continually improving the UI with your help and feedback. For example: in OpenMRS 2.1, we’ll let you add your own forms without having to write a module and we’ll include some pre-built reports along with an ad-hoc query tool. But we think it’s important to show the direction OpenMRS is moving, so current and future implementations can start planning around these changes. For more information on upcoming features, see the Road Map wiki page for OpenMRS 2.0.

You can download OpenMRS 2.0 from our downloads page using one of these options:

  • OpenMRS 2.0 Standalone, recommended for new people exploring OpenMRS. A self-contained ZIP archive that includes an embedded database and application server, as well the option to install demo data, so you can quickly test out the new system.
  • OpenMRS Enterprise WAR package and a 2.0 Modules ZIP archive, for upgrading an existing implementation to 2.0, or for mixing and matching modules.

Please visit our implementer documentation to learn more about how to setup and use OpenMRS 2.0.

Darius Jazayeri

Additional Technical Details

  • Everything is built using reusable components on top of our new App Framework module that lets you build small “apps” using multiple technologies, including the OpenMRS UI Framework, HTML+JavaScript+REST, and the more traditional traditional Spring MVC.
  • A higher-level, more opinionated EMR-related APIs in the EMR API module, and a new “encountertransaction” REST web service that lets clients build an encounter in real-time, by making multiple submissions, with improved semantics.
  • A core set of configurable apps in the Core Apps module.
  • A reference set of concepts, encounter types, etc in the Reference Metadata module.

You can leverage some or all of these technologies to build your own OpenMRS distribution. Learn more about developing for OpenMRS 2.x.

Bundled Modules

  1. App Framework v. 2.1
  2. App UI v. 1.1
  3. Calculation v. 1.1
  4. Core Apps v. 1.2.1
  5. Data Exchange v. 1.1
  6. EMR API v. 1.1
  7. Event v. 2.1
  8. HTML Form Entry 1.9 Ext v. 1.4
  9. HTML Form Entry v. 2.2.1
  10. HTML Form Entry UI v. 1.0
  11. HTML Widgets v. 1.6.5
  12. ID Gen v. 2.7
  13. Logic v. 0.5.2
  14. Metadata Mapping v. 1.0.1
  15. Metadata Sharing v. 1.1.8
  16. Name Phonetics v. 1.4
  17. Provider Management v. 2.1
  18. Reference Application v. 1.0.1
  19. Reference Metadata v. 1.1
  20. Registration App v. 1.0
  21. Registration Core v. 1.0
  22. Reporting v. 0.8.1
  23. Serialization XStream v. 0.2.7
  24. UI Commons v. 1.2.1
  25. UI Framework v. 3.2.1
  26. UI Library v. 2.0.4
  27. Webservices REST v. 2.4

Resolved Issues

type key priority summary

Unable to locate Jira server for this macro. It may be due to Application Link configuration.


A huge thanks to the 114 people that have contributed to the code base and helping us to get this far:

Individual IT Services

Indraneel Rao

Mr. Marvin

Vatsal Singhal