Processing transactions using a structured natural language

• US 20050033583A1
• Filed: 09/05/2003
• Published: 02/10/2005
• Est. Priority Date: 07/27/2000
• Status: Abandoned Application

• Current Assignee: HealthEdge, Inc.
• Original Assignee: HealthEdge, Inc.
• Inventors: Easton, Chris, Kennedy, Andrew, Kennedy, James, Sprecher, Benjamin, Trustman, John, Bergeron, Heather Ellen, Pringle, Simone Lemos, Peled, Alon, Pai, Jayant, Jhaveri, Kunjan
• Application Number:
  US10/656,909
• Publication Number:
  US 20050033583A1
• Time in Patent Office: Days
• US Class Current: 704/277
• CPC Class Codes: G06F 40/30 Semantic analysis
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

The disclosed technology can identify indicia associated with different entity types that interact within an industry, identify one or more relationships (e.g., contractual provisions) that can affect interactions between such entity types, and identify transactions associated with one or more of the interactions. Further, the identified transactions can be organized into one or more transaction sequences. The identified indicia, the one or more identified relationships, and the one or more transaction sequences can then be associated to form a semantic network. An instance of the semantic network can be formed in response to the execution of at least some of the transaction sequence and can serve, at least in part, as the basis for processing requests associated with the entities. The requests can correspond to interactions associated with the entities and may be represented in a natural language format, exhibiting a fixed context and a fixed grammar.

Claims

1. A method, comprising:

receiving a request to change a relationship associated with a plurality of entities interacting within an industry;

parsing the change request to identify a data structure associated with the industry, the data structure including a plurality of entity types and relationship types;

based on at least some of the plurality of entity types and relationship types corresponding to the plurality of entities, identifying a sequence of transactions; and

executing the transaction sequence to process the requested relationship change.

2. The method of claim 1, wherein the request corresponds to an electronic document having a natural language format with a fixed context and a fixed grammar.

3. The method of claim 2, wherein the fixed grammar corresponds to a Backus-Naur format.

4. The method of claim 1, wherein the industry is a service-based industry and the entity types corresponding to at least two of the plurality of entities correspond to at least two of a service provider, a service implementer, a service purchaser, a service beneficiary, a service maintainer, and a service regulator.

5. The method of claim 1, wherein the industry corresponds to a health care industry and the entity types corresponding to at least two of the plurality of entities correspond at least two of a health care subscriber, a health care provider, a health care practitioner, a health care beneficiary, and a health care company.

6. The method of claim 5, wherein the request corresponds to at least one of a request for payment of services performed, a request to authorize proposed services, a request to enroll the health care provider, a request to enroll the health care subscriber, a request to enroll the health care beneficiary, and an adoption of a new contract.

7. The method of claim 1, wherein the industry is a product-based industry and the entity types corresponding to at least two of the plurality of entities correspond to at least two of a product manufacturer, a product distributor, a product reseller, a product marketer, a product seller, a product purchaser, a product maintainer, and a product regulator.

8. The method of claim 1, further comprising:

storing indicia associated with the change request in a first data structure; and

assigning a version number to the first data structure.

9. The method of claim 8, further comprising:

based, at least in part, on the version number of the first data structure, re-executing at least some of the transaction sequence to reprocess the requested relationship change.

10. The method of claim 1, wherein the request is received from an electronic data interchange system.

11. The method of claim 1, wherein the request is received from at least one of an application program interface, a user interface, and a software editing tool.

12. The method of claim 1, wherein parsing the change request comprises:

parsing a natural language representation of the request into a plurality of fields; and

mapping at least some of the fields into at least one database table.

13. The method of claim 1, wherein the requested relationship change corresponds to at least one contractual provision associated with the plurality of entities.

14. The method of claim 1, further comprising:

forming an electronic message in response to detecting an error during the execution of the transaction sequence.

15. The method of claim 1, wherein indicia associated with the plurality of entities correspond to a plurality of nodes in a semantic network and the requested relationship change corresponds to at least one link interconnecting at least some of the plurality of nodes in the semantic network.

16. The method of claim 15, further comprising:

querying the semantic network to obtain data associated with the plurality of entities and the requested relationship change; and

formatting at least some of the obtained data in a natural language format exhibiting a fixed context and a fixed grammar.

17. The method of claim 15, further comprising:

in response to the execution of at least part of the transaction sequence, forming an instance of the semantic network.