Thanks Elmarie, that’s good to know.
My problem is how to deal with aggregate data where the period for treatment outcomes of TB cases has been assigned to the period the report was compiled and not the period when the patients were notified (registered). The standard practice in TB is to report outcomes 12 months after cases are notified. We recommend assigning outcomes to the same period in which cases are notified, but we see many countries that don’t do that, so I was looking for a DHIS2-native way to compare patient numbers notified with patient numbers with treatment outcomes. Of course with tracker this wouldn’t be a problem at all!
Data Manager, Tuberculosis Monitoring and Evaluation, World Health Organization, Geneva, Switzerland
···
From: Elmarie Claasen elmarie@hisp.org
Sent: 06 November 2018 10:32
To: TIMIMI, Hazim Bakir timimih@who.int; DHIS 2 Users list dhis2-users@lists.launchpad.net
Subject: RE: [Dhis2-users] Adding a time lag functionality to DHIS2
Hi Hazim,
We are also eagerly awaiting the flexibility for indicator expressions. Note that if you are collecting data using tracker and using v2.30 or later you can use the analytics period boundaries in program indicators to set up timelag indicators.
Regards,
Elmarie Claasen
Project Manager
Health Information Systems Program
Tel: 041-367 1027
Cell: 082 374 2209
E-mail: elmarie@hisp.org
Skype: elmarie.claasen52
From: Dhis2-users dhis2-users-bounces+elmarie=hisp.org@lists.launchpad.net On Behalf Of TIMIMI, Hazim Bakir
Sent: Tuesday, November 6, 2018 11:18 AM
To: DHIS 2 Users list dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] Adding a time lag functionality to DHIS2
Many thanks Jim. I’m glad this is being looked at and seriously considered. I don’t use DHIS2 regularly, but whenever I do I find it frustrating not to be able to use more flexible expressions such as the ones listed at
https://jira.dhis2.org/browse/DHIS2-4469 when defining indicators.
Cheers,
Hazim
From: Jim Grace jim@dhis2.org
Sent: 05 November 2018 19:30
To: TIMIMI, Hazim Bakir timimih@who.int
Cc: DHIS 2 Users list dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] Adding a time lag functionality to DHIS2
Hazim, you are not alone!
We are looking at exactly this kind of thing now, based on requests from many users. Just now I’ve commented on this at https://community.dhis2.org/t/expression-enhancements-to-space-shift-and-time-shift-data/774.
In the meantime you might consider the use of predictors that can be used to bring data forward in time and store it in new data elements, which can then be used in indicators alongside current data. This does require new data elements, and storing the same data under two different periods in the database. We hope to be able to avoid this in the future by allowing time-shifting in the indicators themselves, very much like what you saw in the Launchpad blueprint. But using predictors is something you could do today with existing DHIS2 functionality.
Cheers,
Jim Grace
On Mon, Nov 5, 2018 at 5:41 PM TIMIMI, Hazim Bakir timimih@who.int wrote:
There are various things we would like to calculate using data from different time periods, such as % change between one period and the next, or to perform cohort analysis. I see this was raised in 2015 (see
https://blueprints.launchpad.net/dhis2/+spec/indicator-time-lags).
Does anyone have any experience of doing this in DHIS2? I didn’t find anything on JIRA. We surely can’t be the only people wondering about this?
Any helpful hints would be most welcome!
Thanks,
Hazim
……
Hazim Timimi
Data Manager, Tuberculosis Monitoring and Evaluation, World Health Organization, Geneva, Switzerland
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
–
Jim Grace
Core developer, DHIS 2
HISP US Inc.
http://www.dhis2.org
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer . Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to
disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
