Methods and apparatuses for providing dynamic definition and selection of metric applications

• US 9,459,843 B1
• Filed: 03/31/2015
• Issued: 10/04/2016
• Est. Priority Date: 03/31/2015
• Status: Active Grant

• Current Assignee: Change Healthcare Holdings, LLC (UnitedHealth Group Incorporated)
• Original Assignee: Mckesson Financial Holdings Limited (McKesson Corp.)
• Inventors: Smith, Eric, Adams, Lucas
• Primary Examiner(s): Wu, Daxin
• Application Number:
  US14/674,789
• Publication Number:
  US 20160291943A1
• Time in Patent Office: 553 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/242 Query formulation
• CPC Class Codes: G06F 8/315 Object-oriented languages
• CPC Class Codes: G06F 8/77 Software metrics

Abstract

A method, apparatus and computer program product are provided for generation, selection, and execution of metric applications. An example of the method includes receiving, via record access circuitry, the set of record data from a record repository, determining, by a processor and from the set of record data, record key data and one or more record data tables for the set of record data, selecting, by metric management circuitry, one or more metric applications based on a mapping performed between record key data and a metric registration structure, wherein the metric registration structure comprises metric application metadata indicating data types required by each of a plurality of metric applications, executing, by a processor, each of the selected one or more metric applications, determining an output of each of the executed selected one or more metric applications, and storing the output in a memory.

Claims

1. A method for executing metric applications against a set of record data, comprising:

receiving, via record access circuitry, the set of record data from a record repository;

determining, by a processor and from the set of record data, record key data and one or more record data tables for the set of record data, wherein the record key data identifies names or values associated with data fields of the one or more record data tables;

selecting, by metric management circuitry, one or more metric applications based on a mapping performed between record key data and a metric registration structure, wherein the metric registration structure comprises metric application metadata indicating data types, including data fields or values, required by each of a plurality of metric applications, and wherein selecting one or more metric applications comprises identifying one or more metric applications that, pursuant to the metric application metadata associated therewith, require the data fields identified by the record key data for the set of record data;

cause execution of each of the selected one or more metric applications by the processor including compiling, linking or building the one or more metric applications in response to their selection;

determining an output of each of the executed selected one or more metric applications; and

storing the output in a memory.

2. The method of claim 1, wherein the output of each of the executed selected one or more metric applications comprises at least one result of a calculation performed by the metric application, an intermediate value determined during performance of the metric application and a list of records included within the set of record data used to obtain the result of the calculation.

3. The method of claim 1, wherein at least one of the selected one or more metric applications are generated by metric definition circuitry, and wherein the method further comprises:

receiving, by the metric definition circuitry, metric definition data;

determining at least one required data type for performing one or more calculations defined in the metric definition circuitry; and

creating an entry in the metric registration structure, the entry comprising a unique identifier associated with a metric application generated from the metric definition data and the at least one required data type.

4. The method of claim 3, wherein the metric definition data is provided in a C# programming language.

5. The method of claim 1, wherein the record repository is a cloud data storage system.

6. The method of claim 1, further comprising generating the record key data and the record data tables upon receipt of the set of record data from the record repository by the record access circuitry.

7. The method of claim 1, wherein the record data tables are formatted by the record access circuitry into a JavaScript Object Notation format.

8. An apparatus for executing metric applications against a set of record data, comprising:

record access circuitry configured to receive the set of record data from a record repository; and

metric management circuitry configured to;

determine, from the set of record data, record key data and one or more record data tables for the set of record data, wherein the record key data identifies names or values associated with data fields of the one or more record data tables;

select one or more metric applications based on a mapping performed between record key data and a metric registration structure, wherein the metric registration structure comprises metric application metadata indicating data types, including data fields or values, required by each of a plurality of metric applications, and wherein the metric management circuitry is configured to select one or more metric applications by identifying one or more metric applications that, pursuant to the metric application metadata associated therewith, require the data fields identified by the record key data for the set of record data;

cause execution of each of the selected one or more metric applications by metric processing circuitry including compiling, linking or building the one or more metric applications in response to their selection; and

the metric processing circuitry configured to;

determine an output of each of the executed selected one or more metric applications; and

store the output in a memory.

9. The apparatus of claim 8, wherein the output of each of the executed selected one or more metric applications comprises at least one result of a calculation performed by the metric application, an intermediate value determined during performance of the metric application and a list of records included within the set of record data used to obtain the result of the calculation.

10. The apparatus of claim 8, further comprising metric definition circuitry configured to:

generate the selected one or more metric applications by;

receiving metric definition data;

determining at least one required data type for performing one or more calculations defined in the metric definition circuitry; and

creating an entry in the metric registration structure, the entry comprising a unique identifier associated with a metric application generated from the metric definition data and the at least one required data type.

11. The apparatus of claim 10, wherein the metric definition data is provided in a C# programming language.

12. The apparatus of claim 8, wherein the record repository is a cloud data storage system.

13. The apparatus of claim 8, wherein the record access circuitry is further configured to generate the record key data and the record data tables upon receipt of the set of record data from the record repository.

14. The apparatus of claim 8, wherein the record data tables are formatted by the record access circuitry into a JavaScript Object Notation format.

15. A non-transitory computer readable storage medium comprising instructions that, when executed by a processor, configure the processor to:

receive the set of record data from a record repository;

determine, from the set of record data, record key data and one or more record data tables for the set of record data, wherein the record key data identifies names or values associated with data fields of the one or more record data tables;

select one or more metric applications based on a mapping performed between record key data and a metric registration structure, wherein the metric registration structure comprises metric application metadata indicating data types, including data fields or values, required by each of a plurality of metric applications, and wherein selecting one or more metric applications comprises identifying one or more metric applications that, pursuant to the metric application metadata associated therewith, require the data fields identified by the record key data for the set of record data;

cause execution of each of the selected one or more metric applications including compiling, linking or building the one or more metric applications in response to their selection;

determine an output of each of the executed selected one or more metric applications; and

store the output in a memory.

16. The computer readable storage medium of claim 15, wherein the output of each of the executed selected one or more metric applications comprises at least one result of a calculation performed by the metric application, an intermediate value determined during performance of the metric application and a list of records included within the set of record data used to obtain the result of the calculation.

17. The computer readable storage medium of claim 15, wherein at least one of the selected one or more metric applications are generated by metric definition circuitry, and wherein the instructions further configure the processor to:

receive metric definition data;

determine at least one required data type for performing one or more calculations defined in the metric definition circuitry; and

create an entry in the metric registration structure, the entry comprising a unique identifier associated with a metric application generated from the metric definition data and the at least one required data type.