Method and system for generating personal/individual health records

• US 20070027721A1
• Filed: 07/28/2006
• Published: 02/01/2007
• Est. Priority Date: 10/11/2000
• Status: Active Grant

• Current Assignee: Healthtrio LLC (Spok Holdings, Inc.)
• Original Assignee: Healthtrio LLC (Spok Holdings, Inc.)
• Inventors: Peterson, John, Hasan, Malik, Wallen, J.
• Granted Patent: US 7,533,030 B2
• Time in Patent Office: Days
• US Class Current: 705/3
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 50/70 for mining of medical data, e.g. analysing previous cases of other patients

Abstract

A system and method for generating and/or updating a personal/individual health record. Inputs of data to the system may come from diverse sources including, but not limited to, patient questionnaires, insurance company (or other payor) claims data, hospitals, clinics and other institutional providers, and individual physicians and physicians'"'"' offices.

Claims

1. A data processing system comprising:

a messaging facility configured to receive a data element indicative of a health related parameter for a patient;

a correlation module configured to determine a SNOMED code corresponding to said data element; and

a PHR population engine operably associated with said correlation module, wherein said PHR population engine is configured to insert health related data associated with said SNOMED code into a personal/individual health record associated with said patient.

2. The system of claim 1, wherein said PHR population engine is configured to insert said SNOMED code into said peronsal/individual health record.

3. The system of claim 2, further comprising an access management module configured to communicate with a client system, wherein said access management module is configured to update said personal/individual health record based on input received from said patient.

4. The system of claim 3, wherein said access management module is configured to transmit a description of said SNOMED code to said client system.

5. The system of claim 4, wherein said PHR population engine is configured to associate a first description and a second description with said SNOMED code, wherein said first description is synonymous with said second description.

6. The system of claim 4, wherein said first description uses medical terminology and wherein said second description uses layman'"'"'s terms.

7. The system of claim 6, further comprising a filtering module configured to determine whether said client system is associated with a healthcare provider and wherein said access management module is configured to transmit said first description if said filtering module determines said client system is associated with a health care provider.

8. The system of claim 7, wherein said access management module is configured to transmit said second description to said client system if said filtering module determines said client system is not associated with a health care provider.

9. The system of claim 4, wherein said filtering module is configured to change the description of said SNOMED code based on a description of a SNOMED code up a SNOMED hierarchy to adjust the resolution of data.

10. The system of claim 8, wherein said PHR population engine is configured to determine whether said personal/individual health record includes any entries related to said SNOMED code.

11. The system of claim 3, wherein said population engine is configured to associate entries in said personal/individual health record related to said SNOMED code.

12. The system of claim 3, further comprising a PHR database configured to store a plurality of personal/individual health records and further comprising a data analysis module configured to identify patterns or relationships among said plurality of personal/individual health records based on related SNOMED codes.

13. The system of claim 12, wherein said data analysis module is configured to identify patterns or relationships among over ten thousand personal/individual health records.

14. The system of claim 13, wherein said data analysis module is configured to measure effectiveness of healthcare treatment based on outcomes associated with said plurality of personal/individual health records having related SNOMED codes.

15. The system of claim 13, wherein said data analysis module is configured to perform population studies based on SNOMED codes in said plurality of personal/individual health records.

16. The system of claim 13, wherein said data analysis module is configured to analyze quality of care associated with health care providers based on an analysis of said plurality of personal/individual health records.

17. The system of claim 13, wherein said data analysis module is configured to analyze cost of health care providers based on an analysis of said plurality of personal/individual health records.

18. A computer-readable medium having stored thereon a data structure comprising:

a diagnosis data field for storing a plurality of diagnosis data elements representative of medical diagnoses associated with a patient, wherein at least one diagnosis data element has been derived from a payor diagnosis code using a SNOMED code.

a procedure data field for storing a plurality of procedure data elements representative of medical procedures associated with said patient, wherein at least one procedure data element has been derived from a payor procedure code using a SNOMED code.

19. The data structure of claim 18, wherein at least one diagnosis data element has been derived from an ICD code.

20. The data structure of claim 18, wherein at least one procedure data element has been derived from a CPT code.

21. The data structure of claim 18, further comprising a medication data field for storing a plurality of medication data elements representative of medications associated with said patient, wherein at least one medication data element has been derived from a health insurance medication code using a SNOMED code.

22. The data structure of claim 19, wherein at least one medication data element has been derived from a NDC code using a SNOMED code.

23. The data structure of claim 18, wherein at least one procedure data element has been derived from a questionnaire answered by said patient using a SNOMED code.

24. The data structure of claim 18, further comprising a relationship field for storing an association data element that establishes a relationship among one of the plurality of diagnosis data elements and one of the plurality of procedure data elements.

25. The data structure of claim 18, further comprising an index field for storing a plurality of index data elements representative of health care patients, wherein each said index data element uniquely identifies an individual health care patient, wherein said index data element is assigned to a patient after determining whether the patient has a unique combination a data elements selected from the group consisting of a tax ID, birthday, gender, and address.

26. The data structure of claim 25, further comprising a security field for storing a plurality of security data elements representative of access rights to said plurality of diagnosis data elements and said plurality of procedure data elements associated with one of said plurality of index data elements.

27. The data structure of claim 26, wherein said security field includes a family field for storing family data elements representative of access rights of family members associated with one of said plurality of index data elements.

28. A computer-usable medium having computer readable instructions stored thereon for execution by a processor to perform a method comprising:

receiving a claims data element indicative of a health insurance claim associated with a patient;

determining a SNOMED code corresponding to said claims data element;

inserting said SNOMED code into a personal/individual health record associated with said patient;

receiving a questionnaire data element indicative of an answer to a questionnaire by said patient;

determining a SNOMED code corresponding said questionnaire data element;

inserting said SNOMED code into said individual health record associated with said patient

receiving a clinical data element indicative of clinical data associated with said patient;

determining a SNOMED code corresponding to said clinical data element; and

inserting said SNOMED code into said individual health record associated with said patient.