dhis2-users team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

Hi Knut,
Not exactly sure if this the same, but in one instance which I help to
support, we are just concerned about the "latest" data. Data may be
submitted for a few months, and maybe stops at a certain point in time when
there is no longer a need for regular surveillance. However, when we
generate a report for say Feb 2014, we need all the latest data. I think
this is somehwat similar to the "On change" period type of DHIS 1.4, but
which is not implemented in DHIS2. It might be that you could simply report
the latest data (Outbreak = Yes/No) for the month in which the change
occurs, and then not bother reporting for the other months.

We have to pull the data out of the system, and create a time series of it,
using the "last observation carried forward" approach of time-series
analysis to determine what the status of all orgunits is at a given point
in time.

Having this type of period/aggregation would also solve some of the
problems with certain data elements like "ART current count", which should
never be aggregated in time, but should always simply use the latest value
reported.

Best regards,
Jason



On Sat, Feb 15, 2014 at 9:16 AM, Knut Staring <knutst@xxxxxxxxx> wrote:

> Dear DHIS2 community, looking for good ideas for a use case which is a bit
> unusual.
>
> We'd like to map epidemic outbreaks, and the data are very simple:
> Outbreak or not, in other words, Yes/No per orgunit (a province or
> district). Perhaps Yes Only would be best here?
>
> The tricky part is the time dimension: We need to produdce maps of
> affected districts at regular intervals, at least monthly, possibly also
> more frequent.
> However, there is a lot of diversity in the data: Sometimes we have a
> start and end date, sometimes just a number of months.
>
> Currently, DHIS2 does not support one screen for multiple periods
>
> I see two possibilities:
>
> 1) Create just one dataelement "Outbreak" as Yes Only in a monthly
> dataset. Then one would have to select every affected month and say YES
>
> 2) Create two additional data elements: "Start date" and "End date" in a
> YEARLY dataset. Then also write a script behind the scenes which populates
> the Outbreak dataelement for the affected months - or even extend it to days
>
> Better ideas?
>
> --
> Knut Staring
> Dept. of Informatics, University of Oslo
> +4791880522
> http://dhis2.org
>
> _______________________________________________
> 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
>
>