Clarity Human Services: October 2025 Feature Updates

Release Schedule: 

• All Training Sites: Monday, September 1, 2025
• All Production Sites: Wednesday, October 1, 2025

Additional Details for Data Standards Updates:

Data Standards Release Dates

• System screens
  • September 1: The 2026 System Screens will be released to Training Sites.
  • September 17: The 2026 System Screens will be released to Production Sites, but the screens will be Inactive and will have a DO NOT USE label.
  • October 1:  The 2026 System Screens will be made Active and the DO NOT USE label will be removed.

• New /Updated fields, new/updated picklist options, updated labels, etc
  • September 1: Updated fields will be released to Training Sites
  • September 17: The following new fields/ picklists will be released to Production Sites: Sex, Mental Health Consultation, SSVF Service Category “Healthcare Navigation,” Funding Source - HUD: CoC Builds. The values will be Inactive and will have a DO NOT USE label.

• October 1: Updates will be applied in Production Sites. New picklist values that were added on September 17 will be made Active and the DO NOT USE label will be removed. The following new fields/picklists will be also released to Production Sites: RHY Critical Family Issues, SSVF HP Targeting Criteria, Race and Ethnicity, Retire Funding Sources - HUD: ESG-CV and HUD: HOPWA-CV

• System templates will automatically be updated to include the 2026 standard screens and will be relabeled to 2026 on the following dates:
  • September 1: Training Sites.
  • October 1: Production Sites.

Data Analysis Release Notes

• Data Analysis release notes are included in this article instead of in a separate article.
• The 2025 Data Services Change Log and Known Issues article and the Data Analysis Upgrade Note articles will continue to be released separately. 

Pentaho Release Notes:

• FY 2026 Federal Reporting Updates are summarized in this article. More  information about Pentaho FY 2026 Data Standards impacts  will be provided in Pentaho release notes and standalone articles as it becomes available.
• Pentaho Release Notes - August 2025
  

Included in the October 2025 release:

FY2026 Data Standards Updates

Area of Impact: Program Setup Screens

• Update: 2.02 Program Information
• Update: 2.06 Funding Sources
  • Looker update included

Area of Impact: Profile Screens

• Update: 3.04 Race and Ethnicity
• Update: 3.06 Gender 

Area of Impact: Program Screens

• Update: 3.20 Housing Move-in Date
• Update: 4.05 - 4.10 Specific Disabling Conditions
• New: 4.21 Sex
  • Looker Update Included
• Update: C4 Translation Assistance Needed
• Update: R3 Sexual Orientation 
  • Looker Update Included
• Update: R13 Family Critical Issues
  • Mapping Included
  • Looker Update Included
• Update: V7 HP Targeting Criteria
  • Looker Update Included
• New: V10 Mental Health Consultation
  • Looker Update Included

Area of Impact: Services

• Update: V2 Services Provided - SSVF
  • Looker Update Included
• Update: V3 Financial Assistance - SSVF
  • Mapping Included
  • Looker Updated Included

Area of Impact: DATA IMPORT

• Update: Data Import Tool (DIT)

Area of Impact: SETTINGS and Database

• Update: Operational API
• Update: Zipcode Geography Crosswalk
• Update: New and Updated Screens
• Update: New and Updated Templates

Area of Impact:  Federal Pentaho Reports

• [HUDX-111-AD] HUD CSV / XML Program Data Export 
• [HUDX-223-AD] System Performance Measures  
• [HUDX-224-AD] PATH Annual Report  
• [HUDX-225-AD] HMIS Data Quality Report 
• [HUDX-227-AD] APR 
• [HUDX-228-AD] ESG CAPER 
• [HUDX-235-AD] CE APR  
• [HUDX-231-AD] LSA Export - Systemwide  
• [HUDX-236-AD] LSA - Project Descriptor HDX Upload Test  
• [HUDX-123-AD] Housing Inventory (HIC) Supplemental 
• [HUDX-230-AD] Shelter Count PIT  

Additional Updates 

• Update: Deleting a Portal User (Customer Portal) 
• Update: Operational API: Relation to Head of Household
• Looker Update: Additional Fields Exposed
• Update: Tracked Characteristic Card/Updated Assessment

FY2026 Data Standards Updates

Update: 2.02 Program Information

Overview: Language was added about the appropriate project type for Pay for Success funded projects.

Required Action: Projects funded with Funding Source (funding_source) HUD: Pay for Success (35) and do not provide permanent housing should use Project Type (Field 6) Other (7).

Update: 2.06 Funding Sources

Overview: One funding source is being added, and two are being retired.

The following will be added to core field Funding Source (funding_source): 

• HUD: CoC Builds (56)

