Audit events written for a job save as
When a job is registered from another registered job using the CCREGN—Save As Job service, then the number of created samples is audited as a single job audit record. This includes when the source job is a template job. Note that individual samples are not audited, just the total count of sample records created.
The following table indicates the data that is written to the job audit record in the job audit transaction resulting from a job save as.
|
Field |
Content |
|---|---|
|
Event Date |
<System_DateTime> |
|
User Id |
<Current_Login_User_ID> |
|
Audit Level |
1 |
|
Correlation Id |
<Unique_ID_per_transaction> |
|
Application Name |
CCREGN |
|
Audit Type |
CRT |
|
Audit Event |
Samples Created (<Number_of_created_samples>) |
|
Organisation Code |
<Current_Login_Organisation_code> |
|
Laboratory Code |
<Current_Login_Laboratory_Code> |
|
Job Id |
<Existing_Job_ID> |
|
Job Code |
<Existing_Job_Code> |
|
Job Name |
<Existing_Job_Name> |
|
Sample Id |
|
|
Sample Code |
|
|
Sample Name |
|
|
Portion Code |
|
|
Scheme Id |
|
|
Scheme Code |
|
|
Scheme Name |
|
|
Scheme Version Id |
|
|
Scheme Version |
|
|
Scheme Version Analyte Id |
|
|
Scheme Version Analyte Code |
|
|
Scheme Version Analyte Name |
|
|
Related Object Type |
J |
|
Related Object Id |
|
|
Related Object Code |
|
|
Related Object Name |
|
|
Is Header? |
Y for the FIRST record of the entire transaction, N for SUBSEQUENT records of the entire transaction. Since job audit records are only written for changed fields, then the header record of the transaction may vary each time a job update is done. |
|
Field |
|
|
Data Type |
6 |
|
From_Id |
|
|
From_Code |
|
|
From_Name |
|
|
From_Description |
|
|
To_Id |
|
|
To_Code |
|
|
To_Name |
|
|
To_Description |
|
