dhis2-devs team mailing list archive

[Bob Jolliffe <bobjolliffe@xxxxxxxxx>]

Hi Calle

I never thought of using categories like that, but it looks to me like it
would work.  Category=DayOfTheMonth,
CategoryOptions="Day1,Day2,...,Day31".  The sum of the categoryoptions add
up to the total for the month which I think is consistent with rational
category design.

Obviously you'll need to make a heavily customized form, but I can't see a
reason why that shouldn't be doable.

Bob

On 30 January 2015 at 13:11, Calle Hedberg <calle.hedberg@xxxxxxxxx> wrote:

> Hi,
>
> I need some urgent feedback on one very specific issue:
>
> 1.
> We have a lot of monthly data that have been captured on a daily basis
> (up to now in 1.4). The data is in reality monthly aggregated data
> because it is the monthly totals that are used for indicators,
> analysis, reports etc - but the data is captured daily into DHIS to
> enable consistency/completeness tracking and to cut down on the
> erroneous manual data compilation from paper forms at the end of every
> month.
>
> 2.
> Initially, the HISP team converted these daily captured values in 1.4
> into datavalues in DHIS2 with dataperiodtype = daily. This approach
> has various shortcomings, in particular when the use of daily
> capturing is slowly being rolled out - meaning that while let us say
> 30% of all facilities captured data on a daily basis themselves, the
> remaining 70% are still submitting monthly summary forms to the
> sub-district office for capturing as monthly total data.
>
> 3.
> I believe a more logical approach is to store the daily data (Day01,
> Day02, ...., Day31) as categories - as mentioned, we are in general
> NOT using those daily values for anything beyond the initial data
> quality and completeness process.
>
> QUESTION:
> 1. Are there any major drawbacks to storing these daily values as
> categories?
>
> 2. Are there any major limitations with regard to the design of data
> entry forms that will make it difficult to have a "matrix" type data
> entry form where
> (a) the user select OrgUnit, DataSet, and the DATE (as in 2015-01-30)
> (b) the year/month part of that date determines the dataperiodid
> (c) the day portion of the date determines which category will be the
> right-most column in the data entry matrix
> (d) we can display let us say 7 preceding days in the matrix to assist
> the data capturer with eyeballing data during capture (dynamic
> selection & display of categories).
>
> So the entry form would show up as
> DataElement          Day23 Day24 Day25 Day26 Day27 Day28 Day29 Day30
> <data element1>         17       14      15       22       18
> 19       20     <entry>
> <data element2>         13       11      19        8        15
> 12       10     <entry>
>
> Any quick feedback would be appreciated
>
> Regards
> Calle
>
> *******************************************
>
> Calle Hedberg
>
> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>
> Tel/fax (home): +27-21-685-6472
>
> Cell: +27-82-853-5352
>
> Iridium SatPhone: +8816-315-19274
>
> Email: calle.hedberg@xxxxxxxxx
>
> Skype: calle_hedberg
>
> *******************************************
>
> _______________________________________________
> 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
>