← Back to team overview

dhis2-devs team mailing list archive

Re: HRIS data import via SDMX-HD

 

And if you hadn't found how to post the dataset from the manual, look here
http://dhis2.org/doc/snapshot/en/user/html/ch23s06.html


On 5 December 2012 00:01, Bob Jolliffe <bobjolliffe@xxxxxxxxx> wrote:

> Hi Carl
>
> Sorry to have been unresponsive on this but have been trapped in a meeting
> the past 2 days.  I will be back at home tomorrow evening and try to give
> some better instruction.
>
> On 4 December 2012 09:56, Frederick Leitner <litlfred@xxxxxxxxxxx> wrote:
>
>> Hi All,
>>
>> I am in Zimbabwe and we are working on setting up a linkage from their
>> HRIS, zHRIS, to DHIS2 via SDMX-HD as a cross-sectional data set.  I am
>> following the same pattern as we have done for Kenya, Zanzibar, and Sierra
>> Leone.  However, I have always worked on the HRIS side of things and this
>> time around I need some direction/helpful hints on the DHIS side.
>>
>> As a first step, we are trying to import in DHIS2 the data (# health
>> workers, facility, post)
>>
>> So far, we have generated the necessary DSD.xml and KF_POST_FACILITY.xsd
>> files and I believe the actual import process will should follow this
>> outline:
>>  http://dhis2.org/doc/snapshot/en/user/html/ch24s04.html
>> How can one associate the DSD and KF_POST_FACILITY.xsd to this process so
>> it can be validated.
>>
>
> We have never implemented the importing of SDMX DSD.  What we did do
> before was was generate the DSD from our side.  Regarding association of
> dsd with schema (in fact schema should be generated from the dsd) let me
> explain more tomorrow.  Its late here now :-)
>
> What you would probably want to do if you are going this way around and
> you already have the codelists, is use those to create dataelements in dxf
> and import them.  Again I can help with the detail but not right now.
>
>
>> Next, I want to know how to properly get the posts properly loaded into
>> DHIS.  These are not (at least for now) going to be further disaggregated
>> by things like gender.  Looking at some previous examples I think that I
>> should be generating a dxf file for this.  Something along the lines of the
>> snippet below.  Is this headed in the right direction?
>>
>
> yes
>
>>
>> Assuming so, I want the categoryCombo to be "default", but it seems that
>> the id is different on each system.  I assume that I would I need to look
>> it up on the target DHIS system first, or is there some other way?
>>
>
> if categorycombo is meant to be default you can just leave it out.
>  Importer is smart enough to figure you mean default by default :-)
>
>
>>
>> The id's for the post dataElements are coming from the zHRIS, e.g.
>> 123456  As I can't guarantee that there won't be collision with ids for
>> existing dataElement ids, can I put a prefix on the id, e.g. HRIS123456?
>> Is there some other way I can avoid collision?
>>
>
> Sure.  The ids don't have to be numeric.  Great relief to have moved
> beyond that.  So any sensible code of your choosing will do and dhis will
> accept it (as long as it doesn't collide).
>
>
>> I have omitted the <uid/>s in the snippet below.  Is this OK?
>>
>
> Yes.
>
> Bob
>
>
>>
>> Cheers,
>> -carl
>> P.S. sorry if this message is a repeat
>>
>>
>> <dxf>
>>  <dataElements>
>>    <dataElement>
>>      <name>Nurse</name>
>>      <shortName>Nurse</shortName>
>>       <code>HRIS_123456</code>  <!-- this code is coming from zHRIS -->
>>       <description></description>
>>       <active>true</active>
>>       <type>int</type>
>>       <domainType>aggregate</domainType>
>>       <aggregationOperator>average</aggregationOperator>
>>       <categoryCombo>5</categoryCombo>  <!-- I want this to be the
>> default categoryCombo.  Suppose that it is 5 on the target DHIS system -->
>>       <lastUpdated>2010-02-05</lastUpdated>
>>    </dataElement>
>>     <!--  etc -->
>> </dataElements>
>>  <!-- assume that I have already created a dataElementGroup "Post" with
>> id 987654 -->
>> <dataElementGroupMembers>
>>    <dataElementGroupMember>
>>       <dataElementGroup>987654</dataElementGroup>
>>       <dataElement>123456</dataElement>
>>    </dataElementGroupMember>
>>    <!--  etc -->
>>  </dataElementGroupMembers>
>> </dxf>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>

Follow ups

References