LabComm is a software solution for interfacing to laboratory analysers and equipment.

The LabComm software runs on a Windows server and does not need an operator. It is normally set to run automatically and may be left running for several weeks or months without requiring any human intervention.

LabComm is used in a number of different Laboratory and Clinical environments such as Vetinary, Stem Cell and Blood Banking, Near Patient or Point of Care Testing (POCT) as well as Clinics and hospitals.

LabComm can be used as a stand alone product, combined with the LabDriver LIMS or combined with a number of different Hospital Information Systems (HIS) or Laboratory Information Management Systems (LIMS)

LabComm communicates with the host HIS or LIMS in a number of different ways:

  • using an ODBC connection (Open Database Connectivity):
    • directly accessing the Postgres database.
  • using the XML format


LabComm has a number of ways to separate QC and results data, depending on which analyser the data is received from.
The Result and QC data can then sent to the host, stored in a file, or stored in the database, independently of each other. This allows a lab to send the QC data to a different system from the results data and means that LabComm can send the data to 2 separate LIMS systems if required.


Several hundred different analysers and lab equipment (eg Scales) have been interfaced to and all the common protocols such as POCT1A and ASTM as well as many exotic and bespoke protocols are supported.
Bespoke protocols include the Sysmex KXN haematology, the VetScan haematology (Vetinary) and the Sepax cell processing device.
A single LabComm server can support up to 30 analysers, but this will vary according to the amount of data sent. Labs with more than 30 analysers are supported by having multiple instances of LabComm running and then merging the data into a single database.
Analysers in different labs in different locations and even different countries can be interfaced together.

Most of the analyser interface solutions on the market will not support different protocols and we often find 5 or 6 different interface solutions, from different manufacturers installed on one site.
The naturally makes it very difficult for the lab staff to manage all the analysers and we know that our solution has overcome these issues.

LabComm connects to laboratory analysers, Point of Care (POCT) analysers and laboratory equipment.

These connections are automatic and the data sent by the analysers is collected automatically.

LabComm runs automatically and will run for weeks or months without requiring any human intervention or supervision. A daily email can be sent out giving the status and last date and time the analysers sent results.

Result and QC data are separated, stored in different tables in the database and can be sent to different LIMS systems. There are a number of algorithms that can be used to standardise the data from analysers, so that results are presented in the same format.

LabComm is used as a standalone product as well as being combined with the LabDriver LIMS.

LabComm will connect with one to several hundred different analysers and will then send data to a host HIS or LIMS in two different ways:

HL7 format (either as files or TCP/IP socket connections)

Directly via a SQL database

LabComm is used in a number of different Laboratory and Clinical environments such as Veterinary, Stem Cell and Blood Banking, Near Patient or Point of Care Testing (POCT) as well as Clinics and hospitals.

In a hospital environment the analyser data can be combined with ADT data and then sent to a the Hospital Information Systems (HIS) or Laboratory Information Management Systems (LIMS)

Several hundred different analysers have been interfaced to and all the common protocols such as POCT1A and ASTM as well as many exotic and bespoke protocols are supported.

Bespoke protocols include the Sysmex KXN haematology, the VetScan haematology (Veterinary) and the Sepax cell processing device.

A single LabComm server can support dozens or even hundreds of different analysers when used with vendors software in a POCT hospital settings.

The connected analysers do not even need to be in the same physical location, they may be in different buildings, different cities or even different countries.

The interfacing of analysers offers huge productivity benefits. It not only saved the Operators the need to write down or enter results but it also allows them to load a sample and move on to the next job, since they no longer need to wait for that sample to be processed.

The latest analyser protocol (POCT1A) will send details of the analyser reagent use and will allow the Operators details to be saved. This can be combined with the LabDriver or another LIMS solution to provide a Stock and Inventory Management system and an Operator Training and Competency system.