Create and modify study objects in the DEV lifecycle only
You should only create and modify study object in the Development lifecycle as described:
-
Recommendation: Use the Development lifecycle to build your study, then promote objects to QC and Production.
-
Rationale: Underlying LSH functionality supports this usage model. QC is the only place where you have a reasonable ability to verify how objects will behave when you promote them to Production. In addition, when you check an object out of the QC or Production lifecycle, you need to re-promote it to QC and back to Production.
-
Additional information: If you check out a model, transformation or validation check in QC or Production, the existing installed version of the object in the QC and Production lifecycles continues to function until you promote the new version to QC or Production and install it there.
We recommend that you use each lifecycle in the following ways:
- Development: Create clinical data models, transformation programs, and validation checks. You can create them manually or from a library, a study, or a study template. Load data into the Development lifecycle schema, and do initial testing there.
- QC: Formally test study components (optional). This is equivalent to the UAT InForm environment.
- Production: Load, review, and clean production study data. The system prevents destructive changes to tables and models in a production environment.
Parent topic: General recommendations