Concurrent / Overlapping Enrollment Alert
Customer requests a feature to alert a user that is creating a new Enrollment for a client when there is already another open Enrollment (i.e. without an Exit Date) at another Agency that would overlap.
Thank you for your feedback. We are currently reviewing this request.
Prevent user from entering an enrollment project start date or end date that overlaps with an existing enrollment for the same client in same project.
Users often back-date new enrollments to when they first enrolled a client who had been previously exited. This creates duplicate enrollments for the same time period. They also enter enrollments that they do not realize have already been entered (and exited). They can also update an end date to overlap with a later existing enrollment, As a result we are finding over one thousand duplicate enrollments each year in King County.
If a family who is in one program gets enrolled in another, is there a way to get a notification in the system?
1.) When Agency has an active program enrollment if the client becomes enrolled in another's Program a notification would be sent to the assigned staff.
example, if someone is in a Family Shelter program, and they get enrolled in a rapid rehousing program, is there a way to set up a notification to the folks at the family shelter so they can serve their families better?
[OVERLAPPING ENROLLMENTS] Add ability for users to get a warning note when they are attempting to enroll a client who is at the same time enrolled in another residential project (within the same CoC)
"Hello Support Team,
The majority of our lingering error flags we received from HUD TA’s feedback about our LSA submission were caused by the overlap of residential project stays. Despite the high penalization of overlapping enrollments in the LSA, currently we don't have any procedure in placed that helps us identifying residential overlapping enrollments within the whole CoC.
We believe that Bitfocus could help their customers tackle this issue, if a system enhancement is implemented in Clarity so that users get a warning note when they are attempting to enroll a client who is at the same time enrolled in another residential project. As this would be a preventive initiative, as opposed to a corrective initiative, this would avoid the creation of overlapping enrollments in residential projects in the first place. Therefore, this feature would be very powerful tool to improve data quality and minimize the number of errors in our next LSA submission.
Since I know Bitfocus strives for supporting their users as best as possible, I would like to request this petition to be forwarded to the team in charge of making system enhancement decisions.
Thank you very much,