System and method for presenting laboratory data to laboratory users

Abstract

A system for presenting laboratory data to a laboratory user includes a perception component configured to continuously collect in-situ contextual data regarding a laboratory and a laboratory user; a user modeling component configured to receive in-situ context data from the perception component to create a user-specific model for each user in the laboratory; a laboratory equipment perceiving assembly configured to monitor a state, performance, alert, and / or maintenance of laboratory equipment within the laboratory; a notification component configured to receive in-situ context data from the perception component and laboratory equipment status data from the laboratory equipment perception component, and configured to process and determine which of these data from the in-situ context data and the laboratory equipment status data are to be presented to a laboratory user; and a presentation component configured to present the processed data from the notification component, where the presented data includes both a public notification and a private notification of the data made to a laboratory user.

Description

This application is a divisional application. The parent application is titled “System and Method for Presenting Laboratory Data to Laboratory Users,” filed on February 25, 2022, with application number 202210184372.9. Technical Field

[0001] The present disclosure generally relates to communication and notification needs in a laboratory environment. Background Art

[0002] Typical known laboratory systems strive to facilitate laboratory information monitoring practices within a laboratory environment. In these known laboratory systems, the laboratory information displayed to a user is typically customized based on the user's movement and the user's spatial proximity to an information source (e.g., a laboratory analyzer). However, these known laboratory systems typically focus on enabling information access based solely on the user's proximity to the information content.

[0003] For example, U.S. Patent Application Publication No. 2016 / 246364 discloses a laboratory system that employs distance-based screen transitions and interactions. Furthermore, U.S. Patent Application Publication No. 2017 / 0228508 discloses a laboratory system that focuses on retrieving medical data based on the proximity between a medical monitoring device and a clinician's mobile device.

[0004] Therefore, considering the potential laboratory information needs of laboratory users and the interaction and flow of information within the laboratory system, it is necessary to provide supportive laboratory information consultation in the laboratory environment. Summary of the Invention

[0005] The elements and components of the embodiments described herein may be described using "a" or "an". This is done for convenience only and to provide a general understanding of the concepts of the present invention. The interpretation should be understood to include one or at least one, and the singular includes the plural unless it is obvious that it has other meanings.

[0006] As used herein, the term "laboratory instrument" or "laboratory equipment" may include any instrument or instrument component operable to perform and / or facilitate the performance of one or more processing steps / workflow steps on one or more biological samples and / or one or more reagents. Thus, the term "processing step" may refer to a physically performed processing step, such as centrifugation, aliquoting, sample analysis, etc. The term "instrument" may encompass pre-analytical instruments, post-analytical instruments, analytical instruments, and laboratory middleware.

[0007] The term "post-analytical instrument" as used herein may include any instrument or instrument component that can be configured to perform one or more post-analytical processing steps / workflow steps, including but not limited to sample unloading, transport, re-capping, de-capping, temporary storage / buffering, archiving (refrigerated or not), retrieval and / or disposal.

[0008] As used herein, the term "pre-analytical instrument" may include any instrument or instrument component that can be configured to perform one or more pre-analytical processing steps / workflow steps, including but not limited to centrifugation, resuspension (e.g., by mixing or vortexing), capping, decapping, recapping, sealing, desealing, sorting, tube type identification, rack loading, sample loading, sample quality determination, and / or aliquoting. Such processing steps may also include adding chemicals or buffers to the sample, concentrating the sample, incubating the sample, etc.

[0009] The term "analyzer" / "analytical instrument" used in this specification may include any instrument or instrument assembly configured to obtain a measurement value. The analyzer is operable to determine the parameter value of a sample or its components via various chemical, biological, physical, optical or other technical procedures. The analyzer may be operable to measure the parameter of a sample or at least one analyte and return the measurement value obtained. The possible analysis result list returned by the analyzer includes but is not limited to: the concentration of the analyte in the sample, the digital (yes or no) result indicating the presence of the analyte in the sample (corresponding to a concentration above the detection level), optical parameters, DNA or RNA sequences, data obtained by mass spectrometry analysis of proteins or metabolites, and various types of physical or chemical parameters. The analyzer may include a unit that helps to pipette, feed and mix the sample and / or reagents. The analyzer may include a reagent holding unit that holds the reagents used to perform the assay. The reagents may, for example, be arranged in the form of a container or box containing individual reagents or a group of reagents, placed in a suitable receptacle or position in a storage room or conveyor belt. It may include a consumables feeding unit. The analyzer may include a processing and detection system whose workflow may be optimized for certain types of analysis. Examples of such analyzers are clinical chemistry analyzers, coagulation chemistry analyzers, immunochemistry analyzers, urine analyzers, nucleic acid analyzers, which are used to detect the results of a chemical or biological reaction or to monitor the progress of a chemical or biological reaction.

[0010] As used herein, the term "laboratory middleware" may refer to any physical or virtual processing device that can be configured to control a laboratory instrument or a system comprising one or more laboratory instruments in such a way that workflows and workflow steps can be performed by the laboratory instrument / system. The laboratory middleware may, for example, issue instructions to cause the laboratory instrument / system to execute pre-analytical, post-analytical, and analytical workflows / workflow steps. The laboratory middleware may receive information from a data management unit regarding which steps need to be performed for a particular sample. In some embodiments, the laboratory middleware may be integrated with the data management unit, may consist of a server computer, and / or may be part of a laboratory instrument, or even distributed across multiple instruments in a laboratory system. The laboratory middleware may, for example, be implemented as a programmable logic controller running a computer-readable program having instructions for performing operations.

[0011] The present invention provides a system for presenting laboratory data to laboratory users. The system may include a perception component configured to continuously collect in-situ contextual data about the laboratory and laboratory users; a user modeling component configured to receive the in-situ contextual data from the perception component to create a user-specific model for each laboratory user in the laboratory; a laboratory equipment awareness component configured to monitor the status, performance, alarms, and / or maintenance of laboratory equipment in the laboratory; a notification component configured to receive the in-situ contextual data from the perception component and laboratory equipment status data from the laboratory equipment awareness component, and process and determine which of the in-situ contextual data and the laboratory equipment status data are to be presented to the laboratory users; and a presentation component configured to present the processed data from the notification component to the laboratory users, wherein the presented data includes both public notifications and private notifications of the data to the laboratory users.

[0012] In situ contextual data can be collected by multi-channel sensors, such as wearable devices worn by lab users, indoor positioning devices set up throughout the lab, motion sensors set up throughout the lab, lab user location data, lab user interactions, lab user biometrics (e.g., fingerprint, voice, iris, and face), and combinations thereof.

[0013] Laboratory users can switch between private and public notifications of data. Private data notifications and public data notifications can be predefined. For example, private data notifications can be presented on smartphones, tablets, laptops, desktops, wearable smart devices, virtual spaces, or any combination thereof, and under the highest security and privacy standards established in international regulations (such as GDPR and HIPAA). Private data notifications can also be auditory (e.g., beeping), visual, taste, olfactory, or tactile (e.g., vibration) alarms. In addition, public data notifications can be located on monitoring displays throughout the laboratory, voice assistant devices set up throughout the laboratory, laboratory equipment displays, alarms (e.g., auditory, visual, or tactile), or any combination thereof. Public data can be data that all laboratory users of the laboratory system can see.

[0014] The laboratory system may further include a database for storing in-situ context data from the sensing component and laboratory equipment status data from the laboratory system awareness component. The data stored in the database may be used to generate statistics and / or predictions to improve services between laboratory customers and suppliers.

[0015] The present invention also provides a method for presenting laboratory data to a laboratory user. The method may include loading a first initial user model; initializing multi-channel sensors throughout the laboratory to collect in-situ data as data occurs; updating the user model and in-situ data by using the work habits and typical laboratory activities of each individual laboratory user; determining whether the laboratory user is interacting with laboratory equipment; if the laboratory user is interacting with laboratory equipment, providing the laboratory user with equipment information through private and public notifications based on the laboratory user's user model; determining whether the laboratory user is en route to perform a task in the laboratory; if the laboratory user is en route, deleting the private notification about the task to be performed and providing the laboratory user with information about the task based on the updated in-situ data; terminating the method if the user requests termination, or otherwise repeating the above method steps until the laboratory user requests termination, saving the in-situ data, and updating the user-specific model.

[0016] The method may further include detecting and storing in a database information about the efficiency with which laboratory users complete tasks.

[0017] The method may further include uploading data currently being a private notification to the laboratory user as a public notification to the laboratory user based on a request from the laboratory user.

[0018] The method may further include downloading data currently in the public notification of the laboratory user to the private notification of the laboratory user upon request of the laboratory user. In addition, the laboratory user has the ability to expand information in the private space of the laboratory user.

[0019] The first initial user model can be based on the lab user's personal demographics, preferences, and lab role. This data can be provided to the lab system at startup.

[0020] In-situ data may include lab users, lab users' locations, lab users' activities, and times.

[0021] Private notifications for lab users can provide confidential information to lab users.

[0022] The method may further include a) initializing the laboratory system after loading a first initial user model, b) updating the laboratory device awareness model, c) updating public user notifications with a standard predefined configuration, d) updating private user notifications based on user preferences, e) determining whether intervention by the laboratory user is required, f) if the laboratory user does not require intervention, repeating update steps c to l(e), g) if the laboratory user requires an invention (intervention), checking current in-situ data to determine a suitable laboratory user to provide the invention (intervention) and updating the laboratory user's private notifications to provide appropriate laboratory user information, h) determining whether the laboratory user wishes to terminate the method, and i) if the laboratory user does not want to terminate the method, repeating steps l(e) to r(i) until the laboratory user wishes to terminate the method. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The following detailed description of specific embodiments of the present disclosure may be best understood when read in conjunction with the following drawings, in which like structures are represented by like reference numerals, and in which: Figure 1 The diagram shows the information interaction flow between various objects in a laboratory according to one embodiment of the present disclosure.

[0024] Figure 2 A smart lab architecture according to one embodiment of the present disclosure is shown.

[0025] Figure 3 A flow chart for presenting lab data to a lab user by using proximity interaction for troubleshooting according to one embodiment of the present disclosure is shown.

[0026] Figure 4 A scenario of privately notifying laboratory users based on SLAT (Subject, Location, Activity, and Time) according to an embodiment of the present disclosure is shown.

[0027] Figure 5 The example illustrates a scenario of supporting a novice lab user according to one embodiment of the present disclosure.

[0028] Figure 6 The example illustrates a scenario of a support service representative according to an embodiment of the present disclosure.

[0029] Figure 7 The example illustrates a scenario of supporting a laboratory manager according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0030] In the following detailed description of the embodiments, reference is made to the accompanying drawings which form a part hereof, and in which are shown by way of illustration and not limitation, specific embodiments in which the present disclosure may be practiced. It will 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.

[0031] A typical lab user constantly consults the lab system for various information throughout the day for various purposes. However, depending on the usage context, different lab users may be interested in different types of lab information regarding lab performance, alarms, medical data, instructions, etc. For example, Table 1 describes examples of different types of lab information that may be required by different lab user roles.

[0032] Table 1. Examples of information needs for different laboratory roles.

[0033] As can be seen in Table 1, laboratory users require a variety of information, including information about other laboratory users in order to coordinate workloads among laboratory users and information about laboratory systems in order to monitor laboratory performance. It is important to note that laboratory systems, including instruments and IT products, also have their own information needs. For example, in a laboratory with connected analytical instruments, the preanalytical instrument will need to know whether the analytical instrument is ready to receive the pre-processed specimen for analysis. Once the results are generated, an IT system, such as a laboratory information system (LIS), can be notified. The laboratory system may also require information about laboratory users so that it can notify and provide laboratory information that is most appropriate for each laboratory user's role.

[0034] First reference Figure 1 , Figure 1The figure illustrates how information flows to address the needs of different entities in the laboratory. As shown, a laboratory user 100 provides information to himself / herself and other laboratory users, and also provides information to the laboratory system 110. In turn, the laboratory system 110 provides information to itself and other laboratory instruments (i.e., pre-analytical instruments, analytical instruments, post-analytical instruments, and combinations thereof) within the laboratory system, as well as to the laboratory users 100. An ideal intelligent laboratory system 110 can facilitate information exchange, such as Figure 1 Today's laboratory automation system 110 is designed to support the interaction between different laboratory components.

[0035] In short, lab users 100 can work in a coordinated manner with lab systems 110 and other lab users 100. This suggests a certain level of "awareness" between lab users and lab systems. Awareness, in this context, refers to understanding what other lab users are doing and what the lab instrument systems are doing. Supporting lab user awareness is crucial, pushing the right information to the right lab users, allowing them to complete the right tasks at the right time and in the right place in the lab.

[0036] This can be translated into the four factors of context awareness, namely subject, location, activity, and time (or SLAT context). By leveraging SLAT context, better coordination of laboratory work can be achieved.

