A ClientTrack client reported their LSA was rejected in HDX 2.0 due to the LSA Export including a future dated project. A data liaison confirmed with the community that no future dated projects should be included in the LSA.

We verified with Abt Associates on 12/7/2023 that the LSA specs do not specify to exclude future dated projects, and the issue is with the flags within HDX 2.0 being out of sync with the specifications. Abt is looking to resolve this issue and there are no updated needed to the LSA in ClientTrack.

Flag is reporting that there are clients enrolled in the project when the HMIS Participation Status is ‘Not Participating’. This is likely an issue related to the LSA Spec & Sample Code.

LSA Code for DQ Section 10.5 is looking to compare HMIS Participation Status versus Enrollments. When an enrollment has no end date (as of the Report End Date), and the HMIS Participation Status End Date is not null, the LSA code looks for the End Date of the HMIS Participation Status to be ≥ to the Enrollment End Date. Because there is not Enrollment End Date, it's not returning an HMIS Participation Status which is causing the error.

Discrepancy between LSA Person and LSA Calculated around clients with Race and Ethnicity value of 6.

Known issue on the HUD Weebly - Waiting on update from Abt

From the HUD Weebly Page:

DateToStreetESSH is not calculating Project Type 0 in the calculation so the number is higher than expected because the report is not able to see the Approximate date this episode of homelessness started.

(Seen in CSV Export file, which is used in the LSA)

The 12/19/2023 release to include RRH: Services Only projects has led to several new vendor flags popping up for communities with these project types.

We've identified this issue as a mistype within our LSA code where ProjectType = 1 was being used instead of ProjectType = 15.

Based on the HDX Weebly page, the Red Banner across the top of the flag report is caused by an unknown structural issue with the upload. Communities are instructed to reach out to their data liaison to investigate further.

As of 12/20/2023, these are believed to be resolved. If you are still receiving a Red Banner upon upload to HDX 2.0, please reach out to your Data Liaison.

There is a known issue for Flag 1338 regarding clients without an Exit Date and HMIS Participation Status' with an End Date. Please see above.

There are other situations that could cause this flag:

1. The project is missing an HMIS Participation Status entirely, or for a period of time between the Project Operating Start Date and the Report End Date
   1. The project has an HMIS Participation Status that aligns with the Project Operating dates, but there are clients with enrollments that pre-date the Project Operating Start Date. This information can be located by using the Calculated Explorer Tool.

There is a common flag generating for multiple CoC's. These flags outline that the 2023 HIC as compared to the LSA Inventory File are not lining up. A common cause of this issue is that the program inventory is being excluded from the LSA run because there is not an active Program Grant attached to the Project in Project Setup. LSA and the Data Standards both state that a Funding Source is a required field, and there must be at least one per project.

Users are advised to review projects to ensure there is an active Program Grant. For those users who have access to Query Designer, the query below can be exported and imported to your environment to review the Projects that have the missing Program Grant.

Right click this box and select ‘Save As’. 

This file needs to save as an XML file in order to be correctly imported into the system.

Flagging when the Count of Chronically Homeless Households is different than the Chronically Homeless Adult Head of Household count. 

Through investigating certain communities' flags, we've found that these are a few one-off data scenarios. If your community is receiving this flag and need assistance in identifying the clients behind this, please submit a ticket through support for Eccovia staff to review. 

Example Client Scenario:

Client A is enrolled in two projects during the LSA Reporting Period.

• Project A: Enrolled 1/1/2023 - 3/31/2023
  • Disabling Condition = No
  • Prior Living Situation = Chronic Homeless 
• Project B: Enrolled 5/1/2023 - 9/30/2023
  • Disabling Condition = Yes
  • Prior Living Situation = Chronic Homeless

For LSA purposes, this client is considered to be a Chronically Homeless Individual. But when the LSA calculates the specific Chronically Homeless Adult Head of Household for Project A, the client isn't appearing because they weren't CH in that project due to having their Disabling Condition as no.

We know this can be a real-world scenario when a client learns of a new disability after their first enrollment, or doesn't have a strong enough rapport to feel comfortable disclosing their disabling condition with Project A. So there isn't necessarily data to correct here, but there may need to be a written explanation for the specific client situation. 

Flagging when the count of Heads of Household is higher than the Count of Individuals in LSA Calculated. The Heads of Households are counted by taking the (HoH Client ID + the Household Type). The Individuals are counted by taking the distinct count of Client IDs in the population during the reporting period.

The issue arises when the Household Type has changed throughout the reporting period. So the Head of Household could have more than one count for the Heads of Household.

Through investigating certain communities' flags, we've found that these are a few one-off data scenarios. If your community is receiving this flag and needs assistance in identifying the clients behind this flag, please submit a ticket through support for Eccovia.

Example Client Scenario:

Client A ages into adulthood during the LSA reporting season

• Client is 17 from 10/1/2022 - 5/31/2023
  • Household Type = Child Only Household
• Client is 18 from 6/1/2023 -9/30/2023
  • Household Type = Adult Only Household

For LSA purposes, this client has two separate households being counted because their original Household Count is ClientA+ChildOnly, but it shifts to ClientA+AdultOnly.

We know this can be a real-world scenario when a client ages into adulthood, or the head of household is changed over time, or case members are exited from the household. There isn't necessarily data to correct here, but there may need to be a written explanation for this specific client situation.