System and method for presenting laboratory data to laboratory users

Abstract

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

Description

Technical Field

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

[0002] Typical known laboratory systems strive to facilitate laboratory information monitoring practices in laboratory environments. In these known laboratory systems, laboratory information that is typically displayed to a user is 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, the laboratory system disclosed in the patent application with the publication number of US 2016 / 246364 adopts the screen conversion and interaction based on the distance. In addition, the laboratory system disclosed in the patent application with the publication number of US 2017 / 0228508 focuses on retrieving medical data based on the proximity between the medical monitoring device and the 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] "A" or "an" may be used to describe elements and components of the embodiments described herein. This is done only for convenience and to provide a general understanding of the concept of the present invention. The explanation 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 cause to be performed 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 in this specification 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, transportation, re-capping, de-capping, temporary storage / buffering, archiving (refrigerated or not), retrieval and / or disposal.

[0008] The term "pre-analytical instrument" as used herein 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 steps. 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 measured 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 parameters of a sample or at least one analyte and return the measured 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 the concentration above the detection level), optical parameters, DNA or RNA sequences, data obtained by mass spectrometry of proteins or metabolites, and various types of physical or chemical parameters. The analytical instrument may include a unit that helps to pipette, feed and mix samples and / or reagents. The analyzer may include a reagent holding unit that holds reagents used to perform the assay. 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, and its 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, used to detect the results of a chemical or biological reaction or to monitor the progress of a chemical or biological reaction.

[0010] The term "laboratory middleware" as used in this specification may refer to any physical or virtual processing device that can be configured to control a laboratory instrument or a system including 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 perform pre-analysis, post-analysis, and analysis workflows / workflow steps. The laboratory middleware may receive information from a data management unit regarding which steps need to be performed on a particular sample. In some embodiments, the laboratory middleware may be integrated with the data management unit, may be composed of a server computer, and / or may be part of a laboratory instrument, or may even be distributed among multiple instruments in a laboratory system. The laboratory middleware may, for example, be implemented as a programmable logic controller running a computer-readable program provided with instructions for performing operations.

[0011] The present invention proposes a system for presenting laboratory data to laboratory users. The system may include a perception component configured to continuously collect in-situ context data about the laboratory and laboratory users; a user modeling component configured to receive the in-situ context 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 context data from the perception component and the laboratory equipment status data from the laboratory equipment awareness component, and process and determine which of these data in the in-situ context data and the laboratory equipment status data will be presented to the laboratory user; and a presentation component configured to present the processed data from the notification component to the laboratory user, wherein the presented data includes both public notifications and private notifications of the data to the laboratory user.

