-
Notifications
You must be signed in to change notification settings - Fork 42
Description
I have a use case where the Incident date is used separately from the enrollment date in a tracker program.
The enrollment date represents "Registration date" while incident date represents the "Date of Exposure".
By default, when the incident date is not activated in the configuration, it is still present in the enrollment properties and copies the enrollment date.
When it is actively used, it may be different from the enrollment date.
It may also be used in the period boundaries of program indicators, which is the case in the trackers I am working with.
It will be helpful to add the Incident Date row to the generated file. (Fetch it from the baseline TEIs).
Additional functionality should include: randomising the dummy data incident date within defined borders in the distribution list.
Otherwise it can follow the same pattern as configured in the baseline TEI, i.e. the same interval between enrollment and incident dates.
For programs where incident date is not relevant, it can still be fetched, but then it will just follow the enrollment date.