dhis2-users team mailing list archive

[Martin Van Aken <martin@xxxxxxxxxxxxxxxx>]

Hi Propser,
The problem is that it all depends - those are linked to changes at the
health program manager level, and it's not a predictable variable. The
problem is that it's stable-ish - for a given month, it will be stable for
a most facilities, but there will probably be changes for a set of
facilities each month or tow (in other words: at least one subset/group of
facilities will have a change every period of two - not the same group each
time of course).

So, the dataSet frequency is not stable - can stay stable for six months,
then change twice in the next three, etc.

Thanks already for your help,

Martin

On Tue, Aug 30, 2016 at 10:53 AM, Prosper BT <ptb3000@xxxxxxxxx> wrote:

> Dear Martin,
>
> Can you share the frequency of change or required frequency that you would
> have to maintain if you choose to create a data element and dataset for
> this case, because its the most viable and given ability to track changes
> over time. This could be a data set only assigned to one Orgunits.
>
> Also how often to use this in analysis, this can also guide on on the
> dataset frequency.
>
> Regards
>
>
>
>
> On Fri, Aug 19, 2016 at 9:46 AM, Martin Van Aken <martin@xxxxxxxxxxxxxxxx>
> wrote:
>
>> Hi everyone,
>> I'm wondering about the best way to manage a use case of ours in DHIS2.
>> We have a specific element of data (prices for services in an RBF system)
>> which is normally the same for every org unit for a given period (and in
>> most case stable for several periods). As an example, we could have
>> something like:
>>
>> Consultation Price:
>> - Jan-December 2016: 2.5$
>> - Jan-June 2016: 2$
>> - July-December 2016: 3$
>>
>> I'm not sure what to use to represent this kind of data in DHIS2:
>>
>> - Constant is not good as it can evolve
>> - Standard Data Element means that when we make a change, we need to
>> "apply" it to every entity for the given period (thus generating hundreds
>> or thousand of copies of that values)
>>
>> Added question: if we go for a Data Element, how could we "fill it" at
>> regular basis (like for the next period each time) - we don't want people
>> to fill as a data entry for individual entities (it does not make any
>> sense, and it's not something they "report" anyway).
>>
>> Any opinion is welcome!
>>
>> Martin
>> --
>> *Martin Van Aken - **Freelance Enthusiast Developer*
>>
>> Mobile : +32 486 899 652
>>
>> Follow me on Twitter : @martinvanaken <http://twitter.com/martinvanaken>
>> Call me on Skype : vanakenm
>> Hang out with me : martin@xxxxxxxxxxxxxxxx
>> Contact me on LinkedIn : http://www.linkedin.com/in/martinvanaken
>> Company website : www.joyouscoding.com
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Prosper Behumbiize, MPH
> Global DHIS2 Implementation| HISP Uganda/University Of Oslo
> +256 752 751 776 | +256 776 139 139
> prosper@xxxxxxxxxxxxxx <ptb3000@xxxxxxxxx> | prosper@xxxxxxxxx | Skype:
> prospertb
>



-- 
*Martin Van Aken - **Freelance Enthusiast Developer*

Mobile : +32 486 899 652

Follow me on Twitter : @martinvanaken <http://twitter.com/martinvanaken>
Call me on Skype : vanakenm
Hang out with me : martin@xxxxxxxxxxxxxxxx
Contact me on LinkedIn : http://www.linkedin.com/in/martinvanaken
Company website : www.joyouscoding.com