Content Packages Explained
Overview
One of the reasons for content package is to allow implementors the ability to have code package that pulls-in the latest community code. As well as their own content packages.
Organization
Each content package is a full content package as explained on the OpenMRS Wiki and can contain any supported metadata described there. However, metadata that should aplpy across all sites should generally be managed via the "Base Content Package" or “Standard org Metadata Content Package”. The content packages will be expanded into a single folder, so that any content included in the facility-specific metadata will override metadata from the "Base Content Package", assuming that the files have the same name. It is recommended that for metadata domains consisting of CSV files, each domain has only a single CSV file to facilitate overriding where necessary.
Below is a an illustration of the refence application in OpenMRS repository that we share for OpenMRS v3 (O3) distribution.
A quick Search for and click on the openmrs-content-referenceapplication-demo under the OpenMRS repository will render the demo content package for the refence application. The content package displays all the meta data that is available for the demo instance of the the Reference Application of OpenMRS v3.
In order to have demo content not tied to the code of the Reference Application, we separate it to metadata content package. That is, all the metadata you see when you login to the demo instance is controlled by the above demo content package.
Country Specific Content Package
There exists country specific content package such Sierra Leonne, Haiti content packages just but a few examples. Such content packages build on the premise of the Country specific EMR needs such as concepts etc. The figure below is an illustration of Country-specific content package.
Site Specific Content Package
In the case of DRC, implementors may have to deal with different sites within the Country. Such sites may have different may be unique in that, they may have different departments or service delivery points. The DRC EMR pulls the 03 Ref App code as illustrated in the image below.
Certainly, DRC has their own metadata for use in all the sites in the country. This necessitates the need for their metadata content package whereby, instead of creating different repository for all the sites, only one repository is created.
The repository below illustrates the base content which is the DRC Base Content metadata package and the site specific content package
The site specific configurations are packaged within the Site. For instance, clicking on the sites folder will display the sites. The actual configurations are within the site.
Below is an illustration of locations specific configurations for Akram and Libikisi respectively.
This documentation is a comprehensive guide on the DRC Content package