Registering Jobs from Draft Jobs

• Registering Jobs from Draft Jobs
  • Overview
  • Process

Overview

Whilst schedule jobs are used to schedule automatic production or internal job registration using the system scheduler and batch processor, they can also be used to interactively create draft jobs which are then enacted into registered production or internal jobs.

A draft job is a transient job that is created interactively from a schedule job, upon which its registration details, samples and tests can be modified prior to it being enacted to create samples in a production or internal job.

Process

As soon as a draft job is configured as required in the CCREGN—Job application, it can be either closed for later use or immediately enacted to create samples in a target production of internal job. Refer to Drafting Jobs from Schedule Jobs.

A draft job cannot be enacted if the target job's Production Job Name is the same as an org-scope template job's Job Name.

Upon enacting a draft job:

• The system attempts to locate a job with a Job Name matching the Production Job Name.

• If a matching job is found, then:

  • If the job is an org-scope template job, then an error is raised.

  • If the job's Job Type does not match the draft job's Required for job type, then an error is raised.

  • Otherwise the job becomes the target job.

• If a matching job is not found, then:

  • The draft job is transformed into the target job, and the target job's Job Type is set to the draft job's Required for job type.

  • Job Name—Set to the draft job's Production Job Name.

  • Workflow Status—Set to Registered.

  • Registered On—Set to the current server date-time, offset by the laboratory's Time Zone.

  • Received On date-time—Set to the current server date-time, offset by the laboratory's Time Zone.

  • All dates are set in the same manner as when Registering Jobs from Template Jobs.

  • The flag to indicate that the job's cost and WIP estimates are outdated is set.

  • Any job stakeholder where Already Exists is cleared and where the entity does not exist as yet on the destination job (matching by the job stakeholder’s Client Code, Contact Code, User Code, Scope Type, Report Template Code, File Name, File Name Syntax Code and Language, in case the destination job was updated after the draft job was created) is added to the destination job.

  • Any job biofield where Already Exists is cleared and where the entity does not exist as yet on the destination job (matching by the job biofield’s Code, in case the destination job was updated after the draft job was created) is added to the destination job.

  • Any job paperwork and labels where Already Exists is cleared and where the entity does not exist as yet on the destination job (matching by the job paperwork and label’s Report Template Code, File Name, File Name Syntax Code and Language, in case the destination job was updated after the draft job was created) is added to the destination job.

• All samples in the draft job that are NOT read-only are registered to the destination job. For each sample:

  • All details are copied from the draft sample to the destination sample, including the Sample Code and Description, with the exception of the following fields:

    • The Sample Name is generated by the syntax that is in scope and has a Syntax Type of Sample and a Syntax Code of SAMPLE_NAME_SYNTAX. If this syntax is not found, an error is returned. The syntax must produce a Sample Name that is unique within the job and contain valid characters.
      If the CODEVALIDATION_SAMPLENAME application preference is:

      • Defined and contains a list of visible ASCII characters, then the Sample Name must only contain characters from this list.
      • Not defined, then the Sample Name must only contain characters from ABCDEFGHIJKLMNOPQRSTUVWXYZ_0123456789.

        A common configuration is for the sample name to be generated by a concatenation of the Job Name + "." + a running sequence of numbers (001 onwards).

    • Workflow Status—Set to Registered.
    • Registration Date—Set to the current server date-time, offset by laboratory's Time Zone.

  • All entities linked to the draft sample are copied to the destination sample, including biofields, tests, specifications and portions.

  • Registration and profile sequences of schemes and analytes on the sample are maintained according to the added samples, as are job scheme and job scheme analytes, and aggregated properties on the job (for example, number of samples, number of unknown samples, number of schemes, number of schemes started, number of schemes completed).

  • Any sample created in a registration process, be it an unknown or QC sample, is assigned a QC Source of 1. Where the sample is a QC sample, then the sample is known as a registration QC sample, that is, it was registered for QC assessment for client purposes.

  • Any sample created for QC assessment of a parent job, that is, any QC samples created by an append/overwrite QC or QC sample maintenance process on a proposal, production, internal, template schedule or draft job, is assigned a QC Source of 2, and the sample is known as a job QC sample.

  • Any samples created for QC assessment of a laboratory batch job, that is, any QC samples created during a batching or QC sample maintenance process on a laboratory batch job, is assigned a QC Source of 3, and the sample is known as a laboratory QC sample. These batch QC samples belong to the laboratory/subcontract batch job—there are no links to the production jobs and samples.

  • A schedule or draft job can be configured to have an update QC process run automatically for the destination job, such that, after samples are added to a production or internal job from a schedule or draft job, if the destination job's Auto Append QC is selected (this setting is inherited from the schedule or draft job), then an update QC process is run to add job QC samples into the destination job, based upon each related sample scheme's QC Mask.

  • Conditions for Calculating Job and Sample Required On Date
  • Conditions for Clearing the Ready Date for Sample Schemes
  • Conditions for Calculating Expiry and Warning Dates
  • Conditions for Defaulting Gridding on Sample Scheme Analyte Copy

  • A schedule or draft job can be configured to have paperwork and labels generated automatically for the destination job, such that, after samples are added to a production or internal job from a schedule or draft job, if the destination job's Is Auto Paperwork is selected (this setting is inherited from the schedule or draft job), then paperwork and labels are generated for the destination job.

  • Note that, in the report request, all samples that are newly added to the production or internal job have their report request sample's Reportable checked, and all samples that already existed in the production or internal job have their report request sample's Reportable cleared, so that paperwork or labels are only created for newly added samples.

• The event is audited. Refer to Reviewing Operational Data Audits.

• The job is opened for update. Refer to Maintaining Jobs.

Enact a draft job to register samples