← Back to team overview

dhis2-devs team mailing list archive

Re: DHIS and logistics management (Was: Re: New requirement from Sri Lanka)

 

On 8 December 2010 04:29, Thuy Nguyen <thuy.hispvietnam@xxxxxxxxx> wrote:

> Dear Johan,
>
>
>> Here also I'm not 100% sure, but if you go to edit data element, you will
>> find the Aggregation Level check box, which if checked will produce a
>> drop-down list of all the levels you can aggregate data from. From the
>> manual:
>>
>> "Aggregation levels: The Aggregation Levels option allows the data element
>> to be aggregated at one or more
>> levels. When the user clicks on the Aggregation levels option, a drop down
>> menu appears which displays available
>> aggregation levels. The desired aggregation level is then selected by
>> clicking the ‘Add Selected’ button. By default,
>> the aggregation will start at the lowest assigned organisation unit."
>>
>> I'm not sure if this adequately explains the funcionality. Others would
>> need to help here, but I *think* this is working by setting the levels
>> that will use "it's own" data rather than aggregate from below. Default
>> only the lowest level is selected, and all higher levels will use data
>> from that level. For example, if you have three levels; Facility,
>> District, National, the last two levels will by default aggregate the data
>> from Facility. If you select District as aggregation level, queries on
>> Facility will use Facility data, District will use District Data, and
>> National will aggregate District data. So in the Sri Lanka case, you can
>> have one data element that you can use for all levels, just set it to have
>> all aggregation levels. But not 100% sure about this, so good if someone
>> can confirm. Also not sure aggregation level is the best name, I vaguely
>> remember some discussion about this.
>>
>
>
> Thanks a lot for explanation about this aggregate. So one problem may solve
> is each org unit level will see their own data. But there is another problem
> .
>
> Example
> Hierarchy of org unit are like this: National, District, Subdistrict
> National level want to see 2 types of report
> - Their own data
> - Total District level data values(without aggregated with the data values
> at national level)
>
> Example National N will enter their data values is N'
> Districts will enter their data values as : District 1 enter D1, District 2
> enter D2
> in District 1 have many SubDistricts, these SubDistrict enter data values
> as : SubDistrict 1 enter S1, SubDistrict  enter S2, SubDistrict 3 enter S3
>
> Then the National level want to generate
> - 1st report with data values is N'
> - 2nd report with datavalues is D1+D2
>
> The district org unit want to generate
> - 1st report with datavalues is D1
> - 2nd report with data of its subdistrict : S1+S2+S3
>
> Note : N' not equal D1+D2, D1 not equal to S1+S2+S3 because each org unit
> level has their stocks, so total of received items is not equal to total
> issued items, coz they always sure that the items must be available in the
> stock more than the min limitation.
>
> From above requirements, if we keep entering from bottom to top org unit
> levels by only one data element. The aggregated level attribute in data
> element can be set at national level, so that every org unit level can
> generate the 1st report. But how to generate the 2nd reports?
>
>
If you need N and D1+D2 as separate aggregates (as two different "national"
figures) you will need to define two different data elements, e.g.
"Paracetamol 500 mg 10px package received national", "Paracetamol 500 mg
10px package received district". And to get D1 and S1+S2+S3 as two different
district values you will need to do add "Paracetamol 500 mg 10px package
received sub-district" as well.  You can then use a standard report
(designed in iReport or BIRT) to put them together in the correct layout or
to do comparisons on these numbers.

The aggregation levels are used to define which data source to use (e.g.
national or district), but only supports 1 aggregation "algorithm" per data
element and not multiple as in your case here.

Ola
------




> Thuy
>
> _______________________________________________
> 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