Methods and systems for managing distributed digital medical data

• US 8,612,259 B2
• Filed: 01/14/2011
• Issued: 12/17/2013
• Est. Priority Date: 08/16/2002
• Status: Active Grant

• Current Assignee: Medecision Incorporated (Health Care Service Corporation)
• Original Assignee: Medecision Incorporated (Health Care Service Corporation)
• Inventors: Menschik, Elliot D., Corio, Christopher R., Davis, Wayne F., Didizian, Haig C.
• Primary Examiner(s): NGUYEN, HIEP VAN
• Application Number:
  US13/006,584
• Publication Number:
  US 20110166890A1
• Time in Patent Office: 1,068 Days
• Field of Search: 705/3
• US Class Current: 705/3
• CPC Class Codes: G06F 16/68 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 70/20 relating to practices or guidelines

Abstract

A network for mediating the peer-to-peer transfer of digital patient medical data includes a plurality of distributed agents each associated with a health care provider and connected to a central system. Periodically the agents collect local information relating to patient medical files and/or data streams, for example diagnostic images and associated reports, and process that information into metadata files acting as pointers to the original files. The metadata files are transmitted to the central system where they are parsed and the attributes are stored on the central system in patient records with records from the same patient grouped together whenever possible. Registered users can search the central system, even in the absence of a unique identifier, to identify patient records pointing to the remote patient medical files. Upon finding a patient medical file, the invention provides a streamlined process for communicating access authorization from the patient to the hospital or facility storing the medical files. Once patient authorization is received, secure processes are provided for transferring the data in its entirety to or for viewing by the user in a peer-to-peer fashion.

Claims

1. A method operable on a computer for managing distributed medical data, comprising the steps of:

receiving, by a computer, a first metadata file containing attributes relating to a first remotely stored patient medical file, the first metadata file including attributes relating to the contents of the first patient medical file and a location of the first patient medical file in a first medical information system, the first metadata file being generated by a first agent associated with the location of the first patient medical file in the first medical information system;

extracting the attributes from the first metadata file;

processing selected attributes extracted from the first metadata file to standardize the attributes for content, the standardized attributes representing data having the same meaning across different medical information systems each medical information system having respective agents that generate metadata files for locally stored patient medical files;

storing the selected standardized attributes in a database entry in a database relating to patients;

receiving, by the computer, a second metadata file containing attributes relating to a second remotely stored patient medical file, the second metadata file including attributes relating to the contents of the second patient medical file and a location of the second patient medical file in a second medical information system, the second metadata file being generated by a second agent associated with the location of the second patient medical file in the second medical information system;

extracting the attributes from the second metadata file; and

comparing, by the computer, the attributes from the second metadata file to the attributes stored in the database entry to determine if the second metadata file matches the database entry.

2. A method in accordance with claim 1 wherein when the second metadata file matches the database entry, the computer stores data from the second metadata file in the database entry;

otherwise, the computer creates a new database entry and stores data from the second metadata file in the new database entry.

3. A method in accordance with claim 1 wherein the step of comparing includes the steps of:

parsing the second metadata file to extract the attributes contained therein; and

matching at least one attribute extracted from the second metadata data file to a corresponding attribute in the database entry.

4. A method in accordance with claim 3 wherein the step of determining if the second metadata file relates to the database entry includes determining if the second metadata file is a match, a non-match or indeterminate with respect to the database entry.

5. A method in accordance with claim 4 and further comprising the steps of:

when the second metadata file matches the database entry, updating the database entry; and

when the second metadata file is a non-match with the database entry, creating a new database entry based on the attributes in the second metadata file.

6. A method in accordance with claim 5 and further including the step of, when the second metadata file is indeterminate in its relationship to the database entry, flagging the second metadata file as indeterminate.

7. A method in accordance with claim 1 wherein the first and second metadata files each further includes attributes relating to the identity of a patient.

8. A method in accordance with claim 1 wherein the step of comparing includes the steps of:

obtaining a statistical analysis of patient population data relating to the database entry;

generating, for specific attributes, an agreement weight and a disagreement weight based on the statistical analysis;

generating scores based on the agreement weight for determining matches;

generating scores based on the disagreement weights for determining non-matches;

generating a composite weight based on the comparison of attributes in the search request with the standardized attributes in the database entry; and

comparing the composite weight to the scores for determining matches and the scores for determining non-matches.

9. A system for managing distributed medical data, comprising:

a processor;

a memory connected to the processor and storing instructions for controlling the operation of the processor;

the processor operative with the instructions in the memory to perform the steps of;

receiving a first metadata file containing attributes relating to a first remotely stored patient medical file, the first metadata file including attributes relating to the contents of the first patient medical file and a location of the first patient medical file in a first medical information system, the first metadata file being generated by a first agent associated with the location of the first patient medical file in the first medical information system;

