DYNAMIC HEALTH RECORD PROBLEM LIST

1 . A system for generating a health record problem list, the system comprising:

an electronic processor; and

memory storing instructions that, when executed by the electronic processor, cause the system to:

obtain electronic health data;

apply natural language processing to generate extracted health data from the electronic health data;

map the extracted health data to normalized terms in one or more ontologies, thereby generating normalized health data;

determine if any relationship exists between the normalized health data, including:

identifying originating medical issue data; and

identifying subsequent relevant medical data;

when a relationship exists between the at least two medical record entries using an ontological list, generate a relationship map relating the originating medical data with the subsequent relevant medical data;

receive a request for dynamic health record problem list data from a client device; and

provide the dynamic health record problem list data to the client device, wherein the dynamic health record problem list data includes the relationship map.

2 . The system according to claim 1 , wherein the memory further stores instructions that, when executed by the electronic processor, cause the system to:

generate a relative ranking of items in the normalized health data, the relative ranking providing a treatment priority indication.

3 . The system according to claim 1 , wherein the memory further stores instructions that, when executed by the electronic processor, cause the system to:

generate a trust ranking of items in the normalized health data, the trust ranking providing a veracity indication.

4 . The system according to claim 1 , wherein the memory further stores instructions that, when executed by the electronic processor, cause the system to:

generate a recommendation based on the normalized health data.

5 . The system according to claim 4 , wherein the recommendation includes a suggested follow-up or a suggested clinical determination.

6 . The system according to claim 5 , wherein the recommendation includes a potential connection between items in the normalized health data.

7 . The system according to claim 1 , wherein obtaining electronic health data includes obtaining data from at least two unrelated medical record databases.

8 . The system according to claim 1 , wherein the memory further stores instructions that, when executed by the electronic processor, cause the system to:

de-duplicate a source of truth in the normalized health data.

9 . The system according to claim 1 , wherein the memory further stores instructions that, when executed by the electronic processor, cause the system to:

deprioritize a resolved issue in the normalized health data.

10 . The system according to claim 1 , wherein the memory further stores instructions that, when executed by the electronic processor, cause the system to:

link normalized health data to one or more source documents.

11 . Non-transitory computer-readable medium including instructions that, when executed by an electronic processor, perform a set of functions, the set of functions comprising:

obtaining electronic health data;

applying natural language processing to generate extracted health data from the electronic health data;

mapping the extracted health data to normalized terms in one or more ontologies, thereby generating normalized health data;

determining if any relationship exists between the normalized health data, including:

identifying originating medical issue data; and

identifying subsequent relevant medical data;

when a relationship exists between the at least two medical record entries using an ontological list, generating a relationship map relating the originating medical data with the subsequent relevant medical data; and

generating a practice recommendation based on the normalized health data.

12 . The non-transitory computer readable medium according to claim 11 , wherein the set of functions further comprises:

receiving a request for patient adjusted health history data from a client device; and

providing the patient adjusted health history data to the client device, wherein the patient adjusted health history data includes the relationship map.

13 . The non-transitory computer readable medium according to claim 12 , wherein the set of functions further comprises:

generating a relative ranking of items in the normalized health data, the relative ranking providing a treatment priority indication; and

generating a trust ranking of items in the normalized health data, the trust ranking providing a veracity indication.

14 . The non-transitory computer readable medium according to claim 13 , wherein the practice recommendation includes a suggested follow-up or a suggested clinical determination; and

wherein obtaining electronic health data includes obtaining data from at least two unrelated medical record databases.

15 . The non-transitory computer readable medium according to claim 13 , wherein the set of functions further comprises:

de-duplicating a source of truth in the normalized health data; and

deprioritizing a resolved issue in the normalized health data.

16 . The non-transitory computer readable medium according to claim 15 , wherein the set of functions further comprises:

linking normalized health data to one or more source documents.

17 . A method for generating an interactive patient data problem list with a server, the method comprising:

obtaining electronic health data;

applying natural language processing to generate extracted health data from the electronic health data;

mapping the extracted health data to normalized terms in one or more ontologies, thereby generating normalized health data;

determining if any relationship exists between the normalized health data, including:

identifying originating medical issue data; and

identifying subsequent relevant medical data;

when a relationship exists between the at least two medical record entries using an ontological list, generating a relationship map relating the originating medical data with the subsequent relevant medical data;

receiving a request for dynamic health record problem list data from a client device; and

providing the dynamic health record problem list data to the client device, wherein the dynamic health record problem list data includes the relationship map.

18 . The method according to claim 17 , wherein obtaining electronic health data includes obtaining data from at least two unrelated medical record databases.

19 . The method according to claim 18 , further comprising:

generating a practice recommendation based on the normalized health data, wherein the practice recommendation includes a suggested follow-up or a suggested clinical determination;

generating a relative ranking of items in the normalized health data, the relative ranking providing a treatment priority indication; and

generating a trust ranking of items in the normalized health data, the trust ranking providing a veracity indication.

20 . The method according to claim 19 , further comprising:

de-duplicating a source of truth in the normalized health data;

deprioritizing a resolved issue in the normalized health data; and

linking the normalized health data to one or more source documents.