Methods and systems for user interface interaction
Inventors
Khalid, Umair • Ravula, Vijay Kumar • Fessler, Jenna • Penna, Varun Reddy • Sameer, Adil • Katkam, Harsha Chaitanya • Sharma, Rajat
Assignees
Interested in licensing this patent?
MTEC can help explore whether this patent might be available for licensing for your application.
Publication Number
US-11741404-B2
Publication Date
2023-08-29
Expiration Date
Abstract
A configuration architecture is described. The configuration architecture may be in communication with a task management application to efficiently generate customized programs.
Core Innovation
The disclosed subject matter is directed to a configuration architecture for specialty medicine patient support programs that interoperates with a task management application. The architecture accesses a program definition data structure associated with a program based on an indication associated with a task, and determines a current activity of a plurality of activities associated with the program. The current activity is used to select a user interface framework that defines a plurality of user interfaces, each associated with a combination of a service, a stage, and an activity.
The architecture determines, based on the combination of the service, stage, and current activity, one or more data entry fields of a plurality of data entry fields for a first user interface to be displayed via the task management application. Remaining data entry fields of the first user interface are not displayed based on the same framework and combination, such that the user interface and displayed fields are driven by program definition configuration metadata. The program definition and user interface configuration support mapping among program/service/stage/activity, including an indication encoding a program/service/stage/activity.
The architecture further includes a process automation engine and orchestration of next best actions using state-machine driven workflows, including parallel workflows. Rules for run-time validation, completion determination, eligibility, and entry/exit/process decision logic are implemented using a rules engine and decision tables, including actions decision table and process decision table. A reusable actions framework executes automated actions and advances workflows while reducing user clicks and implementation complexity.
Claims Coverage
The independent claims cover three related aspects: a method, an apparatus, and a system. Across the independent claims, the same core inventive sequence appears: indication-driven access to a program definition data structure, current-activity determination, service/stage/activity-keyed user interface framework selection, and display of only the data entry fields indicated for that combination in a task management application. The total inventive features emphasized across the independent claims are reflected below for each independent claim.
Indication-driven access to program definition data structure
Accessing, by a task management application, based on an indication associated with a task, a program definition data structure associated with a program.
Current activity determination
Determining, based on the program definition data structure, a current activity of a plurality of activities associated with the program.
User interface framework keyed to service/stage/activity combinations
Determining, based on the program definition data structure, a user interface framework associated with the current activity, wherein the user interface framework defines a plurality of user interfaces that are each associated with a combination of: at least one service of a plurality of services associated with the program, at least one stage of a plurality of stages associated with the at least one service, and at least one activity of the plurality of activities associated with the at least one service.
Service stage selection based on current activity
Determining, based on the current activity, a first stage of the plurality of stages for a first service of the plurality of services associated with the program, wherein the current activity is one of the plurality of activities associated with the first service.
User interface selection based on service/stage/current activity
Selecting a first user interface of the plurality of user interfaces based on the user interface framework and a combination of: the first service, the first stage, and the current activity.
Display-only data entry fields based on framework combination
Determining, based on the user interface framework and the combination, one or more data entry fields, of a plurality of data entry fields of the first user interface, that are to be displayed via the task management application, wherein the user interface framework indicates which data entry fields of the plurality of data entry fields are to be displayed based on the combination of the first service, the first stage, and the current activity; and in response to determining the one or more data entry fields that are to be displayed, causing the first user interface comprising the one or more data entry fields to be displayed by the task management application, wherein the remaining data entry fields, of the plurality of data entry fields of the first user interface, are not displayed via the task management application based on the user interface framework and the combination of the first service, the first stage, and the current activity.
Task management application generates an indication for a task (system)
Generating, by a task management application, an indication associated with a task.
Receive indication and drive program definition access (system)
Receiving, from the task management application, the indication associated with the task; accessing, based on the indication, a program definition data structure associated with a program; determining, based on the program definition data structure, a current activity of a plurality of activities associated with the program; determining, based on the program definition data structure, a user interface framework associated with the current activity, wherein the user interface framework defines a plurality of user interfaces that are each associated with a combination of: at least one service of a plurality of services associated with the program, at least one stage of a plurality of stages associated with the at least one service, and at least one activity of the plurality of activities associated with the at least one service; determining, based on the current activity, a first stage of the plurality of stages for a first service of the plurality of services associated with the program, wherein the current activity is one of the plurality of activities associated with the first service.
Select user interface and display only the indicated data entry fields (system)
Selecting a first user interface of the plurality of user interfaces based on the user interface framework and a combination of: the first service, the first stage, and the current activity; determining, based on the user interface framework and the combination, one or more data entry fields, of a plurality of data entry fields of the first user interface, that are to be displayed via the task management application, wherein the user interface framework indicates which data entry fields of the plurality of data entry fields are to be displayed based on the combination of the first service, the first stage, and the current activity; and in response to determining the one or more data entry fields that are to be displayed, causing the first user interface comprising the one or more data entry fields to be displayed by the task management application, wherein the remaining data entry fields, of the plurality of data entry fields of the first user interface, are not displayed via the task management application based on the user interface framework and the combination of the first service, the first stage, and the current activity.
Across independent claim coverage, the document emphasizes an indication-associated, task-management-driven workflow where program definition data structures determine a current activity, which then selects a user interface framework tied to service/stage/activity combinations. A corresponding user interface is selected and only the data entry fields indicated by the framework and combination are displayed in the task management application, while remaining fields are not displayed. Additional dependent claim refinements referenced in the provided material further specify representation/parsing of the indication as a string, example task and program contexts (patient intake and therapy reimbursement/therapy acquisition and completion), and extensions involving exit rules and action decision tables based on input data values.
Stated Advantages
Reducing user clicks and implementation complexity.
Documented Applications
Configuring and running specialty medicine patient support programs using an interoperable task management application workflow.
Patient intake workflows based on an indication associated with a task.
Therapy reimbursement workflows based on an indication associated with a task.
Interested in licensing this patent?