Workflow Changes in New Submission System

This page highlights some changes in the new workflow compared to the legacy system.

Data Quality Checks

• Finalization in the legacy system is an action that centers perform in which the data is checked against QC rules and moved into the current database. In the new system, QC rules are triggered automatically, and visits that pass QC are flagged for inclusion in future data freezes. So, there is no finalization action in the new system.
• It is not possible to run QC checks on individual forms in the new system, entire packet needs to be complete before submitting.
• A UDS packet is validated independantly from any associated module packets, and if the UDS packet satisfies all QC checks it will be included in freeze data.
• Any associated module packets will not be evaluated until the respective UDS packet has passed QC.
• All visits are validated in the order of the visit date, visit N+1 will not be evaluated until the preceding visit N has passed QC.

Modifying a QC Passed Visit

WARNING

Making modifications to any QC passed visit will reset the QC status of any associated modules and any subsequent visits. All subsequent visits and any associated modules will be automatically re-validated to ensure the longitudinal checks are satisfied after the modification. This action will re-trigger any alerts and they wiil need to be re-verified.

Adding a Missed Visit

WARNING

Adding a missed visit before an already submitted visit will reset the QC status of any subsequent visits (any their associated modules). All subsequent visits and any associated modules will be automatically re-validated to ensure the longitudinal checks are satisfied after the new visit is added. This action will re-trigger any alerts and they wiil need to be re-verified.