You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Within reports, implementors come across a lot of scenarios where an individual is enrolled to same program multiple times. And while writing a report around program encounter & exit details it is not clear how to map it to the right/corresponding program enrolment.
One work around for example we used recently is -
Instead of -
LEFT JOIN individual_mother_exit on individual_mother_exit.individual_id = enl.individual_id
we replaced it with and extra condition
LEFT JOIN individual_mother_exit on individual_mother_exit.individual_id = enl.individual_id and enl.enrolment_date_time = individual_mother_exit.enrolment_date_time
This is quite difficult for (external/internal) implementors to understand, hence we need a clear enrolment ID in the respective program encounter & exit tables.
The text was updated successfully, but these errors were encountered:
Within reports, implementors come across a lot of scenarios where an individual is enrolled to same program multiple times. And while writing a report around program encounter & exit details it is not clear how to map it to the right/corresponding program enrolment.
One work around for example we used recently is -
Instead of -
LEFT JOIN individual_mother_exit on individual_mother_exit.individual_id = enl.individual_id
we replaced it with and extra condition
LEFT JOIN individual_mother_exit on individual_mother_exit.individual_id = enl.individual_id and enl.enrolment_date_time = individual_mother_exit.enrolment_date_time
This is quite difficult for (external/internal) implementors to understand, hence we need a clear enrolment ID in the respective program encounter & exit tables.
The text was updated successfully, but these errors were encountered: