dhis2-users team mailing list archive

[Pamod Amarakoon <pamodm@xxxxxxxxx>]

Thanx a lot Markus. Adding the feature to query individual dates /last
updated date per program stage is going to solve lot of problems we had
lately. Will surely update you on anything that we might encounter on the
way.

On Mon, Apr 10, 2017 at 2:07 PM, Markus Bekken <markus@xxxxxxxxx> wrote:

> Hi Pamod,
> When using enrollment program indicators, the enrollments being aggregated
> in your pivot will be the defined by the enrollment date entered during
> registration/enrollment. Meaning that asking for a report from 2016Q1 will
> give you data for all enrollments that started in this period. You would
> then be able to filter out the enrollments you want using a filter that
> queries the outcome or other data data from one or more program stages
> within the enrollment. The event date of the outcome data event will not be
> taken into account in the current solution.
>
> Created a JIRA issue to support aggregating on different dates in the
> enrollment(this had been planned for a while but not documented):
> DHIS2-1398 <https://jira.dhis2.org/browse/DHIS2-1398>. The last event
> date in the enrollment across all program stages can be accessed in filters
> and expressions calculations by using the V{event_date} variable. However,
> the individual program stages event dates cannot be accessed at the moment,
> so if you use a registration program stage you will not be able to use the
> event date here with enrollment analytics. JIRA issue for adding support
> for this can be found here: DHIS2-1397
> <https://jira.dhis2.org/browse/DHIS2-1397>
>
> Let us know the gaps if your you case doesn't seem to be supported -
> especially interested in the relation between the enrollment and event date
> below. Given the two improvements listed above, can you make a filter or
> expression that covers it?
>
> Best regards
> Markus
>
> 10. apr. 2017 kl. 09.43 skrev Pamod Amarakoon <pamodm@xxxxxxxxx>:
>
> Hi Markus,
>
> What happens when you add enrollment date in defining program indicator
> and also select the compulsory time dimension in pivot table. Just confused
> as to what may take precedence.
>
> eg: In Pramil's case,
>
> He has a registration stage with an enrollment date and he wants to
> analyze the outcome event status of another program stage. Say he wants to
> follow a cohort registered in 2016Q1 who's outcome will only be available
> in a different program stage in 2017Q2, could this be achieved using
> Program indicator in pivot table.
>
> Thanx.
>
> On Mon, Apr 10, 2017 at 1:04 PM, Pramil Liyanage <pramilcl@xxxxxxxxx>
> wrote:
>
>> Thanks Markus. I'm on 2.25. Will update to 2.26 and try. Will get back to
>> you if any issue. Thanks again.
>>
>> Pramil
>>
>> On Mon, Apr 10, 2017 at 12:59 PM, Markus Bekken <markus@xxxxxxxxx> wrote:
>>
>>> Hi there Pramil,
>>> if you are on version 2.26 or later you can make a program indicator
>>> with the "Enrollment" analytics type:
>>> <Skjermbilde 2017-04-10 kl. 09.27.16.png>
>>>
>>> This will let you compare data from different events within the same
>>> enrollment. The enrollment date is used as the aggregation date when
>>> looking at the data in a pivot.
>>>
>>> Hope this helps, get back if you have any further questions.
>>>
>>> Best regards,
>>> Markus
>>>
>>>
>>> 7. apr. 2017 kl. 21.48 skrev Pramil Liyanage <pramilcl@xxxxxxxxx>:
>>>
>>> Hi,
>>>
>>> I need to analyze data across variables in two events in a program with
>>> multiple stages.
>>>
>>> For example, I need to find the number of patients marked as cured in *treatment
>>> outcome* stage,  for a cohort registered during a specified time. Can I
>>> combine enrollment date or date from another event (e.g. *registration
>>> event*)? Event reports will aggregate to the event, *treatment outcome*,
>>> not registration.
>>>
>>> I know that this is not possible to combine elements from two events in
>>> event reports. Is it possible to do this using programme indicators? If so
>>> what is the syntax?
>>>
>>> Regards
>>> Pramil
>>> _______________________________________________
>>> 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
>>>
>>>
>>>
>>
>> _______________________________________________
>> 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
>>
>>
>
>
> --
> Regards,
> Dr. Pamod Amarakoon
> MBBS (SL)
> MSc (Biomedical Informatics), EMSc (Health Admin)
> Medical Officer in Health Informatics
> Nutrition Coordination Division
> Ministry of Health, Nutrition and Indigenous Medicine,
> Sri Lanka
>
> Confidentiality Notice: the information contained in this email and any
> attachments may be legally privileged and confidential. If you are not an
> intended recipient, you are hereby notified that any dissemination,
> distribution, or copying of this e-mail is strictly prohibited. If you have
> received this e-mail in error, please notify the sender and permanently
> delete the e-mail and any attachments immediately. You should not retain,
> copy or use this e-mail or any attachments for any purpose, nor disclose
> all or any part of the contents to any other person.
>
>
>
>
>


-- 
Regards,
Dr. Pamod Amarakoon
MBBS (SL)
MSc (Biomedical Informatics), EMSc (Health Admin)
Medical Officer in Health Informatics
Nutrition Coordination Division
Ministry of Health, Nutrition and Indigenous Medicine,
Sri Lanka

Confidentiality Notice: the information contained in this email and any
attachments may be legally privileged and confidential. If you are not an
intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this e-mail is strictly prohibited. If you have
received this e-mail in error, please notify the sender and permanently
delete the e-mail and any attachments immediately. You should not retain,
copy or use this e-mail or any attachments for any purpose, nor disclose
all or any part of the contents to any other person.