Graphical user interface system

Abstract

Systems, methods, and apparatuses are provided for aggregating information suitable for output to a graphical user interface. The method can include providing a first menu command to display a first menu having one or more user-selectable menu items on a menu portion of an aggregation user interface (AUI) display, and providing a content command to display content on the menu portion of the AUI display in response to a user's selection. The method can further aggregate information related to the one or more user-selectable menu items in the first menu and adapt the information to be displayable on a content portion of the AUI display. By aggregating new information and displaying it on a graphical user interface, a user can quickly and efficiently view and manipulate content in a more organized manner.

Description

[0001] Cross-reference of related applications

[0002] This application claims the benefit of prior U.S. Provisional Patent Application No. 62 / 954,052, filed December 27, 2019, which is incorporated herein by reference in its entirety for all purposes.

[0003] The following patent documents are incorporated herein by reference and incorporated in their entirety: U.S. Patent Application No. 16 / 513,526, entitled "Graphical User Interface System," filed July 16, 2019; PCT Application No. PCT / US2019 / 042079, entitled "Graphical User Interface System," filed July 17, 2019; and U.S. Design Patent Application No. 29 / 675,777, entitled "Display Screen with Graphical User Interface," filed January 4, 2019. Technical Field

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

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

[0006] Generally, computer systems and / or applications utilize a series of menus or the like presented to a user for receiving input to perform the functions of the computer system and / or application. As the user selects options or makes selections from a list of menu items, the computer system and / or application can perform its functions based on the selected options, and / or present another list of menu items (e.g., a sub-menu list of items depending on the selected option). For example, the computer system and / or application continues to perform its menu-driven functions until the functions are completed. In such menu-driven systems, it is often the case that the previously selected options on which the present functions of the computer system and / or application depend are not visible on the user interface. Thus, for example, the present point in the processing of the computer system and / or application cannot be seen in terms of the path of menu items taken. Furthermore, the path taken and the unselected options in the path are not visible on the user interface. Thus, an improved user interface can be desired.

[0007] Laboratories, the data generated by the instrument is stored as a data file on a shared network drive for post processing and import into other electronic systems, i.e., Laboratory Information Management Systems (LIMS). Typically, these integrations require significant and time consuming software development and integration to provide the generated data to the end user. Typically, these data integrations are in a rigorous environment (e.g., 21 CFR Part 11) that requires the generated data to be stored in a manner that ensures the generated data cannot be altered by the end user. Moreover, these integrations are provided to the end user to support post processing of the generated data for supplemental analysis, reporting, and the ability to share with other end users, often referred to as collaborators. In addition, there is a desire to use the instrument and post process the generated data in a regulated, consistent, uniform, and traceable manner among a group of closely working end users to help the end users establish consistent and correct supplemental analysis and reporting. The use of the instrument to generate data for supplemental analysis and reporting typically requires the end user to use consumables (e.g., biological consumables including but not limited to reagents and analytes) with specific lot information and their samples to be tested to establish the reactions to be determined to generate the generated data with specific lot information used in the generation of the supplemental analysis and reporting. To obtain these consumables requires the purchase of the consumables from a supplier who must not only ship the physical consumables to the end user but must also provide the specific lot information of these shipped consumables so that the end user can use the consumables on the instrument and perform the desired post processing. In addition to the normal use of the instrument and related consumables, there is typically significant support functionality to ensure that the instrument and / or related consumables are always providing the best performance possible for the customer. The degree of workflow integration required to optimally perform the collective and collaborative work of the end users using the instrument is very high and is very complex requiring a simple and easy to use user interface to guide the user through all of the complexities of their analysis workflow. Therefore, there is a desire for improved analysis operation systems and user interfaces related to and including the instrument and related consumables.

[0008] Other areas outside of the instrument field face similar difficulties as previously discussed. For example, in various manufacturing settings, workflow integration, part tracking, consumable tracking, work-in-process tracking, documentation of processes and parts production, and all of the problems previously discussed related to instruments are difficult. In addition, the present application provides a solution to the area of workflow organization, prioritization, and improved consumer demand in areas such as business, office, home, travel, and leisure settings. Other examples exist and the solution disclosed in this specification is not limited to the problems discussed above. SUMMARY

[0009] A method and system can be provided for interactively guiding a user through a path of menu selections on a user interface to guide the user in using a computer application. The method is automatically performed by at least one hardware processor. In one embodiment, the method can include displaying a currently selected menu on a first portion of a user interface display.

[0010] The method can also include allowing a user to select a menu item from the currently selected menu displayed on the first portion of the user interface display and to drill down into a menu selection hierarchy based on selecting the menu item in a previous menu selection hierarchy. The method can further include displaying past selected and past unselected menu items of the drilled down hierarchy on a second portion of the user interface display, where the past unselected menu items are displayed as selectable options. The method can also include allowing a user to jump to a different path of menu options by allowing the user to select a past unselected menu item from the previously guided menu hierarchy displayed on the second portion of the user interface display. In one embodiment, the first portion and the second portion can be viewable simultaneously on the user interface display.

[0011] In another embodiment, a method for interactively guiding a user through a path of menu selections on a user interface to guide the user in using a computer application can include displaying a currently selected menu on a first portion of a user interface display. The method can also include allowing a user to select a menu item from the currently selected menu displayed on the first portion of the user interface display and to drill down into a menu selection hierarchy based on selecting the menu item in a previous menu selection hierarchy. The method can also include displaying past selected and past unselected menu items of the drilled down hierarchy on a second portion of the user interface display, where the past unselected menu items are displayed as selectable options. In one embodiment, the first portion and the second portion can be viewable simultaneously on the user interface display. In one embodiment, the graphical user interface maximizes black space by having a background of the user interface display be black, thereby saving storage and improving display speed.

[0012] In yet another embodiment, a method for interactively guiding a user through a path of menu selections on a user interface to guide the user in using a computer application can include displaying a currently selected menu on a first portion of a user interface display. The method can also include allowing a user to select a menu item from the currently selected menu displayed on the first portion of the user interface display and to drill down into a menu selection hierarchy based on selecting the menu item in a previous menu selection hierarchy.

[0013] The method can further include displaying past selected and past unselected menu items of the deeper level on a second portion of the user interface display, where the past unselected menu items are displayed as selectable options. In one embodiment, the first portion and the second portion are concurrently viewable on the user interface display. In one embodiment, at least the first portion includes a search function box, an attached first region, and an attached second region, where the first portion as a whole is scrollable and displays a currently selected menu. In one embodiment, as search term input in the search function box is detected, the first portion is divided into the attached first region and the attached second region that are individually scrollable.

[0014] In yet another embodiment, a method of interactively guiding a user through a path of menu selections on a user interface to guide the user in using a computer application, the method can include displaying a currently selected menu on a first portion of a user interface display. The method can also include allowing a user to select a menu item from the currently selected menu displayed on the first portion of the user interface display, and based on the selection of the menu item, to drill down into a level of menu selections. The method can also include displaying past selected and past unselected menu items of the drilled down level on a second portion of the user interface display, where the past unselected menu items are displayed as selectable options.

[0015] In one embodiment, the first portion and the second portion are concurrently viewable on the user interface display. In one embodiment, the currently selected menu is displayed as a graphical spin wheel of rotating selections. In one embodiment, the graphical spin wheel is rotatable from a first menu item in the currently selected menu to a last menu item in the currently selected menu, and 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 spin wheel.

[0016] In yet another embodiment, a user interface system can be provided that can include at least one hardware processor and a memory device operatively coupled to the hardware processor. The hardware processor can be operable to retrieve a currently selected menu from the memory device and display the currently selected menu on a first portion of a user interface display. The hardware processor can be further operable to allow a user to select a menu item from the currently selected menu displayed on the first portion of the user interface display and select a menu item in a previously selected menu selection layer to drill down into the menu selection layer. The hardware processor can be further operable to display past selected and past unselected menu items of the drilled down layer on a second portion of the user interface display, wherein the past unselected menu items are displayed as selectable options. The hardware processor can be further operable to allow the user to jump to a different path of menu options by allowing the user to select a past unselected menu item from the previously guided menu layer displayed on the second portion of the user interface display. In an embodiment, the first portion and the second portion can be viewable simultaneously on the user interface display.

[0017] In another embodiment, a method for guiding a path through a hierarchical menu layer adapted for output to a graphical user interface (GUI) is provided for execution by at least one processor. The method includes providing, by at least one processor, a first command for displaying a first menu of user selectable options on a first portion of a user interface (UI) display; and providing, by the at least one processor, a second command for displaying a second menu of user selectable options on the first portion of the UI display as a user selects. The second menu is adapted for display on a second portion of the UI display and includes one or more of past selected menu items and past unselected menu items of the hierarchical menu layer and is adapted to be viewable simultaneously with the first portion.

[0018] In another embodiment, a non-transitory computer readable medium having stored thereon computer instructions, which when executed by a processor, cause the processor to perform a method for guiding a path through a hierarchical menu layer adapted for output to a graphical user interface (GUI). The method includes providing a first command for displaying a first menu of user selectable options on a first portion of a user interface (UI) display; and providing a second command for displaying a second menu of user selectable options on the first portion of the UI display as a user selects. The second menu is adapted for display on a second portion of the UI display and includes one or more of past selected menu items and past unselected menu items of the hierarchical menu layer and is adapted to be viewable simultaneously with the first portion.

[0019] In another embodiment, a system for guiding a path through a hierarchy of menu levels adapted to be output to a graphical user interface (GUI) is provided. The system includes at least one processor; a user input device; and a computer-readable storage medium configured to store a computer application, wherein the at least one processor is configured to execute instructions of the computer application. The at least one processor can execute instructions for providing a first command for displaying a first menu of user-selectable options on a first portion of a user interface (UI) display; and providing a second command for displaying a second menu of user-selectable options on the first portion of the UI display as a user's selections are made. The second menu is adapted to be displayed on a second portion of the UI display and includes one or more of past selected menu items and past unselected menu items of the hierarchy of menu levels and is adapted to be viewable concurrently with the first portion.

[0020] A computer-readable storage medium storing a program of instructions executable by a machine to perform one or more methods described in this specification can also be provided.

[0021] Other features and advantages of various embodiments are detailed below in conjunction with the attached drawings. BRIEF DESCRIPTION OF DRAWINGS

[0022] Figure 1 Method for displaying an interactive item on a user interface display for computer-user interaction in an embodiment.

[0023] Figures 2A-2O Illustrating an example graphical user interface display in an embodiment.

[0024] Figure 2P Illustrating an example of a methodical user interface including a high-level context menu in accordance with an embodiment.

[0025] Figure 3 Flowchart illustrating a method for displaying an interactive item on a user interface display for computer-user interaction in another aspect.

[0026] Figure 4 Flowchart illustrating a method for determining a user login interface of a system in an embodiment.

[0027] Figure 5 Flowchart illustrating a method for displaying a launch user interface screen display in an embodiment.

[0028] Figure 6 Diagram illustrating a workflow for defining a method screen in an embodiment.

[0029] Figure 7 FIG. 1 illustrates a diagram of a workflow of a user interface for selecting an assay method in an embodiment.

[0030] Figure 8 FIG. 2 illustrates a flowchart of a workflow of a user interface displayed for defining a sample in an embodiment.

[0031] Figure 9 FIG. 3 illustrates a flowchart of a workflow of a user interface displayed for confirming execution of a definition in an embodiment.

[0032] Figure 10 FIG. 4 illustrates a flowchart of a workflow of a user interface displayed for notifying a user that a job is complete in an embodiment.

[0033] Figure 11 FIG. 5 illustrates a flowchart of a workflow of a user interface displayed for executing / gathering options in an embodiment.

[0034] Figure 12 FIG. 6 illustrates a flowchart of a workflow of a user interface displayed for executing / preparing options in an embodiment.

[0035] Figure 13 FIG. 7 illustrates a flowchart of a workflow of a user interface displayed for executing / executing options in an embodiment.

[0036] Figure 14 FIG. 8 illustrates a flowchart of a workflow of a user interface displayed for executing / executing options in an embodiment.

[0037] Figure 15 FIG. 9 illustrates a flowchart of a workflow of a user interface displayed for executing / not executing options in an embodiment.

[0038] Figure 16 FIG. 10 illustrates a flowchart of a workflow of a user interface displayed for executing / checking options in an embodiment.

[0039] Figure 17 FIG. 11 illustrates a flowchart of a workflow of a user interface displayed for executing / checking options in an embodiment.

[0040] Figure 18 FIG. 12 illustrates elements of a graphical user interface (GUI) system in an embodiment.

[0041] Figure 19 FIG. 13 illustrates a diagram of an example computer or processing system that can implement a graphical user interface system in an embodiment.

[0042] Figure 20Figure 1 is an example screenshot of a screen displaying a graphical scroll tool that maximizes black space on the screen in an embodiment.

[0043] Figure 21 Figure 2 is a schematic illustration of a cloud analytics system in an embodiment.

[0044] Figure 22 Figure 3 is a schematic illustration of a system architecture related to a cloud analytics system in an embodiment.

[0045] Figure 23 Figure 4 is a schematic illustration of a system architecture of a cloud platform related to a cloud analytics system in an embodiment.

[0046] Figure 24 Figure 5 is a schematic illustration of an interaction between a manager computer and a cloud platform in an embodiment.

[0047] Figure 25 Figure 6 is a schematic illustration of an interaction between an analytics user computer and a cloud platform in an embodiment.

[0048] Figure 26 Figure 7 is a schematic illustration of an interaction between a data integration computer and a cloud platform in an embodiment.

[0049] Figure 27 Figure 8 is a schematic illustration of an interaction between a support user computer and a cloud platform in an embodiment.

[0050] Figure 28 Figure 9 is a schematic illustration of an interaction between a support data integration computer and a cloud platform in an embodiment.

[0051] Figure 29 Figure 10 is a schematic illustration of an interaction between a consumable information upload computer and a cloud platform in an embodiment.

[0052] Figure 30 Figure 11 is a schematic illustration of an interaction between an account information upload computer and a cloud platform in an embodiment.

[0053] Figure 31 Figure 12 is a schematic illustration of an interaction between an instrument information upload computer and a cloud platform in an embodiment.

[0054] Figure 32 Figure 13 is a schematic illustration of an interaction between a co-operating instrument computer and a cloud platform in an embodiment.

[0055] Figure 33A Figure 14 is a schematic illustration of an interaction between a personal operating instrument computer and a cloud platform in an embodiment.

[0056] Figure 33B Figure 15 is a schematic illustration of a workflow for an instrument computer and a cloud platform in an embodiment. Figure 33A Figure 16 is a schematic illustration of a workflow for an instrument computer and a cloud platform in an embodiment.

[0057] Figure 34A A first portion of a software architecture for cloud platform services in an embodiment is illustrated.

[0058] Figure 34B A second portion of a software architecture for cloud platform services in the illustrated embodiment is illustrated. Figure 34A

[0059] Figure 35A

[0060] Figure 35B A case of mapping business entities to accounts using the analytics system in an embodiment is illustrated.

[0061] Figure 35C A logical design for team data related to plate data in an embodiment is illustrated.

[0062] Figure 35D A logical design for team data related to assay method data in an embodiment is illustrated.

[0063] Figure 35E A logical design for team data related to execution data in an embodiment is illustrated.

[0064] Figure 35F A logical design for team data related to experiment data in an embodiment is illustrated.

[0065] Figure 36A An exemplary structure for a user account for the analytics system in an embodiment is illustrated.

[0066] Figure 36B A flow for setting up a user account for the analytics system in an embodiment is illustrated.

[0067] Figure 36C A flow for instrument integration with a user account for the analytics system in an embodiment is illustrated.

[0068] Figure 36D A flow for consumable integration with a user account for the analytics system in an embodiment is illustrated.

[0069] Figure 37 A module for a manager software application in an embodiment is illustrated.

[0070] Figure 38A A flow for a manager console module in a manager APP for an account manager in an embodiment is illustrated.

[0071] Figure 38B ​​The flow of the manager console module in the manager APP in relation to team managers in an embodiment is illustrated.

[0072] Figure 38C The flow of the user login process in an embodiment is illustrated.

[0073] Figures 38D-38H Aspects of the work experience flow are illustrated. Figure 38A

[0074] Figure 38I Aspects of the high-level quick view menu in relation to the manager console module are illustrated.

[0075] Figure 39A The flow of the manager review tracking module of the manager APP in an embodiment is illustrated.

[0076] Figures 39B-39E Aspects of the manager review tracking module user interface according to an embodiment are illustrated.

[0077] Figure 40 The module of the analysis user software application in an embodiment is illustrated.

[0078] Figure 41 The flow of the analysis method module of the analysis user APP in an embodiment is illustrated.

[0079] Figure 42A The design flow of the assay method module of the analysis user APP in an embodiment is illustrated.

[0080] Figure 42B The check flow of the assay method module of the analysis user APP in an embodiment is illustrated.

[0081] Figure 43A The design flow of the experiment module of the analysis user APP in an embodiment is illustrated.

[0082] Figure 43B The check flow of the experiment module of the analysis user APP in an embodiment is illustrated.

[0083] Figures 43C-43H Aspects of the reader module user interface according to an embodiment are illustrated.

[0084] Figure 44 The flow of the review tracking module of the analysis user APP in an embodiment is illustrated.

[0085] Figure 45 The module of the collaborative instrument software application in an embodiment is illustrated.

[0086] Figure 46 ​Flowchart illustrating the operation module of the co-operating instrument APP in one embodiment.

[0087] Figure 47 Flowchart illustrating the maintenance module of the co-operating instrument APP in one embodiment.

[0088] Figure 48 Module of the personal operating instrument software application in one embodiment.

[0089] Figure 49A Flowchart illustrating the operation module of the personal operating instrument APP in one embodiment.

[0090] Figure 49A Flowchart illustrating the operation module of the personal operating instrument APP in one embodiment.

[0091] Figure 49B Flowchart illustrating the result check of the operation module of the disc reader as personal operating instrument APP in one embodiment.

[0092] Figure 50 Module of the workflow help instrument software application in one embodiment.

[0093] Figure 51 Flowchart illustrating the workflow help module of the workflow help instrument APP in one embodiment.

[0094] Figure 52 Embodiment of an operational flow for analyzing software automatic updates of a user computer.

[0095] Figure 53 Embodiment of an operational flow for analyzing software automatic updates of an instrument computer.

[0096] Figure 54 Example embodiment of a non-biological analysis use of a disclosed architecture for a software module in a gourmet chef APP.

[0097] Figure 55 Embodiment of a user experience flow through a meal planner starting from a gourmet chef APP.

[0098] Figure 56 Illustrating a system for implementing a systematic user interface according to one embodiment.

[0099] Figure 57 Illustrating a process for navigating a hierarchical menu tree via a user interface.

[0100] Figure 58 Illustrating a first embodiment of a mobile device for aggregating information on a mobile-based user interface display depicted in a portrait orientation.

[0101] Figure 59A schematic illustration of a mobile device depicting a standard content view. Figure 58 a second embodiment of a mobile device schematically illustrated therein.

[0102] Figure 59B schematic illustration of a menu portion Figure 59A a detailed view of a menu portion schematically illustrated therein.

[0103] Figure 60 schematic illustration of a mobile device depicting a detailed content view. Figure 58 a third embodiment of a mobile device schematically illustrated therein.

[0104] Figure 61 a first embodiment of a mobile device for aggregating information on a mobile-based user interface display schematically illustrated in a landscape orientation.

[0105] Figure 62 an alternative embodiment of a mobile device for aggregating information on a mobile-based user interface display.

[0106] Figure 63 a first embodiment of a method for aggregating information on a mobile-based user interface display.

[0107] Figure 64 a first embodiment of a system and computer readable medium for aggregating information on a mobile-based user interface display.

[0108] Figure 65 a first embodiment of an aggregation computing system for implementing a system, method and apparatus for aggregating information on a mobile-based user interface display.

[0109] Figure 66 schematic illustration of a mobile device depicting a detailed content view. Figure 65 a detailed view of an aggregation computing system schematically illustrated therein. DETAILED DESCRIPTION

[0110] The embodiments described in this specification provide technical solutions to various technical problems via improvements to the prior art and establishment of entirely new technologies. The technical problems addressed by the embodiments discussed in this specification include inefficient conventional user interfaces and difficulty integrating different portions of a processing workflow.

[0111] The practical application of the technical solutions discussed in this specification to improve the user interface regarding the problems of conventional user interfaces in terms of user inefficiency, accuracy, repeatability, and computational inefficiency. The technical solutions provided in this specification improve each of these aspects by using the user interface methods and techniques of the present invention. In particular, the technical solutions provided by the user interface disclosed in this specification provide a more efficient guided menu system approach for users for complex processes.

[0112] User interfaces implemented for electronic devices for human interaction or communication typically include a series of menus or similar selection options (e.g., a series of hierarchical options) that are selectable by a user to cause a device, such as a computer, to perform a desired function. In some embodiments, the amount of information presented to the user or the number of menu selections can become overwhelming as the type of application used. The wide array of available menu options can cause the user to try different selections or navigate to different menu selection hierarchies before finding the correct or desired series of selections. In some cases, only about 10% of the user interface selections and functional options available to the user are used. However, with all 100% of the options presented, the user can have difficulty deciding where to navigate to find the 10% that is relevant to the user. Moreover, because the selected menu selection affects the next selection made along the menu selection path, the user switching between selections will mean that the user is also navigating to many different paths from the options. The trial and error that can occur during user interface navigation due to scrolling and paging through many different options can be time consuming, costly, and inefficient.

[0113] The systems, methods, and techniques in the present invention can provide a user interface to guide the user to the selected selection option via the user interface display or another presentation device with less time to find the correct selection. As such, there are fewer attempts at incorrect selections and less time spent by the user navigating to accomplish the desired computational function or goal. In aspects, the user interface of the present invention can present the user with a limited number of options from all available options in a particular way and guide the user through these options to simplify the operation and more effectively provide the user with the ability to focus on the desired computational function. In another aspect, the user interface of the present invention can more directly connect the user to the application.

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

[0115] Embodiments and technical solutions provide practical applications of certain design principles to help guide users through the menus and systems described in this specification. Design principles embodied in this specification include, for example, minimizing the number of guided menus and / or selections a user must make at any one time.

[0116] A further design principle includes providing a user with a single new selection at any particular time, while providing the user with the option to easily revisit previous selections. This principle can be implemented via a two-part display system. A current-part can be configured to display the current user selection, while a history-part can be configured to display information about previous selections. Together, the current-part and the history-part can provide a "direct workflow mode." The current-part, which presents the current user selection, can be strictly limited in the number of menu items displayed, for example, seven, five, three (or any other number), while other potential items in the same menu are displayed elsewhere. Previously selected selections (and the menus from which the selections were made) can be displayed to the user in a nested fashion or a stacked fashion. A series of nested previously guided menus can be presented in a matryoshka fashion, with each previously selected menu item being expanded in a displayed submenu. The nested or stacked previously selected menu items can also provide a Breadcrumb trail that illustrates to the user the path taken to arrive at the current menu. In some embodiments, an indicator column can be provided to draw the user's attention to the previously selected menu items. For example, when the previously selected menu items are arranged in a stacked fashion, an indicator column can be used to help vertically align one or more menus and / or menu items. For example, an indicator column (located below the "add / delete" item) can help draw the user's attention and align the following items: "manage," "legal," and "add / delete." In some embodiments, the indicator column can be depicted like a watch hand. In addition, the indicator column can include a color-coded status (e.g., red for an error status and blue for a non-error status). In some embodiments, the color-coded status can be depicted within a portion of the indicator column by illuminating a pixel of one or more colors. In one example, the color-coded status can be provided within the middle portion of the indicator column, but this status can also be displayed in other portions of the UI display.

[0117] Embodiments of this specification maintain a consistent appearance throughout the use of the interface regardless of the work or process to be accomplished, for example, by maintaining a consistent screen location for menus, so the user does not have to search for the menu in different locations. In other words, the relevant menu will move to the current-part of the screen to draw the user's attention when needed. In embodiments, the current-part of the screen remains in a top-to-bottom and left-to-right orientation. In other embodiments, the size and shape of the menu interface will change depending on the device or screen on which it is viewed. The menu can be spread horizontally on wider screens and / or vertically on taller / narrower screens.

[0118] Embodiments discussed in this specification provide improvements in efficiency and accuracy by enhancing several aspects of the user experience to improve user productivity. The user interfaces described in this specification will focus the user on the most likely use case while minimizing the distraction caused by less utilized options. This focus allows the user interface to minimize visual distraction and focus the user on the most relevant menu selections. The user interfaces described in this specification seek to guide the user through the user interface in different steps while eliminating the point of frustration where the user might wonder what to do next. In embodiments of this specification, the user is kept transparent to the guided path through the interface system to easily select alternative options or exit the current menu. Throughout the process of using the user interface, the user can have the option to view alternative paths throughout the process in a non-distracting manner. Thus, a core function of the user interface software provided in this specification is to reduce the total amount of information presented to the user at any one time while increasing the total amount of relevant information presented to the user at any one time. In the case of low use examples, other information and options are still provided in a non-distracting presentation. Such decisions regarding the information presented through the user interface at any particular time can be guided in advance through predetermined menu workflows and / or can be influenced and updated through analysis of previous user actions and selections.

[0119] Computer functionality can also be improved via embodiments provided in this specification. For example, by focusing on a limited number of options, resource usage in performing the user interface can be reduced, which can involve devices (e.g., user devices and / or server devices). For example, memory usage, processor resource usage (e.g., central processing unit (CPU) usage), persistent storage usage such as hard drives, bandwidth required for communication between devices (e.g., device-to-device, device-to-server, server-to-server) can be reduced. The ability to directly guide to or reach the correct selection or selection path (e.g., without multiple attempts and errors in guidance) can also increase the efficiency of communication between devices and servers, for example, reducing internet communications and the costs associated with such communications.

[0120] Further embodiments discussed in this specification relate to integration of various process workflow aspects. As discussed in this specification, a "process workflow" can relate to an instrument (including a biological instrument) test workflow, a manufacturing workflow, an analysis workflow, and / or any workflow that can relate to one or more controlled devices that are at least partially controlled by one or more computing systems. In further embodiments, a process workflow consistent with embodiments discussed in this specification can include the use of one or more consumables.

[0121] An operating system consistent with the user interface and process workflow management systems discussed in this specification can include various architectures, including but not limited to a single-computing device system, a desktop computing system, a notebook computing system, a tablet computing system, a mobile device computing system, a thin-client computing system, a cloud-oriented 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, or any other appropriate computing system.

[0122] The process interface systems described in this specification increase user accuracy, efficiency, and satisfaction by providing a user interface that is faster to use, reduces the time to find the correct menu item, reduces the selection of incorrect menu items, and reduces the overall workflow time. In contrast to traditional systems that can have immediate access to 100% of the options (of which only 10% are frequently used), the systems described in this specification can provide only the frequently used ones (e.g., 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 95+%, 70-95+%, 80-95+% of usage examples). Instead, the solutions provided in this specification serve to increase computing efficiency, reduce memory usage, and reduce the utilization of CPU, hard drive, power, and communication resources.

[0123] The user interface systems discussed in this specification can 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-controlled system, and / or any other type of visual user interface. In general, the user interface systems consistent with the embodiments of this specification can be referred to as a “systemized user interface (MUI).” The MUI can 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-controlled system, and / or any other type of visual user interface. Although certain principles discussed in this specification are discussed specifically with respect to, for example, a GUI, this is not a limitation, as the principles discussed in this specification can be equally applied to other interface systems.

[0124] The MUIs described in this specification refer to "displays," "interfaces," and "user interfaces." As used in this specification, unless otherwise specified, the terms "display," "interface," and "user interface" refer to text, pictures, visual elements, interactive elements, and any other visual aspect presented or displayed on a screen, projection, or other visual display hardware. Thus, it should be appreciated that "display" and "interface" as used in this specification can be provided via any type of visual display hardware, screen, and / or projector. For convenience, menus, interfaces, and other visual items are referred to in this specification as being viewed on or displayed by the MUI. It should be appreciated that this reference indicates that the MUI is providing a visual presentation of the hardware device as discussed in this specification.

[0125] As described in more detail below, the user interface systems described in this specification can use various visual elements to present menu items. For example, the visual elements can include a vertical "scroll wheel" or a horizontal scroll wheel that rotates through various menu items. As described in this specification, "scroll wheel" is used as a visual element to refer to a way of providing the user with highlighted (emphasized) and unhighlighted (dimmed) options. The scroll wheel visual element can be understood as a virtual scroll wheel with a rim facing the user and a plurality of menu items disposed on the rim of the virtual scroll wheel. The scroll wheel visual element can or can not include any visual indicator of the presence of the scroll wheel. The scroll wheel visual element can provide the user with the option of highlighting in an attention-grabbing manner (i.e., the portion of the scroll wheel that is "closest" to the user), while other dimmed options are presented in a manner that does not grab attention. The highlighted menu item can be brightly displayed in a different color, in a different font, in a larger font, or in other visual indicia that draw attention. As the virtual scroll wheel is rotated, the currently highlighted menu item is rotated (clockwise or counterclockwise) from the user, and the currently dimmed menu item becomes the new highlighted option. In embodiments, the dimmed menu items closest to the highlighted menu item can be displayed to draw more attention than the dimmed menu items farther from the highlighted menu item. For example, the menu items can decrease in size or brightness based on their distance from the currently highlighted menu item. As the "scroll wheel" is "rotated," the dimmed menu items can visually fade. In this way, the virtual scroll wheel provides the user with the sensation and perception that the menu items are all arranged on an actual scroll wheel. The visual elements can further include a horizontal or vertical slider axis that slides through various menu items. Likewise, for the scroll wheel as discussed above, the slider axis can be used to provide a highlighted menu item and dimmed or less emphasized menu items. In embodiments, the slider axis can be distinct from the scroll wheel in that as the slider is slid through the options in the slider axis, the dimmed menu items do not disappear from view. Further embodiments of scroll wheels and slider axes are discussed further in this specification with respect to particular embodiments.

[0126] As discussed in the present specification, menu items can be different "selected," "highlighted," and / or "clicked." As used in the present specification, a "highlighted" menu item means, for example, that a "highlight" option is displayed to the user, that the highlighted menu item is the center of the scroll wheel, and / or that the menu item is visually highlighted to the user. Highlighting can include changing the color, size, font, etc. of the menu item to visually highlight the menu item to the user. A "dimmed" user option can include changing the color, size, font, etc. of the menu item to visually dim the menu item to the user. Menu items can be highlighted or dimmed (e.g., presented as not available for selection or editing by the user) as a result of user action (e.g., via clicking a mouse, touching a touch screen, rotating a scroll wheel, etc.) and / or can be highlighted or dimmed based on action of the interface (e.g., providing a highlighted default option).

[0127] As used in the present specification, a "selected" menu item means that the menu item has been selected by the user and that the user interface has taken one or more menu steps as a result of the selection. A "selected" menu item causes the computer system to execute computer instructions to advance the menu, unlike a simple "highlighted" menu item. For example, a "selected" menu item can cause a new menu to be displayed based on the selection. The selected menu item can be highlighted after selection, but highlighting a menu item does not necessarily include selecting the menu item.

[0128] In some embodiments, menu items can be selected or highlighted via clicking the menu item. As used in the present specification, "clicking" refers to a user action that indicates or selects a menu item using an interface device (e.g., a mouse, a touch screen, etc.). As used in the present specification, a "clicked" menu item is different from a "selected" menu item. Clicking refers to a user action that indicates a menu item, while selecting refers to a computer function that selects a menu item.

[0129] In some embodiments of systems according to this disclosure, menu items can be selected via clicking. Clicking a menu item can cause the system to advance to a next series of menu items. In other aspects of the disclosed systems, clicking a menu item is used to highlight the menu item, but does not select the menu item to cause the system to advance to a next menu item.

[0130] Menu items can be described in the present specification as "selectable." A "selectable" menu item refers to a menu item with which a user can interact via selection or highlighting. A selectable menu item can be displayed in a manner that indicates that it is selectable, such as by changing color, highlighting, font, etc. Menu items can be described in the present specification as "non-selectable." A "non-selectable" menu item refers to a menu item with which a user cannot currently interact via selection or highlighting. A non-selectable menu item can be displayed in a manner that indicates that it is not selectable, such as by changing color, highlighting, font, etc.

[0131] A menu item can also be described as "past selected" and "past unselected." A "past selected" menu item refers to a menu item that was selected to reach the current menu interface display. It does not require the user to have actively selected the "past selected" menu item. Under programmed defaults, if the system takes the user to a menu level below the top level, the menu item or selection in the current path can be indicated as "past selected" even if the user did not actively select it in the current session. A "past unselected" menu item refers to a menu item that was not selected to reach the current menu interface display. For example, where the user has selected a first menu item and not selected a second menu item, the system can continue to display subsequent menus or submenus with the selection of the first menu item in the active portion of the MUI. In the history portion of the MUI, the system can display the first menu item as a past selected menu item and the second menu item as a past unselected menu item. The past unselected menu item can be displayed as selectable.

[0132] For example, a user can scroll a thumbwheel or rotate a scroll wheel to navigate through various menu items. The user can fix the scroll wheel or thumbwheel so that a particular menu item is brightly displayed. In an embodiment, the particular menu item can require further user interaction (e.g., a single click or double click) to "select" to cause the MUI to present a new set of menu items or submenu items with the selection. In this embodiment, the user rotates the scroll wheel or thumbs the thumbwheel to move the desired menu item to the brightly displayed highlighted menu item. The user then clicks, double clicks, or otherwise indicates the brightly displayed menu item as a selection to display the next menu or submenu. In an embodiment, the particular menu item that is brightly displayed can be simultaneously "selected." In this embodiment, rotating the scroll wheel or thumbing the thumbwheel to move the desired menu item to the brightly displayed highlighted menu item will cause the associated submenu to be displayed.

[0133] As discussed throughout this specification, selecting or brightly displaying a menu item can occur by directly selecting (i.e., clicking, touching, etc.) on the menu item, whether it is a scroll wheel, thumbwheel, and / or item list, whether it is a highlighted or dimmed menu item. Selecting or brightly displaying a menu item can also occur with the user manipulating various visual elements to move the menu item to a position to be brightly displayed or selected. For example, the user can rotate the scroll wheel or move the thumbwheel before a particular menu item is highlighted and brightly displayed. The manipulation of the visual elements and / or the direct selection can be accomplished through the use of any suitable user input device, including touchscreens, mice, keyboards, directional keys, eye gaze detection systems, motion detection systems, gesture detection systems, etc.

[0134] Features of embodiments of the interface can be referred to as "first portion" and "second portion." These terms refer to specific portions of the user interface that are displayed at different times and do not require a specific location on the screen to be fixed. As used in this specification, the "first portion" can also be referred to as the "current portion." The "first portion" or "current portion" refers to the portion of the MUI that displays the current or most recent set of menu items. The "first portion" and "current portion" are used interchangeably in this specification. The "second portion" can also be referred to as the "history portion." The "second portion" or "history portion" refers to the portion of the interface that displays previously viewed menus and previously selected and unselected menu items. The "second portion" and "history portion" are used interchangeably in this specification.

[0135] Figure 1 A method of guiding a user through menu selections on a user interface in an embodiment is illustrated schematically. The method can be performed automatically by at least one hardware processor. The method facilitates movement of a user in a system by asking questions, displaying one or more selections made by the user in the past along with other selections that were not selected, while delving into the other selections based on the initial selections. As used in this specification, "asking questions" refers to providing one or more menu selections for the user to choose. The method allows the user to continue along a path or jump to a different path, go back to a selection made in one or more previous steps, or go back to the most recent point at which the user made a selection. In an embodiment, the user interface presents and allows the user to view past or previous selections that have been made and not made, for example, in each step of a path, regardless of where the user is on the path, all on the same screen. For example, the user interface displays an outline of the user's menu selection path, where the unselected menu items are also included. The user interface method allows for more efficient guidance, directing the user to proceed along a path, allowing the user to view the path the user is taking, and allowing the user to deviate from a user-set path to a different path. The user interface method allows the user to be able to view the path of pages backwards and forwards, and where the user is going and where the user can go.

[0136] As discussed in this specification, menus are presented as a series of hierarchical menu trees. Each level of a menu tree contains a plurality of menus that lead to other menus. Thus, a first level of a menu tree includes a plurality of first menus, a second level of a menu tree includes a plurality of second menus, a third level of a menu tree includes a plurality of third menus, and so on. This structure continues for levels of menus. In some discussions in this specification, the first menus are simply referred to as menus, and subsequent levels of menus in the tree are referred to as submenus, sub-submenus, and so on. Sometimes, multiple levels of menus under a current menu can be referred to collectively as submenus. Thus, submenus of a first menu can include a plurality of second menus, a plurality of third menus, a plurality of fourth menus, a plurality of fifth menus, and so on. An example of a hierarchical menu tree structure is illustrated in FIG. 1. Figure 2KThe numbered menus are illustrated in the flowchart of FIG. 6. As used in this description, each level is referred to as a "menu" even when a textual menu is not presented to the user with respect to a hierarchical menu tree. For example, a "menu" can present only an "execute" button to implement processing designed in other parts of the menu. For example, another "menu" can present a tutorial.

[0137] Each of the numbered menus includes a plurality of menu items or options, each item or selection pointing to a new menu at a lower level. Thus, the items in the first menu can each point to one of a plurality of second menus. In some embodiments, menu levels can be skipped. For example, an option in the first menu can point to one of a plurality of third menus.

[0138] In embodiments, each menu can also include additional information displayed in the MUI. The additional menu information can provide user information about the menu items and / or general text about the menu. For example, where the menu presents the user with a save file option, additional information indicating the remaining disk space can be provided. In another example, where the menu presents the user with options regarding performing an assay, additional information about available consumables for the displayed assay can be provided.

[0139] At the execute menu level, the last level in a series of menus, the user can select an execute menu selection or item. These selections or items do not lead to further menus, but rather represent the parameters to take the menu tree to facilitate processing. Selecting an execute menu selection or item causes the system to perform a function with respect to the selected menu option or item. For example, when using an assay design menu tree, the execute menu selections can include options such as file name, assay parameters, reagent selection, etc.

[0140] In embodiments, the execute menu can facilitate the interface between the MUI software and the physical world. The execute menu can provide, for example, to execute commands output by the systematized user interface control system 1102 that interface with a system or instrument to implement processing designed using the MUI. In an example, such an execute command can cause a manufacturing system to begin manufacturing a part, can cause an assay instrument to begin performing an assay, can cause a design system to send a design specification, etc.

[0141] In embodiments, the execute menu can provide a user walkthrough or tutorial. For example, after a design workflow or process, the execute menu can provide a walkthrough or tutorial that conforms to the workflow, providing text-based, audio-based, video-based, and picture-based tutorial steps to guide the user through each step of the design workflow or process.

[0142] In embodiments, the execution menu can provide walkthroughs and / or coaching in conjunction with execution commands sent to physical world instruments and machines. For example, in a modular laboratory system, this combination can provide user instructions to load a machine (e.g., with assay plates and reagents), and then provide machine execution commands to perform processing. As new steps in the processing require user physical intervention (moving assay plates, etc.), the MUI can provide the user with further instructions (text-based, video-based, picture-based, audio-based, etc.) to further the processing at the execution stage. In embodiments, user instructions and notifications for user intervention portions of implementing a process can be provided via various communication mechanisms, including, for example, text (SMS, MMS), email, phone, live messaging, emoji message (Slack message), and any other type of messaging protocol. This variety of communication mechanisms can be useful, for example, when certain portions of a machine process take some time to complete and the user can not want to stay at the processing location during the processing. Thus, in the case of a user initiating a process that takes hours to complete, the user can receive a text message indicating that their involvement is required to further the process.

[0143] These types of "collaborative robot (Cobot)" interactions, in which the MUI comprises a human operator and physical world operations of automated machines, can be applied to various processes or workflows, including laboratory workflows, manufacturing workflows, food production workflows (e.g., beer production, bread production, etc.), transportation and logistics workflows (e.g., binning and picking bins, packaging, etc.). These automated machines can further include non-human machines, such as robots, drones, machine-based machines, or other autonomous or semi-autonomous machines.

[0144] As used in this specification, "display" of a menu includes displaying one or more items in the menu within the MUI. Display of a menu does not require display of all items or options in the menu. Whether or not each menu item is displayed, the menu items or the items comprising the first menu can remain constant. As discussed in more detail below, certain menu items can be excluded or limited for various reasons. As discussed in this specification, a specified "first menu" or "second menu" can be relocated to a different portion of the screen. When relocated, the first menu can continue to display the same set of first menu items and / or can display a different set of first menu items.

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

[0146] In the history portion, the menu items of each past menu can be displayed in a linear fashion in the MUI. All menu items from the menu level are displayed in a single column (horizontally or vertically). The past menu items of each group can be displayed in this linear fashion, while the menu as a whole can be displayed in a stacked or nested fashion. This feature is shown in FIG. 4B, which shows "menu items" displayed in a linear fashion and "sub-menu items" displayed in a linear fashion. The relationship between the "menu items" and the "sub-menu items" is a stacked or nested relationship. Thus, in a single menu level, the menu items are adapted to be displayed in a linear fashion, while the previous and future menu levels are adapted to be displayed in a nested fashion. Figure 2C

[0147] The selection menu can be displayed in a graphical wheel that rotates the options in one direction (e.g., horizontally or vertically (e.g., left and right, up and down) or other direction). In another aspect, the selection menu can be displayed as a graphical slide axis that slides the options in one direction (e.g., horizontally or vertically (e.g., left and right, up and down) or other direction). For example, an initial menu level (first level) can be displayed horizontally and slide left and right, and a next menu level (second level) can be displayed vertically and rotate up and down. In yet another aspect, the selection menu can be displayed as a series of concentric circles, with each menu level displayed as a circle with menu selections (also referred to as options or menu items). For example, an initial menu level (first level) can be displayed in a center circle, a next menu level (second level) can be displayed in a next circle (second circle) surrounding the center circle, a further next menu level (third level) can be displayed in yet another circle surrounding the second circle, and so on. However, the selection menu can be displayed or visualized as a graphical decision tree with nodes and edges. Each level of the graphical decision tree can represent a menu level with selections.

[0148] ​In one embodiment, the scroll wheel and / or the slide wheel does not need to rotate a full rotation, e.g., does not need to rotate a full revolution or a full turn. For example, the scroll wheel and / or the slide wheel rotates or slides from a beginning menu item to an ending menu item, and then rotates or slides from the ending menu item back to the beginning menu item. In this way, for example, the beginning and the end of the menu are always apparent because they are not merged or aggregated together. This technique reduces processing time because the scroll wheel and / or the slide wheel is able to convey (and the user is able to immediately understand) the full selection menu, and clearly indicates where the first menu item is, or which is the first menu item, among the options displayed by the scroll wheel and / or the slide wheel; and where the last menu item is, or which is the last menu item.

[0149] In a further embodiment, the scroll wheel and / or the slide wheel can rotate a full rotation to allow the user to easily access the beginning of the menu after viewing the entire menu. In this embodiment, a visual indicator can be provided to indicate that the menu has rotated a full rotation and returned to the beginning.

[0150] In various embodiments, the terms "software protocol" and "computer instructions" are used to describe software instructions or computer code configured to perform various functions and operations. As used in this specification, the term "manager" refers broadly to a collection of software instructions or code configured to cause one or more processors to perform one or more functional operations. For convenience, various managers, computer instructions, and software protocols will be described as performing various operations or functions, in effect, when the managers, computer instructions, and software protocols program hardware processors to perform the operations and functions. Although described as "software" at various places, it should be appreciated that "managers," "software protocols," and "computer instructions" can equally be implemented in firmware, software, hardware, or any combination thereof, to cause a computer or other electronic device to perform and / or implement a series of steps and / or instructions, as used in this specification. Furthermore, embodiments of this specification are described in terms of method steps, functional steps, and other types of occurrences (e.g., display of menus, selection of options, etc.). Although not explicitly stated in each case, it should be appreciated that these actions are performed in accordance with computer instructions or software protocols executed by one or more computer processors.

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

[0152] In various embodiments, the term "module" is used in this specification to refer to a particular software protocol suite and computer instructions that produce, maintain, and operate the various elements of the MUI as described in this specification. One or more processors described in this specification can be configured to execute the various software protocols to provide a systemized user interface module. As used in this specification, a "systemized user interface module" refers to any one of the subset of modules that provide a particular user interface. For example, the manager console module, the audit trail module, and the reader module are provided as particular systemized user interface modules to implement the work related to system management, auditing, and disk reading, respectively. Each MUI module can be considered to include at least a hierarchical menu tree containing multiple layers of menus. Each module can further include preferred default visual elements, preferred default exclusion and restriction lists, and other features specific to that module. Other modules are discussed in more detail below and throughout this disclosure. Throughout this disclosure, various aspects of the various MUI modules are discussed. The aspects discussed for any particular MUI module are non-exclusive and non-limiting and can be equally applied to any other MUI module. Thus, any MUI feature discussed in this specification (whether broadly or with respect to a particular module) can also be generally applicable to the MUI and / or any other particular MUI module discussed in this specification.

[0153] Please refer to Figure 56 , which schematically illustrates a systemized user interface control system 1102 in accordance with an embodiment. The systemized user interface control system 1102 includes one or more processors 1110 (also referred to interchangeably in this specification as the multiprocessor 1110, the one or more processors 1110, or the processor 1110 for convenience), one or more storage devices 1120, and / or other elements. The CPU 2 (see Figure 19 ) and the hardware processor 1804 (see Figure 18) can be configured as described in this specification. In other embodiments, the functions of the processor can be performed by hardware (e.g., using an application specific integrated circuit ("ASIC"), a programmable gate array ("PGA"), a field programmable gate array ("FPGA"), etc.), or any combination of hardware and software. The storage device 1120 includes any type of non-transitory computer-readable storage medium (media) and / or non-transitory computer-readable storage devices. This computer-readable storage medium or device can store computer-readable program instructions that are used by the processor to perform one or more of the methods described in this specification. The memory 4 (see Figure 19 ) and the memory device 1802 (see Figure 18 ) can be examples of the storage device 1120. Examples of the computer-readable storage medium or device can include, but are not limited to, electronic, magnetic, optical, electromagnetic, semiconductor, or any suitable combination of the foregoing, e.g., the computer diskette, the hard drive, the random access memory (RAM), the read-only memory (ROM), the erasable programmable read-only memory (EPROM or Flash memory), the static random access memory (SRAM), the compact disc read-only memory (CD-ROM), the digital versatile disc (DVD), the memory stick, but are not limited to these examples. In embodiments, the storage device 1120 can include multiple storage devices 1120. The multiple storage devices 1120 consistent with embodiments can be collocated and / or not collocated. For example, a first physical system can include a first storage memory device 1120, and a second physical system can include a second storage memory device 1120.

[0154] In embodiments, the processor 1110 and the storage device 1120 can be implemented via a cloud computing platform or other form of distributed computing. In this implementation, each of the processor and the memory device can include multiple processors and memory devices for implementing the works and functions described in this specification.

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

[0156] The manager as discussed throughout this specification can be implemented in various embodiments to manage the MUI to accomplish various tasks requiring processing workflows. Although this specification describes various software implementations of the MUI with respect to one or more particular embodiments, the methods and functionality provided by the aforementioned manager can be implemented to provide any MUI that processes workflows. The aforementioned manager can be functionally implemented through software libraries.

[0157] The various elements of the systemized user interface control system 1102 work in concert to provide a user systemized user interface display via any type of display hardware, including screens, projections, touchscreens, headphones, etc. In embodiments, the systemized user interface control system 1102 implements one or more software protocols to interactively guide a user through a path of menu items, options, or selections in the MUI. The aforementioned software manager can include computer instruction sets, software libraries, dynamic link libraries, application program interfaces, function libraries, and other compilations of executable code. The systemized user interface control system 1102 can further include appropriate graphics libraries containing graphics needed to implement and instantiate the various visual elements described throughout this specification. The manager from which the MUI is subscribed in a particular implementation uses various data structures to represent module information, including tables, linked lists, databases, B-trees, binary trees, heaps, stacks, queues, hash tables, red-black trees, binomial heaps, Fibonacci heaps, and any other appropriate data structure. Thus, the manager of the MUI can provide a customizable library configured to interface, interact, and integrate with additional computer instructions and data structures to provide the purpose of the MUI module capable of performing a particular task.

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

[0159] The input manager 1052 is a software protocol operating on the systemized user interface control system 1102. The input manager 1052 is configured to manage all inputs received by the systemized user interface control system 1102, including but not limited to user inputs and inputs from other systems. The input manager 1052 can be configured to send commands to other managers of the systemized user interface control system 1102 based on the received inputs. For example, a user action such as a click and other screen interactions cause the input manager 1052 to receive a signal indicating the user interaction. Receipt of this signal can cause the appropriate manager of the systemized user interface control system 1102 to provide a command with the signal, thereby causing one or more actions, including MUI navigation, menu display, etc., as discussed in this specification. For ease of explanation, this interaction and user input can be referred to as causing a particular response, whereas in fact the particular response is caused by the systemized user interface control system 1102 with the interaction or user input.

[0160] The menu manager 1054 is a software protocol operating on the systemized 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, to determine the next menu to be displayed, and to manage all aspects of navigation through the menu tree. The menu manager 1054 can be configured to send commands to other managers of the systemized user interface control system 1102 based on menu navigation requirements.

[0161] The user manager 1056 is a software protocol operating on the systemized user interface control system 1102. The user manager 1056 is configured to manage user access to the systemized user interface control system 1102. The user manager 1506, for example, manages user authorization, including maintenance of user authorization records, verification of user credentials, and other necessary user authentication tasks.

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

[0163] The network manager 1060 is a software protocol operating on the systemized user interface control system 1102. The network manager 1060 is configured to establish, maintain, and manage all network communications between the systemized user interface control system 1102 and the various other system elements discussed in this specification. The established communication paths can utilize any appropriate network transmission protocol and provide for one-way or two-way data transmission. The network manager 1060 can establish the network communications required to communicate all system elements as needed.

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

[0165] The above description 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 provides an overview of the capabilities and workings of these managers. The managers are not limited by the foregoing and, in various embodiments discussed below, the managers can have additional, different, and / or more capabilities. The described architecture of the systemized user interface control system 1102 is merely illustrative and it should be appreciated that the various functions and capabilities of the computer instructions programmed processor described in this specification can be performed, implemented, or realized by alternative architectures of software systems.

[0166] The systemized user interface control system 1102 can present menu options in one or more hierarchical menu levels, where each menu level can include one or more menu items or options. As described in this specification, the hierarchical menu levels refer to multiple levels in a menu system. A selection in a first, highest menu level results in navigation to a lower hierarchical level, i.e., a second menu, submenu, or sublevel. A selection in the second menu or submenu results in navigation to yet a lower hierarchical level, i.e., a third menu or sub-submenu or sub-sublevel. The hierarchical menu structure can include any suitable number of levels. In some embodiments, a selection on a level can result in navigation to one level below the current level, two levels below the current level, three levels below the current level, or more.

[0167] Each menu can display options in the active portion of the interface. The menu can display options in the active portion of the interface. Selection of a menu selection or option can trigger the display or presentation of a subsequent, immediate, or sub-menu, which can include its own plurality of menu options or sub-menu options. When a user selects a menu selection that results in a new menu, the menu items of the old menu can be moved from the active portion of the interface to the history portion, allowing the user to easily move to the new menu options while retaining the contents of the previous menu options. These features are described in more detail below with reference to Figures 2A-2O , Figure 3 , and Figure 57 .

[0168] Figure 57 A flowchart of a process 5200 to illustrate guiding the adaptation of a path to a hierarchical menu layer output to a user interface (e.g., a GUI, MUI, and / or any other type of UI discussed in this specification). The process 5200 is performed 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 the method. The one or more physical processors are hereinafter referred to simply as a processor. In embodiments, the process 5200 is performed via the systemized user interface control system 1102 as described in this specification. The systemized user interface control system 1102 is representative of an example of a combination of hardware and software configured to perform the process 5200, although implementation of the process 5200 is not limited to the combination of hardware and software of the systemized user interface control system 1102. As discussed throughout this specification, any other suitable computer system can also perform and / or implement the process 5200. The description of the process 5200 is not limited and various operations can be changed or modified in accordance with embodiments described in this specification.

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

[0170] In step 5204, the process 5200 includes receiving a selection. The input manager 1052 receives a selection of a menu item from the first menu in accordance with input provided to the system. The input can be a user selection and / or can be an automatic selection as discussed in this specification. For example, a user clicking on a menu item that is highlighted or emphasized can receive a user selection. Once selected, the menu item can be a past selected menu item.

[0171] In step 5206, the process 5200 includes providing a reposition command. The menu manager 1054 provides a reposition command for repositioning the first menu from the first portion of the UI display to the second portion of the UI display. The reposition command can be provided in conjunction with the received selection. Upon repositioning, the menu items of the first menu include one or more past selected menu items and past unselected menu items that are not selected for repositioning. The display of the first menu in the second portion can be provided in accordance with any of the visual elements disclosed herein (e.g., a slider axle type visual element). The reposition command of the menu manager 1054 can be sufficient to update the UI display. In another embodiment, the reposition command can incorporate and / or include a display command provided by the display manager 1050.

[0172] In step 5208, the process 5200 includes providing a second display command. The display manager 1050 provides a second display command in conjunction with the selection of the menu. The second display command causes a second menu of one or more user selectable items to be displayed on the first portion of the UI display, i.e., after the first menu has been repositioned. The second menu can be displayed in accordance with any of the visual elements disclosed herein (e.g., a scroll wheel type visual element). In an embodiment, the second display command can incorporate information received from the menu manager 1054 regarding the hierarchical menu tree navigation. After the first menu is repositioned and the second menu is displayed, the first menu can be viewed in the second portion simultaneously with the second menu being viewed in the first portion, including one or more past selected and past unselected menu items of the hierarchical menu tree.

[0173] The process 5200 can further include additional or different operational steps as described herein.

[0174] Please refer to Figure 1At step 102, a currently selected menu (e.g., a list of menu items) can be displayed on a first portion of a user interface display. At step 104, the user interface allows a user to select a menu item from the currently selected menu displayed on the first portion of the user interface display and to navigate deeper into the menu selection hierarchy based on the selection of the menu item in the previous menu selection hierarchy. At step 106, past selected and past unselected menu items of the deeper hierarchy are displayed on a second portion of the user interface display. The past unselected menu items are displayed as selectable options. Past selected menu items (or options) can also be displayed as selectable options. At step 108, the user interface allows the user to jump to a different path of menu options by allowing the user to select a past unselected menu item from the previous guided menu hierarchy displayed on the second portion of the user interface display. The user interface displays both the first portion and the second portion such that both can be viewed on the same screen of the user interface, e.g., simultaneously.

[0175] In one embodiment, the first portion and the second portion are offset to substantially center the display of the currently selected menu on the first portion of the user interface display while both the first portion and the second portion are arranged on the user interface display. Thus, for example, the first portion and the second portion do not need to remain in a fixed location on the user interface display during navigation or deepening (or moving up) through different menu option hierarchies.

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

[0177] As previously described, the selection menu can be displayed as a rotatable graphical wheel that displays menu items (selections or options) that can be displayed on the wheel as the wheel is rotated. The menu items on the slide axis can be displayed as a similar graphical slide axis that can be slid. The action of rotating or sliding can be performed with motion of a finger on a touch screen or input from a pointing device or another input device. In another aspect, the action of rotating or sliding can be automatically performed by the user interface (or hardware executing the user interface) in a timed manner. In one embodiment, the direction of rotation or sliding can switch to a different direction as the selection menu is repositioned from the first portion to the second portion.

[0178] A currently selected menu can be displayed in a first visual orientation on the first portion of the user interface display, and a deep menu selection layer including past selected and past unselected menu items can be displayed in a second visual orientation on the second portion of the user interface display.

[0179] In one embodiment, the currently selected menu is displayed as a graphical spin wheel or slide axis that is rotated or slid in the direction of the first visual orientation. In one embodiment, the deep layers of menu selections are displayed as graphical spin wheels or slide axes that are rotated or slid in the direction of the second visual orientation.

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

[0181] In one embodiment, the deep menu selection layer displayed in the second portion is displayed as a menu stack.

[0182] In another embodiment, the first portion and the second portion can be displayed as a series of concentric circles. For example, the first portion can be displayed as a center circle of a series of concentric circles, and the past menu layers can be displayed as circles outside or around the center circle. Each circle representing a menu layer can include, for example, rotatable menu items (selections or options) to enable the user to view all the options presented on the menu layer. Once a menu item is selected from the currently selected menu, the currently selected menu will relocate to the outer circle, and the center circle will display the next selection menu according to the selected menu item. For example, the circle (e.g., dial) can include a window that displays the active option, while turning the circle (e.g., dial) displays other options in the window. Although the dial options appear to be limited, the dial options can be unlimited. For example, the dial can keep rotating until the last option is displayed (or if rotated backwards, the first option is displayed).

[0183] In another aspect, a window can be opened to display the selected options as lit up, with one (or more) option on the left and another (or more) option on the right.

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

[0185] In one embodiment, past unselected menu items in the deep layer displayed on the second portion of the user interface display are brightly displayed relative to the past unselected menu items in the deep layer displayed on the second portion of the user interface.

[0186] In one embodiment, upon encountering the last layer in the selection path of menu layers, e.g., upon performing a function related to the selected item in the last menu layer, the user interface can return the current menu view to another item of the upper layer, e.g., the first menu list. For example, the current selection menu can again be the first initial menu layer and can be displayed in the first section. In one embodiment, the first and second sections are not independent, but are linked to each other to make navigation more efficient, allowing the user to proceed along a path and to deviate from a path that the user has set a different path, e.g., to be able to see where the user has visited and where the user can visit in the menu selection path, both backward and forward page paths. In one embodiment, the user interface can guide the user through the efficient path selection such that the user does not need to search around the user interface trying to find the next appropriate path or action. This efficient path guidance can save computer resources, e.g., central processing unit (CPU) cycles, and memory usage spent in the computer executing the user interface swapping in and out processor threads and memory elements.

[0187] Please refer to Figures 18-19 , which provides a system for performing functions related to Figure 1 Another example system is described that performs the methods. As previously described, Figure 18 and 19 The system aspects presented in the foregoing can be Figure 56 embodied and / or implemented by the systemized user interface control system 1102 shown.

[0188] Figure 18 System elements of a graphical user interface (GUI) in one embodiment are illustrated. One or more hardware processors 1804 can execute graphical user interface modules and perform the graphical user interface functions previously described to display graphical elements as previously described on a user interface display device 1806 coupled to the one or more hardware processors 1804. Memory devices 1802 can store menu lists and menu item lists or options available for each menu list that the graphical user interface modules can access for display on the display device 1806. The display device 1806 can include a screen device and / or a touchscreen device. One or more pointing devices 1808 can be coupled to the one or more hardware processors 1804 to allow input via the display device 1806.

[0189] The memory devices 1802 can be any type of computer-readable storage media described in this specification.

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

[0191] For example, a hardware processor 1804 coupled to the memory device 1802 and the display device 1806 can display a currently selected menu on the first portion of the user interface display, allow a user to select a menu item from the currently selected menu displayed on the first portion of the user interface display, and navigate through a menu selection hierarchy according to selecting menu items in previous menu selection hierarchies. The hardware processor 1804 can also display past selected and past unselected menu items of the navigated hierarchy on a second portion of the user interface display, where the past unselected menu items are displayed as selectable options. The hardware processor 1804 can also allow a user to jump to a different path of menu options by allowing the user to select a past unselected menu item from the previously navigated menu hierarchy displayed on the second portion of the user interface display.

[0192] The hardware processor 1804, for example, can perform the methods described with respect to Figure 1 and 3 the GUI techniques described above.

[0193] The GUI techniques described above can be implemented using computer languages such as JAVA and JavaScript, but are not limited to such computer languages. In an embodiment, the functions and modules of the system and methods of the present application can be implemented or executed in a distributed manner in different processing systems or on any single platform, e.g., accessing data stored locally or in a distributed manner on computer networks. Likewise, the software protocols and managers of the present application can be implemented or executed in a distributed manner in different processing systems or on any single platform, e.g., accessing data stored locally or in a distributed manner on computer networks.

[0194] GUI technology can be implemented on any type of computing device, such as a desktop computer, a laptop computer, a mobile device (e.g., Android or Apple IOS), a tablet computer, and using any type of interface (e.g., mouse, touch screen, etc.). GUI technology can also be implemented on an instrument, such as an assay instrument for performing biological assays, such as immunoassays or nucleic acid assays. In some embodiments, the instrument performs electrochemiluminescence assays. In some embodiments, the instrument is an automated assay system, such as one that includes: (a) a single robot controlled 8-channel pipette, (b) a single robot controlled assay disc gripper arm, (c) a single 96-channel channel assay disc washer, (d) a single disc reader, (e) one or more disc shakers with a total capacity of at least 5 disc shaker positions, and (f) a processor adapted to perform assay processes in a 96-well disc to analyze a plurality of samples. Other computing devices, machines, systems, and instruments include wearable devices, automotive computing systems, individual instruments including assay related instruments (e.g., disc washers, disc readers, disc shakers, incubators, workflow assistance instruments such as load cars (e.g., as described in International Patent Application Publication Nos. WO 2018 / 017156 and WO 2017 / 015636, the entireties of which are incorporated herein by reference), medical instruments and machines (e.g., MRI and CT machines), ultrasound systems, consumer products (e.g., household appliances), home systems, including home management systems, air conditioning and heating systems, washing machines and dryers, dishwashers, ovens, slow cookers, and other cooking devices.

[0195] Various embodiments can be a program, software, or computer instructions tangibly embodied on a computer- or machine-readable medium, which makes the computer or machine execute method steps. For example, a program storage device readable by the machine, tangibly embodying a program of instructions executable by the machine to perform various functions and methods described in the present application can be provided.

[0196] The systems and methods of the present application can be implemented and executed on a general purpose computer or a special purpose computer system (or device). The computer system can be any known or heretofore known system and can include a hardware processor, memory device, storage device, input / output device, internal bus, and / or communication interface for communicating with other computer systems, in conjunction with communication hardware and software, etc. The GUI technology of the present application can also be implemented on a mobile device, etc. Implementing various computer instructions, software protocols, and modules described in the present specification on a general purpose computer converts the general purpose computer into a special purpose computer system configured to perform the specific methods, works, operations, and acts described in the present specification.

[0197] Figure 19An example computer system 100 that can implement the systems and / or methods of the present application is shown. One or more central processing units (CPUs) 2 can include one or more arithmetic / logical units (ALUs), caches, and registers and / or register files. A register is a small storage device; a register file can be a set of multiple registers. A cache is a fast storage memory device, e.g., including a static random access (SRAM) chip. The cache is used as a scratchpad area to hold data used by the CPU 2. The display is a simplified hardware configuration. The CPU 2 can include other combinational circuits and storage devices.

[0198] One or more central processing units (CPUs) 2 execute instructions, e.g., stored in memory 4, that are passed to registers in the CPU 2. For example, a bus 6 is a wire that carries data bits between elements. The memory 4 can include an array of dynamic random access memory (DRAM) chips and stores programs and data used by the CPU 2 to execute. The system elements can also include an input / output (I / O) controller and adapter that connect to the CPU 2 and memory 4 via a bus, e.g., an I / O bus, and to I / O devices. For example, a display / graphics adapter connects to a monitor 28 or another display device / terminal. A disk controller 10 connects to a hard disk 24, e.g., for permanent storage; a serial controller 12, e.g., a universal serial bus (USB) controller, can connect to input devices such as a keyboard 22 and mouse 20, output devices such as a printer 26; a network adapter 14 connects the system to another network, e.g., to other machines. The system can also include expansion slots to accommodate other devices that connect to the system. For example, the hard disk 24 can store programs of instructions and data that implement the foregoing methods and systems, which programs can be loaded into the memory 4 and then into the CPU memory, e.g., the cache and registers, for execution by the CPU, e.g., the ALU and / or other combinational circuits or logic. In another aspect, all or some of the programs of instructions and data that implement the foregoing methods and systems can be accessed and / or executed at another computer system or device over the network 18. Figure 19 This is only one example of a computer system. Computer systems that can implement the methods or systems of the present application are not limited to Figure 19 the configuration shown. Rather, another computer system can implement the methods of the present application, e.g., including but not limited to special purpose processors such as field programmable gate arrays (FPGAs) and accelerators.

[0199] In one embodiment, the present application can be embodied as a computer program product, which can include a computer-readable storage medium (or media) and / or a computer-readable storage device. This computer-readable storage medium or device can store computer readable program instructions to make a processor execute one or more methods described in the present specification. In one embodiment, the computer-readable storage medium or device includes a tangible device that can retain and store instructions for use by an instruction execution device. Examples of computer-readable storage medium or device can include, but are not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. For example, computer-readable storage medium or device can include, but are not limited to, computer storage media such as a computer-readable storage medium or device, a floppy diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a compact disc read-only memory (CD-ROM), digital versatile disks (DVDs), a memory stick, and the like, but is not limited to these examples. Computer-readable medium can include a computer-readable storage medium (e.g., the foregoing) or a computer-readable transmission medium. For example, examples of a computer-readable transmission medium can include or consist of propagating transmission media that can be implemented using both wired and / or wireless techniques. Such transmission media can take a variety of forms, including, but not limited to, open wires, wired cables, fiber optics, and carrying electronic waves, magnetic waves, or electromagnetic waves, for example, during radio frequency (RF) and infrared (IR) data communication.

[0200] As used herein, the term "computer system" can include various combinations of fixed and / or portable computer hardware, software, peripherals, mobile devices, and storage devices. The computer system can include a network or linked to perform multiple separate elements in cooperation, or can include one or more independent elements. The hardware and software elements of the computer system of the present application can include and can be included in fixed and portable devices such as desktop computers, laptop computers, and / or servers. A module can be an element of a device, software, program, or system that implements certain "functions" that can be implemented as software, hardware, firmware, electronic circuitry, etc.

[0201] The memory 4 and the memory device 1802, which are exemplary storage devices 1120, can be implemented as one or more computer-readable storage media as described in the present specification, and can be used to store various data and information about the computer system 100.

[0202] In one embodiment, the storage device 1120 can store registration information, such as user identifiers and user accounts. The registration information can be stored by data storage commands sent by the data storage manager 1064. In one embodiment, the registration information is stored in the storage device 1120. The registration information can 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, binomial heaps, Fibonacci heaps, etc. In one example, the registration information can be stored in a registration table. The registration information includes at least user identifiers for users and accounts. Since multiple users can be assigned to the same account, the system can use a shared account flag (e.g., semaphore, bit, etc.) to track the account. When multiple users are assigned to the same account, the shared account flag can be set to a first particular value. Otherwise, the shared account flag can be set to a different particular value. Using a shared account flag is one way to track shared accounts, and the application is not limited to this example. Other methods can be used. The shared account flag can be a column of the registration table. For each user identifier that has the same account, the shared account flag is set to a particular value and is about the user identifier.

[0203] In other aspects, multiple accounts can be linked together. In embodiments, the user manager 1056 can send commands for managing user accounts. In embodiments according to the application, multiple accounts can represent a team, such as a research, project, company, university, or experimental team. The system can use a multiple account flag to track multiple accounts and teams. When different accounts are linked, the multiple account flag can be set to a first particular value, otherwise the multiple account flag can be set to a different particular value. Using a multiple account flag is one way to track different account links, and the application is not limited to this example. Other methods can be used. In one embodiment, the multiple account flag can be a column of the registration table. For each linked account, the multiple account flag is set to a particular value and is about the account.

[0204] In other embodiments, the storage device 1120 can also store login history data. The login history data can be received via the input manager 1052, can be organized via the user manager 1056, and stored via the data storage manager 1064. The login history data can include user identifiers / accounts and time / date information for each time a user (or other user) logs into the system. The login history data can be kept in the storage device 1120 for a predetermined or indefinite period of time. The predetermined period of time can be based on the particular application being performed or to be performed.

[0205] In other embodiments, the storage device 1120 can also store a user selection history. The user selection history can be received by the input manager 1052, can be organized by the user manager 1056, and stored by the data storage manager 1064. The user selection history can include selected menu items, user identifiers / user accounts associated with the selections, and times / dates of the selections. The user selection history can also be stored for a predetermined or indefinite period of time in the storage device 1120. The predetermined period of time can be selected according to the MUI module in which the user selections were originally made. The predetermined period of time for storing the user selection history and the login history data can be the same.

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

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

[0208] In an embodiment, a display command can be provided by the display manager 1050 to display a particular set of hierarchical menu levels (multiple levels) on a particular portion of the MUI. The display command is configured to display one or more menus in one or more portions of the MUI. The particular hierarchical menu levels can include one or more menu items (or options). The display command can include one or more menu items, a particular display order, a display direction, a display size (and format), and a manner of displaying the options (e.g., a scrolling method), although other manners of arranging and / or displaying the options can also be considered. In an embodiment, the scrolling method can define the display direction, and thus, the display command does not necessarily include a separate display direction and scrolling method.

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

[0210] The display command can specify a scrolling method. For example, the display command can specify that the menu items are to be displayed in a graphical wheel, which can rotate the options in a direction, e.g., horizontal or vertical (e.g., left and right or up and down), or another direction. In another embodiment, the display command can specify that the menu items are to be displayed as a graphical sliding axis, which slides the items in a direction, e.g., horizontal or vertical (e.g., left and right, up and down), or another direction.

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

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

[0213] Figure 3 To illustrate a flowchart of a method of interactively displaying interactive items on a user interface display in another aspect, e.g., details of a method in which vertical and horizontal switching of menu levels can be performed. The method can be automatically performed by at least one hardware processor. At step 302, a list of menu items can be displayed on the first portion of the user interface display. The list of menu items is displayed on the first portion in a first visual orientation. For example, the first visual orientation can be a vertical orientation. The list of menu items can include one or more menu items from a first menu, and can be displayed in response to a first display command provided by the display manager 1050.

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

[0215] As Figure 2AAs shown, the menu items 202 of the first menu are displayed in a vertical orientation (i.e., a first orientation) in the first portion 204 of the interface. The MUI includes a display 206. The first portion 204 can display the menu items 202 with a first display command of a first menu of user-selectable options to be displayed on the first portion 204 of the MUI. As previously described, the first display command can be provided by the display manager 1050.

[0216] The first display command includes menu items of a first menu (in an embodiment, the menu items are stored in the storage device 1120), a scrolling method / orientation, and size (and format). For example, the orientation of the menu items of the first menu (to be displayed in the first portion) can be vertical. The first display command can also include a display location, such as a location of the first portion. The first portion can be in a central location on the MUI. Each item can be selectable by a user.

[0217] In an embodiment, the first portion can include a decision zone. The decision zone can be located at a central location within the first portion. The decision zone can be a location in the first or active portion that displays a highlighted or brightened display menu item for immediate selection. For example, in Figure 2A , the menu item "Menu Item 4" is displayed in the decision zone and is displayed in a larger font than the rest of the menu items to highlight or brighten the menu item for immediate selection. The first display command that causes the first menu to be provided can specify that the menu item displayed in the decision zone be highlighted or brightened, such as displayed in a larger font than the other menu items that are not in the decision zone. In other aspects, the menu item displayed in the decision zone can be bolded, italicized, or brightened, or underlined using a different color than the background.

[0218] In other embodiments, the first display command can specify that menu items outside of the decision zone are to be faded, such as made smaller, to appear dim relative to the other menu items in the decision zone.

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

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

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

[0222] The relocation command causes the first menu of menu selection 202 to be relocated from the first portion 204 of the MUI display 206 to the second portion 208. Figure 2BThe repositioning command can include menu selections of the first menu to be displayed in the second portion 208, size and orientation of the display, necessary display visual elements, an indication of which menu items to reposition, and any other information discussed in this specification relating to display commands. The first menu that is repositioned to become a past menu in the history or second portion 208 can include one or more or all of the menu items 202 available to the user and the selections previously made. The menu items 202 selected by the user to be repositioned become past selected menu items, while the menu items 202 that are not selected become past unselected menu items. The past unselected menu items represent a previous directed hierarchical menu level. After the menu items 202 of the first menu are repositioned, the display manager 1050 causes the MUI to display in the active or first portion 204, with the first menu selection, the sub-menu items 210 of the second menu as the new current or subsequent menu item level for user interaction. As shown, the subsequent or second menu selection level includes the second sub-menu items 210 displayed in the active or first portion 204 of the MUI display 206. Figure 2B

[0223] In the method according to an embodiment, a repositioning command is sent upon receiving a signal from the input manager 1052 indicating that a menu item 202 has been selected from the first portion 204. For example, the menu manager 1054 provides a repositioning command to the display manager 1050. The repositioning command causes the display manager 1050 to move the first menu from the first portion 204 of the MUI display 206 to the second portion 208 of the MUI display 206 in the second menu. The second portion 208 is a location on the MUI display 206 that is different from the first portion 204. As a result of the menu item being selected from the first menu of the menu items 202, the repositioned first menu of the menu items 202 will now have past selected menu items and past unselected menu items (e.g., one or more menu items that are available for user selection but not selected). The repositioning command can include the first menu items, scrolling method and / or orientation, size (and format) of the display, and location of the second portion.

[0224] In an embodiment, the second portion 208 is further from the center location of the MUI display 206 than the first portion 204.

[0225] ​In one embodiment, the orientation of the menu items 202 in the second portion 208 is different than the orientation of the sub-menu items 210 in the second menu in the first portion 204. For example, the orientation of the menu items 202 in the second portion 208 can be substantially orthogonal to the orientation of the sub-menu items 210 in the first portion 204. The repositioning command can specify that the orientation of the menu items 202 is horizontal (whereas the first display command specifies that the orientation of the menu items 202 is vertical). In other embodiments, the orientation can be reversed, where the menu items 210 in the first portion 204 are horizontal and the menu items 202 in the second portion 208 are vertical. In embodiments, the first portion 204 is located in the lower center of the MUI display 206, and the second portion 208 is located in the upper portion of the MUI display 206.

[0226] The repositioning command can also specify different sizes of menu items. For example, the selected menu item of the first menu (triggering the repositioning) can be specified to be displayed in a highlighted manner, such as in a larger font than the unselected menu items. In other aspects, the selected menu item can be bolded, italicized, or highlighted, or underlined in a different color than the background. In another aspect, the repositioning command can also specify the relative position of the menu items 202 within the second portion 208. For example, the selected menu item can be located in a central position within the second portion relative to the other menu items (unselected menu items).

[0227] In other aspects, the unselected menu items in the hierarchical menu level can be displayed in a faded manner. For example, the repositioning command can specify the unselected menu items to be in a smaller font size or dimmed relative to the selected menu item. In other aspects, the repositioning command can specify the unselected menu items to be displayed further away from the center portion of the second portion than the selected menu item of the same hierarchical menu level.

[0228] The first portion and the second portion can be displayed non-overlapping on the user interface display. The menu item repositioned to the second portion can be selected from the position or location, and the selected menu item can be graphically highlighted, such as to provide a visual indication of the item in the selected list. The selected menu item can also be centered with the other menu items to the left and / or right of the selected menu item. The sub-menu items displayed at the location of the repositioned menu item (prior to repositioning) are also optional items. Figure 2BAn example of a user interface display shown in an embodiment having a list of repositioned menu items. As shown, the menu items 202 are repositioned to a second portion 208 of the display 206, e.g., above the first portion 204, and displayed horizontally. As described in more detail below, the second portion of the display can include a number of layers of menu items, e.g., past decision layers and unselected options in those layers. Thus, the number of layers of past decisions can be, e.g., 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20 or more, e.g., 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, e.g., 2-20, 2-19, 2-18, 3-20, 3-19, 3-18, etc. For example, the second portion can visualize a path of past decisions made and other decisions not made (other paths) of the path. In an embodiment, the past decisions taken (selected menu items) can be, e.g., vertically, e.g., center aligned.

[0229] Upon a repositioning command for a first menu of user-selectable options for display on the second portion 208 of the MUI display 206, the second portion 208 can be caused to display first menu items 202. As before, the repositioning command is provided by the menu manager 1054 to the display manager 1050. The first menu of user-selectable options can include both past selected and past unselected menu items. The first menu can include one or more of the first menu items 202 that are user-selectable. The menu items 202 can be immediate selection or non-immediate selection.

[0230] The second portion 208 can also include one or more decision zones. The repositioning command can also specify menu items displayed within a decision zone to highlight or brighten. In other aspects, the menu items displayed within a decision zone can be bolded, italicized or brightened, or underlined using a different color than the background. In other embodiments, the repositioning command can specify the same. In other embodiments, the repositioning command can specify to dim or dimly display menu items displayed outside of a decision zone.

[0231] The first portion 204 and the second portion 208 are displayed on the MUI display 206 such that both are viewable, e.g., simultaneously viewable. The MUI display 206 can be presented via one or more physical display screens. The second portion 208 can contain one or more menus, each including both past selected and past unselected menu items of a previously navigated hierarchical menu. In an embodiment, the second portion 208 can include a first menu of past selected menu items and a second menu of past unselected menu items. In an embodiment, the first menu of past selected menu items can be displayed above the second menu of past unselected menu items. In an embodiment, the first menu of past selected menu items can be displayed below the second menu of past unselected menu items. In an embodiment, the first menu of past selected menu items can be displayed to the left of the second menu of past unselected menu items. In an embodiment, the first menu of past selected menu items can be displayed to the right of the second menu of past unselected menu items. Figure 2CIn the illustrated presentation, the second portion 208 (history portion) includes menu items 202 and sub-menu items 210, each of which was included in the first portion 204 of a previous MUI presentation. Past selected menu items 202 and sub-menu items 210 (i.e., those menu items that resulted in the display of sub-sub-menu items 212 in the first portion) can be highlighted or emphasized to indicate that they have been previously selected. As Figure 2C As illustrated, "menu item" 4 and "sub-menu item" 3 are highlighted to indicate that they have been previously selected.

[0232] Past unselected menu and sub-menu items are displayed as selectable options. Past selected menu items (or selections) can also be displayed as selectable options, with both displayed on the second portion 208 (e.g., a history portion, which can include one or more menu items that were previously available to the user). The history portion is in contrast to a current portion, which can include the current user-selectable options of the current hierarchical menu level (e.g., located on the displayed first portion). The history portion can also allow the user to make selections, e.g., by selecting in a previously selected level and / or menu. As such, the history second portion 208 can represent a "page path tour" to display to the user the sequential path of selections made to arrive at the current menu as displayed in the current first portion 204. Further details regarding selections in the second portion 208 are provided below.

[0233] In some embodiments, the first portion 204 can be adapted to occupy a greater portion of the display area of the MUI than the second portion 208. The second portion 208 can be displayed on a smaller area than the first portion 204. The first portion 204 and the second portion 208 can be adapted to be displayed in a manner that their backgrounds form a contrast. For example, the first portion 204 and the second portion 208 can be displayed in bright pixels relative to a dark background or dark pixels relative to a bright background.

[0234] In other embodiments, the menu manager 1054 can provide a command (e.g., a repositioning command) to move or reposition a menu from one portion of the MUI display 206 to another portion of the MUI display 206. In one embodiment, the movement or repositioning of a menu and / or menu items can include providing a command to move the menu from one portion of the display to another portion of the display. In another embodiment, the movement or repositioning of a menu can include sending a plurality of commands, e.g., one command to remove the menu from the first portion 204 of the display and another command to display the menu (in the same format and / or orientation or in a different format and / or orientation) on the second portion 208 of the display. For example, such repositioning can occur as a result of a user selection from a menu (e.g., a first menu).

[0235] Please refer back to Figure 3At step 306, a first list of sub-menu items related to the selected menu item is displayed in a first visual orientation on the first portion of the user interface display, if a list of menu items previously displayed on the first portion prior to repositioning to the second portion. As shown in Figure 2B FIG. 6A, a first list of sub-menu items 210 is displayed, for example, vertically in the first portion 204.

[0236] Please refer back to Figure 3 At step 308, upon 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 the second portion, where the first list of sub-menu items is displayed in a second visual orientation and stacked with the list of menu items displayed in the second portion. At step 310, a second list of sub-menu items related to the selected sub-menu item is displayed in the first visual orientation, for example, vertically, on the first portion of the user interface display. Figure 2C An example of a user interface display with a second list of sub-menu items is shown in an embodiment. As shown, the first list of sub-menu items 210 is repositioned to the second portion 208, for example, stacked below the repositioned list of menu items 202, for example, horizontally stacked. A second list of sub-menu items 212, i.e., sub-sub-menu items related to the selected sub-menu item, is displayed in the first portion 204. Depending on the depth of the guided menu or sub-menu, the horizontal menu structure in the second portion 208 can accumulate more than a number of menu levels that can be displayed together on the display portion at the second portion 208 (e.g., the number of stacked levels exceeds the screen portion allocated for the horizontal menu structure of the second portion 208). In an embodiment, the horizontal menu structure of the second portion 208 can display a number n of menu levels, for example, the last 3 sub-menus, allowing a scrolling capability. For example, scrolling up allows the user to view other menu items. The number n can be any value, but is not limited to 3, for example, 2, 3, 4, 5, etc. In another embodiment, the top m (e.g., 2) menu items can be displayed together with the bottom 1 sub-menu to provide the top level of the last decision. The number m can be any value, not limited to 3, for example, 2, 3, 4, 5, etc. The scrolling function allows other menu items to be displayed, for example, the user can scroll to view other menu items. The user can also expand the entire multi-level of the menu and sub-menus.

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

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

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

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

[0241] In embodiments, the order or arrangement of menu items within their menu level can be determined according to the properties of the menu items. The manner in which menu items are displayed can be displayed according to properties selected from the group consisting of: whether the menu item is a previously selected or previously unselected menu 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 flyout menu (described in more detail below), and / or whether the menu item is in a more central position in the list relative to other positions in the list.

[0242] In embodiments, the manner in which menu items are adapted to be displayed, i.e., the ordering, arrangement, coloring, and presentation of menu items, can be determined according to a number of different factors. For example, the menu manager 1054 and display manager 1050 can be configured to highlight menu items that are selected or previously selected, currently available to the user (i.e., selectable), and / or located in the decision area of the first portion 204 or second portion 208. The menu manager 1054 and display manager 1050 can be further configured to dim menu items that are unselected or previously unselected, currently unavailable to the user, and / or located away from the decision area. In some embodiments, immediately selectable menu items can be highlighted, while non-immediately selectable items can be dimmed. In some embodiments, highlighting or dimming a menu item can include brightly displaying or dimly displaying the menu item, as discussed throughout this specification. Brightly displaying or highlighting can include, for example, bolding, increasing font size, changing font, underlining, changing brightness or contrast, or adjusting position on the display relative to other items. Dimly displaying or dimming can include decreasing font size, changing font, darkening, changing brightness or contrast, or adjusting position on the display relative to other items.

[0243] By allowing the user to select a past unselected menu item in a previously navigated menu level displayed on the second portion 208 of the MUI display 206, and a newly displayed menu item on the first menu of the currently displayed menu on the first portion, the MUI allows the user to jump to a different path of menu items (e.g., by selecting one or more other menu items on the same, higher, or lower hierarchical level of the menu). As discussed previously with respect to Figure 2C The previously navigated menu items (including sub-menu items, sub-sub-menu items, etc.) are repositioned to the second portion 208 after a menu item is selected, as discussed previously with respect to

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

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

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

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

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

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

[0250] In one embodiment, any menu provided in any portion of the MUI display can include a search function. The search function allows the user to enter a keyword or other input regarding a menu item (option). The user input is received via the input manager 1052 and forwarded to the menu manager 1054 for searching. The search allows the entered keyword or other input to be used to filter the functions (menu items), thereby reducing the time required to find a desired menu item. The interface for the search function can be located in a central location of a relative portion of the MUI display 206; or in other portions of the MUI display 206. In further embodiments, the search function does not provide a visual interface. In this embodiment, the user can only access the search function by typing.

[0251] In one embodiment, any menu item that matches or partially matches the keyword can be displayed to highlight the menu item. For example, the menu item can be displayed in a larger size than other menu items that do not match or partially match. In other embodiments, the menu item can be bolded, italicized, or highlighted using a color different from the background, or underlined. In other embodiments, menu items that do not match or partially match the keyword can be smaller text or faded text relative to the text of menu items that match or partially match the keyword. In this embodiment, the scroll axis or wheel can automatically advance and / or rotate to display menu items that match the search item.

[0252] In one embodiment, a first menu selection can be used as a filter on a second menu. In a hierarchical tree, each of a number of items in the first menu can lead to the same second menu. However, the first menu selection made determines the menu items displayed when the second menu is displayed. In a simple example, the first menu can include menu items about team roles, and the second menu can include menus about team responsibilities. Selecting a particular team role on the first menu can filter the second menu to display only team responsibilities relative to the selected role. In some embodiments, this filtering is performed by making particular items of the second menu unselectable.

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

[0254] In one embodiment, one or more menus or menu levels can provide exceptions to the hierarchical menu tree standards discussed in this specification. For example, a menu level can include a visual display and / or a video display instead of text-based visual elements. This can be implemented, for example, where information can be better conveyed through alternative means. For example, as previously mentioned, an execution level menu can include a walkthrough that can be best presented via a video or a series of pictures. In another example, an execution level menu can provide for data analysis, and can provide any combination of graphs, charts, tables, etc. to aid in data analysis.

[0255] In one embodiment, an advanced quick view menu can be provided via one or more commands sent by the menu manager 1054. Figure 2PAn example of a systematized user interface that includes the advanced quick reveal menu 270 is illustrated. The advanced quick reveal menu 270 contrasts with the first and second portions in that it provides a "direct workflow mode" in its entirety. The advanced quick reveal menu 270 is accessible via the advanced quick reveal menu selector 290, which in embodiments can be provided on some or all screens of the systematized user interface. The advanced quick reveal menu 270 provides additional advanced menu items 271 in addition to the items that appear in the current menu of the active first portion 204 or one or more past menus that appear in the historical second portion 208. The advanced quick reveal menu 270 is accessible by clicking or hovering the cursor over the advanced quick reveal menu selector 290 or otherwise indicating that the advanced quick reveal menu 270 is to be accessed. The advanced quick reveal menu 270 includes a selection of advanced menu items 271.

[0256] The selection of advanced menu items 271 can include items that are displayed in the current menu of the first (active) portion 204 and items that are displayed in previous menus of the second (historical) portion 208. In accordance with embodiments thereto, the advanced menu items 271 of the advanced quick reveal menu 270 can be highlighted. For example, the advanced menu items 271 can be displayed in a larger font. In other embodiments, the menu items can be bolded, italicized, or highlighted using a color that is different from the background, or underlined.

[0257] Other items included in the selection of items in the advanced quick reveal menu 270 can be items that are not currently included in one of the displayed menus. That is, the selection of items in the advanced quick reveal menu 270 is driven by the current content of the UI display. For example, five menu items of a first menu can be displayed in the active portion as a current menu. Three additional menu items related to the five menu items of the first menu can be displayed in the advanced quick reveal menu 270. The three additional menu items can be items of the first menu that were excluded or restricted (as discussed further below) from the current menu for various reasons.

[0258] The advanced quick reveal menu 270 provides the user with a larger array of accessible menu items without cluttering the active portion or the historical portion. In embodiments, some of the advanced menu items 271 in the advanced quick reveal menu 270 can be infrequently selected items, e.g., less than 50, 45, 40, 35, 30, 25, 20, 15, 10, or 5% of usage cases. The advanced menu items 271 of the advanced quick reveal menu 270 can be selected based on a pattern of user interaction with the MUI, as explained in more detail below.

[0259] In embodiments, the advanced quick view menu 270 can include three sections. As previously described, the first top section 272 of the advanced quick view menu 270 can include advanced menu items 271 pertaining to the currently active menu. The second middle section 273 of the advanced quick view menu 270 can include advanced menu items 271 pertaining to MUI modules available on the same workstation that the advanced quick view menu 270 is selected. These options can allow the user to switch modules depending on the desired work. The third bottom section 274 of the advanced quick view menu 270 menu can include global functions, such as login / logout functions, user manual and instructions, EULA information, and privacy policy information. The foregoing order is not limiting, and any of the advanced menu items 271 can be provided in a different order.

[0260] In embodiments, when the advanced quick view menu 270 is selected, the MUI causes other graphics, text, etc. to become dimmed and / or blurred. The advanced quick view menu 270 is displayed on a transparent background such that the advanced quick view menu 270 and the rest of the background are the same (e.g., black). Thus, the MUI provides a dialog box adapted to be displayed on a foreground of the UI display to prompt the user for additional information or to notify the user of an error, wherein a background of the dialog box is further adapted to conform to the background of the first and second portions of the UI display, and further wherein one or more of text, graphics, photos, and videos displayed in the background of the first and second portions of the UI display are adapted to be displayed out of focus when the dialog box is displayed on the foreground of the UI display.

[0261] In an embodiment, certain menu items included in the hierarchical menu tree, i.e., first menu, second menu, third menu, etc., can be excluded or limited from display when a menu is displayed. Exclusions and limitations can be managed by the exclusion manager 1058 in conjunction with the menu manager 1054. Displaying any menu in the menu tree includes displaying one or more menu items in the menu, but does not necessarily require displaying all items in the menu. Display of menu items of a hierarchical menu level can be excluded or limited based on an exclusion table. The exclusion table can correspond to a user identifier, email address, user name, team, and / or account number. In other embodiments, one or more entire menus in the menu tree can also be excluded based on an exclusion table. In certain embodiments, the exclusion or limitation information can be stored in the storage device 1120. The exclusion or limitation information can be stored as a data structure. Any of the data structures described in this specification can be employed.

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

[0263] User identifiers, account numbers, and menu items and / or menus to exclude can be entered by an administrator. For example, the administrator console module, discussed in more detail below, can be used to administer and generate an exclusion list. Administration can be accomplished when a user registers with the system. In other embodiments, exclusion information can be added after registration and updated periodically.

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

[0265] In certain embodiments, prior to sending a command to display any menu, the menu manager 1054 can check the exclusion list (e.g., stored in the storage device 1120) to determine if any of the menu items in the initial display menu (e.g., the default menu) are listed for exclusion from display by the user (or account number). In an embodiment, the menu manager 1054 can compare the user identifier and / or account number of the user currently logged in to the user identifiers and / or account numbers listed in the exclusion list. If a match, the menu item listed in the exclusion list is excluded from display in the initial display menu. The exclusion can be performed by sending a separate exclusion command and / or instruction, or alternatively, the exclusion can be performed by modifying any display command that results in the display of the available menu items. The menu manager 1054 can delete the menu items included in the list from the menu items in the initial display menu (e.g., the default menu) and send the first command without the deleted menu items.

[0266] In some embodiments, each time the input manager 1052 receives a selection of a menu item in a current menu, before sending a reposition command, the menu manager 1054 can decide whether to list to exclude any menu items on the hierarchical menu level below the hierarchical menu level on which the MUI display 206 is currently displaying 206 (or to exclude lower hierarchical menus). The decision can use login history data and an exclusion table. The login history data can be used to identify the same user (user identifier or account) that is still logged in and compare it to the user identifiers and accounts in the exclusion table. In other embodiments, the menu manager 1054 can use the user identifier and account received from the user manager 1056 instead of using login history data to make the decision. In other embodiments, a similar decision is made before sending any reposition or display commands.

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

[0268] As previously mentioned, an account can be associated with multiple users (user identifiers). Thus, when using an account as the basis for exclusion, all users associated with the account can have menu items excluded from display on the MUI display 206.

[0269] In another embodiment, because certain accounts can be linked, such that when an account is used, any account linked to the account can also have menu items that have been excluded.

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

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

[0272] Exclusion or restriction information can be stored, for example, in the storage device 1120 as a data structure. Each device can have an identifier, such as a media access control (MAC) address or other unique identifier. The identifier of a device is not limited to a MAC address, and other identifiers can be used, such as an Internet communications protocol (IP) address, machine name, etc. In one embodiment, one column of the table can include the identifier, such as a MAC address. A second column of the table can include menu items or hierarchical menu levels to exclude from display, respectively, in relation to the identifier (e.g., MAC address).

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

[0274] An administrator and / or one or more users with appropriate permissions can enter device identifiers (e.g., MAC addresses) to exclude, and menu items and / or hierarchical menu levels. The exclusion information can be entered when the first MUI module is installed to the device. In other embodiments, the exclusion information can be added after installation and updated periodically.

[0275] In certain embodiments, prior to sending any commands for displaying any menus (and menu items), the hardware processor executing the input manager 1052 can check the exclusion information in the storage device 1120 to determine whether to exclude the initial display menu for the device or any menu items selected in relation thereto upon receiving the login history data or as a notification is received.

[0276] In one embodiment, the menu manager 1054 can compare the device identifier to the device identifiers listed in the exclusion information. When a match is made, certain menu items will be excluded from display on the MUI display 206. For example, when the selection in relation to includes one or more menu items listed to be excluded as the initial display menu (e.g., default menu) for the current menu, or a hierarchical menu level below the hierarchical menu level currently displayed on the MUI display 206, the menu manager 1054 can remove the excluded menu items from the menu prior to sending the display command, and then send the display command with the menu items removed. In this example, the removed menu items will not be displayed on the MUI display 206.

[0277] In other embodiments, certain menu items (or hierarchical menu levels) can be excluded based on the hierarchical menu level currently displayed as the current menu (in the first portion) or a previous menu (in the second portion). In one embodiment, one column of the exclusion table can include menu identifiers for hierarchical menu levels. A second column of the table can include menu items or hierarchical menu levels to exclude from display, respectively, in relation to the menu identifiers.

[0278] The menu identifier indicates the hierarchical menu level that can be displayed on the first menu or the second menu. Excluded menu items are menu items that cannot be selected from the displayed hierarchical menu level. These menu items can be application specific. In some embodiments, when a hierarchical menu is displayed as the current menu in the first portion 204 or as the previous menu in the second portion 208 and a selection is made, the menu manager 1054 checks the exclusion information to determine if any menu items for the displayed hierarchical menu level should be excluded before sending a command. Based on the determination, the menu manager 1054 can remove excluded menu items from the menu before sending a response command, then send the response command using the removed menu items. The exclusion can be performed by sending a separate exclusion command and / or instruction, or alternatively, the exclusion can be performed by modifying the first, second, and / or third display commands that provide a display of available menu items.

[0279] In other embodiments, the exclusion manager 1058 can send an exclusion command in conjunction with the display or reposition command, rather than using removed menu items to send the display or reposition command. In this embodiment, the display command will have all of the menu items for the menu, and the exclusion command will cause the display manager 1050 to delete the performed menu items included in the exclusion command before causing the display.

[0280] In other embodiments, the menu manager 1054 can limit the number of menu items to display based on frequency of use. For example, in one embodiment, the number of menu items can be limited based on frequency of selection. In some embodiments, the frequency can be determined over a predetermined period of time. The frequency of selection can be default or can be customizable, and can include, for example, a frequency of between 50% and 80%, although other frequencies of selection can be considered. By limiting the display of menu items to only include menu items that are used more than a particular threshold frequency, confusion in the menu system can be reduced and the menu experience can be simplified.

[0281] According to this embodiment, the input manager 1052 tracks selections 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 can be a menu item selection table or any other data structure (e.g., as described in detail herein).

[0282] In some embodiments, the selections of the user can be tracked over a default period of time. The period of time can be one day, one week, one month, or other default or customizable period of time. The particular period of time can be based on the application, such as a clinical trial or research type, a test type, an organization type (e.g., university, company), etc. The tracking can be repeated at each default period of time.

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

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

[0285] In other embodiments, the determination can be based on account numbers in addition to the user identifiers. For example, the input manager 1052 can determine the selection frequency for a menu item by at least two user identifiers that have the same account number. In this example, a group of users is formed where a single account number is associated and / or linked with two or more user identifiers. In another example, a group can include two or more account numbers that are associated and / or linked together. In yet another example, a group can be formed whereby N unique users are associated and / or linked with M unique account numbers, where N is greater than M. Identifying user identifiers that have the same account number can be accomplished using a shared account flag in the registry in conjunction with the menu item selection table to determine that at least two user identifiers selected during the period.

[0286] For a menu item, the number of selections of the menu item is aggregated for at least two user identifiers (determined from the menu item selection table). Likewise, the total number of selections is aggregated for at least two user identifiers (also determined from the menu item selection table). Then, the frequency is based on the aggregated selections of the menu item and the aggregated total selections.

[0287] In other embodiments, the frequency determination can be based on selections associated with user identifiers linked to other accounts (e.g., user teams). According to this embodiment, the input manager 1052 can identify linked accounts using a plurality of account flags set to particular values when the accounts are linked. Once identified, the input manager 1052 can determine the frequency of selection using selections from user identifiers associated with one of the linked accounts. In this embodiment, selections from other user identifiers or the same user identifier not associated with one of the linked accounts (in the case of the same user identifier being associated with different accounts) can be ignored (not used in the determination). Similar to the foregoing, the input manager 1052 can determine the number of selections of a menu item and the total number of selections to determine the frequency. In other embodiments, the systematized user interface control system 1102 can use selections from any of the user identifiers associated with one of the linked accounts to make the determination (and can aggregate the selections).

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

[0289] For identifying at least two user identifiers that make menu item selections, a plurality of selections of a menu item are aggregated for the at least two user identifiers (determined from the menu item selection table). Likewise, a total number of selections is aggregated for the at least two user identifiers (also determined from the menu item selection table). The frequency is then based on the aggregated selections of the menu item and the aggregated total selections.

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

[0291] The foregoing frequency can be used in conjunction with a limit command sent by the menu manager 1054. As described previously, the limit command functions similarly to the exclude command. The limit command is used to limit certain menu items to be displayed based on a criterion or two or more criteria. For example, the limit command can be based on the following criteria: (a) the frequency with which a user previously selected an item when logged into his or her account. In one example, this determination can be based on a particular time period. In another example, it can be based on a particular number of times a user logs into his or her account. Another criterion includes: (b) the frequency with which at least two users previously selected an item when logged into an account. In certain embodiments, this can include a particular user or an amount of time based on the total time a user logs into his or her account. Alternatively, it can be based on a particular number of users or a total number of logins. Still further, the criterion can include: (c) the frequency with which a user previously selected an item when logged into an account related to a plurality of accounts; (d) the frequency with which at least two users previously selected an item when logged into one or more accounts related to a plurality of accounts. For both of these examples, as described with respect to the previous examples (a) and (b), the frequency can be based on one or more combinations of a time period or a number of account logins for which the one or more users remain logged in. Still further, the criterion can include: (e) the frequency with which any user previously selected an item when logged into any account; and / or (f) the frequency with which any user previously selected an item when logged into any account related to a plurality of accounts. In both of these examples, a data structure (e.g., a table (or any other data structure described in this specification)) can be used to track previously selected items, which can be periodically purged upon a particular time period elapsing or a certain total number of one or more users logging in, as the case can be. In certain embodiments, the criteria described in the foregoing (c), (d), and (f) can be applied to team accounts, particularly where the users of these accounts are team members having one or more teams related to a plurality of accounts.

[0292] When the determined frequency is greater than or equal to the threshold percentage, the menu item can be limited in the immediately subsequent time period. The threshold can be application based. In one embodiment, the threshold percentage can be 50% or greater. In other embodiments, the threshold percentage can be 60% or greater. In yet other embodiments, the threshold percentage can be 70% or greater. In further embodiments, the threshold percentage can be 80% or greater. In other embodiments, the threshold can be a range of percentages. For example, the threshold percentage can be in a range between 75% and 85%. This specification has described particular percentages by way of example, and the threshold percentage is not limited thereto. Any threshold percentage or range can be used.

[0293] In other embodiments, a selection ratio can be used in place of a 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 can be used.

[0294] In other embodiments, the number of times a menu item is selected can be used in place of a selection frequency. For example, a particular selection threshold can be used in place of a percentage. The particular selection threshold can be 5, 10, 15, etc.

[0295] Once the restricted menu items are determined, the hardware processor can determine which menu items can be displayed on the MUI display 206 in subsequent subsequent time periods, and which menu items will be restricted. According to embodiments, any menu items that have a frequency above a threshold percentage can be displayed (e.g., not restricted).

[0296] In further embodiments, the display restrictions can be based on menu items that have a selection frequency below a certain threshold, such as below 50%, 40%, 30%, 20%, 10%, etc.

[0297] In several embodiments, the restriction commands can be sent based on various criteria. For example, one or more menu items can be excluded based on menu items that are designated as unavailable to a particular user. This can occur, for example, if the particular user does not select one or more menu items within a certain time period. Likewise, one or more menu items can be restricted based on menu items that are designed to be unavailable to two or more groups of users. In this example, the frequency at which two or more users select or do not select one or more menu items over a period of time can affect whether a restriction command is sent for those menu items. For the previous two examples, other embodiments contemplate sending restriction commands in a similar manner, but for individual teams and / or groups of teams (i.e., based on the frequency at which users of the team select menu items). Still further, other embodiments can restrict menu items based on a particular machine or group of machines that execute computer applications that one or more users have logged into.

[0298] In one embodiment, the menu manager 1054 can send a restriction command to the hardware processor that executes the display manager 1050. According to this embodiment, the restriction command can include a determination of menu items that have a frequency above a threshold percentage. The restriction command can be sent in conjunction with one or more display commands. Upon receiving the display command and the restriction command, the display manager 1050 can remove or eliminate menu items that are included in the display command but not included in the restriction command before causing the menu items to be displayed on the MUI display (206).

[0299] In other embodiments, the limit command can include menu items other than menu items determined to have a frequency above the threshold percentage. After receiving the display command and the limit command, the display manager 1050 can delete or remove menu items included in the display command and also included in the limit command before causing the menu items to be displayed in the MUI display 206.

[0300] In other embodiments, rather than a separate limit command, the display command can be modified by the menu manager 1054 to remove menu items other than menu items determined to have a frequency above the threshold percentage.

[0301] By using the limit command, the number of menu items (user selectable items or choices) can be limited to less than the number of menu items on the first menu and the second menu. For example, the first menu can include nine menu items, but the use of the limit command limits the total number of menu items that will be displayed to less than nine. For example, the total number of menu items (user selectable items) can be less than or equal to seven (or less than seven), less than or equal to five, less than or equal to three, or less than or equal to any other number. The number of menu items (finite number) described in this specification is merely an example, and the number can be any number selected to provide a limited display to avoid or prevent user overwhelm. In embodiments, menu items excluded from display due to the limit command are provided in the advanced quick view menu (270). In embodiments, the menu items excluded from display based on the limit number can be selected based on the frequency of selection.

[0302] In some embodiments, if the number of menu items determined to have a frequency of selection greater than the threshold percentage and the number of menu items is greater than the limit number (e.g., seven), the menu manager 1054 can increase the threshold percentage to reduce the number of menu items having a frequency of selection greater than the threshold percentage. Thus, the menu manager 1054 can be configured to select and display a particular number of menu items having the highest frequency of selection.

[0303] In one embodiment, the limiting function can be applied to operate on any type of MUI module as follows. The threshold percentage can be used to determine which menu items will be displayed (e.g., not limited to). For example, a threshold percentage of 90% or 80% can be used, which means that only menu items with a selection frequency higher than 90% or 80% are displayed. In one example, the selection frequency can be applied based on a user login session, which means that only menu items that are selected 90% or 80% of the time that the user is logged in are displayed. The limiting function can be applied to one or more menu levels, i.e., to the first menu level, the second menu level, etc. In some embodiments, the threshold can vary based on the menu level (e.g., lower levels can have a lower frequency display requirement, since lower levels often have more options, so the selection frequency can be lower). These menu items that do not meet the threshold (e.g., use 10% or less, or use 20% or less) are displayed in a high-level quick display menu, which varies depending on the menu currently displayed. In this way, the user's choices are limited to only the most frequently used choices in the entire MUI, allowing the user to navigate significantly faster. In certain embodiments, the choices that are excluded as described above can only be made available through the high-level quick display menu. Thus, for the 90% example, if only 90% of the available menus meet the threshold, then only those are displayed in the current menu, and the remaining portion (10% in this example) is displayed in the high-level quick display menu with a high-level quick display menu selector (also referred to herein as a high-level selector or a high-level quick display selector).

[0304] The 90% / 10% and / or 80% / 20% values are merely exemplary, and other values can be selected depending on the MUI module to be implemented. In one example, the limiting function can also be based on a default protocol, as opposed to a user customized protocol. For example, a vendor can sell an assay kit that includes a standard protocol that further allows the customer to make modifications. As the user moves through the menu system, the standard protocol options can be included in the available menu items displayed in the active portion, while the available user modifications can be displayed in the high-level quick display menu. The division of menu items can be adjusted based on actual user operation after the user has used a particular assay tool a number of times.

[0305] Likewise, by using the limiting command, the menu items (user selectable options) can be limited to less than the number of menu items in the first menu, the second menu, and the third menu.

[0306] In certain embodiments, the menu item selection table can delete the history of the newly decided selections when the time period expires. In this example, the previously excluded menu items become available again.

[0307] In embodiments, the MUI can provide team integration via communication between multiple MUI modules. An integrated system managed by a system consistent with embodiments of the present specification can be managed by multiple MUI modules configured to accomplish different tasks by different operators. For example, using the example of a laboratory information management system (LIMS), a manager console module, an experiment design module, a scale control module, an experiment analysis module, and an experiment procedure module can be provided. The manager console module can provide features and functionality for managing different users, operators, instruments, and teams. The experiment design module can allow one or more members of a team to design experiments to be performed by other members of the team. The scale control module can allow other team members to review scales, order more consumables, consider user experiment history, and future planned experiments. The experiment procedure module can allow team members responsible for performing experiments to access designed experiments and implement via interaction between the MUI, operators, and external systems. Finally, the experiment analysis module can allow other team members to access results of performed experiments. Based on user and team settings prepared via the manager console, each user can log into the system and have access to necessary modules to accomplish their responsible tasks. In embodiments, necessary modules can be installed in appropriate locations on computing devices to accomplish tasks (i.e., the experiment procedure module can be installed on a device connected to a laboratory instrument, while the manager console module can be installed on a desktop device). Thus, the system provided by the present specification allows for integration of workflow between multiple team members via use of a single consistent interface.

[0308] In embodiments, the display manager 1050 can be configured to provide one or more icons or animations to designate a "working" state of the systemized user interface control system 1102. The working state indication is provided to alert users that processing is in progress to prevent impatience when the systemized user interface control system 1102 is processing. In an embodiment, the working state indication is provided via a light fountain display presented in an unoccupied portion of the active or history section of the screen. For example, the bottom of the screen centered below the active section can be used for the light fountain display. The light fountain can provide a series of cascading columns consistent with the rest of the MUI. In an embodiment, the cascading columns can be presented in white and various shades of blue. In an embodiment, the cascading columns present four columns of elongated bars. Each column can contain a number of cascading columns between, for example, two and twenty different lengths. When the system is processing, the cascading columns can flash in different shades of white and blue and different lengths, giving the appearance of a waterfall or light fountain effect.

[0309] The embodiments described herein further include methods of designing a user interface system. For example, such a method can include designing a MUI in accordance with the embodiments described herein. The method of designing a user interface system can include generating a hierarchical menu tree as described herein. The hierarchical menu tree can include a series of menus, each menu containing menu items that lead to a subsequent series of menus. The method of designing a user interface system can further include selecting an execute menu to terminate a branch of the hierarchical menu tree, wherein the execute menu is configured to execute one or more commands within the software to provide one or more sets of instructions to the user and / or output one or more commands to a connected device, system, instrument, or machine. The method of designing a user interface system can further include constructing each menu in the hierarchical menu tree using one or more display modes, including at least an active display mode for display in an active portion of the user interface and a history display mode for display in a history portion of the user interface. Further aspects of the method of designing a user interface can further include methods of designing any of the menu features described herein.

[0310] In further embodiments, a MUI in accordance with the present application can provide an integrated help option during hierarchical menu navigation. A user can request help for a particular menu by pressing a particular key combination and / or by accessing a help option displayed in an advanced pop-up menu. The integrated help option can include one or more dialog boxes for providing the user with information about the displayed option. As described previously, the MUI provides a large amount of white space or background space. Thus, the help option can represent a pop-up window or dialog box that points the user to the portion of the MUI for which help is sought without compromising the original MUI display. In embodiments, the help function can be enabled to cause the dialog box to appear when the user moves a mouse over or otherwise indicates any item in the MUI.

[0311] In further embodiments, the history portion of the MUI can be further adapted to display menu items of a menu subsequent to the current menu. For example, as the user navigates through the current menu, the user can, for example, scroll a vertical scroll wheel to cause different menu items to be highlighted or emphasized. A submenu for the highlighted menu item can be displayed in the history portion to provide a visual representation of the subsequent menu of the current menu, including future items that can be subsequently selected.

[0312] In embodiments, as previously described, each of the first live portion and the second history portion are adapted to be consistently displayed in the same portion of the MUI. While the positioning of each of these portions is not limited to a particular location on the MUI, in certain embodiments, once selected, the location is maintained. Thus, the live portion of the MUI display is adapted to be consistently displayed within a first same area of the UI display to optimize the user's focus when interacting with the UI display, and the history portion of the MUI display is adapted to be consistently displayed within a second same area of the UI display to optimize the user's focus when interacting with the UI display.

[0313] The previous description provides an example menu arrangement for providing a UI display of a plurality of menus in a hierarchical menu tree. Figures 2D-2M Other examples of menu display configurations are provided. The following menu display configurations can be used without limitation in any combination with each other and with the previously disclosed menu configurations. For example, selection of a particular menu item anywhere in the hierarchical menu tree can cause the processor to execute a command to cause the UI display to switch to any of the menu configurations described in this specification. In particular, a particular menu display configuration can be associated with a particular menu selection.

[0314] Figure 2D Another example of a menu display configuration in an embodiment is shown. Figure 2D An example of two scroll wheel configurations is illustrated, where the first scroll wheel option has sub-options in a second scroll wheel. For example, selection of an option in a first scroll wheel having options causes the display of sub-options in the second scroll wheel associated with the selected option. In an embodiment, the first portion 214 of the display can initially display the first scroll wheel, and as options are selected from the first scroll wheel, the first scroll wheel having options can be repositioned to the second portion 216 adjacent to the first portion. The first portion can then display the second scroll wheel having sub-options of the first option, for example, in a parallel fashion (the first scroll wheel is displayed parallel to the second scroll wheel in the same visual orientation).

[0315] In a further embodiment of this embodiment, both the first and second wheels can be displayed in the first portion 214 of the MUI display 206. The first wheel can be displayed in a first sub-portion of the first portion 214, and the second wheel can be displayed in a second sub-portion of the first portion 214. As used in this specification, a sub-portion can be a partition of a larger portion. A sub-portion can also be used interchangeably with a sub-portion. In an embodiment, menu items in the first wheel are selected by clicking on any menu item in the first wheel or by rotating any menu item in the first wheel to a highlighted position. Selecting an item in the first menu on the first wheel can thus cause the second menu displayed on the second wheel to be modified accordingly. In yet a further embodiment of this embodiment, the first portion 214 can be divided into more than two sub-portions, each sub-portion including a wheel displaying a relative menu. Thus, three wheels can display a first, second, and third menu, respectively representing different levels of a hierarchical menu tree. In another example, three wheels can display a second, third, and fourth menu. Other examples can include any number of wheels.

[0316] In a further embodiment, multiple wheels can be displayed in multiple sub-portions of the first portion 204 to allow a user to select multiple menus in the same hierarchical menu level. For example, selecting a particular menu item in one menu level can result in multiple sub-menus being displayed in the same level. Thus, selecting an item in a second menu level can result in multiple third menus being displayed, each third menu containing multiple third menu items. In an embodiment, the multiple sub-menus displayed can be execution menus to allow a user to make multiple execution menu selections simultaneously. In embodiments where multiple sub-menus are displayed, the multiple sub-menus can be related to each other or associated.

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

[0318] Figures 2F-2G Yet another example of a menu display configuration in an embodiment is shown. These figures show the wheel options switching from horizontal to vertical. Figure 2FA selection menu, such as displayed in a graphical wheel, is displayed with the displayed options being rotated in a horizontal direction (left and right). The wheel is displayed in a first portion of the graphical user interface display. Upon selection of an option (menu item in the list of options), the graphical wheel is switched to a vertically rotatable wheel. For example, the wheel is moved or repositioned to a second portion of the graphical user interface display and the first portion of the graphical user interface display now displays a list of sub-options related to the selected option in the previous option menu.

[0319] In one embodiment, the second portion of the display can display up to a critical number of menu levels, for example, after which a different visualization configuration can be employed to display past menu levels to prevent the second portion from becoming too large.

[0320] For example, please refer to Figure 2C If there is more than a critical number of menu levels (for example, Figure 2C two levels 202, 210 are displayed), a visualization mechanism can be employed that can visualize all past menu levels without necessarily growing the second portion of the display (for example, Figure 2C 208). For example, consider a critical number of 3. In this example, the second portion of the display can display 3 menu levels. When the next level (for example, the 4th menu level) is selected, the second portion can display the last 3 selections (the bottom 3 levels) and the items in the second portion can be scrolled up and down. Thus, in this example, the selection of the first menu level can be viewed by scrolling up the second portion. By way of another example, the second portion can always display the top two levels, i.e., the first two decisions and the last decision. In this way, the user displays the overall context of the workflow, for example, from top to bottom. Clicking or scrolling the second portion allows the user to expand the menu items, for example, like a collapsible accordion.

[0321] In another aspect, a search function can be provided in relation to the wheel. A search keyword allows filtering of the wheel options available to the user. The search function is helpful in dealing with long option wheels or multi-option wheels, which can take a long time to navigate.

[0322] Figures 2H-2J An example of the first portion and the second portion being displayed as a series of concentric circles in one embodiment. Please refer to Figure 2H The dial 220 can be rotated clockwise or counterclockwise to view in the option window 218, menu items, or items to be selected. An area of the dial (for example, a circle) 220 is clicked to select an option. Selecting an option, for example, viewed via the option window 218, transitions the user interface to the configuration shown in Figure 21 For example, in Figure 2IIn one embodiment, the concentric dials expand from the inside out, displaying another concentric circle to represent another level (e.g., sub-level) of menu items or paths. Sub-options can be viewed through the option window 222 (also referred to as a dial) on the circle 224 by rotating the dial 224 clockwise or counterclockwise. An option in the level (displayed as sub-option "n") 222 can be selected by clicking on the area of the circle 224 (i.e., not overlapping the inner circle or dial 220). In another embodiment, selecting an option (e.g., as shown in Figure 2I the configuration shown in Figure 2H For example, the next level of options expands from the selected option, expanding the dial to display another inner dial 224 with an option window 222. In one embodiment, the number of options that can be viewed on the option window (e.g., 218 and 222) is not limited, and thus an unlimited number of options can be displayed and selected for an application.

[0323] In one embodiment, the option window (e.g., 218) can be enlarged to display the selected option (e.g., brightly displayed) and one or more unselected options, for example, an unselected option appearing before the selected option and another unselected option appearing after the unselected option.

[0324] In another aspect, the option window (e.g., 219) can display more than one item or option at a time, for example, 3 menu items or options. In this example, clicking on a menu item in the option window selects the option. After selection, the selected option can be displayed in a brightly displayed format or another different format, for example, to distinguish the selected option from the unselected options appearing in the option window.

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

[0326] Figure 2J A tree type of menu levels is shown in one embodiment.

[0327] Figure 2KThe illustrated hierarchical menu tree includes a menu first item menu, 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 the other three execution menus are associated with sub-sub-menu items 1-3. Selection of menu item 1 from the first menu displays the second menu of sub-menu items. Selection of sub-menu item 1 causes the execution menu of sub-menu item 1 in which processing parameters can be selected. Selection of sub-menu item 2 causes the third menu of sub-sub-menu items. Selection of any of sub-sub-menu items 1-3 causes the execution menu of these relative third menu items.

[0328] Figure 2K Another example of a menu display configuration in an embodiment is shown. A graphical element 242, such as a scroll wheel or a slide bar (or another graphical element) is shown in a portion 240 of the display screen. The graphical element 242 (e.g., scroll wheel) is first ordered using the most recent "n" items 244 (in reverse chronological order) with a search function of all menu items 248, this search box or area 246 is adjacent to the list (e.g., text ordered list). In another embodiment, for example, when a search term is entered in the search box 246, the menu items displayed in the menu items 248 will be indexed. The entire scroll wheel 242 is scrollable. For example, the user can scroll the entire scroll wheel 242 or enter a search string in the search box 246. Entering a search term in the search area 246 displays the menu items that match the search term as the search characters are entered. For example, on each character entered, the one or more menu items that most closely match the search characters are indexed in the menu items 248. The scroll wheel 240 is divided into two separate scroll wheels, one scroll wheel displays the most recently selected menu items 244 and the other scroll wheel displays the indexed list or all menu items 248. The two scroll wheels 244 and 248 are independently scrollable or moveable from each other. Thus, for example, the entire wheel 242 is made to move or scroll as one scroll wheel. As the input of search terms or characters in the search area 246 is received or detected, the scroll wheel is divided into two separate scroll wheels 244 and 248 that are independently scrollable. One of the two separate scroll wheels (e.g., 248) displays a filtered list of menu items based on the search.

[0329] Figure 2LAn example is shown of a scrollable wheel that scrolls or slides from a first menu item to a last menu item and from the last menu item back to the first menu item. In this embodiment, the graphical element (e.g., scroll wheel or slide axis) that displays the menu items does not complete a full rotation or revolution, but instead stops at the last menu item or the first menu item (if rotating from the last menu item). In this way, for example, the beginning and end of the menu are always apparent because they are not merged or connected. This technique reduces computer processing cycle time because the scroll wheel and / or slide axis is able to convey (and the user is able to immediately understand) the entire menu of choices and clearly indicates where or what is the first menu item and where or what is the last menu item in the choices displayed by the scroll wheel and / or slide axis, so that the scroll wheel or slide axis does not need to repeat scrolling to try to determine what is the first menu item and what is the last menu item, or to determine whether all menu items have been visited.

[0330] In an embodiment, the scroll wheel and / or slide axis does not need to complete a full revolution; for example, the scroll wheel and / or slide axis does not need to make a full rotation or complete a circular revolution. For example, the scroll wheel and / or slide axis rotates or slides from a beginning menu item to an end menu item and reverses rotation to rotate or slide from the end menu item back to the beginning menu item. In this way, for example, the beginning and end of the menu are always apparent because they are separate and not merged or connected together. This technique reduces processing time because the scroll wheel and / or slide axis is able to convey (and the user is able to immediately understand) the entire menu of choices and clearly indicates where or what is the first menu item and where or what is the last menu item in the choices displayed by the scroll wheel and / or slide axis. In addition, as the scroll wheel and / or slide axis rotates, the selectable choices can be displayed in a more prominent manner, for example, using larger text, bolded text, etc. As the scroll wheel and / or slide axis rotates / slides to different positions or will be selectable as the scroll wheel and / or slide axis continues to rotate / slide, the previously selectable choices can be displayed in a less prominent manner, for example, by shrinking or darkening the text. In an embodiment, the more brightly displayed choices can be displayed as appearing closer to the user than the less brightly displayed choices.

[0331] Please refer to Figures 2M-2O , the first menu item 252 is displayed in the center of the scroll wheel (or slide axis) 250. The menu item displayed in the center can be displayed in a brightly displayed format (e.g., larger characters, different colored font, etc.). A blank space appears before the first menu item (e.g., above the center of the scroll wheel displaying the first menu item). The next menu items (e.g., 254, 256) appear adjacent (e.g., below) the display of the first menu item. The scroll wheel is scrolled (e.g., in a straight direction) to display other menu items, for example, as shown in Figure 2M . For example, as shown in Figure 2N , as the scroll wheel 250 is scrolled upward, the next menu item is displayed. Figure 2NThe last menu item is displayed at the center of the wheel, with the previous menu item displayed adjacent (e.g., above) the last menu item. In this embodiment, the wheel or thumb 250 does not rotate to display the first menu item after the last menu item 258. Rather, the wheel stops rotating at the last menu item 258. A blank sample is displayed below the last menu item 258. Likewise, directing backwards (e.g., scrolling the wheel in the reverse direction) displays the previous menu item above the first menu item.

[0332] Although Figure 2O The example graphical wheel shown illustrates a vertical wheel, but a horizontal wheel would function in a similar manner. For example, the first menu item can appear at the center of the horizontal wheel, with the next menu item appearing horizontally adjacent to the first menu item (e.g., to the right of the center). In this example, scrolling the wheel to the left would display the other menu items. When the last menu item is reached by scrolling, the last menu item appears in the center, and the last menu item is followed (e.g., to the right of the last menu item) by a blank sample. In another aspect, the orientation of the rotation can be reversed: for example, with a vertical wheel, scrolling down (rather than up) to direct from the first menu item to the last menu item; with a horizontal wheel, scrolling right can direct from the first menu item to the last menu item. The number of menu items (options) displayed at one time on the wheel is configurable, e.g., based on the screen size and / or screen area for the wheel arrangement, and is not limited to Figures 2M-2O the six items shown in FIG. 6.

[0333] A non-limiting application of this user interface is to select a channel to watch on a television (TV). A broader category can be displayed in the top horizontal area, with a narrower category displayed below, with the paging items displayed vertically, e.g., on a vertical wheel. For example, see Figure 2N "Roller Option 1" can represent a genre, while "Sub-Option 1" can represent programs and / or movies in a grid.

[0334] In one embodiment, the systemized user interface control system 1102 provides an interface for a user to perform a process. The process can include conducting an experiment, performing one or more manufacturing operations, or any other procedure.

[0335] The following describes in detail various instructions for conducting experiments consistent with embodiments of the present specification. Instructions for conducting experiments can be used to manipulate, design, execute, audit, measure, analyze, store, and perform any other work related to the experiments. Experiments can be, but are not limited to, one or more assays. The systematized user interface control system 1102 can incorporate and / or interface with an assay system and provide commands to generate an MUI display 206 for the system. With the commands, the MUI display 206 can display or provide a visual presentation of a workflow and / or menu item path for an assay. The assay can include one or more electrochemiluminescence (ECL) assays.

[0336] The methods of the present embodiments can be used in conjunction with a variety of assay devices and / or formats. The assay devices can include, for example, assay modules such as assay discs, cartridges, multi-well assay discs, reaction vessels, test tubes, cuvettes, flow cells, assay chips, lateral flow devices, etc. having wells, chambers, or assay regions in which assay reagents (which can include target agents or other binding reagents) are added or pre-loaded as an assay is conducted. These devices can employ a variety of assay formats for specific binding assays such as immunoassays or immunochromatographic assays. Illustrative assay devices and formats are described below in the present specification. In certain embodiments, the methods of the present embodiments can employ assay reagents that are stored in a dry state, and the assay devices / kits can further contain or have desiccant materials for maintaining the assay reagents in a dry state. Assay devices pre-loaded with assay reagents can significantly improve speed, reduce complexity of assay metrics, while maintaining superior stability during storage. The dry assay reagents can be any assay reagents that can be dried and then reconstituted prior to use in an assay. These include, but are not limited to, binding reagents, enzymes, enzyme substrates, indicator dyes, and other reactive compounds that can be used in a binding assay. Assay reagents can also include substances that do not directly participate in the detection mechanism but play a supportive role in the assay, including, but not limited to, blocking agents, stabilizers, detergents, salts, pH buffers, preservatives, etc. The reagents can exist in free form or supported on a solid phase including the surface of a compartment (e.g., chamber, channel, flow cell, well, etc.) in an assay module, or the surface of a gel, bead, or other particulate carrier.

[0337] A variety of solid phases are suitable for the methods of the embodiments, including conventional solid phases from the field of binding assays. The solid phase can be made of a variety of different materials, including polymers (e.g., polystyrene and polypropylene), ceramics, glass, composites (e.g., carbon-polymer composites, such as carbon-based inks). Suitable solid phases include the surface of a macroscopic object, such as the interior surface of an assay vessel (e.g., a test tube, cuvette, flow cell, cassette, well in a multi-well plate, etc.), a slide, an assay chip (e.g., for gene or protein chip measurements), a needle or probe, a bead, a filter medium, a lateral flow medium (e.g., a filter membrane for a lateral flow test strip), etc.

[0338] Suitable solid phases also include particles (including but not limited to colloids or beads) that are commonly used in other types of particle-based assays, such as magnetic, polypropylene, and latex particles, materials that are commonly used in solid phase synthesis, such as polystyrene and polyacrylamide particles, and materials that are commonly used in chromatographic applications, such as silica, alumina, polyacrylamide, polystyrene. The material can also be a fiber, such as a carbon nanofiber. The microparticle can be an inanimate biological entity; or can include animate biological entities, such as cells, viruses, bacteria, etc.

[0339] The particles used in the methods of the application can include any material suitable for attachment to one or more binding partners and / or labels, and can be collected via, e.g., centrifugation, gravity, filtration, or magnetic collection. A variety of different types of particles that can be attached to binding reagents are commercially available for use in binding assays. These include non-magnetic particles as well as particles that include magnetizable material, which allow the particles to be collected by a magnetic field. In one embodiment, the particles are composed of an electrically conductive and / or semiconductive material, such as colloidal gold particles.

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

[0341] Particles used in the present methods can be encoded to allow identification of particular particles or subpopulations of particles in a mixture of particles. The use of such encoded particles has been used to allow multiplexing of assays that utilize particles as solid phase supports for binding assays. In one approach, particles are manufactured to include one or more fluorescent dyes, and particular populations of particles are identified based on the intensity and / or relative intensity of fluorescence emission at one or more wavelengths. This approach has been 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, particles can be encoded by differences in other physical properties (e.g., size, shape, embedded optical patterns, etc.).

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

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

[0344] Methods for measuring the amount of an analyte also include techniques that measure the analyte by detecting a label directly or indirectly attached (e.g., by using a labeled binding partner for the analyte) to the analyte. Suitable labels include labels that are directly visualizable (e.g., particles that are visible to the eye and labels that produce a measurable signal such as light scattering, light absorption, fluorescence, chemiluminescence, electrochemiluminescence, radioactivity, magnetic fields, etc.). Labels that can be used also include enzymes or other chemically reactive species that have a chemical activity that results in a measurable signal such as light scattering, absorbance, fluorescence, etc. Enzyme-linked immunosorbent assays (ELISA) or enzyme immunoassays (EIA) have been well established to use enzymes as labels. In the ELISA format, an unknown amount of antigen is immobilized on a surface, and then specific antibodies are washed over the surface so that they can bind to the antigen. The antibodies are linked to enzymes, and in the final step, a substance is added that the enzymes convert into a product that provides a detectable change in signal. The formation of the product can be detectable, for example, because of a difference between the substrate that results in a difference in a measurable property such as absorbance, fluorescence, chemiluminescence, light scattering, etc. Some, but not all, of the measurement methods that can be used in the solid phase binding methods according to embodiments can benefit from or require a washing step to remove unbound components (e.g., labels) from the solid phase. Thus, the methods of embodiments can include such a washing step.

[0345] The methods disclosed in this specification can be performed manually, using automated techniques, or both. The automated techniques can be partially automated, e.g., one or more modular instruments, or fully integrated automated instruments.

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

[0347] Automated systems (modules and fully integrated) that the methods of the present specification can be implemented in can include the following automated subsystems: computer subsystems, which can include hardware (e.g., personal computers, laptop computers, hardware processors, disks, keyboards, displays, printers), software (e.g., drivers, driver controllers, and data analyzers), and databases; liquid handling subsystems, such as sample and reagent handling, such as robotic dispensing heads, syringes, agitation devices, ultrasonic mixing devices, magnetic mixing devices; sample, reagent, and consumable storage and handling subsystems, such as robotic manipulators, tube or cap or film piercing, decapping devices, conveyance devices such as linear and circular conveyors and robotic manipulators, tube racks, plate carriers, slot carriers, dispenser tip carriers, plate shakers; centrifuges, assay reaction subsystems, such as fluidics and consumable (e.g., test tubes and multi-well plates) based; vessel and consumable washing subsystems, such as plate washing devices; magnetic sorter or magnetic particle concentrator subsystems, such as flow chambers, tubes, and plate types; cell and particle detection, sorting, and isolation subsystems, such as flow cytometers and Coulter counters; detection subsystems, such as colorimetric, turbidimetric, fluorescent, and ECL detectors; temperature control subsystems, such as air handling, air cooling, air heating, fans, blowers, water baths; waste subsystems, such as liquid and solid waste containers; global unique identifier (GUI) detection subsystems, such as 1D and 2D barcode scanners, such as flatbed and wand types; sample identifier detector subsystems, such as 1D and 2D barcode scanners, such as flatbed and wand types. Analysis subsystems, such as chromatographic systems, such as high performance liquid chromatographs (HPLCs), fast protein liquid chromatographs (FPLCs), and mass spectrometers, can also be modules or fully integrated. Automated systems consistent with embodiments of the present specification can be controlled and / or managed by a systemized user interface control system 1102.

[0348] Systems or modules that perform sample identification and preparation can be combined with (or abut or adjacent or mechanically linked or coupled to) systems or modules that perform assays and perform detection or perform both. Multiple modular systems of the same kind can be combined to increase throughput. Modular systems can be combined with modules that perform other types of analysis (e.g., chemical, biochemical, and nucleic acid analysis).

[0349] Automated systems can allow batch, continuous, random access, and point of care workflows, and single, moderate, and high sample throughput.

[0350] The system can include one or more of, for example, a plate sealer (e.g., Zymark), a plate washer (e.g., BioTek, TECAN), a reagent dispenser and / or an automated dispenser 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 sample retrieval module. One or more of these devices are coupled to the apparatus via mechanical means so that the entire assay process can be performed automatically. According to alternative embodiments, the containers (e.g., plates) are manually moved between the apparatus and the various devices (e.g., plate stacks).

[0351] The automated system can be configured to perform one or more of the following functions: (a) moving consumables (e.g., plates) into, out of and within the detection subsystem; (b) moving consumables between other subsystems; (c) storing consumables; (d) sample and reagent handling (e.g., adapted to mix reagents and / or introduce reagents into consumables); (e) consumable shaking (e.g., for mixing reagents and / or for increasing reaction rate); (f) consumable washing (e.g., washing plates and / or performing assay washing steps (e.g., well aspiration); and (g) measuring ECL in flow cells or consumables (e.g., tubes or plates). The automated system can be configured to handle individual tubes, multi-well plates (e.g., 96 or 384 well plates) placed in racks.

[0352] Methods for integrating components and modules in an automated system are well known in the art, as described in this specification, see, for example, Sargeant et al., Application Name: Platform Perfection, Medical Product Outsourcing, filed May 17, 2010.

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

[0354] In embodiments, the control unit controls all instrument functions using a graphical user interface and includes readout devices such as a display, input devices such as a keyboard and mouse, and a personal computer using, for example, a Windows operating system. In embodiments, the core unit is composed of several components to manage sample delivery to each designated analysis module. The actual composition of the core unit depends on the configuration of the analysis modules that can be constructed by one of skill in the art using methods known in the art. In embodiments, the core unit includes at least a sampling unit and a rack rotor as the main components. Transport lines and a second rack rotor are possible extensions. Several other core unit components can include a sample rack loader / unloader, a connection port, a barcode reader (for racks and samples), a water supply system, and a system interface port. In embodiments, the analysis modules perform ECL assays and include a reagent area, a measurement area, a consumable area, and a pre-clean area.

[0355] Methods of the present invention can be applied to single or multiplexed formats, where multiple assay measurements are performed on a single sample. Multiplexed measurements that can be used with the present invention include, but are not limited to, the following uses of multiplexed measurements: i) require the use of multiple sensors; ii) use discrete assay domains on a surface (e.g., an array) that are distinguishable based on their location on the surface; iii) require the use of reagents coated on particles that are distinguishable based on particle properties (e.g., size, shape, color, etc.); iv) produce assay signals that are distinguishable based on optical properties (e.g., absorbance or emission spectra); and / or v) are based on temporal properties of the assay signal (e.g., time, frequency, or phase of the signal).

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

[0357] In one embodiment, the surface comprises a plurality of capture reagents for one or more analytes present in the sample, and the plurality of capture reagents are distributed over a plurality of resolvable binding regions on the surface. A "resolvable binding region" is the smallest surface area associated with a single binding event that can be resolved and distinguished from another region where another single binding event occurs, under the conditions used to perform and analyze the measurement. Thus, the method comprises binding one or more analytes to one or more capture reagents on the surface, determining whether the analyte is present in a plurality of resolvable binding regions on the surface, and identifying the number of resolvable binding regions that contain the analyte of interest and / or the number of regions that do not contain the analyte.

[0358] The resolvable binding regions can be optically interrogated in whole or in part, i.e., each individual resolvable binding region can be individually optically interrogated and / or the entire surface comprising a plurality of resolvable binding regions can be imaged, and one or more pixels or groups of pixels in the image can be mapped to a single resolvable binding region. The resolvable binding regions can also be particles in a plurality of particles. Resolvable binding regions that exhibit a change in their optical signature can be identified by conventional optical detection systems. Depending on the species detected (e.g., the type of fluorescent entity, etc.) and the wavelength of operation, filters designed for a particular wavelength can be used for optical interrogation of the resolvable binding regions. In embodiments that use optical interrogation, the system can comprise more than one light source and / or multiple filters to adjust the wavelength and / or intensity of the light source. In some embodiments, a CCD camera is used to retrieve the optical signal from the plurality of resolvable binding regions. Other non-limiting examples of camera imaging systems that can be used to retrieve the image include charge injection devices (CID), complementary metal-oxide-semiconductor (CMOS) devices, scientific CMOS (sCMOS) devices, and time delay integration (TDI) devices, as are well known to those skilled in the art. In some embodiments, a scanning mirror system coupled to a photodiode or a photomultiplier tube (PMT) can be used for imaging.

[0359] In embodiments, the binding of each analyte to its corresponding capture reagent is performed in parallel by contacting the one or more surfaces with a single liquid phase volume comprising the plurality of analytes. In embodiments, the plurality of analytes comprises the analyte and one or more additional analytes. In embodiments, each step of the method is performed in parallel for each analyte. In embodiments, the method is a simultaneous multiplexed assay. This specification describes multiplexed measurements of analytes on a surface. See also, e.g., U.S. Patent Nos. 10,201,812; 7,842,246; and 6,977,722, the entire contents of which are incorporated herein by reference.

[0360] In a particular embodiment, the methods of the application can be used in a multiplexed format by binding multiple different analytes to multiple capture reagents for those analytes, immobilizing the retrieved analytes on coded beads, such that the code identifies the retrieved reagent (and the analyte target) for a particular bead. The methods can further comprise counting the number of beads with bound analyte (using the detection methods described in this specification).

[0361] Alternatively or in addition, the capture reagents can be bound, directly or indirectly, to one or more solid phases in different discrete binding regions, e.g., as in a binding array, where the binding regions are individual array elements, or in a set of beads, where the binding regions are individual beads, such that a discrete assay signal is generated and measured at each binding region. If the capture reagents for different analytes are immobilized in different binding regions, then different analytes bound to those regions can be measured independently. In one example of this embodiment, the binding regions are prepared by immobilizing discrete regions of capture reagents that bind to the target analytes on one or more surfaces. Alternatively, the surfaces can partially define one or more boundaries of a container (e.g., a flow cell, a well, a cuvette, etc.) that holds the sample, or through which the sample is passed. In preferred embodiments, individual binding regions are formed on electrodes for electrochemical or electrochemiluminescent assays. Multiplexed measurement of analytes on surfaces comprising multiple binding regions using electrochemiluminescent methods has been 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, all of which are incorporated by reference herein in their entireties).

[0362] Still further, the capture reagent can be directly or indirectly bound to the electrode surface, as previously described, with the selectivity including different discrete binding regions. The electrode surface can be a component of a porous disk and / or flow cell. The electrode can comprise an electrically conductive material, such as a metal, e.g., gold, silver, platinum, nickel, steel, iridium, copper, aluminum, electrically conductive allowed materials, etc. The electrode can also comprise an oxide coated metal, such as an alumina coated aluminum. The electrode can comprise a working electrode and a helper electrode made of the same or different materials, such as a metallic helper electrode and a carbon working electrode. In a particular embodiment, the electrode comprises a carbon-based material, such as carbon, carbon black, graphitic carbon, carbon nanotubes, carbon nanofilaments, graphite, graphene, carbon fibers, and mixtures thereof. In an embodiment, the electrode comprises elemental carbon, such as graphite, carbon black, carbon nanotubes, etc. Preferably, the electrode can comprise an electrically conductive carbon polymer composite, electrically conductive particles dispersed in a matrix (e.g., carbon ink, carbon paste, metallic ink, graphene paint), and / or an electrically conductive polymer. A particular embodiment of the present application is an assay module, preferably a porous disk, having an electrode (e.g., working and / or helper electrode) comprising carbon (e.g., a carbon layer, and / or a screen printed layer of carbon ink).

[0363] In embodiments, each binding region comprises a target agent complement capable of binding a target agent, and each anchor reagent and capture reagent comprises a supplemental cross-linking reagent capable of binding a cross-linking reagent, and the method further comprises immobilizing the capture reagent and anchor reagent at each binding region by: (1) binding the capture and anchor reagents to the target agent complement via the supplemental cross-linking reagent to the cross-linking reagent; and (2) binding the product of step (1) to the binding region comprising the target agent complement, wherein (i) each binding region comprises a different target agent complement, and (ii) each target agent complement selectively binds to one of the target agents.

[0364] Thus, in embodiments, the surface comprises a target agent complement; a target agent is linked to a cross-linking reagent; each of the capture reagent and anchor reagent comprises a supplemental cross-linking reagent. Thus, in embodiments, the target agent complement on the surface binds a target agent, the target agent is linked to a cross-linking reagent, which binds to the supplemental cross-linking reagent on the capture reagent and anchor reagent.

[0365] In embodiments, the cross-linking reagent has more than one binding site for a supplemental cross-linking reagent, and the immobilization of the capture reagent and the anchor reagent further comprises: linking the capture and anchor reagents to the target reagent-linked cross-linking reagent via the supplemental cross-linking reagent; and binding the product to a binding region comprising a complement of the target reagent, wherein (i) each binding region comprises a different complement of the target reagent; and (ii) each complement of the target reagent selectively binds one of the target reagents. For example, where the target reagent is an oligonucleotide, the cross-linking reagent is streptavidin, and the supplemental cross-linking reagent is biotin, a biotin-labeled oligonucleotide can bind to a first of four biotin binding sites on the streptavidin to form a target reagent-linked cross-linking reagent. A biotin-labeled capture reagent (i.e., a capture reagent linked to a supplemental cross-linking reagent) can then bind to the remaining biotin binding sites on the streptavidin to link the target reagent to the capture reagent.

[0366] Exemplary target reagents and target reagent complements are described in the specification. In embodiments, the target reagent and the target reagent complement are two members selected from the group consisting of avidin-biotin, streptavidin-biotin, antibody-hapten, antibody-antigen, antibody-antigen label, nucleic acid-complementary nucleic acid, aptamer-aptamer target, and receptor-ligand. In embodiments, the target reagent is biotin and the target reagent complement is streptavidin. In embodiments, the cross-linking reagent and the supplemental cross-linking reagent are different binding partner pairs than the target reagent and target reagent complement pairs. In embodiments, the cross-linking reagent is avidin or streptavidin and the supplemental cross-linking reagent is biotin. In embodiments, the target reagent and the target reagent complement are complementary oligonucleotides.

[0367] In embodiments, the methods of the present application are applied in single or multiplexed formats, in which multiple assay measurements are performed on a single sample. Multiplexed measurements that can be used with the present application include, but are not limited to, multiplexed measurements using i) multiple sensors; ii) discrete assay regions on a surface (e.g., an array) that are distinguishable based on position on the surface; iii) reagents coated on distinguishable particles based on particle properties (e.g., size, shape, color, etc.); iv) distinguishable assay signals based on optical properties (e.g., absorbance or emission spectra); or v) temporal properties of the assay signals (e.g., time, frequency, or phase of the signals). Exemplary assay formats include V-PLEX (www.mesoscale.com / en / products_and_services / assay_kits / v-plex) and U-PLEX (www.mesoscale.com / en / products_and_services / assay_kits / u-plex_gateway, and U.S. Patent Nos. 10,201,812 and 10,189,023, incorporated herein by reference in their entireties). Additional ultrasensitive assay formats include U.S. Provisional Application Nos. 62 / 812,928, filed March 1, 2019, and 62 / 866,512, filed June 25, 2019, incorporated herein by reference in their entireties.

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

[0369] The aforementioned user interface methods can also be incorporated into the user interface of an assay system. The assay system described below allows a user to perform an assay via the user interface. Examples of user interfaces incorporated into an assay system for the method of strategy are described below. The term "system software" or "system" and its user interface, as referenced below in describing the function of the assay system, refers to the software that implements the assay system. The user interface can display or visualize the path of the workflow and / or menu items.

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

[0371] Advanced Context Menu - a menu of options that depends on the particular context (e.g., the current screen, sub-step, and screen state).

[0372] Assay Method - a method of performing an assay, including but not limited to: 1. Instrument specifications that should be performed and parameters for performing the protocol; 2. Test plate planning; 3. Calibration instrument titration discrimination, e.g., dilution factor; 4. Control planning; 5. Sample replication scheme.

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

[0374] Compatible Protocol - protocols are compatible if they have the same basic outline and steps, although dilution ratios, incubation times, wash times, etc. can differ. Protocols are considered compatible if they can be performed together on an automated platform during the same run.

[0375] Completed Run - a run that has been aborted, completed with flags, or successfully completed.

[0376] CV - coefficient of variation.

[0377] Database Purge - resetting the entire database, restoring the database to the state it was in at system installation.

[0378] ECL - electrochemiluminescence. A proprietary format used for detecting biologically significant molecules.

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

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

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

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

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

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

[0385] Instrument Software - Software that controls the instrument hardware

[0386] LED - Light-emitting Diode. Light source.

[0387] Normal State - The state of the instrument if the software is executing properly without any errors or warnings. The instrument will return to the normal state once the error state is recovered and / or the warning message is acknowledged.

[0388] Run - The execution of a run includes 0 or more named samples and 1 or more assays, and the samples are tested according to the information described in the assays.

[0389] Run Owner - The user who established the run.

[0390] Sample - A general term that includes the material to be analyzed, including calibrators, controls, blanks, and unknowns.

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

[0392] Sample Layout - The sample position and sample ID on the plate.

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

[0394] Spot Layout - The analyte position and name in a well on a plate.

[0395] Step - One of a series of individual, consecutive stages in a process toward a goal. A step constitutes a broad phase that can be composed of multiple sub-steps.

[0396] Sub-step - One of a series of independent, consecutive stages in a process toward completing a step. A sub-step constitutes a focused activity within a step.

[0397] Unexpected Barcode - This barcode is different from the expected barcode. Consumables can also be considered to have an "unexpected barcode" if no barcode is read.

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

[0399] UI Warning Event - All messages that require user response. The user should correct the error and / or acknowledge the message before proceeding. For example, a UI warning event can be that the instrument is in an "unready" state.

[0400] System Events Log - A permanent record of events that occur in the software that are not related to the instrument.

[0401] Figure 2E A flowchart of the process for a first user to log into the user interface for the assay system in one embodiment is shown. At 402, at each start, the system software for the assay method can check if the End User License Agreement (EULA) for the assay system has been accepted. When the user first starts the system software, the EULA is displayed. After the user accepts the agreement, a record of the user name, date, and time is established. If the user has not previously accepted the agreement, the EULA is displayed at step 404 and the user is allowed to accept the agreement. At step 406, if the user does not accept the agreement, the software is closed. At step 408, an initial screen is displayed containing: system software branding, copyright, legal disclaimers, software version. The initial login screen requests a user name at step 410. In one embodiment, the system software can display user names that have been used to log into the system in the past to reduce errors due to typing the user name. The user is also allowed to enter a new user name that has not been used to log in before. After the user name is selected (or received) at step 412, the software prompts the user to enter a password for the user name at step 414. In one embodiment, the system software can also use biometric means such as facial recognition, voice, and / or fingerprint to log in or verify the login. In another embodiment, the system software can use a badge key card containing information that can be scanned or read via near field communication. At step 416, the system software receives the entered password. Once the user name and password are entered, the system software verifies the user at step 418. If the user is successfully verified, the user interface proceeds to the start screen at 420. Otherwise, the system software prompts the user to try again via the user interface. In one embodiment, the system software then requires all users to log in to access the software. In one embodiment, authentication can be performed through Microsoft Windows® authentication tools and can be configured to authenticate through Active Directory. In this first user interface display, the user name and password prompt can be displayed in a landscape orientation, for example, horizontally across a horizontal scroll graphical element 422.

[0402] Figure 4 A flow chart illustrating a method of displaying a start-up user interface screen display in one embodiment. This display screen includes lists of menu items in two different visual orientations (e.g., horizontal and vertical). Thus, for example, more general categories of menu items are displayed on a horizontal scroll 502, while sub-menu items are displayed on a vertical scroll 504. For example, a "start" option 506 selected from a log-in user is displayed on the horizontal scroll 502. A second tier of options from the "start" option (406) is displayed on the vertical scroll 504. In this example method, the start-up screen is the initial software screen displayed to the user. The workflow available to the user is listed as options (sub-options) on the vertical scroll that the user can select. In this example method, less common and advanced workflows can be grouped under an advanced menu. In this example method, the options for workflows for the system include: create a new run 508, when the user selects the create new run workflow 510, the user can create a run from scratch or based on a previously defined run 512; continue a previously scheduled or started run 514, when the user selects the continue a previously scheduled or started run 516, the software automatically resumes 518 from the last step completed by the user in the run. Review results of completed runs 520, when the user selects review completed runs 522, the software takes the user to a review screen 524. After the user selects any option 504 from the vertical scroll, the options on the vertical scroll are added to a new horizontal scroll above the screen. The horizontal scroll allows the user to change their selection. For example, after selecting "create new file," the options for "schedule" and "complete" runs move to the horizontal scroll, allowing the user to change their mind. Figure 5

[0403] A diagram illustrating a workflow of defining an assay method screen in one embodiment. In this example, the software requires an assay method to process the sample under consideration. As the "define" option (512) is executed to perform the processing displayed in this screen. The assay method defines: the assay on the plate; the plate schedule; the number of calibrators, the number of controls, and the maximum number of samples; the dilutions of controls, calibrators, and samples; the number of replicates for controls, calibrators, and samples; the instrument specifications (incubation times, execution of blockers, and / or others). Each kit provides a default assay method, and the system software allows the user to create a custom assay method based on the default values. In one embodiment, the assay method is distributed in a global product data (GPD) file. The GPD contains, for example: product barcode; assay; placement of assay materials in the wells; kit lot identification, plate, antibodies, calibrators, controls; concentration measurements for: calibrators, controls; instrument instructions for processing the product; and suggested plate schedule. Figure 4 Figure 6

[0404] ​​Figure 5 A diagram illustrating a user interface workflow for selecting an assay method in one embodiment. This user interface workflow can be followed as the selection or execution of a defined assay method, for example, in Figure 7 The selection or execution of options in the illustrated workflow. The options under "Define Assay Method" can include an "Assay Method" selection option, a "Sample" option, and a "Confirm" option, for example, horizontally oriented on horizontal scroll widget 702. The selected "Assay Method" option can be brightly displayed and / or centered on the horizontal scroll widget on the other unselected options. Sub-layer options under the "Assay Method" option can be vertically oriented, for example, on vertical scroll widget 704. In this example, the user can select an "Assay Method" in three ways: a) selecting the most recently used assay method on the system, sorted in reverse chronological order; and b) selecting all available assay methods installed on the system. In this screen, the UI uses multiple scrolls, and the last scroll contains the desired result before each scroll can filter the results of the next scroll: c) searching the assay methods installed on the system, which can be done using a free text search.

[0405] When the user selects one of the sub-layer options, the sub-layer options move to the horizontal scroll to allow the user to change their "Assay Method" selection model. After the user initially selects an assay method, the user is allowed to select whether to execute a single assay method, where all Mesoscale Diagnostics test plates in the execution use the same assay method, or multiple assay methods, where each assay method in the execution has at least one Mesoscale Diagnostics test plate.

[0406] Figure 6 A flowchart illustrating a workflow for the user interface displayed for defining a sample in one embodiment. Based on the selection of the "Define Sample" option, which is displayed horizontally, for example, on horizontal scroll widget 802, which can stack its parent menu item under the "Define" option, the options for the "Define Sample" option are displayed vertically, for example, on vertical scroll widget 804.

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

[0408] The system can also import from a sample management system. When the user chooses to manually define a sample, the user can define the number of samples to be performed. The software will automatically assign a sample ID.

[0409] Figure 8 A flow diagram illustrating the workflow of displaying a user interface for confirming the execution of a defined sample in one embodiment is shown. Based on the selection of the "Confirm Execution Definition" option, which is a submenu item of the "Define" option, the "Confirm Execution Definition" option is displayed on a horizontal scroll graphical element, e.g., below its parent menu item, the "Define" option. After the user has defined the execution in the previous step, the system provides an execution summary for the user to review and confirm. The following information is displayed to the user: the number of samples in the execution. The user can also select the number of samples to review the sample identifier (ID), the number of Mesoscale Diagnostics plates in the execution, the plate plan, and the execution name. The system provides a default name for the execution and allows the user to change this name. Once the user confirms the execution, the system prompts the user asking if the user wants to continue with the execution or return to the "Launch Target."

[0410] Figure 9 A flow diagram illustrating the workflow of displaying a user interface for notifying the user that a job is complete in one embodiment is shown. The system can use a wizard (an automated help function) to guide the user through the job via a user interface. The main logical steps can be broken down into several targets. In this example, the system has three main targets in the wizard: Launch, where the user starts and selects the operation the user wants to perform in the system; Define, where after the user selects what the user wants to do, the wizard guides the user through the user interface to define any information needed; and Execute, where the system guides the user through performing the job the user selected.

[0411] Figure 10 A flow diagram illustrating the workflow of displaying a user interface for performing / collection options in one embodiment is shown. In this collection screen, the system builds a list of items the user needs to collect to perform the execution. Each item must be marked as collected before proceeding to the operation. The system also allows the user to print this list or use a tablet for collection. For each item to be collected, there are optional items that can be scanned so that the system can check if it is the correct item, expired, lot information. For example, the system can request an item barcode scan. This is done using the barcode that retrieves the GPD (GPI).

[0412] Figure 11A flow diagram illustrating the workflow of the user interface for the execute / prepare option in one embodiment. In this prepare screen, the system displays a list of steps needed to collect the items in the carousel. For each step in the carousel, the system displays a detailed description of the selected prepare step. The detailed prepare step can include: text describing the action to be taken; pictures to visually indicate the action; videos to demonstrate the action; and web content, such as a web page, to provide more detailed information or content about the action. The user will be prompted to indicate that all prepare steps have been completed before proceeding to the next step. The user can also use the tablet to print the prepare steps or complete the prepare steps.

[0413] Figure 12 A flow diagram illustrating the workflow of the user interface for the execute / load option in one embodiment. In this load screen, the system displays a list of items to be loaded into the instrument in the form of a carousel. For each item, the system graphically displays where the item should be loaded. The system provides a graphical indication of whether the item is already loaded or empty. The system will check whether all items have been loaded before proceeding to the next screen.

[0414] Figure 13 A flow diagram illustrating the workflow of the user interface for the execute / execute option in one embodiment. The run screen allows the user to indicate to the system to start the run, for example, via the run button UI control. This screen also allows the user to register other users to have the system update messages. The updates can be communicated through, for example, email, for example, short message service (SMS), social networking applications, and / or blogs (Blog), and / or others. Once the user starts the execution, the system transitions to display a timer of the estimated time to completion. In one embodiment, the timer has 3 modes: 1) an analog watch format of the estimated time; 2) a digital watch format of the estimated time; 3) a live camera feed of the instrument. The user can also request to stop the execution through the advanced flash menu.

[0415] Figure 14 A flow diagram illustrating the workflow of the user interface for the execute / unload option in one embodiment. Upon completion of the execution, the system switches to this unload screen. In the "unload" screen, a list of steps to unload the system of the items is displayed. For each item, the system graphically displays where the item should be unloaded. The system provides a graphical indication of whether the item is loaded or unloaded. The user needs to unload all items before proceeding to the next screen.

[0416] Figure 15A flow chart illustrating the workflow of the user interface shown in one embodiment for the execute / view options. On the view screen, the system displays the results of the execution. The results are also automatically exported in the following formats: file format; transmitted to the LIMS / LIS system; and emailed. The results will be displayed and can be viewed: a) in a graphical presentation panel. The ECL or calculated concentrations are displayed using a brightness scale, where darker / black colors represent lower results and brighter colors represent higher results. A scale bar provides a representation of color brightness to numbers; b) as a table. The table can be exported via file format; transmitted to the LIMS / LIS system; and / or emailed. For example, if the temperature during execution is not within the specified range, the system will record any abnormal operations or results in the table. After the user has reviewed the execution data, the user can move to the "Launch" target to begin another execution or to view the results.

[0417] Figure 16 A flow chart illustrating the workflow of the user interface shown in one embodiment for the execute / view options. In one embodiment, the system categorizes the work that the user can perform into primary workflows and advanced workflows. The primary workflows are the workflows that the user will perform routinely and are optimized to simplify execution. The primary workflows are displayed in the "Target" and steps. The advanced workflows are displayed in the advanced quick view menu and represent workflows that are typically not performed or are not limited to the configuration manager. The user opens the advanced quick view menu by clicking on the [Mesoscale Diagnostics Globe]. The advanced quick view menu items are contained in a vertical scroll wheel with three main groups: functions related to the current screen (context related items that change with the active screen); modules that can be switched to; and functions that apply to all modules, such as logging in and out of the software. In this screen, the selected option, the advanced menu is shown horizontally on the horizontal graphical wheel, and the sub-options of the advanced menu are shown vertically on the vertical graphical wheel.

[0418] In one embodiment, the graphical user interface in one embodiment maximizes the black space by making the background black, thereby minimizing the pixel coloring in the user interface display (e.g., display screen), saving storage and improving display speed. Figure 17 An example screen shot of a screen of a display graphical wheel / slider axis that maximizes the screen black space in one embodiment.

[0419] As previously described, the user interface in the present application, whether used in an assay system or another system, is capable of presenting a complete trace on a single screen of the user interface display, e.g., on a graphical wheel, and allows the user to select any item at any level to return from the current path of the selected item, e.g., without having to enter or type a series of back buttons on a keyboard or other input device. The user interface allows past decisions to be visible, e.g., major decisions and the last few decisions (reviewing the history of decisions via scrolling through a graphical wheel or another graphical element such as a graphical slide axis).

[0420] In one embodiment, the graphical user interface reduces the number of menu selections a user needs to make to navigate the assay system. For example, the order of menu selection display can reduce the number of user options.

[0421] In one embodiment, computer processing time can be improved by reducing the options or selections displayed to the user and receiving input from these selections. The user interface will guide the user through the next steps of the application while providing the minimum number of selections the user needs to make.

[0422] In other embodiments, certain features described herein can be used to divide one or more problems into different segments for multiple users to solve collectively (e.g., sequentially or in parallel). In this regard, the processor can be adapted to receive one or more benchmark inputs (e.g., inputs providing information that supports or solves a larger problem, experiment, assay, etc.). The benchmark inputs can be aggregated, can collectively rely on to collectively solve a problem, conduct an experiment, etc. Such inputs can be based on one or more of: (a) modules; (b) problems or sub-problems to be solved; (c) devices; (d) physical locations; (e) tools; (f) instruments; or (g) equipment. Further, the processor can be adapted to notify one or more users, accounts, or teams of results taken from one or more of the received benchmark inputs. In one example (e.g., performing an assay), this can include notifying a first user, who is responsible for conducting an experiment, that a design of an assay experiment is complete (thereby notifying the researcher that the experiment is ready to be performed), and returning another notification to the first user that the researcher completed conducting the experiment upon completion of the experiment (e.g., so that the first user can review the results of the experiment). Further, the processor can be adapted to provide output as responses are received, such that the output can be adapted to be sent to a device that is communicably connected to the processor (i.e., interfaces with components, devices, etc. of the physical world) to direct the device to perform certain actions (e.g., physical movements or undergo physical transformations). In certain embodiments, the processor causes responses to be made to these components in the physical world as a step in the broader process of dividing one or more problems into different segments to be solved by multiple users as described above. Additionally, the processor can control certain aspects of these (and other processes described herein) through permissions commands. Permissions commands can be used to manage one or more access, security, or control levels of users and teams. These permissions can be based on different tiers, including one or more of roles, users, teams, accounts, instruments, equipment, or devices. In this regard, a complex set of permissions can be created to establish multiple levels of security for multiple applications, such that access, control, and security are strictly maintained and controlled in a highly versatile manner.

[0423] The following discussion provides additional embodiments and implementations of the system presented in this specification. The user interface system discussed above can be widely applied to a variety of applications, including manufacturing environments, testing environments, instrument environments, experimental environments, etc. In a series of embodiments, the user interface system discussed above can be used to provide a user interface for a comprehensive biological instrument system, including software, hardware, testing equipment, and all other desired features. The following discussion addresses such a comprehensive biological instrument system. In particular, the following discussion describes embodiments of the system as a cloud-based platform. The following embodiments are discussed, for example, with respect to Figure 20 The embodiments discussed can also be implemented via alternative network hardware and software platforms.

[0424] The description of the specification is for convenience only and is not intended to limit the scope of the embodiments of the present application. The following description applies to various analytical applications, including but not limited to biological analytical applications, chemical analytical applications, radiological analytical applications, and the like.

[0425] The illustrated components can include, for example, computer-implemented components implemented and / or executed on one or more hardware processors, or coupled to one or more hardware processors. For example, the one or more hardware processors can include components configured to perform various operations described in the present application, such as programmable logic devices, microcontrollers, memory devices, and / or other hardware components. As disclosed in Figures 21-50 the processor and cloud-based processing system can be examples of the processor (1110). The coupled memory devices can be configured to selectively store instructions executable by the one or more hardware processors. As disclosed in Figures 21-50 the memory devices and cloud-based storage system can be examples of the storage devices (1120). Examples of the processor can include, but are not limited to, central processing units (CPUs), graphics processing units (GPUs), field-programmable logic arrays (FPGAs), application-specific integrated circuits (ASICs), cloud-based processing units, another suitable processing component or device, or one or more combinations thereof.

[0426] Figures 21-50 To provide seamless integration of other systems, computers, and instruments, for example, a cloud-based system that supports and optimizes users to perform analytical operations, such as biological analytical operations. The system 21100 boundary surrounds or partially constitutes other systems, computers, and instruments of the analytical computing system 21100, where the operating system on each computer and / or instrument includes, in whole or in part, the analytical computing system 21100, which can include, for example, Windows TM , UNIX, Linux, Mac OS TM , iOS TM , Android TMand / or any other commercial, open-source, and / or special-purpose operating system. The analysis user environment 21101 includes one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which can be used in the system 21100. One or more analysis user environments 21101 can use the analysis system 21100. The support provider environment 21102 includes one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which can be used in the system 21100 to support instruments, consumables, and / or software used by the analysis user in the analysis user environment 21101. There can be one or more support provider environments 21102 that use the analysis computing system 21100. The consumable provider environment 21103 includes one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which can be used in the analysis computing system 21100 to provide consumables to the user in the analysis user environment 21101, or in conjunction with instruments including the instrument environment 21106. There can be one or more consumable provider environments 21103 that use the analysis computing system 21100.

[0427] An instrument provider environment 21105 for an instrument provider of the analysis instruments can be used in an instrument environment 21106, which includes one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which can be used in the analysis computing system 21100 to provide the analysis instruments used by the users in the analysis user environment 21101, for example, for sale or transfer. There can be one or more instrument provider environments 21105 that use the analysis computing system 21100. An analysis computing system provider environment 21104 for a provider of the analysis computing system 21100, which includes one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which can be used in the system 211000 to manage the business of interacting with the analysis computing system 21100 used by the analysis users in the analysis user environment 21101. Each of the "providers" with respect to the environments 21102, 21103, 21104, and 21105 can include one or more entities, including but not limited to a plurality of independent businesses, a single independent business, a combination of different independent businesses, or one or more businesses within any of the "providers" of this specification. The instrument environment 21106 includes one or more instruments, each having at least one computer, which in an embodiment, can be at least partially supplied by the analysis computing system 21100 for use by the users in the analysis user environment 21101 for sample testing. A cloud platform 21107 is a leveraged connection (e.g., a bi-directional connection) through computers, networks, and software, with one embodiment of some or all of the computers in the analysis computing system 21100 having a common computing, software services, and data architecture, such that data can be collected and shared by any computer having the relevant software of the analysis computing system 21100, no matter where, always in a secure manner, the particular computer having the relevant software of the analysis computing system 21100 is located around the world, with in a preferred embodiment, the cloud platform 21107 being hosted by a public cloud provider that provides a shared computing environment, such as Amazon™ Web Services, Google™ Cloud, Microsoft™ Azure, or others. In other embodiments, the analysis computing system provider environment (21104) can host the cloud platform 21107; or the cloud platform can be self-hosted by the analysis user environment that is a user of the analysis computing system 21100; or, the cloud platform can be hosted by a private cloud provider that provides a proprietary computing environment, such as Oracle™ Cloud, IBM™ Cloud, Rackspace, or others; or, the cloud platform can be hosted in some combination of a public cloud, a private cloud, self-hosted, and by the analysis computing system provider environment 21104.All communications with the cloud platform 21107 can be done through a preferred embodiment of a secure communication protocol, such as but not limited to https, to encrypt all communications between the sender and the recipient; however, insecure communication protocols, such as but not limited to hypertext transfer protocol secure (HTTPS), can also be selectively used in secure or insecure situation connection technologies, such as Ethernet for local area network (LAN), metropolitan area network (MAN), and / or wide area network (WAN) configurations, and / or unconnected technologies, such as WIFI, Bluetooth, and / or other similar technologies for decentralized LANs. Furthermore, the analytics computing system 21100 can be entirely deployed on a computer, such that all operations of the analytics computing system 21100 occur on the computer, with only external communications occurring between the computer and related software executing outside of the analytics computing system 21100.

[0428] Figure 21 As such Figure 22The illustrated cloud-based system embodiment provides seamless integration of other systems, computers, and instruments that support and optimize the user's analytical work. The boundaries of the analytical computing system 21100 include other systems, computers, and instruments that are defined in whole or in part by the analytical computing system 21100. The analytical user environment 21101 includes one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which can be used in the analytical computing system 21100. The administrator computer 22202 includes one or more computers having software that is used by the system administrator to manage the systems 21100 used by the users in the analytical user environment 21101 via the services and data storage / retrieval provided by the cloud platform 22223. The analytical user computer 22203 includes one or more computers having software that is used by the users in the analytical user environment 21101 to perform analytical work via the services and data storage / retrieval provided by the cloud platform 22223. The data integration computer 22204 includes one or more computers having software to integrate (e.g., bidirectionally integrate) other business systems 22224 in the analytical user environment 21101 with the analytical computing system 21100 that provides analytical user business system 22224 services via the services and data storage / retrieval provided by the cloud platform 22223. The analytical user business system 22224 can be hosted internally, externally, and / or some combination of internally and externally to the analytical user environment 21101 and can include one or more computer systems optionally having software, such as a laboratory information system (LIMS), data analysis applications, data visualization applications, data reporting applications, business productivity applications, relational and / or non-relational databases, file servers, and / or any other systems to provide data access to the analytical computing system 21100 to users that directly use the analytical computing system 21100, users that do not directly use the analytical computing system 21100, and / or one or more other computer systems having business systems 22224 that do not directly interface with the analytical computing system 21100.

[0429] The support provider environment 21102 is a support provider that supports users of the analytical computing system 21100, users of consumables from consumable providers, and / or instruments in the instrument environment 21106, including one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which can be used in the analytical computing system 21100, to support instruments, consumables, and / or software used by users in the analytical user environment 21101.

[0430] Support user computers 22206 include one or more computers having software providing users of the support provider environment 21102 oversight, management, and / or reporting of activities on the analytics computing system 21100 via services and data storage / retrieval provided by the cloud platform 22223; and support data integration computers 22207 include one or more computers having software and / or firmware for integrating other support business systems 22208 in the support provider environment 21102 with the analytics computing system 21100 providing services of the support business systems 22208 via services and data storage / retrieval provided by the cloud platform 22223. The support business systems 22208 can be hosted internally, externally, and / or by some combination of internal and external to the support provider environment 21102, and can include one or more computer systems optionally having software, such as customer relationship management, enterprise data systems, data analytics applications, data visualization applications, data reporting applications, business productivity applications, relational and / or non-relational databases, file servers, and / or any other systems to provide data access to the analytics computing system 21100 to users directly using the support user computers 22206, users not directly using the support user computers 22206, and / or one or more other computer systems having the support business systems 22208 not directly interfacing with the analytics computing system 21100.

[0431] The consumable provider environment 21103 is a consumable provider environment comprising one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which can be used in the analytics computing system 21100 to provide consumable information to users in the analytics user environment 21101, which can be used in conjunction with instruments in the instrument environment 21106 to provide consumable information to users in the analytics user environment 21101 to select instruments in the instrument environment 21106. The consumable information upload computer 22210 comprises one or more computers with software for communicating consumable information about provided consumables from the consumable provider business system 22211 to the analytics computing system 21100 via services and data storage provided by the cloud platform 22223. As used in this specification, consumable information can include, but is not limited to, global product data (GPD). The consumable provider business system 22211 can be hosted internally, externally, and / or by some combination of internally and externally by the consumable provider environment 21103, and can comprise one or more computer systems optionally with software, such as customer relationship management, enterprise data systems, data reporting applications, business productivity applications, relational and / or non-relational databases, file servers, and / or any other systems that support the business operations of a consumable provider, to support or not support the communication of consumable information to the analytics computing system 21100.

[0432] The analysis computing system provider environment 21104 is an analysis computing system provider environment for the providers of the analysis computing system 21100, including one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which can be used in the analysis computing system 21100 to provide the analysis computing system 21100 to the users in the analysis user environment 21101 and the instruments in the instrument environment 21106, as well as to the various provider environments 21102, 21103, and 21105, where the account information upload computer 22213 includes one or more computers with software for preparing and controlling the use of the analysis computing system 21100 by the users in the analysis user environment 21101 and the instruments in the instrument environment 21106 through the services and data storage provided by the cloud platform 22223. The computing system provider business system 22214 can be hosted internal, external, and / or some combination of internal and external to the analysis computing system provider environment 21104, and can include one or more computer systems optionally with software, such as customer relationship management, enterprise data systems, data reporting applications, business productivity applications, relational and / or non-relational databases, file servers, and / or any other systems that support 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 not at all.

[0433] The instrument provider environment 21105 includes one or more servers, desktop computers, laptop computers, tablet computers, and / or mobile devices, one or more of which can be used in the analysis computing system 21100 to provide the instruments to the users in the analysis user environment 21101, and which can optionally be used as the instruments in the instrument environment 21106 to process the samples under test, and which can optionally have one or more consumables provided by the consumable provider environment 21103. The instrument information upload computer 22216 includes one or more computers with software for communicating instrument information about the provided instruments from the instrument provider business system 22217 to the analysis computing system 21100 through the services and data storage provided by the cloud platform 22223. The instrument provider business system 22217 can be hosted internal, external, and / or some combination of internal and external to the instrument provider environment 21105, and can include one or more computer systems optionally with software, such as customer relationship management, enterprise data systems, data reporting applications, business productivity applications, relational and / or non-relational databases, file servers, and / or any other systems that support the business operations of the instrument provider, to support the communication of instrument information to the analysis computing system 21100, or not at all.

[0434] Instrument environment 21106 includes one or more instruments, where each instrument can be a personal operating instrument 22221, a co-operating instrument 22222, or a workflow assistance instrument 22226 provided by instrument provider environment 21105, which can be leveraged by users of analysis user environment 21101 to selectively combine consumables provided by consumable provider environment 21103 to process samples to generate data analyzed by users in analysis user environment 21101, where personal operating instrument 22221 can have a personal operating instrument computer 22219 to provide integration between personal operating instrument 22221 and analysis computing system 21100, and optionally provide operational control of personal operating instrument 22221, through services and data storage provided by cloud platform 22223, where co-operating instrument 22222 can also have a co-operating instrument computer 22220 to provide integration between co-operating instrument 22222 and analysis computing system 21100, and optionally provide operational control of co-operating instrument 22222, through services and data storage provided by cloud platform 22223, and where workflow assistance instrument 22226 can have a workflow assistance instrument computer 22225 to provide integration between workflow assistance instrument 22226 and analysis computing system 21100, and optionally provide operational control of workflow assistance instrument 22226, through services and data storage provided by cloud platform 22223. Examples of personal operating instruments 22221 include, but are not limited to, plate readers, plate washers, plate incubators, plate shakers, plate incubator shakers, pipetting systems, or any other type of instrument used to analyze sample tests. Co-operating instrument 22222 can combine some or all of the functionality provided by one or more individual operating instruments 22221 into an integrated platform that automatically performs individual operations of individual operating instruments 22221, thereby freeing users from performing various individual operations of individual operating instruments 22221. Workflow assistance instrument 22226 can provide support for users to leverage personal operating instruments 22221 and / or co-operating instrument 22222 to test sample assays in instrument environment 21106, where support includes, but is not limited to, collecting various consumables that can be stored at various temperatures in different physical locations, preparing consumables for use in processing of one or more assays, and / or using one or more personal operating instruments 22221 to guide users through entire assay steps. In addition to or instead of assay tests and plate-based tests described in this specification, consumable provider environment analysis user APP 21103 can also assist with other tests.

[0435] The instruments in the instrument environment 21106 can include zero or more personal operation instruments 22221 each with its corresponding personal operation instrument computer 22219; zero or more co-operation instruments 22222 each with its corresponding co-operation instrument computer 22220; and / or zero or more workflow assistance instruments 22224 each with its corresponding workflow assistance instrument computer 22225. The preferred embodiment of the instrument environment 21106 includes providing separate computers to integrate the zero or more personal operation instruments 22221, the zero or more co-operation instruments 22222, the zero or more workflow assistance instruments 22224, the zero or more personal operation instrument computers 22219, the zero or more co-operation instrument computers 22220, and the zero or more workflow assistance instrument computers 22225 into the analytical computing system 21100 through the services and data storage provided by the cloud platform 22223.

[0436] Figure 21 is an embodiment of the system architecture of the cloud platform 22223 as part of the analytical computing system 21100 that provides common computing, software services, and data architecture, such that the analytical computing system 21100 (and the cloud platform 22223) can be used by multiple users, each with their own personal operation instruments 22221, co-operation instruments 22222, and workflow assistance instruments 22224, and each with their own personal operation instrument computers 22219, co-operation instrument computers 22220, and workflow assistance instrument computers 22225. Figure 23) any computer anywhere in the world that is relevant to the software collects and shares data, with one or more service servers 23302 providing a flexible, robust, and high-performance computing and related software platform to support specific services of the analytics computing system 21100 to retrieve, store, transmit, and / or transform data related to the use of the analytics computing system 21100; one or more database servers 23309 (e.g., including one or more team databases 23310 and one or more system databases 23311) to provide a flexible, robust, and high-performance computing and related software platform for one or more structured databases for storing and / or retrieving data produced and / or used by users of the analytics computing system 21100 and for storing and / or retrieving data produced and / or used by the analytics computing system 21100 for its preparation for use and through its use, where the database technology can be relational in nature, such as SQL Serve, Oracle, MySQL, Postgres, Aurora, and / or other similar relational database technologies; and / or non-relational in nature, such as Dynamo DB, MongoDB, and / or other similar non-relational database technologies; and one or more bulk data servers 23315, which can include system content 23312, instrument content 23313, and consumable content 23314, to provide a flexible, robust, and high-performance computing and related software platform to store and retrieve file-based data provided using the analytics computing system 21100 and / or produced through the use of the analytics computing system 21100. In an embodiment, the service servers 23302 have integrated services with logic, namely: a management with logic integration service 23303 to support the management of the use of the analytics computing system 21100; a dashboard with logic integration service 23304 to support the oversight and control of the use of the analytics computing system 21100; an upload with logic integration service 23305 to support the uploading of consumable and instrument information to the analytics computing system 21100; a system with logic integration service 23306 to support various non-specific user functions related to the overall use of the analytics computing system 21100; an application with logic integration service 23307 to support the typical scientific use of the analytics computing system 21100 by analytics users; and an authentication with logic integration service 23308 to support the secure login to and logout from the analytics computing system 21100.In one implementation, the service server 23302 is a pliable computing infrastructure from one or more servers as represented by the service server 23302, where in the preferred embodiment, each server has deployed all of the logical integrated services of the services 23303, 23304, 23305, 23306, 23307, and 23308 to enable a load balancer to distribute service requests evenly across the one or more servers represented by the service server 23302 to optimize user interaction. For example, if the logical integrated services of the services 23303, 23304, 23305, 23306, 23307, and 23308 are designed using the RESTful (Representational State Transfer) design pattern, i.e., each provided service is stateless, i.e., does not store or store data, then this load balancing technique can be implemented, so that any request on a service can be satisfied by any available server, where the services deployed on the service server 23302 can be based on demand at the time of the request. To support the most preferred deployment and operation of the logical integrated services 23303, 23304, 23305, 23306, 23307, and 23308 on one or more computers, the preferred embodiment builds these services on a distributed object platform, such as the Java Platform Enterprise Edition can support a cross-platform computing architecture, the.NET Framework for a Windows-only computing architecture, or other similar distributed object platforms, or some combination of one or more of these distributed object platforms. The database server 23310 can include one or more databases, such as the team database 23310 and the system database 23311. The team database 23310 is adapted to store information, data, and / or metadata about "teams" (e.g., team names, members, permissions, etc.). The system database 23111 can include files, data, and / or other information about system functionality. In addition, the mass data server 23315 can include various content, such as "system content" 23312, e.g., data or content about system functionality, such as instrument content 23313 (e.g., instrument types, parameters, etc.); and consumables 23314, e.g., consumable types, quantities, etc.

[0437] Figure 21The manager uses the manager computer 24401 to execute the manager APP software 24402 to provide services through the cloud platform 22223 to perform the implementation of the management functions provided by the analytics computing system 21100. As described throughout this specification, the manager APP software can employ a MUI as previously described to facilitate user access to the provided functionality. Thus, embodiments of the systemized user interface control system 1102 can be provided through the combination of the manager computer 24401 and the cloud platform 22223. For example, one or more service servers 24411 can provide various functionality such as authentication, one or more other management functions, functionality to upload data such as to one or more database servers, one or more system functions, one or more application programs (e.g., APP functionality), and / or graphical visualization support via a dashboard. The manager APP 24402 can be executed on the manager computer 24401 through a unique application installed on the manager computer 24401 or accessed via an internet browser installed on the manager computer 24401 that points to a uniform resource locator (URL) provided by the cloud platform 22223 that provides a web service portion of the analytics computing system 21100, which in this embodiment is logically organized using the management 24408, but is not limited to such organization. In an embodiment, the first interaction between the manager and the cloud platform occurs through the manager APP 24402 using a login service request, for example, via the user manager 1056 of the systemized user interface control system 1102, through the service link 24403 to authenticate 24404, using appropriate credentials, for example, including a unique user name and password and / or a token identification code, and can also include selective or required additional authentication inputs, commonly referred to as two-factor authentication, previously established by the manager. In this embodiment, the login service retrieves the user's encrypted credentials from the system database 24406 through the service link 24405 to verify that the manager has access to and can manage the analytics computing system 21100 using login update data stored in the system database 24406 through the service link 24407 to track use of the analytics computing system 21100. If the manager forgets or does not know his password, the manager can also reset his password through the manager APP 24402 via the service link 24403 to verify 24404 through the password reset update data stored in the system database 24406 through the service link 24407 to track use of the analytics computing system 21100.The manager can also build its additional authentication input via the manager APP 24402 through the service link 24403 of the authentication 24404 to track the usage of the analytics computing system 21100 by using the configuration changes to update the data stored in the system database 24406 through the service link 24407, retrieving and changing the configuration of its additional authentication input through the service link 24405 of the system database 24406. After logging in the authentication manager, the manager can use the services provided by the manager 24403 through the manager APP 24402 via the service link 24407 to perform the management functions of the analytics computing system 21100, where these services also build and update these service usage of the data stored in the system database 24406 through the service link 24407 as needed to build, read, update, and / or delete the data stored in the system database 24406 (e.g., via the data storage manager 1064) to track the usage of the analytics computing system 21100. In addition, provided by the manager APP 24402, the manager performing the management functions of the analytics computing system 21100 can build one or more new group users, which use the analytics computing system 21100 through the shared team database 24414 of the service link 24413, and build a new database server 24415 through the service link 24412, the new team database 24414 can be added to optimize the performance of the database server 24415. Finally, the manager can log out from the used analytics computing system 21100 through the service link 24403 via the manager APP 24402 to terminate the current use of the analytics computing system 21100, the logout service of the authentication 24404 updates the login information of the manager through the service link 24409 of the system database 24406, and updates the data stored in the system database 24406 through the service link 24407 to track the usage of the analytics computing system 21100. The analytics computing system 21100 can include one or more service servers 24411. These servers are adapted to host various applications and / or modules, including, system modules, application modules, authentication modules, management modules, dashboard modules, and upload modules. In an embodiment, the authentication and management modules allow users to communicate with the system database 24406 and / or the team database 24414 through the manager APP 24402, for example, through one or more service links.

[0438] Figure 24is an embodiment of an analysis user using an analysis user computer 25502 to execute analysis user APP software 25503 to perform analysis functions provided by the analysis computing system 21100 through services provided by the cloud platform 22223. As discussed throughout this specification, the analysis user APP software 25503 can employ a MUI as previously described to facilitate user access to the provided functions. Thus, embodiments of the systemized user interface control system 1102 can be provided through the combination of the analysis user computer 25502 and the cloud platform 22223. The analysis user computer 25502 can be executed or accessed separately through different applications 25503 installed on the analysis user computer 25502, or via an internet browser installed on the analysis user computer 25502 that uses web page pointing URLs of the service portion of the cloud platform 22223, which in this embodiment is organized using application 25509 logic, but is not limited to such organization. In one embodiment, the first interaction of an analysis user with the cloud platform 22223 is through the service link 25504 using the analysis user APP 25503 that requires login to the service for authentication 25505 with appropriate credentials, which can include a unique user name and password and / or other information (e.g. biometric), and can also include optional or required additional authentication inputs, commonly referred to as two-factor authentication, previously constructed by the administrator for use, where the login service can retrieve the user's encrypted credentials from the system database 25507 through the service link 25506 to verify that the analysis user can access and use the analysis computing system 21100 through the service link 25506 using the login update data stored in the system database 25507 to track use of the analysis computing system 21100. If the user forgets or does not know their password, the analysis user can also reset their own password through the service link 25504 via the analysis user APP 25503 to verify 25505 through the service link 25506 using the password reset update data stored in the system database 25507 to track use of the analysis computing system 21100. The analysis user can also construct their additional authentication inputs through the service link 25504 via the analysis user APP 25503 to verify 25505 through the service link 25506 to retrieve and change their additional authentication configuration stored in the system database 25507 through configuration change update data to change their additional authentication configuration input through the service link 25506 to the system database 25507 to track use of the analysis computing system 21100.After the login authentication analyzes the user, the user can use the services provided by the application 25509 via the service link 25508 through the use of the analyze user APP 25503 to perform the analysis functions provided by the application 25509, where these services use the service link 25510 as needed to create, read, update, and / or delete data stored in the team database 25511 using these services that also use the service link 25510 to create and update data stored in the system database 25507 to track the use of the analysis computing system 21100. Finally, the analyze user can log out of the use of the analysis computing system 21100 via the service link 25504 through the analyze user APP 25503 to terminate the user's current use of the analysis computing system 21100, the logout service updates the analyze user login information through the service link 25506 of the system database 25507, the logout updates the data stored in the system database 25507 through the service link 25506 to track the use of the analysis computing system 21100.

[0439] Figure 25is an embodiment of a data integration computer 26602 executing a data integration APP software 26603 that is a service provided through a cloud platform 22223 between the analytics computing system 21100 and a computing system that is not necessarily part of the analytics computing system 21100 to perform data integration functions provided by the analytics computing system 21100. As described in this specification, the data integration APP software 26603 can employ the aforementioned MUI to facilitate user access to the provided functions. Thus, the combination of the data integration computer 26602 and the cloud platform 22223 can provide an embodiment of the systemized user interface control system 1102. The data integration APP 26603 can be provided as part of the analytics computing system 21100 and / or can be provided by an analytics user or someone working with an analytics user. In one implementation, the first interaction of the data integration APP 26603 with the cloud platform 22223 is a request for a login service through a service link 26604 to authenticate 26605 using appropriate credentials built by an administrator, which preferably include a unique user name and password, and can also include optional or required additional authentication inputs, commonly referred to as two-factor authentication, previously built for use by the administrator, where the login service can retrieve authentication data for the data integration APP 26603 from a system database 26607 through a service link 26606 to verify that the data integration APP 26603 can access and use the analytics computing system 21100 through a service link 26606 using login update data stored in the system database 26607 to track usage of the analytics computing system 21100. After the data integration APP 26603 is authenticated for login, the APP can use services provided by an application 26609 through a service link 26608 to perform analytics functions provided by the application 26609 using the data integration APP 26603, where these services use a service link 26610 to create, read, update, and / or delete data stored in a team database 26611 as needed, where the use of these services also creates and updates data stored in the system database 26607 through the service link 26610 to track usage of the analytics computing system 21100. Finally, the data integration APP can log out of the analytics computing system 21100 through a service link 26604 from the use of the analytics computing system 21100 by the data integration APP 26603 to terminate the current use of the analytics computing system 21100, the logout service updates data integration APP login information through the service link 26606 of the system database 26607, and the logout updates data stored in the system database 26607 through the service link 26606 to track usage of the analytics computing system 21100.

[0440] Figure 26is an example of a user using a support user computer 27702 executing a supervising user APP software 27703 to supervise the use of an analytics computing system 21100 provided through services provided by a cloud platform 22223 to perform the functions provided by the analytics computing system 21100. As described in this specification, the supervising user APP software 27703 can employ a MUI as previously described to facilitate user access to the functions provided. Thus, embodiments of the systemized user interface control system 1102 can be provided through the combination of a support user computer 27702 and a cloud platform 22223. The supervising user APP 27703 can be executed on the support user computer 27702 through a different application installed on the support user computer 27702 or accessed via an Internet browser installed on the support user computer 27702, which in this embodiment ...

Claims

1. A method executed by at least one processor for aggregating information suitable for output to a graphical user interface (GUI), the method comprising: A first menu command, provided by at least one processor, displays a first menu with one or more user-selectable menu items on the menu portion of the aggregate user interface (AUI). In response to a user's selection, the at least one processor provides a second menu command to display a second menu with one or more user-selectable menu items on the menu portion of the AUI display and repositions the first menu from the first portion of the AUI display to the second portion, wherein the first menu and the second menu are adapted to be displayed simultaneously; and In response to a user's selection, the at least one processor provides a content command to display aggregated content on the content portion of the AUI display, the aggregated content being provided as a user-selectable content item, the user-selectable content item being associated with two or more user-selectable menu items from the first menu and the second menu; The aggregated content is adapted to be displayed on the content portion of the AUI display simultaneously with the display of the first menu and the second menu in the menu portion, and is user-selectable.

2. The method according to claim 1, further comprising: Collect multiple content items through a cloud computing platform; as well as The plurality of content items are provided to the at least one processor as aggregated content.

3. The method according to claim 1, further comprising: Multiple content items are collected through the vehicle's computing system; as well as The plurality of content items are provided to the at least one processor as aggregated content.

4. The method of claim 1, wherein the second menu adapted to display user-selectable menu items is limited to the top 10% of the applications most frequently used by the user.

5. The method of claim 1, wherein the second menu having one or more user-selectable menu items includes one or more user-selectable menu items that are at least one hierarchical menu level lower than the first menu.

6. The method of claim 1, wherein each of the first menu and the second menu is adapted to be displayed in a horizontal orientation, and wherein the first menu and the second menu are adapted to be displayed in a nested manner.

7. The method of claim 1, wherein the second menu having one or more user-selectable menu items includes one or more applications within a specific category.

8. The method of claim 1, further comprising: In response to a user's selection, the at least one processor provides a third menu command to display a third menu with one or more user-selectable menu items on the menu portion of the AUI display, wherein the first menu, the second menu, and the third menu are adapted to be collapsible, thereby adapting the AUI display to simultaneously display no more than two of the first menu, the second menu, and the third menu.

9. The method of claim 8, wherein the aggregated content includes only content that was not previously displayed on the AUI display.

10. The method of claim 1, wherein the first menu having one or more user-selectable menu items includes one or more categories of the application.

11. The method of claim 10, wherein the category of the application includes one or more of the following: email, social media, messaging, audio / video conferencing, and shopping.

12. The method of claim 1, wherein the content adapted to be displayed in the content portion is adjusted to be displayed in a vertical orientation, wherein the vertical orientation includes a graphic rotation wheel.

13. The method of claim 1, wherein the first menu and the content are adapted to be displayed on a background comprising pixels, wherein at least 75% of the pixels are black.

14. The method of claim 1, wherein the content adapted to be displayed in the content portion of the AUI is adapted to be displayed in one or more of a first sub-partition and a second sub-partition, wherein the first sub-partition includes the name of an individual or group, and the second sub-partition includes content associated with the name of the individual or group.

15. The method of claim 1, wherein the content portion is adapted to display one or more of current content and additional content, and wherein the current content and additional content are adapted to be highlighted and faded on the AUI display, respectively.

16. The method of claim 1, wherein the content comprises one or more of the following: a person's name, a group's name; a date; a time; a subject; a message; a photo; a video; an attachment; or a link to other content.

17. The method of claim 1, wherein the content portion further comprises an interactive content portion adapted to receive text- or graphic-based input.

18. The method of claim 1, wherein the menu portion further comprises the first menu, a scrolling area, and one or more of a second menu having one or more user-selectable menu items and a third menu having one or more user-selectable menu items, wherein two or more of the first menu, the second menu, and the third menu are adapted to be displayed as a series of concentric wheels, and wherein the scrolling area is adapted to rotate one or more of the first menu, the second menu, and the third menu.

19. The method of claim 18, wherein the menu portion is adapted to be positioned below the content portion on the AUI display.

20. The method of claim 1, wherein the order in which the one or more user-selectable menu items are displayed is determined by user preference and at least one of the user's previous interactions with the one or more user-selectable menu items.

21. The method of claim 1, wherein the aggregated content includes only content that the user has not previously viewed.

22. The method of claim 1, wherein the aggregated content is arranged in reverse chronological order or according to application type.

23. The method of claim 1, wherein repositioning the first menu includes enlarging or shrinking the size of the first menu.

24. A system for aggregating information suitable for output to a graphical user interface (GUI), the system comprising: At least one processor; Arithmetic unit; as well as 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 perform the following operations: The at least one processor provides a first menu command to display a first menu with one or more user-selectable menu items on the menu portion of the aggregate user interface (AUI). In response to a user's selection, the at least one processor provides a second menu command to display a second menu with one or more user-selectable menu items on the menu portion of the AUI display, and repositions the first menu from the first portion of the AUI display to the second portion. The first menu and the second menu are adjusted to be able to be displayed simultaneously; and In response to a user's selection, the at least one processor provides a content command to display aggregated content on the content portion of the AUI display, the aggregated content being provided as a user-selectable content item, the user-selectable content item being associated with two or more user-selectable menu items from the first menu and the second menu; The aggregated content is adapted to be displayed on the content portion of the AUI display simultaneously with the display of the first menu and the second menu in the menu portion, and is user-selectable.

25. The system of claim 24, wherein the computing device is a mobile device.

26. A non-transitory computer-readable medium having computer instructions stored thereon, the instructions, when executed by at least one processor, causing the processor to perform a method for aggregating information suitable for output to a graphical user interface (GUI), the method comprising: The at least one processor provides a first menu command to display a first menu with one or more user-selectable menu items on the menu portion of the aggregate user interface (AUI). In response to a user's selection, the at least one processor provides a second menu command to display a second menu with one or more user-selectable menu items on the menu portion of the AUI display, and repositions the first menu from the first portion of the AUI display to the second portion. The first menu and the second menu are adjusted to be able to be displayed simultaneously; and In response to a user's selection, the at least one processor provides a content command to display aggregated content on the content portion of the AUI display, the aggregated content being provided as a user-selectable content item, the user-selectable content item being associated with two or more user-selectable menu items from the first menu and the second menu; The aggregated content is adapted to be displayed on the content portion of the AUI display simultaneously with the display of the first menu and the second menu in the menu portion, and is user-selectable.

Images