1. Conducting a Study
  2. Batch Loading Data
  3. Batch-Deleting Data
  4. Auditing Data Deletion

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 batch data delete with audit, the records in the deleted CRFs are backed up in a set of audit tables. For each source table that is deleted, a new corresponding audit table is created with a suffix of $BDD (for instance, RECEIVED_DCIS$BDD). Columns in the table include the batch_job_id followed by the same columns as in the source table. For example, RESPONSES$BDD includes batch_job_id followed by same fields as responses.

The job generates audit tables corresponding to the following Oracle Clinical tables:

Parent topic: Batch-Deleting Data