Creating Stream Samples within a Schedule Job
Overview
Stream samples are used directly produce production samples in a scheduled batch process, or to draft samples in an interactive session and then trigger the creation of production samples.
A stream sample is a sample of a known product that is taken a particular location in the production process, or a standard sample that is inserted into the analytical stream of samples from the production process. A stream sample pre-defines the product and other sample information, and tests that are required for the sample collected from the production process.
Process
One or more stream sample must be created in a schedule job, and tests added to each template sample, as required.
This process is very similar to Adding a Group of Samples to a Job except that the sample is left in its unexpanded form, and several fields are available only for stream samples.
Creating a Stream Sample
One stream sample represents one sample type from the production process and the sample syntax within that template sample is designed to identify a routinely received sample of that type. For example, the sample may be called CONCENTRATE DD-MM-YY where the current date is delivered by the syntax code. A stream sample represents a compressed sample group in a target job. Stream sample registration presents an interim sample to the user. Once the identification syntaxes and sample properties are defined, upon submit, the stream sample is left in its unexpanded form. The interim sample essentially becomes the stream sample.
Where lines of business are implemented, all schemes, scheme versions, analytes and products linked to an org-scope stream sample must belong to the same line of business.
Analytes and specifications must belong to the same scheme version for each scheme in a stream sample.
Upon creating a stream sample in a schedule job:
-
The event is audited. Refer to Reviewing Operational Data Audits.
Create a stream sample within a schedule job
Active Status
A schedule sample can be made active or inactive for use by toggling Is Active.
Sample Identification
When a draft sample is created from a stream sample in a schedule job, then the Client Sample Name/Syntax defaults to that in the template, but can be modified in the destination job.
Sample Properties
When a sample is created from a template sample, all sample properties, sample biofields, tests, specifications and portions are maintained as new properties and entities on the destination sample. The only properties that do not inherit are date and workflow related. Refer to:
A template sample's Client Code or Client Group Code can be used to locate the template job containing this template sample when Maintaining Jobs, or used to locate the sample itself when Adding Samples to a Job using a Template Sample.
The template sample's Template Price Code is used to determine a package price for its schemes and analytes when they are registered on a sample using the template sample. When any sample scheme or sample scheme analyte is registered on a sample (either by using a template job, template sample, or adding tests from a template sample), then the sample scheme and sample scheme analyte is linked to the template sample. If the registered sample has Use Package Price selected, then sample schemes and sample scheme analytes linked to a template sample are priced using the package price instead of the price schedules associated with the job scheme's Price Code and job scheme analyte's Price Code.
Default Workflow Status
When a sample scheme is created from a stream sample scheme, the target sample scheme's Workflow Status is set to the stream sample scheme's Default Workflow Status.
When the sample scheme analyte is created from a stream sample scheme analyte, then the target sample scheme's Workflow Status is set to the stream sample scheme analyte's Default Workflow Status.
If the job has a Job Type of Schedule, when the Tests tab is selected on the CCSAMP—Sample Detail screen or the CCREGNSMPLSCH—Sample Scheme Detail screen displays, then a default sample scheme workflow status can be set.
Update the default workflow status for a stream sample scheme
If the job has a Job Type of Schedule, when the Tests tab is selected on the CCSAMP—Sample Detail screen or the CCREGNSMPLSCHANA—Sample Scheme Analyte Detail screen displays, then a default sample scheme analyte workflow status can be set.
Update the default workflow status for a stream sample scheme analyte
Replication Requirements
If the job has a Job Type of Schedule, when the CCREGNSMPLSCH—Sample Scheme Detail screen displays or the Tests tab is selected on the CCSAMP—Sample Detail screen, then the replication details are visible for the stream sample scheme.
When the stream sample scheme is used to create a draft or production sample scheme, the specified number of replicate samples is created and linked to the replicate QC type.
Update replication details for a stream sample scheme
Paperwork Requirements
If the job has a Job Type of Schedule, when the CCREGNSMPLSCH—Sample Scheme Detail screen displays or the Tests tab is selected on the CCSAMP—Sample Detail screen, then the label and paperwork requirements can be updated.
These settings are used as defaults for destination sample schemes when a draft or production job is created from the schedule job.
Update label and paperwork requirements for a stream sample scheme
Sample Schedule and Inclusion
If the job has a Job Type of Schedule, when the Samples tab is selected on the CCSAMP—Sample Detail screen, then the Schedule tab displays.
A valid schedule comprises the Scheduled Months and Scheduled Times, and either the Scheduled Weeks and Scheduled Days, or the Scheduled Days of Month.
Update schedule details for a stream sample
When a schedule executes, only stream sample schemes and stream sample scheme analytes that are flagged for inclusion are registered in the target job.
If the job has a Job Type of Schedule, when the Tests tab is selected on the CCSAMP—Sample Detail screen or the CCREGNSMPLSCH—Sample Scheme Detail screen displays, then the registration inclusion flags are visible for the stream sample scheme.
If the job has a Job Type of Schedule, when the Tests tab is selected on the CCSAMP—Sample Detail screen or the CCREGNSMPLSCHANA—Sample Scheme Analyte Detail screen displays, then the registration flags are visible for the stream sample scheme analyte.
Update registration inclusion flags for a stream sample scheme
Update registration inclusion flags for a stream sample scheme analyte
Importing Samples into a Schedule Job
Samples can be imported into a schedule job.
This activity uses the CCSAMP—Search Sample screen, except that a Job Type search criteria field allows samples to be searched from all jobs, template jobs only, production jobs only, or schedule jobs only.
A sample cannot be added where it contains a sample scheme linked to a scheme version where the scheme is already on another sample in the job for a different scheme version.
The copy includes all sample details, sample biofields, sample specifications, sample notes, sample portions, sample schemes, sample scheme analytes, etc.. These details can be modified, as required.
-
Conditions for Defaulting Scheme Links from the Template Sample
-
Conditions for Defaulting Precursor Scheme Relationships and Holding Time from the Sample Template
Import samples into a schedule job
- Maintaining Template Jobs
- Maintaining Schedule Jobs
- Adding a Group of Samples to a Job
- Adding Samples to a Job using a Template Sample
- Maintaining Template Jobs
- Maintaining Samples
- Maintaining Sample Biofields
- Maintaining Sample Tests
- Maintaining Sample Syntaxes
- Configuring Registration
- Appendix—Cascade Engine
