Method for providing user interface (UI)

Abstract

This invention discloses a method for interactively guiding a user through a menu selection path in a user interface. The method may include displaying a current options menu on a first portion of the user interface display. The user interface allows selection of a menu item from the current options menu and navigation through menu selection layers based on selection of a menu item in a previous selection layer. A second portion of the user interface display shows previously selected and previously unselected menu items in these navigation layers. Previously unselected menu items are displayed as optional options. The user interface allows navigation to different paths of menu options by selecting a previously unselected menu item in a previous navigation menu layer displayed on the second portion of the user interface display.

Description

Technical Field

[0001] This application generally relates to computers and computer applications, and more specifically, to a graphical user interface and a method for displaying user interaction items on said graphical user interface.

[0002] This application claims the benefit of prior U.S. Patent Application No. 62 / 669,381, filed July 17, 2018, the entire contents of which are incorporated herein by reference. Prior Technology

[0003] In various applications, including but not limited to bioanalysis, chemical analysis, radioanalysis, other scientific (e.g., bioscience and bioanalysis work), and industrial processes, which result in the use of scientific testing (e.g., biological testing, bioinstrumentation) instruments and industrial process equipment, the present invention improves testing, analysis, and processing by integrating a consistent software interface across various processing locations and at the instrument and equipment end of the relevant processing.

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

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

[0006] Similar difficulties exist in fields outside of instrumentation. For example, in various manufacturing settings, workflow integration, parts tracking, consumables tracking, work-in-process tracking, process and parts production documentation, and all the aforementioned instrumentation-related issues are challenging. Other examples exist, and the solutions disclosed in this specification are not limited to the problems discussed above. Summary of the Invention

[0007] A method and system are provided for interactively guiding a user through a menu-selected path on a user interface guided by a computer application. The method is executed automatically by at least one hardware processor. In one embodiment, the method may include displaying the currently selected menu on a first portion of the user interface display.

[0008] The method may also include allowing a user to select a menu item from the currently selected menu items displayed on the first portion of the user interface display, and to delve deeper into menu selection layers based on the selection of a menu item in a previous menu selection layer. The method may further include displaying previously selected and previously unselected menu items in these deeper layers on a second portion of the user interface display, wherein the previously unselected menu items are displayed as optional options. The method may also include allowing a user to jump to different paths of menu options by allowing the user to select previously unselected menu items from the previously guided menu layers displayed on the second portion of the user interface display. In one embodiment, the first portion and the second portion may be viewed simultaneously on the user interface display.

[0009] In another embodiment, a method for interactively guiding a user through a menu selection path on a user interface that guides a user via a computer application may include displaying a currently selected menu on a first portion of the user interface display. The method may also include allowing the user to select menu items from the currently selected menu displayed on the first portion of the user interface display, and to delve deeper into menu selection layers based on selection of menu items in previous selection layers. The method may also include displaying previously selected and previously unselected menu items in these deeper layers on a second portion of the user interface display, wherein the previously unselected menu items are displayed as selectable options. In one embodiment, the first portion and the second portion may be viewed simultaneously on the user interface display. In one embodiment, the graphical user interface maximizes black space by making the background of the user interface display black, thereby saving storage and improving display speed.

[0010] In another embodiment, a method for interactively guiding a user through a menu selection path on a user interface that guides a user via a computer application may include displaying a currently selected menu on a first portion of the user interface display. The method may also include allowing the user to select menu items from the currently selected menu displayed on the first portion of the user interface display, and to delve deeper into menu selection layers based on selecting menu items from previous menu selection layers.

[0011] The method may further include displaying previously selected and previously unselected menu items in a second portion of the user interface display, wherein the previously unselected menu items are displayed as selectable options. In one embodiment, the first portion and the second portion can be viewed simultaneously on the user interface display. In one embodiment, at least the first portion includes a search function box, a subordinate first area, and a subordinate second area, wherein the first portion is generally scrollable and displays the currently selected menu. In one embodiment, as search term input is detected in the search function box, the first portion is divided into the individually scrollable subordinate first area and subordinate second area.

[0012] In another embodiment, a method for interactively guiding a user through a menu selection path on a user interface that guides a user via a computer application may include displaying a currently selected menu on a first portion of the user interface display. The method may also include allowing the user to select menu items from the currently selected menu displayed on the first portion of the user interface display, and to delve deeper into menu selection layers based on selection of menu items in previous selection layers. The method may also include displaying previously selected and previously unselected menu items in these deeper selection layers on a second portion of the user interface display, wherein the previously unselected menu items are displayed as optional options.

[0013] In one embodiment, the first portion and the second portion can be viewed simultaneously on the user interface display. In one embodiment, the currently selected menu is displayed as a rotating graphic wheel. In one embodiment, the graphic wheel can rotate from a first menu item in the currently selected menu to a last menu item in the currently selected menu, and the graphic wheel can further rotate from the last menu item to the first menu item, and the first menu item and the last menu item are not connected during the rotation of the graphic wheel.

[0014] In another embodiment, a user interface system is provided, which may include at least one hardware processor and a memory device operatively coupled to the hardware processor. The hardware processor is configured to retrieve a currently selected menu from the memory device and display the currently selected menu on a first portion of the user interface display. The hardware processor is further operable to allow a user to select menu items from the currently selected menu displayed on the first portion of the user interface display, and to delve deeper into menu selection layers based on selection of menu items in previous menu selection layers. The hardware processor is further operable to display previously selected and previously unselected menu items in the deeper layers on a second portion of the user interface display, wherein the previously unselected menu items are displayed as optional options. The hardware processor is further operable to allow a user to jump to different paths of menu options by allowing the user to select previously unselected menu items from previous navigation menu layers displayed on the second portion of the user interface display. In one embodiment, the first portion and the second portion can be viewed simultaneously on the user interface display.

[0015] In another embodiment, a method is provided for guiding a path adapted to output to a tiered menu layer of a graphical user interface (GUI) by at least one processor. The method includes at least one processor providing a first command to display a first menu of user-selectable options on a first portion of the GUI display; and at least one processor providing a second command to display a second menu of user-selectable options on the first portion of the UI display, following user selection. The second menu is adapted to be displayed on a second portion of the UI display and includes one or more of a previously selected menu item and a previously unselected menu item from the tiered menu layer, and is adapted to be viewable simultaneously with the first portion.

[0016] In another embodiment, a non-transitory computer-readable medium storing computer instructions is provided, which, when executed by a processor, cause the processor to perform a method for guiding a path adapted for output to a tiered menu layer of a graphical user interface (GUI). The method includes providing a first command to display a first menu of user-selectable options on a first portion of the user interface (UI) display; and providing a second command to display a second menu of user-selectable options on the first portion of the UI display, following user selection. The second menu is adapted to be displayed on a second portion of the UI display and includes one or more of a previously selected menu item and a previously unselected menu item from the tiered menu layer, and is adapted to be viewable simultaneously with the first portion.

[0017] In another embodiment, a system is provided for guiding a path adapted to output to a tiered menu layer of a graphical user interface (GUI). The system includes at least one processor; a user input device; and a computer-readable storage medium configured to store a computer application, wherein the at least one processor is configured to execute instructions for the computer application. The at least one processor is executable to execute instructions for: providing a first command to display a first menu of user-selectable options on a first portion of the user interface (UI) display; and providing a second command to display a second menu of user-selectable options on the first portion of the UI display, following user selection. The second menu is adapted to be displayed on a second portion of the UI display and includes one or more of a previously selected menu item and a previously unselected menu item from the tiered menu layer, and is adapted to be simultaneously viewable with the first portion.

[0018] A computer-readable storage medium for storing machine-executable instructions to perform one or more methods described herein may also be provided.

[0019] Other features, structures, and operations of various embodiments are described in detail below with reference to the accompanying drawings. Simple Explanation of the Diagram

[0020] [Figure 1] illustrates a method for displaying interactive items on a user interface display for computer-user interaction in one embodiment.

[0021] [Figures 2A] to [Figures 2O] illustrate an example graphical user interface display in one embodiment.

[0022] [Figure 2P] illustrates an example of a systematic user interface (Methodical user interface) including an advanced context menu according to an embodiment.

[0023] [Figure 3] is a flowchart illustrating a method for interactively displaying interactive items on the user interface for computer-user interaction in another scenario.

[0024] [Figure 4] is a flowchart illustrating the user login interface of an analysis system in one embodiment.

[0025] [Figure 5] is a flowchart illustrating a method for displaying the user interface screen in one embodiment.

[0026] [Figure 6] is a diagram illustrating the workflow of a screen defining a measurement method in one embodiment.

[0027] [Figure 7] is a diagram illustrating the workflow of a user interface for selecting a measurement method in one embodiment.

[0028] [Figure 8] is a flowchart illustrating the workflow of the user interface displayed for the definition sample in one embodiment.

[0029] [Figure 9] is a flowchart illustrating the workflow for confirming the execution of a defined user interface in one embodiment.

[0030] [Figure 10] is a flowchart illustrating the workflow of a user interface used to notify a user that a task has been completed in one embodiment.

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

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

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

[0034] [Figure 14] is a flowchart illustrating the workflow of a user interface for executing / executing options shown in one embodiment.

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

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

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

[0038] [Figure 18] Schematic illustration of elements of a graphical user interface (GUI) system in one embodiment.

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

[0040] [Figure 20] is an example screenshot of a screen showing the graphics wheel / scroll tool maximizing the black space of the screen in one embodiment.

[0041] [Figure 21] Schematic illustration of a cloud-based analytics computing system in one embodiment.

[0042] [Figure 22] illustrates the system architecture of a cloud-based analytics computing system in one embodiment.

[0043] [Figure 23] illustrates the system architecture of a cloud platform for a cloud-based analytics computing system in one embodiment.

[0044] [Figure 24] illustrates the interaction between the administrator's computer and the cloud platform in one embodiment.

[0045] [Figure 25] illustrates the interaction between the analysis user's computer and the cloud platform in one embodiment.

[0046] [Figure 26] illustrates the interaction between a data integration computer and a cloud platform in one embodiment.

[0047] [Figure 27] illustrates an embodiment of supporting interaction between a user's computer and a cloud platform.

[0048] [Figure 28] illustrates the interaction between a data integration computer and a cloud platform in one embodiment.

[0049] [Figure 29] illustrates the interaction between a consumable information upload computer and a cloud platform in one embodiment.

[0050] [Figure 30] illustrates the interaction between the computer that uploads account information and the cloud platform in one embodiment.

[0051] [Figure 31] illustrates the interaction between the computer and the cloud platform for uploading instrument information in one embodiment.

[0052] [Figure 32] illustrates the interaction between the collaborative operation instrument computer and the cloud platform in one embodiment.

[0053] [Figure 33A] illustrates the interaction between an individual operating instrument computer and a cloud platform in one embodiment.

[0054] [Figure 33B] illustrates the workflow for the embodiment shown in Figure 33A that facilitates interaction between the instrument computer and the cloud platform.

[0055] [Figure 34A] illustrates the first part of a software architecture for cloud platform services in one embodiment.

[0056] [Figure 34B] illustrates the second part of the software architecture of the cloud platform service for the embodiment shown in Figure 34A.

[0057] [Figure 35A] illustrates the logical design of system data in one embodiment.

[0058] [Figure 35B] illustrates a scenario in which an analytical computing system is used to map business entities to accounts.

[0059] [Figure 35C] illustrates the logical design of team data related to plate data in one embodiment.

[0060] [Figure 35D] illustrates the logical design of team data related to measurement method data in one embodiment.

[0061] [Figure 35E] illustrates the logical design of team data related to execution data in one embodiment.

[0062] [Figure 35F] illustrates the logical design of team data related to experimental data in one embodiment.

[0063] [Figure 36A] illustrates an exemplary structure of a user account for an analytics computing system in one embodiment.

[0064] [Figure 36B] illustrates the process of establishing a user account for an analytical computing system in one embodiment.

[0065] [Figure 36C] illustrates the flow of a user account in conjunction with an analytical computing system in one embodiment.

[0066] [Figure 36D] illustrates the user account flow of a consumables combined analysis computing system in one embodiment.

[0067] [Figure 37] Schematic illustration of a module of a manager software application in one embodiment.

[0068] [Figure 38A] illustrates the flow of the manager console module in the manager APP for account managers in one embodiment.

[0069] [Figure 38B] illustrates the flow of the administrator console module in the administrator APP for team administrators in one embodiment.

[0070] [Figure 38C] illustrates the user login process in one embodiment.

[0071] Figures 38D to 38H are screenshots illustrating the workflow shown in Figure 38A.

[0072] [Figure 38I] is a schematic illustration of the advanced quick display menu of the administrator console module.

[0073] [Figure 39A] illustrates the process of the management review and tracking module of the administrator APP in one embodiment.

[0074] Figures 39B to 39E illustrate the appearance of the user interface of the management review and tracking module according to the embodiment.

[0075] [Figure 40] Schematic illustration of a module for analyzing user software applications in one embodiment.

[0076] [Figure 41] illustrates the flow of an analysis method module for analyzing a user's APP in one embodiment.

[0077] [Figure 42A] illustrates the design flow of a measurement method module for analyzing a user's APP in one embodiment.

[0078] [Figure 42B] illustrates the inspection process of a measurement module for analyzing user apps in one embodiment.

[0079] [Figure 43A] illustrates the design process of an experimental module for analyzing a user's APP in one embodiment.

[0080] [Figure 43B] illustrates the inspection process of the experimental module for analyzing user apps in one embodiment.

[0081] [Figures 43C] to [Figures 43H] schematically illustrate the appearance of a user interface for a reader module according to one embodiment.

[0082] [Figure 44] illustrates the process of a user app review and tracking module in one embodiment.

[0083] [Figure 45] Schematic illustration of a module of a collaborative operation instrument software application in one embodiment.

[0084] [Figure 46] illustrates the operation module of the collaborative operation instrument APP in one embodiment.

[0085] [Figure 47] illustrates the process of the maintenance module of the collaborative operation instrument APP in one embodiment.

[0086] [Figure 48] Schematic illustration of a module of an individual operating instrument software application in one embodiment.

[0087] [Figure 49A] illustrates the operation module of the individual operating instrument APP in one embodiment.

[0088] [Figure 49B] illustrates the process of checking the results of the operation module of the disk reader, which is an individual operating instrument APP, in one embodiment.

[0089] [Figure 50] Schematic illustration of a module of a workflow-aided instrument software application in one embodiment.

[0090] [Figure 51] illustrates the workflow help module of a workflow help instrument APP in one embodiment.

[0091] [Figure 52] is an example of the calculation process for analyzing the automatic software update of a user's computer.

[0092] [Figure 53] is an example of the automatic software update operation process of the analysis instrument computer.

[0093] [Figure 54] is an example embodiment of the non-biological analysis application of the disclosure architecture of a software module in a gourmet chef APP.

[0094] [Figure 55] is an example of the user experience process from the Food Chef APP to the meal planner.

[0095] [Figure 56] Schematic illustration of a system for implementing a systematic user interface according to an embodiment.

[0096] [Figure 57] illustrates the process of guiding a hierarchical selection tree via the user interface.

[0097] Figures 58A to 58HH are example, non-limiting embodiments of the reader module.

[0098] Figures 59A to 59T are example non-limiting embodiments of the experimental module.

[0099] Figures 60A to 60I are exemplary, non-limiting embodiments of the maintenance module.

[0100] [Figure 61A] to [Figure 61Q] are example non-limiting embodiments of the administrator console module.

[0101] Figures 62A to 62P are example, non-limiting embodiments of typical screen captures applicable to this specification of a multi-module.

[0102] [Figure 63] is an example non-limiting embodiment of the audit tracking module.

[0103] [Figures 64A] to [Figures 64RR] are example non-limiting embodiments of the measurement method module. Implementation

[0104] The embodiments described in this specification provide technical solutions to various technical problems by improving upon existing technologies and establishing entirely new technologies. The technical problems addressed by the embodiments discussed in this specification include inefficient conventional user interfaces and difficulties in integrating different parts of a processing workflow.

[0105] This specification provides practical applications of technical solutions to problems in conventional user interfaces, such as inefficiency, accuracy, repeatability, and computational inefficiency, which improve the user interface discussed herein. The technical solutions provided in this specification improve each of these aspects by using the user interface methods and techniques of this invention. In particular, the technical solutions provided by the user interface disclosed in this specification offer users a more efficient guided menu system for complex processes.

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

[0107] The systems, methods, and techniques of this invention provide a user interface that guides users to select options via a user interface display or another presentation device, allowing them to find the correct choice in less time. This reduces the number of attempts to make incorrect selections and the time spent on user guidance in completing desired computational functions or goals. In various embodiments, the user interface of this invention can present a limited selection of all available options to the user in a specific manner, guiding the user through these options, simplifying operation, and providing the user with more efficient access to the desired computational function. In another embodiment, the user interface of this invention can connect the user more directly to the application.

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

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

[0110] Further design principles include providing users with a single new option at any given time, while also offering easy access to previously selected choices. This principle can be implemented through a two-part display system. The current section can be configured to display the user's current selection, while the history section can be configured to display information about previous selections. The current and history sections together provide a "direct workflow mode." The current section, presenting the user's current selection, can strictly limit the number of menu items displayed, such as seven, five, three (or any other number), while other potential items in the same menu are displayed elsewhere. Previously selected choices (and the menus from which the selection was made) can be displayed to the user in a nested or overlay manner. A series of nested previous menus can be presented using a Russian nesting doll (matryoshka) approach, with each previously selected menu item expanding within a displayed sub-menu. Nested or overlayed previously selected menu items can also provide a breadcrumb trail explaining the path taken to reach the current menu.

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

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

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

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

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

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

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

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

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

[0120] As discussed in this manual, menu items can be selected using "Select," "Highlight," and / or "Click." As used in this manual, a "Highlight" menu item means, for example, highlighting the "Highlight" option to the user, such as a menu item highlighted at the center of the scroll wheel. "Highlight" may include changing the color, size, font, etc., of the menu item to visually highlight it for the user. A "Fade" user option may include changing the color, size, font, etc., of the menu item to visually fade it for the user. A menu item may be highlighted or faded based on user actions (e.g., clicking the mouse, touching the touchscreen, rotating the scroll wheel, etc.), and / or may be highlighted or faded based on interface actions (e.g., providing a default "Highlight" option).

[0121] As used in this manual, "select" a menu item means a menu item that the user has selected, and the user interface has performed one or more menu steps based on that selection. "Select" a menu item causes the computer system to execute computer instructions to proceed to the next menu item, rather than simply "highlighting" the menu item. For example, "select" a menu item may be used to display a new menu based on a selection. Selecting a menu item may highlight the selected menu item, but highlighting a menu item does not necessarily include selecting a menu item.

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

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

[0124] Menu items may be described as "selectable" in this manual. A "selectable" menu item is one that the user can interact with by selecting or highlighting it. Selectable menu items may be displayed by changing their color, highlighting, font, etc., to indicate that they are selectable. Menu items may also be described as "non-selectable" in this manual. A "non-selectable" menu item is one that the user cannot currently interact with by selecting or highlighting it. Non-selectable menu items may be displayed by changing their color, highlighting, font, etc., to indicate that they are not selectable.

[0125] Menu items can also be described as "previously selected" and "previously unselected." A "previously selected" menu item refers to the menu item selected to reach the currently displayed menu interface. It does not require the user to actively select a "previously selected" menu item. By default, if the system takes the user to a menu layer below the top layer, even if the user does not actively select anything during the current process, the menu items or selections in the current path can be indicated as "previously selected." A "previously unselected" menu item refers to a menu item that was not selected to reach the currently displayed menu interface. For example, if the user has selected a first menu item but not a second menu item, the system can continue to display subsequent menus or sub-menus as the first menu item is selected in the current section of the MUI. In the history section of the MUI, the system can display the first menu item as a previously selected menu item and the second menu item as a previously unselected menu item. The previously unselected menu item can then be displayed as selectable.

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

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

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

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

[0130] As discussed in this specification, menus are presented as a series of hierarchical menu trees. Each level of the menu tree contains multiple menus leading to other menus. Thus, a first level of the menu tree includes a plurality of first menus, a second level includes a plurality of second menus, a third level includes a plurality of third menus, and so on. This structure continues to execute menu levels. In some discussions in this specification, a first menu is simply referred to as a menu, and subsequent menu levels in the tree are called sub-menus, sub-sub-menus, etc. Sometimes, multiple menu levels below a current menu may be collectively referred to as sub-menus. Thus, a first menu's sub-menus may include a plurality of second menus, a plurality of third menus, a plurality of fourth menus, a plurality of execute menus, etc. An example of a hierarchical menu tree structure is illustrated in Figure 2K. As used in this specification, regarding hierarchical menu trees, each level is referred to as a "menu" even when no text menu is presented to the user. For example, one menu might only present an "Execute" button to implement the processing designed in other parts of the menu. Another menu might present a tutorial.

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

[0132] In this embodiment, each menu may also include additional information displayed in the MUI. This additional menu information may provide user information about the menu item and / or general information about the menu content. For example, in a menu presenting a user with a save file option, additional information indicating remaining disk space may be provided. In another example, in a menu presenting a user with an option to perform a measurement, additional information about the available consumables for the displayed measurement may be provided.

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

[0134] In this embodiment, the execution menu facilitates the interface between the MUI software and the physical world. The execution menu can provide, for example, the execution of commands output by the systematized user interface control system 1102 connected to the system or instrument, to implement processes designed using the MUI. In this example, such an execution command could cause a manufacturing system to begin manufacturing a part, cause a measuring instrument to begin measuring, or cause a design system to send design specifications, etc.

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

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

[0137] These types of "cobot" interactions (where the MUI integrates the physical world operations of human operators and automated machines) can be applied to a variety of processes or workflows, including laboratory workflows, manufacturing workflows, food production workflows (such as beer production, bread production, etc.), and transportation and logistics workflows (such as packing and picking boxes, packaging, etc.).

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

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

[0140] In the history section, menu items for each past menu can be displayed linearly in the MUI. All menu items from that menu layer are displayed in a single column (horizontal or vertical). Each group of past menu items can be displayed linearly, while the menus as a whole can be stacked or nested. This feature is illustrated in Figure 2C, which shows "menu items" and "sub-menu items" displayed linearly. The relationship between the "menu items" and the "sub-menu items" is stacked or nested. Therefore, within a single menu layer, menu items are adapted to be displayed linearly, while previous and subsequent menu layers are adapted to be nested.

[0141] A selection menu may be displayed in a graphic wheel, which is rotated in one direction (e.g., horizontal or vertical (e.g., left and right, up and down) or other directions). In another configuration, a selection menu may be displayed as a graphic slider, which is slidable in one direction (e.g., horizontal or vertical (e.g., left and right, up and down) or other directions). For example, an initial menu layer (first layer) may be displayed horizontally and slid left and right, and the next menu layer (second layer) may be displayed vertically and rotated up and down. In yet another configuration, the selection menu may be displayed as a series of concentric circles, each menu layer displayed as a circle with menu selections (also called options or menu items). For example, an initial menu layer (first layer) may be displayed in a central circle, the next menu layer (second layer) may be displayed in the next circle (second circle) surrounding the central circle, a further next menu layer (third layer) may be displayed in yet another circle surrounding the second circle, and so on. However, the selection menu can be displayed or visualized as a graphical decision tree with nodes and edges. Each level of the graphical decision tree can represent a menu level with selections.

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

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

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

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

[0146] In various embodiments, the term "module" is used in this specification to refer to a specific suite of software protocols and computer instructions for generating, maintaining, and operating multiple elements of a MUI as described herein. One or more processors described herein may be configured to execute multiple software protocols to provide a systematized user interface module. As used herein, "systematized user interface module" refers to any one of a subset of modules that provides a specific user interface. For example, an administrator console module, an audit trace module, and a reader module may be provided as specific systematized user interface modules to respectively perform tasks related to system management, auditing, and disk reading. Each MUI module may be considered to include at least one-level menu tree containing at least multiple levels of menus. Each module may further include preferred preset visual elements, preferred preset exclusion and restriction lists, and other module-specific features. Other modules are discussed in more detail below and throughout the invention. Throughout the invention, various forms of various MUI modules are discussed. The features discussed for any particular MUI module are non-exclusive and non-limiting, and can be applied equivalently to any other MUI module. Therefore, any MUI features discussed in this specification (whether in a broad sense or with respect to a particular module) can generally also be widely applied to the MUI and / or any other particular MUI module discussed in this specification.

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

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

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

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

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

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

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

[0154] The menu manager 1054 is a software protocol that operates on the systematic user interface control system 1102. The menu manager 1054 is configured to manage a hierarchical menu tree and all menu items associated with that tree. The menu manager 1054 is configured to select appropriate menu items for display, determine the next menu to be displayed, and manage all styles of guidance through the menu tree. The menu manager 1054 can also be configured to send commands to other managers of the systematic user interface control system 1102 based on menu guidance requirements.

[0155] The user manager 1056 is a software protocol that operates 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. For example, the user manager 1056 manages user authorization, including maintaining user authorization records, verifying user credentials, and other necessary user authentication tasks.

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

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

[0158] The data storage manager 1064 is a software protocol that operates 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 1102 can interact. The data storage manager 1064 is configured to send commands to any of the various data storage devices discussed in this specification to manage the storage and retrieval of data.

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

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

[0161] Each menu can display options in the active portion of the interface. Menu selection or option selection can trigger the display or presentation of subsequent, immediately following, or sub-menus, which may include multiple menu options or sub-menu options of themselves. When a user selects a menu that leads to a new menu, the menu items of the old menu can be moved from the active portion of the interface to the history portion, allowing the user to easily move to the new menu option while retaining the content of the previous menu option. These features are described in more detail below with reference to Figures 2A-2O, Figure 3, and Figure 57.

[0162] Figure 57 is a flowchart illustrating a process 5200 that guides adaptation to a tiered menu path output to a user interface (such as a GUI, MUI, and / or any other type of UI discussed in this specification). The process 5200 is executed on a computer system having one or more physical processors programmed with computer program instructions, causing the computer system to execute the method when the one or more physical processors execute the computer program instructions. The one or more physical processors are hereinafter simply referred to as processors. In an embodiment, the process 5200 is executed via a systematized user interface control system 1102 as described in this specification. This systematized user interface control system 1102 represents an example of a hardware and software combination configured to execute the process 5200, but implementation of the process 5200 is not limited to the hardware and software combination of the systematized user interface control system 1102. As discussed in this specification, any other suitable computer system may also execute and / or implement the process 5200. The description of the process 5200 is not limited and various operations may be changed or modified according to the embodiments described in this specification.

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

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

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

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

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

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

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

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

[0171] As mentioned above, a selection menu can be displayed as a rotatable graphic wheel showing menu items (selections or options), wherein menu items can be displayed on the wheel as it rotates. Menu items on a sliding axis can be displayed as a similar graphic of the sliding axis, which can slide. The rotation or sliding action can be performed with the movement of a finger on a touch screen or input from a directional device or another input device. In another embodiment, the rotation or sliding action can be performed automatically by the user interface (or the hardware implementing the user interface) in a timing manner. In one embodiment, the rotation or sliding direction can be switched to a different direction as the selection menu is repositioned from the first part to the second part.

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

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

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

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

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

[0177] In another mode, a window can be opened to display the selected options as highlighted options, with one (or more) options on the left and another (or more) options on the right.

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

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

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

[0181] Please refer to Figures 18-19 for an additional example system for performing the method described in Figure 1. As mentioned above, the system configurations presented in Figures 18 and 19 may be embodiments and / or implementations of the systematized user interface control system 1102 shown in Figure 56.

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

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

[0184] Although Figure 18 is specifically related to a GUI system, it is merely an example. It should be understood that the methods and techniques described in this specification can also be implemented via other MUIs, including text-based, virtual reality-based, augmented reality-based, mixed reality-based, and others.

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

[0186] The hardware processor 1804 can, for example, execute the methods described with respect to Figures 1 and 3.

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

[0188] GUI technology can be implemented on any type of computing device, such as desktop computers, laptops, mobile devices (e.g., Android or Apple iOS), tablets, and using any type of interface (e.g., mouse, touch screen, etc.). GUI technology can also be implemented on instruments, such as an instrument for performing biological assays (e.g., immunological or nucleic acid assays). In some embodiments, the instrument performs electrochemiluminescence assays. In some embodiments, the instrument is an automated assay system, for example, comprising: (a) a single robot-controlled 8-channel pipette, (b) a single robot-controlled assay disc clamp, (c) a single 96-channel assay disc washer, (d) a single disc reader, (e) one or more disc oscillators with a total capacity of at least five disc oscillation positions, and (f) a processor adapted to perform assay processing in a 96-well disc to analyze multiple samples.

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

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

[0191] Figure 19 schematically illustrates an example computer system 100 in which the system and / or method of the present invention can be implemented. One or more central processing units (e.g., CPUs) 2 may include one or more arithmetic / logic units (ALUs), cache memory, and temporary registers and / or temporary register files. A temporary register is a small storage device; a temporary register file may be a group of multiple temporary registers. Cache memory is a fast storage memory device, for example, including a static random access (SRAM) chip. Cache memory is used as a temporary storage area to store data used by the CPU 2. The display is a simplified hardware configuration. The CPU 2 may include other combinational circuitry and storage devices.

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

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

[0194] As used in this invention, the term "computer system" can include various combinations of fixed and / or portable computer hardware, software, peripherals, mobile devices, and storage devices. The computer system may include networks or links to collaboratively execute multiple individual components, or may include one or more independent components. The hardware and software components of the computer system of this invention may be included and can be incorporated into fixed and portable devices such as desktop computers, laptops, and / or servers. A module may be a device, software, program, or system element that implements certain "functions," which may be embodied as software, hardware, firmware, electronic circuitry, etc.

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

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

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

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

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

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

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

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

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

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

[0205] Different display commands can specify different scrolling methods or directions, or different commands can use the same or similar scrolling methods or directions. In one embodiment, the orientation in different commands (such as the first command and the second command) can specify that the orientation is substantially orthogonal to each other. In other embodiments, the orientation can be horizontal, substantially horizontal, vertical, substantially perpendicular, concentric, and substantially concentric relative to each other. As used in this specification, it can substantially be + or -5°. In other cases, it can substantially be + or -10°. In yet another case, it can substantially be + or -15°. In still another case, it can substantially be determined by percentages such as 80% or 90%.

[0206] Figures 2A-2O illustrate examples of user interface displays in different embodiments, the details of which are described in more detail below.

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

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

[0209] As shown in Figure 2A, the menu items 202 of a first menu are arranged in the first portion 204 of the interface in a vertically oriented (i.e., first orientation) scroll wheel. The MUI includes a display 206. The first portion 204 can display the menu items 202 in response to a first display command of a first menu of user-selectable options to be displayed on the first portion 204 of the MUI. As mentioned above, the first display command can be provided by the display manager 1050.

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

[0211] In one embodiment, the first portion may include a decision area. The decision area may be located centrally within the first portion. The decision area may be a location in the first or existing portion where a highlighted or brightly displayed menu item is available for immediate selection. For example, in FIG2A, "Menu Item" 4 is displayed in the decision area and in a larger font than other menu items to highlight or brighten the menu item for immediate selection. The first display command that causes the provision of the first menu may specify the menu item displayed in the decision area to be highlighted or brightened, such as by displaying it in a larger font than other menu items not in the decision area. In other embodiments, the menu item displayed in the decision area may be bolded, italicized, brightened, or underlined using a color different from the background.

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

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

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

[0215] Please refer back to Figure 3. In step 304, as a menu item is selected from the detected menu item list, the menu item list is repositioned to a second portion of the user interface display. The menu item list is displayed on the second portion in a second visual orientation that is substantially orthogonal (e.g., perpendicular) to the first visual orientation. For example, the second visual orientation could be a horizontal orientation.

[0216] A relocation command relocates the first menu of menu selection 202 from the first portion 204 of the MUI display 206 to the second portion 208. Figure 2B schematically illustrates the result of the relocation command. The relocation command may include the menu selection of the first menu to be displayed in the second portion 208, the size and orientation of the display, necessary display visual elements, an instruction to select a menu item for relocation, and any other information related to display commands discussed in this specification. The relocated first menu, currently displayed as a past menu in the history or second portion 208, may include user-available menu items 202 and one or more or all of previously made selections. The user selects the relocated menu item 202 to become a previously selected menu item, while unselected menu items in menu item 202 become previously unselected menu items. Previously unselected menu items represent previously guided hierarchical menu layers. After repositioning the menu items 202 of the first menu, the display manager 1050 causes the MUI to display the sub-menu items 210 of the second menu as a new current or subsequent menu item layer for user interaction in the currently active or first section 204, following the first menu selection. As shown in FIG2B, the subsequent or second menu selection layer includes the second sub-menu item 210 displayed in the currently active or first section 204 of the MUI display 206.

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

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

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

[0220] The repositioning command can also specify menu items of different sizes. For example, the selected menu item (triggering repositioning) in the first menu can be specified to be highlighted, such as by displaying it in a larger font than the unselected menu item. In other states, the selected menu item can be highlighted in a different color than the background, bolded, italicized, or highlighted, or underlined. In yet another state, the repositioning command can also specify the relative position of the menu items 202 within the second section 208. For example, a selected menu item can be centered within the second section relative to other menu items (unselected menu items).

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

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

[0223] A relocation command for the first menu of user-selectable options displayed on the second portion 208 of the MUI display 206 causes the second portion 208 to display the first menu item 202. As previously mentioned, this relocation command is 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 these first menu items 202 that are selectable by the user. These menu items 202 may be selected immediately or not immediately.

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

[0225] The first section 204 and the second section 208 are displayed on the MUI display 206, making both viewable, for example, simultaneously. The MUI display 206 can be presented via one or more physical display screens. The second section 208 may contain one or more menus, each menu including both previously selected and previously unselected menu items from the previously guided hierarchical menu. In the presentation shown in Figure 2C, the second section 208 (history section) includes menu item 202 and sub-menu item 210, each of which is included in the first section 204 of the previous MUI presentation. Previously selected menu items 202 and sub-menu items 210 (i.e., those that cause sub-sub-menu items 212 to be displayed in the first section) can be highlighted or highlighted to indicate that they were previously selected. As shown in Figure 2C, "Menu item" 4 and "Sub-menu item" 3 are highlighted to indicate that they were previously selected.

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

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

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

[0229] Please refer back to Figure 3. In step 306, on the first part of the user interface, before repositioning to the second part, the first list of sub-menu items related to the selected menu item is displayed in a first visual orientation. As shown in Figure 2B, the first sub-list of menu item 210 is, for example, displayed vertically in the first part 204.

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

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

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

[0233] Although Figures 2A-2C display 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 another configuration, the first and second visual orientations can be displayed in any other position.

[0234] As mentioned above, menu items and associated sub-menu items can be displayed as a sliding axis graphic element, a rotating wheel graphic element, or another graphical user interface element. For example, a concentric wheel element as described below with reference to Figures 2H-2J can be used.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0249] In one embodiment, an advanced quick menu can be provided via one or more commands sent by the menu manager 1054. Figure 2P schematically illustrates an example of a systemized user interface including the advanced quick menu 270. The advanced quick menu 270 contrasts with the first and second sections, providing a "direct workflow mode" throughout. The advanced quick menu 270 is accessible via an advanced quick menu selector 290, which in this embodiment may be located on some or all screens of a systemized user interface. The advanced quick menu 270 provides additional advanced menu items 271, in addition to items appearing in the current menu of the currently active first section 204 or one or more past menus appearing in the historical second section 208. The advanced quick menu 270 can be accessed by clicking or hovering a cursor over the advanced quick menu selector 290 or otherwise indicating access to the advanced quick menu 270. The advanced quick display menu 270 includes the selection of advanced menu item 271.

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

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

[0252] The advanced quick display menu 270 provides users with a larger array of storable menu items without causing clutter in the current or historical sections. In embodiments, some of the advanced menu items 271 in the advanced quick display menu 270 may be infrequently selected items, for example, fewer than 50, 45, 40, 35, 30, 25, 20, 15, 10, or 5% of the usage case. The advanced menu items 271 of the advanced quick display menu 270 can be selected according to the user's interaction pattern with the MUI, as explained in more detail below.

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

[0254] In this embodiment, when the advanced quick display menu 270 is selected, the MUI dims and / or blurs other graphics, text, etc. The advanced quick display menu 270 is displayed on a transparent background, making it the same as the rest of the background (e.g., black). Therefore, 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 errors. The background of the dialog box is further adapted to conform to the backgrounds of the first and second portions of the UI display. Furthermore, when the dialog box is displayed in the foreground of the UI display, one or more of the text, graphics, photos, and videos displayed in the backgrounds of the first and second portions of the UI display are adjusted to be out of focus.

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

[0256] Exclusion or restriction information can be used to exclude menu items from views of specific users, user groups, user types, etc. For example, administration menu items or menu layers can be excluded from views of engineers or technicians. In another example, design menu items or menu layers can be excluded from views of laboratory assistants or laboratory technicians.

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

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

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

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

[0261] In other embodiments, different exclusion tables may be used depending on whether menu items are to be displayed on the MUI display 206 in the first section 204 or the second section 208. According to this embodiment, the exclusion table may have additional information columns, one column for each section (menu). A column for the first section lists menu items to be excluded when displayed on the first section 204 of the MUI display 206; a column for the second section 208 lists menu items to be excluded when displayed on the second section of the MUI display 206; and columns for the additional sections list additional menu items to be excluded when displayed on any additional section of the MUI display 206.

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

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

[0264] In other embodiments, instead of excluding menu items, menu items can be moved to a position relative to other menu items to dilute the menu items related to other menu items. According to this embodiment, the exclusion table can be used by menu manager 1054 to reorder or change the position of menu items on a hierarchical menu level. A subsequent command (a first command, a second command, and / or a third command) can reflect the changed position of the menu item.

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

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

[0267] In other embodiments, instead of a table (or multiple tables), the list of menu items and / or tiered menu levels is stored and associated with an identifier (e.g., a MAC address).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0294] In other embodiments, instead of a single limiting command, the display command can be modified by menu manager 1054 to remove menu items other than those determined to have a frequency higher than a threshold percentage.

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

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

[0297] In one embodiment, this limiting function can be applied to any type of MUI module as follows. The threshold percentage can be used to determine which menu items will be displayed (e.g., but not limited to). For example, a threshold percentage of 90% or 80% can be used, meaning only menu items selected more than 90% or 80% of the time are displayed. In one example, selection frequency can be applied based on the user's login phase, meaning only menu items displayed during 90% or 80% of the user's login time are shown. This limiting function can be applied to one or more menu tiers, i.e., a first menu tier, a second menu tier, etc. In some embodiments, the threshold can vary based on the menu tier (e.g., lower tiers may have lower display frequency requirements, as they often have more options, thus reducing selection frequency). Menu items that do not meet the threshold (e.g., using 10% or less, or 20% or less) are displayed in advanced quick-access menus, which vary depending on the currently displayed menu. Thus, the user's selection is limited to the most frequently used choices throughout the MUI, allowing for significantly faster user navigation.

[0298] The 90% / 10% and / or 80% / 20% values ​​are merely illustrative and may be selected depending on the MUI module to be implemented. In one example, this limitation function may also be based on a preset protocol, rather than a user-defined protocol. For example, a supplier may sell assay kits that include a standard protocol that further allows customers to make modifications. As the user moves through the menu system, the standard protocol options may include available menu items displayed in the current section, while available user modifications may be displayed in the advanced quick display menu. The division of menu items can be adjusted based on actual user operation after the user has used a particular assay tool multiple times.

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

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

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

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

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

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

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

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

[0307] The previously described example menu configurations provide a UI display of multiple menus in a hierarchical menu tree. Figures 2D-2M provide further examples of menu display configurations. The following menu display configurations can be used without limitation to each other or in any combination with the previously disclosed menu configurations. For example, selecting a specific menu item anywhere in the hierarchical menu tree can cause the processor to execute a command to switch the UI display to any menu configuration described in this specification. In particular, a specific menu display configuration can be combined with a specific menu selection.

[0308] Figure 2D shows another example of a menu display configuration in one embodiment. Figure 2D schematically illustrates a two-wheel configuration, where the first wheel option has sub-options in a second wheel. For example, selecting an option in the first wheel with options will display in the second wheel, and these sub-options are combined with the selected option. In one embodiment, a first portion 214 of the display may initially display the first wheel, and as an option is selected from the first wheel, the first wheel with options may be repositioned to the second portion 216 adjacent to the first portion. The first portion may then, for example, be parallel to display the second wheel with sub-options of the first option (in the same visual orientation, the first wheel is displayed parallel to the second wheel).

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

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

[0311] Figure 2E shows yet another example of a menu display configuration in one embodiment. In this display configuration, two scroll wheels are compressed into one scroll wheel. Scroll wheel options have sub-options represented in one scroll wheel related to the active scroll wheel option. In this configuration, the first and second parts of the display overlap, but all menu items can still be viewed (or viewed by displaying collapsed items, sliding, or rotating the item scroll wheel). For example, the second scroll wheel of an option can be displayed within the first scroll wheel. The first scroll wheel of an option can be rotated in one direction (e.g., vertically up and down), while the second scroll wheel of an option can be rotated in another direction (e.g., horizontal, left, and right). The selected path can also be viewed in the second part. For example, selecting "Sub-option 2" displayed in the display moves the selected option below "First Scroll Wheel Option 1".

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

[0313] In one embodiment, the second portion of the display can show up to a critical number of menu layers, for example, different visualization configurations can be used to display past menu layers to prevent the second portion from becoming too large.

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

[0315] In another version, a search function for the scroll wheel is available. Search keywords allow the user to filter the scroll wheel options available. The search function is helpful for handling long or multi-option scroll wheels, which may require a long navigation time.

[0316] Figures 2H-2J show an example of a first and second portion displayed as a series of concentric circles in one embodiment. Referring to Figure 2H, a dial 220 can be rotated clockwise or counterclockwise to view an option window 218, a menu item, or an item to be selected. Clicking an area of ​​the dial (e.g., a circle) 220 selects an option. Selecting an option, for example, viewed via the option window 218, transforms the user interface into the configuration shown in Figure 2I. For example, in Figure 2I, the concentric dials expand outwards, displaying another concentric circle to represent another layer (e.g., a sub-layer) of a menu item or path. Sub-options can be viewed via an option window 222 (also referred to as a dial) on the circle 224 by rotating the dial 224 clockwise or counterclockwise. Options within that layer (displayed as sub-option "n") 222 (i.e., non-overlapping inner circles or dials 220) can be selected by clicking an area of ​​the circle 224. In another embodiment, selecting an option from a dial or circular menu user interface (e.g., as shown in FIG2H) can transform the user interface state to the configuration shown in FIG2J. For example, the next layer of option selection expands from the selected option, expanding the dial to display another internal dial 224 with an option window 222. In one embodiment, the number of options that can be viewed on the option window (e.g., 218 and 222) is unlimited, thus allowing an unlimited number of options suitable for the application to be displayed and selected.

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

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

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

[0320] Figure 2K shows a tree type for menu levels in one embodiment.

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

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

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

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

[0325] Referring to Figure 2M, the first menu item 252 is displayed at the center of the scroll wheel (or slide shaft) 250. A bright display format (e.g., larger font, different font color, etc.) can be used to display the menu item displayed at the center. A blank sample appears before the first menu item (e.g., above the center of the scroll wheel displaying the first menu item). The next menu item (e.g., 254, 256) appears adjacent to the first menu item (e.g., below). Scrolling the scroll wheel (e.g., in a straight direction) displays other menu items, for example, as shown in Figure 2N. For example, as shown in Figure 2N, the next menu item is displayed when the scroll wheel 250 scrolls upwards. Figure 2O shows the last menu item located at the center of the scroll wheel, where the previous menu item is adjacent to the last menu item (e.g., above). In this embodiment, the scroll wheel or slide shaft 250 does not rotate to display the first menu item after the last menu item 258. Instead, the scroll wheel stops rotating at the last menu item 258. A blank sample is displayed below the last menu item 258. Similarly, backward navigation (e.g., scrolling the wheel in the opposite direction) displays the previous menu item above the first menu item.

[0326] Although the example graphic wheel shown in Figures 2M-2O schematically illustrates a vertical scroll wheel, a horizontal scroll wheel will function in a similar manner. For example, a first menu item may appear in the center of the horizontal scroll wheel, while the next menu item appears horizontally adjacent to the first menu item (e.g., to the right of the center). In this example, scrolling the wheel to the left will display other menu items. When scrolling to the last menu item, the last menu item appears in the center, and after the last menu item (e.g., to the right of the last menu item) is a blank sample sample. In another configuration, the orientation of rotation can be reversed: for example, using a vertical scroll wheel, scrolling down (instead of scrolling up) guides from the first menu item to the last menu item; using a horizontal scroll wheel, scrolling to the right guides from the first menu item to the last menu item. The number of menu items (options) displayed on the scroll wheel at one time is configurable, for example, based on the screen size and / or screen area configured for the scroll wheel, and is not limited to the six items shown in Figure 2N.

[0327] The non-restrictive application of this user interface is selecting television (TV) channels to watch. Wider categories can be displayed in the top horizontal area, while smaller categories are displayed below, and paginated items can be displayed vertically, for example, on a vertical scroll wheel. For example, referring to Figure 2E, "Scroll Wheel Option 1" can represent a style, while "Sub-Option 1" can represent programs and / or movies arranged in a grid.

[0328] In one embodiment, the systematized user interface control system 1102 provides an interface to the user to perform processing. A treatment may include performing an experiment, performing one or more manufacturing operations, or any other procedure.

[0329] The various instructions for performing experiments conforming to the embodiments of this specification are described in detail below. The instructions to conduct the experiment can be used to manipulate, design, execute, audit, measure, analyze, store, and perform any other work regarding that experiment. The experiment may be, but is not limited to, one or more assays. The systematized user interface control system 1102 may merge and / or combine the assay system and provide commands to generate the MUI display 206 for the system. In response to the command, the MUI display 206 is capable of displaying or providing a visual presentation of the workflow and / or menu item paths used for the assay. The assay may include one or more electrochemiluminescence (ECL) assays.

[0330] The methods of this embodiment may be used in combination with a variety of assay devices and / or forms. The assay device may include, for example, assay modules, such as assay disks, cartridges, porous assay discs, reaction vessels, test tubes, photoanalysis tubes (Cuvette), flow cells, assay wafers, side flow devices, etc. having assay reagents (which may include a target agent or other binding reagents) added or preloaded in wells, chambers, or assay areas in the assay module as the assay proceeds. These devices may employ a variety of assay forms for specific binding assays, such as immunoassays or immunochromatography assays. The illustrative assay apparatus and form are described in this instruction manual below. In certain embodiments, the methods of this embodiment may employ assay reagents stored in a dry state, and the assay device / kit may more comprise or have desiccant material for the assay reagent to be kept in a dry state. Assay devices preloaded with assay reagents significantly improve speed and reduce the complexity of assay metrics while maintaining superior stability during storage. The dried assay reagent may be any assay reagent that can be dried and then reconstructed prior to use in the assay. These include, but are not limited to, binding reagents, enzymes, enzyme substrates, indicator dyes, and other reactive compounds that can be used to detect the analyte of interest that can be used for binding assays. Assay reagents may and may include substances that are not directly involved in the detection mechanism but play a helpful role in the assay, including, but not limited to, Blocking agents, stabilizers, detergents, salts, pH buffers, and preservatives. The reagent may be present in free form or supported on a solid phase comprising the surface of a compartment (e.g., a chamber, channel, flow chamber, hole, etc.) in the assay module, or the surface of a colloid, bead, or other particle carrier.

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

[0332] 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, polypropylene, and latex particles; materials commonly used in solid-phase synthesis, such as polystyrene and polyacrylamide particles; and materials commonly used in chromatography applications, such as silica, alumina, polyacrylamide, and polystyrene. These materials may also be fibers, such as carbon fibers. The particles may be inanimate biological entities; or they may include living biological entities, such as cells, viruses, and bacteria.

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

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

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

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

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

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

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

[0340] The example automated system is discussed and described in jointly owned international patent applications disclosed in WO 2018 / 017156 and WO 2017 / 015636 and international patent application disclosure WO 2016 / 164477, the entire contents of which are incorporated herein by reference.

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

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

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

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

[0345] An automated system may be configured to perform one or more of the following functions: (a) moving consumables (such as trays) into, out of, and within a detection subsystem; (b) moving consumables between other subsystems; (c) storing consumables; (d) sample and reagent handling (e.g., preparing reagent mixtures and / or introducing reagents into consumables); (e) consumable shaking (e.g., for mixing reagents and / or for increasing reaction rates); (f) consumable cleaning (e.g., cleaning trays and / or performing a determination cleaning step (e.g., well aspiration); and (g) measuring ECL in a flow chamber or consumable (such as tubes or trays). An automated system may be configured to handle individual tubes or well trays (such as 96- or 384-well trays) placed in a rack.

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

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

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

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

[0350] This invention includes a method for detecting and counting individual detection complexes. In embodiments, a surface includes a plurality of binding domains, and each analyte forms a complex in a different binding domain of the plurality of binding domains. In embodiments, the surface is a particle. In embodiments, the surface is a bead. In embodiments, the surface is a disc. In embodiments, the surface is a pore in a porous 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 one or more added analytes is on a separate surface, and said surface is a bead in a bead array. In embodiments, each binding domain of each analyte of one or more added analytes is on a single surface, and the binding domains form elements of a reagent array on the surface. In embodiments, the surface includes an electrode, and the detection 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.

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

[0352] The resolvable binding region can be optically queried in whole or in part; that is, each individual resolvable binding region can be optically queried individually and / or the entire surface including a plurality of resolvable binding regions can be imaged, and one or more pixels or groups of pixels in the image can be mapped to a single resolvable binding region. A resolvable binding region may also be a particle among a plurality of particles. Resolvable binding regions exhibiting variations in their optical markings can be identified using conventional optical detection systems. Depending on the type detected (e.g., type of fluorescent entity, etc.) and the operating wavelength, filters designed for a specific wavelength can be used for optical querying of the resolvable binding region. In embodiments using optical querying, the system may include more than one light source and / or a plurality of filters to adjust the wavelength and / or intensity of the light source. In some embodiments, a CCD camera is used to capture light signals from a plurality of resolvable binding regions. 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, as are well known to those skilled in the art. In some embodiments, a scanning mirror system coupled to a photodiode or photomultiplier tube (PMT) can be used for imaging.

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

[0354] In one particular embodiment, the method of the present invention can be used in multiple forms by binding a plurality of different analytes to a plurality of acquisition reagents for these analytes, fixing the acquired analytes to coded beads such that the code identifies the acquisition reagent (and analyte target) of a particular bead. The method may further include counting the number of beads with bound analytes (using the detection method described herein).

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

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

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

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

[0359] In embodiments, the crosslinking agent has one or more binding sites for supplementing the crosslinking agent, and the fixation of the acquisition and anchoring agents further includes: connecting the acquisition and anchoring agents to a target agent connected to the crosslinking agent via the supplementing crosslinking agent; and binding the product to a binding region containing a target agent complement, wherein (i) each binding region contains a different target agent complement; and (ii) each target agent complement selectively binds to one of the target agents. For example, in the case where the target agent is an oligonucleotide, the crosslinking agent is streptavidin, and the supplementing crosslinking agent is biotin, the biotin-labeled oligonucleotide may bind to a first of the four biotin-binding sites of streptavidin to form a target agent connected to the crosslinking agent. A biotin-labeled acquisition agent (i.e., an acquisition agent connected to the supplementing crosslinking agent) may then bind to the remaining biotin-binding sites on streptavidin to connect the target agent to the acquisition agent.

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

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

[0362] Exemplary disk readers include the MESO SECTOR S 600 (www.mesoscale.com / en / products_and_services / instrumentation / sector_s_600) and the MESO QUICKPLEX SQ 120 (www.mesoscale.com / en / products_and_services / instrumentation / quickplex_sq_120), both available from Scale Diagnostics, LLC. The disk readers are described in U.S. Patent No. 6,977,722 and U.S. Provisional Patent Application No. 62 / 874,828, entitled "Assay Apparatuses, Methods and Reagents" filed by Krivoy et al., July 16, 2019, Attorney General's Case No. MSD-011.PROV, the entire contents of which are incorporated herein by reference.

[0363] The aforementioned user interface methods can also be incorporated into the user interface of a measurement system. The measurement system described below allows users to perform measurements via a user interface. An example of a user interface incorporated into a measurement system used for decision-making is described below. The terms "system software" or "system" and their user interface, as used in describing the functionality of the measurement system below, refer to the software that implements the measurement system. The user interface can display or visualize the paths of workflows and / or menu items.

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

[0365] Advanced Context Menu - An option menu that depends on specific content (such as the current screen, sub-steps, and screen state).

[0366] Assay Method - The method of performing the assay, including but not limited to: 1. Instrument specifications to be performed and parameters used for the agreed-upon assay; 2. Test pan design; 3. Calibration titration criteria, such as dilution factor; 4. Control design; 5. Sample replication protocol.

[0367] Audit Log - A continuous record of automated and user-initiated events occurring in the system that may affect results. This record is used to track problems and ensure proper operation in a controlled environment. The audit log is permanent and immutable. The audit log includes a subset of information from the instrument logs.

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

[0369] Completed Run - An execution that has been aborted, marked as completed, or completed successfully.

[0370] CV - Coefficient of Variation.

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

[0372] ECL - Electrochemiluminescence. A proprietary format for detecting biologically significant molecules.

[0373] Existing Run - A planned, aborted, completed, or successfully completed run marked with a flag.

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

[0375] A test site can also be called a test point. Test site planning can refer to, for example, an array of test points within a single well of a test or measurement disc.

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

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

[0378] Instrument software - Software used to control instrument hardware.

[0379] LED - Light-emitting Diode. A light source.

[0380] Normal State (Instrument Software) - If the software executes normally without any errors or warnings, the instrument is considered to be in a normal state. Once the error state is resolved and / or the warning messages are acknowledged, the instrument will return to the normal state.

[0381] Run - Runs zero or more named samples and one or more assays, and tests the samples according to the information described in the assay.

[0382] Run Owner - The user who creates the execution.

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

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

[0385] Sample Layout - The location and ID of the samples on the tray.

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

[0387] Spot Layout - The location and name of the analyte in the orifice on the disk.

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

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

[0390] Unexpected Barcode – This barcode differs from the expected barcode. If the barcode is not read, the consumable item may also be considered to have an "unexpected barcode".

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

[0392] UI Warning Events - These are any noticeable messages that require a user response. Users should correct errors and / or acknowledge messages before continuing operation. For example, a UI warning event could be that the device is in a "not ready" state.

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

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

[0395] Figure 5 is a flowchart illustrating a method for displaying a startup user interface screen in one embodiment. This 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 the horizontal scroll wheel 502, while sub-menu items are displayed on the vertical scroll wheel 504. For example, the "Startup" option 506 (Figure 4) selected by the logged-in user is displayed on the horizontal scroll wheel 502. A second layer of options derived from the "Startup" option (406) is displayed on the vertical scroll wheel 504. In this example measurement method, the startup screen displays the initial software screen to the user. User-executable workflows are listed as options (sub-options) on the user-selectable vertical scroll wheel. In this measurement method example, less common and advanced workflows can be grouped under an advanced menu. In this example measurement method, the workflow options for the system include: creating a new run 508, where the user can create an execution from scratch or based on a previously defined run 512 when selecting "Create New Execution Workflow" 510; continuing a previously planned or started execution 514, where the software automatically resumes from the last step completed by the user in the run 516; and viewing the results of a completed execution 520, where the software allows the user to enter a viewing screen 524 when selecting "View Completed Execution" 522. After the user selects any option 504 from the vertical scroll wheel, the options on the vertical scroll wheel are added to a new horizontal scroll wheel at the top of the screen. This horizontal scroll wheel allows the user to change their selection. For example, after selecting "Create New File," the options for "Schedule" and "Complete" execution move to the horizontal scroll wheel, allowing the user to change their mind.

[0396] Figure 6 is a schematic diagram illustrating the workflow of the assay method definition screen in one embodiment. In this example, the software requires an assay method to process the sample under consideration. The "Define" option (Figures 5, 512) is executed to perform the processing shown on this screen. Assay method definition: assay on tray; tray layout; number of calibrators, number of controls, and maximum number of samples; diluents for controls, calibrators, and samples; number of repetitions for controls, calibrators, and samples; instrument specifications (incubation time, administration of blocking agents, and / or others). Each kit provides preset assay methods, and the system software allows users to create custom assay methods based on these preset values. In one embodiment, the assay methods are distributed in the Global Product Data (GPD) file. The GPD includes, for example: product barcode; assay; analyte placement in wells; kit batch identification, tray, antibody, calibrator, control; concentration measurements of the following: calibrator, control; instrument instructions on how to process the product; and recommended tray layout.

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

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

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

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

[0401] This system can also import data from a sample management system. When users choose to manually define samples, they can define the number of samples to be processed. The software will automatically assign sample IDs.

[0402] Figure 9 is a flowchart illustrating the workflow of the user interface for confirming execution definitions in one embodiment. Based on the selection of the "Confirm Execution Definition" option, a sub-menu item of the "Define" option, the "Confirm Execution Definition" option is displayed on a horizontal scroll wheel graphic element, for example, overlaid below its parent menu item "Define". After the user defines the execution in the previous steps, the system provides an execution summary for the user to review and confirm. The following information is displayed to the user: the number of samples being executed. The user can also select the number of samples to view the sample identifier (ID), the number of Mesoscale Diagnostics disks being executed, the disk layout, and the execution name. The system provides a default execution name and allows the user to change this name. Once the user confirms the execution, the system prompts the user whether to continue the execution or return to the "Startup Target".

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

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

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

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

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

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

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

[0410] Figure 17 is a flowchart illustrating the workflow of the user interface for executing / viewing options in one embodiment. In one embodiment, the system categorizes user-executable tasks into main workflows and advanced workflows. Main workflows are those that users routinely execute, optimized for simplified execution. Main workflows are displayed in the "Goals" and "Steps" sections. Advanced workflows are displayed in the advanced pop-up menu and represent workflows that are not typically executed or are not limited to the configuration manager. Users access the advanced pop-up menu by clicking [Mesoscale Diagnostics Globe]. Advanced pop-up menu items are contained in a vertical scroll wheel with three main groups: functions related to the current screen (text-related items that change with the active screen); modules that can be switched to; and functions applicable to all modules, such as software login and logout. In this screen, selected options and the advanced menu are displayed horizontally on the graphics wheel, while sub-options of the advanced menu are displayed vertically on the vertical graphics wheel.

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

[0412] Figures 58-64RR show further screenshot examples conforming to embodiments of this specification. Figures 58A-58HH are exemplary non-limiting embodiments of a reader module. Figures 59A-59T are exemplary non-limiting embodiments of an experimental module. Figures 60A-60I are exemplary non-limiting embodiments of a maintenance module. Figures 61A-61Q are exemplary non-limiting embodiments of an administrator console module. Figures 62A-P are exemplary non-limiting embodiments of typical screenshots applicable to multiple modules in this specification. Figure 63 is an exemplary non-limiting embodiment of an audit tracking module. Figures 64A-64RR are exemplary non-limiting embodiments of screenshots applicable to a measurement method module.

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

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

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

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

[0417] The following discussion provides other embodiments and implementations of the system proposed in this specification. The user interface system discussed above can be widely used in various applications, including manufacturing environments, testing environments, instrumentation environments, experimental environments, etc. In a series of embodiments, the user interface system discussed above can be used to provide a user interface for a comprehensive bioinstrument system, including software, hardware, testing equipment, and all other desired features. This comprehensive bioinstrument system is discussed below. In particular, the following discussion describes an embodiment of the system as a cloud-based platform. The embodiments discussed below, for example with respect to Figures 21-50, can also be implemented via alternative network hardware and software platforms.

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

[0419] The components shown may include, for example, computer implementation components implemented and / or performing, or coupled to one or more hardware processors. For example, one or more hardware processors may include components configured to perform the various functions described herein, such as programmable logic devices, microcontrollers, memory devices, and / or other hardware components. The processors and cloud-based processing systems disclosed in Figures 21-50 may be examples of processor (1110). Coupled memory devices may be configured to selectively store instructions executable by one or more hardware processors. The memory devices and cloud-based storage systems disclosed in Figures 21-50 may be examples of storage devices (1120). Examples of a processor may include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), a cloud-based processing unit, another suitable processing component or device, or one or more combinations thereof.

[0420] Figure 21 illustrates an embodiment of a cloud-based system that provides seamless integration with other systems, computers, and instruments, such as biological instruments, to support and optimize user analysis work (e.g., bioanalytical work). The boundaries of system 21100 surround or partially constitute other systems, computers, and instruments that form part of the analytical computing system 21100, wherein the operating system on each computer and / or instrument wholly or partially includes the analytical computing system 21100, which may include, for example, Windows™, UNIX, Linux, macOS™, iOS™, Android™, and / or any other commercial, open-source, and / or special-purpose operating system. An analytical user environment 21101 includes one or more servers, desktop computers, laptops, tablets, and / or mobile devices, one or more of which may be used in system 21100. One or more analytical user environments 21101 may use analytical system 21100. A support provider environment 21102 includes one or more servers, desktop computers, laptops, tablets, and / or mobile devices, one or more of which can be used in system 21100 to support instruments, consumables, and / or analyze software used by a user in the analysis user environment 21101. There may be one or more support provider environments 21102 using the analysis computing system 21100. A consumable provider environment 21103 includes one or more servers, desktop computers, laptops, tablets, and / or one or more mobile devices that can be used in the analysis computing system 21100 to provide consumables used by a user in the analysis user environment 21101, or in conjunction with instruments including instrument environment 21106. There may be one or more consumable provider environments 21103 using the analysis computing system 21100.

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

[0422] Figure 22 illustrates an embodiment of the cloud-based system shown in Figure 21, providing seamless integration with other systems, computers, and instruments to support and optimize user analysis work. The boundary of the analysis computing system 21100 includes other systems, computers, and instruments defined by all or part of the analysis computing system 21100. An analysis user environment 21101 includes one or more servers, desktop computers, laptops, tablets, and / or mobile devices, one or more of which can be used in the analysis computing system 21100. An administrator computer 22202 includes one or more computers whose software is stored / retrieved by the system administrator through services and data provided by the cloud platform 22223 to manage the system 21100 used by users in the analysis user environment 21101. An analysis user computer 22203 includes one or more computers whose software is available for use by users in the analysis user environment 21101 to perform analysis work through services and data storage / retrieval provided by the cloud platform 22223. Data integration computer 22204 includes one or more computers with software for integrating (e.g., bidirectional integration) other business systems 22224 in the user analysis environment 21101 with the analysis computing system 21100 that provides services and data storage / retrieval to the user analysis business system 22224 through a cloud platform 22223. The analysis user business system 22224 may be hosted internally, externally, and / or in a combination of internal and external environments within the analysis user environment 21101, and may include one or more computer systems with optional software, such as Laboratory Information System (LIS), data analysis applications, data visualization applications, data reporting applications, business productivity applications, associated and / or unassociated databases, file servers, and / or any other system, to provide data access of the analysis computing system 21100 to users who directly use the analysis computing system 21100, users who do not directly use the analysis computing system 21100, and / or one or more other computer systems with the business system 22224 that do not directly interface with the analysis computing system 21100.

[0423] The support provider environment 21102 is a support provider whose support is for users of the analysis computing system 21100, users of consumables from the consumables provider, and / or instruments in the instrument environment 21106, including one or more servers, desktop computers, laptops, tablets, and / or mobile devices, one or more of which can be used in the analysis computing system 21100 to support instruments, consumables, and / or software used by users in the analysis user environment 21101.

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

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

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

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

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

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

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

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

[0432] Figure 25 illustrates an embodiment of an analysis user using an analysis user computer 25502 to execute an analysis user APP software 25503, thereby performing analysis functions provided by the analysis computing system 21100 through services provided by the cloud platform 22223. As discussed in this specification, the analysis user APP software 25503 may employ a MUI as described above to facilitate user access to the provided functions. Therefore, an embodiment of a systematic user interface control system 1102 can be provided by combining the analysis user computer 25502 and the cloud platform 22223. The analysis user computer 25502 is executed or accessed through different applications 25503 installed on the analysis user computer 25502, or through an internet browser installed on the analysis user computer 25502, which uses the web page URLs provided by the cloud platform 22223. In this embodiment, the web page URLs are logically organized using application 25509, but are not limited to this organization. In one implementation, the first interaction between the analytics user and the cloud platform 22223 is via service link 25504 using the analytics user APP 25503, which requires login services, to verify 25505 with appropriate credentials. These credentials may include a unique username and password and / or other information (such as biometric identification), and may also include optional or required additional verification input, commonly referred to as two-factor authentication, previously used by the management infrastructure. The login service can retrieve the user's encrypted credentials from the system database 25507 via service link 25506 to verify whether the analytics user can access and use the analytics computing system 21100 via service link 25506 using login update data stored in the system database 25507, in order to track the use of the analytics computing system 21100. If a user forgets or does not know their password, the analysis user can also reset their password via service link 25504 through the analysis user APP 25503, and then verify 25505 using the password reset update data stored in the system database 25507 through service link 25506, in order to track and analyze the use of the computing system 21100. The analysis user can also construct additional verification inputs for verification 25505 through service link 25504 through the analysis user APP 25503, and retrieve and modify the configuration change update data stored in the system database 25507 through service link 25506, and modify their additional verification configuration input through service link 25506 in the system database 25507, in order to track and analyze the use of the computing system 21100.After logging in and verifying the user, the user can use the services provided by application 25509 through service link 25508 via the user analysis APP 25503 to perform the analysis functions provided by application 25509. These services use service link 25510 as needed to create, read, update and / or delete data stored in system database 25507, in order to track the use of the analysis computing system 21100. Finally, the analysis user can log out of the analysis computing system 21100 via service link 25504 and the analysis user APP 25503, thereby terminating the user's current use of the analysis computing system 21100. The user's login information is updated through the logout service of service link 25506 (authentication 25505) in the system database 25507, and the data stored in the system database 25507 is updated through service link 25506 to track the usage of the analysis computing system 21100.

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

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

[0435] Figure 28 illustrates an embodiment of a supporting data integration computer 28802 that executes a monitoring data integration application software 28803 to perform the monitoring data integration functions provided by the monitoring data integration function provided by the monitoring data integration system 21100, between the analysis computing system 21100 and a computing system that is selectively not part of the analysis computing system 21100, through services provided by the cloud platform 22223. As described in this specification, the monitoring data integration application software 28803 may employ the aforementioned MUI to facilitate user access to the provided functions. Therefore, an embodiment of a systematic user interface control system 1102 can be provided by combining the supporting data integration computer 28802 and the cloud platform 22223. Thus, the monitoring data integration application software is adapted to track, view, and / or monitor one or more features of the data integration functions described in this specification. In one implementation, the first interaction between the monitoring data integration app 28803 and the cloud platform 22223 is a request for login service via service link 28804 to authenticate using appropriate credentials configured by the administrator 28805. These credentials preferably include a unique username and password, and may also include optional or required additional authentication inputs, commonly referred to as two-factor authentication, which has been previously built and used by the administrator. The login service can retrieve the encrypted credentials of the monitoring data integration app 28803 from the system database 28807 via service link 28806 to verify whether the monitoring data integration app uses login update data stored in the system database 28807 via service link 28806 to access and use the analytics computing system 21100 to track the use of the analytics computing system 21100. After logging into the verification monitoring data integration APP 28803, the monitoring data integration APP 28803 can be used via service link 28808 to access the services provided by dashboard 28809 to perform the monitoring functions provided by dashboard 28809. These services also use service link 28810 to create and update data stored in system database 28807 as needed, in order to use service link 28810 to create, read, update, and / or delete data stored in system database 28807 to track and analyze the use of computing system 21100. Finally, the monitoring data integration APP 28803 can log out of the analysis and computing system 21100 it is using via service link 28804, and terminate the currently used analysis and computing system 21100 by using the logout service of verification 28805. It uses the logout update data stored in the system database 28807 via service link 28806 to update the monitoring data integration APP login information in the system database 28807 via service link 28806, so as to track the use of the analysis and computing system 21100.

[0436] Figure 29 illustrates an embodiment of a consumable information upload computer 29902, which executes a consumable information upload APP software 29903 to perform one of the consumable information upload functions provided by the analysis and computing system 21100, via services provided by the cloud platform 22223, between the analysis and computing system 21100 and (optionally) a computing system not part of the analysis and computing system 21100. As described in this specification, the consumable information upload APP software 29903 may employ the aforementioned MUI to facilitate user access to the provided functions. Therefore, an embodiment of this systematized user interface control system 1102 may be provided by a combination of the consumable information upload computer 29902 and the cloud platform 22223. In one implementation, the first interaction between the consumable information uploading application 29903 and the cloud platform 22223 is through a request for login service via service link 29904 to verify 29905 using appropriate credentials. These credentials are preferably constructed to include a unique username and password. The login service can retrieve the encrypted credentials of the consumable information uploading application 29903 from the system database 29907 via service link 29906 to verify whether the consumable information uploading application can access and use the analysis and computing system 21100 via service link 29906 using login update data stored in the system database 29907 to track the use of the analysis and computing system 21100. After logging in and verifying the consumable information upload APP 29903, the APP can use the information provided by upload 29909 through service link 29908 to perform the consumable information upload function provided by upload 29909. These services use service link 29910 as needed, and upload 29909 pushes the subsequent stored data of the relevant specific customer account to be stored in consumable content 29911 to one or more team databases 29913 of the relevant specific customer account, so as to transfer data through service link 29912. These services also use service link 29906 to create and update the data stored in system database 29907 to track and analyze the use of computing system 21100. Once the upload is complete, the Consumable Information Upload App 29903 can log out of the Analysis and Computing System 21100 via service link 29904, terminate the current use of the Analysis and Computing System 21100 using the logout service of verification 29905, and update the Consumable Information Upload App login information in the system database 29907 via service link 29906 to track the use of the Analysis and Computing System 21100.

[0437] Figure 30 illustrates an embodiment of an account information upload APP software 301003 executing an account information upload computer 301002, one of the account update functions provided by the analysis and computing system 21100, via a service provided by a cloud platform 22223, between the analysis and computing system 21100 and (optionally) a computing system not part of the analysis and computing system 21100. As described in this specification, the account information upload APP software 30103 may employ the aforementioned MUI to facilitate user access to the provided functions. Therefore, an embodiment of a systematic user interface control system 1102 can be provided by combining the account information upload computer 301002 and the cloud platform 22223. The account update function may include adding, modifying, and / or deleting information about one or more specific accounts, including, for example, username, password, permissions, and other attributes related to one or more individual or team accounts. In one implementation, the first interaction between the account information upload app 301003 and the cloud platform 22223 is a request for login service via service link 301004 to verify 301005 using appropriate constructed credentials. These credentials preferably include a unique username and password. The login service can retrieve the encrypted credentials of the account information upload app 301003 from the system database 301007 via service link 301006. The login update data stored in the system database 301007 via service link 301006 is used to verify whether the account information upload app can access and use the analytics computing system 21100 to track the use of the analytics computing system 21100. After logging in and verifying account information upload APP 301003, the APP can use the services provided by management 301009 through service link 301008 to perform the account information upload function provided by management 301009. These services use service link 301010 as needed to push information about creating or updating customer accounts to be stored in system database 301007, and also use service link 301010 to create and update the data stored in system database 301007 to track and analyze the use of computing system 21100. Once the upload is complete, the account information upload app 301003 can log out of the analytics system 21100 it is using via service link 301004, and terminate the currently used analytics system 21100 by using the logout service of verification 301005. It then uses the logout update data stored in the system database 301007 via service link 301006 to update the account information upload app login information in the system database 301007 via service link 301006, thereby tracking the use of the analytics system 21100.

[0438] Figure 31 illustrates an embodiment of an instrument information upload computer 311102, which executes an instrument information upload APP software 311103 to perform one of the instrument infor...

Claims

1. A method for guiding a single-layer hierarchical selection, the method comprising: Display one or more user-selectable menu items on a first part of the user interface (UI) display; In response to a user's selection of one of the user-selectable menu items, at least one processor provides a relocation command for relocating the one or more user-selectable menu items to a second portion of the UI display and removing them from the first portion, wherein the second portion displays one or more previously guided menu layers.

2. The method as described in claim 1, wherein the second part provides a visual representation of the following items: (1) the menu hierarchy previously visited by the user, and (2) future menu items that can be selected subsequently.

3. The method as described in claim 1, wherein, Multiple menu items in a single menu layer are adapted to be displayed linearly, and the one or more previously guided menu layers and subsequent menu layers are adapted to be displayed in a nested manner.

4. The method as described in claim 1, wherein the first portion is an existing portion of the UI display, which is adapted to be displayed consistently within the same area of ​​the UI display to optimize the user's focus when interacting with the UI display.

5. The method as described in claim 1, wherein the first portion includes two to five sub-sections displaying one or more user-selectable menu items, wherein the one or more user-selectable menu items in the two to five sub-sections are divided within the sub-sections, and the sub-sections are adapted to display the association between the one or more user-selectable menu items in each of the two to five sub-sections.

6. The method as described in claim 1, further comprising providing an advanced quick-display menu adapted to be displayed in response to a selection of an advanced selector by the at least one processor, wherein the first portion is adapted to display more than 50% of the available menu items from a current menu currently displayed in the first portion based on one or more of the following: (1) the available menu items most frequently selected by all users; (2) the available menu items most frequently selected by the current user; or (3) standard protocol options, wherein the advanced quick-display menu is adapted to display the remaining available items from the current menu.

7. The method as described in claim 1, wherein the at least one processor is adapted to receive input from one or more users, accounts, or teams, wherein the input is adapted to solve one or more problems sequentially or in parallel, and wherein each of the inputs is based on one or more of the following: (a) a module, (b) a problem or subproblem to be solved, (c) a device, (d) a physical location, (e) a tool, (f) an instrument, or (g) a device; and wherein the at least one processor is adapted to notify the one or more users, accounts, or teams of the results obtained from the one or more of the inputs.

8. The method as described in claim 1 further includes, in response to the user's selection, displaying a second menu to be displayed on the first portion of the UI display, the second menu being a submenu of the one or more user-selectable menu items in a hierarchical menu structure.

9. The method as described in claim 1, further comprising: A second command is provided by the at least one processor for displaying a guide item together with one or more user-selectable menu items in the second part of the UI display.

10. The method as described in claim 9, wherein, In response to the selection of this guide item, an option to return to the previously presented menu is provided within the menu hierarchy.

11. A system for guiding a tiered menu path, the tiered menu being adapted to output to a user interface (UI), the system comprising: At least one processor; A user input device; And a computer-readable storage medium configured to store a computer application, wherein the at least one processor is configured to execute a plurality of instructions of the computer application for: providing a first command by the at least one processor for displaying a first menu having one or more user-selectable menu items on a first portion of a user interface (UI) display; In response to a user's selection of a user-selectable menu item from the first menu, the at least one processor provides a relocation command for relocating the one or more user-selectable menu items of the first menu to a second portion of the UI display and removing them from the first portion, wherein the second portion is adapted to display one or more previously guided menu layers and subsequent menu layers to provide a visual representation of: (1) the menu hierarchy previously visited by the user, and (2) future menu items that can be selected subsequently.

12. The system as described in claim 11, wherein, Multiple menu items in a single menu layer are adapted to be displayed linearly, and the one or more previously guided menu layers and the subsequent menu layers are adapted to be displayed in a nested manner.

13. The system as described in claim 11, wherein the first portion is an existing portion of the UI display, adapted to be displayed consistently within the same area of ​​the UI display to optimize user focus when interacting with the UI display.

14. The system as claimed in claim 11, wherein the first portion includes two to five sub-sections displaying one or more user-selectable menu items, wherein the one or more user-selectable menu items in the two to five sub-sections are divided within the sub-sections, and the sub-sections are adapted to display the association between the one or more user-selectable menu items in each of the two to five sub-sections.

15. The system as claimed in claim 11, further comprising an advanced quick-display menu provided by the at least one processor, adapted to display in response to a selection of an advanced selector, wherein the first portion is adapted to display more than 50% of the available menu items from a current menu currently displayed in the first portion based on one or more of the following: (1) the available menu items most frequently selected by all users; (2) the available menu items most frequently selected by the current user; or (3) standard protocol options, wherein the advanced quick-display menu is adapted to display the remaining available items from the current menu.

16. The system of claim 1, wherein the at least one processor is adapted to receive input from one or more users, accounts, or teams, wherein the input is collectively adapted to solve one or more problems sequentially or in parallel, and wherein each of the inputs is based on one or more of the following: (a) a module, (b) a problem or subproblem to be solved, (c) a device, (d) a physical location, (e) a tool, (f) an instrument, or (g) a device; and wherein the at least one processor is adapted to notify the one or more users, accounts, or teams of the results obtained from the one or more of the inputs.

17. The system as described in claim 11 further includes, in response to the user's selection, a second command provided by the at least one processor for displaying a second menu to be shown on the first portion of the UI display, the second menu being a submenu of the first menu in the menu hierarchy.

18. The system as claimed in claim 11 further includes a second command provided by the at least one processor for displaying a guide item together with the one or more user-selectable menu items in the second portion of the UI display.

19. The system as described in claim 18, wherein, In response to the selection of this guide item, an option to return to the previously presented menu is provided within the menu hierarchy.

20. A non-transitory computer-readable medium storing computer instructions, which, when executed by at least one processor, causes the at least one processor to perform a method for guiding a path through a tiered menu layer, the tiered menu layer being adapted to output to a user interface (UI), the method comprising: The at least one processor provides a first command for displaying a first menu having one or more user-selectable menu items on a first portion of a user interface (UI) display; In response to a user's selection of a user-selectable menu item from the first menu, the at least one processor provides a relocation command for relocating the one or more user-selectable menu items of the first menu to a second portion of the UI display and removing them from the first portion, wherein the second portion is adapted to display one or more previously guided menu layers and subsequent menu layers to provide a visual representation of: (1) the menu hierarchy previously visited by the user, and (2) future menu items that can be selected subsequently.

Images