Enrollments
An HMIS Enrollment at the most basic level records assistance provided to a client, and the client’s information at 3 different data points, Entry Exit and Annual Assessment/Update.
There are things to note, all enrollments must collect Universal Data elements.
There are different Enrollment types depending on the funding source for the project, these are RHY, SSVF PATH, CoC and Enrollment Types questions are further managed based on the project type, so a CoC Permanent housing project has different requirements than an RHY Emergency Shelter Project. An enrollment record must contain the Start Date, EnrollmentID Exit Date, Houshold ID(for families) and the required data elements . HSlynk handles these by using different APIs for them.
An enrollment may span multiple years so it is possible that an enrollment may exist during two different standards of data collection. So we may have to different records for the same enrollment in HSlynk. A global enrollment ties these together so that we may reference only 1, we should always display the data elements collected in the latest schema as that is the most likely to be used. We should also have the option to review the data from the prior schema if needed.
Because enrollments can be shared between families, we need to find a way to manage this within HOME.
HOME must pull existing enrollments from HSlynk and display them for a client. Global enrollments should be managed automatically within Hslynk but we should still have a way to merge 2 enrollments manually if they are the same one. (low priority) Global enrollments also should be able to be created for NON-HMIS Data. and we are moving surveys to be under enrollments. so for example, if a client wants to do a VI SPDAT they may add an enrollment which would be a new global enrollment, and then prompt them to do the survey required. so we need a way to tie the surveys to the enrollment