METHOD, APPARATUS AND COMPUTER PROGRAM PRODUCT FOR UTILIZING DYNAMICALLY DEFINED JAVA IMPLEMENTATIONS FOR CREATION OF AN EFFICIENT TYPED STORAGE

• US 20120124080A1
• Filed: 11/16/2010
• Published: 05/17/2012
• Est. Priority Date: 11/16/2010
• Status: Abandoned Application

• Current Assignee: Mckesson Financial Holdings Limited (McKesson Corp.)
• Original Assignee: Mckesson Financial Holdings Limited (McKesson Corp.)
• Inventors: Willard, Keith, Spates, Rick, Altmann, Michael
• Application Number:
  US12/947,425
• Publication Number:
  US 20120124080A1
• Time in Patent Office: Days
• US Class Current: 707/769
• CPC Class Codes: G06F 16/2438 Embedded query languages
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems

Abstract

A method for providing a patient quality monitor may include transforming patient data from a plurality of sources associated with different healthcare entities into a standard representation using a mapping to tag each piece of patient data to a common ontology, mapping the standard representation to corresponding Java class implementations, and mapping the corresponding Java class implementations to a relational database. A corresponding computer program product and apparatus are also provided.

Claims

1. A method comprising:

transforming patient data from a plurality of sources associated with different healthcare entities into a standard representation using a mapping to tag each piece of patient data to a common ontology;

mapping the standard representation to corresponding Java class implementations; and

mapping the corresponding Java class implementations to a relational database.

2. The method of claim 1, further comprising enabling querying of the relational database using a report generation tool that is not specific to any one of a plurality of the different healthcare entities.

3. The method of claim 1, wherein mapping the standard representation to the corresponding Java class implementations comprises mapping the standard representation to corresponding Java beans.

4. The method of claim 1, wherein mapping the corresponding Java class implementations to the relational database comprises utilizing mapping object-relational libraries to map the Java class implementations to a structured query language (SQL) table.

5. The method of claim 1, wherein transforming the patient data comprises transforming generic data into a strongly typed format such that mapping the corresponding Java class implementations to the relational database enables utilization of a type specific relational database for resolving database queries.

6. The method of claim 1, further comprising enabling a same analytic program to be run at any of the different healthcare entities with respect to data in the relational database.

7. The method of claim 1, further comprising enabling bi-directional transformation between the standard representation, corresponding Java class implementations and corresponding entries in the relational database.

8. The method of claim 1, wherein mapping the standard representation to corresponding Java class implementations comprises performing the mapping at a client device at runtime.

9. The method of claim 1, further comprising publishing the standard representation to an enterprise event bus.

10. The method of claim 9, wherein mapping the corresponding Java class implementations to the relational database comprises associating bean types with database tables and associating bean properties with database columns.

11. A computer program product comprising at least one computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions comprising program code instructions for:

transforming patient data from a plurality of sources associated with different healthcare entities into a standard representation using a mapping to tag each piece of patient data to a common ontology;

mapping the standard representation to corresponding Java class implementations; and

mapping the corresponding Java class implementations to a relational database.

12. The computer program product of claim 11, further comprising program code instructions for enabling querying of the relational database using a report generation tool that is not specific to any one of a plurality of the different healthcare entities.

13. The computer program product of claim 11, wherein program code instructions for mapping the standard representation to the corresponding Java class implementations include instructions for mapping the standard representation to corresponding Java beans.

14. The computer program product of claim 11, wherein program code instructions for mapping the corresponding Java class implementations to the relational database include instructions for utilizing mapping object-relational libraries to map the Java class implementations to a structured query language (SQL) table.

15. The computer program product of claim 11, wherein program code instructions for transforming the patient data include instructions for transforming generic data into a strongly typed format such that mapping the corresponding Java class implementations to the relational database enables utilization of a type specific relational database for resolving database queries.

16. The computer program product of claim 11, further comprising program code instructions for enabling a same analytic program to be run at any of the different healthcare entities with respect to data in the relational database.

17. The computer program product of claim 11, further comprising program code instructions for enabling bi-directional transformation between the standard representation, corresponding Java class implementations and corresponding entries in the relational database.

18. The computer program product of claim 11, wherein program code instructions for mapping the standard representation to corresponding Java class implementations include instructions for performing the mapping at a client device at runtime.

19. The computer program product of claim 11, further comprising program code instructions for publishing the standard representation to an enterprise event bus.

20. The computer program product of claim 19, wherein program code instructions for mapping the corresponding Java class implementations to the relational database include instructions for associating bean types with database tables and associating bean properties with database columns.

21. An apparatus comprising processing circuitry configured to:

transform patient data from a plurality of sources associated with different healthcare entities into a standard representation using a mapping to tag each piece of patient data to a common ontology;

map the standard representation to corresponding Java class implementations; and

map the corresponding Java class implementations to a relational database.

22. The apparatus of claim 21, wherein the processing circuitry is further configured to enable querying of the relational database using a report generation tool that is not specific to any one of a plurality of the different healthcare entities.

23. The apparatus of claim 21, wherein the processing circuitry is configured to map the standard representation to the corresponding Java class implementations by mapping the standard representation to corresponding Java beans.

24. The apparatus of claim 21, wherein the processing circuitry is configured to transform the patient data by transforming generic data into a strongly typed format such that mapping the corresponding Java class implementations to the relational database enables utilization of a type specific relational database for resolving database queries.

25. The apparatus of claim 21, wherein the processing circuitry is further configured to enable bi-directional transformation between the standard representation, corresponding Java class implementations and corresponding entries in the relational database.