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]