Have you implemented OpenMRS? Please participate in the Implementation Site Survey. If you already have, thank you!
This page is a draft describing a version of OpenMRS that has yet to be released. We are adapting prior release notes for this new version; during this process some of the information may be incorrect or inconsistent.
Several months ago, the OpenMRS developer community decided that we needed a better release process. We agreed that we would aim to release OpenMRS twice a year, and the platform annually. Our goal was to release OpenMRS 2.1 by September 2014. We just barely missed that goal, but today, in early October, I'm happy to announce the release of OpenMRS 2.1!
This release doesn't bring many user-visible new features to the reference application (the Allergy functionality is nice!), but it has allowed us to focus on refactoring and automating our release process. And further, it gives us a chance to illustrate how an OpenMRS reference application release contains hundreds of under-the-hood improvements to modules that implementers and developers can leverage.
First, I'd like to give a special thanks to Cintia Del Rio, who contributed a huge amount to automating our module release processes, both by helping conceptualize the approach, by setting up bamboo plans, and by documenting the process. We should schedule time on a call to show the new approaches (automation is great!) and work through some last kinks (we have a lot of interdependent modules). Also, Mário Areias popped up out of nowhere to fix broken builds at odd hours just because he noticed them through CI emails, and Mark Goodrich did maven releases for me when I lost my nexus password.
I'd also like to thank Geoffrey Wasilwa, James Arbaugh, Alexis Duque, and Lluis Martinez for answering my last-minute calls for help and getting tickets done fast.
Feature highlights from OpenMRS 2.1:
OpenMRS 2.1 includes new versions of lots of modules. Some highlights of new features since OpenMRS 2.0:
Indeed, there is way more than I can describe here. See the Bundled Modules and Closed Issues section below.
As always, Daniel Kayiwa, Rafal Korytkowski, Wyclif Luyima, Burke Mamlin, Michael Downey, and the Infrastructure Team made big contributions that would take too long to enumerate.
Thanks to the complete list of code contributors to OpenMRS 2.1:
Alexis Duque, Andrew Szell, Angshuman Sarkar, Aniketha Katakam, Anton Kravchenko, Arathy-mac, Benjamin Wolfe, Burke Mamlin, Cintia Del Rio Calvo, Cosmin Ioan, Damian Szafranek, Damitha Kithmal, Daniel Kayiwa, Darius Jazayeri, Deepak N, Filip Biedrzycki, Geoffrey W Wasilwa, Gitahi Ng'ang'a, Glauber Ramos, Harsha Kumara, Hemanth, Jakub Kondrat, Kaweesi Joseph, Krzysztof Kaczmarczyk, Lech Rozanski, Lee Breisacher, Lukas Breitwieser, Madawa Soysa, Marek Szukalski, Mark Goodrich, Mihir, Mike Seation, Miss Beens, Mujir Shaikh, Mário Areias, Nehashri P L, Neissi Torres Lima, Nicholas Ingosi Magaja, Nyoman Ribeka, Pamela Canchanya, Paweł Muchowski, Przemyslaw Gierszewski, Radek Puzdrowski, Radoslaw Puzdrowski, Rafal Korytkowski, Rohan Poddar, Rowan Seymour, Saptarshi Purkayastha, Shruthi Dipali, Suraj Ponugoti, Sushmitha Rao, Vinay Venu, Vinkesh Banka, Wesley Spencer See, Willa Ahmed, Wyclif Luyima, hemanths, indraneelr, Łukasz Gąsior
|Module||Version in OpenMRS 2.1||Version in OpenMRS 2.0||Closed issues|
|Allergy API||1.0.1||not included||included in RA|
|Allergy UI||1.0||not included||included in RA|
|App Framework||2.2.1||2.1||see in JIRA|
|App UI||1.2.2||1.1||included in RA|
|Core Apps||1.4||1.2.1||included in RA|
|EMR API||1.4||1.1||see in JIRA|
|Form Entry App||1.0||not included||included in RA|
|HTML Form Entry||2.4||2.2.1||see in JIRA|
|HTML Form Entry Extensions for OpenMRS 1.9||1.4||same|
|HTML Form Entry UI Framework Integration||1.1||1.0||see in GitHub|
|ID Generation||2.9.1||2.7||see in JIRA|
|Metadata Deploy||1.2||not included||see in JIRA|
|OpenMRS UI Framework||3.2.1||same|
|Provider Management||2.2||2.1||see in JIRA|
|Reference Application (RA)||2.1.1||1.0.1||see in JIRA|
|Reference Demo Data (optional)||1.3||1.0||included in RA|
|Reference Metadata||2.1.1||1.1||included in RA|
|Reporting||0.9.2.1||0.8.1||see in JIRA|
|Reporting REST||1.3||not included|
|Rest Web Services||2.6.9 d2016||2.4||see in JIRA|
|UI Commons||1.3||1.2.1||see in JIRA|
|Story||RA-417||Roles and Privileges using Metadata Deploy|
|Bug||RA-403||Export concepts preserving IDs for OpenMRS 2.1|
|Story||RA-401||OpenMRS 2.1 should be based on OpenMRS Platform 1.10|
|Bug||RA-399||Error when you click to "Find Patient Record": Cannot format given Object as a Date|
|Story||RA-397||Top-level administrative apps|
|Story||RA-396||Include a "sysadmin" user in the demo data|
|Story||RA-393||Implementation-defined forms in Reference Application|
|Story||RA-392||Disable Awaiting Admission app|
|Story||RA-391||Remove reportingui from the refapp distro|
|Story||RA-390||Disable Patient Relationships with a feature toggle|
|Epic||RA-389||Create upgrade path from OpenMRS 2.0 to OpenMRS 2.1|
|Improvement||RA-387||Core Apps: Improve patient dashboard header to display multiple identifiers if exist for an extra patient identifier type|
|Bug||RA-380||Active Vists displays incorrectly in Firefox|
|Bug||RA-379||User session location is not updated when changed|
|Improvement||RA-378||Remove superfluous RA home heading|
|Story||RA-375||Include Atlas in OpenMRS Distribution|
|Improvement||RA-363||[Tech] Refactor app context model to be closer to our ideal representation|
|Story||RA-362||[Tech] fragment that includes and renders all extensions for an extension point|
|Story||RA-356||Find Patient app template in core apps should be configurable with breadcrumbs|
|Bug||RA-351||Fix Reference Metadata build|
|Story||RA-347||Tech Story: Add list of allergens and reactions|
|Bug||RA-343||Include Process HL7 task|
|Story||RA-328||Create static demo data for the reference application|
|Improvement||RA-324||Core Apps: EncounterDispositionTagHander: Admission disposition should not be allowed if a patient is already admitted|
|Improvement||RA-322||Core Apps module should not rely on the activeVisit being injected by the appui module|
|Epic||RA-304||Implementation-defined forms should be available through the RA user interface|
|Story||RA-271||Modules should be able to add content to the clinician facing patient dashboard|