Laboratory Information and Management System (LIMS)
LIMS - for almost all research labs a no-go area. But this is wrong, a well set-up and configured LIMS can support the projects in many ways, without building up additional workload, it can even take away workload.
There is not "The LIMS", every laboratory, every research group needs to define it's own individual requirements for a LIMS, build up on available solutions or in-house programmed.
A LIMS should keep an overview over the samples, the sample flow, the sample storage, the project steps and the data and results.
Data from many instruments can be read directly into the LIMS, non-compatible data, for example most mass spectrometry raw data, are stored in location, connected to the LIMS. This makes it easy to find the data for later analysis.
There are many levels of LIMS commercially available or can be in-house programmed, depending on requirements, resources and finally the budget.
These are only simple functions of a LIMS, programmed in a relative database.
More advanced functions for large studies can be batch generation, stratification, randomisation, generation of sample tables for instruments.
It can also help information about instruments as service, calibration, tuning, training and more, about consumables and reagents and anything else related to the lab work.
A basic LIMS can be done in-house or with free programers, but it must be sure that all is well documented and if the programer is no longer available, others know what to do if needed. Such a LIMS will grow over the years from basic functions to advanced functions.
Highly complex LIMS systems are commercial available, expensive, but not ready to use out-of-the-box. Based on the given background structure, the users have to define the functions and the processes in the LIMS. Tis requires a dedicated person, knowing the workflow in the lab and the LIMS structure and language.
Every LIMS should be SQL-database based. In case of problems the data can still be retrieved.
A simple, non commercial LIMS database can be created using free tools as MySQL and others.
There is not "The LIMS", every laboratory, every research group needs to define it's own individual requirements for a LIMS, build up on available solutions or in-house programmed.
A LIMS should keep an overview over the samples, the sample flow, the sample storage, the project steps and the data and results.
Data from many instruments can be read directly into the LIMS, non-compatible data, for example most mass spectrometry raw data, are stored in location, connected to the LIMS. This makes it easy to find the data for later analysis.
There are many levels of LIMS commercially available or can be in-house programmed, depending on requirements, resources and finally the budget.
- One most important issue for an organised sample workflow is a unique sample identifier (ID). In-house, collaborators or customers will submit samples with fancy names, this have to be linked to an internal unique ID. This allows to track the sample through the whole process, from receiving to the report and track back to the origin of the sample.
- The most basic LIMS allows to record the incoming or in-house generated samples and sign the internal sample ID. All information available for the sample are linked to this ID. The source of the sample, the suppliers and the storage places and the storage conditions are recorded also. This makes it easy to find the sample when the analysis starts. Legal documents, like IRB approval, should be stored in the database and linked to the samples.
- The next step covers all the information about the suppliers in a separate record, like contact, addresses, responsible people on both sites.
- The next level is the workflow applied to the sample. For each step in the process, the standard operation procedure is attached. This can be a pdf or a text file, best with version number in case of changes.
- Further, during every step the operator can add observations or anything happening to the sample.
- The generated data can either be directly read into the LIMS, some software allows this. This works nicely if the data are simple, like a pH value, an UV absorbance, a recorded fluorescence, for example. More complex data, especially proprietary raw data as from HPLC/UHPLC or mass spectrometers should be stored in a save place and this location is recorded in the LIMS.
- After processing the data and analysing them, the results are stored in the LIMS with comments for a future report.
These are only simple functions of a LIMS, programmed in a relative database.
More advanced functions for large studies can be batch generation, stratification, randomisation, generation of sample tables for instruments.
It can also help information about instruments as service, calibration, tuning, training and more, about consumables and reagents and anything else related to the lab work.
A basic LIMS can be done in-house or with free programers, but it must be sure that all is well documented and if the programer is no longer available, others know what to do if needed. Such a LIMS will grow over the years from basic functions to advanced functions.
Highly complex LIMS systems are commercial available, expensive, but not ready to use out-of-the-box. Based on the given background structure, the users have to define the functions and the processes in the LIMS. Tis requires a dedicated person, knowing the workflow in the lab and the LIMS structure and language.
Every LIMS should be SQL-database based. In case of problems the data can still be retrieved.
A simple, non commercial LIMS database can be created using free tools as MySQL and others.