Laboratory collaboration devices, methods, and systems

Abstract

Systems, methods, and devices for laboratory collaboration are provided. A laboratory collaboration device may be configured to interface and communicate with multiple user devices and multiple laboratory instruments. A laboratory collaboration device may be configured to coordinate the activities of multiple laboratory instruments according to multiple experimental protocols acquired via multiple user devices. A laboratory collaboration device may be further configured to provide a user interface to headless laboratory instruments.

Description

Technical Field

[0001] Related Matters This application claims the priority of U.S. Provisional Application No. 63 / 481,512, filed on January 25, 2023, entitled "LABORATORY COORDINATION DEVICES, METHODS, AND SYSTEMS", the entire content of which is incorporated herein by reference in its entirety.

[0002] This application generally relates to computers and computer applications, and more specifically, to graphical user interfaces and display methods for displaying user-interactive items on a graphical user interface. This application further relates to a user interface module configured to guide a user or operator in the preparation and execution of one or more experimental procedures such as assays.

Background Art

[0003] The present disclosure improves testing, analysis, and processing through the integration between a software interface having consistency at various process positions and instrumentation devices and equipment associated with the process in various applications including, but not limited to, biological analysis, chemical analysis, radiation analysis, other sciences (such as bioscience and biometric operations), and industrial processes, which lead to the use of instrumentation devices for scientific tests (such as biological tests, biometric measurements) and equipment for industrial processes.

[0004] In many cases, computer systems and / or applications utilize a series of menus or similar elements presented to the user to receive input in order to perform their functions. When the user selects an option or chooses from a list of menu items, the computer system and / or application performs its function based on the selected option and / or may present another list of menu items (e.g., a list of submenu items that depend on the selected option). The computer system and / or application continues this process of executing its menu-driven function, for example, until the function is completed. In such menu-driven systems, previously selected options on which the ongoing function of the computer system and / or application depends are often not visible on the user interface. Therefore, for example, the path of a retrieved menu item may not be visible at the time the computer system and / or application process is in progress. Furthermore, options for unselected paths, as well as retrieved paths, may also not be visible on the user interface. Therefore, improving the user interface is often desirable.

[0005] In many cases, instrumentation devices used in conjunction with analytical applications (e.g., biometric measurements, but not limited to these) are used in laboratories. Therefore, data generated by these instrumentation devices is stored as data files on a shared network drive for post-processing and import into other electronic systems, namely laboratory information management systems (LIMS). Typically, these integrations require extensive and time-consuming software development and integration to provide the generated data to end users. Typically, these data integrations occur in a regulated environment (e.g., 21 CFR Part 11), an environment that requires the generated data to be stored in a way that ensures it cannot be altered by end users. Furthermore, these integrations are provided to end users to support post-processing of the generated data for supplemental analysis, reporting, and sharing with other end users, often referred to as collaborators. Additionally, the use of instrumentation devices and post-processing of the generated data should preferably be carried out under a controlled, uniform, unified, and traceable process within a closely collaborating group of end users. This helps in producing consistently accurate supplemental analyses and reports. To use instrumentation for generating data for supplemental analysis and reporting, the end user typically needs to use lot-specific consumables (e.g., biological consumables including, but not limited to, reagents and analytes) in combination with the sample under test to create the reaction to be measured for generating data, and to use the lot-specific information used for supplemental analysis and reporting. To obtain these consumables, the end user must purchase them from a provider, which must not only ship the physical consumables to the end user but also provide lot-specific information on the shipped consumables so that the end user can use the consumables on the instrumentation and perform the desired post-processing. In addition to the normal use of the instrumentation and associated consumables, there are usually important support features to ensure that the instrumentation and / or associated consumables always function optimally for the customer.The level of workflow integration required to optimally perform collective and collaborative work related to end-user use of instrumentation equipment is extremely high and complex. This necessitates a simple and user-friendly user interface, while the entire analytical workflow remains complex for the user. Thus, an improved analytical computing system and user interface that is associated with and includes instrumentation equipment and associated consumables may be desirable.

[0006] Additional fields beyond instrumentation systems face similar challenges. For example, various manufacturing settings present difficulties in workflow integration, parts tracking, consumable tracking, work-in-progress tracking, process and parts production documentation, and all of the aforementioned issues with respect to instrumentation systems. In addition, this application provides solutions to areas of consumer needs for organization, prioritization, and workflow improvement in business, office, home, travel, and leisure settings, for example. Other examples exist, and the solutions disclosed herein are not limited to solutions for the problems considered above. [Overview of the Initiative]

[0007] Embodiments described herein may relate to a laboratory collaboration system comprising a laboratory collaboration device, the laboratory collaboration device comprising: a networking component configured to transmit and receive information over a network; a non-temporary computer-readable storage medium configured to store software instructions; and at least one processor configured to execute software instructions in order to establish one or more network connections with one or more laboratory instruments and / or one or more user devices; to acquire an experimental protocol comprising a plurality of experimental steps to be performed; to provide a first instruction in response to a first instruction request for the performance of a first experimental step of the plurality of experimental steps; to receive an indication that the first experimental step has been completed; and to provide a second instruction in response to a second instruction request for the performance of a second experimental step of the plurality of experimental steps.

[0008] Embodiments described herein may relate to a laboratory collaboration system comprising a laboratory collaboration device, the laboratory collaboration device comprising: a networking component configured to transmit and receive information over a network; a non-temporary computer-readable storage medium configured to store software instructions; and at least one processor configured to establish one or more network connections with one or more laboratory instruments or one or more user devices; acquire a plurality of experimental protocols, each experimental protocol comprising a plurality of corresponding experimental steps performed on a corresponding assay plate; receive a first identification of a first assay plate from a first instrument among one or more instruments; select a first experimental protocol from the plurality of experimental protocols according to the first identification; select a first experimental step from the first experimental protocol according to the capabilities of the first instrument; and provide a first instruction to the first instrument to execute a software instruction in order to perform the first experimental step on the first assay plate.

[0009] Embodiments described herein may relate to a laboratory collaboration system comprising a laboratory collaboration device, the laboratory collaboration device comprising: a networking component configured to transmit and receive information over a network; a non-temporary computer-readable storage medium configured to store software instructions; and at least one processor configured to establish one or more network connections with one or more laboratory instruments and / or one or more user devices; acquire an experimental protocol comprising a plurality of experimental steps to be performed; in response to a first instruction request, provide a first instruction to a user via one or more user devices for the performance of 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, execute a software instruction to provide a second instruction to a user via one or more user devices for the performance of a second experimental step of the plurality of experimental steps.

[0010] Embodiments described herein may relate to a laboratory collaboration system comprising a laboratory collaboration device, the laboratory collaboration device comprising: a networking component configured to transmit and receive information over a network; a non-temporary computer-readable storage medium configured to store software instructions; and at least one processor configured to establish one or more network connections with one or more instruments or one or more user devices; to acquire a plurality of experimental protocols, each experimental protocol comprising a plurality of corresponding experimental steps to be performed; to receive a first identification of a first assay plate from a first instrument among one or more instruments; to select a first experimental protocol from the plurality of experimental protocols according to the first identification; to select a first experimental step from the first experimental protocol according to the capabilities of the first instrument; to provide a first instruction to the first instrument to perform the first experimental step; and to provide a second instruction to a user via one or more user devices to execute a software instruction to facilitate a second experimental step.

[0011] Embodiments described herein may relate to a laboratory collaboration system comprising a laboratory collaboration device, the laboratory collaboration device comprising: a networking component configured to transmit and receive information over a network; a non-temporary computer-readable storage medium configured to store software instructions; and at least one processor configured to establish one or more network connections with one or more instrument devices, acquire a plurality of experimental protocols, each experimental protocol comprising a plurality of corresponding experimental steps performed on a corresponding assay plate, receive a first identification of a first assay plate from a first instrument among one or more instruments, select a first experimental protocol from the plurality of experimental protocols according to the first identification, provide a first instruction to the first instrument to perform a first experimental step on the first assay plate, and provide a second instruction to the first instrument to perform a second experimental step on the first assay plate, by executing software instructions.

[0012] Embodiments described herein may relate to a computerized laboratory implementation method performed by a laboratory-cooperative device including at least one processor configured to execute software instructions, wherein the method includes 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 the performance of 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 the performance of a second experimental step of the plurality of experimental steps in response to a second instruction request.

[0013] Embodiments described herein may relate to a laboratory-cooperative computer implementation method performed by a laboratory-cooperative device including at least one processor configured to execute software instructions, wherein the method includes establishing multiple network connections with a plurality of laboratory instruments and / or one or more user devices; identifying instrument types corresponding to the plurality of laboratory instruments; identifying capability sets of the plurality of laboratory instruments according to the plurality of instrument types; acquiring a plurality of experimental protocols, each experimental protocol including a plurality of experimental steps to be performed; and generating a plurality of instructions to be provided to the plurality of laboratory instruments to perform the plurality of experimental protocols.

[0014] Further features and the structure and operation of various embodiments will be described in detail below with reference to the attached drawings. [Brief explanation of the drawing]

[0015] [Figure 1] This is a method for displaying interactive items on a user interface display for computer user interaction, according to one embodiment. [Figure 2A-2O] An exemplary graphical user interface display in one embodiment is shown. [Figure 2P] An example of a systematic user interface including an advanced context menu, according to one embodiment of this specification, is shown. [Figure 3] This flowchart illustrates a method for interactively displaying interactive items on a user interface display for computer user interaction in another aspect. [Figure 4] This is a flowchart showing the user login interface of an assay system in one embodiment. [Figure 5] This is a flowchart illustrating a method for displaying the start user interface screen display in one embodiment. [Figure 6] A diagram showing the workflow of a definition assay method screen in one embodiment. [Figure 7] A diagram showing the user interface workflow for selecting an assay method in one embodiment. [Figure 8] A flowchart showing the workflow of the user interface displayed for defining a sample in one embodiment. [Figure 9] A flowchart showing the workflow of the user interface displayed for verifying the startup definition in one embodiment. [Figure 10] A flowchart showing the workflow of the user interface displayed for notifying the user of completed tasks in one embodiment. [Figure 11] A flowchart showing the workflow of the user interface displayed for execution / collection options in one embodiment. [Figure 12] A flowchart showing the workflow of the user interface displayed for execution / preparation options in one embodiment. [Figure 13] A flowchart showing the workflow of the user interface displayed for execution / load options in one embodiment. [Figure 14] A flowchart showing the workflow of the user interface displayed for execution / startup options in one embodiment. [Figure 15] A flowchart showing the workflow of the user interface displayed for execution / unload options in one embodiment. [Figure 16] A flowchart showing the workflow of the user interface displayed for execution / review options in one embodiment. [Figure 17] A flowchart showing the workflow of the user interface displayed for execution / review options in one embodiment. [Figure 18]Shows components of a graphical user interface (GUI) system in one embodiment. [Figure 19] Shows a schematic diagram of an exemplary computer or processing system that can implement a graphical user interface system in one embodiment. [Figure 20] Is an exemplary screenshot of a screen showing a graphical wheel / slider that maximizes the screen black space in one embodiment. [Figure 21] Shows a cloud-based analysis computing system in one embodiment. [Figure 22] Shows the system architecture of a cloud-based analysis computing system in one embodiment. [Figure 23] Shows the system architecture of a cloud platform in a cloud-based analysis computing system in one embodiment. [Figure 24] Shows the interaction between an administrator computer and a cloud platform in one embodiment. [Figure 25] Shows the interaction between an analysis user computer and a cloud platform in one embodiment. [Figure 26] Shows the interaction between a data integration computer and a cloud platform in one embodiment. [Figure 27] Shows the interaction between a support user computer and a cloud platform in one embodiment. [Figure 28] Shows the interaction between a support data integration computer and a cloud platform in one embodiment. [Figure 29] Shows the interaction between a consumable information upload computer and a cloud platform in one embodiment. [Figure 30]This illustrates the interaction between an account information upload computer and a cloud platform in one embodiment. [Figure 31] This illustrates the interaction between an instrument information upload computer and a cloud platform in one embodiment. [Figure 32] This illustrates the interaction between a linked operating instrument computer and a cloud platform in one embodiment. [Figure 33A] This illustrates the interaction between an individual instrument computer and a cloud platform in one embodiment. [Figure 33B] Figure 33A illustrates the interaction between the workflow auxiliary instrument computer and the cloud platform in the embodiment shown. [Figure 34A] The first part of a software architecture for a cloud platform service in one embodiment is shown. [Figure 34B] Figure 34A shows a second part of the software architecture for the cloud platform service of the embodiment shown. [Figure 35A] This shows the logical design of system data in one embodiment. [Figure 35B] This describes the mapping of business entities to accounts using an analytical computing system in one embodiment. [Figure 35C] This document describes the logical design of team data related to plate data in one embodiment. [Figure 35D] This describes the logical design of team data related to assay method data in one embodiment. [Figure 35E] This document shows the logical design of team data related to startup data in one embodiment. [Figure 35F] This document describes the logical design of team data related to experimental data in one embodiment. [Figure 36A] An exemplary structure of an account for a user of an analytical computing system in one embodiment is shown. [Figure 36B] This illustrates the flow for creating an account for a user of an analytical computing system in one embodiment. [Figure 36C] This illustrates the flow of associating instruments with user accounts in an analytical computing system in one embodiment. [Figure 36D] This describes a flow in one embodiment for associating consumables with a user account of an analytical computing system. [Figure 37] This shows a module within an administrator software application in one embodiment. [Figure 38A] This illustrates the flow of the admin console module within the administrator app for account administrators in one embodiment. [Figure 38B] This illustrates the flow of the admin console module within the admin app for team administrators in one embodiment. [Figure 38C] This shows the user login process flow in one embodiment. [Figures 38D-38H] Figure 38A provides a screenshot illustrating the work experience flow as an example. [Figure 38I] This document provides an example of an advanced context menu associated with the management console module. [Figure 39A] This illustrates a flow for the administrative audit trail module in an administrator application in one embodiment. [Figures 39B-39E] This shows a user interface configuration for a management audit trail module consistent with the embodiments described herein. [Figure 40] This shows a module in an analytical user software application in one embodiment. [Figure 41] This shows a flow for an analysis method module in an analysis user application in one embodiment. [Figure 42A] This document shows the design flow of an assay method module in an analytical user application in one embodiment. [Figure 42B] This shows the review flow of the assay method module in an analytical user application in one embodiment. [Figure 43A] This document shows the design flow of an experimental module in an analytical user application in one embodiment. [Figure 43B] This describes the review flow of the experimental module in an analysis user application in one embodiment. [Figures 43C-43H] This section shows an embodiment of the reader module user interface consistent with the embodiments described herein. [Figure 44] This describes a flow for the audit trail module in an analytics user application in one embodiment. [Figure 45] This shows a module in a linked instrument software application in one embodiment. [Figure 46] This shows a flow for the operation module in the linked instrument application in one embodiment. [Figure 47] This shows the flow of the maintenance module within the linked instrument app in one embodiment. [Figure 48] This shows a module in an individual instrument software application in one embodiment. [Figure 49A] This shows a flow for the operation module in an individual instrument application in one embodiment. [Figure 49AA] The following shows a flow for the control module in an individual control instrument application in another embodiment. [Figure 49B] This describes the flow of results review as an individual instrument application in an operating module related to a plate reader in one embodiment. [Figure 50] This shows a module in a workflow auxiliary instrument software application in one embodiment. [Figure 51] This shows the workflow assistance module in a workflow assistance instrument application in one embodiment. [Figure 52]This is one embodiment of a computing flow for automated software updates for an analytical user computer. [Figure 53] This is one embodiment of a computing flow for automated software updates for analytical instrument computers. [Figure 54] This is one embodiment of an example of a non-biological use of the disclosed architecture for a software module within a chef app. [Figure 55] This is one embodiment of a user experience flow that starts with a chef app and proceeds through a meal planner module. [Figure 56] This document describes a system for implementing a systematic user interface according to one embodiment. [Figure 57] This demonstrates the process of navigating a hierarchical menu tree through a user interface. [Figures 58A-58HH] This is an exemplary, non-limiting embodiment of a leader module. [Figures 59A-59T] This is an exemplary, non-limiting embodiment of the experimental module. [Figures 60A-60I] This is an exemplary, non-limiting embodiment of a maintenance module. [Figures 61A-61Q] This is an exemplary, non-limiting embodiment of the management console module. [Figures 62A-62P] This is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules of this specification. [Figure 63] This is an exemplary, non-limiting embodiment of an audit trail module. [Figures 64A-64RR] This is an example of a non-limiting embodiment of the assay method module. [Figure 65] This shows a UI display consistent with the collection and preparation module in one embodiment. [Figure 66] This shows a UI display consistent with the collection and preparation module in one embodiment. [Figure 67] This shows a UI display consistent with the collection and preparation module in one embodiment. [Figure 68] This shows a UI display consistent with the collection and preparation module in one embodiment. [Figure 69] This shows a UI display consistent with the collection and preparation module in one embodiment. [Figure 70] This shows a UI display consistent with the collection and preparation module in one embodiment. [Figure 71] This shows a UI display consistent with the collection and preparation module in one embodiment. [Figure 72] This shows a UI display consistent with the collection and preparation module in one embodiment. [Figure 73A-C] This shows the laboratory system configured for the performance of the assay steps. [Figures 73D-73F] The components of a laboratory system consistent with the embodiments described herein are shown. [Figure 74] This shows a UI display consistent with the assay guide module in one embodiment. [Figure 75] This shows a UI display consistent with the assay guide module in one embodiment. [Figure 76] This shows a UI display consistent with the assay guide module in one embodiment. [Figure 77(a)-(c)] This shows a UI display that matches the instrument submodule of the assay guide module in one embodiment. [Figure 78] This specification describes the operational workflow of multiple users interacting with a collaborative server according to the embodiments described herein. [Figure 79A-D] The operating modes of the laboratory system according to embodiments of this specification are shown. [Figure 80A-C] This document describes the operation method of a laboratory-linked device according to embodiments of this specification. [Figure 81A] The assay scheduling operation according to the embodiments specified herein is shown. [Figure 81B] The assay execution operation according to the embodiments of this specification is shown. [Figure 82]This describes the offline mode of operation of the laboratory-connected device according to the embodiments of this specification. [Figure 83] This specification describes the online mode of operation of the laboratory-connected device according to the embodiments described herein. [Figure 84] This specification describes the collaboration modes of operation for laboratory-connected devices according to the embodiments described herein. [Modes for carrying out the invention]

[0016] The embodiments described herein provide technical solutions to a variety of technical problems through improvements to existing technologies and the creation of entirely new technologies. Among the technical problems addressed by the embodiments considered herein are the inefficiencies of conventional user interfaces and the difficulties in integrating different parts of process workflows.

[0017] The user interface improvements discussed herein provide practical applications of technical solutions to problems in conventional user interfaces related to user inefficiency, accuracy, repeatability, and computing inefficiency. The technical solutions provided herein improve each of these embodiments through the use of the user interface methods and techniques of the present invention. In particular, the technical solutions provided by the user interfaces disclosed herein provide users with a more efficient means of navigating menu systems for complex processes.

[0018] User interfaces for electronic devices implemented for human-computer interaction or communication often include a set of menus or similar selection options that the user chooses (e.g., selecting a set of options in a hierarchical manner) to get the computer or similar device to perform a desired function. In some embodiments, depending on the type of application, the amount of information or the number of menu options presented to the user may be overwhelming. Using broad menu options, the user may try various options or navigate through various menu selection hierarchies before finding the correct set of options or the desired option. In some examples, only about 10% of the user interface and functional options available to the user are used. On the other hand, if all options are presented 100%, it may be difficult for the user to decide where to navigate to find that 10% that is relevant to them. Also, since the selected menu option affects the next option that is performed under the menu option path, when a user switches options, it means the user also navigates through multiple different paths that lead from that option. Such trial and error can be time-consuming, costly, and inefficient when scrolling and paging through the many different options that may arise during user interface navigation.

[0019] The systems, methods, and techniques of this disclosure can provide a user interface that guides the user through a selection of options, selected via a user interface display or another presentation device, thereby reducing the time it takes to find the correct selection. In this way, the number of incorrect selection attempts is reduced, the time spent navigating the user is shortened, and the desired calculation function or goal can be completed. In some embodiments, the user interface of this disclosure can present the user with a selectively limited number of options from all available options in a particular manner, guiding the user through those options, streamlining the operation, and allowing the user to focus on more efficiently reaching the desired calculation function. In another embodiment, the user interface of this disclosure allows the user to connect to the application more directly.

[0020] Embodiments and technical solutions provide practical applications of certain visual principles to assist users when navigating the menus and systems described herein. Such visual principles include minimizing visual content and maximizing background or empty space in order to reduce visual clutter and highlight areas of interest. By providing a dark or otherwise uniform background and increasing the contrast between content and background, the user's attention can be drawn to the appropriate area.

[0021] The embodiments and technical solutions provide practical applications of specific design principles for assisting users when navigating the menus and systems described herein. These design principles include, for example, minimizing the number of menus and / or selections that a user must navigate at one time.

[0022] Further design principles include presenting the user with a single new choice at any given time, while also offering the option to easily revisit previously selected choices. This principle may be implemented via a two-part display system. The active part may be configured to display the user's current choice, and the history part may be configured to display information related to previous choices. Together, the active and history parts may provide a "direct workflow mode." The active part, which presents the user's current choice, may have a strict limit on the number of menu items displayed, e.g., 7, 5, 3 (or any other number), and other potential items from the same menu may be displayed in other locations. Previously selected choices (and the menus in which they were selected) may be presented to the user in a nested or stacked format. A nested series of previously navigated menus may be presented in the style of Russian nesting dolls (Matryoshka), where each previously selected menu item expands into a displayed submenu. Nested or stacked previously selected menu items may also provide a breadcrumb trail, which shows the user the path taken to arrive at the current menu. In certain embodiments, an indicator bar may be provided to draw the user's attention to previously selected menu items. For example, if previously selected menu items are arranged in a stack format, the use of an indicator bar may help to vertically align one or more menus and / or menu items. This is illustrated, for example, in Figure 61D. In this example, an indicator bar (located below the “Add / Remove” item) helps to draw the user's attention to and align the “Administrative,” “Legal,” and “Add / Remove” items. In this example, an indicator bar (located below the “Add / Delete” item) helps to draw the user's attention to and align the following items, namely “Administrative,” “Legal,” and “Add / Delete.” In certain embodiments, the indicator bar may be depicted to resemble a watchhand, as illustrated in Figure 61D. Furthermore, the indicator bar may include color-coded states (e.g., red to indicate an error state, blue to indicate a non-error state).In a particular embodiment, a color-coded state can be depicted within a portion of an indicator bar by illuminating pixels of one or more colors. In one example, the color-coded state may be provided within the middle portion of the indicator bar, as illustrated in Figure 61D, but this state may also be displayed in other parts of the UI display.

[0023] Embodiments of this specification maintain a consistent appearance throughout the use of the interface, regardless of the task or process being completed, by maintaining a consistent screen position of menus, for example, so that the user does not need to search for menus in different locations. In other words, the relevant menu is moved to the active portion of the screen as needed to attract the user's attention. In embodiments, the active portion of the screen remains centered, with respect to top-down and left-to-right perspectives. In further embodiments, the size and shape of the menu interface are modified according to the device or screen on which the menu interface is viewed. The menu can be expanded horizontally on wider screens and / or vertically on taller / narrower screens.

[0024] The embodiments described herein enhance user productivity by providing improvements in efficiency and accuracy through enhancements to several aspects of the user experience. The user interface described herein focuses the user on the most likely use case while minimizing distractions caused by less frequently used options. This focus minimizes visual distractions from the user interface, keeping the user focused on the most relevant menu options. The user interface described herein aims to guide the user from one step to the next while eliminating the problem of the user becoming confused about what to do next. In the embodiments described herein, the user's navigation path through the interface system remains transparent to the user to facilitate the selection of alternative options or backing out of the current menu. Throughout the process of using the user interface, the user may have the option to discreetly browse alternative paths throughout the process. Thus, a core function of the user interface software provided herein is to reduce the total amount of information presented to the user at once, while increasing the total amount of relevant information presented to the user at once. Additional information and options for less frequently used cases remain available in a discreet presentation style. Such decisions regarding information to be presented via the user interface at any given time may be guided in advance through a predetermined menu workflow and / or influenced and updated through an analysis of previous user actions and choices.

[0025] Furthermore, computer functionality can be improved through embodiments provided herein. For example, resource usage of devices that may be involved in launching a user interface (e.g., user devices and / or server devices) can be reduced by focusing on a limited number of options. For example, processor resource usage such as memory usage and central processing unit (CPU) usage, hard drive or similar persistent storage usage, and bandwidth required for communication between devices (e.g., device-to-device, device-to-server, server-to-server) may be reduced. Also, the ability to directly navigate to or reach the correct selection or path of selection can improve communication efficiency between devices and servers, for example, by eliminating the need for a lot of trial-and-error navigation. This can reduce, for example, the internet communication and costs associated with such communication.

[0026] Further embodiments discussed herein relate to the integration of various process workflow configurations. As discussed herein, “process workflow” can be derived in relation to instrumentation (including biometric) testing workflows, manufacturing workflows, analytical workflows, and / or any workflow that may involve one or more instruments at least partially controlled by one or more computing systems. In additional embodiments, a process workflow consistent with the embodiments discussed herein may include the use of one or more consumables.

[0027] Computing systems consistent with the user interface and process workflow management systems considered herein include, but are not limited to, a variety of architectures including, a single computing device system, a desktop computing system, a laptop computing system, a tablet computing system, a mobile device computing system, a thin client computing system, a cloud-based computing system, a server computing system, a multi-device computing system, a device / printer system, a device / server computing system, a system including multiple devices and servers, or any other suitable computing system.

[0028] The process interface system described herein plays a role in improving user accuracy, efficiency, and satisfaction by providing a user interface that is faster to use, reduces the time it takes to find the correct menu item, reduces the selection of inaccurate menu items, and shortens overall workflow time. Compared to conventional systems that can provide instant access to 100% of options (of which only 10% are frequently used), the system described herein can provide instant access only to frequently used functions (e.g., in usage examples of 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 95% or more, 70-95% or more, 80-95% or more). The solution provided herein then helps improve computing efficiency, reduce memory usage, and decrease the utilization of CPU, hard drive, power, and communication resources.

[0029] The user interface systems discussed herein 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. Collectively, user interface systems consistent with the embodiments described herein may be referred to as “systematic 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. Some of the principles discussed herein are considered specifically in relation to GUIs, for example, but are not intended to be limiting, and the principles discussed herein may also be applied to other interface systems.

[0030] As used herein, MUI refers to “Display,” “Interface,” and “User Interface.” As used herein, “Display,” “Interface,” and “User Interface” refer to text, images, visual components, interactive elements, and any other visual aspects shown or displayed on a screen, projection, or other visual display hardware, unless otherwise specified. Thus, as used herein, “Display” and “Interface” are understood to be provided via any type of visual display hardware, screen, and / or projector. For convenience, menus, interfaces, and other visual items refer herein to being viewed on or displayed by the MUI. Such reference is understood to indicate that the MUI is visually presented via a hardware device as considered herein.

