We are thinking about harmonize all defaults of our 5 DHIS2 platforms (Particularly, to set to each default element the same ID throughout all the databases (4 different IDs in total, no only 1 of course), and to change the UIDs references in all the DB). Do you think that can be useful to avoid import/export issues we currently have? Or the new update on 28 about this topic solves this kind of issues?
South Africa is using a National Data Dictionary (DHIS2-based) to “control” most meta-data, which means we have standardised uids and codes for
orgunits
data elements
indicators
validation rules
categories/options/combos
etc.
Makes life a lot easier when you have many separate DHIS2 instances.
This is now increasingly also coming up as an international / global challenge - since DHIS2 does not have any kind of import matching mechanism where the incoming uid/code/name can be matched to internal uid/code/name (if different), you end up with a lot of uid fiddling. The need to be able to export program indicator data as aggregate values to other systems exacerbate this challenge.
Regards
Calle
···
On 6 February 2018 at 11:06, Ramón José Jiménez Pomareta dhis2@pomareta.ch wrote:
Hello,
We are thinking about harmonize all defaults of our 5 DHIS2 platforms (Particularly, to set to each default element the same ID throughout all the databases (4 different IDs in total, no only 1 of course), and to change the UIDs references in all the DB). Do you think that can be useful to avoid import/export issues we currently have? Or the new update on 28 about this topic solves this kind of issues?
This is also now part of the process we are doing as a collaboration between WHO and UiO. So far, we have mainly worked on HIV, TB, malaria and Immunization, but the plan is to bring in all the health programs.
South Africa is using a National Data Dictionary (DHIS2-based) to “control” most meta-data, which means we have standardised uids and codes for
orgunits
data elements
indicators
validation rules
categories/options/combos
etc.
Makes life a lot easier when you have many separate DHIS2 instances.
This is now increasingly also coming up as an international / global challenge - since DHIS2 does not have any kind of import matching mechanism where the incoming uid/code/name can be matched to internal uid/code/name (if different), you end up with a lot of uid fiddling. The need to be able to export program indicator data as aggregate values to other systems exacerbate this challenge.
On 6 February 2018 at 11:06, Ramón José Jiménez Pomareta dhis2@pomareta.ch wrote:
Hello,
We are thinking about harmonize all defaults of our 5 DHIS2 platforms (Particularly, to set to each default element the same ID throughout all the databases (4 different IDs in total, no only 1 of course), and to change the UIDs references in all the DB). Do you think that can be useful to avoid import/export issues we currently have? Or the new update on 28 about this topic solves this kind of issues?
Department of Information, Evidence and Research
World Health Organization, Geneva, Switzerland
Office: +41 22 791 3683 Mob1: +33 6 4434 2931 Mob2: +47 9188 0522
Skype: knutstar
You can also use the new feature which allows you to specify a coding scheme during import. Its not quite the same functionality as in DHIS1.4, where you could map the data elements during import, but if you can specify a code on your “destination” system which is present in your “source” system, you can also use that to import data with a specified coding scheme.
Regards,
Jason
···
On Tue, Feb 6, 2018 at 10:45 AM, Knut Staring knutst@gmail.com wrote:
Thanks Calle and Ramon,
This is also now part of the process we are doing as a collaboration between WHO and UiO. So far, we have mainly worked on HIV, TB, malaria and Immunization, but the plan is to bring in all the health programs.
South Africa is using a National Data Dictionary (DHIS2-based) to “control” most meta-data, which means we have standardised uids and codes for
orgunits
data elements
indicators
validation rules
categories/options/combos
etc.
Makes life a lot easier when you have many separate DHIS2 instances.
This is now increasingly also coming up as an international / global challenge - since DHIS2 does not have any kind of import matching mechanism where the incoming uid/code/name can be matched to internal uid/code/name (if different), you end up with a lot of uid fiddling. The need to be able to export program indicator data as aggregate values to other systems exacerbate this challenge.
Department of Information, Evidence and Research
World Health Organization, Geneva, Switzerland
Office: +41 22 791 3683 Mob1: +33 6 4434 2931 Mob2: +47 9188 0522
Skype: knutstar
On 6 February 2018 at 11:06, Ramón José Jiménez Pomareta dhis2@pomareta.ch wrote:
Hello,
We are thinking about harmonize all defaults of our 5 DHIS2 platforms (Particularly, to set to each default element the same ID throughout all the databases (4 different IDs in total, no only 1 of course), and to change the UIDs references in all the DB). Do you think that can be useful to avoid import/export issues we currently have? Or the new update on 28 about this topic solves this kind of issues?