System and method for facilitating the collection, analysis, use and management of clinical analytics results to improve healthcare

1. A process for transforming health-related data for an individual from multiple sources in preparation for health-related analytical processing thereof comprising:

extracting by a first processing system core data files from a core system, the core data files containing medical claims payment data which is separately processed by the core system to determine payment by a payer to a medical service provider for medical services provided to the individual, wherein the core data files also contain first health-related data for the individual;

loading by the first processing system the extracted core data files, including the first health-related data for the individual, into a staging database;

determining whether the individual has opted out of analytical processing of any portion of the first health-related data in the core data files;

receiving by the first processing system non-core data files from a non-core system, the non-core data files containing second health-related data for the individual;

loading by the first processing system the extracted non-core data files, including the second health-related data for the individual, into the staging database;

determining whether the individual has opted out of analytical processing of any portion of the second health-related data in the non-core data files;

matching by the first processing system staged first and second health-related data from the core and non-core data files to the same individual using one or more matching rules, wherein opted-out portions of the first and second health related data are excluded from the matching;

compressing by the first processing system the matched first and second health-related data for the individual into at least one compressed file, wherein each portion of the matched first and second health-related data in the at least one compressed file is assigned an identical universal individual identifier and the universal individual identifier is unique to the individual;

providing the at least one compressed file to an analytics engine for performing one or more predetermined analytical processes thereon and creating at least one analytics results file therefrom;

receiving by a second processing system the at least one analytics results file from the analytics engine and decompressing the at least one analytics results file using the universal individual identifier to access the analytics results for the individual; and

providing access to the analytics results for the individual to at least one user, wherein the user utilizes the analytics results in a process related to the health of the individual.

2. The process according to claim 1 , wherein the non-core system is selected from the group consisting of pharmacy data processors, laboratory data processors and health risk assessment processors.

3. The process according to claim 1 , wherein the one or more matching rules include matching a combination of at least two of the following attributes of persons from the staged first and second health-related data: last name, first name, at least part of social security number, year of birth, date of birth, zip code, gender.

4. The process according to claim 3 , wherein the one or more matching rules include matching a combination of at least three of the following attributes of persons from the staged first and second health-related data: last name, first name, at least part of social security number, year of birth, date of birth, zip code, gender.

5. The process according to claim 4 , wherein the one or more matching rules further include determining a confidence level for proposed matches, wherein staged first and second health-related data matched with a determined confidence level in a first range is assigned the universal individual identifier, staged data matched with a determined confidence level in a second range is not assigned the universal individual identifier, and staged data matched with a determined confidence level in a third range is flagged for manual review to determine whether or not to assigned the universal individual identifier.

6. The process according to claim 1 , wherein each of the first and second health-related data include independent identifiers, separate from an assigned universal individual identifier, wherein the independent identifiers identify the first and second health-related data to the core and non-core systems.

7. The process according to claim 1 , wherein extracting by the first processing system core data files from the core system, includes at least one of:

receiving the core data files in response to a pull request from the first processing system to the core system; and

receiving the non-core data files as a result of a push from the non-core system.

8. The process according to claim 1 , wherein receiving by the first processing system non-core data files from the non-core system, includes receiving the non-core data files in response to a request from the first processing system to the non-core system.

9. The process according to claim 1 , wherein the receiving by a second processing system the at least one analytics results file from the analytics engine further includes at least one of:

receiving the at least one analytics results file in response to a request from the second processing system to the analytics engine; and

receiving the at least one analytics results file as a result of a push from the analytics engine to the second processing system.

10. The process according to claim 1 , wherein the second processing system is the non-core system.

11. A process for transforming health-related data for an individual from multiple sources in preparation for health-related analytical processing thereof comprising:

extracting by a first processing system core data files from a core system, the core data files containing medical claims payment data which is separately processed by the core system to determine payment by a payer to a medical service provider for medical services provided to the individual, wherein the core data files also contain first health-related data for the individual;

loading by the first processing system the extracted core data files, including the first health-related data for the individual, into a staging database;

determining whether the individual has opted out of analytical processing of any portion of the first health-related data in the core data files and excluding opted-out portions of the first health-related data from further processing;

receiving by the first processing system non-core data files from a non-core system, the non-core data files containing second health-related data for the individual;

loading by the first processing system the extracted non-core data files, including the second health-related data for the individual, into the staging database;

determining whether the individual has opted out of analytical processing of any portion of the second health-related data in the non-core data files and excluding opted-out portions of the second health-related data from further processing;

compressing by the first processing system the first and second health-related data for the individual into at least one compressed file usable by an analytics engine, wherein each portion of the first and second health-related data in the at least one compressed file is assigned an identical universal individual identifier and the universal individual identifier is unique to the individual; and

publishing the at least one compressed file for access by the analytics engine.

12. The process according to claim 11 , wherein each of the first and second health-related data include independent identifiers, separate from an assigned universal individual identifier, wherein the independent identifiers identify the first and second health-related data to the core and non-core systems.

13. The process according to claim 11 , wherein extracting by the first processing system core data files from the core system, includes at least one of:

receiving the core data files in response to a pull request from the first processing system to the core system; and

receiving the non-core data files as a result of a push from the non-core system.

14. The process according to claim 11 , wherein receiving by the first processing system non-core data files from the non-core system, includes receiving the non-core data files in response to a request from the first processing system to the non-core system.

15. The process according to claim 11 , wherein the first and second health-related data for the individual are compressed by the first processing system into two separate files, the first health-related data being compressed in a first compressed file and the second health-related data being compressed in a second compressed file; and

further wherein the first and second compressed files are published for access by the analytics engine.

16. The process according to claim 11 , further comprising:

performing by the analytics engine an analytical processes using at least a portion of the first and second health-related data and creating at least one analytics results file therefrom; and

receiving by a second processing system the at least one analytics results file from the analytics engine and decompressing the at least one analytics results file using the universal individual identifier to access the analytics results for the individual.

17. The process according to claim 16 , wherein the receiving by a second processing system the at least one analytics results file from the analytics engine further includes at least one of:

receiving the at least one analytics results file in response to a request from the second processing system to the analytics engine; and

receiving the at least one analytics results file as a result of a push from the analytics engine to the second processing system.

18. The process according to claim 16 , wherein the second processing system is the non-core system.