[0031] As will be described in more detail below, the user interface systems described herein may use various visual components to present menu items. For example, visual components may include a vertical “wheel” or a horizontal wheel that rotates through various menu items. As described herein, the use of a “wheel” as a visual component refers to the way in which prominent (highlighted) and receding (unhighlighted) options are presented to the user. A wheel-shaped visual component can be understood as a virtual wheel with its rim facing the user, and multiple menu items arranged on the rim of the virtual wheel. A wheel-shaped visual component may or may not include any visual indicator of the wheel’s presence. A wheel-shaped visual component may present prominent options to the user in an attention-grabbing manner (i.e., on the part of the wheel “closest” to the user), while other receding options may be presented in a non-attention-grabbing manner. Prominent menu items may be highlighted in different colors, presented in different fonts, presented in larger fonts, or otherwise marked to visually attract attention. As the virtual wheel rotates, the currently selected prominent menu item rotates away from the user (either clockwise or counterclockwise), and the currently selected receding menu item becomes a new prominent option. In embodiments, a receding menu item closest to a prominent menu item may be displayed to attract more attention than a menu item further receding from the prominent menu item. For example, menu items may be reduced in size or brightness based on their distance from the currently selected prominent menu item. As the “wheel” “rotates”, receding menu items may be faded out of view. In this form, the virtual wheel provides the user with the perception and sensation that all menu items are located on the actual wheel. The visual component may further include horizontal or vertical sliders for sliding through various menu items. Similarly, as considered above, sliders may be used to provide prominent menu items, receding menu items, or non-prominent menu items to the wheel.In some embodiments, the slider may differ from the wheel in that the back menu items are not obscured from view as the options within the slider slide past. Further embodiments of the wheel and slider are discussed further herein with respect to specific embodiments.

[0032] As discussed herein, menu items can be “selected,” “highlighted,” and / or “clicked.” As used herein, “highlighting” a menu item means that the “highlighted” option is made conspicuously visible to the user, for example, as a prominent menu item in the center of the wheel. “Highlighting” may include changing the color, size, font, etc., of the menu item to visually emphasize it to the user. “Dehighlighting” a user option may include changing the color, size, font, etc., of the menu item to make it less conspicuous to the user. Menu items may be highlighted or dehighlighted in response to user actions (for example, via clicking a mouse, touching a touchscreen, rotating a wheel, etc.) (for example, by presenting a menu item that the user cannot select or edit), and / or based on an interface action (for example, by presenting a highlighted default option).

[0033] As used herein, "selecting" a menu item means that the menu item has been selected by the user and the user interface has advanced one or more menu steps according to the selection. When a menu item is "selected," the computer system not only "highlights" the menu item but also executes computer instructions to advance the menu. For example, selecting a menu item may display a new menu based on the selection. A selected menu item may be highlighted after selection, but highlighting a menu item does not necessarily involve selecting the menu item.

[0034] In some embodiments, menu items may be selected or highlighted by clicking them. As used herein, “click” refers to a user action of pointing to or selecting a menu item by clicking, tapping, or otherwise using an interface device (e.g., a mouse, touchscreen, etc.). As used herein, “clicking” a menu item is not the same as “selecting” a menu item. Click refers to a user action of pointing to a menu item, while selection refers to the computer function associated with selecting a menu item.

[0035] In some embodiments of the system according to this specification, menu items may be selected by clicking. Clicking a menu item may cause the system to proceed to the next set of menu items. In other embodiments of the disclosed system, clicking a menu item serves to highlight the menu item, but does not select the menu item and cause the system to proceed to the next menu item.

[0036] Menu items may be described herein as “selectable.” A “selectable” menu item is one that the user can interact with either by selecting it or by highlighting it. Selectable menu items may be indicated as selectable through changes such as coloring, highlighting, or font changes. Menu items may also be described herein as “not selectable.” A “not selectable” menu item is one that the user cannot currently interact with either by selecting or highlighting it. Not selectable menu items may be indicated as not selectable through changes such as coloring, highlighting, or font changes.

[0037] Menu items may also be described as "previously selected" and "previously not selected." A "previously selected" menu item refers to a menu item that was selected to arrive at the ongoing menu interface display. A "previously selected" menu item does not need to be actively selected by the user. If the system, by programmed default, brings the user to a menu level below the top level, a menu item or choice in the current path may be indicated as "previously selected," even if the user did not actively select it during the ongoing session. A "previously not selected" menu item refers to a menu item that was not selected to arrive at the ongoing menu interface display. For example, if the user has selected a first menu item and not a second menu item, the system may proceed to display a subsequent menu or submenu in response to the selection of the first menu item in the active portion of the MUI. In the history portion of the MUI, the system may display the first menu item as a previously selected menu item and the second menu item as a previously not selected menu item. A previously not selected menu item may be displayed as selectable.

[0038] For example, the user may scroll a slider or rotate a wheel through various menu items. The user can adjust the wheel or slider so that a particular menu item is highlighted. In one embodiment, a particular menu item may require a further user interaction (e.g., a single or double-click) to be "selected," so that the MUI presents a new set of menu items or submenu items in response to the selection. In one such embodiment, the user rotates the wheel or scrolls the slider to move the desired menu item to the highlighted prominent menu item. The user then clicks, double-clicks, or otherwise indicates selection as confirmation of the highlighted menu item to display the next menu or submenu. In one embodiment, a particular menu item may be "selected" at the same time it is highlighted. In one such embodiment, the associated submenu is presented immediately when the desired menu item is highlighted by rotating the wheel or scrolling the slider to move the desired menu item to the highlighted prominent menu item position.

[0039] As discussed herein, the selection or highlighting of a menu item may be triggered by directly selecting (i.e., clicking, touching, etc.) the menu item, whether it is a prominent menu item or a backed-up menu item, and wherever it is located on the wheel, slider, and / or list item. The selection or highlighting of a menu item may also occur in response to user interaction with various visual components, moving the menu item to a highlighted or selected position. For example, the user may rotate the wheel or move the slider until a particular menu item becomes a prominent menu item or a highlighted menu item. Interaction with visual components and / or direct selection may be implemented by using any suitable user input device, including touchscreens, mice, keyboards, arrow keys, gaze detection systems, motion detection systems, and gesture detection systems.

[0040] Features of an interface embodiment may be referred to as the “first part” and the “second part.” These terms refer to specific parts of the displayed user interface and do not need to be fixed in a specific position on the screen. As used herein, the “first part” may also be referred to as the “active part.” The “first part” or “active part” represents the part of the MUI that displays the current or most recent set of menu items. The “first part” and “active part” may be used interchangeably herein. The “second part” may also be referred to as the “history part.” The “second part” or “history part” represents the part of the interface that displays previously viewed menus, previously selected menu items, and previously unselected menu items. The “second part” and “history part” may be used interchangeably herein.

[0041] Figure 1 illustrates a method in one embodiment for interactively navigating a user through a path of menu options on a user interface. The method may be performed automatically by at least one hardware processor. The method facilitates user navigation through the system by displaying one or more past choices made by the user, along with other unselected options, and by asking questions, while drilling down to additional choices based on initial choices. As used herein, “asking questions” means presenting the user with one or more menu options from which to select. The method allows the user to continue along the path, jump to a different path, go back in time to choices made in one or more previous steps, or return to the most recent point in time of the choices the user has selected. In one embodiment, the user interface can present and display, on the same screen, whether past or previous choices were selected or not, at each step of the path, regardless of where the user is on the path. For example, the user interface presents an overview of the user’s menu option path, including unselected menu items. User interface techniques enable more efficient navigation, guiding the user along a path, allowing users to confirm their path, and enabling them to deviate from their assigned path. User interface techniques also allow users to view breadcrumb trails before and after their current location, confirming where they are going and where they can go.

[0042] As discussed herein, menus are presented as a hierarchical menu tree. Each level of the menu tree contains multiple menus that lead to other menus. For example, 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 up to the execute menu level. In some discussions herein, the first menu is simply referred to as a menu, and subsequent menu layers in the tree are referred to as sub-submenus, etc. In this case, multiple layers of menus below the ongoing menu may be collectively referred to as submenus. Therefore, a submenu of the first menu may contain multiple second menus, multiple third menus, multiple fourth menus, multiple execute menus, etc. An example of a hierarchical menu tree structure is shown in Figure 2K. As used herein, with respect to a hierarchical menu tree, each level is referred to as a "menu" even if it does not present a literal menu to the user. For example, a "menu" may only present an "execute" button to implement a process designed through the rest of the menu. Another "menu" could, for example, present a tutorial.

[0043] Each numbered menu contains multiple menu items or options, each item or option pointing to a newer menu at a lower level. Thus, each item in the first menu may point to one of several second menus. In some embodiments, menu layers may be skipped. For example, an option in the first menu may point to one of several third menus.

[0044] In embodiments, each menu may also include additional information for display within the MUI. This additional menu information may provide user information about the items within the menu and / or general context about the menu. For example, if a menu presents a save file option to the user, additional information indicating the remaining disk space may be provided. In another example, if a menu presents an option related to an assay to be launched, additional information about available consumables related to the assay being displayed may be provided.

[0045] At the execution menu level, that is, the final level of a series of menus, the user can select an execution menu option or item. These options or items do not lead to further menus, but instead represent a selection of process parameters intended to facilitate the menu tree. By selecting an execution menu option or item, the system executes the function associated with the selected menu option or item. For example, when using an assay design menu tree, the execution menu options may include options such as a file name, assay parameters, and reagent selections.

[0046] In the embodiment, the execution menu can facilitate the interface between the MUI software and the material world. The execution menu can implement a process designed through the use of the MUI by executing commands output to a system or instrument connected by the systematic user interface control system 1102, for example. In the example, such an execution command may cause a manufacturing system to start manufacturing a part, an assay instrument to start performing an assay, or a design system to send a design specification.

[0047] In the embodiment, the execution menu can provide the user with a walkthrough or tutorial. For example, after designing a workflow or process, the execution menu may provide a walkthrough or tutorial that matches the workflow, and may provide text-based, audio-based, video-based, and image-based tutorial steps to explain each step of the designed workflow or process to the user.

[0048] In embodiments, the execution menu can provide a walkthrough and / or tutorial in conjunction with execution commands issued to instruments and machines in the material world. For example, in a modular laboratory system, such a combination may provide the user with instructions to load the machine (including, for example, assay plates and reagents), and then provide the machine with execution commands to start the process. If a new step in the process requires physical intervention by the user (such as moving an assay plate), the MUI may, at the execution level, provide the user with additional instructions (text-based, video-based, image-based, audio-based, etc.) to advance the process. In embodiments, user instructions and notifications implementing the user intervention portion of the process may be provided via various means of communication, including, for example, text (SMS, MMS), email, telephone, instant messaging, Slack messaging, and any other type of messaging protocol. Such various means of communication may be useful, for example, when part of the machine processing takes some time to complete and the user does not wish to remain at the process location during processing. Thus, if the user has started a process that takes several hours, they may receive a text message indicating that intervention is needed to advance the process.

[0049] In these types of "cobot" interactions, the MUI integrates both the material world actions of a human operator and the material world actions of an automated machine, and 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., boxing and picking, packaging, etc.). These automated machines may further include non-human machines such as robots, drones, robot-based machines, or other autonomous or semi-autonomous machines.

[0050] As used herein, “displaying” a menu includes displaying one or more items within the menu within the MUI. Displaying a menu does not require displaying all items or options within the menu. Regardless of whether each menu item is displayed, the one or more menu items that make up the first menu remain the same. Certain menu items may be excluded or restricted for various reasons, as will be considered in more detail below. As considered herein, a designated “first menu” or “second menu” may be rearranged to different parts of the screen. When rearranged, the first menu may continue to display the same set of first menu items, and / or a different set of first menu items.

[0051] As discussed herein, menus may also be referred to based on their temporal state. A “current menu” refers to the menu currently active in the active portion of the MUI, from which the user is prompted 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 “successor menu” refers to the next menu that becomes active after the current menu has become a past menu. For example, a first menu may be displayed as a current menu. After a selection is made from the first menu, the first menu may then be rearranged to become a past menu. Subsequently, a second menu selected from the first menu may be displayed as a current menu. Current menus may be displayed in the first or active portion of the user interface, and past menus may be displayed in the second or history portion of the user interface.

[0052] In the history section, each menu item from past menus can be displayed linearly in the MUI. All menu items at a menu level are displayed on a single line (horizontal or vertical). Each set of past menu items can be displayed linearly, while the entire menu can be displayed in a stacked or nested format. This feature is illustrated, for example, in Figure 2C, which shows linearly displayed MENU ITEMS and linearly displayed SUBMENU ITEMS. The relationship between MENU ITEMS and SUBMENU ITEMS is either a stacked or nested relationship. Thus, within a single menu level, menu items are adapted to be displayed linearly, while previously navigated menu levels and subsequent menu levels are adapted to be displayed in a nested format.

[0053] The selection menu may be displayed as a graphical wheel that rotates the selection horizontally or vertically (e.g., left-right, up-down) or in another direction. In another embodiment, the selection menu may be displayed as a graphical slider that slides the selection horizontally or vertically (e.g., left-right, up-down) or in another direction. For example, the initial menu level (first level) may be displayed horizontally and slide left and right, and the next menu level (second level) may be displayed vertically and rotate up and down. In yet another embodiment, the selection menu may be displayed as a series of concentric circles, with each menu level displayed as a circle having menu selections (also referred to as options or menu items). For example, the initial menu level (first level) may be displayed in the central circle, the next menu level (second level) may be displayed in the next circle (second circle) surrounding the central circle, and the next menu level (third level) may be displayed in yet another circle surrounding the second circle. Furthermore, the selection menu may be displayed or visualized as a graphical decision tree with nodes and edges. Each level of the graphical decision tree may represent a menu level with a selection.

[0054] In one embodiment, the wheel and / or slider does not need to rotate completely, for example, it does not need to make a full turn or rotation. For example, the wheel and / or slider rotates or slides from the start menu item to the end menu item and back from the end menu item to the start menu item. In this way, for example, the start and end of the menu are always displayed because they are never combined or merged together. This technique reduces processing time because the wheel and / or slider can communicate the entire menu of choices (and the user can understand it immediately) while clearly indicating which of the choices presented by the wheel and / or slider is the first menu item and which is the last menu item.

[0055] In further embodiments, the wheel and / or slider may rotate fully to allow the user to easily access the start of the menu after reviewing the entire menu. In such embodiments, a visual indicator may be provided to show that the menu has rotated fully and returned to the beginning.

[0056] In various embodiments, the terms “software protocol” and “computer instruction” 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 set of software instructions or code configured to cause one or more processors to perform one or more functional tasks. For convenience, various managers, computer instructions, and software protocols are actually described as performing various operations or tasks when managers, computer instructions, and software protocols program hardware processors to perform operations and tasks. While “manager,” “software protocol,” and “computer instruction” are described in various places as “software,” it is understood that they can also be implemented as firmware, software, hardware, or any combination thereof for instructing a computer or other electronic device to perform and / or execute a series of steps and / or instructions. Furthermore, embodiments herein are described in terms of method steps, functional steps, and other types of occurrences such as menu display, option selection, etc. Although not explicitly stated in all examples, it will be understood that these actions occur in accordance with computer instructions or software protocols executed by one or more computer processors.

[0057] The functions of the managers and software protocols considered herein may be provided by the issuance of one or more commands. As considered herein, “commands” issued by managers and software protocols refer to signals and instructions provided to various aspects of a computing system to produce various actions. Commands may be issued from one manager to another manager and / or to other components of the system. For example, a manager may provide a command that causes the display of a particular visual component within a menu interface. Such a command may be directed to a physical display screen and may include the signals and instructions necessary to produce the visual component. Where used herein, when it is stated that a manager performs an action or performs a particular function, it should be understood that the manager has issued a command that causes such action or function.

[0058] In various embodiments, the term “module” is used to refer to a particular set of software protocols and computer instructions that generate, maintain, and operate multiple components of the MUI described herein. One or more processors described herein may be configured to run multiple software protocols and provide systematic user interface modules. Where used herein, “systematic user interface module” refers to any subset of modules that provide a particular user interface. For example, the administration console module, the audit trail module, and the reader module are provided as specific systematic user interface modules for performing tasks related to system administration, auditing, and plate reading, respectively. Each MUI module may be understood to include a hierarchical menu tree containing at least several layered menus. Each module may further include preferred default visual components, preferred default exclusion and restriction lists, and other functions specific to the module. Other modules are considered in more detail below and throughout this disclosure. Throughout this disclosure, multiple embodiments of various MUI modules are considered. Any considered embodiment of any particular MUI module is non-exclusive and non-limiting and may similarly apply to any other MUI module. Therefore, any MUI feature considered herein can be broadly applied to MUI in general, or to any other specific MUI module considered herein, in a broad sense or with respect to a particular module.

[0059] Referring here to Figure 56, a systematic user interface control system 1102 consistent with the embodiments herein is shown. The systematic user interface control system 1102 includes one or more processors 1110 (for convenience, also referred to herein as multiple processors 1110, processor 1110, or processor 1110), one or more storage devices 1120, and / or other components. CPU 2 (see Figure 19) and hardware processor 1804 (see Figure 18) may be examples of processors 1110 configured as described herein. In other embodiments, the functions of the processors may be performed by hardware (e.g., through the use of application-specific integrated circuits ("ASICs"), programmable gate arrays ("PGAs"), field-programmable gate arrays ("FPGAs"), or any combination of hardware and software. The storage devices 1120 include any type (one or more) non-temporary computer-readable storage media and / or non-temporary computer-readable storage devices. Such computer-readable storage medium or device may store computer-readable program instructions for causing a processor to perform one or more of the techniques described herein. Memory 4 (see Figure 19) and memory device 1802 (see Figure 18) may be examples of storage device 1120. Examples of computer-readable storage medium or device include, but are not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any preferred 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), portable compact disk read-only memory (CD-ROM), digital multipurpose disk (DVD), and memory sticks. In embodiments, storage device 1120 may include a plurality of storage devices 1120. The plurality of storage devices 1120 consistent with the embodiments herein may be co-located and / or unco-located.For example, one physical system may include a first memory storage device 1120, and a second physical system may include a second memory storage device 1120.

[0060] In embodiments, the processor 1110 and the storage device 1120 may be implemented via a cloud computing platform or other form of distributed computing. In such implementations, the processor and the storage device may each include multiple processors and storage devices for performing the tasks and functions described herein.

[0061] The processor 1110 is programmed by one or more computer program instructions and / or software protocols, referred to as “managers,” which are 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 will be understood that the functions of the various managers considered herein are representative and not limiting. Furthermore, the functions of the various managers may be combined into one or more modules, applications, programs, services, tasks, scripts, libraries, applications, or executable code as needed.

[0062] The managers considered herein may be implemented in various embodiments to manage MUIs and complete various tasks requiring process workflows. Various software implementations of MUIs are described herein with respect to one or more specific embodiments, but the methods and functions provided by the aforementioned managers may be implemented to provide MUIs for any process workflow. The aforementioned managers may be functionally implemented through software libraries.

[0063] The various components of the systematic user interface control system 1102 work together to provide the user with a systematic user interface display via any type of display hardware, including screens, projections, touchscreens, headsets, etc. In embodiments, the systematic user interface control system 1102 implements one or more software protocols for interactively navigating the user through paths of menu items, options, or choices within the MUI. The software manager described above may include a set of computer instructions, software libraries, dynamic link libraries, application programming interfaces, function libraries, and other compilations of executable code. The systematic user interface control system 1102 may further include a suitable graphics library, which contains the graphics required for the implementation and instantiation of the various visual components described herein. The manager may be customized for use in a particular implementation form through the use of various data structures representing module information, including tables, linked lists, databases, b-trees, binary trees, heaps, stacks, queues, hash tables, red-black trees, binary heaps, Fibonacci heaps, and any other suitable data structures. Therefore, the MUI manager may be provided as a customizable code library configured to interface with, interact with, and integrate in different ways with additional computer instructions and data structures, for the purpose of providing MUI modules capable of performing specific tasks.

[0064] The display manager 1050 is a software protocol that operates on the systematic user interface control system 1102. The display manager 1050 is configured to manage the systematic user interface display, including all of its visual components. The display manager 1050 may be configured to issue commands that trigger the display of various menu items as needed.

[0065] The input manager 1052 is a software protocol operating on the systematic user interface control system 1102. The input manager 1052 is configured to manage all inputs received by the systematic user interface control system 1102, including but not limited to user inputs and inputs from other systems. The input manager 1052 may be configured to issue commands to other managers of the systematic user interface control system 1102 in accordance with the received inputs. User actions, such as clicks and other screen interactions, cause the input manager 1052 to receive a signal indicating a user interaction. Receiving such a signal causes the appropriate manager of the systematic user interface control system 1102 to provide a command in response, as considered herein, thereby triggering one or more actions, including MUI navigation, menu display, etc. For ease of explanation, such interactions and user inputs may be referred to as triggering a specific response when a specific response is actually triggered by the systematic user interface control system 1102 in response to the interaction or user input.

[0066] The menu manager 1054 is a software protocol operating on the systematic user interface control system 1102. The menu manager 1054 is configured to manage a hierarchical menu tree and all menu items associated with it. It is configured to select the appropriate menu item for display, determine the next menu to display, and otherwise manage all aspects of navigation through the menu tree. The menu manager 1054 may be configured to issue commands to other managers in the systematic user interface control system 1102 according to menu navigation requirements.

[0067] User Manager 1056 is a software protocol that operates on the Systematic User Interface Control System 1102. User Manager 1056 is configured to manage user access to the Systematic User Interface Control System 1102. User Manager 1506 manages user authentication, including, for example, maintaining user authentication records, verifying user credentials, and other necessary user authentication tasks.

[0068] The exclusion manager 1058 is a software protocol operating on the systematic user interface control system 1102. The exclusion manager 1058 is configured to manage the exclusion and restriction of menu items. As considered herein, menu items may be excluded or restricted based on various factors. The exclusion manager 1058 can be configured to issue commands to implement such exclusions and restrictions.

[0069] The network manager 1060 is a software protocol operating on the systematic user interface control system 1102. The network manager 1060 is configured to establish, maintain, and manage all network communications between the systematic user interface control system 1102 and various other system components considered herein. Established communication paths can utilize any suitable network transport protocol and provide one-way or two-way data transfer. The network manager 1060 may establish as many network communications as necessary to communicate with all system components.

[0070] The data storage manager 1064 is a software protocol operating on the systematic 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 systematic user interface control system 1102 may interface with. The data storage manager 1064 is configured to issue commands to any of the various data storage devices considered herein in order to manage the storage and retrieval of data.

[0071] The above descriptions of the display manager 1050, input manager 1052, menu manager 1054, user manager 1056, exclusion manager 1058, network manager 1060, and data storage manager 1064 provide an overview of the capabilities and tasks of these managers. The managers are not limited by the above descriptions and may have additional, different, and / or more capabilities in various embodiments, such as those considered below. The described structure of the systematic user interface control system 1102 is for illustrative purposes only, and it should be understood that various functions and capabilities of the computer instruction program processor described herein may be implemented, performed, or enabled by software systems of alternative structures.

[0072] The systematic user interface control system 1102 can present menu options between one or more hierarchical menu levels, each menu level may contain one or more menu items or options. The hierarchical menu levels described herein refer to multiple levels within a menu system. A selection at the first, highest-level menu level triggers navigation to a lower hierarchical level, i.e., a second menu, submenu, or sublevel. A selection within the second menu or submenu triggers navigation to an even lower hierarchical level, i.e., a third menu, sub-submenu, or sub-sublevel. The hierarchical menu structure may include any preferred number of levels. In some embodiments, a selection at a certain level may trigger navigation to levels 1, 2, 3 or higher, below the current level.

[0073] Each menu may present options in the active portion of the interface. Menu options may be selectable and represent options that the user chooses. The selection of a menu option or option may trigger the display or presentation of subsequent submenus, which may include several menu options or their own submenu options. When the user selects a menu option that leads to a new menu, the menu items of the old menu may be moved from the active portion to the history portion of the interface. This allows the user to easily move to new menu options while retaining knowledge of previous menu options. These features are described in more detail below with respect to Figures 2A-2O, Figure 3, and Figure 57.

[0074] Figure 57 is a flowchart of process 5200 navigating a hierarchical menu-level path adapted to output to a user interface such as a GUI, MUI, and / or any other type of UI considered herein. Process 5200 runs on a computer system having one or more physical processors programmed with computer program instructions, which, when executed by one or more physical processors, cause the computer system to perform the method. One or more physical processors are hereafter simply referred to as processors. In embodiments, process 5200 is carried out via a systematic user interface control system 1102, as described herein. Systematic user interface control system 1102 represents an example of a combination of hardware and software configured to carry out process 5200. However, the implementation of process 5200 is not limited to the combination of hardware and software of systematic user interface control system 1102. Process 5200 may also be carried out and / or implemented by any other suitable computer system considered herein. The description of process 5200 is not limiting, and various operations may be modified or corrected according to the embodiments described herein.

[0075] In operation 5202, process 5200 includes providing a first display command. Display manager 1050 provides a first display command for displaying a first menu having one or more user-selectable items in a first part of the UI display. The first menu may be displayed in the first part according to the visual components disclosed herein, for example, a wheel-type visual component. The selectable items of the first menu may be determined by menu manager 1054, for example, as considered herein.

[0076] In operation 5204, process 5200 includes receiving a selection. Input manager 1052 receives a selection of a menu item from a first menu according to input provided to the system. The input may be a user selection and / or an automatic selection as considered herein. A user selection may be received, for example, from a user who clicks on a highlighted or emphasized menu item. Upon selection, the menu item may become a previously selected menu item.

[0077] In operation 5206, process 5200 includes providing a relocation command. Menu manager 1054 provides a relocation command for a first menu to be relocated from a first part of the UI display to a second part of the UI display. The relocation command may be provided in response to a selection received. During relocation, the menu items of the first menu include one or more previously selected menu items and menu items that have not been previously selected, which were not selected to trigger the relocation. The display of the first menu in the second part may be provided according to any of the visual components disclosed herein, for example, a slider-type visual component. The relocation command of menu manager 1054 may be sufficient to trigger an update to the UI display. In another embodiment, the relocation command may be combined with and / or include a display command provided by display manager 1050.

[0078] In operation 5208, process 5200 includes providing a second display command. The second display command is provided by the display manager 1050 in response to a menu selection. The second display command causes a second menu of one or more user-selectable items to be displayed in the first part of the UI display (i.e., displayed after the first menu has been rearranged). The second menu may be displayed according to the visual components disclosed herein, for example, a wheel-shaped visual component. In embodiments, the second display command may incorporate information received from the menu manager 1054 regarding hierarchical menu tree navigation. After the rearrangement of the first menu and the display of the second menu, the first menu, which includes one or more previously selected and unselected menu items of the hierarchical menu tree, may be viewed in the second part simultaneously with the second menu being viewed in the first part.

[0079] Process 5200 may further include additional or different operational steps, as described throughout this disclosure.

[0080] Referring to Figure 1, in operation 102, the ongoing selection menu (e.g., a list of menu items) may be displayed in the first part of the user interface display. In operation 104, the user interface allows the user to drill down levels of menu options based on selecting a menu item from the ongoing selection menu displayed in the first part of the user interface display and selecting a menu item from a previous level of menu options. In operation 106, previously selected and previously unselected menu items at the drilled-down level are displayed in the second part of the user interface display. Previously unselected menu items are displayed as selectable options. Previously selected menu items (or options) may also be displayed as selectable options. In operation 108, the user interface allows the user to jump to different paths of menu options by enabling the user to select previously unselected menu items from previously navigated menu levels displayed in the second part of the user interface display. The user interface displays both the first and second parts so that they are viewable on the same screen of the user interface, for example, so that they are viewable simultaneously.

[0081] In one embodiment, the first and second parts are shifted to the substantial center of the first part, which displays the selection menu in progress on the user interface display, while both the first and second parts are adapted to the user interface display. Therefore, for example, the first and second parts do not need to remain in a fixed position on the user interface display during navigation or drill-down (or drill-up) through different levels of menu selections.

[0082] In one embodiment, in response to the detection of a selection of a menu item from the ongoing selection menu, the user interface display rearranges the ongoing selection menu in a second part of the user interface display and displays the next level of menu options in the first part of the user interface display based on the selected menu item. The rearranged ongoing selection menu is shown in the second part of the user interface display and consists of previously selected and previously unselected menu items from the past menu level. The next level of menu options is shown in the first part as the ongoing selection menu.

[0083] As described above, the selection menu may be displayed as a rotatable graphical wheel that shows menu items (selections or options) that can be displayed on the wheel as the wheel is rotated. A similar graphical slider exists that can display menu items on the slider when the slider is slid. The rotation or sliding action may be performed in response to finger movements on a touchscreen or input from a pointing device or another input device. In another embodiment, the rotation or sliding action may be performed automatically and in a timely manner by the user interface (or the hardware running the user interface). In one embodiment, when the selection menu is rearranged from a first part to a second part, the rotation or sliding direction may switch to a different orientation.

[0084] The currently selected menu may be displayed in a first visual orientation on a first portion of the user interface display, and the drill-down levels of menu selections, including previously selected and previously unselected menu items, may be displayed in a second visual orientation on a second portion of the user interface display.

[0085] In one embodiment, the ongoing selection menu is displayed as a graphical rotating wheel or a slider that rotates or slides the selections in the direction of a first visual orientation. In one embodiment, the drill-down levels in the menu selections are displayed as a graphical rotating wheel or slider that rotates or slides the drill-down level selections in the direction of a second visual orientation.

[0086] In one embodiment, the second visual orientation is substantially perpendicular to the first visual orientation. In one embodiment, the first visual orientation is vertical orientation and the second visual orientation is horizontal orientation. In another embodiment, the first visual orientation is horizontal orientation and the second visual orientation is vertical orientation.

[0087] In one embodiment, the drilled-down levels of menu options rearranged in the second section are displayed as a stack of menu levels.

[0088] In another embodiment, the first and second parts may be represented as a series of concentric circles. For example, the first part may be represented as the central circle of the series of concentric circles, and past menu levels may be represented as circles outside or around the central circle. Each circle representing a menu level may include a rotatable menu item (choice or option) so that, for example, the user can view all options present on that menu level. When a menu item is selected from the ongoing choice menu, the ongoing choice menu is rearranged in the outer circle, and the central circle displays the next choice menu based on the selected menu item. For example, a circle (e.g., a dial) may contain a window showing the active option, and turning the circle (e.g., the dial) displays other options in the window. Although the dial options appear finite, there may be an infinite number of dial options. For example, the dial continues to rotate until the last option (or the starting option if rotating backward) is displayed.

[0089] In another embodiment, the window may open and display the selected option as a light-up, with one or more options on the left and another one or more options on the right.

[0090] In another embodiment, the first and second parts may be represented as a graphical decision tree.

[0091] In one embodiment, previously selected menu items at the drill-down level displayed in the second part of the user interface display are highlighted compared to previously unselected menu items at the drill-down level displayed in the second part of the user interface display.

[0092] In one embodiment, when the user reaches the last level in a selected path within a menu level, and when, for example, a function related to a selected item within the last menu level is executed, the user interface can return the ongoing menu view to another item in a higher level, such as a first menu list. For example, the ongoing choice menu may again become the first initial menu level, or it may be displayed in the first part. In one embodiment, the first and second parts are not independent but linked to each other, making navigation more efficient, guiding the user along a path, allowing the user to see the path they are on, allowing deviations from the path set for the user to become another path, for example, allowing the user to see previous and subsequent breadcrumbs, knowing where the user has been, and knowing where the user can go within the path of menu choices. In one embodiment, the user interface can guide the user through efficient path choices so that the user does not have to wander around the user interface trying to find the next appropriate path or action. Such efficient path guidance can save, for example, computer resources during central processing unit (CPU) cycles, and the amount of memory usage spent on swapping and switching processor threads and memory elements within the computer that launch the user interface.

[0093] Referring now to Figures 18-19, additional exemplary systems for implementing the method described with respect to Figure 1 are provided. As discussed above, the systems presented in Figures 18 and 19 may be embodiments and / or implementations of the systematic user interface control system 1102 shown in Figure 56.

[0094] Figure 18 shows the components of a graphical user interface (GUI) system in one embodiment. One or more hardware processors 1804 may execute a graphical user interface module or execute the graphical user interface functions described above, thereby displaying the graphical elements described above on a user interface display device 1806 coupled to one or more hardware processors 1804. A memory device 1802 may store a list of menus and a list of menu items or a list of available choices for each menu, and the graphical user interface module may access a display on the display device 1806. The display device 1806 may include a screen device and / or a touchscreen device. One or more pointing devices 1808 may be coupled to one or more hardware processors 1804 to enable input via the display device 1806.

[0095] The memory device 1802 may be any type of computer-readable storage medium, as described herein.

[0096] Figure 18 specifically shows a GUI system, but this is for illustrative purposes only. It should be understood that the methods and techniques described herein may also be implemented via other MUIs, such as text-based, virtual reality-based, augmented reality-based, and mixed reality-based systems.

[0097] For example, a hardware processor 1804 coupled to a memory device 1802 and a display device 1806 may display a selection menu in progress in a first part of the user interface display, and allow the user to drill down levels of menu selections based on selecting a menu item from the selection menu in progress displayed in the first part of the user interface display and selecting a menu item from a previous level of menu selections. The hardware processor 1804 may also be further operable to display previously selected and previously unselected menu items at the drill-down level in a second part of the user interface display, where previously unselected menu items may be displayed as selectable options. The hardware processor 1804 may also allow the user to jump to different paths of menu selections by allowing the user to select previously unselected menu items from a previously navigated menu level displayed in the second part of the user interface display.

[0098] For example, the hardware processor 1804 may perform the method described with respect to Figures 1 and 3.

[0099] The GUI technologies described above may be implemented using computer languages ​​such as Java and JavaScript, but are not limited to these languages. In one embodiment, the functions and modules of the systems and methods of the disclosure may be implemented or executed in a distributed manner on different processing systems or on any single platform, for example, by accessing locally stored data or in a distributed manner over a computer network. Similarly, the software protocols and managers of the disclosure may be implemented or executed in a distributed manner on different processing systems or on any single platform, by accessing locally stored data or in a distributed manner over a computer network.

[0100] GUI technology may be implemented on any type of computing device, e.g., desktop computers, laptop computers, mobile devices (e.g., Android or Apple iOS), tablets, and may use any type of interface, e.g., a mouse, a touchscreen, etc. GUI technology may also be implemented on an instrument, e.g., an assay instrument for performing biological assays such as immunological assays or nucleic acid assays. In some embodiments, the instrument performs an electrochemiluminescence assay. In some embodiments, the instrument is an automated assay system that includes, for example, (a) a single robot-controlled 8-channel pipette, (b) a single robot-controlled assay plate gripper arm, (c) a single 96-channel channel assay plate washer, (d) a single plate reader, (e) one or more plate shakers having a total capacity of at least five plate shake positions, and (f) a processor adapted to perform an assay process for analyzing multiple samples in a 96-well plate. Other computing devices, machines, systems, and instruments include individual instruments, such as wearable devices, automotive computing systems, assay-related instruments, such as plate washers, plate readers, plate shakers, incubators, and loading carts (for example, described in International Patent Application Publications 2018 / 017156 and 2017 / 015636, the entirety of which is incorporated herein by reference), medical instruments and machines such as MRI and CT machines, ultrasound systems, consumer products such as home appliances, home management systems, air conditioning and heating systems, washing machines and dryers, dishwashers, ovens, slow cookers, and other cooking devices, as well as home systems.

[0101] Various embodiments may be programs, software, or computer instructions embodied or stored on a computer or machine-readable, readable, or executable medium that causes a computer or machine to perform steps of the method when executed on a computer, processor, and / or machine. For example, a machine-readable program storage device may be provided that tangibly embodies a program of machine-executable instructions for performing the various functions and methods described herein.

[0102] The systems and methods of this disclosure may be implemented and invoked on a general-purpose computer or a special-purpose computer system (or device). The computer system may be any type of known or recognized system and may include a hardware processor, memory devices, storage devices, input / output devices, internal buses, and / or communication hardware and software, as well as a communication interface for communicating with other computer systems. The GUI technology of this disclosure may also be implemented on a mobile device or the like. Implementing the various computer instructions, software protocols, and modules described herein on a general-purpose computer may serve to transform the general-purpose computer into a special-purpose computer system configured to perform the specific methods, tasks, operations, and actions described herein.

[0103] Figure 19 shows an exemplary computer system 100 that may implement the system and / or method of the present disclosure. One or more central processing units (e.g., CPUs) 2 may include one or more arithmetic / logic units (ALUs), high-speed cache memory, and registers and / or register files. Registers are small storage devices, and register files may be sets of multiple registers. The cache is a high-speed storage memory device, for example, including a static random access (SRAM) chip. The cache functions as a temporary staging area for holding data used by the CPU 2. A simplified hardware configuration is shown. The CPU 2 may include other combinational circuits and storage devices.

[0104] One or more central processing units (CPUs) 2 execute instructions stored in memory 4, which are transferred to the registers of the CPUs 2, for example. Bus 6 is, for example, electrical wiring that carries bits of data between components. Memory 4 may include an array of dynamic random access memory (DRAM) chips and may store programs and data used by the CPUs 2 for execution. System components may also include input / output (I / O) controllers and adapters connected to the CPUs 2 and memory 4 via buses, such as I / O buses, and connected to I / O devices. For example, a display / graphical adapter 8 connects to a monitor 28 or another display device / terminal; a disk controller 10 connects to a hard disk 24 for permanent storage, for example; a serial controller 12, such as a Universal Serial Bus (USB) controller, may connect to input devices such as a keyboard 22 and a mouse 20, and output devices such as a printer 26; and a network adapter 14 may connect the system to another network, such as another machine. The system may also include expansion slots for accommodating other devices to connect to the system. For example, the hard disk 24 may store a program of instructions and data that implements the above-described methods and systems, where these methods and systems may be loaded into memory 4 and then into the CPU's storage (e.g., cache and registers) for execution by the CPU (e.g., ALU and / or other combinational circuits or logic). In another embodiment, all or part of the program of instructions and data that implements the above-described methods and systems may be accessed and / or executed by another computer system or device via network 18. Figure 19 is merely an example of a computer system. Computer systems that can implement the methods or systems of the Disclosure are not limited to the configuration shown in Figure 19. Rather, other computer systems may implement the methods of the Disclosure, including, but not limited to, special processors such as field-programmable gate arrays (FPGAs) and accelerators.

[0105] In one embodiment, the present invention may be embodied as a computer program product which may include (one or more) computer-readable storage media and / or computer-readable storage devices. Such computer-readable storage media or devices may store computer-readable program instructions for a processor to perform one or more of the techniques described herein. In one embodiment, the computer-readable storage media or devices include tangible devices capable of holding and storing instructions for use by an instruction execution device. Examples of computer-readable storage media or devices are, 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), portable compact disk read-only memory (CD-ROM), digital multipurpose disks (DVDs), and memory sticks. The computer-readable media may include both computer-readable storage media and computer-readable transmission media (as described above), such as coaxial cables, copper wires, and optical fibers. Computer-readable transmission media may also take the form of sound waves or light waves, such as those generated in other media including radio frequencies, infrared radiation, radio waves, magnetic waves, or electromagnetic waves.

[0106] The term “computer system” as used in this application may include various combinations of fixed computer hardware and / or portable computer hardware, software, peripherals, mobile devices, and storage devices. A computer system may include multiple individual components that are networked or linked to perform collaborative actions in other ways, or it may include one or more standalone components. The hardware and software components of a computer system in this application may include, or be contained within, fixed and portable devices such as desktops, laptops, and / or servers. A module may be a device, software, program, or system component that implements some “functions,” and “functions” may be embodied as software, hardware, firmware, electronic circuits, etc.

[0107] The memory 4 and the memory device 1802 exemplify the storage device 1120, which may be implemented as one or more computer-readable storage media as described herein and may be used to store various data and information relating to the computer system 100.

[0108] In one embodiment, the storage device 1120 may store registration information, such as a user identifier and a user account number. The registration information may also be stored via data storage commands issued 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, binary heaps, Fibonacci heaps, etc. In one example, the registration information may be stored in a registration table. The registration information includes at least a user identifier and an account number associated with a user. Since multiple users may be assigned to the same account number, the system may track this using a shared account flag, such as a semaphore or a bit. If multiple users are assigned to the same account number, the shared account flag may be set to a first specific value. Otherwise, the shared account flag may be set to another specific value. Using a shared account flag is one way of tracking shared accounts, and this disclosure is not limited to this example. Other methods may be used. The shared account flag may be a column in the registration table. For each user identifier with the same account number, the shared account flag is set to a specific value and associated with the user identifier.

[0109] In other embodiments, multiple account numbers may be linked together. In embodiments, user manager 1056 may issue commands for managing user account numbers. In one embodiment thereof, multiple account numbers may represent teams such as research teams, project teams, corporate teams, university teams, or experimental teams. The system can track multiple account numbers and teams using multiple account flags. When different account numbers are linked, multiple account flags may be set to a first specific value, or alternatively, multiple account flags may be set to different specific values. Using multiple account flags is one way of tracking links between different account numbers, and this disclosure is not limited to this example. Other methods may be used. In one embodiment, multiple account flags may be columns in a registration table. For each linked account number, multiple account flags are set to a specific value and associated with the account number.

[0110] In other embodiments, the storage device 1120 may also store login history data. Login history data may be received via the input manager 1052, organized via the user manager 1056, or stored via the data storage manager 1064. The login history data may include user identifier / account number and time / date information each time a user (or a different user) logs 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 that is running or scheduled to run.

[0111] In other embodiments, the storage device 1120 may also store user selection history. The user selection history may be received via the input manager 1052, compiled via the user manager 1056, or stored via the data storage manager 1064. The user selection history may include the selected menu item, the user identifier / user account associated with the selection, and the time / date of the selection. The user selection history may also be stored in the storage device 1120 for a predetermined or unspecified period. The predetermined period may be selected according to the MUI module in which the user selection was first made. The predetermined periods for stored user selection history and login history data may be the same.

[0112] In other embodiments, the storage device 1120 may include exclusion information. The exclusion information may include menu items and / or selections that are excluded from the display at the hierarchical menu level on the MUI for one or more users, devices, or interfaces. The exclusion information may be managed by commands issued via the exclusion manager 1058 or stored by commands issued via the data storage manager 1064.

[0113] Commands issued or provided by the menu manager 1054 of the systematic user interface control system 1102 allow the user to move bidirectionally (backward and forward) between hierarchical menu levels, including the ability to view past or previous menu items that are selected or not selected, with backward movement enabling movement to higher hierarchical menu levels and forward movement enabling movement to lower hierarchical menu levels. For example, various menu levels and / or choices from one or more levels of a given path in a hierarchical menu can be viewed simultaneously on the MUI.

[0114] In one embodiment, a display command may be provided by the display manager 1050 for a specific set of hierarchical menu levels to be displayed in a particular part of the MUI. The display command is configured to display one or more menus in one or more parts of the MUI. A particular hierarchical menu level may include one or more menu items (or choices). The display command may include one or more menu items such as a scroll method, a specific display order, display orientation, display size (and format), and a display style for the choices, but other styles of arranging and / or displaying the choices are also contemplated. In one embodiment, the scroll method may define the display orientation. Thus, the display command does not necessarily include separate display orientations and scroll methods.

[0115] In one embodiment, each menu item at a particular hierarchical menu level may be displayed at the same size. In other embodiments, one or more particular menu items may be displayed larger or smaller than the others.

[0116] The display command allows you to specify the scrolling method. For example, the display command may specify that menu items are displayed on a graphical wheel that rotates the items horizontally or vertically (e.g., left-right or up-down) or in another direction. In another embodiment, the display command may specify that menu items are displayed as a graphical slider that slides the items horizontally or vertically (e.g., left-right or up-down) or in another direction.

[0117] Different display commands may be specified with different scrolling methods or orientations, or different commands may use the same or similar scrolling methods or orientations. In one embodiment, the orientations of different commands (such as a first command and a second command) may specify that the orientations are substantially orthogonal to each other. In other embodiments, the orientations may be horizontal to each other, substantially horizontal, vertical, substantially vertical, concentric, and substantially concentric opposite each other. As used herein, this may be substantially +5° or -5°. In other embodiments, this may be substantially +10° or -10°. In other embodiments, this may be substantially +15° or -15°. In other embodiments, this may be substantially determined by a percentage such as 80% or 90%.

[0118] Figures 2A to 2O show examples of user interface displays in different embodiments, which are further described below.

[0119] Figure 3 is a flowchart detailing, in another embodiment, a method for interactively displaying interactive items on a user interface display for computer user interaction, for example, a method in which vertical and horizontal switching of menu levels may be performed. The method may be performed automatically by at least one hardware processor. In operation 302, a list of menu items may be displayed on a first part of the user interface display. The list of menu items is displayed on the first part in a first visual orientation. For example, the first visual orientation may be vertical orientation. The list of menu items may include 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.

[0120] Figure 2A shows an example of a user interface display in one embodiment. As shown, menu item 202 is displayed in a single orientation, for example, vertically, in the first portion 204 of display 206. The menu item is interactive in that, for example, the item is selectable, and selection (for example, the user clicks on a user interface menu item to select it) causes the computer to perform a programmed function.

[0121] As shown in Figure 2A, the menu item 202 of the first menu is provided in the orientation of the first part 204 of the interface with the wheel oriented vertically, i.e., the first orientation. The MUI includes a display 206. The first part 204 may display the menu item 202 in response to a first display command of the first menu of user-selectable choices displayed on the first part 204 of the MUI. As discussed above, the first display command may be provided by the display manager 1050.

[0122] The first display command includes menu items of the first menu (in one embodiment, the scroll method / orientation and size (and format) stored in the storage device 1120). For example, the orientation of the menu items of the first menu (displayed in the first portion) may be vertical. The first display command may also include the display position, for example, the position of the first portion. The first portion may be in the center position on the MUI. Each menu item may be selectable by the user.

[0123] In one embodiment, the first part may include a decision zone. The decision zone may be located in the center of the first part. The decision zone may be located within the first part or within the active part, where a prominent or highlighted menu item is displayed for immediate selection. For example, in Figure 2A, MENU ITEM 4 is shown in the decision zone and is displayed in a larger font than the remaining menu items so that it is a prominent or highlighted menu item displayed for immediate selection. A first display command to trigger the provision of the first menu may specify that the menu items displayed in the decision zone should be highlighted or emphasized, for example, in a larger font than other menu items not in the decision zone. In other embodiments, the menu items displayed in the decision zone may be bolded, italicized, highlighted using a different color from the background, or underlined.

[0124] In other embodiments, the first display command may specify, for example, that menu items displayed outside the decision zone should not stand out from other menu items within the decision zone, such as by displaying them in a reduced or faded font.

[0125] A first display command is executed by the hardware processor to display a first menu in the first part of the MUI. The MUI allows the user to select one or more menu items from the displayed menu items on the first part 204 and drill down the hierarchical menu levels of the menu items based on the selection of menu items from the hierarchical menu levels before and / or after the menu item. When a menu item is selected from the first menu displayed in the first part 204 of the MUI, the input manager 1052 receives and interprets the selection.

[0126] As shown in Figure 2A, all first menu items 202 displayed in the first section 204 are selectable. MENU ITEM 4 is displayed as a prominent menu item and is highlighted as immediately selectable. As used herein, “immediately selectable” means that a single action by the user, such as a click, triggers the selection of the menu item. MENU ITEM 4 is selectable and highlighted as a prominent menu item, while the other MENU ITEMS (1, 2, 3, 5, and N) are not highlighted as back menu items. Back menu items are not immediately selectable; that is, two or more user actions are required for selection. When the user clicks a highlighted immediately selectable menu item, it is selected. Other menu items may be highlighted for immediate selection by rotating the wheel or clicking. When the input manager 1052 receives a signal indicating a click on an immediately selectable menu item, the input manager 1052, running on the processor 1110, detects the selection of the prominent immediately selectable menu item. Depending on the selection, the input manager 1052 issues a command to the menu manager 1054 indicating the selection. The menu manager 1054 then determines the new menu layout to be displayed according to the selection and provides a rearrangement command to the display manager 1050 to trigger a change in the MUI.

[0127] Returning to Figure 3, in operation 304, in response to the detection of a selection of a menu item from the list of menu items, the list of menu items is rearranged in a second part of the user interface display. The list of menu items is displayed in a second visual orientation on the second part, which is substantially orthogonal (e.g., perpendicular) to the first visual orientation. For example, the second visual orientation may be horizontal.

[0128] The reposition command repositions the first menu of menu options 202 from the first part 204 to the second part 208 of the MUI display 206. Figure 2B shows the result of the reposition command. The reposition command may include the menu options of the first menu displayed in the second part 208, the size and orientation of the display, the visual components required for the display, instructions regarding which menu items were selected to trigger the reposition, and any other information considered herein with respect to display commands. The repositioned first menu, displayed in the history part or the second part 208 as a past menu, may include one or more or all of the menu items 202 and options that were previously available to the user. Menu items 202 selected by the user to be repositioned become previously selected menu items, and menu items not selected from menu items 202 become previously unselected menu items. Previously unselected menu items represent previously navigated hierarchical menu levels. After rearranging the menu item 202 of the first menu, the display manager 1050 causes the MUI to display the submenu item 210 of the second menu in the active portion or first portion 204 as a new current or subsequent level menu option for the user to interact with in response to the first menu selection. As shown in Figure 2B, the subsequent level or second level menu option includes the second submenu item 210 displayed in the active portion or first portion 204 of the MUI display 206.

[0129] In one embodiment, when the input manager 1052 receives a signal indicating that menu item 202 has been selected from the first portion 204, a relocation command is issued. For example, the menu manager 1054 provides the relocation command to the display manager 1050. The relocation command instructs the display manager 1050 to move the first menu in the second menu from the first portion 204 of the MUI display 206 to the second portion 208 of the MUI display 206. The second portion 208 is in a different position on the MUI display 206 than the first portion 204. Because the menu item of menu item 202 has been selected from the first menu, the relocated first menu of menu item 202 now has both previously selected menu items and previously unselected menu items (e.g., one or more menu items that the user could have selected but did not). The relocation command may include the first menu item, the scrolling method and / or orientation, the display size (and format), and the position of the second portion.

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

[0131] In one embodiment, the orientation for displaying menu item 202 in the first menu within the second portion 208 is different from the orientation for displaying submenu item 210 in the second menu within 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. A rearrange command may specify that the orientation of menu item 202 is horizontal (the first display command may specify that the orientation of menu item 202 is 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 bottom center of the MUI display 206, and the second portion 208 is located at the top of the MUI display 206.

[0132] The rearrange command may also specify different sizes for menu items. For example, a menu item selected from the first menu (which triggered the rearrangement) may be highlighted, such as by being displayed in a larger font size than the unselected menu items. In other embodiments, the selected menu item may be highlighted by being bolded, italicized, or using a different color from the background, or by being underlined. In yet another embodiment, the rearrange command may also specify the relative position of the menu item 202 within the second section 208. For example, the selected menu item may be positioned centrally within the second section relative to the other menu items (the unselected menu items).

[0133] In other embodiments, menu items not selected from a hierarchical menu level may be displayed in an inconspicuous manner. For example, a rearrangement command may specify that unselected menu items be displayed in a smaller font size or in a lighter font than selected menu items. In other embodiments, a rearrangement command may specify that unselected menu items be displayed further away from the center of the second section than selected menu items for the same hierarchical menu level.

[0134] The first and second parts may be displayed on the user interface display in such a way that they do not overlap. Menu items repositioned in the second part may be selectable from their position or location, and selected menu items may be graphically highlighted, for example, to provide a visual indication of which item has been selected from the list. Selected menu items may be centered relative to other menu items to their left and / or right. Submenu items displayed in the location where the repositioned menu item was displayed (before repositioning) are also selectable items. Figure 2B shows an example of a user interface display in one embodiment having a repositioned list of menu items. As shown, menu item 202 is repositioned, for example, in the second part 208 of display 206 above the first part 204 and displayed horizontally. As will be described in more detail below, the second part of the display may also include multiple levels of the menu item, for example, levels of past decisions and options of those levels that were not selected. Therefore, the number of levels of past decisions may 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, for example, 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 within them, for example, 2-20, 2-19, 2-18, 3-20, 3-19, 3-18, etc. The second part visualizes, for example, the representation of paths of past decisions made and other decisions not made (other paths). In one embodiment, past decisions made (selected menu items) may be aligned vertically, for example, or centered.

[0135] The second portion 208 can display a first menu item 202 in response to a relocation command for a first menu of user-selectable options displayed on the second portion 208 of the MUI display 206. As discussed above, the relocation command may be provided to the display manager 1050 by the menu manager 1054. The first menu of user-selectable options may include both previously selected menu items and menu items that have not been previously selected. The first menu may include one or more of the first menu items 202 that are selectable by the user. The menu items 202 may be immediately selectable or not immediately selectable.

[0136] The second part 208 may also include one or more decision zones. The rearrange command may also specify that menu items displayed within a decision zone should be highlighted or emphasized. In other embodiments, menu items displayed within a decision zone may be highlighted in bold, italics, or a different color from the background, or underlined. In other embodiments, the rearrange command may specify the same. In other embodiments, the rearrange command may specify that menu items displayed outside a decision zone should be made less conspicuous or unhighlighted.

[0137] The MUI display 206 is displayed so that both the first part 204 and the second part 208 are viewable, for example, so that they are viewable simultaneously. The MUI display 206 may be presented via one or more physical display screens. The second part 208 may contain one or more menus, each menu containing both previously selected and previously unselected menu items from a previously navigated hierarchical menu. In the representation shown in Figure 2C, the second part 208 (history part) contains menu item 202 and submenu item 210, each of which was included in the first part 204 in a previous MUI representation. Previously selected menu item 202 and submenu item 210 (i.e., menu items for which a sub-submenu item 212 now appears in the first part) may be highlighted or emphasized to indicate that they were previously selected. As shown in Figure 2C, MENU ITEM 4 and SUBMENU ITEM 3 are highlighted to indicate that they were previously selected.

[0138] Menu and submenu items that have not been previously selected are displayed as selectable options. Menu items (or options) that have been previously selected may also be displayed as selectable options, both of which are displayed on the second part 208 (e.g., the history part, which may contain one or more menu items that were previously available to the user). The history part is in contrast to the active part, which may contain ongoing user-selectable options at the ongoing hierarchical menu level (e.g., located in the first part of the display). The history part may also allow the user to make selections, for example, by selecting between previously selected hierarchical levels and / or menus. In this way, the second part 208 of the history may represent a "breadcrumb trail" showing the user the ordered path of selections made to arrive at the ongoing menu, as displayed in the active first part 204. Further details of the selections made in the second part 208 are provided below.

[0139] In some embodiments, the first portion 204 may be adapted to occupy a larger portion of the MUI's display area than the second portion 208. The second portion 208 may be displayed over a smaller area than the first portion 204. The first portion 204 and the second portion 208 may be adapted in a manner that provides contrast to the background on which they are displayed. For example, the first portion 204 and the second portion 208 may be displayed with light-colored pixels against a dark background, or with dark-colored pixels against a light background.

[0140] In other embodiments, commands (e.g., relocation commands) may be provided by the menu manager 1054 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 items 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 issuing a plurality of commands, for example, one command to clear the menu from the first part 204 of the display, and another command to display the menu on the second part 208 of the display (either in the same format and / or orientation, or in a different format and / or orientation). This relocation may be performed, for example, in response to a user selection from a menu (e.g., a first menu).

[0141] Referring back to Figure 3, in operation 306, in the first part of the user interface display, where the list of menu items was previously displayed before being rearranged to the second part, the first list of submenu items associated with the selected menu item is displayed in the first visual orientation. As shown in Figure 2B, the first list of submenu items 210 is displayed, for example, vertically in the first part 204.

[0142] Referring back to Figure 3, in operation 308, upon detection of a selection of a submenu item from the first list of submenu items, the first list of submenu items is rearranged into a second section, where the first list of submenu items is displayed in a second visual orientation and stacked on top of the list of menu items displayed in the second section. In operation 310, in the first section of the user interface display, the second list of submenu items associated with the selected submenu item is displayed in the first visual orientation, for example, vertically. Figure 2C shows an example of a user interface display having a second list of submenu items in one embodiment. As shown, the first list of submenu items 210 is rearranged into the second section 208, for example, stacked horizontally below the rearranged list of menu items 202. The first section 204 displays the second list of sub-submenu items 212, i.e., the submenu items associated with the selected submenu item. Depending on the depth of the navigated menu or submenu, the horizontal menu structure within the second section 208 may accumulate a number of menu levels that exceeds the number that can be displayed together in the display portion of the second section 208 (for example, the number of stacked levels exceeds the screen portion allocated to 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 levels (e.g., the last three submenus) to enable scrolling functionality. For example, by scrolling up, the user can see other menu items. The number n may be any number, such as 3 (e.g., 2, 3, 4, 5, etc.). In another embodiment, the top m items (e.g., 2) of menus may be displayed together with one submenu at the bottom to provide top-level context for the final decision. The number m may be any number, such as 3 (e.g., 2, 3, 4, 5, etc.). The scrolling functionality makes it possible to display other menu items, for example, the user can scroll to view other menu items.The user may also extend the entire multi-level menu and submenu.

[0143] As shown in Figure 2C, a subsequent level menu option, such as a sub-submenu item 212, may be at least one hierarchical menu level (from a third menu) or two or more hierarchical menu levels (from menus such as a fourth, fifth, sixth, etc.) below the first menu of menu item 202. In the example in Figure 2C, the sub-submenu item 212 represents a third menu, which is two hierarchical levels below the first menu of menu item 202.

[0144] When a menu item is selected, the level of the menu item may continue to rise or fall, for example, by a process of rearranging the menu item from one part of the user interface display to another. For example, the processing in operations 308 and 310 in Figure 3 may be repeated for additional levels of submenus. In another embodiment, selecting a menu item from a rearranged list of menu items may function as a "back" button without the user having to explicitly click a back button to return to the previous list of menu items. In yet another embodiment, if the number of rearranged lists of stacked menu / submenu items reaches a predetermined number or threshold, for example, in the sense that the area of ​​the second part becomes too large and encroaches on the area of ​​the first part, the stack itself may be displayed, for example, as a rotating wheel or slider in the first visual orientation. Thus, for example, each menu item in the stacked list may be displayed in the second visual orientation (the item is slidable in that direction, for example, horizontally), while each list in the stacked list is slidable in the first visual orientation (for example, vertically). In this way, the vertical breadcrumb list is provided on a horizontal slider and can be contextualized by other options (selected items) to the left and / or right of the center. Any layer can be adjusted in real time without having to go back. Such display of the vertical and horizontal sliders allows navigating a tree of options and selecting the desired leaf-like options. In another embodiment, the number of menu and / or submenu items can be collapsible and expandable. For example, the newest level, the bottom or last "n" level (e.g., 3 levels), may be displayed with the remaining levels collapsed. These collapsed levels can be expanded, for example, by user input. As another example, the top "m" level (e.g., 2 levels) and the bottom level (e.g., "1" level) may be displayed, representing the context of the top level having the most recent option or decision (i.e., the bottom level) that the user is working with.

[0145] Figures 2A-2C show the first visual orientation as vertical and the second visual orientation as horizontal, but the orientations can be switched. For example, the first visual orientation may be horizontal and the second visual orientation may be vertical. In another embodiment, the first and second visual orientations may be any other positional orientation.

[0146] As described above, menu items and associated submenu items may be displayed as slider graphical elements, rotary wheel graphical elements, or other graphical user interface elements. For example, concentric wheel elements may be used with respect to Figures 2H to 2J, as described below.

[0147] In embodiments, the ordering or arrangement of menu items within those menu levels may be determined according to the attributes of the menu items. The display format of a menu item may be based on attributes selected from whether the menu item is a previously selected or unselected item, whether the menu item is selectable or not, whether the menu item contains one or more characters entered 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 has a more central position in the list compared to other items in the list.

[0148] In some embodiments, the method by which menu items are adapted to be displayed (i.e., ordering, arrangement, coloring, and presentation of menu items) may be determined according to some different factors. For example, the menu manager 1054 and the display manager 1050 may together be configured to highlight menu items that are selected or have been selected in the past, menu items that are currently available to the user (i.e., selectable), and / or menu items that are located in the decision zone of the first part 204 or the second part 208. The menu manager 1054 and the display manager 1050 may further be configured to downplay menu items that are not selected or have not been selected in the past, menu items that are currently unavailable to the user, and / or menu items that are located away from the decision zone. In some embodiments, immediately selectable menu items may be highlighted, and non-immediately selectable items may be downplayed. In some embodiments, highlighting or downplaying menu items may include highlighting or not highlighting menu items, as discussed herein. Highlighting or emphasizing may include, for example, bolding, increasing font size, changing font, underlining, changing brightness or contrast, or adjusting the display position relative to other items. Not highlighting or making something less conspicuous may include decreasing font size, changing font, fading, changing brightness or contrast, or adjusting the display position relative to other items.

[0149] The MUI allows the user to jump to different paths of menu items by enabling them to select a previously unselected menu item from a previously navigated menu level displayed in the second part 208 of the MUI display 206, and to select a newly displayed menu item on the first menu that displays the ongoing menu displayed in the first part (for example, by selecting one or more additional menu items at the same hierarchical level, a higher hierarchical level, or a lower hierarchical level of the menu). As considered above with respect to Figure 2C, previously navigated menu items (including submenu items, sub-submenu items, etc.) may be rearranged in the second part 208 after a menu item has been selected.

[0150] Previously selected menu items in the second section 208 may be highlighted or emphasized to visually indicate the menu path taken to arrive at the menu or submenu currently displayed in the first section 204. Previously unselected menu items from the second section may be selected to allow the user to jump to that branch of the menu. In the example in Figure 2C, the user has previously selected MENU ITEM 4 and SUBMENU ITEM 3. When a new, previously unselected submenu item 210 is selected from the second section 208, the menu manager 1054 issues a command for a new list of sub-submenu items 212 associated with the newly selected submenu item 210, which will be displayed as a menu in progress in the first section 204. By selecting a new, previously unselected menu item from menu item 202, the menu manager 1054 issues a command to display a new list of submenu items associated with the newly selected menu item 202, so that a menu in progress is displayed in the first section 204. In this way, users can actively jump between different parts of the menu tree without having to navigate through previously made decisions.

[0151] When a previously unselected menu item (or submenu item, or sub-submenu item, etc.) is selected, a save command may be issued to store the state of the ongoing menu in the first part before the subsequent menu of the first part is displayed. In embodiments, as disclosed in more detail below, the user can make one or more parameter selections by navigating to the final branch in the menu tree via menu items at the executable menu level. If the user navigates without going through the executable menu, the parameters currently selected when the user navigated without going through may be stored via a save command issued by the menu manager 1054 to the data storage manager 1064. Thus, if the user later wishes to return to the executable menu, the last selected parameters will be displayed.

[0152] Menu items that have not been previously selected may be selectable within past menus of previously navigated menu items. In embodiments, previously selected menu items may be instantly selectable, requiring only a click for selection, or they may be non-instantly selectable, requiring another step of highlighting the menu item before selection. In embodiments, previously selected menu items may be unavailable because the user has already selected them. In further embodiments, only previously selected menu items from the lowest hierarchical level of past menus (i.e., the menu immediately preceding the current first menu) may be unavailable, while previously selected menu items from higher hierarchical levels remain selectable. In the example provided by Figure 2C, SUBMENU ITEM 3 may be unavailable, while MENU ITEM 4 may be selectable.

[0153] In embodiments, various menus are displayed on the background. In one embodiment, the menus are superimposed 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 a single color. For example, at least a predetermined percentage of the background pixels may be black. For example, 75% of the background may be a single color (e.g., black, white, gray, etc.). The specific percentages are described as examples, and other percentages may be used.

[0154] In some embodiments, display commands and rearrange commands may specify a background including a predefined proportion and color, such as black, white, or gray. In certain embodiments, the background may also include areas for non-text menus (e.g., menu items). In one embodiment, the menu text is displayed in a color that contrasts with or highlights the text against the background. For example, if a black background is used, white or yellow may be used for the text color, but other colors may also be used. In other embodiments, the background and / or text may consist of two or more colors.

[0155] In some embodiments, the initial or first menu, i.e., the Start / In Progress menu, may be the default menu displayed when a registered user logs in. In one embodiment, the default menu may be customized for a specific user identifier. In other embodiments, the default menu may be specific to the MUI module. For example, the default menu may include a list of menu items such as Assay, Test, Start, Clinical Trial, etc. In embodiments according to this specification, the default menu is determined according to one or more of the following: the MUI module being started, the location of the device starting the MUI module, the user identifier, and the application of the menu. For example, a device located on the user's desktop may start an MUI module with a default menu set as the default, which is suitable for selecting options for experimental design or experimental analysis. In another example, a device located on a clinical instrument may start an MUI module and provide a default menu that is suitable for starting an experiment and selecting options for 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 level in a hierarchical menu tree.

[0156] 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 inputs associated with menu items (optional). User input is received via input manager 1052 and forwarded to menu manager 1054 for search purposes. Searching allows filtering of functions (menu items) using the entered keywords or other inputs, reducing the time required to find the desired menu item. The interface for the search function may be located in the center of each part of the MUI display 206, or alternatively, in another part of the MUI display 206. In a further embodiment, no visual interface is provided for the search function. In such an embodiment, the user may access the search function simply by typing.

[0157] In one embodiment, any menu item that matches or partially matches the keyword may be displayed and highlighted. For example, the menu item may be displayed in a larger size than other menu items that do not match or partially match. In another embodiment, the menu item may be highlighted in bold, italics, or a different color from the background, or underlined. In another embodiment, menu items that do not match or partially match the keyword may be made less prominent, for example, by reducing or fading the text of the menu item with respect to the text of the matching or partially matching menu item. In embodiments of this specification, a slider or wheel can be automatically moved forward and / or rotated to display menu items that match the search term.

[0158] In one embodiment, a first menu selection may act as a filter on a second menu. In a hierarchical tree, each of several items in the first menu may 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 include menu items related to team roles, and the second menu may include menus related to team responsibilities. By selecting a particular team role in the first menu, the second menu can be filtered to show only the team responsibilities corresponding to the selected role. In some embodiments, such filtering is performed by making certain items in the second menu unselectable.

[0159] In one embodiment, any selection made in any menu acts as a filter for menu items displayed in any other menu. For example, in one embodiment, a set of items in a first menu may be a set of category filters, each leading to a second menu. Each second menu leads to a set of submenus, which ultimately lead to one or more execution menus, allowing the user to select parameters for the selected category filter. After selecting a category filter in one or more of the category filter submenus, the user can then select another first menu item that provides a list of second menu items filtered according to the previously selected category filter.

[0160] In one embodiment, one or more menus or menu levels may be presented as exceptions to the hierarchical menu tree standards considered herein. For example, a menu level may include visual and / or video displays rather than text-based visual components. Exceptions may be implemented, for example, in situations where information can be better conveyed through alternative means. For example, as considered above, a run-level menu may include a walkthrough, which may be best presented via video or a series of images. In another example, a run-level menu may be presented for data analysis and may provide any combination of graphs, charts, tables, etc., to assist in data analysis.

[0161] In one embodiment, an advanced context menu may be provided via one or more commands issued by the menu manager 1054. Figure 2P shows an example of a systematic user interface including an advanced context menu 270. The advanced context menu 270 is in contrast to the first and second parts, which together provide a “direct workflow mode”. In embodiments, the advanced context menu 270 may be accessed via an advanced context menu selector 290, which may be present on some or all screens of the systematic user interface. The advanced context menu 270 provides additional advanced menu items 271, rather than items displayed in the ongoing menu within the active first part 204, or one or more past menus displayed within the second part 208 of the history. The advanced context menu 270 may be accessed by clicking or mouseover over the advanced context menu selector 290, or otherwise by indicating a desire to access the advanced context menu 270. The advanced context menu 270 includes the selection of an advanced menu item 271.

[0162] The selection of an advanced menu item 271 may include items displayed in the ongoing menu of the first (active) section 204 and items displayed in the previous menu of the second (history) section 208. According to one embodiment of this specification, the advanced menu item 271 of the advanced context menu 270 may be highlighted. For example, the advanced menu item 271 may be displayed in a larger font size. In other embodiments, the menu item may be highlighted in bold, italicized, or using a different color from the background, or it may be underlined.

[0163] Other items included in the selection of items within the advanced context menu 270 may be items related to one of the displayed menus but not currently included. In other words, the selection of items within the advanced context menu 270 is driven by the current context of the UI display. For example, five menu items of the first menu may be displayed as the active part of the ongoing menu. Three additional menu items related to the five menu items of the first menu may be displayed in the advanced context menu 270. The three additional menu items may be items of the first menu that have been excluded or limited from the ongoing menu display for various reasons (as will be further considered below).

[0164] The advanced context menu 270 provides the user with a larger array of accessible menu items without causing clutter in the active or history portion. In embodiments, some of the advanced menu items 271 of the advanced context menu 270 may be items that are rarely selected, for example, in less than 50%, 45%, 40%, 35%, 30%, 25%, 20%, 15%, 10%, or 5% of use cases. The advanced menu items 271 of the advanced context menu 270 may be selected according to patterns of user interaction with the MUI, as will be described in more detail below.

[0165] In some embodiments, the advanced context menu 270 may include three parts. The first upper part 272 of the advanced context menu 270 may include advanced menu items 271 related to the currently active menu, as described above. The second middle part 273 of the advanced context menu 270 may include advanced menu items 271 related to MUI modules available on the same workstation from which the advanced context menu 270 is selected. These options may allow the user to swap modules based on the desired task. The third lower part 274 of the advanced context 270 menu may include global functions such as login / logout functionality, user manual and help, EULA information, and privacy policy information. The above ordering is not limiting, and any of the listed advanced menu items 271 may be presented in a different order.

[0166] In this 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). Thus, the MUI provides a dialog box adapted to appear in the foreground of the UI display to prompt the user for additional information or notify the user of an error. Here, the background of the dialog box is further adapted to match the backgrounds of the first and second parts of the UI display, and further, one or more of the text, graphics, photographs, and videos displayed in the backgrounds of the first and second parts of the UI display are adapted to appear out of focus when the dialog box is displayed in the foreground of the UI display.

[0167] In one embodiment, certain menu items included in a hierarchical menu tree, namely the first menu, the second menu, the third menu, etc., may be excluded from display or have their display restricted when that menu is displayed. Exclusions and restrictions may be managed by an exclusion manager 1058 in conjunction with the menu manager 1054. Displaying any menu from the menu tree includes displaying one or more menu items from that menu, but does not necessarily require displaying all items from that menu. Menu items at the hierarchical menu level can be excluded or restricted from display based on an exclusion table. The exclusion table may correspond to a user identifier, email address, username, team, and / or account number. In other embodiments, one or more entire menus from the menu tree may also be excluded based on an exclusion table. In certain embodiments, exclusion or restriction information may be stored in a storage device 1120. Exclusion or restriction information may be stored as a data structure. Any data structure described herein may be used.

[0168] Exclusion or restriction information can be used to exclude menu items from views such as specific users, user groups, or user types. For example, administrative menu items or menu levels may be excluded from the view of users or operators who are engineers or technicians. In another example, design menu items or menu levels may be excluded from the view of users or operators who are lab assistants or lab technicians.

[0169] User identifiers, account numbers, and menu items and / or menus for exclusion can be entered by the administrator. For example, the administration console module, which will be discussed in more detail below, may be used to manage and generate the exclusion table. Management may be performed when the user registers with the system. In other embodiments, exclusion information may be added after registration and updated periodically.

[0170] In one embodiment, the hardware processor maintains a record of logins (and logouts) via the data storage manager 1064 each time a user logs into the system. In one embodiment, this record, i.e., the login history data, may be in any form of data structure described herein. In one embodiment, this login history data may include a user identifier and / or account number, login time / date, and logout time / date. In one embodiment, upon receiving login information, the data storage manager 1064 adds the user identifier and / or account number, and login time / date to the login history data.

[0171] In a particular embodiment, before issuing a command to display any menu, the menu manager 1054 may check an exclusion table (stored, for example, in the storage device 1120) to determine whether any menu item in the initial display menu (e.g., the default menu) is listed to be excluded from display for the user (or account number). In one embodiment, the menu manager 1054 may match the user identifier and / or account number of the currently logged-in user with a user identifier and / or account number listed in the exclusion table. If a match is found, the menu item listed in the exclusion table is excluded from being displayed in the initial display menu. This exclusion may be carried out through the issuance of separate exclusion commands and / or instructions, or alternatively, the exclusion may be carried out by modifying any display command that displays the available menu items. The menu manager 1054 may also issue a first command that does not include the menu items included in the list, and remove the menu items from the menu items of the initial display menu (e.g., the default menu).

[0172] In a particular embodiment, before issuing a rearrangement command, whenever the input manager 1052 receives a selection of a menu item in the ongoing menu, the menu manager 1054 may determine whether the ongoing menu is enumerated in such a way that menu items at lower hierarchical menu levels than the hierarchical menu level currently displayed by the MUI display 206 are excluded (or whether lower hierarchical menus are excluded). Login history data and exclusion tables may be used for the determination. Login history data may be used to confirm that the same user (user identifier or account number) is still logged in and match it with the user identifier and account number in the exclusion table. In other embodiments, the menu manager 1054 may use the user identifier and account number received from the user manager 1056 instead of login history data for the determination. In other embodiments, a similar determination is made before issuing any rearrangement or display command.

[0173] In yet another embodiment, different exclusion tables may be used depending on whether a menu item is displayed on the MUI display 206 in the first part 204 or the second part 208. According to this embodiment, the exclusion table may have additional information columns, one column for each part (menu). The column for the first part lists the menu items that are excluded when displayed in the first part 204 of the MUI display 206. The column for the second part 208 lists the menu items that are excluded when displayed in the second part of the MUI display 206. The column for additional parts lists additional menu items that are excluded when displayed in any additional part of the MUI display 206.

[0174] As explained above, an account number can be associated with multiple users (user identifiers). Thus, when using an account number as an exclusion criterion, all users associated with that account number may be excluded from the menu items displayed in MUI display 206.

[0175] In another embodiment, a specific account number may be linked, so that when an account number is used, any account number linked to that account number may also exclude menu items.

[0176] In other embodiments, instead of excluding menu items, menu items may be moved to their respective menu locations to make them less conspicuous relative to other menu items. According to this embodiment, the exclusion table may be used by the menu manager 1054 to reorder or change the positions of menu items on the hierarchical menu level. Subsequent commands (the first command, the second command, and / or the third command) may reflect the changed positions of the menu items.

[0177] In other embodiments, menu items (or hierarchical menu levels) may be excluded based on a specific device or based on the location of a device. The device on which a menu item is excluded may be one or more devices that execute various software instructions of the systematic user interface control system 1102.

[0178] 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 or machine name. In one embodiment, one column in the table may contain an identifier, for example, a MAC address. A second column in the table may contain menu items or hierarchical menu levels associated with the identifier (e.g., MAC address) that are excluded from display.

[0179] In other embodiments, instead of one (or more) tables, the list of menu items and / or hierarchical menu levels is stored associated with an identifier (e.g., MAC address).

[0180] Device identifiers such as MAC addresses, as well as menu items and / or hierarchical menu levels for exclusion, may be entered by an administrator and / or one or more users with appropriate permissions. This exclusion information may be entered when the first MUI module is installed on the device. In other embodiments, the exclusion information may be added after installation and updated periodically.

[0181] In a particular embodiment, when login history data is received, or in response to a notification is received, before issuing any command to display any menu (and menu items), the hardware processor running the input manager 1052 may check exclusion information in the storage device 1120 to determine whether any menu item of the initial display menu, or a menu item associated with a selection, is excluded from the device.

[0182] In one embodiment, the menu manager 1054 can compare a device identifier with a device identifier listed in the exclusion information. If a match is found, a particular menu item is excluded from display on the MUI display 206. For example, if a hierarchical menu level lower than the hierarchical menu level currently displayed on the MUI display 206 as the initial display menu (e.g., the default menu) or a menu in progress associated with a selection contains one or more menu items listed to be excluded, the menu manager 1054 may remove the excluded menu items from the menu before issuing a display command, and then issue a display command with the menu items removed. In this example, the removed menu items are not displayed on the MUI display 206.

[0183] In other embodiments, certain menu items (or hierarchical menu levels) may be excluded based on which hierarchical menu levels are currently displayed as the ongoing menu (in the first part) or the previous menu (in the second part). In one embodiment, one column in the exclusion table may contain the menu identifier of the hierarchical menu level. A second column in the table may contain the menu items or hierarchical menu levels associated with the menu identifier that are excluded from display.

[0184] A menu identifier represents a hierarchical menu level that can be displayed in either the first or second menu. Excluded menu items are menu items that are unavailable for selection from the displayed hierarchical menu level. These menu items may be application-specific menu items. In a particular embodiment, when a hierarchical menu is displayed as an ongoing menu in the first part 204 or a previous menu in the second part 208 and a selection is made, before issuing a command, the menu manager 1054 checks the exclusion information to determine whether any menu items associated with the hierarchical menu level selected to be displayed should be excluded. Based on the determination, the menu manager 1054 may remove the excluded menu items from the menu before issuing a response command, and then issue a response command with the menu items removed. This exclusion may be performed through the issuance of separate exclusion commands and / or instructions, or alternatively, the exclusion may be performed by modifying the first, second, and / or third display commands that provide the available menu items to be displayed.

[0185] In other embodiments, instead of a display or rearrange command being issued with menu items cleared, an exclude command may be issued by the exclude manager 1058 in combination with a display or rearrange command. In this embodiment, the display command has all menu items associated with the menu, and the exclude command causes the display manager 1050 to delete the executed menu items included in the exclude command before triggering the display.

[0186] In other embodiments, the number of menu items displayed may be limited by the menu manager 1054 based on usage frequency. For example, in one embodiment, the number of menu items may be limited based on selection frequency. In a particular embodiment, the frequency may be determined over a predetermined period. The selection frequency can be pre-configured or customizable and may include, for example, a frequency of 50% to 80%, but other selection frequencies are also contrivant. By limiting the display of menu items to include only those used above a certain threshold frequency, clutter within the menu system is reduced and the menu experience is streamlined.

[0187] According to this embodiment, the input manager 1052 tracks the selection of all menu items and stores them in the storage device 1120. In one embodiment, a 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., those specifically described herein).

[0188] In certain embodiments, the selection of one or more users can be tracked over a predetermined period. This period may be a day, a week, a month, or any other predetermined or customizable period. The specific period may be based on the application, such as the type of clinical trial or study, the type of trial, or the type of organization (e.g., university, company). Tracking may be repeated for each predetermined period.

[0189] Each time the input manager 1052 receives a notification from the hardware processor running the input manager 1052, the input manager 1052 may record the user identifier, username, email address, and / or account number, the selected menu item, and the time and date of selection within a pre-configured period. The date and time may be obtained from a timestamp included in the notification. In one embodiment, the user identifier and account number may be obtained from a login history table. In other embodiments, the user identifier and account number may be included in the notification.

[0190] At the end of a specific period, the input manager 1052 determines the selection frequency for each menu item. In one embodiment, the input manager 1052 can determine the selection frequency for a user identifier. The selection frequency is based on the number of times the menu item has been selected and the total number of selections (within the specified period) by the user identifier.

[0191] In other embodiments, the determination may be based on account numbers in addition to user identifiers. For example, input manager 1052 may determine the selection frequency of a menu item by at least two user identifiers having the same account number. In this example, users form a team if a single account number is associated with and / or linked to two or more user identifiers. In another example, a team may include two or more account numbers that are associated with and / or linked together. In yet another example, N unique users may form a team associated with and / or linked to M unique account numbers, where N is greater than M. Identifying user identifiers having the same account number can be achieved by using a shared account flag in the registration table in combination with the menu item selection table to determine that at least two user identifiers have made a selection within a given period.

[0192] For menu items, selections of multiple menu items are aggregated for at least two user identifiers (as determined from the menu item selection table). Similarly, the total number of selections is aggregated for at least two user identifiers (as determined from the menu item selection table). The frequency is then based on the aggregated selections and aggregated total selections of the menu items.

[0193] In other embodiments, frequency determination may be based on selections where a user identifier is associated with an account number linked to another account number (e.g., a user's team). In this embodiment, the input manager 1052 may identify linked account numbers using a number of account flags that are set to specific values ​​when an account number is linked. Once identified, the input manager 1052 can determine selection frequency by using selections from user identifiers associated with one of the linked account numbers. In this embodiment, selections from other user identifiers or from the same user identifier not associated with one of the linked account numbers (if the same user identifier is associated with a different account number) may be ignored (not used in the determination). As above, the input manager 1052 may determine frequency by determining the number of selections for a menu item and the total number of selections. In other embodiments, the systematic user interface control system 1102 may use selections from any user identifier associated with one of the linked account numbers for determination (and may aggregate the selections).

[0194] In other embodiments, frequency determination may be based on the selection of at least two user identifiers, where the user identifier is associated with one or more account numbers linked to other accounts. According to this embodiment, the hardware processor running the input manager 1052 may identify linked account numbers using a plurality of account flags that are set to specific values ​​when account numbers are linked. Once linked account numbers are identified, the hardware processor running the input manager 1052 can further identify at least two user identifiers (associated with linked account numbers) that have made selections within a period of time, using a menu item selection table.

[0195] For at least two identified user identifiers that have made a selection, the selection of multiple menu items is aggregated for at least two user identifiers (as determined from the menu item selection table). Similarly, the total number of selections is aggregated for at least two user identifiers (as determined from the menu item selection table). The frequency is then based on the aggregated selections and aggregated total selections of the menu items.

[0196] In other embodiments, frequency determination may be based on all selections, regardless of the user identifier and / or account number. According to this embodiment, the input manager 1052 may determine the frequency for each menu item by determining the number of selections for each menu item relative to the total number of selections (of any menu items) during the period.

[0197] The frequencies described above can be used in conjunction with restriction commands issued by menu manager 1054. The function of restriction commands is similar to that of exclusion commands, as discussed above. Restriction commands serve to restrict the display of certain menu items based on one or more criteria. For example, a restriction command may be based on: (a) how often a user has previously selected an item while logged into their account. In one example, this determination may be based on a given period of time. In another example, the determination may be based on the number of times a given user logs into their account. Other criteria may include: (b) how often an item has previously been selected while at least two users are logged into their account. In a particular embodiment, this may include a time period for a given user, or a time period based on the total time a user has been logged into their account. Alternatively, it may be based on the total number of logins for a given user or the total number of logins being aggregated. Furthermore, criteria may include: (c) how often a user has previously selected an item while logged into an account associated with multiple accounts, or (d) how often an item has previously been selected while at least two users are logged into one or more accounts associated with multiple accounts. For both of these examples, as described with respect to examples (a) and (b) above, the frequency may be based on one or more combinations of the duration that one or more users remain logged into an account or the number of account logins. Furthermore, the criteria may include: (e) how often any user previously selected an item while logged into any account, and / or (f) how often any user previously selected an item while logged into any account associated with multiple accounts. In these two examples, a data structure such as a table (or any other data structure described herein) can be used to track previously selected items, and the table may be cleared periodically after a given period of time has elapsed or after a certain total number of logins by one or more users have occurred.In certain embodiments, the criteria described in (c), (d), and (f) above may apply to team accounts in particular if the users of those accounts are team members who have one or more teams associated with multiple accounts.

[0198] If the determined frequency is greater than or equal to a threshold percentage, the menu item may be restricted for the period immediately following. The threshold may be based on usage. In one embodiment, the threshold percentage may be 50% or more. In another embodiment, the threshold percentage may be 60% or more. In yet another embodiment, the threshold percentage may be 70% or more. In yet another embodiment, the threshold percentage may be 80% or more. In another embodiment, the threshold may be a range of a certain percentage. For example, the threshold percentage may be in the range of 75% to 85%. Specific percentages are described herein as examples, and the threshold percentage is not limited to them. Any threshold percentage or range may be used.

[0199] In other embodiments, a selection ratio may be used instead of selection frequency. The ratio is defined as the number of selections for one menu item divided by the number of selections for other menu items. For example, 9:1, 7:1, 5:1, 3:1, or any other preferred ratio may be used.

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

[0201] If it is determined that menu items may be restricted, the hardware processor can determine which menu items may be displayed on the MUI display 206 in the following period, and which menu items are restricted. According to the embodiment, any menu item that is determined to have a frequency exceeding a threshold ratio may be displayed (for example, without restriction).

[0202] In further embodiments, display restrictions may be based on menu items having a selection frequency below a certain threshold, for example, less than 50%, 40%, 30%, 20%, or 10%.

[0203] In some embodiments, restriction commands can be issued based on various criteria. For example, one or more menu items may be excluded based on menu items designated as unavailable to a particular user. This could occur, for example, if a particular user has not selected one or more menu items over a certain period of time. Similarly, one or more menu items may be restricted based on menu items designed to be unavailable to a group of two or more users. In this example, the frequency with which two or more users select or do not select one or more menu items over a certain period of time may influence whether a restriction command is issued for those menu items. Other embodiments intend to issue restriction commands in a similar manner to the previous two examples, but not for individual teams and / or groups of teams (i.e., based on the frequency with which users associated with a team select a menu item). Furthermore, in other embodiments, menu items can be restricted based on a particular machine or group of machines running a computer application that one or more users are logged into.

[0204] In one embodiment, the menu manager 1054 can issue a restriction command to the hardware processor running the display manager 1050. According to this embodiment, the restriction command may include menu items that have been determined to have a frequency exceeding a threshold ratio. The restriction command may be issued in conjunction with one or more display commands. Upon receiving display commands and restriction commands, the display manager 1050 can delete or remove menu items that are included in the display command but not in the restriction command before displaying the menu items in the MUI display 206.

[0205] In other embodiments, the restriction command may include menu items other than those determined to have a frequency exceeding the threshold ratio. Upon receiving a display command and a restriction command, the display manager 1050 may delete or erase menu items included in the restriction command and also included in the display command before displaying the menu items on the MUI display 206.

[0206] In other embodiments, instead of a separate limit command, the display command may be modified by the menu manager 1054 to clear menu items other than those determined to have a frequency exceeding the threshold percentage.

[0207] Through the use of limit commands, menu items (user-selectable options or choices) may be limited to a smaller number of menu items on the first and second menus. For example, the first menu may contain nine menu items, but the use of limit commands limits the total number of menu items displayed to less than nine. For example, the total number of menu items (user-selectable options) may be seven or less (or less than seven), five or less, three or less, or any other number. The number of menus (limited number) described herein is merely an example, and the number may be any number selected to provide a limited display that avoids or prevents the user from being overwhelmed by choices. In embodiments, menu items excluded from display for the purpose of limit commands are provided in an advanced context menu 270. In embodiments, menu items excluded from display based on the limited number may be selected according to their selection frequency.

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

[0209] In one embodiment, the restriction function may operate as follows, so as to be applicable to any type of MUI module: A threshold percentage can be used to determine which menu items are displayed (e.g., without limitation). For example, a threshold percentage of 90% or 80% may be used. This means that only menu items with a selection frequency exceeding 90% or 80% will be displayed. In one example, the selection frequency may be applied based on the user login session. This means that menu items that are used only 90% or 80% of the time the user is logged in will be displayed. The restriction function can be applied to one or more menu levels, i.e., a first menu level, a second menu level, and so on. In some embodiments, the threshold may vary based on the menu level (e.g., lower levels may have lower frequency requirements for display, because lower levels often have more options that may be selected less frequently). Menu items that do not meet the threshold (e.g., used 10% or less, or used 20% or less) are displayed in an advanced context menu, which changes according to the currently displayed menu. In this way, the user's choices are limited to those most frequently used throughout the MUI, significantly speeding up user navigation. In certain embodiments, the choices excluded as described above can be made available only in the advanced context menu. Thus, in 90% of cases, if only 90% of the available menus meet the threshold, only those will be displayed in the ongoing menu, while the remainder (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).

[0210] The values ​​90% / 10% and / or 80% / 20% are illustrative only, and other values ​​may be selected according to the MUI module being implemented. For example, the restriction function may also be based on a default protocol compared to a user-customized protocol. For instance, a vendor may market an assay kit that includes a standard protocol that allows for further customer modifications. The standard protocol option may be included in an available menu item that appears in the active section as the user navigates through the menu system. On the other hand, available customer modifications may be displayed in an advanced context menu. This division of menu items can be adjusted based on actual user behavior after the particular assay kit has been used several times by the user.

[0211] Similarly, by using the restriction command, the number of menu items (user-selectable options) on the first menu, the second menu, and the third menu may be limited to a smaller number.

[0212] In a particular embodiment, after a period of time has elapsed, the menu item selection table can delete the selection history for new determination. In this example, previously excluded menu items become available again.

[0213] In embodiments, the MUI can provide team integration through communication between multiple MUI modules. An integration system managed by a system consistent with the embodiments herein can be managed by multiple MUI modules configured to complete different tasks by different operators. For example, using the example of a laboratory information management system (LIMS), an administration console module, an experiment design module, an inventory management module, an experiment analysis module, and an experiment procedure module may be provided. The administration console module can provide features and functions for managing various users, operators, instruments, and teams. The experiment design module can allow one or more members of a team to design experiments to be performed by other members of the team. The inventory management module may allow other team members to review the inventory and order more consumables in light of the experiment history and future planned experiments. The experiment procedure module may allow a team member responsible for initiating an experiment to access and implement already designed experiments through interaction between the MUI, operators, and external systems. Finally, the experiment analysis module may allow other team members to access the results of an experiment after it has been performed. Based on user and team setups prepared via the management console, each user may be provided with access to the modules necessary to log into the system and complete the tasks they are responsible for. In embodiments, the necessary modules may be installed on computing devices located in appropriate locations for completing tasks (i.e., experimental procedure modules may be installed on devices connected to experimental instruments, and management console modules may be installed on desktop devices). Thus, the system provided herein enables the integration of workflows among multiple team members using a single, consistent interface.

[0214] In one embodiment, the display manager 1050 can be configured to provide one or more icons or animations to indicate the "working" status of the systematic user interface control system 1102. When the systematic user interface control system 1102 is processing, a work status indicator can be provided to warn the user that processing is taking place, thereby preventing waiting times. In one embodiment, the work status indicator may be provided via a light fountain-type display presented on a portion of the screen not occupied by the active portion or history portion. For example, the lower part of the screen, centered on the lower side of the active portion, may be used for the light fountain-type display. The light fountain may provide a series of cascading bars shown in colors that match the rest of the MUI. In one embodiment, the cascading bars may be presented in various shades of white and blue. In one embodiment, the bars are presented in four rows of elongated bars. Each row may contain, for example, 2 to 20 bars of different lengths. When the system is processing, the bars may flash in different shades of white and blue and of different lengths to give the impression of a waterfall or light fountain.

[0215] Embodiments described herein further include methods for designing user interface systems. For example, such methods may include designing a MUI consistent with the embodiments described herein. Methods for designing user interface systems may include generating a hierarchical menu tree as described herein. The hierarchical menu tree may include a set of menus, each containing a menu item that leads to a subsequent set of menus. Methods for designing user interface systems may further include selecting an execute menu that terminates a branch of the hierarchical menu tree, where the execute menu is configured to execute one or more commands within the software, provide one or more instruction sets to the user, and / or output one or more commands to a connected device, system, instrument, or machine. Methods for designing user interface systems may further include configuring each of the menus in the hierarchical menu tree in one or more display modes, where one or more display modes include at least an active display mode for displaying in the active portion of the user interface and a history display mode for displaying in the history portion of the user interface. Further embodiments of user interface design methods may further include methods for designing any of the menu functions described herein.

[0216] In further embodiments, a MUI consistent with the present disclosure may provide an integrated help option during hierarchical menu navigation. A user may request help regarding a given menu by pressing a specific key combination and / or by accessing a help option displayed by an advanced context menu. The integrated help option may include one or more dialog boxes designed to provide the user with an explanation of the presented option. As considered above, the MUI provides a large amount of whitespace or background space. Therefore, the help option may be presented as a pop-up or dialog box pointing to the portion of the MUI the user is requesting help for, without compromising the original MUI display. In embodiments, enabling the help function may cause a dialog box to appear when the user hovers the cursor over or otherwise displays any item within the MUI.

[0217] In further embodiments, the MUI history section may be further adapted to display menu items for menus that follow the ongoing menu. For example, as the user navigates the ongoing menu, the user may, for instance, scroll the vertical wheel to highlight or emphasize different menu items. Submenus related to the highlighted menu items may be displayed in the history section to provide a visual representation of the subsequent menus to the ongoing menu, which may contain future items that may then be selected.

[0218] In the embodiments, as discussed above, the first active portion and the second history portion are adapted for consistent display within the same portion of the MUI. The positioning of each of these portions is not limited to a specific location on the MUI, but in certain embodiments, the selected position is maintained. Thus, the active portion of the MUI display is adapted to be consistently displayed within the same first area of ​​the UI display to optimize user focus while interacting with the UI display. The history portion of the MUI display is adapted to be consistently displayed within the same second area of ​​the UI display to optimize user focus while interacting with the UI display.

[0219] The above description provides an example of a menu configuration for providing a UI display of multiple menus within a hierarchical menu tree. Figures 2D-2M provide additional examples of menu display configurations. The following menu display configurations can be used in any combination with each other and with the previously disclosed menu configurations, but are not limited to these. For example, when a particular menu item is selected at any position in the hierarchical menu tree, the processor may execute a command to shift the UI display to one of the menu configurations described herein. In particular, a particular menu display configuration may be associated with a particular menu selection.

[0220] Figure 2D shows another example of a menu display configuration in one embodiment. Figure 2D shows a two-wheel configuration in which a first wheel option has sub-options on a second wheel. For example, when an option is selected on the first wheel of options, the sub-options associated with the selected option are displayed on the second wheel. In one embodiment, the first portion 214 of the display may initially display the first wheel, and in response to the selection of an option from the first wheel, the first wheel containing that option may be repositioned on a second portion 216 adjacent to the first portion. The first portion may then display the second wheel with sub-options for the first option, for example, in a parallel format (the first wheel is displayed parallel to the second wheel in the same visual orientation).

[0221] In a further embodiment of this embodiment, both a first wheel and a second wheel may be displayed in a first portion 214 of the MUI display 206. The first wheel may be displayed in a first sub-part of the first portion 214, and the second wheel may be displayed in a second sub-part of the first portion 214. As used herein, a sub-part may be a division of a larger part. A sub-part may be used interchangeably with a sub-section. In an embodiment, selection of a menu item in the first wheel may be caused simply by clicking any menu item in the first wheel, or by rotating any menu item in the first wheel to a prominent and highlighted position. When an item is selected from a first menu on the first wheel, the second menu displayed on the second wheel may be corrected accordingly. In yet another embodiment of this embodiment, the first portion 214 may be divided into two or more sub-parts, each sub-part including a wheel that displays a corresponding menu. Thus, the three 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 wheels could display a second menu, a third menu, and a fourth menu. Other examples may include any number of wheels.

[0222] In further embodiments, multiple wheels may be displayed in multiple sub-parts of the first part 204, allowing the user to select from multiple menus at the same hierarchical menu level. For example, selecting a particular menu item at one menu level may lead to the display of multiple submenus at the same level. Thus, selecting an item at a second menu level may lead to the display of multiple third menus, each containing multiple third menu items. In embodiments, the displayed submenus may be execution menus, allowing the user to make multiple execution menu selections simultaneously. In embodiments where multiple submenus are displayed, the submenus may be related to each other or otherwise associated with each other.

[0223] Figure 2E shows yet another example of a menu display configuration in one embodiment. In this display configuration, two wheels are compressed into one wheel. The wheel options have sub-options that are represented within one wheel associated with the active wheel option. In this configuration, the first and second portions of the display overlap, yet all menu items can still be visualized (or, in the case of collapsed items, can be visualized by expanding and sliding or rotating the wheel of the item). For example, the second wheel of options may be displayed within the first wheel. The first wheel of options may be rotatable in one direction (e.g., vertically up and down), and the second wheel of options may be rotatable in a different direction (e.g., horizontally left and right). The selected path is also visualized in the second portion. For example, when “Sub-option 2” displayed on the display is selected, the selected option moves under “First wheel option 1”.

[0224] Figures 2F - 2G show yet another example of a menu display configuration in one embodiment. The figures show the switching of wheel options from a horizontal direction to a vertical direction. Figure 2F shows, for example, a menu of options displayed on a graphical wheel where the options being displayed are rotatable in a horizontal direction (left and right). The wheel is displayed in the first portion of the graphical user interface display. When an option (a menu item within the list of options) is selected, the graphical wheel switches to a vertically rotatable wheel. For example, the wheel moves or relocates to the second portion of the graphical user interface display, and the first portion of the graphical user interface display here displays a list of sub-options related to the option selected in the previous menu of options.

[0225] In one embodiment, the second part of the display can display a maximum number of threshold menu levels and then, using a different visualization configuration for displaying past menu levels, prevent the second part from growing too large.

[0226] For example, referring to FIG. 2C, when there are menu levels exceeding the number of thresholds (as an example, FIG. 2C shows two levels (202, 210)), a visualization mechanism may be used that can visualize all past menu levels without the need to enlarge the second part of the display (e.g., FIG. 2C, 208). For example, assume the number value of the threshold is 3. In that example, the second part of the display may show three menu levels. When an additional option for the next level is selected (e.g., the fourth menu level), the second part shows the most recent past three selection contents (the lower three levels), and the items in the second part may be scrollable up and down. In this example, the options of the first menu level are displayed when the second part is scrolled. As another example, the second part may always show the top two levels, i.e., the first two decisions and the last decision. In this way, the user can show, for example, the overall context of the workflow top-down. By tapping or scrolling the second part, menu items can be expanded like an accordion.

[0227] In another aspect, a search function associated with the wheel can be provided. Using search keywords, the user can filter the wheel options available for use. The search function helps to process long wheel options or multi-wheel options. This may take a long time to navigate.

[0228] Figures 2H-2J show examples of a first and second part displayed as a series of concentric circles in one embodiment. Referring to Figure 2H, the dial 220 can be rotated clockwise or counterclockwise to browse menu items or items to select in the options window 218. Tapping the dial area (e.g., circle) 220 selects an option. For example, when an option viewed through the options window 218 is selected, the user interface transitions to the configuration shown in Figure 2I. For example, in Figure 2I, the concentric dial extends inward, showing another concentric circle representing a different level (e.g., a sublevel) of a menu item or path. A sub-option may be viewed via an options window 222 on the circle 224 (also referred to as the dial) by rotating its dial 224 clockwise or counterclockwise. Selection of an option 222 at that level (indicated as sub-option "n") may be done by tapping the area of ​​the circle 224 (i.e., not overlapping with the inner circle or dial 220). In another embodiment, selecting an option from a dial or circular menu user interface (for example, as shown in Figure 2H) can transition the user interface state to the configuration shown in Figure 2J. For example, the next level of option selection expands from the selected option, and the dial expands to show another inner dial 224 with an option window 222. In one embodiment, the number of options viewable in the option windows (e.g., 218 and 222) does not need to be limited, and as a result, an unlimited number of options can be displayed and selected to apply to the application.

[0229] In one embodiment, the options window (e.g., 218) may be enlarged to show the selected option (e.g., highlighted), one or more unselected options (e.g., unselected options displayed before the selected option), and another unselected option displayed after the selected option.

[0230] In another embodiment, the options window (e.g., 219) may display two or more items or options at once, for example, three menu items or options. In this example, an option is selected by tapping a menu item in the options window. After the selection is made, the selected option may be displayed in a highlighted format or another distinguishing format to distinguish it from the unselected options displayed in the options window, for example.

[0231] In another embodiment, the rearrangement command may specify that the second portion is concentric with the first portion, and that the rearranged menu is displayed adjacent to the first portion (and concentrics) which is displayed on the MUI display 206 as a series of concentric circles. For example, the first portion may be displayed as the central circle of the series of concentric circles, and the rearranged menu level of the hierarchy may be displayed as a circle outside or around the central circle.

[0232] Figure 2K shows a tree-type menu level in one embodiment.

[0233] The hierarchical menu tree shown in Figure 2K includes a first menu item, a second menu item, a third menu item, and four execution menus. One execution menu is associated with submenu item 1, and three more execution menus are associated with sub-submenu items 1-3. Selecting menu item 1 from the first menu leads to the display of submenu item 2. Selecting submenu item 1 leads to the execution menu of submenu item 1, where process parameters can be selected. Selecting submenu item 2 leads to the third menu item, a sub-submenu item. Selecting any one of sub-submenu items 1-3 leads to the execution menu of their respective third menu items.

[0234] Figure 2L shows another example of a menu display configuration in one embodiment. A graphical element 242, such as a wheel or slider (or another graphical element), is displayed on a portion 240 of the display screen. The graphical element 242 (e.g., a wheel) uses a search function, such as a search box or area 246, to first (in reverse chronological order) order the most "n" most recent items 244, followed by a list of all menu items 248, for example, sorted alphanumerically. In another embodiment, the menu items shown in 248 are displayed as indexed items, for example, when a search term is entered into the search box 246. The entire wheel 242 is scrollable. For example, the user can either scroll the entire wheel 242 or enter a search string into the search box 246. When a search keyword is entered into the search area 246, menu items that match the search keyword as the search character is entered are displayed. For example, for each character entered, one or more menu items closest to the search character are indexed in 248. Wheel 240 is divided into two independent wheels, one displaying recently selected menu items 244 and the other displaying an indexed list or all menu items 248. The two wheels 244 and 248 are scrollable or movable independently of each other. Thus, for example, the entire wheel 242 is moved or scrolled as a single wheel. In response to receiving or detecting an entry of a search term or character in the search area 246, the wheel branches into two separate wheels 244 and 248 that can be scrolled independently. One of the two separate wheels (e.g., 248) displays a list of menu items filtered based on the search.

[0235] Figures 2M-2O show an example of a scrollable wheel that scrolls or slides from the first menu item to the last menu item and returns from the last menu item to the first menu item. In this embodiment, the graphical element (e.g., wheel or slider) that displays the menu items stops at the last menu item or (if rotating from the last menu item) the first menu item without completely turning or rotating. In this way, for example, the start and end of the menu are always displayed because they are never combined or connected. This technique can reduce the computer's processing cycle time (and be immediately understandable to the user) because the wheel and / or slider can convey the entire menu of choices while clearly indicating which of the choices presented by the wheel and / or slider is the first menu item and which is the last menu item. As a result, the wheel or slider does not need to repeatedly scroll to determine which menu item is the first menu item, which menu item is the last menu item, or whether all menu items have been visited.

[0236] In the embodiment, the wheel and / or slider does not need to rotate completely, for example, it does not make a full rotation or a full circle. For example, the wheel and / or slider rotates or slides from the start menu item to the end menu item and then rotates or slides back from the end menu item to the start menu item. In this way, for example, the start and end of the menu are always displayed, either joined together or spaced apart so as not to be together. This technique reduces processing time because the wheel and / or slider can convey the entire menu of choices (and the user can understand it immediately) while clearly indicating which of the choices presented by the wheel and / or slider is the first menu item and which is the last menu item. Furthermore, as the wheel and / or slider rotates, the selectable choices can be displayed in a more prominent format, such as using larger text, bolder fonts, etc. When the wheel and / or slider is rotated / slid to a different position, previously selectable options, or options that become selectable as the wheel and / or slider continues to rotate / slide, may be displayed in a less conspicuous format, such as by reducing the size of the text or displaying it in a faint font. In one embodiment, the more conspicuous options may be displayed as if they were closer to the user than the less conspicuous options.

[0237] Referring to Figure 2M, the first menu item 252 is shown in the center of the wheel (or slider) 250. The menu item shown in the center may be shown in a highlighted format (e.g., large letters, different colored fonts, etc.). A blank space is shown before the first menu item (e.g., above the center of the wheel where the first menu item is displayed). The next menu items (e.g., 254, 256) are shown adjacent to the first menu item (e.g., below). As the wheel is scrolled (e.g., vertically), additional menu items are displayed, as shown in Figure 2N. For example, as shown in Figure 2N, the next menu item is shown when the wheel 250 is scrolled upwards. Figure 2O shows the last menu item in the center of the wheel, and the previous menu items are shown adjacent to the last menu item (e.g., above). In this embodiment, the wheel or slider 250 does not rotate to display the first menu item after the last menu item 258. Instead, the wheel stops rotating at the last menu item 258. Below the last menu item, 258, a blank space is displayed. Similarly, navigating back (for example, scrolling the wheel in the opposite direction) will display the previous menu items up to the first menu item.

[0238] The illustrative graphical wheels shown in Figures 2M-2O illustrate a vertical wheel, but a horizontal wheel functions in a similar manner. For example, the first menu item may be displayed in the center of the horizontal wheel, and the next menu item may be displayed horizontally adjacent to the first menu item (e.g., to the right of the center). In this example, scrolling the wheel to the left displays additional menu items. When scrolling to the last menu item, that last menu item is displayed in the center, with empty space outside of the last menu item (e.g., to the right of the last menu item). In another embodiment, the orientation of rotation may be reversed. For example, with a vertical wheel, you scroll downwards (not upwards) to navigate from the first menu item to the last menu item, and with a horizontal wheel, you scroll to the right to navigate from the first menu item to the last menu item. The number of menu items (optional) displayed on the wheel at one time can be configurable based on, for example, the screen size and / or screen area assigned to the wheel, and is not limited to the six items shown in Figure 2N.

[0239] A non-exclusive use of such a user interface is to select channels to watch on television (TV). Broader categories may be displayed in the upper horizontal area, finer categories may be stacked below, and leaf-shaped items may be displayed vertically, for example, on a vertical wheel. For example, referring to Figure 2E, “Wheel Option 1” may represent genres, and “Sub-Option 1” may represent shows and / or movies organized within a grid.

[0240] In one embodiment, the systematic user interface control system 1102 provides the user with an interface for initiating a process. The process may include conducting an experiment, performing one or more manufacturing operations, or any other procedure.

[0241] The following details various instructions for performing experiments consistent with embodiments of this specification. Instructions for performing an experiment may also be instructions for operating, designing, executing, reviewing, measuring, analyzing, storing, and carrying out any other tasks related to the experiment. An experiment may be, but is not limited to, one or more assays. A systematic user interface control system 1102 may be incorporated into and / or associated with an assay system and may provide commands for generating an MUI display 206 for the system. In response to a command, the MUI display 206 may display or provide a visual representation of the workflow and / or menu item paths for the assay. An assay may include one or more electrochemiluminescence (ECL) assays.

[0242] The method of this embodiment can be used in conjunction with various assay devices and / or formats. The assay device may include, for example, assay modules such as assay plates, cartridges, multi-well assay plates, reaction vessels, test tubes, cuvettes, flow cells, assay tips, and lateral flow devices, and may have assay reagents (which may include targeting agents or other binding reagents) that are added as the assay progresses or pre-filled within the wells, chambers, or assay areas of the assay module. These devices can be used with various assay formats for specific binding assays (e.g., immunoassays or immunochromatographic assays). Exemplary assay devices and assay formats are described below herein. In certain embodiments, the method of this embodiment can use assay reagents stored in a dry state, and the assay device / kit may further include, or be supplied with, a desiccant material for maintaining the assay reagents in a dry state. Assay devices pre-filled with assay reagents can significantly improve the speed of assay measurements and reduce the complexity of assay measurements while maintaining excellent stability during storage. The dry assay reagents may be any assay reagents that can be dried and reconstituted before use in the assay. These include, but are not limited to, binding reagents, enzymes, enzyme substrates, indicator dyes, and other reactive compounds that may be used to detect the analyte of interest, which are useful in binding assays. Assay reagents may also include, but are not limited to, substances that do not directly participate in the detection mechanism but play an auxiliary role in the assay, such as blockers, stabilizers, detergents, salts, pH buffers, and preservatives. Reagents may be present in a free form on the surface of compartments in the assay module (e.g., chambers, channels, flow cells, wells, etc.) or on a solid phase including the surface of colloids, beads, or other microparticle supports, or they may be supported.

[0243] A wide variety of solid phases, including conventional solid phases from the art of binding assays, are suitable for use in the method of this embodiment. The solid phase 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 composite materials such as carbon-based inks). Suitable solid phases include the surfaces of macroscopic objects such as the inner surfaces of assay vessels (e.g., test tubes, cuvettes, flow cells, cartridges, wells in multiwell plates), slides, assay tips (e.g., those used for measuring gene or protein tips), pins or probes, beads, filtration media, and lateral flow media (e.g., filtration membranes used in lateral flow test strips).

[0244] Suitable solid phases include particles commonly used in other types of particle-based assays, such as magnetic particles, polypropylene particles, and latex particles (including, but not limited to, colloids or beads), materials typically used in solid-phase synthesis, such as polystyrene and polyacrylamide particles, and materials typically used in chromatographic applications, such as silica, alumina, polyacrylamide, and polystyrene. The material may also be a fiber, such as carbon fiber. The microparticles may be inanimate, or alternatively, they may contain animal biological entities such as cells, viruses, and bacteria.

[0245] The particles used in this method may consist of any material suitable for binding to one or more binding partners and / or labels, and may be collected, for example, by centrifugation, gravity, filtration, or magnetic collection. A wide variety of different types of particles that can bind to binding reagents are commercially available for use in binding assays. These include non-magnetic particles, as well as particles containing magnetizable materials that allow for particle collection in a magnetic field. In one embodiment, the particles consist of conductive and / or semiconducting materials, such as colloidal gold particles.

[0246] Microparticles can have a wide variety of sizes and shapes. By way of example, and not limitation, the microparticles can be from 5 nanometers to 100 micrometers. Preferably, the microparticles have a size from 20 nm to 10 micrometers. The particles can be spherical, rectangular, rod-shaped, etc., or can have an irregular shape.

[0247] The particles used in the method can be encoded to enable the identification of specific particles or sub-populations of particles in a mixture of particles. Such encoded particles are used to enable multiplexing of assays that use the particles as a solid-phase support for binding assays. In one approach, the particles are manufactured to contain one or more fluorescent dyes, and specific populations of particles are identified based on the intensity and / or relative intensity of fluorescence emission at one or more wavelengths. This approach is used in the Luminex xMAP system (see, e.g., U.S. Patent No. 6,939,720) and the Becton Dickinson cytometric bead array system. Alternatively, the particles can be encoded through differences in other physical properties such as size, shape, embedded optical patterns, etc.

[0248] The methods of the embodiments can be used with a variety of methods for measuring the amount of an analyte, particularly the amount of an analyte bound to a solid phase. Techniques that can be used include, but are not limited to, cell incubation-based assays, binding assays (agglutination assays, immunoassays, serum assays, nucleic acid assays such as hybridization assays, etc.), enzyme assays, colorimetric assays, and other techniques known in the art. Other suitable techniques will be readily apparent to those of skill in the art. In some measurement techniques, measurement can be by visual inspection, while in other techniques, the use of an instrument may be required to perform the measurement or may provide an advantage.

[0249] Methods for measuring the quantity of an analyte include, but are not limited to, label-free techniques, which include: i) techniques for measuring the change in mass or refractive index on a surface after the analyte has been bonded to the surface (e.g., surface acoustic wave techniques, surface plasmon resonance sensors, ellipsometry techniques, etc.); ii) mass spectrometry techniques (including techniques such as MALDI and SELDI that can measure analytes on a surface); iii) chromatography or electrophoresis techniques; and iv) fluorescence techniques (which may be based on the inherent fluorescence of the analyte).

[0250] Methods for measuring the quantity of an analyte also include techniques for measuring the analyte through the detection of a label that may be directly or indirectly attached to the analyte (e.g., through the use of a labeled binding partner of the analyte). Suitable labels include those that can be directly visualized (e.g., visually identifiable particles, and labels that produce measurable signals such as light scattering, optical absorbance, fluorescence, chemiluminescence, electrochemiluminescence, radioactivity, and magnetic fields). Labels that can be used also include enzymes or other chemically reactive species that have chemical activity leading to measurable signals such as light scattering, absorbance, and fluorescence. The use of enzymes as labels is well established in enzyme-linked immunosorbent assays, also known as ELISA, enzyme immunoassay, or EIA. In the ELISA format, an unknown amount of antigen is attached to a surface, and then a specific antibody is washed onto the surface so that it can bind to the antigen. This antibody is linked to an enzyme, and in the final step, a substance is added that converts the enzyme into a product that produces a measurable signal change. The formation of the product may be detectable in measurable properties such as absorbance, fluorescence, chemiluminescence, and light scattering, for example, due to the relative difference with the substrate. Certain (but not all) measurement methods that may be used in conjunction with the solid-phase bonding method according to the embodiment may benefit from, or require, a washing step to remove unbonded components (e.g., labels) from the solid phase. Therefore, the method of the embodiment may include such a washing step.

[0251] The methods disclosed herein can be carried out manually, using automated technology, or both. The automated technology may be partially automated and may, for example, consist of one or more modular instruments or a fully integrated automated instrument.

[0252] Exemplary automated systems are discussed and described in International Patent Application Publications 2018 / 017156, 2017 / 015636, and 2016 / 164477, each of which is incorporated herein by reference in its entirety.

[0253] The automated systems (modules and fully integrated) on which the methods described herein can be implemented may include the following automated subsystems: a computer subsystem which may include hardware (e.g., personal computers, laptops, hardware processors, disks, keyboards, displays, printers), software (e.g., processes such as drivers, driver controllers, and data analyzers), and a database; a liquid handling subsystem, e.g., sample handling and reagent handling, e.g., robotic pipette heads, syringes, agitators, ultrasonic mixers, magnetic mixers; a storage and handling subsystem for samples, reagents, and consumables, e.g., robotic manipulators, tube or cap or foil punching devices, cap removal devices, linear and circular conveyors and robotic manipulators; a tube rack, plate carrier, trough carrier, pipette tip carrier, and plate shaker. The system may also include a centrifuge, assay reaction subsystems (e.g., fluid-based and consumable-based systems such as tubing and multiwell plates), container and consumable washing subsystems (e.g., plate washing devices), magnetic separator or magnetic particle concentrator subsystems (e.g., flow cells, tubing, and plate types), cell and particle detection, classification, and separation subsystems (e.g., flow cytometers and Coulter counters), detection subsystems such as colorimetric, turbidimetric, fluorescence, and ECL detectors, temperature control subsystems (e.g., air treatment, air cooling, air heating, fans, blowers, water baths), waste subsystems (e.g., liquid and solid waste containers), globally unique identifier (GUI) detection subsystems (e.g., 1D and 2D barcode scanners such as flatbed and wand types), and sample identifier detection subsystems (e.g., 1D and 2D barcode scanners such as flatbed and wand types). Analytical subsystems (e.g., chromatographic systems such as high-performance liquid chromatography (HPLC), high-performance protein liquid chromatography (FPLC), and mass spectrometers) may also be modular or fully integrated. An automated system consistent with the embodiments of this specification may be controlled and / or managed by a systematic user interface control system 1102.

[0254] A system or module that performs sample identification and preparation can be combined with (or linked, adjacent to, or robotically connected to) a system or module that performs assays, detection, or both. Multiple modular systems of the same type can be combined to increase throughput. Modular systems may also be combined with modules that perform other types of analysis, such as chemical analysis, biochemical analysis, and nucleic acid analysis.

[0255] Automated systems enable batch, sequential, random access, and point-of-care workflows, as well as single, medium, and high sample throughput.

[0256] The system may include, for example, one or more of the following devices: plate sealers (e.g., Zymark), plate washers (e.g., BioTek, TECAN), reagent dispensers and / or automated pipetting stations and / or liquid handling stations (e.g., TECAN, Zymark, Labsystems, Beckman, Hamilton), incubators (e.g., Zymark), plate shakers (e.g., Q. Instruments, Inheco, Thermo Fisher Scientific), compound libraries or sample storage and / or compound and / or sample retrieval modules. One or more of these devices may be coupled to the apparatus via a robotic assembly, thereby enabling the entire assay process to be performed automatically. According to an alternative embodiment, containers (e.g., plates) are moved manually between the apparatus and various devices (e.g., stacks of plates).

[0257] The automated system may be configured to perform one or more of the following functions: (a) moving consumables such as plates into and out of the detection subsystem; (b) moving consumables between other subsystems; (c) storing consumables; (d) processing samples and reagents (e.g., mixing reagents and / or adapting them to be introduced into consumables); (e) shaking consumables (e.g., to mix reagents and / or to increase the reaction rate); (f) washing consumables (e.g., performing a wash plate and / or an assay wash step (e.g., well aspiration)); and (g) measuring ECL in a flow cell or in consumables such as tubes or plates. The automated system may be configured to process individual tubes arranged in a rack, multi-well plates such as 96 or 384-well plates.

[0258] Methods for integrating components and modules into automated systems such as those described herein are well known in the art; see, for example, Sargeant et al., Platform Perfection, Medical Product Outsourcing, May 17, 2010.

[0259] In the embodiment, the automated system is fully automated, modular, and computerized, performing in vitro quantitative and qualitative tests on a wide range of analytes, including photometric assays, ion-selective electrode measurements, and / or electrochemiluminescence (ECL) assays. In the embodiment, the system includes hardware units, namely a control unit, a core unit, and at least one analytical module.

[0260] In the embodiment, the control unit uses a graphical user interface to control all instrument functions and consists of a readout device such as a monitor, input devices such as a keyboard and mouse, and a personal computer using, for example, a Windows operating system. In the embodiment, the core unit consists of some components that manage the transport of samples to each assigned analysis module. The actual composition of the core unit depends on the configuration of the analysis modules, which can be configured using methods known to those skilled in the art. In the embodiment, the core unit includes at least a sampling unit and one rack rotor as main components. Expansion of conveyor lines and a second rack rotor is possible. Some other core unit components may include a sample rack loader / unloader, ports, barcode readers (for racks and samples), a water supply device, and a system interface port. In the embodiment, the analysis module performs an ECL assay and includes a reagent area, a measurement area, a consumables area, and a pre-clean area.

[0261] The methods of the present invention can be applied to one or more formats in which multiple assay measurements are performed on a single sample. Multiple measurements that can be used in the present invention include, but are not limited to, i) multiple measurements using multiple sensors; ii) multiple measurements using separate assay domains on a surface (e.g., an array) that is distinguishable based on its position on the surface; iii) multiple measurements using reagents coated on particles that are distinguishable based on particle characteristics such as size, shape, and color; iv) multiple measurements that generate assay signals that are distinguishable based on optical properties (e.g., absorbance or emission spectrum); and / or v) multiple measurements based on the temporal characteristics of the assay signal (e.g., time, frequency, or phase of the signal).

[0262] The present invention includes a method for detecting and counting individual detection complexes. In an embodiment, the surface includes multiple binding domains, and each analyte forms a complex within different binding domains of the multiple binding domains. In an embodiment, the surface is a particle. In an embodiment, the surface is a bead. In an embodiment, the surface is a plate. In an embodiment, the surface is a well in a multiwell array. In an embodiment, the surface includes an electrode. In an embodiment, the electrode is a carbon ink electrode. In an embodiment, each binding domain of each analyte among one or more additional analytes is on a separate surface, and the surface is a bead in a bead array. In an embodiment, each binding domain of each analyte among one or more additional analytes is on a single surface, and the binding domains form an element of a capture reagent array on the surface. In an embodiment, the surface includes an electrode, and the detection step of the method includes applying a potential to the electrode and measuring electrochemiluminescence. In an embodiment, applying a potential to the electrode generates an electrochemiluminescence signal.

[0263] In certain embodiments, the surface contains multiple capture reagents for one or more analytes present in the sample, and the multiple capture reagents are dispersed across multiple degradable binding regions positioned on the surface. Under the conditions used to perform and analyze the measurement, a “degradable binding region” is the minimum surface area associated with an individual binding event that can be degraded and differentiated from another region where additional individual binding events are occurring. Thus, the method includes binding one or more analytes to one or more capture reagents on the surface, determining the presence or absence of analytes within multiple degradable binding regions on the surface, and identifying the number of degradable binding regions containing the analytes of interest and / or the number of domains that do not contain the analytes.

[0264] Resolvable coupling regions can be optically investigated in whole or in part. That is, each individual resolvable coupling region can be optically investigated individually, and / or an entire surface containing multiple resolvable coupling regions can be imaged, and one or more pixels or groups of pixels in the image can be mapped to individual resolvable coupling regions. Resolvable coupling regions may also be microparticles within multiple microparticles. Resolvable coupling regions exhibiting changes in optical signature can be identified by conventional photodetection systems. Optical filters designed for specific wavelengths can be used for optical introduction of resolvable coupling regions depending on the detected species (e.g., type of fluorescent entity) and operating wavelength. In embodiments where optical introduction is used, the system includes two or more light sources and / or multiple filters, and the wavelength and / or intensity of the light sources can be adjusted. In some embodiments, optical signals from multiple resolvable coupling regions are captured using a CCD camera. Other non-limiting examples of camera imaging systems that may be used to capture images include charge injection devices (CIDs), complementary metal-oxide-semiconductor (CMOS) devices, scientific CMOS (sCMOS) devices, and time-delay integration (TDI) devices. In some embodiments, a scan mirror system coupled with a photodiode or photomultiplier tube (PMT) may be used for imaging.

[0265] In embodiments, the binding of each analyte to its corresponding capture reagent is performed in parallel by bringing one or more surfaces into contact with a single liquid volume containing multiple analytes. In embodiments, the multiple analytes include an analyte and one or more additional analytes. In embodiments, each step of the method is performed in parallel for each analyte. In embodiments, the method is a simultaneous multiplex assay. Multiplex measurements of analytes on surfaces are described herein and should also be referred to, for example, U.S. Patents 10,201,812, 7,842,246, and 6,977,722, whose full contents are incorporated herein by reference.

[0266] In certain embodiments, the method of the present invention can be used in a multiplexed format by binding multiple different analytes to multiple capture reagents for those analytes. The capture analytes are immobilized on coded beads such that the coding identifies the capture reagent (and analyte) of a particular bead. The method may further include counting the number of beads having bound analytes (using the detection approach described herein).

[0267] Alternatively or additionally, the capture reagent can be directly or indirectly bound to different distinct binding domains on one or more solid phases, for example, in a binding array where the binding domains are individual array elements, or in a set of beads where the binding domains are individual beads. When the capture reagents for different analytes are immobilized on different binding domains, the different analytes bound to those domains can be measured independently. In one example of such an embodiment, the binding domains are prepared by immobilizing distinct domains of the capture reagent that bind to the analyte of interest on one or more surfaces. Optionally, the surfaces may partially define the boundaries of one or more containers that hold the sample or through which the sample passes (e.g., flow cells, wells, cuvettes, etc.). In a preferred embodiment, the individual binding domains are formed on electrodes for use in electrochemical or electrochemiluminescence assays. Multiplex measurements of surface analytes containing multiple binding domains using electrochemiluminescence are used in the Meso Scale Diagnostics, LLC, MULTI-ARRAY® and SECTOR® Imager product lines (see, for example, U.S. Patents 10,201,812, 7,842,246, and 6,977,722, which are incorporated herein by reference in their entirety).

[0268] Furthermore, the capture reagent can be directly or indirectly bound to an electrode surface containing, optionally, different distinct binding domains, as described above. The electrode surface may be a component of a multiwell plate and / or flow cell. The electrode may contain conductive materials, such as metals, e.g., gold, silver, platinum, nickel, steel, iridium, copper, aluminum, and conductive materials. The electrode may also contain oxide-coated metals, such as aluminum oxide-coated aluminum. The electrode may include a working electrode and a counter electrode, which may be made from the same or different materials (e.g., a metal counter electrode and a carbon working electrode). In a particular embodiment, the electrode contains carbon-based materials such as carbon, carbon black, graffiti carbon, carbon nanotubes, carbon fibrils, graphite, graphene, carbon fibers, and mixtures thereof. In one embodiment, the electrode contains elemental carbon, such as graphite, carbon black, and carbon nanotubes. Advantageously, they may also contain conductive carbon polymer composites, conductive particles dispersed in a matrix (e.g., carbon ink, carbon paste, metal ink, graphene ink), and / or conductive polymers. One specific embodiment of the present invention is an assay module, preferably a multiwell plate, having electrodes (e.g., a working electrode and / or a counter electrode) comprising carbon, for example, a carbon layer and / or a screen-printed carbon ink layer.

[0269] In the embodiment, each binding domain comprises a target reagent complement that can bind to a target reagent complement, each anchor reagent and capture reagent comprises a supplemental linking reagent that can bind to a linking reagent, and the method further comprises (1) binding the capture reagent and anchor reagent to a targeted reagent complement connected to a linking reagent via a supplemental linking reagent, and (2) binding the product of step (1) to a binding domain comprising a targeted reagent complement, wherein (i) each binding domain comprises a different targeted reagent complement, and (ii) each targeted reagent complement selectively binds to one of the targeted reagents, thereby immobilizing the capture reagent and anchor agent to each binding domain.

[0270] Therefore, in the embodiment, the surface contains a targeting reagent complement, the targeting reagent is connected to a linking reagent, and each of the capture reagent and anchor reagent contains a supplemental linking reagent. Therefore, in the embodiment, the targeting reagent complement on the surface is bound to the targeting reagent connected to the linking reagent, where the linking reagent is bound to the supplemental linking reagent on the capture reagent and anchor reagent.

[0271] In embodiments, the linking reagent has two or more binding sites for additional linking reagents, and the immobilization of the capture reagent and anchor reagent further includes (i) each binding domain containing a different targeting reagent complement, and (ii) each targeting reagent complement selectively binding to one of the targeting reagents. For example, if the targeting agent is an oligonucleotide, the linking reagent is streptavidin, and the supplemental linking reagent is biotin, the biotin-labeled oligonucleotide can bind to the first of the four biotin-binding sites of streptavidin to form a targeting reagent linked to the linking reagent. The biotin-labeled capture reagent (i.e., the capture reagent linked to the supplemental linking reagent) can then bind to the remaining biotin-binding sites on streptavidin to link the targeting agent to the capture reagent.

[0272] Exemplary targeting reagents and targeting reagent complements are described herein. In embodiments, the targeting reagent and targeting reagent complement are two members of a binding partner pair selected from avidin-biotin, streptavidin-biotin, antibody-hapten, antibody-antigen, antibody-epitope tag, nucleic acid complementary nucleic acid, aptamer-aptamer target, and receptor ligand. In embodiments, the targeting reagent is biotin and the targeting reagent complement is streptavidin. In embodiments, the linking reagent-supplement linking reagent pair is a different binding partner pair from the targeting reagent-targeting reagent complement pair. In embodiments, the linking reagent is avidin or streptavidin and the supplement linking reagent is biotin. In embodiments, the targeting reagent and targeting reagent complement are complementary oligonucleotides.

[0273] In embodiments, the methods of the present invention are applicable to one or more formats in which multiple assay measurements are performed on a single sample. Multiple measurements that can be used in the present invention include, but are not limited to, i) multiple measurements involving the use of multiple sensors; ii) multiple measurements using separate assay domains on a surface (e.g., an array) that is distinguishable based on its position on the surface; iii) multiple measurements involving the use of reagents coated on particles that are distinguishable based on particle characteristics such as size, shape, or color; iv) multiple measurements that generate assay signals that are distinguishable based on optical properties (e.g., absorbance or emission spectrum); or v) multiple measurements based on the temporal characteristics of the assay signal (e.g., time, frequency, or phase of the signal). Exemplary assay formats 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, respectively, which are incorporated herein by reference in their entirety. Further ultra-high sensitivity assay formats include those disclosed in U.S. Patent Application No. 17 / 434,938 filed on 30 August 2021 and U.S. Patent Application No. 62 / 866,512 filed on 25 June 2019, each of which is incorporated herein by reference in its entirety.

[0274] Examples of plate readers include the MESO SECTOR S 600 (www.mesoscale.com / en / products_and_services / instrumentation / sector_s_600) and MESO QUICKPLEX SQ 120 (www.mesoscale.com / en / products_and_services / instrumentation / quickplex_sq_120), both available from Meso Scale Diagnostics, LLC, as well as the plate readers described in U.S. Patent No. 6,977,722 and U.S. Patent Application No. 16 / 929,757, filed July 15, 2020, entitled “Assay Apparatuses, Methods and Reagents,” each of which is incorporated herein by reference in its entirety.

[0275] The user interface techniques described above can also be incorporated into the user interface of an assay system. The assay systems described below allow users to perform assays via a user interface. An example of a user interface incorporated into an assay system for an assay method is described below. In describing the functions of the assay system and its user interface, the terms “system software” or “system” refer to the software that implements the assay system. The user interface can display or visualize the workflow and / or menu item paths.

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

[0277] Advanced Context Menu - A menu of options that depend on a specific context (such as the screen in progress, substep, or screen state) for advanced users.

[0278] Assay method - a method for carrying out the assay, including but not limited to: 1. the instrument protocol to be performed and the parameters for performing that protocol, 2. the layout of the test plate, 3. the calibrator titration scheme, including the dilution factor, 4. the control layout, and 5. the sample replication scheme.

[0279] Audit Log - A continuous record of automated and user-initiated events that occur in the system and may affect the generated results. This record is used to track problems and ensure proper operation in a managed environment. The audit log is a persistent and immutable log. It contains a subset of information from the instrument log.

[0280] Compatibility Protocols - Protocols are compatible if they share the same basic outline and steps, although dilution ratios, incubation times, wash times, etc., may differ. Protocols are considered compatible if they can be run together on an automated platform during the same startup.

[0281] Completed startup - aborted startup, startup completed with a flag, or startup completed successfully.

[0282] CV - Coefficient of Variation.

[0283] Database Clean - Resets the entire database and restores it to its state at the time of system installation.

[0284] ECL - Electrochemiluminescence. A proprietary format for detecting molecules of biological interest.

[0285] Existing startups - planned startups, aborted startups, startups completed with a flag, or startups that completed successfully.

[0286] Global Product Data (GPD) - Data for a specific item identified by GPI. The same data can be used for multiple items, while GPI allows for data matching to a single specific item. GPD may include information used to identify at least one element, including (i) assay consumables, (ii) one or more test sites within the consumable, (iii) reagents and / or samples used in or applied to the consumable, or (iv) a combination thereof. Furthermore, GPD may be used to distinguish the first test site within a consumable from different test sites within the consumable. GPD may also include lot identification information, lot-specific analytical parameters, manufacturing process information, raw material information, expiration date, calibration data, threshold information, the location of individual assay reagents and / or samples within one or more test sites of the assay consumable, Material Safety Data Sheet (MSDS) information, or a combination thereof. GPD may also include data generated during and / or after assay execution, assay system maintenance information, system consumable promotion information, system and / or consumable technical support information, or one or more analytical tools applicable by the system for analyzing a combination thereof. In addition, the GPD includes identification information and / or configuration information of the consumables, as well as one or more steps of an assay protocol that can be applied by the system in performing an assay using the consumables.

[0287] A test site may also be referred to as a spot. A spot layout may refer, for example, to an array of test sites within a single well of a test plate or assay plate.

[0288] Global Product Identifier (GPI) - A unique identifier designated by a system / instrument / consumable vendor for individual, specific products such as assay consumables. The identifier may consist of any number of components. For consumables such as assay plates, the identifier may be the associated manufacturing barcode.

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

[0290] Instrument Log – A detailed log file that records all actions performed by the system and all failures or error conditions that occurred during those actions. The instrument log is a rolling, cyclical log containing stored information, limited by the amount of memory space allocated to this log file. For example, older entries are overwritten over time.

[0291] Instrument software - software that controls the hardware of an instrument.

[0292] LED - Light-emitting diode. Light source.

[0293] Normal state - If the software is functioning without any errors or warnings, the instrument is considered to be in a normal state. Once the error condition is resolved and / or the warning message is acknowledged, the instrument returns to a normal state.

[0294] The initiation process includes zero or more named samples and one or more assay methods, and the samples are tested according to the information described in the assay method.

[0295] Startup Owner - The user who created the startup program.

[0296] A sample is a general term that includes the analyte, including calibrators, controls, blanks, and unknown substances.

[0297] Sample ID - A unique identifier for each sample.

[0298] Sample layout - Sample position and sample ID on the plate.

[0299] Sample type - The functional type of the sample, such as calibrator, control, blank, or unknown substance.

[0300] Spot layout - The location and name of the analytes within the wells on the plate.

[0301] Step – One of a series of separate, sequential stages progressing toward a goal. A step constitutes a broader stage that may consist of multiple substeps.

[0302] Substep – One of a series of distinct, sequential stages in the progress toward completing a step. Substeps constitute concentrated activities within a step.

[0303] An unexpected barcode – a barcode that differs from what was expected. Consumables may also be considered to have an "unexpected barcode" if the barcode cannot be read.

[0304] User Interface (UI) - A software interface through which the user of an instrument interacts to control and monitor the system.

[0305] UI Warning Events - All warning messages that require user response. The user must correct the error and / or acknowledge the message before proceeding. For example, a UI warning event might indicate that an instrument is in a "Not Ready" state.

[0306] System Event Log - A persistent log of events that occur in software unrelated to the instrument.

[0307] Figure 4 is a flowchart illustrating a first user login user interface for an assay system in one embodiment. In 402, the system software for the assay method can verify that the End User License Agreement (EULA) associated with the assay system has been accepted each time the assay system is started. When the user first starts the system software, the EULA is displayed. A record of the username and date and time is created when the user accepts the agreement. If the user has not previously accepted the agreement, in 404, the EULA is displayed, allowing the user to accept the agreement. In 406, if the user does not accept the agreement, the software closes. In 408, a splash screen is displayed, including system software branding, copyright, legal notices, and software version. The initial login screen requests a username in 410. In one embodiment, the system software can minimize errors caused by entering a username by presenting past usernames used to log in to the system. The user can also enter a new username that has not been used to log in before. After selecting (or receiving) a username in 412, the software prompts the user to enter a password for the username in 414. In one embodiment, the system software may use a biometric authentication method such as facial recognition, voice, and / or fingerprint to log in or verify the login. In another embodiment, the system software may use a badge key card containing information that can be scanned or read via near-field communication. In 416, the system software receives the entered password. Once the username and password are entered, the system software authenticates the user in 418. If the user is successfully authenticated, the user interface proceeds to the start screen in 420. Otherwise, the system software via the user interface prompts the user to try again. In one embodiment, the system software then requires all users to log in in order to access the software.In one embodiment, authentication may be performed via the Microsoft Windows® authentication function, or it may be configured to authenticate via Active Directory. In this first user interface display, the username and password prompts may be displayed, for example, in a single horizontal orientation on a horizontal wheel graphical element 422.

[0308] Figure 5 is a flowchart illustrating how the start user interface screen display is shown in one embodiment. This display screen includes, for example, a list of menu items in two different visual orientations: horizontal and vertical. Thus, for example, more general categories of menu items are displayed on the horizontal wheel 502, and submenu items are displayed on the vertical wheel 504. For example, the START option 506 selected by the logged-in user (Figure 4) is presented on the horizontal wheel 502. A second level of options arising from the START option 406 is presented on the vertical wheel 504. In this example assay method, the start screen is the initial software screen displayed to the user. The workflows that the user can execute are enumerated as options (sub-options) on the selectable vertical wheel. In this example assay method, advanced workflows, rather than general workflows, may be grouped under the advanced menu. In this example assay method, the system workflow options are as follows: When a new launch 508 is created and the user chooses to create a new launch workflow 510, the user can create a launch from scratch or create a launch based on a predefined launch 512. If the user chooses to continue a previously planned or started startup 514, or to continue a previously planned or started startup 516, the software automatically resumes 518 from the last step the user completed in the startup. If the user chooses to view the results of a completed startup 520, or to view a completed startup 522, the software guides the user to a review screen 524. After the user selects any option from the vertical wheel 504, the options on the vertical wheel are added to a new horizontal wheel on the screen. This horizontal wheel allows the user to change their selection. For example, after selecting "Create New," the "Planned Startups" and "Completed Startups" options are moved to the horizontal wheel, changing the user's focus.

[0309] Figure 6 shows the workflow of the Define Assay Method screen in one embodiment. In this example, the software requires an assay method to process the sample under consideration. The processing shown on this screen may be performed in response to the execution of the DEFINE option (Figure 5, 512). The assay method defines the assay on the plate, the plate layout, the maximum number of calibrators, controls, and samples, the dilution amounts of controls, calibrators, and samples, the number of copies of controls, calibrators, and samples, and the instrument protocol (incubation time, blocker execution, and / or others). A default assay method is provided for all kits, and custom assay methods can be created based on the defaults using the system software. In one embodiment, the assay method is distributed in a Global Product Data (GPD) file. The GPD includes the product barcode, the assay, the arrangement of the assay in the wells, lot identification of the kit, plate, antibody, calibrator, and control, the measured concentrations of the calibrator and control, an instrument description of the product processing method, and a recommended plate layout.

[0310] Figure 7 shows a user interface workflow for selecting an assay method in one embodiment. This user interface workflow may follow the selection or execution of a defined assay method, for example, by being selected or executed as an option in the workflow shown in Figure 6. Options under [Assay Method Definition] may include [Assay Method Selection Options], [Sample] Options, and [Confirmation] Options, which are shown, for example, in a horizontal orientation on a horizontal wheel graphical element 702. The selected [Assay Method] option may be highlighted on the horizontal wheel and / or centered more than other unselected options. Sub-level options below the [Assay Method] options may be displayed, for example, in a vertical orientation on a vertical wheel graphical element 704. In this example, there may be three ways in which the user can select an assay method: a) selecting from the most recently used assay methods in the system sorted in reverse chronological order; b) selecting from all available assay methods installed in the system (on this screen, the UI uses multiple wheels, each wheel filtering the results of the next wheel until the last wheel contains results); and c) searching for assay methods installed in the system (this can be done using a free-text search).

[0311] When a user selects one of the sublevel options, the sublevel option moves to the horizontal wheel, allowing the user to change the [Assay Method] selection model. After the user has made an initial selection of the assay method, the user can choose whether to launch only a single assay method or multiple assay methods. With a single assay method, all launched mesoscale diagnostic test plates use the same assay method. With multiple assay methods, there is at least one mesoscale diagnostic test plate for each launched assay method.

[0312] Figure 8 is a flowchart illustrating the workflow of the user interface displayed for defining a sample in one embodiment. Based on the selection of the “Define Sample” option, the options are shown horizontally oriented on a horizontal wheel graphical element 802, which can be stacked, for example, under its parent menu item, the “Define” option. Sublevels of options associated with the “Define Sample” option are shown vertically, for example, on a vertical wheel graphical element 804.

[0313] On the sample [definition] screen, the user can choose whether to import the sample through the user interface or define the sample manually. These options move to the horizontal wheel after the user selects an option. If the user chooses to import a sample from a file, the software presents the sample file that the user can use via the vertical wheel through the user interface. Alternatively, the system can import from a laboratory information system or laboratory information management system.

[0314] The system can also import from a sample management system. When the user chooses to define samples manually, they can define the number of samples to launch. The software automatically assigns sample IDs.

[0315] Figure 9 is a flowchart illustrating the workflow of the user interface displayed to confirm the launch definition in one embodiment. When the "Confirm Launch Definition" option, a submenu item of the "Define" option, is selected, the "Confirm Launch Definition" option appears in the horizontal wheel graphical element, stacked, for example, under the parent menu item, the "Define" option. After the user has defined the launch in a previous step, the system provides a summary of the launch for the user to review and confirm. The following information is displayed to the user: The number of samples being launched. The user may also select the number of samples for which to view sample identifiers (IDs), the number of mesoscale diagnostic plates being launched, the plate layout, and the name of the launch. The system assigns a default name to the launch, which the user can change. Once the user confirms the launch, the system displays a prompt asking the user whether to continue running the launch or return to [Target Launch].

[0316] Figure 10 is a flowchart illustrating the workflow of a user interface displayed to notify the user of completed tasks in one embodiment. The system can guide the user through completing tasks via a user interface (automatic help function) within a wizard. Key logical steps may be categorized as objectives. In this example, the system has three main objectives: Start, where the user gets started and selects what they want to do with the system; Define, where, after the user has selected what they want to do, the wizard guides the user through the user interface to define the necessary information; and Execute, where the system guides the user through the execution of the tasks selected by the user.

[0317] Figure 11 is a flowchart illustrating the workflow of the user interface displayed for the execution / collection option in one embodiment. On this collection screen, the system creates a list of items that the user needs to collect in order to perform the execution. Each item must be marked as a collection 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, the item may optionally be scanned, and the system can verify that it is the correct item, expiration date, lot information. For example, the system may request a barcode scan on the item. This is done using a barcode (GPI), and the GPD is obtained.

[0318] Figure 12 is a flowchart illustrating the workflow of the user interface displayed for the Run / Prepare option in one embodiment. On this preparation screen, the system presents a list of steps required to prepare the items collected in the wheel. For each step in the wheel, the system presents detailed instructions for that preparation step once it has been selected. Detailed preparation steps may include text describing the action, images visually representing the action, videos demonstrating the action, and web content such as web pages providing details or context for the action. The user is prompted to indicate that all preparation steps are complete before proceeding to the next step. The user may also print the preparation steps or complete them using a tablet.

[0319] Figure 13 is a flowchart illustrating the workflow of the user interface displayed for the run / load option in one embodiment. On this load screen, the system displays a list of items to load into the instrument in a wheel format. For each item, the system graphically displays the loading position for the item. The system provides a graphical indication of whether the item has been loaded or is empty. The system verifies that all items have been loaded before proceeding to the next screen.

[0320] Figure 14 is a flowchart illustrating the workflow of the user interface displayed for the run / startup option in one embodiment. This startup screen allows the user to command the system to start the startup, for example, via the startup button UI control. On this screen, the user can also register other users for system update messages. Updates may be distributed, for example, via email, text such as short message service (SMS), social networking applications and / or blogs, and / or other means. Once the user starts the startup, the system proceeds to present a timer showing the estimated time to completion. In one embodiment, the timer has three modes: 1) estimated time in analog clock format, 2) estimated time in digital watch format, and 3) live camera feed of the instrument. The user may also request to stop the startup from an advanced context menu.

[0321] Figure 15 is a flowchart illustrating the workflow of the user interface displayed for the run / unload option in one embodiment. Once startup is complete, the system proceeds to this unload screen. The unload screen presents a list of steps for unloading the system within the wheel. For each item, the system graphically displays the position where the item should be unloaded. The system provides a graphical indication of whether an item is loaded or unloaded. All items must be unloaded before proceeding to the next screen.

[0322] Figure 16 is a flowchart illustrating the workflow of the user interface displayed for the run / review option in one embodiment. On the review screen, the system presents the startup results. These results are automatically exported in file format, sent to the LIMS / LIS system for automatic export, and automatically exported via email. The results are presented and a) viewed graphically as a plate representation. ECL or calculated density is displayed using a luminance scale, where dark / black indicates low results and light indicates high results. A scale is displayed to annotate color luminance numerically. b) The results are also available as a table. This table can be exported in file format, sent to the LIMS / LIS system, and / or via email. The system records abnormal behavior or results in the table, for example, if the temperature during startup is not within a specified range. After the user has finished reviewing the startup data, the user may proceed to [Target Start] to start another startup or view the results.

[0323] Figure 17 is a flowchart illustrating the workflow of the user interface displayed for execution / review options in one embodiment. In one embodiment, the system categorizes tasks that the user can perform into primary workflows and advanced workflows. Primary workflows are those that the user performs routinely and are optimized for ease of execution. Primary workflows are displayed in the wizard's goals and steps. Advanced workflows reside in the advanced context menu and represent workflows that are not performed routinely or are not restricted to the Configuration Manager. The user opens the advanced context menu by clicking the Mesoscale Diagnostic Globe. The advanced context menu items are contained within a vertical wheel with three main groups: functions related to the current screen (context-sensitive items that change depending on the active screen), toggly modules, and functions applicable to all modules, such as software login and logout. On this screen, the advanced menu, which is the selected option, is displayed horizontally on the horizontal graphical wheel, and the sub-options of the advanced menu are displayed vertically on the vertical graphical wheel.

[0324] In one embodiment, the graphical user interface maximizes black space by making the background black, thereby minimizing pixel coloration in the user interface display (e.g., display screen), saving memory, and improving presentation speed. Figure 20 is an exemplary screenshot of a screen displaying a graphical wheel / slider that maximizes screen black space in one embodiment.

[0325] Further screenshot examples consistent with the embodiments described herein are shown in Figures 58–63. Figures 58A–58HH are exemplary non-limiting embodiments of the reader module. Figures 59A–59T are exemplary non-limiting embodiments of the experiment module. Figures 60A–60I are exemplary non-limiting embodiments of the maintenance module. Figures 61A–61Q are exemplary non-limiting embodiments of the administration console module. Figures 62A–P are exemplary non-limiting embodiments of general screenshots applicable to multiple modules of this specification. Figure 63 is an exemplary non-limiting embodiment of the audit trail module. Figures 64A–64RR are examples of non-limiting embodiments of the assay method module.

[0326] Further screenshots consistent with the embodiments described herein are included in U.S. Design Patent Application No. 29 / 675,777, filed on January 4, 2019, titled "Display Screen with Graphical User Interface," which is incorporated herein by reference in its entirety.

[0327] As described above, the user interface of this disclosure, whether used in an assay system or another system, presents the complete trajectory on a single screen of the user interface display, for example, on a graphical wheel, allowing the user to select any item at any level and return from the current path of the selected item, instead of typing or pressing a series of back buttons on a keyboard or another input device. The user interface allows visualization of past decisions, for example, the primary decision and the last n most recent decisions (the history of decisions may be visualized by scrolling through another graphical element, such as a graphical wheel or graphical slider).

[0328] In one embodiment, the graphical user interface minimizes the number of menu choices the user must make to navigate the assay system. For example, the order in which the menu choices are presented may minimize the number of user options.

[0329] In one embodiment, computer processing time can be improved by minimizing the number of options or choices presented to the user and from which input is received. The user interface guides the user to the next step in the application while minimizing the number of choices the user needs to make.

[0330] In other embodiments, certain features described herein can be used to divide one or more problems into different segments for multiple users to solve collaboratively (e.g., sequentially or in parallel). In this regard, the processor may be adapted to receive one or more benchmark inputs (e.g., inputs providing information to support or solutions to larger problems, experiments, assays, etc.). The benchmark inputs can be aggregated and relied upon together to collaboratively solve problems or conduct experiments. Such inputs are methods based on one or more of the following: (a) modules, (b) problems or sub-problems to be solved, (c) devices, (d) physical locations, (e) tools, (f) instruments, or (g) equipment. Furthermore, the processor may 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 an assay), this may include notifying the researcher responsible for performing the experiment that the first user has completed the design of the assay experiment (and thus notifying the researcher that the experiment is ready to be performed), and after the experiment is completed, notifying the first user that the researcher has completed the experiment (e.g., so that the first user can review the results of the experiment). Furthermore, the processor can be adapted to supply an output in response to the response received. As a result, the output can be adapted to be sent to a device communicatively connected to the processor (i.e., interfaced with a component of the material world, a device, etc.) to instruct the device to perform a specific action (e.g., undergo physical movement or physical transformation). In a particular embodiment, the processor triggers responses to these components in the material world as steps in a broader process in which one or more problems are divided into different segments for multiple users to solve, as described above. In addition, certain aspects of these (and other processes 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. These permissions can be based on various levels, including one or more of roles, users, teams, accounts, instruments, equipment, or devices. In this regard, a highly sophisticated set of permissions can be created to establish multiple levels of security for multiple applications, so that access, control, and security can be strictly maintained and controlled in a highly general manner.

[0331] The following discussion provides additional embodiments and implementations of the system presented herein. The user interface system discussed above may be broadly applicable to a variety of applications, including manufacturing environments, test environments, instrumentation environments, experimental environments, and others. In a series of embodiments, the user interface system discussed above may be used to provide a comprehensive biometric system that encompasses software, hardware, test equipment, and all additional necessary features. The following discusses such a comprehensive biometric system. In particular, the following discusses one embodiment of the system discussed herein as a cloud-based platform. For example, the embodiments discussed below with respect to Figures 21-50 may also be implemented via alternative networked hardware and software platforms.

[0332] This specification uses drawings for illustrative purposes only and does not limit the scope of the embodiments described herein. The following description is applicable to a variety of analytical applications, including but not limited to bioanalysis, chemical analysis, and radioanalysis.

[0333] The components shown may include, for example, computer implementation components implemented and / or launched on one or more hardware processors, or computer implementation components coupled with one or more hardware processors. One or more hardware processors may include components such as programmable logic devices, microcontrollers, memory devices, and / or other hardware components that can be configured to perform each of the tasks described in this disclosure. The processors and cloud-based processing systems disclosed in Figures 21-50 may be examples of processor 1110. The coupled memory device may be configured to selectively store instructions that can be executed by one or more hardware processors. The memory devices and cloud-based storage systems disclosed in Figures 21-50 may be examples of storage device 1120. Examples of processors include, but are not limited to, central processing units (CPUs), graphics processing units (GPUs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), cloud-based processing units, other suitable processing components or devices, or one or more combinations thereof.

[0334] Figure 21 shows one embodiment of a cloud-based system that provides seamless integration of other systems, computers, and instruments, such as biomedical instruments, to support and optimize users performing bioanalysis tasks, for example. 21100 is a system boundary around other systems, computers, and instruments that constitute the analytical computing system 21100, either entirely or partially. Here, the operating system of each computer and / or instrument may, in whole or in part, include the analytical computing system 21100 and may include, for example, Windows®, UNIX, Linux, MacOS®, iOS®, Android®, and / or other commercial, open-source, and / or special-purpose operating systems. 21101 is an analytical user environment including one or more servers, desktop computers, laptop computers, tablets, and / or mobile devices, one or more of which may be used with system 21100. One or more analytical user environments 21101 may use the analytical system 21100. 21102 is a support provider environment including one or more servers, desktop computers, laptop computers, tablets, and / or mobile devices, one or more of which can be used in system 21100 to support instruments, consumables, and / or software used by analytical users in the analytical user environment 21101. In 21102, there may be one or more support provider environments using the analytical computing system 21100. 21103 is a consumables provider environment including one or more servers, desktop computers, laptop computers, tablets, and / or mobile devices, one or more of which can be used in analytical computing system 21100 to provide consumables used by users in the analytical user environment 2001, optionally in combination with instrumentation equipment including instrumentation equipment environment 21106. In 103, there may be one or more consumables provider environments using the analytical computing system 21100.

[0335] 21105 is an analytical instrumentation provider environment for an instrumentation provider that can be used in an instrumentation environment 21106, which includes one or more servers, desktop computers, laptop computers, tablets, and / or mobile devices, one or more of which can be used in the analytical computing system 21100 to provide instruments used by users in an analytical user environment 21101, for example, by selling or otherwise transferring them. In 21105, there may be one or more instrumentation provider environments that use the analytical computing system 21100. 21104 is an analytical computing system provider environment for a provider of the analytical computing system 21100, which includes one or more servers, desktop computers, laptop computers, tablets, and / or mobile devices, one or more of which can be used in system 211000 to manage business interactions with the analytical computing system 21100 used by analytical users in an analytical user environment 2001. Each of the “providers” associated with the environments in 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, among any one of the “providers” herein. 21106 is an instrumentation environment including one or more instruments, each having at least one computer, which in one practical form may be at least partially used by an analytical computing system 21100 to initiate a test on a sample for a user in an analytical user environment 21101.21107 is a cloud platform utilized to connect (e.g., bidirectionally) some or all of the computers in an analytical computing system 21100, which has a common computing, software services, and data architecture in a single practical form, through computers, networking, and software, so that data can be collected and shared by any computer having the relevant software in the analytical computing system 21100, provided that a specific computer with the relevant software in the analytical computing system 21100 is located securely around the world. Here, in a preferred embodiment, the cloud platform 21107 is hosted by a public cloud provider that provides a shared computing environment, such as Amazon® Web Services, Google® Cloud, or Microsoft® Azure. In other embodiments, the cloud platform 21107 may be hosted by an analytics computing system provider at 21104, or self-hosted by an analytics user environment that is a user of the analytics computing system 21100, or hosted by a private cloud provider that provides a dedicated computing environment, such as Oracle® Cloud, IBM® Cloud, rack space, or others, or it may be hosted by a public cloud, private cloud, self-hosted, or analytics computing system provider 21104. All communication with the cloud platform 21107 may be conducted through a preferred embodiment of a secure communication protocol such as HTTPS to encrypt all communication between the sender and receiver.However, insecure communication protocols such as Hypertext Transfer Protocol Secure (HTTPS) may be optionally used in either secure or insecure case connection technologies, such as Ethernet for local area networks (LANs), metropolitan area networks (MANs), and / or wide area network (WAN) configurations, and / or Wi-Fi, Bluetooth, and / or other similar technologies for distributed LANs. Additionally, the analytical computing system 21100 can be fully deployed on a single computer so that all operations of the analytical computing system 21100 occur on that computer, and the only external communication occurring between the computer and associated software is initiated outside of the analytical computing system 21100.

[0336] Figure 22 is an embodiment of the cloud-based system shown in Figure 21, which provides seamless integration of other systems, computers, and instruments to support and optimize users performing analytical tasks. 21100 depicts the boundary of the analytical computing system, encompassing other systems, computers, and instruments, which in whole or in part include the system bounded by 21100. 21101 is an analytical user environment, including one or more servers, desktop computers, laptop computers, tablets, and / or mobile devices, one or more of which may be used in the analytical computing system 21100. Administrator computers 22202 include one or more computers with software used by system administrators to manage the use of system 21100 by users within the analytical user environment 21101 through services and data storage / retrieval provided by the cloud platform 22223. Analytical user computers 22203 include one or more computers with software used to perform analytical tasks by users in the analytical user environment 21101 through services and data storage / retrieval provided by the cloud platform 22223. The data integration computer 22204 includes one or more computers equipped with software used to integrate (bidirectionally) other business systems 22224 in the analytical user environment 21101, and the analytical computing system 21100 provides services to the analytical user business systems 22224 through services and data storage / retrieval provided by the cloud platform 22223.The analytical user business system 22224 can be hosted internally, externally, and / or in any combination of internal and external to the analytical user environment 21101, and may optionally include one or more computer systems equipped with software, for example, a laboratory information system (LIMS), data analysis applications, data visualization applications, data reporting applications, business productivity applications, relational and / or non-relational databases, a file server, and / or any other systems that provide access to the data of the analytical computing system 21100 to users who directly use the analytical computing system 21100, users who do not directly use the analytical computing system 21100, and / or one or more other computer systems included in the business system 22224 that do not have a direct interface with the analytical computing system 21100.

[0337] The support provider environment 21102 comprises users of the analytical computing system 21100, users of consumables from consumable providers, and / or support providers for instrumentation in the instrumentation environment 21106, and includes one or more servers, desktop computers, laptop computers, tablets, and / or mobile devices, one or more of which can be used in the analytical computing system 21100 to support instruments, consumables, and / or software used by analytical users in the analytical user environment 21101.

[0338] The support user computer 22206 includes one or more computers having software provided to users associated with the support provider environment 21102, which, among other things, can monitor, manage, and / or report on activity on the analytical computing system 21100 through services and data storage / retrieval provided by the cloud platform 22223. The support data integration computer 22207 includes one or more computers having software and / or firmware used to integrate other support business systems 22208 into the support provider environment 21102, and the analytical computing system 21100 provides services for the support business systems 22208 through services and data storage / retrieval provided by the cloud platform 22223. The support operations system 22208 may be hosted internally, externally, and / or in any combination of internal and external to the support provider environment 21102, and may optionally include one or more computer systems equipped with software (for example, customer relationship management, enterprise data systems, data analysis applications, data visualization applications, data reporting applications, business productivity applications, relational and / or non-relational databases, file servers, and / or any other systems that provide access to data in the analytical computing system 21100 to users who directly use the support user computer 22206 and users who do not directly use the support user computer 22206), and / or one or more other computer systems included in the support operations system 22208 that do not have a direct interface with the analytical computing system 21100.

[0339] The consumables provider environment 21103 is a consumables provider environment including one or more servers, desktop computers, laptop computers, tablets, and / or mobile devices, one or more of which can be used in the analytical computing system 21100 for providing consumables to users in the analytical user environment 21101, which can optionally be used in combination with instrumentation in the instrumentation environment 21106 to provide consumables to users in the analytical user environment 21101, and optionally with instruments in the instrumentation environment 21106. The consumables information upload computer 22210 includes one or more computers having software used to distribute consumables information about consumables provided from the consumables provider business system 22211 to the analytical computing system 21100 through services and data storage provided by the cloud platform 22223. As used herein, consumables information may include, but is not limited to, global product data (GPD). The consumables provider business system 22211 can be hosted internally, externally, and / or in any combination of internal and external to the consumables provider environment 21103, and may optionally include one or more computer systems equipped with software (for example, customer relationship management, enterprise data systems, data reporting applications, business productivity applications, relational and / or non-relational databases, file servers, and / or any other systems that support business operations to support the distribution of consumables information to the analytical computing system 21100 for consumables providers), or one or more computer systems that are not used at all in the distribution of consumables information to the analytical computing system 21100.

[0340] The analytical computing system provider environment 21104 is an analytical computing system provider environment for providers of the analytical computing system 21100, and includes one or more servers, desktop computers, laptop computers, tablets, and / or mobile devices, one or more of which can be used with the analytical computing system 21100 to provide the analytical computing system 21100 to users of the analytical user environment 21101 and instrumentation equipment of the instrumentation equipment environment 21106, as well as to various providers of 21102, 21103, and 21105. Here, the account information upload computer 22213 includes one or more computers equipped with software used to prepare and control the use of the analytical computing system 21100 by users in the analytical user environment 21101 and the instrumentation equipment of the instrumentation equipment environment 21106, through services and data storage provided by the cloud platform 22223. The Computing System Provider business system 22214 can be hosted internally, externally, and / or in any combination of internal and external to the Analytical Computing System Provider environment 21104, and may optionally include one or more computer systems equipped with software, such as, for example, customer relationship management, enterprise data systems, data reporting applications, business productivity applications, relational databases and / or non-relational databases, file servers, and / or 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 are not used at all in the preparation and control of the use of the Analytical Computing System 21100.

[0341] The instrumentation provider environment 21105 includes one or more servers, desktop computers, laptop computers, tablets, and / or mobile devices, one or more of which can be used in the analytical computing system 21100 for instrumentation provider to users in the analytical user environment 21101, optionally as instrumentation in the instrumentation environment 21106 for processing samples under test, and optionally used with one or more consumables provided by the consumables provider environment 21103. The instrument information upload computer 22216 includes one or more computers having software used to distribute instrument information about instrumentation provided from the instrumentation provider business system 22217 to the analytical computing system 21100 through services and data storage provided by the cloud platform 22223. The instrumentation provider business system 22217 can be hosted internally, externally, and / or in any combination of internal and external to the instrumentation provider environment 21105, and may optionally include one or more computer systems equipped with software, for example, customer relationship management, enterprise data systems, data reporting applications, business productivity applications, relational databases and / or non-relational databases, file servers, and / or other systems that support business operations for the instrumentation provider, support the distribution of instrument information to the analytical computing system 21100, or are not used at all in the distribution of instrument information to the analytical computing system 21100.

[0342] The instrumentation environment 21106 includes one or more instruments, each instrument being one of an individual operating instrument 22221, a linked operating instrument 22222, or a workflow auxiliary instrument 22226 provided by the instrumentation provider environment 21105, which can be utilized by a user in the analysis user environment 21101 to process a sample in connection with consumables provided by the consumable provider environment 21103 to generate data for analysis by a user in the analysis user environment 21101, and the individual operating instrument 22221 provides integration between the individual operating instrument 22221 and the analysis computing system 21100 through services and data storage provided by the cloud platform 22223, and optionally provides operational control for the individual operating instrument 22221. The computer 22219 may have a collaborative operating instrument 22222, which may also have a collaborative operating instrument computer 22220 that provides integration between the collaborative operating instrument 22222 and the analytical computing system 21100 through services and data storage provided by the cloud platform 22223, and optionally provides operational control for the collaborative operating instrument 22222, and the workflow auxiliary instrument 22226 may have a workflow auxiliary instrument computer 22225 that provides integration between the workflow auxiliary instrument 22226 and the analytical computing system 21100 through services and data storage provided by the cloud platform 22223, and optionally provides operational control for the workflow auxiliary instrument 224. Examples of individual operating instruments 22221 include, but are not limited to, plate readers, plate washers, plate incubators, plate shakers, plate incubator shakers, pipetting systems, or other types of instruments used for analytical sample testing. The linked control instrument 22222 can combine some or all of the functions provided by one or more individual control instruments 22221 into an integrated platform that automates the execution of individual operations of the individual control instruments 22221, thereby eliminating the need for the user to perform various individual operations of the individual control instruments 22221.The workflow auxiliary instrument 22226 can provide support to a user testing an assay on a sample in the instrumentation environment 21106 using either the individual operating instrument 22221 and / or the linked operating instrument 22222. This support includes, but is not limited to, collecting various consumables stored at different physical locations and potentially different temperatures, preparing consumables used in processing one or more assays, and / or guiding the user through the overall assay steps using one or more of the individual operating instruments 22221. Alternatively, the consumable provider environment analysis user app 21103 can assist with other tests in addition to, or instead of, the assay tests and / or plate-based tests described herein.

[0343] The instrumentation in the instrumentation environment 21106 may include zero or more individual operating instruments 22221, each having a corresponding individual operating instrument computer 22219; zero or more linked operating instruments 22222, each having a corresponding linked operating instrument computer 22220; and / or zero or more workflow auxiliary instruments 22224, each having a corresponding workflow auxiliary instrument computer 22225. A preferred embodiment for the instrumentation environment 21106 includes providing an analytical computing system 21100 with a separate computer that integrates the zero or more individual operating instruments 22221, zero or more linked operating instruments 22222, zero or more workflow auxiliary instruments 22224, zero or more individual operating instrument computers 22219, zero or more linked operating instrument computers 22220, and zero or more workflow auxiliary instrument computers 22225 through services and data storage provided by the cloud platform 22223.

[0344] Figure 23 shows one embodiment of the system architecture for a cloud platform 22223 as part of an analytical computing system 21100 (Figure 21), which provides a common computing, software services, and data architecture so that data is collected and shared by any computer around the world having the relevant software. Here, one or more service servers 23302 provide a scalable, robust, and high-performance computing and related software platform and support services specific to the analytical computing system 21100 for acquiring, storing, transferring, and / or transforming data related to the use of the analytical computing system 21100. One or more database servers 23309 (including, for example, one or more team databases 23310 and one or more system databases 23311) provide a scalable, robust, and high-performance computing and associated software platform through its preparation for use and use for one or more structured databases used to store and / or retrieve data generated by and / or used by the analytical computing system 21100, and for storing and / or retrieving data generated and / or used by the analytical computing system 21100. The database technology may be inherently relational, such as SQL Server, Oracle, MySQL, Postgres, Aurora and / or other similar relational database technologies, and / or may be inherently non-relational, such as DynamoDB, MongoDB and / or other similar non-relational database technologies.One or more bulk data servers 23315, which may include system content 23312, instrument content 23313, and consumable content 23314, provide a scalable, robust, high-performance computing and associated software platform for storing and retrieving file-based data provided for use with and / or generated through the use of the analytical computing system 21100. In one embodiment, the service server 23302 is associated with an administrator 23303 which includes a logical collection of services, namely, a logical collection of services that support the management of the use of the analytical computing system 21100; a dashboard 23304 which includes a logical collection of services that support the monitoring and control of the use of the analytical computing system 21100; an upload 23305 which includes a logical collection of services that support the uploading of consumables and instrument information to the analytical computing system 21100; a system 23306 which includes a logical collection of services that support various non-user-specific functions related to the overall use of the analytical computing system 21100; an application 23307 which includes a logical collection of services that support typical scientific use of the analytical computing system 21100 by analytical users; and an authentication 23308 which includes a logical collection of services that support secure login to and logout from the analytical computing system 21100. In one practical application, the service server 23302 is a readily scalable computing infrastructure consisting of one or more servers represented by the service server 23302, where, in a preferred embodiment, each server deploys all logical collections of services 23303, 23304, 23305, 23306, 23307, and 23308, and a load balancer enables the service requests to be evenly distributed across one or more servers represented by the service server 23302 to optimize user interaction.This load balancing technique can be implemented, for example, when the logical collection of services 23303, 23304, 23305, 23306, 23307, and 23308 is designed using a RESTful (Representation State Transfer) design pattern, i.e., when each service provided is stateless, i.e., does not store or retain data, and therefore any request made on the service can be satisfied by any available server, which deploys the service to service server 23302 based on the demand at the time of the request. To support the optimal deployment and operation of the logical collection of services 23303, 23304, 23305, 23306, 23307, and 23308 on one computer or many computers, in a preferred embodiment, these services are built on a distributed object platform, such as the Java Platform Enterprise Edition, and can support cross-platform computing architectures, .NET Framework for Windows only computing architectures, or other similar distributed object platforms, or can leverage one or more combinations of these distributed object platforms. The database server 23310 may include one or more databases, for example, a team database 23310 and a system database 23311. The team database 23310 is adapted to store information, data, and / or metadata related to teams (e.g., team name, members, permissions, etc.). The system database 23111 may include files, data, and / or other information related to system functions. Furthermore, the bulk data server 23315 may include various contents, for example, system content 23312 (e.g., data or content related to system functions, etc.), instrument content 23313 (e.g., instrument type, parameters, etc.), and consumables content 23314 (e.g., consumable type, quantity, etc.).

[0345] Figure 24 shows one embodiment of an administrator running administrator application software 24402 using administrator computer 24401, which invokes management functions provided by the analytical computing system 21100 through services provided through the cloud platform 22223. As considered herein, the administrator application software may use the above-described MUI to facilitate user access to the provided functions. Thus, embodiments of the systematic user interface control system 1102 may be provided by a combination of administrator computer 24401 and the cloud platform 22223. As an example, one or more service servers 24411 may provide various functions such as authentication, one or more other management functions (e.g., functions for uploading data 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 a dashboard. In this embodiment, the administrator application 24402 may run on the administrator computer 24401 via a separate application installed on the administrator computer 24401, or it may be accessed via an internet browser installed on the administrator computer 24401, pointing to a uniform resource locator (URL) having a website portion of services provided by the cloud platform 22223, which is logically organized with the administrator 24408, but is not limited to such organization. In one embodiment, the first interaction between the administrator and the cloud platform occurs by performing authentication 24404 through the use of the administrator application 24402 requesting a login service, for example via the user manager 1056 of the systematic user interface control system 1102, via the service link 24403, with appropriate authentication information, which may include, for example, a unique username and password and / or metrics identifier, and any or required additional authentication input, commonly referred to as two-factor authentication, which has been previously configured for use by the administrator.In this embodiment, the login service obtains encrypted user credentials from the system database 24406 via service link 24405, allowing the administrator to access and manage the analytical computing system 21100. The login verifies that data stored in the system database 24406 is updated via service link 24407, enabling tracking of the analytical computing system 21100's usage. The administrator can also reset their own password via the administrator app 24402 via service link 24403, and perform authentication 24404 if they forget or do not know their password. The password reset updates data stored in the system database 24406 via service link 24407, enabling tracking of the analytical computing system 21100's usage. The administrator can also configure additional authentication inputs via the administrator app 24402 through service link 24403 to perform authentication 24404, and retrieve and modify the configuration of additional authentication inputs to the system database 24406 via service link 24405. Configuration changes update the data stored in the system database 24406 via service link 24407 to track the usage of the analytical computing system 21100. After the administrator is authenticated upon login, the administrator can use the services provided by administrator 24403 via service link 24407 to perform management functions of the analytical computing system 21100. These services, as needed, use service link 24407 to create, read, update, and / or delete data stored in the system database 24406, for example, via the data storage manager 1064. The use of these services creates and updates data stored in the system database 24406 via service link 24407 to track the usage of the analytical computing system 21100.Additionally, an administrator performing the management functions of the analytics computing system 21100 provided by the administrator app 24402 can create one or more new user groups, whose use of the analytics computing system 21100 is conducted through the shared team database 24414 via service link 24413, and can also create a new database server 24415 via service link 24412 to add a new team database 24414 to optimize the performance of the database server 24415. Finally, the administrator can log out of their current use of the analytics computing system 21100 via the administrator app 24402 through service link 24403. The logout service of authentication 24404 updates the administrator's login information in the system database 24406 via service link 24409, and the logout updates the data stored in the system database 24406 via service link 24407 to track the usage of the analytics computing system 21100. The analytical computing system 21100 may include one or more service servers 24411. These servers are adapted to host various applications and / or modules, including system modules, application modules, authentication modules, administration modules, dashboard modules, and upload modules. In one embodiment, authentication and administration modules enable users to communicate with the system database 24406 and / or team database 24414 through an administrator app 24402, for example, via one or more service links.

[0346] Figure 25 shows one embodiment of an analysis user running analysis user application software 25503 using an analysis user computer 25502, which invokes analysis functions provided by the analysis computing system 21100 through services provided through the cloud platform 22223. As considered herein, the analysis user application software 25503 may use the above-described MUI to facilitate user access to the provided functions. Thus, embodiments of the systematic user interface control system 1102 may be provided by a combination of the analysis user computer 25502 and the cloud platform 22223. In this embodiment, the analysis user application 25503 may run on the analysis user computer 25502 via a separate application installed on the analysis user computer 25502, or it may be accessed via an internet browser installed on the analysis user computer 25502 by pointing to a URL having a website portion of the services provided by the cloud platform 22223 logically organized in application 25509, but is not limited to such organization. In one practical application, the first interaction between the analytics user and the cloud platform 22223 is performed by authentication 25505 using appropriate authentication information, which may include a unique username and password, and / or other information such as biometric identification, and which may include any or required additional authentication inputs, commonly referred to as two-factor authentication, configured previously by the administrator, using the analytics user application 25503 which requests a login service via service link 25504. Here, the login service retrieves the user's encrypted authentication information from the system database 25507 via service link 25506 and verifies that the analytics user can access and use the analytics computing system 21100, and by logging in, update data stored in the system database 25507 via service link 25506 and track the usage of the analytics computing system 21100.The analysis user can also reset their password via the analysis user app 25503 through service link 25504, and perform authentication 25505 if they have forgotten or do not know their password. Password reset updates the data stored in the system database 25507 via service link 25506 to track the usage of the analysis computing system 21100. The analysis user can also configure additional authentication inputs via the analysis user app 25503 through service link 25504 to perform authentication 25505, and retrieve and modify the configuration of additional authentication inputs to the system database 25507 via service link 25506. Configuration changes update the data stored in the system database 25507 via service link 25506 to track the usage of the analysis computing system 21100. After the analysis user is authenticated upon login, the analysis user can use the services provided by application 25509 via service link 25508 and the analysis user app 25503 to perform the analysis functions provided by application 25509. Here, these services, as needed, use service link 25510 to create, read, update, and / or delete data stored in team database 25511, and also use these services to create and update data stored in system database 25507 via service link 25510, tracking the usage of the analytical computing system 21100. Finally, the analytical user can log out of use of the analytical computing system 21100 via the analytical user app 25503 through service link 25504, ending their current use of the analytical computing system 21100. The authentication logout service 25505 updates the analytical user's login information in system database 25507 via service link 25506, and the logout updates the data stored in system database 25507 via service link 25506, tracking the usage of the analytical computing system 21100.

[0347] Figure 26 shows one embodiment of the data integration computer 26602 that launches the data integration application software 26603, which performs data integration functions provided by the analytical computing system 21100 through services provided via the cloud platform 22223 between the analytical computing system 21100 and, optionally, computing systems that are not part of the analytical computing system 21100. As considered herein, the data integration application software 26603 may use the above-described MUI to facilitate user access to the functions provided. Thus, embodiments of the systematic user interface control system 1102 may be provided by a combination of the data integration computer 26602 and the cloud platform 22223. The data integration application 26603 may be provided as part of the analytical computing system 21100 and / or by the analytical user or a person working with the analytical user. In one practical application, the first interaction for the data integration application 26603 with the cloud platform 22223 is to request a login service via service link 26604 to perform authentication 26605, where appropriate credentials may include any or required additional authentication inputs, commonly referred to as two-factor authentication, configured by the administrator and configured for prior use by the administrator, preferably including a unique username and password. Here, the login service can obtain encrypted credentials for the data integration application 26603 from the system database 26607 via service link 26606, and the login verifies that the data integration application 26603 can access and use the analytical computing system 21100 to update data stored in the system database 26607 via service link 26606 and track the usage of the analytical computing system 21100.After the data integration app 26603 is authenticated upon login, the analytical user can perform analytical functions provided by application 26609 using services provided by application 26609 through the use of the data integration app 26603 via service link 26608. These services, as needed, use service link 26610 to create, read, update, and / or delete data stored in the team database 26611, and also use these services to create and update data stored in the system database 26607 via service link 26610, and the usage of the analytical computing system 21100 is tracked. Finally, the data integration app can log out of its use of the analytical computing system 21100 via the data integration app 26603 through service link 26604, ending its current use of the analytical computing system 21100. The logout service of authentication 26605 updates the login information of the data integration application in the system database 26607 via service link 26606. Logout updates the data stored in the system database 26607 via service link 26606, tracking the usage of the analytical computing system 21100.

[0348] Figure 27 shows one embodiment of a user monitoring the use of the analytical computing system 21100 using a support user computer 27702, launching monitoring user application software 27703 to perform monitoring functions provided by the analytical computing system 21100 through services provided via the cloud platform 22223. As considered herein, the monitoring user application software 27703 may use the above-described MUI to facilitate user access to the provided functions. Thus, embodiments of the systematic user interface control system 1102 may be provided by a combination of the support user computer 27702 and the cloud platform 22223. In this embodiment, the monitoring user application 27703 may run on the support user computer 27702 via a separate application installed on the support user computer 27702, or it may be accessed via an internet browser installed on the support user computer 27702 by pointing to a URL having a website portion of the services provided by the cloud platform 22223 logically organized in the dashboard 27709, but is not limited to these. In one practical application, the first interaction between the support user computer and the cloud platform is performed by authentication 27705 using a monitoring user application 27703 that requests a login service via service link 27704, using appropriate credentials which may include a unique username and password and / or metrics identifier, and which may include any or necessary additional authentication inputs, commonly referred to as two-factor authentication, configured previously for use by the administrator. Here, the login service retrieves the user's encrypted credentials from the system database 27707 via service link 27706 and verifies that the monitoring user can access and monitor the analytical computing system 21100, and that by logging in, can update data stored in the system database 27707 via service link 27706 and track the usage of the analytical computing system 21100.The monitoring user can also reset their password via the monitoring user app 27703 through service link 27704, perform authentication 27705 if they have forgotten or do not know their password, and update the data stored in the system database 27707 via service link 27706 to track the usage of the analytical computin...

Claims

1. It is a laboratory collaboration system, It is equipped with a laboratory collaboration device, and the laboratory collaboration device is A networking component configured to transmit and receive information over a network, A non-temporary computer-readable storage medium configured to store software instructions, At least one processor, Establish one or more network connections with one or more laboratory instruments and / or one or more user devices, Obtain an experimental protocol that includes the multiple experimental steps to be performed. In response to a first command request, a first command is provided for the execution of the first experimental step among the plurality of experimental steps. Upon receiving a notification that the first experimental step has been completed, A laboratory collaboration system comprising: at least one processor configured to execute a software instruction in order to provide a second instruction for carrying out a second experimental step among a plurality of experimental steps in response to a second instruction request.

2. The laboratory collaboration system according to claim 1, wherein obtaining the experimental protocol includes obtaining a stored experimental protocol.

3. The laboratory collaboration system according to claim 2, wherein obtaining the stored experimental protocol includes obtaining the stored experimental protocol from a stored list of experimental protocols.

4. The laboratory collaboration system according to claim 3, wherein the stored list is prioritized.

5. The stored list is, Maximizing throughput, Minimizing the completion of a single experiment, and / or The laboratory collaboration system according to claim 4, which is prioritized according to at least one of the priority coefficients.

6. The laboratory collaboration system according to claim 2, wherein retrieving the stored experimental protocols includes retrieving a plurality of stored experimental protocols according to the ability of one or more laboratory instruments to identify each other.

7. The aforementioned identified ability is Instrument functionality, Instrument capacity, Instrument processing time, Instrument movements, Instrument response time, Instrument parameters, and The laboratory collaboration system according to claim 6, comprising one or more of the following: compatibility of consumables for instruments.

8. The aforementioned identified ability is The remaining capacity of the instrument, Instrument supply levels, Instrument availability, Instrument operating time, and The laboratory collaboration system according to claim 6, comprising one or more of the following: instrument positions.

9. The aforementioned at least one processor, Generate multiple instructions corresponding to the multiple stored experimental protocols, The laboratory collaboration system according to claim 6, further configured to provide the plurality of commands to the one or more laboratory instruments in an interleaved manner on the one or more laboratory instruments.

10. The aforementioned at least one processor, A second experimental protocol is acquired while executing the instructions related to the aforementioned experimental protocol. To generate additional instructions for carrying out the steps related to the second experimental protocol described above, The laboratory collaboration system according to claim 1, further configured to provide the additional commands to one or more laboratory instruments so that the additional commands are executed in an interleaved manner along with the execution of the commands relating to the experimental protocol.

11. The aforementioned at least one processor, Access a conversion library selected from among multiple conversion libraries, each containing machine instructions that correspond to a type of laboratory instrument and are configured to execute a corresponding assay protocol step on the laboratory instrument corresponding to each of the said laboratory instrument types, based on the identified instrument type of one or more laboratory instruments. The laboratory collaboration system according to claim 1, further configured to generate the first instruction according to the conversion library.

12. The type of the aforementioned laboratory instrument is, Instrument manufacturers, Instrument model, Instrument software version, Instrument hardware version, Instrument adjustments, The functionality of the instrument, and The laboratory collaboration system according to claim 11, comprising at least one of the following: an instrument identifier.

13. The laboratory collaboration system according to claim 1, wherein obtaining the experimental protocol includes obtaining the experimental protocol in accordance with input via one or more user devices.

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

15. The laboratory collaboration system according to claim 1, wherein the instructions are provided in at least one of visual, textual, and audible formats.

16. The laboratory collaboration system according to claim 1, wherein the indication that the first experimental step has been completed is received from a user device operating a graphical user interface via one or more network connections.

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

18. The second command request is received from a second instrument among the one or more instruments, after the indication that the first experimental step has been completed, in response to the second instrument identifying the assay plate. The laboratory collaboration system according to claim 16, wherein the second instruction is generated in accordance with the correspondence between the second experimental step and the second instrument.

19. The first command request is received from a first instrument among the one or more instruments in response to the first instrument identifying the assay plate. The laboratory collaboration system according to claim 1, wherein the first command is generated in accordance with the correspondence between the first experimental step and the first instrument.

20. The aforementioned correspondence indicates the capability of the first instrument to perform the first experimental step. The laboratory collaboration system according to claim 18, wherein the first instruction includes a command for carrying out the first experimental step.

21. The laboratory collaboration system according to claim 20, wherein the command for performing the first experimental step causes the first instrument to perform an action associated with the first experimental step.

22. The capability of the first instrument is Online / Offline status, Usage status, Functional status, and The laboratory collaboration system according to claim 20, defined according to at least one of the availability status of consumables.

23. The aforementioned correspondence indicates a lack of capability of the first instrument used to perform the first experimental step. The laboratory collaboration system according to claim 18, wherein the first instruction does not include a command for carrying out the first experimental step.

24. The laboratory collaboration system according to claim 1, wherein the experimental protocol is an assay protocol performed on an assay plate.

25. The laboratory collaboration system according to claim 24, wherein the assay protocol is an electrochemiluminescence protocol.

26. The one or more laboratory instruments described above, Electrochemiluminescence leader, Assay plate washing machine, Assay plate shaker, Assay plate incubator, and The laboratory collaboration system according to claim 1, comprising at least one of the following: a pipette.

27. It is a laboratory collaboration system, It is equipped with a laboratory collaboration device, and the laboratory collaboration device is A networking component configured to transmit and receive information over a network, A non-temporary computer-readable storage medium configured to store software instructions, At least one processor, Establish one or more network connections with one or more laboratory instruments or one or more user devices, Obtain multiple experimental protocols, each experimental protocol comprising a corresponding set of experimental steps performed on a corresponding assay plate. The first identification of the first assay plate is received from the first instrument among the one or more instruments. In accordance with the first identification, a first experimental protocol is selected from the plurality of experimental protocols. In accordance with the capabilities of the first instrument, a first experimental step is selected from the first experimental protocol. A laboratory collaboration system comprising: at least one processor configured to provide a first instruction to the first instrument and execute the software instruction to carry out the first experimental step on the first assay plate.

28. The laboratory collaboration system according to claim 27, wherein the command for carrying out the first experimental step causes the first instrument to perform an action associated with the first experimental step.

29. The aforementioned software instruction, The second identification of the second assay plate is received from the second instrument among the one or more instruments. In accordance with the second identification described above, a corresponding second experimental protocol is selected from the plurality of experimental protocols. In accordance with the capabilities of the second instrument, a second experimental step is selected from the corresponding second experimental protocol. The laboratory collaboration system according to claim 27, further configured to provide a second command to the second instrument to carry out the second experimental step on the second assay plate.

30. The laboratory collaboration system according to 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 collaboration system according to claim 30, wherein the first experimental protocol is different from the second experimental protocol.

32. The aforementioned software instruction, The second identification of the first assay plate is received from the second instrument among the one or more instruments. In accordance with the second identification, the first experimental protocol is selected from the plurality of experimental protocols. In accordance with the capabilities of the second instrument, a second experimental step is selected from the first experimental protocol. The laboratory collaboration system according to claim 27, further configured to provide a second command to the second instrument to carry out the second experimental step on the first assay plate.

33. The aforementioned software instruction, In accordance with the second capability of the first instrument, a second experimental step is selected from the first experimental protocol. The laboratory collaboration system according to claim 27, further configured to provide a second command to the first instrument to carry out the second experimental step on the first assay plate.

34. The aforementioned software instruction, The laboratory collaboration system according to claim 27, further configured to provide a guide command to a first user device, wherein the guide command includes a list of assay plate identifiers and a list of corresponding instrument identifiers.

35. The laboratory collaboration system according to claim 34, wherein the list of corresponding instrument identifiers includes instrument types corresponding to assay plate identifiers.

36. The laboratory collaboration system according to claim 34, wherein the list of corresponding instrument identifiers includes specific instruments corresponding to the assay plate identifiers.

37. The laboratory collaboration system according to claim 34, wherein the software instruction is further configured to determine the guide instruction according to a load balancing criterion.

38. The aforementioned load balancing criteria are Instrument availability, Operator availability, Availability of consumables, and The laboratory collaboration system according to claim 37, comprising at least one of the following: the efficiency of the equipment.

39. Receiving notification of the change in the load balancing criteria, The laboratory collaboration system according to claim 37, further comprising updating the guide instructions in accordance with the changes to the load balancing criteria.

40. The first experimental step described above is, Washing step, Additional steps, Incubation step, and The laboratory collaboration system according to claim 27, comprising at least one of the following steps: reading, etc.

41. The first experimental step includes a reading step, and the software instruction is, Obtain the reading from the first instrument, The laboratory collaboration system according to claim 36, further configured to transmit the reading results to a first user device.

42. The laboratory collaboration system according to claim 27, wherein obtaining the plurality of experimental protocols includes obtaining the plurality of experimental protocols from a plurality of user devices.

43. The laboratory collaboration system according to claim 27, wherein the experimental protocol is an assay protocol performed on an assay plate.

44. The laboratory collaboration system according to claim 43, wherein the assay protocol is an electrochemiluminescence protocol.

45. The one or more laboratory instruments described above, Electrochemiluminescence leader, Assay plate washing machine, Assay plate shaker, Assay plate incubator, and The laboratory collaboration system according to claim 27, comprising at least one of the following: a pipette.

46. It is a laboratory collaboration system, It is equipped with a laboratory collaboration device, and the laboratory collaboration device is A networking component configured to transmit and receive information over a network, A non-temporary computer-readable storage medium configured to store software instructions, At least one processor, Establish one or more network connections with one or more laboratory instruments and / or one or more user devices, Obtain an experimental protocol that includes the multiple experimental steps to be performed. In response to a first command request, the first command is provided to the user via one or more user devices for the execution of the first experimental step among the plurality of experimental steps. Upon receiving a notification that the first experimental step has been completed, A laboratory collaboration system comprising: at least one processor configured to execute the software instructions in order to provide the user with the second instruction via one or more user devices for the execution of the second experimental step of the plurality of experimental steps, in response to a second instruction request.

47. It is a laboratory collaboration system, It is equipped with a laboratory collaboration device, and the laboratory collaboration device is A networking component configured to transmit and receive information over a network, A non-temporary computer-readable storage medium configured to store software instructions, At least one processor, Establish one or more network connections with one or more instruments or one or more user devices, Multiple experimental protocols, each experimental protocol includes a corresponding set of experimental steps, and multiple experimental protocols are obtained. The first instrument among the one or more instruments receives the first identification of the first assay plate. In accordance with the first identification, a first experimental protocol is selected from the plurality of experimental protocols. In accordance with the capabilities of the first instrument, a first experimental step is selected from the first experimental protocol. The first command is provided to the first instrument to perform the first experimental step. A laboratory collaboration system comprising: at least one processor configured to execute software instructions via one or more user devices to provide a second instruction to a user in order to facilitate a second experimental step.

48. It is a laboratory collaboration system, It is equipped with a laboratory collaboration device, and the laboratory collaboration device is A networking component configured to transmit and receive information over a network, A non-temporary computer-readable storage medium configured to store software instructions, At least one processor, Establish one or more network connections with one or more instrument devices, Obtain multiple experimental protocols, each experimental protocol comprising a corresponding set of experimental steps performed on a corresponding assay plate. The first instrument among the one or more instruments receives the first identification of the first assay plate. In accordance with the first identification, a first experimental protocol is selected from the plurality of experimental protocols. A first command is provided to the first instrument to perform the first experimental step on the first assay plate. A laboratory collaboration system comprising: at least one processor configured to execute a software instruction to provide a second instruction to the first instrument in order to perform a second experimental step on the first assay plate.

49. A laboratory-collaborative computer implementation method, which is performed by a laboratory-collaborative device including at least one processor configured to execute software instructions, wherein the method is Establishing one or more network connections with one or more laboratory instruments and / or one or more user devices, Obtain an experimental protocol that includes multiple experimental steps to be performed, In response to a first command request, a first command is provided for the execution of the first experimental step among the plurality of experimental steps. Receiving an indication that the first experimental step has been completed, A computer implementation method comprising: providing a second instruction for carrying out a second experimental step among a plurality of experimental steps in response to a second instruction request.

50. A laboratory-collaborative computer implementation method, which is performed by a laboratory-collaborative device including at least one processor configured to execute software instructions, wherein the method is Establishing multiple network connections with multiple laboratory instruments and / or one or more user devices, Identifying the instrument type corresponding to the aforementioned multiple laboratory instruments, Identifying the capability sets of the plurality of laboratory instruments according to the plurality of instrument types, Obtaining multiple experimental protocols, each of which includes multiple experimental steps to be performed, A computer implementation method comprising generating a plurality of instructions to be provided to a plurality of laboratory instruments in order to carry out the plurality of experimental protocols.

51. Access to multiple conversion libraries, each of which includes machine instructions that correspond to a type of laboratory instrument and are configured to execute a corresponding assay protocol step on the laboratory instrument corresponding to the respective type of laboratory instrument, selected based on the instrument type of the multiple laboratory instruments, The laboratory-cooperative computer implementation method according to claim 50, further comprising generating the plurality of instructions according to the conversion library.

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

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

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

55. The stored list is, Maximizing throughput, Minimizing the completion of a single experiment, and / or The computer implementation method according to claim 54, which is prioritized according to at least one of the priority coefficients.

56. The computer implementation method according to claim 52, wherein retrieving the plurality of stored experimental protocols includes retrieving the plurality of stored experimental protocols in accordance with the identification capabilities of one or more laboratory instruments.

57. The aforementioned identified ability is Instrument functionality, Instrument capacity, Instrument processing time, Instrument movements, Instrument response time, Instrument parameters, and The computer implementation method according to claim 50, comprising one or more of the following: compatibility of consumables for instruments.

58. The aforementioned identified ability is The remaining capacity of the instrument, Instrument supply levels, Instrument availability, Instrument operating time, and The computer implementation method according to claim 50, comprising one or more of the positions of instruments.

59. The type of the aforementioned laboratory instrument is, Instrument manufacturers, Instrument model, Instrument software version, Instrument hardware version, Instrument adjustments, The functionality of the instrument, and The computer implementation method according to claim 50, comprising at least one of the instrument identifiers.

60. The capabilities of the laboratory instrument are Online / Offline status, Usage status, Functional status, and The computer implementation method according to claim 50, defined according to at least one of the availability status of consumables.

61. The computer-assisted method according to claim 50, wherein at least one of the plurality of experimental protocols includes an electrochemiluminescence assay protocol.

62. The one or more laboratory instruments described above, Electrochemiluminescence leader, Assay plate washing machine, Assay plate shaker, Assay plate incubator, and The computer implementation method according to claim 50, comprising at least one of the following: a pipette.

Images