System and method for providing a generic health care data repository

• US 20030233252A1
• Filed: 03/05/2003
• Published: 12/18/2003
• Est. Priority Date: 03/06/2002
• Status: Abandoned Application

• Current Assignee: Siemens Medical Solutions USA Incorporated (Siemens AG)
• Original Assignee: Siemens Medical Solutions USA Incorporated (Siemens AG)
• Inventors: Cassidy, James, Haskell, Robert Emmons, Heil, John Andrew
• Application Number:
  US10/382,323
• Publication Number:
  US 20030233252A1
• Time in Patent Office: Days
• US Class Current: 705/2
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 70/00 ICT specially adapted for the handling or processing of medical references
• 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

Abstract

A system for providing a generic healthcare data repository includes an input processor for acquiring healthcare transaction message data in at least one of a plurality of different data formats. A data processor extracts message content type and patient associated identifier information from the transaction message data, processes the transaction message data for storage in a structured repository in a location specified using the patient associated identifier information. A storage processor stores the processed transaction message data in the structured repository.

Claims

1. A system for providing a generic data repository, comprising:

an input processor for acquiring transaction message data in at least one of a plurality of different data formats;

a data processor for;

parsing said transaction message data and extracting message content type and associated identifier information from said transaction message data, using said extracted message content type in extracting said associated identifier information from said transaction message data, and

processing said transaction message data for storage in a structured repository in a location specified using said associated identifier information; and

a storage processor for storing said processed transaction message data in said structured repository.

2. A system according to claim 1, wherein said data processor parses transaction message data of a plurality of different types and processes said transaction message data of different types for storage in data fields of said structured repository irrespective of transaction message content.

3. A system according to claim 1, wherein said extracted message content type identifies a location of said associated identifier information in said transaction message data.

4. The system of claim 1 wherein the transaction message data is healthcare transaction message data which includes patient identifier information as the associated identifier information.

5. A system according to claim 4, wherein said patient associated identifier information comprises at least one of, (a) a patient medical record identifier, (b) an account identifier, (c) a customer identifier, (d) a patient visit identifier, (e) a transaction message source identifier and (f) a patient identifier.

6. A system according to claim 4, further comprising:

a database associating said patient associated identifier information with at least one of, (a) a patient medical record identifier, (b) an account identifier, (c) a customer identifier, (d) a patient visit identifier, (e) a transaction message source identifier and (f) a patient identifier; and

wherein,

said data processor uses said database in specifying the structured repository storage location associated with a specific patient for storing said transaction message data.

7. A system according to claim 1, wherein said transaction message data is processed for storage by placing data items of said transaction message in data fields of said structured repository substantially unchanged.

8. A system according to claim 1, wherein said data processor further extracts at least one of, (a) transaction message source identification information and (b) customer identification information associated with said transaction message, from said transaction message data.

9. The system of claim 8, further comprising:

a database associating said transaction message source identification information and said customer identification information; and

wherein,

said data processor uses said database in specifying the structured repository storage location for storing said transaction message data.

10. A system according to claim 1, wherein said transaction message data comprises at least one of, (a) a communication to a healthcare enterprise laboratory, (b) a communication to a healthcare enterprise pharmacy, (c) a communication to a healthcare enterprise radiology department, (d) a communication to a healthcare enterprise modality department, (e) a communication to a healthcare enterprise administration operation and (f) a communication to a healthcare enterprise orders or results management operation.

11. A system according to claim 1, wherein said data processor processes said transaction message data based on said extracted content type identification information by converting said transaction message data to a data format compatible with storage of said content type in said structured repository.

12. A system for providing a healthcare data repository, comprising:

an input processor for acquiring healthcare transaction message data in at least one of a plurality of different data formats;

a data processor for,

parsing said transaction message data and extracting message content type, patient associated identifier information, and customer associated identifier information from said transaction message data, using said extracted message content type in extracting said patient associated identifier information and customer associated identifier information from said transaction message data, and

processing said transaction message data for storage in a structured repository in a location associated with the associated customer and the associated patient, said customer and patient associated location being specified using said patient associated identifier information and said customer associated identifier information; and

a storage processor for storing said processed transaction message data in said structured repository.

13. A system according to claim 12, wherein said patient associated identifier information comprises at least one of, (a) a patient medical record identifier, (b) an account identifier, (c) a customer identifier, (d) a patient visit identifier, (e) a transaction message source identifier and (f) a patient identifier.

14. A system according to claim 12, wherein said customer is at least one of, (a) a party to said transaction involving said transaction message data and (b) a source of said transaction message data.

15. A system according to claim 12, wherein said data processor specifies said storage location using a database associating a plurality of patient associated identifiers comprising at least two of, (a) a patient medical record identifier, (b) an account identifier, (c) a customer identifier, (d) a patient visit identifier, (e) a transaction message source identifier and (f) a patient identifier.

16. A system according to claim 15, wherein said data processor generates and associates a patient specific identifier to said transaction message data and said patient specific identifier is associated with individual identifiers of said plurality of patient associated identifiers.

17. A system according to claim 12, further comprising:

a database associating said patient specific identifier to at least one of, (a) a patient medical record identifier, (b) an account identifier, (c) a customer identifier, (d) a patient visit identifier, (e) a transaction message source identifier and (f) a patient identifier; and

wherein,

said data processor uses said database in specifying said structured repository location associated with said customer and said patient, for storing said transaction message data.

18. A system according to claim 12, wherein

said extracted message content type identifies a location of said patient associated identifier information in said transaction message data.

19. A system for providing a healthcare data repository, comprising:

an input processor for acquiring healthcare transaction message data in at least one of a plurality of different data formats; and

a data processor for,

parsing said transaction message data and extracting message content type and patient associated identifier information from said transaction message data, using said extracted message content type in extracting said patient associated identifier information from said transaction message data,

processing said transaction message data for storage in a structured repository location associated with a source of said transaction message data and a patient, said source and patient associated location being specified using said patient associated identifier information,

retrieving and collating transaction message data associated with a particular source in response to user command; and

processing said collated transaction message data for access by a user.

20. A system according to claim 19, wherein

said data processor retrieves and collates transaction message data according to at least one of, (a) a patient identifier, (b) a customer identifier, and (c) a message source identifier;

and

said processing step comprises processing said collated transaction message data for access by a user.

21. A system according to claim 20 wherein the data processor further retrieves and collates transaction message data according to at least one of, (a) an account identifier, (b) a patient visit identifier.

22. A system according to claim 20 wherein the patient identifier is a patient medical record identifier number.

23. A system for providing a healthcare data repository, comprising:

an input processor for acquiring healthcare transaction message data in at least one of a plurality of different data formats;

a data processor for,

extracting message content type and patient associated identifier information from said transaction message data,

processing said transaction message data for storage in a structured repository in a location specified using said patient associated identifier information; and

a storage processor for storing said processed transaction message data in said structured repository.

24. A system for providing a healthcare data repository, comprising:

means for acquiring healthcare transaction message data in at least one of a plurality of different data formats;

means for parsing said transaction message data and extracting message content type and patient associated identifier information from said transaction message data;

means for using said extracted message content type in extracting said patient associated identifier information from said transaction message data;

means for processing said transaction message data for storage in a structured repository in a location specified using said patient associated identifier information; and

means for storing said processed transaction message data in said structured repository.

25. A method for providing a healthcare data repository, comprising the steps of:

acquiring healthcare transaction message data in at least one of a plurality of different data formats;

parsing said transaction message data and extracting message content type and patient associated identifier information from said transaction message data;

using said extracted message content type in extracting said patient associated identifier information from said transaction message data;

processing said transaction message data for storage in a structured repository in a location specified using said patient associated identifier information; and

storing said processed transaction message data in said structured repository.

26. A method for providing a healthcare data repository, comprising the steps of:

acquiring healthcare transaction message data in at least one of a plurality of different data formats;

parsing said transaction message data and extracting message content type and patient associated identifier information from said transaction message data,

using said extracted message content type in extracting said patient associated identifier information from said transaction message data;

processing said transaction message data for storage in a structured repository location associated with a customer and a patient, said customer and patient associated location being specified using said patient associated identifier information; and

storing said processed transaction message data in said structured repository.

27. A method for providing a healthcare data repository, comprising the steps of:

acquiring healthcare transaction message data in at least one of a plurality of different data formats;

parsing said transaction message data and extracting message content type and patient associated identifier information from said transaction message data, using said extracted message content type in extracting said patient associated identifier information from said transaction message data,

processing said transaction message data for storage in a structured repository location associated with a source of said transaction message data and a patient, said source and patient associated location being specified using said patient associated identifier information;

retrieving and collating transaction message data associated with a particular source in response to user command; and

processing said collated transaction message data for access by a user.

28. A computer-readable medium containing instructions for activities comprising:

acquiring healthcare transaction message data in at least one of a plurality of different data formats;

parsing said transaction message data and extracting message content type and patient associated identifier information from said transaction message data, using said extracted message content type in extracting said patient associated identifier information from said transaction message data;

processing said transaction message data for storage in a structured repository in a location specified using said patient associated identifier information; and

storing said processed transaction message data in said structured repository.