Requirements for using the LIMS-plus 3.x DNA Module


Requirements for using the LIMS-plus 3.x DNA Module

Affected Users:

LIMS Administrators, DNA Analysts, Evidence Custodians

Fielded Statements:

How are DNA Requests created within LIMS?

What is the difference between DNA Services that use the General Analytical Module for results entry versus using the LIMS-Plus DNA Module.

On the Request Tab, I assigned a request to myself but I am unable to use the DNA Module for results. What is wrong?

What case requirements must be met in order to successfully use the DNA Module for results entry.


Using the DNA Module within LIMS-plus 3.x inherently involves utilizing the DNA Batch Process. Keep in mind, many laboratories choose to process their DNA cases using their own standard operating procedures and historical business worklows. There are several laboratories that choose to enter DNA results into the LIMS application but do not explicitly use the LIMS-plus DNA module itself. In these situations, laboratories may create a service called DNA Analysis but tie the service to the General Analytical Module. In those cases, the DNA analysis and calculations entered into LIMS are being performed manually outside of the LIMS application itself. When the DNA Module is tied to a service within LIMS, a laboratory is able to effectively manage controls and aspects of the DNA Analysis across the board. It also allows the application to be interfaced with external instruments involved in the quantification, observations and subsequent results. The LIMS-plus 3.x application code for the DNA Module is written with a set of assumptions that may not fall within the business workflow by default

For more detailed information regarding the use of the DNA Module within LIMS-plus 3.x, please refer to you LIMS-plus 3.x manual. Additional information can also be obtained from the JusticeTrax FTP site.

Root Cause:

There is some basic criteria that need to be met before you can use (or troubleshoot) the DNA module. These criterion can involve several aspects of the LIMS-plus 3.x application such as Services, Reporting, Module Configuration, Request Assignments, and Evidence Attributes. Therefore it is imperative that a lab organization know its own processes before working requests that are tied to services using the DNA Module. Simply changing the module listed in the properties of a service will have serious consequences to end users and reporting.


The DNA Module must be configured to meet the business requirements outlined in a Laboratory’s standard operating procedure (SOP). This means that the LIMS Administrator must be aware of the business workflows and requirements of their laboratory (specifically the DNA department or unit). Once the SOPs are known, the DNA Module within LIMS-plus 3.x can be configured to meet those requirements and/or guidelines.

Within the LIMS System Administration, one or more services must be configured to use the DNA module.

Within a case, there must be one or more pieces of evidence related to a request for a service that uses the DNA module. The request MUST be unassigned.

The evidence items related to the request MUST have an origin and an extraction set. The current location of the evidence MUST be a storage location.

When you create a DNA batch (the first step of using the DNA module) the evidence items are transferred to the batch creator and the requests are assigned. This is why the requests must all be at UNASSIGNED and the evidence items' current location must be in a storage location. Evidence that is in the possession of another lab analyst cannot be used when creating a batch.


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk