System and method for inventory sharing in laboratory management systems

Abstract

To provide a system and a method for sharing consumable inventory in a novel laboratory management system.SOLUTION: A middleware system 300 includes a middleware software component controlled by a processor, a plurality of instruments 204 and 302 operatively coupled to the middleware software component by a communications network, and a consumable item configured to be removably installed in a first selected instrument of the plurality of instruments. The first selected instrument uses the consumable item to perform tests specified by a laboratory management system, and partially depletes the consumable item. The first selected instrument is configured to update status and usage information regarding the consumable item.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] [Cross - reference to Related Applications] This application claims the benefit of priority of U.S. Provisional Patent Application No. 62 / 368,308, filed on July 29, 2016, the entire disclosure of which is incorporated herein by reference.

[0002] The present invention generally relates to systems and methods for sharing reagent inventory among multiple instruments in a laboratory.

Background Art

[0003] Laboratories use various laboratory management systems for the integration of laboratory software and instruments, the management of samples, laboratory users and standards, the control of other laboratory functions such as quality assurance (QA) and quality control (QC), the execution of sample planning, invoicing and plate management, and the management of workflows. Laboratory management systems can include various different types of systems for managing samples, information and / or instruments within a laboratory, such as laboratory information systems (LIS), process development execution systems (PDES), and laboratory information management systems or laboratory integrated management solutions (LIMS).

[0004] A laboratory information system ( "LIS") is a group of software that receives, processes, and stores information generated by medical laboratory processes. LIS systems often have to interact with instruments and other information systems such as hospital information systems (HIS). A process development execution system (PDES) is a system used by companies to conduct development activities for manufacturing processes.

[0005] A Laboratory Information Management System (LIMS), or Laboratory Integrated Management Solution (LIMS), is a software system used in laboratories for integrating laboratory software and equipment, managing samples, laboratory users and standards, other laboratory functions such as quality assurance (QA) and quality control (QC), sample planning, invoice creation, plate management, and workflow automation. LIMS systems can also support information gathering, decision-making, calculation, reconsideration, and returning to the work area away from the laboratory. Recently, LIMS systems have begun to extend to electronic lab notebooks, assay data management, data mining, and data analysis.

[0006] Laboratory equipment is used to process and analyze blood or tissue samples using reagents. Reagents, also called stock, can take the form of containers, vials, and reagent packs. Reagents can require a considerable capital investment and are subject to shelf-life constraints (expiration dates), and once opened for use, they are subject to significantly shorter shelf-life constraints than unopened reagent packs.

[0007] Each reagent or reagent pack is configured to provide reagents for a set number of tests or assays. When a reagent pack is attached to an instrument, the instrument identifies the reagent pack and tracks and stores the status information associated with it. Typically, the instrument performs calibration and quality control tests on newly attached reagent packs. Based on the status information, the instrument tracks the total number of tests the reagent pack can provide, the number of tests used, the number of tests remaining, and various expiration dates.

[0008] However, this information only corresponds to a specific reagent pack identified by the specific instrument to which the reagent pack was attached. Therefore, when a specific reagent pack is attached to an instrument and then removed, the instrument should continue to identify only the previously attached specific reagent pack and perform further tests. In known systems, a specific reagent pack only functions on one instrument at a time.

[0009] Specifically, if a reagent pack is removed from an instrument and then reattached to the same instrument, the instrument will identify the reagent pack, for example by reading a barcode label or RFID (radio frequency identification) tag, and accurately track the remaining amount of reagent pack to be used or the number of tests it can perform. [Overview of the Initiative] [Problems that the invention aims to solve]

[0010] However, changes in the state of the reagent pack, such as whether it has been used or has a remaining number of tests and its shelf life, are not stored or memorized by returning them to the reagent pack's packaging or central location. The reagent pack itself does not have active memory. Such information is only stored locally in the specific instrument associated with that particular reagent pack. Currently, there is a one-to-one relationship between a specific instrument and its corresponding reagent pack. Therefore, if a partially used reagent pack is attached to a different instrument, this new instrument will not recognize that the reagent pack is partially used and will treat it as a new reagent pack, even if it is partially depleted. As a result, the reagent pack may run out and an error may occur after performing significantly fewer tests than expected.

[0011] Known instrument and laboratory information systems do not share reagent pack history between instruments or with a central database. Rather, the history of such reagent packs is limited to a single instrument based on the barcode identifier (or other identifier) ​​corresponding to that reagent pack.

[0012] Therefore, when using reagent packs in multiple instruments, it is desirable to provide instruments with accessible status and tracking information regarding those reagent packs. Since certain tests using specific reagents are likely to be performed infrequently, the ability of instruments to "share" reagent packs enhances the efficiency and flexibility of the instruments and the laboratory environment. If such a reagent pack can be removed from a first instrument and used in a second instrument in the future, the first instrument can then perform other tests using different reagent packs. In one embodiment, if an infrequently performed test is planned to be performed again, a partially used reagent pack can be collected and possibly reused in a different instrument. [Means for solving the problem]

[0013] In one embodiment, a system for sharing consumable inventory in a laboratory management system includes a middleware software component controlled by a processor, a plurality of instruments operably coupled to the middleware software component by a communication network, and consumables configured to be detachably attached to a first selected instrument among the plurality of instruments. The first selected instrument can use the consumables to partially deplete them by performing tests specified by the laboratory management system. The first selected instrument can be configured to update status and usage information about the consumables. A consumable database is operably coupled to the middleware software component, and the processor is configured to store the updated status and usage information in the consumable database corresponding to the consumables. Since the consumable database is accessible to multiple instruments, a second selected instrument among these multiple instruments can use the consumables to perform tests based on the corresponding updated status and usage information retrieved from the consumable database.

[0014] The ability to share reagent inventory across multiple instruments in a laboratory increases efficiency and reduces costs. In known systems, reagents or reagent packs must be used on only one instrument. This is partly due to the limitations of known commercially available industry-standard laboratory software systems. In such known systems, if a small number of tests are performed and no further tests of this type are required before the expiration date of the reagent pack, the remaining reagents go unused and expire. This is very costly and inefficient. According to one embodiment, reagents can be shared across multiple instruments, allowing certain types of tests to be performed on different instruments, even in small quantities. Furthermore, if one instrument malfunctions during the execution of one type of test, the reagent pack can be removed from the malfunctioning instrument and attached to another similar or identical instrument to continue the test. Inventory sharing allows for the sharing of reagents, calibrations, and control materials across instrument modules while maintaining usage and stability data.

[0015] The scope of this invention is defined solely by the appended claims and is not influenced by the statements in this summary.

[0016] The present invention can be further understood by referring to the following drawings and description. The elements in the drawings are not necessarily to scale, and the emphasis is rather on illustrating the principles of the present invention. [Brief explanation of the drawing]

[0017] [Figure 1] This is a block diagram of an exemplary computer system according to one embodiment of the present invention. [Figure 2] This is a diagram of a laboratory in which instruments are connected to a computer running a laboratory management system, according to one embodiment. [Figure 3] A block diagram showing a reagent sharing module coupled to a LIS according to one embodiment. [Figure 4] This is a block diagram of a configuration according to one embodiment. [Figure 5]This is a block diagram of a configuration according to one embodiment. [Figure 6] This figure shows an overview of an inventory sharing configuration according to one embodiment. [Modes for carrying out the invention]

[0018] The present invention generates an instrument information representation in response to receiving information generated by an instrument, and can display this instrument information representation on a display. Users of the laboratory management system can quickly and visually check the status of the instruments and confirm graphically presented information that shows the QC results of a specific instrument in detail.

[0019] In the following description, unless otherwise indicated, the subject matter of this application will be described with reference to operations and symbolic arithmetic representations performed by one or more computers. Thus, such operations and arithmetic, sometimes referred to as computer-executed, will be understood to include the manipulation of electrical signals representing data in a structured form by the processing units of a computer. This manipulation transforms or maintains data in locations within the computer's storage that reconfigure or otherwise alter the computer's operation in a manner well understood by those skilled in the art. The data structure of the location where the data is maintained is a physical location in memory having specific characteristics defined by the format of the data. However, since those skilled in the art will understand that some of the operations and arithmetic described below can also be implemented in hardware, software and / or firmware, and / or a combination thereof, the subject matter of this application is not intended to be limiting, even when described in the above context.

[0020] Figure 1 shows an exemplary computer system implementing an embodiment. Figure 1 includes a computer 100 that executes a computer program 150, such as a laboratory management system (LMS) software application 400. The LMS software application 400 includes software applications such as a laboratory information management system (LIMS) software application 401, a laboratory information system (LIS) software application 402, or a process development execution system (PDES) software application.

[0021] The LIMS software application 401 is a software application used in a laboratory for the integration of laboratory software and instruments, the management of samples, laboratory users and specifications, other laboratory functions such as quality assurance (QA) and quality control (QC), sample planning, invoicing, plate management, and workflow automation. The LIS software application 402 is a software application that receives, processes, and stores information generated by medical laboratory processes. The LIS software application 402 often has to interact with instruments and other information systems such as a hospital information system (HIS). The LIS software application 402 is a highly configurable application that is customized to facilitate various laboratory flow models. The PDES software application 403 is a software application used by companies to conduct development activities in the manufacturing process.

[0022] Computer 100 includes a processor 110 that communicates with a computer-readable storage medium 120. The computer-readable storage medium 120 is any medium that can be used to store information that the processor 110 can later access. The computer-readable storage medium 120 includes computer memory 125 and a data storage device 130. The computer memory 120 is preferably high-speed access memory and is used to execute program instructions that the processor 110 can execute. The computer memory 120 includes random access memory (RAM), flash memory, and read-only memory (ROM). The data storage device 130 is preferably a physical device and is used to store any information or computer programs that the processor 110 can access, such as an operating system 140, a computer program 150 such as an LMS software application 400, a program module 160 such as a graphics display module 410 that operates as part of the LMS software application 400, and program data 180. The data storage device 130 and its associated computer-readable storage medium store computer-readable instructions, data structures, program modules, and other data for computer 100. The data storage device 130 includes magnetic media such as floppy disks, hard disk drives, and magnetic tapes, optical media such as compact discs (CDs), digital video discs (DVDs), and Blu-ray discs, and solid memory such as random access memory (RAM), flash memory, and read-only memory (ROM).

[0023] Computer 100 further includes an input device 190 that enables data to be input into the computer 100 automatically or by a user entering commands and data. The input device 190 can include an electronic digitizer, a flatbed scanner, a barcode reader, a microphone, a camera, a video camera, a keyboard, a pointing device generally referred to as a mouse, trackball or touchpad, a pinpad, any USB device, any Bluetooth-enabled device, an RFID or NFC device, and a debit card reader. Other input devices can include a joystick, a gamepad, a satellite broadcast receiving antenna, a scanner, instruments, and sensors, etc. In one or more embodiments, the input device 190 is a portable device that can instruct the display or instantiation of an application operating on the processor 110.

[0024] These and other input devices 190 can be connected to the processor 110 via a user input interface coupled to the system bus 192, but can also be connected by other interfaces and bus structures such as a parallel port, a game port, or a Universal Serial Bus (USB). A computer such as computer 100 can also include other peripheral output devices such as speakers, printers and / or display devices that can be connected via an output peripheral interface 194, etc.

[0025] Computer 100 also includes a wireless radio 198, or other type of communication device that uses an antenna to wirelessly transmit and receive data for the computer 100. The wireless radio 198 can wirelessly transmit and receive data using WiMAX (trademark), 802.11a / b / g / n, Bluetooth (registered trademark), 2G, 2.5G, 3G and 4G wireless standards.

[0026] Computer 100 can operate within a network environment 195 using logical connections to one or more remote computers, such as remote servers 240. The remote servers 240 can be personal computers, servers, routers, network PCs, peer devices, or other common network nodes, and may include many, though not all, of the elements described above in relation to computer 100. Network environments are commonplace in offices, enterprise-scale computer networks, intranets, and the Internet. For example, in the subject matter of this application, computer 100 may include a source machine that is the source of data transfer, and remote computers may include destination machines. However, the source and destination machines do not need to be connected by a network or other means; instead, data can be transferred via any medium that allows writing by the source platform and reading by the destination platform. When computer 100 is used in a LAN or WLAN network environment, it is connected to the LAN or WLAN via a network interface 196 or an adapter. When computer 100 is used in a WAN network environment, it may include a modem or other means such as a radio 198 that establishes communication over the WAN with an environment such as the Internet or another remote computer. It will be understood that other means may also be used to establish a communication link between computer 100 and other remote computers.

[0027] In one embodiment, computer 100 communicates with remote server 240, and LMS software application 400 is executed on remote server 240 to receive commands and information from computer 100 entered by the user. The information from the LMS software application 400 running on remote server 240 is displayed on a display connected to computer 100.

[0028] Referring to Figures 1 and 2, a graphic display module 410 is provided that graphically generates an instrument information representation 220 in response to receiving information 212 generated by one or more instruments 204. The graphic display module 410 is connected to, or operates within, a laboratory management system (LMS) software application 400 used to manage the laboratory 200. The laboratory 200 is any place of manufacture or analysis in which equipment or instruments 204 are used to act on or test a sample 206. The laboratory 200 includes various types of laboratories, such as medical or clinical laboratories, biological laboratories, chemical laboratories, chemical or petroleum laboratories, commercial or manufacturing plants, forensic or criminal laboratories, pathology laboratories, public safety and public health laboratories, water treatment and water testing facilities, etc. The sample 202 is any object that enters the laboratory 200 to act on or test. Sample 202 includes biological samples taken from patients such as blood, urine, or tissue; evidence samples taken from crime scenes such as bullets, biological samples, photographs, and videos; material, liquid, or compound samples; and tissue or component. Apparatus 204 is any type of equipment capable of acting on, analyzing, or testing Sample 206, and includes laboratory equipment, manufacturing equipment such as welding tools and robotic arms, sensors such as temperature sensors and weight sensors, and imaging devices such as barcode scanners or cameras.

[0029] Once the instrument becomes operational and the sample 206 enters or leaves the laboratory 200, the instrument 204 can generate information 212 and send it to the LMS software application 400. The information 212 may include status information 214 detailing the status of the instrument 204, including any error messages received from the instrument 204 and any information regarding the instrument 204's current operating status; instrument information, including information representing the instrument such as its type and model number; the current workload of the instrument 204, including how many jobs can be packed into the instrument 204's queue; QC information 216 generated by the instrument 204 for quality control (QC) samples; and result information 218. An instrument information representation 220 as described herein can display the real-time QC status of each assay performed on the instrument 204. If any assay fails, one of the QC rules defined in the LMS software application 400, such as the Westgard rule, custom rule, or moving average rule, is applied to the QC information 216 and displayed by the instrument information representation 220, allowing the user to receive a warning about the malfunction of the instrument 204 and view the QC information 216 in real time on the display.

[0030] When a sample 206 is sent to a specific instrument 204 in the laboratory 200, a test or action is performed on the sample 206, and the instrument 204 can generate result information 218 related to the sample 206 and transmit it to the LMS software application 400. The result information 218 is generated by the instrument 204 in the laboratory 200 and is related to, or obtained by, the test or action performed on the sample 206, and includes the status as a test result or sample characteristic, and any other information that the instrument 204 can obtain from the sample 206 that may be related to the sample 206. Finally, the result information 218 is entered into a database managed by the LMS software application 400.

[0031] Figure 3 is a block diagram showing a middleware system 300 that can be operably coupled to the LIS402. Alternatively, the middleware system 300 can be integrated into the LIS402. Such a middleware system or application 300 can be the AMS platform (also known as the AlinIQ AMS system) available from Abbott Laboratories. The middleware system 300 can be coupled to the laboratory instrument 204 via various communication protocols such as HL7 (Health Level Seven) and ASTM (American Society on the International Associate for Testing and Materials). These protocols are industry standard protocols, and most, though not all, of the laboratory instruments 204 can communicate using these protocols. The middleware system 300 may include an HL7 or ASTM interface adapted to communicate with instruments that have HL7 or ASTM capabilities. The middleware system 300 can be a software component that interacts with and communicates with the instrument, sending and receiving data, commands, and status, etc.

[0032] The devices may also include devices having non-industry standard interfaces or proprietary standard interfaces that can be operably coupled to the intelligent interface module 304 of the middleware system 300, such as one or more of the intelligent devices 302 shown in Figure 3. The intelligent interface module 304 may be part of the middleware system 300, incorporated into the middleware system 300, or operably coupled to the middleware system 300 remotely. The intelligent devices 302 may also include known industry standard interfaces such as HL7 and ASTM as described above.

[0033] The middleware system 300 may include a manual test results viewer 306, an automatic verification module 308, a laboratory viewer 310, a quality control module 312, an equipment maintenance module 314, and a monitoring module 316. The laboratory viewer 310 can be used to view the specific operation and results of various connected instruments 204, 302.

[0034] The intelligent instrument 302 coupled to the intelligent interface module 304 provides the ability to share reagents or stock among various intelligent instruments 302. As mentioned above, such reagent sharing is not possible using standard instruments 204 with standard HL7 and ASTM interfaces. The intelligent interface module 304 is configured to provide a robust communication protocol that facilitates the sharing of reagents or stock among intelligent instruments 302.

[0035] The intelligent interface module 304 is operablely coupled to and can access a reagent sharing database or memory 320 (consumables database) that can reside locally or remotely. Thus, the reagent sharing database or memory 320 can be a cloud-based remote database 322. Reagent sharing allows laboratory staff to seamlessly share partially used stock (reagent packs) between intelligent instruments 302 or working cells, saving the time and cost required to maintain and track individual stocks of each instrument.

[0036] Referring to Figures 3 and 4, the intelligent interface module 304 can be operably coupled to or include the reagent sharing database 320. Furthermore, Figure 4 also shows multiple working cells 410 operably coupled to the intelligent interface module 304. Any suitable number of working cells 410 can be coupled to the intelligent interface module 304 depending on the application and test environment. Each working cell 410 can be a cluster of intelligent instruments 302. Typically, a working cell 410 contains one to four intelligent instruments 302, but other configurations are possible. Intelligent instruments 302 can be clustered together as the application allows, but clusters of more than four instruments may not provide the same efficiency benefits.

[0037] The intelligent devices 302 can be clustered together within a work cell 410 to enhance efficiency and throughput, and each work cell may contain similar or identical types of intelligent devices 302, or different types or models of intelligent devices 302. The intelligent interface module 304 in Figure 4 demonstrates the flexibility of the intelligent interface module 304, and in some embodiments, it may also include other software applications such as a daily planner, an operational dashboard 432, and an assay viewer 434, which are referred to as PlanMyDay 430 in the figure.

[0038] Figure 5 shows a specific data flow related to the intelligent interface module 304. One or more working cells 410 operably coupled to the intelligent interface module 304 communicate inventory data 510 to the intelligent interface module 304. Such information is stored and updated in the inventory or reagent sharing database 320. Because industry standard communication protocols such as HL7 and ASTM are not robust enough to provide, receive, or track such reagent information, such communication is handled through a dedicated protocol. Existing known protocols such as HL7 and ASTM cannot support reagent sharing information.

