Registering Jobs from other Registered Jobs

Overview

Sometimes the samples that are received and the requested tests are similar to what was analysed in a previous production job, in which case, that production job can be used to create the new production job. A production or internal job can be used to create a copy of itself, as a new job.

Process

Using a production, proposal and internal job to create a job is slightly different to using a template job to create a job. Refer to Registering Jobs from Template Jobs.

Copying a Job

Registered job, that is, production, internal and proposal jobs, can be saved as a new production, internal, proposal, template or schedule job using the CCREGN—Job application.

Upon job copy, the destination job's Job Type must be selected. Limitations are placed on the Job Type of the destination job based upon the source job.

A Client Code must be entered with an optional Project Code and Contact Code.

  • If the selected client has a Primary Project Code defined, then that project is used as the default Project Code.

  • A job can only link to a client has is flagged as being able to submit samples.

  • Whether the Project Code is optional is driven by MANDATORY_PROJECT application preference.

  • A job can link only to a project that is flagged as being able to submit samples and where the job's Received Date falls in the project's Project Open Date and Project Close Date time frame.

    Note: The drop-down selection list excludes projects that cannot submit samples, but it does not exclude those outside of the job's Received Date as that date is not calculated until an attempt to create the job is made. Where a project is selected that cannot have samples submitted or the job's Received Date is outside the project date, then an error is returned upon submit.

  • Whether the Contact Code is optional is driven by the MANDATORY_CONTACT application preference.

  • If a project is selected and the project has a Primary Contact Code defined, then that contact is used as the default Contact Code. Otherwise, if a project is not selected and the client has a Primary Contact Code defined, then that contact is used as the default Contact Code.

Refer to Maintaining Clients.

Jobs have two primary identifiers: Code and Job Name.

  • Each job Code and Job Name must be unique within the organisation for org-scope jobs, and unique within the laboratory for lab-scope jobs.

  • Either select a Job Name Syntax Code to generate the job name or enter the Job Name. The JOB_NAME_ONLY_FROM_SYNTAX application preference is used to force syntax use.

    Some laboratories let the LIMS identify and 'pick' the next job number, whereas other laboratories pre-identify a series of job numbers that can be assigned to groups of samples without the need of a live connection to the LIMS. These might be provided as labels or barcode labels, or they might just be contained in a central 'book'. This mainly works if the sample receipt is at a central location, but if this is a dispersed function, then letting the LIMS identify the job number is probably a better solution.

    Using syntaxes to generate job codes and names allows for automatic incrementing codification. The system can be set to force job name creation from syntax only to control job coding and naming.

  • The DEFAULT_PRODUCTION_JOB_NAME_SYNTAX application preference is used to set a default Job Name Syntax Code for a production job.

  • The DEFAULT_INTERNAL_JOB_NAME_SYNTAX application preference is used to set a default Job Name Syntax Code for an internal job.
  • The DEFAULT_PROPOSAL_JOB_NAME_SYNTAX, preference is used to set a default Job Name Syntax Code for a proposal job.
  • The DEFAULT_ORG_TEMPLATE_JOB_NAME_SYNTAX, preference is used to set a default Job Name Syntax Code for a template job.
  • The DEFAULT_SCHEDULE_JOB_NAME_SYNTAX application preference is used to set a default Job Name Syntax Code for a schedule job.

Refer to:

Upon Copying Jobs

Upon job copy:

Register a job from another registered job

Auto Receiving Jobs

The AUTO_RECEIVE_JOBS application preference configures whether the destination job's Received Date and Received By are set automatically, or left empty for manual update.