[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, biometrics of lab users (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 pre-defined. 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., beeps), 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 proposes a method for presenting laboratory data to laboratory users. The method may include loading a first initial user model; initializing multi-channel sensors throughout the laboratory to collect in-situ data when data occurs; updating the user model by using the work habits and usual laboratory activities of each individual laboratory user, and updating the in-situ data; determining whether the laboratory user is interacting with laboratory equipment, and if the laboratory user is interacting with laboratory equipment, providing equipment information to the laboratory user through private and public notifications based on the user model of the laboratory user; determining whether the laboratory user is on the way to perform a task in the laboratory, and if the laboratory user is on the way, 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 of laboratory users in completing 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 to the laboratory user to the private notification of the laboratory user based on the 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 individual demographics, preferences, and laboratory roles of the lab users. 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 time.

[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 equipment 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:

[0024] Figure 1 The diagram shows the information interaction flow between various objects in a laboratory according to an embodiment of the present disclosure.

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

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

[0027] Figure 4 A scenario of privately notifying a lab user based on SLAT (subject, location, activity, and time) according to an embodiment of the present disclosure is shown.

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

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

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

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

[0032] 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 possible different types of lab information required by different lab user roles.

[0033]

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

[0035] As can be seen in Table 1, laboratory users require a variety of information, including information about other laboratory users in order to coordinate the workload between 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 pre-analytical instrument will need to know whether the analytical instrument is ready to receive the pre-processed specimen from the pre-analytical instrument 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 need information about the laboratory users so that the laboratory system can notify and provide laboratory information that is most appropriate for each laboratory user's role.

[0036] First reference Figure 1 , Figure 1The figure illustrates how information flows to address the needs of different entities in the laboratory. As shown, the 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 and to the laboratory users 100. An ideal intelligent laboratory system 110 can facilitate information interaction, such as Figure 1 Today's laboratory automation system 110 is born to support the interaction between different laboratory components.

[0037] In short, the lab user 100 can work in a coordinated manner with the lab system 110 and other lab users 100. This suggests that there needs to be a certain level of "awareness" between the lab user and the lab system. Here, awareness refers to knowing what other lab users are doing and what the lab instrument system is doing. It is important to support lab user awareness and push the right information to the right lab user to complete the right task at the right time and in the right place in the lab.

[0038] 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.

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

[0040] The 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 is a registered Lab User of the Lab System for security reasons and to maintain the integrity of the information. 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 actively choose to "upload" information from the Lab User's Private Space to the Public Space. If the Lab User chooses to upload information from the Lab User's Private Space to the Public Space, the Lab User's registration will be accompanied by the upload for the purpose of tracking errors, i.e., the wrong private information is uploaded or uploaded to the wrong location in the Public Space.

[0041] In contrast, a public space can be an interactive space where each individual lab user or consumer can interact publicly. Information in a public space can also be publicly ingested. In other words, all lab users are able to perceive, i.e., see and / or hear, the information in the public space. Public information can also be transmitted and / or saved to a 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, a 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.

[0042] One of the main advantages of the present disclosure is that it can improve the efficiency of laboratory work 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 position, and 4) who needs what information at what specific time.

[0043] Thus, 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 (e.g., 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.

[0044] 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.

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

[0046] The first component is the perception component 210. The perception component 210 provides information about contextual / environmental data that occurs outside the laboratory system. In this component 210, the smart laboratory uses various means to extract in-situ SLAT (subject, location, activity, and time) context data, such as identification, location, motion, duration, and interaction. In one embodiment, the laboratory user can be identified by the login data on the laboratory equipment. In another embodiment, the laboratory user can be identified by the wearable device of the laboratory user. The indoor positioning system can be used to extract the absolute position of the laboratory user. Based on the layout of the laboratory, the absolute position of the laboratory user can be converted to a position relative to a predefined position, such as the location of laboratory instruments, desks, or any other relevant objects in the laboratory. Motion sensors within the laboratory can also be used to detect motion, such as the direction of movement of the laboratory user. Such information can be calculated through the tracked real-time location. The location data can also be used to calculate the time spent in certain locations. The interaction data on the screen can be used to calculate the time spent on a specific screen. In addition, the interaction of the laboratory user with the laboratory system can also provide context about the activities that the laboratory user is currently engaged in.

[0047] The second component is the user modeling component 220. In this component 220, each lab user can be modeled. A priori models are initially built based on known data (e.g., demographics, preferences, and roles) for each lab user. The user model can be continuously configured with in-situ context 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. The user model can also be updated as the lab system learns about each lab user.

[0048] 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. In this component 230, the lab system operates and is 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 files a lab user may need during their interaction with the lab (i.e., help). All of this information is fed or communicated to the fourth component, the notification logic component 340.

[0049] The notification logic component 240 includes maintaining an ever-changing in-situ contextual state of all lab users and lab systems, and algorithms that decide what, where, and how information is 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 the information. The algorithm can be supported by machine learning so that it enriches itself through use and can be improved as the algorithm gains experience through this use. The use of the algorithm can create a secure database to generate statistics and / or predictions and improve services between customers and suppliers.

[0050] The fifth component is a presentation component 250. In this component 250, all possible presentation modes are defined for public space and private space notifications. Public space notifications may include, for example, monitoring displays positioned throughout the laboratory, voice assistants positioned throughout the laboratory, laboratory equipment displays, and alarms. Private space notifications may include, for example, wearable devices such as smartphones, tablets, laptops and desktops, smart watches or Google Glass, and virtual spaces enabled by virtual or augmented reality. Private notifications to laboratory users typically provide confidential information for that particular laboratory user. Laboratory users can switch between private and public presentations of notifications and data as needed. For example, a laboratory user can upload data currently belonging to a private notification of the laboratory user as a public notification for the laboratory user at the request of the laboratory user. Conversely, a laboratory user can also download data currently being publicly notified to the laboratory user as a private notification for the laboratory user. Laboratory users can exchange information between private and public spaces according to different data transmission mechanisms. For example, data transmission can be through image processing and / or proximity connections.

[0051] In addition, the smart lab system architecture 200 may also include a database 260 for storing in-situ context data from the sensing component 210 and lab equipment status data from the lab system awareness component 230. In addition, the development and efficiency of lab users performing tasks may be measured and stored in the database 260 by the smart lab system.

[0052] Figure 3 A flow chart of a method for presenting lab data to a lab user by troubleshooting using proximity interaction is shown.

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

[0054] 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 may be collected from multi-channel sensors, which may be, for example, wearable devices, indoor positioning devices, motion sensors, lab user location data, lab user interactions, and combinations thereof. In-situ data may include data about lab users, locations of lab users, activities of lab users, and time.

[0055] 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 by the multi-channel sensor and stored in the database. In addition, in step 314, the in-situ / SLAT data is simultaneously updated and stored.

[0056] Next, in step 316, it is determined whether the laboratory user is interacting with any laboratory equipment in the laboratory. If it is determined that the laboratory user is interacting with the laboratory equipment, the laboratory equipment information is provided to the laboratory user through the private notification and public notification of the laboratory user according to the user model of the laboratory user. The information provided by the public notification and the private notification can be predefined by default. Public data can be considered as data that all laboratory users of the laboratory system may need to view, such as operating instructions and useful tips. The public data can be presented to the laboratory user, for example, on a monitoring display, a voice assistant device, a laboratory equipment display, an alarm, or any combination thereof located throughout the laboratory. Private data can be presented to the laboratory user, for example, on a laboratory user's smartphone, a tablet computer, a laptop, a desktop, a wearable smart device, a virtual space, or any combination thereof. The laboratory user can also upload the data currently provided as a private notification to the laboratory user according to the laboratory user's request to provide it as a public notification for the laboratory user. In other words, if it is detected that the laboratory user is interacting with the laboratory equipment, the correct information will be pushed to the correct method of notifying the laboratory user according to the user model of the specific laboratory user.

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

[0058] In step 320, it may be determined whether the lab user is on the way to perform a lab task. If it is detected that the lab user is on the way 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 on the way to perform a task, the information about the need to perform the task will be deleted from the lab user's private notification in step 322, and the lab user will receive information about the task based on the updated in-situ data in step 324. The information may include, for example, navigation assistance, directions to the task location, and operational instructions on how to perform the task.

[0059] If the lab user is not interacting with any lab equipment, or is not on the way to perform 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.

[0060] 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 .

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

[0062] 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 the interaction with the laboratory equipment, i.e., task execution.

[0063] 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.

[0064] At step 340, it is determined 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 (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 in the laboratory, steps 336 to 340 are repeated.

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

[0066] In step 346, the lab system may determine whether the lab user wishes to terminate the method. If the lab user does not want to terminate the method, steps 334 to 346 are repeated until such time as the lab user ultimately requests to terminate the method.

[0067] 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 .

[0068] Use Cases

[0069] Private notification to users based on SLAT

[0070] Figure 4A use case is presented in which a laboratory technician 410 has just completed a laboratory task and is walking in the laboratory 400 and passing through 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 a monitoring display, i.e., a display that is spread over the entire laboratory, and a display of the laboratory device 430 that needs reagents publicly provides the notification. Since the laboratory technician 410 is currently idle and is located at the position closest to the reagent storage 420 among all the laboratory technicians in the laboratory 400, the laboratory technician 410 receives private notifications on his / her equipment 450. Then, the laboratory technician 410 can decide to accept the task. If the laboratory technician 410 decides to undertake the task, the laboratory technician 410 can retrieve the necessary complete reagents from the reagent storage 420, and can move to the laboratory device 430 that needs new reagents. Since the smart lab system knows that the lab technician 410 has accepted the task and is about to 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 reagents 430. The directions provided to the lab technician 410 may be indicated visually, such as by a directional arrow displayed on the monitor of the instrument or by a flashing light, audibly, such as by a sound (e.g., a beep) emitted by 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 reagents 430.

[0071] Support for novice users

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

[0073] Support Representative

[0074] like Figure 6 As shown, after the service representative 610 enters the laboratory 600, the service representative 610 receives the service task 620 from his private space device. Because the service representative 610 is the only service user in the laboratory 600, the service task 620 will not be provided on the public monitoring device. Figure 4 Similarly to the illustrated user case, when the service representative 610 walks up to the lab equipment 630 that needs service, the public monitoring device, such as a monitoring screen, will indicate the location of the device 630 that needs service in the lab 600. The location can be indicated visually, such as by a directional arrow displayed on the monitor of the instrument or by a flashing light, auditorily, such as by the lab equipment 630 that needs service emitting a sound such as a beep, tactilely, such as by sensors placed throughout the lab 600, or by any other possible indicator that enables the service representative 610 to easily find the lab equipment 630 that needs service in the lab 600. When the service representative 610 arrives at the lab equipment 630 that needs service, the lab equipment display 640 will provide more details related to the service task, the problem, possible instructions, etc. For example, these details can be provided on the display screen of the lab equipment 630 that needs service. The service representative 610 can then download key technical details to his private space by clicking his device on the lab equipment 630 so that the service representative 610 can search for more information about the lab equipment 630 when needed.

[0075] Support for laboratory managers

[0076] like Figure 7 As shown, the laboratory manager 710 continuously makes key decisions based on the status of the laboratory 700 managed by the laboratory manager 710 to ensure that the laboratory 700 effectively delivers results. For example, the smart laboratory system can privately notify the laboratory manager 710 that the throughput of the laboratory 700 has dropped significantly. For example, this may occur due to a transportation jam 720 on the way to the analyzer 740, so that laboratory samples do not arrive at the analyzer 740 in a timely manner.

[0077] The smart lab system may then provide at least two options to the lab manager 710 via private notification 730 as backup solutions to increase throughput based on the smart algorithm. The lab manager 710 may then decide between the options provided and assign a responsible person in the lab 700, such as a lab technician 750, to correct the problem. The smart lab system may then send a notification to the responsible person 750 so that the person 750 is aware of the lab manager's 710 decision. The lab manager 710 may make such decisions remotely without having to be close to the lab instruments 740 in the lab 700 or even in the lab area 700. These decisions may be based on the choices previously made by the lab manager 710 and the options that the smart lab system deems appropriate and can improve overall lab performance.

[0078] 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, make the analytical laboratory 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.

[0079] The present invention further discloses and proposes a non-transitory computer-readable storage medium, which includes 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.

[0080] 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.

[0081] 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. Instead, 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.

[0082] For the purposes of describing and defining the present disclosure, it is noted that the term "substantially" is used 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.

[0083] The present disclosure has been described in detail with reference to specific embodiments of the present disclosure, and it will be apparent that modifications and variations may be made 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 (200) for presenting laboratory data to one or more laboratory users (100), the system (200) comprising: a sensing component (210) configured to continuously collect in-situ context data about the laboratory and the laboratory user (100), wherein the in-situ context data includes data of the laboratory user (100), the location of the laboratory user, the activity of the laboratory user, and time; a user modeling component (220) configured to communicatively receive the in-situ context data from the perception component (210) to create a user-specific model for each lab user (100) in the lab; a lab equipment awareness component (230) configured to monitor status, performance, alarms and / or maintenance of lab equipment within the laboratory; a notification component (240) configured to communicatively receive the in-situ context data from the sensing component (210) and the lab-device status data from the lab-device awareness component (230), and configured to process these data from the in-situ context data and the lab-device status data based on the in-situ context data and the user-specific model and determine which of these data are to be presented to which lab user (100) and how these data are to be presented; as well as A presentation component (250) is communicatively connected to the notification component (240) and is configured to present processed data from the notification component (240) to the laboratory user (100), wherein the presented data includes both public notifications and private notifications of data to the laboratory user (100).

2. A system (200) according to claim 1, wherein the in-situ contextual data is collected from multi-channel sensors, such as wearable devices, indoor positioning devices, motion sensors, laboratory user location data, laboratory user interaction with the laboratory, and combinations thereof.

3. The system (200) of claim 1 or 2, wherein the laboratory user (100) switches between private notification and public notification of data.

4. The system (200) according to claim 1 or 2, wherein private notification and public notification of data are predefined.

5. The system (200) of claim 1 or 2, wherein private notification of data is presented to the laboratory user (100) on a smartphone, tablet computer, laptop computer, desktop computer, wearable smart device, virtual space, or any combination thereof.

6. A system (200) according to claim 1 or 2, wherein public notification of data is presented to the laboratory user (100) on a monitoring display located throughout the laboratory, a voice assistant device located throughout the laboratory, a laboratory equipment display, an alarm, or any combination thereof.

7. The system (200) according to claim 1 or 2, wherein the publicly notified data is data that can be seen by all laboratory users (100) of the system.

8. The system (200) according to claim 1 or 2, further comprising: A database (260) for storing the in-situ context data received from the sensing component (210) and the laboratory equipment status data received from the laboratory system awareness component (230).

9. A method (300) for presenting laboratory data to a laboratory user (100), the method (300) comprising: a) loading a first initial user model; b) initializing multi-channel sensors positioned throughout the laboratory to collect in-situ context data when data occurs, wherein the in-situ context data includes data of the laboratory user (100), the location of the laboratory user, the activity of the laboratory user, and time; c) updating the user model by using the working habits and usual laboratory activities of each individual laboratory user; d) updating the in-situ context data; e) determining whether the lab user (100) is interacting with a lab device of the lab; f) if the lab user (100) is interacting with a lab device located in the lab, providing device information to the lab user (100) through private notification and public notification based on the user model of the lab user; g) determining whether the laboratory user (100) is in the process of performing a task in the laboratory; h) if the laboratory user (100) is on the way, removing the notification about the task to be performed from the private notification of the laboratory user, and reporting information about the task to the laboratory user (100) based on the updated in-situ context data; i) terminating the method (300) if requested by the lab user (100), or otherwise repeating steps c) to h) until the lab user (100) requests termination; and j) Saving the in-situ context data and updating the user-specific model.

10. The method (300) of claim 9, further comprising: The degree to which the lab user (100) completes the task is measured and the efficiency is stored in a database (260).

11. The method (300) according to claim 9 or 10, further comprising: Data currently being uploaded as a private notification to the lab user (100) is provided to the lab user (100) as a public notification upon request of the lab user.

12. The method (300) of claim 9 or 10, wherein the first initial user model is based on personal demographics, preferences and laboratory roles of the laboratory user.

13. The method (300) according to claim 9 or 10, wherein the private notification of the laboratory user provides confidential information to the laboratory user (100).

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

Images