We separate QC from test results and store them in different tables. In a hospital environment we may send the data to different systems.  Some protocols such as POCT1A provide different identifiers between QC and result data. With many other analysers other options need to be used. LabComm provides an algorithm that allows analyser data to be separated from QC data irrespective of the protocol used to send the data.

Our example clinic has 5 analysers

Seperating QC and Tests-01

The analysers are for Haematology, Chemistry, Urine, Virology & Microbiology

The haematology analyser is the Sysmex KXN which does separate QC from result data. 

The other analysers are a combination of ASTM (Chemistry and Microbiology) bespoke (CombiScan 100)  Urine and Virology 

Seperating QC and Tests-02

We want to separate result from QC data. We want to send the result data to a HIS (Hospital Information System). The Hospital HIS does not deal with QC data and we are going to send the QC data to another system.

The ASTM and Sysmex data have fields indicating QC data, which we use. The UA analyser requires that we search in a specific field for the presence of specific data.

We then separate the data using an analyser specific setting. Our analyser specific settings can then search specific fields for either test or QC and Calibration data

If QC or calibration data is found the whole message is recognised as QC data and stored in the QC tables.

We have now separated the QC from the result data. We store the QC data in QC tables by analyser. We can create reports and monitor our QC data.