Skip to main content
All CollectionsWhat's NewRelease Notes2022 Release Notes
Apricot for Homelessness | Compliance Reporting 3.8.0
Apricot for Homelessness | Compliance Reporting 3.8.0

This release includes several enhancements and a defect fix related to HMIS reporting, released March 17, 2022

Updated over a year ago

Overview

This release includes several enhancements and a defect fix related to HMIS reporting.

Enhancements

The following enhancements related to HMIS reporting are in this release:

  • For the Longitudinal Systems Analysis (LSA) report, we have added logic to the GeographyType crosswalk. Now, we have implemented logic to the LSA report that will automatically correct the GeographyType when that value is incorrect (based on HUD's crosswalk documentation) or empty. We have also added a table to the report output that will display to the end user the records that were corrected in this manner. Below is a screenshot of what the report output will now look like if discrepancies are found:

Table

Description automatically generated with medium confidence
  • The Point In Time (PIT) report has been updated to match the FY 2022 standards. For more information, please see HUD’s documentation.

  • For the Coordinated Entry Annual Performance Report (CE APR), we have implemented logic to produce an error message when there are no organizations/projects that meet the criteria to report on. The report will not run if there are no organizations or projects to report on. Below is a screenshot of the error message that is now produced:

Background pattern

Description automatically generated
  • We have added the "Excluded Enrollments With More Than One HoH Per HouseholdID" table to all HMIS reports, as opposed to just the LSA. Below is an example of the newly added table for the System Performance Measurement report.

Graphical user interface, application

Description automatically generated

Fixes

We also fixed the following defect:

  • Previously, for APR Q27f the report was not counting participants properly. Now, participants are counted on their respective exit destinations if they classify as a youth >= 12 <= 24 years of age.


Did this answer your question?