Longitudinal Systems Analysis Report Clarity integration with HUD LSA validation flags and errors

The key idea is that a user wouldn't need to leave the Clarity app to submit an LSA and receive the LSA report flags. Flags are ingested into Clarity, and the Clarity UI can help resolve the flags.

“It seems like if you’ve got control of the LSA Export compiler, and if you’re hashing (storing a persistent record) of the data going into it, it would be simple to connect the dots backward to the origin of the error.

Right now, everyone in the country is doing this manually or using Jesse’s Jorstadt’s tool that reads the HUD CSV Export data instead of the LSA Export and figuring out the difference manually.

So a Clarity LSA export API would send off an LSA CSV file set. Then, the LSA report submission flags come back from HUD's LSA server as a CSV file. Then that LSA flags CSV file is read in by Clarity, and then those parsed flags get stored and are viewable from the Clarity UI, so you never have to leave Clarity to submit your LSA and receive the flags. Corrective action for the flags could be proposed by Clarity at a client record level.

[anonymous customer submitter]

End users have provided a lot of feedback in our implementation about reading through case notes in Clarity. They find it time consuming to open each individual case note to read the notes, or to run the "Case Notes" report on the Client Profile.

It would be very helpful to have a pop up window that displays the note details when you hover over the case note. This would be similar to the way Referral notes are set up; if you hover over the "comment" icon for the Referral on the history tab, a pop up window appears and displays the most recent Referral note. Could this same logic be applied to individual case notes that are added to a client's file and/or program enrollments?

We would like to see updates to the HMIS Population Over Time model

It would be useful to have more data elements including:

a. Household Type

b. Relationship to Head of Household

c. Project Start/Exit Month/Year just like setup in HMIS Performance and Client Model.

d. Reporting Period Start/End Date

e. Referrals

Etc.

1. It is currently difficult to perform population-based measure without additional data elements in this model. Using a Merge Query doesn't work for visualizations requiring pivot. For example

a. How to get Households served by different project types over time pivoted by Household Type?

b. In a quarter – how to create a table of client counts with first, second, and third month of quarter as column?

Documentation Requirements- Allow for logic/conditions when configuring documentation requirements.

When configuring documentation requirements for a program, you can only list required documents but do not have the ability to indicate AND/OR conditions. The way it works now, you can add multiple documents but the system thinks that all documents are required. This is problematic because, for some programs, we want to indicate that a driver's license OR a passport is required but the system would think both are required.

For example, for housing programs, clients would only need to show one form of ID. Either the driver's license or a passport, not both. We need a way to include conditions using and/or statements to benefit from this feature.

We wanted to request a feature enhancement regarding audit logs. Our hope is that we would be able to report on a history of changes to client profile data. We would like to be able to identify the fields that were changed, the user that made the changes, and the date that the changes were made. This is currently available to system admins on a limited basis by going into individual client profiles and reviewing an audit log, but it would be helpful to be able to run a canned report or even have a Looker model dedicated to tracking an audit log for changes to client data.

What we're looking for is something similar to the [STFF-104] Staff Client Data Activity Report, but we're looking for a little more detail on the specific changes that were made. For example, listing the data entered for each field at each update. We would like the ability to see the history of data entered for a client from client creation and every subsequent update after that.

Currently Assessment Due Warnings only populate for HUD-required Annual Assessments. We would like to see the option to set Assessment Due Warnings for status update screens, so that users can receive reminders to complete status updates on a more frequent basis. For example, if the Case Status field in the program template is set to "Every Month", the user would receive an Assessment Due Warning each month a client is active in a program.
In addition, we would like to see the "Assessment Due" date on the "Status Due" tab of the Caseload tab to reset each time a status assessment is completed, to provide a reminder for the next date an assessment is due to be completed.

For agencies who are trying to save time, it would be very beneficial to have a download/print function within Clarity, tied to the enrollment form. Some agencies can enter directly into HMIS, and do not need a paper copy, but there are many agencies who are required to store paper forms. They have to do their enrollments on paper forms, then enter into HMIS. If you could print the form, it would save them a lot of time. Currently, when you print an enrollment form using the basic web browser function, it does not retain the responses to checkboxes, such as health insurance and non-cash benefits.