Generic Enrollments

Generic enrollments are linked to global enrollments, just as HMIS version specific schema are linked to global enrollments. That way, a global enrollment can span multiple HMIS version specific data standard years. A global enrollment can also link one or more HMIS version specific data standard years with a single generic enrollment, to track non-HMIS aspects of an enrollment.

Generic enrollments can be used for any purpose, and have nothing to do necessarily with HMIS data standards. Generic enrollments must support a few simple and mostly optional fields:

• generic enrollment id: type id
• global enrollment id: type id
• global project id: type id
• date created: type date-time
• date updated: type date-time
• user creating: type user id
• user updating: type user id
• start date: type date-time
• end date: type date-time
• inactive: type boolean
• global household id (optional): type id ; The ID of a household associated with this enrollment

[the following are removed, since they would be in the transactional records within Entity Support]

• data collection stages (optional): type enumeration
  • at entry
  • during enrollment
  • at exit

Service transactions, needs, and other client transactional records can be linked to the generic enrollment via the global enrollment id. Surveys are already linked via the global enrollment ID. With the global enrollment ID, any generic enrollments and/or HUD HMIS enrollments, surveys, and entities for a given client can be retrieved.

Expected functionality:

• Since each generic enrollment is tied to a global project, if a client consent period for allowing access to one or more global projects expires, then access to the generic enrollment data will also expire with the consent expiration.