Sequencing Jobs, Samples and Tests in the Reportable Result Set

The sequence of jobs, samples and tests in the reportable result set is driven by the report template. There are various sequence fields that can be used: the default order of entities within the report request, and for schemes and analytes, an overriding report sequence that is an optional field.

The sequence of schemes and analytes within the reportable result set can be overridden by placing logic either in a report template or report script to place a scheme or analyte higher up on the report with respect to other schemes and analytes. For example, placing all schemes with a defined report sequence at the top of the report, or placing all analytes with a defined report sequence at the top of the report, then placing the rest of the schemes or analytes after that in their relative sequence in the report request.

The sequence of samples and tests within the report request defaults to the sequence of samples and tests in the job.

In the scheme In the job In the report request

 

 

ccReportRequestJob.defaultSequence

  • Defaults to the order in which jobs are added to the report request

 

 

ccReportRequestJob.reportSequence

 

ccJobScheme.registrationSequence

  • Based on the order in which the job schemes are created, that is, as group sample schemes are added to the job causing the creation of job schemes.
  • Maintaining Job Tests to re-sequence schemes within a job.

ccReportRequestScheme.defaultSequence

  • Defaults to the order in which schemes are added to the report request, based on the job schemes' registration sequence

 

ccJobScheme.reportSequence

  • Inherited from the first sample scheme causing the creation of the job scheme.

ccReportRequestScheme.reportSequence

 

ccJobSchemeAnalyte.registrationSequence

  • Based on the order in which the job scheme analytes are created, that is, as group sample scheme analytes are added to the job causing the creation of job scheme analytes.
  • When all analytes for a scheme are added to a sample group, they are added in their relative sequence within the scheme version.

ccReportRequestSchemeAnalyte.defaultSequence

  • Defaults to the order in which analytes are added to the report request, based on the job schemes analytes' registration sequence

 

ccJobSchemeAnalyte.reportSequence

  • Inherited from the first sample scheme analyte causing the creation of the job scheme analyte.

ccReportRequestSchemeAnalyte.reportSequence

 

ccSample.registrationSequence

  • Defaults to the order in which samples are registered in the job

ccReportRequestSample.defaultSequence

  • Defaults to the order in which samples are added to the report request—for all jobs, initially by the samples' registration sequence within the job; any laboratory batch QC samples are added at the end

 

 

ccReportRequestSample.registrationSequence

ccScheme.reportSequence

  • Refer to Maintaining Schemes to specify a report sequence override when configuring reporting details

ccSampleScheme.reportSequence

ccReportRequestSampleScheme.reportSequence

* The current report request interface does display report request sample schemes. However, after sample schemes are added to a report request, when a report request scheme is updated, the report sequence is pushed down to each related report request sample scheme.

ccSchemeVersionAnalyte.reportSequence

ccSampleSchemeAnalyte.reportSequence

ccReportRequestSampleSchemeAnalyte.reportSequence

* The current report request interface does display report request sample scheme analytes. However, after sample scheme analytes are added to a report request, when a report request scheme analyte is updated, the report sequence is pushed down to each related report request sample scheme analyte.