Note: This update applies to ETO customers using HMIS functionality for HUD-funded programs.
Overview
This release includes comprehensive updates to ETO's HMIS functionality in preparation for the HUD FY2026 data standards. These changes ensure alignment with HUD's latest compliance requirements and support streamlined data collection, reporting accuracy, and improved client assessments.
Key updates include enhancements to demographics, TouchPoint forms, conditional logic, CSV exports, and validation rules. Organizations using HUD-funded projects should review these updates closely to prepare for the new reporting standards effective FY2026.
Enhancements
Note: All ETO enterprises will see an updated option to add Regex fields when adding a text element. Any user with access to edit TouchPoints will see this option, as seen below.
Demographic and Assessment Updates
New "Sex (HUD)" Demographic:
A required, exclusive-choice demographic was introduced for HMIS sites with options: Female, Male, Client Doesn't Know, Client Prefers Not to Answer, Data Not Collected.
This new demographic is now included in the Client.csv data pull and subject to validation if left blank (when required).
Race/Ethnicity Option Update:
Updated the term "Hispanic Latina/e/o" to "Hispanic/Latina/o" across demographic fields and CSV outputs for consistency with HUD's updated terminology.
Retired Demographics:
The following demographics have been disabled and removed from data pulls and validations:
Gender (HUD)
If Different Identity...
Pseudonym Enhancements:
Added standardized pseudonyms to custom demographics (e.g., HUD Sex, HUD Ethnicity) to ensure consistency in data exports and compliance checks.
Updated Logic for Missing Demographic Validation:
Validations now correctly identify missing "Sex (HUD)" values only when the field is marked required in the site's settings.
TouchPoint and Form Logic Updates
V1.5 and V1.6 HMIS Data Standards Implementation:
All required updates for both HMIS v1.5 and v1.6 have been applied, including:
Text changes (e.g., replacing Emergency Housing Voucher with Housing Stability Voucher)
Conditional logic adjustments for field visibility and requirements
Updated CSV version metadata to reflect "2026 v1.0"
New Conditional Logic for Housing Move-In Date (3.20):
Added rules to handle special cases for:
Pay for Success projects with "Other" project type
Projects funded by VA: Grant Per Diem - Case Management/Housing Retention
Project types under Permanent Housing (PH)
Mental Health Consultation (V10):
New multiple-choice field added to the HUD Assessment form.
Logic updated to display the field only for veterans, based on funding source and project type.
Element is included in the Enrollments.csv export.
HUD CoC Codes & Formatting Enhancements:
Improved validation rules for HUD-assigned CoC codes to ensure correct formatting.
Added regular expression enforcement on form fields and data exports.
TouchPoint Option Updates:
Added new option "Healthcare Navigation" to element V2.02.
Updated question text for V7.P and V7.Q to align with HUD's revised language.
Funding Source Updates
Added Funding Source:
"HUD: CoC Builds" has been added and integrated into multiple conditional rules across HUD forms and validations.
Retired Funding Sources:
"HUD: ESG-CV" and "HUD: HOPWA-CV" have been disabled across the platform.
Removed from Rules:
Veteran-specific funding sources (e.g., VA: GPD programs, HUD VASH) have been removed from conditional logic affecting disability and health-related fields (4.05-4.10).
Expanded Rules:
"HUD: CoC - Youth Homelessness Demonstration Program (YHDP)" added to relevant rules across Coordinated Entry and Street Outreach programs.
CSV and Export Updates
Client.csv and Enrollment.csv Enhancements:
New columns added for "Sex (HUD)" and "Mental Health Consultation."
Sanitization logic now applied to all text values in CSV exports, stripping invalid characters and escaping quotes to ensure clean formatting.
Export.csv Improvements:
CoC Code and SourceType columns updated to align with HUD requirements.
Additional logic added to validate inputs based on regex patterns.
Disabled Translation-Relation Fields:
Elements and rules for "Translation Assistance Needed", "Preferred Language", and related fields have been disabled and removed from CSVs and validations.
Action Required for Organizations with ETO HMIS
Review and update internal documentation and staff training to reflect the new "Sex (HUD)" demographic and retired fields.
Update any custom reports or processes that reference deprecated fields like "Gender (HUD)" or "Translation Assistance Needed."
Confirm proper visibility of the Housing Move-In Date and V10 elements based on your project types and funding sources.