User:Shawndouglas/sandbox/sublevel4

LIMS Requirement Development Is More Than a Laboratory Wish List

When planning a project, it makes perfect sense to initially research and detail the specifics of the project. In the case of software development, this initial planning is vital to ensuring the project is legitimate in the eyes of critical stakeholders. This demands the development of a software requirements specification. Merriam-Webster defines a "specification" as "a detailed precise presentation of something or of a plan or proposal for something." From the perspective of submitting a software requirements specification to stakeholders, this definition makes sense. Without this critical specification step, the software development project is sure to face the second most commonly cited reason for project failure: poor requirements management.

How should software developers approach their software requirements specification? The ISO/IEC/IEEE 29148:2018 standard describes the characteristics that make up quality software requirement development, including aspects such as:

• correctly describing system behavior;
• effectively removing ambiguity from the language used;
• completely covering the system behavior and features;
• accurately prioritizing and ranking the requirements; and
• unequivocally ensuring the requirements are testable, modifiable, and traceable.

In the scope of laboratory information management system (LIMS) development, the developer and distributor (i.e., the vendor) has a head-start on the targeted end user: the vendor has a standard to turn to in its requirements development. The laboratory seeking a LIMS doesn't really have such a standard for developing a set of requirements for their acquisition, and many won't even know they should develop a set of LIMS requirements before engaging the acquisition process.

The rest of this article will examine what a laboratory should consider in developing and using LIMS requirements as part of acquiring and implementing a LIMS.

What is a requirement, and what requirements are typically associated with a LIMS?

Broadly speaking, a requirement is a statement of a need, sometime accompanied by additional context. A requirement typically begins with "the system/user/vendor shall/should ..." and focuses on a provided service, reaction to input, or expected behavior in a given situation. The statement may be abstract (high-level) or specific and detailed to a precise function. The statement may also be of a functional nature, describing functionality or services in detail, or of a non-functional nature, describing the constraints of a given functionality or service and how it's rendered. An example of a functional software requirement could be "the user shall be able to query either all of the initial set of databases or select a subset from it." This statement describes specific functionality the system should have. On the other hand, a non-functional requirement, for example, may state "the system's query tool shall conform to the ABC 123-2019 standard." The statement describes a constraint placed upon the system's query functionality.

Over the years, a wide variety of companies, consultants, and researchers have compiled collections of requirement statements like these for laboratory informatics systems. These compiled lists of requirements for how a given laboratory informatics solution should be developed, implemented, and maintained have changed as technology and user demand have evolved. Historically, however, LIMS requirement lists have expanded to encompass a mix of "wishlist" requirements from laboratories seeking a LIMS, as well as regulation-mandated requirements. Over the years, the wishlist items haven't necessarily been ignored by developers, with many of them making their way into broader LIMS functionality. However, laboratories submitting these wishlist requirements do in fact need to prioritize them as "nice to have" or "essential to system operation," or something in between (more on this a bit later).

The end result is the functionality of a LIMS has evolved over the past few decades, and so have the requirements laboratories have for their LIMS. This evolution of software and requirement lists has found its way into several key places. One critical place to find such LIMS requirements is the ASTM E1578-18 Standard Guide for Laboratory Informatics, last updated in 2019. Its Appendix X1. Laboratory Informatics Functional Requirements makes for a great starting place for any lab seeking to acquire a LIMS or some other laboratory informatics solution. Another source for LIMS requirements is LIMSpec, which incorporates most of ASTM E1578 and adds requirements influenced by a wide variety of other standards, regulations, and guidelines. A sampling of some of the more crucial requirements includes:

1.18 The system shall have the ability to maintain the chain of custody of every sample, meaning the recording of every single sample distribution step to personnel—including details such as unique identifier, name, location, date, and time—while the sample is in the laboratory’s possession.

3.13 The system shall be able to record a complete record of all data created in the course of a test or experiment, including instruments used, calculations performed, and associated graphs, charts, and spectra. The record should also be able to capture the signatures of those who performed the test or experiment, as well as those who reviewed the record for compliance purposes.

7.1 The system shall be capable of creating, managing, and securely holding a variety of document types, while also allowing for the review and approval of those documents using version and release controls.

14.1 The system shall allow for accurate inventory management of all standards, reagents, and consumables used for laboratory testing. The system shall also be able to link manufacturer documents such as material safety data sheets and in-house instructions to their respective materials.

27.4 The system shall provide a guaranteed means to retrieve and restore archived data and metadata that is readable and accurate.

31.4 The system shall have a mechanism to securely retain data in the system for a specific time period and enable protections that ensure the accurate and ready retrieval of that data throughout the records retention period.

How should labs develop their requirements?

1. Detail the existing information management system or processes (even if they are manual).
2. Define the associated information and data, and classify their criticality.
3. Identify current and previous information management policy and tools, as well as their effectiveness.
4. Identify the regulations, standards, and best practices affecting your laboratory and its digital assets.
5. Identify the laboratory's various practical workflows and detail how information management tools intersect and improve the workflows.
6. Perform a gap analysis of the current information management system or processes (i.e., define what needs are currently not being met).
7. Declare and describe objectives based on the outcomes of the above assessments, highlighting how you envision identified gaps should be filled.
8. Select and refine requirements based on the assessments, objectives, and policies highlighted prior, identifying a handful of the most critical requirements.

What other considerations should a lab make with their LIMS requirements?

While a laboratory can call up LIMS vendors, ask for a demo, and compare notes on the lab's requirements, it may make sense for the lab to issue a formal request for information (RFI) or request for proposal (RFP) and have major vendors approach the lab with how they can meet its needs. The RFI and RFP are traditional means towards soliciting bidding interest in an organization's project, typically containing the organization's specific requirements and vital questions that the bidder should be able to effectively answer. However, even if your organization chooses to do most of the investigative work of researching and approaching LIMS vendors, turning to a key set of questions typically found in an RFI is extremely valuable for "fact finding."

An RFI is an ideal means for learning more about a potential solution and how it can solve your problems, or for when you're not even sure how to solve your problem yet. However, the RFI should not be unduly long and tedious to complete for prospective vendors; it should be concise, direct, and honest. This means not only presenting a clear and humble vision of your own organization and its goals, but also asking just the right amount of questions to allow potential vendors to demonstrate their expertise and provide a clearer picture of who they are. Some take a technical approach to an RFI, using dense language and complicated spreadsheets for fact finding. However, vendors appreciate a slightly more inviting approach, with practical questions or requests that are carefully chosen because they matter to you. Remember, however, that an RFI is not meant to answer all of your questions. The RFI is meant as a means to help narrow down your search to a few quality candidates while learning more about each other. Once the pool of potential MSSPs is narrowed down, more pointed questions can be asked to ensure those providers meet your needs.

Be cognizant, however, that there may be no LIMS vendor that can meet each and every need of your lab. Your lab will have to make important decisions about which requirements are non-negotiable and which are more flexible. The vendors you engage with may be able to provide realistic advice in this regard, based upon your lab's requirements and their past experience with labs in your industry. As such, those vendors with real-world experience developing systems for laboratories in your industry may have a strong leg up on other vendors, as they can make informed comments about your lab’s requirements based on their past experiences.

If you have zero experience developing an RFI, you may want to first seek out various example RFIs on the internet, as well as some basic advice articles on the topic. Some websites may provide templates to examine for further details.