Individual health record system and apparatus

• US 10,460,841 B2
• Filed: 06/19/2014
• Issued: 10/29/2019
• Est. Priority Date: 09/26/2006
• Status: Active Grant

• Current Assignee: CentrifyHealth, Inc.
• Original Assignee: CentrifyHealth, Inc.
• Inventors: Korpman, Ralph A., Post, Cindy A., Hilado, Rudy R., Clegg, W. Randal
• Primary Examiner(s): Holcomb, Mark
• Application Number:
  US14/308,873
• Publication Number:
  US 20140304006A1
• Time in Patent Office: 1,958 Days
• Field of Search: 705 2- 4, 707794, 707E17009, 707600-606
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 50/20 for computer-aided diagnosis, e.g. based on medical expert systems

Abstract

A system, apparatus, and related methods for the collection, processing, evaluation, transformation, and reporting of individual health care information from diverse information systems and sources. A individual health record (IHR) of the present invention provides a structure for individuals to participate in, and manage, their health and their medical care, while still meeting the needs of health care organizations and caregivers. An IHR object may be formed by obtaining information from diverse health care information systems and sources, and transforming and re-purposing into a coherent account of the individual'"'"'s overall health and care using a comprehensive health care ontology. As information from various sources is updated or available, the IHR is dynamically updated on a continuous or periodic basis. In one embodiment, the IHR system is contained in a self-contained package or “appliance” designed to “plug and play” in existing health care information technology systems and networks, with minimal effort and intervention.

Claims

1. A computer-implemented method for processing, storing and handling health care information, comprising the steps of:

receiving, in a self-contained, plug-and-play appliance device adapted to be incorporated into an existing network or information technology system, data or information relating to a patient'"'"'s or individual'"'"'s health from one or more information sources, said data comprising data in any form;

parsing some or all of the received data or information to identify elements of the data or information;

transforming or normalizing some or all of the received data or information, and some or all of the parsed data elements, to created transformed or normalized data elements;

assigning a confidence indicator or weight to the transformed or normalized data elements, wherein said confidence indicator is a value in a non-binary range;

mapping the transformed or normalized data elements in accordance with an ontology;

obtaining a first set of matching criteria rules that identify whether the transformed or data elements sufficiently match an existing health care object as a function of one or more person or entity criteria;

automatically determining whether to create a new health care object or modify an existing health care object based on the outcome of application of the first set of matching criteria rules;

automatically modifying an existing health care object or creating anew health care object from said transformed or normalized data elements based on the outcome of said determination step, wherein said existing or new health care object is an object-oriented software environment object subject to an object hierarchy;

automatically obtaining and applying a second set of rules specifying time-dependent criteria for scheduling healthcare events every time said new health care object is created or said existing health care object is modified; and

storing the mapped data elements in a data store in accordance with a health information model, wherein said health information model associates the patient or individual with a patient or individual record, said record comprising;

identification information for one or more third parties associated with providing healthcare for the patient or individual;

health condition and health service information for the patient or individual, including timeline information;

medication information for the patient or individual;

lifestyle information for the patient or individual;

health treatment, monitoring and encounter information for the patient or individual; and

medical findings and measure data for the patient or individual.

2. The method of claim 1, further comprising the steps of:

receiving data or information relating to a health condition, service, product, treatment or encounter for the patient or individual; and

determining healthcare decisions, diagnoses or treatment for said patient or individual based upon the data or information relating to a health condition, service, product, treatment or encounter, and the mapped data elements stored in a data store in accordance with the health information model.

3. The method of claim 1, further comprising the steps of:

receiving data or information relating to a plurality of health services performed for or provided to the patient or individual; and

determining, based upon the mapped data elements stored in a data store in accordance with the health information model, whether any one or more of said plurality of health services is related to or associated with one or more health conditions of the patient or individual.

4. The method of claim 3, further comprising the step of creating a timeline of health services or events related to or associated with the patient or individual, based upon information in the patient or individual'"'"'s health record.

5. The method of claim 2, wherein the step of mapping the transformed or normalized data elements in accordance with an ontology is performed using one or more code sets, vocabularies, or rule sets;

and

further wherein the one or more code sets, vocabularies, or rule sets are updated, modified, or extended based upon the healthcare decision, diagnosis or treatment determination.

6. The method of claim 1, wherein the transformed or normalized data elements comprise standardized healthcare diagnostic, treatment and management codes.

7. The method of claim 1, wherein the transformed or normalized data elements comprise standardized healthcare or clinical terms and classifications.

8. The method of claim 1, wherein the transformed or normalized data elements comprise standardized medical findings and measure terms and units.

9. The method of claim 1, wherein the confidence indicator or weight is based on the identity of the source of information or data.

10. The method of claim 1, wherein the confidence indicator or weight is based on history and amount of processing required, and how and when the information or data is received;

and

further wherein the confidence indicator or weight is adjusted over time.

11. The method of claim 1, wherein the confidence indicator or weight is based on the relevance of the data in relation to an ontology.

12. A non-transitory computer-readable storage medium in a self-contained, plug-and-play appliance device adapted to be incorporated into an existing network or information technology system, storing instructions that cause a microprocessor or processor to perform the following steps:

receiving, in the self-contained, plug-and-play appliance device, data or information relating to a patient'"'"'s or individual'"'"'s health from one or more information sources, said data comprising data in any form;

parsing some or all of the received data or information to identify elements of the data or information;

transforming or normalizing some or all of the received data or information, and some or all of the parsed data elements, to created transformed or normalized data elements;

assigning a confidence indicator or weight to the transformed or normalized data elements, wherein said confidence indicator is a value in a non-binary range;

mapping the transformed or normalized data elements in accordance with an ontology;

obtaining a first set of matching criteria rules that identify whether the transformed or data elements sufficiently match an existing health care object as a function of one or more person or entity criteria;

automatically determining whether to create a new health care object or modify an existing health care object based on the outcome of application of the first set of matching criteria rules;

automatically modifying an existing health care object or creating a new health care object from said transformed or normalized data elements based on the outcome of said determination step, wherein said existing or new health care object is an object-oriented software environment object subject to an object hierarchy;

automatically obtaining and applying a second set of rules specifying time-dependent criteria for scheduling healthcare events every time said new health care object is created or said existing health care object is modified; and

storing the mapped data elements in a data store in accordance with a health information model, wherein said health information model associates the patient or individual with a patient or individual record, said record comprising;

identification information for one or more third parties associated with providing healthcare for the patient or individual;

health condition and health service information for the patient or individual, including timeline information;

medication information for the patient or individual;

lifestyle information for the patient or individual;

health treatment, monitoring and encounter information for the patient or individual; and

medical findings and measure data for the patient or individual.

13. The medium of claim 12, further wherein the microprocessor or processor is caused by the instructions to perform the following steps:

receiving data or information relating to a health condition, service, product, treatment or encounter for the patient or individual; and

determining healthcare decisions, diagnoses or treatment for said patient or individual based upon the data or information relating to a health condition, service, product, treatment or encounter, and the mapped data elements stored in a data store in accordance with the health information model.

14. The medium of claim 12, further wherein the microprocessor or processor is caused by the instructions to perform the following steps:

receiving data or information relating to a plurality of health services performed for or provided to the patient or individual; and

determining, based upon the mapped data elements stored in a data store in accordance with the health information model, whether any one or more of said plurality of health services is related to or associated with one or more health conditions of the patient or individual.

15. The medium of claim 14, further wherein the microprocessor or processor is caused by the instructions to perform the step of creating a timeline of health services or events related to or associated with the patient or individual, based upon information in the patient or individual'"'"'s health record.

16. The medium of claim 13, wherein the step of mapping the transformed or normalized data elements in accordance with an ontology is performed using one or more code sets, vocabularies, or rule sets;

and

further wherein the one or more code sets, vocabularies, or rule sets are updated, modified, or extended based upon the healthcare decision, diagnosis or treatment determination.

