Virtual physician office systems and methods

• US 7,248,688 B2
• Filed: 01/27/2003
• Issued: 07/24/2007
• Est. Priority Date: 01/27/2003
• Status: Expired due to Fees

• Current Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Original Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Inventors: Wellons, David L., Turcan, Diane Brown
• Primary Examiner(s): Deane, Jr., William J.
• Application Number:
  US10/351,801
• Publication Number:
  US 20040148194A1
• Time in Patent Office: 1,639 Days
• Field of Search: 379/219, 37926501-26514, 379/220.01, 379/221.01, 705/1, 705/2, 705/3
• US Class Current: 379/265.1
• CPC Class Codes: G06F 16/24 Querying
• CPC Class Codes: G06F 16/24564 Applying rules; Deductive queries
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 50/265 Personal security, identity or safety
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 40/20 for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Methods and systems are disclosed for enabling a virtual physician office (VPO) that uses a network-based physician practice application and leverages the assets of a shared, communications network of legacy systems. 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 communications. 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 communication to a communications system, the electronic healthcare communication comprising a communications address associated with one of a physician office legacy system, another legacy system, and a non-participant legacy system;

matching the communications address to a list of registered communications addresses of the physician office legacy system;

if the communications address matches a registered communications address, then automatically categorizing the electronic healthcare communication, the category comprising (1) data associated with an access agent, (2) data associated with a security agent, (3) data associated a messaging agent, (4) data associated with a transactional agent, (5) data associated with a troubleshooting agent, and (6) data associated with an application agent;

if the communications address does not match one of the registered communications addresses, then receiving an identifier and categorizing the electronic healthcare communication, the identifier associating the healthcare communication with one of another legacy system and the non-participant legacy system; and

if the electronic healthcare communication is associated with the application agent, then accessing and using a physician management application to process the electronic healthcare communication, the physician management application running on a server of the communications system,

wherein the communications system enables an exchange of the electronic healthcare communication among the physician office legacy system and one or more communications devices associated with at least one telecommunications service provider.

2. The method of claim 1, the physician management application comprising (i) a calendar and schedule, (ii) patient information, (iii) charges and fees, (iv) receipts, (v) laboratory testing, (vi) prescriptions, (vii) reports, (viii) office facilities and maintenance, (ix) compliance and inspections, (x) patient triage and medical protocols, (xi) on-call services, (xii) insurance billing and appeals, (xiii) patient billing, and (xiv) back-up storage settings.

3. The method of claim 1, wherein categorizing the electronic healthcare communication further comprises:

accessing at least one rule-based application dataserver associated with a server of a data network, the rule-based application dataserver providing a rule-based engine to interpret the electronic healthcare communication; and

using the rule-based application dataserver to categorize the electronic healthcare communication.

4. The method of claim 1, further comprising:

using the data associated with the access agent to verify the electronic healthcare communication meets authenticity requirements of the physician office legacy system; and

using the data associated with the security agent to verify the electronic healthcare communication meets security requirements of the physician office legacy system.

5. The method of claim 1, wherein categorizing the electronic healthcare communication comprises accessing a dataserver associated with a telecommunications facility, the telecommunications facility comprising telephone switching and routing equipment, mobile telephone switching and routing equipment, intelligent edge devices, an application server, and an integrated delivery system.

6. The method of claim 1, the communications address comprising a telecommunications address, a data communications address, a mobile switching telecommunications address, and a satellite communications address.

7. The method of claim 2, wherein accessing and using the physician practice management application to process the electronic healthcare communication comprises accessing and using the physician management application for managing at least one of the following:

(i) a calendar and schedule, (ii) patient information, (iii) charges and fees, (iv) receipts, (v) laboratory testing, (vi) prescriptions, (vii) reports, (viii) office facilities and maintenance, (ix) compliance and inspections, (x) patient triage and medical protocols, (xi) on-call services, (xii) insurance appeals, (xiii) patient billing, and (xiv) back-up storage settings.

8. The method of claim 2, wherein categorizing the electronic healthcare communication further comprises:

accessing at least one rule-based application dataserver, the rule-based application dataserver providing a rule-based engine to interpret the electronic healthcare communication; and

using the rule-based application dataserver to select the category of the electronic healthcare communication.

9. The method of claim 8, wherein the rule-based application dataserver comprises the server associated with the communications system having the physician practice management application.

10. The method of claim 8, wherein the rule-based application dataserver comprises an application server comprising an access agent, a security agent, a messaging/communications agent, a transactional agent, a troubleshooting agent, and an application agent.

11. The method of claim 8, further comprising:

managing the rule-based application dataserver to control access among the physician office legacy system and the communications devices.

12. The method of claim 8, further comprising:

converting the electronic healthcare communication from a first data format to a second data format associated with the physician office legacy system; and

converting the electronic healthcare communication from the second data format to the first data format.

13. The method of claim 12, wherein the first data format comprises a printed text format, a voice data format, a video data format, a dual tone multi-frequency data format, and a digital data format.

14. The method of claim 13, wherein the second data format comprises a printed text format, a voice data format, a video data format, a dual tone multi-frequency data format, and a digital data format.

15. The method of claim 14, wherein the digital data format comprises ASCII.

16. The method of claim 12, further comprising:

(i) communicating the second data format to a storage device associated with the telecommunications service provider, (ii) archiving the second data format, (iii) encrypting the second data format, (iv) copying the second data format, and (v) associating the second data format with related data in the receiver legacy system.

17. The method of claim 16, further comprising communicating the first data format to the physician office legacy system, the physician office legacy system comprising:

a wireless communications device,

a mobile phone,

a cellular phone,

a WAP phone,

a satellite phone,

a computer,

a modem,

a pager,

a digital music device,

a digital recording device,

a personal digital assistant,

an interactive television,

a digital signal processor, and

a Global Positioning System device.

18. The method of claim 16, further comprising communicating the second data format to a communications device, the communications device comprising:

a wireless communications device,

a mobile phone,

a cellular phone,

a WAP phone,

a satellite phone

a computer,

a modem,

a pager,

a digital music device,

a digital recording device,

a personal digital assistant,

an interactive television,

a digital signal processor, and

a Global Positioning System device.

19. The method of claim 18, wherein communicating the second data format comprises communicating the second data format via at least one of the following:

an analog line;

a Digital Subscriber Line (DSL);

an Integrated Services Digital Network (ISDN) line;

an ATM Sonet;

a SmartRing service line;

a Frame Relay service line; and

a local loop of a telecommunications network.

20. The method of claim 18, wherein communicating the second data format comprises communicating the second data format via means for optically transmitting data.

21. The method of claim 18, wherein communicating the second data format comprises communicating the second data format via wireless transmission.

22. A method, comprising:

establishing a first data connection between a communications device of a physician office legacy system and a communications system;

receiving an electronic healthcare communication from the communications device over the first data connection;

accessing a physician practice management application running on a server of the communications system;

using the physician practice management application to manage the electronic healthcare communication, the physician management application comprising (i) a calendar and schedule, (ii) patient information, (iii) charges and fees, (iv) receipts, (v) laboratory testing, (vi) prescriptions, (vii) reports, (viii) office facilities and maintenance, (ix) compliance and inspections, (x) patient triage and medical protocols, (xi) on-call services, (xii) insurance billing and appeals, (xiii) patient billing, and (xiv) back-up storage settings;

establishing a second data connection between the communications system and a second legacy system, the second data connection using a rule-based application dataserver to control access to and from the second legacy system, the rule-based application dataserver comprising rules for categorizing the electronic healthcare communication, the category of the electronic healthcare communication comprising (1) data associated with an access agent, (2) data associated with a security agent, (3) data associated a messaging agent, (4) data associated with a transactional agent, (5) data associated with a troubleshooting agent, and (6) data associated with an application agent; and

communicating the electronic healthcare communication via the first data connection and the second data connection,

wherein the communications system enables an exchange of at least one of the electronic healthcare communication between one or more networks of communications devices associated with at least one telecommunications service provider.

23. A computer-readable medium on which is encoded instructions for performing:

receiving an electronic healthcare communication to a communications system, the electronic healthcare communication comprising a communications address associated with one of a physician office legacy system, another legacy system, and a non-participant legacy system;

matching the communications address to a list of registered communications addresses of the physician office legacy system;

if the communications address matches a registered communications address, then automatically categorizing the electronic healthcare communication, the category comprising (1) data associated with an access agent, (2) data associated with a security agent, (3) data associated a messaging agent, (4) data associated with a transactional agent, (5) data associated with a troubleshooting agent, and (6) data associated with an application agent;

if the communications address does not match one of the registered communications addresses, then receiving an identifier and categorizing the electronic healthcare communication, the identifier associating the healthcare communication with one of another legacy system and the non-participant legacy system; and

if the electronic healthcare communication is associated with the application agent, then accessing and using a physician management application to process the electronic healthcare communication, the physician management application running on a server of the communications system, wherein the communications system enables an exchange of the electronic healthcare communication among the physician office legacy system and one or more communications devices associated with at least one telecommunications service provider.