Force additional edit checks on CAP's during Interim Assessments
Functionality that requires that the Assessor responds to a CAP's Status.

-
Michael Frederick commented
Have checks for scoring changes for controls related to required CAPs. If CAP status in listed as complete, then check for score of 100,100,100 for first 3 domains. If CAP status is Started then check for scoring changes, if no scoring changes alert assessor for commentary indicating progress. If no scoring change and CAP status is not started, then do not select for interim QA.
-
• Current problem: When interim objects are created for clients who are subscribers, the status of CAPs (not started, completed, at risk, etc.) gets brought in as-is into the interim assessment object. The status of the CAPs defaults to what the status was in the validated assessment (which is usually “Not started”). Because the customers don’t always update the CAP status (nor do the assessors) before submission, The QA team gets the object with most CAPs still showing as “not started” and isn’t able to easily tell the true CAP status.
• Recommended solution / the change request: When interim objects are created for clients who are subscribers, the status of CAPs should default to blank / empty / not populated. This, plus preventing the interim assessment object itself from being submitted to HITRUST unless all CAP status fields are populated, will force assessors to update the status of all CAPs present.The tool should also enforce the following edit checks:
1) If a CAP is marked as completed, the associated requirement statement's scoring should have increased as a result of interim testing.
2) If a requirement statement's scoring increases as a result of interim testing above the CAP-required threshold, any associated CAPs should be marked as completed.