Batch-Deleting Data
You can use a batch job to delete study data when appropriate. For example:
-
After loading an Out of Study file, you can delete all data associated with a bad data file or data file group.
-
You can also delete batch data loads of externally maintained data where the audit history is maintained in an external system.
-
There are also two types of manually entered data that can be deleted from Oracle Clinical without causing problems with the audit trail:
- First-pass data entered into a study but never made accessible.
- Data in development databases where audit is not required.
You can navigate to the batch job for deleting study data from the Conduct menu, by selecting Security, and then selecting Delete Study Information or Delete Study Information with Audit. PSUB window appears. If you do not specify any values for DCI, document number, data file, or data file group, all data in the study will be deleted.
If the study is a flexible study, after completing the batch data delete job, the system automatically runs the full expectedness calculation job. See Oracle Clinical Creating a Study for more information.
Note:
The batch data delete that is not audited is a hard delete - you will not be able to roll back changes made after such a delete. Use this function with extreme care.
Note:
Most users have access only to the Batch Data Deletion with Audit job. However some users may have access to the Batch Data Deletion job, which has an additional Audit parameter allowing the user to either audit the data deletion or not.
You can change data entry information and maintain an audit trail by selecting Update from the Data Entry menu and making changes in Data Entry Update mode. You can also use the batch job Delete Study Information with Audit.
See more: