Graphical user interface system for quality control

Abstract

A method for providing guidance through a graphical user interface (GUI) to assist in the completion of one or more steps of an experimental process may include: one or more processors may receive a first command to select an experiment including one or more steps to be performed on an instrument or other device; the one or more processors may further provide a second command to display at least a subset of the one or more steps of the experiment on a UI display; and the one or more processors may further provide a third command to instruct the instrument or other device to at least partially perform one or more steps of the experiment.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 479,068, filed January 9, 2023, which is incorporated herein by reference in its entirety.

[0002] This application relates generally to computers and computer applications, and more particularly to graphical user interfaces and display methods for displaying user-interactive items on a graphical user interface. This application further relates to user interface modules configured to guide a user or operator in preparing and performing one or more experimental procedures, such as assays. [Background technology]

[0003] The present disclosure improves testing, analysis, and processing through integration between instrumentation and equipment associated with processes and software interfaces that are consistent at various process locations in a variety of applications, including, but not limited to, bioanalysis, chemical analysis, radiological analysis, other sciences (e.g., bioscience and bioanalytical work), and industrial processes, leading to the use of instrumentation for scientific testing (e.g., biological testing, bioinstrumentation) and equipment for industrial processing.

[0004] Computer systems and / or applications often utilize a series of menus or the like that are presented to a user to receive input and perform their functions. When a user selects an option or chooses from a list of menu items, the computer system and / or application may perform its function based on the selected option and / or 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 performing its menu-driven function until, for example, 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 displayed on the user interface. Thus, for example, the path of menu items obtained may not be visible at the time the computer system and / or application process is in progress. Furthermore, options for not only the selected path but also the unselected paths may not be visible on the user interface. Therefore, improving the user interface may be desirable.

[0005] Often, instrumentation used in analytical applications (e.g., but not limited to, bioinstrumentation) is used in laboratories. As such, data generated by the instrumentation is stored as data files on a shared network drive for post-processing and import into other electronic systems, i.e., 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 are in regulated environments (e.g., 21 CFR Part 11), which require the generated data to be stored in a manner that ensures it cannot be altered by the end user. These integrations are also 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, it is desirable for the use of the instrumentation and post-processing of the generated data to be performed under a controlled, uniform, unified, and traceable process within a set of closely collaborating end users. This helps to produce consistently accurate supplemental analyses and reports. Use of an instrumentation device for the generation of data for supplemental analyses and reports typically requires an end user to use consumables (e.g., biological consumables, including but not limited to reagents and analytes) with lot-specific information in combination with the sample under test to create reactions that are measured to generate the generated data, and the lot-specific information used to generate the supplemental analyses and reports. Obtaining these consumables requires purchasing them from a provider, who must not only ship the physical consumables to the end user, but also provide lot-specific information for the shipped consumables so that the end user can use the consumables on the instrumentation device and perform desired post-processing. In addition to the normal use of the instrumentation device and associated consumables, there are typically important support functions to ensure that the instrumentation device and / or associated consumables are always functioning optimally for the customer.The level of workflow integration required to optimally perform the collective and collaborative tasks associated with the use of instrumentation by end users is very high and complex. This requires a simple, easy-to-use user interface, making the analytical workflow complex for users. Thus, improved analytical computing systems and user interfaces associated with and including instrumentation and related consumables may be desirable.

[0006] Additional fields beyond instrumentation face similar challenges as those discussed above. For example, various manufacturing settings present challenges with workflow integration, parts tracking, consumables tracking, work-in-progress tracking, process and part production documentation, and all of the problems discussed above with respect to instrumentation. Additionally, the present application provides solutions to areas of consumer need for organization, prioritization, and workflow improvement in, for example, business, office, home, travel, and leisure situations. Other examples exist, and the solutions disclosed herein are not limited to solutions to the problems discussed above. Summary of the Invention [Means for solving the problem]

[0007] In an embodiment, a method is provided, executed by at least one processor, for providing guidance via a graphical user interface (GUI) to assist in the completion of one or more steps of a process. The method includes receiving, by the at least one processor, a first command for selecting an experiment including one or more steps to be performed on an instrument or other device, providing, by the at least one processor, a second command for displaying at least a subset of the one or more steps of the experiment on a UI display, and providing, by the at least one processor, a third command for directing the instrument or other device to at least partially perform one or more steps of the experiment.

[0008] In a further embodiment, a system is provided for providing guidance via a graphical user interface (GUI) to assist in the completion of one or more steps of a process. The system comprises at least one processor, a user input device, and a computer-readable storage medium configured to store a computer application, the at least one processor configured to execute instructions of the computer application for processing. These steps include receiving, by the at least one processor, a first command to select an experiment including one or more steps to be performed on an instrument or other equipment, providing, by the at least one processor, a second command to display, by the at least one processor, at least a subset of the one or more steps of the experiment on a UI display, and providing, by the at least one processor, a third command to direct the instrument or other equipment to at least partially perform one or more steps of the experiment.

[0009] In a further embodiment, a computer-readable storage medium is provided for providing guidance via a graphical user interface (GUI) to assist in the completion of one or more steps of a process. The storage medium is configured to store a computer application, and at least one processor is configured to execute instructions of the computer application. Processing steps of the computer application may include receiving, by the at least one processor, a first command to select an experiment including one or more steps to be performed on an instrument or other equipment, providing, by the at least one processor, a second command to display at least a subset of the one or more steps of the experiment on a UI display, and providing, by the at least one processor, a third command to direct the instrument or other equipment to at least partially perform one or more steps of the experiment.

[0010] In a further embodiment, a method executed by at least one processor for navigating a path of hierarchical menu levels adapted for output to a graphical user interface (GUI) is provided, the method including: providing, by the at least one processor, a first command for a first menu of one or more user-selectable menu items to be displayed on a first portion of a user interface (UI) display; and providing, by the at least one processor, in response to a user selection, a second command for a second menu of one or more user-selectable menu items to be displayed on the first portion of the UI display, wherein at least one of the user-selectable menu items of the first menu is adapted to be displayed on the second portion of the UI display and comprises one or more previously selected and non-previously selected menu items of the hierarchical menu level and is adapted to be viewed simultaneously with the second menu in the first portion, and further wherein the one or more user-selectable menu items of the second menu include a menu item providing for establishing at least one criterion to be applied to one or more experiments.

[0011] In a further embodiment, a method executed by at least one processor for navigating a path of hierarchical menu levels adapted for output to a graphical user interface (GUI) is provided, the method including: providing, by the at least one processor, a first command for a first menu of one or more user-selectable menu items to be displayed on a first portion of a user interface (UI) display; and providing, by the at least one processor, in response to a user selection, a second command for a second menu of one or more user-selectable menu items to be displayed on the first portion of the UI display, wherein at least one of the user-selectable menu items of the first menu is adapted to be displayed on the second portion of the UI display and comprises one or more previously selected and non-selected menu items of the hierarchical menu level and is adapted to be viewed simultaneously with the second menu in the first portion, and wherein the one or more user-selectable menu items of the second menu include a menu item providing at least one option for creating, organizing, and / or aggregating data associated with one or more experiments.

[0012] In a further embodiment, a method executed by at least one processor for navigating a path through hierarchical menu levels adapted for output to a graphical user interface (GUI) is provided, the method including: providing, by the at least one processor, a first command for a first menu of one or more user-selectable menu items to be displayed on a first portion of a user interface (UI) display; and providing, by the at least one processor, in response to a user selection, a second command for a second menu of the one or more user-selectable menu items to be displayed on the first portion of the UI display, wherein at least one of the user-selectable menu items of the first menu is adapted to be displayed on the second portion of the UI display and comprises one or more previously selected and non-previously selected menu items of the hierarchical menu level and is adapted to be viewed simultaneously with the second menu in the first portion, and further wherein the one or more user-selectable menu items of the second menu include a menu item providing at least one option for reviewing and / or analyzing data associated with one or more experiments.

[0013] In a further embodiment, a method executed by at least one processor for navigating a path of hierarchical menu levels adapted for output to a graphical user interface (GUI) is provided, the method including: providing, by the at least one processor, a first command for a first menu of one or more user-selectable menu items to be displayed on a first portion of a user interface (UI) display; and providing, by the at least one processor, in response to a user selection, a second command for a second menu of the one or more user-selectable menu items to be displayed on the first portion of the UI display, wherein at least one of the user-selectable menu items of the first menu is adapted to be displayed on the second portion of the UI display and comprises one or more previously selected and non-previously selected menu items of the hierarchical menu level and is adapted to be viewed simultaneously with the second menu in the first portion, and wherein the one or more user-selectable menu items of the second menu include a menu item providing at least one option for manipulating data associated with one or more experiments.

[0014] Further features, as well as the structure and operation of various embodiments, are described in detail below with reference to the accompanying drawings. [Brief explanation of the drawings]

[0015] [Figure 1] In one embodiment, a method for displaying interactive items in a user interface display for computer user interaction. [Figure 2A] 1 illustrates an exemplary graphical user interface display in one embodiment. [Figure 2B] 1 illustrates an exemplary graphical user interface display in one embodiment. [Figure 2C] 1 illustrates an exemplary graphical user interface display in one embodiment. [Figure 2D]1 illustrates an exemplary graphical user interface display in one embodiment. [Figure 2E] 1 illustrates an exemplary graphical user interface display in one embodiment. [Figure 2F] 1 illustrates an exemplary graphical user interface display in one embodiment. [Figure 2G] 1 illustrates an exemplary graphical user interface display in one embodiment. [Figure 2H] 1 illustrates an exemplary graphical user interface display in one embodiment. [Figure 2I] 1 illustrates an exemplary graphical user interface display in one embodiment. [Figure 2J] 1 illustrates an exemplary graphical user interface display in one embodiment. [Figure 2K] 1 illustrates an exemplary graphical user interface display in one embodiment. [Figure 2L] 1 illustrates an exemplary graphical user interface display in one embodiment. [Figure 2M] 1 illustrates an exemplary graphical user interface display in one embodiment. [Figure 2N] 1 illustrates an exemplary graphical user interface display in one embodiment. [Figure 2O] 1 illustrates an exemplary graphical user interface display in one embodiment. [Figure 2P] 1 illustrates an example of an organizational user interface including an advanced context menu, according to an embodiment of the present disclosure. [Figure 3] FIG. 10 is a flow diagram illustrating a method for interactively displaying interactive items on a user interface display for computer user interaction, in another aspect. [Figure 4] FIG. 1 is a flow diagram illustrating a user login interface for the assay system in one embodiment. [Figure 5]FIG. 10 is a flow diagram illustrating a method for displaying a start user interface screen display in one embodiment. [Figure 6] FIG. 1 illustrates the workflow of a Define Assay Method screen in one embodiment. [Figure 7] FIG. 1 illustrates a user interface workflow for selecting an assay method in one embodiment. [Figure 8] FIG. 1 is a flow diagram illustrating the workflow of the user interface displayed for defining a sample in one embodiment. [Figure 9] FIG. 10 is a flow diagram illustrating the workflow of a user interface displayed for confirming a launch definition in one embodiment. [Figure 10] FIG. 10 is a flow diagram illustrating the workflow of a user interface displayed to notify a user of completed tasks in one embodiment. [Figure 11] FIG. 10 is a flow diagram illustrating the workflow of the user interface displayed for the run / collect option in one embodiment. [Figure 12] FIG. 10 is a flow diagram illustrating the workflow of the user interface displayed for the run / prepare option in one embodiment. [Figure 13] FIG. 10 is a flow diagram illustrating the workflow of the user interface displayed for the run / load option in one embodiment. [Figure 14] FIG. 10 is a flow diagram illustrating the workflow of the user interface displayed for the run / launch option in one embodiment. [Figure 15] FIG. 10 is a flow diagram illustrating the workflow of the user interface displayed for the run / unload option in one embodiment. [Figure 16] FIG. 10 is a flow diagram illustrating the workflow of the user interface displayed for the run / review option in one embodiment. [Figure 17]FIG. 10 is a flow diagram illustrating the workflow of the user interface displayed for the run / review option in one embodiment. [Figure 18] 1 illustrates components of a graphical user interface (GUI) system in one embodiment. [Figure 19] 1 illustrates a schematic diagram of an exemplary computer or processing system that may implement a graphical user interface system in one embodiment. [Figure 20] 10 is an exemplary screenshot of a screen displaying a graphical wheel / slider for maximizing screen black space in one embodiment. [Figure 21] 1 illustrates a cloud-based analytical computing system in one embodiment. [Figure 22] 1 illustrates a system architecture for a cloud-based analytical computing system in one embodiment. [Figure 23] 1 illustrates a system architecture of a cloud platform in a cloud-based analytical computing system in one embodiment. [Figure 24] 1 illustrates the interaction between an administrator computer and a cloud platform in one embodiment. [Figure 25] 1 illustrates the interaction between an analysis user computer and a cloud platform in one embodiment. [Figure 26] 1 illustrates the interaction between a data integration computer and a cloud platform in one embodiment. [Figure 27] 1 illustrates the interaction between a support user computer and a cloud platform in one embodiment. [Figure 28] 1 illustrates the interaction between a support data integration computer and a cloud platform in one embodiment. [Figure 29]1 illustrates the interaction between a consumable information upload computer and a cloud platform in one embodiment. [Figure 30] 1 illustrates the interaction between an account information upload computer and a cloud platform in one embodiment. [Figure 31] 1 illustrates the interaction between a meter information upload computer and a cloud platform in one embodiment. [Figure 32] 1 illustrates the interaction between a collaborative instrument computer and a cloud platform in one embodiment. [Figure 33A] 1 illustrates the interaction between an individual operating instrument computer and a cloud platform in one embodiment. [Figure 33B] 33B illustrates the interaction between the workflow assistant instrument computer and the cloud platform of the embodiment shown in FIG. 33A. [Figure 34A] 1 illustrates a first portion of a software architecture for cloud platform services in one embodiment. [Figure 34B] 34B illustrates a second portion of the software architecture for the cloud platform service of the embodiment illustrated in FIG. 34A. [Figure 35A] 1 illustrates a logical design of system data in one embodiment. [Figure 35B] 1 illustrates mapping of business entities to accounts using an analytical computing system in one embodiment. [Figure 35C] 1 illustrates the logical design of team data relative to plate data in one embodiment. [Figure 35D] 1 illustrates the logical design of team data in relation to assay method data in one embodiment. [Figure 35E] 1 illustrates the logical design of team data relative to activation data in one embodiment. [Figure 35F]1 illustrates the logical design of team data with respect to experimental data in one embodiment. [Figure 36A] 1 illustrates an exemplary structure of an account for a user of an analytical computing system in one embodiment. [Figure 36B] 1 illustrates a flow for creating an account for a user of an analytical computing system in one embodiment. [Figure 36C] 1 illustrates a flow diagram for associating an instrument with a user's account on an analytical computing system in one embodiment. [Figure 36D] 1 illustrates a flow for associating consumables with an account of a user of an analytical computing system in one embodiment. [Figure 37] 1 illustrates modules within an administrator software application in one embodiment. [Figure 38A] 1 illustrates the flow of an Admin Console module within an administrator app for an account administrator in one embodiment. [Figure 38B] 1 illustrates the flow of an Admin Console module within an Admin app for a team admin in one embodiment. [Figure 38C] 1 illustrates a flow of a user login process in one embodiment. [Figure 38D] 38A provides a screenshot illustrating an aspect of the work experience flow illustrated in FIG. 38A. [Figure 38E] 38A provides a screenshot illustrating an aspect of the work experience flow illustrated in FIG. 38A. [Figure 38F] 38A provides a screenshot illustrating an aspect of the work experience flow illustrated in FIG. 38A. [Figure 38G] 38A provides a screenshot illustrating an aspect of the work experience flow illustrated in FIG. 38A. [Figure 38H] 38A provides a screenshot illustrating an aspect of the work experience flow illustrated in FIG. 38A. [Figure 38I]10 presents an example of an advanced context menu associated with an administration console module. [Figure 39A] 10 illustrates a flow for an admin audit trail module in an administrator app in one embodiment. [Figure 39B] 1 illustrates aspects of a user interface of an administrative audit trail module consistent with embodiments herein. [Figure 39C] 1 illustrates aspects of a user interface of an administrative audit trail module consistent with embodiments herein. [Figure 39D] 1 illustrates aspects of a user interface of an administrative audit trail module consistent with embodiments herein. [Figure 39E] 1 illustrates aspects of a user interface of an administrative audit trail module consistent with embodiments herein. [Figure 40] 1 illustrates modules in an analysis user software application in one embodiment. [Figure 41] 1 illustrates a flow for an Analytical Methods module in an Analytical User App in one embodiment. [Figure 42A] 1 illustrates the design flow of the Assay Methods module in the Analysis User App in one embodiment. [Figure 42B] 13 illustrates the review flow of the Assay Methods module in the Analysis User App in one embodiment. [Figure 43A] 1 illustrates a design flow for an experiment module in an analysis user application in one embodiment. [Figure 43B] 10 illustrates a review flow for an experiment module in an analysis user app in one embodiment. [Figure 43C] 10 illustrates aspects of a reader module user interface consistent with embodiments herein. [Figure 43D] 10 illustrates aspects of a reader module user interface consistent with embodiments herein. [Figure 43E] 10 illustrates aspects of a reader module user interface consistent with embodiments herein. [Figure 43F] 10 illustrates aspects of a reader module user interface consistent with embodiments herein. [Figure 43G] 10 illustrates aspects of a reader module user interface consistent with embodiments herein. [Figure 43H] 10 illustrates aspects of a reader module user interface consistent with embodiments herein. [Figure 44] 12 illustrates the flow for the audit trail module in the Analytics User App in one embodiment. [Figure 45] 1 illustrates modules in a collaborative instrument software application in one embodiment. [Figure 46] 10 illustrates a flow for an operation module in a collaborative operation instrument app in one embodiment. [Figure 47] 10 illustrates the flow of a maintenance module within a collaborative instrument application in one embodiment. [Figure 48] 1 illustrates modules in an individual operating instrument software application in one embodiment. [Figure 49A] 10 illustrates a flow for an operation module in an individual operation instrument app in one embodiment. [Figure 49AA] 10 illustrates a flow for an operation module in an individual operation instrument app in another embodiment. [Figure 49B] 10 illustrates the flow of results review as a separate operating instrument app in an operating module associated with a plate reader in one embodiment. [Figure 50] 1 illustrates modules in a workflow assistance instrument software application in one embodiment. [Figure 51] 1 illustrates the flow of a workflow assistance module in a workflow assistance instrument app in one embodiment. [Figure 52] 1 is an embodiment of a computing flow for automatic software updates for an analysis user computer. [Figure 53]1 is an embodiment of a computing flow for automatic software updates for an analytical instrument computer. [Figure 54] FIG. 1 is an embodiment of an example of a non-biometric use of the disclosed architecture for a software module within a Chef app. [Figure 55] 1 is an embodiment of a user experience flow starting from the chef app and through the meal planner module. [Figure 56] 1 illustrates a system for implementing an organized user interface, according to one embodiment. [Figure 57] 1 illustrates a process for navigating a hierarchical menu tree through a user interface. [Figure 58A] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58B] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58C] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58D] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58E] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58F] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58G] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58H] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58I] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58J] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58K] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58L] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58M]1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58N] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58O] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58P] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58Q] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58R] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58S] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58T] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58U] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58V] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58W] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58X] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58Y] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58Z] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58AA] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58BB] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58CC] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58DD] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58EE] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58FF] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58GG] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 58HH] 1 is an exemplary, non-limiting embodiment of a reader module. [Figure 59A] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59B] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59C] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59D] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59E] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59F] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59G] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59H] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59I] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59J] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59K] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59L] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59M] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59N] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59O] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59P] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59Q]1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59R] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59S] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 59T] 1 is an exemplary, non-limiting embodiment of an experiment module. [Figure 60A] 1 is an exemplary, non-limiting embodiment of a maintenance module. [Figure 60B] 1 is an exemplary, non-limiting embodiment of a maintenance module. [Figure 60C] 1 is an exemplary, non-limiting embodiment of a maintenance module. [Figure 60D] 1 is an exemplary, non-limiting embodiment of a maintenance module. [Figure 60E] 1 is an exemplary, non-limiting embodiment of a maintenance module. [Figure 60F] 1 is an exemplary, non-limiting embodiment of a maintenance module. [Figure 60G] 1 is an exemplary, non-limiting embodiment of a maintenance module. [Figure 60H] 1 is an exemplary, non-limiting embodiment of a maintenance module. [Figure 60I] 1 is an exemplary, non-limiting embodiment of a maintenance module. [Figure 61A] 1 is an exemplary, non-limiting embodiment of a management console module. [Figure 61B] 1 is an exemplary, non-limiting embodiment of a management console module. [Figure 61C] 1 is an exemplary, non-limiting embodiment of a management console module. [Figure 61D] 1 is an exemplary, non-limiting embodiment of a management console module. [Figure 61E] 1 is an exemplary, non-limiting embodiment of a management console module. [Figure 61F] 1 is an exemplary, non-limiting embodiment of a management console module. [Figure 61G]1 is an exemplary, non-limiting embodiment of a management console module. [Figure 61H] 1 is an exemplary, non-limiting embodiment of a management console module. [Figure 61I] 1 is an exemplary, non-limiting embodiment of a management console module. [Figure 61J] 1 is an exemplary, non-limiting embodiment of a management console module. [Figure 61K] 1 is an exemplary, non-limiting embodiment of a management console module. [Figure 61L] 1 is an exemplary, non-limiting embodiment of a management console module. [Figure 61M] 1 is an exemplary, non-limiting embodiment of a management console module. [Figure 61N] 1 is an exemplary, non-limiting embodiment of a management console module. [Figure 61O] 1 is an exemplary, non-limiting embodiment of a management console module. [Figure 61P] 1 is an exemplary, non-limiting embodiment of a management console module. [Figure 61Q] 1 is an exemplary, non-limiting embodiment of a management console module. [Figure 62A] 1 is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules herein. [Figure 62B] 1 is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules herein. [Figure 62C] 1 is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules herein. [Figure 62D] 1 is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules herein. [Figure 62E] 1 is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules herein. [Figure 62F]1 is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules herein. [Figure 62G] 1 is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules herein. [Figure 62H] 1 is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules herein. [Figure 62I] 1 is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules herein. [Figure 62J] 1 is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules herein. [Figure 62K] 1 is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules herein. [Figure 62L] 1 is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules herein. [Figure 62M] 1 is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules herein. [Figure 62N] 1 is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules herein. [Figure 62O] 1 is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules herein. [Figure 62P] 1 is an exemplary, non-limiting embodiment of a general screenshot applicable to multiple modules herein. [Figure 63] 1 is an exemplary, non-limiting embodiment of an audit trail module. [Figure 64A] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64B] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64C]1 is an example of a non-limiting embodiment of an assay method module. [Figure 64D] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64E] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64F] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64G] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64H] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64I] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64J] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64K] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64L] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64M] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64N] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64O] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64P] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64Q] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64R] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64S] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64T] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64U] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64V] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64W] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64X] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64Y] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64Z] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64AA] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64BB] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64CC] 1 is an example of a non-limiting embodiment of an assay method module. [Fig. 64DD] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64EE] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64FF] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64GG] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64HH] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64II] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64JJ] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64KK] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64LL] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64MM] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64NN] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64OO] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64PP] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64QQ] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 64RR] 1 is an example of a non-limiting embodiment of an assay method module. [Figure 65] 10 illustrates a UI display consistent with the collection and preparation module in one embodiment. [Figure 66] 10 illustrates a UI display consistent with the collection and preparation module in one embodiment. [Figure 67] 10 illustrates a UI display consistent with the collection and preparation module in one embodiment. [Figure 68] 10 illustrates a UI display consistent with the collection and preparation module in one embodiment. [Figure 69] 10 illustrates a UI display consistent with the collection and preparation module in one embodiment. [Figure 70] 10 illustrates a UI display consistent with the collection and preparation module in one embodiment. [Figure 71] 10 illustrates a UI display consistent with the collection and preparation module in one embodiment. [Figure 72] 10 illustrates a UI display consistent with the collection and preparation module in one embodiment. [Figure 73] 1 illustrates a laboratory system configured for implementation. [Figure 74] 10 illustrates a UI display consistent with the assay guide module in one embodiment. [Figure 75] 10 illustrates a UI display consistent with the assay guide module in one embodiment. [Figure 76] 10 illustrates a UI display consistent with the assay guide module in one embodiment. [Figure 77a] 10 illustrates a UI display consistent with the Instrumentation module of the Assay Guide module in one embodiment. [Figure 77b] 10 illustrates a UI display consistent with the Instrumentation module of the Assay Guide module in one embodiment. [Figure 77c] 10 illustrates a UI display consistent with the Instrumentation module of the Assay Guide module in one embodiment. [Figure 78] 10 illustrates a UI display consistent with the QC criteria module in the first embodiment. [Figure 79] 10 illustrates a UI display consistent with the QC criteria module in the second embodiment. [Figure 80] 1 illustrates a UI display consistent with a project module in one embodiment. [Figure 81] 1 illustrates a UI display consistent with a project module in one embodiment. [Figure 82] 1 illustrates a UI display consistent with a project module in one embodiment. [Figure 83] 10 illustrates a UI display consistent with the analysis module in the first embodiment. [Figure 84] 10 illustrates a UI display consistent with the analysis module in the second embodiment. [Figure 85] 1 illustrates a UI display showing a dashboard for a particular project, according to one embodiment. [Figure 86] 1 illustrates a UI display with the "Results" menu item selected, according to one embodiment. [Figure 87] 1 illustrates a UI display with the "Charts" menu item selected, according to one embodiment. [Figure 88] 1 illustrates a UI display with the "Contrast" menu item selected, according to one embodiment. [Figure 89] 86 shows the portion of the UI display of FIG. 85 with the "Dashboard" menu item selected. [Figure 90] 10 shows a UI display with the "Add Assay" option selected, according to one embodiment. [Figure 91]12 illustrates the Data Table view under the Review menu item, according to one embodiment. [Figure 92] 10 illustrates a UI display that prompts a user to enter a specific restart reason, according to one embodiment. [Figure 93] 13 illustrates a UI display showing an assay being restarted, according to one embodiment. [Figure 94] 1 illustrates a UI display with a warning displayed, according to one embodiment. [Figure 95] 1 illustrates a UI display with a dashboard view of a project, according to one embodiment. [Figure 96] 13 shows a UI display with all samples / assays marked for restart, according to one embodiment. [Figure 97] 1 illustrates a UI display showing a reboot review view, according to one embodiment. [Figure 98] 1 illustrates a UI display showing an assay selection view, according to one embodiment. [Figure 99] 1 is a flowchart of an exemplary method for conducting one or more experiments. DETAILED DESCRIPTION OF THE INVENTION

[0016] The embodiments described herein provide technical solutions to a variety of technical problems through the improvement of existing technologies and the creation of entirely new technologies. Among the technical problems addressed by the embodiments discussed herein are the inefficiencies of traditional user interfaces and the difficulty in integrating different parts of a process workflow.

[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 aspects 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 series of menus or similar choice options from which a user selects (e.g., selecting a series of options in a hierarchical manner) to cause a computer or similar device to perform a desired function. In some embodiments, depending on the type of application, the amount of information or number of menu choices presented to a user may be overwhelming. Using a wide range of menu options may cause a user to try different options or navigate through various menu selection hierarchies before finding the correct series of options or the desired option. In some examples, of 100% of the user interface choices and functional options available to a user, only about 10% are used. However, if 100% of all options are presented, a user may have difficulty determining where to navigate to find that 10% that is relevant to the user. Additionally, because a selected menu choice affects the next choice made down the menu choice path, switching between options by a user may also mean navigating multiple different paths that lead from that choice. Such trial and error is time consuming, expensive 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 the present disclosure can provide a user interface that guides a user through selection options to be selected via a user interface display or another presentation device, reducing the time it takes to find the correct selection. In this manner, the number of incorrect selection attempts is reduced, and the user's navigation time can be reduced to complete a desired computing function or goal. In an aspect, the user interface of the present disclosure can present the user with a selectively limited number of options from all available options in a specific manner and guide the user through those options, streamlining operation and allowing the user to focus on arriving at a desired computing function more efficiently. In another aspect, the user interface of the present disclosure can provide a more direct connection to the application.

[0020] The embodiments and technical solutions provide practical applications of certain visual principles to assist users in navigating the menus and systems described herein. Such visual principles include minimizing visual content and maximizing background or void space to reduce visual clutter and highlight areas of interest. Providing a dark or otherwise uniform background can increase the contrast between content and background and draw the user's attention to the appropriate area.

[0021] The embodiments and technical solutions provide practical applications of certain design principles to assist users in navigating the menus and systems described herein. The design principles embodied herein include, for example, minimizing the number of menus and / or selections a user must navigate at one time.

[0022] A further design principle includes presenting the user with a single new choice at any given time while offering the option to easily revisit previously selected choices. This principle may be implemented via a two-part display system. An active part may be configured to display the user's current choice, and a 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 positions. Previously selected choices (and the menus from which those selections were made) may be displayed to the user in a nested or stacked format. A nested series of previously navigated menus may be presented in the style of a Russian nesting doll (matryoshka), with each previously selected menu item expanding into a displayed submenu. Nested or stacked previously selected menu items may also provide a breadcrumb trail, indicating to the user the path taken to arrive at the ongoing menu. In certain embodiments, an indicator bar may be provided to draw the user's attention to a previously selected menu item. For example, if previously selected menu items are arranged in a stacked format, the use of an indicator bar may help to vertically align one or more menus and / or menu items. This is shown, for example, in FIG. 61D. In this example, the indicator bar (located below the "Add / Remove" item) helps to draw the user's attention and align the following items: "Administration," "Legal," and "Add / Remove." In certain embodiments, the indicator bar may be displayed to resemble the hands of a watch, as shown in FIG. 61D. Additionally, the indicator bar may include color-coded states (e.g., red to indicate an error state and blue to indicate a non-error state).In certain embodiments, the color-coded state may be depicted within a portion of the indicator bar by illuminating pixels of one or more colors. In one example, the color-coded state may be provided within a middle portion of the indicator bar, as illustrated in FIG. 61D, although the state may also be displayed in other portions of the UI display.

[0023] Embodiments herein maintain a consistent appearance throughout use of the interface, regardless of the task or process being completed, for example, by maintaining a consistent screen location for menus so that the user does not have to search for different locations for the menu. In other words, relevant menus are 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 from top to bottom and left to right. In further embodiments, the size and shape of the menu interface changes according to the device or screen on which it is viewed. Menus can span horizontally on wider screens and / or vertically on taller / narrower screens.

[0024] The embodiments discussed herein enhance user productivity by providing improved efficiency and accuracy through enhancements to several aspects of the user experience. The user interfaces described herein focus users on the most likely use cases while minimizing distractions caused by underutilized options. This focus minimizes visual distractions from the user interface and keeps users focused on the most relevant menu choices. The user interfaces described herein aim to guide users from one step through the user interface while eliminating the potential for users to become confused about what to do next. In embodiments herein, a user's navigation path through the interface system remains transparent to the user to facilitate the selection of alternative options or backing out of an ongoing menu. Throughout the process of using the user interface, the user may have the option to unobtrusively browse alternative paths through the process. Thus, a core function of the user interface software provided herein is to increase the total amount of relevant information presented to a user at any one time while reducing the total amount of information presented to a user at any one time. Additional information and options for less frequent use cases remain available in an unobtrusive presentation style. Such decisions regarding the information to be presented via the user interface at any given time may be pre-guided through a predetermined menu workflow and / or influenced and updated through analysis of previous user actions and choices.

[0025] Computer functionality may also be improved via the embodiments provided herein. For example, focusing on a limited number of options may reduce resource usage on devices (e.g., user devices and / or server devices) that may be involved in launching a user interface. For example, memory usage, processor resource usage such as central processing unit (CPU) usage, hard drive or similar persistent storage usage, and bandwidth required for device-to-device (e.g., device-to-device, device-to-server, server-to-server) communication may be reduced. Additionally, the ability to navigate or reach the correct selection or selection path directly may increase the efficiency of communication between devices and servers, for example, without requiring extensive trial-and-error navigation. This may, for example, reduce Internet communication and costs associated with such communication.

[0026] Further embodiments discussed herein relate to the integration of various process workflow aspects. As discussed herein, a "process workflow" may relate to an instrumentation (including bioinstrumentation) testing workflow, a manufacturing workflow, an analytical workflow, and / or any workflow that may involve one or more devices controlled at least in part 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 discussed herein may include a variety of architectures, including, but not limited to, 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 multiple device computing system, a device / printer system, a device / server computing system, a system including multiple devices and a server, or any other suitable computing system.

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

[0029] 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-controlled systems, and / or any other type of visual user interface. Collectively, user interface systems consistent with embodiments 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-controlled systems, and / or any other type of visual user interface. Some of the principles discussed herein are specifically discussed with respect to GUIs, for example, but this is not intended to be limiting, and the principles discussed herein may apply to other interface systems as well.

[0030] The MUI described herein refers to a "display," an "interface," and a "user interface." As used herein, the terms "display," "interface," and "user interface," unless otherwise specified, 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. Accordingly, as used herein, it is understood that "display" and "interface" may be provided via any type of visual display hardware, screen, and / or projector. For convenience, menus, interfaces, and other visual items are referred to herein as being viewed on or displayed by the MUI. It is understood that such references indicate that the MUI, as discussed herein, is visually presented via a hardware device.

[0031] As described in more detail below, the user interface systems described herein may use various visual components to present menu items. For example, the visual component may include a vertical “wheel” or a horizontal wheel that rotates through various menu items. As described herein, the use of “wheel” as a visual component refers to the manner in which prominent (highlighted) and recessed (unhighlighted) options are presented to the user. A wheel-shaped visual component may be understood as a virtual wheel with the rim facing the user and multiple menu items disposed on the rim of the virtual wheel. A wheel-shaped visual component may or may not include any visual indicator of the presence of a wheel. The wheel-shaped visual component may present prominent options to the user in an attention-grabbing manner (i.e., on the portion of the wheel “closest” to the user), while other recessed options may be presented in a less attention-grabbing manner. Prominent menu items may be highlighted in a different color, presented in a different font, presented in a larger font, or otherwise marked to visually attract attention. As the virtual wheel rotates, the active prominent menu item rotates away from the user (either clockwise or counterclockwise), and the active receding menu item becomes the new prominent option. In embodiments, receding menu items closest to the prominent menu item may be displayed to attract more attention than menu items that are further receding from the prominent menu item. For example, menu items may decrease in size or brightness based on their distance from the active prominent menu item. As the "wheel" "spins," receding menu items may be dimmed from view. In this format, the virtual wheel provides the user with the perception and feeling that the menu items are all arranged on a physical wheel. The visual component may further include a horizontal or vertical slider for sliding through the various menu items. Similarly, as discussed above, sliders may be used to provide prominent menu items, receding menu items, or non-prominent menu items for the wheel.In embodiments, a slider may differ from a wheel in that back menu items do not appear to fade from view as options in the slider slide past. Further embodiments of wheels and sliders are discussed further herein with respect to specific embodiments.

[0032] As described herein, menu items may be variously "selected," "highlighted," and / or "clicked." As discussed herein, menu items may be variously "selected," "highlighted," and / or "clicked." As used herein, "highlighting" a menu item means that the "highlighted" option is prominently displayed to the user, for example, as a prominent menu item in the center of a wheel. "Highlighting" may include changing the color, size, font, etc. of the menu item to visually highlight the menu item to the user. "Dehighlighting" a user option may include changing the color, size, font, etc. of the menu item to make the menu item visually less prominent to the user. Menu items may be highlighted or dehighlighted in response to a user action (e.g., via clicking a mouse, touching a touchscreen, rolling a wheel, etc.) (e.g., by presenting a menu item that the user cannot select or edit) and / or based on an interface action (e.g., by presenting a highlighted default option).

[0033] As used herein, "selecting" a menu item means that the menu item has been selected by a user and the user interface has advanced one or more menu steps in accordance with the selection. "Selecting" a menu item causes the computer system to execute computer instructions to advance through the menu, rather than simply "highlighting" the menu item. For example, "selecting" a menu item may cause a new menu to be displayed based on the selection. Although a selected menu item may be highlighted after selection, highlighting a menu item does not necessarily include selecting the menu item.

[0034] In some embodiments, a menu item may be selected or highlighted via clicking on the menu item. As used herein, "clicking" refers to a user action of clicking, tapping, or otherwise using an interface device (e.g., a mouse, a touchscreen, etc.) to indicate or select a menu item. As used herein, "clicking" a menu item is different from "selecting" the menu item. Clicking refers to a user action that indicates a menu item, while selection refers to a computer function associated with selecting a menu item.

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

[0036] Menu items may be described herein as "selectable." Menu items may be described herein as "selectable." A "selectable" menu item refers to a menu item that a user can interact with by either selecting or highlighting the menu item. Selectable menu items may be displayed through a change in color, highlighting, font, etc. in a manner that indicates that they are selectable. Menu items may be described herein as "non-selectable." A "non-selectable" menu item refers to a menu item that a user cannot currently interact with through selection or highlighting. A non-selectable menu item may be displayed in a manner that indicates that they are not selectable through a change in color, highlighting, font, etc.

[0037] Menu items may also be described as “previously selected” and “not previously selected.” A “previously not selected” menu item refers to a menu item that was not selected to arrive at the ongoing menu interface display. A “previously selected” menu item does not need to have been 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 option in the current path may be indicated as “previously selected” even if the user has not actively selected 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 but not a second menu item, the system may proceed to display a subsequent menu or submenu in response to selecting 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 menu item that was not previously selected may be displayed as selectable.

[0038] For example, a user may scroll a slider or turn a wheel through various menu items. The user can adjust the wheel or slider so that a particular menu item is highlighted. In embodiments, a particular menu item may require further user interaction (e.g., a single or double-click) to "select" it, causing the MUI to present a new set of menu or sub-menu items in response to the selection. In one such embodiment, the user rotates a wheel or scrolls a slider to move a desired menu item to the highlighted prominent menu item. The user then clicks, double-clicks, or otherwise indicates acceptance of the highlighted menu item as a selection to display the next menu or sub-menu. In embodiments, a particular menu item may be "selected" simultaneously with its highlighting. In one such embodiment, an associated sub-menu is presented immediately upon highlighting the desired menu item by rotating a wheel or scrolling a slider to move the desired menu item to the highlighted prominent menu position.

[0039] As discussed herein, selection or highlighting of a menu item may be caused by directly selecting (i.e., clicking, touching, etc.) the menu item anywhere on a wheel, slider, and / or list item, regardless of whether it is a prominent or recessed menu item. Selection or highlighting of a menu item may also occur in response to user manipulation of various visual components to move the menu item to a highlighted or selected position. For example, a user may rotate a wheel or move a slider until a particular menu item becomes the prominent or highlighted menu item. Manipulation and / or direct selection of a visual component may be implemented through the use of any suitable user input device, including a touchscreen, a mouse, a keyboard, arrow keys, an eye gaze detection system, a motion detection system, a gesture detection system, etc.

[0040] Features of embodiments of the interface may be referred to as a "first portion" and a "second portion." These terms refer to specific portions of the user interface that are displayed at various times and are not necessarily fixed to a specific location on the screen. As used herein, a "first portion" may also be referred to as an "active portion." A "first portion" or "active portion" refers to a portion of the MUI that displays the ongoing or current set of menu items. The "first portion" and "active portion" may be used interchangeably herein. A "second portion" may also be referred to as a "history portion." A "second portion" or "history portion" refers to a portion of the interface that displays previously viewed menus and previously selected and unselected menu items. The "second portion" and "history" portions may be used interchangeably herein.

[0041] FIG. 1 illustrates a method for interactively navigating a user through a path of menu choices on a user interface in one embodiment. The method may be automatically executed by at least one hardware processor. The method facilitates a user's movement through the system by displaying and asking questions about one or more past choices made by the user, along with other options that were not selected, while drilling down to additional choices based on the initial choice. As used herein, "asking a question" refers to presenting the user with one or more menu choices to choose from. The method allows the user to continue the path, jump to a different path, go back in time to a choice made in one or more previous steps, or return to the most recent point in time of a choice selected by the user. In one embodiment, the user interface allows past or previous choices, whether selected or not, to be presented and displayed on the same screen, regardless of where the user is on the path, for example, at each step of the path. For example, the user interface presents an overview of the user's menu choice path, including menu items that were not selected. The user interface techniques allow for more efficient navigation, guiding the user along a path, allowing the user to see the path they are taking, allowing the user to deviate from the path set for the user onto another path, allowing the user to see previous and next breadcrumbs, allowing the user to see where they are going and where they can go.

[0042] As discussed herein, menus are presented as a series of hierarchical menu trees. Each level of the menu tree contains multiple menus that lead to other menus. Thus, for example, a first level of the menu tree contains multiple first menus, a second level of the menu tree contains multiple second menus, and a third level of the menu tree contains multiple third menus. This structure continues up to the execution 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, the menus in the layers below the execution menu may be collectively referred to as submenus. Thus, a submenu of a first menu may contain multiple second menus, multiple third menus, multiple fourth menus, multiple execution menus, etc. An example of a hierarchical menu tree structure is shown in FIG. 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 present only an "execute" button for implementing a process designed through other portions of the menu. Another "menu" may present, for example, a tutorial.

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

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

[0045] At the run menu level, i.e., the last level in the series of menus, the user can select run menu choices or items. These choices or items do not lead to further menus, but instead represent selection of parameters for the process that the menu tree is intended to facilitate. Selecting a run menu choice or item causes the system to perform the function associated with the selected menu choice or item. For example, when using an assay design menu tree, run menu choices may include options such as filename, assay parameters, reagent choices, etc.

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

[0047] In embodiments, the execution menu may provide a walkthrough or tutorial to the user. 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 guide the user through each step of the designed workflow or process.

[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 physical world. For example, in a modular laboratory system, such a combination may provide instructions to a user to load a machine (e.g., with an assay plate and reagents) and then provide execution commands to the machine to launch a process. If a new step in a process requires physical intervention by the user (e.g., moving an assay plate), the MUI may provide additional instructions (text-based, video-based, image-based, audio-based, etc.) to the user at the execution level to advance the process. In embodiments, user instructions and notifications implementing the user-intervention portion of the process may be provided via various communication means, including, for example, text (SMS, MMS), email, phone, instant message, Slack message, and any other type of messaging protocol. Such various communication means may be useful, for example, when a portion of a machine process takes some time to complete and the user does not want to remain at the process location during the process. Thus, if a user initiates a process that takes several hours, they may receive a text message indicating that their intervention is required 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 automated machines 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.), transportation and logistics workflows (e.g., boxing and picking, packaging, etc.), 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 in the menu within the MUI. Displaying a menu does not require displaying all items or options in 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. As discussed in more detail below, certain menu items may be excluded or restricted for various reasons. As discussed herein, a designated "first menu" or "second menu" may be relocated to various portions of the screen. When relocated, the first menu may continue to display the same set of first menu items and / or may display a different set of first menu items.

[0051] As discussed herein, menus may also be referenced based on their temporal state. An "ongoing menu" refers to a menu that is 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 previously selected an option. A past menu may be displayed in the history portion of the MUI. A "subsequent menu" refers to the next menu that becomes active after the ongoing menu becomes the past menu. For example, a first menu may be displayed as the ongoing menu. After a selection is made from the first menu, the first menu may then be repositioned to become the past menu. Thereafter, a second menu selected from the first menu may be displayed as the ongoing menu. The ongoing menu may be displayed in the first or active portion of the user interface, and a past menu may be displayed in the second or history portion of the user interface.

[0052] In the history section, each menu item in a past menu may be displayed in a linear fashion in the MUI. All menu items at that menu level are displayed in a single row (horizontal or vertical). Each set of past menu items may be displayed in such a linear fashion, while the entire menu may be displayed in a stacked or nested fashion. This feature is shown, for example, in FIG. 2C, which shows menu items displayed linearly and submenu items displayed linearly. The relationship between menu items and submenu items is 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 fashion.

[0053] The menu of options may be displayed, for example, as a graphical wheel that rotates the options horizontally or vertically (e.g., left / right, up / down) or in another direction. In another aspect, the menu of options may be displayed, for example, as a graphical slider that slides the options horizontally or vertically (e.g., left / right, up / down) or in another direction. For example, an initial menu level (first level) may be displayed horizontally and slid left / right, and a subsequent menu level (second level) may be displayed vertically and rotated up / down. In yet another aspect, the menu of options may be displayed as a series of concentric circles, with each menu level displayed as a circle having menu options (also referred to as options or menu items). For example, the initial menu level (first level) may be displayed in a central circle, the subsequent menu level (second level) may be displayed in a subsequent circle (second circle) surrounding the central circle, and the subsequent menu level (third level) may be displayed in a further circle surrounding the second circle. Additionally, the menu of options may be displayed or visualized as a graphical decision tree with nodes and edges, where each level of the graphical decision tree may represent a menu level with options.

[0054] In one embodiment, the wheel and / or slider need not rotate completely, e.g., not make a full revolution or circle. For example, the wheel and / or slider may rotate or slide from a start menu item to an 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 a menu are always displayed because they are coupled and never together. This technique can reduce processing time because the wheel and / or slider can convey (and the user can immediately understand) an entire menu of options while clearly indicating which is the first menu item and which is the last menu item among the options presented by the wheel and / or slider.

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

[0056] In various embodiments, the terms “software protocol” and “computer instructions” are used to describe software instructions or computer code configured to perform various tasks and operations. As used herein, the term “manager” broadly refers to a collection of software instructions or code configured to cause one or more processors to perform one or more functional tasks. For convenience, the various managers, computer instructions, and software protocols are described as actually performing various operations or tasks when the managers, computer instructions, and software protocols program a hardware processor to perform the operations and tasks. While “managers,” “software protocols,” and “computer instructions” as used herein are described in various places as “software,” it is understood that they may also be implemented as firmware, software, hardware, or any combination thereof for instructing a computer or other electronic device to execute and / or perform 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 displaying a menu, selecting an option, etc. Although not explicitly stated in every instance, 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 functionality of the managers and software protocols discussed herein may be provided by the issuance of one or more commands. As discussed herein, "commands" issued by the managers and software protocols refer to signals and instructions provided to various aspects of the computing system to cause various actions to occur. 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 in a menu interface. Such a command may be directed to a physical display screen and may include the signals and instructions necessary to generate the visual component. As used herein, when a manager is described as performing an action or implementing a particular function, it should be understood that the manager issued the command that caused such action or function to occur.

[0058] In various embodiments, the term “module” is used to refer to a specific set of software protocols and computer instructions that generate, maintain, and operate the components of the MUI described herein. One or more processors described herein may be configured to execute the software protocols to provide an organizational user interface module. As used herein, “organizational user interface module” refers to any subset of modules that provide a specific user interface. For example, an administrative console module, an audit trail module, and a reader module are provided as specific organizational user interface modules for performing tasks related to system management, auditing, and plate reading, respectively. Each MUI module may be understood to include a hierarchical menu tree that includes at least multiple hierarchical menus. Each module may further include preferred default visual components, preferred default exclusion and restriction lists, and other functionality specific to the module. Other modules are discussed in more detail below and throughout this disclosure. Aspects of various MUI modules are discussed throughout this disclosure. Discussed aspects of any particular MUI module are non-exclusive and non-limiting and may apply to any other MUI module as well. Thus, any MUI feature discussed herein, either broadly or with respect to a particular module, may be applied generally to the MUI in general and / or to any other particular MUI module discussed herein.

[0059] Referring now to FIG. 56, an organized user interface control system 1102 consistent with embodiments herein is illustrated. The organized user interface control system 1102 includes one or more processors 1110 (also referred to herein as processors 1110, processor 1110, or processor 1110 for convenience), one or more storage devices 1120, and / or other components. CPU2 (see FIG. 19) and hardware processor 1804 (see FIG. 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 an application-specific integrated circuit (“ASIC”), a programmable gate array (“PGA”), a field-programmable gate array (“FPGA”), etc.), or any combination of hardware and software. The storage device 1120 includes any type of non-transitory computer-readable storage medium(s) and / or non-transitory computer-readable storage device(s). Such a computer-readable storage medium or device may store computer-readable program instructions that cause a processor to perform one or more of the techniques described herein. Memory 4 (see FIG. 19) and memory device 1802 (see FIG. 18) may be examples of storage device 1120. Examples of computer-readable storage media or devices may include, but are not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof, such as computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disk read-only memory (CD-ROM), digital versatile disk (DVD), and memory sticks. In embodiments, storage device 1120 may include multiple storage devices 1120. Multiple storage devices 1120 consistent with embodiments herein may be collocated and / or non-collocated.For example, one physical system may contain a first memory storage device 1120 and a second physical system may contain a second memory storage device 1120.

[0060] In an embodiment, the processor 1110 and the storage device 1120 may be implemented via a cloud computing platform or other form of distributed computing, in which the processor and storage device may each include multiple processors and storage devices to perform 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," stored on 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 functionality of the various managers discussed herein is exemplary and not limiting. Furthermore, the functionality of the various managers may be combined into one or more modules, applications, programs, services, tasks, scripts, libraries, applications, or executable code, as desired.

[0062] The managers discussed herein may be implemented in various embodiments to manage a MUI to complete various tasks involving a process workflow. While various software implementations of a MUI are described herein with respect to one or more specific embodiments, the methods and functionality provided by such managers may be implemented to provide a MUI for any process workflow. Such managers may be functionally implemented through software libraries.

[0063] The various components of the systematic user interface control system 1102 work cooperatively to provide a systematic user interface display to a user via any type of display hardware, including a screen, projection, touchscreen, headset, etc. In embodiments, the systematic user interface control system 1102 implements one or more software protocols for interactively navigating a user through a path of menu items, options, or choices within the MUI. The software managers described above may include sets of computer instructions, software libraries, dynamic link libraries, application program 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 needed to implement and instantiate the various visual components described herein. Managers may be customized for use in a particular implementation 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, binomial heaps, Fibonacci heaps, and any other suitable data structures. Thus, the MUI manager may be provided as a customizable code library configured to interface, interact, and otherwise integrate with additional computer instructions and data structures to provide MUI modules capable of performing specific tasks.

[0064] The display manager 1050 is a software protocol running 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 can be configured to issue commands that cause the display of various menu items as needed.

[0065] The input manager 1052 is a software protocol running on the systematic user interface control system 1102. The input manager 1052 is configured to manage all input received by the systematic user interface control system 1102, including, but not limited to, user input and input from other systems. The input manager 1052 can be configured to issue commands to other managers of the systematic user interface control system 1102 according to the received input. User actions, such as clicks and other screen interactions, cause the input manager 1052 to receive signals indicative of a user interaction. Receipt of such signals causes appropriate managers of the systematic user interface control system 1102 to provide commands in response thereto, thereby causing one or more actions, including MUI navigation, menu display, etc., as discussed herein. For ease of explanation, such interactions and user inputs may be referred to as causing a particular response when, in fact, a particular response is caused 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 running on the systematic user interface control system 1102. The menu manager 1054 is configured to manage the hierarchical menu tree and all menu items associated with the menu tree. The menu manager 1054 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 can be configured to issue commands to other managers of the systematic user interface control system 1102 according to menu navigation requirements.

[0067] The user manager 1056 is a software protocol running on the systematic user interface control system 1102. The user manager 1056 is configured to manage user access to the systematic user interface control system 1102. The user manager 1056 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 running on the systematic user interface control system 1102. The exclusion manager 1058 is configured to manage the exclusion and restriction of menu items. As discussed herein, menu items may be excluded or restricted based on various factors. The exclusion manager 1058 can be configured to issue commands that implement such exclusions and restrictions.

[0069] The network manager 1060 is a software protocol running 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 the various other system components discussed herein. The established communication paths may utilize any suitable network transport protocol and provide for 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 running 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 with which the systematic user interface control system 1102 may interface. The data storage manager 1064 is configured to issue commands to any of the various data storage devices discussed herein 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 as discussed below. It should be understood that the described structure of the systematic user interface control system 1102 is by way of example only, and that the various functions and capabilities of the computer instruction program processor described herein may be performed, implemented, or enabled by software systems of alternative structures.

[0072] The systematic user interface control system 1102 can present menu choices among one or more hierarchical menu levels, each of which can include one or more menu items or options. Hierarchical menu levels, as described herein, refer to multiple levels within a menu system. Selection of a first, top-level menu level causes navigation to a lower hierarchical level, i.e., a second menu, sub-menu, or sub-level. Selection within a second menu or sub-menu causes navigation to an even lower hierarchical level, i.e., a third menu or sub-sub-menu or sub-sub-level. A hierarchical menu structure can include any suitable number of levels. In some embodiments, selection at one level may cause navigation to one, two, three, or more levels below the current level.

[0073] Each menu may present options in the active portion of the interface. Menu choices may be selectable and represent options that the user selects. Selection of a menu choice or option may trigger the display or presentation of a subsequent submenu, which may contain several menu choices or submenu choices of its own. When a 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 navigate to the new menu choice while retaining knowledge of previous menu choices. These features are described in more detail below with respect to FIGS. 2A-2O, 3, and 57.

[0074] FIG. 57 is a flowchart illustrating a process 5200 for navigating a path of hierarchical menu levels adapted for output to a user interface, such as a GUI, a MUI, and / or any other type of UI discussed herein. Process 5200 executes on a computer system having one or more physical processors programmed with computer program instructions that, when executed by the one or more physical processors, cause the computer system to perform a method. The one or more physical processors are hereinafter referred to simply as processors. In an embodiment, process 5200 is implemented via the systematic user interface control system 1102, as described herein. The systematic user interface control system 1102 represents an example of a combination of hardware and software configured to implement process 5200. However, implementation of process 5200 is not limited to the hardware and software combination of the systematic user interface control system 1102. Process 5200 may also be performed and / or implemented by any other suitable computer system discussed herein. The description of process 5200 is not intended to be limiting, and various operations may be altered or modified in accordance with the embodiments described herein.

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

[0076] At operation 5204, process 5200 includes receiving a selection. The input manager 1052 receives a selection of a menu item from the first menu according to input provided to the system. The input may be a user selection and / or an automatic selection as discussed herein. The user selection may be received, for example, from a user clicking a highlighted or highlighted menu item. Upon making the selection, the menu item may be a previously selected menu item.

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

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

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

[0080] Referring to FIG. 1 , at operation 102, an ongoing menu of options (e.g., a list of menu items) may be displayed in a first portion of a user interface display. At operation 104, the user interface allows a user to select a menu item from the ongoing menu of options displayed in the first portion of the user interface display and to drill down levels of menu options based on selecting a menu item from a previous level of menu options. At operation 106, previously selected and previously unselected menu items of the drilled-down level are displayed in a second portion of the user interface display. The previously unselected menu items are displayed as selectable options. Previously selected menu items (or options) may also be displayed as selectable options. At operation 108, the user interface allows a user to jump to a different path of menu options by allowing the user to select a previously unselected menu item from a previously navigated menu level displayed in the second portion of the user interface display. The user interface displays both the first and second portions viewable on the same screen of the user interface, e.g., simultaneously.

[0081] In one embodiment, the first and second portions are shifted to a substantial center of the first portion to display an ongoing menu of options on the user interface display while fitting both the first and second portions onto the user interface display. Thus, for example, the first and second portions need not remain in a fixed position on the user interface display while navigating or drilling down (or up) through different levels of menu options.

[0082] In one embodiment, in response to detecting a selection of a menu item from the current option menu, the user interface display rearranges the current option menu in a second portion of the user interface display and displays next level menu options based on the selection of the menu item in a first portion of the user interface display. The rearranged current option menu is shown in the second portion of the user interface display, with previously selected menu items and previously unselected menu items from previous menu levels. The next level menu options are shown in the first portion as the current option menu.

[0083] As described above, the options menu may be displayed as a rotatable graphical wheel showing menu items (options or options) on the wheel, which may be revealed as the wheel is rotated. Similar graphical sliders exist that may reveal menu items on a slider when slid. The rotating 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 aspect, the rotating or sliding action may be automatically performed in a timely manner by the user interface (or hardware running the user interface). In one embodiment, the rotating or sliding direction may switch to a different orientation when the options menu is repositioned from a first portion to a second portion.

[0084] The ongoing menu of options may be displayed in a first visual orientation on a first portion of the user interface display, and a drilled-down level of menu options, including previously selected menu items 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 menu of options is displayed as a graphical rotating wheel or slider that rotates or slides the options in a first visual orientation. In one embodiment, drill-down levels of menu options are displayed as graphical rotating wheels or sliders that rotate or slide the options in the drill-down levels in a second visual orientation.

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

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

[0088] In another embodiment, the first and second portions may be displayed as a series of concentric circles. For example, the first portion may be displayed as the center circle of the series of concentric circles, and previous menu levels may be displayed as circles outside or surrounding the center circle. Each circle representing a menu level may include rotatable menu items (choices or options), for example, so that a user can view all options present on that menu level. Selecting a menu item from the current menu of options rearranges the current menu of options in the outer circle, and the center circle displays the next menu of options based on the selected menu item. For example, a circle (e.g., a dial) may include a window showing the active option, and turning the circle (e.g., the dial) displays other options in the window. While the dial options appear finite, the dial options may be infinite. For example, the dial continues to turn until the last option (or the starting option, if turning backward) is displayed.

[0089] Alternatively, the window may display the selected option as open and lit up, with one or more options to the left and another option or options to the right.

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

[0091] In one embodiment, previously selected menu items of the drill-down level displayed in the second portion of the user interface display are displayed in a highlighted manner relative to previously non-selected menu items of the drill-down level displayed in the second portion of the user interface display.

[0092] In one embodiment, when the last level in a selected path of menu levels is reached, and, for example, a function related to a selected item in the last menu level is executed, the user interface can return the ongoing menu view to another item in a higher level, for example, the first menu list. For example, the ongoing menu of options may again be the first initial menu level and may be displayed in the first portion. In one embodiment, the first and second portions are linked to each other rather than being independent, making navigation more efficient, guiding the user along the path, allowing the user to see the path they are on, allowing deviations from the path set for the user to become alternative paths, for example, allowing the user to see previous and next breadcrumbs, allowing the user to know where they have been, and where they can go within the path of menu options. In one embodiment, the user interface can guide the user through efficient path options 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 conserve computer resources, for example, central processing unit (CPU) cycles, and memory usage spent on shuffling and switching processor threads and memory elements in the computer running the user interface.

[0093] 18-19, additional exemplary systems are provided for implementing the method described with respect to Figure 1. As discussed above, aspects of 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] FIG. 18 illustrates components of a graphical user interface (GUI) system, in one embodiment. One or more hardware processors 1804 may execute a graphical user interface module and perform the graphical user interface functions described above, thereby displaying the graphical elements described above on a user interface display device 1806 coupled to the one or more hardware processors 1804. A memory device 1802 may store a list of menus and a list of menu items or available options 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 the 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] 18 specifically refers to a GUI system, this is by way of example only, and it will be appreciated that the methods and techniques described herein may be implemented via other MUIs, such as text-based, virtual reality-based, augmented reality-based, mixed reality-based, etc.

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

[0098] For example, the hardware processor 1804 may perform the methods described with respect to FIGS.

[0099] The GUI techniques described above may be implemented using computer languages ​​such as, but not limited to, JAVA and JavaScript. In one embodiment, the functions and modules of the disclosed system and method may be implemented or performed in a distributed manner on different processing systems or on any single platform, e.g., accessing locally stored data or in a distributed manner over a computer network. Similarly, the disclosed software protocols and managers may be implemented or performed in a distributed manner on different processing systems or on any single platform, accessing locally stored data or in a distributed manner over a computer network.

[0100] The GUI technology may be implemented on any type of computing device, e.g., a desktop computer, a laptop computer, a mobile device (e.g., Android or Apple IOS), or a tablet, and may use any type of interface, e.g., a mouse, a touchscreen, etc. The 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, e.g., including: (a) a single robotically controlled 8-channel pipettor; (b) a single robotically controlled assay plate gripper arm; (c) a single 96-channel assay plate washer; (d) a single plate reader; (e) one or more plate shakers having a total capacity of at least five plate shaking positions; and (f) a processor adapted to execute an assay process for analyzing multiple samples in a 96-well plate. Other computing devices, machines, systems, and instruments include wearable devices, automotive computing systems, individual instruments including assay-related instruments such as plate washers, plate readers, plate shakers, incubators, workflow aid instruments such as loading carts (e.g., as described in WO 2018 / 017156 and WO 2017 / 015636, which are incorporated herein by reference in their entireties), medical instruments and machines such as MRI and CT machines, ultrasound systems, consumer products such as home appliances, home management systems, home systems including air conditioning and heating systems, clothes washers and dryers, dishwashers, ovens, slow cookers, and other cooking devices.

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

[0102] The systems and methods of the present disclosure may be implemented and run on a general-purpose computer or a special-purpose computer system (or device). The computer system may be any type of known or currently known system and may include a hardware processor, memory devices, storage devices, input / output devices, an internal bus, and / or communications interfaces for communicating with other computer systems, along with communications hardware and software, etc. The GUI techniques of the present disclosure may also be implemented in mobile devices, etc. Implementation of 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] 19 illustrates an exemplary computer system 100 that may implement the systems and / or methods 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. A register is a small storage device. A register file may be a set of multiple registers. A cache is a high-speed storage memory device, including, for example, static random access memory (SRAM) chips. The cache serves as a temporary staging area for holding data used by CPU 2. A simplified hardware configuration is shown. CPU 2 may also include other combinational circuits and storage devices.

[0104] One or more central processing units (CPUs) 2 execute instructions stored in memory 4, e.g., transferred to CPU 2 registers. Bus 6 is, e.g., 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 CPU 2 during execution. System components may also include input / output (I / O) controllers and adapters connected to CPU 2 and memory 4 via a bus, e.g., an I / O bus, and to I / O devices. For example, a display / graphics adapter may connect a monitor 28 or another display device / terminal (8), a disk controller 10 may connect a hard disk 24, e.g., for permanent storage, a serial controller 12, e.g., a universal serial bus (USB) controller, may connect 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, e.g., other machines. The system may also include expansion slots to accommodate other devices for connecting to the system. For example, hard disk 24 may store programs of instructions and data implementing the above-described methods and systems, where these methods and systems may be loaded into memory 4 and then loaded into CPU storage (e.g., cache and registers) for execution by the CPU (e.g., ALU and / or other combinatorial circuitry or logic). In another aspect, all or a portion of the programs of instructions and data implementing the above-described methods and systems may be accessed and / or executed over network 18 on another computer system or device. FIG. 19 is only one example of a computer system. Computer systems that may implement the techniques or systems of the present disclosure are not limited to the configuration shown in FIG. 19. Rather, other computer systems may implement the techniques of the present disclosure, including, but not limited to, specialized 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 causing a processor to perform one or more of the techniques described herein. In one embodiment, a computer-readable storage medium or device includes a tangible device capable of holding and storing instructions for use by an instruction-execution device. Examples of computer-readable storage media or devices may include, but are not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof, such as, but not limited to, 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 versatile disk (DVD), and memory sticks. A computer-readable medium may include both a computer-readable storage medium or a computer-readable transmission medium (as described above), which may include, for example, coaxial cable, copper wire, and fiber optics. Computer-readable transmission media may also take the form of acoustic or light waves, such as those generated in radio frequency, infrared, radio, or other media including radio waves, magnetic waves, or electromagnetic waves.

[0106] The term "computer system" as used herein may include various combinations of fixed and / or portable computer hardware, software, peripherals, mobile devices, and storage devices. A computer system may include multiple individual components that are networked or otherwise linked to perform in concert, or may include one or more stand-alone components. The hardware and software components of the computer system of 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 "function," which may be embodied as software, hardware, firmware, electronic circuitry, etc.

[0107] The storage devices 1120, exemplified by memory 4 and memory device 1802, may be implemented as one or more computer-readable storage media described herein and may be used to store various data and information related 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 be stored via a data storage command 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 a linked list, a b-tree, a binary tree, a heap, a stack, a queue, a hash table, a red-black tree, a binomial heap, a Fibonacci heap, or the like. In one example, the registration information may be stored in a registration table. The registration information includes at least one user identifier and one account number associated with a user. Because multiple users may be assigned the same account number, the system may track this using a shared account flag, such as a semaphore, a bit, or the like. If multiple users are assigned the same account number, the shared account flag may be set to a first particular value. Otherwise, the shared account flag may be set to another particular 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 a registration table. For each user identifier with the same account number, the shared account flag is set to a particular value and associated with the user identifier.

[0109] In other aspects, multiple account numbers may be linked together. In an embodiment, the user manager 1056 may issue commands to manage user account numbers. In one embodiment accordingly, the multiple account numbers may represent a team, such as a research team, a project team, a corporate team, a university team, or an experimental team. The system may track multiple account numbers and teams using multiple account flags. When different account numbers are linked, the multiple account flags may be set to a first specific value, or alternatively, the multiple account flags may be set to different specific values. Using multiple account flags is one way of tracking the linking of different account numbers, and the disclosure is not limited to this example. Other methods may be used. In one embodiment, the multiple account flag may be a column in a registration table. For each linked account number, the multiple account flag is 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. The login history data may be received via the input manager 1052, organized via the user manager 1056, and stored via the data storage manager 1064. The login history data may include a 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 of time. The predetermined period of time may be based on the particular application being run or to be run.

[0111] In other embodiments, the storage device 1120 can also store a user selection history. The user selection history may be received via the input manager 1052, organized via the user manager 1056, and 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 indefinite period of time. The predetermined period may be selected according to the MUI module in which the user selection was originally made. The predetermined period of time for the stored user selection history and login history data may be the same.

[0112] In other embodiments, storage device 1120 may contain exclusion information. Exclusion information may include menu items and / or options that are excluded from display at hierarchical menu levels on the MUI for one or more users, devices, or interfaces. Exclusion information may be managed by commands issued via exclusion manager 1058 and may be stored by commands issued via 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 navigate bidirectionally (backward and forward) between hierarchical menu levels, including allowing the user to view past or previous menu items, selected or unselected, where backward allows navigation to higher hierarchical menu levels and forward allows navigation to lower hierarchical menu levels. For example, various menu levels and / or options from one or more levels of a given path of a hierarchical menu can be viewed simultaneously on the MUI.

[0114] In one embodiment, display commands may be provided by the display manager 1050 for a particular set of hierarchical menu levels to be displayed in a particular portion of the MUI. The display commands are configured to cause one or more menus to be displayed in one or more portions of the MUI. A particular hierarchical menu level may include one or more menu items (or options). The display commands may include one or more menu items, a particular display order, display orientation, display size (and format), and display manner of the options, such as a scrolling method, although other ways of arranging and / or displaying the options are also contemplated. In one embodiment, the scrolling method may define the display orientation. Thus, a display command does not necessarily include a separate display orientation and scrolling method.

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

[0116] The display command may specify a scrolling method. For example, the display command may specify that the menu items be displayed, for example, as 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 the menu items be displayed, for example, 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 orientation of different commands (e.g., a first command and a second command) may specify that the orientations are substantially perpendicular to each other. In other embodiments, the orientations may be horizontal, substantially horizontal, vertical, substantially vertical, concentric, and substantially concentric across from each other. As used herein, substantially may be +5° or −5°. In other aspects, substantially may be +10° or −10°. In other aspects, substantially may be +15° or −15°. In other aspects, substantially may be determined by a percentage, such as 80% or 90%.

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

[0119] 3 is a flow diagram illustrating, in another aspect, a method for interactively displaying interactive items on a user interface display for computer user interaction, e.g., switching between vertical and horizontal menu levels, in detail. 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 portion of the user interface display. The list of menu items may be displayed in a first visual orientation on the first portion. For example, the first visual orientation may be a 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 display manager 1050.

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

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

[0122] The first display command includes the menu items of the first menu (in one embodiment, stored in the storage device 1120, the scroll method / orientation and size (and format)). 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 position of the display, for example, the position of the first portion. The first portion may be in a center position on the MUI. Each menu item may be selectable by the user.

[0123] In one embodiment, the first portion may include a decision-making zone. The decision-making zone may be located at a central position within the first portion. The decision-making zone may be a position within the first portion or within the active portion where a salient or highlighted menu item is displayed for immediate selection. For example, in FIG. 2A , menu item 4 is shown in the decision-making zone and is displayed in a larger font size than the remaining menu items so that it is the salient or highlighted menu item displayed for immediate selection. The first display command for triggering the presentation of the first menu may specify that the menu item displayed within the decision-making zone be emphasized or highlighted, e.g., displayed in a larger font size than other menu items not within the decision-making zone. In other aspects, the menu item displayed within the decision-making zone may be highlighted using bolding, italics, or a color different from the background, or may be underlined.

[0124] In other embodiments, the first display command may specify that menu items displayed outside the decision-making zone should be made less prominent relative to other menu items within the decision-making zone, for example by minimizing or dimming the menu items.

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

[0126] As shown in FIG. 2A , all first menu items 202 displayed in first portion 204 are selectable. Menu item 4 is displayed as the prominent menu item and is highlighted as immediately selectable. As used herein, “instantly selectable” means that a single action, such as a click by the user, causes selection of the menu item. Menu item 4 is selectable and highlighted as the prominent menu item, while the other menu items (1, 2, 3, 5, and N) are not highlighted as backsliding menu items. Backsliding menu items are not instantly selectable, meaning that more than one user action is required for selection. When the user clicks on a highlighted instantly selectable menu item, it is selected. Other menu items may be highlighted for immediate selection by rolling the wheel or clicking. Upon receiving a signal indicating a click on an instantly selectable menu item by input manager 1052, input manager 1052 executing on processor 1110 detects selection of the prominent instantly selectable menu item. In response to the selection, input manager 1052 issues a command to menu manager 1054 indicating the selection. The Menu Manager 1054 then determines the new menu arrangement to be displayed according to the selection and provides rearrangement commands to the Display Manager 1050 to cause the MUI to change.

[0127] 3 , in operation 304, in response to detecting a selection of a menu item from the list of menu items, the list of menu items is repositioned to a second portion of the user interface display. The list of menu items is displayed in a second visual orientation on the second portion, the second visual orientation being substantially perpendicular (e.g., vertical) to the first visual orientation. For example, the second visual orientation may be a horizontal orientation.

[0128] The rearrange command rearranges the first menu of menu options 202 from the first portion 204 to the second portion 208 of the MUI display 206. FIG. 2B illustrates the results of the rearrange command. The rearrange command may include the menu options of the first menu to be displayed in the second portion 208, the size and orientation of the display, the visual components required for the display, an indication of which menu item was selected to cause the rearrangement, and any other information discussed herein with respect to display commands. The rearranged first menu, displayed in the history portion or second portion 208 as a past menu, may include one or more or all of the menu items 202 and options previously available to the user. The menu item 202 selected by the user to be rearranged becomes the previously selected menu item, and any menu item not selected from the menu items 202 becomes the previously unselected menu item. The previously unselected menu items represent previously navigated hierarchical menu levels. After rearranging the menu items 202 of the first menu, the display manager 1050 causes the MUI to display in the active or first portion 204 the submenu items 210 of the second menu as new current or subsequent level menu options for the user to interact with in response to the first menu selection. As shown in FIG. 2B , the subsequent or second level menu options include the second submenu items 210 displayed in the active or first portion 204 of the MUI display 206.

[0129] In a method according to one embodiment, a rearrangement command is issued upon receiving a signal from input manager 1052 indicating that menu item 202 has been selected from first portion 204. For example, menu manager 1054 provides the rearrangement command to display manager 1050. The rearrangement command instructs display manager 1050 to move the first menu from first portion 204 of MUI display 206 to second portion 208 of MUI display 206 in a second menu. Second portion 208 is in a different location on MUI display 206 than first portion 204. Because a menu item was selected from the first menu of menu item 202, the rearranged first menu of menu item 202, as displayed in second portion 208, now includes both previously selected menu items and previously unselected menu items (e.g., one or more menu items that the user was able to select but did not select). The rearrangement command may include the first menu item, the scrolling method and / or orientation, the display size (and format), and the location of the second portion.

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

[0131] In one embodiment, the orientation for displaying menu items 202 in the first menu in second portion 208 is different from the orientation for displaying sub-menu items 210 in the second menu in first portion 204. For example, the orientation of menu items 202 in second portion 208 may be substantially perpendicular to the orientation of sub-menu items 210 in first portion 204. The rearrange command may specify that the orientation of menu items 202 is horizontal (and the first display command may specify that the orientation of menu items 202 is vertical). In other embodiments, the orientations may be reversed, where menu items 210 in first portion 204 are horizontal and menu items 202 in second portion 208 are vertical. In an embodiment, first portion 204 is located at the bottom center of MUI display 206 and second portion 208 is located at the top of MUI display 206.

[0132] The rearrangement command may also specify different sizes for the menu items. For example, the menu item selected from the first menu (which triggered the rearrangement) may be specified in a highlighted manner, such as being displayed in a larger font size than the unselected menu items. In other aspects, the selected menu item may be highlighted using bolding, italics, or a color different from the background, or may be underlined. In another aspect, the rearrangement command may also specify the relative position of the menu items 202 within the second portion 208. For example, the selected menu item may be positioned in a center position within the second portion relative to the other menu items (unselected menu items).

[0133] In other aspects, unselected menu items from a hierarchical menu level may be displayed in a less prominent manner. For example, a rearrange command may specify that unselected menu items be displayed in a smaller font size or dimmed font relative to selected menu items. In other aspects, a rearrange command may specify that unselected menu items be displayed further away from the center of the second portion than selected menu items for the same hierarchical menu level.

[0134] The first and second portions may be displayed on the user interface display so that they do not overlap. A menu item relocated to the second portion may be selectable from its position or location, and the selected menu item may be graphically highlighted, for example, to provide a visual indication of which item was selected from the list. The selected menu item may be centered relative to other menu items to the left and / or right of the selected menu item. Submenu items that appear in the location where the relocated menu item was displayed (prior to the relocation) are also selectable items. FIG. 2B shows an example user interface display in one embodiment with a rearranged list of menu items. As shown, menu item 202 is relocated and displayed horizontally, e.g., above first portion 204, to second portion 208 of display 206. As described in more detail below, the second portion of the display may also include multiple levels of menu items, e.g., levels of past decisions and options at those levels that were not selected. Thus, 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, such as 1-2, 1-3, 1-4, 1-5, 1-6, 1-7, 1-8, 1-9, 1-10, 1-11, 1-12, 1-13, 1-14, 1-15, 1-16, 1-17, 1-18, 1-19, 1-20, and nested ranges therein, such as 2-20, 2-19, 2-18, 3-20, 3-19, 3-18, etc. The second part visualizes, for example, a representation of the paths of past decisions that were made and other decisions that were not made (other paths). In one embodiment, past decisions made (selected menu items) may be, for example, vertically aligned, for example, center aligned.

[0135] The second portion 208 may display the first menu items 202 in response to a rearrangement command of a first menu of user-selectable options displayed on the second portion 208 of the MUI display 206. As discussed above, the rearrangement 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 and previously unselected menu items. The first menu may include one or more of the first menu items 202 selectable by the user. The menu items 202 may be instantly selectable or non-instantly selectable.

[0136] The second portion 208 may also include one or more decision-making zones. The rearrangement command may also specify that menu items displayed within the decision-making zones be emphasized or highlighted. In other aspects, menu items displayed within the decision-making zones may be highlighted using bolding, italics, or a color different from the background, or may be underlined. In other embodiments, the rearrangement command may specify the same. In other embodiments, the rearrangement command may specify that menu items displayed outside the decision-making zones be de-emphasized or unhighlighted.

[0137] In the MUI display 206, both the first portion 204 and the second portion 208 are displayed so that they are viewable, e.g., simultaneously. The MUI display 206 may be presented via one or more physical display screens. The second portion 208 may include one or more menus, each including both previously selected and previously unselected menu items from previously navigated hierarchical menus. In the representation shown in FIG. 2C , the second portion 208 (the history portion) includes menu items 202 and submenu items 210, each of which was included in the first portion 204 in a previous MUI representation. The previously selected menu items 202 and submenu items 210 (i.e., menu items from which sub-submenu items 212 are displayed in the first portion) may be highlighted or accentuated to indicate that they were previously selected. As shown in FIG. 2C , menu item 4 and submenu item 3 are highlighted to indicate that they were previously selected.

[0138] Previously unselected menu and submenu items are displayed as selectable options. Previously selected menu items (or choices) may also be displayed as selectable options, both of which are displayed in the second portion 208 (e.g., a history portion, which may include one or more menu items previously available to the user). The history portion contrasts with the active portion (e.g., located in the first portion of the display), which may include the current user-selectable choices for the current hierarchical menu level. The history portion may also allow the user to make selections, for example, by selecting between previously selected hierarchical levels and / or menus. In this manner, the history second portion 208 may represent a "breadcrumb trail" that shows the user the ordered path of selections made to arrive at the current menu, as displayed in the active first portion 204. Further details of selections made in the second portion 208 are provided below.

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

[0140] In other embodiments, commands (e.g., rearrangement commands, etc.) may be provided by menu manager 1054 to move or rearrange menus from one portion of MUI display 206 to another portion of MUI display 206. In one embodiment, moving or rearranging menus and / or menu items may include providing a command to move a menu from one portion of the display to another. In another embodiment, moving or rearranging a menu may include issuing multiple commands, for example, one command to remove the menu from first portion 204 of the display and another command to display the menu (either in the same format and / or orientation or in a different format and / or orientation) on second portion 208 of the display. This rearrangement may occur, for example, in response to a user selection from a menu (e.g., the first menu).

[0141] 3, in operation 306, a first list of sub-menu items associated with the selected menu item is displayed in a first visual orientation in a first portion of the user interface display where the list of menu items was previously displayed before being relocated to the second portion. As shown in FIG. 2B, the first list of sub-menu items 210 is displayed, for example, vertically in first portion 204.

[0142] Referring back to FIG. 3 , in operation 308, in response to detecting a selection of a submenu item from the first list of submenu items, the first list of submenu items is rearranged to a second portion, where the first list of submenu items is displayed in a second visual orientation and stacked with the list of menu items displayed in the second portion. In operation 310, in the first portion of the user interface display, a second list of submenu items associated with the selected submenu item is displayed in the first visual orientation, e.g., vertically. FIG. 2C shows an example of a user interface display with a second list of submenu items in one embodiment. As shown, the first list of submenu items 210 is rearranged to the second portion 208, e.g., stacked below the rearranged list of menu items 202, e.g., stacked horizontally. In the first portion 204, a second list of sub-submenu items 212, i.e., the submenu items associated with the selected submenu item, is displayed. Depending on the depth of the navigated menu or submenu, the horizontal menu structure in the second portion 208 may accumulate a number of menu levels that exceed the number that can be displayed together in the display portion of the second portion 208 (e.g., the number of stacked levels exceeds the screen portion allocated to the horizontal menu structure of the second portion 208). In one embodiment, the horizontal menu structure of the second portion 208 may show n number of menu levels (e.g., the last three submenus) to enable a scrolling function. For example, scrolling up allows the user to view other menu items. The number n may be any number, including but not limited to, three (e.g., 2, 3, 4, 5, etc.). In another embodiment, m top menus (e.g., two) may be displayed with one bottom submenu to provide top-level context for the final decision. The number m may be any number, including but not limited to, three (e.g., 2, 3, 4, 5, etc.). The scrolling function allows other menu items to be displayed, for example, the user can scroll to view other menu items.The user may also expand entire multi-level menus and submenus.

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

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

[0145] 2A-2C illustrate the first visual orientation as vertical and the second visual orientation as horizontal, the orientations can be switched. For example, the first visual orientation can be horizontal and the second visual orientation can be vertical. In other embodiments, the first and second visual orientations can be any other position indicating orientations.

[0146] As noted above, the menu items and associated submenu items may be displayed as slider graphical elements, rotating wheel graphical elements, or other graphical user interface elements, such as concentric wheel elements, as described below with respect to Figures 2H-2J.

[0147] In embodiments, the ordering or placement of menu items within those menu levels may be determined according to attributes of the menu items. The display style of a menu item may be based on attributes selected from whether the menu item is a previously selected item or a previously unselected item, whether the menu item is selectable or unselectable, 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 embodiments, the manner in which menu items are adapted to be displayed (i.e., the ordering, arrangement, coloring, and presentation of the menu items) may be determined according to a number of different factors. For example, menu manager 1054 and display manager 1050 may, together, be configured to highlight selected or previously selected menu items, menu items currently available (i.e., selectable) to the user, and / or menu items positioned in a decision-making zone of first portion 204 or second portion 208. Menu manager 1054 and display manager 1050 may further be configured to obscure unselected or previously unselected menu items, menu items currently unavailable to the user, and / or menu items positioned away from the decision-making zone. In some embodiments, immediately selectable menu items may be highlighted, and non-instantly selectable items may be obscured. In some embodiments, highlighting or obscuring a menu item may include highlighting or not highlighting a menu item, as discussed herein. Highlighting or emphasis may include, for example, bolding, increasing font size, changing font, underlining, changing brightness or contrast, or adjusting position on the display relative to other items. Non-highlighting or de-emphasizing may include decreasing font size, changing font, dimming, changing brightness or contrast, or adjusting position on the display relative to other items.

[0149] The MUI allows the user to jump to different paths of menu items (e.g., by selecting one or more additional menu items at the same, higher, or lower hierarchical levels of the menu) by allowing the user to select a previously unselected menu item from a previously navigated menu level displayed in the second portion 208 of the MUI display 206 and select a newly displayed menu item on the first menu displayed in the first portion of the ongoing menu. As discussed above with respect to FIG. 2C, previously navigated menu items (including submenu items, sub-submenu items, etc.) may be relocated to the second portion 208 after the menu item is selected.

[0150] Previously selected menu items in the second portion 208 may be highlighted or accentuated to visually indicate the menu path taken to arrive at the menu or submenu currently displayed in the first portion 204. A previously unselected menu item from the second portion may be selected to allow the user to jump to that branch of the menu. In the example of FIG. 2C , the user previously selected menu item 4 and submenu item 3. Selecting a new, previously unselected submenu item 210 from the second portion 208 causes the menu manager 1054 to issue a command for a new list of sub-submenu items 212 associated with the newly selected submenu item 210 to be displayed as the ongoing menu displayed in the first portion 204. Selecting a new, previously unselected menu item from menu item 202 causes the menu manager 1054 to issue a command for the display of a new list of submenu items associated with the newly selected menu item 202 so that the ongoing menu is displayed in the first portion 204. In this way, the user can actively jump between various portions 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 portion before the subsequent menu in the first portion is displayed. In an embodiment, as disclosed in more detail below, navigating through menu items at the executable menu level to the final branch in the menu tree allows the user to make one or more parameter selections. If the user bypasses an execution-level menu, the parameters currently selected when the user bypassed 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 an execution-level menu, the last selected parameters will be displayed.

[0152] Previously unselected menu items may be selectable within the past menu of the previously navigated menu item. In embodiments, previously unselected menu items may be instantly selectable, requiring only a click for selection, or may be non-instantly selectable, requiring an additional step of highlighting the menu item before selection. In embodiments, previously selected menu items may be unselectable because the user has already selected them. In further embodiments, only previously selected menu items from the lowest hierarchical level of the past menu (i.e., the menu immediately preceding the current first menu) are unselectable, while previously selected menu items from higher hierarchical levels remain selectable. In the example provided by FIG. 2C , submenu item 3 may be unselectable and menu item 4 may be selectable.

[0153] In embodiments, various menus are displayed on a background. In one embodiment, the menus are overlaid on the background. The background may be comprised of one or more colors. In one embodiment, at least a preset percentage of the background pixels may be a solid color. For example, at least a preset percentage of the background pixels may be black. For example, 75% of the background may be a solid color (e.g., black, white, gray, etc.). The particular percentages are described as examples, and other percentages may be used.

[0154] In embodiments, the display and rearrange commands may specify a background that includes a preset percentage and color, such as black, white, gray, etc. In certain embodiments, the background may also include areas of the menu other than the text (e.g., menu items). In one embodiment, the text of the menu is displayed in a color to contrast or highlight the text with the background. For example, if a black background is used, white or yellow may be used for the text color, although other colors may also be used. In other embodiments, the background and / or text may be composed of two or more colors.

[0155] In some embodiments, the initial or first menu, i.e., the start-up menu, may be a default menu displayed upon login for a registered user. In one embodiment, the default menu may be customized for a particular user identifier. In other aspects, the default menu may be specific to a MUI module. For example, the default menu may include a list of assays, tests, activations, clinical trials, etc. as menu items. In embodiments according to the present disclosure, the default menu is determined according to one or more of the MUI module being activated, the location of the device activating the MUI module, the user identifier, and the application of the menu. For example, a device located on a user's desktop may activate a MUI module that defaults to a default menu suitable for selecting options for experimental design or experimental analysis. In another example, a device located on a clinical instrument may activate a MUI module to provide a default menu suitable for selecting options for launching an experiment and collecting data. In embodiments, the default menu may be a first menu, a second menu, a third menu, and / or any other menu from a level in a hierarchical menu tree.

[0156] In one embodiment, any menu provided in any portion of the MUI display may include a search function. The search function allows a user to enter keywords or other input associated with a menu item (option). User input is received via input manager 1052 and forwarded to menu manager 1054 for searching purposes. Searching allows functions (menu items) to be filtered using the entered keywords or other input, reducing the time required to find a desired menu item. An interface for the search function may be located in a central location in the respective portion of MUI display 206, or alternatively, in another portion of MUI display 206. In a further embodiment, no visual interface for the search function is provided. In such an embodiment, a user may access the search function by simply typing.

[0157] In one embodiment, any menu item that matches or partially matches the keywords may be displayed to highlight the menu item. For example, the menu item may be displayed in a larger size than other menu items that do not match or partially match. In other embodiments, the menu item may be highlighted using bolding, italics, or a color different from the background, or may be underlined. In other embodiments, menu items that do not match or partially match the keywords may be made less noticeable, for example, by displaying reduced or lightened text relative to the text of menu items that the menu item matches or partially matches. In embodiments herein, a slider or wheel may automatically advance and / or rotate to display menu items that match the search terms.

[0158] In one embodiment, a first menu selection may act as a filter on a second menu. In a hierarchical tree, several items in a first menu may each lead to the same second menu. However, when a first menu selection is made, the menu items shown when the second menu is displayed are determined. In a simple example, the first menu may include menu items related to team roles, and the second menu may include menu items related to team responsibilities. Selection of a particular team role in the first menu may filter the second menu 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 the menu items displayed in any other menu. For example, in one embodiment, a series of items in a first menu may be a series of category filters, each leading to a second menu. Each second menu leads to a series of submenus, ultimately leading to one or more action 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, which 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 standard discussed herein. For example, a menu level may include a visual and / or animated display rather than a text-based visual component. Exceptions may be implemented, for example, in situations where information may be better conveyed through alternative means. For example, as discussed above, a performance-level menu may include a walkthrough, which may be best presented via a video or series of images. In another example, a performance-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. FIG. 2P illustrates an example of an organizational user interface including an advanced context menu 270. The advanced context menu 270 contrasts with the first and second portions, which together provide a “direct workflow mode.” The advanced context menu 270 may be accessed via an advanced context menu selector 290, which, in embodiments, may be present on some or all screens of the organizational user interface. The advanced context menu 270 provides additional advanced menu items 271 in addition to the items displayed in the ongoing menu in the active first portion 204 or one or more past menus displayed in the history second portion 208. The advanced context menu 270 may be accessed by clicking or hovering over the advanced context menu selector 290, or by otherwise indicating a desire to access the advanced context menu 270. The advanced context menu 270 includes the selection of the advanced menu item 271.

[0162] Selection of advanced menu items 271 may include items displayed in the ongoing menu in the first (active) portion 204 and items displayed in the previous menu in the second (history) portion 208. According to one embodiment herein, advanced menu items 271 in advanced context menu 270 may be highlighted. For example, advanced menu items 271 may be displayed in a larger font size. In other embodiments, menu items may be highlighted using bolding, italics, a color different from the background, or may be underlined.

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

[0164] The advanced context menu 270 provides the user with a larger array of accessible menu items without cluttering the active or history portions. 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 described in more detail below.

[0165] In embodiments, the advanced context menu 270 may include three sections. The first, top section 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 section 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, bottom section 274 of the advanced context menu 270 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 described advanced menu items 271 may be presented in a different order.

[0166] In embodiments, when the advanced context menu 270 is selected, the MUI dims and / or obscures other graphics, text, etc. The advanced context menu 270 is displayed on a transparent background so 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 be displayed in the foreground of the UI display to prompt the user for additional information or notify the user of an error. The background of the dialog box is further adapted to match the backgrounds of the first and second portions of the UI display, and further, one or more of the text, graphics, photos, and videos displayed in the background of the first and second portions of the UI display are 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, i.e., a first menu, a second menu, a third menu, etc., may be excluded or limited from display when that menu is displayed. Exclusions and limitations 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 not necessarily all items from that menu. Menu items at a hierarchical menu level may be excluded or limited 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 a menu tree may also be excluded based on an exclusion table. In certain embodiments, the exclusion or limitation information may be stored in the storage device 1120. The exclusion or limitation information may be stored as a data structure. Any of the data structures described herein may be used.

[0168] Exclusion or restriction information can be used to exclude menu items from the view of particular users, groups of users, types of users, etc. For example, an Administration menu item or menu level may be excluded from the view of users or operators who are engineers or technicians. In another example, a Design menu item or menu level may be excluded from the view of users or operators who are lab assistants or lab technicians.

[0169] The user identifier, account number, and menu items and / or menus for exclusions can be entered by an administrator. For example, an administrative console module, discussed in more detail below, may be used to manage and generate the exclusion table. Management may occur when a user registers with the system. In other embodiments, exclusion information may be added after registration and updated periodically.

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

[0171] In particular embodiments, before issuing a command to display any menu, the menu manager 1054 may check an exclusion table (e.g., stored in the storage device 1120) to determine whether any menu items in the initially displayed menu (e.g., the default menu) are 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 occurs, the menu items listed in the exclusion table are excluded from displaying in the initially displayed menu. This exclusion may be accomplished through the issuance of a separate exclusion command and / or instruction, or alternatively, the exclusion may be accomplished by modifying any display command that causes the available menu items to be displayed. The menu manager 1054 may issue a first command that removes the menu items from the list of menu items in the initially displayed menu (e.g., the default menu) and does not include the removed menu items.

[0172] In particular embodiments, prior to issuing a rearrange command, each time 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 lists menu items at a hierarchical menu level lower than the hierarchical menu level currently displayed by the MUI display 206 in a manner that excludes them (or whether a lower hierarchical menu is excluded). Login history data and an exclusion table may be used to make this determination. The login history data may be used to verify that the same user (user identifier or account number) is still logged in and may be matched with a 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 in place of the login history data for this determination. In other embodiments, a similar determination is made prior to issuing any rearrange or display commands.

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

[0174] As explained above, an account number may be associated with multiple users (user identifiers). Thus, when using the account number as an exclusion criterion, all users associated with the account number may exclude a menu item from being displayed on the MUI display 206.

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

[0176] In other embodiments, instead of excluding menu items, the menu items may be moved to their respective menu positions to make the menu items less prominent 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 the menu items on the hierarchical menu levels. Subsequent commands (first command, second command, and / or third command) may reflect the changed menu item positions.

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

[0178] The 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; other identifiers, such as an Internet Protocol (IP) address, machine name, etc., may be used. In one embodiment, one column in the table may include an identifier, for example, a MAC address. A second column in the table may include menu items or hierarchical menu levels, each of which is excluded from display, associated with an identifier (e.g., a MAC address).

[0179] In other embodiments, instead of a single table (or multiple tables), a list of menu items and / or hierarchical menu levels is stored in association with an identifier (eg, a MAC address).

[0180] The device identifier, such as a MAC address, and the 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 particular embodiments, upon receiving login history data or in response to receiving a notification, and before issuing any command to display any menus (and menu items), the hardware processor executing the input manager 1052 may check the exclusion information in the storage device 1120 to determine whether any menu items in the initially displayed menu, or menu items associated with the selection, are excluded for the device.

[0182] In one embodiment, the menu manager 1054 may compare the device identifier with device identifiers listed in the exclusion information. If there is a match, the 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., default menu) or the ongoing menu associated with the selection includes one or more menu items listed as excluded, the menu manager 1054 may remove the excluded menu items from the menu before issuing the display command, and then issue the 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, particular menu items (or hierarchical menu levels) may be excluded based on which hierarchical menu level is currently displayed as the current menu (first portion) or the previous menu (second portion). In one embodiment, one column in the exclusion table may contain the menu identifiers of the hierarchical menu levels. A second column in the table may contain the menu items or hierarchical menu levels, respectively, associated with the menu identifiers, that are to be excluded from display.

[0184] The menu identifiers represent hierarchical menu levels that are displayable in either the first menu or the 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 particular embodiments, when a hierarchical menu is displayed as the ongoing menu in the first portion 204 or the previous menu in the second portion 208 and a selection is made, the menu manager 1054 checks the exclusion information to determine whether any menu items associated with the hierarchical menu level selected for display should be excluded before issuing a command. Based on that determination, the menu manager 1054 may remove the excluded menu items from the menu before issuing a response command, and then issue the response command with the menu items removed. This exclusion may be implemented through the issuance of a separate exclusion command and / or instruction, 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 another embodiment, instead of a show or rearrange command being issued with the menu items cleared, a remove command can be issued by the remove manager 1058 in combination with the show or rearrange command. In this embodiment, the show command has all menu items associated with the menu, and the remove command causes the display manager 1050 to remove the executed menu items included in the remove command before causing their display.

[0186] In other embodiments, the number of menu items displayed may be limited by menu manager 1054 based on frequency of use. For example, in one embodiment, the number of menu items may be limited based on frequency of selection. In particular embodiments, the frequency may be determined over a predetermined period of time. The frequency of selection may be preset or customizable and may include, for example, a frequency of 50% to 80%, although other frequencies of selection are contemplated as well. Limiting the display of menu items to include only menu items used above a certain threshold frequency reduces clutter within the menu system and streamlines the menu experience.

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

[0188] In certain embodiments, one or more user selections may be tracked for a preset period of time. The period may be one day, one week, one month, or other preset or customizable period. The particular period may be based on the application, such as the type of clinical trial or study, the type of study, the type of organization (e.g., university, corporate), etc. Tracking may be repeated for each preset period.

[0189] Each time a notification is received by the hardware processor executing 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 preset 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 specified time period, the input manager 1052 determines the selection frequency of 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 is selected and the total number of selections (within the specified time period) by the user identifier.

[0191] In other embodiments, the determination may be based on the account number in addition to the user identifier. For example, the input manager 1052 may determine the frequency of menu item selection by at least two user identifiers having the same account number. In this example, if a single account number is associated and / or linked with two or more user identifiers, the users form a team. In another example, a team may include two or more account numbers associated and / or linked together. In yet another example, N unique users may form a team associated and / or linked with M unique account numbers, where N is greater than M. Identifying user identifiers with the same account number may 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 selections within a period of time.

[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 also determined from the menu item selection table). The frequency is then based on the aggregated selections of the menu items and the aggregated total selections.

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

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

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

[0196] In other embodiments, the frequency determination may be based on all selections, regardless of 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 of each menu item relative to the total number of selections (of any menu item) within a time period.

[0197] The above frequencies may be used in conjunction with a limiting command issued by the menu manager 1054. The function of the limiting command is similar to that of the exclude command, as discussed above. The limiting command serves to limit the particular menu items displayed based on one or more criteria. For example, the limiting command may be based on (a) how often the user previously selected the item while logged into the account. In one example, this determination may occur based on a given time period. In another example, the determination may be based on the number of times a given user logs into their account. Another criterion includes (b) how often the item was previously selected while at least two users were logged into the account. In particular embodiments, this may include an amount of time for a given user, or an amount of time based on the total time the user was logged into the account. Alternatively, it may be based on the total number of logins or the total number of logins for a given user. Further criteria may include (c) how often the user previously selected the item while logged into an account associated with multiple accounts, or (d) how often at least two users previously selected the menu item while 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 one or more users remain logged in to an account or the number of account logins. Additionally, the criteria may include (e) the frequency with which any user previously selected an item while logged in to any account, and / or (f) the frequency with which any user previously selected an item while logged in to any account associated with multiple accounts. In these two examples, a data structure such as a table (or any other data structure described herein) may be used to track the previously selected items, and the table may be periodically cleared after a given period of time has passed or after a certain number of total logins by one or more users have occurred.In certain embodiments, the criteria set forth in (c), (d), and (f) above may apply to team accounts, particularly if the users of those accounts are team members with one or more teams associated with multiple accounts.

[0198] If the determined frequency is equal to or greater than a threshold percentage, the menu item may be restricted for an immediate period of time. The threshold may be application-based. In one embodiment, the threshold percentage may be equal to or greater than 50%. In another embodiment, the threshold percentage may be equal to or greater than 60%. In yet another embodiment, the threshold percentage may be equal to or greater than 70%. In a further embodiment, the threshold percentage may be equal to or greater than 80%. In other embodiments, the threshold may be a range of percentages. For example, the threshold percentage may be in the range of 75% to 85%. Specific percentages are described herein by way of example, and the threshold percentages are not limited thereto. 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 of a menu item divided by the number of selections of another menu item. For example, 9:1, 7:1, 5:1, 3:1, or any other suitable ratio may be used.

[0200] In other embodiments, the number of times a menu item is selected may be used instead of the 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] Once it is determined that a menu item may be restricted, a hardware processor may determine which menu items may be displayed on the MUI display 206 during an immediate period of time, and which menu items are restricted. According to an embodiment, any menu item determined to have a frequency above a threshold percentage may be displayed (e.g., without limitation).

[0202] In further embodiments, the display restriction may be based on menu items having a selection frequency below a certain threshold, for example, below 50%, 40%, 30%, 20%, 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 may occur, for example, if a particular user has not selected one or more menu items for a particular period of time. Similarly, one or more menu items may be restricted based on menu items designed to be unavailable to a collection 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 period of time may affect whether a restriction command is issued for those menu items. Other embodiments contemplate issuing restriction commands in a manner similar to the previous two examples (i.e., based on the frequency with which menu items are selected by users associated with a team) rather than for individual teams and / or collections of teams. Furthermore, in other embodiments, menu items may be restricted based on a particular machine or collection of machines running a computer application on which one or more users are logged in.

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

[0205] In other embodiments, the limit command may include menu items other than the menu items determined to have a frequency above a threshold percentage. Upon receiving a display command and a limit command, the display manager 1050 may remove or clear menu items that are included in the limit command and that are also included in the display command before causing the menu items to be displayed in 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 remove menu items other than those determined to have a frequency above a threshold percentage.

[0207] Through the use of the limit command, menu items (user-selectable options or choices) may be limited to a smaller number of menu items on the first menu and the second menu. For example, the first menu may include nine menu items, but the use of the limit command limits the total number of displayed menu items 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 or less. 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 with choices. In an embodiment, menu items excluded from display due to the limit command are provided in the advanced context menu 270. In an embodiment, menu items excluded from display based on the limit number may be selected according to frequency of selection.

[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 is greater than a limited number (e.g., 7), the menu manager 1054 may increase the threshold percentage to decrease the number of menu items with a selection frequency greater than the threshold percentage. Thus, the menu manager 1054 may be configured to select and display a certain number of menu items with the highest selection frequency.

[0209] In one embodiment, the restriction feature may operate as follows, as applied to any type of MUI module: A threshold percentage may 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, meaning that only menu items with a selection frequency greater than 90% or 80% are displayed. In one example, the selection frequency may be applied based on the user login session, meaning that menu items that are only used 90% or 80% of the time the user is logged in are displayed. The control feature may apply to one or more menu levels, i.e., a first menu level, a second menu level, etc. In some embodiments, the threshold may vary based on the menu level (e.g., lower levels may have lower frequency requirements for display because there are often a greater number of options at lower levels, and they 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 that changes according to the current menu being displayed. In this way, the user's choices are limited to those most frequently used across the MUI, which can significantly speed up user navigation. In certain embodiments, the options excluded as described above may be available only in the advanced context menu. Thus, in the 90% example, 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 90% / 10% and / or 80% / 20% values ​​are exemplary only, and other values ​​may be selected according to the MUI module being implemented. In one example, the limiting function may also be based on a default protocol compared to a user-customized protocol. For example, a vendor may market an assay kit that includes a standard protocol that still allows for customer modifications. The standard protocol option may be included in available menu items that are displayed in the active portion as the user navigates through the menu system, while available customer modifications may be displayed in an advanced context menu. This division of menu items can be adjusted based on actual user interaction after that particular assay kit has been used by the user several times.

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

[0212] In certain embodiments, after a period of time has passed, the menu item selection table may purge the selection history for new determinations, in this example making previously excluded menu items available again.

[0213] In embodiments, the MUI can provide team integration through communication between multiple MUI modules. An integrated system managed by a system consistent with 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), a management console module, an experiment design module, an inventory management module, an experiment analysis module, and an experiment procedure module can be provided. The management console module can provide features and functionality for managing various users, operators, instruments, and teams. The experiment design module can enable one or more members of a team to design experiments to be performed by other members of the team. The inventory management module can enable other team members to review inventory and order more consumables in light of experiment history and future planned experiments. The experiment procedure module can enable team members responsible for initiating experiments to access and implement already designed experiments through interactions between the MUI, operators, and external systems. Finally, the experiment analysis module can enable other team members to access the results of experiments after they have been conducted. Based on the user and team setup provided via the administrative console, each user may log into the system and be provided access to the modules necessary to complete their assigned tasks. In embodiments, the necessary modules may be installed on a computing device appropriately located to complete the task (i.e., an experimental procedure module may be installed on a device connected to an experimental instrument, and an administrative console module may be installed on a desktop device). In this manner, the system provided herein enables the integration of workflows among multiple team members using a single, consistent interface.

[0214] In embodiments, the display manager 1050 may 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 may be provided to alert the user that processing is occurring, preventing wait times. In one embodiment, the work status indicator may be provided via a light fountain display presented in a portion of the screen not occupied by the active or historical portions. For example, the bottom of the screen, centered below the active portion, may be used for the light fountain display. The light fountain may provide a series of cascading bars displayed 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 as four rows of elongated bars. Each row may include multiple bars of different lengths, for example, between two and twenty. When the system is processing, the bars may flash in different shades of white and blue for different lengths, creating the impression of a waterfall or light fountain.

[0215] The embodiments described herein further include a method for designing a user interface system. For example, such a method may include designing a MUI consistent with embodiments herein. The method for designing a user interface system may include generating a hierarchical menu tree as described herein. The hierarchical menu tree may include a series of menus including menu items, each of which leads to a subsequent series of menus. The method for designing a user interface system may further include selecting an action menu that terminates a branch of the hierarchical menu tree, the action menu configured to execute one or more commands in software, provide one or more instruction sets to a user, and / or output one or more commands to a connected device, system, instrument, or machine. The method for designing a user interface system may further include configuring each of the menus in the hierarchical menu tree in one or more display modes, including at least an active display mode for display in an active portion of the user interface and a history display mode for display in a history portion of the user interface. Further aspects of the method for user interface design may further include a method 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 for 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 explanations for the presented options. As discussed above, MUIs provide a large amount of white space or background space. Therefore, the help option may be presented as a pop-up or dialog box that points to the portion of the MUI for which the user seeks help, without disrupting the original MUI display. In embodiments, enabling the help feature may cause a dialog box to appear when the user places the cursor over or otherwise views any item within the MUI.

[0217] In further embodiments, the MUI history portion may be further adapted to display menu items of a menu subsequent to the ongoing menu. For example, as a user navigates through the ongoing menu, the user may highlight or highlight different menu items, for example, by scrolling a vertical wheel. Submenus associated with the highlighted menu items may be displayed in the history portion to provide a visual representation of subsequent menus in the ongoing menu, including future items that may be subsequently selected.

[0218] In embodiments, as discussed above, the first active portion and the second historical portion are each adapted for consistent display within the same portion of the MUI. The positioning of each of these portions is not limited to a particular location on the MUI, but in certain embodiments, the location is maintained once selected. In this manner, the active portion of the MUI display is adapted for consistent display within the same first region of the UI display to optimize user focus while interacting with the UI display. The historical portion of the MUI display is adapted for consistent display within the same second region of the UI display to optimize user focus while interacting with the UI display.

[0219] The preceding description provides examples of menu configurations for providing a UI display of multiple menus in a hierarchical menu tree. Figures 2D-2M provide additional examples of menu display configurations. The following menu display configurations may be used in any combination with each other and with the previously disclosed menu configurations, without limitation. For example, selecting a particular menu item anywhere in the hierarchical menu tree may cause a processor to execute a command to shift the UI display to any of the menu configurations described herein. In particular, a particular menu display configuration may be associated with a particular menu selection.

[0220] 2D illustrates another example of a menu display configuration in one embodiment. FIG. 2D illustrates a two-wheel configuration in which a first wheel option has sub-options in a second wheel. For example, selecting an option in a first wheel of options causes sub-options associated with the selected option to be displayed in a second wheel. In one embodiment, a first portion 214 of the display may initially display a first wheel, and in response to selecting an option from the first wheel, the first wheel with that option may be relocated to a second portion 216 adjacent to the first portion. The first portion may then display a second wheel with sub-options for the first option, e.g., in a side-by-side format (the first wheel is displayed side-by-side with 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 the first portion 214 of the MUI display 206. The first wheel may be displayed in a first sub-portion of the first portion 214, and the second wheel may be displayed in a second sub-portion of the first portion 214. As used herein, a sub-portion may be a division of a larger portion. A sub-portion may be used interchangeably with a subsection. In an embodiment, selection of a menu item in the first wheel may be triggered by simply clicking on any menu item in the first wheel or by rotating any menu item in the first wheel to a prominent and highlighted position. Selecting an item from the first menu on the first wheel may cause the second menu displayed on the second wheel to be corrected accordingly. In yet another embodiment of this embodiment, the first portion 214 may be divided into more than two sub-portions, each including a wheel displaying a corresponding menu. Thus, 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 may display a second menu, a third menu, and a fourth menu. In other examples, any number of wheels may be included.

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

[0223] FIG. 2E illustrates yet another example of a menu display configuration in one embodiment. In this display configuration, two wheels are compressed into one wheel. Wheel options have sub-options represented within the one wheel associated with the active wheel option. In this configuration, the first and second portions of the display overlap, but all menu items can still be made visible (or, in the case of collapsed items, expanded and made visible by sliding or rotating the item's wheel). For example, a 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 another direction (e.g., horizontally left and right). The selected path is also made visible in the second portion. For example, selecting "Sub-option 2" displayed on the display moves the selected option below "First Wheel Option 1."

[0224] 2F-2G show yet another example of a menu display configuration in one embodiment. The figures illustrate switching wheel options from horizontal to vertical orientation. FIG. 2F, for example, shows a menu of options displayed in a graphical wheel where the displayed options are rotatable horizontally (left and right). The wheel is displayed in a first portion of the graphical user interface display. Upon selecting an option (a menu item in the list of options), the graphical wheel switches to a vertically rotatable wheel. For example, the wheel is moved or repositioned to a second portion of the graphical user interface display, and the first portion of the graphical user interface display now displays a list of sub-options related to the option selected in the previous menu of options.

[0225] In one embodiment, the second portion of the display can display a maximum threshold number of menu levels, after which a different visualization configuration for displaying past menu levels can be used to prevent the second portion from becoming too large.

[0226] For example, referring to FIG. 2C , if there are more than a threshold number of menu levels (e.g., FIG. 2C shows two levels (202, 210)), a visualization mechanism may be used that allows all previous menu levels to be visible without having to enlarge the second portion of the display (e.g., FIG. 2C , 208). For example, assume the threshold number is three. In that example, the second portion of the display may show three menu levels. When additional options for the next level are selected (e.g., the fourth menu level), the second portion may show the last three selections (the bottom three levels), with the items in the second portion scrollable up and down. In this example, the options for the first menu level are displayed by scrolling the second portion. As another example, the second portion may always show the top two levels, i.e., the first two decisions and the last decision. In this way, the user is presented with the overall context of the workflow, e.g., top-down. By tapping or scrolling the second portion, the user can expand menu items, e.g., in an accordion-like fashion.

[0227] In another aspect, a search function associated with the wheel may be provided. Search keywords may be used to allow a user to filter the available wheel options. The search function is useful for navigating long or multi-wheel options, which may take a long time to navigate.

[0228] 2H-2J show examples of first and second portions displayed as a series of concentric circles in one embodiment. Referring to FIG. 2H, a dial 220 can be rotated clockwise or counterclockwise to view menu items or selections in an options window 218. Tapping on an area (e.g., a circle) 220 of the dial selects an option. For example, upon selecting an option viewed via the options window 218, the user interface transitions to the configuration shown in FIG. 2I. For example, in FIG. 2I, the concentric dial expands inward to reveal another concentric circle representing another level (e.g., sublevel) of the menu item or path. Suboptions may be viewed via an options window 222 on that circle 224 (also referred to as a dial) by rotating that dial 224 clockwise or counterclockwise. Selection of an option 222 at that level (shown as suboption "n") may be performed by tapping on an area of ​​that 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 (e.g., as shown in FIG. 2H) can transition the state of the user interface to the configuration shown in FIG. 2J. For example, the next level of option selection from the selected option expands, expanding the dial to reveal another inner dial 224 with options window 222. In one embodiment, the number of options viewable in the options windows (e.g., 218 and 222) need not be limited, such that an unlimited number of options can be displayed and selected to apply to an application.

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

[0230] In another aspect, an options window (e.g., 219) may show more than one item or option at a time, e.g., three menu items or options. In this example, tapping on a menu item in the options window selects an option. After a selection is made, the selected option may be displayed in a highlighted or otherwise differentiated format, for example, to distinguish the selected option from unselected options displayed in the options window.

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

[0232] FIG. 2K illustrates a tree-type menu level in one embodiment.

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

[0234] FIG. 2L illustrates 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 a display screen. The graphical element 242 (e.g., a wheel) is ordered by a search function, such as a search box or area 246, with the most "n" most recent items first (in reverse chronological order) at 244, followed by a list of all menu items 248, e.g., sorted alphanumeric. In another embodiment, the menu items shown at 248 are displayed as indexed, e.g., when a search term is entered into the search box 246. The entire wheel 242 is scrollable. For example, a user can scroll the entire wheel 242 or enter a search string into the search box 246. When entering a search keyword in the search area 246, menu items that match the search keyword are displayed as the search character is entered. For example, for each character entered, one or more menu items that are closest to the search character are indexed at 248. Wheel 240 is divided into two separate 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 one another. Thus, for example, the entire wheel 242 is moved or scrolled as a single wheel. In response to receiving or detecting the entry of a search term or character within search field 246, the wheel bifurcates into two separate, independently scrollable wheels 244 and 248. One of the two separate wheels (e.g., 248) shows a list of menu items filtered based on the search.

[0235] 2M-2O show an example of a scrollable wheel that scrolls or slides from the first menu item to the last menu item and then back to the first menu item. In this embodiment, the graphical element (e.g., wheel or slider) representing the menu items does not fully pivot or rotate, but stops at the last menu item or (if rotating from the last menu item) the first menu item. In this way, for example, the beginning and end of a menu are always visible because they are not joined or connected. This technique can reduce computer processing cycle time (and be immediately understandable to the user) because the wheel and / or slider can convey an entire menu of options while clearly indicating which is the first menu item and which is the last menu item among the options presented by the wheel and / or slider. As a result, the wheel or slider does not need to be repeatedly scrolled to determine which menu item is the first menu item and which is the last menu item, or to determine whether all menu items have been visited.

[0236] In embodiments, the wheel and / or slider need not rotate completely, e.g., not make a full rotation or a full circle. For example, the wheel and / or slider may rotate or slide from a start menu item to an end menu item, then back off and rotate or slide from the end menu item back to the start menu item. In this way, for example, the beginning and end of a menu are always visible because they are spaced apart so that they are not joined or joined together. This technique can reduce processing time because the wheel and / or slider can convey (and the user can immediately understand) the entire menu of options while clearly indicating which is the first menu item and which is the last menu item among the options presented by the wheel and / or slider. Furthermore, as the wheel and / or slider rotates, the selectable options can be displayed in a more prominent format, such as using larger text, a bolder font, etc. Options that were previously selectable when the wheel and / or slider was rotated / slid to a different position, or options that become selectable as the wheel and / or slider continues to rotate / slide, may be displayed in a less prominent format, such as with reduced or faded text, In one embodiment, options that are displayed more prominently may be displayed as if they are closer to the user than options that are less prominent.

[0237] Referring to FIG. 2M, a first menu item 252 is shown in the center of wheel (or slider) 250. The centered menu item may be shown in a highlighted format (e.g., larger text, a different colored font, etc.). A blank space is displayed before the first menu item (e.g., above the center of the wheel where the first menu item is displayed). The next menu item (e.g., 254, 256) is displayed adjacent to (e.g., below) the first menu item. As the wheel is scrolled (e.g., vertically), additional menu items are displayed, as shown in FIG. 2N. For example, as shown in FIG. 2N, when wheel 250 is scrolled up, the next menu item is displayed. FIG. 2O shows the last menu item in the center of the wheel, with the previous menu item displayed adjacent to (e.g., above) the last menu item. In this embodiment, 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. A blank space is shown below the last menu item 258. Similarly, navigating back (e.g., scrolling the wheel in the opposite direction) displays the previous menu items up to the first menu item.

[0238] While the exemplary graphical wheels shown in FIGS. 2M-2O depict vertical wheels, horizontal wheels function in a similar manner. For example, a first menu item may be displayed in the center of a horizontal wheel, with the next menu item displayed horizontally adjacent to the first menu item (e.g., to the right of center). In this example, scrolling the wheel left displays additional menu items. When scrolling to the last menu item, the last menu item is displayed in the center, with blank space outside the last menu item (e.g., to the right of the last menu item). In another aspect, the orientation of rotation can be reversed, e.g., using a vertical wheel to scroll down (rather than up) to navigate from the first menu item to the last menu item, and with a horizontal wheel to scroll right to navigate from the first menu item to the last menu item. The number of menu items (options) displayed on the wheel at one time is configurable, for example, based on the screen size and / or screen area allocated to the wheel, and is not limited to the six items shown in FIG. 2N.

[0239] A non-limiting use of such a user interface is selecting channels to watch on a television (TV). Broader categories may be displayed on a horizontal area at the top, finer categories may be stacked below, and leaf-like items may be displayed vertically, for example, on a vertical wheel. For example, referring to FIG. 2E, "Wheel Option 1" may represent genres, and "Sub-Option 1" may represent shows and / or movies organized in a grid.

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

[0241] The following describes in detail various instructions for conducting an experiment consistent with embodiments herein. Instructions for conducting an experiment may be instructions for operating, designing, executing, reviewing, measuring, analyzing, archiving, and performing any other task 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 the assay system and may provide commands for generating an MUI display 206 for the system. In response to commands, the MUI display 206 may display or provide a visual representation of the workflow and / or menu item path for the assay. The assay may include one or more electrochemiluminescence (ECL) assays.

[0242] The methods of the present embodiments can be used in conjunction with a variety of assay devices and / or formats. Assay devices may include assay modules, such as assay plates, cartridges, multi-well assay plates, reaction vessels, test tubes, cuvettes, flow cells, assay chips, and lateral flow devices, with assay reagents (which may include targeting agents or other binding reagents) added as the assay progresses or pre-loaded into the wells, chambers, or assay regions of the assay modules. These devices can use a variety of assay formats for specific binding assays (e.g., immunoassays or immunochromatographic assays). Exemplary assay devices and assay formats are described herein below. In certain embodiments, the methods of the present embodiments can use assay reagents stored in a dried state, and the assay device / kit may further include or be supplied with a desiccant material to maintain the assay reagents in a dried state. Assay devices pre-loaded with assay reagents can significantly increase the speed and reduce the complexity of assay measurements while maintaining excellent stability during storage. Dried assay reagents can be any assay reagents that can be dried and reconstituted prior to use in an assay. These include, but are not limited to, binding reagents useful in binding assays, enzymes, enzyme substrates, indicator dyes, and other reactive compounds that can be used to detect the analyte of interest. Assay reagents may also include substances that do not directly participate in the detection mechanism but play an ancillary role in the assay, including, but not limited to, blocking agents, stabilizers, detergents, salts, pH buffers, preservatives, etc. Reagents may be present in free form or supported on a solid phase, including the surface of a compartment (e.g., chamber, channel, flow cell, well, etc.) in an assay module, or the surface of a colloid, bead, or other particulate support.

[0243] A wide variety of solid phases are suitable for use in the methods of the present invention, including conventional solid phases from the field of binding assays. Solid phases can be made from a variety of different materials, including polymers (e.g., polystyrene and polypropylene), ceramics, glass, and composites (e.g., carbon-polymer composites 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, etc.), slides, assay chips (such as those used in gene or protein chip assays), pins or probes, beads, filtration media, and lateral flow media (e.g., filtration membranes used in lateral flow test strips).

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

[0245] The particles used in the present method may be composed of any material suitable for binding to one or more binding partners and / or labels, and may be collected, for example, via 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 and particles containing magnetizable materials that allow the particles to be collected in a magnetic field. In one embodiment, the particles are composed of conductive and / or semiconductive materials, such as colloidal gold particles.

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

[0247] The particles used in this method can be coded to allow for the identification of specific particles or subpopulations of particles in a mixture of particles. Such coded particles have been used to enable multiplexing of assays using the particles as solid supports in binding assays. In one approach, 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 their fluorescent emission at one or more wavelengths. This approach has been used in the Luminex xMAP system (see, e.g., U.S. Pat. No. 6,939,720) and the Becton Dickinson cytometric bead array system. Alternatively, particles may be coded through differences in other physical properties, such as size, shape, or embedded optical patterns.

[0248] The method of the embodiments can be used with various methods for measuring the amount of an analyte, particularly the amount of analyte bound to a solid phase. Techniques that can be used include, but are not limited to, cell incubation-based assays, binding assays (agglutination tests, immunoassays, serological assays, nucleic acid assays, such as hybridization assays), enzymatic assays, colorimetric assays, and other techniques known in the art. Other suitable techniques will be readily apparent to those skilled in the art. While some measurement techniques allow for measurement by visual inspection, other techniques may require or benefit from the use of an instrument to perform the measurement.

[0249] Methods for measuring the amount of an analyte include label-free techniques, which may include, but are not limited to, i) techniques that measure the change in mass or refractive index at a surface following binding of the analyte 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, SELDI, etc. that may measure the analyte on a surface), iii) chromatography or electrophoresis techniques, and iv) fluorescence techniques (which may be based on the intrinsic fluorescence of the analyte).

[0250] Methods for determining the amount of an analyte also include techniques that measure the analyte through the detection of a label, which can be directly or indirectly attached to the analyte (e.g., through the use of a labeled binding partner of the analyte). Suitable labels include labels that can be directly visualized (e.g., visually visible particles and labels that generate a measurable signal, such as light scattering, absorbance, fluorescence, chemiluminescence, electrochemiluminescence, radioactivity, or magnetic fields). Labels that can be used also include enzymes or other chemically reactive species that have a chemical activity that leads to a measurable signal, such as light scattering, absorbance, or fluorescence. The use of enzymes as labels is well established in enzyme-linked immunosorbent assays, also known as ELISAs, enzyme immunoassays, or EIAs. In the ELISA format, an unknown amount of antigen is attached to a surface, and then a specific antibody is washed over the surface to bind to the antigen. This antibody is linked to an enzyme, and in a final step, a substance is added that the enzyme converts into a product, resulting in a detectable signal change. Product formation can be detected in a measurable property, such as absorbance, fluorescence, chemiluminescence, or light scattering, for example, by a difference relative to the substrate. Certain (but not all) assay methods that may be used with solid phase binding methods according to embodiments may benefit from or require a wash step to remove unbound components (e.g., label) from the solid phase, and therefore, the methods of embodiments may include such a wash step.

[0251] The methods disclosed herein can be performed manually, using automated techniques, or both, which may be partially automated, e.g., using one or more modular instruments, or fully integrated automated instruments.

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

[0253] An automated system (both modular and fully integrated) in which the methods herein may be implemented may include the following automation 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 databases; a liquid handling subsystem such as sample and reagent manipulation, e.g., robotic pipette heads, syringes, stirrers, ultrasonic mixers, magnetic mixers; a sample, reagent, and consumable storage and handling subsystem, e.g., robotic manipulators, tube or lid or foil punchers, lid removers, transport devices such as linear and carousel conveyors and robotic manipulators; a tube rack, a plate carrier, a trough carrier, a pipette tip carrier, a plate shaker. centrifuges, assay reaction subsystems, e.g., fluid-based and consumable-based (such as tubes and multiwell plates), vessel and consumable washing subsystems, e.g., plate washers, magnetic separator or magnetic particle concentrator subsystems, e.g., flow cell, tube, and plate types, cell and particle detection, sorting, and separation subsystems, e.g., flow cytometers and Coulter counters, detection subsystems such as colorimetric, nephelometric, fluorescent, and ECL detectors, temperature control subsystems, e.g., air handling, 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, sample identifier detection subsystems, e.g., 1D and 2D barcode scanners, such as flatbed and wand types. Analytical subsystems, e.g., chromatography systems, such as high performance liquid chromatography (HPLC), fast protein liquid chromatography (FPLC), and mass spectrometers, can also be modular or fully integrated. An automated system consistent with embodiments herein may be controlled and / or managed by an organized user interface control system 1102 .

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

[0255] The automated system allows for batch, continuous, random access, and point-of-care workflows, and single, medium, and high sample throughput.

[0256] The system may include, for example, one or more of the following devices: a plate sealer (e.g., Zymark), a plate washer (e.g., BioTek, TECAN), a reagent dispenser and / or automated pipetting station and / or liquid handling station (e.g., TECAN, Zymark, Labsystems, Beckman, Hamilton), an incubator (e.g., Zymark), a plate shaker (e.g., Q.Instruments, Inheco, Thermo Fisher Scientific), a compound library or sample storage and / or a compound and / or sample retrieval module. One or more of these devices may be coupled to the apparatus via a robotic assembly, such that the entire assay process can be performed automatically. According to alternative embodiments, containers (e.g., plates) are manually transferred between the apparatus and various devices (e.g., stacks of plates).

[0257] The automated system can be configured to perform one or more of the following functions: (a) moving consumables, such as plates, into, within, 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 reagents for introduction into the consumable), (e) shaking consumables (e.g., to mix reagents and / or increase reaction rate), (f) washing consumables (e.g., performing wash plate and / or assay wash steps (e.g., well aspiration)), and (g) measuring ECL in flow cells or consumables, such as tubes or plates. The automated system can be configured to process individual tubes placed in racks, multiwell 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, e.g., Sargeant et al., Platform Perfection, Medical Product Outsourcing, May 17, 2010.

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

[0260] In an embodiment, the control unit uses a graphical user interface to control all instrument functions and is composed 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 an embodiment, the core unit is composed of several components that manage the transport of samples to each assigned analytical module. The actual configuration of the core unit depends on the configuration of the analytical module, which can be configured by those skilled in the art using methods known in the art. In an embodiment, the core unit includes at least a sampling unit and one rack rotor as its main components. A conveyor line and a second rack rotor are possible extensions. Other core unit components include a sample rack loader / unloader, ports, a barcode reader (for racks and samples), a water supply, and a system interface port. In an embodiment, the analytical module performs the ECL assay and includes a reagent area, a measurement area, a consumables area, and a pre-wash area.

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

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

[0263] In certain embodiments, the surface includes multiple capture reagents for one or more analytes present in the sample, the multiple capture reagents being dispersed across multiple degradable binding regions positioned on the surface. Under the conditions used to perform and analyze the assay, a "degradable binding region" is the smallest surface area associated with an individual binding event that can be degraded and differentiated from other regions where additional individual binding events occur. Thus, the method includes binding one or more analytes to one or more capture reagents on the surface, determining the presence or absence of the analyte within the multiple degradable binding regions on the surface, and identifying the number of degradable binding regions that include the analyte of interest and / or the number of domains that do not include the analyte.

[0264] The degradable binding regions can be optically interrogated in whole or in part. That is, each individual degradable binding region can be optically interrogated individually, and / or the entire surface containing multiple degradable binding regions can be imaged, and one or more pixels or groups of pixels in the image can be mapped to individual degradable binding regions. The degradable binding regions can also be microparticles within multiple microparticles. Degradable binding regions that exhibit changes in optical signatures can be identified by conventional optical detection systems. Optical filters designed for specific wavelengths can be used for optical interrogation of the degradable binding regions, depending on the species detected (e.g., type of fluorescent entity) and operating wavelength. In embodiments where optical interrogation is used, the system can include two or more light sources and / or multiple filters to adjust the wavelength and / or intensity of the light source. In some embodiments, the optical signals from multiple degradable binding regions are captured using a CCD camera. Other non-limiting examples of camera imaging systems that can 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 scanning mirror system coupled with a photodiode or photomultiplier tube (PMT) can be used for imaging.

[0265] In embodiments, binding of each analyte to its corresponding capture reagent is carried out in parallel by contacting one or more surfaces with a single liquid volume containing multiple analytes. In embodiments, the multiple analytes include the 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 multiplexed assay. Multiplexed measurement of analytes on a surface is described herein, e.g., U.S. Pat. Nos. 10,201,812, 7,842,246, and 6,977,722, which are incorporated by reference in their entireties.

[0266] In certain embodiments, the methods of the 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 can further include counting the number of beads with bound analytes (using detection approaches 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, such as 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. As a result, distinct assay signals are generated on and measured from each binding domain. When capture reagents for different analytes are immobilized to different binding domains, the different analytes that bind 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 analytes of interest on one or more surfaces. Optionally, the surfaces may partially define one or more boundaries of a vessel (e.g., a flow cell, well, cuvette, etc.) that holds or through which the sample is passed. In a preferred embodiment, the individual binding domains are formed on electrodes for use in electrochemical or electrochemiluminescent assays. Multiplexed measurement of analytes on surfaces containing multiple binding domains using electrochemiluminescence is used in Meso Scale Diagnostics, LLC's MULTI-ARRAY® and SECTOR® Imager product lines (see, e.g., U.S. Pat. Nos. 10,201,812, 7,842,246, and 6,977,722, which are incorporated by reference in their entireties).

[0268] Additionally, the capture reagent can be directly or indirectly bound to an electrode surface, which optionally includes different, distinct binding domains, as described above. The electrode surface can be a component of a multiwell plate and / or a flow cell. The electrode can include a conductive material, e.g., a metal such as gold, silver, platinum, nickel, steel, iridium, copper, aluminum, or a substance capable of conducting electricity. The electrode can also include an oxide-coated metal, e.g., aluminum oxide-coated aluminum. The electrode can include a working electrode and a counter electrode, which can be made of the same material or different materials (e.g., a metal counter electrode and a carbon working electrode). In a particular embodiment, the electrode includes a carbon-based material, such as carbon, carbon black, graffiti carbon, carbon nanotubes, carbon fibrils, graphite, graphene, carbon fiber, and mixtures thereof. In one embodiment, the electrode includes elemental carbon, e.g., graphite, carbon black, carbon nanotubes, etc. Advantageously, they can include 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 multi-well plate, having electrodes (e.g., working electrodes and / or counter electrodes) comprising carbon, e.g., a carbon layer, and / or a screen-printed carbon ink layer.

[0269] In embodiments, each binding domain comprises a targeting reagent complement capable of binding to the targeting reagent complement, and each anchor reagent and capture reagent comprises a complementary linking reagent capable of binding to the linking reagent, and the method further comprises: (1) binding the capture reagent and anchor reagent to the targeting reagent complement connected to the linking reagent through the complementary linking reagent; and (2) binding the product of step (1) to a binding domain comprising the targeting reagent complement, wherein (i) each binding domain comprises a different targeting reagent complement, and (ii) each targeting reagent complement selectively binds to one of the targeting reagents, thereby immobilizing the capture reagent and fixative to each binding domain.

[0270] Thus, in embodiments, the surface comprises a targeting reagent complement, the targeting reagent is connected to a linking reagent, and the capture reagent and anchor reagent each comprise a complementary linking reagent. Thus, in embodiments, 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 complementary 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 immobilizing the capture reagent and anchor reagent further includes binding the capture reagent and anchor reagent to a targeting reagent connected to the linking reagent through a complementary linking reagent, and binding the product to binding domains containing targeting reagent complements, where (i) each binding domain contains a different targeting reagent complement, and (ii) each targeting reagent complement selectively binds to one of the targeting reagents. For example, if the targeting agent is an oligonucleotide, the linking reagent is streptavidin, and the complementary linking reagent is biotin, a biotin-labeled oligonucleotide can bind to the first of the four biotin-binding sites of the streptavidin to form a targeting reagent linked to the linking reagent. The biotin-labeled capture reagent (i.e., the capture reagent linked to the complementary linking reagent) can then bind to the remaining biotin-binding site on the streptavidin to connect 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 target, and receptor ligand. In embodiments, the targeting reagent is biotin and the targeting reagent complement is streptavidin. In embodiments, the linking reagent and complementary linking reagent pair is a different binding partner pair than the targeting reagent and complementary linking reagent pair. In embodiments, the linking reagent is avidin or streptavidin and the complementary 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 applied in single or multiple formats, in which multiple assay measurements are performed on a single sample. Multiplexed measurements that can be used in the present invention include, but are not limited to, i) involving the use of multiple sensors, ii) using separate assay domains on a surface (e.g., an array) that are distinguishable based on their location on the surface, iii) involving the use of reagents coated on particles that are distinguishable based on particle characteristics such as size, shape, color, etc., iv) producing distinguishable assay signals based on optical properties (e.g., absorbance or emission spectra), or v) based on temporal characteristics of the assay signal (e.g., the 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, each of which is incorporated by reference in its entirety. Additional ultrasensitive assay formats include those disclosed in U.S. Patent Application No. 17 / 434,938, filed August 30, 2021, and U.S. Patent Application No. 62 / 866,512, filed June 25, 2019, each of which is incorporated by reference in its entirety.

[0274] Exemplary plate readers include the MESO SECTOR S 600 (www.mesoscale.com / en / products_and_services / instrumentation / sector_s_600) and the MESO QUICKPLEX SQ 120 (www.mesoscale.com / en / products and services / instrumentation / quickplex sq 120), both available from Meso Scale Diagnostics, LLC, as well as the plate readers described in U.S. Pat. No. 6,977,722 and U.S. patent application Ser. No. 16 / 929,757, entitled "Assay Apparatuses, Methods and Reagents," Krivoy et al., filed July 15, 2020, each of which is incorporated by reference in its entirety.

[0275] The above user interface techniques may also be incorporated into the user interface of an assay system. The assay system described below allows a user to run an assay via a user interface. An example of a user interface incorporated into an assay system for an assay method is described below. The terms "system software" or "system," referred to below when describing the functionality of the assay system and its user interface, refer to the software that implements the assay system. The user interface may display or visualize a workflow and / or a path of menu items.

[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 current screen, substep, or screen state) for advanced users.

[0278] Assay Methodology - How to perform the assay, including but not limited to: 1. The instrument protocol to be run and the parameters for running that protocol, 2. The layout of the test plate, 3. The calibrator titration scheme, including dilution factors, 4. The control layout, and 5. The sample replication scheme.

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

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

[0281] Completed Launches - Launches that were aborted, completed with a flag, or successfully completed.

[0282] CV - coefficient of variation.

[0283] Database Clean - Resets the entire database and restores it to the state it was in when the system was installed.

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

[0285] Existing launches - planned launches, aborted launches, launches that were flagged as completed, or launches that were successfully completed.

[0286] Global Product Data (GPD)—Data for a specific item identified in the GPI. While the same data can be used for multiple items, the GPI allows for matching of data to one specific item. The GPD may include information used to identify at least one element, including (i) the assay consumable, (ii) one or more test sites within the consumable, (iii) reagents and / or samples used or intended for use in the consumable, or (iv) a combination thereof. Additionally, the GPD may be used to distinguish between the first test site within the consumable and different test sites within the consumable. The GPD may 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. The GPD may also include one or more analytical tools applicable by the system to analyze data generated during and / or after assay performance, assay system maintenance information, system consumable promotion information, system and / or consumable technical support information, or a combination thereof. Additionally, the GPD includes the identity and / or configuration information of the consumable, as well as one or more steps of an assay protocol that may be applied by the system in performing an assay using the consumable.

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

[0288] Global Product Identifier (GPI) - A system / instrument / consumable vendor-specified unique identifier for an individual specific product, such as an assay consumable. The identifier may be of any number of configurations. For consumables such as assay plates, the identifier may be the associated manufacturing barcode.

[0289] Types of GPIs and GPDs are known, see, e.g., U.S. Pat. No. 8,770,471, WO 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 any fault or error conditions that occur during that action. The instrument log is a rolling, circular log containing stored information, limited by the amount of memory space allocated to this log file; e.g., older entries are overwritten over time.

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

[0292] LED - Light Emitting Diode. Light source.

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

[0294] Initiation - An initiation involves zero or more named samples and one or more assay methods, and the samples are tested according to the information provided in the assay methods.

[0295] Launch Owner - The user who created the launch.

[0296] Sample - A general term that includes the analyte, including calibrators, controls, blanks, and test materials.

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

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

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

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

[0301] Step - One of a series of separate and consecutive stages in progress towards a goal. A step comprises a broader phase that may be made up of multiple sub-steps.

[0302] Sub-step - One of a series of separate and consecutive stages in the progression towards the completion of a step. A sub-step constitutes a focused activity within a step.

[0303] Unexpected Barcode - A barcode that is different from what is expected. A consumable may also be considered to have an "unexpected barcode" if the barcode cannot be read.

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

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

[0306] System Event Log - A persistent log of events that occur in software that are not instrument-related.

[0307] FIG. 4 is a flow diagram illustrating the first user login user interface of the assay system in one embodiment. At 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 user name and date and time is created when the user accepts the agreement. If the user has not previously accepted the agreement, the EULA is displayed at 404, allowing the user to accept the agreement. If the user does not accept the agreement at 406, the software closes. At 408, a splash screen containing system software branding, copyright, legal notices, and software version is displayed. The initial login screen requests a username at 410. In one embodiment, the system software can present previous usernames used to log in on the system to minimize errors due to entering a username. The user can also enter a new username that has not been used to log in before. After selecting (or receiving) a username at 412, the software prompts the user to enter a password for the username at 414. In one embodiment, the system software may allow or verify login using biometric authentication methods such as facial recognition, voice, and / or fingerprint. In another embodiment, the system software may use a badge key card containing information that can be scanned or read via near field communications. At 416, the system software receives the entered password. Once the username and password are entered, the system software authenticates the user at 418. If the user is successfully authenticated, the user interface proceeds to a start screen at 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 to access the software.In one embodiment, authentication may be performed via Microsoft Windows® authentication functionality or may be configured to authenticate via Active Directory. In this first user interface display, the username and password prompt may be displayed in one orientation, for example, horizontally on a horizontal wheel graphical element 422.

[0308] FIG. 5 is a flow diagram illustrating a method for displaying a start user interface screen display in one embodiment. This display screen includes a list of menu items in two different visual orientations, e.g., horizontal and vertical. Thus, for example, more general categories of menu items are displayed on horizontal wheel 502, and submenu items are displayed on vertical wheel 504. For example, start option 506 selected by the logged-in user (FIG. 4) is presented on horizontal wheel 502. A second level of options stemming from start option 406 is presented on vertical wheel 504. In this example assay method, the start screen is the initial software screen displayed to the user. Workflows that the user can execute are listed as options (sub-options) on the vertical wheel that can be selected. In this example assay method, advanced workflows, rather than general workflows, may be grouped under an advanced menu. In this exemplary assay method, the system's workflow options include: Create a new launch (508). When the user selects the Create a New Launch workflow (510), the user can create a launch from scratch or based on a previously defined launch (512). Continuing a previously planned or initiated launch (514). If the user selects continuing a previously planned or initiated launch (516), the software automatically resumes from the last step the user completed in the launch (518). The software displays the results of a completed launch (520). If the user selects to view a completed launch (522), the software directs the user to a review screen (524). After the user selects an option from the vertical wheel (504), the options on the vertical wheel are added to a new horizontal wheel at the top of the screen. This horizontal wheel allows the user to change their selection. For example, after selecting "Create New," the "Planned Launch" and "Completed Launch" options are moved to the horizontal wheel, allowing the user to change their mind.

[0309] Figure 6 illustrates 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 process shown on this screen can be performed in response to the Define option (Figure 5, 512) being executed. The assay method defines the following: assays on the plate, plate layout, number of calibrators, controls, and maximum sample number; control, calibrator, and sample dilutions; number of replicates for controls, calibrators, and samples; instrument protocol (incubation time, run blockers, and / or other). A default assay method is provided with every kit, and the system software allows users to create custom assay methods based on the defaults. In one embodiment, assay methods are distributed in a global product data (GPD) file. The GPD includes, for example, product barcodes, assays, placement of assays in wells, kit, plate, antibody, calibrator, and control lot identification; measured concentrations of calibrators and controls; instrument instructions on how to process the product; and a recommended plate layout.

[0310] 7 illustrates 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, which may be selected or executed as an option in the workflow shown in FIG. 6, for example. The Assay Method Definition options may include an Assay Method selection option, a Sample option, and a Confirm option, which are shown, for example, in a horizontal orientation on a horizontal wheel graphical element 702. A selected Assay Method option may be highlighted and / or centered in the horizontal wheel relative to other unselected options. Sub-level options under the Assay Method option 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) select from the Assay Methods most recently used on the system sorted in reverse chronological order; b) select from all available Assay Methods installed on the system (in this screen, the UI uses multiple wheels, with each wheel filtering the results of the next wheel until the final wheel contains results); or c) search for Assay Methods installed on the system (this can be done using a free text search).

[0311] When the user selects one of the sublevel options, the sublevel option moves to a horizontal wheel, allowing the user to change the Assay Method selection model. After the user makes an initial selection of an assay method, the user can select whether to activate only a single assay method or multiple assay methods, where single assay method means all activated mesoscale diagnostic test plates use the same assay method, and multiple assay methods means there is at least one mesoscale diagnostic test plate per activated assay method.

[0312] 8 is a flow diagram illustrating the workflow of a user interface displayed for defining a sample in one embodiment. Upon selection of a "Define Sample" option, the option is shown in a horizontal orientation, for example, on a horizontal wheel graphical element 802, which may be stacked under its parent menu item, the "Define Sample" option. A sublevel of options associated with the "Define Sample" option is displayed vertically, for example, on a vertical wheel graphical element 804.

[0313] In the Sample Definition screen, the user can choose whether the user interface will import samples or manually define them. These options move on a horizontal wheel after the user selects an option. If the user selects to import samples from a file, the software presents the user with sample files via the user interface that can be used on a vertical wheel. The system can alternatively 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 manually define samples, the user can define the number of samples to launch. The software will automatically assign a sample ID.

[0315] FIG. 9 is a flow diagram illustrating the workflow of the user interface displayed for confirming a launch definition in one embodiment. When the "Review Launch Definition" option, a submenu item of the "Define" option, is selected, the "Review Launch Definition" option appears in a horizontal wheel graphical element, e.g., stacked below the parent menu item, "Define." After the user defines the launch in the previous steps, the system provides a summary of the launch for the user to review and confirm. The following information is displayed to the user: Number of samples in the launch. The user may also select the number of samples viewing sample identifiers (IDs), the number of mesoscale diagnostic plates in the launch, the plate layout, and a name for the launch. The system provides a default name for the launch and allows the user to change it. Once the user confirms the launch, the system displays a prompt requesting the user to continue running the launch or return to [Start Target].

[0316] Figure 10 is a flow diagram illustrating the workflow of the user interface displayed to inform the user of completed tasks in one embodiment. The system can guide the user through accomplishing the task through the user interface (automated help function) within the wizard. Major logical steps may be categorized into goals. In this example, the system has three major goals within the wizard: Initiate: The user begins and selects what they want to do within the system. Define: After the user selects what they want to do, the wizard walks the user through the user interface through defining any information needed. Execute: The system walks the user through the execution of the task they selected.

[0317] FIG. 11 is a flow diagram illustrating the workflow of the user interface displayed for the Run / Collect option in one embodiment. In this collection screen, the system creates a list of items the user needs to collect to execute the activation. Each item must be marked for collection before proceeding. The system also allows the user to print this list or collect using a tablet computer. For each item collected, the item may optionally be scanned so the system can verify it is the correct item, expiration date, and lot information. For example, the system may require a barcode scan on the item. This is done using the barcode (GPI) and the GPD is obtained.

[0318] FIG. 12 is a flow diagram illustrating the user interface workflow displayed for the Run / Prepare option in one embodiment. In 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 when that preparation step is selected. The detailed preparation steps may include text describing the action to be taken, an image visually illustrating the action, a video illustrating the action, and web content, such as in a web page, that provides further details or context about the action. The user is asked 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 flow diagram illustrating the workflow of the user interface displayed for the Run / Load option in one embodiment. In 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 location to load the item. The system provides a graphical indication of whether the item is loaded or empty. The system verifies that all items have been loaded before proceeding to the next screen.

[0320] FIG. 14 is a flow diagram illustrating the user interface workflow displayed for the run / launch option in one embodiment. This launch screen allows the user to command the system to initiate a launch, for example, via a launch button UI control. This screen also allows the user to subscribe other users to system update messages. Updates may be distributed, for example, via electronic mail (email), text such as short message service (SMS), social networking applications and / or blogs, and / or others. Once the user initiates a launch, the system transitions to presenting a timer for 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 clock format, and 3) a live camera feed of the instrument. The user may also request to stop the launch from an advanced context menu.

[0321] FIG. 15 is a flow diagram illustrating the user interface workflow displayed for the Run / Unload option in one embodiment. Once startup is complete, the system transitions to this unload screen. The unload screen presents a list of steps to unload the system in the wheel. For each item, the system graphically displays the location to unload the item. The system provides a graphical indication of whether the item is loaded or unloaded. The user must unload all items before proceeding to the next screen.

[0322] FIG. 16 is a flow diagram illustrating the user interface workflow displayed for the Run / Review option in one embodiment. In the Review screen, the system presents run-up results. Results are also automatically exported in file format and emailed to a LIMS / LIS system. Results are presented and can be viewed a) graphically as a plate representation. ECL or calculated concentrations are displayed using a brightness scale, with dark / black indicating a low result and light indicating a high result. A scale is presented for annotating color brightness to numbers, and b) results are also available as a table. This table can be exported via file format and / or emailed to a LIMS / LIS system. The system records any abnormal behavior or results in the table, for example, if the temperature during the run was not within a specified range. After the user completes reviewing the run-up data, the user may navigate to Start Goal to start another run or view the results.

[0323] FIG. 17 is a flow diagram illustrating the user interface workflow displayed for the Run / Review option in one embodiment. In one embodiment, the system categorizes tasks a user can perform into primary and advanced workflows. Primary workflows are workflows that users perform routinely and are optimized for ease of execution. Primary workflows are displayed in wizard 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 clicks on the Mesoscale Diagnostic Globe to open the advanced context menu. The advanced context menu items are contained in a vertical wheel with three main groups: functions related to current screen context-sensitive items that change depending on the active screen; modules that can be switched; and functions applicable across all modules, such as logging in and out of the software. In this screen, the selected option, the advanced menu, is displayed horizontally in a horizontal graphical wheel, and the advanced menu's sub-options are displayed vertically in a vertical graphical wheel.

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

[0325] Further example screenshots consistent with embodiments herein are shown in Figures 58-63. Figures 58A-58HH are exemplary, non-limiting embodiments of a Reader module. Figures 59A-59T are exemplary, non-limiting embodiments of an Experiment module. Figures 60A-60I are exemplary, non-limiting embodiments of a Maintenance module. Figures 61A-61Q are exemplary, non-limiting embodiments of an Administration Console module. Figures 62A-P are exemplary, non-limiting embodiments of general screenshots applicable to multiple modules herein. Figure 63 is an exemplary, non-limiting embodiment of an Audit Trail module. Figures 64A-64RR are examples of non-limiting embodiments of an Assay Method module.

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

[0327] As described above, the user interface of the present disclosure, whether used in an assay system or another system, presents the complete trajectory on a single screen of the user interface display, e.g., 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 also allows past decisions to be visualized, e.g., the primary decision and the last n most recent decisions (the decision history can be visualized by scrolling a graphical wheel or another graphical element, such as a graphical slider).

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

[0329] In one embodiment, computer processing time can be improved by minimizing the options or choices that are presented to the user and receiving input from those choices. The user interface guides the user to the next step in the application while minimizing the choices the user must 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., serially or in parallel). In this regard, the processor can be adapted to receive one or more benchmark inputs (e.g., inputs providing information that support or provide a solution to a larger problem, experiment, assay, etc.). The benchmark inputs can be aggregated, which can be collectively relied upon to collaboratively solve the problem, perform the experiment, etc. Such inputs can be based on one or more of: (a) modules; (b) problems or sub-problems to be solved; (c) devices; (d) physical locations; (e) tools; (f) instruments; or (g) equipment. Additionally, the processor can be adapted to notify more users, accounts, or teams of results derived from one or more of the received benchmark inputs. In one example (e.g., running an assay), this may include notifying a researcher responsible for conducting the experiment that the first user has completed the design of the assay experiment (thus notifying the researcher that the experiment is ready to be conducted), and notifying the researcher back to the first user that the experiment has been completed after the experiment is complete (e.g., so that the first user can review the results of the experiment). Further, the processor may be adapted to provide an output in response to the received response. The output may then be adapted to be transmitted to a device communicatively connected to the processor (i.e., interfacing with a component, device, etc., in the physical world) to instruct the device to perform a particular action (e.g., undergo a physical movement or physical transformation). In certain embodiments, the processor triggers the response on these components in the physical world as a step within a broader process of dividing one or more problems into different segments for multiple users to solve, as described above. Additionally, certain aspects of these (and other processes described throughout) may be controlled by the processor via permission commands.Permission commands can be used to manage one or more of user and team levels of access, security, or control. These permissions can be based on a variety of levels, including one or more of role, user, team, account, instrument, equipment, or device. 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 tightly maintained and controlled in a very versatile manner.

[0331] The following discussion provides additional embodiments and implementations of the systems presented herein. The user interface systems discussed above may be broadly applicable to a variety of applications, including manufacturing environments, test environments, instrumentation environments, laboratory environments, and others. In a series of embodiments, the user interface systems discussed above may be used to provide a user interface system for a comprehensive biometric system that encompasses software, hardware, test equipment, and all additional required 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] The description herein is made with reference to the drawings for convenience only, which is not limiting as to the scope of the embodiments herein. The description below is adaptable to a variety of analytical applications, including, but not limited to, bioanalytical applications, chemical analytical applications, radioanalytical applications, etc.

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

[0334] FIG. 21 illustrates one embodiment of a cloud-based system that provides seamless integration of other systems, computers, and instruments, such as biometric instruments, to support and optimize users performing biometric analysis tasks. 21100 is a system boundary around the other systems, computers, and instruments that, in whole or in part, comprise the analytical computing system 21100. Here, the operating systems of each computer and / or instrument, in whole or in part, comprise 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 that includes one or more servers, desktop computers, laptop computers, tablets, and / or mobile devices, one or more of which may be used with the 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 may be used in system 21100 to support instruments, consumables, and / or software used by analytical users in analytical user environment 21101. In 21102, there may be one or more support provider environments that use analytical computing system 21100. 21103 is a consumable provider environment including one or more servers, desktop computers, laptop computers, tablets, and / or mobile devices, one or more of which may be used in analytical computing system 21100 to provide consumables used by users in analytical user environment 21101, optionally in combination with instrumentation devices, including instrumentation device environment 21106. In 103, there may be one or more consumable provider environments that use analytical computing system 21100.

[0335] 21105 is an analytical instrumentation provider environment for an instrumentation provider that can be used in 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 analytical computing system 21100, for example, to provide, e.g., sell, or otherwise transfer, instruments used by users in analytical user environment 21101. In 21105, there can be one or more instrumentation provider environments that use analytical computing system 21100. 21104 is an analytical computing system provider environment for a provider of 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 21100 to manage business interactions with analytical computing system 21100 used by analytical users in analytical user environment 21101. Each of the "providers" associated with the environments in 21102, 21103, 21104, and 21105 can include one or more entities, including, but not limited to, multiple independent businesses, a single independent business, a combination of different independent businesses, or one or more businesses within any of the "providers" herein. 21106 is an instrumentation environment that includes one or more instruments, each having at least one computer, and which, in one implementation, can be used at least in part by analytic computing system 21100 to launch tests on samples for users in analytic user environment 21101.21107 is a cloud platform utilized to connect (e.g., bidirectionally connect) some or all of the computers in analytics computing system 21100 with a common computing, software services, and data architecture in one embodiment through computers, networking, and software, such that data can be collected and shared by any computer with associated software in analytics computing system 21100, provided that the particular computer with associated software in analytics computing system 21100 is located in a secure manner around the world. Here, in a preferred embodiment, cloud platform 21107 is hosted by a public cloud provider offering a shared computing environment, e.g., Amazon™ Web Services, Google™ Cloud, Microsoft™ Azure, etc. In other embodiments, the cloud platform 21107 may be hosted by the analytics computing system provider at 21104, or may be self-hosted by an analytics user environment that is a user of the analytics computing system 21100, or may be hosted by a private cloud provider that provides dedicated computing environments, e.g., Oracle™ Cloud, IBM™ Cloud, Rackspace, etc., or may be hosted on some combination of public cloud, private cloud, self-hosted, and hosted by the analytics computing system provider 21104. All communications with the cloud platform 21107 may be conducted throughout the preferred embodiment via a secure communications protocol, such as, but not limited to, https, to encrypt all communications between sender and receiver.Either secure or insecure case connection technologies, such as Ethernet for local area network (LAN), metropolitan area network (MAN), and / or wide area network (WAN) configurations, and / or non-connection technologies such as WIFI, Bluetooth, and / or other similar technologies for distributed LANs, may be optionally used, as may insecure communication protocols such as, but not limited to, Hypertext Transfer Protocol Secure (HTTPS). Additionally, the analytics computing system 21100 may be deployed entirely on one computer such that all operations of the analytics computing system 21100 occur on that computer, and the only external communications occurring between the computer and associated software are initiated outside of the analytics computing system 21100.

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

[0337] The support provider environment 21102 is a support provider for users of the analytical computing system 21100, users of consumables from consumable providers, and / or 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 may be used in the analytical computing system 21100 to support the instruments, consumables, and / or software used by analytical users in the analytical user environment 21101.

[0338] Support user computers 22206 include one or more computers having software provided to users associated with support provider environment 21102 that can, among other things, monitor, manage, and / or report activity on analytics computing system 21100 through services and data storage / retrieval provided by cloud platform 22223. Support data integration computer 22207 includes one or more computers having software and / or firmware used to integrate other support business systems 22208 into support provider environment 21102, and analytics computing system 21100 provides services for support business systems 22208 through services and data storage / retrieval provided by cloud platform 22223. The support operations system 22208 may be hosted internally, externally, and / or by some combination of internal and external to the support provider environment 21102, and may optionally include one or more computer systems with software (e.g., 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 from the analytics 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 directly interface with the analytics computing system 21100.

[0339] Consumable provider environment 21103 is a consumable provider environment including one or more servers, desktop computers, laptop computers, tablets, and / or mobile devices, one or more of which may be used in analytics computing system 21100 for the provider of consumables to users in analytics user environment 21101, optionally in combination with instrumentation in instrumentation environment 21106 to provide consumables to users in analytics user environment 21101, and optionally in combination with instruments in instrumentation environment 21106. Consumable information upload computer 22210 includes one or more computers having software used to distribute consumable information about consumables provided from consumable provider business system 22211 to analytics computing system 21100 through services and data storage provided by cloud platform 22223. As used herein, consumable information may include, but is not limited to, global product data (GPD). The consumable provider business system 22211 may be hosted internally, externally, and / or by some combination of internal and external to the consumable provider environment 21103 and may optionally include one or more computer systems with software (e.g., 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 supporting business operations for supporting the delivery of consumable information to the analytics computing system 21100 for the consumable provider), or one or more computer systems not used at all in the delivery of consumable information to the analytics computing system 21100.

[0340] The analytic computing system provider environment 21104 is an analytic computing system provider environment for the provider of the analytic 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 by the analytic computing system 21100 to provide the analytic computing system 21100 to users of the analytic user environment 21101 and instrumentation devices of the instrumentation device 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 with software used to prepare and control use of the analytic computing system 21100 by users in the analytic user environment 21101 and instrumentation devices of the instrumentation device environment 21106 through services and data storage provided by the cloud platform 22223. The computing system provider business systems 22214 may be hosted internally, externally, and / or in some combination internally and externally 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 and / or non-relational databases, file servers, and / or other systems that support the analytical computing system provider's business operations to support the provision and control of use of the analytical computing system 21100, or that are not used at all in the provision and control of 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 by the analytical computing system 21100 for providing instrumentation to users in the analytical user environment 21101, and optionally used 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 device provider business system 22217 may be hosted internally, externally, and / or by some combination of internal and external to the instrumentation device provider environment 21105 and may optionally include one or more computer systems with software, such as, for example, customer relationship management, enterprise data systems, data reporting applications, business productivity applications, relational and / or non-relational databases, file servers, and / or other systems that support business operations for the instrumentation device provider and that support the delivery of meter information to the analytics computing system 21100 or that are not used at all in the delivery of meter information to the analytics computing system 21100.

[0342] The instrumentation environment 21106 includes one or more instruments, each of which is either an individually operated instrument 22221, a collaboratively operated instrument 22222, or a workflow assistance instrument 22226 provided by the instrumentation provider environment 21105 that can be utilized by a user in the analytical user environment 21101 to process samples, optionally in conjunction with consumables provided by the consumables provider environment 21103, to generate data for analysis by the user in the analytical user environment 21101, and the individually operated instrument 22221 is integrated into the analytical computing system 21100 through services and data storage provided by the cloud platform 22223, which provides integration between the individually operated instrument 22221 and the analytical computing system 21100, as well as optionally providing operational control over the individually operated instrument 22221. The collaboratively operated instruments 22222 may also have a collaborative instrument computer 22220 that provides integration between the collaborative instruments 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 instruments 22222, and the workflow auxiliary instruments 22226 may have a workflow auxiliary instrument computer 22225 that provides integration between the workflow auxiliary instruments 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 instruments 224. Examples of individually operated 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. A collaboratively operated instrument 22222 can combine some or all of the functionality provided by one or more individually operated instruments 22221 into an integrated platform that automates the execution of the individual operations of the individually operated instruments 22221, thereby eliminating the need for a user to perform various individual operations of the individually operated instruments 22221.The workflow support instruments 22226 can utilize either the individually operated instruments 22221 and / or the collaboratively operated instruments 22222 to provide support to a user testing assays on samples in the instrumentation environment 21106, where support can include, but is not limited to, collecting various consumables stored in different physical locations, potentially at various temperatures, preparing consumables used in processing one or more assays, and / or guiding a user through the overall assay steps using one or more of the individually operated instruments 22221. Alternatively, the consumable provider environment analysis user app 21103 can assist with other tests in addition to or in place of the assay tests and / or plate-based tests described herein.

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

[0344] FIG. 23 is an embodiment of a system architecture for a cloud platform 22223 as part of an analytics computing system 21100 that provides a common computing, software services, and data architecture so that data may be collected and shared by any computer anywhere in the world that has the associated software of the analytics computing system 21100 (FIG. 21), and one or more service servers 23302 provide scalable, robust, high performance computing resources to support services specific to the analytics computing system 21100 for retrieving, storing, transferring, and / or transforming data related to use of the analytics 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 robust, high performance computing and related software platform for one or more structured databases used to store and / or retrieve data generated by and / or for users of the analytics computing system 21100, and to store and / or retrieve data generated and / or used by the analytics computing system 21100 in preparation for and throughout its use, where the database technology may be relational in nature, such as, for example, SQL Server, Oracle, MySQL, Postgres, Aurora, and / or other similar relational database technologies, and / or may be non-relational in nature, such as, for example, Dynamo DB, Mongo DB, and / or other similar non-relational database technologies.and one or more bulk data servers 23315, which may include system content 23312, instrument content 23313, and consumable content 23314, that provide a scalable, robust, high-performance computing and associated software platform for storing and retrieving file-based data provided for use by the analytical computing system 21100 and / or generated through use of the analytical computing system 21100. Service server 23302, in one embodiment, includes a logical collection of services, namely, administration 23303, which includes a logical collection of services that support managing the use of the analytics computing system 21100; dashboard 23304, which includes a logical collection of services to support monitoring and controlling the use of the analytics computing system 21100; upload 23305, which includes a logical collection of services that support uploading consumable and meter information to the analytics computing system 21100; systems 23306, which includes a logical collection of services that support various non-user specific functions associated with the overall use of the analytics computing system 21100; and authentication 23308, which includes a logical collection of services that support typical scientific use of the analytics computing system 21100 by analytics users, and is associated with applications 23307, which includes a logical collection of services that support secure login to and logout from the analytics computing system 21100. In one implementation, service server 23302 is an easily scalable, scaled computing infrastructure from one or more servers represented by service server 23302, and in a preferred embodiment, each server deploys the entire logical collection of services 23303, 23304, 23305, 23306, 23307, and 23308, allowing a load balancer to distribute service requests evenly across one or more servers represented by 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 the RESTful (Representational State Transfer) design pattern, i.e., each provided service is stateless, i.e., does not store or retain data, and therefore any request made on a service can be satisfied by any available server on which the service is deployed on service server 23302 based on demand at the time of the request. To support 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, for example, the Java Platform, Enterprise Edition, which may support a cross-platform computing architecture, the .NET Framework for Windows only computing architecture, or other similar distributed object platforms, or may leverage some combination of one or more of these distributed object platforms. The database server 23310 may include one or more databases, such as 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 names, members, permissions, etc.). The system database 231...

Claims

1. 1. A method executed by at least one processor for navigating a path of hierarchical menu levels adapted for output to a graphical user interface (GUI), the method comprising: providing, by at least one processor, a first command for a first menu of one or more user-selectable menu items to be displayed on a first portion of a user interface (UI) display; providing, by the at least one processor, in response to a user selection, a second command for a second menu of one or more user-selectable menu items to be displayed on the first portion of the UI display; At least one of the user-selectable menu items of the first menu is adapted to be displayed on a second portion of the UI display, and comprises one or more of a previously selected menu item and a previously unselected menu item of the hierarchical menu level, and is adapted to be viewed simultaneously with the second menu in the first portion; Further, the one or more user-selectable menu items of the second menu include a menu item that provides for establishing at least one criterion to be applied to one or more experiments.

2. 10. The method of claim 1, wherein the one or more criteria provide for establishing, invoking, refining, modifying, and / or editing one or more criteria to be applied to data associated with the one or more experiments.

3. The method of claim 1 or 2, wherein the one or more experiments comprise an assay-based experiment.

4. 4. The method of claim 3, wherein the assay-based experiment is an electrochemiluminescence (ECL)-based assay.

5. The method of any one of claims 1 to 4, wherein the one or more criteria provide for filtering, limiting, truncating, and / or customizing one or more datasets associated with the one or more experiments.

6. 6. The method of claim 5, wherein the one or more data sets may be limited and / or filtered by upper and / or lower data limits for data associated with the one or more experiments.

7. 7. The method of claim 5 or 6, wherein the one or more data sets can be limited and / or filtered by one or more customizable ranges of data associated with the one or more experiments.

8. 8. The method of claim 1, wherein options in the first menu of one or more user-selectable menu items include designing one or more criteria, creating one or more new criteria, and / or recalling one or more previously created criteria.

9. 9. The method of claim 8, wherein in response to selecting to create the one or more new criteria, the first portion is adapted to display options for restricting, excluding, and / or flagging certain data from the data associated with the one or more experiments.

10. 10. The method of claim 8 or 9, wherein the one or more new criteria include ECL-related parameters including one or more of signal, adjusted signal, signal %CV, calculated concentration, calculated concentration %CV, and / or % recovery.

11. 11. The method of claim 9 or 10, wherein the options for restricting, excluding, and / or flagging particular data include filtering the data by one or more of: less than, equal to, greater than, within a range of values, and / or within one or more reference values.

12. The method of any one of claims 8 to 11, wherein the first part is adapted to display a confirmation screen for storing the one or more new criteria.

13. The method of claim 12 , wherein the one or more newly created criteria can be later recalled, edited, and / or modified.

14. 14. The method of any one of claims 8 to 13, wherein in response to a selection to invoke one or more previously created criteria, the first portion is adapted to display criteria from a set of previously created and saved criteria.

15. The method of claim 14 , wherein the set of criteria comprises one or more criteria associated with the experiment.

16. 16. The method of any one of claims 1 to 15, wherein the first menu options of one or more user-selectable menu items include displaying one or more of recent and / or available criteria.

17. 17. The method of claim 16, wherein in response to a selection of the available criteria, the first portion is adapted to display one or more of the individual who created the criteria, the date the criteria was created, and / or the name of the criteria.

18. 18. The method of any one of claims 1 to 17, wherein the UI display further includes an advanced selector, and in response to a first selection of the advanced selector, the UI display is adapted to display an advanced context menu including advanced menu options.

19. The method of claim 18 , wherein the advanced menu selection includes an option to display one or more of a set of criteria.

20. 20. The method of claim 19, wherein the display of one or more sets of criteria includes displaying existing criteria, displaying only visible criteria, displaying all criteria, and / or displaying only hidden criteria.

21. 20. The method of claim 18 or 19, wherein the advanced menu selection includes an option to hide criteria that, when selected, excludes hidden criteria from being displayed by the UI display.

22. 22. The method of claim 21, wherein the advanced menu selection includes an option to show visible criteria that, when selected, displays all criteria except the hidden criteria on the UI display.

23. 23. The method of any one of claims 18 to 22, wherein the advanced menu selection includes a show all criteria option, which when selected enables all criteria to be displayed by the UI display.

24. 1. A method executed by at least one processor for navigating a path of hierarchical menu levels adapted for output to a graphical user interface (GUI), the method comprising: providing, by at least one processor, a first command for a first menu of one or more user-selectable menu items to be displayed on a first portion of a user interface (UI) display; providing, by the at least one processor, in response to a user selection, a second command for a second menu of one or more user-selectable menu items to be displayed on the first portion of the UI display; At least one of the user-selectable menu items of the first menu is adapted to be displayed on a second portion of the UI display, and comprises one or more of a previously selected menu item and a previously unselected menu item of the hierarchical menu level, and is adapted to be viewed simultaneously with the second menu in the first portion; Further, the one or more user-selectable menu items of the second menu include a menu item that provides at least one option for creating, organizing, and / or aggregating data associated with one or more experiments.

25. 25. The method of claim 24, wherein the organization and / or aggregation of data provides for compilation, review, processing, and / or combination of the data associated with the one or more experiments.

26. 26. The method of claim 24 or 25, wherein the one or more experiments comprise an assay-based experiment.

27. 27. The method of claim 26, wherein the assay-based experiment is an electrochemiluminescence (ECL)-based assay.

28. 28. The method of any one of claims 24 to 27, wherein the organizing and / or aggregating data comprises displaying one or more data summaries comprising one or more of charts, graphs, and / or tabular data.

29. 29. The method of any one of claims 25 to 28, wherein the data relating to the one or more experiments comprises data from two or more dissimilar experiments.

30. 30. The method of any one of claims 25 to 29, wherein the data relating to the one or more experiments comprises data from two or more similar experiments.

31. 1. A method executed by at least one processor for navigating a path of hierarchical menu levels adapted for output to a graphical user interface (GUI), the method comprising: providing, by at least one processor, a first command for a first menu of one or more user-selectable menu items to be displayed on a first portion of a user interface (UI) display; providing, by the at least one processor, in response to a user selection, a second command for a second menu of one or more user-selectable menu items to be displayed on the first portion of the UI display; At least one of the user-selectable menu items of the first menu is adapted to be displayed on a second portion of the UI display, and comprises one or more of a previously selected menu item and a previously unselected menu item of the hierarchical menu level, and is adapted to be viewed simultaneously with the second menu in the first portion; Further, the one or more user-selectable menu items of the second menu include a menu item that provides at least one option for reviewing and / or analyzing data associated with one or more experiments.

32. 32. The method of claim 31, wherein reviewing and / or analyzing the data comprises highlighting and / or focusing on data of particular interest associated with the one or more experiments.

33. 33. The method of claim 31 or 32, wherein the one or more experiments comprise an assay-based experiment.

34. The method of any one of claims 31 to 33, wherein the assay-based experiment is an electrochemiluminescence (ECL)-based assay.

35. 35. The method of any one of claims 31 to 34, wherein highlighting and / or focusing on the particular data of interest is performed on one or more attributes of the data, including patient age, sex, and / or disease type.

36. The method of any one of claims 32 to 35, wherein only the highlighted and / or focused data is displayed by the UI display.

37. The method of any one of claims 32 to 36, wherein the highlighted and / or focused data is adapted to be selected by a user.

38. 1. A method executed by at least one processor for navigating a path of hierarchical menu levels adapted for output to a graphical user interface (GUI), the method comprising: providing, by at least one processor, a first command for a first menu of one or more user-selectable menu items to be displayed on a first portion of a user interface (UI) display; providing, by the at least one processor, in response to a user selection, a second command for a second menu of one or more user-selectable menu items to be displayed on the first portion of the UI display; At least one of the user-selectable menu items of the first menu is adapted to be displayed on a second portion of the UI display, and comprises one or more of a previously selected menu item and a previously unselected menu item of the hierarchical menu level, and is adapted to be viewed simultaneously with the second menu in the first portion; Further, the one or more user-selectable menu items of the second menu include a menu item that provides at least one option for manipulating data associated with one or more experiments.

39. 39. The method of claim 38, wherein the data manipulation comprises establishing, invoking, refining, modifying, and / or editing one or more criteria to be applied to data associated with the one or more experiments.

40. 40. The method of claim 38 or 39, wherein the data manipulation comprises compiling, reviewing, processing, and / or combining the data associated with the one or more experiments.

41. 41. The method of any one of claims 38 to 40, wherein said data manipulation comprises highlighting and / or focusing on data of particular interest associated with said one or more experiments.

42. The method of any one of claims 38 to 41, wherein the one or more experiments comprise an assay-based experiment.

43. 43. The method of claim 42, wherein the assay-based experiment is an electrochemiluminescence (ECL)-based assay.

44. The method of any one of claims 38 to 43, wherein the data is obtained from an ECL-based immunoassay.

45. 1. A method executed by one or more processors for navigating a path of hierarchical menu levels adapted for output to a graphical user interface (GUI), the method comprising: providing, by the one or more processors, a first command for a first menu of one or more user-selectable menu items to be displayed on a first portion of a user interface (UI) display; providing, by the one or more processors, in response to a user selection, a second command for a second menu of one or more user-selectable menu items to be displayed on the first portion of the UI display; At least one of the user-selectable menu items of the first menu is adapted to be displayed on a second portion of the UI display, and comprises one or more of a previously selected menu item and a previously unselected menu item of the hierarchical menu level, and is adapted to be viewed simultaneously with the second menu in the first portion; Further, the one or more user-selectable menu items of the second menu include data related to one or more experiments and at least one corresponding indicator.

46. 46. ​​The method of claim 45, wherein the indicator indicates whether the results of one or more samples from among the one or more experiments meet a quality standard.

47. 47. The method of claim 46, wherein the quality criteria comprises a threshold value for a particular sample based on a control.

48. 47. The method of claim 46, wherein in response to the results for a particular sample not meeting the quality criteria, the one or more processors indicate that the particular sample is to be restarted.

49. 47. The method of claim 46, wherein the quality criteria include ECL-related parameters including one or more of signal, adjusted signal, signal %CV, calculated concentration, calculated concentration %CV, and / or % recovery.

50. 50. The method of claim 49, wherein the one or more processors are further configured to activate one or more sample-corresponding indicators that affect a particular assay corresponding to the particular sample.

51. 51. The method of claim 50, wherein the one or more samples affecting the particular assay met the quality criteria.

52. 51. The method of claim 50, wherein the one or more processors are further configured to deactivate an indicator in response to receiving input from a user.

53. 49. The method of claim 48, wherein the one or more processors are further configured to display instructions to guide the user through a reboot process.

54. 46. ​​The method of claim 45, wherein the indicator indicates whether one or more samples of the one or more experiments should be restarted.

55. 46. ​​The method of claim 45, wherein the indicator indicates whether a particular spot, well, and / or plate of the one or more experiments should be restarted.

56. 56. The method of claim 55, wherein the one or more samples from among the one or more experiments are derived from a single well, multiple wells, a single plate, and / or multiple plates.

57. 46. ​​The method of claim 45, wherein the indicator is activated in response to receiving input from a user.

58. aggregating results of one or more samples from one or more experiments, each having one or more active indicators; displaying the aggregated results along with an indication of why the one or more activity indicators were activated; and 46. ​​The method of claim 45, further comprising: providing, by the one or more processors, in response to a user selection, a third command for a third menu of one or more user-selectable menu items to be displayed on the first portion of the UI display, wherein a menu item from among the third menu includes one or more assays indicated to be reactivated.

59. defining quality control criteria via a quality control module; analyzing the data based on the quality control criteria; 46. ​​The method of claim 45, further comprising:

60. 46. ​​The method of claim 45, further comprising displaying one or more charts representing the data associated with one or more experiments, wherein the data displayed in the one or more charts is user selectable.

61. 61. The method of claim 60, wherein the at least one corresponding indicator is activated in response to corresponding data being selected in the one or more charts.

62. 62. The method of claim 61 , wherein the one or more processors are further configured to activate indicators based on quality control criteria, and wherein the one or more of the activated indicators are deactivated in response to input from the user.

63. 46. ​​The method of claim 45, wherein the one or more user-selectable menu items of the second menu include a project that includes the one or more experiments.

64. 64. The method of claim 63, wherein the project comprises n experiments that can be expanded into z experiments, where z>n.

65. 65. The method of claim 64, wherein the project can be expanded through n+m experiments up to z experiments, where m is one or more new experiments subsequently added to the project and / or relaunches of previously launched experiments from the original set of n experiments.

66. 66. The method of claim 65, wherein the project spans time, with n experiments running up to a first instance in time and m experiments running after the first instance in time.

67. 1. A method for performing one or more experiments, executed by one or more processors, said method comprising: displaying on a graphical user interface (GUI) aggregated data corresponding to one or more samples of one or more assays of said one or more experiments, wherein one or more assays are performed in one or more vessels; displaying an indicator on the GUI to indicate which of the one or more samples should be repeated; and providing, by one or more processors, a command to repeat the one or more represented samples.

68. 68. The method of claim 67, wherein the indicator is displayed based on the aggregated data corresponding to the one or more samples that do not meet a quality criterion, the quality criterion comprising a threshold value for a particular sample.

69. 69. The method of claim 68, wherein the threshold value for a particular sample is based on a control.

70. 70. The method of claim 69, wherein in response to results for a particular sample not meeting the quality criteria, the one or more processors indicate that the particular sample be repeated.

71. 71. The method of claim 70, wherein the quality criteria include ECL-related parameters including one or more of signal, adjusted signal, signal %CV, calculated concentration, calculated concentration %CV, and / or % recovery.

72. 72. The method of claim 71, wherein the one or more processors are further configured to activate one or more sample-corresponding indicators that affect a particular assay corresponding to the particular sample.

73. 73. The method of claim 72, wherein the one or more samples affecting the particular assay met the quality criteria.

74. 73. The method of claim 72, wherein the one or more processors are further configured to deactivate the indicator in response to input from a user.

75. 71. The method of claim 70, wherein the one or more processors are further configured to display instructions to guide the user through a reboot process.

76. 68. The method of claim 67, wherein the indicator further indicates whether one or more samples should be excluded from the aggregated data.

77. 68. The method of claim 67, wherein the indicator indicates whether a particular sample performed in a particular one of the one or more vessels should be repeated.

78. 78. The method of claim 77, wherein the particular container comprises a spot, a well, and / or a plate.

79. 79. The method of claim 78, wherein the one or more samples are derived from a single well, multiple wells, a single plate, and / or multiple plates.

80. 68. The method of claim 67, wherein the indicator is activated in response to receiving input from a user.

81. aggregating results of the one or more samples, each having one or more active indicators; displaying the aggregated results along with an indication of why the one or more activity indicators were activated; and providing, by the one or more processors, in response to receiving a user selection, a command for a menu of one or more user-selectable menu items to be displayed on a first portion of the GUI; 68. The method of claim 67, further comprising:

82. defining quality control criteria via a quality control module; analyzing the data based on the quality control criteria; 68. The method of claim 67, further comprising:

83. 68. The method of claim 67, further comprising displaying one or more charts representing the aggregated data associated with one or more experiments, wherein the data displayed in the one or more charts is user-selectable.

84. 84. The method of claim 83, wherein the indicator is activated in response to corresponding data being selected in the one or more charts.

85. 85. The method of claim 84, wherein the one or more processors are further configured to activate indicators based on quality control criteria, and wherein the one or more of the activated indicators are deactivated in response to input from the user.

86. 68. The method of claim 67, wherein the aggregated data represents a project that includes the one or more experiments.

87. 87. The method of claim 86, wherein the project comprises n experiments that can be expanded into z experiments, where z>n.

88. 88. The method of claim 87, wherein the project can be expanded through n+m experiments up to z experiments, where m is one or more new experiments subsequently added to the project and / or repetitions of experiments previously launched from the original set of n experiments.

89. 90. The method of claim 88, wherein the project spans time, with n experiments being run up to a first instance in time and m experiments being run after the first instance in time.

Images