Network-based healthcare information systems

• US 7,298,836 B2
• Filed: 09/24/2002
• Issued: 11/20/2007
• 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 BLS Intelectual Property Inc (AT&T, Inc.)
• Inventors: Turcan, Diane Brown, Wellons, David L.
• Primary Examiner(s): Deane, Jr., William J.
• Application Number:
  US10/253,500
• Publication Number:
  US 20040059598A1
• Time in Patent Office: 1,883 Days
• Field of Search: 379/219, 37926501-26514, 379/220.01, 379/221.01, 705/2, 705/3, 705/1
• US Class Current: 379/219
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G16H 80/00 ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
• CPC Class Codes: H04L 51/42 Mailbox-related aspects, e.g. synchronisation of mailboxes
• CPC Class Codes: H04M 15/68 Payment of value-added services
• CPC Class Codes: H04M 2215/0196 Payment of value-added services, mainly when their charges are added on the telephone bill, e.g. payment of non-telecom services, e-commerce, on-line banking
• CPC Class Codes: H04M 2215/2026 Wireless network, e.g. GSM, PCS, TACS
• CPC Class Codes: H04M 2215/32 Involving wireless systems
• CPC Class Codes: H04W 4/24 Accounting or billing

Abstract

Methods and systems are disclosed for enabling a telecommunications network-based healthcare information system (NBHIS). A data connection is established with a rule-based application dataserver of a telecommunications network facility to control access, sharing, notification, security, and/or management of electronic healthcare data exchanged between or among different legacy systems of NBHIS participants. Typically, the rule-based application dataserver is associated with a central office (“CO”), a mobile telephone switching center (“MTSO”), or a combination CO/MTSO.

Claims

1. A method, comprising:

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

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

when both the sender'"'"'s address and the recipient'"'"'s address are matched to the list of health care participant addresses, then sending the electronic healthcare message to a rule-based engine, interpreting the object according to the rule-based engine to categorize the object as (1) data associated with an access agent, (2) data associated with a security agent, (3) data associated with a messaging agent, (4) data associated with a transactional agent, and (5) data associated with a troubleshooting agent, and converting the attached object from a format compatible with the sender'"'"'s legacy system into another format compatible with the receiver'"'"'s legacy system; 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 and categorizing the electronic healthcare message, the identifier associating the electronic healthcare message with another legacy system and a non-participant legacy system,

the sender legacy system and the receiver legacy system associated with an integrated delivery system that enables an exchange of healthcare data between healthcare participants.

2. The method of claim 1, further comprising:

selecting a transaction reply for delivery to a sender communication device associated with the sender legacy system when the categorization step applies a sender reply rule; and

routing the transaction reply to the sender communications device.

3. The method of claim 1, further comprising:

selecting a transaction notification for delivery to a receiver communication device associated with the receiver legacy system when the categorization step applies a receiver notification rule; and

routing the transaction notification to the receiver communications device.

4. The method of claim 1, wherein the step of interpreting the object further comprises:

accessing at least one rule-based application dataserver associated with a central office of a telecommunications network, the rule-based application dataserver providing the rule-based engine; and

utilizing the rule-based application dataserver to categorize the object.

5. The method of claim 4, wherein the rule-based application dataserver comprises an application server having at least one of an access agent, a security agent, a messaging agent, a transactional agent, and a troubleshooting agent.

6. The method of claim 5, wherein interpreting the object further comprises:

verifying the object meets authenticity requirements associated with at least one of the receiver legacy system and the sender legacy system; and

verifying the object meets security requirements associated with at least one of the receiver legacy system and the sender legacy system.

7. The method of claim 1, further comprising:

managing the rule-based application dataserver to control access to at least one of the receiver legacy system and the sender legacy system.

8. The method of claim 1, wherein processing the object into the receiver legacy system comprises:

converting the object from a first data format associated with the sender legacy system to a compatible object having a second data format associated with the receiver legacy system.

9. The method of claim 8, wherein the first data format is one of a printed text format, a voice data format, a video data format, a dual tone multi-frequency data format, and a digital data format.

10. The method of claim 9, wherein the second data format is a second digital data format.

11. The method of claim 10, wherein the first and second digital data formats are ASCII.

12. The method of claim 8, wherein processing the object into the receiver legacy system further comprises at least one of (i) storing the compatible object to a storage device, (ii) archiving the compatible object, (iii) encrypting the compatible object, (iv) copying the compatible object, and (v) associating the compatible object with related data in the receiver legacy system.

13. The method of claim 1, wherein communicating the compatible object comprises communicating the compatible object via means for optically transmitting data.

14. The method of claim 1, wherein communicating the compatible object comprises communicating the compatible object via means for wirelessly transmitting data.

15. The method of claim 1, wherein interpreting the object comprises accessing a rule-based application dataserver that stores rules for converting the attached object from the sender legacy system to the receiver legacy system.

16. A system, comprising:

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

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

when both the sender'"'"'s address and the recipient'"'"'s address are matched to the list of health care participant addresses, then means for sending the electronic healthcare message to a rule-based engine, interpreting the object according to the rule-based engine to categorize the object as (1) data associated with an access agent. (2) data associated with a security agent. (3) data associated with a messaging agent, (4) data associated with a transactional agent, and (5) data associated with a troubleshooting agent, and means for converting the attached object from a format compatible with the sender'"'"'s legacy system into another format compatible with the receiver'"'"'s legacy system; and

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

the sender legacy system and the receiver legacy system associated with an integrated delivery system that enables an exchange of healthcare data between healthcare participants.

17. The system of claim 16, further comprising means for selecting a transaction reply for delivery to a sender communication device associated with the sender legacy system when the categorization step applies a sender reply rule, and means for routing the transaction reply to the sender communications device.

18. A method, comprising:

detecting and decoding an incoming electronic healthcare data communication to identify a participating sender'"'"'s communications address and a participating receiver'"'"'s communications address, the electronic healthcare communication associated with an object;

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

when both the sender'"'"'s address and the recipient'"'"'s address are matched to the list of health care participant addresses, then sending the electronic healthcare message to a rule-based application dataserver;

establishing a data connection between the participating sender'"'"'s legacy system and the participating receiver'"'"'s legacy system, the data connection using the rule-based application dataserver to control access between the sender legacy system and the receiver legacy system;

interpreting the object according to a set of rules that categorize the object as (1) data associated with an access agent, (2) data associated with a security agent, (3) data associated with a messaging agent, (4) data associated with a transactional agent, and (5) data associated with a troubleshooting agent; and

converting the object according to the category selected by the rule-based application dataserver, the object converted from a format that is compatible with the sender legacy system into another format that is compatible with the receiver legacy system;

communicating the electronic healthcare data communication and the converted object via the data connection to exchange healthcare data between healthcare participants; 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 and categorizing the electronic healthcare message, the identifier associating the electronic healthcare message with another legacy system and a non-participant legacy system.

19. A system operative to:

detect and decode an incoming electronic healthcare data communication to identify a participating sender'"'"'s communications address and a participating receiver'"'"'s communications address, the electronic healthcare communication associated with an object;

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

when both the sender'"'"'s address and the recipient'"'"'s address are matched to the list of health care participant addresses, then send the electronic healthcare message to a rule-based application dataserver;

establish a data connection between the participating sender'"'"'s legacy system and the participating receiver'"'"'s legacy system, the data connection using the rule-based application dataserver to control access between the sender legacy system and the receiver legacy system;

interpret the object according to a set of rules that categorize the object as (1) data associated with an access agent, (2) data associated with a security agent, (3) data associated with a messaging agent, (4) data associated with a transactional agent, and (5) data associated with a troubleshooting agent;

convert the object according to the category selected by the rule-based application dataserver, the object converted from a format that is compatible with the sender legacy system into another format that is compatible with the receiver legacy system;

communicate the electronic healthcare data communication and the converted object via the data connection to exchange healthcare data between healthcare participants; 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 and categorize the electronic healthcare message, the identifier associating the electronic healthcare message with another legacy system and a non-participant legacy system.