17. The medium of claim 12, wherein the transformed or normalized data elements comprise one or more of the following:

standardized healthcare diagnostic, treatment and management codes;

standardized healthcare or clinical terms and classifications;

or

standardized medical findings and measure terms and units.

18. The medium of claim 12, wherein the confidence indicator or weight is based on one or more of the following:

the identity of the source of information or data;

the history and amount of processing required, and how and when the information or data is received, wherein the confidence indicator or weight is adjusted over time;

or

the relevance of the data in relation to an ontology.

19. A system for processing, storing and handling health care information, comprising:

a self-contained, plug-and-play appliance device adapted to be incorporated into an existing network or information technology system, said appliance device comprising one or more microprocessors or processors operatively coupled to a memory, said memory operable to store at least one program, said program, when executed by said one or more microprocessors or processors, causing the one or more microprocessors or processors to;

receive data or information relating to a patient'"'"'s or individual'"'"'s health from one or more information sources, said data comprising data in any form;

parse some or all of the received data or information to identify elements of the data or information;

transform or normalize some or all of the received data or information, and some or all of the parsed data elements, to created transformed or normalized data elements;

assign a confidence indicator or weight to the transformed or normalized data elements, wherein said confidence indicator is a value in a non-binary range;

map the transformed or normalized data elements in accordance with an ontology;

obtain a first set of matching criteria rules that identify whether the transformed or data elements sufficiently match an existing health care object as a function of one or more person or entity criteria;

automatically determine whether to create anew health care object or modify an existing health care object based on the outcome of application of the first set of matching criteria rules;

automatically modify an existing health care object or create a new health care object from said transformed or normalized data elements based on the outcome of said determination step, wherein said existing or new health care object is an object-oriented software environment object subject to an object hierarchy;

automatically obtain and apply a second set of rules specifying time-dependent criteria for scheduling healthcare events every time said new health care object is created or said existing health care object is modified;

and

store the mapped data elements in a data store in accordance with a health information model, wherein said health information model associates the patient or individual with a patient or individual record, said record comprising;

identification information for one or more third parties associated with providing healthcare for the patient or individual;

health condition and health service information for the patient or individual, including timeline information;

medication information for the patient or individual;

lifestyle information for the patient or individual;

health treatment, monitoring and encounter information for the patient or individual; and

medical findings and measure data for the patient or individual.

20. The system of claim 19, further wherein the microprocessor or processor is caused by the program to:

receive data or information relating to a health condition, service, product, treatment or encounter for the patient or individual; and

determine healthcare decisions, diagnoses or treatment for said patient or individual based upon the data or information relating to a health condition, service, product, treatment or encounter, and the mapped data elements stored in a data store in accordance with the health information model.

21. The system of claim 19, further wherein the microprocessor or processor is caused by the program to:

receive data or information relating to a plurality of health services performed for or provided to the patient or individual; and

determine, based upon the mapped data elements stored in a data store in accordance with the health information model, whether any one or more of said plurality of health services is related to or associated with one or more health conditions of the patient or individual.

22. The system of claim 21, further wherein the microprocessor or processor is caused by the program to create a timeline of health services or events related to or associated with the patient or individual, based upon information in the patient or individual'"'"'s health record.

23. The system of claim 20, wherein the mapping the transformed or normalized data elements in accordance with an ontology is performed using one or more code sets, vocabularies, or rule sets;

and

further wherein the one or more code sets, vocabularies, or rule sets are updated, modified, or extended based upon the healthcare decision, diagnosis or treatment determination.

24. The system of claim 19, wherein the transformed or normalized data elements comprise one or more of the following:

standardized healthcare diagnostic, treatment and management codes;

standardized healthcare or clinical terms and classifications;

or

standardized medical findings and measure terms and units.

25. The system of claim 19, wherein the confidence indicator or weight is based on one or more of the following:

the identity of the source of information or data;

the history and amount of processing required, and how and when the information or data is received, wherein the confidence indicator or weight is adjusted over time;

or

the relevance of the data in relation to an ontology.