In DHIS2 can’t “global” be set as OUlevel zero (above national/OU1)? If multiple countries were to be integrated into one instance it would require all existing OUlevels to be incremented unless level zero could be accommodated with some dynamic settings for different ‘branches’ (assuming all country instances share a common and proportionate number of vertical levels).
The other option is going a much more sophisticated route and virtualizing a DHIS2 instance from multiple ‘live’ instances but that would be a whole new kind of approach - probably unnecessarily complex …
···
On Fri, Jun 20, 2014 at 4:43 AM, Knut Staring knutst@gmail.com wrote:
I guess I am talking about somehow parametrizing the PT favorites - and being able to share the parametrizable favorites between DHIS2 instances.
–
Knut Staring
Dept. of Informatics, University of Oslo
+4791880522
On Fri, Jun 20, 2014 at 4:39 AM, Knut Staring knutst@gmail.com wrote:
While I agree on the recommendation of a common meta-data repository for Data Elements and Indicators, this obviously does not help in the least when it comes to OrgUnits in different countries. We have OrgUnit as a parameter in the “ordinary” reports, but not for pivot tables (periods are of course already standardised across most countries - those that use ISO calendars).
I suppose the question highlights the increasing use of more flexible PT for reporting in addition to (or completely replacing) conventional reports. Does it make sense to think of an App that makes it easy to pass parameters (OU, periods) to ready-made pivot layouts - or would that really just be recreating the PT GUI? Is the API already capable of handling this?
Knut
–
Knut Staring
Dept. of Informatics, University of Oslo
+4791880522
On Thu, Jun 19, 2014 at 8:49 PM, Greg Rowles greg.rowles@gmail.com wrote:
Hi, Also agree with the abovementioned. We’re working towards a “master” data-dictionary for indicator and data element definitions to ensure alignment and standardization here in South Africa. It might be good to begin assessing alignment possibilities starting with indicators as they determine which elements get collected…
Regards,
Greg
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
–
Knut Staring
Dept. of Informatics, University of Oslo
+4791880522
On Thu, Jun 19, 2014 at 8:33 PM, Lars Helge Øverland larshelge@gmail.com wrote:
Lars
Hi, agree with Jason. On an additional note, if the meta-data (data elements in particular) actually are consistent across several instances it might be a good effort to standardize the UID, will be useful if you want to do comparative analysis across countries at a later stage.
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
Business Intelligence Planner
Health Information Systems Programme
**- - - - - - - ****- - - - - - - ****- - - - - - - ****- - - - - - - ****- - - - - **
Mobile : 073 246 2992
Landline: 021 554 3130
Fax: 086 733 8432
Skype: gregory_rowles
–
On Thu, Jun 19, 2014 at 7:34 PM, Jason Pickering jason.p.pickering@gmail.com wrote:
I would think the best way to go about this would be to have a common meta-data repository. It would seem to be quite a bit of effort to try and map metadata definitions between different instances, but the usual approach here would be to have a “master” instance, which other “slave” instances would draw their metadata from. In this case, the exchange of pivots/reports would be possible, but very troublesome otherwise.
It is certainly possible, but building the transformation would be one more piece to maintain and would be quite fragile, as changes on either side would break it.
Best regards,
Jason
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
On Thu, Jun 19, 2014 at 7:29 PM, Laura E. Lincks laura.lincks@icap.columbia.edu wrote:
We have individual DHIS instances installed for individual countries. Many configuration needs are similar across countries including the set up of many reports. Is it possible to take a pivot table definition set up in one country and export that definition to another country’s DHIS instance? I see that details can be exported for a pivot table using Meta-Data Export but it of course contains unique identifiers for that country which will not apply in another country’s instance. Is there a way to query the data from the backend, create an output script, changing the unique IDs to the new country’s respective IDs and then insert the data in the new country’s database? It may be more trouble doing it that way than simply manually creating the pivot table structures in the new country, but I thought I’d ask if anyone has had success doing it in a more automated fashion.
Laura E. Lincks
Database
Developer
ICAP -
Columbia University
Mailman School of Public Health
60 Haven Ave, Floor B1New York, NY 10032
Tel: 212 304 7132
–
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp