Abstract: Methods, systems and carrier media for viewing business rules are disclosed. Components of the business rules may be stored as entries in one or more database tables. A rule editor may access business rule components and assemble the components to form a graphical display of a business rule. The graphical display may allow the user to view, edit and/or create business rules. In some embodiments, one or more human language translations of one or more business rule components may be provided. A human language translation may be substituted for a business rule component in the graphical display.

Abstract: Methods, systems and carrier media for viewing business rules are disclosed. Components of the business rules may be stored as entries in one or more database tables. A rule editor may access business rule components and assemble the components to form a graphical display of a business rule. In various embodiments, the graphical display may allow the user to view, edit and/or create business rules.

Abstract: Components of the business rules may be stored as entries in one or more database tables. A rule editor may access business rule components and assemble the components to form a graphical display of a business rule. The graphical display may allow the user to view, edit and/or create business rules. The system may track changes made to a business rule and may store a log file of changes made. The system may delay implementing the modifications until the modifications are approved by a user having appropriate authority.

Abstract: An improved method and system to process insurance claims using a graphical user interface with structured data collection. The insurance claims processing software provides the user with an estimated value for a user specified insurance claim. An insurance claims processing software user uses a table of contents (TOC) display screen to display the steps associated with the processing of the insurance claim. The user selects any intermediary step from a structured list of steps, included in the table of contents, to view a display screen associated with the selected intermediary step and to provide user inputs. The structured list of steps, included in the table of contents, is dynamically and automatically updated in response to business rules and/or user inputs. As a final step, the insurance claims processing software displays the estimated value for the specified insurance claim.

Abstract: An improved method and system for providing context-sensitive help and interactive search capability in an insurance claims processing system is described. Context-sensitive help for a step in processing an insurance claim may be automatically invoked when entering the step. Alternatively, the user may interactively invoke context-sensitive help once the step is displayed. The insurance claims processing system may display information from a located help table in order of relevance. A search interface may also be provided by the insurance claims processing system.

Abstract: An improved method and system for providing context-sensitive help and interactive search capability in an insurance claims processing system. A help information database may include one or more index tables, one or more header tables and one or more text tables. In one embodiment, the context-sensitive help for a step in processing an insurance claim may be automatically invoked when entering the step. Alternatively, the user may interactively invoke context-sensitive help once the step is displayed. The insurance claims processing system may search one or more index tables for entries including a page ID and/or codes from one or more elements of the page. The insurance claims processing system may locate one or more entries in the one or more index tables and then locate entries in the one or more help tables using information from the entries located in the one or more index tables.

Abstract: An improved method and system for providing context-sensitive help and interactive search capability in an insurance claims processing system. A help information database may include one or more index tables, one or more header tables and one or more text tables. The insurance claims processing system may display information from located help table entries in order of relevance. In one embodiment, entries in the index table may include a relevance value for the occurrence of the term in the help database. In one embodiment, the relevance values for the entries in the index table may be calculated and stored in the index table prior to a user accessing the help database. In another embodiment, the relevance value for an entry in the index table may be calculated dynamically when the entry is identified as an occurrence of a search term or of a step or step element code in context-sensitive help.

Abstract: Methods, systems and carrier media for viewing business rules are disclosed. Components of the business rules may be stored as entries in one or more database tables. A rule editor may access business rule components and assemble the components to form a graphical display of a business rule. The graphical display may allow the user to view, edit and/or create business rules. The system may track changes made to a business rule. For example, the system may store a log file of changes made. The system may delay implementing the modifications until the modifications are approved by a user having appropriate authority.

Abstract: Methods, systems and carrier media for viewing business rules are disclosed. Components of the business rules may be stored as entries in one or more database tables. A rule editor may access business rule components and assemble the components to form a graphical display of a business rule. The graphical display may allow the user to view, edit and/or create business rules. A number of business rules may utilize one or more of the same business rule components in such a system. A graphical display of a business rule may identify other business rules or business rule components that use a selected business rule component.

Abstract: Methods, systems and carrier media for viewing business rules are disclosed. Components of the business rules may be stored as entries in one or more database tables. A rule editor may access business rule components and assemble the components to form a graphical display of a business rule. In various embodiments, the graphical display may allow the user to view, edit and/or create business rules.

Abstract: Methods, systems and carrier media for modifying business rules are disclosed. Components of the business rules may be stored as entries in one or more database tables. A rule editor may access business rule components and assemble the components to form a graphical display of a business rule. The graphical display may allow the user to view, edit and/or create business rules. Modifications to business rules may be stored in one or more database tables.

Abstract: Methods, systems and carrier media for forming business rules are disclosed. Components of business rules may be stored as entries in one or more database tables. A rule editor may access business rule components and assemble the components to form a graphical display of a business rule. The graphical display may allow the user to create new business rules. A new business rule formed in the graphical display may be stored in one or more database tables as one or more business rule components.

Abstract: Methods, systems and carrier media for viewing business rules are disclosed. Components of the business rules may be stored as entries in one or more database tables. A rule editor may access business rule components and assemble the components to form a graphical display of a business rule. The graphical display may allow the user to view, edit and/or create business rules. In some embodiments, one or more human language translations of one or more business rule components may be provided. A human language translation may be substituted for a business rule component in the graphical display.