Creating Template Samples within a Template Job

Overview

Template samples exist in template jobs. A template sample pre-defines the product and other sample information, and tests that are required for a sample of this type. A template sample can contain a suite of tests that can be added to a registered sample.

Process

One or more template sample can be created in a template job, and tests added to each template sample, as required. Refer to Maintaining Template Jobs.

Creating template samples in template jobs is very similar to Adding a Group of Samples to a Job except that a template sample is left in its unexpanded form, and several fields are available only where the sample is a template sample.

Creating a Template Sample

The CCREGN—Job and CCSAMP—Sample applications are used to create within template jobs. Samples can be maintained either within the context of a job using the CCREGN—Job application or without job context using the CCSAMP—Sample application.

One template sample represents one sample type 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 template sample represents a compressed sample group in a target job. Template sample registration presents an interim sample to the user. Once the identification syntaxes and sample properties are defined, upon submit, the template sample is left in its unexpanded form. The interim sample essentially becomes the template sample.

Where lines of business are implemented, all schemes, scheme versions, analytes and products linked to an org-scope template sample must belong to the same line of business.

Analytes and specifications must belong to the same scheme version for each scheme in a template sample.

Upon creating a template sample in a template job:

Create a template sample within a template job

Indication of the Sample being a Template Sample

On the sample screen, Is Template is selected and read-only to indicate that the sample belongs to a template job, and is, by default, itself a template sample.

Active Status

A template sample can be made active or inactive for use by toggling Is Active.

When Maintaining Samples or Adding Tests using a Template Sample to a Sample, template samples are searchable by whether they are active for use. When Adding Samples using a Template Sample to a Job, available template samples are filtered by whether they are active for use (and ignores whether the associated template job is active or inactive for use).

Sample Identification

When a sample group in a registered job is created from a template sample, then the Client Sample Name/Syntax defaults to that in the template, but can be modified in the destination job.

Sample Properties

The scope of a template sample follows the scope of the template job in which it exists.

Regardless of the client linked from a template job, a template sample itself can link to:

  • No client, thereby making the template sample available for use for registering samples from template in any job

  • A client, thereby making the template sample available for use for registering samples from template only in a job linked to the same client

  • A client group, thereby making the template sample available for use for registering samples from template only in a job linked to a client that exists in the client group.

This prevents an incorrect template sample being selected for the registration of a job's samples.

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

If the job has a Job Type of Template, 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.

When a sample scheme is created from a template sample scheme, the target sample scheme's Workflow Status is set to the template sample scheme's Default Workflow Status.

Update the default workflow status for a template sample scheme

If the job has a Job Type of Template, 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.

When the sample scheme analyte is created from a template sample scheme analyte, then the target sample scheme's Workflow Status is set to the template sample scheme analyte's Default Workflow Status.

Update the default workflow status for a template sample scheme analyte