LIMSzine
The following column highlights a particular session that was held at
the 10th International LIMS Conference in which attendees were asked what
they would like to have in a next generation LIMS. Sometimes a new technology
that was being implemented by a vendor was discussed; sometimes the issue
was related to workflow in the lab.
If you could design the perfect LIMS (Laboratory Information Management
System) for your lab, what would you include? This question was the topic
of a focus group session at the International LIMS Conference held earlier
this year in Pittsburgh, PA. About 50 users and a handful of vendors gathered
to discuss the most desired features and functions of the next generation
LIMS in the hour-long session moderated by Jeffrey Miller of Bayer Corporation.
A list of functions and capabilities -- from interfaces to architectures
-- was provided to spark discussion. Miller started the session by stating
that while vendors seem to be controlling the future of LIMS, this is the
perception rather than the reality of the marketplace. "This forum
is designed to get information from end-users on what you would include
in your 'Dream LIMS' if you actively designed one," he stated. Several
key points emerged.
Interfaces
Interfacing issues generated the greatest response, and covered not just
the interface to the instrument, but the interface to the enterprise as
well. "I'd like to have plug-and-play software, plug-and-play LIMS
right off the bat," offered one end-user. Better system administrative
tools -- such as archiving, files, and data access -- from more than one
platform, including spectroscopy, chromatography, and MS data, were another
coveted capability.
Desire was also expressed for an easier-to-use interface to legacy systems
as well as corporate systems, peer systems, and MRP/process control systems.
Often the LIMS feeds these other systems with the data they need to perform
their functions. One user pointed out that most LIMS are custom-coded and
are thus difficult to modify or link to other systems. This underscores
the need for a plug-and-play capability to other areas of the organization.
Several people touched on the possibility of using the Internet as a common
interface.
Dr. Reinhold Schaefer of Weisbaden University, Germany, stated that the
concept of plug-and-play functionality, particularly when using third party
packages, is useless if the data extraction capabilities do not exist within
the LIMS.
Without interfaces to other systems in the organization, bottlenecks arise.
As a result, there was strong consensus that not only are cleaner interfaces
between systems required, but so is a recognition on the part of the vendors
to anticipate these needs.
According to Connie Bradberry of HBOI, Ft. Pierce, FL, part of the problem
is access to internal resources as well as access to internal systems. Help
is needed to collect data, such as instrument calibration, from other resources
within the company. LIMS vendors should accommodate wider needs such as
these. "Right now," observed another user, "vendors are saying
it's not their job."
Communications
The need for hands-on, face-to-face communications emerged as a key requirement
to ensure LIMS success. "Part of the confusion regarding how a LIMS
connects other internal systems is caused by the lack of strong definitions
by the vendors," explained one user. "It is not clear what the
vendors will do and what they won't."
Such interaction also points to the need for greater communication between
the IT/IS (Information Technology/Information Systems) department and the
lab. For instance, report writers on most LIMS are not fourth generation
language (4GL), but 3GL or a scripting language that has limited functionality
in regards to data parsing and expansion. As a result, the report writers
rarely take full advantage of the LIMS. This might not be the case if IS/IT
better understood the needs of the lab.
Bob Megargle of the University of Cleveland, OH, stated that "the conceptual
part of the LIMS has worked from the beginning." He pointed out that
a lot of what users want is possible and is often available, just not widely
publicized. "But the point is that these features and functions need
to be easier to use. And in a lot of cases, you need to have a very in-depth
knowledge of the system." In regards to the relationship between the
lab and IT/IS, he added that the LIMS needs to be easier for the chemist
to use rather than the programmer.
Standardization
The importance of on-going dialogue between the lab and IT/IS is driven
by the increasing need for a standard interface for all the systems in the
organization. This requirement will only continue to grow. One user stressed
the role standardization plays if only because of the support problems that
can, will and do occur.
The number of systems that need to be logged into was discussed, and a standard
interface was deemed necessary, especially to access diverse operating systems
(OS), because users want to jump back and forth between systems.
One complaint is that new robotics were difficult to add because these currently
come with proprietary interfaces. Again, a common interface and open standards
were endorsed as the best solution.
Growing the LIMS
To wrap up the session, Miller asked "Where do you see things going?
Is NT going to be the next wave of OS?" Several users stated that they
were planning to skip Windows 95 altogether and upgrade their system straight
to NT. Either way, it was the general consensus that those who set up LIMS
found it difficult to do so.
In regards to the difficulties of evolving a LIMS, one user pointed out
that "you need to have a philosophy of programming your vendors with
the ability to grow not only out, but deeper. A 'manage-your vendor' approach
is best."
The importance of projecting how the LIMS should function in three to five
years was also discussed.
"Resource allocation is a guessing game" added another user. "It's
difficult to assess future needs." Many users want the LIMS to help
with resource planning and capacity planning in the lab. For instance, if
the user knows how long it takes to run specific tests, and the MRP system
provides order and inventory projections, then the Lab Manager can better
plan lab activities and requirements.
In summary, many of the elements of the 'Dream LIMS' are dependent upon
the incorporation of existing technologies into the structure of the LIMS.
With a common interface, open standards, and open dialogue between the various
parties, most of the issues blocking the realization of the perfect LIMS
are resolved.