The following will be labeled as retired and moved to the bottom of the picklist for core field Funding Source (funding_source):

• RETIRED (HUD: ESG-CV) (47)
• RETIRED (HUD: HOPWA-CV) (48)

Required Action: 

• Update any programs funded by these sources
• Update relevant paper and/or online program setup forms to include 56: HUD: CoC Builds as a funding source and to reflect that 47: HUD: ESG-CV and 48: HUD: HOPWA-CV are retired funding sources.
  
  

Data Analysis Updates: 

Funding Sources 47: HUD: ESG-CV and 48: HUD: HOPWA-CV have been removed and 56: HUD: CoC Builds has been added to the measures that count errors on the DQ Client Program Demographics view of the Data Quality Model. 

56: HUD: CoC Builds has been added to the universe of programs used for the calculation of the measures exposed on System Performance Measures, Measure 4 in the HMIS Performance Model.

Data Analysis Required Action: Identify and update any Looker reports, dashboards, or filters that include Funding Source.

Update: 3.04 Race and Ethnicity

Overview: For Race and Ethnicity (race_ethnicity), the picklist option Hispanic/Latina/e/o has been updated to Hispanic/Latina/o and the Additional Race and Ethnicity Detail (Field 2) should be set to Not Required. 

Required Action: 

• For paper forms using Race and Ethnicity, update Hispanic/Latina/e/o to Hispanic/Latina/o. 
• For custom screens and paper forms using Additional Race and Ethnicity Detail (Field 2), set Data Quality Check to Not Required. Please note: it is possible this is already set to “Not Required” if custom screens were copied from the System profile screen.

Update: 3.06 Gender

Overview: The Gender field (gender)  has been retired from HUD Data Standards. The Gender field will remain in the system and is included in a new Clarity Intake screen for communities who wish to continue using the field. More information about the new Clarity Intake screen can be found here in this article.  

Required Action: For custom screens and paper forms that include Gender (gender), the field may be removed or Data Quality Check set to Not Required based on community determinations.

Update: 3.20 Housing Move-in Date

Overview: Housing Move-in Date must be collected for VA: Grant Per Diem - Case Management/Housing Retention Projects. VA Enrollment screens will be updated.

Required Action: For custom screens and paper forms, update Housing Move-In Date (move_in_date) to allow collection for VA: Grant Per Diem - Case Management/Housing Retention Projects.

Update: 4.05 - 4.10 Specific Disabling Conditions

Overview: The following fields are not required for VA-funded and HUD: VASH programs:

• Physical Disability (health_phys_disability)
• Long Term Physical Disability (health_phys_disability_longterm)
• Developmental Disability (health_dev_disability)
• Chronic Health Condition (health_chronic)
• Long Term Chronic Health Condition (health_chronic_longterm)
• HIV – AIDS (health_hiv)
• Mental Health Disorder (health_mental)
• Long Term Mental Health Problem (health_mental_longterm)
• Substance Use Disorder (health_substance_abuse)
• Long Term Substance Abuse Problem (health_substance_abuse_longterm)

These fields and any related warnings will be removed from system VA Enrollment, VA Status, and VA Exit screens.

HUD: CoC - Youth Homeless Demonstration Program (YHDP) and HUD: CoC Builds (56) has been added as relevant funding sources. 

Required Action: For custom screens and paper forms, the following fields and any related warnings should be removed from VA-funded and HUD: VASH programs:

• Physical Disability (health_phys_disability)
• Long Term Physical Disability (health_phys_disability_longterm)
• Developmental Disability (health_dev_disability)
• Chronic Health Condition (health_chronic)
• Long Term Chronic Health Condition (health_chronic_longterm)
• HIV – AIDS (health_hiv)
• Mental Health Disorder (health_mental)
• Long Term Mental Health Problem (health_mental_longterm)
• Substance Use Disorder (health_substance_abuse)
• Long Term Substance Abuse Problem (health_substance_abuse_longterm)

Update: 4.21 Sex

Overview: A new Core field Sex (sex) will be added with this update.

The Sex field will be added to the system enrollment screens:

• Data Quality Check is set to Required
• The field is visible for all clients

Responses to the Sex field are included in clients' enrollment audit logs.

Required Action:

• Update the appropriate custom enrollment screens
• Update any paper enrollment screens. 

Data Analysis Updates: 

The new Sex field is available in the following Looker models:

• Client Model
• Coordinated Entry Model
• Data Quality Model
• HMIS Performance Model
• Outreach Model
• Population Over Time Model

Data Analysis Required Action:

Add the Sex field to relevant Looker reports or dashboards.

Update: C4 Translation Assistance Needed 

Overview: The following C4 Translation Assistance Needed fields have been retired:

• Translation Assistance Needed (translation_assistance_needed)
• Preferred Language (preferred_language)
• If Different Preferred Language, please specify (different_preferred_language)

Required Action: For custom screens and paper forms, that include the following fields, they can be removed or Data Quality Check set to Not Required:

• Translation Assistance Needed (translation_assistance_needed)
• Preferred Language (preferred_language)
• If Different Preferred Language, please specify (different_preferred_language)

Update: R3 Sexual Orientation

Overview: In the Field Editor, Sexual Orientation (rhy_sexual_orientation) and Other Sexual Orientation (rhy_sexual_orientation_other) are marked as retired. The core fields will be marked retired in the following ways:

Field Display Name	Comments Text	Tooltip Text
RETIRED (Sexual Orientation)	RETIRED: R3: Sexual Orientation	RETIRED: Enter the Sexual Orientation of the client
RETIRED (Other Sexual Orientation)	RETIRED: R3: Sexual Orientation	RETIRED: If Other Sexual Orientation, please describe

In addition, Sexual Orientation and Other Sexual Orientation have been removed from the following system enrollment screens:

• 2026 HHS: RHY Project Enrollment
• 2026 HUD: YHDP Project Enrollment
• 2026 HUD: CoC Standard Project Enrollment
  • The ‘Additional Information’ label is also removed from this screen

Clarity Human Services Required Action:

• Remove Sexual Orientation and Other Sexual Orientation from custom screens if this data will no longer be collected in the community
• Update any relevant paper enrollment forms to remove Sexual Orientation and Other Sexual Orientation if this data will no longer be collected in the community.

Data Analysis Updates: Sexual Orientation (rhy_sexual_orientation) and Other Sexual Orientation (rhy_sexual_orientation_other) will remain in Looker, but are marked as retired in the field’s description. The affected models are: Client Model, Coordinated Entry Model, Data Quality Model, HMIS Performance Model, Inventory Model, Population Over Time Model, and Services Model.

Data Analysis Required Action: Identify and update any Looker reports, dashboards, or filters that include Sexual Orientation and/or Other Sexual Orientation.

Update: R13 Family Critical Issues

Mapping Information Included

Overview: The following fields will be converted from toggle fields in Clarity to picklist fields:

• Unemployment - Family Member (rhy_crit_unemployment_family)
• Mental Health Disorder - Family member (rhy_crit_mental_family)
• Physical Disability - Family Member (rhy_crit_disability_physical_family)
• Alcohol or Substance Use Disorder - Family member (rhy_crit_substance_family)
• Insufficient Income to Support Youth - Family Member (rhy_crit_income_family)
• Incarcerated Parent of Youth (rhy_crit_incarcerated_parent)

The picklist response options for each of the fields above are:

• No
• Yes
• Client doesn’t know
• Client prefers not to answer
• Data not collected

Required Action:

• Update relevant paper enrollment forms to include response options of ‘No’, ‘Yes’, ‘Client doesn’t know', ‘Client prefers not to answer’, and ‘Data not collected’ for the R13 Family Critical Issues fields.

Mapping:

For each of the fields that are/were toggled ON, a Yes value will be applied when the fields are converted to picklist fields.

For each of the fields that are/were toggled OFF, a No value will be applied when the fields are converted to picklist fields.

If there are constraints/eligibility requirements/eligibility presets based on the fields, the constraints will be updated to reflect the following:

• Where the constraint shows the toggle is ON, the constraint is updated to show the response equals Yes
• Where the constraint shows the toggle is OFF, the constraint is updated to show the response equals No.

Data Analysis Updates:

The following RHY Family Critical Issues dimensions have been updated from Yes/No values to the picklist values 0: Yes, 1: No, 8: Client doesn't know, 9: Client refused, and 99: Data not collected in the Client Model, HMIS Performance Model, and Coordinated Entry Model:

• Unemployment - Family Member (rhy_crit_unemployment_family)
• Mental Health Disorder - Family member (rhy_crit_mental_family)
• Physical Disability - Family Member (rhy_crit_disability_physical_family)
• Alcohol or Substance Use Disorder - Family Member (rhy_crit_substance_family)
• Insufficient Income to Support Youth - Family Member (rhy_crit_income_family)
• Incarcerated Parent of Youth (rhy_crit_incarcerated_parent)

The Family Critical Issues Error dimension in the DQ Client Program Specific view for the Data Quality Model has been updated to recognize 0, 1, 8, 9 and 99 as valid codes in data quality checks for the RHY Family Critical Issues dimensions listed above.  In addition, the choices 8: Client doesn't know, 9: Client refused, and 99: Data not collected are reported specifically with their own error messages.

