What is an ilab? 1. No Real-Time Control of Users: 2. Limited Management of Workflow:

Transcription

1 ilab, an acronym for integrated laboratory, is a term that describes a new type of laboratory informatics system - a total laboratory automation system. Understanding the value of an ilab starts with an understanding of 4 key problems with today s informatics systems. 1. No Real-Time Control of Users: On a daily basis analysts are required to follow SOPs, but there is no way to enforce the SOP. For example, an analyst is expected to check that a reagent is suitable for the test that they are doing, but there is nothing in the system that ensures that the check is made. It is left up to the analyst to check SOP requirements and make decisions about each step in the process. Analysts are being asked to make far too many decisions about the processes they are completing. 2. Limited Management of Workflow: To illustrate this point, ask yourself the following question, How does my informatics system adjust itself when an instrument breaks down at 2:00 pm? What should your system be able to do in this case? It should check to see if a different instrument can be used for the same tests. If the other instrument is already booked, then it needs to reassign samples so that the high priority samples are analyzed first. It might need to reschedule the work for someone, so that the repair of the instrument is a priority. The system may need to notify others outside of the lab that the test results will be delayed. All of these decisions should be automatic, and they need to take into account all of the available information about the lab and its resources. Today s informatics systems are not close to providing real management of workflow.

2 3. Most processes are human driven or paper driven, not Event-Driven: As long as a process is paper-based, it is human driven, not Event-Driven. People are expected to make too many decisions - approving results, prioritizing work and making sure they are following procedures. A totally automated system will have almost all decisions made by the system. The system will check and ensure that the correct processes are being followed the same way, all of the time. These decisions will be based on events that take place. An event can be any action. It could be something that an analyst does, like select an instrument from a list or it could be an action that the system takes, like checking training records. 4. Limited integration of information: Anyone who is working with more than one software system in their lab will recognize this problem - the lack of integration between software systems and between instruments and software systems. With proper integration, you gain two very valuable benefits: a) Information is only stored in one place b) Information is instantly available when and where it is needed. When you look at these four key issues, you soon realize that they add up to No Automated Workflow Control. If users are not removed from the decision making process and systems are not integrated, you cannot have automated workflow control. What does an ilab look like? An ilab system that solves all of the above problems can be visualized as follows: Figure 1: In the ilab, applications are connected through the Real-Time Integration layer. Workflow Control automates workflow decisions by applying business rules to information from all applications. At the bottom of the diagram you have the main laboratory application systems LIMS, ELN, Instrument software, etc. Each of these operates on their own and carries out very specific functions for the laboratory. Each application is connected to all of the other applications through the Real-Time Integration layer, not directly to each other. Page 2 of 5

3 This is critical in the design of the system to keep the number of integration points to a minimum. Any information in any of the applications is available to all of the other applications, when and where it is required. If ELN needs information about the calibration of an instrument, it gets it from the calibration application through the Real-Time Integration layer. Above the Real-Time Integration layer is the Workflow Control layer. This layer takes information from all applications and applies business rules to maximize the correct Workflows. If an instrument breaks down, it is this layer that reschedules work for everyone, so that the whole lab is best able to meet its targets. Real-Time Integration and Workflow Control are very critical concepts in the ilab design. So, let s look at each of those in more detail. Real-Time Integration Real-Time Integration means that all data is available immediately, when and where it is required. Having data available immediately means that the system can perform a lot of automated checks, and it can prevent errors from occurring. It is also able to make decisions for users. Data and Events are validated immediately and automatically. Each new piece of data is evaluated, approved and stored in its correct location. Events are reviewed and approved by the system before subsequent events can be initiated. Data is stored in a single correct location. Nothing causes more problems to an automated system than trying to maintain information in more than one location. Workflow Control Each event (anything that happens) automatically initiates other events. Some of these events will require a human to complete and others will be completed automatically. Some events will affect the current schedule and, therefore, future events will be re-scheduled and reprioritized. For example, in an ilab, an event like selecting a balance will automatically initiate the following series of events: Check for calibration Check suitability of the balance for the planned work Check training records Log use of the balance into an instrument log book Retrieve calibration information Retrieve an instructional SOP In this example, the single event of selecting a balance triggered an interaction with as many as 5 other applications. Page 3 of 5

4 What is Nexxis ilab and how does it compare to the ilab described above? The following diagram illustrates Labtronics Nexxis ilab product. Nexxis ilab can provide support for each of the applications excluding ERP and instruments. For example, you can remove Nexxis SDMS and replace it with either NuGenesis (from Waters) or CyberLAB ECM (from Agilent) applications without losing functionality. Since the API design for the SDMS is the same for each of these applications, the replacement of one for another only requires a simple one screen configuration. Once configured, the Real-Time Integration layer is unaware of which SDMS is connected. Figure 2: Nexxis ilab meets all of the requirements of an ilab, but it does not include applications for instrument software or ERP. Nexxis ilab adds some additional functionality to the ilab system. Plug & Play applications The design of the connection between the application and the Real-Time integration layer is critical to the ilab s ability to support the selection of best of breed applications. Labtronics has designed a set of API standards for communication between the applications and the Integration layer. This means that the applications are interchangeable. Figure 3: Using Labtronics' API for communication, applications can be interchanged with just a simple screen configuration. Nexxis ilab s API is so generic that even popular documentation systems could be used in place of the SDMS. This Plug & Play feature is very important when adding ilab to a laboratory that already has existing informatics systems. There is no need to replace existing systems. Page 4 of 5

5 Out-of-the-Box Configuration Much of Nexxis ilab has been designed to provide you with simple configuration instead of scripting and programming custom solutions. For example, the ReDI Technology in Nexxis ELN lets you create automated worksheets with simple click and drag functionality. Connecting an ELN worksheet to instrument calibration information, training records and updating instrument log books is accomplished in a minute or two by simple configuration. Connecting to existing LIMS systems is done through standardized LIMS modules, which require only simple, one screen configurations. Delivering Results... Automatically Labtronics Inc. Tel: (519) Fax: (519) info@labtronics.com Art Rev1.2 Page 5 of 5