Through OpenMRS 1.9, the user interface for OpenMRS got little attention. The majority of the user interface comprised administrative functions and a tabbed patient dashboard. As of OpenMRS 2.0, a new and more contemporary UI was introduced via a UI framework and the legacy UI was kept around for administrative functions that were not yet implemented in the new UI. While we plan to retire the legacy UI by the end of the summer 2015, there are many implementations and modules that still rely on it. In order to maintain backwards compatibility, we want to move the legacy UI functions into a module that these implementations can install until they are able to migrate away from it. Since most of the implementations of OpenMRS around the world are running OpenMRS 1.9, there will be dozens (if not hundreds) of implementations around the world thankful for this module.
Here is the module page
If you visit demo.openmrs.org (username: admin, password: Admin123):
click on the System Administration app on the main dashboard:
and then click the Advanced Administration app, you'll see the legacy administration UI:
From the header on this legacy administration UI, you can click on the Find/Create Patient, Dictionary, and Reporting links in the header to see the legacy patient search, legacy concept dictionary management, and legacy reporting UIs:
Finally, if you search for a patient in the legacy Find/Create Patient page (e.g., "smith" and select first entry), you'll see the legacy Patient Dashboard:
These pages (legacy patient dashboard, patient search, dictionary, reporting, and administration) and the extension hooks they provided represent the majority of OpenMRS' legacy UI. Looking under the hood, you would find that several of these (patient dashboard, dictionary management, and reporting) are already hooking into a legacy home page that provides the basic structure used by all of these pages and is hidden (replaced with the new home page) in OpenMRS 2.0+. Creating a module that includes the legacy home page structure and supports the legacy approach to web page extension points will be the bulk of the work involved in this project. Once that is achieved, then you should be able to migrate most of the code for the legacy UI into it without making major changes to the code.