Choice of Solutions

Once you have decided that you’re ready to transition to a new ELN or LIMS you will need to decide whether to implement a

1. Traditional solution
2. A Cloud hosted solution
3. A Cloud solution provided as a service (Software as a Service or SaaS)

Traditional ELN/LIMS vendors have historically controlled the market, however SaaS providers have made recent advances. As you consider a solution for your lab, you will need to assess the risk/benefits associated with each type of solution.

Progression to the Cloud

Cloud computing concepts are not as new as you would think. In fact, since the 1950s the computer revolution was driven by hugely expensive mainframes shared among “dumb” terminals. This configuration shares similarities with the Cloud only limited within a company. Introduction of affordable personal computing in the 80s and 90s revolutionized home computing but companies continued to keep big, expensive, server farms inside their corporate walls.

The advent of the Internet introduced the “Cloud” era.  Products like Salesforce and services like Amazon Web Services gave Cloud access to any size company providing scalable, secure and inexpensive remote computing.  This revolution is not (only) driven by the research of computing power but, rather, by the infinite possibilities of having a system that can be used anywhere and by anyone.

Some of the benefits derived from Cloud solutions:

• Ability to access data remotely
• Minimize Total Cost of Ownership – IT footprint (Hardware, Maintenance, Personnel)
• Scalability – easily scale hardware to support user load.

Recognize the Total Cost of Ownership of a traditional solution

Actually, “out of the box” traditional solutions entail a big effort to install, setup, and configure.

These are complex systems that require dedicated Servers, Databases, File Shares and Integration with other systems.  Once those items have been accounted for there will still be a need to allocate a team to support the various systems and take care of all the periodic activities like monitoring and patch installations.

Even if your Company already has a strong IT footprint, ask yourself, “How efficient can our IT department be when supporting a tool that’s not developed by them? How many hours, days or months would they need to invest in keeping themselves up to date with the latest releases or investigating every issue that will arise? Is this necessary for our core business?”.

This article will focus on the Pharmaceutical industry and the transition these labs are making from paper to digital documentation for a paperless lab. For years, investment in digital solutions to manage, record, and make sense of lab data was mainly limited to major pharmaceutical institutions.

These companies initially deployed Laboratory Information Management systems (LIMs) and more recently Electronic Laboratory Notebooks (ELNs). Now, even smaller laboratories can afford and benefit from the transition from physical notebooks to a digital environment.

Why Go Paperless?

1. Data is stored in one easy to find location.
   The data isn’t in multiple notebooks stuffed into the bottom of someone’s desk or in off-site storage but accessed via a database or cloud solution.
2. The capability of sharing documents.
   Through managed access, users can share documents, review documents, and approve documents, increasing the laboratories efficiency.
3. Search Tools.
   Users can search for documents, resources, methods, etc. when they need them. Instead of having to leave the lab and look for a specific item, the user is able to digitally find, review and, if desired, reference or attach supporting documentation.
4. Cost Savings.
   The laboratory will be able to complete more tasks using the same resources, with documented efficiency increases of 30% over paper systems. In addition, the lab also avoids the costs of off-site storage for physical notebooks.
5. Compliance.
   Some ELN and LIM systems are Regulatory Compliant.

What does ELN and LIMS mean and Why It Matters?

The strength of an ELN solution is its ability to efficiently document laboratory work processes, enhancing collaboration and document sharing among colleagues. However, typical ELN solutions often lack robust support for defining samples, conducting detailed analyses, and structuring results—essential for advanced developmental stages. They also fall short in workflow management, including document and sample review cycles, and adhering to Good Manufacturing Practice (GMP) regulations. Consequently, ELNs are primarily suited for early-stage development or must be supplemented with a LIMS for comprehensive support in pharmaceutical development.
The strength of a LIMS lies in its comprehensive management capabilities, effectively overseeing samples, users, instruments, resources (such as solutions and standards), structured data, and integrating applications seamlessly. Positioned at the core of information management, LIMS enables processing and reporting of data essential for later stages of drug development. However, its highly structured framework can impede capturing real-time bench data effectively. Moreover, implementing and maintaining a LIMS poses challenges, especially for smaller companies lacking dedicated IT resources.

Combining ELN and LIMS offers significant advantages for companies involved in advanced drug development stages. ELN serves as a practical solution for recording bench activities efficiently, interfacing seamlessly with LIMS to access managed resources, while LIMS acts as the central control and reporting hub. Previously, integrating ELN and LIMS required substantial corporate commitment and resources. Recent advancements, exemplified by SciCord, highlight a shift towards hybrid solutions that integrate the best features of both ELN and LIMS into a single application. This approach eliminates the need for complex integration processes, thereby minimizing implementation and maintenance efforts required to achieve a fully paperless laboratory environment.

