Configure a Sample Retest
Samples can be sent for retesting directly from the Results Summary screen. By default, retesting is performed on held samples, ensuring they are excluded from the final report until new results are obtained. However, you can also select samples for retesting based on specific criteria, such as Flagged results, Sample has comment, Results below lower method limit, or by manually selecting individual samples.
Retesting can be conducted by creating a new instrument run for the selected samples and schemes, creating a new laboratory job to weight the samples again or by starting a new client job, which initiates the full analysis workflow. Additionally, you can generate a new client job with a different analysis method, allowing for alternative testing approaches. This approach uses the Ad-Hoc Retest option which allow you more flexibility when creating a retest.
You can also use the Retest from Package option, which is available when retesting rules have been configured to automatically flag samples that fall outside of specified conditions. For more information, see Add and Configure Packages.
This activity describes the steps to create an ad-hoc retest: a manually triggered retest that allows users to select specific samples for additional analysis as needed, rather than relying on predefined criteria. It also describes the options to manage retests within AssayNet LIMS. For more details, see Configure Retest Options for Analysis Codes.
This activity presumes that the samples have final results updated and approved. For more details, see View and Approve Results. Additionally, the Ad-hoc Retest and Package Retest field should be selected in the Retest Options category of the Analysis Code.
Activity Steps
- On the Job Book screen, click Instrument Runs.
- Locate and select the Run ID.
- Alternatively, use any AssayNet LIMS page to locate and select the corresponding Batch Code or Job Number.
- Click Working View, then locate and select the Run ID.
-
Click Results » Go.
The Results Summary screen displays, showing approved results in green and held results in red.
- Click Retest.
- Select the retest type from:
- Ad-Hoc Retest—Enable you to build a custom retest from three different option, see step 7.
- Retest from Package—Retest packages is pre-defined, and samples are automatically selected based on samples that fall outside of specified conditions. Samples can only be removed. See Step 8.
- To create a Ad-Hoc Retest:
- The Retest screen displays.
- To change how sample IDs display, select one of the following in the Sample ID category:
- Lab Code—A unique identifier for each sample, combining the batch code and sequence number as listed in the table.
- Client ID—The name assigned by the client to each sample in the batch. This is also the default column for sample IDs.
- Select the Retest Type from the following options:
- Re-Run—Creates a new instrument run from the same laboratory job. In the Retest screen, manually select the analyte schemes for retesting (see step g 7).
- Re-Analyze—Creates a new laboratory job from the same client job. This option may be useful when new measurements (for example, weights) are needed. In the Retest screen, manually select the analyte schemes for retesting (see step g 7).
- Re-Test—Creates a new client job using the same packages assigned to the samples or allows selecting a different set of packages if required.
- To manually select samples for retesting:
- Select the sample from the Samples list.
- Click the Select Sample icon to move the sample to the Samples for Retest list.
- Repeat steps c 1-2 to add additional samples.
- Click Select All Samples to send all samples to the Samples for Retest list.
- To automatically select samples for retesting:
- Click Options.
- The Retest Options screen displays. The Retest Options screen displays.
- Select from the following options:
- Results above upper instrument limit
- Results below lower instrument limit
- Results above upper method limit
- Results below lower method limit
- Results exceeding client analyte flag value
- Results on hold—Selected by default. Samples must be on hold in the Results Summary screen. For more information, see View and Approve Results.
- Flagged results—Samples must be flagged in the Results Summary screen.
- Sample has comment
- Sample has NCS code
- Click OK.
- Click Auto.
- The system adds samples that meet the selected conditions to the Samples for Retest list.
Click Next.
When Re-Run or Re-Analyze is selected in the step 7 c, the Scheme Code list displays.
When Re-Test, AssayNet LIMS displays the next step of the Retest process, because for this option, you do not need to select the scheme code. Go to step g 8.
To select the required analyte schemes:
Select the Scheme Code.
Note: If not all analytes require retesting, ensure that all necessary schemes are selected, as some calculations depend on others. In most cases, the analyte code (e.g., Cu) represents calculated schemes, while the analyte code + Read (e.g., Cu Read) represents raw values. To maintain accuracy, always select all Scheme Codes that contain the required analyte code.
- Click the Select Analyte Schemes icon to move the scheme code to the list on the right.
- Repeat steps g 1-2 to add more analyte schemes.
- Click Select All Analyte Schemes to move all scheme codes to the right.
- Click Next.
- Uncheck unnecessary schemes for specific samples.
- Click Next.
- To finalize the retest configuration, see Create a Sample Retest.
Note: If multiple sample IDs are selected, you can edit individual schemes for each sample.
-
To create a Retest from a Package:
Note: A package retest must be configured to use this option. For more information, Configure a Package Retest.The Retest screen displays, the rules are shown in the Client ID list.
-
Select the Rules Name (when more than one is created).
The samples in the Sample list are adjusted based on the selected rule condition.
-
To remove a sample when required:
-
Select the sample in the Sample list.
-
Click Remove.
-
-
Click OK.
A AssayNet LIMS message displays indicating that a new client job has been created.
-