Understanding of the product and the process underpins science-based and risk-based decisions about computerized systems: the specification, verification and operational controls of a system are scaled to what the supported business process needs, its critical quality attributes and critical process parameters, and the regulated data it carries. The guide expects the organization to understand the process the system supports before it defines requirements, so that effort goes to the aspects that bear on patients, product quality and the integrity of data, and it treats maps of the business process and diagrams of data flow as the way that understanding is captured and kept current.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.