Data Analysis Required Action: Identify and update any Looker reports, dashboards, or filters that use the RHY Family Critical Issues.

Update: V7 HP Targeting Criteria

Overview: The field display names will be updated for ssvf_targeting_field_15 and ssvf_targeting_overrepresented_population. The fields will be updated in both the field editor and on the system VA: Project Enrollment screen.

Current Display Name	Field Data Name	Updated Display Name
Household size of 5 or more requiring at least 3 bedrooms (due to age/gender mix)	ssvf_targeting_field_15	Household size of 5 or more requiring at least 3 bedrooms (due to household composition)
Household includes one or more members of an overrepresented population in the homelessness system when compared to the general population.	ssvf_targeting_overrepresented_population	Households which may include one or more members meeting other criteria for targeting prevention determined by the CoC.

Clarity Human Services Required Action: 

• Update any relevant paper enrollment forms to reflect the updated display names for ssvf_targeting_field_15 and/or ssvf_targeting_overrepresented_population.
• Update the display name for ssvf_targeting_field_15 and ssvf_targeting_overrepresented_population on any custom screens
• Update the Display Name for any additional custom fields that copy/mimic ssvf_targeting_field_15 and/or ssvf_targeting_overrepresented_population on any custom screens you have created
• Update the Field Display Name for any custom fields that copy/mimic ssvf_targeting_field_15 and/or ssvf_targeting_overrepresented_population in the Field Editor

Data Analysis Updates: 

The labels for entry_screen.ssvf_targeting_field_15 and entry_screen.ssvf_targeting_overrepresented_population dimensions have been updated. These dimensions are exposed on the Entry Screen view under the SSVF/VASH group label for the Client Model, Coordinated Entry Model, HMIS Performance Model, and Population Over Time Model.

Current Label	Field Data Name	Updated Label
Household size of 5 or more requiring at least 3 bedrooms (due to age/gender mix)	entry_screen.ssvf_targeting_field_15	Household size of 5 or more requiring at least 3 bedrooms (due to household composition)
Household includes one or more members of an overrepresented population in the homelessness system when compared to the general population.	entry_screen.ssvf_targeting_overrepresented_population	Households which may include one or more members meeting other criteria for targeting prevention determined by the CoC.

Data Analysis Required Action: Identify and update any Looker reports, dashboards, or filters that include ssvf_targeting_field_15 and/or ssvf_targeting_overrepresented_population.

New: V10 Mental Health Consultation

Overview: A new data element V10: Mental Health Consultation has been added as a new Core picklist field.

The response options for the Mental Health Consultation field are:

• Mental health consultation completed
• Mental health consultation being coordinated/arranged with VA provider
• Mental health consultation being coordinated/arranged with other provider
• Offer declined

The Mental Health Consultation field will be added to the following system screen:

• 2026 VA: Project Enrollment screen
  • The field will be in the Additional Information section below the General Health Status field
  • Data Quality Check is set to Required

The field will be visible for heads of household and veterans who are being enrolled in any of the following programs:

• VA: SSVF-funded Homelessness Prevention project
• VA: SSVF-funded Rapid Rehousing project
• VA: Grant per Diem-Case Management/Housing Retention-funded Services Only project

Responses to the Mental Health Consultation field are included in the clients' enrollment audit logs.

Clarity Human Services Required Action:

• Add the Mental Health Consultation field to the appropriate custom enrollment screen(s) in training and live instances.
• Update relevant paper enrollment forms to include Mental Health Consultation.

Data Analysis Updates: 

The Mental Health Consultation field has been added underneath the Entry Screen view in the HMIS Performance Model, Client Model, Population over Time Model, Data Quality Model, and Coordinated Entry Model.  

View	Label	Description	LookML Field Name
Entry Screen	Mental Health Consultation	HMIS Data Element V10	mental_health_consultation

Data Analysis Required Action: Add the Mental Health Consultation field to relevant Looker reports or dashboards.

Update: V2 Services Provided - SSVF

Overview: The System field VA SSVF Service (si_cat_1_2700) will be updated to include “Healthcare Navigation” as a service.

• The Service Title is “Healthcare Navigation”
• The picklist value is 10
• The Category is VA SSVF Service

The “Healthcare Navigation” service will be added to any new programs where the system VA: SSVF Project program template is applied after October 1, 2025. For any existing programs that use the VA: SSVF Project program template, or any existing programs that use a custom VA: SSVF Project program template, the new “Healthcare Navigation” service must be manually added.

New Clarity Interface

Within the new Clarity interface, end users can provide the new VA SSVF Healthcare Navigation service to clients, as well. The steps to provide the new service are the same as the steps to provide any other service using the new Clarity interface.

Required Action:

• Add 10: Healthcare Navigation as a service for existing VA SSVF-funded RRH and HP projects that are using a custom VA: SSVF Project program template
• Add 10: Healthcare Navigation as a service for existing VA SSVF-funded RRH and HP projects that are using the system VA: SSVF Project program template
• Update relevant paper forms to include 10: Healthcare Navigation as a service that can be provided to clients served in VA SSVF-funded RRH and HP projects.

Data Analysis Updates: 

The field Type Provided, under the Services view in the Services Model, has been updated to include the new VA SSVF Service, "Healthcare Navigation." 

The field SSVF Services Provided Error in the Data Quality Model has been updated to ensure the new value "Healthcare Navigation" is not counted as an error.

Data Analysis Required Action: Identify and update any Looker reports, dashboards, or filters that include V2 VA SSVF services.

Update: V3 Financial Assistance - SSVF

Mapping Included

Overview: The date field Event Date of Financial Assistance will be renamed Date Provided for V3 SSVF Financial Assistance services with:

•  A Delivery Type of Single Event
• The Category = VA SSVF Service, AND
• A service item with a Category = Financial Assistance

 The following updates will also be made:

• Two new date fields, Start Date of Financial Assistance and End Date of Financial Assistance have been added
  • These fields are on a single row below the Date Provided field
  • Start Date of Financial Assistance corresponds to FAStartDate in the HMIS CSV Services.csv file
  • End Date of Financial Assistance corresponds to FAEndDate in the HMIS CSVServices.csv file
• The Expense Date field was hidden to avoid repetitive data entry. Instead, the new Date Provided field populates the Expense Date field in the database.
  • The Expense Amount field was relabeled Financial Assistance Amount for SSVF Financial Services only
• On the Modify Expense screen, Expense Amount has been renamed Financial Assistance Amount
• The Date Provided and Start Date of Financial Assistance fields are required to be completed when the user provides V3 SSVF Financial Assistance services to clients
• The End Date of Financial Assistance field is not required at the time the user provides the V3 SSVF Financial Assistance service to the client; it can be added later
• Date Provided populates the Service Start Date field in the database. The Service Start Date data from the database will be used in the HMIS CSV Services.csv file. 

New Clarity Interface:

The same three fields are also available in the new Clarity Human Services interface for V3 SSVF Financial Assistance services with a Delivery Type of Single Event, Category = VA SSVF Service, AND a service item with a Category = Financial Assistance:

• Start Date of Financial Assistance

• End Date of Financial Assistance

• Date Provided

The steps to provide the new service are the same as the steps to provide any other service in the new Clarity interface.

Mapping Provided

V3 SSVF Financial Assistance services that had been set up with a Delivery Type = Long Term will be updated to Delivery Type = Single Event:

• Services updated are those with a service Category = VA SSVF Service, AND the service item Category = Financial Assistance AND the Delivery Type = Long Term
• If there is an Expense Date associated with the service, this date is mapped to Date Provided
• If there is no Expense Date associated with the service, the Start Date of Financial Assistance date is mapped to Date Provided
• If there is no Expense Date and no Start Date of Financial Assistance date associated with the service, “DateCreated” is mapped to Date Provided.

For V3 SSVF Financial Assistance services that were already set up with a Delivery Type = Single Event:

• Services updated are those with a  service Category = VA SSVF Service, AND the service item Category = Financial Assistance, AND a Delivery Type = Single Event
• If there is an Expense Date associated with the service, this date is mapped to Date Provided
• If there is no Expense Date associated with the service, the previous Start Date of Financial Assistance date is mapped to Date Provided
• If there is no Date Provided and no previous Start Date of Financial Assistance date associated with the service, “DateCreated” is mapped to Date Provided.

These updates will be reflected in client service audit logs.

Required Action:

• Update relevant paper forms to include Start Date of Financial Assistance and End Date of Financial Assistance with V3 SSVF Financial Assistance services.

Data Analysis Updates: 

The description for the existing Services Start Date field has been updated to explain that this field is also used as “Date Provided in V3 Financial Assistance - SSVF.”

Two new date fields, Financial Assistance Start Date and Financial Assistance End Date, were added to the “Services” view for the following models: Client Model, Coordinated Entry Model, HMIS Performance Model, and Services Model. 

The new date fields, Financial Assistance Start Date and Financial Assistance End Date, were also added to the “Client Services” view for the following models: Data Quality Model and Reservations Model. 

Data Analysis Required Action: Identify and update any Looker reports, dashboards, or filters that include V3 SSVF Financial Assistance services.

Update: Data Import Tool (DIT)

