Interfacing Instruments and Systems to LIMS: It Can’t Wait!
In the laboratory informatics (LIMS, ELN, LES, SDMS, etc.) universe, the value of interfacing and/or integrating lab instruments, lab data systems, business systems, and other enterprise information systems [i.e., enterprise resource planning (ERP) systems, a manufacturing execution system (MES), platform, etc.) to your LIMS has been well known and documented. These types of interfaces and the information and knowledge that can be garnered from them often are some of the biggest business drivers for implementing a LIMS. Additionally, these interfaces are major sources of efficiency gains, increasing collaboration and facilitating fast decision-making. The benefits are clear, but why is it that interfacing systems and instruments to a LIMS tend to be one of the last things done during a LIMS implementation if it is done at all?
This blog looks at some of the many reasons why instrument and system interfacing is still one of the underused pathways to informatics systems’ return on investment (ROI). In the years since this blog was first published, those reasons have only increased, while the potential ROI has only grown.
Recent innovations in systems and practices
In recent years, even traditionally conservative and risk-averse organizations (looking at you, Big Pharma) have begun to embrace the potential of cutting-edge innovations. Ten years ago, suggesting an Agile approach to project management at a pharmaceutical company of any appreciable size could have gotten you laughed out of the building. Now, all you hear is talk of scrums and sprints. This willingness to embrace an iterative, fast-paced process has opened the door for many other approaches to deriving value from institutional data, spurred on by technological advances.
Technological changes to informatics systems
One major recent change that affects how instruments and systems are integrated with a LIMS has to do with the software. The advent of cloud-based LIMS, the proliferation of extract–transform–load (ETL) tools, and the growth of generative artificial intelligence (AI) have greatly changed the landscape when it comes to integrations. Not only are there more ways to achieve integration, but the range of instruments and systems with which it is possible to integrate LIMS has also increased. So, why are instrument integrations still the red-headed stepchild of informatics projects? There are several common reasons why organizations delay or avoid interfacing, despite the clear benefits.
Excuses for why LIMS interfaces are put off
When it comes to not integrating instruments and systems with LIMS, everyone’s got their favorite excuse.
We ran out of time!
One of the main rationalizations we hear when organizations are asked why they did not interface any instruments or other lab data systems to the LIMS is that they were going to, but they ran out of time or budget. You see, these organizations felt that the LIMS needed to be nearly fully implemented and stable before interfacing instruments or systems to the LIMS or platform could be pursued. This assertion generally comes from the IT members of the implementation team. Although the sentiment is undeniably correct that no one wants to redo work on a system in flux, the reality is that rigid adherence to this adage is unrealistic and unnecessary.
Having an almost fully implemented LIMS or platform before you begin instrument interfacing is overkill. Does every data construct within your system need to be finalized before you begin interfacing? No, not really, but the data structures and entities within the LIMS in which the data you are capturing or exchanging with the instrument or system will reside should be clearly defined and mostly stable. We say mostly stable because when you start to integrate the instrument or system with the LIMS or platform, other data elements may be needed to properly complete the interface. These additional data elements may not be obvious when you are just working on one set of data structures and will only be recognized as necessary when you are in the midst of the interface design.
We lost momentum!
Another common rationalization to explain why no interfaces were implemented in the system or platform is that the organization lost momentum. Consequently, Phase 2 of the project and the interfaces never happened. Even though interfaces to lab instruments and other lab data and enterprise systems are often critical sources of cost savings and therefore ROI, they are very often postponed or neglected.
Relegating instrument and system interfaces to Phase 2 or beyond often happens due to project phase imbalances. Unbalanced phases can occur when the project stakeholders from management (who tend to be the sponsors) prioritize meeting their needs and requirements (reports, KPIs, etc.) in Phase 1 while excluding the needs and requirements of other stakeholders. Interfaces to instruments and systems that primarily benefit the bench scientists and the other parts of the organization that use the laboratory data are not considered top priorities and, hence, get put off. Then, when Phase 1 is delivered, and the scientists and other stakeholders determine that their needs were not really addressed, the LIMS project will lose momentum, and Phase 2, with all the great instrument and system interfaces, never happens.
Instrument integrations are too difficult!
In the early days of lab automation, interfacing instruments to a LIMS was an exercise that included breakout boxes, custom wiring, custom programming, and significant effort. However, over time, new tools, capabilities, and technologies have been developed in the lab informatics space that make interfacing your LIMS or platform to lab instruments and other data and information systems an achievable, yet sometimes challenging, endeavor.
In fact, most LIMS vendors today provide several tools, subsystems, and APIs to facilitate integrating their LIMS to instruments and systems. They also offer standardized, supported interfaces for some of the most popular lab instruments and enterprise systems, such as chromatography data systems (CDS), ERP systems like SAP, and data visualization systems like Spotfire or Tableau. Interface drivers are also commercially available today, which makes interfacing most instruments much easier. So, the excuse that LIMS interfaces are too difficult to implement is no longer valid.
We couldn’t get the team on board!
Taking instruments or systems out of service for even a brief window for physically making the connection and then validating it (if needed) can be a significant roadblock in some labs. It’s important to stress that the benefits of having fully integrated systems and instruments far outweigh the temporary inconvenience. Many routine tasks will be able to be automated, which will save your team time. Data will be more secure and accurate, increasing your lab’s compliance and efficiency.
▶ Additional Reading: Why You Should Interface Your Instruments to LIMS
If you have put off interfacing your lab instruments, data systems, or other enterprise information systems to your LIMS, will you now consider doing them?
Comments