Skip to content
← Clarity Human Services

How can we improve Clarity Human Services?

Clarity Human Services

Categories

(thinking…)

Quality Assurance: Chronological Date Entry Logic

Users at times enter in start dates that occur after the exit date or vise versa. Similarly, users enter Housing Move-in date that may be outside the enrollment (before start date or after exit date).

While there are canned reports ([DQXX-121] Project Start Date > Project Exit Date, [GNRL-106] Program Roster), a pro-active approach would be better.

Also, include logic that detects if enrollment dates are future dated and either generate an alert or possibly and this as "On/Off" switch for system admins to manage.

29 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Rene Ortega shared this idea  ·   ·  Report…  ·  Admin →
Comments are closed An error occurred while saving the comment
  • Jessica Salazar commented  ·   ·  Report

    This aligns with another idea I posted that recommends HUD standards are validated by the system at the point of data entry. Similar to this suggestion would be the Engagement Date for Outreach projects, they should be dated after enrollment start date, and before enrollment exit date. There is the Move in Date, that should also be after enrollment start date and before exit date. Program service dates would be the same. There is currently a check at exit that allows the control of service end dates from going beyond an enrollment exit date, however it is still possible to bypass this. These are just a few examples of how the system could enforce many data standards and hopefully minimize data integrity issues caused by naturally existing human error.