Have you implemented OpenMRS? Please participate in the Implementation Site Survey. If you already have, thank you!
Skip to end of metadata
Go to start of metadata

AdminUI Module completion

Primary mentor

Daniel Kayiwa

Backup mentor


Assigned to



Some initial work was done to move metadata management to the admin ui module for the reference application to end up with the links on this page: http://qa-refapp.openmrs.org/openmrs/adminui/metadata/configureMetadata.page. There is still some more functionality that needs to be moved over. The goal of this is to ensure that one can comfortably run the reference application without requiring the legacyui module for metadata management. You will see the management links for the legacy ui from http://qa-refapp.openmrs.org/openmrs/admin/index.htm 

For the initial work done, you can take a look at these tickets.

Required Skills

  • Strong Java skills
  • CSS, HTML, AngularJS
  • Familiarity with the OpenMRS API
  • Familiarity with the OpenMRS REST API
  • A basic understanding of the old legacy ui of openmrs.


We need to implement the following functionality in the adminui module:

  • Managing encounters
  • Manage Observations
  • Manage Scheduler
  • Manage Programs
  • Manage Triggered State Conversions
  • System Information
  • Manage Modules
  • Complete the module wiki documentation


Present Project Wiki: Admin UI Module

Github codebase: https://github.com/openmrs/openmrs-module-adminui

Project Tickets: https://issues.openmrs.org/browse/RA/

AdminUI Talk post: https://talk.openmrs.org/t/admin-ui-sprint-what-is-high-priority/2257

AdminUI sprint kick off meeting: