The ability for users to remove inheritance was submitted to the assessor
Currently, there is no way for users to remove inheritance or inheritance requests once submitted. If the auditor tests it, and finds that inheritance is not appropriate, there needs to be an easier way to remove inheritance rather than requesting from HITRUST support.
Michael Seegel
shared this idea
-
Lat Kennedy
commented
We constantly use inheritance in our assessments. With a rigorous timeframe in submission, it's important for our assessors to be able to adjust these when deemed necessary instead of having to engage another request/process.
-
Brian Scheuber
commented
I'd say this is an absolute must. Given the sheer number of requirements, auditors need the flexibility to respond quickly to those that are applicable and cannot be inherited. The ability to remove inheritance would give the auditor the immediate capabilities to address the needs of the requirement and move on to others that they are accountable for.