-
-
Notifications
You must be signed in to change notification settings - Fork 0
HMIS Boundary
On Record can eventually complement a Continuum of Care, HMIS, coordinated entry, or Shelter Ready workflow. It is not an HMIS because it has signed records or a map.
Public: consented, de-identified asks, exchanges, service-directory facts, and neighborhood aggregates. Private: identity, enrollment, coordinated-entry assessments, case management, disability/health details, victim-service records, recovery material, and provider audit logs.
Do not add HUD data elements to the public schema for convenience. A protected integration must map the minimum fields to the current HUD HMIS Data Standards release and local CoC dictionary, with versioned tests. Victim-service providers may require a separate workflow under VAWA, FVPSA, and related rules.
Before enabling a connector, document fields and direction of flow, legal basis and notice, roles, retention/deletion, correction/withdrawal/grievance, threat model, synthetic fixtures, incident plan, freshness/provenance, and rollback. A connector that cannot answer these questions stays disabled.
On Record is a prototype. Do not enter real protected information. Guidance should be reviewed before each pilot or distribution. Return to Home · Report a security issue
About the site
Audience guides
Commitments and tools
Governance and technical
Participation