[0039] As described above, the intelligent interface module can communicate with the intelligent instrument 302 via a custom communication protocol that transmits reagent information, distinct from the industry-standard protocols used by the HL7 or ASTM network. This custom protocol is not compatible with the HL7 and ASTM protocols, and is therefore far more robust and flexible. The HL7 and ASTM protocols are inherently limited because they are intended to be general-purpose and are compatible with virtually all instruments 204 connected to the LIS. The HL7 and ASTM protocols are inherently inflexible because they are designed for broad compatibility and support a very limited set of datasets.

[0040] For example, existing HL7 and ASTM protocols in middleware-coupled-to-middleware systems do not support reporting of reagent status and usage information that changes dynamically during instrument handling. Status and reagent usage information may include, among many other pieces of information, 1) the identity of the consumable, 2) the total number of tests corresponding to the consumable, 3) the number of tests remaining for the consumable, 4) the shelf life of the consumable, 5) the remaining life after the initial opening of the consumable, 6) quality control information for the consumable, and 7) calibration information for the consumable.

[0041] Typically, the identity of a consumable or reagent container can be obtained by an intelligent instrument scanning a barcode label attached to the reagent container during loading. Alternatively, the reagent container may include an RFID tag indicating the identity of the consumable.

[0042] Each consumable can inherently contain a certain number of tests it can support before depletion. The intelligent interface module 304, which communicates with each intelligent instrument 302, tracks all such relevant information. For example, when a consumable is first loaded into an intelligent instrument 302 and its identity is first determined, the maximum number of tests before depletion is retrieved from this consumable and updated in the consumable database 320. As various tests are performed using this consumable, the number of tests performed (corresponding to the amount of reagent used) is tracked and the consumable database 320 is updated. In one example, a consumable can be used until depletion causes a pending notification that the consumable is out of stock to interrupt the test. In another example, even if a test using that consumable is interrupted or completed, the consumable is not yet depleted and can be used at a later time. Therefore, the number of tests used corresponding to the identity of that consumable is recorded so that it can be used in subsequent tests, possibly in a different intelligent instrument 302. Thus, the total number of tests or maximum number of tests, and the remaining number of tests, corresponding to that consumable are recorded.

[0043] The consumable database 320, corresponding to each identified consumable, also stores lifespan information. This information includes the maximum shelf life of the reagent, such as 24 months, and the expected post-opening shelf life, which is a value less than the maximum shelf life. For example, if a consumable is used in a first instrument and then stored, and later reattached to a second instrument, the lifespan information is retrieved from the consumable database 320 to verify that the post-opening shelf life has not been exceeded. If it has, the consumable is considered old and its use is not permitted.

[0044] Regarding the date / time lifetime values, these values ​​can be in JSON format and compliant with ISO 8601. These date and time values ​​are generated when the item is created and installed, based on the lot expiration date of the specific reagent.

[0045] The status and reagent usage information described above in known systems cannot be stored or retrieved outside the instrument performing the test due to the limitations of existing protocols such as HL7 and ASTM, which do not support or cannot support such information transfer. On the other hand, the custom protocol used by the intelligent interface module 304 is designed to support the transfer of such reagent usage and status information, and thus such information is stored in a central repository such as the reagent sharing or consumables database 320. Since the intelligent interface module 304 can access the reagent sharing database 320, it can retrieve or supply such data to or from any intelligent instrument 302 to which the middleware system 300 is coupled. This enables the sharing or transfer of reagent packs among such intelligent instruments 302.

[0046] For example, a consumable such as a reagent pack can be detachably attached to a selected first intelligent instrument 302 from among several intelligent instruments that can be located within the same or different working cells 410. The selected first intelligent instrument 302 can perform a test specified by the LIS using this reagent pack. The selected intelligent instrument 302 can update the status and usage information of the reagent pack. This update can be performed in real time or near real time. Periodic updates can be performed at a high frequency, such as several times per second. When the intelligent instrument 302 performs a specified test, the intelligent interface module 304 can retrieve and store the latest status and usage information in the reagent sharing database 320 corresponding to the reagent pack.

[0047] For various reasons, it may be desirable to remove a reagent pack from a particular intelligent instrument 302, regardless of whether the reagent pack is completely depleted or not. In one example, all requested tests using a particular reagent pack may be completed even if the reagent pack is only partially consumed. Alternatively, a malfunction of the instrument may necessitate taking the currently operating intelligent instrument 302 offline. Since all intelligent instruments 302 can access the reagent sharing database 320 via the intelligent interface module 304, if continuous testing is to be performed using the removed reagent pack, the partially consumed reagent pack described in the above example can be removed from the first intelligent instrument 302 and attached to the selected second intelligent instrument 302.

[0048] The latest status and usage information regarding a partially depleted reagent pack can be retrieved from the reagent sharing database 320 and provided to a second selected intelligent instrument 302 to which the partially depleted reagent pack is attached. The selected second intelligent instrument 302 can then continue performing the test using the partially depleted reagent pack removed from the first intelligent instrument 302. In this way, reagent packs are used in the most efficient and economical manner, minimizing waste.

