A lab can have a very large number of analysers and can process several thousand samples per day.

LabComm saves data in an SQL compliant database. The LabComm database can get very large if no archiving is setup. Access to historical data can be very useful, such as to create reference ranges or look at trend analysis

We may need to store and have access to the data for 20 years for regulatory reasons

Problem

Archiving Data-01

The lab has 25 analysers. LabComm interfaces the analysers, separates QC and results and sends the the data to a LIMS / HIS system

LabComm sends the QC results to a separate QC system. The lab then has analyser data in two systems, one for QC as well as the main LIS (Laboratory Information System)

Requirement

Archiving Data-02

The lab wants to keep all data from all analysers. LabComm as a middleware product does not need to store data for long as the data is forwarded immediately to a HIS or LIMS system

Solution

 

QC and Test Data that is older than 90 days is archived. A historical DB can keep all the analyser data

The archiving process is automatic via a configuration setting. Data that is older than the configured time period is automatically archived from the DB.