Patent Description:
In a typical laboratory, there currently is not an efficient way to perform overall maintenance in transportation systems in large laboratories that process test sample continuously without requiring a full laboratory stoppage.

Document <CIT> discloses a method of performing maintenance on an analyzer that include determining a maintenance operation to perform, automatically selecting a maintenance carrier to perform the maintenance operation in response to detecting an error or at a prescheduled time, and under control of a processor, automatically deploying the maintenance carrier onto a track when the affected stations are prepared and not in use when the maintenance carrier arrives.

Document <CIT> discloses a system where certain maintenance processes, such as, routine track cleanings, can be scheduled such as, for example, at the end of each shift of an operator. An operator can request when a maintenance operation occurs. The system can determine the moment when maintenance is appropriate based on current conditions with the analyzer and allows maintenance to be performed without interfering with normal sample analysis and operations of the analyzer.

Document <CIT> discloses a laboratory sample distribution system comprising a transport plane and a cleaning device for cleaning the transport plane. The cleaning device is adapted to automatically clean the transport plane in a way that is similar to the way sample container carriers move on the transport plane.

Document <CIT> discloses a method for loading specimen containers into centrifuge adapters.

Therefore, there is a need to technically prevent a complete laboratory system stoppage while providing maintenance to the laboratory analyzers and/or transportation systems while still maintaining peak performance of the laboratory system. In addition, there is also a need to ensure the proper priorization of the test sample container carrier during periods of high laboratory workloads without losing the flexibility that a laboratory middleware test sample workflow engine provides.

It is an object of the present disclosure to provide a method of routing test sample container carrier during periods of laboratory disruption in a laboratory system by masking certain laboratory analyzers and/or other target devices such that sample containers are not allowed to exit the laboratory analyzers and/or other target devices in order to create the necessary time window for performing crucial laboratory maintenance tasks.

There are several diverse reasons why it might be necessary to prevent sample test containers from exiting a retrievable device such as, for example, laboratory analyzer, buffer, and/or archival device.

One reason is to stop the laboratory system from transporting sample test containers to provide maintenance tasks such as, for example, cleaning the transportation surface of the transportation system. Additional maintenance tasks may include replacing a transportation tile or plate when a magnetic transportation system is used or replacing a belt when using a conveyor belt transportation system. Additionally, when a transportation plate is broken or damaged, it is important to ensure that no sample test containers are on or move on that broken or damaged transportation plate.

Another reason to stop the laboratory system from transporting test sample container carriers is when the laboratory system is about to finish the last shift of the day. In this case, the test sample container carriers that are not already in an archival target location should still be processed by the laboratory system but no additional test sample container carriers should be loaded into the laboratory system for processing.

Another reason to prevent test sample container carriers from exiting a retrievable device is to reduce the workload on the transportation system. For example, when a large batch of test sample container carriers with a high processing priority, e.g., STAT status, arrives at the laboratory system, the analytical devices of the laboratory system need to be available to process those high processing priority test sample container carriers first.

The present invention relates to a method of routing test sample container carriers during periods of laboratory disruption in a laboratory system, as defined in claim <NUM>, and to a laboratory system, as defined in claim <NUM>. Preferred features of the invention are set out in the dependent claims.

The advantages of the present disclosure comprise a gain in efficiency of the overall laboratory and better management of test sample flow in periods of high workloads on the laboratory transportation system and the laboratory system. Upon competition of the maintenance event (or any other event requiring the retrieval masking of a laboratory device), a recalculation of the workflow by the laboratory middleware can occur in order to efficiently restart the processing of the test samples that had remained in the laboratory device during the masking of that laboratory device.

According to the present disclosure, laboratory devices can be masked by the laboratory system so that test sample container carriers cannot be retrieved from the laboratory devices, i.e., test sample container carriers cannot leave the laboratory device. When a laboratory device is masked, the laboratory system will deem that any test sample container carriers inside the device cannot be retrieved. When a laboratory device is unmasked, the laboratory system via the laboratory middleware will recalculate the test sample workflow. This means the laboratory system will determine which test samples in the test sample container carriers in the previously masked laboratory device need to have further processing and will request that those test sample container carriers be retrieved for further processing.

The laboratory system can mask and unmask specific laboratory devices in the plurality of laboratory devices connect to or integrated with the transportation system. By that, it can be possible to continue retrieving and processing test sample container carriers on the non-effected portions of the transportation system.

The retrieval masking of certain laboratory devices can be limited to a specific subset of test sample container carriers. For example,.

In addition, retrieval masking can also be applied to specific test sample container carriers at a specific laboratory device. For example, test sample container carriers for which a specific test result was received that had recently visited a laboratory analyzer or that needs to be cooled down for a certain time may not be retrieved from an archival laboratory device.

Retrieval masking of a laboratory device can be enabled/disabled automatically via laboratory configuration rules of the laboratory middleware that can be triggered by internal or external events. Internal triggers can be, for example, a daily maintenance job schedule; daily peak workload time is approaching/ending; daily end of normal business time or the daily beginning of normal business is approaching; an unusually high/low number of new incoming test sample container carriers is registered; and the like. External triggers can be, for example, laboratory instrument or module status messages from the laboratory middleware reporting the availability/unavailability of certain laboratory instruments or modules.

Alternatively, the retrieval masking of a laboratory device can be enabled/disabled manually through a laboratory operator interface with the laboratory middleware of the laboratory system.

In addition, the activation/deactivation of retrieval masking of a laboratory device can be triggered immediately or can be applied with a preconfigured delay such as, for example, at the end of the day or shift.

In the following detailed description of the embodiments, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration, and not by way of limitation, specific embodiments in which the disclosure may be practiced. It is to be understood that other embodiments may be utilized and that logical, mechanical and electrical changes may be made without departing from the spirit and scope of the present disclosure.

The use of the 'a' or 'an' can be employed to describe elements and components of the embodiments herein. This is done merely for convenience and to give a general sense of the inventive concepts. This description should be read to include one or at least one and the singular includes the plural unless it is obvious that it is meant otherwise.

The term "test sample" as used herein can be a broad term and can be given its ordinary and customary meaning to a person of ordinary skill in the art and may not be limited to a special or customized meaning. The term specifically may refer, without limitation, to an aliquot of a substance such as a chemical or biological compound. Specifically, the test sample may be or may comprise at least one biological specimen, such as one or more of: blood; blood serum; blood plasma; urine; saliva. Additionally, or alternatively, the test sample may be or may comprise a chemical substance or compound and/or a reagent. The test sample may specifically be a liquid test sample, such as an aliquot of a fluid substance of the chemical or biological compound. For example, the liquid test sample may be or may comprise at least one pure liquid, such as a liquid substance and/or a solution containing one or more liquid substances, comprising the at least one chemical and/or the biological substance. As another example, the liquid test sample may be or may comprise a liquid mixture, such as a suspension, an emulsion and/or a dispersion of one or more chemical and/or biological substances. However, other, in particular non-liquid test samples can be possible. For example, the container may be a reagent container. Other test sample types may be, for example, tissue, homogenized material, calibration or monitoring container-like devices may be the handling subject.

The term "test sample container" as used herein can be a broad term and can be given its ordinary and customary meaning to a person of ordinary skill in the art and may not be limited to a special or customized meaning. The term specifically may refer, without limitation, to a receptacle, which can be configured for one or more of containing, storing and/or transporting a test sample, specifically, a liquid test sample. Further, the test sample container may be configured for being handled in a test sample handling system. Specifically, the test sample container may be used in the field of medical and/or chemical laboratories. For example, the test sample container may be selected from the group comprising of: a vessel; a vial; a syringe; a cartridge; an ampoule; or a container. For example, the test sample container may comprise a test sample container body for containing the test sample and a test sample container closure, such as a cap for sealing the test sample container. In the following, without restricting further possibilities, the option of a test sample tube will be described, wherein the test sample tube, as an example, may be positioned in a test sample holder, with an open end pointing upwards.

The term ' test sample container carrier' as used herein can refer to any kind of holder configured to receive one or more test sample containers and configured to be used for transporting test sample container(s). Test sample container carriers may be of two major types, single holders and sample racks.

A 'single holder' can be a type of test sample container carrier configured to receive and transport a single test sample container. Typically, a single holder can be provided as a puck, i.e., a flat cylindrical object with an opening to receive and retain a single test sample container.

A 'sample rack' can be a type of test sample container carrier, typically made of plastics and/or metal, adapted for receiving, holding and transporting a plurality of test sample container, e.g., five or more test sample container e.g., disposed in one or more rows. Apertures, windows or slits may be present to enable visual or optical inspection or reading of the test sample container or of the test samples in the test sample container or of a label, such as a barcode, present on the test sample container held in the sample rack.

The term 'laboratory instrument' or "laboratory device" as used herein can encompass any apparatus or apparatus component operable to execute and/or cause the execution of one or more processing steps /workflow steps on one or more biological samples and/or one or more reagents. The expression 'processing steps' thereby can refer to physically executed processing steps such as centrifugation, aliquotation, sample analysis and the like. The term 'instrument' can cover pre-analytical instruments, post-analytical instruments, analytical instruments and laboratory middleware.

The term 'laboratory middleware' as used in the present description can refer to any physical or virtual processing device configurable to control a laboratory instrument/device or system comprising one or more laboratory instruments/devices in a way that workflow(s) and workflow step(s) can be conducted by the laboratory instrument/system. The laboratory middleware may, for example, instruct the laboratory instrument/system to conduct pre-analytical, post analytical and analytical workflow(s)/ workflow step(s). The laboratory middleware may receive information from a data management unit regarding which steps need to be performed with a certain test sample. In some embodiments, the laboratory middleware can be integral with a data management unit, can be comprised by a server computer and/or be part of one laboratory instrument or even distributed across multiple instruments of the laboratory system. The laboratory middleware may, for instance, be embodied as a programmable logic controller running a computer-readable program provided with instructions to perform operations.

A 'data storage unit' or 'database' can be a computing unit for storing and managing data such as a memory, hard disk or cloud storage. This may involve data relating to biological/medical test sample(s) to be processed by the automated system. The data management unit may be connected to an LIS (laboratory information system) and/or an HIS (hospital information system). The data management unit can be a unit within or co-located with a laboratory instrument. It may be part of the laboratory middleware. Alternatively, the database may be a unit remotely located. For instance, it may be embodied in a computer connected via a communication network.

The term 'communication network' as used herein can encompass any type of wireless network, such as a WiFi™, GSM™, UMTS or other wireless digital network or a cable based network, such as Ethernet™ or the like. In particular, the communication network can implement the Internet protocol (IP). For example, the communication network can comprise a combination of cable-based and wireless networks.

The term 'remote system' or 'server' as used herein can encompass any physical machine or virtual machine having a physical or virtual processor, capable of receiving; processing and sending data. A server can run on any computer including dedicated computers, which individually can also often be referred to as 'the server' or shared resources such as virtual servers. In many cases, a computer can provide several services and have several servers running. Therefore, the term server may encompass any computerized device that shares a resource with one or more client processes. Furthermore, the terms 'remote system' or 'server' can encompass a data transmission and processing system distributed over a data network (such as a cloud environment).

The term "transportation system" as used herein can be a broad term and can be given its ordinary and customary meaning to a person of ordinary skill in the art and may not be limited to a special or customized meaning. The term specifically may refer, without limitation, to an arbitrary system, which can be configured for moving and/or transporting and/or transferring and/or carrying objects from one position to another. Specifically, the transportation system may be configured for moving the plurality of test sample container carriers through the test sample transportation system such as from a laboratory loading device to another laboratory device of the test sample transportation system. The other laboratory device may be an analysis station. As an example, the transportation system may comprise at least one transport element selected from the group comprising of: a conveyor, such as a belt conveyor or a chain conveyor, or a vehicle system, such as an electronic vehicle system. The test sample transportation system may be or may comprise a multilane transportation system having a plurality of transport elements. The test sample transportation system may be or may comprise a plurality of parallel transport elements. The transport devices may be arranged in a common plane and/or in different planes such as on top of each other.

The term "moving" the plurality of test sample container carriers as used herein, can be a broad term and can be given its ordinary and customary meaning to a person of ordinary skill in the art and may not be limited to a special or customized meaning. The term specifically may refer, without limitation, to an action of transporting and/or transferring and/or carrying the test sample container carriers by using the test sample transportation system. Specifically, the test sample transportation system may be configured for moving the test sample container carriers individually. For example, each of the test sample container carriers may be moved in at least one individual direction, specifically, independently from each other. For example, the movement of the test sample container carriers may be a one-dimensional movement in one direction along the test sample transportation system. As another example, the movement of the test sample container carriers may be a two-dimensional movement in two directions along the test sample transportation system. Additionally, or alternatively, the test sample container carriers may be moved in a third direction by the test sample transportation system by passing a difference in height of the test sample handling system. Further, the test sample transportation system may be configured for moving the plurality of test sample container carriers in a bidirectional manner.

Referring initially to <FIG> illustrates a typical laboratory system setup <NUM>. In a typical laboratory system <NUM>, a plurality of different laboratory devices such as, for example, such as pre-analytical laboratory devices <NUM>, analytical laboratory devices <NUM>, <NUM>, and post-analytical laboratory devices <NUM> can be connected together via a transportation system <NUM>. A pre-analytical laboratory device <NUM> can usually be used for the preliminary processing of test samples <NUM> or test sample container carriers <NUM>. An analytical laboratory device <NUM> can be designed, for example, to use a test sample or part of the test sample and a test reagent in order to produce a measurable signal, based on which it is possible to determine whether an analyte is present, and if desired in what concentration. A post-analytical laboratory device <NUM> can be used for the post-processing of test samples or test sample vessels like the archiving of test samples or test sample container carriers.

The transportation system <NUM> can be used to transport test sample container carriers <NUM> comprises test samples between the plurality of different laboratory devices <NUM>, <NUM>, <NUM>. Control of the movement of the test sample container carriers <NUM> between the plurality of laboratory devices <NUM>, <NUM>, <NUM> can be managed by a laboratory middleware <NUM>. The laboratory middleware <NUM> can communicate with the plurality of laboratory devices <NUM>, <NUM>, <NUM> as well as, the transportation system <NUM>.

In one embodiment, during the operation of the laboratory system <NUM>, a temporary buffer <NUM>, i.e., an add-on buffer <NUM>, may be formed on the transportation system <NUM>. The temporary buffer <NUM> can receive and house several test sample container carriers <NUM> during periods when the analytical laboratory devices <NUM> may be at capacity and, therefore, can no longer accept test samples. The temporary buffer <NUM> can serve as place to house the test sample container carriers <NUM> in order to prevent logjams and bottleneck traffic flow issues on the transportation system <NUM>.

<FIG> illustrates a flowchart of a method for routing of test sample container carriers <NUM> while a laboratory device in a laboratory system <NUM> is masked. In step <NUM>, a test sample container carrier <NUM> can be in a typically retrievable laboratory device such as, for example, post-analytical station <NUM> such as, for example, a refrigerator. However, the retrievable laboratory device <NUM> can be masked by the laboratory middleware <NUM> of the laboratory system <NUM> so that the test sample container carrier <NUM> cannot leave the laboratory device. The laboratory device <NUM> can be masked for several reasons, which will be described in more detail in the following.

In step <NUM>, a request can be made by the laboratory middleware <NUM> of the laboratory system <NUM> to retrieve one of the test sample container carriers <NUM> from the masked laboratory device <NUM>. In one embodiment, since the laboratory device <NUM> is masked, the test sample container carrier <NUM> cannot be retrieved. In another embodiment, the laboratory middleware <NUM> of the laboratory system <NUM> can determine if the target laboratory device <NUM> for which the test samples <NUM> in the test sample container carrier <NUM> is needed is also masked. If the target laboratory device <NUM> is not masked, the test sample container carrier <NUM> may be retrieved and sent to the unmasked target device <NUM>.

In step <NUM>, the laboratory middleware <NUM> of the laboratory system <NUM> can then determine if manual retrieval of the test sample container carrier <NUM> from the masked laboratory device <NUM> was requested by a laboratory operator. If manual retrieval was requested, the test sample container carrier <NUM> can be retrieved, in step <NUM>, independently of the masking status of the laboratory device <NUM>. If manual retrieval was not requested, the test sample container carrier <NUM>, in step <NUM>, is not retrieved.

In step <NUM>, the laboratory device <NUM> is unmasked. After unmasking, the workflow for the test sample container carriers <NUM> in the previously masked laboratory device <NUM> can be recalculated by the laboratory middleware <NUM>. If it is determined that one of the test sample container carriers <NUM> needs to be retrieved because, for example, that test sample container carrier <NUM> has outstanding open test results for the test samples <NUM>, time has expired for that test sample container carrier <NUM> at that laboratory device <NUM>, the forced retrieval was unsuccessful, and the like, that test sample container carrier <NUM> is retrieved in step <NUM>.

In this example, a connection point <NUM> such as, for example, a bidirectional reformatter, between the transportation system <NUM> and a target laboratory device <NUM> such as, for example, an archival laboratory device <NUM> such as, for example, a refrigerator becomes unavailable. <FIG> illustrates a flowchart of this method for routing test samples during periods of a blocked transportation connection point in a laboratory system.

In step <NUM>, the laboratory middleware <NUM> receives a status message from a laboratory analytical device <NUM> indicating that transportation connection point <NUM> is not available. This message than triggers, in step <NUM>, the masking of the target device <NUM> for sorting, i.e., there will no attempt to route test sample container carriers <NUM> from the transportation system <NUM> to the target laboratory device <NUM> through the unavailable connection point <NUM>, as well as for retrieval, i.e., there will be no attempt to retrieve test sample container carriers <NUM> from the target laboratory device <NUM> through the unavailable connection point <NUM>.

At the same time as the target laboratory device <NUM> is masked, a laboratory operator may receive a warning about the unavailability of the connection point <NUM>, in step <NUM>. The laboratory operator can be warned in several ways. For example, a visual indication on the connection point <NUM> itself such as, for example, a red error or yellow warning light can flash depending on the reason of the connection point's <NUM> unavailability; a notification message may appear on the graphic user interface (GUI) of the control unit of the target laboratory device <NUM>; and/or a notification message may appear in the notification section of the laboratory middleware <NUM> GUI.

The test sample container carriers <NUM> that were originally being routed to the target laboratory device <NUM> will, in step <NUM>, now be routed to/or remain in a temporary buffer or add-on buffer (AOB) <NUM> section of the transportation system <NUM>. The routing of the test sample container carriers <NUM> can be controlled by the laboratory middleware <NUM> by requesting that the temporary buffer <NUM> be used in place of the target laboratory device <NUM> or by not sending a sample retrieval request to those test sample container carriers <NUM> already in the temporary buffer <NUM>.

