search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
33 LIMS & Lab Automation


updates do not disrupt the confi guration. Changes made to the confi guration are immediately refl ected in both the desktop and web applications, requiring no additional effort.


Myth 6: All LIMS are confi gurable - are they really?


Given that each laboratory is unique, even within the same industry, it’s common to encounter claims from various vendors asserting that their LIMS is highly confi gurable. However, the reality is often far less clear-cut, and the term ‘confi gurable’ can have different interpretations among vendors.


a) ‘Administrative Setup’: Some vendors may consider basic tasks like confi guring tests, user profi les, submitters, and other metadata as part of their confi guration capabilities. In truth, these activities are primarily administrative functions within the LIMS and don’t truly constitute confi guration.


b) ‘Scripting and Programming’: Other vendors may rely on scripting or programming languages like LimsBasic, C#, or Java and label this as confi gurable software. However, this approach essentially amounts to customisation rather than true confi guration. It poses challenges, such as falling into GAMP Category 5 [2], which can impact the validation of the initial solution and future upgrades. Changes made through coding may not seamlessly integrate into a user’s system during upgrades, often requiring additional work and potential compatibility issues.


In contrast, our supplier employs a distinct Confi guration Tools approach during both implementation and updates. These tools don’t demand programming expertise, resulting in cost-effective and swift implementation compared to customisation. All changes remain separate from the underlying code, ensuring they don’t affect it, and vice versa. This streamlined core system facilitates easier upgrades with minimal validation and re-validation concerns. Moreover, all changes are version-controlled and can be rolled back if needed. Confi guration changes undergo approval before general use, providing a high degree of control. Users can even receive training in these confi guration tools, granting them greater autonomy in making confi guration adjustments. Importantly, changes made using confi guration tools are immediately visible and verifi able on real screens, eliminating the need to write code and then verify the outcomes.


This leads to a fundamental question regarding systems relying on customisation: do they offer the same benefi ts? To gauge whether a system is genuinely confi gurable or relies on customisation, a simple test is to inquire with the vendor about their support for the changes you might make, and whether this support is part of the standard agreement without extra charges. Our confi dence in our confi guration approach is such that we support all customer-developed or modifi ed confi gurations as a standard part of our support agreement, without any additional cost.


Myth 7: If the lab implements a LIMS, how will this affect


my job Laboratory staffs sometimes worry that a LIMS will remove the need for their role. This is because LIMS are often initially justifi ed by effi ciency gains and cost savings. Often this comes down to estimating how many Full Time Equivalents (FTEs) of time will be saved by implementing a LIMS and automating lab processes. Taking an over-simplifi ed approach like this can lead to the fear that time saved in processes such as automating sample receipt, result


entry, calculations, review, and approval of results, and creating certifi cates of analysis will just result in cuts to staffi ng levels in the lab.


Over and over again we have seen that cutting staff is rarely, if ever, the end result of a successful LIMS implementation. The reality is that effi ciency gains allow the laboratory staff to better use their key skills, training, and ability to innovate while the organisation improves its performance, quality, and throughput.


Myth 8: Can we afford a LIMS?


The real question to consider here is whether you can afford to go without a LIMS. Laboratories, often overwhelmed with manual paperwork, result validation, and certifi cate generation, can sometimes overlook the clear benefi ts of adopting electronic data management and leveraging software capabilities for tasks like certifi cate creation, generating management reports, establishing self-service client portals, and more. Customer case studies provide concrete evidence that embracing electronic data management and software-driven processes leads to more effi cient resource utilisation.


To explore these advantages in detail, we encourage you to reach out to the author and request the ‘Justify the Purchase of a LIMS’ white paper. This resource will help you recognise the tangible benefi ts of implementing a LIMS, including time savings, enhanced inventory management, and reductions in human error and re-work. Armed with this information, you’ll be better equipped to build a compelling business case for adopting a LIMS within your organisation.


Furthermore, it’s worth noting that a reputable LIMS should offer a subscription-based pricing model, allowing you to pay an annual fee rather than an upfront cost for user licenses. This operational expenditure approach might be easier to justify within your budgetary framework compared to capital expenditure, making it a viable option for your consideration.


Summary


LIMS systems vary signifi cantly, so how can you narrow down your options to create a shortlist of potential solutions? One of the most crucial inquiries to prioritise is the confi guration process. Is this solution confi gurable, and can customers confi gure it to suit their specifi c needs? Additionally, does the vendor’s helpdesk provide support for customer-confi gured setups? It’s essential to recognise that no two labs are identical; each one has its unique requirements. To make informed decisions, employ compare and contrast techniques to unveil concrete facts and dispel any myths, whether they originate from vendors or internal staff. A discerning and critical approach will serve as a valuable guide in your selection process.


For more information, please email the author Dr Phil Williams at phil@lims4u.co.uk or visit ‘LIMS4U’ on LinkedIn. Phil has 38 years’ experience in Lab automation. He founded LIMS4U in 2019 and offers LIMS marketing services primarily via LinkedIn (29,850+ followers).


Acknowledgements: Thanks to Autoscribe [1] who supplied some of the dialogue used.


References: 1. https://www.autoscribeinformatics.com/ 2. https://ispe.org/topics/gamp


Software-as-a-Service LIMS for QA/QC


LabWare QA/QC is a full featured Software-as-a-Service (SaaS) LIMS designed to support analytical testing laboratory workflows in any industry. Based on the powerful LabWare lab automation platform, LabWare QA/QC is cloud hosted and accessible on any browser and on any device. LabWare QA/QC comes fully validated enabling rapid deployment in your testing environment in under 30 days. Automate sample management, improve throughput, and ensure compliance by adhering to all data integrity guidelines in your laboratory. More information online: ilmt.co/PL/L56mz


57196pr@reply-direct.com


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64