dhis2-users team mailing list archive

["Alvin B. Marcelo" <alvin.marcelo@xxxxxxxxx>]

Hi Knut, 

Here are what we needed in PhilHealth but I could not get enough experienced writers (locally) to do:

1. Guidelines for routine reporting. This may contain things such as:
- All official reports are generated _____ monthly for "facilities", quarterly for "districts" and "provinces", and  annually for "regions" and "national". 

- All facilities are expected to complete their submissions no later than the 5th day of the following month (eg, complete reports submitted on or before Fenruary 5 for January)

- A national management team will be formed composed of: __, __, __ with the following roles and responsibilities:

- A regional management team will be formed composed of:

- A provincial management team will be composed of:

2. Policy for Creating Forms in DHIS2
- 

3. Policies for 'pay for performance' (or the document that explicitly links how entering data into dhis2 becomes a payment to the healthworkers.

These are just some that would have been nice to have ready when we started implementing DHIS2. Mind you, I encountered a lot of pushback with my implementation because my staff were already overworked and could not accommodate more projects. But even if we did pursue the outsourced-to-academe option, even the outsourcing document got stalled (because it still required my internal staff to write this).

I will therefore share our outsource documents for use of others...so they can outsource more easily...


Sent from my BB Curve 9320

-----Original Message-----
From: Knut Staring <knutst@xxxxxxxxx>
Date: Tue, 22 Oct 2013 07:46:51 
To: Alvin Marcelo<alvin.marcelo@xxxxxxxxx>
Cc: Lars Helge Øverland<larshelge@xxxxxxxxx>; dhis2-users@xxxxxxxxxxxxxxxxxxx<dhis2-users@xxxxxxxxxxxxxxxxxxx>; DHIS 2 developers<dhis2-devs@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Dhis2-devs] [Dhis2-users] Analytics history

Hi Alvin,

Thanks for valuable input - we have tried to amass "best practice"
guidelines in the implementation manual, but I'm sure it would be useful to
have "policy templates" as well. Given your experience, could you perhaps
detail a bit more what you think such templates should look like? And what
topics you think should be covered?

Cheers,
Knut


On Tue, Oct 22, 2013 at 12:32 AM, Alvin Marcelo <alvin.marcelo@xxxxxxxxx>wrote:

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


-- 
Knut Staring
Dept. of Informatics, University of Oslo
+4791880522
http://dhis2.org