We have a case (TB case-based surveillance) with some requirements with regards to enrolment and event dates that we are struggling with. We want to use the “enrolment date” in the program as “TB notification date”, which is what enrolment analytics needs to be based on. However, we also have a “baseline” program stage where we want to use the same date, so that event analytics for that baseline program is also using the notification date. Also, the notification (enrolment) date needs to be editable.
Setting the baseline stage to be scheduled 0 days after enrolment, to be auto-generated and to be opened after enrolment, things work fine initially, BUT the enrolment date is not editable because we are auto-generating events based on the enrolment date. In other words, this approach does not work.
Disabling auto-generation of program stages (which is not ideal) allows modification of the enrolment date, but the baseline stage event date then needs to be set and later modified manually, since there’s no way of assigning event dates with program rules as far as I can see. Still, this is the closest we have gotten to a solution at the moment, since we can at least show a warning if there is a mismatch between the two notification dates.
Does anyone have suggestions for better solutions? To recap, we want:
- enrolment date and event date of the first program stage to always be the same
- this date needs to be editable
- we would ideally still be able to schedule and auto-generate events