Buying a LIMS can seem overwhelming given the choice of solutions on the market. This ten-step guide helps you through the process and arms you with the questions you need to ask.
Requirements should be recorded using some form of requirements document. Many software products exist to help create and manage requirements and may be useful for large projects, but often it is possible to use standard tools such as Word or Excel.
It is sometimes said that a LIMS is a LIMS, but this is not necessarily the case. Most LIMS will support the basics of sample, test, and result management, but there can be significant differences between systems and the markets they target.
LIMS requirements are often ill-defined, imprecise and incomplete. This can make selecting the correct LIMS can be difficult and does not set the project up for success.
LIMS needs to have built-in flexibility to easily apply different types of limits within the broad range of industries served. Matrix Gemini LIMS is well known for its highly flexible capabilities and able to address these limit types with ease.
A two-part series covering what limits are and how to apply them in a LIMS. One of the many benefits of implementing a LIMS is the reduction, or elimination, of potential user error and the consistent application of standard operating procedures. Nowhere is this more important than in checking test results against predefined limits.