[0049] In some embodiments, when a partially depleted reagent pack is removed from the first intelligent instrument 302 and attached to the second intelligent instrument 302, the second intelligent instrument 302 can perform QC and calibration corresponding to the partially depleted reagent pack. This is especially true if the second intelligent instrument 302 has not previously had a partially depleted reagent pack attached to it. The reagent sharing database 302 can store QC, calibration, and status information for each intelligent instrument 302 to which a specific reagent pack is attached.

[0050] Stock or reagent sharing enables the sharing of stock items across multiple instruments. The intelligent interface module 304 supports portability by centrally tracking and updating status information about consumed stock items in the reagent sharing database 320, which each intelligent instrument 302 accesses to obtain the latest status of its stock items.

[0051] Reagent inventory sharing involves stock items such as reagent packs and calibration / control materials that can be loaded into intelligent instruments 302 within the work cell 410. Ownership of these stock items is registered in the work cell 410 within the reagent sharing database 320. When an item is removed, the stock item information in the intelligent interface module 304 can be updated with usage information (e.g., number of tests). When an item is loaded into another work cell 410, the work cell retrieves the latest usage / stability information from the intelligent interface module 304 before proceeding with the item's consumption. This also provides a mechanism for asynchronous inventory updates and adjustments in case of temporary errors or offline states. The same intelligent interface module 304 can support multiple types of instruments within the laboratory.

[0052] The reagent sharing database 320 can be a passive database that does not recognize the type or example of the connected intelligent instrument 302. It is preferable that the work cell 410 be responsible for ensuring the unique identity of each stock item so that sharing is limited to "similar" types.

[0053] Referring to Figures 4-6, the communication format between the work cell 410 and the intelligent interface module 304 can use an HTTP-based scheme known as Representational State Transfer (REST). The server can expose a Secure Hypertext Transfer Protocol (HTTPS) endpoint to support inventory sharing services. The payload to be sent can be represented in the form of Javascript® Object Notation (JSON) data. The work cell hosts components specifically designed to mediate communication with its remote service endpoints. These components are used by other components to meet business requirements as needed.

[0054] Figure 6 shows another embodiment of the intelligent interface module in the inventory configuration. The intelligent interface module 304 may include an inventory sharing service 610 and a remote inventory sharing service 620. The inventory sharing service 610 can be operably coupled to an inventory sharing configuration provider 624, a data logger 626, a service control center (SCC) function module 630, and a reconciliation queue provider 632. The remote inventory sharing service 620 can be coupled to a JSON serialization interface 640, a REST client factory interface 642, and a REST client module 644.

[0055] The remote inventory sharing service 620 enables seamless interface and remote sharing between the remote service components of the intelligent interface module 304. The service control center (SCC) function module 630 is essentially a computer involved in data processing in a specific work cell 410.

[0056] The adjustment queue provider 632 manages the queue for shared requests. The inventory sharing service 610 persists the inventory information adjustment requests in the queue, where each item in the queue represents an item that needs adjustment, and this queue is persistent. The embodiments described herein do not assume a specific persistence technology, but rather allow consumer applications to satisfy this as interface-dependent.

[0057] The JSON serialization interface 640 provides serialization / deserialization functionality for converting inventory information to and from Javascript Object Notation (JSON) representations used in the communication protocol. The REST client factory interface 642 handles communication with the work cell 410 using the Representational State Transfer (REST) ​​scheme over a secure hypertext transfer protocol (HTTPS). The inventory sharing components described herein can rely on REST client behavior specifically for establishing communication. The REST client factory interface 642 constructs and supplies REST client objects to the inventory sharing service 610.

[0058] In some embodiments, the terms “reagent” or “reagent sharing” may not necessarily be limited to actual reagent chemicals but may be more general in nature and may include any consumables used within a laboratory apparatus, such as reagents, calibrators, control groups, or other consumable stocks.

[0059] In one embodiment, the intelligent interface module 304 can be integrated with the LIMS. In another embodiment, the intelligent interface module 304 can be separated from the LIMS. In yet another embodiment, the intelligent interface module 304 is located within a hospital or laboratory computer system. In yet another embodiment, the intelligent interface module 304 can be distributed across multiple instrument computer control systems. In this way, a particular intelligent instrument 302 having a database that tracks reagent information used in its own instrument can broadcast updates to its database to other instruments on the same communication network. Each instrument that subscribes to the broadcasted updates can update its database that tracks its reagent information. Thus, reagent usage information is "shared" among different instruments.

[0060] Furthermore, in some embodiments, a centralized reagent sharing database may be unnecessary. To replace the central reagent sharing database 320, a publish / subscribe technique can be used to share reagent or other inventory information among multiple instruments. In such specific embodiments, each intelligent instrument 302 can locally store reagent information for all inventory items. When the status of an inventory item changes, the corresponding intelligent instrument 302 broadcasts that status change over the network. Other intelligent instruments 302 are configured to listen to these messages, receive and process each message when it is broadcast, and update their corresponding local reagent sharing databases accordingly. In this way, all intelligent instruments 302 store and maintain reagent / status information for all other instruments.

