Maintaining Batch Samples
Overview
Often a laboratory batch job is referred to as a 'batch' since samples from multiple registered jobs are grouped together for analysis by common scheme or linked schemes. In reality, a batch is any job scheme, or linked job schemes, since the related sample schemes are already grouped together in the job for analysis by a scheme or linked schemes.
Therefore, batch samples are those samples within a registered job scheme, or a laboratory or subcontract batch job.
This process details how samples in batch jobs are maintained, including:
-
Viewing samples within a job scheme in a registered or batch job
-
Allows the sequence of unknown and QC samples to be seen in context of the job scheme
Note: A linked job schemes have the same QC samples and rack layout.
-
-
Re-sequencing samples within a job scheme in a registered or batch job
-
Samples may need to be moved around within a rack or across racks
- A sample may become urgent due to a client request, requiring it to be analysed earlier in the instrument run
- Standards and blanks might need to be moved around the rack(s) or removed from the racks
- Additional standards and blanks need to be added, based on the operator's experience in the client's samples or based on some initial results
- A standard is not available to the operator and a suitable replacement needs to be used
- A standard lot is not available to the operator and a suitable replacement needs to be used
-
-
Re-racking samples within a job scheme in a registered or batch job
-
Changing the type of analytical assessment for a QC sample
- Linking duplicate, replicate or spike samples to a different original sample
- There may not be enough of the original sample to create the duplicate, replicate or spike, so another sample needs to be used
-
Linking blank, standard or spike samples to a different standard material or standard lot
- Adding QC samples to a job scheme in a registered or batch job
- Deleting QC samples from a job scheme in a registered or batch job
-
De-linking a sample scheme analyte from a batch job
When considering laboratory batch jobs, there are times that the registered samples that have been added to a laboratory batch job need to be removed, that is, de-linked, from it
-
Updating analytes in related QC samples of a registered job scheme and related batch samples and batch QC samples in a batch job scheme
Where additional analytes are added to sample schemes in a registered job, then the analytes generally need to be added to:
-
Related duplicate, replicate and spike QC samples (but not vice versa) in the same registered job
-
Related blank and standard QC samples in the same registered job
-
Related duplicate, replicate and spike QC samples (but not vice versa) added to, or created for, a related laboratory batch job
-
Related blank and standard QC samples added to, or created for, a related laboratory batch job.
-
Note: QC samples can be added to a job in two other ways:
-
By Creating QC Samples using a QC Mask on a registered or batch job.
-
During registration along with the unknown samples. Refer to Adding a Group of Samples to a Job.
Appendix—The Different Types of QC Samples
The Different Types of Analytical Limits used in CCLAS
Restriction
This process cannot be performed on a job that is locked or has a Workflow Status of Finalised or Cancelled.
Process
Viewing Samples within a Job Scheme in a Registered or Batch Job
Viewing Samples within a Job Scheme using QC Sample Maintenance
The CCQCSM—QC Sample Maintenance application is used to view the samples within a job scheme, allowing the sequence of unknown and QC samples to be seen in context of the job scheme. This application then allows re-sequencing of samples in the job scheme, and the adding and deletion of QC samples for the job scheme.
Open QC sample maintenance for a job scheme
The sample schemes returned from a search based on the selected scheme display the primary and QC assessment details for the sample, and are ordered in sample scheme Profile Sequence.
Samples returned from a search in the CCQCSM—QC Sample Maintenance application can be exported to a report. Refer to Generating Grid Reports. Available report templates are defined in the SEARCH_REPORT_CCQCSM application preference.
Viewing Samples within a Job Scheme using Batch Sample Maintenance
The CCBTSM—Batch Sample Maintenance application, accessed from the search results grid in the CCREGN—Job application, is used to view the samples within a job scheme, allowing the sequence of unknown and QC samples to be seen in context of the job scheme. This application then allows de-linking of sample scheme analytes from a batch job.
Open batch sample maintenance for a job scheme
The sample schemes returned from a search based on the selected scheme display the primary sample details and the linked sample details from any related laboratory batch job, and are ordered in sample scheme Profile Sequence.
Samples returned from a search in the CCBTSM—Batch Sample Maintenance application can be exported to a report. Refer to Generating Grid Reports. Available report templates are defined in the SEARCH_REPORT_CCBTSM application preference.
Where a registered job is viewed in the CCBTSM—Batch Sample Maintenance application, samples can occur more than once in the grid where they are included in more than one laboratory batch job, with the Linked Job Name indicating the laboratory batch job where the sample scheme and some/all analytes are included, and the Linked Sample Name and Linked Client Sample Name being the same as those on the registered sample.
For example, for a particular production job scheme viewed in the CCBTSM—Batch Sample Maintenance application:
| Primary Sample Code | Primary Analytical Type | Primary Job Name | Primary Sample Name | Primary Client Sample name | Linked Job Name | Linked Sample Name | Linked Client Sample Name |
|---|---|---|---|---|---|---|---|
| S3435 | Unknown | J123 | J123.001 | SAMPLE_01 | |||
| S3436 | Unknown | J123 | J123.002 | SAMPLE_02 | LB233 | J123.002 | SAMPLE_02 |
| S3436 | Unknown | J123 | J123.002 | SAMPLE_02 | LB234 | J123.002 | SAMPLE_02 |
It can be seen that sample J123.001 has not been included in any laboratory batch job, and that J123.002 has been included in two laboratory batch jobs, that is, some of the scheme's analytes were included in one laboratory batch job, and other of the scheme's analytes were included in another laboratory batch job.
Where a laboratory batch job is viewed in the CCBTSM—Batch Sample Maintenance application, samples occur once in the grid, with the Linked Job Name indicating which registered job the samples belong to.
For the linked LB233 laboratory batch job scheme viewed in the CCBTSM—Batch Sample Maintenance application:
| Primary Sample Code | Primary Analytical Type | Primary Job Name | Primary Sample Name | Primary Client Sample name | Linked Job Name | Linked Sample Name | Linked Client Sample Name |
|---|---|---|---|---|---|---|---|
| S3437 | Unknown | LB233 | J123.002 | SAMPLE_02 | J123 | J123.002 | SAMPLE_02 |
It can be seen that, whilst the J123.002 sample is a separate sample in its own right and has a unique Primary Sample Code, it has the same Primary Sample Name as the original registered sample, and Linked Job Name shows the original registered job.
For the linked LB234 laboratory batch job scheme viewed in the CCBTSM—Batch Sample Maintenance application:
| Primary Sample Code | Primary Analytical Type | Primary Job Name | Primary Sample Name | Primary Client Sample name | Linked Job Name | Linked Sample Name | Linked Client Sample Name |
|---|---|---|---|---|---|---|---|
| S3438 | Unknown | LB234 | J123.002 | SAMPLE_02 | J123 | J123.002 | SAMPLE_02 |
It can be seen that, whilst the J123.002 sample is a separate sample in its own right and has a unique Primary Sample Code, it has the same Primary Sample Name as the original registered sample, and Linked Job Name shows the original registered job.
Re-sequencing Samples within a Job Scheme in a Registered or Batch Job
The CCQCSM—QC Sample Modification application is used to re-sequence samples within a job scheme.
Re-sequence samples for a job scheme
This updates each sample scheme's Profile Sequence.
Note: Profile Sequence is the order of the sample schemes within the job scheme, and Registration Sequence is the order of the schemes within the sample.
The event is audited.
Re-racking Samples within a Job Scheme in a Registered or Batch Job
The CCQCSM—QC Sample Modification application is used to re-rack samples within a job scheme. The event is audited.
Samples are re-racked for a job scheme to place the samples in racks with a rack size denoted by the scheme version's Default Rack Size, thereby aligning them in the way in which they are going to be placed in physical racks or in an instrument feeder.
Re-rack samples for a job scheme
The Registration Sequence and Rack Number are made identical for all linked job schemes, that is, they are registered for all linked job schemes (although a duplicate, replicate or spike QC sample is only registered in a linked job scheme as long as the original sample is registered also for that job scheme), and are placed in the same relative order in the rack.
When selecting multiple samples to move them up and down chosen positions, there is an option to re-rack from that dialog. Refer to Resequence samples for a job-scheme for the steps.
Changing the Type of Analytical Assessment for a QC Sample
The CCQCSM—QC Sample Modification application is used to change the type of analytical assessment for a QC sample by changing the sample's Secondary Analytical Type and Secondary QC Type Code.
Where an unknown sample is suspected or being a hidden QC sample, sent in by the client, then at point of analysis, the unknown sample can be updated so that it undergoes the required analytical assessment for the suspected analytical type.
Configure an unknown sample as a hidden QC sample
Where two or more blank, standard or spike QC samples are paired with an original blank, standard or spike QC sample, the paired blank, standard or spike QC sample has a Primary Analytical Type of Blank, Standard or Spike, subsequently, and a Secondary Analytical Type of Duplicate or Replicate, as determined by the selected Secondary QC Type Code.
Configure a blank, standard or spike QC sample as a paired duplicate or replicate QC sample
These events are audited.
Linking Duplicate, Replicate or Spike Samples to a Different Original Sample
The CCQCSM—QC Sample Modification application is used to link duplicate, replicate and spike samples to a different original sample.
Where the sample's Primary Analytical Type or Secondary Analytical Type is Duplicate or Replicate, then the QC sample has:
- A link to the duplicate's or replicate's original sample, used for precision assessment, such that, the results from both samples are compared against the limits in the scheme version analyte.
Where the sample's Primary Analytical Type or Secondary Analytical Type is Spike, then the QC sample has:
- A link to the spike's original sample, used for standard assessment, such that, the difference between the result from the original sample and the result from the spike sample is compared against the limits in the specification on the standard lot.
Configure the original unknown sample for a duplicate, replicate or spike QC sample
The event is audited. Refer to Reviewing Operational Data Audits.
Linking blank, standard or spike samples to a different standard material or standard lot
The CCQCSM—QC Sample Modification application is used to link duplicate, replicate and spike samples to a different original sample.
Where the sample's Primary Analytical Type or Secondary Analytical Type is Blank, Standard or Spike, then the QC sample has:
- A link to the standard and standard lot, used for standard assessment, such that, the results from the sample is compared against the limits in the specification on the standard lot. In the case of a spike QC sample, the expected value of the standard is subtracted from the measured value of the original sample and then compared against the limits in the specification on the standard lot.
The CCQCSM—QC Sample Modification application is used to link blank, standard and spike samples to a different standard material or standard lot by , replicate and spike samples to a different original sample.
Configure the standard material and lot for a blank, standard or spike QC sample
The event is audited. Refer to Reviewing Operational Data Audits.
Adding QC Samples to a Job Scheme in a Registered or Batch Job
The CCQCSM—QC Sample Modification application is used to add QC samples to, or delete QC samples from, a job scheme.
Add Duplicate or Replicate QC Samples
Add duplicate or replicate QC samples to a job scheme
Duplicate QC samples can only be added to a registered job.
Duplicate, replicate or spike QC samples are created and placed at the position defined by the QC Placement, and linked to the selected samples.
When a duplicate QC sample is created for a sample, then it is registered for all schemes on the sample.
When a replicate or spike QC sample is created for a sample, then it is registered only for the specific scheme and any schemes linked to that sample scheme.
If Request Repeat is selected for the added QC sample, then in addition to creating the new replicate or duplicate, a repeat is requested in which the original sample's Workflow Status is set to Repeat and a new empty reading is created for each associated sample scheme analyte, affectively clearing the current results. IS THIS ONLY FOR REPLICATES?
Refer to the default settings for duplicate and replicate QC samples.
Add Blank or Standard QC Samples
Add blank or standard QC samples to a job scheme
The standard or blank QC samples are created and placed at the position defined by the QC placement, and added to the current job scheme and to all linked schemes and sequel schemes.
Refer to the default settings for blank and standard QC samples.
Add Spike QC Samples
Add spike QC samples to a job scheme
Note: Only standards and standard lots that have specification limits defined for the current scheme is available to be selected. Standard lots must not be expired or have a zero inventory stock level. Based on whether the ALLOW_STANDARDS_AS_SPIKES application preference is checked, both standards and spike QC samples are available for selection.
Each subsequent spike QC sample has a Primary QC Type of Spike, and a Secondary QC Type of Duplicate or Replicate, as determined by the selected Secondary QC Type Code.
The spike QC samples are created and placed at the position defined by the QC Placement, and each linked to the relevant selected sample.
Refer to the default settings for spike QC samples.
Upon Adding QC Samples to Linked and Sequel Job Schemes
After QC samples are registered to a job scheme, then the QC sample is registered in each linked or sequel job scheme as follows:
-
QC samples are inserted into the sequel job scheme in the same relative position as they exist in the job scheme during the propagation.
-
When a duplicate QC sample is created in a laboratory batch job, then the duplicate QC sample is propagated into linked and explicit and implicit sequel job schemes, but only where the target job scheme contains the duplicate QC sample's original sample. An explicit sequel scheme is one based upon master scheme precursor relationships, and an implicit sequel scheme for a sample preparation scheme is any analytical preparation or analytical scheme.
-
When a replicate or spike QC sample is created in a registered or laboratory batch job, then the replicate or spike QC sample is propagated into linked and explicit sequel job schemes, but only where the target job scheme contains the replicate or spike QC sample's original sample.
-
When a blank or standard QC sample is created in a registered or laboratory batch job, then the standard or blank QC sample is propagated into linked and explicit sequel job schemes.
The event is audited. Refer to Reviewing Operational Data Audits.
Deleting QC Samples from a Job Scheme in a Registered or Batch Job
QC samples can be deleted for the job, but only where they are owned by the job. For example, when a laboratory batch job is opened for QC sample modification, then only QC samples owned by the laboratory batch job (that this, those QC samples that have a QC Source of 3) can be deleted. When a registered job is opened for QC sample modification, then only QC samples owned by the registered job (that is, those QC samples that have a QC Source of 1 or 2) can be deleted.
Delete QC samples from a job scheme
A user can delete a QC sample of a nominated type only where they are a member of the respective user group:
-
When an attempt is made to delete a QC sample that has a Primary Analytical Type of Duplicate, if the ALLOW_DELETE_DUP_USERGROUP application preference is not defined, or is defined and the user is a member of the user group, then the action proceeds. Otherwise, if the preference is defined and the user is not a member of the user group, then the action does not proceed.
-
When an attempt is made to delete a QC sample that has a Primary Analytical Type of Replicate, if the ALLOW_DELETE_REP_USERGROUP application preference is not defined, or is defined and the user is a member of the user group, then the action proceeds. Otherwise, if the preference is defined and the user is not a member of the user group, then the action does not proceed.
-
When an attempt is made to delete a QC sample with a Primary Analytical Type of Blank, if the ALLOW_DELETE_BLK_USERGROUP application preference is not defined, or is defined and the user is a member of the user group, then the action proceeds. If the preference is defined and the user is not a member of the user group, then the action does not proceed.
-
When an attempt is made to delete a QC sample with a Primary Analytical Type of Standard, if the ALLOW_DELETE_STD_USERGROUP application preference is not defined, or is defined and the user is a member of the user group, then the action proceeds. Otherwise, if the preference is defined and the user is not a member of the user group, then the action does not proceed.
-
When an attempt is made to delete a QC sample with a Primary Analytical Type of Spike, if the ALLOW_DELETE_SPK_USERGROUP application preference is not defined, or is defined and the user is a member of the user group, then the action proceeds. Otherwise, if the preference is defined and the user is not a member of the user group, then the action does not proceed.
When a QC sample is deleted from a job scheme, then the sample scheme and related sample scheme analytes are deleted for the current scheme and all linked schemes and sequel schemes.
If the sample no longer has any associated sample scheme then the sample is deleted as follows:
- If the QC sample's parent job is a production job then it is deleted from the production job scheme, in which case the sample scheme analytes that might have contained links to laboratory batch jobs are also deleted, so if a laboratory batch job that contained one of those sample scheme analytes was opened the cell would be highlighted as grey even though the laboratory batch job still contains the associated laboratory batch sample.
- If the QC sample's parent job is a laboratory batch job, then it is deleted from the laboratory batch job.
- When a QC sample is deleted, if there is a related record in QC history, then that QC history record is set to inactive.
The event is audited. Refer to Reviewing Operational Data Audits.
Deleting QC Samples from Linked and Sequel Job Schemes
Upon deletion, a QC sample is deleted from all linked job schemes as well, however, it is not deleted from all sequel job schemes.
De-linking a Sample Scheme Analyte from a Batch Job
De-link samples from a laboratory or subcontract batch job
Where a laboratory or subcontract batch job is opened in batch sample maintenance, selected samples can be de-linked from the batch. This removes the related sample scheme analytes' Lab Batch Job Code and Lab Batch Sample Code.
De-linking cannot occur where the laboratory or subcontract batch job is locked by another user. Refer to Maintaining Job Locks.
The service used to de-link samples from a batch job is CCJobBatchMaintenance.Delink.
The SampleDTO is passed in as a parameter, such that, for each production sample scheme analyte where the Lab Batch Job Code matches a selected laboratory batch job, then the sample scheme analyte's Lab Batch Job Code and Lab Batch Sample Code are cleared, essentially removing the production sample scheme analyte from the laboratory batch job.
During de-linking, the laboratory batch sample is not deleted, however, it now only contains production sample scheme analytes that are still linked to the laboratory batch job.
Also note that for any QC sample within the laboratory batch job that has a QC Source of 3, created when Batching Samples for Analysis and QC samples are created for the laboratory batch job (refer to Creating QC Samples), then these samples remain in the laboratory batch as they belong to it and not to any production job, however:
- For a replicate QC sample, the sample's Dup Original Sample Code is cleared since the original replicated sample is de-linked from the laboratory batch job.
- For a spike QC sample, the sample's Spike Original Sample Code is cleared since the original spiked sample is de-linked from the laboratory batch job.
- Each sample scheme associated with the sample has the sample scheme's Workflow Status set to Not Analysed, which, after a workflow status cascade, results in the sample's Workflow Status being set to Not Analysed, so that the laboratory batch job is not left in a state where it can never be completed.
The event is audited. Refer to Reviewing Operational Data Audits.
Conditions for Calculating Expiry and Warning Dates
For a sample scheme with a precursor scheme, Holding Time is counted from the Completed Date of the precursor sample scheme. Where a precursor sample scheme is included in a laboratory batch job, the sequel sample scheme's Completed Date in the laboratory batch job is used to determine the sequel sample scheme's Expiry Date in the production job. Therefore, when a sample is de-linked from a laboratory batch job, then the sequel sample scheme's Expiry Date in the production job is redetermined to counted from the sequel sample scheme's Completed Date in the production job.
An unknown or duplicate sample scheme's Expires On and Warning On dates or an unknown or duplicate sample scheme analyte's Expires On and Warning On dates are calculated using the sample scheme's Holding Time and scheme version's Warning Time or the sample scheme analyte's Holding Time and scheme version's Warning Time, respectively, and:
- If a sample scheme has a Precursor Scheme Code, then the precursor sample scheme's Completed Date
- If a sample scheme does not have a Precursor Scheme Code, then the sample's Sampled Date and Received Date.
This process is performed by the holding time engine. Refer to Using Sample Expiry.
Note that Expires On and Warning On dates are NOT determined for replicate, blank, standard or spike sample schemes and sample scheme analytes, even where their sample schemes contain holding and/or warning times, respectively.
Updating Analytes in Related QC Samples of a Registered Job Scheme and Related Batch Samples and Batch QC Samples in a Batch Job Scheme
Where sample schemes are included in a laboratory batch, and especially where analysis has started on the laboratory batch (maybe weighed up and digested), such that the laboratory batch should not be deleted and re-batched, then additional analytes can be added to related sample schemes.
Updating Analytes in Related QC Sample Schemes of Registered Job Schemes
The CCCREGN—Job application, for selected job schemes in a production job, allows:
-
The adding of missing analytes to related duplicate, replicate and spike QC samples, but not vice versa, and to related blank and standard QC samples.
Update QC sample analytes for job schemes
Upon updating analytes in related QC sample schemes of a registered job scheme:
- Duplicate and Replicate QC samples—Where an analyte exists on the parent original sample scheme but does not exist on the duplicate/replicate QC sample scheme, then that analyte is added to the duplicate/replicate QC sample scheme.
- Spike QC samples—Where an analyte exists on the spike original sample scheme but does not exist on the spike QC sample scheme, then that analyte is added to the spike QC sample scheme.
- Blank and standard QC samples—Where an analyte exists as a job scheme analyte but does not exist on the blank/standard QC sample, then that analyte is added to the blank/standard QC sample.
The event is audited. Refer to Reviewing Operational Data Audits.
Note: Any laboratory batch job that has that job scheme analyte and contains a related QC sample scheme analyte touched by this process shows the sample scheme analyte as not being in the laboratory batch job. This is because the sample scheme analyte's Lab Batch Job Code and Lab Batch Sample Code are empty. This can be managed by using the next activity instead which updates related batch job schemes as well.
Updating Analytes in Related QC Sample Schemes of a Registered Job Scheme AND Related Batch Sample Schemes and Batch QC Sample Schemes in a Related Batch Job Scheme
The CCCREGN—Job application, for a selected job scheme in a production job, allows:
-
The adding of missing analytes to related duplicate, replicate and spike QC samples, but not vice versa, and to related blank and standard QC samples.
-
The adding of missing analytes to a related batch job, such that, where analytes are on a production sample scheme (including those for QC samples) but are not included in latest batch sample scheme associated with the sample scheme's analytes, then those analytes are added to that laboratory batch sample scheme.
Update batched sample scheme analytes for a registered job scheme
Upon updating analytes in related QC sample schemes of a registered job scheme AND related batch sample schemes and batch QC sample schemes in a related batch job scheme:
- Duplicate and Replicate QC samples—Where an analyte exists on the parent original sample scheme but does not exist on the duplicate/replicate QC sample scheme, then that analyte is added to the duplicate/replicate QC sample scheme.
- Spike QC samples—Where an analyte exists on the spike original sample scheme but does not exist on the spike QC sample scheme, then that analyte is added to the spike QC sample scheme.
- Blank and standard QC samples—Where an analyte exists as a job scheme analyte but does not exist on the blank/standard QC sample, then that analyte is added to the blank/standard QC sample.
The related sample scheme analytes that are not associated with a laboratory batch job and sample are linked to the latest laboratory batch associated with the sample scheme's analytes:
-
The sample scheme analyte's Lab Batch Job Code and Lab Batch Sample Code is updated for any unknown or QC sample include in the laboratory batch, to link to the laboratory batch job and sample.
-
Sample scheme analytes are created in the batch job for any replicate or spike QC sample owned by the batch job.
-
Sample scheme analytes are created in the batch job for any blank or standard QC sample owned by the batch job.
-
Job scheme analyte are created within the laboratory batch.
Presumption: The whole sample schemes are batched, and that individual analytes on a sample scheme are not batched into separate laboratory batches. Where a production sample scheme's analytes are included in more than one laboratory batch, it is the latest created laboratory batch that is updated.
The event is audited. Refer to Reviewing Operational Data Audits.
The following properties are updated on the laboratory batch job's QC samples for the new analyte:
|
Sample Scheme Analyte field |
Blank/standard QC Sample |
Replicate/spike QC Sample |
|---|---|---|
|
WEIGHT |
Weight SSA's NumericFinalValue |
Weight SSA's NumericFinalValue |
|
VOLUME |
SSA's NumericFinalValue |
Volume SSA's NumericFinalValue |
|
INT_LOWER_DET_LIMIT |
SVA's Internal Lower DL |
Original sample SSA's Internal Lower DL |
|
INT_UPPER_DET_LIMIT |
SVA's Internal Upper DL |
Original sample SSA's Internal Upper DL |
|
CORRECTED_INT_LOWER_DET_LIMIT |
SVA's Internal Lower DL |
Original sample SSA's Internal Lower DL |
|
CORRECTED_INT_UPPER_DET_LIMIT |
SVA's Internal Upper DL |
Original sample SSA's Internal Upper DL |
|
HOLDING_TIME |
SVA in scope |
Original sample SSA's Holding Time |
|
IS_INCLUDE_ON_WORKSHEET |
SVA in scope |
Ensure it is the original sample's Is Include on worksheet |
|
IS_INT_LOWER_LIM_CRITICAL |
SVA in scope |
Original sample SSA's Is Int Lower Lim Critical |
|
IS_INT_UPPER_LIM_CRITICAL |
SVA in scope |
Original sample SSA's Is Int Upper Lim Critical |
|
IS_QC_ACTIVE |
SVA in scope |
Original sample SSA's Is QC Active |
|
IS_REPORTABLE |
SVA in scope |
Original sample SSA's Is Reportable |
|
IS_INVOICEABLE |
SVA in scope |
Original sample SSA's Is Invoiceable |
|
IS_WORKFLOW_ACTIVE |
SVA in scope |
Original sample SSA's Is Workflow Active |
|
IS_USED_IN_AGGREGATE |
Y |
Y |
|
JOB_SCHEME_ANALYTE_ID |
Lab batched job's JOB_SCHEME_ANALYTE.ID |
Lab batched job's JOB_SCHEME_ANALYTE.ID |
|
PACKAGE_PRICE_CODE |
<Not applicable> |
Original sample SSA's Package Price Code |
|
PACKAGE_PRICE_CODE_LAB_CODE |
<Not applicable> |
Original sample SSA's Package Price Code Lab Code |
|
REPORT_SEQUENCE |
SVA in scope |
Original sample SSA's Report Sequence |
|
REPORT_UNIT_CODE |
SVA in scope |
Original sample SSA's Report Unit Code |
|
REPORT_UNIT_ID |
SVA in scope |
Original sample SSA's Report Unit Id |
|
REP_LOWER_DET_LIMIT |
SVA in scope |
Original sample SSA's Rep Lower DL |
|
REP_UPPER_DET_LIMIT |
SVA in scope |
Original sample SSA's Rep Upper DL |
|
REQUIRED_DATE |
<Not applicable> |
Original sample SSA's Required Date |
|
ROUNDING_TABLE_CODE |
SVA in scope |
Original sample SSA's Rounding Table Code |
|
ROUNDING_TABLE_ID |
SVA in scope |
Original sample SSA's Rounding Table Id |
|
SPREADSHEET_FORMULA |
SVA in scope |
Original sample SSA's Spreadsheet Formula |
|
UNIT_CODE |
SVA in scope |
Original sample SSA's Unit Code |
|
UNIT_ID |
SVA in scope |
Original sample SSA's Unit Id |
|
EXPIRY_DATE |
Empty |
Empty |
|
WARNING_DATE |
Empty |
Empty |
|
INCLUDE_IN_AUTO_REG |
Y |
Original sample SSA's Include in Auto Reg |
|
INCLUDE_IN_MANUAL_REG |
Y |
Original sample SSA's Include in Manual Reg |
Note: SVA in scope means the enabled-scope for a linked org-scope scheme and the lab-scope for a linked lab-scope scheme.
Example: A production job contains unknown and QC samples added from an update QC process, and then the A3 analyte is removed from the S1 and from S6 Replicate sample schemes. After this, the sample schemes (all unknowns and QC samples) are included in a laboratory batch job.
| Production job | Laboratory batch job | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| QC Source | Sample | A1 | A | A3 | A4 | A5 | A1 | A2 | A3 | A4 | A5 | |
|
3 |
BLANK (LB) |
|
|
|
|
|
|
|
|
|
|
|
|
2 |
BLANK |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S1 |
|
|
|
|
|
|
|
|
|
|
|
|
3 |
S1 REP (LB) |
|
|
|
|
|
|
|
|
|
|
|
|
2 |
S1 REP |
|
|
|
|
|
|
|
|
|
|
|
|
2 |
STD1 |
|
|
|
|
|
|
|
|
|
|
|
|
2 |
STD3 |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S2 |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S3 |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S4 |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S5 |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S6 |
|
|
|
|
|
|
|
|
|
|
|
|
3 |
S6 REP (LB) |
|
|
|
|
|
|
|
|
|
|
|
|
3 |
STD1 (LB) |
|
|
|
|
|
|
|
|
|
|
|
|
2 |
S6 REP |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S7 |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S8 |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S9 |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S10 |
|
|
|
|
|
|
|
|
|
|
|
|
2 |
STD2 |
|
|
|
|
|
|
|
|
|
|
|
|
3 |
STD1 (LB) |
|
|
|
|
|
|
|
|
|
|
|
|
3 |
STD3 (LB) |
|
|
|
|
|
|
|
|
|
|
|
After updating QC sample analytes for the job scheme:
| Production job | Laboratory batch job | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| QC Source | Sample | A1 | A2 | A3 | A4 | A5 | A1 | A2 | A3 | A4 | A5 | |
|
3 |
BLANK (LB) |
|
|
|
|
|
|
|
|
|
|
|
|
2 |
BLANK |
|
|
Added |
Added |
Added |
|
|
|
Added |
Added |
Added |
|
1 |
S1 |
|
|
|
|
|
|
|
|
|
|
|
|
3 |
S1 REP (LB) |
|
|
|
|
|
|
|
|
|
|
|
|
2 |
S1 REP |
|
|
Added |
Added |
|
|
|
|
Added |
Added |
|
|
2 |
STD1 |
|
|
|
Added |
Added |
|
|
|
|
Added |
Added |
|
2 |
STD3 |
|
|
Added |
Added |
Added |
|
|
|
Added |
Added |
Added |
|
1 |
S2 |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S3 |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S4 |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S5 |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S6 |
|
|
|
|
|
|
|
|
|
|
|
|
3 |
S6 REP (LB) |
|
|
|
|
|
|
|
|
|
|
|
|
3 |
STD1 (LB) |
|
|
|
|
|
|
|
|
|
|
|
|
2 |
S6 REP |
|
Added |
|
|
|
|
|
|
|
|
|
|
1 |
S7 |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S8 |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S9 |
|
|
|
|
|
|
|
|
|
|
|
|
1 |
S10 |
|
|
|
|
|
|
|
|
|
|
|
|
2 |
STD2 |
|
|
|
Added |
Added |
|
|
|
|
Added |
Added |
|
3 |
STD1 (LB) |
|
|
|
|
|
|
|
|
|
|
|
|
3 |
STD3 (LB) |
|
|
|
|
|
|
|
|
|
|
|
Related processes...