Difference between revisions of "User:Shawndouglas/sandbox/sublevel6"

From CannaQAWiki
Jump to navigationJump to search
Line 130: Line 130:
'''Title''': ''LIMS Buyer’s Guide for Cannabis Testing Laboratories''
'''Title''': ''LIMS Buyer’s Guide for Cannabis Testing Laboratories''


'''Author for citation''': Shawn E. Douglas
'''Author for citation''': Shawn E. Douglas, Alan Vaughan


'''License for content''': [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International]
'''License for content''': [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International]

Revision as of 21:38, 23 January 2021


-----Return to the beginning of this guide-----

4. LIMS acquisition, implementation, and support

4.1 Business considerations

4.2 Acquisition and licensing

When selecting a cannabis testing LIMS, there are two primary questions to ask at the outset:

1. What do I want the LIMS to do for me?

2. What kind of budget do I have?

The answer to the first question is largely the same as most other kinds of labs. The benefits a LIMS provides includes:

  • increased accuracy: the minimization or elimination of transcription and other errors;
  • streamlined processes: ensuring each process step in a protocol/method is completed in the proper order, with all requirements met, updating sample statuses automatically;
  • automation: integration with instruments, allowing for automatic uploading of samples and returning of results;
  • regulatory and standards compliance: functionality that aids with compliance, including reporting results to state and local authorities;
  • data security: role-based, configurable, secure access to data, processes, reporting, etc.;
  • custom reporting: reporting tools that allows for the design and generation of certificates of authority and other reports to lab- and regulation-based specs;
  • instant data retrieval: query tools for finding data instantly according to any criteria (date range, test, product type, etc.); and
  • configurability and cost-effectiveness: a user-configurable system (as opposed to hard-coded, requiring development for any modifications) that is flexible enough to adapt to rapid changes in test volume and type over time, without breaking the bank.

Addressing the second question concerning budget is more difficult, as a cannabis testing LIMS comes in all kinds of price ranges. How are you supposed to judge the appropriate system price for your lab? There are some basic realities that can help in figuring an appropriate budget:

1. Vendor pricing is generally based on how many will be using the LIMS. This can be measured in concurrent users (how many will be using the LIMS at any one time) or named users (the number of total users who will ever use the LIMS, by name). Additionally, cannabis testing LIMS vendors increasingly offer the option of a cloud-hosted subscription, which of course has the advantage of not requiring your own IT department, and allowing labs to defray cost over time, with little or no actual license fee. Think about your usage strategy and choose the pricing format that makes the most sense for you.
2. Most costs are related to the work involved with installing, configuring, and migrating data to the LIMS. Try to choose a solution that has what you need out of the box, as much as possible. The more customized or unique options you ask for up-front, the more it tends to cost, as extra items are a function of the time it takes developers to add them.
3. "User-configurable" beats "vendor-configurable" on cost-effectiveness. Many LIMS vendors offer a free or low-cost option, but don't be fooled. They are in business to make money, and they are counting on the fact that you'll need to pay them to make things work, add necessary functionality, and provide support and training. If you can find a vendor who offers a genuinely user-configurable LIMS, and whose manuals and other support materials are clearly helpful and available so that you can adjust things the way you want, when you want, then that will go a long way toward budget efficiency and longevity.
4. Additional interfaces cost money. If necessary, consider phasing in any additional instrument and software interfaces over time, as revenue eases cash flow. You can go live with your LIMS operations more quickly, entering results manually until you can afford to interface your instruments one-by-one. This goes for reports as well; a simple reporting module that meets regulatory requirements will do. You can make fancier ones later.

Additional considerations

In addition to those two primary questions, you'll want to make a few more acquisition-related considerations. First, can the vendor provide a full demonstration of their software, addressing your own requirements at the same time? You likely are familiar with all of your lab's or potential lab's processes and methods, as well as the regulations that drive them, but that doesn't mean you necessarily have a full understanding of how a cannabis testing LIMS fits in to those processes and methods. That's where a knowledgeable and prepared vendor steps in. A quality developer already generally understands your kind of lab but will ask you a lot of questions about exactly how you do things. It's the exceptions that need catering to. Sitting in on a live, interactive demo that can be recorded—so you can review and share it with others later—is a great context for exploring how the LIMS performs the functions your lab requires. Being live, you can also see just how it performs in real time, and you can ask as many hypotheticals as you like. That kind of scenario can go a long way towards giving you a real feel for its suitability. Additionally, both you and the vendor can gain a concept of budget and how the LIMS fits with it, based on what your lab does, what you want the LIMS to do, and how it is implemented.

Second–after the demo—you should consider develop your requirements list or specification. By proceeding with this after the demo, a common error is avoided: too often labs think the first thing they must do is create a requirements list, then sit back and let the LIMS vendors tell them how they meet it. As mentioned earlier, even though they understand their processes, most labs don't have as strong a grasp on the informatics portion. Participating in a demo before creating the requirements list is a great way to plug in the LIMS features you have seen demonstrated to your lab's processes and needs. After all, how can you effectively require cannabis testing LIMS functions if you don't fully know what such a LIMS is capable of? As for making your requirements list or specification, you may wish to turn to the LIMSpec for Cannabis Testing, a specification document designed specifically to help vendors and buyers with the system requirements of a cannabis testing LIMS. This specification document is detailed further in Chapter 5.

At this point you are much more equipped to create a requirements list, which later becomes the contractual product set and scope of work (SOW) that represents the implementation of your LIMS.

4.3 Implementation, maintenance, and warranty

You may have heard other people's stories about an enterprise-class software deployment gone wrong. But they often go right, thanks to knowledgeable, well-prepared staff with experience in getting new software up and running in a business. The tricky part, of course, is finding a developer who both makes a quality product and is skillful in helping you get it implemented into your unique workflow. That developer should, ideally, also provide clear guidance on what maintenance of your system should look like, as well as what their support and warranty services are.

4.4 LIMS solutions for cannabis testing labs

The following LIMS solutions are known (publically marketed) to specifically offer features that support the cannabis testing laboratory:

Table 1. Known LIMS solutions publically marketed as addressing the needs of cannabis testing labs
LIMS solution Developer
ApolloLIMS Common Cents Systems, Inc.
Bika LIMS Bika Lab Systems (Pty) Ltd and
the SENAITE Foundation
CannabLIS Cannabliss New England, LLC
CannaLIS Specialty Testing Solutions Ca, LLC
CannaQA LIMS LabLynx, Inc.
CGM LABDAQ CompuGroup Medical AG
CloudLIMS and FreeLIMS CloudLIMS.com, LLC
Confident Cannabis LIMS CC Software, LLC
Element LIMS Promium, LLC
HORIZON LIMS HORIZON Lab Systems, LLC
LabWare GROW LabWare, Inc.
LabFlow AINZ Corp.
LIMS ABC BGASoft, Inc.
Lockbox LIMS Third Wave Analytics, Inc.
Matrix Gemini Autoscribe Informatics, Inc.
Omega LIMS Khemia Software, Inc.
QBench Junction Concepts, Inc.
QLIMS OnQ Software Pty. Ltd.
reLIMS Carobar Business Solutions, LLC
-----Go to the next chapter of this guide-----

Citation information for this chapter

Chapter: 4. LIMS acquisition, implementation, and support

Edition: Winter 2020

Title: LIMS Buyer’s Guide for Cannabis Testing Laboratories

Author for citation: Shawn E. Douglas, Alan Vaughan

License for content: Creative Commons Attribution-ShareAlike 4.0 International

Publication date: TBD