LabDriver have a solution to import the data from a range of ELISA analysers including the TECAN range. Results and calculations can be imported, in several different ways to cater for different lab requirements.

QC and Result records are separated at source and can be sent to other LIMS and statistics or QC software using a number of data formats such as HL7, files and SQL database.

The Tecan analyser details are imported – and displayed with other analysers used in the laboratory. This provides a centralised management console and is analyse vendor independent.


The complete range of Tecan ELISA analysers are supported – from single plate readers


To batch and multiple plates



To fully automated analysers



The properties of the analysers can be configured including the Sample Type, Operator and Analyser groups. Analyser groups allow the same or similar analyser to share the same properties. This makes the management of multiple analysers easier.

We can create a group that share the same test codes


Filtering of Tecan ELISA data

The user can choose which result statuses are accepted when the analyser import process takes place. Do we only want to include results with a status of OK or all results irrespective of status?



It may be necessary to accept all results for reasons such as insufficient sample volume. (The lab should  have validated that the results prior to doing this ). The import status options are based on filtering the results by status. There are four options that determine which statuses are accepted – both for the results and the calculated tests - BothOk, LineOk-Value , LineOk-All, BothAll

Some data needs to be converted since it may include parenthesis and /or other values which will make it impossible to use in a calculation. The original and the converted data is stored to provide a full audit trail.



Selection of Tecan ELISA well data

The lab may need to select data from a specific well and for that data to be processed as part of a calculation. We can select any data from specific wells and convert that data into a test record – this may be necessary for a calculation that references a specific data record



The user would select which well nos were used for eg QC or positive controls. This has to be consistent across all plates



HL7 data

The Tecan data is available in an SQL database and / or HL7 format. The HL7 data can be sent as files or TCP/IP sockets.










NTE|1||405 nm|

Test Dictionary

The LabDriver test dictionary allows a test to have an extensive range of attributes including Alert values, LOD values, formulas, Loinc codes and group or age specific reference ranges.


Import process – test code matching

The Tecan and many ELISA analysers do not send the test code with the data.

If the analyser does not send a testcode in the data stream, but carries out the same test or a Container or Cartridge ID or Plate we can use this identifier to match with a test code.

The parameter sent from an analyser is then linked to a test. In the next screenshot tests with no direct link to a parameter may be calculated tests.


The Container ID`s (Elisa plates) can be exported to a Excel or CSV file



The Translations can be imported from an Excel or CSV file, with a matching test code



Import – Individual, batch or automated

An individual result can be imported. This may be useful if comments need to be entered for a sample, specific user Electronic signatures (ESigs) or if there are existing results


Sample and Profile comments can be entered manually or from a selection of pre-defined comments


A batch process will allow all the data from one or several analysers to be imported simultaneously.



An automated import will import the data automatically, as the samples are processed according to a set of pre-defined rules setup by the laboratory.

A batch or automated process needs to have the testcode file imported, after which several hundred thousand results can easily be imported per day.

A log of events including missing Sample nos or Container ID can be saved and reviewed.


Test codes and calculated tests

The Lab may want to perform additional calculated tests which are either not set up on the Tecan or were not available at the time the samples were processed. The lab may want to setup a calculated test after the Tecan has processed the samples.



The method of automating the processing of the plates does not affect how the data is processed



Result processing is just one part of the LabDriver solution:

A trial is available using one of our cloud servers.

LabDriver ®   © 2017