About Object Validation

Your organization must develop standards for testing Oracle Life Sciences Data Hub defined objects to demonstrate that they are valid; that is, that they handle data as they are designed to do, without introducing any corruption.

As you create object definitions and instances you must follow your organization's policy for validating them in compliance with industry regulations.

All Oracle Life Sciences Data Hub objects that are contained directly in a Domain, Application Area, or Work Area—including definitions and instances of Tables, Programs, Load Sets, Data Marts, Report Sets, Workflows, and Business Areas, as well as Variables, Parameters, and Notifications—have an attribute called Validation Status with possible values Development, Quality Control, Production, and Retired.

To support object validation, Oracle Life Sciences Data Hub provides the following tools:

• Validation Status. When an object definition or instance meets the standards set by your organization for a higher validation status, you can change its status. See Validation Statuses for further information.
• Validation Supporting Information. You can link an object with outputs and documents. See Adding Supporting Information for further information.
• Report Coversheets. You can generate a coversheet for every report output that displays all the defined objects that interacted with the data in the report from when it was loaded into Oracle Life Sciences Data Hub to when it was reported out of Oracle Life Sciences Data Hub, including the validation status of each object. See "Generating a Coversheet with Validation and Data Currency Information" in the Oracle Life Sciences Data Hub User's Guide for further information.
• Work Area Usage Intent and Cloning. Work Areas have an attribute called Usage Intent with the same list of values (except Retired) as the Validation Status attribute: Development, Quality Control, Production. Oracle LSH enforces Validation Rules based on the interaction of Work Area usage intent and object validation statuses. Work Areas also have a special operation called cloning that enables you to create clean, distinct environments for testing objects and for production; see Cloning Work Areas for Testing and Production.