Healthcare information system with clinical information exchange

• US 10,181,011 B2
• Filed: 04/18/2016
• Issued: 01/15/2019
• Est. Priority Date: 01/18/2002
• Status: Expired due to Term

• Current Assignee: Epic Systems Corporation
• Original Assignee: Epic Systems Corporation
• Inventors: Dvorak, Carl, Seow, Khiang, Young, Charles
• Primary Examiner(s): Porter, Rachel L.
• Application Number:
  US15/131,738
• Publication Number:
  US 20160232305A1
• Time in Patent Office: 1,002 Days
• CPC Class Codes: G06F 11/30 Monitoring
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 15/00 ICT specially adapted for medical reports, e.g. generation or transmission thereof
• 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: G16H 40/63 for local operation
• CPC Class Codes: G16H 40/67 for remote operation

Abstract

In a system for distributed computing in a health care environment in which multiple different applications are in use connected on a common computer network, the improvement comprising at least one clinical exchange server on the network, the clinical exchange server including memory, the clinical exchange server programmed to perform the steps of (i) maintaining a separate patient record for each of a plurality of patients wherein each patient record includes an event registry including separate event data subsets for each event recorded by any of the different applications where each event data subset indicates the application that recorded the event and event summary data wherein the event summary data is less than all of the data recorded by the application that recorded the event, (ii) receiving a first query from the first application for patient information associated with a first patient where the first query includes information usable to identify an event in the event registry, (iii) using the information in the first query and the event data subsets in the event registry to identify an event in the event registry associated with the first query, the event identified being an identified event, (iv) identifying an application that recorded the identified event from the event data subset associated with the identified event, the application identified being an identified application, (v) generating a second query that specifies the identified event, and (vi) transmitting the second query to the identified application.

Claims

1. In a system for distributed computing in a health care environment in which multiple different applications are in use connected on a common computer network, the improvement comprising:

at least one clinical exchange server on the network and acting as an intermediary between a plurality of different applications, each of the plurality of applications running on corresponding application servers on the network, the clinical exchange server including memory for storing data corresponding to the patients, the clinical exchange server programmed to perform the steps of;

maintaining a patient record including an event registry including data corresponding to each event recorded by the different applications the event data including;

(a) the application that recorded the event;

(b) data summarizing the event recorded by the application;

(ii) receiving a query from a first applications to identify an event in the registry corresponding to a patient, the query in a predetermined structured format comprising at least one of an XML, an HTML, and an HL-7;

(iii) using the information in the query and the data in the event registry to identify an event in the event registry corresponding to the query;

(iv) identifying an application that recorded the identified event from the data subset corresponding to the identified event;

(v) generating a second query in the predetermined structured format; and

(vi) transmitting the second query to the identified application, wherein the clinical exchange server uses the predetermined structured query comprising at least one of an XML, an HTML, and an HL-7 to transfer the event data from the server corresponding to the identified application to the first application.

2. The system as recited in claim 1, wherein the applications are affiliated with a health care service.

3. The system as recited in claim 2, wherein the health care service is selected from the group consisting of an in-patient service, an out-patient service, an ancillary service, a physical therapy service, an occupational therapy service, a scheduling service, a remote access service, and a home assistance or nursing care service.

4. The system as recited in claim 1, wherein the applications comprise at least one server.

5. The system as recited in claim 1, wherein the at least one server comprise a processor, a random access memory, and a mass storage device.

6. The system as recited in claim 5, wherein the mass storage device is selected from the group consisting of a magnetic disk and a tape drive.

7. The system as recited in claim 1, wherein the system further includes a plurality of terminals, wherein a user may use the plurality of terminals to operate the applications.

8. The system as recited in claim 7, wherein the terminals comprise a computer.

9. The system as recited in claim 1, wherein the clinical exchange server also maintains an abstract about the events sent to it to facilitate exchange of information between the applications.

10. The system as recited in claim 1, wherein the clinical exchange server also stores health insurance information about each patient, wherein the health insurance information can be accessed by any of the applications.

11. The system as recited in claim 1, wherein each patient record further includes an identification cross reference table that includes a list of applications on the network and, for each application, an application unique patient identifier used by the application wherein first and second different applications use first and second different patient identifiers for a first patient, respectively, the step of receiving a first query including receiving a query that identifies the first patient via the first patient identifier, the clinical exchange server further programmed to perform the step of using the first patient identifier to identify a first patient record associated with the first patient, the step of using the information in the first query and the event data subsets in the event registry to identify an event in the event registry associated with the first query including the step of identifying an event in the event registry of the first patient record, the clinical exchange server further programmed to perform the step of using the identification cross reference table to identify the second patient identifier, and the step of generating a second query including generating a second query that specifies the identified event and the second patient identifier.

12. The system as recited in claim 11, wherein the reference table includes a master patient index identification code assigned to the patient as well as an application specific identification number assigned to the patient by each application.

13. The system as recited in claim 11, wherein the first query includes an audit reference for tracking and logging the requests and responses.

14. The system as recited in claim 11, wherein the first query comprises a format parameter for specifying a format for returning the query.

15. The system as recited in claim 1, wherein an event comprises data corresponding to a patient encounter tracked or recorded by any of the different health care applications.

16. The system as recited in claim 1, wherein an event comprises data corresponding to at least one of a laboratory report, a chart entry, an accounting entry, and an insurance entry.

17. The system as recited in claim 1, wherein the different applications comprise at least one of an accounting system, an in-patient scheduling system, a laboratory results reporting system, a home assistance system, and a managed care system.

18. The system as recited in claim 1, wherein the different applications comprise at least one of a patient tracking application, a scheduling application, and a vendor application.

19. The system as recited in claim 1, wherein the different applications are programmed to maintain a security and an access code.

20. The system as recited in claim 1, wherein the different applications maintain a patient information access policy for the application.