Transitioning Output Artifacts into the Next Step

In a highly automated workflow, a lab gains little value from manually selecting samples into the ice bucket and then transitioning them through a step. Ideally, upon completion of one step, a following step could be automated such that the output analytes were transitioned through to the Record Details screen.

The Clarity LIMS External Program Plugin (EPP)/automation system cannot aid in this transition. The last point at which an automation can be triggered is before the step completion.

This scenario requires a stand-alone API application, which can be run by an automation at the end of a step.

Using this approach, a standalone app would poll the API until each of the output analytes from the previous step were queued for the next step. After they are queued, they can be walked through to the Record Details stage.

The steps are as follows:

  1. EPP / automation triggers at step completion and launches an API app as a new Linux process and then finishes. The parameter for the API app is the URL for the current process.

  2. API app polls to see if each output analyte is queued.

    • Use the artifacts batch endpoint (api/v2/artifacts/batch/retrieve) to poll.

    • Check the last workflow-stage node within workflow-stages and look for status="QUEUED".

  3. API app moves the output analytes through the step to Record Details.

    • Use the /api/v2/steps endpoints to start the step and then move the analytes forward.

Last updated