When capturing Medical Certificate of Cause of death on our COD instance, It was observed that the date of death was allowing future date to be captured. the date being for date of death is the system date for event capture.
This was tested on trainingland using antenatal visits event program and same problem was observed for all stable versions of DHIS2.
There is the need to fix this and probably replicate the checkbox that allow users to either decide to capture future dates or not as implemented in tracker programs under the enrolment details. Default should current and previous date while a check box can then be added to allows users to check if they wanted allows capture of future dates in their event programs.
I have a suggestion in this scenario but please feel free to correct me if I’m not getting it right. How about using a program rule to assign this based on the system date rather than the user selecting the date?
@Caroline We have a use-case where we would like to allow the entry of future dates for a Data Element with the ‘date’ type. We are using the Event Model, and are trying to allow for campaign workers to record the “scheduled activity” date (in the future) during pre-activity mobilization activities. Data are being captured via DHIS2 Android Capture app. I do not see an option to allow for future dates to be entered for Date-type Data Elements. Can you advise on how we can try to achieve this?
