Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate consistency of findings between general and findings forms #4433

Closed
phildominguez-gsa opened this issue Nov 5, 2024 · 4 comments

Comments

@phildominguez-gsa
Copy link
Contributor

Spinning this off of this ticket

The relevant text from that ticket:

The `general` table has indicators of whether there are only unmodified opinions. The `findings` table can, however, report modified opinions on compliance. This is inconsistent.

1. These should not be "at odds" with each-other. An audit with inconsistent reporting should be blocked from submission.
2. If a modified opinion is reported in the `general` table, then there must be corresponding entries in the `findings` table; it cannot be that there are no corresponding findings.

Before implementing this validation, we first need to confirm that this restriction is in fact "real" and isn't going to cause problems for auditors in the future. It seems this validation idea came from HHS/Federal audit reviewers, so we want to run it by those who actually submit audits.

@github-project-automation github-project-automation bot moved this to Triage in FAC Nov 5, 2024
@phildominguez-gsa
Copy link
Contributor Author

@Leighdiddy @James-Paul-Mason @analynd Would this be something you guys could assist with?

@analynd
Copy link

analynd commented Nov 7, 2024

Hi @phildominguez-gsa, sorry I missed this in my inbox! This actually sounds relevant to something that was brought up during our call with HHS today.

I'm still unfamiliar and learning about findings so gonna pass this to @danswick and @Leighdiddy for guidance. Thanks!

@phildominguez-gsa
Copy link
Contributor Author

Still looking for assistance here @Leighdiddy @analynd @danswick

@Leighdiddy
Copy link
Contributor

@phildominguez-gsa I can confirm that this is correct, we just reviewed this with HUD last week :) Regardless of pushback from auditors, this should be a set if/than rule. We will keep an eye out for edge cases after implementation, but this can move forward.

@github-project-automation github-project-automation bot moved this from Triage to Done in FAC Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants