Laboratory coordination apparatus, method and system

Abstract

Systems, methods, and devices for laboratory coordination are provided. A laboratory coordination device may be configured to interface and communicate with a plurality of user devices and a plurality of laboratory instruments. A laboratory coordination device may be configured to coordinate activity of a plurality of laboratory instruments according to a plurality of experimental protocols obtained via the plurality of user devices. The laboratory coordination device may be further configured to provide a user interface to interface with the headless laboratory instrument.

Description

[0001] Related matters

[0002] This application claims priority to U.S. Provisional Application No. 63 / 481,512, filed January 25, 2023, entitled “Laboratory Coordination Devices, Methods, and Systems,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application generally relates to computers and computer applications, and more specifically, to a graphical user interface and a method for displaying user interaction items on said graphical user interface. This application further relates to a user interface module configured to guide a user or operator in preparing and performing one or more laboratory procedures, such as assays. Background Technology

[0004] In a wide range of applications including, but not limited to, bioanalysis, chemical analysis, radioanalysis, other scientific (e.g., bioscience and bioanalysis work), and industrial processes that result in the use of instruments and industrial process equipment for scientific testing (e.g., biological testing, bioinstruments), the present invention improves testing, analysis, and processing by integrating consistent software interfaces between various processing locations and the instruments and equipment involved in the processing.

[0005] Typically, computer systems and / or applications utilize a series of menus presented to the user to receive input and perform their functions. When the user selects an option from a list of menu items, the computer system and / or application may perform its functions based on the selected option and / or by presenting another list of menu items (e.g., a list of submenu items depending on the selected option). For example, the computer system and / or application may continue processing its menu-driven function until it completes its task. In this menu-driven system, it is common practice that previously selected options upon which the current function of the computer system and / or application depends are not visible on the user interface. Therefore, for example, at the current point in the processing of the computer system and / or application, the path of the menu item taken is not visible. Furthermore, the taken path and any unselected options within that path are also not visible on the user interface. Therefore, an improved user interface is desired.

[0006] Laboratory Information Management Systems (LIMS) are typically used in laboratories with instruments (e.g., but not limited to biological instruments) that are paired with analytical applications. The data generated by these instruments is stored as data files on a shared network drive for post-processing and import into other electronic systems. These integrations often require significant and time-consuming software development and integration to make the generated data available to end users. Typically, these data integrations occur in stringent environments (e.g., 21 CFR Part 11) where the generated data must be stored in a way that ensures it cannot be altered by end users. Furthermore, these integrations provide end users with support for post-processing the generated data for supplementary analysis, reporting, and sharing with other end users, often referred to as collaborators. Additionally, the goal is to enable a group of closely working end users to use instruments and post-process the generated data under controlled, consistent, uniform, and traceable conditions to help end users create consistent and accurate supplementary analyses and reports. Using instruments to generate data for supplemental analysis and reporting typically requires end-users to create the desired reaction using consumables (e.g., biological consumables, including but not limited to reagents and analytes) and their test samples, generating data with specific batch information used in the supplemental analysis and reporting. Obtaining these consumables requires purchasing them from a supplier, who must not only physically ship the consumables to the end-user but also provide the specific batch information for these shipped consumables, enabling the end-user to use the consumables on the instrument and perform the desired post-processing. In addition to normal instrument use and related consumables, there are usually important support functions to ensure that the best-performing instruments and / or related consumables are always provided to the customer. The workflow integration required for optimal performance of instruments by end-users is very high and complex, necessitating a simple and easy-to-use user interface to guide users through all the complexities of the analytical workflow. Therefore, there is a need for improved analytical computing systems and user interfaces that encompass instruments and related consumables.

[0007] Similar difficulties exist in fields outside the instrumentation domain. For example, workflow integration, parts tracking, consumables tracking, work-in-process tracking, process and parts production documentation, and all the aforementioned instrumentation-related issues present challenges in various manufacturing settings. Furthermore, this application provides solutions for consumer needs in areas such as organizing, prioritizing, and improving workflows in business, office, home, travel, and leisure settings. Other examples exist, and the solutions disclosed in this specification are not limited to the problems discussed above. Summary of the Invention

[0008] The embodiments described herein may relate to a laboratory coordination system comprising: a laboratory coordination device including: a networking component configured to send and receive information via a network; a non-transitory computer-readable storage medium configured to store software instructions; and at least one processor configured to execute the software instructions for: establishing one or more network connections with one or more laboratory instruments and / or one or more user devices; obtaining an experimental protocol comprising a plurality of experimental steps to be performed; providing a first instruction for performing a first experimental step of the plurality of experimental steps in response to a first instruction request; receiving an indication that the first experimental step has been completed; and providing a second instruction for performing a second experimental step of the plurality of experimental steps in response to a second instruction request.

[0009] The embodiments described herein may relate to a laboratory coordination system comprising: a laboratory coordination device including: a networking component configured to send and receive information via a network; a non-transitory computer-readable storage medium configured to store software instructions; and at least one processor configured to execute the software instructions for: establishing one or more network connections with one or more laboratory instruments or one or more user devices; obtaining a plurality of experimental protocols, each experimental protocol including a plurality of corresponding experimental steps to be performed on a corresponding assay plate; receiving a first identifier of a first assay plate from a first instrument of one or more instruments; selecting a first experimental protocol from the plurality of experimental protocols based on the first identifier; selecting a first experimental step from the first experimental protocol based on the capabilities of the first instrument; and providing a first instruction to the first instrument to perform the first experimental step on the first assay plate.

[0010] The embodiments described herein may relate to a laboratory coordination system comprising: a laboratory coordination device including: a networking component configured to send and receive information via a network; a non-transitory computer-readable storage medium configured to store software instructions; and at least one processor configured to execute the software instructions for: establishing one or more network connections with one or more laboratory instruments and / or one or more user devices; obtaining an experimental protocol comprising a plurality of experimental steps to be performed; providing a first instruction to a user via one or more user devices in response to a first instruction request for performing a first experimental step of the plurality of experimental steps; receiving an indication that the first experimental step has been completed; and providing a second instruction to a user via one or more user devices in response to a second instruction request for performing a second experimental step of the plurality of experimental steps.

[0011] The embodiments described herein may relate to a laboratory coordination system comprising: a laboratory coordination device including: a networking component configured to send and receive information via a network; a non-transitory computer-readable storage medium configured to store software instructions; and at least one processor configured to execute the software instructions for: establishing one or more network connections with one or more instruments or one or more user devices; obtaining a plurality of experimental protocols, each experimental protocol including corresponding plurality of experimental steps to be executed; receiving a first identifier of a first assay plate from a first instrument of one or more instruments; selecting a first experimental protocol from the plurality of experimental protocols based on the first identifier; selecting a first experimental step from the first experimental protocol based on the capabilities of the first instrument; providing a first instruction to the first instrument to execute the first experimental step; and providing a second instruction to a user via one or more user devices to facilitate a second experimental step.

[0012] The embodiments described herein may relate to a laboratory coordination system comprising: a laboratory coordination device including: a networking component configured to send and receive information via a network; a non-transitory computer-readable storage medium configured to store software instructions; and at least one processor configured to execute the software instructions for: establishing one or more network connections with one or more instrument devices; obtaining a plurality of experimental protocols, each experimental protocol including a plurality of corresponding experimental steps to be performed on a corresponding assay plate; receiving a first identifier of a first assay plate from a first instrument of one or more instruments; selecting a first experimental protocol from the plurality of experimental protocols based on the first identifier; providing a first instruction to the first instrument to perform a first experimental step on the first assay plate; and providing a second instruction to the first instrument to perform a second experimental step on the first assay plate.

[0013] The embodiments described herein may relate to a computer-implemented method for laboratory coordination, performed by a laboratory coordination device including at least one processor configured to execute software instructions, the method comprising: establishing one or more network connections with one or more laboratory instruments and / or one or more user devices; obtaining an experimental protocol including a plurality of experimental steps to be performed; providing a first instruction for performing a first experimental step of the plurality of experimental steps in response to a first instruction request; receiving an indication that the first experimental step has been completed; and providing a second instruction for performing a second experimental step of the plurality of experimental steps in response to a second instruction request.

[0014] The embodiments described herein may relate to a computer-implemented method for laboratory coordination, performed by a laboratory coordination device including at least one processor configured to execute software instructions, the method comprising: establishing multiple network connections with multiple laboratory instruments and / or one or more user devices; identifying instrument types corresponding to the multiple laboratory instruments; identifying capability sets of the multiple laboratory instruments according to the multiple instrument types; obtaining multiple experimental protocols, each of which includes multiple experimental steps to be performed; and generating multiple instructions to be provided to the multiple laboratory instruments for performing the multiple experimental protocols.

[0015] Other features, structures, and operations of various embodiments are described in detail below with reference to the accompanying drawings. Attached Figure Description

[0016] Figure 1 In one embodiment, this is a method for displaying interactive items on a user interface display for computer-user interaction.

[0017] Figures 2A to 2O An example graphical user interface display is shown in one embodiment.

[0018] Figure 2P An example of a systematic user interface (Methodical user interface) including an advanced context menu is shown according to one embodiment.

[0019] Figure 3 This is a flowchart illustrating a method for interactively displaying interactive items on a user interface for computer-user interaction in another aspect.

[0020] Figure 4 A flowchart illustrating the user login interface of an analysis system in one embodiment is provided.

[0021] Figure 5 This is a flowchart illustrating a method for displaying a startup user interface screen in one embodiment.

[0022] Figure 6 This diagram illustrates the workflow of a screen defining a measurement method in one embodiment.

[0023] Figure 7 This diagram illustrates the workflow of a user interface for selecting a measurement method in one embodiment.

[0024] Figure 8 A flowchart illustrating the workflow of the user interface displayed for a defined sample in one embodiment is provided.

[0025] Figure 9This is a flowchart illustrating a workflow for verifying the operation of a defined user interface in one embodiment.

[0026] Figure 10 This is a flowchart illustrating a workflow for displaying a user interface to notify a user that a task has been completed, as shown in one embodiment.

[0027] Figure 11 A flowchart illustrating the workflow of the user interface for executing / collecting options shown in one embodiment.

[0028] Figure 12 This is a flowchart illustrating the workflow of the user interface for executing / preparing options shown in one embodiment.

[0029] Figure 13 This is a flowchart illustrating the workflow of the user interface for executing / loading options shown in one embodiment.

[0030] Figure 14 A flowchart illustrating the workflow of the user interface for executing / running options shown in one embodiment.

[0031] Figure 15 This is a flowchart illustrating the workflow of the user interface for executing / uninstalling options shown in one embodiment.

[0032] Figure 16 This is a flowchart illustrating the workflow of the user interface for executing / reviewing options shown in one embodiment.

[0033] Figure 17 This is a flowchart illustrating the workflow of the user interface for executing / reviewing options shown in one embodiment.

[0034] Figure 18 Elements of a graphical user interface (GUI) system in one embodiment are shown.

[0035] Figure 19 A schematic diagram of an example computer or processing system in one embodiment of which a graphical user interface system may be implemented is shown.

[0036] Figure 20 This is an example screenshot showing, in one embodiment, a screen where the graphics wheel / scrolling tool maximizes the black space of the screen.

[0037] Figure 21 A cloud analytics computing system is shown in one embodiment.

[0038] Figure 22 The system architecture of a cloud analytics computing system is shown in one embodiment.

[0039] Figure 23The system architecture of a cloud platform for a cloud analytics computing system is shown in one embodiment.

[0040] Figure 24 The interaction between the administrator's computer and the cloud platform is shown in one embodiment.

[0041] Figure 25 This illustration shows the interaction between the user's computer and the cloud platform in one embodiment.

[0042] Figure 26 This illustration shows the interaction between a data integration computer and a cloud platform in one embodiment.

[0043] Figure 27 This illustration shows an embodiment that supports interaction between a user's computer and a cloud platform.

[0044] Figure 28 This illustration shows the interaction between a data integration computer and a cloud platform in one embodiment.

[0045] Figure 29 This illustration shows the interaction between a computer that uploads consumable information and a cloud platform in one embodiment.

[0046] Figure 30 This illustration shows the interaction between the account information uploading computer and the cloud platform in one embodiment.

[0047] Figure 31 This illustration shows the interaction between the instrument information uploading computer and the cloud platform in one embodiment.

[0048] Figure 32 The interaction between the coordinating operating instrument computer and the cloud platform is shown in one embodiment.

[0049] Figure 33A The interaction between a personal operating instrument computer and a cloud platform is shown in one embodiment.

[0050] Figure 33B Showing targets Figure 33A The workflow of the illustrated embodiment facilitates interaction between the instrument computer and the cloud platform.

[0051] Figure 34A The first part of a software architecture for cloud platform services is shown in one embodiment.

[0052] Figure 34B Showing targets Figure 34A The second part of the software architecture of the cloud platform service in the illustrated embodiment.

[0053] Figure 35A The logical design of system data in one embodiment is shown.

[0054] Figure 35BThis illustration shows an example of using an analytics computing system to map business entities to accounts.

[0055] Figure 35C The following is a logical design of team data related to plate data in one embodiment.

[0056] Figure 35D The logical design of team data related to measurement method data is shown in one embodiment.

[0057] Figure 35E The logical design of team data related to operational data is shown in one embodiment.

[0058] Figure 35F The logical design of team data related to experimental data is shown in one embodiment.

[0059] Figure 36A An exemplary structure of a user account for an analytical computing system is shown in one embodiment.

[0060] Figure 36B This document illustrates a process for creating a user account for an analytics computing system in one embodiment.

[0061] Figure 36C The flow of a user account for an instrument combined with an analytical computing system is shown in one embodiment.

[0062] Figure 36D The flowchart of a user account in a consumables-based analytics calculation system is shown in one embodiment.

[0063] Figure 37 A module of a manager software application is shown in one embodiment.

[0064] Figure 38A This document illustrates the flow of the administrator console module in an administrator app for account administrators in one embodiment.

[0065] Figure 38B This illustrates the flow of the administrator console module in an administrator app for a team administrator in one embodiment.

[0066] Figure 38C The flow of user login processing in one embodiment is shown.

[0067] Figures 38D to 38H To show Figure 38A Screenshots showing aspects of the work experience process.

[0068] Figure 38I To display the advanced context menu for the administrator console module.

[0069] Figure 39A The flowchart of the management audit tracking module of the administrator APP in one embodiment is shown.

[0070] Figures 39B to 39E An aspect of the user interface for the management audit trail module according to an embodiment is shown.

[0071] Figure 40 A module for analyzing a user software application is shown in one embodiment.

[0072] Figure 41 The flowchart of the analysis method module for analyzing a user's APP is shown in one embodiment.

[0073] Figure 42A The design flow of the measurement method module for analyzing user APP is shown in one embodiment.

[0074] Figure 42B The review process for the measurement method module for analyzing user apps in one embodiment is shown.

[0075] Figure 43A The design flow of the experimental module for analyzing a user's app is shown in one embodiment.

[0076] Figure 43B The review process for an experimental module analyzing a user app is shown in one embodiment.

[0077] Figures 43C to 43H An aspect of the user interface of a reader module according to one embodiment is shown.

[0078] Figure 44 The flowchart of the audit trail module for analyzing user apps is shown in one embodiment.

[0079] Figure 45 A module of a coordinated operation instrument software application is shown in one embodiment.

[0080] Figure 46 The flowchart of the operation module of the coordinated operation instrument APP in one embodiment is shown.

[0081] Figure 47 The flowchart of the maintenance module of the coordinated operation instrument APP in one embodiment is shown.

[0082] Figure 48 A module of a personal operating instrument software application is shown in one embodiment.

[0083] Figure 49A The flowchart of the operation module of a personal operating instrument APP in one embodiment is shown.

[0084] Figure 49AAThe flowchart of the operation module of a personal operating instrument app in another embodiment is shown.

[0085] Figure 49B This document illustrates a process for reviewing the results of an operation module related to a board reader, which functions as a personal operating instrument (APP), in one embodiment.

[0086] Figure 50 A module of the workflow-assisting instrument software application is shown in one embodiment.

[0087] Figure 51 The flowchart of the workflow help module of the instrument APP is shown in one embodiment.

[0088] Figure 52 An example of analyzing the computational process of automatic software updates on a user's computer.

[0089] Figure 53 An example of a calculation process for automatically updating the software of an analytical instrument computer.

[0090] Figure 54 An example embodiment of a public architecture for non-biological analysis purposes of a software module in a gourmet chef app.

[0091] Figure 55 This is an example of a user experience process for meal planners, starting with a gourmet chef app.

[0092] Figure 56 A system for implementing a systematic user interface is shown according to one embodiment.

[0093] Figure 57 This demonstrates the process of navigating a hierarchical menu tree via the user interface.

[0094] Figures 58A to 58HH This is an example, non-limiting embodiment of the reader module.

[0095] Figures 59A to 59T This is an example of a non-limiting embodiment of the experimental module.

[0096] Figures 60A to 60I This is an exemplary, non-limiting embodiment of the maintenance module.

[0097] Figures 61A to 61Q This is a sample, non-limiting embodiment of the administrator console module.

[0098] Figures 62A to 62P Examples of non-limiting embodiments of general screenshots applicable to multiple modules in this specification.

[0099] Figure 63 This is a sample, non-limiting embodiment of the audit trail module.

[0100] Figures 64A to 64RR This is an example of a non-limiting embodiment of the determination method module.

[0101] Figure 65 The UI display of the conformal collection and preparation module in one embodiment is shown.

[0102] Figure 66 The UI display of the conformal collection and preparation module in one embodiment is shown.

[0103] Figure 67 The UI display of the conformal collection and preparation module in one embodiment is shown.

[0104] Figure 68 The UI display of the conformal collection and preparation module in one embodiment is shown.

[0105] Figure 69 The UI display of the conformal collection and preparation module in one embodiment is shown.

[0106] Figure 70 The UI display of the conformal collection and preparation module in one embodiment is shown.

[0107] Figure 71 The UI display of the conformal collection and preparation module in one embodiment is shown.

[0108] Figure 72 The UI display of the conformal collection and preparation module in one embodiment is shown.

[0109] Figures 73A to 73C A laboratory system configured to perform a measurement procedure is shown.

[0110] Figures 73D to 73F The components of a laboratory system conforming to an embodiment of the present invention are shown.

[0111] Figure 74 The UI display of the conformity determination guidance module in one embodiment is shown.

[0112] Figure 75 The UI display of the conformity determination guidance module in one embodiment is shown.

[0113] Figure 76 The UI display of the conformity determination guidance module in one embodiment is shown.

[0114] Figures 77(a) to 77(c) The UI display of the instrument submodule conforming to the measurement guidance module in one embodiment is shown.

[0115] Figure 78 This illustrates the workflow of multiple users interacting with a coordination server according to an embodiment of the present invention. Figures 79A to 79DThe operating mode of a laboratory system according to an embodiment of the present invention is shown.

[0116] Figures 80A to 80C The operation method of the laboratory coordination device according to an embodiment of the present invention is shown.

[0117] Figure 81A The measurement scheduling operation according to an embodiment of the present invention is illustrated.

[0118] Figure 81B The measurement execution operation according to an embodiment of the present invention is illustrated.

[0119] Figure 82 The offline operation mode of the laboratory coordination device according to an embodiment of the present invention is shown.

[0120] Figure 83 The online operation mode of the laboratory coordination device according to an embodiment of the present invention is shown.

[0121] Figure 84 The collaborative operation mode of the laboratory coordination device according to an embodiment of the present invention is shown. Detailed Implementation

[0122] The embodiments described in this specification provide technical solutions to various technical problems through improvements to existing technologies and the creation of entirely new technologies. The technical problems addressed by the embodiments discussed in this specification include inefficient conventional user interfaces and difficulties in integrating different parts of processing workflows.

[0123] The improved user interface discussed in this specification provides practical solutions to problems related to inefficiency, accuracy, repeatability, and computational inefficiency in conventional user interfaces. The technical solutions provided in this specification improve each of these aspects by using the user interface methods and techniques of the present invention. In particular, the technical solutions provided by the user interface disclosed in this specification offer users a more efficient way to navigate menu systems for complex processes.

[0124] User interfaces of electronic devices implemented for human-computer interaction or communication typically include a series of menus or similar selection options (e.g., a series of hierarchical options) that the user can choose from to enable the device, such as a computer, to perform the desired function. In some embodiments, the amount of information or menu selections presented to the user can become overwhelming, depending on the type of application used. A wide range of available menu options may cause the user to try different choices or navigate to different menu selection hierarchies before finding the correct or desired set of options. In some cases, only about 10% of the 100% of user interface selections and functional options available to the user may be used. However, with all 100% of the options presented, the user may find it difficult to decide where to navigate to find the 10% that is relevant to them. Moreover, because selecting a menu option affects the next choice made along the menu selection path, switching between selections means that the user is also navigating to many different paths starting from that option. The trial and error that can occur during user interface navigation due to scrolling and page-turning with many different options is time-consuming, costly, and inefficient.

[0125] The systems, methods, and techniques of this invention provide user interfaces that guide users to select options via a user interface display or another presentation device, allowing them to find the correct choice in less time. This results in fewer attempts at making incorrect selections and less time spent on user navigation to accomplish the desired computational function or goal. In one aspect, the user interface of this invention can present a selective, limited number of options from all available choices to the user in a specific manner, guiding the user through these options, simplifying operation, and providing the user with a more efficient way to focus on the desired computational function. In another aspect, the user interface of this invention can connect the user more directly to the application.

[0126] The embodiments and technical solutions provide practical applications of specific visual principles to help users navigate the menus and systems described in this specification. These visual principles involve minimizing the content being viewed and maximizing background or blank space to reduce visual clutter and enhance focus areas. By providing a dark or uniform background and increasing the contrast between content and background, the user's attention can be drawn to the appropriate area.

[0127] The embodiments and technical solutions provide practical applications of specific design principles to help users navigate the menus and systems described in this specification. The design principles specifically implemented in this specification include, for example, ensuring that the user minimizes the number of menus and / or selections at any given time.

[0128] A further design principle involves providing the user with a single new choice at any given time, while simultaneously offering easy access to previously selected options. This principle can be implemented via a two-part display system. The current section can be configured to display the user's current selection, while the history section can be configured to display information about previous selections. Together, the current and history sections can provide a "direct workflow mode." The current section, presenting the user's current selection, can strictly limit the number of menu items displayed, such as seven, five, three (or any other number), while other potential items in the same menu are displayed elsewhere. Previously selected choices (and the menus used to make those choices) can be displayed to the user in a nested or overlay manner. A series of nested previously selected menu items can be presented in a matryoshka fashion, with each previously selected menu item expanding within a displayed submenu. Nested or overlayed previously selected menu items can also provide a breadcrumb trail illustrating the path taken to reach the current menu. In some embodiments, an indicator bar can be provided to draw the user's attention to previously selected menu items. For example, when arranging previously selected menu items in a stacked manner, the indicator bar can be used to help vertically align one or more menu items and / or menu items. This is illustrated in, for example... Figure 61D In this example, the indicator bar (located below the "Add / Remove" item) helps to draw the user's attention to and align with the following items: "Administration," "Law," and "Add / Remove." In some embodiments, the indicator bar may be depicted as resembling clock hands, such as... Figure 61D As shown in the diagram. Furthermore, the indicator bar may include color-coded states (e.g., red indicating an error state and blue indicating a normal state). In some embodiments, the color-coded states can be depicted within a portion of the indicator bar by illuminating pixels of one or more colors. In one example, as... Figure 61D As shown, the color-coded status can be provided in the middle section of the indicator bar, but this status can also be displayed in other parts of the UI.

[0129] The embodiments of this specification maintain a consistent appearance throughout the use of the interface, regardless of the work or processing to be performed. For example, by maintaining a consistent screen position for menus, users do not have to search for different locations of menus. In other words, relevant menus are moved to the currently used portion of the screen so that the user can notice them when needed. In these embodiments, the currently used portion of the screen remains centered from top to bottom and from left to right. In other embodiments, the size and shape of the menu interface will change depending on the device or screen on which it is viewed. Menus may expand horizontally on wider screens and / or vertically on taller / narrower screens.

[0130] The embodiments discussed in this specification improve user productivity by enhancing efficiency and accuracy in several aspects of the user experience. The user interface described herein allows the user to focus on the most likely use cases while minimizing distractions caused by less frequently used options. This focus allows the user interface to minimize visual clutter and allow the user to concentrate on the most relevant menu choices. The user interface described herein attempts to guide the user through the interface in different steps while eliminating bottlenecks that might leave the user wondering what to do next. In the embodiments of this specification, the user remains transparent through the navigation path of the interface system, making it easy to select alternative options or exit the current menu. Throughout the process of using the user interface, the user has the option to view alternative paths in a non-distracting manner. Therefore, the core functionality of the user interface software provided in this specification is to reduce the total amount of information displayed to the user at any given time while increasing the amount of relevant information displayed to the user at any given time. In cases of low usage, other information and options are still provided in a non-distracting manner. Such decisions regarding the information presented through the user interface at any given time can be pre-guided by a menu workflow and / or influenced and updated by analysis of previous user actions and selections.

[0131] Computer functionality can also be improved through the embodiments provided in this specification. For example, by focusing on a limited number of options, resource usage on devices (e.g., user devices and / or server devices) that may be involved in running the user interface can be reduced. For example, memory usage, processor resource usage (such as Central Processing Unit (CPU) usage), persistent storage usage of hard disk drives, etc., and bandwidth required for communication between devices (e.g., device-to-device, device-to-server, server-to-server) can be reduced. The ability to directly navigate to or reach the correct selected or chosen path (e.g., without multiple attempts and incorrect navigation) can also increase the efficiency of communication between devices and servers, for example, reducing Internet communication and the costs associated with such communication.

[0132] The further embodiments discussed in this specification relate to the integration of various processing workflows. As discussed in this specification, a "processing workflow" may relate to instrument (including biological instruments) testing workflows, manufacturing workflows, analytical workflows, and / or possibly any workflow relating to one or more controlled devices that are at least partially controlled by one or more computing systems. In another embodiment, a processing workflow conforming to the embodiments discussed in this specification may involve the use of one or more consumables.

[0133] The computing system that conforms to the user interface and processing workflow management system discussed in this specification may include various architectures, including but not limited to single-device computing systems, desktop computing systems, laptop computing systems, tablet computing systems, mobile device computing systems, thin client computing systems, cloud-oriented computing systems, server computing systems, multi-device computing systems, device / printer systems, device / server computing systems, systems that include multiple devices and servers, or any other suitable computing system.

[0134] The processing interface system described in this specification increases user accuracy, efficiency, and satisfaction by providing a faster user interface, reducing time spent searching for the correct menu items, reducing the selection of incorrect menu items, and reducing overall workflow time. Compared to traditional systems that offer immediate access to 100% of options (of which only 10% are frequently used), the system described in this specification provides only the frequently used functions (e.g., 50%, 55%, 60%, 65%, 70%, 75%, 80%, 85%, 90%, 95%, 95+%, 70-95+%, 80-95+%). Instead, the solutions provided in this specification increase computational efficiency, reduce memory usage, and lower the utilization of CPU, hard disk drive, power supply, and communication resources.

[0135] The user interface systems discussed in this specification may be provided in the form of graphical user interfaces (GUIs), text-based user interface systems, virtual, augmented, or mixed reality (VAMR) interface systems, projection-based systems, gesture control systems, and / or any other type of visual user interface. Generally, user interface systems conforming to the embodiments of this specification may be referred to as "Methodical User Interfaces (MUIs)." MUIs may include graphical user interfaces (GUIs), text-based user interface systems, virtual, augmented, or mixed reality (VAMR) interface systems, projection-based systems, gesture control systems, and / or any other type of visual user interface. Although some principles discussed in this specification are specifically addressed to, for example, GUIs, this is not limiting; rather, the principles discussed in this specification can be equally applied to other interface systems.

[0136] The MUI described in this specification refers to "display," "interface," and "user interface." As used herein, unless otherwise stated, the terms "display," "interface," and "user interface" mean text, images, visual elements, interactive elements, and any other visual aspects presented or displayed on a screen, projector, or other visual display hardware. Therefore, it should be understood that "display" and "interface," as used herein, can be provided via any type of visual display hardware, screen, and / or projector. For convenience, menus, interfaces, and other visual items are referred to in this specification as being viewed on or displayed by the MUI. It should be understood that this reference indicates the visual presentation of the MUI via the hardware device discussed herein.

[0137] As described in more detail below, the user interface system described in this specification may use various visual elements to present menu items. For example, a visual element may include a vertical or horizontal "scroll wheel" that rotates through various menu items. As described in this specification, using a "scroll wheel" as a visual element means providing the user with options that are highlighted and blurred. A scroll wheel visual element can be understood as a virtual scroll wheel with its rim facing the user and multiple menu items arranged on the rim of the virtual scroll wheel. A scroll wheel visual element may or may not contain any visual indicators of the presence of the scroll wheel. A scroll wheel visual element may provide highlighted options to the user in an attention-grabbing manner (i.e., in the portion of the scroll wheel "closest" to the user), while other blurred options are presented in a less attention-grabbing manner. Highlighted menu items may be displayed in different colors, in different fonts, in larger fonts, or highlighted with other attention-grabbing visual markers. As the virtual scroll wheel rotates, the currently highlighted menu item rotates away from the user (clockwise or counterclockwise), and the currently blurred menu item becomes the new highlighted option. In embodiments, a blurred menu item closest to the highlighted menu item may be displayed to attract more attention than a blurred menu item farther away from the highlighted menu item. For example, a menu item may be smaller or brighter based on its distance from the currently highlighted menu item. As the "scroll wheel" "rotates," a dimmed menu item may visually fade. In this way, the virtual scroll wheel provides the user with the feeling and sensation that menu items are arranged on the physical scroll wheel. Visual elements may be further contained within horizontal or vertical sliding axes that slide through various menu items. Similarly, for a scroll wheel as discussed above, a sliding axis may be used to provide highlighted menu items and blurred or less highlighted menu items. In embodiments, a sliding axis may differ from a scroll wheel in that blurred menu items do not disappear from the view when swiping through an option on the sliding axis. Further embodiments of scroll wheels and sliding axes will be discussed further with respect to specific embodiments in this specification.

[0138] As discussed in this specification, menu items may be "selected," "highlighted," and / or "clicked." As used in this specification, a "highlighted" menu item means, for example, highlighting the "highlighted" option to the user, such as a highlighted menu item centered on the scroll wheel. "Highlighted" may include changing the color, size, font, etc., of the menu item to visually highlight it to the user. A "faded" user option may include changing the color, size, font, etc., of the menu item to visually fade it to the user. Menu items may be highlighted or faded based on user actions (e.g., by clicking the mouse, touching the touchscreen, rotating the scroll wheel, etc.) (e.g., by presenting menu items that cannot be selected or edited by the user), and / or may be highlighted or faded based on interface actions (e.g., providing the default highlighted option).

[0139] As used in this specification, a "select" menu item means a menu item that the user has selected, and the user interface has performed one or more menu steps based on that selection. A "select" menu item causes the computer system to execute computer instructions to proceed with the menu, rather than simply "highlighting" the menu item. For example, a "select" menu item may be used to display a new menu based on a selection. The selected menu item may be highlighted after selection, but highlighting a menu item does not necessarily include the selected menu item.

[0140] In some embodiments, menu items can be selected or highlighted by clicking on them. As used in this specification, "click" means a user action of clicking, tapping, or using an interface device (e.g., a mouse, touchscreen, etc.) to indicate or select a menu item. As used in this specification, "clicking" a menu item is different from "selecting" a menu item. Clicking refers to a user action of indicating a menu item, while selecting refers to a computer function relating to selecting a menu item.

[0141] In some embodiments of the system according to this, menu items can be selected by clicking. Clicking a menu item allows the system to proceed to the next menu item sequence. In other aspects of the disclosed system, clicking a menu item serves to highlight the menu item, but does not select the menu item to proceed to the next menu item.

[0142] Menu items may be described as "selectable" in this manual. "Selectable" menu items are those that the user can interact with by selecting or highlighting. Selectable items can be displayed by changing their color, highlighting, font, etc., to indicate their selectability. Menu items may also be described as "non-selectable" in this manual. "Non-selectable" menu items are those that the user cannot currently interact with by selecting or highlighting. Non-selectable menu items can be displayed by changing their color, highlighting, font, etc., to indicate their non-selectability.

[0143] Menu items can also be described as "previously selected" and "previously unselected." "Previously selected" menu items refer to those selected to reach the currently displayed menu interface. Users do not need to actively select "previously selected" menu items. By default, if the system takes the user to a menu layer below the top layer (i.e., the user did not actively select anything during the current process), the menu items or selections in the current path can be indicated as "previously selected." "Previously unselected" menu items refer to those not selected to reach the currently displayed menu interface. For example, if the user has selected a first menu item but not a second, the system can continue displaying subsequent menus or submenus as the first menu item is selected in the current section of the MUI. In the history section of the MUI, the system can display the first menu item as a previously selected menu item and the second menu item as a previously unselected menu item. The previously unselected menu items can be displayed as selectable.

[0144] For example, a user can scroll or rotate a slider to navigate through various menu items. The user can fix the slider or scroll wheel to highlight a specific menu item. In one embodiment, a specific menu item may require further user interaction (e.g., a single click or double click) to cause the MUI to present a new set of menu items or submenu items upon selection. In this embodiment, the user rotates the slider or scroll wheel to move the desired menu item to the highlighted position. The user then clicks, double-clicks, or indicates a selection on the highlighted menu item to display the next menu or submenu. In another embodiment, a specific highlighted menu item can be selected simultaneously. In this embodiment, as long as the desired menu item is highlighted, rotating the slider or scroll wheel to move the desired menu item to the highlighted position will display the associated submenu.

[0145] As discussed in this specification, selection or highlighting of menu items can be caused by direct selection on the menu item (i.e., clicking, touching, etc.), whether it is a scroll wheel, slider, and / or item list, and whether it is a highlighted or dimmed menu item. Selection or highlighting of menu items can also occur as the user manipulates various visual elements to move the menu item to the position to be highlighted or selected. For example, the user can rotate a scroll wheel or move a slider before a particular menu item is highlighted and highlighted. Manipulation and / or direct selection of visual elements can be achieved using any suitable user input device, including touchscreens, mice, keyboards, arrow keys, eye gaze detection systems, motion detection systems, gesture detection systems, etc.

[0146] The features of an embodiment of the interface may be referred to as "first part" and "second part". These terms refer to specific portions of the user interface displayed at different times and do not need to be fixed in a specific position on the screen. As used in this specification, "first part" may also be referred to as "current part". "First part" or "current part" means the portion of the MUI that displays the current or latest group of menu items. "First part" and "current part" are used interchangeably in this specification. "Second part" may also be referred to as "historical part". The "second part" or "historical part" means the portion of the interface that displays previously viewed menus and previously selected and unselected menu items. "Second part" and "historical part" are used interchangeably in this specification.

[0147] Figure 1 This embodiment illustrates a method for interactively guiding a user through a menu-selected path on a user interface. The method can be executed automatically by at least one hardware processor. The method facilitates user movement within the system by asking questions and displaying one or more previously made choices, along with other unselected choices, while simultaneously exploring other options based on the initial selection. As used herein, "asking questions" means providing one or more menu selections selected by the user. The method allows the user to continue along a path or jump to different paths, promptly returning to choices made in one or more previous steps, or returning to the most recent point in time. In one embodiment, the user interface presents and allows the user to view, for example, past or previous choices made and unmade at each step of the path, all on the same screen regardless of the user's location on the path. For example, the user interface displays an outline of the user's menu-selected path, including unselected menu items. This user interface method allows for more efficient navigation, guiding the user along the path, allowing the user to see the path the user is traversing, and allowing the user to deviate from the user-set path to different paths. The user interface method allows the user to view backward and forward page paths (Breadcrumb), as well as where the user wants to go and where the user can go.

[0148] As discussed in this specification, the menu is presented as a series of hierarchical menu trees. Each level of the menu tree includes multiple menus leading to other menus. Therefore, the first level of the menu tree contains multiple first menus, the second level contains multiple second menus, the third level contains multiple third menus, and so on. This structure continues to execute menu levels. In some discussions in this specification, the first menu is simply referred to as a menu, while subsequent menu levels in the tree are called submenus, sub-submenus, etc. Sometimes, multiple menu levels below the current menu can be collectively referred to as submenus. Therefore, a submenu of a first menu may contain multiple second menus, multiple third menus, multiple fourth menus, multiple execution menus, etc. An example of a hierarchical menu tree structure is provided in [link to documentation]. Figure 2KAs shown in the diagram. As used in this specification, regarding hierarchical menu trees, each level is referred to as a "menu" even when no text menu is presented to the user. For example, a "menu" might simply present an "Execute" button to implement a process designed in another part of the menu. Another "menu," for example, might present a tutorial.

[0149] Each of the numbered menus includes multiple menu items or options, each item or option pointing to a new menu at a lower level. Therefore, items in the first menu may each point to one of multiple second menus. In some embodiments, menu levels may be skipped. For example, options in the first menu may point to one of multiple third menus.

[0150] In embodiments, each menu may also include additional information displayed in the MUI. This additional menu information can provide user information about the menu item and / or general context about the menu. For example, in a menu that presents the user with a save file option, additional information indicating remaining disk space may be provided. In another example, in a menu that presents the user with an option to run a measurement, additional information about the available consumables for the displayed measurement may be provided.

[0151] At the execution menu level, which is the last level in a series of menus, the user can select to execute a menu selection or item. These selections or items do not lead to further menus, but rather represent the parameters that the menu tree intends to process. Selecting an execution menu selection or item causes the system to perform the function related to the selected menu option or item. For example, when using an assay design menu tree, the execution menu selection may include options such as file name, assay parameters, reagent selection, etc.

[0152] In this embodiment, the execution menu facilitates the interface between the MUI software and the physical world. The execution menu provides, for example, the ability to execute commands output by the systematized user interface control system 1102, which connects to the system or instrument, to implement processes designed using the MUI. In this example, such an execution command could cause a manufacturing system to begin manufacturing a part, cause a measuring instrument to begin taking measurements, or cause a design system to send design specifications, etc.

[0153] In this embodiment, the execution menu can provide a user walkthrough or tutorial. For example, after designing a workflow or process, the execution menu can provide a walkthrough or tutorial that conforms to the workflow, offering text-based, audio-based, video-based, and image-based tutorial steps to guide the user through each step of the workflow or process design.

[0154] In embodiments, the execution menu can be combined with execution commands sent to physical world instruments and machines to provide walkthroughs and / or instruction. For example, in a modular laboratory system, this combination can provide user instructions to load the machine (e.g., with assay plates and reagents) and then provide machine execution commands to run the process. Since new steps in the process require physical user intervention (moving assay plates, etc.), the MUI can provide additional user instructions (text-based, video-based, image-based, audio-based, etc.) for further processing during the execution phase. In embodiments, user instructions and notifications for implementing user intervention portions of the process can be provided via various communication mechanisms, including, for example, text (SMS, MMS), email, telephone, instant messaging, slack messages, and any other type of messaging protocol. These various communication mechanisms can be useful, for example, when certain parts of the machine processing take some time to complete and the user may not want to remain at the processing location during the process. Thus, in the case of a user initiating a process that takes several hours, the user may receive a text message indicating that their involvement is required for further processing.

[0155] These types of "cobot" interactions (where the MUI integrates the physical-world operations of human operators and automated machines) can be applied to a variety of processes or workflows, including laboratory workflows, manufacturing workflows, food production workflows (e.g., beer production, bread production, etc.), and transportation and logistics workflows (e.g., packing and picking boxes, packaging, etc.). These automated machines can further include non-human machines, such as robots, drones, robot-based machines, or other autonomous or semi-autonomous machines.

[0156] As used in this specification, the "display" of a menu includes displaying one or more items from the menu within the MUI. Displaying a menu does not require showing all items or options in the menu. Menu items, or the items that constitute the first menu, may remain unchanged regardless of whether each menu item is displayed. As discussed in more detail below, certain menu items may be excluded or restricted for various reasons. As discussed in this specification, a designated "first menu" or "second menu" may be repositioned to different parts of the screen. When repositioned, the first menu may continue to display the same group of first menu items and / or may display different groups of first menu items.

[0157] As discussed in this specification, menus can also be referenced based on their time state. A "current menu" refers to the currently active menu in the active portion of the MUI that prompts the user to select an option. A "past menu" refers to a menu from which the user has previously selected an option. Past menus may be displayed in the history portion of the MUI. A "next menu" refers to the next menu to become active after the current menu becomes a past menu. For example, a first menu may be displayed as the current menu. After a selection is made from the first menu, the first menu may then be repositioned as a past menu. The next menu, i.e., the second menu indicated by a selection from the first menu, may then be displayed as the current menu. The current menu may be displayed in the first or active portion of the user interface, while the past menu may be displayed in the second or history portion of the user interface.

[0158] In the history section, menu items for each past menu can be displayed linearly in the MUI. All menu items from the aforementioned menu layer are displayed in a single line (horizontal or vertical). Each group of past menu items can be displayed linearly, while the menu as a whole can be stacked or nested. This feature is illustrated as shown in... Figure 2C The system displays "menu items" and "submenu items" in a linear fashion. The relationship between the "menu items" and the "submenu items" is one of stacking or nesting. Therefore, within a single menu layer, menu items are adapted to be displayed linearly, while previous navigation and subsequent menu layers are adapted to be displayed in a nested fashion.

[0159] Selection menus can be displayed in a graphical scroll wheel, which allows options to be rotated in one direction (e.g., horizontal or vertical (e.g., left and right, up and down) or other directions). Alternatively, selection menus can be displayed as a graphical slider, which allows options to be slid in one direction (e.g., horizontal or vertical (e.g., left and right, up and down) or other directions). For example, an initial menu layer (first layer) can be displayed horizontally and slid left and right, and the next menu layer (second layer) can be displayed vertically and rotated up and down. Yet another way, selection menus can be displayed as a series of concentric circles, each menu layer displayed as a circle with menu selections (also called options or menu items). For example, the initial menu layer (first layer) can be displayed in a central circle, the next menu layer (second layer) can be displayed in the next circle (second circle) surrounding the central circle, the next menu layer (third layer) can be displayed in yet another circle surrounding the second circle, and so on. However, selection menus can also be displayed or visualized as a graphical decision tree with nodes and edges. Each layer of the graphical decision tree can represent a menu layer with selections.

[0160] In one embodiment, the scroll wheel and / or the sliding axis does not need to rotate completely; for example, it does not need to rotate completely or circle around. For instance, the scroll wheel and / or the sliding axis rotates or slides from the starting menu item to the ending menu item, and then rotates or slides back from the ending menu item to the starting menu item. Thus, for example, the beginning and end of the menu are always obvious because they do not merge or converge. This technique reduces processing time because the scroll wheel and / or the sliding axis can convey (and the user can immediately understand) the complete selection menu and clearly indicate where, or which of the options displayed by the scroll wheel and / or the sliding axis is, the first menu item; and where, or which of the last menu items is, it is.

[0161] In a further embodiment, the scroll wheel and / or sliding axis can be fully rotated to allow the user to easily access the beginning of the menu after reviewing the entire menu. In this embodiment, a visual indicator may be provided to indicate that the menu has rotated a full rotation and returned to the beginning.

[0162] In various embodiments, the terms "software protocol" and "computer instructions" are used to describe software instructions or computer code configured to perform various tasks and operations. As used herein, the term "manager" broadly refers to a collection of software instructions or code configured to cause one or more processors to perform one or more functional tasks. For convenience, in practice, various managers, computer instructions, and software protocols will be described as performing various operations or tasks when they are programmed into hardware processors to perform operations and tasks. Although described as "software" in different places, it should be understood that, as used herein, "manager," "software protocol," and "computer instructions" can be implemented in the same way as firmware, software, hardware, or any combination thereof to instruct a computer or other electronic device to perform and / or implement a series of steps and / or instructions. Furthermore, embodiments of this specification are described from the perspective of method steps, functional steps, and other types of appearance (such as the display of menus, the selection of options, etc.). Although not explicitly stated in each case, it should be understood that these actions are performed according to computer instructions or software protocols executed by one or more computer processors.

[0163] The functions and software protocols of the manager discussed in this specification can be provided by sending one or more commands. As discussed in this specification, a “command” sent by the manager and software protocols refers to signals and instructions provided to various aspects of the computing system to cause various actions. Commands can be sent from one manager to another and / or to other components of the system. For example, a manager can provide a command to display certain visual elements in a menu interface. This command may be directed to a physical display screen and may contain the signals and instructions required to generate the visual elements. As used in this specification, when the manager is described as performing actions or implementing certain functions, it should be understood that the manager has sent commands to cause the actions or functions to occur.

[0164] In various embodiments, the term "module" is used in this specification to refer to a specific suite of software protocols and computer instructions that generate, maintain, and operate multiple elements of a MUI as described herein. One or more processors described herein may be configured to execute multiple software protocols to provide a systematized user interface module. As used herein, a "systematized user interface module" refers to any one of a subset of modules that provides a specific user interface. For example, an administrator console module, an audit trail module, and a reader module may be provided as specific systematized user interface modules to respectively implement functions related to system management, auditing, and board reading. Each MUI module may be considered to contain at least one hierarchical menu tree with at least multiple levels of menus. Each module may further contain preferred default visual elements, preferred default exclusion and restriction lists, and other module-specific features. Other modules are discussed in more detail below and throughout the invention. Throughout the invention, various aspects of various MUI modules are discussed. The aspects discussed for any particular MUI module are non-exclusive and non-limiting and can be equivalently applied to any other MUI module. Therefore, any MUI features discussed in this specification (whether in a broad sense or in relation to a specific module) can generally also be applied broadly to the MUI and / or any other specific MUI modules discussed in this specification.

[0165] Please refer to this. Figure 56 The illustration shows a systematic user interface control system 1102 conforming to an embodiment. The systematic user interface control system 1102 includes one or more processors 1110 (for convenience, they may be interchangeably referred to as multiprocessor 1110, one or more processors 1110, or processor 1110 in this specification), one or more storage devices 1120, and / or other elements. The CPU 2 (see...) Figure 19 ) and the hardware processor 1804 (see Figure 18The processor 1110 may be an example configured as described in this specification. In other embodiments, the functionality of the processor may be performed by hardware (e.g., using an application-specific integrated circuit (ASIC), programmable gate array (PGA), field-programmable gate array (FPGA), etc.) or any combination of hardware and software. The storage device 1120 comprises any type of non-transitory computer-readable storage medium (multi-media) and / or non-transitory computer-readable storage device. This computer-readable storage medium or device may store computer-readable program instructions for causing the processor to perform one or more methods described in this specification. The memory 4 (see...) Figure 19 ) and the memory device 1802 (see Figure 18 Examples of storage devices 1120 may be provided. Examples of computer-readable storage media or devices may include, but are not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof, such as computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), compact disc read-only memory (CD-ROM), digital versatile disk (DVD), and memory sticks, but are not limited to these examples. In embodiments, storage device 1120 may include multiple storage devices 1120. Multiple storage devices 1120 conforming to embodiments may be arranged side-by-side and / or not side-by-side. For example, a physical system may include a first memory storage device 1120, and a second physical system may include a second memory storage device 1120.

[0166] In some embodiments, the processor 1110 and the storage device 1120 may be implemented via a cloud computing platform or other forms of distributed computing. In such embodiments, each of the processor and the memory device may include multiple processors and storage devices for implementing the work and functions described herein.

[0167] The processor 1110 is programmed by one or more computer program instructions and / or software protocols (referred to as "managers") stored in the storage device 1120. For example, the processor 1110 is programmed by a display manager 1050, an input manager 1052, a menu manager 1054, a user manager 1056, an exclusion manager 1058, a network manager 1060, and a data storage manager 1064. It should be understood that the functions of the various managers discussed in this specification are representative and not limiting. Furthermore, the functions of the various managers can be combined as needed into one or more modules, application services, programs, services, jobs, instruction set scripts, software libraries, applications, or executable code.

[0168] The manager discussed in this specification can be implemented in various embodiments to manage a MUI to perform various tasks that require processing workflows. Although this specification describes various software implementations of an MUI with respect to one or more specific embodiments, the methods and functions provided by the aforementioned manager can be implemented to provide any MUI that processes workflows. The aforementioned manager can be functionally implemented through a software library.

[0169] The various components of the systematized user interface control system 1102 work together to provide a systematized user interface display to the user via any type of display hardware (including screens, projectors, touchscreens, headphones, etc.). In embodiments, the systematized user interface control system 1102 implements one or more software protocols to interactively guide the user through menu items, options, or selected paths in the MUI. The aforementioned software manager may include computer instruction sets, software libraries, dynamic link libraries, application programming interfaces, function libraries, and other compilations of executable code. The systematized user interface control system 1102 may further include a suitable graphics library, which includes graphics required to implement and instantiate the various visual elements described in this specification. The manager for a particular implementation scheme can be customized by using various data structures representing module information, including tables, linked lists, databases, B-trees, binary trees, heaps, stacks, queues, hash tables, red-black trees, binomial heaps, Fibonacci heaps, and any other suitable data structures. Therefore, the manager of the MUI can be provided as a customizable library that is configured to interface, interact, and integrate with additional computer instructions and data structures to provide MUI modules capable of performing specific tasks.

[0170] The display manager 1050 is a software protocol that operates on the systematized user interface control system 1102. The display manager 1050 is configured to manage the systematized user interface display, including all its visual elements. The display manager 1050 can be configured to send commands as needed to display various menu items.

[0171] The input manager 1052 is a software protocol operating on the systematized user interface control system 1102. The input manager 1052 is configured to manage all input received by the systematized user interface control system 1102, including but not limited to user input and input from other systems. The input manager 1052 can be configured to send commands to other managers of the systematized user interface control system 1102 based on received input. User actions such as clicks and other screen interactions cause the input manager 1052 to receive signals indicative of user interaction. Receiving this signal allows the appropriate manager of the systematized user interface control system 1102 to provide commands in response to the signal, thereby resulting in one or more actions, including MUI navigation, menu display, etc., as discussed in this specification. For ease of explanation, this interaction and user input may be referred to as causing a specific response; in reality, the specific response is caused by the systematized user interface control system 1102 in response to the interaction or user input.

[0172] The menu manager 1054 is a software protocol operating on the systematized user interface control system 1102. The menu manager 1054 is configured to manage a hierarchical menu tree and all menu items related to the menu tree. The menu manager 1054 is configured to select appropriate menu items for display, determine the next menu item to be displayed, and manage all aspects of navigation through the menu tree. The menu manager 1054 can be configured to send commands to other managers of the systematized user interface control system 1102 based on menu navigation requirements.

[0173] The user manager 1056 is a software protocol that operates on the systematized user interface control system 1102. The user manager 1056 is configured to manage user access to the systematized user interface control system 1102. The user manager 1056, for example, manages user authorization, including maintaining user authorization records, verifying user credentials, and other necessary user authentication tasks.

[0174] The exclusion manager 1058 is a software protocol operating on the systematized user interface control system 1102. The exclusion manager 1058 is configured to manage the exclusion and restriction of menu items. As discussed in this specification, menu items can be excluded or restricted based on various factors. The exclusion manager 1058 can be configured to send commands to implement such exclusions and restrictions.

[0175] The network manager 1060 is a software protocol operating on the systematized user interface control system 1102. The network manager 1060 is configured to establish, maintain, and manage all network communications between the systematized user interface control system 1102 and various other system components discussed in this specification. Established communication paths can utilize any suitable network transport protocol and provide one-way or bidirectional data transmission. The network manager 1060 can establish the network communications required for communication with all system components as needed.

[0176] The data storage manager 1064 is a software protocol that operates on the systematized user interface control system 1102. The data storage manager 1064 is configured to store, retrieve, archive, manipulate, and manage all data structures and data storage devices that the systematized user interface 1102 can interact with. The data storage manager 1064 is configured to send commands to any of the various data storage devices discussed in this specification to manage the storage and retrieval of data.

[0177] The foregoing description of display manager 1050, input manager 1052, menu manager 1054, user manager 1056, exclusion manager 1058, network manager 1060, and data storage manager 1064 provides an overview of the capabilities and operation of these managers. The managers are not limited to the foregoing, and in the various embodiments discussed below, the managers may have additional, different, and / or more capabilities. The described structure of the systematic user interface control system 1102 is merely illustrative, and it should be understood that the various functions and capabilities of the computer instruction programming processor described herein can be executed, implemented, or realized by software systems with alternative structures.

[0178] The systematic user interface control system 1102 can present menu options in one or more hierarchical menu layers, where each menu layer can contain one or more menu items or options. As described in this specification, the hierarchical menu layer refers to multiple layers in a menu system. A selection in the highest first menu layer leads to navigation to a lower hierarchical level, namely a second menu, submenu, or sublayer. A selection in a second menu or submenu leads to navigation to an even lower hierarchical level, namely a third menu, sub-submenu, or sub-sublayer. The hierarchical menu structure can contain any suitable number of layers. In some embodiments, a selection on a layer can lead to navigation to one, two, three, or more layers below the current layer.

[0179] Each menu can display options in the currently active portion of the interface. Menu selection or option selection can trigger the display or presentation of subsequent, immediately following, or submenus, which may contain multiple menu options or submenu options of their own. When a user selects a menu item that leads to a new menu, the menu items of the old menu can be moved from the currently active portion of the interface to the history portion, allowing the user to easily move to the new menu option while retaining the content of the previous menu option. These features are referenced below. Figures 2A to 2O , Figure 3 ,and Figure 57 More detailed description.

[0180] Figure 57 This is a flowchart illustrating a process 5200 that adapts navigation to output paths to a hierarchical menu layer of a user interface (such as a GUI, MUI, and / or any other type of UI discussed herein). The process 5200 is executed on a computer system having one or more physical processors programmed with computer program instructions, which cause the computer system to perform the method when the one or more physical processors execute the computer program instructions. The one or more physical processors are simply referred to as processors below. In an embodiment, the process 5200 is executed via a systematized user interface control system 1102 as described herein. The systematized user interface control system 1102 represents an example of a hardware and software combination configured to execute the process 5200, but implementations of the process 5200 are not limited to the hardware and software combination of the systematized user interface control system 1102. As discussed herein, any other suitable computer system may also execute and / or implement the process 5200. The description of the process 5200 is not limiting and various operations may be changed or modified according to the embodiments described herein.

[0181] In step 5202, the process 5200 includes providing a first display command. The display manager 1050 provides the first display command to display a first menu having one or more user-selectable items to be displayed on the first portion of the UI. The first menu in the first portion can be displayed using any visual element disclosed in this specification (e.g., a scroll wheel visual element). The selectable items of the first menu can be determined, for example, by the menu manager 1054 as discussed in this specification.

[0182] In step 5204, the process 5200 includes receiving a selection. The input manager 1052 receives a selection of a menu item from the first menu based on input provided to the system. The input may be a user selection and / or an automatic selection as discussed in this specification. For example, a user selection may be received by clicking a brightly displayed or highlighted menu item. Once selected, the menu item may be a previously selected menu item.

[0183] In step 5206, the process 5200 includes providing a relocation command. The menu manager 1054 provides a relocation command to relocate the first menu from a first portion of the UI display to a second portion of the UI display. The relocation command may be provided in response to a received selection. During relocation, the menu items of the first menu include one or more previously selected menu items that were not selected for relocation and previously unselected menu items. The display of the first menu in the second portion may be provided according to any visual element disclosed in this specification (e.g., a sliding axis visual element). The relocation command of the menu manager 1054 may be sufficient to update the UI display. In another embodiment, the relocation command may be combined with and / or include a display command provided by the display manager 1050.

[0184] In step 5208, the process 5200 includes providing a second display command. The display manager 1050 provides the second display command in response to menu selection. The second display command causes a second menu of one or more user-selectable items to appear on the first portion of the UI display, i.e., after the first menu has been repositioned. The second menu can be displayed using any visual element disclosed herein (e.g., a scroll wheel visual element). In an embodiment, the second display command may incorporate information received from the menu manager 1054 regarding navigation of the hierarchical menu tree. After repositioning the first menu and displaying the second menu, the first menu can be viewed in a second portion, which includes one or more previously selected and previously unselected menu items of the hierarchical menu tree, while simultaneously viewing the second menu in the first portion.