[0037] For this interaction, it is also important to distinguish between the public and private notification spaces of lab users.

[0038] A private space is an interactive space where each lab user can interact privately. In this private space, information is used privately only by the lab user, who, for security reasons and to maintain the integrity of the information, needs to be a registered lab user in the lab system. The private space provides information and notifications that are only of interest to a specific lab user or a specific group of lab users. Confidential information can also be provided in the private space. However, if desired, the lab user can choose to proactively "upload" information from the lab user's private space to the public space. If a lab user chooses to upload information from the lab user's private space to the public space, the lab user's registration will be included with the upload to facilitate tracking errors, such as incorrect private information being uploaded or uploaded to the wrong location in the public space.

[0039] In contrast, the public space can be an interactive space where each individual lab user or consumer can interact publicly. Information in the public space can also be publicly ingested. In other words, all lab users can perceive, i.e., see and / or hear, the information in the public space. Public information can also be transferred and / or saved to the lab user's private space. In the public space, information is primarily visible to all lab users to increase their awareness of certain lab information. If necessary, the lab user can choose to "download" information from the public space to the private space. Again, for security reasons and to maintain the integrity of the information, only registered lab users can download information from the public space to the private space. In addition, lab users can add information to the lab user's private space. The most relevant lab information can be automatically pushed to the lab user's public space based on the lab user's proximity.

[0040] One of the main advantages of the present disclosure is that it can improve laboratory work efficiency through these intuitive interactions. In other words, the smart laboratory system can know: 1) who is interested in what, 2) who has what skills, 3) who is doing what work in which location, and 4) who needs what information at what specific time.

[0041] Therefore, if there is an event that a lab user needs to handle, the smart lab system can determine who is the right person to notify and how to notify them (for example, through private or public notification). If a lab user is performing a task, the smart lab system also has the ability to determine what information the lab user may need at each step of the task.

[0042] The system and method provide a solution that can help achieve maximum efficiency in the laboratory without relying solely on specific laboratory roles in certain areas, and can help support laboratory systems by enhancing the tasks of multidisciplinary teams at maximum performance.

[0043] Now turn Figure 2 , Figure 2 The architecture of the smart lab system is shown 200. The architecture consists of five main components.

[0044] The first component is the perception component 210. The perception component 210 provides information about contextual / environmental data occurring outside the lab system. Within this component 210, the smart lab employs various means to extract in-situ SLAT (subject, location, activity, and time) contextual data, such as identity, location, motion, duration, and interaction. In one embodiment, lab users can be identified through login data on lab equipment. In another embodiment, lab users can be identified through their wearable devices. Indoor positioning systems can be used to extract the absolute location of lab users. Based on the lab layout, the absolute location of lab users can be converted to a location relative to predefined locations, such as lab instrument locations, desks, or any other relevant objects in the lab. Motion sensors within the lab can also be used to detect motion, such as the direction of movement of lab users. This information can be calculated from tracked real-time location. Location data can also be used to calculate time spent in certain locations. On-screen interaction data can be used to calculate time spent on specific screens. Furthermore, a lab user's interactions with the lab system can provide context about the lab user's current activities.

[0045] The second component is the user modeling component 220. In this component 220, each lab user can be modeled. An a priori model is initially constructed based on known data about each lab user (e.g., demographics, preferences, and roles). This user model can be continuously configured using in-situ contextual information received from the perception component 210. In this way, each lab user can be modeled using the lab user's work habits and activities. This user model can also be updated as the lab system learns about each lab user.

[0046] The third component is the lab system awareness component 230. The lab system awareness component 230 provides information about data occurring within the lab system itself. Within this component 230, the lab system operates and becomes self-aware of what it is currently doing (i.e., status), how the lab system is performing (i.e., performance), whether lab user intervention is required in the lab (i.e., reminders and alerts), and what documentation lab users may need during their interactions with the lab (i.e., help). All of this information is fed or communicated to the fourth component, the notification logic component 340.

[0047] The notification logic component 240 includes a constantly changing, in-situ contextual state of all lab users and lab systems, as well as algorithms that determine what, where, and how information should be displayed to which lab user at a given time. The notification logic component 240 receives input from the perception component 210 and the lab awareness component 230 and provides instructions to the fifth component, the presentation component 250, on how to present information. This algorithm can be powered by machine learning so that it is enriched through usage and can improve as the algorithm gains experience through such usage. Use of this algorithm can create a secure database for generating statistics and / or predictions and improving service between customers and suppliers.

[0048] The fifth component is the presentation component 250. In this component 250, all possible presentation methods for public and private space notifications are defined. Public space notifications can include, for example, monitoring displays located throughout the lab, voice assistants located throughout the lab, lab equipment displays, and alarms. Private space notifications can include, for example, smartphones, tablets, laptops and desktops, wearable devices such as smartwatches or Google Glass, and virtual spaces enabled by virtual or augmented reality. Private notifications for a lab user typically provide confidential information for that specific lab user. The lab user can switch between private and public presentation of notifications and data as needed. For example, at the lab user's request, the lab user can upload data currently belonging to the lab user's private notifications as the lab user's public notifications. Conversely, the lab user can download data currently belonging to the lab user's public notifications as the lab user's private notifications. The lab user can exchange information between the private space and the public space using different data transmission mechanisms. For example, data transmission can be through image processing and / or proximity connections.

[0049] Furthermore, the smart lab system architecture 200 may further include a database 260 for storing in-situ contextual data from the sensing component 210 and lab equipment status data from the lab system awareness component 230. Furthermore, the performance and efficiency of lab users performing tasks may be measured and stored in the database 260 by the smart lab system.

[0050] Figure 3 A flow chart illustrating a method of presenting laboratory data to a laboratory user by using proximity interaction for troubleshooting.

[0051] The method of presenting lab data to a lab user begins by loading a first initial user model in step 300. The first initial user model can be based on, for example, the lab user's personal demographics, preferences, and lab role.

[0052] In the next step 310, multi-channel sensors throughout the lab are initialized to collect in-situ data as data is produced within the lab. In-situ contextual data can be collected from the multi-channel sensors, which can be, for example, wearable devices, indoor positioning devices, motion sensors, lab user location data, lab user interactions, and combinations thereof. The in-situ data can include data about lab users, their locations, their activities, and time.

[0053] In the next step 312, the user model is updated by using the work habits and usual laboratory activities of each individual laboratory user detected using the multi-channel sensor and stored in the database. In addition, in step 314, the in situ / SLAT data is simultaneously updated and stored.

[0054] Next, in step 316, it is determined whether the lab user is interacting with any lab equipment in the lab. If it is determined that the lab user is interacting with a lab equipment, lab equipment information is provided to the lab user via private and public notifications based on the lab user's user profile. The information provided in public and private notifications can be predefined by default. Public data can be considered data that all lab users of the lab system may need to view, such as operating instructions and helpful tips. This public data can be presented to the lab user, for example, on monitoring displays located throughout the lab, voice assistant devices, lab equipment displays, alarms, or any combination thereof. Private data can be presented to the lab user, for example, on the lab user's smartphone, tablet, laptop, desktop, wearable smart device, virtual space, or any combination thereof. The lab user can also, upon request, upload data currently provided as a private notification to the lab user so that it can be provided as a public notification to the lab user. In other words, if it is detected that the lab user is interacting with a lab equipment, the correct information will be pushed to the correct method to notify the lab user based on the user profile of that specific lab user.

[0055] Furthermore, the development and efficiency of tasks performed by laboratory users are measured by the intelligent laboratory system under continuous improvement criteria to ensure continuous optimization and effective performance. The development and efficiency of tasks performed by laboratory users can also be saved by the laboratory system, for example in a database.

[0056] In step 320, it can be determined whether the lab user is en route to perform a lab task. If it is detected that the lab user is en route to perform a task, information is pushed to the lab user's notification based on the lab user's SLAT (Subject, Location, Activity, and Time). In addition, when the lab user is en route to perform a task, information about the need to perform the task is deleted from the lab user's private notification in step 322, and the lab user receives information about the task based on the updated in-situ data in step 324. This information may include, for example, navigation assistance, directions to the task location, and operational instructions on how to perform the task.

[0057] If the lab user has not interacted with any lab equipment, or is not on the way to performing a lab task, the lab user may wish to terminate the method at 326. If the lab user does not wish to terminate the method, steps 314 through 326 are repeated until the lab user requests termination.

[0058] If the lab user does request termination in step 326 , the in-situ data is saved in step 330 and the user-specific model is updated in step 312 .

[0059] Concurrently with step 310 , after the first initial user model is loaded, the laboratory system is initialized in step 332 .

[0060] After the laboratory system is initialized, in step 334, the laboratory equipment awareness component is updated, including the current status of the laboratory, the current performance of the laboratory, whether laboratory user intervention is required, what alarms are needed to remind the laboratory user that intervention is required, and what files, i.e., help, the laboratory user may need in interacting with the laboratory equipment, i.e., performing tasks.

[0061] After the lab device awareness component is updated, in step 336 , the public notifications to the lab users are updated with the standard predefined configuration, and in step 338 , the private notifications to the lab users are also updated according to the lab users' preferences.

[0062] At step 340, a determination is made as to whether laboratory user intervention is required. If troubleshooting of a problem within the laboratory is required (e.g., in the event of a laboratory instrument failure or a laboratory user requiring assistance), laboratory user intervention may be required based on a number of factors (e.g., laboratory performance, laboratory instrument status), or any combination thereof. If laboratory user intervention is not currently required within the laboratory, steps 336 to 340 are repeated.

[0063] If the lab system requires lab user intervention, the lab system can analyze and determine the correct lab user, determine the appropriate lab user to provide intervention in step 342 by examining the current in-situ data, and update the private notification to the lab user in step 344 to provide appropriate lab user intervention information.

[0064] In step 346, the lab system may determine whether the lab user wishes to terminate the method. If the lab user does not wish to terminate the method, steps 334 through 346 are repeated until the lab user ultimately requests termination of the method.

[0065] If the lab user requests termination at step 346 , the method is terminated at step 328 , the in-situ data is saved at step 330 and the user-specific model is updated at step 312 .

[0066] Use Cases Private notification to users based on SLAT Figure 4A use case is presented in which a laboratory technician 410 has just completed a laboratory task and is walking through the laboratory 400 and passing the reagent storage area 420. At this time, a laboratory device 430 in the laboratory 400 needs to be loaded with reagents. For example, a public notification can be provided on a display 440, including monitoring displays, that is, displays throughout the laboratory, and the display of the laboratory device 430 that needs the reagent to publicly provide the notification. Since the laboratory technician 410 is currently idle and is located closest to the reagent storage 420 among all the laboratory technicians in the laboratory 400, the laboratory technician 410 receives a private notification on his / her device 450. The laboratory technician 410 can then decide to accept the task. If the laboratory technician 410 decides to take on the task, the laboratory technician 410 can retrieve the necessary complete reagent from the reagent storage 420 and can move to the laboratory device 430 that needs the new reagent. Because the smart lab system knows that the lab technician 410 has accepted the task and will complete it, each time the lab technician 410 passes by a monitoring display in the lab 400, the monitoring display provides the lab technician 410 with directions to lab equipment in the lab 400 that requires a reagent 430. The directions provided to the lab technician 410 may be indicated visually, such as by a directional arrow displayed on the instrument's monitor or by a flashing light, audibly, such as by a sound (e.g., a beep) emitting from the lab equipment 430 that requires maintenance, tactilely, such as by sensors placed throughout the lab 400, or by any other potential placement of indicators that will allow the lab technician 410 to easily locate the lab equipment in the lab 400 that requires a reagent 430.

[0067] Support for novice users like Figure 5 As shown, lab intern 510 has been with lab 500 for a week. Although lab intern 510 has received training on how to use lab equipment 520, lab intern 510 is far from proficient. The smart lab system detects that lab intern 510 is a novice based on lab intern 510's user profile. As lab intern 510 interacts with lab equipment 520, especially when completing complex tasks, lab intern 510 receives additional help or guidance 530 to help them complete the task. Lab intern 510's user profile can automatically evolve as lab intern 510 becomes more proficient. As the system continuously evaluates lab intern 510's performance and learning, at some point, the guidance for the novice will no longer be displayed.

[0068] Support Representative like Figure 6As shown, after the service representative 610 enters the lab 600, the service representative 610 receives a service task 620 from his private space device. Because the service representative 610 is the only service user in the lab 600, the service task 620 will not be provided on the public monitoring device. Figure 4 Similarly, in the illustrated use case, when a service representative 610 approaches a lab device 630 requiring service, a public monitoring device, such as a monitoring screen, indicates the location of the lab device 630 requiring service within the lab 600. This location can be indicated visually, such as by a directional arrow displayed on the instrument's monitor or by a flashing light; auditorily, such as by a sound such as a beep emitted by the lab device 630 requiring service; tactilely, such as by sensors placed throughout the lab 600; or by any other possible indicator that enables the service representative 610 to easily locate the lab device 630 requiring service within the lab 600. When the service representative 610 reaches the lab device 630 requiring service, the lab device display 640 provides further details regarding the service task, the problem, possible instructions, and the like. For example, these details can be provided on the display screen of the lab device 630 requiring service. The service representative 610 can then download key technical details to their private space by clicking on the lab device 630, allowing the service representative 610 to search for more information about the lab device 630 when needed.

[0069] Support for lab managers like Figure 7 As shown, laboratory manager 710 continuously makes critical decisions based on the status of laboratory 700 managed by laboratory manager 710 to ensure that laboratory 700 efficiently delivers results. For example, the smart lab system can privately notify laboratory manager 710 that the throughput of laboratory 700 has significantly decreased. This may occur, for example, due to a transport congestion 720 on the way to analyzer 740, resulting in laboratory samples not reaching analyzer 740 in a timely manner.

[0070] The smart lab system can then provide the lab manager 710 with at least two options as backup solutions for increasing throughput based on intelligent algorithms via private notification 730. The lab manager 710 can then decide between the provided options and assign a responsible individual in the lab 700, such as a lab technician 750, to correct the problem. The smart lab system can then send a notification to the responsible individual 750, informing them of the lab manager's 710 decision. The lab manager 710 can make such decisions remotely, without having to be near the lab instruments 740 in the lab 700 or even physically present in the lab area 700. These decisions can be based on previous choices made by the lab manager 710 and options that the smart lab system deems appropriate and can improve overall lab performance.

[0071] The present invention further discloses a computer program product, which includes the following instructions: these instructions, when executed by the control unit of the analytical laboratory, cause the analytical laboratory to perform the steps of any one of the methods disclosed herein. Therefore, specifically, a computer or computer network (such as cloud computing services) or any suitable data processing equipment can be used to perform one, multiple or even all of the method steps disclosed herein. As used herein, a computer program product may refer to a program as a tradable product. The product can generally be present on a local computer-readable data carrier or at a remote location (cloud) in any format, such as in the format of a downloadable file. The computer program product can be stored on a non-transient computer-readable data carrier, on a server computer, and on a transient computer-readable data carrier such as a data carrier signal. Specifically, the computer program product can be distributed on a data network. In addition, the computer program product and the execution hardware can be located locally or remotely, such as in a cloud environment.

[0072] The present invention further discloses and proposes a non-transitory computer-readable storage medium comprising instructions that, when executed by a control unit of an analytical laboratory, cause the analytical laboratory to perform the steps of any one of the methods disclosed herein.

[0073] The present invention further discloses and proposes a modulated data signal comprising instructions which, when executed by a control unit of an analytical laboratory, cause the analytical laboratory to perform the steps of any one of the methods disclosed herein.

[0074] It should be noted that terms such as "preferably," "generally," and "typically" are not used herein to limit the scope of the claimed embodiments or to imply that certain features are critical, essential, or even important to the structure or function of the claimed embodiments. Rather, these terms are merely intended to highlight alternative or additional features that may or may not be used in a particular embodiment of the present disclosure.

[0075] For the purposes of describing and defining this disclosure, it is noted that the term "substantially" is utilized herein to represent the inherent degree of uncertainty that may be attributed to any quantitative comparison, value, measurement, or other representation. The term "substantially" is also utilized herein to represent the degree by which a quantitative representation may vary from a stated reference without resulting in a change in the basic function of the subject matter at issue.

[0076] Having described the present disclosure in detail with reference to specific embodiments thereof, it will be apparent that modifications and variations are possible without departing from the scope of the present disclosure as defined in the appended claims. More specifically, although some aspects of the present disclosure are identified herein as preferred or particularly advantageous, it is contemplated that the present disclosure is not necessarily limited to these preferred aspects of the present disclosure.

Claims

1. A system for presenting laboratory data to a laboratory user, the system comprising: a perception component configured to continuously collect in-situ contextual data about the laboratory and users of said laboratory; a user modeling component configured to communicatively receive the in-situ contextual data from the perception component to create a user-specific model for each lab user in the lab; a lab-equipment awareness component configured to monitor status, performance, alarms, and / or maintenance of lab-equipment within the laboratory; a notification component configured to communicatively receive the in-situ context data from the sensing component and the lab-device status data from the lab-device awareness component, and configured to process and determine which of these data from the in-situ context data and the lab-device status data are to be presented to the lab user; as well as A presentation component is communicatively connected to the notification component and configured to present processed data from the notification component to the lab user, wherein the presented data includes both public notifications and private notifications of data destined for the lab user.

2. The system of claim 1, wherein the in-situ contextual data comprises data of a laboratory user. 3 . The system of claim 1 , wherein the in-situ contextual data comprises data of a laboratory user, a location of a laboratory user, and / or an activity of a laboratory user.

4. The system of claim 1, wherein the in-situ contextual data is collected from at least one of: a wearable device, an indoor positioning device, a motion sensor, laboratory user location data, laboratory user interaction with the laboratory, and a combination thereof.

5. The system of any one of claims 1 to 4, wherein the laboratory user switches between private and public notification of data.

6. The system according to any one of claims 1 to 4, wherein private notification and public notification of data are predefined.

7. The system of any one of claims 1 to 4, wherein private notification of data is presented to the laboratory user on a smartphone, tablet computer, laptop computer, desktop computer, wearable smart device, virtual space, or any combination thereof.

8. The system of any one of claims 1 to 4, wherein public notification of data is presented to the laboratory user on monitoring displays located throughout the laboratory, voice assistant devices located throughout the laboratory, laboratory equipment displays, alarms, or any combination thereof.

9. The system according to any one of claims 1 to 4, wherein the publicly notified data is data that can be seen by all laboratory users of the system.

10. The system according to any one of claims 1 to 4, further comprising: A database for storing the in-situ context data received from the sensing component and the laboratory-device status data received from the laboratory-system awareness component.

11. A method for presenting laboratory data to a laboratory user, the method comprising: a) loading a first initial user model; b) Initialize multi-channel sensors positioned throughout the laboratory to collect in-situ contextual data as it occurs; c) updating the user model by using the work habits and typical laboratory activities of each individual laboratory user; d) updating the in-situ context data; e) determining whether the lab user is interacting with a lab device of the lab; f) if the lab user is interacting with a lab device located in the lab, providing device information to the lab user through private notification and public notification based on the user model of the lab user; g) determining whether the laboratory user is in the process of performing a task in the laboratory; h) if the lab user is on the way, removing the notification about the task to be performed from the lab user's private notification, and reporting information about the task to the lab user based on the updated in-situ context data; i) terminating the method if requested by the lab user, or otherwise repeating steps c) to h) until the lab user requests termination; and j) Saving the in-situ context data and updating the user-specific model. The method of claim 11 , wherein the in-situ contextual data comprises data of a laboratory user.

13. The method of claim 11, wherein the in-situ contextual data comprises data of a laboratory user, a location of a laboratory user, and / or an activity of a laboratory user.

14. The method of claim 11, wherein the in-situ contextual data is collected from at least one of: a wearable device, an indoor positioning device, a motion sensor, laboratory user location data, laboratory user interaction with the laboratory, and a combination thereof.

15. The method according to any one of claims 11 to 14, further comprising: The degree to which the lab user completes the task is measured and the efficiency is stored in a database.

16. The method according to any one of claims 11 to 14, further comprising: The data, which is currently a private notification, is uploaded to the lab user so that upon request of the lab user the data is also provided to the lab user as a public notification.

17. The method of any one of claims 11 to 14, wherein the first initial user model is based on the laboratory user's personal demographics, preferences, and laboratory role.

18. The method of any one of claims 11 to 14, wherein the in-situ context data comprises data of the lab user, a location of the lab user, an activity of the lab user, and a time.

19. The method of any one of claims 11 to 14, wherein the private notification to the laboratory user provides confidential information to the laboratory user.

20. The method according to any one of claims 11 to 14, further comprising: k) initializing the laboratory system after loading the first initial user model; l) Update the laboratory equipment awareness model; m) updating public notifications to users of said laboratory with a standard predefined configuration; n) updating the private notification of the laboratory user according to the preferences of the laboratory user; o) determining whether intervention by a user of the laboratory is required; p) if no intervention from the laboratory user is required, repeating steps m) to o); q) if intervention from the lab user is required, examining the current in-situ contextual data to determine an appropriate lab user to provide the intervention, and updating a private notification to the lab user to provide appropriate user information; r) determining whether the laboratory user wishes to terminate the method; as well as s) If the laboratory user does not want to terminate the method, steps 1) to r) are repeated until the laboratory user wants to terminate the method.

Images