Integration with DHIS: Difference between revisions
From IHRIS Wiki
Sturlington (talk | contribs) No edit summary |
|||
| (9 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
This page is intended as a planning document for integration of iHRIS Manage with DHIS. | This page is intended as a planning document for integration of iHRIS Manage with DHIS. | ||
For reference, see also: | |||
*[http://www.tghin.org/node/236#comment-152 tghin discussion] | |||
*[http://groups.google.com/group/sdmx_hd/web/documentation SDMX_HD] | |||
*[https://blueprints.launchpad.net/dhis2/+spec/dxf-format dxf format] | |||
==Technical Documentation for DHIS 2.0== | ==Technical Documentation for DHIS 2.0== | ||
Some information on the [https://mail.intrahealth.org/exchweb/bin/redir.asp?URL=http://bazaar.launchpad.net/%257Edhis2-devs-core/dhis2/trunk/download/head%253A/technicalarchitectur-20090303164601-edynttiof6lqx3ke-17/Technical%2520Architecture%2520DHIS%25202.doc Database structure] in DHIS 2.0. | |||
==Possibilities for Integration== | ==Possibilities for Integration== | ||
| Line 8: | Line 14: | ||
It might be useful to start looking at iHRIS's ability to export data to XML. | It might be useful to start looking at iHRIS's ability to export data to XML. | ||
We could then possibly write some xslt transformations to transform that into something more easily consumable by DHIS2. Currently this would likely be our "native" DXF format but there are a number of reasons why we might consider evolving from there: | We could then possibly write some xslt transformations to transform that into something more easily consumable by DHIS2. Currently this would likely be our "native" DXF format but there are a number of reasons why we might consider evolving from there: | ||
*some of our internal discussion around the | *some of our internal discussion around the [https://blueprints.launchpad.net/dhis2/+spec/dxf-format native dxf format] | ||
*we wish to consider supportting SDMX HD (the new generation IXF) being promoted by WHO. Its intent is primarily to support the exchange of statistical data and metadata between (international) organizations it seems not as well optimized for the movement of bulk data on a routine basis as our current format. | *we wish to consider supportting SDMX HD (the new generation IXF) being promoted by WHO. Its intent is primarily to support the exchange of statistical data and metadata between (international) organizations it seems not as well optimized for the movement of bulk data on a routine basis as our current format. | ||
These are two ways this could evolve: | These are two ways this could evolve: | ||
*you export what you export "naturally"; we import what we import | *you export what you export "naturally"; we import what we import naturally and we try to build the bridge with xslt. (preferred) | ||
naturally and we try to build the bridge with xslt. (preferred) | *iHRIS Manage exports SDMX HD and DHIS imports SDMX HD. | ||
* | |||
==Getting Data Out of iHRIS Manage== | ==Getting Data Out of iHRIS Manage== | ||
You can see how we data in | You can see how we data in iHRIS Manage might be exported in an XML | ||
format. | format. [http://bazaar.launchpad.net/~intrahealth%2Binformatics/ihris-common/3.2-dev/annotate/head%3A/modules/Person/modules/Demographic/Demographic.xml Here] is a sample for the "gender" form (look starting | ||
line 49) | |||
This is how data is loaded in for the " | This is how data is loaded in for the "magic data" [[Form Storage Mechanisms|form storage mechanism]]. This can be easily exported, as you suggested, via our "Magic Data Export". In fact, with the "Magic Data Browser", you can browse to a the appropriate place in magic data and hit the "Export" button. | ||
There is a second, distinct, way to export the data will work if the data is not already stored in magic data, or if you need a more complicated "slice" of the data. This is to use the custom reporting facility to dump the data out out. Right now there is a CSV and html dump implemented. Doing an XML dump would be a quick matter. | There is a second, distinct, way to export the data will work if the data is not already stored in magic data, or if you need a more complicated "slice" of the data. This is to use the custom reporting facility to dump the data out out. Right now there is a CSV and html dump implemented. Doing an XML dump would be a quick matter. | ||
==Translating XML Data== | ==Translating XML Data== | ||
[[Category:Archived Pages]] | |||
Latest revision as of 13:53, 16 July 2013
This page is intended as a planning document for integration of iHRIS Manage with DHIS.
For reference, see also:
Technical Documentation for DHIS 2.0
Some information on the Database structure in DHIS 2.0.
Possibilities for Integration
It might be useful to start looking at iHRIS's ability to export data to XML. We could then possibly write some xslt transformations to transform that into something more easily consumable by DHIS2. Currently this would likely be our "native" DXF format but there are a number of reasons why we might consider evolving from there:
- some of our internal discussion around the native dxf format
- we wish to consider supportting SDMX HD (the new generation IXF) being promoted by WHO. Its intent is primarily to support the exchange of statistical data and metadata between (international) organizations it seems not as well optimized for the movement of bulk data on a routine basis as our current format.
These are two ways this could evolve:
- you export what you export "naturally"; we import what we import naturally and we try to build the bridge with xslt. (preferred)
- iHRIS Manage exports SDMX HD and DHIS imports SDMX HD.
Getting Data Out of iHRIS Manage
You can see how we data in iHRIS Manage might be exported in an XML format. Here is a sample for the "gender" form (look starting line 49)
This is how data is loaded in for the "magic data" form storage mechanism. This can be easily exported, as you suggested, via our "Magic Data Export". In fact, with the "Magic Data Browser", you can browse to a the appropriate place in magic data and hit the "Export" button.
There is a second, distinct, way to export the data will work if the data is not already stored in magic data, or if you need a more complicated "slice" of the data. This is to use the custom reporting facility to dump the data out out. Right now there is a CSV and html dump implemented. Doing an XML dump would be a quick matter.
