Skip to main content Skip to main navigation Skip to search Skip to footer

LIMS Integration Framework Model

LIMS Integration Framework Model

Abstract

Today’s LIMS business applications rarely live in isolation. The LIMS users expect instant access to all the LIMS business functions an enterprise can offer, regardless of which LIMS system the functionality may reside in. This requires disparate LIMS applications to be connected into a larger, integrated solution. This integration is usually achieved through the use of some form of “middleware”. Middleware provides the “plumbing” such as data transport, data transformation, and routing.

Excerpts from the Paper

Architecting LIMS integration solutions is a complex task. There are many conflicting LIMS process rule engines and even more possible ‘right’ solutions. Most integration vendors provide methodologies and best practices, but these instructions tend to be very much geared towards the vendor-provided tool set and often lack treatment of the bigger picture, including underlying guidelines, principles and best practices. Asynchronous messaging architectures have proven to be the best strategy for enterprise integration because they allow for a loosely coupled solution that overcomes the limitations of remote communication, such as latency and unreliability.

The trend towards asynchronous messaging has manifested itself in a variety of EAI (Enterprise Asynchronous Integration) suites as well emerging standards for reliable, asynchronous web services. Many of the assumptions that hold true when developing single, synchronous applications are no longer valid. What is needed is vendor-independent design guidance and framework model on building robust LIMS integration architectures based on asynchronous messaging.

DOWNLOAD THE WHITEPAPER

Contact Us
MAX CHARACTERS: 10,000

We will treat any information you submit with us as confidential. Please read our privacy statement for additional information.

We will treat any information you submit with us as confidential. Please read our privacy statement for additional information.