Life cycle activities are scaled to how far the system affects patients, product quality and the integrity of data, to its complexity and novelty, and the outcome of the supplier assessment, so that a simple, low-impact system carries far less documentation and verification than a complex, high-impact custom application. Scaling applies to the rigor of specification, the depth of design and code review, the extent of testing and the formality of records, and it is a positive duty: unnecessary activities and records add cost without adding assurance, and the rationale for the scaling chosen should be documented so it can be explained to a regulator.
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.