With this update, the Clarity DIT user can:

• Upload a FY26 Data Standard-compliant HMIS CSV v1.0 zipfile and equivalent Clarity XML file to the DIT (FY24 format option is still available to select as well)
• Validate the uploaded HMIS CSV v1.0 files and equivalent Clarity XML file against the FY26 HMIS CSV v1.0 Specification and the the new FY26 HMIS-compliant Clarity XML Schema, respectively
• Import the same HMIS CSV/Clarity XML zipfile file into Clarity Human Services.

Please note that:

• All applicable FY26 HMIS Data Standard changes implemented in Clarity for this release are reflected in this new DIT release.
• The system will continue to import Clarity XML with Gender and Sexual Orientation fields.
• There is a small validation improvement: For V3 Financial Assistance – SSVF, RecordType 152 if the TypeProvided value in the CSV or XML record (such as Tenant Incentive = “18”) is not mapped to a Clarity Service Item of Clarity type "SSVF Financial Services", this single Service record will be rejected, and a non-blocking error (rejected) will be logged.
• The customer-available DIT CSV Validations catalog has been updated with these changes.

Required Action: None.

Update: Operational API

Clarity Operational APIs Have Been Updated To The FY2026 Data Standards. 

• The updated Operational API GraphQL Schema and example Postman Collection will be released as soon as they are available, with an incremented version number (currently at v2.3.0) to reflect these changes.  
• All applicable FY26 Data Standard changes will be made.  These include changes to, or additions of, the following HMIS Data Elements:
  • 4.21 Sex
  • Gender (will remain in the API, but no longer possessing the HMIS data element ID of #3.06 for FY26). 
  • R3 Sexual Orientation
  • R13 Family Critical Issues
  • V2 Services Provided SSVF
  • V3 Financial Assistance SSVF
  • V10 Mental Health Consultation
  • Removal of C4 Translation Assistance 

Update: Zipcode Geography Crosswalk

Overview: Reference data and lookup logic has been updated to align with HUD’s 2026 Data Standards ZIP code/geography type crosswalk. 

Required Action: None.

Update: New and updated Screens

The following new System Profile screens will be created: 

• [2026] HMIS General Intake
• [2026] HMIS Minimum Intake

The following new Profile screen will be created:

• [2026]  Clarity General Intake
  • This is a new system profile screen that includes the retired Gender field.

The following new System Enrollment, Status, and Exit screens will be created: 

• [2026] HUD: CoC Standard Project
• [2026] Minimum Project
• [2026] HUD: HOPWA Project
• [2026] HUD: YHDP Project 
• [2026] HHS: PATH Project
• [2026] HHS: RHY Project
• [2026] VA: Project

The following new Enrollment, Status, and Exit screens will be created:

• [2026] Clarity Project
  • These new system screens exclude the new Sex field.

The following new System Post-Exit Screens will be created:

• [2026] HUD: CoC Standard Project
• [2026] HHS: RHY Project

Screen Update Schedule

• September 1: The 2026 System Screens will be released to Training Sites.
• September 17: The 2026 System Screens will be released to Production Sites, but the screens will be Inactive and will have a DO NOT USE label.
• October 1:  The 2026 System Screens will be made Active and the DO NOT USE label will be removed.

Update: New and updated Templates

The following new Program Template will be created:

• [2026] Clarity Project
  • This is a new system Program Template that includes the new [2026] Clarity screens.

The following Program Templates will be updated:

• [2026] CoC Project [Standard]
• [2026] Minimal Project
• [2026] HUD: HOPWA Project
• [2026] HUD: VASH Project
• [2026] HUD: YHDP Project
• [2026] HHS: PATH Project
• [2026] HHS: RHY Project
• [2026] VA: GPD/HCHV Project
• [2026] VA:SSVF Project

Program Template Update Schedule

October 1: Existing 2024 System templates will be automatically renamed and screens replaced with 2026 System screens. 

• Custom templates will need to be updated manually.

Update: Federal Reporting

The following updates are being applied to Federal Reporting to align with FY 2026 Data Standards and relevant Reporting Specifications:

• [HUDX-111-AD] HUD CSV / XML Program Data Export 

XML Deprecation	Clarity XML: Updated to align with FY 26 Updates; Gender and Sexual Orientation are no longer required for import
Characters Permitted in String Fields	Allowed Character Set updated to UTF-8 (No Report Impact)
Export.csv Updates	Source ID: SourceID logic was updated to return a concatenated list of all relevant CoCs when applicable. Maximum length updated to 350 characters (S350), previously S32.
Client.csv Updates	3.04 Race Ethnicity: Updated column label for Hispanic/Latina/o data  3.06 Gender: Removed from CSV Report Output Format   4.21 Sex: Added the New HMIS Element   Veteran Element Clarification: Expected to be null for non-veterans (No Report Impact)
Enrollment.csv Updates	R13 Family Critical Issues: Updated applicable list to 1.8 No/Yes/Reasons for Missing Data to accommodate the updated picklist response options (8/9/99)  V10 MentalHealthConsultation: Added the New HMIS Element  R3 Sexual Orientation: Removed from CSV Report Output Format  C4 Translation Assistance Needed: Removed from CSV/XML
Exit.csv Updates	Applicable Lists were updated from 1.7(No/Yes/Missing) to 1.10(No/Yes) the following Elements/Columns:   R18.1Counseling Received  R18.A Individual Counseling, Family Counseling, Group Counseling  R18.3 Post Exit Counseling Plan  R20.A  Email Social Media
CurrentLivingSituation.csv Updates	4.12.3 VerifiedBy: Maximum length updated to 200 characters (S200)
Services.csv Updates	V2.2 SSVF Services: New Healthcare Navigation (Value = 10) added to List V2.2 SSVFServices; Returns in TypeProvided column in Services.csv  V3 SSVF FA Service Updates: Date Provided. FA Start Date, and FA End Date have been added to the Standard V3 SSVF FA Service Configuration, in addition to updates to Expense Record display behaviors. As Date Provided will no longer need to be inferred for these records, the export will return the following data when compared to the Clarity UI:  Delivery Type = Single Event  DateProvided: Manually Entered Display Name in Services UI “Date Provided” (previously Event Date)    FAAmount: FA Amount  FAStartDate: Manually Entered Start Date of Financial Assistance Field  FAEndDate: Manually Entered End Date of Financial Assistance Field

• [HUDX-223-AD] System Performance Measures  

• • Updates were applied to Measure 1b, Measure 2, Measure 3, and Measure 4 to ensure alignment with the SPM specifications. 

• [HUDX-224-AD] PATH Annual Report  

• • Updates were applied to update relevant row number and table references, removed Q26a. Gender, added Q26l. Sex,  and improved logic for Q26f. Co-occurring disorder, Q26g. Connection with SOAR, and Q26k. Domestic Violence to return the latest non-null value within the enrollment.  

• [HUDX-225-AD] HMIS Data Quality Report 

• • Updates were applied to remove Gender data quality checks from table Q2. Personally Identifiable Information (PII) and update logic in table Q7. Inactive Records: Street Outreach and Emergency Shelter – Contact to exclude Emergency Shelter – Night-by-Night enrollments and include PATH-funded SSO enrollments.  

• [HUDX-227-AD] APR and [HUDX-228-AD] ESG CAPER 

• • Updates were applied to remove Gender references/tables (Q6a. DQ Table Row, Q10. Gender, Q25c. Gender – Veterans, Q26c. Gender of Chronically Homeless Persons, Q27c. Gender – Youth), remove Q24d. Translation Assistance Needed, and Q24c. Sexual Orientation of Adults in PSH, added table Q24e. Sex, and updated Hispanic/Latina/o Labels. 

• [HUDX-235-AD] CE APR  

• • Updates were applied to remove Gender references in the Q6a. Data Quality Table, and Report Universe/Q4 Logic based on CE APR specification updates where there must be “at least one [CE Participation Status] (2.09) record with [Project is a Coordinated Entry Access Point] (2.09.1) = yes (1)”. 

• [HUDX-231-AD] LSA Export - Systemwide  

• • LSA updates are ongoing as we work with LSA TA Partners to discuss relevant shifts. Updates at this time include removing Gender references, updating AHAR labeling to AIR (Active in Residence), and logic updates for HHChronic (LSAExit.csv) and active client logic on a specific date for Emergency Shelter – Night-by-Night Enrollments.  

• • As updates approach finalization, downstream logic updates will be applied to: 

• • • [HUDX-236-AD] LSA - Project Descriptor HDX Upload Test  

• • • [HUDX-123-AD] Housing Inventory (HIC) Supplemental 

• [HUDX-230-AD] Shelter Count PIT  

• • Updates were applied to remove Gender from the PIT table shell and Persons by Programs Table and update Hispanic/Latina/o labels.  

General Report and Custom Report Impacts

General reports will be updated to align with FY 2026 Data Standards and impacted custom reports have been identified. Additional information about general and custom reports will be communicated as it becomes available via Pentaho Release Notes and/or targeted communication/documentation.

Additional Updates

Update: Deleting a Portal User (Customer Portal)

System administrators now have the ability to delete a Customer Portal user.

New Settings

A new toggle field, Delete Portal User Accounts, has been added to SETUP →SETTINGS→Customer Portal.

• The field appears when Customer Portal Enabled = ON
• End users with the Admin access role type AND Setup = ON in their access role can enable or disable this field
• The field is only available in instance-wide settings; this setting is not available in CoC Override settings
• When this field is ON, System Administrators (users with access role type = Admin) can manually delete Customer Portal user accounts.

A new picklist field, Automatically Delete Portal User Accounts, has been added in SETUP→SETTINGS→Customer Portal:

• The field appears when Delete Portal User Accounts = ON
• Users with the Admin access role type AND Setup = ON in their access role can select a response for this field
• The field defaults to None but is editable.

When any selection other than None is chosen for this field, inactive Customer Portal user accounts are automatically deleted after the threshold/number of days selected occurs.

The picklist response options are:

 

Deleting a Portal User Manually

When the account is inactive: System Administrators are able to manually delete Customer Portal user accounts for client accounts that are inactive.

When the System Administrator clicks on the “Inactive” status on the client’s Clarity profile, a CUSTOMER PORTAL CONNECTION pop-up appears that shows the client’s name, Email address, Phone number, Inactive since date and time, and a DELETE PORTAL ACCOUNT button.

When the user clicks on DELETE PORTAL ACCOUNT, a pop-up warning message appears that reads:
This will delete the client’s Portal account. Please confirm the removal of this record.

When the end user clicks OK, the user’s account is deleted. After the user’s account is deleted, the client’s profile in Clarity will show Send Invite.

When the user clicks Cancel, the end user remains on the Customer Portal Connection pop-up and the user’s account is not deleted.

When the account is connected: If the Customer Portal user’s account is Connected and the System Administrator wants to delete the account, they have to disconnect the account first. The System Administrator would click on Connected in the client profile, opening the Customer Portal Connection pop-up, and click on DISCONNECT.

 

Deleting a Portal User Automatically

If the Automatically Delete Portal User Accounts Threshold setting is enabled, inactive Customer Portal user accounts can be automatically deleted. When any selection other than None is chosen for this field, inactive Customer Portal user accounts are automatically deleted after the threshold/number of days selected occurs.

If a portal user’s account is Connected, then the user’s account will not be automatically deleted.

Required Action: None.

Update: Operational API - Head of Household

Prior to this update, “OtherProfileHouseholdMember” and  “ProfileHouseholdMember” were missing a quick way to retrieve the member’s relationship to the rest of the household. Now, two additional properties to the Operational API have been added:

• the Profile Household Member’s and Other Profile Household Members’ relationship to the Head of Household as “relationshipToHoh”, and
• the  Other Profile Household Members’ status as “head of that particular household?” [true/false] as “isHead”.

Operational API Schema changes (reflected on the right, which is this changeset version, v2.3.0):

Required Action: None.

Looker Update: Additional Fields Exposed

Date Updated Fields 

The field Date Updated has been updated to a dimension group, just as the field Date Created Date is, containing values for "Date," "Month," "Quarter," "Time," "Week," and "Year." By making this a dimension group, the label for the Date Updated field will change.  However, cases where Date Updated was used previously will still function as before. The following will be available in the Client Model. 

The field Hidden has been added to the Project Descriptor Model, under the "Questions" view.  This field displays the value of the "Hidden" toggle associated with each field per screen in Clarity.

VI-Y-SPDAT Fields

VI-Y-SPDAT fields that overlap with VI-SPDAT are available in the same VI-SPDAT fields and can be pulled from the Client Assessments view.

VI-Y-SPDAT Assessment  Question 8, Question 15a, and Question 24 descriptions have been updated.  Also, the VI-YSPDAT Assessment V2 Question 8, Question 27, Question 28c, and Question 7 have been added within the VI-Y-SPDAT Assessment Questions section underneath the "Client Assessment" in the Coordinated Entry Model and the Client Model.

Data Analysis Required Action: None.

We Welcome Your Ideas

We encourage you to suggest improvements and new features for our products. You can create feature suggestions or vote, watch, and comment on existing suggestions at ideas.bitfocus.com. Refer to our Feature Suggestions article for additional details.  

New and Updated Help Center Resources

We will either update or create the following articles in response to this Clarity Human Services update by EOD, Wednesday, October 1, 2025.

Reminder: Feature updates will be available in all training sites on Monday, September 1, 2025, and in all production sites on Wednesday, October 1, 2025. FY 2026 Data Standards updates will be available on these dates, but also follow a more nuanced schedule, which is detailed at the top of this article. Links and articles will be added here when articles are live with updated or new content.

Updated Articles	New Articles
System Advanced Options: Customer Portal

 

Published: 08/25/2025