extracting the attributes from the first metadata file;

processing selected attributes extracted from the first metadata file to standardize the selected attributes for content, the standardized attributes representing data having the same meaning across different medical information systems each medical information system having respective agents that generate metadata files for locally stored patient medical files;

storing the selected standardized attributes in a database entry in a database relating to patients;

receiving a second metadata file containing attributes relating to a second remotely stored patient medical file, the second metadata file including attributes relating to the contents of the second patient medical file and a location of the second patient medical file in a second medical information system, the second metadata file being generated by a second agent associated with the location of the second patient medical file in the second medical information system;

extracting the attributes from the second metadata file; and

comparing the attributes from the second metadata file to the attributes stored in the database entry to determine if the second metadata file matches the database entry.

10. A system in accordance with claim 9 wherein when the second metadata file matches the database entry, the computer stores data from the second metadata file in the database entry;

otherwise, the computer creates a new database entry and stores data from the second metadata file in the new database entry.

11. A system in accordance with claim 9 wherein the step of comparing includes the steps of:

parsing the second metadata file to extract the attributes contained therein; and

matching at least one attribute extracted from the second metadata data file to a corresponding attribute in the database entry.

12. A system in accordance with claim 11 wherein the step of determining if the second metadata file relates to the database entry includes determining if the second metadata file is a match, a non-match or indeterminate with respect to the database entry.

13. A system in accordance with claim 12 and further comprising the steps of:

when the second metadata file matches the database entry, updating the database entry; and

when the second metadata file is a non-match with the database entry, creating a new database entry based on the attributes in the second metadata file.

14. A system in accordance with claim 13 and further including the step of, when the second metadata file is indeterminate in its relationship to the database entry, flagging the second metadata file as indeterminate.

15. A system in accordance with claim 9 wherein the first and second metadata files each further includes attributes relating to the identity of a patient.

16. A system in accordance with claim 9 wherein the step of comparing includes the steps of:

obtaining a statistical analysis of patient population data relating to the database entry;

generating, for specific attributes, an agreement weight and a disagreement weight based on the statistical analysis;

generating scores based on the agreement weight for determining matches;

generating scores based on the disagreement weights for determining non-matches;

generating a composite weight based on the comparison of attributes in the search request with the standardized attributes in the database entry; and

comparing the composite weight to the scores for determining matches and the scores for determining non-matches.

17. A system for managing distributed medical data, comprising:

means for receiving a first metadata file containing attributes relating to a first remotely stored patient medical file, the first metadata file including attributes relating to the contents of the first patient medical file and a location of the first patient medical file in a first medical information system, the first metadata file being generated by a first agent associated with the location of the first patient medical file in the first medical information system;

means for extracting the attributes from the first metadata file;

means for processing selected attributes extracted from the first metadata file to standardize the attributes for content, the standardized attributes representing data having the same meaning across different medical information systems each medical information system having respective agents that generate metadata files for locally stored patient medical files;

means for storing the selected standardized attributes in a database entry in a database relating to patients;

means for receiving a second metadata file containing attributes relating to a second remotely stored patient medical file, the second metadata file including attributes relating to the contents of the second patient medical file and a location of the second patient medical file in a second medical information system, the second metadata file being generated by a second agent associated with the location of the second patient medical file in the second medical information system;

means for extracting the attributes from the second metadata file; and

means for comparing the attributes from the second metadata file to the attributes stored in the database entry to determine if the second metadata file matches the database entry.

18. A non-transitory computer readable storage medium storing thereon a computer program operable on a computer for managing distributed medical data by performing the steps of:

receiving, by the computer, a first metadata file containing attributes relating to a first remotely stored patient medical file, the first metadata file including attributes relating to the contents of the first patient medical file and a location of the first patient medical file in a first medical information system, the first metadata file being generated by a first agent associated with the location of the first patient medical file in the first medical information system;

extracting the attributes from the first metadata file;

processing selected attributes extracted from the first metadata file to standardize the attributes for content, the standardized attributes representing data having the same meaning across different medical information systems each medical information system having respective agents that generate metadata files for locally stored patient medical files;

storing the selected standardized attributes, in a database entry in a database relating to patients;

receiving, by the computer, a second metadata file containing attributes relating to a second remotely stored patient medical file, the second metadata file including attributes relating to the contents of the second patient medical file and a location of the second patient medical file in a second medical information system, the second metadata file being generated by a second agent associated with the location of the second patient medical file in the second medical information system;

extracting the attributes from the second metadata file; and

comparing, by the computer, the attributes from the second metadata file to the attributes stored in the database entry to determine if the second metadata file matches the database entry.