Scenarios and use cases
You might still be wondering how MD Sync can make your life easier, well, below you can find some of the main use cases. Take a look and and contact us if you have a new cool use case!
Complex DHIS2 data platforms are usually composed by multiple instances (DEV, DEV-CONTINUOUS, PREPROD, PROD... ), each instance has its purpose and hence is slightly different from the others. The workflow usually starts with the metadata developed in DEV and later migrated to PREPROD or PROD, to finally migrate to PROD when everything looks fine. When new metadata is ready to be published, a metadata package with its dependencies needs to be moved from DEV to PROD. It is important that only certain parts of the metadata with the desired dependencies can be moved from one instance to another.
MDSync enables the admins to create profiles of metadata, save them, and then sync them with one or multiple instances
Having a unique OU tree permanently synchronized across multiple DHIS2 instances can be challenging and typically requires a lot of manual transfers of Organization Units. With MDSync we can keep full OU tree synchronized across platforms.
Countries or organizations may have created a infrastructure composed of several DHIS2 instances. For example, international organizations may have different instances implemented at different levels (Regional, national) and may need to transfer data between them. In these situations, the UIDs of the metadata and OU of the different instances may be different, hampering the exchange of data between them. MD Sync app allows to exchange data between different DHIS2 instances. It does so by mapping the metadata from these instances and applying the necessary transformation as data is sent from one to another one.
There are different situations where data needs to be shared between DHIS2 instances, but the data contains information that shouldn't be shared. For instance, a program has name, gender and age of people among the gathered information but the rest of the data in the program has to be shared. By using MD Sync it is possible to always exclude certain kind of metadata during the synchronization process.
MD Sync can change data type within the same DHIS2 instances. For example, of data from the same disease is being collected through a tracker program in one pilot district and aggregate in another one, MD sync can send tracker data to a DataSet.
If using a separate DHIS2 instance to create a data repository, MD Sync and be used to load the all or selected meta-data from the routine HMIS DHIS2 instance to the repository; this includes (OrgUnits, Data Elements, Indicators, Category combinations, OptionSets, Users, etc.). Once the meta-data is loaded, the system can be used to import data and maintain both meta-data and data synchronized.
Enter the details of the packages store, download and install packages and configure as needed. You can use the mapping feature to map the variables in the packages to your local equivalents along with the proper disaggregation.