[0061] In other embodiments, the need for a centralized consumables database 320 can be eliminated by using a point-to-point method. In such embodiments, each intelligent device 302 is configured to have the IP addresses of all other related intelligent devices 302 on the network, and each intelligent device 302 can directly send message update / status information to all other devices specified in its list.

[0062] Those skilled in the art will recognize that cutting-edge technology has advanced to the point where there is little distinction between implementing a system in hardware or software, and that the use of hardware or software is generally a design choice representing a trade-off between cost and efficiency (though not always, as the choice between hardware and software can be important in some contexts). Those skilled in the art will understand that there are various means (e.g., hardware, software, and / or firmware) that can achieve the processes and / or systems and / or other technologies described herein, and that the preferred means among these depends on the context in which the processes and / or systems and / or other technologies are deployed. For example, an implementer may choose primarily hardware and / or firmware means if speed and accuracy are the top priorities, or primarily software implementation if flexibility is the top priority, or a combination of hardware, software, and / or firmware. Therefore, there are multiple means by which the processes and / or apparatus and / or other techniques described herein can be achieved, and the means used may differ, each being a choice that depends on the context in which they are deployed and the specific concerns of the implementer (e.g., speed, flexibility, or predictability), so that no means is inherently superior to others. Those skilled in the art will recognize that optical implementations generally involve the use of optically oriented hardware, software, and / or firmware.

[0063] The detailed description above illustrates various embodiments of the apparatus and / or process through block diagrams, flowcharts and / or examples. Those skilled in the art will understand that, where such block diagrams, flowcharts and / or examples include one or more functions and / or operations, each function and / or operation in such block diagrams, flowcharts and / or examples can be implemented individually and / or collectively by a wide range of hardware, software, firmware or substantially all combinations thereof. In one embodiment, several parts of the subject matter described herein can be implemented by application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs) or other integrated formats.

[0064] However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein can be equivalently implemented in whole or in part within an integrated circuit as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or substantially all combinations thereof, and that designing the circuits and / or writing the software and / or firmware code falls well within the scope of the art in light of this disclosure. Furthermore, those skilled in the art will understand that the mechanisms of the subject matter described herein can be distributed as various forms of program products, and that the exemplary embodiments of the subject matter described herein are applicable regardless of the specific type of signaling medium used for actual distribution. Examples of signal transmission media include, but are not limited to, magnetic media such as floppy disks, hard disk drives, and magnetic tapes; optical media such as compact discs (CDs), digital multipurpose discs (DVDs), and Blu-ray® discs; computer-readable storage media such as random access memory (RAM), flash memory, and read-only memory (ROM); and transmission media such as digital and / or analog communication media such as fiber optic cables, waveguides, wired communication links, and wireless communication links.

[0065] The subjects described herein may sometimes show different components that are included in or connected to other different components. The architectures shown in this manner are merely illustrative, and it should be understood that many other architectures can be implemented to achieve the same functionality. Conceptually, any configuration of components that achieve the same functionality is effectively “related” to each other in such a way that the desired functionality is achieved. Therefore, any two components in this specification that combine to achieve a particular functionality can be considered to be “related” or “connected” to each other, regardless of the architecture or intervening components, in such a way that the desired functionality is achieved. Similarly, any two such related components can be considered to be “operably connected” or “operably coupled” to each other in such a way that the desired functionality is achieved, and any two components that can be related in such a way can be considered to be “operably coupled” to each other in such a way that the desired functionality is achieved. Specific examples of operatably coupled components include, but are not limited to, physically coupled and / or physically interacting components, and / or wirelessly interacting and / or wirelessly interacting components, and / or logically interacting and / or logically interacting components.

[0066] While specific aspects of the subject matter described herein have been illustrated and illustrated, it will be clear to those skilled in the art that modifications and alterations can be made based on the teachings herein without departing from the subject matter and its broader aspects described herein, and that the appended claims also include all such modifications and alterations that fall within the true spirit and scope of the subject matter described herein. Furthermore, it should be understood that the present invention is defined by the appended claims. Accordingly, the present invention should not be limited by any means other than in reference to the appended claims and their equivalents. [Explanation of Symbols]

[0067] 204 Third Party Instrument 204 Instruments 300 Middleware Systems 302 Intelligent Devices 304 Intelligent Interface Module 306 Manual Test Results Review 308 Automated Verification 310 Laboratory Viewer 312 Quality Control 314 Equipment Maintenance 316 Monitoring 320 Reagent Sharing Database 320 Database 322 Cloud 402 LIS

Claims

1. Consumables database and A processor circuit that communicates with the consumables database and the first experimental apparatus, A system comprising, the processor circuit, Access the equipment status information relating to the first experimental equipment from the first experimental equipment via the first communication protocol. Consumable information relating to consumables from the first experimental apparatus is accessed via a second communication protocol different from the first communication protocol, wherein the first communication protocol includes the HL7 communication protocol or the ASTM communication protocol, and the second communication protocol is different from the HL7 communication protocol and the ASTM communication protocol. Instead of storing the equipment status information, the consumable information is stored in the consumable database corresponding to the consumable. A system characterized by the following features.

2. The instrument status information includes one or more of the following: the operating status of the first experimental instrument, the workload of the first experimental instrument, quality control information generated by the first experimental instrument for a sample processed by the first experimental instrument, or the sample analysis results generated by the first experimental instrument. The system according to claim 1.

3. The consumable information includes one or more of the following: the number of tests performed using the first laboratory equipment with the consumable; the number of remaining tests to be performed using the first laboratory equipment or other laboratory equipment with the consumable; the expiration date data of the consumable; the quality control information of the consumable; or the calibration information of the consumable. The system according to claim 1.

4. The consumable information includes (a) first consumable information relating to the first test, corresponding to the number of tests conducted before the depletion of the consumable, and (a) second consumable information relating to the second test after the first test, corresponding to the number of tests conducted before the depletion of the consumable, and the test can be performed using the first laboratory apparatus or other laboratory apparatus. The system according to claim 1.

5. The processor circuit updates the first consumable information in the consumable database based on the second consumable information. The system according to claim 4.

6. The processor circuit updates the consumable information in the consumable database in response to an instruction that the consumable has been removed from the first experimental apparatus. The system according to claim 1.

7. The first database and A second database, different from the first database mentioned above, The first experimental apparatus, The second experimental apparatus, The first apparatus is equipped with, The consumables received in the first experimental apparatus are identified, The first consumable information of the consumable is retrieved from the first database via the first communication protocol. The instrument status information of the first experimental apparatus is transmitted to the second database via a second communication protocol different from the first communication protocol, the second communication protocol includes the HL7 communication protocol or the ASTM communication protocol, and the first communication protocol is different from the HL7 communication protocol and the ASTM communication protocol. After the consumable has been partially used by the first experimental apparatus and a partially used consumable has been generated, second consumable information of the partially used consumable is transmitted to the first database via the first communication protocol, The second experimental apparatus is, The partially used consumables received in the second experimental apparatus are identified, Before the partially used consumable is used by the second experimental apparatus, the second consumable information is retrieved from the first database via the first communication protocol. A system characterized by the following features.

8. The first consumable information includes the remaining number of first tests to be used with the consumable, and the second consumable information includes the remaining number of second tests to be used with the partially used consumable, and the tests for the first and second tests can be performed using the first or second laboratory equipment. The system according to claim 7.

9. The number of the first test is the number of remaining tests to be used with the consumable, The system according to claim 8.

10. The second experimental apparatus transmits the apparatus status information of the second experimental apparatus to the second database via the second communication protocol. The system according to claim 7.

11. The second experimental apparatus transmits third consumable information of the partially used consumable to the first database via the first communication protocol, and after the partially used consumable has been used by the second experimental apparatus. The system according to claim 7.

12. The first experimental apparatus is a first type of experimental apparatus, and the second experimental apparatus is a second type of experimental apparatus that is different from the first type. The system according to claim 7.

13. The aforementioned consumables include reagents. The system according to any one of claims 7 to 12.

14. At least one memory containing a machine-readable instruction, wherein the machine-readable instruction, at least, Access the first consumable information of the reagent from the first experimental apparatus via the first communication protocol. The first consumable information of the reagent is stored in the consumable database. Access to the instrument status information from the first experimental apparatus is provided via a second communication protocol different from the first communication protocol, the second communication protocol includes the HL7 communication protocol or the ASTM communication protocol, and the first communication protocol is different from the HL7 communication protocol and the ASTM communication protocol. The equipment status information of the first experimental equipment is stored in the equipment status database. Access to second consumable information received from a second experimental apparatus different from the first experimental apparatus via the first communication protocol, Based on the second consumable information of the reagent, the first consumable information of the reagent stored in the consumable database is updated to generate third consumable information. The processor circuit is made to do this. A memory characterized by the following:

15. The machine-readable instruction causes the processor circuit to transmit the first consumable information to the second laboratory via the first communication protocol in response to a request from the second laboratory that indicates the reagent has been received by the second laboratory. The at least one memory according to claim 14.

16. The machine-readable instruction causes the processor circuit to update the third consumable information based on the fourth consumable information of the reagent, which is received from the second laboratory equipment after the second consumable information. The at least one memory according to claim 14.

17. The first consumable information includes the number of first tests related to the reagent, and the second consumable information includes the number of second tests related to the reagent. At least one memory according to claim 14 or 15.

18. The aforementioned equipment status information includes one or more of the following: the operating state of the first experimental equipment, the workload of the first experimental equipment, or the test results generated by the first experimental equipment. The at least one memory according to claim 14.

Images