Without this functionality, the laboratory middleware <NUM> typically would have requested that the test sample container carriers <NUM> be routed to the target laboratory device <NUM>. Since the connection point <NUM> was unavailable, the laboratory middleware <NUM> would have had to send the test sample container carriers <NUM> to alternative destinations since the requested laboratory target <NUM> was not available. In the worst case, this could result in the loss of test sample container carrier tracking information when the laboratory middleware <NUM> is unable to interpret the misalignment between expected and actual test sample container carrier <NUM> routing. Additionally, laboratory middleware <NUM> functionality that could be used to manage workload balancing across multiple target laboratory devices <NUM>, <NUM> on the transportation system <NUM> could be comprised since test sample container carriers <NUM> could be unintentionally routed to unexpected destinations.

Additionally, test sample container carriers <NUM> already located in the target laboratory device <NUM> will remain in the target laboratory device <NUM> if additional testing had been requested of those test sample container carriers <NUM>. The laboratory middleware <NUM> will simply not send sample retrieval requests for test sample container carriers <NUM> currently in a masked target laboratory device <NUM>.

In one embodiment, if it is determined, in step <NUM>, that the processing of the test sample container carriers <NUM> is urgent i.e., the test sample container carrier <NUM> contains STAT test samples, the laboratory operator can request manual retrieval of that test sample container carrier <NUM> from the target laboratory device <NUM> via the user control interface of the laboratory middleware <NUM>, in step <NUM>, and will be able to retrieve and manually process test samples <NUM> in that test sample container carrier <NUM>.

Without this functionality, the laboratory middleware <NUM> would have requested that the test sample container carriers <NUM> be retrieved from the target laboratory device <NUM>. Without this functionality, the target laboratory device <NUM> would be unaware of the unavailable connection point <NUM>. With the unavailable connection point <NUM>, test sample container carriers <NUM> would be retrieved from the target laboratory device <NUM> but would not be able to be processed any further. This would result in the sample test containers <NUM> remaining in the area of the connection point <NUM> and transportation system <NUM>, an area that is not temperature or humidity controlled, until the connection point <NUM> becomes functional. At this location, it will also be more difficult for the laboratory operator to manually access important test sample container carriers <NUM> for further processing. If the test sample container carrier <NUM> were in the area of the connection point <NUM>, the laboratory operator would have to search for test sample container carrier <NUM> in the group of retrieved and locked test sample container carriers <NUM>. Instead, if the test sample container carriers <NUM> remain the target laboratory device <NUM>, the laboratory operator can simply request manual retrieval of that test sample container carrier <NUM> from the target laboratory device <NUM> via the user control interface of the laboratory middleware <NUM>.

The laboratory operator can determine and fix the issue with the connection point <NUM> and the connection point <NUM> becomes available again in step <NUM>. The laboratory middleware <NUM> will then receive a status message that the connection point <NUM> is now operational. This message then triggers the laboratory middleware <NUM> to unmask the target laboratory device <NUM> for both sorting and retrieval in step <NUM>. After unmasking, the workflow for the test sample container carriers <NUM> in the previously masked laboratory device <NUM> can be recalculated by the laboratory middleware <NUM>.

In step <NUM>, test sample container carriers <NUM> that had been routed to the temporary buffer <NUM> while the target laboratory device <NUM> was masked can now be retrieved from the temporary buffer <NUM> and sent to the target laboratory device <NUM>. This process is controlled by the laboratory middleware <NUM> by sending test sample retrieval request messages to the transportation system <NUM>.

Additionally, in step <NUM>, the test samples <NUM> in the test sample container carriers <NUM> with outstanding test requests that were in the target laboratory device <NUM> while the target laboratory device <NUM> was masked can now be retrieved from the target laboratory device <NUM> for further processing.

In this example, the end of a normal laboratory routine operation is approaching and the laboratory operator wants to reduce and ultimately stop the test sample processing on the laboratory system <NUM> and its connected laboratory analytical devices <NUM>. <FIG> illustrates a flowchart of a method for routing test sample container carriers at the end of a shift/day in a laboratory system <NUM>.

At the end of the day/shift, the laboratory operator, in step <NUM>, can stop loading test samples container carriers into the input modules of the pre-analytic devices <NUM> of the transportation system <NUM> of the laboratory system <NUM>. Instead, all incoming test samples container carriers <NUM> can be manually stored in a post-analytical device <NUM> such as, for example, an archival device such as, for example, a refrigerator for processing on the next day/shift.

In step <NUM>, the laboratory operator accesses the laboratory middleware <NUM> routine client to mask the archival target device <NUM> for retrieval, i.e., no test sample container carriers <NUM> will be able to leave the archival target device <NUM>. In another embodiment, the masking of the archival target device <NUM> can happen automatically based on the configuration of the rule engine of the laboratory middleware <NUM> such as, for example, the retrieval masking can occur based on the time of day.

In one embodiment, the masking of the archival target device <NUM> for retrieval can be applied to only test sample container carriers <NUM> containing test samples <NUM> with routine priority. This way, the STAT test samples <NUM> can still be processed the same way during normal operating times.

In one embodiment, in step <NUM>, the temporary buffer targets <NUM> can reduce the test sample container carrier <NUM> buffer duration times, i.e., the amount of time a test sample container carrier <NUM> can remain in the temporary buffer <NUM> assigned to the test sample container carriers <NUM> so that the test sample container carriers <NUM> are retrieved from the temporary buffer <NUM> and routed to the archival target device <NUM> sooner. This reduction in time can be configured to happen automatically based on the time of day by the laboratory middleware <NUM>.

In one embodiment, in step <NUM>, the laboratory operator can access the laboratory middleware <NUM> routine client to mask the temporary buffer targets <NUM> for distribution so that the test sample container carriers <NUM> are routed directly to the archival target device <NUM> once all open test requests are processed for those test sample container carriers <NUM>. In another embodiment, the masking of the temporary buffer target device <NUM> can happen automatically based on the configuration of the rule engine of the laboratory middleware <NUM> such as, for example, based on the time of day.

In step <NUM>, all test sample container carriers <NUM> still located on the laboratory transportation system <NUM> or in the connected laboratory analytic devices <NUM> will continue to be processed as normal. However, once the test sample container carriers <NUM> reach the archival target device <NUM>, the test sample container carriers <NUM> will not be retrieved for any additional processing.

Then, when routine operation resumes the next day/shift, the laboratory operator, in step <NUM>, accesses the laboratory middleware <NUM> routine client and unmasks the archival target devices <NUM> for retrieval. In another embodiment, the unmasking of the archival target device <NUM> can happen automatically based on the configuration of the rule engine of the laboratory middleware <NUM> such as, for example, based on the time of day. After unmasking, the workflow for the test sample container carriers <NUM> in the previously masked archival laboratory device <NUM> can be recalculated by the laboratory middleware <NUM>.

In step <NUM>, the test sample container carriers <NUM> that currently are in the archival target device <NUM> and that have open test requests for the test samples <NUM> in the test sample container carriers <NUM> will be retrieved by the laboratory system <NUM> to the transportation system <NUM>. This occurs by the laboratory middleware <NUM> sending retrieval requests to the archival target device <NUM>.

Without this functionality, the reduction of workload into the laboratory system <NUM> may only be achieved by switching off the laboratory analytic devices <NUM> and collecting the test sample container carriers <NUM> that have already been retrieved from the archival target device <NUM>. This would result in test samples <NUM> being in non-temperature and humidity controlled environments. Additionally, without this functionality, the automated handling of STAT test samples <NUM> different from routine handling of test sample container carriers <NUM> would not be allowed.

In this example, maintenance of part of the transportation system <NUM> is necessary while the rest of the transportation system <NUM> remains functional is illustrated. <FIG> illustrates a flowchart of a method for routing test sample container carriers <NUM> during periods of transportation system <NUM> maintenance in a laboratory system <NUM>.

In step <NUM>, it is determined that maintenance of part of the transportation system <NUM> is necessary since that part of the transportation system <NUM> is crucial for the routing of retrieved test sample container carriers <NUM> from an archive target device <NUM> or a test sample temporary buffer <NUM> to the laboratory analytic devices <NUM> or that routing of test sample container carriers <NUM> around the section of the transportation system <NUM> needing maintenance results in traffic jams and a locked transportation system <NUM>.

In step <NUM>, the target laboratory device <NUM> is masked for retrieval or for both retrieval and distribution depending on the impact to the transportation system <NUM>.

In step <NUM>, temporary buffers <NUM> are also masked for retrieval or for both retrieval and distribution depending on the impact to the transportation system <NUM>.

In step <NUM>, test sample container carriers <NUM> already at the target laboratory device <NUM> or in the temporary buffers <NUM> but receive addition al test orders for the test samples <NUM> in the test sample container carriers <NUM> will remain at the target laboratory device <NUM> or temporary buffer <NUM>. This allows the workload of the laboratory system <NUM> to be reduced during maintenance of the transportation system <NUM>.

In one embodiment, if the target laboratory device <NUM> is masked for distribution of test sample container carriers <NUM>, test sample container carriers <NUM> usually routed to the target laboratory device <NUM> will now be routed to alternative targets in step <NUM>. This will result in redirecting test sample container carrier <NUM> flow away from the affected area of the transportation system <NUM>.

Depending on the nature of the laboratory system <NUM>, the nature of the root cause of the maintenance issue, and the exact location of maintenance issue on the transportation system <NUM>, the masking can either be triggered automatically through the processing of module availability messaging by the laboratory middleware <NUM> or manually by the laboratory operator through access via the routine client of the laboratory middleware <NUM>.

Once the maintenance is completed, the affected target laboratory devices <NUM> and temporary buffers <NUM> can be unmasked, in step <NUM>, either manually by the laboratory operator or automatically through the processing of module availability messaging of the laboratory middleware <NUM>. After unmasking, the workflow for the test sample container carriers <NUM> in the previously masked laboratory device <NUM> can be recalculated by the laboratory middleware <NUM>.

In step <NUM>, the test samples <NUM> in the test sample container carriers <NUM> with open test requests that had remained in the previously masked laboratory target device <NUM> and/or temporary buffer devices <NUM> can now be retrieved. This process is controlled by the laboratory middleware <NUM> by sending sample retrieval request messages to the previously masked laboratory target devices <NUM> and/or temporary buffer devices <NUM>.

In step <NUM>, test sample container carriers <NUM> that had remained in test sample temporary buffer target <NUM> even though their storage duration had elapsed while the test sample temporary buffer <NUM> was masked for retrieval can now be retrieved and routed to their final archival target device <NUM>. This process is controlled by the laboratory middleware <NUM> by sending sample retrieval request messages to the previously masked temporary buffer devices <NUM>.

In step <NUM>, the test sample container carriers <NUM> that had been rerouted to alternative targets while their original target laboratory device <NUM> were masked for distribution can follow different scenarios.

Note that cases a-c are merely examples of a reasonable configuration for the laboratory middleware <NUM>. Different behavior such as, for example, prioritizing the initial target device even if test samples containers <NUM> had been routed to a target device of similar function, can be configured as well.

Without this functionality, either the entire laboratory system <NUM> would have to be shut down for maintenance even if that would not be required from the hardware itself or the overloading of the transportation system <NUM> or parts of the transportation system <NUM> could not be prevented. Depending on the nature of the transportation system <NUM>, overloading a small part of the transportation system <NUM> can stop the complete transportation system <NUM> from working properly.

In this example, the prevention of the overloading of the laboratory system <NUM> due to a peak time of new incoming test samples <NUM> is described. <FIG> illustrates a flowchart of a method for routing test sample container carriers <NUM> during periods of peak sample/STAT sample loading in a laboratory system <NUM>.

In step <NUM>, a high number of incoming test sample container carriers <NUM> or an incoming batch of test sample container carriers <NUM> from an emergency ward (i.e., STAT test samples <NUM>) is detected by the laboratory middleware <NUM> of the laboratory system <NUM>. The detection of the test sample container carriers <NUM> can happen by:.

In anticipation of the large number of test samples containers <NUM> or of STAT test sample container carriers, in step <NUM>, the archival target device <NUM> and/or the temporary buffer targets <NUM> are masked for retrieval automatically. This masking can help reduce the workload or help prioritize STAT test samples on the laboratory system <NUM>.

When the reduction of the test sample container carriers <NUM> is detected or the STAT test sample container carriers have been processed, the masked archival laboratory target <NUM> and temporary buffer targets <NUM> are unmasked for retrieval in step <NUM>. After unmasking, the workflow for the test sample container carriers <NUM> in the previously masked laboratory device <NUM> can be recalculated by the laboratory middleware <NUM>.

In step <NUM>, the test samples <NUM> in the test sample container carriers <NUM> with open test requests that had been in the masked archival laboratory device <NUM> and temporary buffer target <NUM> will now be retrieved. This process is controlled by the laboratory middleware <NUM> by sending sample retrieval request messages to the previously masked archival laboratory target <NUM> and/or temporary buffer devices <NUM>.

In step <NUM>, the test sample container carriers <NUM> that had remained in test sample temporary buffer targets <NUM> even though their storage duration had elapsed while the test sample temporary buffer <NUM> was masked for retrieval can now be retrieved and routed to their final archival target laboratory device <NUM>. This process is controlled by the laboratory middleware <NUM> by sending sample retrieval request messages to the previously masked temporary buffer devices <NUM>.

Without this functionality, the prevention of a general overloading of the laboratory system <NUM> would become more difficult in the routine time or would require more complex configuration of the laboratory middleware <NUM> during the laboratory system <NUM> set-up time.

In this example, the prevention of the overloading of alternative analytic laboratory targets due to urgent maintenance of an important laboratory analytic devices is illustrated. <FIG> illustrates a flowchart of a method for routing test sample container carriers <NUM> during periods of urgent laboratory analyzer maintenance in a laboratory system.

In step <NUM>, a laboratory analytical device <NUM> that usually processes a high fraction of the test sample workload has to be disconnected from the transportation system <NUM> of the laboratory system <NUM> to undergo urgent maintenance.

During maintenance, the laboratory analytical device <NUM> will be masked for distribution in the laboratory middleware <NUM> in step <NUM>. The laboratory analytical device <NUM> can be masked either manually by the laboratory operator or by the laboratory middleware <NUM> sending out a status message.

