Auditing Data Deletion
The Oracle Clinical table STUDY_DATA_DELETE_AUDIT records each time a batch data delete job is run. The table records:
- the parameters used to invoke the deletion
- the actual number of each object that is deleted by the run
This audit table enables you to document the use and impact of the data deletion facility and may help you diagnose whether a problem has been caused by a hard data delete.
When you execute Delete Study Information with Audit (Audit = ‘Y’), the records for the deleted CRFs are backed up in a set of audit tables with suffix $BDD. For each record from the source table that is deleted, a record is inserted into the corresponding audit table (for instance, RECEIVED_ DCIS$BDD). Columns in the audit table include the batch_job_id followed by the same columns as in the source table. For example, RECEIVED_ DCIS$BDD includes batch_job_id followed by same fields as the RECEIVED_DCIS table.
The job generates audit tables corresponding to the following Oracle Clinical tables: