Abstract: Electronic data interchange (EDI) documents are validated by creating an inventory of all rules, dynamically adjusting the inventory based upon entity specific rules derived from a plurality of companion guides, determining a profile containing pointers to select rules in the inventory for each companion guide and storing the profile for each companion guide in a storage. A runtime checker can then be used to check a received EDI document with a corresponding rule set, forward the EDI document if the EDI document matches its current rule set and return the EDI document if the EDI document does not match its current rule set. EDI rules may be enforced, for example, by determining entity-specific rules from corresponding companion guides, by expressing each rule in a neutral and machine readable format, by classifying the rules and/or by creating an inventory of rules and pointers to entity-specific rules.

Abstract: A method for augmenting business process execution using natural language processing is provided in the illustrative embodiments Information related to a state in a business process is extracted from the business process executing in a data processing system. A set of natural language (NL) questions is formed based on the information and a transition from the state defined in the business process. The set of NL questions is answered with a corresponding set of NL answers, an NL answer in the set of NL answers having an associated confidence rating. A determination is made whether a confidence rating in the set of NL answers exceeds a threshold level of confidence. In response to the confidence rating exceeding the threshold, a task is executed to perform the transition in the business process.

Abstract: A system, and computer program product for augmenting business process execution using natural language processing are provided in the illustrative embodiments Information related to a state in a business process is extracted from the business process executing in a data processing system. A set of natural language (NL) questions is formed based on the information and a transition from the state defined in the business process. The set of NL questions is answered with a corresponding set of NL answers, an NL answer in the set of NL answers having an associated confidence rating. A determination is made whether a confidence rating in the set of NL answers exceeds a threshold level of confidence. In response to the confidence rating exceeding the threshold, a task is executed to perform the transition in the business process.

Abstract: Electronic data interchange (EDI) documents are validated by creating an inventory of all rules, dynamically adjusting the inventory based upon entity specific rules derived from a plurality of companion guides, determining a profile containing pointers to select rules in the inventory for each companion guide and storing the profile for each companion guide in a storage. A runtime checker can then be used to check a received EDI document with a corresponding rule set, forward the EDI document if the EDI document matches its current rule set and return the EDI document if the EDI document does not match its current rule set. EDI rules may be enforced, for example, by determining entity-specific rules from corresponding companion guides, by expressing each rule in a neutral and machine readable format, by classifying the rules and/or by creating an inventory of rules and pointers to entity-specific rules.

Abstract: Electronic data interchange (EDI) documents are validated by creating an inventory of all rules, dynamically adjusting the inventory based upon entity specific rules derived from a plurality of companion guides, determining a profile containing pointers to select rules in the inventory for each companion guide and storing the profile for each companion guide in a storage. A runtime checker can then be used to check a received EDI document with a corresponding rule set, forward the EDI document if the EDI document matches its current rule set and return the EDI document if the EDI document does not match its current rule set. EDI rules may be enforced, for example, by determining entity-specific rules from corresponding companion guides, by expressing each rule in a neutral and machine readable format, by classifying the rules and/or by creating an inventory of rules and pointers to entity-specific rules.

Abstract: Electronic data interchange (EDI) documents are validated by creating an inventory of all rules, dynamically adjusting the inventory based upon entity specific rules derived from a plurality of companion guides, determining a profile containing pointers to select rules in the inventory for each companion guide and storing the profile for each companion guide in a storage. A runtime checker can then be used to check a received EDI document with a corresponding rule set, forward the EDI document if the EDI document matches its current rule set and return the EDI document if the EDI document does not match its current rule set. EDI rules may be enforced, for example, by determining entity-specific rules from corresponding companion guides, by expressing each rule in a neutral and machine readable format, by classifying the rules and/or by creating an inventory of rules and pointers to entity-specific rules.

Abstract: An efficient organizer of companion guide rules is created by a validation application from the common set of rules among an industry's implementation guide and the rulebooks, such as companion guides of one or more entities, such as payers. The organizer of companion guide rules creates an inventory of all rules and a profile for each companion guide and stores each profile in metadata storage. Each profile contains pointers to code in the inventory for all the rules employed by the corresponding companion guide. After an EDI document reaches the validation application, a runtime checker engine checks metadata storage for a current rule set for the payer. A rule set is created the first time a profile is accessed during the validation process and whenever the profile is updated. The runtime checker engine attempts to validate the EDI document by comparing it to the current rule set for a payer's companion guide.