Favorite LIMS Implementation Tips From LabLynx’s Staff

Finding the right laboratory information management system (LIMS) is hard. Implementing it once you find it can be even harder if you do not have the right support around you. At LabLynx, we’ve applied our 25 years of experience in the LIMS industry to simplifying our implementation process and making it as painless as possible. A big component of our success in this area is our knowledgeable staff. Most having come from the laboratory industry themselves; our team brings their industry insights to help our clients through the big change management process that comes with implementing a LIMS.

In this article, our team shares some of their favorite LIMS implementation tips to help clients prepare for the transition process and make it as easy as possible:

“Make sure to assign one contact from your team that has the end say in how the system is setup.  So many times during implementations, we meet with a group or two and they want it to work this way but another groups wants it to work that way. It is important for your team to work together to decide how you want it to flow, what you want it to look like, from the overall workflow down to the sample number layout.” – Stacie Albenesius, Senior Application Engineer

“Discuss a change management procedure with your Application Engineer/LIMS project manager. Some clients employ a project manager to oversee the implementation while a separate group, such as lab team members, conduct the implementation with the Application Engineer. A change management procedure will help the team pinpoint key features and areas needed by the client team and help minimize going out-of-scope on the project.” – Patrick Cansler, Application Engineer

“Document EVERYTHING. Any current process, any workflow, wish list items, and all reports/labels currently used. Having a thorough list of all documented requirements from the client is extremely helpful for an implementation.” – Jon Stoll, Associate Application Engineer

“If transitioning from a current system or method, be careful to not focus only on resolving pain points, but also on what currently works well. With a new system, it is common to primarily focus on what could be improved and lose sight what is working, potentially causing project delay and overages down the line, or worst case, a system that can’t accommodate necessary functionality.” – Nathan Farmer, Associate Application Engineer

“When working on interfaces that are file based, wait until the instrument is fully validated and multiple tests have been run through before providing documentation. Once that is complete, then provide an example result file that has more than one sample (if instrument runs more than one sample at a time). Providing a file too early on or with only one sample can result in having to go back and make changes down the road to the interface. Be sure to fully validate the instrument first to save costs in the long run.” – Senior Application Engineer, Dr. Stephanie Pate

“Try every scenario and try it again! Cancel tests, put samples on hold – don’t leave any button untouched when going through the site before going live.” – Julianna Vale, Associate Application Engineer

“Plan for the change and have appropriate expectations with the timeline as you never know what will come up with implementation.” – Sara Allen, Associate Application Engineer

LIMS Implementation You Can Trust

Are you looking to make a switch to a new LIMS? Get started today with an experienced team that will support you through the implementation process and beyond. Find out more about our highly configurable and flexible ELab LIMS designed for your laboratory by scheduling a call with a member of our team.