Page Comparison

Background

OpenMRS is a highly-configurable system, with lots of generic functionality. The advantage of this is that it's a very powerful and flexible system, but it does have a cost too: using OpenMRS requires defining a large quantity of metadata. After installing OpenMRS, a system administrator will typically have to create Locations (e.g. "Harborview Hospital"), Encounter Types (e.g. "Outpatient Consultation"), and even concepts (e.g. "Weight" and "Hematocrit").

...

The Metadata Sharing Module, originally written during GSoC 2010 lets an administrator select a set of metadata, and it generates an export "package" of those metadata and all their dependencies as a zip file. That zip file can be manually shared with other OpenMRS users. So our hypothetical Malaria treatment program could share its metadata package with other projects interested in replicating their program.

Purpose

Domain Expert(s) / User(s)

• Andy Kanter
• Ellen Ball

Required Skills

• Strong Java skills
  • You will need to understand and add to the Metadata Sharing module's codebase: https://source.openmrs.org/browse/Modules/metadatasharing/trunk
• Familiarity with REST web services

Objectives

1. Implement a workflow that allows metadata packages to be tagged with a version number, and make it easy to create a new version starting from an existing one.
2. Allow an OpenMRS installation to publish packages, with:
   • Name
   • Version number
   • Publishing authority (e.g. "WHO")
   • What URL to check for updates
3. Allow an OpenMRS installation to subscribe to a published package, either by uploading a zip file or entering a URL.

Deliverables

1. Package subscription
2. Package publishing
3. Creation of versioned packages
4. Automatic notifications about package updates

Timeline

Project's timeline

Resources

...

• Artifacts from previous GSoC project: Metadata Sharing Project