How to decide on an ELN and LIMS?

Selecting an ELN or LIMS system depends largely on a laboratory’s specific needs and developmental stage. Considerations include the types of work planned for the future and whether an ELN alone suffices or if integrating a LIMS is necessary. For non-GMP laboratories, investing in expensive GMP-compliant digital documentation systems may not be necessary. Additionally, the size of the laboratory plays a crucial role in determining the feasibility of implementing and maintaining these systems.
While larger companies may prefer integrated ELN and LIMS solutions for comprehensive data management, smaller organizations lacking extensive implementation and maintenance resources might opt for hybrid models. It is essential to assess where and how the ELN/LIMS will be deployed, its integration with existing IT infrastructure, user interface friendliness, instrumentation compatibility, licensing models, and compliance requirements. Understanding these factors ensures that the chosen ELN and LIMS system effectively meets the laboratory’s operational needs and facilitates a smooth transition towards a paperless environment.

The continuous evolution of ELN and LIMS technologies provides laboratories with increasingly sophisticated tools to streamline workflows, enhance data integrity, and meet regulatory requirements. Advancements such as cloud-based solutions and integrated platforms offer flexibility and scalability, allowing laboratories of all sizes to adopt tailored solutions that optimize efficiency and support innovation in scientific research and development. By leveraging these technologies, laboratories can achieve greater operational agility, reduce costs, and accelerate the pace of discovery and development in the pharmaceutical and life sciences sectors.

Here are other items to consider:

• Where will the ELN/LIMS be in use?
• What is the Main Purpose?
• How will it be integrated with the current IT Infrastructure?
• Is the User Interface easily understood? ‘Friendly’?
• Instrumentation Connection?
• What type of Licensing Model?
• Compliant or Not Compliant?

Understand your needs before jumping-in to buy an ELN or LIMS. Too many times companies have sunk large amounts of money into Laboratory IT programs that sputter along and eventually fail. End-user adoption is important, but if the ELN or LIMS doesn’t integrate well with other systems, the end-user will never have a chance to utilize the ‘friendliness’.

SciCord offers a GMP-compliant product that can be used for Analytical QC, Developmental Studies, Synthetic Chemistry, and Manufacture Batch Records. It combines the compliance and structured aspects of the LIMS with the flexibility of an ELN. As SciCord is a cloud solution, no hardware will need to be purchased and integration with any current IT infrastructure is simple. The program can either be accessed via the web or through a Client portal downloaded onto the desktop. Also, because SciCord utilizes the spreadsheet paradigm the user interface is highly intuitive making the solution an easy transition for users.

Going Paperless

Choosing an ELN, LIMS, or Hybrid system is the first step towards transitioning to the paperless environment. The remaining way isn’t always easy.

Road bumps can be found with IT integration, end-user adoption, customization and validation issues. Nonetheless, the benefits of such a system far outweigh any of these road blocks and the best systems find a way to minimize these issues as laboratories make the transition.

Spreadsheets are utilized throughout the Pharmaceutical industry, which is why spreadsheet validation is so important. Well designed spreadsheets increase both efficiency and compliance, while poor spreadsheet validation and design can lead to frustration and in some cases to reporting incorrect results. The process by which spreadsheets are implemented is also critical for compliant laboratories and laboratory data validation. Weak controls around spreadsheet security and management have been the source of many regulatory findings. This article focuses on aspects of spreadsheet design that deliver solutions which increase efficiency and compliance. Design criteria which support compliant spreadsheet implementation are also addressed.

The design principles in this article assume a templated deployment pattern, where copies of a controlled template are created each time the process is run. The term “template” will be used to identify the master spreadsheet and “document” will describe template copies.

Scoping

Before embarking on spreadsheet creation, key aspects of the environment surrounding the eventual use of the spreadsheet should be identified. The key aspects are compliance, target audience, and specificity of functionality.
Obtaining answers to the following questions drives the applicability of specific design components which are described in detail below.

Is Compliance a Factor?

Determining if compliance is a factor is the most critical decision point in spreadsheet design. Compliant templates must adhere to regulatory requirements with careful design to facilitate document review and potentially template validation. Templates not utilized for compliant work can opt out of many design strategies specifically targeted at compliance. There are two strategies to assure accuracy of the information produced by a compliant template/document.

100% Review of each Document

This design option relies on qualified reviewers to verify the outcome of each formula in the spreadsheet. In addition, reviewers need to verify the results of automated outcomes (code which generates content), cell format of numeric results, and conditional formats which can flag outcomes (green/red for pass/fail results). This option is feasible for relatively simple spreadsheets or in situations where use is sporadic. In these cases, the overhead of individual document review can be less burdensome than the template validation strategy defined below. Spreadsheets should be designed to:

• Make sure that formulas are visible and easily understood
• Avoid use of conditional format or cell formats which transform cell values

Template Validation

Validation of the template is a variation on 100% review in which the spreadsheet functionality is specified, tested, and documented once. The major advantage of template validation is avoiding the need to review templated results and reports. For compliant organization, template is all but mandatory for complex spreadsheets and/or high volume usage.

Significant effort is required to validate and maintain validated spreadsheet compliance. Validated spreadsheets (including copies) must be maintained within an automated system or a set of manual processes must be in place which enforce version control and maintain custody.

Spreadsheet design must secure formulas or automated template functionality which generates results. The design should:

• Clearly indicate formulas or sections of the template which are validated and do not require additional review
• Lock and protect validated formulas
• Protect the spreadsheet from user interactions which could invalidate the verification (ie: deletion of a required formula precedent)

Who is Your Target Audience?

A second determinate of spreadsheet design is the target user community. The design criteria are very different as the number of users in the target community grows. The design for a personal spreadsheet can make assumptions regarding security, expertise, training, work process, and physical environment. For instance, a personal template can be designed to work with a specific instrument, target a specific sequence of events, assume knowledge of spreadsheet work arounds, and of course a personal template is a known commodity.

As the expected template audience increases, design must compensate for the different factors described above to deliver a robust solution generating quality results.

A widespread issue is the personal or small group template that becomes wildly successful beyond the initial group. In this situation, the template is often deployed to a wider audience without addressing new design requirements. Lack of a suitable wide audience design can result in a less successful roll out.

How Specific is the Functionality?

The trade-off between specific and generic should be carefully considered to determine if the upfront effort for a generic template offsets the added maintenance required for multiple specific templates.

Below are a list of some of the Pros and Cons to help in determining how specific You should be in your Template Design:

Specific Functionality

Generic Functionality

Design Components

Tables

Tables are used extensively in most spreadsheets. The tables may record samples, preparation data, resources, results, etc. Tables in most spreadsheets are predefined meaning that the maximum number of table rows/columns is ascertained during spreadsheet development. For instance, a sample preparation table may be defined to support up to 20 preparations. Each preparation may require cells for weights, volumes, and formulas to calculate concentrations. If each preparation is displayed on a row, there will be a total of 20 rows complete with predefined cells for weights, volumes, and concentrations.

Cell Fill and Font Colors

Consistent use of cell color in spreadsheets is an important design component. A unified color scheme can:

• Designate cells with specific functionality
• Flag potential issues or compliance concerns
• Increase usability for both the Author and Reviewer
• Increase reviewer efficiency

Color schemes are optional for personal spreadsheets, but spreadsheets deployed to a wider audience should implement a consistent color scheme. Be sure the selected color scheme is printable as some fill/font combinations do not translate to grey scale printers (many office printers).

Define Colors for cells containing:

• Formulas:
  Cells containing predefined calculations are typically locked to prevent inadvertent changes. Identifying formula cells alerts authors to the location of cells which are not normally edited. Reviewers are alerted to formulas which do or do not require review depending on the validation strategy
• Expected Entry:
  Cells where entry by the author is expected. By identifying these cells, authors are guided through the process and reviewers can verify that all expected entries are as expected
• Available:
  Cells which are not predefined for a purpose but can be utilized by authors to record
• Status:
  Cells which define the standing of a material, instrument, or other component. Status is often an indicator of a potential compliance issue and should be clearly flagged. Traffic light colors will make this information stand out and quickly identify compliance concerns

Example:

Data Validation

The best path to creating a robust spreadsheet is to assure the initial data entry is recorded correctly. Data validation of numbers allows spreadsheet developers to force data entry values to be within acceptable parameters which also assists with spreadsheet validation since endpoints are defined by the data validation max and mins. This also means that you need to use the right data validation tools. One caution with this technique is that limits may not be defined broadly enough and legitimate values cannot be recorded. This potential drawback can be avoided by using a data validation “Warning” rather than “Stop” when an error condition is encountered.

Conditional Format

A great way to highlight alert situations or pass/fail results is through conditional formats. The format of target ranges can be manipulated based on any input.

Conditional formats are however difficult to maintain since the underlying conditional formula is not easily displayed or obvious. To overcome this issue, place all formulas which evaluate a condition in hidden cells on the spreadsheet and include only simple references in the conditional formula. A simplistic example is a result to be colored red if greater than 7. A hidden cell would contain the evaluation in a formula myResult > 7″. The conditional formula would reference this hidden cell =myCondition=TRUE.