Graphical user interface system

Abstract

To provide a graphical user interface and a user interactive item displayed on the graphical user interface.SOLUTION: A method of interactively navigating a user through a path of menu options on a user interface may include displaying an ongoing menu of options in a first portion of a user interface display. The user interface allows drill-down of levels of menu options based on selecting of menu items from the ongoing menu of options and selecting of menu items from previous levels of menu options. A second portion of the user interface display presents previously selected and previously unselected menu items of the drill-down level. Previously unselected menu items appear as selectable options.SELECTED DRAWING: Figure 2B

Description

Technical Field

[0001] Cross - Reference to Related Applications This application claims the benefit of U.S. Patent Application No. 62 / 669,381, filed on Jul. 17, 2018, the entire content of which is incorporated herein by reference.

[0002] This application generally relates to computers and computer applications, and more specifically, to graphical user interfaces and display methods for displaying user - interactive items on a graphical user interface.

Background Art

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

[0004] Often, a computer system and / or an application utilizes a series of menus etc. presented to a user to receive input and execute its functions. When the user selects an option or chooses an alternative from a list of menu items, the computer system and / or the application can execute its functions based on the selected option and / or present another list of menu items (e.g., a list of sub-menu items that depends on the selected option). The computer system and / or the application can continue this process of executing the menu-driven function, for example, until the function is completed. In such a menu-driven system, the previously selected option (on which the ongoing function of the computer system and / or the application depends) is often not displayed on the user interface. Thus, for example, the path of the obtained menu items cannot be seen at the time during the progress of the computer system and / or the application process. Further, not only the selected path but also the options of the non-selected paths may not be displayed on the user interface. Thus, it may be desirable to improve the user interface.

[0005] Often, instrumentation devices (e.g., but not limited to, biometric measurements) used for analytical purposes are those used in a laboratory. As such, data generated by the instrumentation device is stored as a data file on a shared network drive for post - processing and import into other electronic systems, namely, a Laboratory Information Management System (LIMS). Typically, these integrations require extensive and time - consuming software development and integration to provide the generated data to the end - user. Typically, these data integrations are in a regulated environment (e.g., 21 CFR Part 11), which requires that the generated data be stored in such a way as to ensure that it cannot be changed by the end - user. Also, these integrations are provided to the end - user to support post - processing of the generated data for supplementary analysis, reporting, and sharing with other end - users, often referred to as collaborators. In addition, the use of the instrumentation device and the post - processing of the generated data are desirably executed under a controlled, uniform, unified, and traceable process within a set of closely collaborating end - users. This helps to create consistently correct supplementary analysis and reporting. To use the instrumentation device for generating data for supplementary analysis and reports, typically, the end - user has to combine consumables (e.g., but not limited to, biological consumables including reagents and analytes) having lot - specific information with the sample(s) under test to create a reaction that is measured to generate the generated data and use the lot - specific information used for supplementary analysis and report generation. To obtain these consumables, the end - user has to purchase the consumables from a provider(s), and the provider(s) has to not only ship the physical consumables to the end - user but also provide the lot - specific information of the shipped consumables so that the end - user can use the consumables on the instrumentation device and perform the desired post - processing. In addition to the normal use of the instrumentation device and related consumables, there are typically important support functions to ensure that the instrumentation device and / or related consumables are always functioning optimally for the customer.The level of workflow integration required to optimally perform collective and collaborative tasks related to the use of instrumentation devices by end-users is very high and complex. This requires a simple and easy-to-use user interface, and for the user, the entire analysis workflow is complex. Thus, an improved analytical computing system and user interface associated with and including the instrumentation device and related consumables may be desirable.

[0006] Additional fields other than instrumentation devices face similar difficulties as described above. For example, in various manufacturing settings, workflow integration, part tracking, consumable tracking, work-in-progress tracking, documentation of processes and part production, and all the problems described above regarding instrumentation devices are difficult. Furthermore, the present application provides solutions for areas of consumer needs for organization, prioritization, and workflow improvement, for example, in business, office, home, travel, and leisure situations. There are also examples other than the above, and the solutions disclosed in this specification are not limited to the solutions to the problems discussed above. SUMMARY OF THE INVENTION

[0007] A method and system can be provided for interactively navigating a user via a path of menu options on a user interface and guiding the user via a computer application. Such a method is automatically executed by at least one hardware processor. The method may include, in one embodiment, displaying an ongoing options menu in a first portion of the user interface display.

[0008] The method may also include enabling the user to drill down into levels of menu options based on the user selecting menu items from an in-progress options menu displayed in a first portion of the user interface display and selecting menu items from previous levels of menu options. The method may further include displaying, in a second portion of the user interface display, menu items that were previously selected at the drill-down level and menu items that were not previously selected, with the menu items that were not previously selected being displayed as selectable options. The method may also include enabling the user to jump to different paths of menu options by enabling the user to select menu items that were not previously selected from a previously navigated menu level displayed in the second portion of the user interface display. In one embodiment, the first portion and the second portion are simultaneously viewable on the user interface display.

[0009] In another embodiment, when guiding a user through a computer application, a method of interactively navigating the user through a path of menu options on a user interface may include displaying an in-progress options menu in a first portion of the user interface display. The method may also include enabling the user to drill down levels of menu options based on the user selecting menu items from the in-progress options menu displayed in the first portion of the user interface display and selecting menu items from previous levels of menu options. The method may further include displaying in a second portion of the user interface display menu items that were previously selected at the drill-down level and menu items that were not previously selected, with the menu items that were not previously selected being displayed as selectable options. In one embodiment, the first portion and the second portion are simultaneously viewable 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 the speed of presentation.

[0010] In yet another embodiment, when guiding a user through a computer application, a method of interactively navigating the user through a path of menu options on a user interface may include displaying an in-progress options menu in a first portion of the user interface display. The method may also include enabling the user to drill down levels of menu options based on the user selecting menu items from the in-progress options menu displayed in the first portion of the user interface display and selecting menu items from previous levels of menu options.

[0011] The method may further include displaying, in a second portion of the user interface display, menu items selected in the past at the drill-down level and menu items not selected in the past, and the menu items not selected in the past are displayed as selectable options. In one embodiment, the first portion and the second portion are simultaneously viewable on the user interface display. In one embodiment, at least the first portion includes a search function box, a sub-first region, and a sub-second region, and the first portion is scrollable as a whole and shows an ongoing selection menu. In one embodiment, in response to detecting an entry of a search term in the search function box, the first portion is divided into a sub-first region and a sub-second region that are individually scrollable.

[0012] In yet another embodiment, when guiding a user through a computer application, a method of interactively navigating a user through a menu selection path on a user interface may include displaying an ongoing selection menu in a first portion of the user interface display. The method may also include enabling the user to select a menu item from the ongoing selection menu displayed in the first portion of the user interface display and drill down to a level of the menu selection based on selecting menu items from previous levels of menu selections. The method may further include displaying, in a second portion of the user interface display, menu items selected in the past at the drill-down level and menu items not selected in the past, and the menu items not selected in the past are displayed as selectable options.

[0013] In one embodiment, the first portion and the second portion are viewable simultaneously on the user interface display. In one embodiment, an in-progress options menu is displayed as a graphical rotating wheel that rotates the options. In one embodiment, the graphical rotating wheel is rotatable from a first menu item of the in-progress options menu to a last menu item of the in-progress options menu, and the graphical rotating wheel is further rotatable from the last menu item to the first menu item, and the first menu item and the last menu item are not connected in the rotation of the graphical rotating wheel.

[0014] In yet another embodiment, a user interface system may be provided, which may include at least one hardware processor and a memory device operably coupled to the hardware processor. The hardware processor may be operable to obtain an in-progress options menu from the memory device and display the in-progress options menu on a first portion of the user interface display. The hardware processor may be further operable to enable the user to drill down into levels of menu options based on selecting menu items from the in-progress options menu displayed on the first portion of the user interface display and selecting menu items from previous levels of menu options. The hardware processor may be further operable to display on a second portion of the user interface display menu items selected in past drill-down levels and menu items not selected in the past, and the menu items not selected in the past are displayed as selectable options. The hardware processor may be further operable to enable the user to jump to different paths of menu options by enabling the user to select menu items not selected in the past from previously navigated menu levels displayed on the second portion of the user interface display. In one embodiment, the first portion and the second portion are viewable simultaneously on the user interface display.

[0015] In another embodiment, a method executed by at least one processor is provided for navigating a hierarchical menu level path adapted for output to a graphical user interface (GUI). The method includes providing, by the at least one processor, a first command for a first menu of user-selectable options to be displayed in a first portion of a user interface (UI) display, and in response to a user selection, providing, by the at least one processor, a second command for a second menu of user-selectable options to be displayed in the first portion of the UI display. The second menu is adapted to be displayed in a second portion of the UI display and includes one or more of the previously selected menu items and the non-previously selected menu items at the hierarchical menu level and is adapted to be viewed simultaneously with the first portion.

[0016] In another embodiment, a non-transitory computer-readable medium storing computer instructions is provided that, when executed by a processor, cause the processor to implement a method for navigating a hierarchical menu level path adapted for output to a graphical user interface (GUI). The method includes providing a first command for a first menu of user-selectable options to be displayed in a first portion of a user interface (UI) display, and in response to a user selection, providing a second command for a second menu of user-selectable options to be displayed in the first portion of the UI display. The second menu is adapted to be displayed in a second portion of the UI display and includes one or more of the previously selected menu items and the non-previously selected menu items at the hierarchical menu level and is adapted to be viewed simultaneously with the first portion.

[0017] In another embodiment, a system is provided for navigating a hierarchical menu level path adapted for output to 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, and the at least one processor is configured to execute instructions of the computer application. The at least one processor provides a first command for a first menu of user-selectable options to be displayed in a first portion of a user interface (UI) display, and in response to a user selection, provides a second command for a second menu of user-selectable options to be displayed in the first portion of the UI display. The second menu is adapted to be displayed in a second portion of the UI display and includes one or more of the previously selected menu items and the previously unselected menu items of the hierarchical menu level, and is adapted to be viewed simultaneously with the first portion.

[0018] A computer-readable storage medium storing a program of machine-executable instructions for performing one or more of the methods described herein may also be provided.

[0019] Additional features and the structure and operation of various embodiments are described in detail below with reference to the accompanying drawings.

Brief Description of the Drawings

[0020]

Figure 1

Figures 2A - 2O

Figure 2P

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33A

Figure 33B

Figure 34A

Figure 34B

Figure 35A

Figure 35B

Figure 35C

Figure 35D

Figure 35E

Figure 35F

Figure 36A

Figure 36B

Figure 36C

Figure 36D

Figure 37

Figure 38A

Figure 38B

Figure 38C

Figures 38D - 38H

Figure 38I

Figure 39A

Figures 39B - 39E

Figure 40

Figure 41

Figure 42A

Figure 42B

Figure 43A

Figure 43B

Figures 43C - 43H

Figure 44

Figure 45

Figure 46

Figure 47

Figure 48

Figure 49A

Figure 49AA

Figure 49B

Figure 50

Figure 51

Figure 52

Figure 53

Figure 54

Figure 55

Figure 56

Figure 57

Figures 58A - 58HH

Figures 59A - 59T

Figures 60A - 60I

Figures 61A - 61Q

Figures 62A - 62P

Figure 63

Figures 64A - 64PP

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

[0022] The improvement of the user interface discussed herein provides a practical application of technical solutions to problems in conventional user interfaces related to user inefficiencies, accuracy, reproducibility, and computing inefficiencies. The technical solutions provided herein improve each of these aspects through the use of the user interface methods and technologies of the present invention. In particular, the technical solutions provided by the user interface disclosed herein provide the user with a more efficient means of navigating menu systems for complex processes.

[0023] User interfaces for electronic devices implemented for interaction or communication between humans and computers often include a series of menus or similar selection options that a user selects (e.g., selects a series of options in a hierarchical manner) to cause a computer or similar device to perform a desired function. In some embodiments, depending on the type of application, the amount of information presented to the user or the number of menu options may be overwhelmingly large. By using a wide range of menu options, a user can try various options or navigate through various menu selection hierarchies before finding the correct series of options or the desired options. In some examples, only about 10% of the user interface selection options and function options available to the user are being used out of 100%. On the other hand, if all options are presented at 100%, it can be difficult for the user to determine where to navigate to find that 10% that is relevant to the user. Also, since the selected menu option affects the next options that are made under the path of the menu option, a user switching an option means that the user also navigates to a plurality of different paths led by that option. Such trial and error requires a certain amount of time and cost and becomes inefficient when scrolling and paging through the many various options that can occur during user interface navigation.

[0024] The systems, methods, and techniques of the present disclosure can provide a user interface that guides the user through option options selected via a user interface display or another presentation device and can reduce the time to find the correct selection. In this way, the number of attempts at incorrect selections is reduced, the time taken for user navigation is shortened, and the desired computing function or goal can be completed. In an aspect, the user interface of the present disclosure selectively presents the user with a limited number of options out of all available options in a particular manner, guides the user through those options, streamlines the operation, and enables the user to focus on reaching the desired computing function more efficiently. In another aspect, the user interface of the present disclosure enables the user to connect to the application more directly.

[0025] Embodiments and technical solutions provide a practical application of certain visual principles for assisting in the navigation of the menus and systems described herein. Such visual principles include minimizing visual content and maximizing background or void space to reduce visual clutter and highlight the area of interest. By providing a dark or otherwise uniform background and increasing the contrast between the content and the background, the user's attention can be drawn to the appropriate area.

[0026] Embodiments and technical solutions provide a practical application of certain design principles for assisting the user in navigating the menus and systems described herein. Design principles embodied herein include, for example, minimizing the number of menus and / or selections that the user needs to navigate at one time.

[0027] Further design principles include providing the user with new options at any time, while offering the option to easily revisit previously selected options. This principle may be implemented via a two-part display system. The active part may be configured to display the ongoing user options, and the history part is configured to display information related to previous options. Together, the active part and the history part may provide a "direct workflow mode". The active part presenting the ongoing user options may have a strict limit on the number of menu items displayed, e.g., 7, 5, 3 (or any other number), and other potential items from the same menu may be displayed elsewhere. The previously selected options (and the menus in which those selections were made) may be presented to the user in a nested or stack format. A nested series of previously navigated menus may be presented in the manner of Russian nested dolls (matryoshka), with each previously selected menu item being expanded in a displayed sub-menu. Also, the nested or stack-type previously selected menu items may provide a trail of the breadcrumb list, which shows the user the path taken to arrive at the ongoing menu. In certain embodiments, an indicator bar may be provided to draw the user's attention to previously selected menu items. For example, when previously selected menu items are arranged in a stack format, the use of the indicator bar may help to vertically align one or more menus and / or menu items. This is illustrated, for example, in FIG. 61D. In this example, the indicator bar (located under the "Add / Delete" item) helps to draw the user's attention and align the items "Management", "Legal Matters", and "Add / Delete". In certain embodiments, the indicator bar may be depicted to resemble a watch hand, as illustrated in FIG. 61D. Further, the indicator bar may include color-coded states (e.g., red indicating an error state, blue indicating a non-error state). In certain embodiments, the color-coded state may be depicted within a portion of the indicator bar by irradiating one or more colored pixels.In one example, the color-coded state may be provided within the central portion of the indicator bar as illustrated in FIG. 61D, although this state may also be displayed in other portions of the UI display.

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

[0029] The embodiments contemplated herein improve the user's productivity by providing improvements in efficiency and accuracy through enhancing some aspects of the user experience. The user interfaces described herein focus the user on the most likely use cases while minimizing distraction caused by less frequently used options. By so focusing, the user interfaces minimize visual distraction and keep the user focused on the most relevant menu choices. The user interfaces described herein are aimed at guiding the user interface from one step to the next while eliminating the problem of the user wondering what to do next. In the embodiments herein, the user's navigation path through the interface system remains transparent to the user to facilitate selection of alternative options or backing out of an ongoing menu. Throughout the process of using the user interface, the user may have the option of browsing alternative paths through the process unobtrusively. Thus, the core function of the user interface software provided herein is to increase the total amount of relevant information presented to the user at any one time while decreasing the total amount of information presented to the user at once. Additional information and options for less frequent use cases remain available in an unobtrusive presentation style. Such decisions regarding what information should be presented to the user via the user interface at any given time may be pre-directed through a given menu workflow and / or be influenced and updated through analysis of previous user actions and choices.

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

[0031] Further embodiments contemplated herein relate to the integration of various process workflow aspects. As contemplated herein, "process workflow" is obtained in relation to any workflow that may involve instrumentation device (including biometric measurement) test workflows, manufacturing workflows, analysis workflows, and / or one or more devices at least partially controlled by one or more computing systems. In additional embodiments, a process workflow consistent with the embodiments contemplated herein may include the use of one or more consumables.

[0032] A computing system that conforms to the user interface and process workflow management system considered in this specification may include a single computing device system, a desktop computing system, a laptop computing system, a tablet computing system, a mobile device computing system, a thin client computing system, a cloud-based computing system, a server computing system, a multiple device computing system, a device / printer system, a device / server computing system, a system including multiple devices and servers (s), or any other suitable computing system, and may include various architectures including, but not limited to, these.

[0033] The process interface system described in this specification plays a role in improving user accuracy, efficiency, and satisfaction by providing a user interface, and the user interface is used faster, reducing the time to find the correct menu item, reducing the selection of incorrect menu items, and shortening the overall workflow time. Compared with a conventional system that can provide immediate access to 100% of the options (only 10% of which are frequently used), the system described in this specification can provide immediate access only to the functions that are frequently used (for example, in usage examples of 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 95% or more, 70-95% or more, 80-95% or more). The solution provided herein then helps to improve computing efficiency, reduce memory usage, and reduce the usage rates of CPU, hard drive, power, and communication resources.

[0034] The user interface systems contemplated herein may be provided in the form of a graphical user interface (GUI), a text-based user interface system, a virtual, augmented, or mixed reality (VAMR) interface system, a projection-based system, a gesture control system, and / or any other type of visual user interface. Collectively, user interface systems consistent with embodiments herein may be referred to as a “systematic user interface” (MUI). The MUI may include a graphical user interface (GUI), a text-based user interface system, a virtual, augmented, or mixed reality (VAMR) interface system, a projection-based system, a gesture control system, and / or any other type of visual user interface. Some of the principles contemplated herein are specifically contemplated with respect to, for example, GUIs, but are not intended to be limiting, and the principles contemplated herein may apply equally to other interface systems.

[0035] The MUI described herein refers to a “display,” an “interface,” and a “user interface.” As used herein, the terms “display,” “interface,” and “user interface” refer to text, images, visual components, interactive elements, and any other visual aspect shown or presented on a screen, projection, or other visual display hardware, unless otherwise specified. Thus, it is understood that as used herein, “display” and “interface” may be provided via any type of visual display hardware, screen(s), and / or projector. For convenience, menus, interfaces, and other visual items are referred to herein as being viewed on or presented by the MUI. Such reference is understood to indicate that the MUI is visually presented via a hardware device as contemplated herein.

[0036] As described in more detail below, the user interface systems described herein may use various visual components to present menu items. For example, the visual components may include a vertical "wheel" or a horizontal wheel that rotates through various menu items. As described herein, the use of a "wheel" as a visual component refers to how prominent (highlighted) options and receded (non-highlighted) options are presented to the user. A wheel-type visual component can be understood as a virtual wheel with the rim facing the user and a plurality of menu items arranged on the rim of the virtual wheel. A wheel-type visual component may or may not include any visual indicator of the presence of the wheel. A wheel-type visual component may present prominent options to the user in a way that draws attention (i.e., on the part of the wheel "closest" to the user), and other receded options may be presented in a way that does not draw attention. Prominent menu items may be highlighted in different colors, presented in different fonts, presented in a larger font, or otherwise marked to draw visual attention. As the virtual wheel rotates, the ongoing prominent menu item rotates away from the user (either clockwise or counterclockwise), and the ongoing receded menu item becomes the new prominent option. In an embodiment, the receded menu item closest to the prominent menu item may be displayed to draw more attention than a menu item that is further receded from the prominent menu item. For example, the menu items may decrease in size or brightness based on their distance from the ongoing prominent menu item. As the "wheel" "rotates", the receded menu items may become dimmed in view. In this format, the virtual wheel provides the user with the perception and feeling that all the menu items are arranged on an actual wheel. The visual components may further include a horizontal slider or a vertical slider that slides through various menu items. Similarly, as discussed above, for the wheel, a slider may be used to provide prominent menu items, or receded or non-prominent menu items.In an embodiment, the slider may differ from the wheel in that the back menu item does not appear to be dimmed from view as the option within the slider slides past. Further embodiments of the wheel and slider are further considered herein with respect to particular embodiments.

[0037] As discussed herein, menu items can be variously "selected", "highlighted", and / or "clicked". As used herein, to "highlight" a menu item means that the "highlighted" option is prominently displayed to the user, for example, as the prominent menu item at the center of the wheel. "Highlighting" may include changing the color, size, font, etc. of the menu item to visually emphasize the menu item to the user. "Unhighlighting" a user option may include changing the color, size, font, etc. of the menu item to make the menu item less visually prominent to the user. Menu items may be highlighted or unhighlighted in response to a user action (such as via clicking a mouse, touching a touch screen, rotating a wheel, etc.) (such as by presenting a menu item that the user cannot select or edit), and / or based on an action of the interface (such as by presenting a highlighted default option).

[0038] As used herein, to "select" a menu item means that the menu item is selected by the user and the user interface has advanced one or more menu steps according to the selection. Selecting a menu item causes the computer system to not only simply "highlight" the menu item, but also execute computer instructions to advance the menu. For example, selecting a menu item may cause a new menu to be displayed based on the selection. The selected menu item may be highlighted after selection, but highlighting a menu item does not necessarily include selecting the menu item.

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

[0040] In some embodiments of the systems according to this specification, a menu item may be selected through clicking. When a menu item is clicked, the system may proceed to the next series of menu items. In other aspects of the disclosed systems, clicking on a menu item serves to highlight the menu item, but does not select the menu item and advance the system to the next menu item.

[0041] A menu item may be described herein as "selectable". A "selectable" menu item refers to a menu item with which a user can interact by either selecting or highlighting the menu item. A selectable menu item may be displayed in a way that indicates it can be selected through changes such as coloring, highlighting, font, etc. A menu item may be described herein as "non-selectable". A "non-selectable" menu item refers to a menu item with which the current user cannot interact through selection or highlighting. A non-selectable menu item may be displayed in a way that indicates it cannot be selected through changes such as coloring, highlighting, font, etc.

[0042] Menu items may also be described as "previously selected" and "not previously selected". "Previously selected" menu items refer to menu items selected to reach the current menu interface display. It is not necessary for "previously selected" menu items to be actively selected by the user. If the system, by programmed default, brings the user to a menu level below the top level, menu items or options within the current path may be shown as "previously selected" even if the user has not actively selected them during the current session. "Not previously selected" menu items refer to menu items not selected to reach the current menu interface display. For example, if the user has selected a first menu item and not selected a second menu item, the system may proceed to display subsequent menus or submenus in response to the selection of the first menu item in the active portion of the MUI. In the history portion of the MUI, the system may display the first menu item as a previously selected menu item and the second menu item as a not previously selected menu item. Not previously selected menu items may be shown as selectable.

[0043] For example, the user may scroll a slider or turn a wheel through various menu items. The user can adjust the wheel or slider so that a particular menu item is highlighted. In an embodiment, a particular menu item may require “selecting” a further user interaction (e.g., a single or double click), whereby the MUI presents a new set of menu items or sub-menu items in response to the selection. In such an embodiment, the user rotates the wheel or scrolls the slider to move the desired menu item to the highlighted prominent menu item. Next, the user clicks, double-clicks, or otherwise indicates approval of the highlighted menu item as a selection to display the next menu or sub-menu. In an embodiment, a particular menu item may be “selected” simultaneously with it being highlighted. In such an embodiment, by rotating the wheel or scrolling the slider to move the desired menu item to the highlighted prominent menu position, the associated sub-menu is presented immediately when the desired menu item is highlighted.

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

[0045] The features of the interface embodiments may be referred to as the "first portion" and the "second portion". These terms refer to specific portions of the displayed user interface and need not be fixed to specific locations on the screen. As used herein, the "first portion" may also be referred to as the "active portion". The "first portion" or "active portion" represents the portion of the MUI that displays the current, or most recent, set of menu items. The "first portion" and "active portion" may be used interchangeably herein. The "second portion" may also be referred to as the "history portion". The "second portion" or "history portion" represents the portion of the interface that displays previously browsed menus as well as previously selected menu items, and menu items that were not previously selected. The "second portion" and "history portion" may be used interchangeably herein.

[0046] FIG. 1 shows a method for interactively navigating a user via a path of menu options on a user interface. The method can be automatically executed by at least one hardware processor. In this method, while drilling down additional option(s) based on an initial option, one or more past options made by the user are displayed together with other option(s) that were not selected, and by asking questions, the movement of the user through the system is facilitated. As used herein, "asking questions" refers to presenting the user with one or more menu options to select from. By this method, it becomes possible for the user to continue the path, jump to a different path, go back in time to the options made at one or more previous step(s), or return to the most recent point of the option selected by the user. In one embodiment, the user interface can present and display, on the same screen, whether past options or previous option(s) were selected or not, at each step of the path for example, regardless of where the user is on the path. For example, the user interface presents an overview of the user's menu option path including also menu item(s) not selected. By this user interface approach, more efficient navigation becomes possible, guiding the user along the path, allowing the user to confirm the path the user is taking, and allowing the user to deviate from the path set for the user to another path. By this user interface approach, the user can view the forward and backward breadcrumb trail(s), and can confirm where the user is going and where the user can go.

[0047] As discussed herein, the menu is presented as a series of hierarchical menu trees. Each level of the menu tree contains a plurality of menus that lead to other menus. Thus, for example, the first level of the menu tree contains a plurality of first menus, the second level of the menu tree contains a plurality of second menus, and the third level of the menu tree contains a plurality of third menus. This structure continues up to the execution menu level. In some discussions herein, the first menu is simply referred to as the menu, and subsequent menu layers within the tree are referred to as sub - sub - menus and the like. At this time, the plurality of layers of menus under the ongoing menu can be collectively referred to as sub - menus. Thus, the sub - menu of the first menu may include a plurality of second menus, a plurality of third menus, a plurality of fourth menus, a plurality of execution menus, and the like. An example of the hierarchical menu tree structure is shown in FIG. 2K. As used herein, with respect to the hierarchical menu tree, each level is referred to as a "menu" even if it does not present a literal menu to the user. For example, a "menu" may present only an "execute" button for implementing a process designed through other parts of the menu. Another "menu" may present, for example, a tutorial.

[0048] Each numbered menu contains a plurality of menu items or options, and each item or option refers to a new menu at a lower level. Thus, an item within the first menu can each refer to one of a plurality of second menus. In some embodiments, menu layers can be skipped. For example, an option of the first menu may refer to one of a plurality of third menus.

[0049] In an embodiment, each menu may also include additional information for display within the MUI. The additional menu information may provide user information regarding items within the menu and / or general context regarding the menu. For example, if the menu presents save file options to the user, additional information indicating the remaining disk space may be provided. In another example, if the menu presents options related to an assay to be launched to the user, additional information regarding available consumables related to the displayed assay may be provided.

[0050] At the execution menu level, i.e., the last level of a series of menus, the user can select an execution menu option or item. These options or items do not lead to further menus, but instead represent the selection of process parameters for the purpose of facilitating the menu tree. Selecting an execution menu option or item causes the system to execute a function related to the selected menu option or item. For example, when using an assay design menu tree, the execution menu options may include options such as file names, assay parameters, reagent options, etc.

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

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

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

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

[0055] As used herein, "displaying" a menu includes presenting one or more items within the menu within the MUI. It is not necessary to display all items or options within the menu to display the menu. Whether each menu item is displayed or not, the one or more menu items that make up the first menu remain the same. As discussed in more detail below, certain menu items may be excluded or restricted for various reasons. As discussed herein, the designated "first menu" or "second menu" may be repositioned to various parts of the screen. When repositioned, the first menu may continue to display the same set of first menu items and / or may display a different set of first menu items.

[0056] As discussed herein, the menus can also be referenced based on their temporal state. An "in-progress menu" refers to the menu that is currently active in the active portion of the MUI, from which the user is required to select an option. A "past menu" refers to the menu from which the user previously selected an option. The past menu may be displayed in the history portion of the MUI. A "subsequent menu" refers to the next menu that becomes active after the in-progress menu becomes a past menu. For example, a first menu may be displayed as the in-progress menu. After a selection is made from the first menu, the first menu may then be repositioned to become the past menu. Thereafter, a second menu selected from the first menu may be displayed as the in-progress menu. The in-progress menu may be displayed in the first or active portion of the user interface, and the past menu may be displayed in the second or history portion of the user interface.

[0057] In the history portion, each menu item of the past menu can be displayed linearly in the MUI. All menu items at that menu level are displayed in one row (horizontal or vertical). Each set of past menu items can be displayed linearly, while the overall menu can be displayed in a stack or nested format. This feature is shown in FIG. 2C, which shows, for example, linearly displayed MENU ITEMS and linearly displayed SUBMENU ITEMS. The relationship between the MENU ITEMS and the SUBMENU ITEMS is a stack or nested relationship. Thus, within a single menu level, the menu items are adapted to be displayed linearly, while the previously navigated menu levels and subsequent menu levels are adapted to be displayed in a nested format.

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

[0059] In one embodiment, the wheel and / or slider do not need to rotate completely, for example, they do not need to make a full turn or a full circle. For example, the wheel and / or slider rotate or slide from a start menu item to an end menu item and back from the end menu item to the start menu item. In this way, for example, the start and end of the menu are always displayed because they do not join or merge together. This technique can shorten the processing time because the wheel and / or slider can convey all the menu options (and be immediately understandable by the user) while clearly indicating which is the first menu item and which is the last menu item among the options presented by the wheel and / or slider.

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

[0061] In various embodiments, the terms "software protocol" and "computer instructions" are used to describe software instructions or computer code configured to perform various tasks and operations. The term "manager" as used herein broadly refers to a set of software instructions or code configured to cause one or more processors to perform one or more functional tasks. For convenience, the various managers, computer instructions, and software protocols are described as actually performing various operations or tasks when, in fact, the managers, computer instructions, and software protocols are implemented as firmware, software, hardware, or any combination thereof that programs a hardware processor to perform the operations and tasks. Although the "manager", "software protocol", and "computer instructions" used herein are described as "software" in various places, it is understood that these may also be implemented as firmware, software, hardware, or any combination thereof for instructing a computer or other electronic device to execute and / or perform a series of steps and / or instructions. Further, the embodiments herein are described from the perspective of method steps, functional steps, and other types of occurrences such as the display of menus and the selection of options. Although not explicitly stated in all examples, it will be understood that these actions occur in accordance with computer instructions or software protocols executed by one or more computer processors.

[0062] The functions of the managers and software protocols contemplated herein can be provided by the issuance of one or more commands. As contemplated herein, a "command" issued by a manager and software protocol refers to signals and instructions provided to various aspects of a computing system to cause various actions. A command may be issued from one manager to another manager and / or to other components of the system. For example, a manager may provide a command that causes the display of a particular visual component within a menu interface. Such a command may be directed to a physical display screen and may include the signals and instructions necessary to generate the visual component. As used herein, when a manager is described as performing an action or implementing a particular function, it should be understood that the manager issued a command that caused such action or function.

[0063] In various embodiments, the term "module" is used to refer to a particular set of software protocols and computer instructions that generate, maintain, and operate multiple components of the MUI described herein. One or more processors described herein may be configured to execute multiple software protocols to provide a systematic user interface module. As used herein, a "systematic user interface module" refers to any of a subset of modules that provide a particular user interface. For example, an administrative console module, an audit trail module, and a leader module are each provided as a particular systematic user interface module for performing tasks related to system administration, auditing, and plate reading, respectively. Each MUI module can be understood to include a hierarchical menu tree that includes at least a plurality of layered menus. Each module may further include preferred default visual components, preferred default exclusion and restriction lists, and other functions specific to the module. Other modules are considered in more detail below and throughout the present disclosure. Throughout the present disclosure, multiple aspects of various MUI modules are considered. The aspects considered for any particular MUI module are non-exclusive and non-limiting and may equally apply to any other MUI module. Accordingly, any MUI feature considered herein may apply broadly, either generally to the MUI or with respect to a particular module, and / or to any other particular MUI module considered herein.

[0064] Referring now to FIG. 56, a systematic user interface control system 1102 consistent with an embodiment of the present specification is shown. The systematic user interface control system 1102 includes one or more processors 1110 (for convenience, also referred to herein as a plurality of processors 1110, processors (plural) 1110, or processor 1110), one or more storage devices (plural) 1120, and / or other components. CPU 2 (see FIG. 19) and hardware processor 1804 (see FIG. 18) may be examples of processors 1110 configured as described herein. In other embodiments, the functions of the processor may be performed by hardware (e.g., through the use of application specific integrated circuits (“ASICs”), programmable gate arrays (“PGAs”), field programmable gate arrays (“FPGAs”), etc.) or any combination of hardware and software. The storage device 1120 includes any type of (one or more) non-transitory computer-readable storage media and / or non-transitory computer-readable storage devices. Such computer-readable storage media or devices may store computer-readable program instructions for causing the processor to implement one or more of the techniques described herein. Memory 4 (see FIG. 19) and memory device 1802 (see FIG. 18) may be examples of storage device 1120. Examples of computer-readable storage media or devices include, but are not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof, such as computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disk read only memory (CD-ROM), digital versatile disk (DVD), memory stick. In an embodiment, the storage device 1120 may include a plurality of storage devices 1120. The plurality of storage devices 1120 consistent with an embodiment of the present specification may be co-located and / or non-co-located.For example, one physical system may include a first memory storage device 1120, and a second physical system may include a second memory storage device 1120.

[0065] In an embodiment, the processor 1110 and the memory device 1120 may be implemented via a cloud computing platform or other forms of distributed computing. In such an implementation, the processor and the memory device may each include a plurality of processors and memory devices for performing the tasks and functions described herein.

[0066] The processor 1110 is programmed by one or more computer program instructions and / or software protocols referred to as "managers" stored in the memory device 1120. For example, the processor 1110 is programmed by a display manager 1050, an input manager 1052, a menu manager 1054, a user manager 1056, an exclusion manager 1058, a network manager 1060, and a data storage manager 1064. It will be understood that the functions of the various managers discussed herein are representative and not limiting. Further, the functions of the various managers may be combined, as needed, into one or more modules, applications, programs, services, tasks, scripts, libraries, applications, or executable code.

[0067] The managers discussed herein may, in various embodiments, be implemented to manage the MUI to complete various tasks that require a process workflow. Various software implementations of the MUI are described herein with respect to one or more specific embodiments, but the methods and functions provided by the aforementioned managers may be implemented to provide an MUI for any process workflow. The aforementioned managers may be functionally implemented through a software library.

[0068] The various components of the systematic user interface control system 1102 cooperate to operate so as to provide a systematic user interface display to the user via any type of display hardware including a screen, projection, touch screen, headset, and the like. In an embodiment, the systematic user interface control system 1102 implements one or more software protocols for interactively navigating the user via a path (s) of menu items, options, or choices within the MUI. The software manager described above may include a set of computer instructions, software libraries, dynamic link libraries, application program interfaces, function libraries, and other compilations of executable code. The systematic user interface control system 1102 may further include an appropriate graphics library, which includes the graphics required for the implementation and instantiation of the various visual components described herein. The manager can be customized for use in a particular implementation through the use of various data structures representing module information, including tables, linked lists, databases, b-trees, binary trees, heaps, stacks, queues, hash tables, red-black trees, binary heaps, Fibonacci heaps, and any other suitable data structure. Thus, the manager of the MUI can be provided as a customizable code library configured to interface with, interact with, and integrate differently with additional computer instructions and data structures for the purpose of providing MUI modules capable of performing specific tasks.

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

[0070] The input manager 1052 is a software protocol operating on the systematic user interface control system 1102. The input manager 1052 is configured to manage all inputs received by the systematic user interface control system 1102, including but not limited to user inputs and inputs from other systems. The input manager 1052 may be configured to issue commands to other managers of the systematic user interface control system 1102 according to the received inputs. User actions such as clicks and other screen interactions cause the input manager 1052 to receive a signal indicating the user interaction. The receipt of such a signal causes the appropriate manager of the systematic user interface control system 1102 to provide a command in response thereto, thereby causing one or more actions including MUI navigation, menu display, etc. For ease of explanation, such interactions and user inputs may be referred to as causing a particular response when an actual particular response is caused by the systematic user interface control system 1102 in response to the interaction or user input.

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

[0072] The user manager 1056 is a software protocol operating on the systematic user interface control system 1102. The user manager 1056 is configured to manage user access to the systematic user interface control system 1102. The user manager 1506 manages user authentication, including, for example, maintaining user authentication records, verifying user qualification information, and other necessary user authentication tasks.

[0073] 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 herein, menu items may be excluded or restricted based on various factors. The exclusion manager 1058 can be configured to issue commands to implement such exclusions and restrictions.

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

[0075] The data storage manager 1064 is a software protocol operating on the systematic user interface control system 1102. The data storage manager 1064 is configured to store, retrieve, archive, manipulate, and manage all data structures and data storage devices that the systematic user interface control system 1102 may have an interface to. The data storage manager 1064 is configured to issue commands to any of the various data storage devices discussed herein to manage the storage and retrieval of data.

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

[0077] The system user interface control system 1102 can present menu options between one or more hierarchical menu levels, and each menu level can include one or more menu items or options. The hierarchical menu levels described herein refer to multiple levels within the menu system. Selection of the first, topmost menu level causes navigation to a lower hierarchical level, i.e., a second menu, submenu, or sub-level. Selection within the second menu or submenu causes further navigation to a lower hierarchical level, i.e., a third menu or sub-submenu or sub-sub-level. The hierarchical menu structure can include any suitable number of levels. In some embodiments, selection at a level may cause navigation to levels 1, 2, 3, etc. levels below the current level.

[0078] Each menu can present options in the active portion of the interface. Menu options may be selectable and represent the options selected by the user. Selection of a menu option or option can trigger the display or presentation of subsequent submenus, which may include some menu options or unique submenu options. When the user selects a menu option that leads to a new menu, the menu items of the old menu can be moved from the active portion to the history portion of the interface. This enables the user to easily move to new menu options while retaining knowledge of previous menu options. These features are described in more detail below with respect to FIGS. 2A-2O, 3, and 57.

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

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

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

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

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

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

[0085] Referring to FIG. 1, in operation 102, an ongoing options menu (e.g., a list of menu items) may be displayed in a first portion of the user interface display. In operation 104, the user interface enables the user to drill down into the level(s) of menu options based on selecting a menu item from the ongoing options menu displayed in the first portion of the user interface display and selecting a menu item from the previous level of menu options. In operation 106, the previously selected menu item(s) and the non - previously selected menu items at the drilled - down level are displayed in a second portion of the user interface display. The non - previously selected menu items are displayed as selectable options. The previously selected menu item (or option) may also be displayed as a selectable option. In operation 108, the user interface enables the user to jump to a different path of menu options by enabling the user to select a non - previously selected menu item from the previously navigated menu level displayed in the second portion of the user interface display. The user interface displays both the first portion and the second portion such that they are viewable on the same screen of the user interface, e.g., viewable simultaneously.

[0086] In one embodiment, the first portion and the second portion are shifted to the substantial center of the first portion that displays the ongoing options menu on the user interface display while fitting both the first portion and the second portion on the user interface display. Thus, for example, the first portion and the second portion do not need to remain in a fixed position on the user interface display during navigation or drill - down (or drill - up) through different levels of menu options.

[0087] In one embodiment, in response to detecting a selection of a menu item from an ongoing options menu, the user interface display relocates the ongoing options menu to a second portion of the user interface display and displays the next level of menu selection options based on the selection of the menu item in a first portion of the user interface display. The relocated ongoing options menu is shown in the second portion of the user interface display and becomes the menu items that were previously selected and the menu items that were not previously selected at the past menu level. The next level of menu selection options is shown in the first portion as the ongoing options menu.

[0088] As described above, the options menu can be displayed as a rotatable graphical wheel that shows menu items (options or choices) where the menu items on the wheel can be shown when the wheel rotates. There is a similar graphical slider that can display the menu items of the slider when the slider is slid. The rotation or slide action can be performed in response to finger movement on a touch screen or input from a pointing device or another input device. In another aspect, the rotation or slide action can be automatically performed timely by the user interface (or the hardware that executes the user interface). In one embodiment, when the options menu is relocated from the first portion to the second portion, the rotation direction or slide direction may switch to a different orientation.

[0089] The ongoing options menu may be displayed in a first visual orientation on the first portion of the user interface display, and the drilled-down level of menu selection options including the menu items that were previously selected and the menu items that were not previously selected may be displayed in a second visual orientation on the second portion of the user interface display.

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

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

[0092] In one embodiment, the drilled-down level of the menu selection options repositioned in the second portion is displayed as a stack of menu levels.

[0093] In another embodiment, the first portion and the second portion 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 past menu levels may be displayed as circles outside or around the central circle. Each circle representing a menu level may include rotatable menu items (options or choices) such that a user can view all the options present on that menu level. Selecting a menu item from the ongoing selection menu causes the ongoing selection menu to be repositioned to the outer circle, and the next selection menu based on the selected menu item is displayed in the central circle. For example, the circle (e.g., a dial) may include a window(s) indicating the active option(s), and rotating the circle (e.g., the dial) causes other options within the window(s) to be displayed. Although the dial options may appear to be finite, the dial options may be infinite. For example, the dial continues to rotate until the last option (or the starting option when rotating backward) is displayed.

[0094] In another aspect, the window may display the selected option as an open light-up, with one (or more) options on the left and another one (or more) options on the right.

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

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

[0097] In one embodiment, when reaching the last level within the selected path at the menu level and, for example, when executing a function associated with the selected item within the last menu level, the user interface can return the ongoing menu view to another item within the upper level, for example, the first menu list. For example, the ongoing options menu may again become the first initial menu level and may be displayed in the first portion. In one embodiment, the first and second portions are not independent but are linked to each other, making navigation more efficient, guiding the user along the path, enabling the user to view the path being traversed, enabling deviation from the path set for the user to another path, for example, being able to view the forward and backward breadcrumb lists, knowing where the user has come from, and knowing where the user can go within the path of menu options. In one embodiment, the user interface can guide the user through efficient path options so that the user does not need to wander around the user interface trying to find the next appropriate path or action. Such efficient path guidance can save, for example, computer resources during central processing unit (CPU) cycles, and the memory usage spent on swapping and switching processor threads and memory elements within the computer that launches the user interface.

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

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

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

[0101] Although Figure 18 specifically refers to a GUI system, this is merely exemplary. It is understood that the methods and techniques described herein may be implemented via other MUIs such as text-based, virtual reality-based, augmented reality-based, mixed reality-based, and the like.

[0102] For example, a hardware processor 1804 coupled to a memory device 1802 and a display device 1806 can display an in - progress options menu in a first portion of the user interface display, enable a user to select menu items from the in - progress options menu displayed in the first portion of the user interface display, and drill down levels of menu options based on the user selecting menu items from previous levels of menu selections. The hardware processor 1804 can also be further operable to display in a second portion of the user interface display, menu items that were previously selected at the drill - down level and menu items that were not previously selected, and the menu items that were not previously selected can be displayed as selectable options. The hardware processor 1804 can also enable a user to jump to different paths of menu options by enabling the user to select menu items that were not previously selected from a previously navigated menu level displayed in the second portion of the user interface display.

[0103] For example, the hardware processor 1804 can execute the methods described with respect to FIGS. 1 and 3.

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

[0105] The GUI technology may be implemented on any type of computing device, such as a desktop computer, laptop computer, mobile device (e.g., Android or Apple IOS), tablet, and may use any type of interface, such as a mouse, touch screen, etc. The GUI technology may also be implemented on an instrument, such as an assay instrument for performing biological assays such as immunological assays or nucleic acid assays. In some embodiments, the instrument performs an electrochemiluminescence assay. In some embodiments, the instrument is an automated assay system including, for example, (a) a single robot-controlled 8-channel pipette, (b) a single robot-controlled assay plate gripper arm, (c) a single 96-channel channel assay plate washer, (d) a single plate reader, (e) one or more plate shakers having a total volume at at least 5 plate shaking positions, and (f) a processor adapted to execute an assay process for analyzing a plurality of samples in a 96-well plate. Other computing devices, machines, systems, and instruments include individual instruments such as wearable devices, automotive computing systems, assay-related instruments such as workflow assist instruments such as plate washers, plate readers, plate shakers, incubators, loading carts (e.g., described in International Patent Application Publication Nos. WO2018 / 017156 and WO2017 / 015636, the entire contents of which are incorporated herein by reference), medical instruments and machines such as MRI and CT machines, ultrasonic systems, consumer products such as household appliances, home management systems, air conditioning and heating systems, clothes washers and dryers, dishwashers, ovens, slow cookers, and other cooking devices, and home systems including these.

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

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

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

[0109] One or more central processing units (CPUs) 2 execute, for example, instructions stored in a memory 4 transferred to a register of the CPU 2. A bus 6 is, for example, electrical wiring that carries bits of data between components. The memory 4 may include an array of dynamic random access memory (DRAM) chips and may store programs and data used by the CPU 2 for execution. The system components may also include an input / output (I / O) controller and adapter connected to the CPU 2 and the memory 4 via a bus, such as an I / O bus, and connected to I / O devices. For example, a display / graphics adapter 8 connects a monitor 28 or another display device / terminal, a disk controller 10 connects a hard disk 24, for example, for permanent storage, a serial controller 12 such as a universal serial bus (USB) controller may connect input devices such as a keyboard 22 and a mouse 20, output devices such as a printer 26, and a network adapter 14 may connect the system to another network, such as another machine. The system may also include expansion slots for accommodating other devices for connecting to the system. For example, the hard disk 24 may store programs of instructions and data implementing the above-described methods and systems, where these methods and systems are loaded into the memory 4 and then loaded into the storage of the CPU (e.g., cache and registers) for execution by the CPU (e.g., ALU and / or other combinational circuits or logic). In another aspect, all or part of the programs of instructions and data implementing the above-described methods and systems may be accessed and / or executed via a network 18 by another computer system or device. FIG. 19 is only an example of a computer system. The computer system capable of implementing the techniques or systems of the present disclosure is not limited to the configuration shown in FIG. 19. Rather, another computer system may implement the techniques of the present disclosure and may include, for example, but not limited to, special processors such as field programmable gate arrays (FPGAs) and accelerators.

[0110] In one embodiment, the invention may be embodied as a computer program product that can include one or more computer-readable storage media and / or computer-readable storage devices. Such computer-readable storage media or devices may store computer-readable program instructions for causing a processor to perform one or more of the techniques described herein. In one embodiment, the computer-readable storage media or devices include tangible devices that can hold and store instructions for use by an instruction execution device. Examples of computer-readable storage media or devices include, but are not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof, such as computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disk read-only memory (CD-ROM), digital versatile disk (DVD), memory stick. A computer-readable medium can include both computer-readable storage media or computer-readable transmission media as described above, which can include, for example, coaxial cables, copper wire, and fiber optics. A computer-readable transmission medium may also take the form of acoustic or light waves, such as those generated in wireless frequencies, infrared, wireless, or radio waves, magnetic waves, or electromagnetic waves in other media.

[0111] The term "computer system" as used herein may include various combinations of fixed computer hardware and / or portable computer hardware, software, peripherals, mobiles, and storage devices. The computer system may include multiple individual components that are networked or otherwise linked to cooperate in execution, or may include one or more stand-alone components. The hardware and software components of the computer system of the present application may include fixed devices and portable devices such as desktops, laptops, and / or servers, and may be included within these devices. A module may be a component of a device, software, program, or system that implements some "function", and the "function" may be embodied as software, hardware, firmware, electronic circuits, etc.

[0112] The memory device 1120 exemplified by the memory 4 and the memory device 1802 may be implemented as one or more computer-readable storage media described herein and may be used to store various data and information regarding the computer system 100.

[0113] In one embodiment, the memory device 1120 can store registration information such as user identifiers and user account numbers. The registration information may be stored via data storage commands issued by the data storage manager 1064. In one embodiment, the registration information is stored in the memory device 1120. The registration information may be stored as one or more data structures. These data structures can include linked lists, b-trees, binary trees, heaps, stacks, queues, hash tables, red-black trees, binary heaps, Fibonacci heaps, and the like. In one example, the registration information may be stored in a registration table. The registration information includes at least a user identifier and an account number associated with the user. Since multiple users can be assigned the same account number, the system can track this using a shared account flag such as a semaphore, bit, etc. When multiple users are assigned the same account number, the shared account flag can be set to a first specific value. Otherwise, the shared account flag may be set to another specific value. Using the shared account flag is one way to track shared accounts, and this disclosure is not limited to this example. Other methods may be used. The shared account flag may be a column in the registration table. For each user identifier having the same account number, the shared account flag is set to a specific value and associated with the user identifier.

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

[0115] In other embodiments, the memory device 1120 can also store login history data. The login history data may be received via the input manager 1052, may be compiled via the user manager 1056, and may be stored via the data storage manager 1064. The login history data may include user identifier / account number and time / date information each time a user (or a different user) logs in to the system. The login history data can be maintained in the memory device 1120 for a predetermined period or an indefinite period. The predetermined period may be based on a specific application that is running or scheduled to run.

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

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

[0118] Commands issued or provided by the menu manager 1054 of the systematic user interface control system 1102 enable the user to move bidirectionally (backward and forward) between hierarchical menu levels, including enabling the user to view past or previous menu items that have or have not been selected. Moving backward moves to a higher hierarchical menu level, and moving forward moves to a lower hierarchical menu level. For example, various menu levels and / or options from one or more levels of a given path in the hierarchical menu can be viewed simultaneously on the MUI.

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

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

[0121] The display command can specify a scrolling method. For example, the display command may specify that the menu items are displayed on a graphical wheel that rotates the items in, for example, a horizontal or vertical (e.g., left - right or up - down direction) or another direction. In another embodiment, the display command may specify that the menu items are displayed as a graphical slider that slides the items in, for example, a horizontal or vertical direction (e.g., left - right, up - down direction) or another direction.

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

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

[0124] FIG. 3 is a flowchart showing details of a method of interactively displaying interactive items on a user interface display for computer - user interaction in another aspect, for example, a method by which vertical and horizontal switching of menu levels can be performed. The method can be automatically executed by at least one hardware processor. In operation 302, a list of menu items can be displayed in a first portion of the user interface display. The list of menu items is displayed in a first visual orientation on the first portion. For example, the first visual orientation may be a vertical orientation. The list of menu items may include one or more menu items from a first menu and may be displayed in response to a first display command provided by a display manager 1050.

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

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

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

[0128] In one embodiment, the first portion may include a decision-making zone. The decision-making zone may be located at a central position within the first portion. The decision-making zone may be a position within the first portion or the active portion where prominent menu items or highlighted menu items are displayed for immediate selection. For example, in FIG. 2A, MENU ITEM 4 is shown in the decision-making zone and is presented in a font size larger than the remaining menu items so as to be a prominent menu item or a highlighted menu item displayed for immediate selection. The first display command for causing the provision of the first menu may specify that the menu items displayed within the decision-making zone are highlighted or emphasized, for example, displayed in a font size larger than other menu items not within the decision-making zone. In other aspects, the menu item(s) displayed within the decision-making zone may be highlighted by being bolded, italicized, or using a color different from the background, or may be underlined.

[0129] In other embodiments, the first display command may specify, for example, that menu items displayed outside the decision-making zone, such as reduced display or faint display of menu items, are made less prominent relative to other menu items within the decision-making zone.

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

[0131] As shown in FIG. 2A, all of the first menu items 202 displayed in the first portion 204 are selectable. MENU ITEM 4 is displayed as a prominent menu item and is highlighted as being immediately selectable. As used herein, "immediately selectable" means that a single action by the user, such as a click, causes the selection of the menu item. MENU ITEM 4 is selectable and highlighted as a prominent menu, while the other MENU ITEMS (1, 2, 3, 5, and N) are not highlighted as back menu items. Back menu items are not immediately selectable. That is, two or more user actions are required for selection. When the user clicks on the highlighted immediately selectable menu item, it is selected. The other menu items may be highlighted so that they can be immediately selected by rotating the wheel or clicking. When the input manager 1052 receives a signal indicating a click on an immediately selectable menu item, the input manager 1052, which runs on the processor 1110, detects the selection of the prominent immediately selectable menu item. In response to the selection, the input manager 1052 issues a command indicating the selection to the menu manager 1054. The menu manager 1054 then determines the new menu layout to be displayed according to the selection and provides a rearrangement command to the display manager 1050 to cause a change in the MUI.

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

[0133] With a rearrangement command, the first menu of menu option 202 is rearranged from the first part 204 to the second part 208 of the MUI display 206. FIG. 2B shows the result of the rearrangement command. The rearrangement command may include the menu options of the first menu displayed in the second part 208, the size and orientation of the display, the visual components required for the display, instructions regarding which menu item was selected to cause the rearrangement, and any other information discussed herein regarding the display command. The rearranged first menu, which is displayed as a history part or the second part 208 as the past menu, may include one or more or all of the menu items 202 and the options that were previously available to the user. The menu item 202 selected by the user to cause the rearrangement becomes the menu item that was selected in the past, and the menu items not selected from the menu item 202 become the menu items that were not selected in the past. The menu items that were not selected in the past represent the hierarchical menu levels that were previously navigated. After the rearrangement of 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 new current or subsequent level menu options for the user to interact with in response to the first menu selection in the active part or the first part 204. As shown in FIG. 2B, the subsequent level or second level menu options include the second sub-menu items 210 displayed in the active part or the first part 204 of the MUI display 206.

[0134] In the method according to one embodiment, when the input manager 1052 receives a signal indicating that the menu item 202 has been selected from the first portion 204, a rearrangement command is issued. For example, the menu manager 1054 provides the rearrangement command to the display manager 1050. The rearrangement command instructs the display manager 1050 to move the first menu in the second menu from the first portion 204 of the MUI display 206 to the second portion 208 of the MUI display 206. The second portion 208 is at a position on the MUI display 206 different from that of the first portion 204. Since a menu item has been selected from the first menu of the menu item 202, the rearranged first menu of the menu item 202, as displayed in the second portion 208, will here have both the previously selected menu item(s) and the menu item(s) not previously selected (e.g., one or more menu items that the user could have selected but did not). The rearrangement command may include the first menu item, the scrolling method and / or orientation, the display size (and format), as well as the position of the second portion.

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

[0136] In one embodiment, the orientation in which the menu item 202 is displayed in the first menu within the second portion 208 is different from the orientation in which the sub-menu item 210 is displayed within the second menu within the first portion 204. For example, the orientation of the menu item 202 in the second portion 208 may be substantially orthogonal to the orientation of the sub-menu item 210 in the first portion 204. The rearrangement command may specify that the orientation of the menu item 202 is horizontal (the first display command may specify that the orientation of the menu item 202 is vertical). In other embodiments, the orientation may be reversed, where the menu item 210 in the first portion 204 is horizontal and the menu item 202 in the second portion 208 is vertical. In an embodiment, the first portion 204 is located at the lower center of the MUI display 206, and the second portion 208 is located at the upper part of the MUI display 206.

[0137] The rearrangement command can also specify different sizes for menu items. For example, the menu item(s) selected from the first menu (triggering the rearrangement) may be specified in an emphasized manner, such as being displayed in a larger font size than the unselected menu items. In other aspects, the selected menu item(s) may be highlighted by being bolded, italicized, or using a color different from the background, or may be underlined. In another aspect, the rearrangement command may also specify the relative position of the menu item 202 within the second portion 208. For example, the selected menu item(s) may be positioned at the central position within the second portion relative to other menu items (unselected menu items).

[0138] In other aspects, menu items not selected from the hierarchical menu level may be displayed in an unobtrusive manner. For example, the rearrangement command may specify that unselected menu items are in a smaller font size or are displayed in light type relative to the selected menu item. In other aspects, the rearrangement command may specify unselected menu items to be displayed further away from the central portion of the second portion than the selected menu item(s) for the same hierarchical menu level.

[0139] The first part and the second part can be displayed on the user interface display so that they do not overlap. The menu items rearranged to the second part are selectable from their position or location, and the selected menu item may be graphically highlighted, for example, to provide a visual indication of which item was selected from a list. The selected menu item may be centered with respect to other menu items to the left and / or right of the selected menu item. Sub-menu items that are displayed at the location where the rearranged menu item was displayed (before rearrangement) are also selectable items. FIG. 2B shows an example of a user interface display in an embodiment having a rearranged list of menu items. As shown, menu item 202 is rearranged, for example, to the second part 208 of the display 206 over the first part 204 and is displayed horizontally. As will be described in more detail below, the second part of the display may also include many levels of menu items, for example, levels of past decisions, and options for those levels that were not selected. Thus, the number of levels of past decisions may be, for example, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20 or more, for example, 1-2, 1-3, 1-4, 1-5, 1-6, 1-7, 1-8, 1-9, 1-10, 1-11, 1-12, 1-13, 1-14, 1-15, 1-16, 1-17, 1-18, 1-19, 1-20, and nested ranges therein, for example, 2-20, 2-19, 2-18, 3-20, 3-19, 3-18, etc. The second part visualizes, for example, the representation of the paths of past decisions made and other decisions not made (other paths). In one embodiment, the past decisions made (selected menu items) may be aligned vertically, for example, centered.

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

[0141] The second portion 208 may also include one or more decision zones. The rearrangement command can also specify that menu items displayed within the decision zone are highlighted or otherwise highlighted. In other embodiments, the menu item(s) displayed within the decision zone may be highlighted using bold, italics, or a color different from the background, or may be underlined. In other embodiments, the rearrangement command may specify the same. In other embodiments, the rearrangement command can specify that menu items displayed outside the decision zone are made unobtrusive or de-highlighted.

[0142] The MUI display 206 is displayed such that both the first portion 204 and the second portion 208 are viewable, for example, viewable simultaneously. The MUI display 206 may be presented via one or more physical display screens. The second portion 208 may include one or more menus, and each menu includes both previously selected menu items from a hierarchically navigated menu and menu items that have not been previously selected. In the representation shown in FIG. 2C, the second portion 208 (history portion) includes the menu item 202 and the submenu item 210, each of which was included in the first portion 204 in a previous MUI representation. The previously selected menu item 202 and submenu item 210 (i.e., the menu item such that the sub-submenu item 212 became displayed in the first portion) may be highlighted or emphasized to indicate that they were previously selected. As shown in FIG. 2C, MENU ITEM 4 and SUBMENU ITEM3 are highlighted to indicate that they were previously selected.

[0143] Menu and submenu items that have not been previously selected are displayed as selectable options. A previously selected menu item (or option) may also be displayed as a selectable option, where both are displayed on the second portion 208 (e.g., a history portion that may include one or more menu items previously available to the user). The history portion is in contrast to an active portion that may include in-progress user-selectable options at the in-progress hierarchical menu level (e.g., located in the first portion of the display). The history portion may, for example, also enable the user to make a selection by selecting between previously selected hierarchical levels and / or menus. In this way, the second portion 208 of the history may represent a "breadcrumb trail" that shows the user an ordered path of selections made to arrive at the in-progress menu so as to be displayed in the active first portion 204. Further details of selections made in the second portion 208 are provided below.

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

[0145] In other embodiments, commands (e.g., rearrangement commands, etc.) may be provided by the menu manager 1054 to move or relocate a menu from one part of the MUI display 206 to another part of the MUI display 206. In one embodiment, moving or relocating a menu and / or menu item(s) may include providing a command to move the menu from one part of the display to another. In another embodiment, moving or relocating a menu may include issuing a plurality of commands, e.g., one command to erase the menu from the first portion 204 of the display, and another command to display the menu on the second portion 208 of the display (either in the same format and / or orientation, or a different format and / or orientation). This rearrangement may be performed, for example, in response to a user selection from a menu (e.g., the first menu).

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

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

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

[0149] When a menu item is selected, for example, the level of the menu item may continue to increase or decrease by a process of repositioning the menu item from one part of the user interface display to another. For example, the processes at operations 308 and 310 in FIG. 3 may be repeated for additional levels of sub-menus. In another aspect, selecting a menu item from the repositioned list of menu items may function as a "back" button such that the user does not have to explicitly click a back button to return to the previous list of menu items. In yet another aspect, if the number of repositioned lists of stacked menu / sub-menu items reaches a predetermined number or threshold, for example, where the area of a second portion is too large and encroaches on the area of a first portion, the stack itself may be displayed as a rotating wheel or slider, for example, in a first visual orientation. Thus, for example, each menu item of the stacked list may be displayed in a second visual orientation (the items may be slidable horizontally, for example, in that direction), while each of the lists within the stacked list is slidable (vertically, for example) in the first visual orientation. In this way, a vertical pan list may be provided on a horizontal slider and contextualized by other options (selected items) to the left and / or right of the center. Any layer can be adjusted in real time, but there is no need to go back. Such a display of vertical and horizontal sliders enables navigating through an options tree and selecting a desired leaf option. In another aspect, the number of menu and / or sub-menu items may be collapsible and expandable. For example, the bottom or last "n" levels (e.g., 3 levels), which are the most recent levels, may be displayed with the remaining levels collapsed. These collapsed levels may be made expandable, for example, by user input. As another example, the top "m" levels (e.g., 2 levels) and the bottom level (e.g., "1" level) may be displayed, representing the context of the top level with the most recent option or decision (i.e., the bottom level) that the user is working on.

[0150] Figures 2A - 2C are shown with the first visual orientation vertical and the second visual orientation horizontal, but the orientations can be switched. For example, the first visual orientation may be horizontal and the second visual orientation may be vertical. In another aspect, the first visual orientation and the second visual orientation may be any other positional display orientation.

[0151] As described above, the menu items and associated sub - menu items may be displayed as slider graphical elements, rotating wheel graphical elements, or other graphical user interface elements. For example, as described below with respect to FIGS. 2H - 2J, concentric wheel elements may be used.

[0152] In an embodiment, the ordering or arrangement of the menu items within those menu levels can be determined according to the attributes of the menu items. The display style of the menu item may be selected based on whether the menu item is a previously selected item or a not - previously - selected item, whether the menu item is selectable or non - selectable, whether the menu item contains one or more characters entered by the user, whether the menu item is part of an advanced context menu (described in more detail below), and / or whether the menu item has a more central position within the list compared to other items in the list.

[0153] In an embodiment, the way in which menu items are adapted to be displayed (i.e., the ordering, placement, coloring, and presentation of the menu items) can be determined according to some different factors. For example, the menu manager 1054 and the display manager 1050, together, may be configured to highlight menu items that are selected or were previously selected, menu items that are currently available (i.e., selectable) to the user, and / or menu items that are positioned in the decision zones of the first portion 204 or the second portion 208. The menu manager 1054 and the display manager 1050 may be further configured to make non - selected or non - previously - selected menu items, menu items that are currently unavailable to the user, and / or menu items that are positioned away from the decision zones less prominent. In some embodiments, immediately - selectable menu items may be highlighted and non - immediately - selectable items may be made less prominent. In some embodiments, highlighting or making a menu item less prominent may include, as discussed herein, highlighting or not highlighting the menu item. Highlighting or emphasizing may include, for example, boldface, an increase in font size, a change in font, underlining, a change in brightness or contrast, or an adjustment of the position on the display relative to other items. To not highlight or make less prominent may include a decrease in font size, a change in font, lightface, a change in brightness or contrast, or an adjustment of the position on the display compared to other items.

[0154] The MUI enables the user to select menu items that were not previously selected from a previously navigated menu level displayed in the second part 208 of the MUI display 206, and to select newly displayed menu item(s) on the first menu that displayed the ongoing menu in the first part, thereby enabling the user to jump to different paths of menu items (e.g., by selecting one or more additional menu items at the same hierarchical level, a higher hierarchical level, or a lower hierarchical level of the menu). As discussed above with respect to FIG. 2C, previously navigated menu items (including sub-menu items, sub-sub-menu items, etc.) may be rearranged to the second part 208 after the menu item is selected.

[0155] Previously selected menu items in the second part 208 may be highlighted or emphasized to visually indicate the menu path taken to reach the menu or sub-menu currently displayed in the first part 204. Menu items not previously selected from the second part may be selected to enable the user to jump to that branch of the menu. In the example of FIG. 2C, the user has previously selected MENU ITEM 4 and SUBMENU ITEM3. Selecting a new and previously unselected sub-menu item 210 from the second part 208 causes the menu manager 1054 to issue a command for a new list of sub-sub-menu items 212 associated with the newly selected sub-menu item 210, which will be displayed as the ongoing menu in the first part 204. Selecting a new and previously unselected menu item from menu item 202 causes the menu manager 1054 to issue a command to display a new list of sub-menu items associated with the newly selected menu item 202 such that the ongoing menu is displayed in the first part 204. In this way, the user can actively jump between various parts of the menu tree without having to navigate past previous decisions.

[0156] When a menu item (or sub-menu item, or sub-sub-menu item, etc.) that has not been previously selected is selected, a save command may be issued to store the state of the in-progress menu in the first portion before the subsequent menu of the first portion is displayed. In embodiments, as disclosed in more detail below, by navigating to the final branch within the menu tree via a menu item at the executable menu level, the user can make one or more parameter selections. If the user navigates without going through the execution-level menu, the parameters currently selected when the user navigates without going through may be stored via a save command issued by the menu manager 1054 to the data storage manager 1064. Thus, if the user later desires to return to the execution-level menu, the last selected parameters are displayed.

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

[0158] In an embodiment, various menus are displayed on a background. In one embodiment, the menu is superimposed on the background. The background can be composed of one or more colors. In one embodiment, at least a pre-set percentage of the background pixels may be a single color. For example, at least a pre-set percentage of the background pixels may be black. For example, 75% of the background may be a single color (e.g., black, white, gray, etc.). The specific percentage is provided by way of example, and other percentages may be used.

[0159] In an embodiment, the display command and the rearrangement command may specify a background including a pre-set percentage and color, e.g., black, white, gray, etc. In a particular embodiment, the background may also include areas of the menu other than text (e.g., menu items). In one embodiment, the text of the menu is displayed in a color for contrasting or highlighting the text with the background. For example, if a black background is used, white or yellow may be used as the color of the text, but other colors may also be used. In other embodiments, the background and / or the text may be composed of two or more colors.

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

[0161] In one embodiment, any menu provided in any part of the MUI display may include a search function. Using the search function, a user can enter keywords or other inputs associated with menu items (options). The user input is received via the input manager 1052 and transferred to the menu manager 1054 for search purposes. By searching, functions (menu items) can be filtered using the entered keywords or other inputs, and the time required to find the desired menu item is reduced. The interface for the search function may be positioned at the center of each part of the MUI display 206 or, alternatively, at other parts of the MUI display 206. In a further embodiment, a visual interface for the search function is not provided. In such an embodiment, the user may access the search function simply by entering.

[0162] In one embodiment, any menu item(s) that match or partially match the keyword(s) may be displayed to highlight the menu item(s). For example, the menu item(s) may be displayed in a larger size than other menu items that do not match or partially match. In other embodiments, the menu item(s) may be highlighted using bold, italic, or a color different from the background, or may be underlined. In other embodiments, menu item(s) that do not match or partially match the keyword(s) may be made less prominent, for example, the text may be displayed in a reduced size or in a lighter font with respect to the text of the menu item(s) that match or partially match. In the embodiments of the present specification, a slider or wheel can be automatically advanced and / or rotated to display menu items that match the search term.

[0163] In one embodiment, the first menu selection may act as a filter on the second menu. In a hierarchical tree, each of some items of the first menu may lead to the same second menu. However, when the first menu selection is made, the menu items shown when the second menu is displayed are determined. In a simple example, the first menu may include menu items regarding team roles, and the second menu may include a menu regarding team responsibilities. Selection of a particular team role in the first menu can filter the second menu to show only the team responsibilities corresponding to the selected role. In some embodiments, such filtering is performed by making certain items of the second menu unselectable.

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

[0165] In one embodiment, one or more menus or menu levels may be presented as exceptions to the hierarchical menu tree standard discussed herein. For example, a menu level may include a visual display and / or a video display rather than a text-based visual component. The exception may be implemented, for example, in situations where information can be better communicated via alternative means. For example, as discussed above, the execution level menu may include a walkthrough, which may be optimally presented via a video or a series of images. In another example, the execution level menu may be presented for data analysis and may provide any combination of graphs, charts, tables, etc. to assist in data analysis.

[0166] In one embodiment, an advanced context menu may be provided via one or more commands issued by the menu manager 1054. FIG. 2P shows an example of a systematic user interface including an advanced context menu 270. The advanced context menu 270 is contrasted with a first portion and a second portion, both of which provide a "direct workflow mode". The advanced context menu 270 may, in an embodiment, be accessed via an advanced context menu selector 290 that may be present on some or all of the screens of the systematic user interface. The advanced context menu 270 provides additional advanced menu items 271 rather than items displayed in the active ongoing menu within the first portion 204 or one or more past menus displayed within the history second portion 208. The advanced context menu 270 may be accessed by clicking or mouse-overing the advanced context menu selector 290 or otherwise indicating a desire to access the advanced context menu 270. The advanced context menu 270 includes the selection of advanced menu items 271.

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

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

[0169] The advanced context menu 270 provides the user with a larger array of accessible menu items without causing clutter in the active or history portions. In an embodiment, some of the advanced menu items 271 of the advanced context menu 270 may be items that are generally not selected, for example, less than 50%, 45%, 40%, 35%, 30%, 25%, 20%, 15%, 10%, or 5% of the usage cases. The advanced menu items 271 of the advanced context menu 270 may be selected according to the pattern of user interaction with the MUI, as described in more detail below.

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

[0171] In embodiments, when the advanced context menu 270 is selected, the MUI dims and / or obscures other graphics, text, etc. The advanced context menu 270 is displayed on a transparent background so that the advanced context menu 270 and the rest of the background are the same (e.g., black). Thus, the MUI provides a dialog box adapted to appear in the foreground of the UI display to prompt the user for additional information or notify the user of an error. Here, the background of the dialog box is further adapted to match the backgrounds of the first and second portions of the UI display, and further, one or more of the text, graphics, photos, and videos displayed in the background of the first and second portions of the UI display are adapted to appear out of focus when the dialog box is displayed in the foreground of the UI display.

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

[0173] The exclusion information or restriction information can be used to exclude menu items from the view of a particular user, group of users, type of user, etc. For example, the administrative menu items or menu level may be excluded from the view of a user or operator who is an engineer or technician. In another example, the design menu items or menu level may be excluded from the view of a user or operator who is a lab assistant or lab technician.

[0174] The user identifier, account number, and menu item(s) and / or menu for exclusion can be input by an administrator. For example, the administrative console module, which is discussed in more detail below, may be used to manage and generate the exclusion table. The management can occur when the user registers with the system. In other embodiments, the exclusion information can be added after registration and updated periodically.

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

[0176] In certain embodiments, before issuing a command to display any menu, the menu manager 1054 can check an exclusion table (e.g., stored in the storage device 1120) to determine whether any menu items within the initial display menu (e.g., the default menu) are listed to be excluded from display for the user (or account number). In one embodiment, the menu manager 1054 can match the user identifier and / or account number of the currently logged-in user with the user identifiers and / or account numbers listed in the exclusion table. If there is a match, the menu items listed in the exclusion table are excluded from being displayed in the initial display menu. This exclusion may be performed through the issuance of a separate exclusion command and / or instruction, or alternatively, the exclusion may be done by modifying any display command that causes available menu item(s) to be displayed. The menu manager 1054 may erase the menu items included in the list from the menu items of the initial display menu (e.g., the default menu) and issue a first command that does not include the erased menu items.

[0177] In certain embodiments, each time the input manager 1052 receives a selection of a menu item within the active menu before issuing a rearrangement command, the menu manager 1054 may determine whether the menu items at a hierarchical menu level lower than the hierarchical menu level currently being displayed by the MUI display 206 are listed such that they are excluded (or whether the lower hierarchical menu is excluded) as the active menu. Login history data and an exclusion table may be used for such determination. The login history data may be used to confirm that the same user (user identifier or account number) is still logged in and may be matched with the user identifiers and account numbers within the exclusion table. In other embodiments, the user identifier and the account number received from the user manager 1056 may be used by the menu manager 1054 instead of the login history data for the determination. In other embodiments, a similar determination is made before issuing any rearrangement command or display command.

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

[0179] As described above, an account number may be associated with multiple users (user identifiers). Thus, when using the account number as a criterion for exclusion, all users associated with the account number may have the menu items displayed on the MUI display 206 excluded.

[0180] In another embodiment, since a specific account number can be linked, when the account number is used, any menu items linked to the account number can also be excluded.

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

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

[0183] The exclusion information or restriction information may be stored in the storage device 1120 as a data structure, for example. Each device may have an identifier such as a media access control (MAC) address or other unique identifier. The identifier of the device is not limited to the MAC address, and other identifiers such as an Internet protocol (IP) address or a machine name may be used. In one embodiment, one column in the table may include an identifier, for example, a MAC address. The second column of the table may include the menu item(s) or hierarchical menu level(s) to be excluded from the display, respectively, associated with the identifier (e.g., MAC address).

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

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

[0186] In certain embodiments, when receiving login history data or in response to receiving a notification, before issuing any command to display any menu (and menu item), the hardware processor executing the input manager 1052 checks the exclusion information in the storage device 1120 to determine whether any menu item of the initial display menu or a menu item associated with a selection is excluded for the device(s).

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

[0188] In other embodiments, certain menu items (or hierarchical menu levels) may be excluded based on which hierarchical menu level is currently being displayed as the in-progress menu (of the first portion) or the previous menu (of the second portion). In one embodiment, one column in the exclusion table may include menu identifiers for hierarchical menu levels. A second column in the table may include the menu item(s) or hierarchical menu level(s) to be excluded from display, respectively, associated with the menu identifier.

[0189] The menu identifier represents a hierarchical menu level that can be displayed in either the first menu or the second menu. An excluded menu item is a menu item that cannot be selected from the displayed hierarchical menu level. These menu items can be application-specific menu items. In certain embodiments, a hierarchical menu is displayed as the in-progress menu in the first portion 204 or the previous menu in the second portion 208, and when a selection is made, before issuing a command, the menu manager 1054 checks the exclusion information to determine whether any menu items associated with the hierarchical menu level selected for display should be excluded. Based on this determination, the menu manager 1054 may erase the excluded menu items from the menu before issuing a response command and then issue the response command with the menu items erased. This exclusion may be performed through the issuance of a separate exclusion command and / or instruction, or alternatively, the exclusion may be done by modifying the first, second, and / or third display commands that provide the available menu item(s) to be displayed.

[0190] In other embodiments, instead of issuing a display or rearrangement command with the menu item deleted, the exclusion command may be issued by the exclusion manager 1058 in combination with the display or rearrangement command. In this embodiment, the display command has all the menu items associated with the menu, and the exclusion command causes the display manager 1050 to delete the executed menu items included in the exclusion command before causing the display.

[0191] In other embodiments, the number of menu items to be displayed may be restricted by the menu manager 1054 based on usage frequency. For example, in one embodiment, the number of menu items may be restricted based on selection frequency. In a particular embodiment, the frequency may be determined over a predetermined period. The selection frequency can be preset or customizable and may include, for example, frequencies of 50% to 80%, although other selection frequencies are equally contemplated. By restricting the display of menu items to only those that are used above a particular threshold frequency, clutter within the menu system is reduced and the menu experience is rationalized.

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

[0193] In a particular embodiment, the selections of one or more users can be tracked over a preset period. The period may be one day, one week, one month, or other preset or customizable period. The particular period may be based on applications such as the type of clinical trial or study, type of test, type of organization (e.g., university, enterprise). The tracking may be repeated every preset period.

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

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

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

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

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

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

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

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

[0202] The above frequency can be used in conjunction with a restriction command issued by the menu manager 1054. The function of the restriction command is similar to that of the exclusion command, as discussed above. The restriction command serves to restrict specific menu items that are displayed based on one criterion or two or more criteria. For example, the restriction command can be based on the following: (a) the frequency with which an item was previously selected while the user was logged into an account. In one example, this determination can occur based on a given period. In another example, the determination can be based on the number of times a given user logs into their account. Other criteria include the following: (b) the frequency with which an item was previously selected while at least two users were logged into an account. In a particular embodiment, this can include an amount of time for a given user or an amount of time based on the total time the user has been logged into the account. Alternatively, it can be based on the total number of logins of a given user or the total number of logins during aggregation. Further, the criteria can include the following: (c) the frequency with which an item was previously selected while the user was logged into an account associated with multiple accounts, or (d) the frequency with which an item was previously selected while at least two users were logged into one or more accounts associated with multiple accounts. For both of these examples, as described for examples (a) and (b) above, the frequency can be based on one or more combinations of the period during which one or more users were logged into the account or the number of account logins. Further, the criteria can include the following: (e) the frequency with which any user previously selected an item while logged into any account, and / or (f) the frequency with which any user previously selected an item while logged into any account associated with multiple accounts. In these two examples, a data structure such as a table (or any other data structure described herein) can be used to track previously selected items, and the table can be periodically cleared after a given period has elapsed or after a certain number of total logins by one or more users have occurred.In certain embodiments, the criteria set forth in (c), (d), and (f) above may apply to a team account, particularly when the users of those accounts are team members who have one or more teams associated with multiple accounts.

[0203] If the determined frequency is above a threshold percentage, the menu item may be restricted for a subsequent period. The threshold may be based on the usage. In one embodiment, the threshold percentage may be 50% or more. In other embodiments, the threshold percentage may be 60% or more. In still other embodiments, the threshold percentage may be 70% or more. In further embodiments, the threshold percentage may be 80% or more. In other embodiments, the threshold may be in a range of percentages. For example, the threshold percentage may be in the range of 75% to 85%. Specific percentages are described herein by way of example and the threshold percentage is not limited thereto. Any threshold percentage or range may be used.

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

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

[0206] When it is determined that a menu item may be restricted, the hardware processor can determine which menu items can be displayed in the MUI display 206 and which menu item(s) are restricted for a subsequent period. According to an embodiment, any menu item determined to have a frequency exceeding the threshold percentage may be displayed (e.g., without limitation).

[0207] In a further embodiment, the display restriction may be based on menu items having a selection frequency less than a particular threshold, e.g., less than 50%, 40%, 30%, 20%, 10%.

[0208] In some embodiments, the restriction command can be issued based on various criteria. For example, one or more menu items may be excluded based on menu items (s) designated as unavailable to a particular user. This may occur, for example, when a particular user has not selected one or more menu items over a particular period of time. Similarly, one or more menu items may be restricted based on menu items (s) designed to be unavailable to a group of two or more users. In this example, the frequency with which two or more users select or do not select one or more menu items over a period of time may affect whether a restriction command is issued for those menu items (s). Other embodiments contemplate issuing a restriction command in a similar manner for the previous two examples, but based on the selection frequency of menu items (s) by users associated with a team (i.e., not for individual teams and / or groups of teams). Further, in other embodiments, menu items can be restricted based on a particular machine or set of machines on which one or more users are running a computer application logged in.

[0209] In one embodiment, the menu manager 1054 can issue 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 above a threshold percentage. The restriction command may be issued in cooperation with one or more display commands. Upon receiving the display command and the restriction command, the display manager 1050 can delete or remove menu items included in the display command but not included in the restriction command before displaying the menu items on the MUI display 206.

[0210] In other embodiments, the restriction command may include menu items other than the menu items determined to have a frequency exceeding the threshold ratio. When receiving the display command and the restriction command, the display manager 1050 may delete or eliminate the menu items included in the restriction command and also included in the display command before causing the menu items to be displayed in the MUI display 206.

[0211] In other embodiments, instead of a separate restriction command, the display command may be modified by the menu manager 1054 to eliminate menu items other than the menu items determined to have a frequency exceeding the threshold ratio.

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

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

[0214] In one embodiment, the restriction function may operate as follows to be applicable to any type of MUI module. Using a threshold ratio, it is possible to determine (without limitation, for example) which menu items are displayed. For example, a threshold ratio of 90% or 80% may be used. This means that only menu items with a selection frequency exceeding 90% or 80% are displayed. In one example, the selection frequency may be applied based on the user login session. This means that menu items that are used only 90% or 80% of the time when the user logs in are displayed. The restriction function can be applied to one or more menu levels, i.e., the first menu level, the second menu level, etc. In some embodiments, the threshold may vary based on the menu level (for example, lower levels may have lower frequency requirements for display. This is because there are often more options at lower levels, and they can be selected less frequently). These menu items that do not meet the threshold (for example, those used 10% or less, or 20% or less) are displayed in an advanced context menu, and the advanced context menu changes according to the ongoing menu being displayed. In this way, the user's options are limited to those most frequently used throughout the MUI, and navigation by the user can be significantly accelerated. In certain embodiments, the options excluded as described above can be made available only in the advanced context menu. Thus, in the 90% example, if only 90% of the available menus meet the threshold, only those are displayed in the ongoing menu, while the remainder (10% in this example) are displayed in the advanced context menu in response to an advanced context menu selector (also referred to throughout as the advanced selector or advanced context selector).

[0215] The 90% / 10% and / or 80% / 20% values are for illustrative purposes only, and other values may be selected according to the MUI module being implemented. In one example, the limiting function may also be based on the default protocol as compared to a protocol customized by the user. For example, a vendor may market an assay kit that includes a standard protocol that allows further customer modifications. The standard protocol options may be included in the available menu items that are displayed in the active portion as the user moves through the menu system. On the other hand, the available customer modifications may be displayed in an advanced context menu. This split of menu items can be adjusted based on actual user operations after that particular assay kit has been used several times by the user.

[0216] Similarly, by using the limiting command, the menu items (user-selectable options) may limit the menu items on the first menu, the second menu, and the third menu to a smaller number.

[0217] In certain embodiments, over time, the menu item selection table can delete the selection history for new determination. In this example, previously excluded menu item(s) become available again.

[0218] In an embodiment, the MUI can provide team integration through communication between multiple MUI modules. An integration system managed by a system consistent with the embodiments herein can be managed by a plurality of MUI modules configured to complete different tasks by different operators. For example, using the example of a Laboratory Information Management System (LIMS), a management console module, an experiment design module, an inventory management module, an experiment analysis module, and an experimental procedure module may be provided. The management console module can provide features and functions for managing various users, operators, instruments, and teams. The experiment design module can enable one or more members of a team to design experiments to be performed by other members of the team. The inventory management module may enable other team members to review the inventory and order more consumables in view of the experiment history and future planned experiments. The experimental procedure module can enable a team member responsible for starting an experiment to access and implement the already designed experiments through the interaction between the MUI, the operator, and an external system. Finally, the experiment analysis module may enable other team members to access the results of the experiment after it has been performed. Based on the setup of users and teams prepared through the management console, each user can log in to the system and be provided access to the modules necessary to complete the tasks they are responsible for. In an embodiment, the necessary modules may be installed on a computing device in a suitable location to complete the task (i.e., the experimental procedure module may be installed on a device connected to the experimental instrument, and the management console module may be installed on a desktop device). Thus, the system provided herein enables the integration of workflows between multiple team members by using a single, consistent interface.

[0219] In an embodiment, the display manager 1050 can be configured to provide one or more icons or animations to specify the "working" status of the systematic user interface control system 1102. When the systematic user interface control system 1102 is in processing, waiting time can be prevented by providing a working status display to warn the user that processing is being performed. In one embodiment, the working status display may be provided via a light fountain display presented on a part of the screen not occupied by the active part or the history part. For example, the lower part of the screen centered on the lower side of the active part may be used for the light fountain display. A series of cascade bars shown in colors matching the rest of the MUI may be provided by the light fountain. In one embodiment, the cascade bars may be presented in various shades of white and blue. In one embodiment, the bars are presented as four rows of elongated bars. Each row may include, for example, a plurality of bars of different lengths from 2 to 20. When the system is being processed, the bars can blink in different lengths and different shades of white and blue, giving the impression of a waterfall or a light fountain.

[0220] The embodiments described in this specification further include a method of designing a user interface system. For example, such a method may include designing a MUI that conforms to the embodiments of this specification. The method of designing a user interface system may include generating a hierarchical menu tree as described in this specification. The hierarchical menu tree may include a series of menus each including menu items that each lead to a subsequent series of menus. The method of designing a user interface system may further include selecting an execution menu that terminates a branch of the hierarchical menu tree, where the execution menu is configured to execute one or more commands within software, provide one or more command sets to a user, and / or output one or more commands to a connected device, system, instrument, or machine. The method of designing a user interface system may further include configuring each of the menus within the hierarchical menu tree in one or more display modes, where the one or more display modes include at least an active display mode for display in an active portion of the user interface and a history display mode for display in a history portion of the user interface. Further aspects of the method of user interface design may further include a method of designing any of the menu functions described in this specification.

[0221] In a further embodiment, a MUI consistent with the present disclosure may provide a help option integrated within the hierarchical menu navigation. The user may request help regarding a given menu by pressing a specific key combination and / or by accessing the help option presented by an advanced context menu. The integrated help option may include one or more dialog boxes designed to provide the user with an explanation of the presented options. As discussed above, the MUI provides a large amount of whitespace or background space. Thus, the help option may be presented as a pop-up or dialog box that points to the part of the MUI where the user requests help without impairing the original MUI display. In an embodiment, enabling the help function may cause a dialog box to be displayed when the user places the cursor over or otherwise displays any item within the MUI.

[0222] In a further embodiment, the MUI history portion may be further adapted to display menu items of the menu following the in-progress menu. For example, as the user navigates the in-progress menu, the user may scroll a vertical wheel, for example, to highlight or emphasize different menu items. A sub-menu associated with the highlighted menu item may be displayed in the history portion to provide a visual representation of subsequent menus to the in-progress menu that may include future items that may be selected thereafter.

[0223] In an embodiment, as discussed above, the first active portion and the second history portion are each adapted for a consistent display within the same portion of the MUI. The positioning of each of these portions is not limited to a particular location on the MUI, but in a particular embodiment, the location once selected is maintained. Thus, the active portion of the MUI display is adapted to be consistently displayed within the same first region of the UI display to optimize the user's concentration while interacting with the UI display. The history portion of the MUI display is adapted to be consistently displayed within the same second region of the UI display to optimize the user's concentration while interacting with the UI display.

[0224] In the foregoing description, an example of a menu configuration for providing a UI display of a plurality of menus within a hierarchical menu tree has been provided. FIGS. 2D-2M provide additional examples of menu display configurations. The following menu display configurations, without limitation, can be used with each other and in any combination with the menu configurations disclosed previously. For example, when a particular menu item is selected at any position in the hierarchical menu tree, the processor may execute a command to shift the UI display to any of the menu configurations described herein. In particular, a particular menu display configuration may be associated with a particular menu selection.

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

[0226] In a further embodiment of this embodiment, both the first wheel and the second wheel can be displayed in the first portion 214 of the MUI display 206. The first wheel can be displayed in the first sub-portion of the first portion 214, and the second wheel can be displayed in the second sub-portion of the first portion 214. As used herein, a sub-portion can be a divided portion of a larger portion. A sub-portion can be used interchangeably with a sub-section. In an embodiment, the selection of a menu item within the first wheel can be caused by simply clicking on any menu item within the first wheel or by rotating any menu item within the first wheel to a prominent and highlighted position. When an item is selected from the first menu on the first wheel, the second menu displayed on the second wheel can be corrected accordingly. In yet another embodiment of this embodiment, the first portion 214 can be divided into more than two sub-portions, and each sub-portion can include a wheel that displays a corresponding menu. Thus, three wheels can display a first menu, a second menu, and a third menu representing different levels of a hierarchical menu tree. In another example, three wheels can display a second menu, a third menu, and a fourth menu. In other examples, any number of wheels may be included.

[0227] In a further embodiment, a plurality of wheels may be presented in a plurality of sub - portions of the first portion 204, enabling a user to select from a plurality of menus at the same hierarchical menu level. For example, selection of a particular menu item at one menu level may lead to the presentation of a plurality of sub - menus at the same level. Thus, selection of an item at the second menu level may lead to the presentation of a plurality of third menus, each including a plurality of third menu items. In an embodiment, the plurality of sub - menus presented may be execution menus, enabling a user to make a plurality of execution menu selections simultaneously. In embodiments where a plurality of sub - menus are presented, the plurality of sub - menus may be related to each other or otherwise associated with each other.

[0228] FIG. 2E shows yet another example of a menu display configuration in one embodiment. In this display configuration, two wheels are compressed into one wheel. The wheel options include sub - options represented within one wheel associated with the active wheel option. In this configuration, the first and second portions of the display overlap, yet all menu items can still be visualized (or, in the case of folded items, expanded and visualized by sliding or rotating the wheel of items). For example, the second wheel of options may be presented within the first wheel. The first wheel of options may be rotatable in one direction (e.g., vertically up and down), and the second wheel of options may be rotatable in a different direction (e.g., horizontally left and right). The selected path is also visualized in the second portion. For example, selecting "Sub - option 2" presented on the display causes the selected option to move under "First wheel option 1".

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

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

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

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

[0233] Figures 2H - 2J illustrate examples of a first portion and a second portion displayed as a series of concentric circles in one embodiment. Referring to FIG. 2H, the dial 220 can be rotated clockwise or counterclockwise to browse menu items or items to be selected within the option window 218. Tapping on the area (e.g., circle) of the dial 220 selects an option. For example, when an option browsed through the option window 218 is selected, the user interface transitions to the configuration shown in FIG. 2I. For example, in FIG. 2I, the concentric dials expand inwardly, showing another concentric circle representing another level (e.g., sub - level) of menu items or paths. Sub - options can be browsed through the option window 222 on that circle 224 (also referred to as a dial) by rotating the dial 224 clockwise or counterclockwise. Selection of an option 222 (shown as sub - option "n") at that level may be done by tapping on the area of that circle 224 (i.e., not overlapping with the inner circle or dial 220). In another embodiment, selecting an option from the user interface of the dial or circular menu (e.g., as shown in FIG. 2H) can transition the state of the user interface to the configuration shown in FIG. 2J. For example, the next - level option selection expands from the selected option, expanding the dial to show another inner dial 224 with an option window 222. In one embodiment, the number of options viewable in the option windows (e.g., 218 and 222) need not be limited, and as a result, an unlimited number of options can be displayed and selected for application to the application.

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

[0235] In another aspect, an option window (e.g., 219) may display two or more items or options at a time, such as three menu items or options. In this example, tapping a menu item of the option window selects the option. After the selection is made, the selected option may be displayed in a highlighted or other distinguishable format, for example, to distinguish the selected option from the unselected options displayed in the option window.

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

[0237] FIG. 2K shows a tree-type menu level in one embodiment.

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

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

[0240] Figures 2M through 2O show examples of a scrollable wheel that scrolls or slides from the first menu item to the last menu item and returns from the last menu item to the first menu item. In this embodiment, the graphical element (e.g., wheel or slider) indicating the menu item stops at the last menu item or (when rotating from the last menu item) the first menu item without making a full revolution or rotation. In this way, for example, the start and end of the menu are always displayed because neither is joined or connected. This technique can shorten the computer's processing cycle time (and be immediately understandable to the user) because the wheel and / or slider can convey the entire menu of options while clearly indicating which option is the first menu item and which is the last menu item among the options presented by the wheel and / or slider. As a result, the wheel or slider does not need to repeatedly scroll to determine which menu item is the first menu item and which is the last menu item, or to determine whether all menu items have been visited.

[0241] In an embodiment, the wheel and / or slider do not have to rotate completely, for example, they do not have to make a full turn or a complete circle. For example, the wheel and / or slider rotate or slide from a start menu item to an end menu item and then slide back in reverse from the end menu item to the start menu item. In this way, for example, the start and end of the menu are always displayed, either joined together or spaced apart so as not to be together. This technique enables the wheel and / or slider to convey the entire menu of options (and be immediately understandable to the user) while clearly indicating which option is the first menu item and which is the last menu item among the options presented by the wheel and / or slider, thus reducing processing time. Further, as the wheel and / or slider rotate, selectable options can be displayed in a more prominent form, such as using larger text, bolder fonts, etc. Options that were previously selectable when the wheel and / or slider were rotated / slid to different positions, or options that become selectable as the wheel and / or slider continue to rotate / slide, can be displayed in a less prominent form, such as by reducing the text size or using a thinner font. In one embodiment, the more prominently displayed options may be displayed as if they are closer to the user than the less prominent options.

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

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

[0244] A non - limiting use of such a user interface is to select channels to view on a television (TV). Broader categories may be displayed on the upper horizontal region, more detailed categories may be stacked below, and leaf - like items may be displayed vertically, for example, on a vertical wheel. For example, referring to FIG. 2E, "Wheel Option 1" may represent a genre, and "Sub - Option 1" may represent shows and / or movies organized within a grid.

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

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

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

[0248] A wide variety of solid phases, including conventional solid phases from the technical field of binding assays, are suitable for use in the method of this embodiment. The solid phase can be made from a variety of different materials, including polymers (e.g., polystyrene and polypropylene), ceramics, glass, composite materials (e.g., carbon polymer composite materials such as carbon-based inks), etc. Suitable solid phases include the inner surface of an assay container (e.g., the well in a test tube, cuvette, flow cell, cartridge, multi-well plate, etc.), slides, assay chips (such as those used in gene or protein chip measurements), pins or probes, beads, filtration media, lateral flow media (e.g., the filtration membrane used in a lateral flow test strip), etc., including the surface of macroscopic objects.

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

[0250] The particles used in this method may be composed of any material suitable for binding to one or more binding partners and / or labels, and may be collected, for example, via centrifugation, gravity, filtration, or magnetic capture. A wide variety of different types of particles that can bind to a binding reagent are commercially available for use in binding assays. These include non-magnetic particles and particles containing a magnetizable material that enables the collection of the particles in a magnetic field. In one embodiment, the particles are composed of a conductive material and / or a semiconductive material, such as colloidal gold particles.

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

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

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

[0254] Methods for measuring the amount of an analyte include label-free techniques, which can include, but are not limited to, i) techniques for measuring changes in mass or refractive index at a surface after binding of the analyte to the surface (e.g., surface acoustic wave techniques, surface plasmon resonance sensors, ellipsometry techniques, etc.), ii) mass spectrometry techniques (including techniques such as MALDI, SELDI that can measure analytes on a surface), iii) chromatography or electrophoresis techniques, and iv) fluorescence techniques (which can be based on the intrinsic fluorescence of the analyte).

[0255] Methods for measuring the amount of an analyte also include techniques for measuring the analyte through detection of a label that can be attached directly or indirectly (e.g., through use of a labeled binding partner of the analyte) to the analyte. Suitable labels include labels that can be directly visualized (e.g., visually confirmable particles and labels that generate measurable signals such as light scattering, optical absorbance, fluorescence, chemiluminescence, electrochemiluminescence, radioactivity, magnetic fields, etc.). Labels that can be used also include enzymes or other chemically reactive species having chemical activity leading to measurable signals such as light scattering, absorbance, fluorescence, etc. The use of enzymes as labels is well established in enzyme-linked immunosorbent assays, also referred to as ELISA, enzyme immunoassays or EIAs. In the ELISA format, an unknown amount of antigen is attached to a surface, and then a specific antibody is washed over the surface such that it can bind to the antigen. This antibody is linked to an enzyme, and in a final step, a substance is added that the enzyme converts to a product that results in a change in a detectable signal. Formation of the product can be detectable in measurable properties such as absorbance, fluorescence, chemiluminescence, light scattering, etc., for example, due to differences relative to a substrate. In certain (but not all) measurement methods that can be used with the solid-phase binding methods according to embodiments, benefit is obtained from or the washing step for removing unbound components (e.g., labels) from the solid phase may be required. Thus, the methods of the embodiments may include such a washing step.

[0256] The methods disclosed herein may be performed manually, using automated techniques, or both. Automated techniques may be partially automated, for example, with one or more modular instruments, or fully integrated automated instruments.

[0257] Exemplary automated systems are discussed and described in International Patent Application Publication Nos. WO2018 / 017156, WO2017 / 015636, and WO2016 / 164477, each of which is hereby incorporated by reference in its entirety.

[0258] Automated systems (modules and fully integrated systems) in which the methods described herein can be implemented may include the following automated subsystems, namely, hardware (e.g., personal computers, laptops, hardware processors, disks, keyboards, displays, printers), software (e.g., processes such as drivers, driver controllers, and data analysis devices), and computer subsystems (s) that may include databases (s), liquid handling subsystems (s) (e.g., sample handling and reagent handling, (e.g., robotic pipetting heads, syringes, stirrers, ultrasonic mixing devices, magnetic mixing devices)), sample, reagent, and consumable storage and handling subsystems (s) (e.g., robotic manipulators, tube or lid or foil piercing devices, lid removal devices, linear and circular conveyors and robotic manipulators, tube racks, plate carriers, trough carriers, pipette tip carriers, plate shakers, etc. transport devices), centrifuges, assay reaction subsystems (s) (e.g., fluid-based and consumable-based ones (tubes and multiwell plates, etc.)), container and consumable washing subsystems (s) (e.g., plate washers), magnetic separator or magnetic particle concentrator subsystems (s) (e.g., flow cell, tube, and plate types), cell and particle detection, sorting and separation subsystems (s) (e.g., flow cytometers and counters), detection subsystems (s) such as colorimeters, nephelometry, fluorescence, and ECL detectors, temperature control subsystems (s) (e.g., air handling, air cooling, air warming, fans, blowers, water baths), waste subsystems (s) (e.g., liquid and solid waste containers), global unique identifier (GUI) detection subsystems (s) (e.g., 1D and 2D barcode scanners such as flatbed and wand types), and sample identifier detection subsystems (s) (e.g., 1D and 2D barcode scanners such as flatbed and wand types).Analysis subsystem(s) (e.g., chromatography systems such as high performance liquid chromatography (HPLC), fast protein liquid chromatography (FPLC), and mass spectrometers) can also be modules or can be fully integrated. An automated system consistent with the embodiments of this specification may be controlled and / or managed by a systematic user interface control system 1102.

[0259] A system or module that performs sample identification and preparation can be combined with (or adjacent to, joined to, robotically linked to, or coupled with) a system or module that performs an assay, performs detection, or both. Multiple modular systems of the same type can be combined to increase throughput. The modular system(s) can be combined with module(s) that perform other types of analysis such as chemical analysis, biochemical analysis, and nucleic acid analysis.

[0260] An automated system can enable batch, continuous, random access, and point-of-care workflows, as well as single sample throughput, medium sample throughput, and high sample throughput.

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

[0262] The automated system can be configured to perform one or more of the functions of (a) moving consumables such as plates into and out of a detection subsystem, (b) moving consumables between other subsystems, (c) storing consumables, (d) processing samples and reagents (e.g., mixing reagents and / or adapting to introduce reagents into consumables), (e) agitating consumables (e.g., for mixing reagents and / or increasing reaction rates), (f) cleaning consumables (e.g., performing a wash plate and / or an assay wash step (e.g., well aspiration)), and (g) measuring ECL in a flow cell or in a consumable such as a tube or a plate. The automated system may be configured to process individual tubes placed in a rack, multi-well plates such as 96 or 384 well plates.

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

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

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

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

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

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

[0269] The resolvable binding regions can be optically investigated in whole or in part. That is, each individual resolvable binding region can be optically investigated individually and / or the entire surface containing a plurality of resolvable binding regions can be imaged, and one or more pixels or groups of pixels within that image can be mapped to the individual resolvable binding regions. The resolvable binding regions can also be particles within a plurality of particles. Resolvable binding regions that exhibit a change in optical signature can be identified by conventional light detection systems. Optical filters designed for a particular wavelength can be used for optical interrogation of the resolvable binding regions, depending on the detected species (e.g., type of fluorescent entity, etc.) and the operating wavelength. In embodiments where optical interrogation is used, the system includes two or more light sources and / or a plurality of filters and can adjust the wavelength and / or intensity of the light sources. In some embodiments, optical signals from a plurality of resolvable binding regions are captured using a CCD camera. Other non-limiting examples of camera imaging systems that can be used to capture an image include charge injection devices (CID), complementary metal oxide semiconductor (CMOS) devices, scientific CMOS (sCMOS) devices, and time delay integration (TDI) devices. In some embodiments, a scanning mirror system coupled to a photodiode or a photomultiplier tube (PMT) can be used for imaging.

[0270] In embodiments, the binding of each analyte to its corresponding capture reagent is performed in parallel by contacting one or more surfaces with a single liquid volume containing a plurality of analytes. In embodiments, the plurality of analytes includes an analyte and one or more additional analytes. In embodiments, each step of the method is performed in parallel for each analyte. In embodiments, the method is a simultaneous multiplex assay. Multiplex measurements of analytes on a surface are described herein, and reference is also made to, for example, U.S. Patent Nos. 10,201,812, 7,842,246, and 6,977,722, the entire disclosures of which are incorporated herein by reference.

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

[0272] Alternatively or additionally, the capture reagent can be bound directly or indirectly to different distinct binding domains on one or more solid phases, such as in a binding array where the binding domains are individual array elements, or in a set of beads where the binding domains are individual beads. As a result, distinct assay signals are generated and measured from each binding domain. When the capture reagents for different analytes are immobilized on different binding domains, the different analytes that bind to those domains can be measured independently. In one example of such an embodiment, the binding domains are prepared by immobilizing distinct domains of a capture reagent that binds to an analyte of interest on one or more surfaces. Optionally, the surface(s) can partially define one or more boundaries of a container that holds the sample, or through which the sample passes (e.g., a flow cell, well, cuvette, etc.). In a preferred embodiment, the individual binding domains are formed on electrodes for use in electrochemical or electrochemiluminescence assays. Multiplex measurements of analytes on a surface containing a plurality of binding domains using electrochemiluminescence are used in the Meso Scale Diagnostics, LLC, MULTI-ARRAY® and SECTOR® Imager product lines (see, e.g., U.S. Patent Nos. 10,201,812, 7,842,246, and 6,977,722, which are incorporated herein by reference in their entirety).

[0273] In addition, the capture reagent can be directly or indirectly bound to the electrode surface, which optionally contains different separate binding domains as described above. The electrode surface can be a component of a multi-well plate and / or a flow cell. The electrode may include a conductive material, such as a metal including gold, silver, platinum, nickel, steel, iridium, copper, aluminum, a conductive substance, etc. The electrode may include a metal with an oxide coating, such as aluminum oxide-coated aluminum. The electrode may include a working electrode and a counter electrode that can be made of the same material or different materials (e.g., a metal counter electrode and a carbon working electrode). In a particular embodiment, the electrode includes a carbon-based material such as carbon, carbon black, graphite carbon, carbon nanotubes, carbon fibrils, graphite, graphene, carbon fibers, and mixtures thereof. In one embodiment, the electrode includes elemental carbon, such as graphite, carbon black, carbon nanotubes, etc. Advantageously, they may include a conductive carbon polymer composite material, conductive particles dispersed in a matrix (e.g., carbon ink, carbon paste, metal ink, graphene ink), and / or a conductive polymer. One specific embodiment of the present invention is an assay module, preferably a multi-well plate, having an electrode (e.g., a working electrode and / or a counter electrode) including carbon, such as a carbon layer, and / or a screen-printed carbon ink layer.

[0274] In an embodiment, each binding domain includes a targeting reagent complement that can bind to a targeting reagent, each anchor reagent and capture reagent includes a complementary ligation reagent that can bind to a ligation reagent, and the method further includes (1) binding the capture reagent and the anchor reagent to the targeting reagent complement connected to the ligation reagent through the complementary ligation reagent, and (2) binding the product of step (1) to a binding domain including the targeting reagent complement, wherein (i) each binding domain includes a different targeting reagent complement, and (ii) each targeting reagent complement selectively binds to one of the targeting reagents, thereby further including immobilizing the capture reagent and the anchor agent to each binding domain.

[0275] Thus, in an embodiment, the surface contains a targeting reagent complement, the targeting reagent is connected to a linking reagent, and each of the capture reagent and the anchor reagent contains a complementary linking reagent. Accordingly, in an embodiment, the targeting reagent complement on the surface is bound to the targeting reagent connected to the linking reagent, where the linking reagent is bound to the complementary linking reagent on the capture reagent and the anchor reagent.

[0276] In an embodiment, the linking reagent has two or more binding sites for additional linking reagents, and immobilization of the capture reagent and the anchor reagent includes binding the capture reagent and the anchor reagent to the targeting reagent connected to the linking reagent through the complementary linking reagent, and binding the product to a binding domain containing the targeting reagent complement, where (i) each binding domain contains a different targeting reagent complement, and (ii) each targeting reagent complement selectively binds to one of the targeting reagents. For example, when the targeting agent is an oligonucleotide, the linking reagent is streptavidin, and the complementary linking reagent is biotin, a biotin-labeled oligonucleotide can bind to the first of the four biotin binding sites of streptavidin to form a targeting reagent connected to the linking reagent. Next, a biotin-labeled capture reagent (i.e., a capture reagent connected to the complementary linking reagent) can bind to the remaining biotin binding sites on streptavidin to connect the targeting agent to the capture reagent.

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

[0278] In an embodiment, the method of the present invention is applied to one or more formats in which multiple assay measurements are performed on a single sample. Multiplex measurements that can be used in the present invention include, but are not limited to, i) multiplex measurements involving the use of multiple sensors, ii) multiplex measurements using distinct assay domains on a surface (e.g., an array) that are distinguishable based on their position on the surface, iii) multiplex measurements involving the use of reagents coated on particles that are distinguishable based on particle characteristics such as size, shape, color, etc., iv) multiplex measurements that generate assay signals distinguishable based on optical properties (e.g., absorbance or emission spectrum), or v) multiplex measurements based on the temporal characteristics of the assay signal (e.g., the time, frequency, or phase of the signal). Exemplary assay formats include V-PLEX (www.mesoscale.com / en / products_and_services / assay_kits / v-plex) and U-PLEX (www.mesoscale.com / en / products_and_services / assay_kits / u-plex_gateway, and each of which is incorporated herein by reference in its entirety by U.S. Patent Nos. 10,201,812 and 10,189,023). Additional ultra-high sensitivity assay formats include those described in U.S. Patent Application No. 62 / 812,928, filed March 1, 2019, and U.S. Patent Application No. 62 / 866,512, filed June 25, 2019, each of which is incorporated herein by reference in its entirety.

[0279] Exemplary plate readers include the MESO SECTOR S 600 (www.mesoscale.com / en / products_and_services / instrumentation / sector_s_600) and the MESO QUICKPLEX SQ 120 (www.mesoscale.com / en / products_and_services / instrumentation / quickplex_sq_120) (both available from Meso Scale Diagnostics, LLC), and the plate readers described in U.S. Patent No. 6,977,722 and U.S. Patent Application No. 62 / 874,828 (Attorney Docket No. MSD-011.PROV, each of which is incorporated herein by reference in its entirety) entitled "Assay Apparatuses, Methods and Reagents" by Krivoy et al., filed on July 16, 2019.

[0280] The above user interface techniques can also be incorporated into the user interface of an assay system. The assay systems described below enable a user to perform an assay via the user interface. Hereinafter, an example of a user interface incorporated into an assay system for an assay method will be described. The term "system software" or "system" referred to hereinafter when describing the functions of the assay system and its user interface refers to the software implementing the assay system. The user interface can display or visualize the workflow and / or the path of menu items.

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

[0282] Advanced context menu - A menu of options that depends on a specific context for advanced users (such as the in-progress screen, sub-step, screen status, etc.).

[0283] Assay method - A method for performing an assay. It includes, but is not limited to, 1. the instrument protocol to be executed and the parameters for executing that protocol, 2. the test plate layout, 3. the calibrator titration scheme such as the dilution factor, 4. the control layout, and 5. the sample replication scheme.

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

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

[0286] Completed run - A run that has been aborted, a run that has been completed with a flag(s), or a run that has been completed successfully.

[0287] CV - Coefficient of variation.

[0288] Database screen - Resets the entire database and restores it to the state at system installation.

[0289] ECL - Electrochemiluminescence. A unique format for detecting molecules of biological interest.

[0290] Existing run - A planned run, an aborted run, a run that has been completed with a flag(s), or a run that has been completed successfully.

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

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

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

[0294] The types of GPI and GPD are known. For example, refer to U.S. Patent No. 8,770,471, International Patent Application No. WO2011 / 017082, and International Patent Application No. 2006 / 199196.

[0295] A detailed log file that records all actions performed by the instrument-log system and all malfunctions or error states that occurred during the performance. The instrument log is a rolling cycle log that includes the stored information and is limited by the amount of memory space allocated to this log file. For example, old entries are overwritten over time.

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

[0297] LED - Light-emitting diode. A light source.

[0298] Normal state - When the software is functioning without errors or warnings, the instrument is considered to be in a normal state. When the error state is recovered and / or the warning message is confirmed, the instrument returns to the normal state.

[0299] Startup - As startup, it includes zero or more named samples and one or more assay methods, and the samples are tested according to the information described in the assay method.

[0300] Startup owner - The user who created the startup.

[0301] Sample - A general term that includes the substance to be analyzed, including calibrators, controls, blanks, and contaminants.

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

[0303] Sample layout - The sample positions and sample IDs on the plate.

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

[0305] The position and name of the analyte within the well on the spot layout - plate.

[0306] Step - One of a series of distinct consecutive stages that are in progress towards a goal. A step constitutes a broad stage that can be composed of multiple sub - steps.

[0307] Sub - step - One of a series of distinct consecutive stages in the progression towards the completion of a step. A sub - step constitutes an intensive activity within a step.

[0308] Unexpected barcode - A barcode that is different from what is expected. Consumables can also be considered to have an "unexpected barcode" if the barcode cannot be read.

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

[0310] UI warning event - Any caution message that requires a user response. The user needs to correct the error and / or confirm the message before proceeding. For example, in a UI warning event, the instrument may be in a "Not Ready" state.

[0311] System event log - A permanent log of events that occur in software not related to the instrument.

[0312] Figure 4 is a flowchart illustrating a first user login user interface of an assay system in one embodiment. At 402, the system software for the assay method can verify that an end user license agreement (EULA) associated with the assay system has been accepted each time the assay system starts. When the user first starts the system software, the EULA is displayed. Records of the username and date / time are created when the user agrees to the contract. If the user has not previously accepted the contract, at 404, the EULA is displayed and the user is enabled to accept the contract. At 406, if the user does not accept the contract, the software closes. At 408, a splash screen including system software branding, copyright, legal notice, and software version is displayed. The initial login screen requests a username at 410. In one embodiment, the system software can present past usernames used to log in on the system to minimize errors by entering the username. The user can also enter a new username that has never been used for login before. After selecting (or receiving) the username at 412, the software prompts the user to enter the password for the username at 414. In one embodiment, the system software may use biometric authentication methods such as face recognition, voice, and / or fingerprint to log in or verify the login. In another embodiment, the system software may use a badge key card containing information that can be scanned or read via near field communication. At 416, the system software receives the entered password. When the username and password are entered, the system software authenticates the user at 418. If the user is successfully authenticated, the user interface proceeds to the start screen at 420. Otherwise, the system software via the user interface prompts the user to retry. 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 the Microsoft Windows® authentication function or may be configured to authenticate via Active Directory. In this first user interface display, the username and password prompts may be displayed, for example, horizontally in one orientation on the horizontal wheel graphical element 422.

[0313] FIG. 5 is a flowchart showing a method of displaying a start user interface screen display in one embodiment. This display screen includes, for example, a list of menu items in two different visual orientations, horizontal and vertical. Thus, for example, more general categories of menu items are displayed on the horizontal wheel 502, and sub-menu items are displayed on the vertical wheel 504. For example, the START option 506 selected by the logged-in user (FIG. 4) is presented on the horizontal wheel 502. The second level of options resulting from the START option 406 is presented on the vertical wheel 504. In the assay method of this example, the start screen is the initial software screen presented to the user. The workflows that the user can execute are listed as options (sub-options) on the selectable vertical wheel. In this example of the assay method, advanced workflows, rather than general workflows, may be grouped under an advanced menu. In the assay method of this example, the options for the system's workflows are as follows. When creating a new startup 508 and the user selects to create a new startup workflow 510, the user can create a startup from scratch or based on a pre-defined startup 512. When continuing a previously planned or started startup 514 and the user selects to continue a previously planned or started startup 516, the software automatically resumes at 518 from the last step the user completed in the startup. When viewing the results of a completed startup 520 and the user selects to view a completed startup 522, the software guides the user to a review screen 524. After the user selects any option from the vertical wheel 504, the options on the vertical wheel are added to a new horizontal wheel above the screen. This horizontal wheel allows the user to change the selection. For example, after selecting "New Creation", the options of [Planned Startup] and [Completed Startup] are moved to the horizontal wheel, which can change the user's awareness.

[0314] FIG. 6 is a diagram showing the workflow of a definition assay method screen in one embodiment. In this example, the software requires an assay method to process the sample under consideration. The processes shown in this screen can be executed in response to the DEFINE option (FIG. 5, 512) being executed. The assay method defines the assay on the plate, the plate layout, the maximum number of calibrators, controls, and samples, the dilution of the controls, calibrators, and samples, the number of replicates of the controls, calibrators, and samples, and the instrument protocol (incubation time, execution of blockers, and / or others). A default assay method is provided for all kits, and using the system software, a custom assay method can be created based on the default. In one embodiment, the assay method is distributed in a Global Product Data (GPD) file. The GPD includes the product barcode, the assay, the arrangement of the assay in the wells, the lot identification of the kit, plate, antibody, calibrator, control, the measured concentration of the calibrator and control, the description of the instrument regarding the method of processing the product, and the recommended plate layout.

[0315] FIG. 7 is a diagram showing a user interface workflow for selecting an assay method in one embodiment. This user interface workflow may follow the selection or execution of a defined assay method, for example, it may be selected or executed as an option in the workflow shown in FIG. 6. The options for [Assay Method Definition] may include [Assay Method Selection Option, [Sample] Option, and [Confirmation] Option, which may be shown in a horizontal orientation on, for example, the horizontal wheel graphical element 702. The selected [Assay Method] option can have its horizontal wheel highlighted and / or centered relative to other unselected options. Sub-level options below the [Assay Method] option may be displayed in a vertical orientation on, for example, the vertical wheel graphical element 704. In this example, there may be three ways for the user to select an [Assay Method], namely, a) select from the [Assay Methods] most recently used in a system sorted in reverse chronological order, b) select from all available assay methods installed in the system (in this screen, the UI uses multiple wheels, and each wheel filters the results of the next wheel until the final wheel contains the results), and c) search for [Assay Methods] installed in the system (this can be done using free text search).

[0316] When the user selects one of the sub-level options, the sub-level option moves to the horizontal wheel, enabling the user to change the [Assay Method] selection model. After the user makes an initial selection of an assay method, the user can choose whether to launch only a single assay method or multiple assay methods. In the case of a single assay method, all method-scale diagnostic test plates being launched use the same assay method. In the case of multiple assay methods, there is at least one method-scale diagnostic test plate for each assay method being launched.

[0317] FIG. 8 is a flowchart showing the workflow of a user interface displayed to define a sample in one embodiment. Based on the selection of the "Sample Definition" option, the option is presented in a horizontal orientation, for example, on a horizontal wheel graphical element 802 that can be stacked under the [Definition] option, which is its parent menu item. Sub-levels of options associated with the "Sample Definition" option are presented vertically, for example, on a vertical wheel graphical element 804.

[0318] On the screen of the [Definition] of the sample, the user interface can select whether to import a sample or define a sample manually. These options move to the horizontal wheel after the user selects an option. When the user selects to import a sample from a file, the software presents a sample file that the user can use with the vertical wheel via the user interface. The system can alternatively import from a laboratory information system or a laboratory information management system.

[0319] The system can also import from a sample management system. When the user selects to define a sample manually, the user can define the number of samples to initiate. The software automatically assigns a sample ID.

[0320] Figure 9 is a flowchart showing the workflow of a user interface displayed to confirm the definition of startup in one embodiment. When the "Confirmation of Startup Definition" option, which is a sub-menu item of the "Definition" option, is selected, the "Confirmation of Startup Definition" option is displayed in a horizontal wheel graphical element and stacked, for example, under the "Definition" option which is the parent menu item. After the user defines the startup in a previous step, the system provides a summary of the startup for the user to review and confirm. The following information is displayed to the user: the number of samples during startup. The user may also select the number of samples to view the sample identifier (ID), the number of method-scale diagnostic plates during startup, the layout of the plates, and the name of the startup. The system gives a default name to the startup and allows the user to change it. When the user confirms the startup, the system displays a prompt asking whether the user wants to continue with the execution of the startup or return to [Target Start].

[0321] Figure 10 is a flowchart showing the workflow of a user interface displayed to notify the user of completed tasks in one embodiment. The system can guide the user by achieving tasks through the user interface (automatic help function) within the wizard. The main logical steps may be classified into goals. In this example, the system has the following three main goals: In the start, the user starts and selects what the user wants to do in the system. In the definition, after the user selects what to do, the wizard guides the user by defining the necessary information through the user interface. In the execution, the system guides the user through the execution of the task selected by the user.

[0322] FIG. 11 is a flowchart showing the workflow of a user interface displayed for the execution / collection option in one embodiment. In this collection screen, the system creates a list of items that the user needs to collect in order to execute the startup. Before proceeding, each item needs to be marked as collected. The system also enables the user to print this list or collect it using a tablet computer. For each item collected, the item may optionally be scanned, and the system can verify that it is the correct item, expiration date, and lot information. For example, the system may request a barcode scan on the item. This is done using a barcode (GPI), and the GPD is obtained.

[0323] FIG. 12 is a flowchart showing the workflow of a user interface displayed for the execution / preparation option in one embodiment. In this preparation screen, the system presents a list of steps necessary to prepare the items collected in the wheel. For each step within the wheel, when that preparation step is selected, the system presents detailed instructions for that preparation step. The detailed preparation steps may include web content such as text explaining the action, an image visually showing the action, a video demonstrating the action, or a web page providing details or context of the action. The user is required to indicate that all preparation steps are complete before proceeding to the next step. The user may also print the preparation steps or complete them using a tablet.

[0324] FIG. 13 is a flowchart showing the workflow of a user interface displayed for execution / load options in one embodiment. In this load screen, the system displays a list of items to be loaded into the instrument in a wheel format. For each item, the system graphically displays the location where the item is to be loaded. The system provides a graphical indication of whether the item has been loaded or is empty. The system checks whether all items have been loaded before proceeding to the next screen.

[0325] FIG. 14 is a flowchart showing the workflow of a user interface displayed for execution / startup options in one embodiment. This startup screen enables the user to command the system to start the startup, for example, via the startup button UI control. On this screen, the user can also register other users for system update messages. The updates may be distributed, for example, via text such as email (electronic mail), short message service (SMS), social network applications and / or blogs, and / or others. When the user starts the startup, the system transitions to present a timer for the estimated time until completion. In one embodiment, the timer has three modes: 1) the estimated time in analog clock format, 2) the estimated time in digital watch format, and 3) the live camera feed of the instrument. The user may also request to stop the startup from an advanced context menu.

[0326] FIG. 15 is a flowchart showing the workflow of a user interface displayed for execution / unload options in one embodiment. When the startup is complete, the system transitions to this unload screen. In the unload screen, a list of steps for unloading the system within the wheel is presented. For each item, the system graphically displays the location where the item is to be unloaded. The system provides a graphical indication of whether the item is being loaded or unloaded. It is necessary to unload all items before proceeding to the next screen.

[0327] Figure 16 is a flowchart showing the workflow of a user interface displayed for execution / review options in one embodiment. On the review screen, the system presents the startup results. Also, the results are automatically exported in file format, sent to the LIMS / LIS system and automatically exported, and automatically exported by email. When the results are presented, a) they are graphically viewed as a plate representation. The ECL or calculated concentration is displayed using a luminance scale, with dark colors / black indicating low results and light colors indicating high results. A scale annotating the color luminance with numerical values is displayed. b) The results are also available as a table. This table can be exported in file format, sent to the LIMS / LIS system, and / or by email. The system records abnormal operations or results in the table, for example, if the temperature during startup is not within the specified range. After the user has completed the review of the startup data, the user may move to [Target Start] to start another startup or view the results.

[0328] FIG. 17 is a flowchart showing a workflow of a user interface displayed for execution / review options in one embodiment. In one embodiment, the system classifies tasks that a user can perform into a main workflow and an advanced workflow. The main workflow is the workflow that a user routinely executes and is optimized to facilitate execution. The main workflow is displayed in the wizard's goals and steps. The advanced workflow exists in an advanced context menu and represents workflows that are not routinely performed or are not restricted to the configuration manager. The user clicks on [Methoscale Diagnostic Glove] to open the advanced context menu. The advanced context menu items are included in a vertical wheel having three main groups, namely, functions related to the in-progress screen (context-sensitive items that change according to the active screen), switchable modules, and functions applicable to all modules such as software login and logout. On this screen, the selected option, the advanced menu, is displayed horizontally in a horizontal graphical wheel, and the sub-options of the advanced menu are displayed vertically in a vertical graphical wheel.

[0329] In one embodiment, the graphical user interface in one embodiment maximizes the black space by making the background black, thereby minimizing the coloring of pixels during the user interface display (e.g., display screen), saving memory, and improving the presentation speed. FIG. 20 is an exemplary screen shot of a screen showing a graphical wheel / slider that maximizes the screen black space in one embodiment.

[0330] Further exemplary screenshots consistent with the embodiments of this specification are shown in FIGS. 58-63. FIGS. 58A-58HH are exemplary non-limiting embodiments of a leader module. FIGS. 59A-59T are exemplary non-limiting embodiments of an experiment module. FIGS. 60A-60I are exemplary non-limiting embodiments of a maintenance module. FIGS. 61A-61Q are exemplary non-limiting embodiments of an administrative console module. FIGS. 62A-P are exemplary non-limiting embodiments of general screenshots applicable to multiple modules of this specification. FIG. 63 is an exemplary non-limiting embodiment of an audit trail module.

[0331] Examples of further screenshots consistent with the embodiments of this specification are included in U.S. Design Patent Application No. 29 / 675,777, entitled "Display Screen with Graphical User Interface," filed on January 4, 2019, the entire contents of which are incorporated herein by reference.

[0332] As described above, the user interface of the present disclosure presents a complete trajectory on a single screen of the user interface display, e.g., on a graphical wheel, regardless of whether it is used in an assay system or another system, enabling the user to select any item at any level and return from the current path of the selected item, instead of entering or inputting a series of back buttons on a keyboard or another input device. The user interface enables visualization of past decisions, e.g., the primary decision and the last n most recent decisions (the history of decisions can be visualized by scrolling another graphical element such as a graphical wheel or a graphical slider).

[0333] In one embodiment, the graphical user interface minimizes the number of menu options that a user needs to make to navigate an assay system. For example, the order in which menu options are presented may minimize the number of user options.

[0334] In one embodiment, computer processing time can be improved by minimizing the options or choices presented to the user and receiving input from those choices. The user interface guides the user to the next step of the application while minimizing the choices the user has to make.

[0335] In other embodiments, the specific features described herein can be used to divide one or more problems into different segments for multiple users to solve collaboratively (e.g., sequentially or in parallel). In this regard, the processor can be adapted to receive one or more benchmark inputs (e.g., inputs that support a larger problem, experiment, assay, etc., or provide information for its solution). The benchmark inputs can be aggregated and collectively relied upon to solve problems collaboratively or conduct experiments. Such inputs can be based on one or more of (a) modules, (b) problems or sub-problems to be solved, (c) devices, (d) physical locations, (e) tools, (f) instruments, or (g) equipment. Further, the processor can be adapted to notify more users, accounts, or teams of the results derived from one or more of the received benchmark inputs. In one example (e.g., running an assay), this can include notifying a researcher responsible for conducting the experiment that a first user has completed the design of the assay experiment (thus notifying the researcher that the experiment is ready to be conducted), and after the experiment is completed, notifying the first user back that the researcher has completed the experiment (e.g., so that the first user can review the results of the experiment). Further, the processor can be adapted to supply an output in response to the received response. As a result, the output can be adapted to be transmitted to a device communicatively connected to the processor (i.e., having an interface with a component, device, etc. in the physical world) to instruct the device to perform a specific action (e.g., undergo a physical movement or physical transformation). In certain embodiments, the processor causes a response to these components in the physical world as a step within a broader process of dividing one or more problems into different segments for multiple users to solve as described above. Additionally, specific aspects of these (and other processes described throughout) can be controlled by the processor via permission commands.Using permission commands, one or more of the access level, security level, or control level of users and teams can be managed. These permissions can be based on various levels, including one or more of roles, users, teams, accounts, instruments, devices, or equipment. In this regard, a very high-level set of permissions can be created to establish multiple levels of security for multiple applications so that access, control, and security can be strictly maintained and controlled in a very general way.

[0336] The following considerations provide additional embodiments and implementations of the systems presented herein. The user interface system discussed above can be widely applicable to various applications, including manufacturing environments, test environments, instrumentation environments, experimental environments, and others. In a series of embodiments, the user interface system discussed above can be used to provide a user interface system to an inclusive biometric measurement system that includes software, hardware, test equipment, and all additional necessary features. The following discusses such an inclusive biometric measurement system. In particular, the following discusses an embodiment of the system considered herein as a cloud-based platform. For example, the embodiments discussed below with respect to FIGS. 21-50 may also be implemented via alternative networked hardware and software platforms.

[0337] In this specification, for convenience, the description is made with reference to the drawings, which does not limit the scope of the embodiments of this specification. The following description is applicable to various analysis applications, including but not limited to biological analysis applications, chemical analysis applications, radiation analysis applications, etc.

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

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

[0340] 21105 is an analytical instrumentation provider environment for an instrumentation provider that can be used in an instrumentation device environment 21106, which includes one or more servers, desktop computers, laptop computers, tablets, and / or mobile devices, one or more of which can be used in an analytical computing system 21100, for example, to provide instruments used by a user in an analytical user environment 21101, for example, for sale or otherwise transfer. In 21105, there can be one or more instrumentation provider environments that use the analytical computing system 21100. 21104 is an analytical computing system provider environment for a provider of the analytical computing system 21100, which includes one or more servers, desktop computers, laptop computers, tablets, and / or mobile devices, one or more of which can be used in a system 211000 to manage business interactions with the analytical computing system 21100 used by an analytical user in an analytical user environment 2001. Each of the "providers" associated with the environments in 21102, 21103, 21104, and 21105 can include one or more entities, including but not limited to, multiple independent businesses, a single independent business, a combination of different independent businesses, or one or more businesses, among any of the "providers" in this specification. 21106 is an instrumentation device environment that includes one or more instruments, each having at least one computer, and in one implementation, can be at least partially used by the analytical computing system 21100 to initiate tests on samples for a user within the analytical user environment 21101.21107 is a cloud platform utilized to connect (e.g., bidirectionally) some or all of the computers within an analytical computing system 21100 with common computing, software services, and data architecture in one practice form through computers, networking, and software. Data can be collected and shared by any computer having the relevant software of the analytical computing system 21100 if a particular computer with the relevant software within the analytical computing system 21100 is located anywhere in the world in a secure manner. Here, in a preferred embodiment, the cloud platform 21107 is hosted by a public cloud provider that provides a shared computing environment, e.g., Amazon (trademark) Web Services, Google (trademark) Cloud, Microsoft (trademark) Azure, etc. In other embodiments, the cloud platform 21107 can be hosted by the analytical computing system provider at 21104, or can be self-hosted by an analytical user environment that is a user of the analytical computing system 21100, or can be hosted by a private cloud provider that provides a dedicated computing environment, e.g., hosted by Oracle (trademark) Cloud, IBM (trademark) Cloud, Rackspace, or others, or can be public cloud, private cloud, self-hosted, and can be hosted by the analytical computing system provider 21104. All communications with the cloud platform 21107 can be carried out through a preferred embodiment rather than a secure communication protocol such as https to encrypt all communications between the sender and the receiver.However, insecure communication protocols such as Hypertext Transfer Protocol Secure (HTTPS) can optionally be used with either secure or insecure case connection technologies such as Ethernet for local area network (LAN), metropolitan area network (MAN), and / or wide area network (WAN) configurations, and / or other similar technologies such as WIFI, Bluetooth, and / or distributed LAN. Additionally, the analysis computing system 21100 can be fully deployed on one computer such that all operations of the analysis computing system 21100 occur on that computer, and the only external communication that occurs between the computer and the associated software is initiated outside of the analysis computing system 21100.

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

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

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

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

[0345] The analysis computing system provider environment 21104 is an analysis computing system provider environment for a provider of the analysis computing system 21100, and includes one or more servers, desktop computers, laptop computers, tablets, and / or mobile devices, including one or more of them, and uses one or more of them in the analysis computing system 21100 to provide the analysis computing system 21100 to users in the analysis user environment 21101, instrumentation devices in the instrumentation device environment 21106, and various providers of 21102, 21103, and 21105. Here, the account information upload computer(s) 22213 includes one or more computers equipped with software used to prepare and control the use of the analysis computing system 21100 by users in the analysis user environment 21101 and the instrumentation devices in the instrumentation device environment 21106 through services and data storage provided by the cloud platform 22223. The computing system provider business system 22214 can host the analysis computing system provider environment 21104 internally, externally, and / or in any combination of internal and external, and optionally can include one or more computer systems equipped with software, for example, customer relationship management, enterprise data systems, data reporting applications, business productivity applications, relational databases and / or non-relational databases, file servers, and / or support the business operations of the analysis computing system provider to support the preparation and control of the use of the analysis computing system 21100, or there are other systems that are not used at all in the preparation and control of the use of the analysis computing system 21100.

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

[0347] The instrumentation device environment 21106 includes one or more instruments, each of which can be any of an individual operation instrument 22221, a coordinated operation instrument 22222, or a workflow assistance instrument(s) 22226 provided by the instrumentation device provider environment 21105. These can be used by the user in the analysis user environment 21101 to optionally process samples in combination with consumables provided by the consumables provider environment 21103 and generate data for analysis by the user in the analysis user environment 21101. Here, the individual operation instrument 22221 can have an individual operation instrument computer 22219 that provides integration between the individual operation instrument 22221 and the analysis computing system 21100 through services and data storage provided by the cloud platform 22223, and optionally provides operation control of the individual operation instrument 22221. The coordinated operation instrument 22222 can also have a coordinated operation instrument computer 22220 that provides integration between the coordinated operation instrument 22222 and the analysis computing system 21100 through services and data storage provided by the cloud platform 22223, and optionally provides operation control of the coordinated operation instrument 22222. The workflow assistance instrument 22226 can have a workflow assistance instrument computer 22225 that provides integration between the workflow assistance instrument 22226 and the analysis computing system 21100 through services and data storage provided by the cloud platform 22223, and optionally provides operation control of the workflow assistance instrument 224. Examples of the individual operation instrument 22221 include, but are not limited to, a plate reader, a plate washer, a plate incubator, a plate shaker, a plate incubator shaker, a pipetting system, or other types of instruments used in analytical sample testing. The coordinated operation instrument 22222 can combine some or all of the functions provided by one or more individual operation instruments 22221 into an integrated platform that automates the execution of the individual operations of the individual operation instruments 22221, thereby eliminating the need for the user to perform the various individual operations of the individual operation instruments 22221.The workflow assistance instrument 22226 can provide support to a user who tests an assay on a sample within the instrumentation environment 21106 using either the individual operation instrument(s) 22221 and / or the coordinated operation instrument 22222. Here, the support includes, but is not limited to, collecting various consumables potentially stored at various temperatures in different physical locations, preparing the consumables used for the processing of one or more assays, and / or guiding the user through the overall assay steps using one or more of the individual operation instruments 22221. Alternatively, the consumable provider environment analysis user application 21103 can assist with other tests in addition to, or instead of, the assay tests and / or plate-based tests described herein.

[0348] The instrumentation in the instrumentation environment 21106 can include zero or more individual operation instruments 22221, each having a corresponding individual operation instrument computer 22219, zero or more coordinated operation instruments 22222, each having a corresponding coordinated operation instrument computer 22220, and / or zero or more workflow assistance instruments 22224, each having a corresponding workflow assistance instrument computer 22225. A preferred embodiment for the instrumentation environment 21106 includes providing a separate computer to the analytical computing system 21100 that integrates zero or more individual operation instruments 22221, zero or more coordinated operation instruments 22222, zero or more workflow assistance instruments 22224, zero or more individual operation instrument computers 22219, zero or more coordinated operation instrument computers 22220, and zero or more workflow assistance instrument computers 22225 through services and data storage provided by the cloud platform 22223.

[0349] FIG. 23 is an embodiment of a system architecture for a cloud platform 22223 as part of an analytics computing system 21100 (FIG. 21), and the analytics computing system 21100 provides a common computing, software service, and data architecture such that data is collected and shared by any computer in the world having associated software. Here, one or more service servers 23302 provide scalable, robust, high-performance computing and related software platforms and support services specific to the analytics computing system 21100 for obtaining, storing, transferring, and / or transforming data related to the use of the analytics computing system 21100. One or more database servers 23309 (including, for example, one or more team databases 23310 and one or more system databases 23311) provide a scalable, robust, high-performance computing and related software platform for one or more structured databases used to store and / or obtain data generated by and / or for the users of the analytics computing system 21100, and for preparing for and through the use of data generated and / or used by the analytics computing system 21100 to store and / or obtain such data. Database technology can be essentially relational, such as, for example, SQL Server, Oracle, MySQL, Postgres, Aurora, and / or other similar relational database technologies, and / or can be essentially non-relational, such as DynamoDB, MongoDB, and / or other similar non-relational database technologies.One or more bulk data servers 23315, which may include system content 23312, instrument content 23313, and consumable content 23314, provide a scalable, robust, high-performance computing and related software platform for storing and retrieving file-based data provided for use by the analysis computing system 21100 and / or generated through the use of the analysis computing system 21100. The service server(s) 23302, in one embodiment, is associated with an administrator 23303 that includes a logical collection of services that support the management of the use of the analysis computing system 21100, a dashboard 23304 that includes a logical collection of services that support the monitoring and control of the use of the analysis computing systemThis load balancing technology can be implemented, for example, when a logical collection of services 23303, 23304, 23305, 23306, 23307, and 23308 is designed using the RESTful (Representational State Transfer) design pattern, i.e., it can be implemented when each provided service is stateless, i.e., it does not store or hold data, and thus any request made on the service can be satisfied by any available server on which the service is deployed in service server(s) 23302 based on the demand at the time of request. To support the optimal deployment and operation of the logical collection of services 23303, 23304, 23305, 23306, 23307, and 23308 on one or many computers, in a preferred embodiment, these services are built on a distributed object platform such as, for example, the Java Platform, Enterprise Edition, to support a cross-platform computing architecture, a computing architecture for Windows only such as the.NET Framework, or other similar distributed object platforms, or to utilize some combination of one or more of these distributed object platforms. The database server 23310 can include one or more databases, for example, a team database 23310 and a system database 23311. The team database 23310 is adapted to store information, data, and / or metadata related to a team (e.g., team name, members, permissions, etc.). The system database 23111 can include files, data, and / or other information related to system functions. Further, the bulk data server 23315 can include various contents, for example, system content 23312 (e.g., data or content related to the functions of the system, etc.), instrument content 23313 (e.g., instrument type, parameters, etc.), and consumable content 23314 (e.g., consumable type, quantity, etc.).

[0350] In FIG. 24, it is an embodiment of an administrator who uses the administrator computer 24401 to execute the administrator application software 24402, and activates the management function provided by the analysis computing system 21100 through the service provided through the cloud platform 22223. As considered herein, the administrator application software may use the above-described MUI to facilitate user access to the provided functions. Therefore, an embodiment of the systematic user interface control system 1102 may be provided by the combination of the administrator computer 24401 and the cloud platform 22223. As an example, one or more service servers 24411 may provide various functions such as authentication, one or more other management functions (for example, the function for uploading data to one or more database servers), one or more system functions, one or more applications (for example, app functions), and / or graphical visualization support via a dashboard. In this embodiment, the administrator application 24402 can be executed on the administrator computer 24401 via a separate application installed on the administrator computer 24401, or via the Internet browser installed on the administrator computer 24401, and accessed by pointing to the uniform resource locator (URL) of the web site portion of the service provided by the cloud platform 22223 logically composed with the supervisor 24408, but not limited to its composition. In one embodiment, the first interaction between the administrator and the cloud platform occurs by performing authentication 24404 with appropriate authentication information including, for example, a unique username and password and / or metric identification, and also any or required additional authentication inputs generally referred to as two-factor authentication previously configured for use by the administrator, through the use of the administrator application 24402 that requests a login service, for example, via the user manager 1056 of the systematic user interface control system 1102, via the service link 24403.In this embodiment, the login service obtains the encrypted credential information of the user from the system database 24406 via the service link 24405, allowing the administrator to access and manage the analysis computing system 21100. Upon login, the data stored in the system database 24406 is updated via the service link 24407, verifying that the usage of the analysis computing system 21100 can be tracked. The administrator can also reset their own password via the administrator app 24402 through the service link 24403 to perform authentication 24404 when they forget or do not know the password. The password reset updates the data stored in the system database 24406 via the service link 24407 to track the usage of the analysis computing system 21100. The administrator can also configure additional authentication inputs via the administrator app 24402 through the service link 24403 to perform authentication 24404, and can obtain and change the configuration of the additional authentication inputs to the system database 24406 via the service link 24405. The configuration change updates the data stored in the system database 24406 via the service link 24407 to track the usage of the analysis computing system 21100. After the administrator is authenticated upon login, the administrator can use the services provided by the administrator 24403 via the administrator app 24402 through the service link 24407 to execute the management functions of the analysis computing system 21100. Here, these services can, if necessary, use the service link 24407 to create, read, update, and / or delete the data stored in the system database 24406, for example, via the data storage manager 1064. The use of these services creates and updates the data stored in the system database 24406 via the service link 24407 to track the usage of the analysis computing system 21100.In addition, an administrator who executes the management functions of the analytical computing system 21100 provided by the administrator application 24402 can create one or more new user groups for which the use of the analytical computing system 21100 is done through the service link 24413 through the shared team database 24414, and can create a new database server 24415 through the service link 24412 for adding a new team database 24414 in order to optimize the performance of the database server(s) 24415. Finally, the administrator can log out from the use of the analytical computing system 21100 via the administrator application 24402 through the service link 24403 to end the current use of the analytical computing system 21100. By the logout service of the authentication 24404, the administrator's login information is updated in the system database 24406 through the service link 24409, and by the logout, the data stored in the system database 24406 is updated through the service link 24407 to track the usage status of the analytical computing system 21100. The analytical computing system 21100 may include one or more service servers 24411. These servers are adapted to host various applications and / or modules including a system module, an application module, an authentication module, a management module, a dashboard module, and an upload module. In one embodiment, the authentication and management modules enable a user to communicate with the system database 24406 and / or the team database 24414 through the administrator application 24402, for example, through one or more service links.

[0351] FIG. 25 shows an embodiment of an analysis user who executes analysis user application software 25503 using an analysis user computer 25502, and activates an analysis function provided by an analysis computing system 21100 through a service provided through a cloud platform 22223. As discussed herein, the analysis user application software 25503 may use the MUI described above to facilitate user access to the provided functions. Accordingly, an embodiment of the systematic user interface control system 1102 may be provided by a combination of the analysis user computer 25502 and the cloud platform 22223. In this embodiment, the analysis user application 25503 may be executed on the analysis user computer 25502 via a separate application installed on the analysis user computer 25502, or accessed via a web browser installed on the analysis user computer 25502, by pointing to a URL having a website portion of a service provided by the cloud platform 22223 logically organized in the application 25509, but not limited to such organization. In one practical embodiment, the first interaction between the analysis user and the cloud platform 22223 is performed using the analysis user application 25503 that requests a login service through the service link 25504, and may include a unique username and password, and / or other information such as biometric identification, and may include any or required additional authentication inputs, generally referred to as two-factor authentication, configured to be used previously by an administrator, and is performed by authentication 25505 using appropriate authentication information. Here, the login service obtains the encrypted authentication information of the user from the system database 25507 via the service link 25506, and verifies that the analysis user can access and use the analysis computing system 21100, update the data stored in the system database 25507 via the service link 25506 by logging in, and track the usage status of the analysis computing system 21100.The analyzing user can also reset the password through the analyzing user application 25503 via the service link 25504 to perform authentication 25505 when the password is forgotten or unknown. With the password reset, the data stored in the system database 25507 is updated through the service link 25506 to track the usage of the analyzing computing system 21100. The analyzing user can also configure additional authentication inputs through the analyzing user application 25503 via the service link 25504 to perform authentication 25505 and can obtain and change the configuration of the additional authentication inputs to the system database 25507 through the service link 25506. With the configuration change, the data stored in the system database 25507 is updated through the service link 25506 to track the usage of the analyzing computing system 21100. After the analyzing user is authenticated at login, the analyzing user can use the services provided by the application 25509 through the use of the analyzing user application 25503 via the service link 25508 to execute the analyzing functions provided by the application 25509. Here, these services can create, read, update, and / or delete the data stored in the team database 25511 using the service link 25510 as needed, and can also use these services to create and update the data stored in the system database 25507 through the service link 25510, and the usage of the analyzing computing system 21100 is tracked. Finally, the analyzing user can log out from the use of the analyzing computing system 21100 through the analyzing user application 25503 via the service link 25504 to end the current use of the analyzing computing system 21100. With the logout service of authentication 25505, the login information of the analyzing user is updated to the system database 25507 via the service link 25506, and with the logout, the data stored in the system database 25507 is updated through the service link 25506 to track the usage of the analyzing computing system 21100.

[0352] FIG. 26 is an embodiment of a data integration computer 26602 that launches data integration application software 26603, and executes a data integration function provided by an analysis computing system 21100 through a service provided through a cloud platform 22223 between the analysis computing system 21100 and optionally one or more computing systems (plural) that are not part of the analysis computing system 21100. As discussed herein, the data integration application software 26603 may use the MUI described above to facilitate user access to the provided functions. Thus, an embodiment of the systematic user interface control system 1102 may be provided by a combination of the data integration computer 26602 and the cloud platform 22223. The data integration application 26603 may be provided as part of the analysis computing system 21100 and / or may be provided by an analysis user or a person working with...

Claims

1. A method executed by at least one processor for navigating a hierarchical menu level path adapted to be output to a graphical user interface (GUI), the method comprising: providing, by at least one processor, a first command for a first menu of one or more user-selectable menu items to be displayed in a first portion of a user interface (UI) display; providing, by the at least one processor, a second command for a second menu of one or more user-selectable menu items to be displayed in the first portion of the UI display in response to a user selection, wherein the first menu is adapted to be displayed in a second portion of the UI display and includes one or more of previously selected menu items and non-previously selected menu items of the hierarchical menu level, and is adapted to be viewed simultaneously with the second menu in the first portion.

2. The method of claim 1, further comprising providing, by the at least one processor, a rearrangement command for rearranging the first menu to the second portion of the UI display in response to the user selection, wherein the second menu includes menu items at a subsequent level for the user to select.

3. The method of claim 2, wherein the menu items at the subsequent level include one or more user-selectable menu items of at least one hierarchical menu level lower than the first menu.

4. The method of claim 2, wherein the menu items at the subsequent level include one or more user-selectable menu items at two or more hierarchical menu levels lower than the first menu.

5. The method of claim 1, wherein the non-previously selected menu items include previously navigated hierarchical menu levels.

6. The method of claim 1, wherein the first portion includes an active portion including one or more ongoing user-selectable menu items, and the second portion includes a history portion including menu items previously available to the user.

7. The method of claim 1, wherein the first portion and the second portion are adapted to be displayed in a first visual orientation and a second visual orientation, respectively.

8. The method according to claim 7, wherein the second visual orientation is substantially orthogonal to the first visual orientation.

9. The method according to claim 7, wherein the first visual orientation is a vertical orientation and the second visual orientation is a horizontal orientation.

10. The method according to claim 7, wherein the first visual orientation is configured to provide one or more user-selectable menu items in one or more of a vertical orientation, a horizontal orientation, or a concentric orientation.

11. The method according to claim 7, wherein the second visual orientation is configured to provide user-selectable menu items in one or more of a vertical orientation, a horizontal orientation, or a concentric orientation.

12. The style adapted to display the menu item is (a) being the selected menu item, (b) having a more central position within the list as compared to other menu items in the list, (c) being available or unavailable to the user, (d) including one or more characters input by the user, and (e) being part of an advanced context menu, based on one or more attributes selected from the group consisting of: The method according to claim 1.

13. The style adapted to display the menu item is (a) highlighting a menu item that is one or more of being the selected menu item, positioned within a decision-making zone, or available to the user, and (b) making a menu item that is one or more of not being the selected menu item, positioned away from the decision-making zone, or unavailable to the user, less prominent. The method according to claim 12, including one or both of the above.

14. The method according to claim 13, wherein the menu item is adapted to be highlighted on the UI display by one or more of highlighting, bolding, enlarging, underlining, or positioning as compared to other menu items.

15. The method according to claim 13, wherein the menu item is adapted to be made less prominent on the UI display by one or more of lightening, shrinking, or positioning as compared to other menu items.

16. The method according to claim 13, wherein the decision-making zone is adapted to be displayed in a centrally located area.

17. The method according to claim 1, wherein the first and second menus are adapted to be displayed on a background, and the background is adapted to be displayed in a manner contrasting with the first and second menus.

18. The method according to claim 1, wherein the second portion is adapted to be displayed over a region smaller than the first portion.

19. The method according to claim 7, wherein the first visual orientation is one or more of parallel, orthogonal, perpendicular, horizontal, and concentric with respect to the second visual orientation.

20. The method according to claim 1, wherein each of the steps of providing is performed by the processor by executing a computer application stored in a machine.

21. The method according to claim 20, wherein the computer application includes an application for operating, designing, executing, reviewing, measuring, or analyzing an experiment.

22. The method according to claim 21, wherein the experiment includes one or more assays.

23. The method according to claim 21, wherein the experiment includes one or more electrochemiluminescence assays.

24. The total number of menu items to be displayed, (a) the frequency with which the menu item was previously selected while the user was logged into their account, (b) the frequency with which the menu item was previously selected while at least two users were logged into an account, (c) the frequency with which the menu item was previously selected while the user was logged into an account associated with multiple accounts, (d) the frequency with which the menu item was previously selected while at least two users were logged into one or more accounts associated with multiple accounts, (e) the frequency with which any user previously selected the menu item while logged into any account, and (f) the frequency with which any user previously selected the menu item while logged into any account associated with multiple accounts, further comprising providing a restriction command that restricts the total number of menu items to be displayed based on at least one of the criteria.

25. The method according to claim 24, wherein the plurality of accounts of elements (c), (d), and (f) are accounts associated with a team, and the user is a team member of the one or more teams associated with the plurality of accounts.

26. (a) A menu item designated as unavailable in the current module, (b) A menu item designated as unavailable to the user, (c) A menu item designated as unavailable to a set of users, (d) A menu item designated as unavailable to a specific machine storing the one or more copies of the computer application, (e) A menu item designated as unavailable to a set of machines, where each machine stores one or more copies of the computer application, further comprising providing an exclusion command to exclude from being displayed a menu item based on at least one of the criteria. The method according to claim 20.

27. The method according to claim 24, wherein the frequency is determined over a defined period.

28. The method according to claim 24, wherein the frequency is 50% or more.

29. The method according to claim 24, wherein the frequency is 80% or more.

30. The method according to claim 1, wherein the first and second menus are adapted to display a total of less than 7 user-selectable menu items at any given time.

31. The method according to claim 17, wherein the background comprises pixels, and at least 75% of the pixels are of a single color.

32. The method according to claim 17, wherein the background comprises pixels, and at least 75% of the pixels are black.

33. Further comprising providing a third command for a third menu of one or more user-selectable menu items to be displayed in a third portion of the UI display, the third menu being adapted to be viewed simultaneously with the first and second portions of the UI display. The method according to claim 2.

34. Further comprising providing a third command for a third menu of user-selectable menu items to be displayed in the first portion of the UI display in response to a user selection from the second menu. The method according to claim 1, wherein one or more of the menu items selected in the past and the menu items not selected in the past at the hierarchical menu level from the second menu are displayed in the second portion and adapted to be viewed simultaneously with the first portion.

35. The method according to claim 34, wherein the second portion further includes a subsequent menu, and the subsequent menu is selected from among at least one lower hierarchical menu level of one or more of the first menu, the second menu, and the third menu, and includes one or more of the sub-menu items selected in the past and the subsequent menu items not selected in the past.

36. A system for navigating a path of a hierarchical menu level adapted for output to a graphical user interface (GUI), the system comprising: at least one processor; a user input device; a computer-readable storage medium configured to store a computer application, wherein the at least one processor is configured to execute instructions of the computer application to: provide a first command for displaying a first menu of one or more user-selectable menu items in a first portion of a user interface (UI) display; in response to a user's selection, provide a second command for displaying a second menu of one or more user-selectable menu items in the first portion of the UI display; A system, wherein the first menu is adapted to be displayed in a second portion of the UI display, includes one or more of the menu items selected in the past and the menu items not selected in the past at the hierarchical menu level, and is adapted to be viewed simultaneously with the second menu in the first portion.

37. A non-transitory computer-readable medium storing computer instructions that, when executed by a processor, cause the processor to implement a method for navigating a path of a hierarchical menu level adapted for output to a graphical user interface (GUI), the method comprising: Providing a first command for a first menu among one or more user-selectable menu items to be displayed in a first portion of a user interface (UI) display; In response to a user's selection, providing a second command for a second menu among one or more user-selectable menu items to be displayed in the first portion of the UI display, A non-transitory computer-readable storage medium, wherein the first menu is adapted to be displayed in a second portion of the UI display and includes one or more of the previously selected menu items and the previously unselected menu items of the hierarchical menu level, and is adapted to be viewed simultaneously with the second menu in the first portion.

38. A method executed by at least one processor for navigating a path of a hierarchical menu level adapted to be output to a graphical user interface (GUI), the method comprising: Providing, by at least one processor, a first command for a first menu among one or more user-selectable menu items to be displayed in a first portion of a user interface (UI) display; In response to a user's selection, providing, by the at least one processor, a second command for a second menu among one or more user-selectable menu items to be displayed in the first portion of the UI display; Providing, by the at least one processor, an advanced context menu adapted to be displayed 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 the menu currently displayed in the first portion based on one or more of (1) the most frequently used available menu items, (2) the results or importance to the user, (3) the options typically made by the user, or (4) the options typically made in the industry, and further, the advanced context menu is adapted to display the remaining available items from that menu. The first menu is adapted to be displayed in a second portion of the UI display, includes one or more of the menu items selected in the past and not selected in the past of the hierarchical menu level, and is adapted to be viewed simultaneously with the second menu in the first portion. Further, the second portion is adapted to display at least one menu item from among one or more previously navigated menu levels and subsequent menu levels to provide a visual representation of (1) the user's previous traversal of the menu hierarchy and (2) future menu items that can be selected thereafter. Furthermore, the first portion is an active portion of the UI display that is consistently displayed within the same region of the UI display and is adapted to optimize the user's concentration while interacting with the UI display.

39. A method executed by at least one processor for navigating a path of a hierarchical menu level adapted to be output to a graphical user interface (GUI), the method comprising: providing, by at least one processor, a first command for a first menu of one or more user-selectable menu items to be displayed in a first portion of a user interface (UI) display; providing, by the at least one processor, a second command for a second menu of one or more user-selectable menu items to be displayed in the first portion of the UI display in response to a user's selection; providing, by the at least one processor, a permission command, the permission command being adapted to manage one or more of a level of access of a user and a team, a level of security, or a level of control, the level of access being adapted to be assigned based on one or more of a role, a user, a team, an account, an instrument, a device, or a device. The first menu is adapted to be displayed in a second portion of the UI display, includes one or more of the menu items selected in the past and not selected in the past of the hierarchical menu level, and is adapted to be viewed simultaneously with the second menu in the first portion. Furthermore, the second portion is adapted to display at least one menu item from among one or more previously navigated menu levels and subsequent menu levels, and to provide a visual representation of (1) a previous traversal of a user of the menu hierarchy, and (2) future menu items that may subsequently be selected. Furthermore, the first portion includes two to five subsections of one or more user-selectable menu items, these menu items being divided among these subsections, and the subsections being adapted to be displayed so as to create an association between the menu items from each of the respective subsections. Claim 40 A method executed by at least one processor for navigating a path of hierarchical menu levels adapted to be output to a graphical user interface (GUI), the method comprising: providing, by at least one processor, a first command for a first menu of one or more user-selectable menu items to be displayed in a first portion of a user interface (UI) display; providing, by the at least one processor, a second command for a second menu of one or more user-selectable menu items to be displayed in the first portion of the UI display in response to a user selection; providing, by the at least one processor, an output in response to a received response, the output being adapted to be transmitted to a device communicatively connected to the processor and to command the device to perform a physical movement or to undergo a physical transformation; the first menu being adapted to be displayed in a second portion of the UI display, including one or more of the menu items selected in the past and not selected in the past of the hierarchical menu level, and being adapted to be viewed simultaneously with the second menu in the first portion. Furthermore, the at least one processor is adapted to receive benchmark inputs from one or more users, accounts, or teams, the set of benchmark inputs is adapted to collaboratively solve one or more problems either sequentially or in parallel, and further, each of the benchmark inputs is adapted to be based on one or more of (a) a module, (b) a problem or sub - problem to be solved, (c) a device, (d) a physical location, (e) a tool, (f) an instrument, or (g) an apparatus. Furthermore, the at least one processor is adapted to notify the one or more users, accounts, or teams of results derived from one or more of the received benchmark inputs. A method. Claim 41 A method executed by at least one processor for navigating a hierarchical menu - level path adapted to be output to a graphical user interface (GUI), the method comprising: Providing, by at least one processor, a first command for a first menu of one or more user - selectable menu items to be displayed in a first portion of a user interface (UI) display. In response to a user's selection, providing, by the at least one processor, a second command for a second menu of one or more user - selectable menu items to be displayed in the first portion of the UI display. The first menu is adapted to be displayed in a second portion of the UI display, and includes one or more of the previously selected menu items and the not - previously - selected menu items at the hierarchical menu level, and is adapted to be viewed simultaneously with the second menu in the first portion. Furthermore, the second portion is adapted to display at least one menu item from one or more of the previously navigated menu levels and subsequent menu levels, the menu items within a single menu level are adapted to be linearly displayed, and the previously navigated menu levels and subsequent menu levels are adapted to be displayed in a nested format. Furthermore, the first portion includes only the items of a single menu at a given point in time. Furthermore, a method, wherein the first portion includes two to five subsections of one or more user-selectable menu items, these menu items are divided among these subsections, and the subsections are adapted to be displayed so as to create an association between the menu items from each of the respective subsections.

Images