[0185] The process 5200 may further include additional or different operational steps as described in this invention.

[0186] Please refer to this. Figure 1In step 102, the currently selected menu (e.g., a list of menu items) may be displayed on a first portion of the user interface display. In step 104, the user interface allows the user to select a menu item from the currently selected menu displayed on the first portion of the user interface display, and to navigate deeper into menu selection layers based on the selection of menu items in the previous menu selection layer. In step 106, previously selected and previously unselected menu items from the deeper selection layers are displayed on a second portion of the user interface display. The previously unselected menu items are displayed as optional options. Previously selected menu items (or options) may also be displayed as optional options. In step 108, the user interface allows the user to jump to different paths of menu options by allowing the user to select a previously unselected menu item from the previous navigation menu layer displayed on the second portion of the user interface display. The user interface displays both the first and second portions such that both can be viewed on the same screen of the user interface, for example, simultaneously.

[0187] In one embodiment, the first and second portions are offset to substantially center the display of the currently selected menu on the user interface display, while both the first and second portions are arranged on the user interface display. Therefore, for example, during navigation or deeper (or upward) navigation through different menu option layers, the first and second portions do not need to remain in a fixed position on the user interface display.

[0188] In one embodiment, upon detecting a selection of a menu item from the currently selected menu, the user interface repositions the currently selected menu to the second portion of the user interface display and displays a next menu option layer on the first portion of the user interface display based on the selection of the menu item. The repositioned currently selected menu is displayed on the second portion of the user interface display and becomes the previously selected and previously unselected menu items of the past menu layer. The next menu option layer is displayed in the first portion as the currently selected menu.

[0189] As mentioned above, the selection menu can be displayed as a rotatable graphic wheel showing menu items (selections or options), wherein menu items can be displayed on the wheel as it rotates. Menu items on a sliding axis can be displayed as a similar graphic of the sliding axis, which can slide. Rotation or sliding actions can be performed with the movement of a finger on the touchscreen or input from a pointing device or another input device. Alternatively, the rotation or sliding action can be performed automatically by the user interface (or hardware executing the user interface) in a timing manner. In one embodiment, the rotation or sliding direction can switch to a different direction as the selection menu is repositioned from the first portion to the second portion.

[0190] The currently selected menu can be displayed on the first part of the user interface in a first visual orientation, and a deeper menu selection layer containing previously selected and previously unselected menu items can be displayed on the second part of the user interface in a second visual orientation.

[0191] In one embodiment, the current selection menu is displayed as a graphic wheel or slider for selecting by rotating or sliding in a first visual orientation. In another embodiment, the deeper layers of the menu selection are displayed as a graphic wheel or slider for selecting the deeper layers by rotating or sliding in a second visual orientation.

[0192] In one embodiment, the second visual orientation is substantially orthogonal to the first visual orientation. In one embodiment, the first visual orientation is a vertical orientation, and the second visual orientation is a horizontal orientation. In another embodiment, the first visual orientation is a horizontal orientation, and the second visual orientation is a vertical orientation.

[0193] In one embodiment, the deep menu selection layer relocated to the second part is displayed as a menu overlay.

[0194] In another embodiment, the first and second portions may be displayed as a series of concentric circles. For example, the first portion may be displayed as the central circle of a series of concentric circles, and the previous menu layer may be displayed as a circle outside or around the central circle. Each circle representing a menu layer may contain, for example, rotatable menu items (selections or options) to allow the user to view all options presented on the menu layer. Once a menu item is selected from the currently selected menu, the currently selected menu is repositioned to the outer circle, and the central circle displays the next selection menu based on the selected menu item. For example, the circle (e.g., a dial) may contain a window displaying the active option, while rotating the circle (e.g., the dial) displays other options in the window. Although the dial options may appear finite, they can be infinite. For example, the dial may remain rotated until the last option is displayed (or the starting option if rotated backward).

[0195] On the other hand, a window can be opened to display the selected options as highlighted, with one (or more) options on the left and another (or more) options on the right.

[0196] In yet another embodiment, the first portion and the second portion may be displayed as a graphical decision tree.

[0197] In one embodiment, the previously unselected menu items in the depth layer displayed on the second portion of the user interface are highlighted relative to the previously unselected menu items in the depth layer displayed on the second portion of the user interface.

[0198] In one embodiment, upon encountering the last layer in a menu selection path, for example, when performing a function related to a selected item in the last menu layer, the user interface can return the current menu view to another item in the upper layer, such as a first menu list. For example, the currently selected menu may again be the first initial menu layer and may be displayed in a first section. In one embodiment, the first and second sections are not independent but linked to each other to make navigation more efficient, allowing the user to proceed along the path and allowing deviations from paths already set by the user, for example, being able to see the locations the user has visited and the backward and forward page paths to locations the user can visit in the menu selection path. In one embodiment, the user interface can guide the user through efficient path selection, eliminating the need for the user to search around the user interface trying to find the next appropriate path or action. This efficient path guidance can save computer resources, such as central processing unit (CPU) cycles and memory usage spent on swapping in and out processor threads and memory elements in the computer running the user interface.

[0199] Please refer to this. Figures 18 to 19 Provides for performing about Figure 1 Another example system describing the method. As mentioned above, Figure 18 and Figure 19 The system aspects presented in the middle can be as follows: Figure 56 Examples and / or implementations of the systematic user interface control system 1102 shown.

[0200] Figure 18 System elements of a graphical user interface (GUI) are illustrated in one embodiment. One or more hardware processors 1804 may execute a graphical user interface module and perform the aforementioned graphical user interface functions, thereby displaying the aforementioned graphical elements on a user interface display device 1806 coupled to one or more hardware processors 1804. A memory device 1802 may store menu lists and menu item lists, or options available for each menu list, that are accessible to the graphical user interface module and displayed on the display device 1806. The display device 1806 may include a screen device and / or a touch screen device. One or more pointing devices 1808 may be coupled to one or more hardware processors 1804 to allow input via the display device 1806.

[0201] The memory device 1802 may be any type of computer-readable storage medium described in this specification.

[0202] although Figure 18 This is particularly relevant to GUI systems, but this is only an example. It should be understood that the methods and techniques described in this specification can also be implemented via other MUIs, including text-based, virtual reality-based, augmented reality-based, mixed reality-based, and others.

[0203] For example, a hardware processor 1804 coupled to the memory device 1802 and the display device 1806 may display a currently selected menu on the first portion of the user interface display, allowing the user to select a menu item from the currently selected menu displayed on the first portion of the user interface display, and to navigate through menu selection layers based on the selection of menu items in the previous menu selection layer. The hardware processor 1804 may also display previously selected and previously unselected menu items in the navigating layers on a second portion of the user interface display, wherein the previously unselected menu items are displayed as optional options. The hardware processor 1804 may also allow the user to jump to different paths of menu options by allowing the user to select previously unselected menu items from the previous navigation menu layer displayed on the second portion of the user interface display.

[0204] The hardware processor 1804, for example, can execute commands related to... Figure 1 and Figure 3 The method described.

[0205] The aforementioned GUI technology can be implemented using computer languages ​​such as JAVA and JavaScript, but is not limited to these languages. In one embodiment, the functions and modules of the system and method of the present invention can be implemented or executed in a distributed manner on different processing systems or any single platform, for example, accessing data stored locally or distributedly on a computer network. Similarly, the software protocols and managers of the present invention can be implemented or executed in a distributed manner on different processing systems or any single platform, for example, accessing data stored locally or distributedly on a computer network.

[0206] GUI technology can be implemented on any type of computing device, such as desktop computers, laptop computers, mobile devices (e.g., Android or Apple iOS), tablet computers, and using any type of interface (e.g., mouse, touchscreen, etc.). GUI technology can also be implemented on instruments, such as assay instruments for performing biological assays (such as immunological or nucleic acid assays). In some embodiments, the instrument performs an electrochemiluminescence assay. In some embodiments, the instrument is an automated assay system, for example, comprising: (a) a single-robot-controlled 8-channel pipette, (b) a single-robot-controlled assay plate clamp, (c) a single 96-channel assay plate washer, (d) a single plate reader, (e) one or more plate shakers with a total capacity of at least five plate shaking positions, and (f) a processor adapted to perform assay processing in a 96-well plate to analyze multiple samples. Other computing devices, machines, systems, and instruments include wearable devices; automotive computing systems; personal instruments, including measurement-related instruments such as plate washers, plate readers, plate shakers, and incubators; workflow-aiding instruments such as loading vehicles (e.g., described in International Patent Application Publications Nos. WO 2018 / 017156 and WO 2017 / 015636, which are incorporated herein by reference in their entirety); medical instruments and machines such as MRI and CT machines; ultrasound systems; and consumer products such as home appliances and home systems, including home management systems, air conditioning and heating systems, washing machines and dryers, dishwashers, ovens, slow cookers, and other cooking appliances.

[0207] Various embodiments may be programs, software, or computer instructions embodied or stored in a computer or machine-usable, readable, or executable medium, which, when executed by a computer, processor, and / or machine, cause the computer or machine to perform the steps of a method. For example, a machine-readable program storage device may be provided, tangibly embodied with a machine-executable program of instructions to perform the various functions and methods described herein.

[0208] The systems and methods of this invention can be implemented and operated on a general-purpose computer or a special-purpose computer system (or device). The computer system can be any known or future known system and may include hardware processors, memory devices, storage devices, input / output devices, internal buses, and / or communication interfaces for other computer systems, combining communication hardware and software. The GUI technology of this invention can also be implemented on mobile devices, etc. Implementing the various computer instructions, software protocols, and modules described herein on a general-purpose computer can convert the general-purpose computer into a special-purpose computer system configured to perform the specific methods, operations, actions, and behaviors described herein.

[0209] Figure 19An example computer system 100 is shown that can implement the systems and / or methods of the present invention. One or more central processing units (e.g., CPUs) 2 may include one or more arithmetic logic units (ALUs), cache memory, and registers and / or register files. Registers are small storage devices; a register file may be a set of multiple registers. Cache memory is a fast storage memory device, for example, comprising static random access (SRAM) chips. Cache memory is used as a temporary buffer to store data used by the CPU 2. The illustration shows a simplified hardware configuration. The CPU 2 may include other combinational circuitry and storage devices.

[0210] One or more central processing units (CPUs) 2 execute instructions, for example, stored in memory 4, which are then transferred to registers in CPU 2. For example, bus 6 is a wire carrying data bits between components. Memory 4 may contain an array of dynamic random access memory (DRAM) chips and store programs and data used by CPU 2 for execution. System components may also include input / output (I / O) controllers and adapters connected to CPU 2 and memory 4 via buses (e.g., I / O buses) and to I / O devices. For example, a display / graphics adapter connects to monitor 28 or another display device / terminal. Disk controller 10 connects to hard disk 24, for example, for permanent storage; serial controller 12, such as a Universal Serial Bus (USB) controller, can connect input devices such as keyboard 22 and mouse 20, and output devices such as printer 26; network adapter 14 connects the system to another network, for example, to other machines. The system may also include expansion slots to accommodate other devices connected to the system. For example, hard disk 24 can store programs containing instructions and data for implementing the aforementioned methods and systems. These programs can be loaded into memory 4 and then into CPU storage devices (e.g., cache memory and registers) for execution by the CPU (e.g., ALU and / or other combinational circuitry or logic). Alternatively, all or some of the instructions, programs, and data for implementing the aforementioned methods and systems can be accessed and / or executed via network 18 at another computer system or device. Figure 19 This is merely an example of a computer system. Computer systems in which the methods or systems of this invention can be implemented are not limited to... Figure 19 The configuration shown. Rather, another computer system may implement the methods of the invention, for example, including, but not limited to, dedicated processors such as field-programmable gate arrays (FPGAs) and accelerators.

[0211] In one embodiment, the present invention may be embodied as a computer program product, which may include a computer-readable storage medium (or multiple media) and / or a computer-readable storage device. This computer-readable storage medium or device may store computer-readable program instructions to cause a processor to perform one or more methods described herein. In one embodiment, the computer-readable storage medium or device includes a tangible means for holding and storing instructions used by an instruction execution means. Examples of computer-readable storage media or devices may include, but are not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof, such as computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), read-only optical disk (CD-ROM), digital versatile disk (DVD), memory sticks, but are not limited to these examples. A computer-readable medium may include a computer-readable storage medium (as described above) or a computer-readable transmission medium, which may include, for example, coaxial cable, copper wire, and optical fiber. Computer-readable transmission media may also take the form of sound waves or light waves, such as those generated during radio frequency, infrared, wireless, or other media that contain radio waves, magnetic waves, or electromagnetic waves.

[0212] As used herein, the term "computer system" can encompass various combinations of fixed and / or portable computer hardware, software, peripherals, mobile devices, and storage devices. The computer system may comprise multiple individual elements networked or linked for collaborative execution, or may comprise one or more independent elements. The hardware and software elements of the computer system of this invention may be contained within and may be included in fixed and portable devices such as desktop computers, laptop computers, and / or servers. Modules may be elements of means, software, programs, or systems that implement certain "functions," which may be embodied as software, hardware, firmware, electronic circuits, etc.

[0213] Memory 4 and memory device 1802 represent the example storage device 1120, which can be implemented as one or more computer-readable storage media as described in this specification and can be used to store various data and information about computer system 100.

[0214] In one embodiment, the storage device 1120 may store registration information, such as user identifiers and user accounts. Registration information can be stored via data storage commands sent by the data storage manager 1064. In one embodiment, the registration information is stored in the storage device 1120. The registration information may be stored as one or more data structures. These data structures may include linked lists, B-trees, binary trees, heaps, stacks, queues, hash tables, red-black trees, binomial heaps, Fibonacci heaps, etc. In one example, the registration information may be stored in a registry. The registration information contains at least a user identifier related to the user and account. Since multiple users can be assigned to the same account, the system can use shared account flags (such as semaphores, bits, etc.) to track the account. When multiple users are assigned to the same account, the shared account flag may be set to a first specific value. Otherwise, the shared account flag may be set to different specific values. Using shared account flags is one way to track shared accounts, and the invention is not limited to the example described. Other methods may be used. The shared account flag may be a column in the registry. For each user identifier with the same account, the shared account flag is set to a specific value and related to the user identifier.

[0215] In other respects, multiple accounts can be linked together. In an embodiment, the user manager 1056 can send commands for managing user accounts. In embodiments of the invention, multiple accounts can represent teams such as research, projects, companies, universities, or experimental teams. The system can use multiple account flags to track multiple accounts and teams. When different accounts are linked, multiple account flags can be set to a first specific value; otherwise, multiple account flags can be set to different specific values. Using multiple account flags is one way to track links between different accounts, and the invention is not limited to the examples described. Other methods can be used. In one embodiment, multiple account flags can be columns in a registry. For each linked account, multiple account flags are set to specific values ​​related to the account.

[0216] In other embodiments, the storage device 1120 may also store login history data. The login history data may be received via the input manager 1052, organized via the user manager 1056, and stored via the data storage manager 1064. The login history data may include user identifier / account and time / date information for each user (or other user) logging into the system. The login history data may be maintained in the storage device 1120 for a predetermined or indefinite period. The predetermined period may be based on a specific application to be executed or to be executed.

[0217] In other embodiments, the storage device 1120 may also store user selection history. User selection history can be received by the input manager 1052, organized by the user manager 1056, and stored by the data storage manager 1064. User selection history may include selected menu items, the user identifier / user account related to the selection, and the time / date of the selection. User selection history may also be stored in the storage device 1120 within a predetermined or indefinite period. The predetermined period may be selected based on the MUI module that initially made the user selection. The predetermined period for storing user selection history and login history data may be the same.

[0218] In other embodiments, the storage device 1120 may include exclusion information. The exclusion information may include menu items and / or selections to be excluded from display on a tiered menu layer on a MUI for one or more users, devices, or interfaces. The exclusion information can be managed via commands sent through the exclusion manager 1058 and stored via commands sent through the data storage manager 1064.

[0219] Commands sent or provided by the menu manager 1054 of the systematized user interface control system 1102 allow users to move bidirectionally between hierarchical menu layers (forward and backward), where backward movement leads to a higher hierarchical menu layer and forward movement leads to a lower hierarchical menu layer, including the ability to view selected or unselected past or previous menu items. For example, on the MUI, various menu layers and / or selections in one or more layers of a specific path of hierarchical menus can be viewed simultaneously.

[0220] In one embodiment, a display command may be provided by a display manager 1050 to display a specific set of hierarchical menu layers (multi-layers) on a specific portion of the MUI. The display command is configured to display one or more menus in one or more portions of the MUI. A specific hierarchical menu layer may contain one or more menu items (or options). The display command may include one or more menu items, a specific display order, display orientation, display size (and format), and the manner in which display options are displayed (such as a scrolling method), although other arrangements and / or display options may also be considered. In one embodiment, the scrolling method may define the display orientation; therefore, the display command does not necessarily include a separate display orientation and scrolling method.

[0221] In one embodiment, each menu item in a specific tiered menu layer may be displayed at the same size. In other embodiments, one or more specific menu items may be displayed larger or smaller than other menu items.

[0222] The display command can specify a scrolling method. For example, the display command can specify that menu items should be displayed in a graphics wheel, which can be rotated in, for example, horizontal or vertical (e.g., left and right or up and down) or another direction. In another embodiment, the display command can specify that menu items should be displayed as a graphics slider, which slides the items in, for example, horizontal or vertical (e.g., left and right, up and down) or another direction.

[0223] Different display commands can specify different scrolling methods or directions, or different commands can employ the same or similar scrolling methods or directions. In one embodiment, the orientation in different commands (such as a first command and a second command) can specify that the orientations are substantially orthogonal to each other. In other embodiments, the orientation can be horizontal, substantially horizontal, vertical, substantially perpendicular, concentric, and substantially concentric with respect to each other. As used in this specification, it can be substantially + or -5°. In other aspects, it can be substantially + or -10°. In another aspect, it can be substantially + or -15°. In other aspects, it can be substantially determined by percentages such as 80% or 90%.

[0224] Figures 2A to 2O Examples of user interface displays in different embodiments are shown, the details of which are described in more detail below.

[0225] Figure 3 A flowchart illustrating another aspect of a method for interactively displaying interactive items on a user interface display is provided, including details of the method, where vertical and horizontal switching of the menu layer is possible. The method may be executed automatically by at least one hardware processor. In step 302, a list of menu items may be displayed on the first portion of the user interface display. The menu item list is displayed on the first portion in a first visual orientation. For example, the first visual orientation may be vertical. The menu item list may contain one or more menu items from a first menu and may be displayed in response to a first display command provided by the display manager 1050.

[0226] Figure 2A An example of a user interface display in one embodiment is shown. As shown, the menu item 202 is displayed in an orientation (e.g., vertical) in the first portion 204 of the display 206. The menu item is interactive, for example, in that the menu item is selectable, and selection (e.g., a user selects a menu item by clicking on a user interface menu item) causes the computer to perform a programmed function.

[0227] like Figure 2AAs shown, the menu item 202 of the first menu is positioned in the first portion 204 of the interface in a vertically oriented (i.e., first orientation) scroll wheel. The MUI includes a display 206. The first portion 204 can display the menu item 202 with a first display command of a first menu of user-selectable options to be displayed on the first portion 204 of the MUI. As previously mentioned, the first display command can be provided by the display manager 1050.

[0228] The first display command includes menu items of the first menu (in one embodiment, the menu items are stored in the storage device 1120), scrolling method / orientation, and size (and format). For example, the orientation of the menu items of the first menu (which will be displayed in the first section) may be vertical. The first display command may also include a display position, such as the position of the first section. The first section may be located in the center of the MUI. Each item can be selected by the user.

[0229] In one embodiment, the first portion may include a decision area. The decision area may be located in a central position within the first portion. The decision area may be a location in the first or currently used portion where menu items are highlighted or brightly displayed for immediate selection. For example, in Figure 2A In the decision area, "Menu Item 4" is displayed in a larger font than other menu items to highlight or brighten the menu item for immediate selection. The first display command that triggers the provision of the first menu can specify the menu item displayed in the decision area to be highlighted or brightened, such as by displaying it in a larger font than other menu items not in the decision area. In other aspects, the menu item displayed in the decision area can be bolded, italicized, brightened, or underlined using a color different from the background.

[0230] In other embodiments, the first display command may specify menu items to be dimmed outside the decision area, such as making the menu items smaller and dimmer relative to other menu items in the decision area.

[0231] The first display command is executed by the hardware processor and causes the first menu to be displayed on a first section of the MUI. The MUI allows the user to select one or more menu items from the menu items displayed on the first section 204, and to navigate through hierarchical menu layers based on the selection of previous and / or subsequent menu items. When a menu item is selected from the first menu displayed on the first section 204 of the MUI, the input manager 1052 receives and interprets the selection.

[0232] like Figure 2AAs shown, all first menu items 202 displayed in the first section 204 are selectable. "Menu item" 4 is displayed as a highlighted menu item and is brightly displayed as immediately selectable. As used in this specification, "immediately selectable" means a single action, such as a user click, to select a menu item. "Menu item" 4 is selectable and brightly displayed as a highlighted menu item, while other "menu items" (1, 2, 3, 5, and N) are dimmed as dark menu items. Darkened menu items are not immediately selectable, meaning they require more than one user action to select. The user selects a brightly displayed immediately selectable menu item by clicking it. Other menu items can be brightly displayed to be immediately selected by rotating the scroll wheel or clicking it. The input manager 1052 receives a signal indicating that an immediately selectable menu item has been clicked, causing the input manager 1052 to execute on the processor 1110 to detect the selection of the highlighted immediately selectable menu item. Upon selection, the input manager 1052 sends a command to the menu manager 1054 indicating the selection. Menu manager 1054 then determines the new menu layout to be displayed based on the selection and provides a relocation command to display manager 1050 to cause a change in MUI.

[0233] Please refer to the reference again immediately. Figure 3 In step 304, upon detecting a menu item selection in the menu item list, the menu item list is repositioned to a second portion of the user interface display. The menu item list is displayed on the second portion in a second visual orientation that is substantially orthogonal (e.g., perpendicular) to the first visual orientation. For example, the second visual orientation could be a horizontal orientation.

[0234] The relocation command causes the first menu of menu selection 202 to be relocated from the first portion 204 of the MUI display 206 to the second portion 208. Figure 2B The result of the relocation command is shown. The relocation command may include the menu selection of the first menu to be displayed in the second section 208, the size and orientation of the display, the necessary display visual elements, an instruction to select a menu item for relocation, and any other information discussed in this specification regarding the display command. The relocated first menu, currently displayed as a past menu in the history or second section 208, may contain one or more or all of the menu items 202 available to the user and previously made selections. The user-selected menu item 202 becomes a previously selected menu item, while unselected menu items in menu item 202 become previously unselected menu items. Previously unselected menu items represent the hierarchical menu layers of the previous navigation. After relocating the menu item 202 of the first menu, the display manager 1050 causes the MUI to display the submenu items 210 of the second menu as a new current or subsequent menu item layer for user interaction in the current or first section 204, following the first menu selection. Figure 2B As shown, the subsequent or second menu selection layer includes the second submenu item 210 displayed in the current or first part 204 of the MUI display 206.

[0235] In the method according to the embodiment, a relocation command is sent once a signal indicating that menu item 202 has been selected from the first portion 204 is received from the input manager 1052. For example, the menu manager 1054 provides the relocation command to the display manager 1050. The relocation command causes the display manager 1050 to move the first menu from the first portion 204 of the MUI display 206 to the second portion 208 of the MUI display 206 in the second menu. The second portion 208 is a position on the MUI display 206 different from the first portion 204. Since the menu item was selected from the first menu of the menu item 202, as shown in the second portion 208, the relocated first menu of the menu item 202 will now have previously selected menu items and previously unselected menu items (e.g., one or more menu items that the user could select but did not select). The relocation command may include the first menu item, scrolling method and / or orientation, display size (and format), and the position of the second portion.

[0236] In one embodiment, the second portion 208 is further away from the center of the MUI display 206 than the first portion 204.

[0237] In one embodiment, the orientation of menu item 202 displayed in the first menu of the second portion 208 differs from the orientation of submenu item 210 displayed in the second menu of the first portion 204. For example, the orientation of menu item 202 in the second portion 208 may be substantially orthogonal to the orientation of submenu item 210 in the first portion 204. The relocation command may specify the orientation of menu item 202 as horizontal (while the first display command specifies the orientation of menu item 202 as vertical). In other embodiments, the orientation may be reversed, where menu item 210 in the first portion 204 is horizontal and menu item 202 in the second portion 208 is vertical. In this embodiment, the first portion 204 is located at the lower center of the MUI display 206, while the second portion 208 is located at the upper part of the MUI display 206.

[0238] The relocation command can also specify menu items of different sizes. For example, the selected menu item (triggering relocation) of the first menu can be specified to be highlighted, such as by displaying it in a larger font than the unselected menu items. In other aspects, the selected menu item can be displayed in a bolder, italic, or brighter color than the background, or underlined. In another aspect, the relocation command can also specify the relative position of the menu items 202 within the second section 208. For example, the selected menu item can be positioned in the center of the second section relative to other menu items (unselected menu items).

[0239] In other aspects, unselected menu items in a tiered menu layer can be displayed in a faded manner. For example, the reposition command can specify a smaller font size or a dimmer appearance for unselected menu items relative to selected menu items. In other aspects, the reposition command can specify unselected menu items to be displayed further away from the center of the second section compared to selected menu items in the same tiered menu layer.

[0240] The first and second parts may be displayed on the user interface display without overlapping. Menu items repositioned to the second part can be selected from said position or location, and the selected menu item can be graphically highlighted, for example, to provide a visual indication of items in the selected list. The selected menu item can also be centered to the left and / or right of other menu items. The sub-menu items displayed before repositioning the menu item are also optional. Figure 2B An example of a user interface display shown in an embodiment with a repositioned menu item list. As shown, menu item 202 is repositioned to a second portion 208 of display 206, for example, above the first portion 204, and displayed horizontally. As described in more detail below, the second portion of the display may contain multiple layers of menu items, such as past decision layers and options not selected in these layers. Therefore, the number of layers for past decisions can be, for example, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20 or more, such as 1-2, 1-3, 1-4, 1-5, 1-6, 1-7, 1-8, 1-9, 1-10, 1-11, 1-12, 1-13, 1-14, 1-15, 1-16, 1-17, 1-18, 1-19, 1-20, and nested ranges therewith, such as 2-20, 2-19, 2-18, 3-20, 3-19, 3-18, etc. For example, the second part can visualize the path presentation of past decisions made and paths where no other decisions were made (other paths). In one embodiment, the past decisions taken (selected menu items) can be, for example, vertically or, for example, center-aligned.

[0241] A relocation command for a first menu of user-selectable options displayed on the second portion 208 of the MUI display 206 causes the second portion 208 to display a first menu item 202. As previously mentioned, the relocation command is provided to the display manager 1050 by the menu manager 1054. The first menu of user-selectable options may contain both previously selected and previously unselected menu items. The first menu may contain one or more of the first menu items 202 that are selectable by the user. The menu items 202 may be selected immediately or not immediately.

[0242] The second part 208 may also include one or more decision areas. The relocation command may also specify menu items displayed within the decision area to be highlighted or emphasized. In other aspects, the menu items displayed within the decision area may be bolded, italicized, highlighted, or underlined using a color different from the background. In other embodiments, the relocation command may specify the same. In other embodiments, the relocation command may specify menu items displayed outside the decision area to be faded or diluted.

[0243] The first portion 204 and the second portion 208 are displayed on the MUI display 206, such that both are viewable, for example, simultaneously. The MUI display 206 may be presented via one or more physical display screens. The second portion 208 may include one or more menus, each containing both previously selected and previously unselected menu items from the previously navigated tiered menus. Figure 2C In the presentation shown, the second section 208 (history section) contains menu item 202 and submenu item 210, each of which is contained within the first section 204 of the previous MUI presentation. Previously selected menu item 202 and submenu item 210 (i.e., those that caused sub-submenu item 212 to appear in the first section) may be highlighted or emphasized to indicate that they were previously selected. Figure 2C As shown, "Menu Item" 4 and "Submenu Item" 3 are highlighted to indicate that they were previously selected.

[0244] Previously unselected menu and submenu items are displayed as selectable options. Previously selected menu items (or selections) may also be displayed as selectable options, both shown in the second section 208 (e.g., the history section, which may contain one or more menu items previously available to the user). The history section contrasts with the current section, which may contain the currently available user options for the current tiered menu layer (e.g., located in the first section displayed). The history section may also allow the user to make selections, for example, by making selections in previously selected layers and / or menus. Thus, the second history section 208 may represent a "page path guide" to show the user the sequential path to the currently selected menu as shown in the first current section 204. Further details regarding selections in the second section 208 are provided below.

[0245] In some embodiments, the first portion 204 may be adapted to occupy a larger portion of the display area of ​​the MUI than the second portion 208. The second portion 208 may be displayed on an area smaller than the first portion 204. The first portion 204 and the second portion 208 may be adapted to be displayed in a way that contrasts with their backgrounds. For example, the first portion 204 and the second portion 208 may be displayed as bright pixels relative to a dark background or dark pixels against a bright background.

[0246] In other embodiments, the menu manager 1054 may provide commands (such as a relocation command) to move or relocate a menu from one part of the MUI display 206 to another part of the MUI display 206. In one embodiment, moving or relocating a menu and / or menu item may include providing a command to move the menu from one part of the display to another. In another embodiment, moving or relocating a menu may include sending multiple commands, such as one command to delete a menu from a first part 204 of the display, and another command to display the menu (in the same format and / or orientation or in a different format and / or orientation) on a second part 208 of the display. For example, this relocation may occur as a user selects from a menu (e.g., a first menu).

[0247] Please refer to the reference again immediately. Figure 3 In step 306, on the first portion of the user interface display, in the case of the menu item list previously displayed before repositioning to the second portion, a first list of submenu items related to the selected menu item is displayed in a first visual orientation. For example... Figure 2B As shown, the first sublist of menu items 210 is, for example, displayed vertically in the first section 204.

[0248] Please refer to the reference again immediately. Figure 3In step 308, as a selection of a submenu item is detected from the first list of submenu items, the first list of submenu items is repositioned to the second portion, wherein the first list of submenu items is displayed in a second visual orientation and stacked with the menu item list displayed in the second portion. In step 310, on the first portion of the user interface display, a second list of submenu items related to the selected submenu item is displayed in a first visual orientation (e.g., vertical). Figure 2C An example of a user interface display showing a second list of submenu items in one embodiment is shown. As shown, a first list 210 of submenu items is repositioned to the second section 208, for example, stacked below the repositioned list of menu items 202, for example, horizontally stacked. A second list of submenu items 212 (i.e., sub-submenu items related to the selected submenu item) is displayed in the first section 204. Depending on the depth of the navigation menus or submenus, the horizontal menu structure in the second section 208 may accumulate to a number of menu layers exceeding the number displayed together on the display portion at the second section 208 (e.g., the number of stacked layers exceeds the screen portion allocated for the horizontal menu structure of the second section 208). In one embodiment, the horizontal menu structure of the second section 208 may display n number of menu layers, for example, the last 3 submenus, thereby allowing scrolling capability. For example, scrolling up allows a user to view other menu items. The number n can be any value, but is not limited to 3, for example 2, 3, 4, 5, etc. In another embodiment, the top m (e.g., 2) menus may be displayed together with the bottom 1 submenu to provide a top-level context for final decision-making. The number m can be any value, not limited to 3, such as 2, 3, 4, 5, etc. The scrolling function allows other menu items to be displayed; for example, the user can scroll to view other menu items. The user can also expand the entire multi-level menu and submenus.

[0249] like Figure 2C As shown, the subsequent layer of menu selection (e.g., sub-submenu item 212) can be at least one hierarchical menu layer (from the third menu) or more than one hierarchical menu layer below the first menu of menu item 202 (from the fourth, fifth, sixth, etc. menus). Figure 2C In the example, sub-submenu item 212 represents a third menu in a two-tiered hierarchy below the first menu of menu item 202.

[0250] For example, when a menu item is selected, the process of repositioning the menu item from one part of the user interface display to another can continue up or down the menu item layer. Figure 3The processing of steps 308 and 310 can be repeated for additional layers of submenus. In another aspect, selecting a menu item from the repositioned list of menu items can function as a "back" button, eliminating the need for the user to specifically click the back button to return to the previous list of menu items. In yet another aspect, for example, if the number of repositioned lists of stacked menu / submenu items reaches a predetermined number or threshold, causing the stacked lists in the area of ​​the second part to become too large and encroach on the area of ​​the first part, the stack itself can be displayed, for example, as a rotating wheel or sliding axis in a first visual orientation. Thus, for example, each menu item in the stacked list can be displayed in a second visual orientation (items can slide along, for example, a horizontal direction), while each list in the stacked list can slide along a direction in the first visual orientation (e.g., vertical). In this way, the vertical page path can be set on the horizontal sliding axis and contextualized by other options located to the left and / or right of the center one (selected option). Any layer can be adjusted in real time without having to go back. This display of the vertical and horizontal sliding axes allows for the navigation of an option tree and the selection of desired leaf options. On the other hand, the number of menu and / or submenu items can be collapsed and expanded. For example, the most recent lowest or last 'n' level (e.g., 3 levels) can be displayed, while the remaining levels are collapsed. For example, the collapsed levels can be expanded by user input. To illustrate further, the highest 'm' level (e.g., 2 levels) and the lowest level (e.g., '1' level) can be displayed, representing the top-level context with the most recent option or decision that the user is currently processing (i.e., the lowest level).

[0251] Although Figures 2A to 2C The first visual orientation is displayed vertically, and the second visual orientation is displayed horizontally, but the orientations can be switched. For example, the first visual orientation can be horizontal, and the second visual orientation can be vertical. Alternatively, the first and second visual orientations can be displayed in any other position.

[0252] As mentioned above, menu items and related sub-menu items can be displayed as a slider graphic element, a rotary wheel graphic element, or another graphical user interface element. For example, the following reference can be used. Figures 2H to 2J The concentric wheel element mentioned above.

[0253] In an embodiment, the order or arrangement of menu items within a menu layer can be determined based on the attributes of the menu items. The way menu items are displayed can be based on attributes selected from the following: whether the menu item is selected from previously selected or previously unselected menu items, whether the menu item is selectable or unselectable, whether the menu item includes one or more characters typed by the user, whether the menu item is part of an advanced context menu (described in more detail below), and / or whether the menu item is located in a more central position in the list relative to other positions in the list.

[0254] In embodiments, the way menu items are adapted for display can be determined based on several different factors, namely, the order, arrangement, coloring, and presentation of menu items. For example, the menu manager 1054 and display manager 1050 can be configured together to highlight menu items that are selected or previously selected, currently available to the user (i.e., optional), and / or located in the decision area of ​​the first portion 204 or the second portion 208. The menu manager 1054 and display manager 1050 can be further configured to fade menu items that are not selected or previously not selected, currently unavailable to the user, and / or located far from the decision area. In some embodiments, immediately selectable menu items can be highlighted, while non-immediately selectable items can be faded. In some embodiments, highlighting or fading menu items can include brightening or dimming the display of menu items, as discussed in this specification. Brightening or highlighting can include, for example, bolding, increasing font size, changing font, underlining, changing brightness or contrast, or adjusting the position on the display relative to other items. Fading or dimming can include reducing font size, changing font, darkening, changing brightness or contrast, or adjusting the position on the screen relative to other items.

[0255] By allowing users to select previously unselected menu items in the previous navigation menu layer displayed on the second part 208 of the MUI display 206, and newly displayed menu items on the first menu displayed on the first part, the current menu, the MUI allows users to jump to different paths of menu items (e.g., by selecting one or more other menu items on the same, higher, or lower levels of the menu). (See also:) Figure 2C As discussed earlier, after selecting a menu item, the previously navigated menu item (including submenu items, sub-submenu items, etc.) is relocated to the second part 208.

[0256] Previously selected menu items in Part 208 can be highlighted or emphasized to visually indicate the menu path taken to reach the menu or submenu currently displayed in Part 104. Previously unselected menu items in Part 208 can be selected to allow the user to jump to that branch of the menu. Figure 2C In the example, the user has previously selected "Menu Item" 4 and "Submenu Item" 3. Selecting a new and previously unselected submenu item 210 from the second section 208 will cause the menu manager 1054 to send a command to display a new list of sub-submenu items 212 related to the newly selected submenu item 210 as the current menu to be displayed in the first section 204. Selecting a new and previously unselected menu item from menu item 202 will cause the menu manager 1054 to send a command to display a new list of submenu items related to the newly selected menu item 202 as the current menu to be displayed in the first section 204. In this way, the user can actively jump between sections of the menu tree without being guided back to a previous decision.

[0257] When a previously unselected menu item (or submenu item, or sub-submenu item, etc.) is selected, a save command can be sent to store the current menu state in the first section before displaying subsequent menus in the first section. In an embodiment, as disclosed in more detail below, navigating to the last branch of the menu tree in the executable menu layer via menu items allows the user to select one or more parameters. If the user navigates away from the executable layer menu, a save command can be sent via menu manager 1054 to data storage manager 1064 to store the parameters currently selected when the user navigated. Therefore, if the user later wants to return to the executable layer menu, the last selected parameter will be displayed.

[0258] Previously unselected menu items can be selected within the past menu of previously navigated menu items. In one embodiment, previously unselected menu items can be selected immediately, requiring only a click; or they may not be immediately selectable, requiring another step to highlight them before selection. In another embodiment, previously selected menu items may be unselectable because the user has already selected them. In a further embodiment, only previously selected menu items in the lowest tier of the past menu (i.e., the menu immediately preceding the current first menu) are unselectable, while previously selected menu items from higher tiers remain selectable. Figure 2C In the provided example, "Submenu Item" 3 is not selectable, while "Menu Item" 4 is selectable.

[0259] In one embodiment, various menus are displayed on a background. In another embodiment, the menus are overlaid on the background. The background may consist of one or more colors. In one embodiment, at least a predetermined percentage of the background pixels may be monochrome. For example, at least a predetermined percentage of the background pixels may be black. For example, 75% of the background pixels may be monochrome (e.g., black, white, gray, etc.). Specific percentages have been described by example, and other percentages may be used.

[0260] In embodiments, the display command and relocation command can specify a background, including preset percentages and colors, such as black, white, gray, etc. In some embodiments, the background may also include a menu area other than text (e.g., menu items). In one embodiment, the menu text is displayed with a color that contrasts with or highlights the background text. For example, when using a black background, white or yellow can be used as the text color, although other colors may also be used. In other embodiments, the background and / or text may contain more than one color.

[0261] In some embodiments, the initial or first menu (i.e., the startup current menu) may be the default menu displayed when a registered user logs in. In one embodiment, the default menu may be customized to serve as a specific user identifier. In other aspects, the default menu may be specific to a MUI module. For example, the default menu may contain menu items as a list of assays, tests, runs, clinical trials, etc. In embodiments according to this, the default menu may be determined based on one or more of the following: the MUI module to be run, the device location running the MUI module, the user identifier, and the menu application. For example, a device located on a user's desktop may run an MUI module that defaults to a default menu suitable for selecting experimental design or experimental analysis options. In another example, a device located on a clinical instrument may run an MUI module to provide a default menu suitable for selecting options for running experiments and collecting data. In embodiments, the default menu may be a first menu, a second menu, a third menu, and / or any other menu from a layer within a hierarchical menu tree.

[0262] In one embodiment, any menu provided in any part of the MUI display may include a search function. The search function allows the user to enter keywords or other input regarding menu items (options). User input is received via input manager 1052 and forwarded to menu manager 1054 for searching. The search allows filtering functions (menu items) using entered keywords or other input, thereby reducing the time required to find the desired menu item. The interface for the search function may be located in the center of an opposite portion of the MUI display 206; or, it may be located in other parts of the MUI display 206. In a further embodiment, the search function does not provide a visual interface. In this embodiment, the user can access the search function only by typing.

[0263] In one embodiment, any menu item that matches or partially matches the keyword may be displayed to highlight the menu item. For example, the menu item may be displayed in a larger size than other menu items that do not match or partially match the keyword. In other embodiments, the menu items(s) may be bolded, italicized, or highlighted, or underlined, using a color different from the background. In other embodiments, the menu items that do not match or partially match the keyword may have smaller or lighter text compared to the text of the menu items that match or partially match the keyword. In this embodiment, the slider or scroll wheel may automatically advance and / or rotate to display menu items that match the search query.

[0264] In one embodiment, a first menu selection can be used as a filter on a second menu. In a hierarchical tree, each of several items in the first menu can lead to the same second menu. However, the first menu selection determines which menu items are displayed when the second menu is shown. In a simple example, the first menu may contain menu items related to team roles, while the second menu may contain menu items related to team responsibilities. Selecting a specific team role on the first menu filters the second menu to display only team responsibilities relative to the selected role. In some embodiments, this filtering is performed by making specific items in the second menu unselectable.

[0265] In one embodiment, any selection made in any menu can serve as a filter for displaying menu items in any other menu. For example, in one embodiment, a series of items in a first menu can be a series of category filters leading to a second menu. Each second menu leads to a series of submenus and ultimately to one or more execution menus to allow the user to select parameters for the selected category filter. After selecting a category filter from one or more of the category filter submenus, the user can then select another first menu item to provide a list of second menu items filtered according to the previously selected category filter.

[0266] In one embodiment, one or more menus or menu layers may be provided as an exception to the hierarchical menu tree standard discussed herein. For example, a menu layer may contain visual displays and / or video displays, rather than text-based visual elements. For example, it may be implemented where information can be better conveyed through alternative components. For example, as mentioned above, an execution layer menu may contain a walkthrough that is best presented via video or a series of images. In another example, an execution layer menu may be provided for data analysis and may provide any combination of graphs, charts, tables, etc., to aid in data analysis.

[0267] In one embodiment, an advanced context menu can be provided via one or more commands sent by the menu manager 1054. Figure 2PAn example of a systematized user interface including the advanced context menu 270 is shown. The advanced context menu 270 contrasts with the first and second sections, providing a “direct workflow mode” throughout. The advanced context menu 270 is accessible via an advanced context menu selector 290, which, in embodiments, may be located on some or all screens of the systematized user interface. In addition to items appearing in the current menu of the currently active first section 204 or one or more past menus appearing in the history second section 208, the advanced context menu 270 provides other advanced menu items 271. The advanced context menu 270 is accessible by clicking or hovering a cursor over the advanced context menu selector 290, or by otherwise indicating access to the advanced context menu 270. The advanced context menu 270 contains a selection of advanced menu items 271.

[0268] The selection of advanced menu item 271 may include items displayed in the current menu of the first (current) section 204 and items displayed in the previous menu of the second (history) section 208. According to embodiments therein, advanced menu item 271 of the advanced context menu 270 may be highlighted. For example, a larger font may be used to display advanced menu item 271. In other embodiments, the menu items(s) may be bolded, italicized, brightly displayed, or underlined using a color different from the background.

[0269] The other items included in the item selection in the advanced context menu 270 may be items that are not currently included in one of the displayed menus. That is, the selection of items in the advanced context menu 270 is driven by the current content displayed by the UI. For example, the five menu items of the first menu may be displayed as the current menu in the currently active section. Three additional menu items related to the five menu items of the first menu may be displayed in the advanced context menu 270. These three additional menu items may be items that have been excluded or restricted from the current menu for various reasons (discussed further below) from the first menu.

[0270] The advanced context menu 270 provides users with a larger array of accessible menu items without causing clutter in the currently used or historical sections. In embodiments, some of the advanced menu items 271 in the advanced context menu 270 may be infrequently selected items, for example, fewer than 50, 45, 40, 35, 30, 25, 20, 15, 10, or 5% of the use cases. The advanced menu items 271 of the advanced context menu 270 can be selected based on the user's interaction pattern with the MUI, as explained in more detail below.

[0271] In this embodiment, the advanced context menu 270 may comprise three sections. As previously described, the first top 272 of the advanced context menu 270 may contain advanced menu items 271 related to currently used menus. The second middle section 273 of the advanced context menu 270 may contain advanced menu items 271 related to MUI modules available on the same workstation where the advanced context menu 270 is selected. These options allow the user to switch modules according to their desired workflow. The third bottom 274 of the advanced context menu 270 may contain global functions such as login / logout functionality, user manuals and instructions, EULA information, and privacy policy information. The aforementioned order is not limiting, and any of the advanced menu items 271 may be provided in a different order.

[0272] In an embodiment, when the advanced context menu 270 is selected, the MUI dims and / or blurs other graphics, text, etc. The advanced context menu 270 is displayed on a transparent background such that the advanced context menu 270 and the rest of the background are the same (e.g., black). Therefore, the MUI provides dialog boxes adapted to be displayed in the foreground of the UI display to provide additional information or notify the user of errors, wherein the background of the dialog box is further adapted to conform to the background of the first and second portions of the UI display, and further wherein when the dialog box is displayed in the foreground of the UI display, one or more of the text, graphics, photos, and videos displayed in the background of the first and second portions of the UI display are adjusted to be out of focus.

[0273] In one embodiment, when a menu is displayed, certain menu items contained in the hierarchical menu tree, i.e., the first menu, second menu, third menu, etc., can be excluded or restricted. Exclusion and restriction can be managed together by the exclusion manager 1058 and the menu manager 1054. Any menu in the displayed menu tree contains one or more menu items from that menu, but not necessarily all items in that menu need to be displayed. The display or restriction of menu items in the hierarchical menu layer can be based on an exclusion table. The exclusion table may correspond to a user identifier, email address, username, team, and / or account. In other embodiments, one or more entire menus in the menu tree can also be excluded based on the exclusion table. In some embodiments, exclusion or restriction information can be stored in the storage device 1120. The exclusion or restriction information can be stored as a data structure. Any data structure described herein can be used.

[0274] Exclusion or restriction information can be used to exclude menu items from the view of specific users, user groups, user types, etc. For example, management menu items or menu layers can be excluded from the view of an engineer or technician user or operator. In another example, design menu items or menu layers can be excluded from the view of a lab assistant or lab technician user or operator.

[0275] The user identifiers, accounts, and menu items and / or menus to be excluded can be entered by the administrator. For example, the administrator console module, which will be discussed in more detail below, can be used to manage and generate exclusion tables. Management can be completed when a user registers with the system. In other embodiments, exclusion information can be added after registration and updated periodically.

[0276] In one embodiment, whenever a user logs into the system, the hardware processor maintains a login (and logout) record via the data storage manager 1064. In one embodiment, the record (i.e., the login history data) can be in the form of any data structure described herein. In one embodiment, the login history data may include a user identifier and / or account, login time / date, and logout time / date. In one embodiment, once login information is received, the data storage manager 1064 adds the user identifier and / or account and login time / date to the login history data.

[0277] In some embodiments, before sending a command to display any menu, the menu manager 1054 may check an exclusion table (e.g., stored in the storage device 1120) to determine whether any menu items in the initial display menu (e.g., the default menu) are listed to be excluded from the display of the user (or account). In one embodiment, the menu manager 1054 may compare the user identifier and / or account of the currently logged-in user with the user identifier and / or account listed in the exclusion table. If a match is found, the menu item listed in the exclusion table is excluded and not displayed in the initial display menu. The exclusion may be performed by sending a separate exclusion command and / or instruction, or alternatively, by modifying any display command that results in the display of available menu items. The menu manager 1054 may remove menu items included in the list from the menu items in the initial display menu (e.g., the default menu) and send a first command for the menu items that have not been removed.

[0278] In some embodiments, each time the input manager 1052 receives a menu item selection in the current menu, before sending a relocation command, the menu manager 1054 may decide whether to list any menu items (or exclude lower-level menus) that are currently in the current menu but are lower than the tiered menu layer currently displayed on the MUI display 206. This decision may use login history data and an exclusion table. The login history data can be used to identify the same user (user identifier or account) still logged in and compare it with the user identifier and account in the exclusion table. In other embodiments, the menu manager 1054 may use the user identifier and account received from the user manager 1056 instead of login history data to make this decision. In other embodiments, a similar decision is made before sending any relocation or display command.

[0279] In other embodiments, different exclusion tables may be used depending on whether the menu item is to be displayed on the MUI display 206 in the first portion 204 or the second portion 208. According to this embodiment, the exclusion table may have additional information columns, one column for each portion (menu). The columns for the first portion list menu items to be excluded when displayed on the first portion 204 of the MUI display 206, the columns for the second portion 208 list menu items to be excluded when displayed on the second portion of the MUI display 206, and some columns for the additional portions list additional menu items to be excluded when displayed on any additional portion of the MUI display 206.

[0280] As mentioned earlier, an account can be associated with multiple users (user identifiers). Therefore, when an account is used as the basis for exclusion, all users associated with that account can have a menu item for displaying exclusions on the MUI display 206.

[0281] In another embodiment, since certain accounts can be linked, any account linked to the account can also have excluded menu items when the account is used.

[0282] In other embodiments, instead of excluding menu items, menu items can be moved to a position relative to the menu to dilute the menu items related to other menu items. According to the embodiments described, the exclusion table can be used by the menu manager 1054 to reorder or change the position of menu items on a hierarchical menu layer. Subsequent commands (first command, second command, and / or third command) can reflect the changed position of the menu items.

[0283] In other embodiments, menu items (or hierarchical menu layers) may be excluded based on a specific device or the location of a device. The exclusion may be based on any one or more devices that execute various software instructions of the systematized user interface control system 1102.

[0284] Exclusion or restriction information may be stored, for example, as a data structure in the storage device 1120. Each device may have an identifier, such as a Media Access Control (MAC) address or other unique identifier. The device identifier is not limited to a MAC address and may use other identifiers such as an Internet Protocol (IP) address, machine name, etc. In one embodiment, a column in the table may contain identifiers, such as MAC addresses. A second column in the table may contain menu items or tiered menus for identifiers (e.g., MAC addresses) to be excluded from the display.

[0285] In other embodiments, instead of a table (or multiple tables), the list storage of menu items and / or hierarchical menu layers is associated with identifiers (e.g., MAC addresses).

[0286] An authorized administrator and / or one or more users can enter device identifiers (such as MAC addresses) and menu items and / or hierarchical menu levels to exclude. This exclusion information can be entered when the first MUI module is installed on the device. In other embodiments, the exclusion information can be added after installation and updated periodically.

[0287] In some embodiments, before sending any command to display any menu (and menu items), once login history data is received or a notification is received, the hardware processor executing the input manager 1052 may check exclusion information in the storage device 1120 to determine whether to exclude the device's initial display menu or any menu items selected.

[0288] In one embodiment, the menu manager 1054 may compare a device identifier with a device identifier listed in exclusion information. When a match is found, certain menu items will be excluded from the display on the MUI display 206. For example, when the initial display menu for which the selection is currently displayed (e.g., the default menu), or a hierarchical menu layer below the hierarchical menu layer currently displayed on the MUI display 206, contains a list of one or more menu items to be excluded, the menu manager 1054 may remove the excluded menu items from the menu before sending a display command, and then send a display command to remove the menu items. In this example, the deleted menu items will not be displayed on the MUI display 206.

[0289] In other embodiments, certain menu items (or hierarchical menu layers) may be excluded based on the hierarchical menu layer currently displayed as the current menu (in the first part) or the previous menu (in the second part). In one embodiment, a column in the exclusion table may contain menu identifiers for the hierarchical menu layers. A second column in the table may contain menu items or hierarchical menu layers associated with the menu identifiers that are excluded from the display.

[0290] Menu identifiers indicate tiered menu layers that can be displayed on a first or second menu. Excluded menu items are those that cannot be selected from the displayed tiered menu layer. These menu items may be for specific applications. In some embodiments, when a tiered menu is displayed, as the current menu in the first section 204 or the previous menu in the second section 208, and a selection is made, the menu manager 1054 checks exclusion information to determine whether any menu items displayed in the selected tiered menu layer should be excluded before sending a command. Based on this determination, the menu manager 1054 may remove the excluded menu items from the menu before sending a response command, and then use the deleted menu items to send the response command. The exclusion can be performed by sending separate exclusion commands and / or instructions, or alternatively, by modifying the first, second, and / or third display commands that provide the display of available menu items.

[0291] In other embodiments, the exclusion manager 1058 may send an exclusion command in conjunction with the display or relocation command, instead of sending a display or relocation command using a deleted menu item. In this embodiment, the display command will have all menu items related to the menu, and the exclusion command will cause the display manager 1050 to delete the executed menu item included in the exclusion command before causing a display.

[0292] In other embodiments, the menu manager 1054 may limit the number of menu items to be displayed based on usage frequency. For example, in one embodiment, the number of menu items may be limited based on a selected frequency. In some embodiments, the frequency may be determined within a predetermined time period. The selected frequency may be preset or customizable and may include, for example, frequencies between 50% and 80%, although other selected frequencies may also be considered. By limiting the display of menu items to only those used more frequently than a certain threshold, clutter in the menu system can be reduced and the menu experience simplified.

[0293] According to this embodiment, the input manager 1052 tracks all menu item selections and stores them in the storage device 1120. In one embodiment, the list of previously selected menu items is stored in a data structure. For example, the data structure may be a menu item selection table or any other data structure (e.g., as specifically described in this specification).

[0294] In some embodiments, user choices can be tracked over a preset time period. This time period can be a day, a week, a month, or other preset or customizable periods. The specific time period can be based on the application, such as the type of clinical trial or research, the type of test, or the type of organization (e.g., a university, a company). Tracking can be repeated within each preset time period.

[0295] Each time the hardware processor of the input manager 1052 receives a notification, the input manager 1052 may record the user identifier, user name, email address, and / or account, selected menu item, and the selected time and date within a preset time period. The time and date can be obtained from a timestamp included in the notification. In one embodiment, the user identifier and account can be obtained from a login history table. In other embodiments, the user identifier and account may be included in the notification.

[0296] At the end of a specific time period, the input manager 1052 determines the selection frequency of each menu item. In one embodiment, the input manager 1052 may determine a user identifier and a selection frequency. The selection frequency is based on a comparison of the number of times a user identifier selects a menu item with the total number of selections (within the specified time period).

[0297] In other embodiments, the decision may be based on accounts in addition to the user identifier. For example, the input manager 1052 may determine the selection frequency of menu items by using at least two user identifiers with the same account. In this example, users form teams, where a single account is associated with and / or linked to two or more user identifiers. In another example, a team may contain two or more accounts associated with and / or linked together. In yet another example, teams may be formed where N unique users are associated with and / or linked to M unique accounts, where N is greater than M. A shared account flag in a registry combined with the menu item selection table can be used to identify user identifiers with the same account to determine at least two user identifiers making selections within a given time period.

[0298] For each menu item, the number of selections is aggregated for at least two user identifiers (determined from the menu item selection table). Similarly, the total number of selections is aggregated for at least two user identifiers (also determined by the menu item selection table). The frequency is then calculated based on the aggregated selections of the menu item and the total aggregated selections.

[0299] In other embodiments, frequency determination may be based on selection, where the user identifier is associated with an account linked to other accounts (e.g., user teams). According to this embodiment, when an account is linked, the input manager 1052 may use multiple account flags set to specific values ​​to identify the linked account. Once identified, the input manager 1052 may determine the frequency of selection by using selections from the user identifier of one of the linked accounts. In this embodiment, selections from other user identifiers or the same user identifier not associated with one of the linked accounts (where the same user identifier is associated with different accounts) may be ignored (not used in the decision). Similar to the foregoing, the input manager 1052 may determine the number of times menu items are selected and the total number of selections to determine the frequency. In other embodiments, the systematized user interface control system 1102 may use selections from any user identifier of one of the linked accounts to make the decision (and may aggregate selections).

[0300] In other embodiments, the frequency determination may be based on the selection of at least two user identifiers, wherein the user identifiers are associated with one or more accounts linked to other accounts. According to this embodiment, the hardware processor executing the input manager 1052 may identify the linked account using multiple account flags set to specific values ​​when the account is linked. Once the linked account is identified, the hardware processor executing the input manager 1052 may further use a menu item selection table to identify at least two user identifiers (related to the linked account) selected within a given time period.

[0301] For at least two user identifiers that indicate menu item selection, multiple selections of the menu item are summarized for each of the at least two user identifiers (determined from the menu item selection table). Similarly, the total number of selections is summarized for each of the at least two user identifiers (also determined from the menu item selection table). The frequency is then based on the summarized selections of the menu item and the total number of summarized selections.

[0302] In other embodiments, the frequency determination may be based on all selections, independent of user identifiers and / or accounts. According to this embodiment, for each menu item, the input manager 1052 may determine the frequency by comparing the number of selections of a relative menu item within a time period with the total number of selections for (any menu item).

[0303] The aforementioned frequencies can be used in conjunction with restriction commands sent by the menu manager 1054. As previously stated, the restriction command functions similarly to the exclusion command. The restriction command is used to restrict certain menu items to be displayed based on one or more criteria. For example, the restriction command may be based on the following criteria: (a) the frequency with which a user previously selected an item when logging into their account. In one example, this decision may be based on a specific time period. In another example, it may be based on the number of times a specific user logs into their account. Another criterion includes: (b) the frequency with which at least two users previously selected an item when logging into their account. In some embodiments, this may include a specific user or the amount of time based on the total time a user logs into their account. Alternatively, it may be based on the total number of logins by a specific user or the total number of logins. Furthermore, the criterion may include: (c) the frequency with which a user previously selected an item when logging into an account with multiple accounts; (d) the frequency with which at least two users previously selected an item when logging into one or more accounts with multiple accounts. For both of these examples, as described with respect to the preceding examples (a) and (b), the frequency may be based on one or more combinations of the time period during which one or more users remain logged into their accounts or the number of account logins. Furthermore, the criteria may include: (e) the frequency with which any user previously selected items when logging into any account; and / or (f) the frequency with which any user previously selected items when logging into any account involving multiple accounts. In both examples, a data structure (such as a table (or any other data structure described in this specification)) may be used to track previously selected items, which may be periodically cleared after a specific period of time has passed or after a certain total number of one or more users have logged in. In some embodiments, the criteria described in (c), (d), and (f) above may be applied to team accounts, particularly those where the users are team members of one or more teams involving multiple accounts.

[0304] When the frequency of a decision is greater than or equal to a threshold percentage, menu items can be restricted in subsequent time periods. The threshold may be application-based. In one embodiment, the threshold percentage may be 50% or greater. In other embodiments, the threshold percentage may be 60% or higher. In still other embodiments, the threshold percentage may be 70% or higher. In a further embodiment, the threshold percentage may be 80% or higher. In other embodiments, the threshold may be a percentage range. For example, the threshold percentage may be in the range of 75% to 85%. Specific percentages have been described by example in this specification, and the threshold percentage is not limited thereto. Any threshold percentage or range may be used.

[0305] In other embodiments, a selection ratio can be used instead of selection frequency. The ratio is defined as the number of menu items selected divided by the number of other menu items selected. For example, ratios of 9:1, 7:1, 5:1, 3:1, or any other suitable ratio can be used.

[0306] In other embodiments, the number of times a menu item is selected can be used instead of the selection frequency. For example, a specific selection threshold can be used instead of a percentage. The specific selection threshold could be 5, 10, 15, etc.

[0307] Once a menu item can be restricted, the hardware processor can determine which menu items can be displayed on the MUI display 206 in subsequent time periods, and which menu items will be restricted. According to an embodiment, any menu item that is determined to have a frequency higher than a threshold percentage can be displayed (e.g., unrestricted).

[0308] In a further embodiment, the display limit may be based on menu items with a selection frequency below a certain threshold, such as below 50%, 40%, 30%, 20%, 10%, etc.

[0309] In several embodiments, restriction commands can be sent based on various criteria. For example, one or more menu items can be excluded based on menu items designated as unavailable to a particular user. This occurs, for example, if a particular user does not select one or more menu items within a specific time period. Similarly, one or more menu items can be restricted based on menu items designed to be unavailable to two or more user groups. In this example, the frequency with which two or more users select or do not select one or more menu items within a period of time affects whether a restriction command is sent for those menu items. Other embodiments consider sending restriction commands in a similar manner to the previous two examples, but for a single team and / or group of teams (i.e., based on the frequency with which users in that team select menu items). Furthermore, other embodiments can restrict menu items based on a specific machine or group of machines executing one or more computer applications that users are logged into.

[0310] In one embodiment, the menu manager 1054 may send a restriction command to the hardware processor executing the display manager 1050. According to this embodiment, the restriction command may include menu items determined to have a frequency exceeding a threshold percentage. The restriction command may be sent in conjunction with one or more display commands. Upon receiving both the display command and the restriction command, the display manager 1050 may delete or remove menu items included in the display command but not yet included in the restriction command before displaying the menu items on the MUI display (206).

[0311] In other embodiments, the restriction command may include menu items other than those determined to have a frequency higher than a threshold percentage. Upon receiving the display command and the restriction command, the display manager 1050 may delete or remove menu items contained in both the display command and the restriction command before displaying the menu items on the MUI display 206.

[0312] In other embodiments, instead of a separate restriction command, the display command may be modified by menu manager 1054 to delete menu items other than those determined to have a frequency higher than a threshold percentage.

[0313] By using the restriction command, the number of menu items (user selectables or choices) can be limited to fewer than the number of menu items on the first and second menus. For example, the first menu may contain nine menu items, but the restriction command is used to limit the total number of menu items displayed to fewer than nine. For example, the total number of menu items (user selectables) may be less than or equal to seven (or less than seven), less than or equal to five, less than or equal to three, or less than or equal to any other number. The number of menus (limited number) described in this specification is merely an example, and the number may be any selected number to provide a limited display to avoid or prevent user confusion. In an embodiment, menu items excluded from display due to the restriction command are provided in the advanced context menu (270). In an embodiment, the menu items excluded from display based on the restriction number may be selected according to the selection frequency.

[0314] In some embodiments, if, after determining the number of menu items with a selection frequency greater than a threshold percentage and the number of menu items is greater than a limit (e.g., seven), the menu manager 1054 may increase the threshold percentage to reduce the number of menu items with a selection frequency greater than the threshold percentage. Therefore, the menu manager 1054 can be configured to select and display a specific number of menu items with the highest selection frequency.

[0315] In one embodiment, the limiting function can be applied to any type of MUI module for operation as follows. The threshold percentage can be used to determine which menu items will be displayed (e.g., not limited to). For example, a threshold percentage of 90% or 80% can be used, meaning only menu items selected more than 90% or 80% of the time are displayed. In one example, selection frequency can be applied based on the user's login phase, meaning only menu items displayed during 90% or 80% of the user's login time are displayed. The limiting function can be applied to one or more menu layers, i.e., a first menu layer, a second menu layer, etc. In some embodiments, the threshold can vary based on the menu layer (e.g., lower layers may have lower frequency display requirements, as they often have more options, thus reducing selection frequency). These menu items that do not meet the threshold (e.g., using 10% or less, or using 20% ​​or less) are displayed in advanced context menus, which vary depending on the currently displayed menu. Thus, the user's choices are limited to the most frequently used options throughout the MUI, allowing the user to navigate significantly faster. In some embodiments, the excluded options as described above may be provided only through the advanced context menu. Therefore, for the 90% example, if only 90% of the available menus meet the threshold, only those menus will be displayed in the current menu, while the rest (10% in this example) will be displayed in the advanced context menu in response to the advanced context menu selector (also referred to throughout as the advanced selector or advanced context selector).

[0316] The 90% / 10% and / or 80% / 20% values ​​are merely illustrative and other values ​​may be selected depending on the MUI module to be implemented. In one example, the limiting functionality may also be based on a default protocol, rather than a user-customized protocol. For example, a vendor may sell assay kits that include a standard protocol that allows customers to make further modifications. As the user moves through the menu system, standard protocol options may be included in the available menu items displayed in the "Current" section, while available user modifications may be displayed in the "Advanced Context Menu." The division of menu items may be adjusted based on actual user operations after the user has used a particular assay kit multiple times.

[0317] Similarly, by using the restriction command, the number of menu items (user-selectable options) can be limited to fewer than the number of menu items in the first menu, the second menu, and the third menu.

[0318] In some embodiments, when the time period expires, the menu item selection table can delete the selection history of the new decision. In this example, previously excluded menu items will become available again.

[0319] In embodiments, the MUI can provide team integration via communication between multiple MUI modules. An integrated system managed by a system conforming to embodiments of this specification can be managed by multiple MUI modules configured for different operators to perform different tasks. For example, using a Laboratory Information Management System (LIMS) as an example, an administrator console module, an experiment design module, a scale control module, an experiment analysis module, and an experiment procedure module can be provided. The administrator console module provides features and functions for managing different users, operators, instruments, and teams. The experiment design module allows one or more members of a team to design experiments that other team members will conduct. The scale control module allows other team members to review scales, order additional consumables, and consider user experiment history and future planned experiments. The experiment procedure module allows team members to be responsible for running experiments and accessing and implementing designed experiments through interaction between the MUI, operators, and external systems. Finally, the experiment analysis module allows other team members to access the results of the conducted experiments. Based on user and team settings prepared via the administrator console, each user can log in to the system and have access to the modules necessary to complete their assigned tasks. In this embodiment, the necessary modules may be installed in appropriate locations on the computing device to perform the work (i.e., the experimental procedure module may be installed on a device connected to laboratory instruments, while the administrator console module may be installed on a desktop device). Therefore, the system provided in this specification allows for the integration of workflows among multiple team members using a single, consistent interface.

[0320] In an embodiment, the display manager 1050 may be configured to provide one or more icons or animations to indicate the “working” state of the systematized user interface control system 1102. The working status indication is provided to alert the user that processing is in progress and to prevent impatience while the systematized user interface control system 1102 is processing. In one embodiment, the working status indication is provided via a light fountain display presented in a currently or historically unoccupied portion of the screen. For example, the bottom of the screen, centered below the currently used portion, may be used for the light fountain display. The light fountain may provide a series of stacked columns that conform to the rest of the MUI. In one embodiment, the stacked columns may be presented in white and various shades of blue. In one embodiment, the stacked columns are presented as four rows of thin bars. Each row may include, for example, multiple stacked columns of varying lengths between two and twenty. When the system is processing, these stacked columns may flash with different shades of white and blue and different lengths, creating a waterfall or light source effect.

[0321] The embodiments described in this specification further include methods for designing user interface systems. For example, this method may include a MUI design conforming to the embodiments of this specification. The method of designing a user interface system may include generating a hierarchical menu tree as described in this specification. The hierarchical menu tree may include a series of menus, each menu including menu items leading to a subsequent series of menus. The method of designing a user interface system may further include selecting an execution menu to terminate a branch of the hierarchical menu tree, wherein the execution menu is configured to execute one or more commands within the software to provide a set of or more sets of instructions to a user, and / or output one or more commands to a connected device, system, instrument, or machine. The method of designing a user interface system may further include using one or more display modes to configure each menu in the hierarchical menu tree, said display modes including at least an active display mode for display in the current portion of the user interface and a historical display mode for display in the historical portion of the user interface. A further aspect of the user interface design method may further include design methods for any menu functionality described in this specification.

[0322] In a further embodiment, the MUI conforming to the present invention can provide integrated explanatory options during tiered menu navigation. Users can request explanations for specific menus by pressing specific key combinations and / or by accessing explanatory options displayed in an advanced context menu. The integrated explanatory options may include one or more dialog boxes to provide the user with explanations about the displayed options. As mentioned above, the MUI provides ample blank sample or background space. Therefore, explanatory options can represent pop-up windows or dialog boxes pointing to the MUI section where the user seeks help, without compromising the original MUI display. In an embodiment, enabling the explanatory function allows the dialog box to appear when the user hovers the mouse over it or points to any item in the MUI.

[0323] In a further embodiment, the MUI history section can be further adapted to display menu items after the current menu. For example, when a user navigates the current menu, the user can, for instance, scroll with a vertical scroll wheel to highlight or emphasize different menu items. Submenus for the highlighted menu items can be displayed in the history section to provide a visual representation of subsequent menus to the current menu, including future items that can be selected later.

[0324] In an embodiment, as described above, each of the first active portion and the second historical portion is adapted to display consistently within the same area of ​​the MUI. While the positioning of each of these portions is not limited to a specific location on the MUI, in some embodiments, the location is maintained once selected. Therefore, the active portion of the MUI display is adapted to display consistently within a first identical area of ​​the UI display to optimize user focus when interacting with the UI display, and the historical portion of the MUI display is adapted to display consistently within a second identical area of ​​the UI display to optimize user focus when interacting with the UI display.

[0325] The previous description provides an example menu layout for displaying multiple menus in a hierarchical menu tree. Figures 2D to 2M Other examples of menu display configurations are provided. The following menu display configurations can be used without limitation in any combination with or in relation to the previously disclosed menu configurations. For example, selecting a specific menu item anywhere in the hierarchical menu tree can cause the processor to execute a command to switch the UI display to any menu configuration described in this specification. In particular, a specific menu display configuration can be combined with a specific menu selection.

[0326] Figure 2D This shows another example of the menu display configuration in one embodiment. Figure 2D A two-scroll configuration is shown, wherein the first scroll wheel option has sub-options in the second scroll wheel. For example, selecting an option in the first scroll wheel with the option will display it in the second scroll wheel, the sub-options being combined with the selected option. In one embodiment, the first portion 214 of the display may initially display the first scroll wheel, and as an option is selected from the first scroll wheel, the first scroll wheel with the option may be repositioned to the second portion 216 adjacent to the first portion. The first portion may then, for example, be arranged in a parallel manner to display the second scroll wheel with the sub-options of the first option (in the same visual orientation, the first scroll wheel appears parallel to the second scroll wheel).

[0327] In a further embodiment of this example, both the first scroll wheel and the second scroll wheel may be displayed in a first portion 214 of the MUI display 206. The first scroll wheel may be displayed in a first sub-part of the first portion 214, and the second scroll wheel may be displayed in a second sub-part of the first sub-part 214. As used herein, a sub-part may be a larger portion of the division. Sub-parts may also be used interchangeably. In an embodiment, a menu item in the first scroll wheel is selected by clicking any menu item in the first scroll wheel or by rotating any menu item in the first scroll wheel to a prominent position. Selecting an item in the first menu on the first scroll wheel may thus modify the display of the second menu on the second scroll wheel. In yet another further embodiment of this example, the first portion 214 may be divided into two or more sub-parts, each sub-part containing a scroll wheel displaying a relative menu. Thus, three scroll wheels may display a first menu, a second menu, and a third menu, representing different levels of a hierarchical menu tree. In another example, three scroll wheels may display a second, third, and fourth menu. Other examples may include any number of scroll wheels.

[0328] In a further embodiment, multiple scroll wheels may be displayed in multiple sub-sections of the first portion 204 to allow a user to select multiple menus within the same hierarchical menu layer. For example, selecting a specific menu item in a menu layer may result in multiple sub-menus being displayed on the same layer. Therefore, selecting an item in a second menu layer may result in the display of multiple third menus, each including multiple third menu items. In embodiments, the displayed multiple sub-menus may be execution menus to allow a user to make multiple execution menu selections simultaneously. In embodiments displaying multiple sub-menus, the multiple sub-menus may be related to or associated with each other.

[0329] Figure 2E This is yet another example of a menu display configuration shown in one embodiment. In this display configuration, two scroll wheels are compressed into one scroll wheel. Scroll wheel options have sub-options represented in the scroll wheel for the active scroll wheel option. In this configuration, the first and second portions of the display overlap, but all menu items are still visible (or can be viewed by expanding the collapsed items, sliding, or rotating the item scroll wheel). For example, the second scroll wheel for an option may be displayed within the first scroll wheel. The first scroll wheel for an option can be rotated in one direction (e.g., vertically up and down), while the second scroll wheel for an option can be rotated in another direction (e.g., horizontal, left, and right). The selected path is also visible in the second portion. For example, selecting 'sub-option 2' displayed in the display moves the selected option below 'first scroll wheel option 1'.

[0330] Figures 2F to 2G This shows yet another example of a menu display configuration in one embodiment. These diagrams show the scroll wheel options switching from horizontal to vertical. Figure 2FThe display shows a selection menu, for example, in a scroll wheel, with options that rotate horizontally (left and right). The scroll wheel is displayed in the first part of the graphical user interface display. After an option (a menu item in the options list) is selected, the scroll wheel switches to a vertically rotatable wheel. For example, moving or repositioning the scroll wheel to the second part of the graphical user interface display will cause the first part of the graphical user interface display to now display a list of sub-options related to the previously selected option in the options menu.

[0331] In one embodiment, the second portion of the display may show up to a threshold number of menu layers, for example, different visual configurations may be used to display past menu layers to prevent the second portion from becoming too large.

[0332] For example, please refer to Figure 2C If there is more than one threshold number of menu layers (e.g., Figure 2C If two layers (202, 210) are displayed, a visualization mechanism that can visualize all past menu layers can be used, without having to grow the second part of the display (e.g., Figure 2C (e.g., 208). For example, consider a threshold of 3. In this example, the second section could display 3 menu layers. When another layer is selected (e.g., the 4th menu layer), the second section could display the 3 most recent selections (the bottom 3 layers), and items in the second section could be scrolled up and down. Thus, in this example, scrolling on the second section allows viewing the selections of the first menu layer. To illustrate further, the second section could always display the top two layers, namely the first two decisions and the last decision. In this way, the user sees the overall context of the workflow, for example, from top to bottom. Clicking or scrolling the second section allows the user to expand menu items, for example, like a retractable accordion.

[0333] On the other hand, a search function for the scroll wheel is available. Search keywords allow users to filter the scroll wheel options available to them. The search function is helpful for handling long or multi-option scroll wheels, which may require a long time to navigate.

[0334] Figures 2H to 2J This shows an example of a first and second portion displayed as a series of concentric circles in one embodiment. Please refer to [link / reference needed]. Figure 2H The dial 220 can be rotated clockwise or counterclockwise to view options window 218, menu items, or the item to be selected. Clicking an area of ​​the dial (e.g., a circle) 220 selects an option. Selecting an option, for example, viewed via options window 218, transforms the user interface into... Figure 2I The configuration shown. For example, in Figure 2IIn this configuration, concentric dials expand outwards to display another concentric circle, representing another layer (e.g., a sub-layer) of menu items or paths. Sub-options can be viewed via an option window 222 (also referred to as a dial) on the circle 224 by rotating dial 224 clockwise or counterclockwise. Options within the layer (displayed as sub-options 'n') 222 (i.e., non-overlapping inner circles or dials 220) can be selected by tapping an area of ​​the circle 224. In another embodiment, options are selected from the dial or circular menu user interface (e.g., such as...). Figure 2H (As shown) can change the user interface state to Figure 2J The configuration is shown. For example, the next layer of option selection expands from the selected option, expanding the dial to display another internal dial 224 with an options window 222. In one embodiment, the number of options that can be viewed on the options window (e.g., 218 and 222) is unlimited, so an unlimited number of options suitable for the application can be displayed and selected.

[0335] In one embodiment, the options window (e.g., 218) may be enlarged to display a selected option (e.g., highlighted) and one or more unselected options, such as one unselected option appearing before the selected option and another unselected option appearing after the unselected option.

[0336] In another scenario, an options window (e.g., 219) may display more than one item or option at a time, such as three menu items or options. In this example, clicking a menu item in the options window will select that option. After selection, the selected option can be displayed in a bright format or another different format, for example, to distinguish the selected option from the unselected option appearing in the options window.

[0337] In another embodiment, the relocation command may specify that the second part is concentric with the first part, and the relocated menu is displayed adjacent to (and concentric with) the first part, wherein the first and second parts are displayed on the MUI display 206 as a series of concentric circles. For example, the first part may be displayed as the central circle of a series of concentric circles, and the hierarchical relocation menu layer may be displayed outside or around the central circle.

[0338] Figure 2K This illustrates the tree type of the menu layer in one embodiment.

[0339] Figure 2KThe hierarchical menu tree shown contains a first menu item, a second menu item for sub-menu items, a third menu item for sub-sub-menu items, and four execution menus. One execution menu is associated with sub-menu item 1, and the other three execution menus are associated with sub-sub-menu items 1-3. Selecting menu item 1 from the first menu displays the second menu item for the sub-menu. Selecting sub-menu item 1 results in the execution menu item for sub-menu item 1, where processing parameters can be selected. Selecting sub-menu item 2 results in the third menu item for the sub-sub-menu item. Selecting any of sub-sub-menu items 1-3 results in the execution menu item for that sub-sub-menu item.

[0340] Figure 2L Another example of the menu display configuration in one embodiment is shown. A graphical element 242, such as a scroll wheel or slider (or another graphical element), is displayed in a portion 240 of the display screen. The graphical element 242 (e.g., the scroll wheel) is first sorted using the most recent "n" items (in reverse chronological order) 244, and has search functionality for all menu items 248, this search box or area 246, adjacent to a list (e.g., a text order list). In another embodiment, for example, when a search term is entered in the search box 246, the menu items displayed in the menu items 248 will be displayed as an index. The entire scroll wheel 242 is scrollable. For example, a user can scroll the entire scroll wheel 242 or enter a search string in the search box 246. Entering a search term in the search area 246 displays the menu items that match the search term when the search character is entered. For example, for each character entered, one or more menu items closest to matching the search character are indexed in the menu items 248. The scroll wheel 240 is divided into two independent scroll wheels: one scroll wheel displays the most recently selected menu item 244, while the other scroll wheel displays an index list or all menu items 248. The two scroll wheels 244 and 248 can be scrolled or moved independently of each other. Thus, for example, the entire wheel 242 can be moved or scrolled as a single scroll wheel. Upon receiving or detecting input of search terms or characters in the search area 246, the scroll wheel is divided into two independently scrollable separate scroll wheels 244 and 248. One of the two separate scroll wheels (e.g., 248) displays a filtered list of menu items based on the search.

[0341] Figures 2M to 2OAn example of a scrollable wheel is shown, which scrolls or slides from a first menu item to a last menu item and back from a last menu item to a first menu item. In this embodiment, the graphical element displaying the menu items (e.g., a scroll wheel or slider) does not rotate completely, but stops at either the last or first menu item (if rotating from the last menu item). Thus, for example, the beginning and end of the menu are always obvious because they are not merged or connected. This technique reduces computer processing cycle time because the scroll wheel and / or slider can convey (and the user can immediately understand) the entire menu selection and clearly indicate where or which of the selections displayed by the scroll wheel and / or slider is the first menu item and where or which is the last menu item, so that the scroll wheel or slider does not need to repeatedly scroll to try to determine which is the first menu item and which is the last menu item, or to determine whether all menu items have been visited.

[0342] In this embodiment, the scroll wheel and / or slider does not need to rotate completely; for example, the scroll wheel and / or slider does not need to rotate completely or complete a full circle. For example, the scroll wheel and / or slider rotates or slides from a start menu item to an end menu item, and rotates in the opposite direction to rotate or slide back from the end menu item to the start menu item. Thus, for example, the start and end of the menu are always obvious because they are separate and not merged or connected. This technique reduces processing time because the scroll wheel and / or slider can convey (and the user can immediately understand) the entire selection menu and clearly indicate where or which of the options displayed by the scroll wheel and / or slider is the first menu item and where or which is the last menu item. Furthermore, as the scroll wheel and / or slider rotates, the selectable options can be displayed in a more salient manner, such as using larger text, bold text, etc. As the scroll wheel and / or slider rotates / slides to different positions or as the selectable option continues to rotate / slide, previously selectable options can be displayed in a less salient manner, such as by shrinking or darkening the text. In one embodiment, the brighter display option may be presented as something that appears closer to the user's relatively muted display option.

[0343] Please refer to this. Figure 2M The first menu item 252 is displayed at the center of the scroll wheel (or sliding axis) 250. A bright display format (e.g., larger characters, different font colors, etc.) can be used to display the menu item displayed at the center. A blank sample appears before the first menu item (e.g., above the center of the scroll wheel displaying the first menu item). The next menu item (e.g., 254, 256) appears adjacent to (e.g., below) the first menu item. Scrolling the scroll wheel (e.g., in a vertical direction) displays other menu items, such as... Figure 2N As shown. For example, as Figure 2N As shown, when the scroll wheel 250 is scrolled upwards, the next menu item is displayed. Figure 2OThe last menu item is displayed at the center of the scroll wheel, with previous menu items displayed adjacent to (e.g., above) the last menu item. In this embodiment, the scroll wheel or sliding shaft 250 does not rotate to display the first menu item after the last menu item 258. Instead, the scroll wheel stops rotating at the last menu item 258. A blank sample is displayed below the last menu item 258. Similarly, backward navigation (e.g., scrolling the wheel in the opposite direction) displays previous menu items above the first menu item.

[0344] although Figures 2M to 2O The example graphic wheel shown illustrates a vertical scroll wheel, but a horizontal scroll wheel would function similarly. For example, the first menu item might appear in the center of the horizontal scroll wheel, while the next menu item appears horizontally adjacent to the first menu item (e.g., to the right of the center). In this example, scrolling the wheel to the left would display additional menu items. When scrolling to the last menu item, it appears in the center, and a blank sample follows it (e.g., to the right of the last menu item). Alternatively, the orientation of rotation could be reversed: for example, using the vertical scroll wheel, scrolling down (instead of up) navigates from the first menu item to the last; using the horizontal scroll wheel, scrolling to the right navigates from the first menu item to the last. The number of menu items (options) displayed on the scroll wheel at a time is configurable, for example, based on the screen size and / or screen area for the arrangement of the scroll wheel, etc., and is not limited to. Figure 2N The six items shown.

[0345] The primary, non-restrictive use of this user interface is selecting television (TV) channels to watch. Wider categories can be displayed in the top horizontal area, while smaller categories appear below, and paginated items can be displayed vertically, for example, on a vertical scroll wheel. For example, please refer to... Figure 2E 'Scroll wheel option 1' can represent a style, while 'sub-option 1' can represent a program and / or movie composed of a grid.

[0346] In one embodiment, the systematized user interface control system 1102 provides a user interface for running processes. These processes may include conducting experiments, performing one or more manufacturing operations, or any other procedures.

[0347] The following describes in detail various instructions for conducting experiments conforming to embodiments of this specification. These instructions can be used to manipulate, design, execute, review, measure, analyze, store, and perform any other work related to the experiments. An experiment may be, but is not limited to, one or more assays. A systematic user interface control system 1102 can incorporate and / or combine the assay system and provide commands to generate a MUI display 206 for the system. Along with the commands, the MUI display 206 is capable of displaying or providing a visual representation of the workflow and / or menu item paths for the assays. The assays may include one or more electrochemiluminescence (ECL) assays.

[0348] The method of this embodiment can be used in combination with various assay devices and / or forms. The assay device may include, for example, assay modules such as assay plates, cartridges, multiwell assay plates, reaction vessels, test tubes, cuvettes, flow cells, assay chips, lateral flow devices, etc., having assay reagents (which may contain targeted agents or other binding reagents) added to or pre-loaded in the assay module as the assay proceeds, in wells, chambers, or assay areas. These devices can employ various assay formats for specific binding assays, such as immunoassays or immunochromatographic assays. Illustrative assay devices and forms are described below in this specification. In some embodiments, the method of this embodiment may employ assay reagents stored in a dry state, and the assay device / kit may further include or have a desiccant material for keeping the assay reagents dry. Assay devices pre-loaded with assay reagents can significantly improve speed, reduce the complexity of assay measurements, and maintain superior stability during storage. The dried assay reagents can be any assay reagent that can be dried and then reconstructed before use in an assay. These include, but are not limited to, binding reagents, enzymes, enzyme substrates, indicator dyes, and other reactive compounds that can be used for binding assays to detect target analytes. Assay reagents may also contain substances that do not directly participate in the assay but play a supporting role, including, but not limited to, blocking agents, stabilizers, detergents, salts, pH buffers, preservatives, etc. Reagents may exist in free form or be supported on a solid phase, which may include the surface of compartments (e.g., chambers, channels, flow cells, orifices, etc.) in the assay module, or the surface of colloids, beads, or other particle carriers.

[0349] Various solid phases are suitable for the methods of this embodiment, including conventional solid phases from the field of binding assays. Solid phases can be made from a variety of different materials, including polymers (e.g., polystyrene and polypropylene), ceramics, glass, and composite materials (e.g., carbon-polymer composites, such as carbon-based inks). Suitable solid phases include the surface of macroscopic objects, such as the inner surface of a assay container (e.g., test tubes, optical discs, flow chambers, cassettes, holes in multi-well plates, etc.), glass slides, assay chips (such as those used for gene or protein chip measurements), needles or probes, beads, filter media, side-flow media (e.g., filter membranes for side-flow test strips), etc.

[0350] Suitable solid phases may also include particles (including but not limited to colloids or beads) commonly used in other types of particle-based assays, such as magnetic, polypropylene, and latex particles; materials commonly used in solid-phase synthesis, such as polystyrene and polyacrylamide particles; and materials commonly used in chromatography applications, such as silica, alumina, polyacrylamide, and polystyrene. The materials may also be fibers, such as carbon fibers. The particles may be inanimate biological entities; or they may contain living biological entities, such as cells, viruses, bacteria, etc.

[0351] The particles used in the method of this invention may comprise any material suitable for attachment to one or more binding partners and / or markers, and may be collected via, for example, centrifugation, gravity, filtration, or magnetic collection. A variety of different types of particles that can attach to binding reagents are commercially available for binding assays. These include non-magnetic particles as well as particles comprising magnetizable materials, which allow for collection via a magnetic field. In one embodiment, the particles are composed of conductive and / or semi-conductive materials, such as colloidal gold particles.

[0352] The particles can have a variety of sizes and shapes. For example, and without limitation, particles can range from 5 nanometers to 100 micrometers. Preferably, the particles have a size between 20 nm and 10 micrometers. The particles can be spherical, rectangular, rod-shaped, etc.; or the particles can be irregularly shaped.

[0353] The particles used in this method can be encoded to allow the identification of a specific particle or a subgroup of particles in a mixture of particles. The use of such encoded particles has been used to enable the polynomial of determinations that utilize particles as solid supports for binding assays. In one method, the particles are fabricated to contain one or more fluorescent dyes and to identify a specific particle group based on the intensity and / or relative intensity of fluorescence emission at one or more wavelengths. This method has been used in the Luminex xMAP system (see, for example, U.S. Patent No. 6,939,720) and the Becton Dickinson Cytometric Bead Array system. Alternatively, the particles can be encoded by differences in other physical properties, such as size, shape, embedded optical patterns, etc.

[0354] The methods of the embodiments can be used in conjunction with various methods for measuring the amount of analyte, particularly for measuring the amount of analyte bound to a solid phase. Applicable techniques include, but are not limited to, those known in the art, such as cell culture-based assays, binding assays (including agglutination assays, immunoassays, serological assays, nucleic acid assays such as hybridization assays, etc.), enzyme activity assays, colorimetric assays, etc. Other suitable techniques will be apparent to those skilled in the art. Some measurement techniques allow for measurement by visual inspection, while others may require or benefit from the use of instruments for measurement.

[0355] Methods for measuring analyte content include unlabeled techniques, including but not limited to i) techniques for measuring surface mass or refractive index changes after the analyte has bound to the surface (e.g., surface acoustic wave technology, surface plasmon resonance sensor, elliptic polarization technology, etc.), ii) mass spectrometry techniques (including techniques such as MALDI, SELDI, etc. that can measure analytes on the surface), iii) chromatography or electrophoresis techniques, iv) fluorescence techniques (which may be based on the intrinsic fluorescence of the analyte), etc.

[0356] Methods for measuring analyte amounts also include techniques for measuring analytes by detecting markers that are directly or indirectly attached to the analyte (e.g., by using a marker-binding pair of the analyte). Suitable markers include those that are directly visual (e.g., visually visible particles and those that generate measurable signals, such as light scattering, light absorption, fluorescence, chemiluminescence, electrochemiluminescence, radioactivity, magnetic fields, etc.). Usable markers also include enzymes or other chemically reactive species that have chemical activity that results in measurable signals, such as light scattering, absorbance, fluorescence, etc. Enzyme-linked immunosorbent assays (ELISA) or enzyme immunoassays (EIA) have been well-established for using enzymes as markers. In the ELISA format, an unknown amount of antigen is immobilized on a surface, and then a specific antibody is washed onto the surface to allow it to bind to the antigen. This antibody is linked to the enzyme, and in a final step, a substance is added that converts the enzyme into a preparation that provides a detectable signal change. The formation of the article can be detectable, for example, due to differences in measurable properties caused by variations between substrates, such as absorbance, fluorescence, chemiluminescence, light scattering, etc. Some (but not all) measurement methods applicable to the solid-bonding method according to the embodiments may benefit from or require a cleaning step to remove unbonded components (e.g., markers) from the solid phase. Therefore, the method of the embodiments may include this cleaning step.

[0357] The methods disclosed in this specification can be performed manually, using automated techniques, or both. Automated techniques can be partial automation, such as one or more modular instruments or fully integrated automated instruments.

[0358] The example automated system is discussed and described in International Patent Applications No. WO 2018 / 017156 and No. WO 2017 / 015636 and International Patent Application No. WO 2016 / 164477, the entire contents of which are incorporated herein by reference.

[0359] The automated systems (modular and fully integrated) achievable by the methods described in this specification may include the following automated subsystems: a computer subsystem, which may include hardware (e.g., personal computer, laptop computer, hardware processor, disk, keyboard, monitor, printer), software (e.g., processing such as drivers, driver controllers, and data analyzers), and a database; a liquid handling subsystem, such as sample and reagent handling, such as mechanical dispensing heads, syringes, stirring devices, ultrasonic mixing devices, and magnetic mixing devices; and a sample, reagent, and consumable storage and handling subsystem. Examples include mechanical manipulators, tube or cap or film puncture and removal devices, conveying devices such as linear and circular conveyors and mechanical manipulators, tube racks, plate carriers, tank carriers, dispenser tip carriers, plate shakers; centrifuges, assay reaction subsystems, such as fluid-based and consumable-based (such as test tubes and well plates); container and consumable cleaning subsystems, such as plate cleaning devices; magnetic separator or magnetic particle concentration meter subsystems, such as flow chambers, tubes, and plate types; cell and particle detection, classification, and separation subsystems, such as flow cytometers and Coulter counters. The system includes: a counter; detection subsystems such as colorimetric, turbidity, fluorescence, and ECL detectors; temperature control subsystems such as air handling, air cooling, air heating, fans, blowers, and water baths; waste subsystems such as liquid and solid waste containers; globally unique identifier (GUI) detection subsystems such as 1D and 2D barcode scanners, including flatbed and rod-type scanners; and sample identifier detection subsystems such as 1D and 2D barcode scanners, including flatbed and rod-type scanners. Analytical subsystems, such as chromatography systems, including high-performance liquid chromatography (HPLC), fast-protein liquid chromatography (FPLC), and mass spectrometry, may also be modular or fully integrated. Automated systems conforming to embodiments of this specification can be controlled and / or managed by a systematized user interface control system 1102.

[0360] Systems or modules for sample identification and preparation can be combined (or adjacent, adjacent, mechanically linked, or combined) with systems or modules for assays and detections, or both. Multiple modular systems of the same type can be combined to increase throughput. Modular systems can be combined with modules for performing other types of analyses (such as chemical, biochemical, and nucleic acid analyses).

[0361] Automated systems allow for batch, continuous, random access, and point-of-care workflows, as well as single, medium, and high sample throughput.

[0362] The system may include one or more of the following devices: a plate sealer (e.g., Zymark), a plate washer (e.g., BioTek, TECAN), a reagent dispenser and / or an automated dispensing station and / or a liquid handling station (e.g., TECAN, Zymark, Labsystems, Beckman, Hamilton), an incubator (e.g., Zymark), a plate shaker (e.g., Q. Instruments, Inheco, Thermo Fisher Scientific), a compound library, or a sample storage and / or compound and / or sample retrieval module. One or more of these devices are mechanically coupled to the device, enabling automation of the entire assay process. According to an alternative embodiment, containers (e.g., plates) are manually moved between the device and various devices (e.g., plate stacks).

[0363] Automated systems can be configured to perform one or more of the following functions: (a) moving consumables (such as plates) into, out of, and within a detection subsystem; (b) moving consumables between other subsystems; (c) storing consumables; (d) sample and reagent handling (e.g., adapting reagents for mixing and / or introducing reagents into consumables); (e) consumable shaking (e.g., for mixing reagents and / or for increasing reaction rates); (f) consumable cleaning (e.g., cleaning plates and / or performing assay cleaning steps (e.g., well aspiration); and (g) measuring the ECL in a flow chamber or consumable (such as tubes or plates). Automated systems can be configured to process individual tubes or multi-well plates (such as 96- or 384-well plates) placed in a rack.

[0364] As described in this specification, methods for integrating components and modules in automated systems are well known in the art, see, for example, Sargeant et al., application dated May 17, 2010, entitled “Platform Perfection, Medical Product Outsourcing”.

[0365] In this embodiment, the automated system is fully automated, modular, and computerized, performing in vitro quantitative and qualitative testing of multiple analytes, including photometric measurements, ion-selective electrode measurements, and / or electrochemiluminescence (ECL) measurements. In this embodiment, the system includes the following hardware units: a control unit, a core unit, and at least one analytical module.

[0366] In this embodiment, the control unit uses a graphical user interface to control all instrument functions and includes a readout device such as a display, input devices such as a keyboard and mouse, and a personal computer using, for example, a Windows operating system. In this embodiment, the core unit consists of several components to manage sample delivery to each designated analytical module. The actual composition of the core unit depends on the configuration of the analytical modules, which can be configured by a person skilled in the art using methods known in the art. In this embodiment, the core unit includes at least a sampling unit and a rack rotor as primary components. A transmission line and a second rack rotor are possible extensions. Several other core unit components may include a sample rack loader / unloader, connection ports, a barcode reader (for the rack and sample), a water supply system, and a system interface port. In this embodiment, the analytical module performs ECL determinations and includes a reagent area, a measurement area, a consumables area, and a pre-cleaning area.

[0367] The method of the present invention can be applied in single or multiple forms, wherein multiple measurements are performed on a single sample. Multiple measurements that may be used with the present invention include, but are not limited to, the following uses of multiple measurements: i) requiring the use of multiple sensors; ii) using discontinuous measurement domains on a surface (e.g., an array) that are distinguishable based on position on the surface; iii) requiring the use of reagents coated on particles that are distinguishable based on particle properties (such as size, shape, color, etc.); iv) generating measurement signals that are distinguishable based on optical properties (e.g., absorbance or emission spectrum); and / or v) based on the temporal properties of the measurement signals (e.g., the time, frequency, or phase of the signal).

[0368] This invention includes a method for detecting and counting individual detection complexes. In embodiments, a surface comprises a plurality of binding domains, and each analyte forms a complex in a different binding domain of the plurality of binding domains. In embodiments, the surface is a particle. In embodiments, the surface is a bead. In embodiments, the surface is a plate. In embodiments, the surface is a pore in a porous array. In embodiments, the surface comprises an electrode. In embodiments, the electrode is a carbon ink electrode. In embodiments, each binding domain of each analyte of one or more added analytes is on a separate surface, and the surface is a bead in a bead array. In embodiments, each binding domain of each analyte of one or more added analytes is on a single surface, and the binding domains form elements of a trapping reagent array on the surface. In embodiments, the surface comprises an electrode, and the detection step of the method comprises applying a potential to the electrode and measuring electrochemiluminescence. In embodiments, applying a potential to the electrode generates an electrochemiluminescence signal.

[0369] In a specific embodiment, the surface includes a plurality of capture reagents for one or more analytes present in the sample, and the plurality of capture reagents are distributed on a plurality of resolvable binding regions located on the surface. Under conditions for performing and analyzing measurements, a “resolvable binding region” is the smallest surface area associated with a single binding event, which is resolvable and distinguishable from another region where a further single binding event occurs. Therefore, the method includes binding one or more analytes to one or more capture reagents on the surface, determining the presence of the analyte in the plurality of resolvable binding regions on the surface, and identifying the number of resolvable binding regions, which includes the number of regions containing the target analyte and / or regions not containing the analyte.

[0370] Resolvable binding regions can be optically interrogated in whole or in part; that is, each individual resolvable binding region can be optically interrogated individually and / or the entire surface containing multiple resolvable binding regions can be imaged, and one or more pixels or groups of pixels in the image can be mapped to a single resolvable binding region. Resolvable binding regions can also be particles among multiple particles. Resolvable binding regions exhibiting variations in their optical signature can be identified using conventional optical inspection systems. Depending on the type detected (e.g., type of fluorescent entity, etc.) and the operating wavelength, filters designed for specific wavelengths can be used for optical interrogation of resolvable binding regions. In embodiments using optical interrogation, the system may include more than one light source and / or multiple filters to adjust the wavelength and / or intensity of the light source. In some embodiments, a CCD camera is used to capture light signals from multiple resolvable binding regions. Other non-limiting examples of camera imaging systems that can be used to capture images include charge injection devices (CID), complementary metal-oxide-semiconductor (CMOS) devices, scientific CMOS (sCMOS) devices, and time-delay integration (TDI) devices, as well as those well known in the art. In some embodiments, a scanning mirror system coupled with a photodiode or photomultiplier tube (PMT) can be used for imaging.

[0371] In embodiments, the binding of each analyte to its corresponding capture reagent is performed in parallel by contacting one or more surfaces with a single liquid volume comprising multiple analytes. In embodiments, the multiple analytes comprise an analyte and one or more additive analytes. In embodiments, each step of the method is performed in parallel for each analyte. In embodiments, the method is a simultaneous multiple determination. This specification describes multiple measurements of analytes on a surface. See also, for example, U.S. Patents 10,201,812, 7,842,246, and 6,977,722, the entire contents of which are incorporated herein by reference.

[0372] In certain embodiments, the method of the present invention can be used in multiple forms by binding multiple different analytes to multiple capture reagents for these analytes, immobilizing the capture analytes on coded beads such that the coding identifies the capture reagent (and analyte target) of a particular bead. The method may further include counting the number of beads with bound analytes (using the detection method described herein).

[0373] Alternatively or additionally, the capture reagent can be directly or indirectly bound to one or more discontinuous binding regions on a solid phase, for example, in a binding array where the binding regions are individual array elements, or in a set of beads where the binding regions are individual beads, such that a discontinuous measurement signal is generated and measured at each binding region. If the capture reagent for different analytes is fixed in different binding regions, the different analytes bound to these regions can be measured independently. In one example of this embodiment, the binding regions are prepared by fixing discontinuous regions of the capture reagent bound to the target analyte on one or more surfaces. Alternatively, the surface may partially define one or more boundaries of a container holding the sample (e.g., a flow chamber, a hole, a photodiode, etc.), or through which the sample is transferred. In a preferred embodiment, individual binding regions are formed on electrodes used for electrochemical or electrochemiluminescence determination. Multiple measurements of analytes using electrochemiluminescence on surfaces comprising multiple binding regions have been used in Meso Scale Diagnostics, LLC, MULTI- and Imager product family (see, for example, U.S. Patent Nos. 10,201,812, 7,842,246 and 6,977,722, the entire contents of which are incorporated herein by reference).

[0374] Furthermore, the capturing reagent can be directly or indirectly bound to the electrode surface, as described above, with selectivity including different discontinuous binding regions. The electrode surface can be an assembly of a porous plate and / or a flow chamber. The electrode can include conductive materials, such as metals like gold, silver, platinum, nickel, steel, iridium, copper, aluminum, conductive-allowing materials, etc. The electrode can also include an oxide-coated metal, such as aluminum oxide coated with aluminum. The electrode can include a working electrode and an auxiliary electrode made of the same or different materials, such as a metal auxiliary electrode and a carbon working electrode. In a particular embodiment, the electrode includes carbon-based materials, such as carbon, carbon black, graphitic carbon, carbon nanotubes, carbon filaments, graphite, graphene, carbon fibers, and mixtures thereof. In one embodiment, the electrode includes elemental carbon, such as graphite, carbon black, carbon nanotubes, etc. Preferably, the electrode can include a conductive carbon polymer composite, conductive particles distributed in a matrix (e.g., carbon ink, carbon paste, metallic ink, graphene varnish), and / or a conductive polymer. A specific embodiment of the present invention is a measuring module, preferably a porous plate, having electrodes (e.g., working and / or auxiliary electrodes) comprising carbon (e.g., carbon layers and / or screen-printed layers of carbon ink).

[0375] In an embodiment, each binding region includes a target reagent complement capable of binding a target reagent complement, and each anchoring reagent and capturing reagent includes a supplementary crosslinking reagent capable of binding a crosslinking reagent, and the method further includes curing the capturing reagent and anchoring reagent in each binding region by: (1) binding the capturing and anchoring reagents to the target reagent complement connecting the crosslinking reagent by supplementary crosslinking reagent; and (2) binding the product of step (1) to the binding region including the target reagent complement, wherein (i) each binding region includes a different target reagent complement, and (ii) each target reagent complement selectively binds to one of the target reagents.

[0376] Therefore, in an embodiment, the surface includes a target reagent complement; the target reagent is linked to a crosslinking reagent; each of the capturing reagent and the anchoring reagent includes a supplementary crosslinking reagent. Thus, in an embodiment, the target reagent complement on the surface binds to the target reagent, which is linked to the crosslinking reagent, and binds to the supplementary crosslinking reagent on the capturing reagent and the anchoring reagent.

[0377] In embodiments, the crosslinking agent has more than one binding site for supplementing the crosslinking agent, and the immobilization of the capturing and anchoring agents further comprises: connecting the capturing and anchoring agents to the target reagents connected to the crosslinking agent by supplementing the crosslinking agent; and binding the product to a binding region comprising a target reagent complement, wherein (i) each binding region comprises a different target reagent complement; and (ii) each target reagent complement selectively binds to one of the target reagents. For example, in the case where the target reagent is an oligonucleotide, the crosslinking agent is streptavidin, and the supplementary crosslinking agent is biotin, the biotin-labeled oligonucleotide may bind to a first of the four biotin-binding sites of streptavidin to form a target reagent connected to the crosslinking agent. The biotin-labeled capturing agent (i.e., the capturing agent connected to the supplementary crosslinking agent) may then bind to the remaining biotin-binding sites on streptavidin to connect the target reagent to the capturing agent.

[0378] Exemplary target reagents and target reagent complements are described in this specification. In embodiments, the target reagent and target reagent complement are two members selected from avidin-Biotin, streptavidin-Biotin, antibody-hapten, antibody-antigen, antibody-antigen labeling, complementary nucleic acid, aptamer targeting, and receptor ligand. In embodiments, the target reagent is biotin, and the target reagent complement is streptavidin. In embodiments, the cross-linking reagent and supplementary cross-linking reagent pair is a binding pairing different from the target reagent and target reagent complement pair. In embodiments, the cross-linking reagent is avidin or streptavidin, and the supplementary cross-linking reagent is biotin. In embodiments, the target reagent and target reagent complement are complementary oligonucleotides.

[0379] In embodiments, the method of the present invention is applied to single or multiple forms, wherein multiple measurements are performed on a single sample. Multiple measurements that can be used in conjunction with the present invention include, but are not limited to, the use of: i) with the use of multiple sensors; ii) with the use of discontinuous measurement regions on a surface (e.g., an array) that are distinguishable based on surface location; iii) with the use of reagents coated on particles that are distinguishable according to particle properties (such as size, shape, color, etc.); iv) with distinguishable measurement signals based on optical properties (e.g., absorbance or emission spectrum); or v) with time properties based on the measurement signal (e.g., the time, frequency, or phase of the signal). Exemplary measurement forms include V-PLEX (www.mesoscale.com / en / products_and_services / assay_kits / v-plex) and U-PLEX (www.mesoscale.com / en / products_and_services / assay_kits / u-plex_gateway, and U.S. Patent Nos. 10,201,812 and 10,189,023, the entire contents of which are incorporated herein by reference). Other forms of ultrasensitive assays include U.S. Application No. 17 / 434,938, filed August 30, 2021, and U.S. Application No. 62 / 866,512, filed June 25, 2019, the entire contents of which are incorporated herein by reference.

[0380] Exemplary plate readers include the MESO SECTOR S 600 (www.mesoscale.com / en / products_and_services / instrumentation / sector_s_600) and the MESO QUICKPLEX SQ 120 (www.mesoscale.com / en / products_and_services / instrumentation / quickplex_sq_120), both available from Scale Diagnostics, LLC. The plate readers are described in U.S. Patent No. 6,977,722 and U.S. Patent Application No. 16 / 929,757, entitled "Assay Apparatuses, Methods and Reagents" filed July 15, 2020, the entire contents of which are incorporated herein by reference.

[0381] The aforementioned user interface methods can also be incorporated into the user interface of the measurement system. The measurement system described below allows users to perform measurements via a user interface. An example of a user interface incorporated into a measurement system used for a measurement method is described below. The term "system software" or "system" and its user interface, as used in describing the functions of the measurement system below, refer to the software that implements the measurement system. The user interface can display or visualize the path of workflows and / or menu items.

[0382] The following terms are used to describe the measurement system and its user interface workflow.

[0383] Advanced Context Menu – An options menu that depends on specific content, such as the current screen, substeps, and screen state.

[0384] Assay Method – The method of performing the assay, including but not limited to: 1. Instrument specifications to be followed and parameters used to perform the protocol; 2. Test plate design; 3. Calibration titration criteria, such as dilution factor; 4. Control design; 5. Sample replication protocol.

[0385] An audit log is a continuous record of automated and user-initiated events that occur in the system and may affect the results produced. This record is used to track problems and ensure proper operation in a controlled environment. The audit log is permanent and immutable. It contains a subset of information from the instrument logs.

[0386] Compatible Protocols – Protocols are compatible if they share the same basic outline and steps, although dilution ratios, incubation times, washing times, etc., may differ. Protocols are also considered compatible if they can be run together on an automated platform during the same run.

[0387] Completed Run – A run that has been aborted, marked as completed, or completed successfully.

[0388] CV – Coefficient of variation.

[0389] Database cleanup – Resets the entire database, restoring it to its state at the time of system installation.

[0390] ECL—Electrochemiluminescence. A proprietary format for detecting molecules of biological significance.

[0391] Existing Run – A run that has been planned, aborted, completed, or successfully completed with a flag indicating completion.

[0392] Global Product Data (GPD) – Data used for specific items identified through GPI. While the same data can be used for multiple items, GPI allows data to be matched to a specific item. GPD may include information for identifying at least one element, including (i) assay consumables; (ii) one or more test sites of the consumables; (iii) reagents and / or samples that have been or will be used in the consumables; or (iv) combinations thereof. Furthermore, GPD can be used to distinguish a first test site within a consumable from different test sites within the consumable. GPD may include batch identification information, specific batch analysis parameters, process information, raw material information, expiry date, calibration data, threshold information, the location of individual assay reagents and / or samples within one or more test sites of the assay consumables, Material Safety Data Sheet (MSDS) information, or a combination thereof. GPD may also include one or more analytical tools that the system can use to analyze data generated during and / or after the assay process, assay system maintenance information, system consumable promotional information, system and / or consumable technical support information, or a combination thereof. In addition, GPD includes consumable identification and / or configuration information, as well as one or more steps in the process of measuring using consumables by which the system applies the measurement protocol.

[0393] A test site is also called a test point. Test site planning can refer to, for example, an array of test sites within a single well of a test plate or measurement plate.

[0394] A Global Product Identifier (GPI) is a unique identifier assigned by the system / instrument / consumable supplier to a specific product (such as a measurement consumable). The identifier can be configured in any number of ways. In the case of consumables such as measurement plates, the identifier can be the associated manufacturing barcode.

[0395] The types of GPI and GPD are known to us, for example, see U.S. Patent No. 8,770,471, International Patent Application Publication No. WO 2011 / 017082 and U.S. Patent Application Publication No. 2006 / 199196.

[0396] Instrument Log – A detailed log file that records all system operations and any faults or errors that occur during operation. The instrument log is a scrolling, cyclical log containing stored information, limited by the amount of storage space allocated to this log file; for example, older items may be rolled back over time.

[0397] Instrument software – the software that controls the hardware of an instrument.

[0398] LED—Light-emitting Diode. A light source.

[0399] Normal State – If the software executes normally without any errors or warnings, the instrument is considered to be in a normal state. Once the error state is resolved and / or the warning message is acknowledged, the instrument will return to the normal state.

[0400] Run – A run consists of 0 or more named samples and 1 or more assay methods, and tests the samples according to the information described in the assay method.

[0401] Run Owner – The user who creates the run.

[0402] Sample – a general term encompassing the material to be analyzed, including calibrators, reference standards, blank samples, and unknowns.

[0403] Sample ID – A unique identifier for each sample.

[0404] Sample Layout – The location and ID of the samples on the board.

[0405] Sample Type – The functional type of the sample, such as calibrator, control, blank sample, or unknown.

[0406] Spot layout – the location and name of the analyzer in the holes on the board.

[0407] A step is one of a series of individual, sequential stages in the process of moving toward a goal. A step can be a broad stage consisting of multiple sub-steps.

[0408] A sub-step is one of a series of independent, consecutive stages leading to the completion of a step. Sub-steps constitute the key activities within a step.

[0409] Unexpected Barcode – This barcode differs from the expected barcode. Consumables may also be considered to have an “unexpected barcode” if the barcode is not read.

[0410] User Interface (UI) – The software interface through which instrument users interact to control and monitor the system.

[0411] UI Warning Events – These are any noticeable messages that require a user response. Users should correct errors and / or acknowledge messages before continuing. For example, a UI warning event could be that the instrument is in a “not ready” state.

[0412] System Events Log – A permanent record of events that occur in the software and are independent of the instrument.

[0413] Figure 4 A flowchart illustrating the first user login user interface for a measurement system in one embodiment is provided. At 402, upon each startup, the system software for the measurement method checks whether an End User License Agreement (EULA) for the measurement system has been accepted. The EULA is displayed when the user first starts the system software. Upon acceptance of the agreement, a record of the username, date, and time is created. If the user has not previously accepted the agreement, the EULA is displayed in step 404, allowing the user to accept it. In step 406, if the user does not accept the agreement, the software closes. In step 408, an initial screen is displayed, including: system software brand, copyright, legal notice, and software version. The initial login screen requests a username in step 410. In one embodiment, the system software may display usernames previously used to log in to the system to reduce errors caused by typing usernames. Users are also allowed to enter new usernames not previously used for login. After selecting (or receiving) a username in step 412, the software prompts the user for a password for the username in step 414. In one embodiment, the system software may also use biometric methods such as facial recognition, voice, and / or fingerprints for login or authentication. In another embodiment, the system software may use a badge key card that includes information that can be scanned or read via near-field communication. In step 416, the system software receives an entered password. Once a username and password are entered, the system software authenticates the user in step 418. If the user is successfully authenticated, the user interface displays a startup screen at 420. Otherwise, the system software prompts the user to try again via the user interface. In one embodiment, the system software then requires all users to log in to access the software. In one embodiment, authentication may be via Microsoft. The authentication tool is executed and can be configured to authenticate via Active Directory. In this first user interface display, the username and password prompts can be displayed in one position, for example, horizontally above the horizontal scroll wheel graphic element 422.

[0414] Figure 5This is a flowchart illustrating a method for displaying a startup user interface screen in one embodiment. This screen contains a list of menu items in two different visual orientations (e.g., horizontal and vertical). Thus, for example, more general categories of menu items are displayed on the horizontal scroll wheel 502, while sub-menu items are displayed on the vertical scroll wheel 504. For example, the "Startup" option 506 selected by the logged-in user (…) Figure 4 The startup screen is displayed on the horizontal scroll wheel 502. A second layer of options derived from the "Start" option (406) is displayed on the vertical scroll wheel 504. In this example testing method, the startup screen displays the initial software screen to the user. User-executable workflows are listed as options (sub-options) on the user-selectable vertical scroll wheel. In this example testing method, less common and advanced workflows can be grouped under the Advanced menu. In this example testing method, the options for the system's workflows include: Create a new run 508, where the user can create a run from scratch or based on a previously defined run 512 when the user selects to create a new run workflow 510; Continue a previously planned or started run 514, where the software automatically resumes from the last step completed by the user in the run 516 when the user selects to continue a previously planned or started run 516; View the results of a completed run 520, where the software leads the user to a review screen 524 when the user selects to view the completed run 522. After the user selects any option 504 from the vertical scroll wheel, the options on the vertical scroll wheel are added to a new horizontal scroll wheel above the screen. The horizontal scroll wheel allows the user to change their selection. For example, after selecting "Create New File", the options for "Plan" and "Finish" will move to the horizontal scroll wheel, allowing the user to change their mind.

[0415] Figure 6 This diagram illustrates the workflow of a screen for defining a measurement method in one embodiment. In this example, the software requires a measurement method to process the sample under consideration. This is done in conjunction with executing the "Define" option (...). Figure 5 (512) Perform the processing shown in this screen. Assay definition: assay on the plate; plate planning; number of calibrators, number of controls, and maximum number of samples; diluents for controls, calibrators, and samples; number of repetitions for controls, calibrators, and samples; instrument specifications (incubation time, administration of blocking agents, and / or others). Each kit provides a default assay, and the system software allows users to create custom assays based on the defaults. In one embodiment, the assay is distributed in a Global Product Data (GPD) file. The GPD includes, for example: product barcode; assay; placement of analytes in wells; kit batch identification, plate, antibody, calibrator, control; concentration measurements of the following: calibrator, control; instrument instructions on how to handle the product; and recommended plate planning.

[0416] Figure 7 This is a diagram illustrating a user interface workflow for selecting a measurement method in one embodiment. This user interface workflow can be configured to select or execute a defined measurement method, for example, in... Figure 6 The workflow shown illustrates the selection or execution of options. Options under "Define Measurement Method" may include a "Measurement Method" selection option, a "Sample" option, and a "Confirmation" option, displayed horizontally on a horizontal scroll wheel graphic element 702. When other unselected options are present, selecting the "Measurement Method" option will highlight and / or center it on the horizontal scroll wheel. Sub-layer options below the "Measurement Method" option may be displayed vertically, for example, on a vertical scroll wheel graphic element 704. In this example, the user can select the "Measurement Method" in three ways: a) selecting the most recently used measurement methods on the system, sorted in reverse chronological order; b) selecting all available measurement methods installed on the system. In this screen, the UI uses multiple scroll wheels, with each scroll filtering the results of the next scroll before the last scroll includes the desired result; c) searching for measurement methods installed on the system, which can be done using free text search.

[0417] When a user selects a sub-layer option, the sub-layer option moves to the horizontal scroll wheel, allowing the user to change their "Measurement Method" selection model. After the user initially selects a measurement method, they can choose to run either a single measurement method or multiple measurement methods: a single measurement method, where all Mesoscale Diagnostics test panels used in the run use the same measurement method; or multiple measurement methods, where each measurement method used in the run has at least one Mesoscale Diagnostics test panel.

[0418] Figure 8 A flowchart illustrating the workflow of the user interface displayed for defining a sample in one embodiment is provided. Based on the selection of the "Define Sample" option, the option is displayed horizontally, for example on a horizontal scroll wheel graphic element 802, which can overlay its parent menu item below the "Define" option. The sub-layer of options related to the "Define Sample" option is displayed vertically, for example on a vertical scroll wheel graphic element 804.

[0419] In the "Define Sample" screen, the user interface allows the user to choose to import a sample or manually define one. After the user selects an option, these options move to the horizontal scroll wheel. When the user selects to import a sample from a file, the software displays the sample file available to the user via the vertical scroll wheel. The system can alternatively import samples from a "Laboratory Information System" or "Laboratory Information Management System".

[0420] The system can also import samples from a sample management system. When a user chooses to manually define samples, they can define the number of samples to run. The software will automatically assign sample IDs.

[0421] Figure 9 This is a flowchart illustrating a workflow for displaying a user interface for confirming a run definition in one embodiment. Based on the selection of the "Confirm Run Definition" option, a sub-menu item of the "Define" option, the "Confirm Run Definition" option is displayed on a horizontal scroll wheel graphic element, for example, overlaid below its parent menu item "Define". After the user defines the run in the previous steps, the system provides a run summary for the user to review and confirm. The following information is displayed to the user: the number of samples in the run. The user can also select the number of samples to view the sample identifier (ID), the number of MesoscaleDiagnostics boards in the run, the board plan, and the run name. The system provides a default name for the run and allows the user to change this name. Once the user confirms the run, the system prompts the user to either continue the run or return to the "Startup Target".

[0422] Figure 10 This is a flowchart illustrating a workflow for displaying a user interface to notify a user that a task has been completed, as shown in one embodiment. The system can use a wizard (automatic help function) to guide the user through the task via the user interface. The main logical steps can be broken down into several objectives. In this example, the system has three main objectives in the wizard: initiation, where the user begins and selects the operation they want to perform in the system; definition, where, after the user selects what they want to do, the wizard guides the user via a user interface that defines any necessary information; and execution, where the system guides the user by performing the task selected by the user.

[0423] Figure 11 This is a flowchart illustrating the workflow of a user interface for executing / collecting options as shown in one embodiment. In this collection screen, the system creates a list of items that the user needs to collect to execute a run. Each item must be marked as collected before proceeding. The system also allows the user to print this list or collect it using a tablet computer. For each item to be collected, items can be selectively scanned, allowing the system to check if it is the correct item, expired, or has batch information. For example, the system can request a barcode scan for the item. This is done using a retrieved GPD barcode (GPI).

[0424] Figure 12This is a flowchart illustrating the workflow of a user interface for performing / preparing options as shown in one embodiment. In this preparation screen, the system displays a list of steps required to prepare for collecting items in a scroll wheel. For each step in the scroll wheel, the system displays a detailed description of the selected preparation step. The detailed preparation steps may include: text describing the actions to be taken; images visually indicating the actions; videos demonstrating the actions; and web content, such as web pages, providing more detailed information or content about the operation. The user is prompted to indicate that all preparation steps have been completed before proceeding to the next step. The user can also use a tablet computer to print out or complete the preparation steps.

[0425] Figure 13 This is a flowchart illustrating the workflow of a user interface for executing / loading options as shown in one embodiment. In this loading screen, the system displays a list of items to be loaded into the instrument in the form of a scroll wheel. For each item, the system graphically displays where the item should be loaded. The system provides a graphical indication of whether the item is loaded or empty. Before proceeding to the next screen, the system checks whether all items have been loaded.

[0426] Figure 14 This is a flowchart illustrating the workflow of a user interface for executing / running options as shown in one embodiment. The run screen allows the user to instruct the system to start the run, for example, via a run button UI control. This screen also allows the user to register other users to update the system with messages. These updates can be circulated via, for example, email, a Short Message Service (SMS), social networking applications and / or blogs and / or others. Once the user starts the run, the system switches to display a timer indicating the estimated completion time. In one embodiment, the timer has three modes: 1) an estimated time in analog watch format; 2) an estimated time in spreadsheet format; and 3) a live camera feed from the instrument. The user can also request to stop the run via an advanced context menu.

[0427] Figure 15 This is a flowchart illustrating the workflow of the user interface for executing / uninstalling options as shown in one embodiment. Upon completion, the system switches to this uninstall screen. The "Uninstall" screen displays a list of steps for the uninstallation scroll wheel system. For each item, the system graphically displays where the item should be uninstalled. The system provides graphical instructions for loading or uninstalling items. The user needs to uninstall all items before proceeding to the next screen.

[0428] Figure 16This is a flowchart illustrating the workflow of a user interface for executing / reviewing options as shown in one embodiment. On the review screen, the system displays the run results. The results are also automatically exported in the following formats: file format; transmitted to a LIMS / LIS system; and email. The results are displayed and viewable: a) as a graphical presentation panel. A brightness scale displays the ECL or calculated concentration, where dark / black indicates lower results and bright colors indicate higher results. The scale provides a numerical representation of color brightness; b) the results can also be used as a table. The table can be exported in a file format; transmitted to a LIMS / LIS system; and / or email. For example, if the temperature during the run is outside the specified range, the system records any abnormal operation or result in the table. After the user reviews the run data, the user can move to the "Start" target to begin another run or view the results.

[0429] Figure 17 This is a flowchart illustrating a workflow for a user interface used to execute / review options in one embodiment. In one embodiment, the system categorizes user-executable tasks into primary workflows and advanced workflows. Primary workflows are those that the user regularly performs and optimizes for streamlined execution. Primary workflows are displayed in the "Goals" and "Steps" sections. Advanced workflows are displayed in the advanced context menu and represent workflows that are not typically executed or are not limited to the Configuration Manager. The user accesses the advanced context menu by clicking [Mesoscale Diagnostics Globe]. Advanced context menu items are included in a vertical scroll wheel with three main groups: functions related to the current screen (context-related items that change with the active screen); modules that can be switched to; and functions applicable to all modules, such as software login and logout. In this screen, selected options and the advanced menu are displayed horizontally on the graphics wheel, while sub-options of the advanced menu are displayed vertically on the vertical graphics wheel.

[0430] In one embodiment, the graphical user interface maximizes the black space by making the background black, thereby minimizing pixel coloring in the user interface display (e.g., display screen), saving storage and improving display speed. Figure 20 This is an example screenshot of a screen that maximizes the black space of the display graphics wheel / slide axis in one embodiment.

[0431] Figure 58 to Figure 64RR Showing further screenshot examples conforming to embodiments of this specification. Figures 58A to 58HH This is an exemplary, non-limiting embodiment of the reader module. Figures 59A to 59T This is an exemplary, non-limiting embodiment of the experimental module. Figures 60A to 60I This is an exemplary, non-limiting embodiment of the maintenance module. Figures 61A to 61QThis is an exemplary, non-limiting embodiment of the administrator console module. Figures 62A to 62P These are exemplary, non-limiting embodiments of general screenshots applicable to the multiple modules described in this specification. Figure 63 This is an exemplary, non-limiting embodiment of the audit trail module. Figures 64A to 64RR Examples of non-limiting embodiments of the determination method module.

[0432] Other screenshot examples conforming to the embodiments of this specification are included in U.S. Design Patent Application No. 29 / 675,777, filed January 4, 2019, entitled “Display Screen with Graphical User Interface,” the entire contents of which are incorporated herein by reference.

[0433] As mentioned above, whether used in a measurement system or another system, the user interface of this invention is able to present the complete trace on a single screen displayed by the user interface, such as on a graphics wheel, and allow the user to select any item on any layer to return from the current path of the selected item, for example, without having to type or press a series of back buttons on a keyboard or other input device. The user interface allows past decisions to be visible, such as major decisions and the most recent decision (viewing the decision history via scrolling through the graphics wheel or another graphical element such as a graphics slider).

[0434] In one embodiment, the graphical user interface reduces the number of menu selections a user needs to make to navigate the measurement system. For example, the order in which menu selections are displayed can reduce the number of options available to the user.

[0435] In one embodiment, computer processing time can be improved by reducing the number of options or choices displayed to the user and from which input is received. The user interface guides the user through the next step of the application while providing the user with the minimum number of selections required.

[0436] In other embodiments, certain features described herein can be used to divide one or more problems into distinct parts for multiple users to solve collaboratively (e.g., sequentially or in parallel). In this regard, the processor can be adapted to receive one or more benchmark inputs (e.g., inputs providing information that offers support or solutions for larger problems, experiments, measurements, or the like). Benchmark inputs can be aggregated, and these inputs can be collectively relied upon to collaboratively solve problems, conduct experiments, etc. These inputs can be based on one or more of the following: (a) a module; (b) a problem or sub-problem to be solved; (c) a device; (d) a physical location; (e) a tool; (f) an instrument; or (g) a device. Additionally, the processor can be adapted to notify more users, accounts, or teams of results derived from one or more of the received benchmark inputs. In one example (e.g., performing a measurement), this could include notifying the researcher responsible for conducting the experiment that the first user has completed the design of the measurement experiment (and thus notifying the researcher that the experiment is ready to be performed), and returning to the first user after the experiment is completed to further notify the researcher that the experiment has been performed (e.g., allowing the first user to review the results of the experiment). Furthermore, the processor can be adapted to supply output in response to received responses, such that the output can be adapted to be transmitted to a device communicatively connected to the processor (i.e., interfacing with components, devices, etc. in the physical world) for guiding the device to perform certain actions (e.g., physical movement or undergoing physical transformation). In some embodiments, the processor induces responses to these components in the physical world as steps within a broader process that breaks down one or more problems into distinct parts for multiple users to solve, as described above. Additionally, certain aspects of these processes (and others described throughout) can be controlled by the processor via permission commands. Permission commands can be used to manage one or more levels of access, security, or control for users and teams. Those permissions can be based on various levels, including one or more roles, users, teams, accounts, instruments, devices, or apparatuses. In this regard, a complex set of permissions can be created to create multiple security levels for multiple applications, allowing access, control, and security to be rigorously maintained and controlled in a highly generic manner.

[0437] The following discussion provides other embodiments and implementations of the system proposed in this specification. The user interface system discussed above can be widely used in various applications, including manufacturing environments, testing environments, instrumentation environments, experimental environments, etc. In a series of embodiments, the user interface system discussed above can be used to provide a user interface for a comprehensive biological instrument system, including software, hardware, testing equipment, and all other required features. This comprehensive biological instrument system is discussed below. In particular, the following discussion focuses on embodiments described in this specification as cloud-based systems. Examples are given below regarding... Figures 21 to 50 The embodiments discussed can also be implemented via alternative network hardware and software platforms.

[0438] For convenience only, the description herein is based on the accompanying drawings; it is not limited to the scope of embodiments of the invention. The following description applies to various analytical applications, including but not limited to bioanalytical applications, chemical analytical applications, radioanalytical applications, etc.

[0439] The components shown may include, for example, computer implementation components implemented and / or running on, or coupled to, one or more hardware processors. For example, one or more hardware processors may include components such as programmable logic devices, microcontrollers, memory devices, and / or other hardware components configured to perform the various functions described herein. Figures 21 to 50 The processor and cloud-based processing system disclosed herein may be examples of the processor (1110). Coupled memory devices may be configured to selectively store instructions executable by one or more hardware processors. (As in...) Figures 21 to 50 The memory devices and cloud-based storage systems disclosed herein may be examples of storage devices (1120). Examples of processors may include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a cloud-based processing unit, another suitable processing component or device, or one or more combinations thereof.

[0440] Figure 21To provide seamless integration with other systems, computers, and instruments, such as biological instruments, cloud-based systems are implemented to support and optimize user analytical work (e.g., bioanalytical work). System 21100 boundaries surround or partially constitute other systems, computers, and instruments that form part of the analytical computing system 21100, wherein the operating system on each computer and / or instrument is wholly or partially integrated with the analytical computing system 21100, and may include, for example, Windows™, UNIX, Linux, macOS™, iOS™, Android™, and / or any other commercial, open-source, and / or proprietary operating systems. Analytical user environments 21101 include one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which may be used in system 21100. One or more analytical user environments 21101 may use analytical system 21100. Support provider environment 21102 includes one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which can be used in system 21100 to support instruments, consumables, and / or software used by users in analysis user environment 21101. There may be one or more support provider environments 21102 using analysis computing system 21100. Consumable provider environment 21103 includes one or more servers, desktop computers, laptop computers, tablet computers, and / or one or more mobile devices that can be used in analysis computing system 21100 to provide consumables used by users in analysis user environment 21101, or in conjunction with instruments including instrument environment 21106. There may be one or more consumable provider environments 21103 using analysis computing system 21100.

[0441] An analytical instrument provider environment 21105 for instrument providers may be used in an instrument environment 21106, which includes one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which may be used in an analytical computing system 21100 to provide instruments for use by users, such as for sale or transfer, in an analytical user environment 21101. One or more instrument provider environments 21105 may use the analytical computing system 21100. An analytical computing system provider environment 21104 is for providers of the analytical computing system 21100, which includes one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which may be used in a system 211000 to manage business interactions with the analytical computing system 21100 used by analytical users in the analytical user environment 21101. Each of the “providers” in environments 21102, 21103, 21104, and 21105 may include one or more entities, including, but not limited to, multiple independent businesses, a single independent business, a combination of different independent businesses, or one or more businesses within any of the “providers” in this specification. Instrument environment 21106 includes one or more instruments, each having at least one computer, which in one implementation may be at least partially provided by analytical computing system 21100 for a user to run sample tests in analytical user environment 21101. Cloud platform 21107 provides leveraged connectivity (e.g., bidirectional connectivity) via computers, networks, and software. Some or all computers in analytics computing system 21100 have an implementation of a general-purpose computing, software services, and data architecture that allows data to be collected and shared by any computer with the associated software of analytics computing system 21100, regardless of location. The specific computers with the associated software in analytics computing system 21100 are always securely located worldwide. In a preferred embodiment, cloud platform 21107 is hosted by a public cloud provider offering a shared computing environment, such as Amazon. TM Web Services, Google TM Cloud, Microsoft TM Azure or others. In other embodiments, the analytics computing system provider environment (21104) may host cloud platform 21107; or the cloud platform may be self-hosted by an analytics user environment that is a user of analytics computing system 21100; or the cloud platform may be hosted by a private cloud provider that provides a dedicated computing environment, such as Oracle. TM Cloud, IBM TMCloud, Rackspace, or other; or, the cloud platform may be hosted in a combination of public cloud, private cloud, self-hosted, or hosted by the analytics computing system provider environment 21104. All communication with the cloud platform 21107 may be accomplished through preferred embodiments of secure communication protocols, such as, but not limited to, HTTPS, to encrypt all communication between the sender and receiver; however, insecure communication protocols (such as, but not limited to, Hypertext Transfer Protocol Secure, HTTPS) may also be selectively used in secure or insecure situations. Connection technologies (such as Ethernet for Local Area Network (LAN), Metropolitan Area Network (MAN), and / or Wide Area Network (WAN) configurations) and / or unconnected technologies (such as Wi-Fi, Bluetooth, and / or other similar technologies for distributed LANs) may be used. Furthermore, the analytics computing system 21100 may be deployed entirely on a single computer, such that all operations of the analytics computing system 21100 occur on said computer, with only external communication occurring between the computer and related software running outside the analytics computing system 21100.

[0442] Figure 22 For example Figure 21The illustrated cloud-based embodiment seamlessly integrates with other systems, computers, and instruments that support and optimize user analysis. The boundaries of the analytical computing system 21100 include other systems, computers, and instruments defined by all or part of the analytical computing system 21100. The analytical user environment 21101 includes one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which can be used in the analytical computing system 21100. The administrator computer 22202 includes one or more computers with software provided by the system administrator through services and data storage / retrieval provided by the cloud platform 22223 to manage the system 21100 used by users in the analytical user environment 21101. The analytical user computer 22203 includes one or more computers with software provided by the cloud platform 22223 for users in the analytical user environment 21101 to perform analytical tasks. Data integration computer 22204 includes one or more computers with software for integrating (e.g., bidirectional integration) other business systems 22224 in the analysis user environment 21101 with the analysis computing system 21100 that provides services and data storage / retrieval to the analysis user business system 22224 via cloud platform 22223. The analysis user business system 22224 may be hosted internally, externally, and / or in some combination of internal and external environments of the analysis user environment 21101, and may include one or more selectively software-enabled computer systems, such as Laboratory Information System (LIS), data analysis applications, data visualization applications, data reporting applications, business productivity applications, associated and / or unassociated databases, file servers, and / or any other systems, to provide data access of the analysis computing system 21100 to users who directly use the analysis computing system 21100, users who do not directly use the analysis computing system 21100, and / or one or more other computer systems with the business system 22224 that do not directly interface with the analysis computing system 21100.

[0443] Support provider environment 21102 is a support provider whose support is for users of analytical computing system 21100, users of consumables from consumables providers, and / or instruments in instrumentation environment 21106, including one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which can be used in analytical computing system 21100 to support instruments, consumables, and / or software used by users in analytical user environment 21101.

[0444] User support computer 22206 includes one or more computers having software provided to users of the support provider environment 21102, the software being able to monitor, manage, and / or report activities on the analytical computing system 21100 through services and data storage / retrieval provided by the cloud platform 22223; and data integration support computer 22207 includes one or more computers having software and / or firmware for integrating other support business systems 22208 in the support provider environment 21102 with the analytical computing system 21100 that provides services to support business systems 22208 through services and data storage / retrieval provided by the cloud platform 22223. The supporting business system 22208 may be hosted internally, externally, and / or through some combination of internal and external environments in the support provider environment 21102, and may include one or more computer systems with optional software, such as customer relationship management, enterprise data systems, data analysis applications, data visualization applications, data reporting applications, business productivity applications, associated and / or unassociated databases, file servers, and / or any other systems, to provide data access to the analytical computing system 21100 to users who directly use the supporting user computer 22206, users who do not directly use the supporting user computer 22206, and / or one or more other computer systems with the supporting business system 22208 that do not directly interface with the analytical computing system 21100.

[0445] Consumable provider environment 21103 is a consumable provider environment comprising one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which can be used in analytical computing system 21100 to provide consumables to users in analytical user environment 21101. It can also be used selectively in conjunction with instruments in instrumentation environment 21106 to provide consumables to users in analytical user environment 21101, with selective use of instruments in instrumentation environment 21106. Consumable information uploading computer 22210 comprises one or more computers with software for transferring consumable information about the provided consumables from consumable provider business system 22211 to analytical computing system 21100 via services and data storage provided by cloud platform 22223. As used in this specification, consumable information may include, but is not limited to, Global Product Data (GPD). The consumable provider business system 22211 may be hosted internally, externally, and / or through some combination of internal and external environments within the consumable provider environment 21103, and may include one or more computer systems with optional software, such as customer relationship management, enterprise data systems, data reporting applications, business productivity applications, associated and / or unassociated databases, file servers, and / or any other systems that support the consumable provider's business operations to support the delivery of consumable information to the analytical computing system 21100 or not at all to the analytical computing system 21100.

[0446] The analytical computing system provider environment 21104 is an analytical computing system provider environment for the provider of analytical computing system 21100, which includes one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which can be used in analytical computing system 21100 to provide analytical computing system 21100 to users in analytical user environment 21101 and instruments in instrument environment 21106, as well as to various provider environments 21102, 21103, and 21105. The account information uploading computer 22213 includes one or more computers with software for preparing and controlling the use of analytical computing system 21100 by the users in analytical user environment 21101 and instruments in instrument environment 21106, through services provided via cloud platform 22223 and data storage. The business system 22214 of the computing system provider may be hosted within, outside and / or in some combination of internal and external environments of the analytical computing system provider environment 21104, and may include one or more computer systems with optional software, such as customer relationship management, enterprise data systems, data reporting applications, business productivity applications, associated and / or unassociated databases, file servers, and / or any other systems that support the business operations of the analytical computing system provider to support the preparation and control of the use of the analytical computing system 21100, or may not be used at all for the preparation and control of the use of the analytical computing system 21100.

[0447] The instrument provider environment 21105 includes one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which can be used in the analytical computing system 21100 to provide instruments to users in the analytical user environment 21101, and can optionally be used as instruments in the instrument environment 21106 to process samples to be tested, and may optionally have one or more consumables provided in the consumable provider environment 21103. The instrument information uploading computer 22216 includes one or more computers with software for transferring instrument information, including information about the provided information, from the instrument provider business system 22217 to the analytical computing system 21100 via services and data storage provided by the cloud platform 22223. The instrument provider business system 22217 may be hosted internally, externally, and / or in some combination of internal and external environments within the instrument provider environment 21105, and may include one or more computer systems with optional software, such as customer relationship management, enterprise data systems, data reporting applications, business productivity applications, associated and / or unassociated databases, file servers, and / or any other systems that support the instrument provider’s business operations to support the transmission of instrument information to the analytical computing system 21100, or may not be used at all for the transmission of instrument information to the analytical computing system 21100.

[0448] Instrumentation environment 21106 includes one or more instruments, each of which may be a personal operating instrument 22221, a coordinated operating instrument 22222, or a workflow assisting instrument 22226 provided by instrument provider environment 21105. The user of analysis user environment 21101 can leverage this to selectively process samples using consumables provided by consumable provider environment 21103, generating data to be analyzed by the user in analysis user environment 21101. Personal operating instrument 22221 may have a personal operating instrument computer 22219 to provide integration between personal operating instrument 22221 and analysis computing system 21100 through services and data storage provided by cloud platform 22223. The system may selectively provide operational control for the individual operating instrument 22221; the coordinated operating instrument 22222 may also have a coordinated operating instrument computer 22220 to provide integration between the coordinated operating instrument 22222 and the analytical computing system 21100 through services and data storage provided by the cloud platform 22223, and selectively provide operational control for the coordinated operating instrument 22222; and the workflow assistance instrument 22226 may have a workflow assistance instrument computer 22225 to provide integration between the workflow assistance instrument 22226 and the analytical computing system 21100 through services and data storage provided by the cloud platform 22223, and selectively provide operational control for the workflow assistance instrument 22226. Examples of a single operating instrument 22221 include, but are not limited to, plate readers, plate cleaners, plate incubators, plate shakers, plate incubator shakers, dispensing systems, or any other type of instrument used for analyzing sample testing. The coordinated operating instrument 22222 can automatically perform some or all of the functions provided by one or more individual operating instruments 22221 into an integrated platform for the individual operation of the individual operating instruments 22221, thereby freeing the user from performing the various individual operations of the individual operating instruments 22221. The workflow assistance instrument 22226 can support the user in leveraging the individual operating instruments 22221 and / or the coordinated operating instrument 22222 to test sample determinations in the instrument environment 21106, which supports, but is not limited to, collecting various consumables that may be stored in different physical locations at various temperatures, preparing consumables for use in the processing of one or more determinations, and / or using one or more individual operating instruments 22221 to guide the user through the entire determination process. In addition to or replacing the determination tests and board-based tests described in this specification, the consumable provider environment analysis user APP 21103 can also assist with other tests.

[0449] The instruments in the instrumentation environment 21106 may include zero or more individual operating instruments 22221, each with its corresponding individual operating instrument computer 22219; zero or more coordinated operating instruments 22222, each with its corresponding coordinated operating instrument computer 22220; and / or zero or more workflow assistance instruments 22224, each with its corresponding workflow assistance instrument computer 22225. A preferred embodiment of the instrumentation environment 21106 includes providing a separate computer to integrate the zero or more individual operating instruments 22221, zero or more coordinated operating instruments 22222, zero or more workflow assistance instruments 22224, zero or more individual operating instrument computers 22219, zero or more coordinated operating instrument computers 22220, and zero or more workflow assistance instrument computers 22225 into the analysis and computing system 21100 via services and data storage provided by the cloud platform 22223.

[0450] Figure 23 This is an embodiment of the system architecture of a cloud platform 22223 as part of an analytical computing system 21100 that provides public computing, software services, and data architecture, enabling the use of an analytical computing system 21100 ( Figure 21The related software allows any computer anywhere in the world to collect and share data, wherein one or more service servers 23302 provide a flexible, robust, and high-performance computing and related software platform to support specific services of the analytical computing system 21100 for retrieving, storing, transmitting, and / or transforming data related to the use of the analytical computing system 21100; one or more database servers 23309 (e.g., comprising one or more team databases 23310 and one or more system databases 23311) provide a flexible, robust, and high-performance computing and related software platform for one or more structured databases for storing and / or retrieving data generated and / or used by users of the analytical computing system 21100, and for storing and / or retrieving data generated and / or used by the analytical computing system 21100 for its preparation and use, wherein the database technology may be inherently relational, such as SQL Server, Oracle, MySQL, Postgres, Aurora, and / or other similar relational database technologies; and / or inherently non-relational database technologies, such as Dynamo DB, MongoDB, etc. DB, and / or other similar non-relational database technologies; and one or more large data servers 23315, which may contain system content 23312, instrument content 23313 and consumable content 23314, to provide a flexible, robust, and high-performance computing and related software platform for storing and retrieving file-based data provided by and / or generated by the analytical computing system 21100. In one embodiment, the service server 23302 is integrated with logical integration services, namely: management 23303 with logical integration services to support the management of the use of the analytical computing system 21100; dashboard 23304 with logical integration services to support monitoring and control of the use of the analytical computing system 21100; upload 23305 with logical integration services to support uploading consumable and instrument information to the analytical computing system 21100; system 23306 with logical integration services to support various non-user-specific functions related to the overall use of the analytical computing system 21100; application 23307 with logical integration services to support typical scientific use of the analytical computing system 21100 by analytical users; and authentication 23308 with logical integration services to support secure login to and logout from the analytical computing system 21100.In one implementation, service server 23302 is a flexible computing infrastructure from one or more servers represented by service server 23302. In a preferred embodiment, each server has deployed all logically integrated services 23303, 23304, 23305, 23306, 23307, and 23308, enabling a load balancer to evenly distribute service requests across the one or more servers represented by service server 23302 to optimize user interaction. For example, this load balancing technique can be implemented if the logically integrated services 23303, 23304, 23305, 23306, 23307, and 23308 are designed using the RESTful (representing state transition) design pattern, i.e., each provided service is stateless, i.e., does not store or store data. Therefore, any request on the service can be satisfied by any available server, wherein the services deployed on service server 23302 can be based on the demand at the time of the request. To support optimal deployment and operation of logically integrated services 23303, 23304, 23305, 23306, 23307, and 23308 on one or more computers, preferred embodiments configure these services on a distributed object platform, such as, for example, Java Platform Enterprise Edition capable of supporting cross-platform computing architectures, the .NET Framework on Windows-only computing architectures, or other similar distributed object platforms, or leveraging some combination of one or more of these distributed object platforms. Database server 23310 may contain one or more databases, such as a team database 23310 and a system database 23311. Team database 23310 is adapted to store information, data, and / or metadata (e.g., team name, members, permissions, etc.) about a “team.” System database 23111 may contain files, data, and / or other information about system functions. In addition, the large data server 23315 may contain various contents, such as "system contents" 23312, such as data or contents related to system functions, such as instrument contents 23313 (e.g., instrument type, parameters, etc.); and consumables 23314, such as consumable type, quantity, etc.

[0451] Figure 24This is an embodiment whereby an administrator uses an administrator computer 24401 to run administrator APP software 24402 to provide services via cloud platform 22223 to perform management functions provided by analytical computing system 21100. As described in this specification, the administrator APP software may employ a MUI as described above to facilitate user access to the provided functions. Therefore, an embodiment of a systematic user interface control system 1102 can be provided through a combination of administrator computer 24401 and cloud platform 22223. For example, one or more service servers 24411 may provide various functions such as authentication, one or more other management functions, the ability to upload data, such as to one or more database servers, one or more system functions, one or more applications (e.g., APP functions), and / or graphical visualization support via dashboards. The administrator app 24402 can be executed on the administrator computer 24401 via a unique application installed on the administrator computer 24401, or accessed via an internet browser installed on the administrator computer 24401, which points to a Uniform Resource Locator (URL) provided by the cloud platform 22223 for the web service portion. In this embodiment, it uses the logical organization of management 24408, but is not limited to that organization. In one embodiment, the initial interaction between the administrator and the cloud platform occurs by using the administrator app 24402 to request a login service, for example, via the user manager 1056 of the systematized user interface control system 1102, through service link 24403 for authentication 24404, using appropriate credentials, such as a unique username and password and / or indicator identifier, and may also include optional or required additional authentication input, commonly referred to as two-factor authentication, previously configured and used by the administrator. In this embodiment, the login service retrieves the user's encrypted credentials from the system database 24406 via service link 24405. It then uses login update data stored in the system database 24406 via service link 24407 to verify whether the administrator can access and manage the analytics computing system 21100, thereby tracking the use of the analytics computing system 21100. If the administrator forgets or does not know their password, they can also reset their password via the administrator app 24402 via service link 24403. This is then verified 24404 using password reset update data stored in the system database 24406 via service link 24407, to track the use of the analytics computing system 21100.Administrators can also configure additional authentication inputs via service link 24403 (authentication 24404) through administrator app 24402, use service link 24407 to update configuration changes of data stored in system database 24406, and retrieve and change the configuration of additional authentication inputs via service link 24405 (system database 24406) to track the use of analytics computing system 21100. After logging in as an administrator, administrators can use services provided by management 24403 via service link 24407 through administrator app 24402 to perform management functions of analytics computing system 21100. These services also create and update data stored in system database 24406 as needed via service link 24407. These services are used to create, read, update, and / or delete data stored in system database 24406 (e.g., via data storage manager 1064) using service link 24407 to track the use of analytics computing system 21100. Furthermore, provided by the administrator APP 24402, the administrator performing the management functions of the analytics computing system 21100 can create one or more new group users. These users use the analytics computing system 21100 through the shared team database 24414 via service link 24413, and create a new database server 24415 via service link 24412. New team databases 24414 can be added to optimize the performance of database server 24415. Finally, the administrator can log out of the analytics computing system 21100 via service link 24403 through the administrator APP 24402 to terminate current use of the analytics computing system 21100. The logout service of authentication 24404 updates the administrator's login information via service link 24409 of the system database 24406, and updates the data stored in the system database 24406 via service link 24407 to track the use of the analytics computing system 21100. The analytics computing system 21100 may contain one or more service servers 24411. These servers are adapted to host various applications and / or modules, including system modules, application modules, authentication modules, management modules, dashboard modules, and upload modules. In one embodiment, the authentication and management modules allow users to communicate with the system database 24406 and / or team database 24414 via, for example, through one or more service links via the administrator APP 24402.

[0452] Figure 25This is an embodiment of an analytical user who uses an analytical user computer 25502 to run analytical user APP software 25503 to perform analytical functions provided by analytical computing system 21100 through services provided by cloud platform 22223. As discussed in this specification, analytical user APP software 25503 may employ a MUI as described above to facilitate user access to the provided functions. Therefore, an embodiment of a systematic user interface control system 1102 can be provided through a combination of analytical user computer 25502 and cloud platform 22223. The analytical user computer 25502 is executed or accessed by different applications 25503 installed on the analytical user computer 25502, or via an internet browser installed on the analytical user computer 25502, the internet browser using the webpage pointing URLs provided by cloud platform 22223, which in this embodiment is logically organized using application 25509, but is not limited to such organization. In one implementation, the initial interaction between the analytics user and the cloud platform 22223 is via service link 25504 using the analytics user app 25503, which requires login, and authentication 25505 with appropriate credentials. These credentials may include a unique username and password and / or other information (such as biometric identifiers), and may also include optional or required additional authentication input, commonly referred to as two-factor authentication, previously configured for management use. The login service can retrieve the user's encrypted credentials from the system database 25507 via service link 25506 to verify whether the analytics user can access and use the analytics computing system 21100 via service link 25506 using login update data stored in the system database 25507 to track the use of the analytics computing system 21100. If a user forgets or does not know their password, the analytics user can also reset their password via service link 25504 through the analytics user app 25503, and then verify 25505 using password reset update data stored in the system database 25507 via service link 25506 to track the use of the analytics computing system 21100. The analytics user can also configure their additional verification inputs for verification 25505 via service link 25504 through the analytics user app 25503, and update data retrieval and changes to their additional verification configuration entered via service link 25506 through the system database 25507 via service link 25506, to track the use of the analytics computing system 21100.After logging in and verifying their user account, the user can access services provided by application 25509 via service link 25508 through the user analysis app 25503 to perform analytics functions provided by application 25509. These services, as needed, utilize service link 25510 to create, read, update, and / or delete data stored in team database 25511, using data also created and updated in system database 25507 via service link 25510, to track the use of analytics computing system 21100. Finally, the user can log out of analytics computing system 21100 via service link 25504 through the user analysis app 25503, terminating their current use of analytics computing system 21100. The user's login information is updated via service link 25506 (authentication 25505) through system database 25507, and the data stored in system database 25507 is updated via service link 25506 to track the use of analytics computing system 21100.

[0453] Figure 26This is an embodiment of a data integration computer 26602 running data integration APP software 26603, which performs data integration functions provided by the analysis computing system 21100 through services provided by the cloud platform 22223 between the analysis computing system 21100 and computing systems that are selectively not part of the analysis computing system 21100. As described in this specification, the data integration APP software 26603 may employ the aforementioned MUI to facilitate user access to the provided functions. Therefore, the combination of the data integration computer 26602 and the cloud platform 22223 provides an embodiment of a systematic user interface control system 1102. The data integration APP 26603 may be provided as part of the analysis computing system 21100 and / or may be provided by the analysis user or someone working with the analysis user. In one implementation, the initial interaction between the data integration app 26603 and the cloud platform 22223 is a request for a login service via service link 26604 to authenticate 26605 using appropriate credentials configured by the administrator. These credentials preferably include a unique username and password, and may also include optional or required additional authentication inputs, commonly referred to as two-factor authentication, previously configured by the administrator. The login service can retrieve the encrypted credentials of the data integration app 26603 from the system database 26607 via service link 26606 to verify whether the data integration app 26603 can access and use the analytics computing system 21100 via service link 26606 using login update data stored in the system database 26607, in order to track the use of the analytics computing system 21100. After logging in and verifying the data integration APP 26603, the APP can use the services provided by application 26609 via service link 26608 to perform analysis functions provided by application 26609. As needed, these services use service link 26610 to create, read, update, and / or delete data stored in team database 26611. The use of these services also uses service link 26610 to create and update data stored in system database 26607 to track the use of analysis computing system 21100. Finally, the data integration app can log out of the analysis and computing system 21100 via service link 26604 through the data integration app 26603 to terminate the current use of the analysis and computing system 21100. Through service link 26606 of the system database 26607, the data integration app login information is updated by the authentication service 26605. The data stored in the system database 26607 is also updated via service link 26606 to track the use of the analysis and computing system 21100.

[0454] Figure 27This is an embodiment of a user monitoring an analytical computing system 21100 using a supporting user computer 27702 with user monitoring app 27703, wherein the monitoring functions provided by the analytical computing system 21100 are performed via services provided by cloud platform 22223. As described in this specification, the user monitoring app 27703 may employ the aforementioned MUI to facilitate user access to the provided functions. Therefore, an embodiment of a systematic user interface control system 1102 can be provided through a combination of supporting user computer 27702 and cloud platform 22223. The user monitoring app 27703 can be executed on the supporting user computer 27702 through various applications installed on the supporting user computer 27702 or accessed via an internet browser installed on the supporting user computer 27702. In this embodiment, the internet browser uses a website pointing URL, but is not limited to, a service provided by cloud platform 22223 with a dashboard 27709 logical organization. In one implementation, the initial interaction between the user's computer and the cloud platform is achieved by using the monitoring user app 27703 to request a login service via service link 27704, authenticating with appropriate credentials 27705. These credentials preferably include a unique username and password and / or indicator identifier, and may also include optional or required additional verification input, commonly referred to as two-factor authentication, previously configured by the administrator. The login service can retrieve the user's encrypted credentials from the system database 27707 via service link 27706 to verify whether the monitoring user can access and monitor the analytics computing system 21100 via service link 27706 using login update data stored in the system database 27707 to track the use of the analytics computing system 21100. If the user forgets or does not know their password, the monitoring user can also reset their password via service link 27704 through the monitoring app 27703, authenticating with password reset update data stored in the system database 27707 via service link 27706 27705 to track the use of the analytics computing system 21100. The monitoring user can also configure their own additional verification inputs for verification 27705 via the monitoring user APP 27703 through service link 27704, and use the configuration change update data stored in the system database 27707 through service link 27706 to retrieve and change their additional verification input configuration in the system database 27707 through service link 27706, in order to track and analyze the use of the computing system 21100.After logging in and verifying their user account, users can use services provided by dashboard 27709 via monitoring user app 27703 through service link 27708 to perform monitoring functions of analytics computing system 21100. These services, as needed, use service link 27710 to create, read, update, and / or delete data stored in system database 27707 to track the use of analytics computing system 21100. Finally, monitoring users can log out of analytics computing system 21100 via monitoring user app 27703 through service link 27704 to terminate their current use of analytics computing system 21100 using verified logout service 27705. Logout update data stored in system database 27707 is then used via service link 27706 to update the administrator's login information to track the use of analytics computing system 21100.

[0455] Figure 28This is an embodiment of a data integration computer 28802 that runs monitoring data integration application software 28803 to perform monitoring data integration functions provided by the analysis computing system 21100, between the analysis computing system 21100 and a computing system that is selectively not part of the analysis computing system 21100, via services provided by the cloud platform 22223. As described in this specification, the monitoring data integration APP software 28803 may employ the aforementioned MUI to facilitate user access to the provided functions. Therefore, an embodiment of a systematic user interface control system 1102 can be provided by a combination of the data integration computer 28802 and the cloud platform 22223. Thus, the monitoring data integration APP software is adapted to track, review, and / or monitor one or more features of the data integration functions described in this specification. In one implementation, the initial interaction between the monitoring data integration app 28803 and the cloud platform 22223 is a request for login service via service link 28804 to authenticate 28805 using appropriate credentials configured by the administrator. These credentials preferably include a unique username and password and may also include optional or required additional authentication input, commonly referred to as two-factor authentication, which has been previously configured for use by the administrator. The login service can retrieve the encrypted credentials of the monitoring data integration app 28803 from the system database 28807 via service link 28806...

Claims

1. A laboratory coordination system, comprising: Laboratory coordination device, comprising: A networking component that is configured to send and receive information via a network; A non-transitory computer-readable storage medium configured to store software instructions; and At least one processor is configured to execute the software instructions for: Establish one or more network connections with one or more laboratory instruments and / or one or more user devices; Obtain an experimental protocol, which contains multiple experimental steps to be performed; In response to a first instruction request, a first instruction is provided for performing a first experimental step of the plurality of experimental steps; Receive an indication that the first experimental step has been completed; and In response to a second instruction request, a second instruction is provided for performing a second experimental step among the plurality of experimental steps.

2. The laboratory coordination system of claim 1, wherein obtaining the experimental protocol includes obtaining the stored experimental protocol.

3. The laboratory coordination system of claim 2, wherein obtaining the stored experimental protocols comprises obtaining the stored experimental protocols from a stored list of experimental protocols.

4. The laboratory coordination system of claim 3, wherein the stored list is prioritized.

5. The laboratory coordination system of claim 4, wherein the stored list is prioritized according to at least one of the following: Maximize throughput; Minimize in a single experiment; and / or Priority factor.

6. The laboratory coordination system of claim 2, wherein obtaining the stored experimental protocols comprises obtaining a plurality of stored experimental protocols based on the identified capabilities of the one or more laboratory instruments.

7. The laboratory coordination system of claim 6, wherein the identified capability comprises one or more of the following: Instrument functionality Instrument capacity, Instrument processing time, The instrument moves. Instrument response time, Instrument parameters, and Instrument consumables compatibility.

8. The laboratory coordination system of claim 6, wherein the identified capability comprises one or more of the following: Remaining instrument capacity Instrument supply level, Instrument availability, Instrument uptime, and Instrument location.

9. The laboratory coordination system of claim 6, wherein the at least one processor is further configured to: Generate multiple instructions corresponding to the multiple stored experimental protocols; and The multiple instructions are provided to the one or more laboratory instruments to be performed in an interleaved manner on the one or more laboratory instruments.

10. The laboratory coordination system of claim 1, wherein the at least one processor is further configured to: A second experimental protocol is obtained during the execution of instructions related to the aforementioned experimental protocol; Generate additional instructions for performing steps related to the second experimental protocol; and The additional instructions are provided to the one or more laboratory instruments to enable the additional instructions to be executed in an interleaved manner with the instructions related to the execution of the experimental protocol.

11. The laboratory coordination system of claim 1, wherein the at least one processor is further configured to: The conversion library is accessed from a plurality of conversion libraries, each corresponding to a type of laboratory instrument and containing machine instructions configured to execute corresponding measurement protocol steps on a laboratory instrument of a corresponding type, wherein the conversion library is selected based on the identified instrument type of the one or more laboratory instruments; and The first instruction is generated based on the conversion library.

12. The laboratory coordination system of claim 11, wherein the type of said laboratory instrument includes at least one of the following: Instrument manufacturer Instrument model Instrument software version Instrument hardware version, Instrument modification, Instrument functionality, and Instrument identifier.

13. The laboratory coordination system of claim 1, wherein obtaining the experimental protocol comprises obtaining the experimental protocol based on input via the one or more user devices.

14. The laboratory coordination system of claim 1, wherein the first instruction request is received from a user device operating a graphical user interface via the one or more network connections, and the first instruction includes a first command configured to cause the graphical user interface to provide instructions for the first experimental step.

15. The laboratory coordination system of claim 1, wherein the instructions are provided in at least one of visual, text, and auditory formats.

16. The laboratory coordination system of claim 1, wherein the instruction to complete the first experimental step is received from a user device operating a graphical user interface via the one or more network connections.

17. The laboratory coordination system of claim 16, wherein the instruction includes the second instruction request, and the second instruction includes a second command configured to cause the graphical user interface to display instructions for the second experimental step.

18. The laboratory coordination system according to claim 16, wherein: The second instruction request is received from the second instrument in response to the instruction of the second instrument of the one or more instruments after the first experimental step is completed, identifying the measurement plate. The second instruction is generated based on the correspondence between the second experimental step and the second instrument.

19. The laboratory coordination system according to claim 1, wherein: The first instruction request is received from the first instrument in response to a first instrument identification measuring plate in one or more of the instruments, and The first instruction is generated based on the correspondence between the first experimental step and the first instrument.

20. The laboratory coordination system of claim 18, wherein the correspondence indicates the capability of the first instrument to perform the first experimental step; and The first instruction contains a command to execute the first experimental step.

21. The laboratory coordination system of claim 20, wherein executing the command of the first experimental step causes the first instrument to perform an action associated with the first experimental step.

22. The laboratory coordination system of claim 20, wherein the capability of the first instrument is defined according to at least one of the following: Online / offline status; Usage status; Functional status; and Consumable availability status.

23. The laboratory coordination system of claim 18, wherein the correspondence indicates the impossibility of the first instrument performing the first experimental step; and The first instruction does not contain a command to execute the first experimental step.

24. The laboratory coordination system of claim 1, wherein the experimental protocol is a measurement protocol to be executed on the measurement plate.

25. The laboratory coordination system of claim 24, wherein the assay protocol is an electrochemiluminescence protocol.

26. The laboratory coordination system of claim 1, wherein the one or more laboratory instruments comprise at least one of the following: Electrochemiluminescence reader, Test plate washer, Measuring plate oscillator, Assay plate incubator, and Pipettes.

27. A laboratory coordination system, comprising: Laboratory coordination device, comprising: A networking component that is configured to send and receive information via a network; A non-transitory computer-readable storage medium configured to store software instructions; and At least one processor is configured to execute the software instructions for: Establish one or more network connections with one or more laboratory instruments or one or more user devices; Multiple experimental protocols were obtained, each containing multiple corresponding experimental steps to be performed on the corresponding test plate; Receive a first identifier from the first instrument of the one or more instruments; Select a first experimental protocol from the plurality of experimental protocols based on the first identifier; Select the first experimental step from the first experimental protocol based on the capabilities of the first instrument; as well as The first instruction is provided to the first instrument to perform the first experimental step on the first measurement plate.

28. The laboratory coordination system of claim 27, wherein the instruction for executing the first experimental step causes the first instrument to perform an action associated with the first experimental step.

29. The laboratory coordination system of claim 27, wherein the software instructions are further configured to: Receive the second identifier of the second measuring plate from the second instrument of the one or more instruments; Select the corresponding second experimental protocol from the plurality of experimental protocols according to the second identifier; Select a second experimental step from the corresponding second experimental protocol based on the capabilities of the second instrument; as well as The second instruction is provided to the second instrument to perform the second experimental step on the second measuring plate.

30. The laboratory coordination system of claim 29, wherein at least a portion of the first experimental step is performed simultaneously with a portion of the second experimental step.

31. The laboratory coordination system of claim 30, wherein the first experimental protocol is different from the second experimental protocol.

32. The laboratory coordination system of claim 27, wherein the software instructions are further configured to: Receive a second identifier from the second instrument of the one or more instruments; The first experimental protocol is selected from the plurality of experimental protocols based on the second identifier; Select a second experimental step from the first experimental protocol based on the capabilities of the second instrument; as well as The second instruction is provided to the second instrument to perform the second experimental step on the first measuring plate.

33. The laboratory coordination system of claim 27, wherein the software instructions are further configured to: Select a second experimental step from the first experimental protocol based on the second capability of the first instrument; and The second instruction is provided to the first instrument to perform the second experimental step on the first measuring plate.

34. The laboratory coordination system of claim 27, wherein the software instructions are further configured to: The guidance instructions are provided to the first user device, and the guidance instructions include a list of measurement plate identifiers and a corresponding list of instrument identifiers.

35. The laboratory coordination system of claim 34, wherein the correspondence list of instrument identifiers includes instrument types corresponding to the identifiers of the measurement plates.

36. The laboratory coordination system of claim 34, wherein the correspondence list of instrument identifiers includes specific instruments corresponding to the identifiers of the measurement plates.

37. The laboratory coordination system of claim 34, wherein the software instructions are further configured to determine the guidance instructions according to a load balancing criterion.

38. The laboratory coordination system of claim 37, wherein the load balancing criterion comprises at least one of the following: Instrument availability; Operator availability; Consumable availability, and Equipment efficiency.

39. The laboratory coordination system of claim 37, further comprising: Receive notification of changes to the load balancing criteria; as well as The guidance instructions are updated according to the changes made to the load balancing criteria.

40. The laboratory coordination system of claim 27, wherein the first experimental step comprises at least one of the following: Washing steps, Add steps, Cultivation steps, and Reading steps.

41. The laboratory coordination system of claim 36, wherein the first experimental step includes a reading step and the software instructions are further configured to: Obtain the reading result from the first instrument; and The reading result is transmitted to the first user device.

42. The laboratory coordination system of claim 27, wherein obtaining the plurality of experimental protocols comprises obtaining the plurality of experimental protocols from a plurality of user devices.

43. The laboratory coordination system of claim 27, wherein the experimental protocol is a measurement protocol to be executed on the measurement plate.

44. The laboratory coordination system of claim 43, wherein the measurement protocol is an electrochemiluminescence protocol.

45. The laboratory coordination system of claim 27, wherein the one or more laboratory instruments comprise at least one of the following: Electrochemiluminescence reader, Test plate washer, Measuring plate oscillator, Assay plate incubator, and Pipettes.

46. ​​A laboratory coordination system, comprising: Laboratory coordination device, comprising: A networking component that is configured to send and receive information via a network; A non-transitory computer-readable storage medium configured to store software instructions; and At least one processor is configured to execute the software instructions for: Establish one or more network connections with one or more laboratory instruments and / or one or more user devices; Obtain an experimental protocol, which contains multiple experimental steps to be performed; In response to a first instruction request, a first instruction is provided to the user via the one or more user devices for performing the first experimental step of the plurality of experimental steps; Receive the indication that the first experimental step has been completed; as well as In response to a second instruction request, a second instruction is provided to the user via the one or more user devices for performing a second experimental step among the plurality of experimental steps.

47. A laboratory coordination system, comprising: Laboratory coordination device, comprising: A networking component that is configured to send and receive information via a network; A non-transitory computer-readable storage medium configured to store software instructions; and At least one processor is configured to execute the software instructions for: Establish one or more network connections with one or more instruments or one or more user devices; Multiple experimental protocols are obtained, and each experimental protocol contains multiple corresponding experimental steps to be executed; Receive a first identifier from the first instrument of the one or more instruments; Select a first experimental protocol from the plurality of experimental protocols based on the first identifier; Select the first experimental step from the first experimental protocol based on the capabilities of the first instrument; The first instruction is provided to the first instrument to execute the first experimental step; as well as The second instruction is provided to the user via the one or more user devices to facilitate the second experimental step.

48. A laboratory coordination system, comprising: Laboratory coordination device, comprising: A networking component that is configured to send and receive information via a network; A non-transitory computer-readable storage medium configured to store software instructions; and At least one processor is configured to execute the software instructions for: Establish one or more network connections with one or more instruments or devices; Multiple experimental protocols were obtained, each containing multiple corresponding experimental steps to be performed on the corresponding test plate; Receive a first identifier from the first instrument of the one or more instruments; Select a first experimental protocol from the plurality of experimental protocols based on the first identifier; The first instruction is provided to the first instrument to perform the first experimental step on the first measuring plate; as well as The second instruction is provided to the first instrument to perform the second experimental step on the first measuring plate.

49. A computer-implemented method for laboratory coordination, performed by a laboratory coordination device comprising at least one processor configured to execute software instructions, the method comprising: Establish one or more network connections with one or more laboratory instruments and / or one or more user devices; Obtain an experimental protocol, which contains multiple experimental steps to be performed; In response to a first instruction request, a first instruction is provided for performing a first experimental step of the plurality of experimental steps; Receive an indication that the first experimental step has been completed; and In response to a second instruction request, a second instruction is provided for performing a second experimental step among the plurality of experimental steps.

50. A computer-implemented method for laboratory coordination, performed by a laboratory coordination device comprising at least one processor configured to execute software instructions, the method comprising: Establish multiple network connections with multiple laboratory instruments and / or one or more user devices; The identifier corresponds to the instrument type of the plurality of laboratory instruments. The capability set of the multiple laboratory instruments is identified according to the multiple instrument types; Multiple experimental protocols are obtained, each of which contains multiple corresponding experimental steps to be executed; as well as Generate multiple instructions to be provided to the multiple laboratory instruments for executing the multiple experimental protocols.

51. The computer-based implementation method for laboratory coordination according to claim 50, further comprising: Access to multiple conversion libraries, each corresponding to a type of laboratory instrument and containing machine instructions configured to execute corresponding measurement protocol steps on a laboratory instrument of a corresponding type, wherein the multiple conversion libraries are selected based on the instrument type of the multiple laboratory instruments; and The multiple instructions are generated based on the conversion library.

52. The computer implementation method of claim 50, wherein obtaining the plurality of experimental protocols includes obtaining a plurality of stored experimental protocols.

53. The computer implementation method of claim 52, wherein obtaining the plurality of stored experimental protocols comprises obtaining the plurality of stored experimental protocols from a stored list of experimental protocols.

54. The computer implementation method of claim 53, wherein the stored list is prioritized.

55. The computer implementation method of claim 54, wherein the stored list is prioritized according to at least one of the following: Maximize throughput; Minimize in a single experiment; and / or Priority factor.

56. The computer implementation method of claim 52, wherein obtaining the plurality of stored experimental protocols comprises obtaining the plurality of stored experimental protocols based on the identified capabilities of the one or more laboratory instruments.

57. The computer implementation method of claim 50, wherein the identified capability comprises one or more of the following: Instrument functionality Instrument capacity, Instrument processing time, The instrument moves. Instrument response time, Instrument parameters, and Instrument consumables compatibility.

58. The computer implementation method of claim 50, wherein the identified capability comprises one or more of the following: Remaining instrument capacity Instrument supply level, Instrument availability, Instrument uptime, and Instrument location.

59. The computer-implemented method of claim 50, wherein the type of said laboratory instrument includes at least one of the following: Instrument manufacturer Instrument model Instrument software version Instrument hardware version, Instrument modification, Instrument functionality, and Instrument identifier.

60. The computer implementation method of claim 50, wherein the capability of the laboratory instrument is defined according to at least one of the following: Online / offline status; Usage status; Functional status; and Consumable availability status.

61. The computer implementation method of claim 50, wherein at least one of the plurality of experimental protocols comprises an electrochemiluminescence assay protocol.

62. The computer-implemented method of claim 50, wherein the one or more laboratory instruments comprise at least one of the following: Electrochemiluminescence reader, Test plate washer, Measuring plate oscillator, Assay plate incubator, and Pipettes.

Images