Workflow Status Cascade
This section explains the cascade engine with respect to the cascading of workflow statuses:
- From sample scheme analyte to sample scheme
- From sample scheme to sample
- From sample to job
- From sample scheme analyte to job scheme analyte
- From sample scheme to job scheme.
|
SSA.WFS → |
SS.WFS → |
S.WFS |
|
↓ |
↓ |
↓ |
|
JSA.WFS |
JS.WFS |
J.WFS |
Workflow Statuses
The following statuses, or some thereof, are possible for a Workflow Status at various levels in a job.
|
Composite Workflow Status |
Definition |
|---|---|
|
Registered (REG) |
The initial state of a job or sample when it is created. |
|
Not Started (NST) |
No results are entered as yet. |
|
Check (CHK) |
A result has exceeded critical detection limits and needs checking. |
|
Repeat (REP) |
An analysis needs to be repeated. |
|
Listed Not Received (LNR) |
A sample is listed on the sample list but has not been received by the laboratory. The entity is not invoiceable. |
|
Insufficient Sample (IS) |
There is not enough material for analysis. The entity is not invoiceable. |
|
Not Analysed (NA) |
A test was not carried out. The entity is not invoiceable. |
|
No Result (NR) |
A test was carried out but the result is indeterminate. The entity is invoiceable. |
|
Started (STA) |
At least one result is entered. |
|
Analysed (ANA) |
All results are determined but results have not yet been released nor validated. |
|
Released (REL) |
All results are determined and released, but results have not yet been validated. |
|
Completed (CPL) |
All results are determined, released and validated. |
|
Validated (VAL) * |
All results are completed, and the job or sample is now also validated. * This is not an actual status as it is based on whether the Date Validated field is set on the entity, but is often treated as a pseudo workflow status. |
|
Finalised (FIN) |
A job is finalised with no more action to be undertaken upon it. |
|
Cancelled (CAN) |
A job that was not yet completed is cancelled. |
Initial State of Workflow Status on a SSA
A sample scheme analyte's Workflow Status is set to Not Started upon creation or when a result is cleared or the sample scheme analyte is reset from LNR, IS, NA, or NR.
Possible Outcomes of SSA's Workflow Status Depending on Actions applied to the SSA
After a sample scheme analyte has:
- a result entered
- a result cleared
- been re-read to obtain another result
- a repeat requested
- a critical detection limit failures ignored
- an upper scheme activated
- a failed a critical detection limit assessment
- been marked as listed not received
- been marked as insufficient sample
- been marked as not analysed or no result,
the possible outcomes for a sample scheme analyte's Workflow Status are:
- Not Started
- Repeat
- Check
- Listed Not Received
- Insufficient Sample
- Not Required
- No Result
- Analysed
When a sample scheme analyte is loaded in context of its production sample, and the sample scheme analyte has a result put against it or its Composite QC Status, Composite Specification Status or Workflow Status is updated after assessment, if there are no critical detection limit failures that forces the sample scheme analyte's Workflow Status to Check, and if the sample scheme analyte's Workflow Status is set to something other than Repeat, then the sample scheme analyte's Workflow Status is set to Analysed.
- Processes that Change Workflow Status on Entities
- Allowable Sample Scheme Analyte Workflow Status Changes
- Setting and Clearing Dates and User on Workflow Status Changes
- Cascading LNR across the Sample and to Related Samples
The outcome of each sample scheme analyte's Workflow Status depends upon the result, its quality control outcomes, and other states that may be assigned to the sample scheme analyte.
|
Workflow Status |
Abbreviation |
Definition |
Comment |
|---|---|---|---|
|
Insufficient Sample |
IS |
Set by marking a sample scheme analyte as IS. |
The sample material is insufficient to determine a result for the SSA (not invoiceable); may or may not have Analysed Date (and a value), no Released Date, no Validated Date. |
|
Not Analysed |
NA |
Set by marking a sample scheme analyte as NA. |
The sample is not analysed for the SSA (not invoiceable); may or may not have Analysed Date (and a value), no Released Date, no Validated Date. |
|
No Result |
NR |
Set by marking a sample scheme analyte as NR. |
The sample analysis was attempted but no result was achievable (invoiceable); may or may not have Analysed Date (and a value), no Released Date, no Validated Date. |
|
Completed (and Validated are the same thing on sample scheme analyte level) |
CPL |
Set manually by the user, or set automatically by the cascade engine where the scheme version analyte's Auto Validate is selected, and where in context of result entry via a laboratory-batch job then also where manual validation is not enforced (Conditions for Forcing Manual Validation of a Laboratory Batch Result), and:
or set by the cascade engine when no auto-validation is in place on the scheme version analyte, but the sample is associated with a product, and the sample's Primary Specification from the product passes (Conditions for Auto-Validation when the Product Passes Specification). |
SSA has Analysed Date (and a value), Released Date, Validated Date. |
|
Released |
REL |
Set manually by the user, or set automatically by the cascade engine where the scheme version analyte's Auto Release is selected, and where in context of result entry via a laboratory-batch job then also where manual release is not enforced (Conditions for Forcing Manual Release of a Laboratory Batch Result), and:
|
SSA has Analysed Date (and a value), Released Date, no Validated Date. |
|
Analysed |
ANA |
Set by any entry of a reading that updates the sample scheme analyte's result, and the result is not numeric, or the result is numeric and inside any critical detection limits, and no auto-release is in place, or by resetting the workflow where a result exists (only allowed where the sample scheme analyte's Workflow Status is Listed Not Received, Insufficient Sample, Not Analysed or No Result), or by ignoring a critical detection limit failure. Note: Where a cell has a WFS=ANA (and a value), and it is set to IS|NA|NR, submit, reset, submit, then the cell should return to WFA=ANA (and a value). |
SSA has Analysed Date (and a value), no Released Date, no Validated Date. |
|
Not Started |
NST |
Set at sample scheme analyte creation, or by applying a reset, only possible where Workflow Status is Listed Not Received, Insufficient Sample, Not Analysed or No Result), and a result does not exist on the sample scheme analyte, or by clearing the sample scheme analyte's result. Note: Where a cell has a WFS=NST (and no value), and it is set to IS|NA|NR, submit, reset, submit, then the cell should return to WFA=NST (and a value). |
SSA has Analysed Date (and no value), no Released Date, no Validated Date. |
|
Check |
CHK |
Set when the samples scheme analyte's result exceeds a critical detection limit. |
SSA has Analysed Date (and a value that has exceeded critical lower or upper detection limit), no Released Date, no Validated Date. |
|
Repeat |
REP |
Set by requesting a repeat for the sample scheme analyte(that is, from a workbook cell where the user wants to repeat the analysis, or when a critical upper detection limit failure results in a sample scheme analyte's Workflow Status being set to Check and the upper sample scheme analyte being triggered manually or automatically, thereby changing the upper sample scheme analyte's Workflow Status from Not Analysed or No Result to Repeat instead of moving it back to Not Started). |
SSA has Analysed Date (and no value), no Released Date, no Validated Date; it is set to Repeat to allow these SSAs to be searched easily for re-analysis. |
|
Listed Not Received |
LNR |
Set by marking a sample scheme analyte as Listed Not Received (only allowed if no sample scheme analyte result exists) such that any related sample scheme analyte's Workflow Status is also set to Listed Not Received. |
SSA has Analysed Date (and no value), no Released Date, no Validated Date. |
Result Release
After a result is released, the sample scheme analyte's Workflow Status is Released.
Result release is dependent upon job type. A sample scheme analyte can be loaded via its production job or via a related laboratory batch job, and have a result put against it. The result release path is different depending upon the whether the result entry is via the production job or the laboratory batch job.
When a sample scheme analyte has a result entered and the result of the assessment is that the sample scheme analyte's Workflow Status is Analysed, then automatic release may occur.
Where the sample scheme analyte is not automatically released, then the result has to be manually released in Workbook (either via a workbook script command run on the sample scheme analyte's workbook cell, or via a script that executes the sample scheme analyte's Release service). Note that a user needs to be a member of section's Release Result User Group to manually release a sample scheme analyte.
When a result is released, the sample scheme analyte's Workflow Status becomes Released, the Released Date is stamped using the laboratory's current date-time, and the Released By User is set to the current user for manual release and left empty for automatic release.
|
Job Type |
Scheme version analyte's Auto Release | LAB_BATCH_MANUAL_RELEASE_RESULTS application preference | Sample scheme analyte's Workflow Status |
|---|---|---|---|
|
Non-laboratory-batch |
Checked |
-- |
Released |
|
Non-laboratory-batch |
Unchecked |
-- |
Analysed |
|
Laboratory-batch |
Checked |
Not defined, or is defined and is cleared |
Released |
|
Laboratory-batch |
Checked |
Defined and is checked (that is, the SVA's auto-release is overridden) |
Analysed |
|
Laboratory-batch |
Unchecked |
-- |
Analysed |
Result Validation
After a result is validated, the sample scheme analyte's Workflow Status is Completed.
Result validation is dependent upon job type. A sample scheme analyte can be loaded via its production job or via a related laboratory batch job, and have a result put against it. The validation release path is different depending upon the whether the result entry is via the production job or the laboratory batch job.
When a sample scheme analyte achieves a Workflow Status of Released, either manually or automatically via the cascade engine, then automatic validation may occur.
Where the sample scheme analyte is not automatically validated, then the result has to be manually validated in Workbook (either via a workbook script command run on the sample scheme analyte's workbook cell, or via a script that executes the sample scheme analyte's Validate service). Note that a user needs to be a member of section's Release Result User Group to manually release a sample scheme analyte, upon which, the sample scheme analyte achieves a Workflow Status of Released.
When a result is released, the sample scheme analyte's Workflow Status becomes Completed, the Validated Date is stamped using the laboratory's current date-time, and the Validated By User is set to the current user for manual validation and left empty for automatic validation.
|
Job Type |
Scheme version analyte's Auto Validate | LAB_BATCH_MANUAL_VALIDATE_RESULTS application preference | Scheme version analyte's QC Active | Sample scheme analyte's Composite QC Status | Sample scheme analyte's Workflow Status |
|---|---|---|---|---|---|
|
Non-laboratory-batch |
Checked |
-- |
Unchecked |
-- |
Completed |
|
Non-laboratory-batch |
Checked |
-- |
Checked |
Passed or Warning |
Completed |
|
Non-laboratory-batch |
Checked |
-- |
Checked |
Not Tested or Failure |
Released |
|
Non-laboratory-batch |
Unchecked |
-- |
-- |
-- |
Released |
|
Laboratory-batch |
Checked |
Not defined, or is defined and is cleared |
Unchecked |
-- |
Completed |
|
Laboratory-batch |
Checked |
Not defined, or is defined and is cleared |
Checked |
Pass or Warning |
Completed |
|
Laboratory-batch |
Checked |
Not defined, or is defined and is cleared |
Checked |
Not Tested or Failure |
Released |
|
Laboratory-batch |
Checked |
Defined and is checked (that is, the SVA's auto-validate is overridden) |
-- |
-- |
Released |
|
Laboratory-batch |
Unchecked |
-- |
-- |
-- |
Released |
Possible Outcomes of Changing SS's Workflow Status from Job Schemes or Job
The Set Scheme Workflow Status flow is launched from a job returned from a search to set the Workflow Status for all miscellaneous or sample preparation sample schemes in the job, or from an individual miscellaneous or sample preparation job scheme, to set the related sample scheme's Workflow Status, to Not Started, Started or Completed. Workflow cascade then takes place from the sample scheme level upwards.
Workflow Status Cascade
After a result is changed for a sample scheme analyte in context of a non-laboratory-batch job, the cascade engine cascades each level of sample scheme, sample, job, job scheme analyte and job scheme Workflow Status within that production, proposal or template job.
After a result is changed for a sample scheme analyte in context of a laboratory-batch job, the cascade engine cascades each level of sample scheme, sample, job, job scheme analyte and job scheme Workflow Status within that laboratory batch job, and within each associated registered or template job.
A Workflow Status is exactly that—a composite of the workflow statuses below it.
Note: A sample/job has to have at least one analytical analyte that is workflow active for a sample to eventually become complete. For example, a sample/job cannot just contain a miscellaneous scheme for the sample/job to become complete.
For example: If a job has four samples and only a miscellaneous scheme registered on each of those samples, if the job scheme is completed using the Set Scheme Workflow Status flow on the job scheme, then each related sample scheme becomes completed, but the sample and the job remain as not started.
Related processes...