Configure Sampling in an Activity

Samples and Results are managed at an Activity level, and can be configured the same or differently for each Activity in a Project.  The Sampling configuration must be completed before samples can be logged and results can be imported from laboratory certificates.

To configure Sampling for an Activity:

1. Open the configuration menu
2. Under Logging, click Activities
3. Click the Activity that you want to configure.  The Sampling step will be selected by default.

The Sampling step in an Activity consists of the following elements:

• Sample Types
• Control Sample Types
• Primary Analysis Sample Flow
• Secondary Analysis Sample Flow

 

Sample types

1. This is where you define what sample types are used when entering samples, and the relationship between the various sample types (e.g. original vs. duplicate).
2. The list of possible sample types is configured in the “Sample Types” option in the “Sample Lists” section on the configuration menu.
3. Start by dragging in the “Original” sample type as this is typically the first type of sample that is created.
4. Next drag the “Duplicate” sample type under the Original sample type, so that it appears indented as a child. This describes the relationship between “parent” and “child” sample types, where a child can only ever be taken from a parent (e.g. a “duplicate” can only be taken from an “original”).

 

Control sample types

1. This is where you define what control sample types are used when entering control samples (standards, blanks) in the sample sequence.
2. The list of possible standards and blanks is configured in the “Reference Material” option in the “Sample Lists” section on the configuration menu.
3. Once you have added your control samples to the Reference Material list, you can come back here and drag them into the activity to make them available when entering samples.

 

Primary sample analysis flow **

1. This is where you define what sample analysis workflow is used for this activity. The sample analysis workflow describes the lab methods that will be used, as well as the validation rules to be applied to the control samples on import.
2. The list of possible sample analysis workflows is configured in the “Sample analysis workflows” option in the “Sample Lists” section of the configuration menu.
3. Once you have configured your sample analysis workflows, you can come back here and drag them into the activity to make them available for this activity.

 

Secondary sample analysis flow **

1. The Secondary sample flow is reserved for check lab results, where the results are to be used as a check against the primary lab results. Any results that are imported through a secondary analysis flow will only be available to plot on QAQC charts for analysis.

 

** The Sample Analysis Workflow contains all the configuration and logic to import assay results from a lab certificate. It describes the sample dispatch header that will be used for submitting samples, the lab sample preparation codes and lab sample analysis codes that will be requested for each batch of samples.

Before configuring a sample analysis workflow, you must first configure the method details for the lab methods that you will be receiving results for. This is done in the Lab Services & Method Details lists.

You will also select the header to be used in the Sample Dispatch module. The default header is always available, or you can create and customize your own to be used in each sample analysis workflow.

Once the sample dispatch header has been selected, and the appropriate sample prep & sample analysis codes have been selected - then the last step is to define the logic that MX Deposit should follow when importing results. This includes the validation rules to apply to your control samples (internal standards & blanks), as well as the rules to apply to map any non-numeric codes that the lab might report (e.g. ">", "<", "ISS").

Only users with the admin role can configure sample analysis workflows, and a sample analysis workflow must be included in an activity before you can dispatch samples and import results.