Methods, systems, and products for categorizing and converting attached objects

• US 7,941,494 B2
• Filed: 05/09/2008
• Issued: 05/10/2011
• Est. Priority Date: 09/24/2002
• Status: Expired due to Fees

• Current Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Wellons, David L., Turcan, Diane Brown
• Primary Examiner(s): Dinh; Khanh Q
• Application Number:
  US12/117,874
• Publication Number:
  US 20080281932A1
• Time in Patent Office: 1,096 Days
• Field of Search: 709/203, 709/206, 709/220, 709/228, 706/47
• US Class Current: 709/206
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Methods, systems, and products systems are disclosed for categorizing and converting an attached object. An electronic message is received from a sender'"'"'s address that is destined for a recipient'"'"'s address and has the attached object associated with a sender legacy system. The sender'"'"'s address and the recipient'"'"'s address are associated to a list of addresses. When both the sender'"'"'s address and the recipient'"'"'s address are matched to the list of addresses, then the electronic message is sent to a rule-based engine that interprets the attached object using a set of rules and that categorizes the attached object. The object is converted based on the category. When the sender'"'"'s address and the recipient'"'"'s address do not match the list of addresses, then an identifier is received that associates the electronic message with another system.

Claims

1. A method, comprising:

associating a sender'"'"'s legacy system and a receiver system to an integrated delivery system that enables an exchange of data;

receiving an electronic message from a sender'"'"'s address that is destined for a recipient'"'"'s address and having an attached object associated with the sender'"'"'s legacy system;

associating the sender'"'"'s address and the recipient'"'"'s address to a list of health care participant addresses;

sending the electronic message to a rule-based engine that interprets the attached object using a set of rules when both the sender'"'"'s address and the recipient'"'"'s address are matched to the list of health care participant addresses; and

when the sender'"'"'s address and the recipient'"'"'s address do not match the list of health care participant addresses, then receiving an identifier that associates the electronic message with another legacy system and with a non-participant legacy system.

2. The method according to claim 1, further comprising categorizing the attached object.

3. The method according to claim 2, further comprising converting the attached object based on the category.

4. The method according to claim 1, further comprising converting the attached object from a first legacy data format associated with the sender'"'"'s legacy system to a second legacy data format compatible with a receiver'"'"'s legacy system.

5. The method according to claim 4, further comprising automatically accepting the conversion of the attached object based on the sender'"'"'s address.

6. The method according to claim 1, wherein when the rule-based engine applies a sender reply rule, then selecting a transaction reply for delivery to the sender'"'"'s address.

7. The method according to claim 1, wherein when the rule-based engine applies a receiver notification rule, then selecting a transaction notification for delivery to the recipient'"'"'s address.

8. The method according to claim 1, further comprising associating the sender'"'"'s legacy system and the receiver'"'"'s legacy system with an integrated delivery system.

9. The method according to claim 1, further comprising accessing a profile stored in a database.

11. The system according to claim 1, further comprising code that causes the processor to categorize the attached object.

12. The system according to claim 11, further comprising code that causes the processor to convert the attached object based on the category.

13. The system according to claim 1, further comprising code that causes the processor to convert the attached object from a first legacy data format associated with the sender'"'"'s legacy system to a second legacy data format compatible with a receiver'"'"'s legacy system.

14. The system according to claim 13, further comprising code that causes the processor to automatically accepting the conversion of the attached object based on the sender'"'"'s address.

15. The system according to claim 1, further comprising code that causes the processor to select a transaction reply for delivery to the sender'"'"'s address when the rule-based engine applies a sender reply rule.

16. The system according to claim 1, further comprising code that causes the processor to select a transaction notification for delivery to the recipient'"'"'s address when the rule-based engine applies a receiver notification rule.

17. The system according to claim 1, further comprising code that causes the processor to associate the sender'"'"'s legacy system and the receiver'"'"'s legacy system with an integrated delivery system.

18. The system according to claim 1, further comprising code that causes the processor to access a profile stored in a database.

10. A system, comprising:

a processor executing code stored in memory that causes the processor to;

associate a sender'"'"'s legacy system and a receiver system to an integrated delivery system that enables an exchange of data;

receive an electronic message from a sender'"'"'s address that is destined for a recipient'"'"'s address and having an attached object associated with the sender'"'"'s legacy system;

associate the sender'"'"'s address and the recipient'"'"'s address to a list of health care participant addresses;

send the electronic message to a rule-based engine that interprets the attached object using a set of rules when both the sender'"'"'s address and the recipient'"'"'s address are matched to the list of health care participant addresses; and

when the sender'"'"'s address and the recipient'"'"'s address do not match the list of health care participant addresses, then receive an identifier that associates the electronic message with another legacy system and with a non-participant legacy system.

19. A memory device storing processor executable instructions for performing a method, the method comprising:

associating a sender'"'"'s legacy system and a receiver system to an integrated delivery system that enables an exchange of data;

receiving an electronic message from a sender'"'"'s address that is destined for a recipient'"'"'s address and having an attached object associated with the sender'"'"'s legacy system;

associating the sender'"'"'s address and the recipient'"'"'s address to a list of health care participant addresses;

sending the electronic message to a rule-based engine that interprets the attached object using a set of rules when both the sender'"'"'s address and the recipient'"'"'s address are matched to the list of health care participant addresses; and

when the sender'"'"'s address and the recipient'"'"'s address do not match the list of health care participant addresses, then receiving an identifier that associates the electronic message with another legacy system and with a non-participant legacy system.

20. The memory device according to claim 19, further comprising code for categorizing the attached object.