Start Date and End Date Validation
Before saving a Start Date or End Date, validate the date is a valid calendar date. This could also check for dates recorded prior to 1/1/1915 as noted in HMIS Reporting Glossary. This could also check for dates in the future and give a warning message when the user saves that it is a date in the future to confirm accuracy. This could apply to both enrollments and services.
Sarah Graham
shared this idea
Thank you for your feedback. We are currently reviewing this request.
-
Joshua Fuentes
commented
Agreed, this does give our HMIS team significant extra work fixing dates (example: HUD UDE 3.917, Prior Living Situation can have dates thousands of years in the distant future).
-
David Wilkie
commented
Last month, one of our users recorded that a client's current episode of homelessness began in the year 9209! Another client's episode supposedly began in the year 2624. It was burdensome to resolve these errors, as they had downstream effects in analysis such that the sources were not immediately obvious. Sensible constraints on date entry would help prevent this.
-
Before saving a Start Date or End Date, validate the date is a valid calendar date. This could also check for dates recorded prior to 1/1/1915 as noted in HMIS Reporting Glossary. This could also check for dates in the future and give a warning message when the user saves that it is a date in the future to confirm accuracy.