Additionally, the laboratory operator may foresee a general overloading of the laboratory system <NUM> and, in step <NUM>, the laboratory operator may mask some, or all, of the test sample temporary buffer targets <NUM> and/or some, or all, of the archival target laboratory devices <NUM> for retrieval in order to reduce the test sample workload of the transportation system <NUM>.

In step <NUM>, the maintenance activity on the laboratory analytical device <NUM> is completed and the laboratory analytical device <NUM> is unmasked. After unmasking of the laboratory analytical device <NUM>, the workflow for the test sample container carriers <NUM> in the previously masked laboratory analytical device <NUM> can be recalculated by the laboratory middleware <NUM>.

Once a reasonable reduction of the workload of the laboratory system <NUM> is determined, the test sample temporary buffers <NUM> and the archival target laboratory devices <NUM>, in step <NUM>, are unmasked for retrieval. After unmasking of the test sample temporary buffers <NUM> and the archival target laboratory devices <NUM>, the workflow for the test sample container carriers <NUM> in the previously masked laboratory device <NUM> can be recalculated by the laboratory middleware <NUM>.

In step <NUM>, the test samples <NUM> in the test sample container carriers <NUM> with open test requests that had been in the masked archival laboratory device <NUM> and/or the masked temporary buffer targets <NUM> will now be retrieved. This process is controlled by the laboratory middleware <NUM> by sending sample retrieval request messages to the previously masked laboratory target <NUM> and/or temporary buffer devices <NUM>.

In one embodiment, the retrieval masking process can be applied selectively depending of the type of the transportation system <NUM>, i.e., the process can be applied at the section level if the transportation system <NUM> allows it such as, for example, if the transportation system <NUM> comprises belt conveyors.

Further disclosed and proposed is a computer program product including computer-executable instructions for performing the disclosed method in one or more of the embodiments enclosed herein when the program is executed on a computer or computer network. Specifically, the computer program may be stored on a computer-readable data carrier or a server computer. Thus, specifically, one, more than one or even all of method steps as indicated above may be performed by using a computer or a computer network, preferably by using a computer program.

As used herein, a computer program product refers to the program as a tradable product. The product may generally exist in any format, such as in a paper format, or on a computer-readable data carrier on premise or located at a remote location. Specifically, the computer program product may be distributed over a data network (such as a cloud environment). Furthermore, not only the computer program product, but also the execution hardware may be located on premise or in a cloud environment.

Further disclosed and proposed is a computer-readable medium comprising instructions which, when executed by a computer system, cause a laboratory system to perform the method according to one or more of the embodiments disclosed herein.

Further disclosed and proposed is a modulated data signal comprising instructions, which, when executed by a computer system, cause a laboratory system to perform the method according to one or more of the embodiments disclosed herein.

Referring to the computer-implemented aspects of the disclosed method, one or more of the method steps or even all of the method steps of the method according to one or more of the embodiments disclosed herein may be performed by using a computer or computer network. Thus, generally, any of the method steps including provision and/or manipulation of data may be performed by using a computer or computer network. Generally, these method steps may include any of the method steps, typically except for method steps requiring manual work, such as providing the samples and/or certain aspects of performing the actual measurements.

Claim 1:
A method of routing test sample container carriers (<NUM>) during periods of laboratory disruption in a laboratory system (<NUM>) wherein the laboratory system (<NUM>) comprises a plurality of laboratory devices (<NUM>, <NUM>, <NUM>, <NUM>), at least one buffer (<NUM>), a transportation system (<NUM>), and a laboratory middleware (<NUM>), the method comprising:
determining, by the laboratory middleware (<NUM>), whether a laboratory device (<NUM>) in the laboratory system (<NUM>) is unavailable, wherein the unavailable laboratory device (<NUM>) is a connection point between the transportation system (<NUM>) and a target laboratory device (<NUM>);
masking a, by the laboratory middleware (<NUM>), the target laboratory device (<NUM>) connected to the unavailable laboratory device (<NUM>) so that test sample container carriers (<NUM>) are not sent to the target laboratory device (<NUM>) and test sample container carriers (<NUM>) cannot be retrieved from the target laboratory device (<NUM>);
rerouting test sample container carriers (<NUM>) originally routed to the target laboratory device (<NUM>) before the unavailability of the laboratory device (<NUM>) to a buffer (<NUM>) located in the laboratory system (<NUM>);
calculating a new laboratory system workflow by the laboratory middleware (<NUM>) after the unavailable laboratory device (<NUM>) becomes available;
unmasking, by the laboratory middleware (<NUM>), the target laboratory device (<NUM>) after the new laboratory workflow is calculated; retrieving test sample container carriers (<NUM>) with outstanding test requests that were in the target laboratory device (<NUM>) while the target laboratory (<NUM>) was masked from the target laboratory device (<NUM>) for further processing; and
retrieving the test sample container carriers (<NUM>) from the buffer (<NUM>) and sending those test sample container carriers (<NUM>) to the target laboratory device (<NUM>).