HMIS Data Standards Dictionary

    A Homeless Management Information System (HMIS) is the information system designated by a local Continuum of Care (CoC) to comply with the requirements of CoC Program interim rule 24 CFR 578. It is a locally-administered data system used to record and analyze client, service, and housing data for individuals and families who are homeless or at risk of homelessness. 
    HMIS is administered by the U.S. Department of Housing and Urban Development (HUD) through the Office of Special Needs Assistance Programs (SNAPS) as its comprehensive data response to the congressional mandate to report annually on national homelessness. It is used by all projects that target services to persons experiencing homelessness within SNAPS and the office of HIV-AIDS Housing. It is also used by other federal partners from the U.S. Department of Health and Human Services (HHS) and the U.S. Department of Veterans Affairs and their respective programs to measure project performance and participate in benchmarking of the national effort to end homelessness.
    The HMIS Data Standards were first published by HUD in 2004 as the HMIS Data and Technical Standards. The original standards served as the foundation for software developers in constructing HMIS applications. In March 2010, HUD updated the Data Standards (March 2010 HMIS Data Standards), primarily to reflect data collection requirements for the Homelessness Prevention and Rapid Rehousing Program (HPRP). HUD, in collaboration with its federal partners, updated the HMIS Data Standards again in 2014 with the release of the 2014 HMIS Data Standards Manual and Data Dictionary. Both documents superseded the previously released HMIS Data Standards. Together, the 2017 HMIS Data Standards Dictionary and Manual are the documentation of requirements for the programming and use of all HMIS systems and comparable database systems,1 effective October 1, 2017.
    This manual is designed for CoCs, HMIS Lead Agencies, HMIS System Administrators, and HMIS Users to help them understand the data elements that are required in an HMIS to meet participation and reporting requirements established by HUD and the federal partners. An HMIS software must be able to collect all the data elements defined within these HMIS Data Standards, support the system logic identified in the HMIS Data Dictionary, and ensure that the visibility of data elements is appropriate to the Project Type and Federal Partner Funding Sources for any given project.
    There are many software products on the market that communities across the county have chosen to use as their HMIS. Each product has unique features and was built to meet the different data collection needs of each community. Each software vendor should provide the guidance, support, and documentation necessary for the CoC to understand the system they are using.

    Communities may elect to add data elements or maintain historical data element collection beyond what is specified in the Data Standards as long as it does not impact the ability of the CoC to accurately collect and report on the required data elements. In these cases, HMIS Leads should work directly with their HMIS vendors to meet their individual needs. 

SUMMARY OF CHANGES

HMIS DATA DICTIONARY OVERVIEW.

  • Introduction

HMIS RELATED DOCUMENTS

  • HMIS Data Standard Documents
  • HMIS Federal Partner Program Manuals

ABOUT THIS DICTIONARY

  • HMIS Concepts and Terms
  • Data Element Structure

PROJECT DESCRIPTOR DATA ELEMENTS

  • 2.1 Organization Identifiers
  • 2.2 Project Identifiers
  • 2.3 Continuum of Care Code
  • 2.4 Project Type
  • 2.5 Method for Tracking Emergency Shelter Utilization
  • 2.6 Federal Partner Funding Sources
  • 2.7 Bed and Unit Inventory
  • 2.8 Additional Project Information

UNIVERSAL DATA ELEMENTS

  • 3.1 Name
  • 3.2 Social Security Number
  • 3.3 Date of Birth
  • 3.4 Race
  • 3.5 Ethnicity
  • 3.6 Gender 
  • 3.7 Veteran Status
  • 3.8 Disabling Condition
  • 3.10 Project Start Date
  • 3.11 Project Exit Date
  • 3.12 Destination
  • 3.15 Relationship to Head of Household 
  • 3.16 Client Location
  • 3.20 Housing Move-In Date
  • 3.917 Living Situation
    • 3. 917A Living Situation
    • 3.917B Living Situation

PROGRAM SPECIFIC DATA ELEMENTS

COMMON DATA ELEMENTS
  • 4.2 Income and Sources
  • 4.3 Non-Cash Benefits
  • 4.4 Health Insurance
  • 4.5 Physical Disability
  • 4.6 Developmental Disability 
  • 4.7 Chronic Health Condition.
  • 4.8 HIV/AIDS
  • 4.9 Mental Health Problem
  • 4.10 Substance Abuse
  • 4.11 Domestic Violence
  • 4.12 Contact
  • 4.13 Date of Engagement
  • 4.14 Bed-night Date
  • 4.18 Housing Assessment Disposition

INDIVIDUAL FEDERAL PARTNER PROGRAM ELEMENTS

CoC Program Element Visibility – Collection Requirements
  • Program Specific Components and Project Types
  • Program Specific Visibility – Collection Requirements
ESG Program Element Visibility – Collection Requirements
  • Program Specific Components and Project Types
  • Program Specific Visibility – Collection Requirements
HOPWA Program Element Visibility – Collection Requirements
  • Program Specific Components and Project Types
  • Program Specific Visibility – Collection Requirements.
  • W1 Services Provided – HOPWA
  • W2 Financial Assistance– HOPWA
  • W3 Medical Assistance
  • W4 T-cell (CD4) and Viral Load 
  • W5 Housing Assessment at Exit
PATH Program Element Visibility – Collection Requirements
  • Program Specific Components and Project Types
  • Program Specific Visibility – Collection Requirements
  • P1 Services Provided – PATH Funded
  • P2 Referrals Provided – PATH
  • P3 PATH Status
  • P4 Connection with SOAR
Pay for Success (PFS) Program Element Visibility – Collection Requirements
  • Program Specific Components and Project Types
  • Program Specific Visibility – Collection Requirements
RHY Program Element Visibility – Collection Requirements
  • Program Specific Components and Project Types
  • Program Specific Visibility – Collection Requirements
  • R1 Referral Source
  • R2 RHY – BCP Status
  • R3 Sexual Orientation
  • R4 Last Grade Completed
  • R5 School Status
  • R6 Employment Status
  • R7 General Health Status
  • R8 Dental Health Status
  • R9 Mental Health Status
  • R10 Pregnancy Status
  • R11 Formerly a Ward of Child Welfare/Foster Care Agency
  • R12 Formerly a Ward of Juvenile Justice System
  • R13 Family Critical Issues
  • R14 RHY Service Connections
  • R15 Commercial Sexual Exploitation/Sex Trafficking
  • R16 Labor Exploitation/Trafficking
  • R17 Project Completion Status
  • R18 Counseling
  • R19 Safe and Appropriate Exit
  • R20 Aftercare Plans
RHSAP Program Element Visibility – Collection Requirements
  • U1 Worst Housing Situation
VA Program Element Visibility – Collection Requirements
  • Program Specific Components and Project Types
  • VA Program Specific Element Visibility – Collection Requirements
  • HUD/VASH and HUD/VASH Other Program Specific Element Visibility – Collection Requirement
  • V1 Veteran’s Information
  • V2 Services Provided – SSVF
  • V3 Financial Assistance – SSVF
  • V4 Percent of AMI (SSVF Eligibility)
  • V5 Last Permanent Address
  • V6 VAMC Station Number
  • V7 SSVF HP Targeting Criteria
  • V8 HUD-VASH Voucher Tracking
  • V9 HUD-VASH Exit Information

METADATA ELEMENTS

  • 5.1 Date Created
  • 5.2 Date Updated
  • 5.3 Data Collection Stage
  • 5.4 Information Date
  • 5.5 Project Identifier
  • 5.6 Enrollment ID
  • 5.7 User Identifier
  • 5.8 Personal ID
  • 5.9 Household ID
  • 5.10 Signed Consent 

REQUIRED COLLECTION POINTS AND METADATA ELEMENTS TABLE SUMMARY

  • Required Collection Points
  • Data Elements with Multiple Collection Points
  • Data Elements with a Single Collection Point
  • Base Metadata
  • Project Identifier, Personal ID, and Household ID
Exhibit 1: 3.917B Flow Chart
              Click HERE for the full manual.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.