dhis2-devs team mailing list archive

[Alvin Marcelo <alvin.marcelo@xxxxxxxxx>]

Lars,

I like this approach. Fundamentally, it boils down to local policy and it
would help policy writers if we can give them templates on how this can be
done. Come to think of it, are there policy templates for DHIS2
implementations? They were my weak areas when I was trying to implement it
at PhilHealth...

Although I knew ours will not be exactly the same as other countries'
implementations, there would be similarities which we could "replicate as
base document" and customize...

alvin







On Mon, Oct 21, 2013 at 10:49 PM, Lars Helge Øverland
<larshelge@xxxxxxxxx>wrote:

> Hi Alvin,
>
> its a good point and something we have been thinking about for a while.
> This is something that we definitely need to act on soon.
>
> The challenge is to find a sensible level of detail for what to store, as
> there are costs in terms of i) system complexity and ii) aggregation
> performance degradation involved here. For example, if facilities are moved
> around in administrative boundaries every month, how do you calculate the
> yearly total for the whole province?
>
> My suggestion, as a reasonable trade-off, would be to create snapshots of
> the organisation unit hierarchy at the end of each year. These snapshots
> are then used for analytics queries for past data. So for instance if you
> query today for "last 12 months", it would use the current "live"
> organisation unit hierarchy for months Jan-Sept 2013, then the "2012
> snapshot" hierarchy for months Oct-Dec 2012.
>
> On an implementation note, this will fit well the analytics solution where
> data is partitioned across years - each data partition will have a
> corresponding org unit hierarchy, making aggregation simple.
>
> Lars
>
>
>
>
>