Method and system for correlating data from multiple sources without compromising confidentiality requirements

• US 20040205080A1
• Filed: 05/04/2004
• Published: 10/14/2004
• Est. Priority Date: 10/04/2000
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Patel, Baiju V.
• Granted Patent: US 7,363,320 B2
• Time in Patent Office: Days
• US Class Current: 707/100
• CPC Class Codes: G06F 21/6254 by anonymising data, e.g. decorrelating personal data from the owner's identification

Abstract

A method and system is provided for correlating data. A data tuple includes a unique record ID and a record. At least one data tuple is sent from a data supplier to a data user. An entity correlator receives at least one pair of the record ID and an identifying ID from a data supplier. The data user forwards a record ID list to the entity correlator. The record ID list includes at least one record ID. The entity correlator generates an entity list and sends it to the data user. The entity list correlates each entity in the entity list with the at least one record ID.

Claims

1. A method, comprising:

receiving, by an entity correlator from a DataSupplier, at least one pair of a record ID and an identifying ID, both being associated with a third-party entity, the record ID including a Supplier ID to identify the DataSupplier, and a RecNum, the RecNum being an identification number assigned by the DataSupplier to the third-party entity to identify the third-party entity and parties other than the DataSupplier cannot identify the entity based solely on the RecNum, and the at least one pair being transmitted in conjunction with a data tuple including the record ID and a record, the record including information about the third-party entity but lacking identifying information to identify the third-party entity;

storing said at least one pair in a memory;

utilizing the identifying ID to identify the third-party entity associated with the RecNum contained in the record ID;

correlating a plurality of RecNums received from a plurality of DataSuppliers to the third-party entity;

receiving a record ID list from a DataUser at said entity correlator;

said record ID list including at least one selected record ID;

generating an entity list, by said entity correlator, said entity list correlating said third-party entity in the entity list with one of said record IDs included in said record ID list; and

sending said entity list from said entity correlator to said DataUser.

2. The method of claim 1, wherein said record includes a medical record.

3. The method of claim 1, wherein said record includes a personal record.

4. The method of claim 1, wherein said third-party entity includes a company.

5. The method of claim 1, wherein said third-party entity includes an organization.

6. A method, comprising:

assigning, by a DataSupplier, an identification number, called a RecNum, to a third-party entity to identify the third-party entity, the RecNum not being able to be used by other parties to identify the third-party entity;

generating data about the third party-entity, including a record containing information about the third-party entity but lacking information to identify the third-party entity, and a record ID, including a supplier ID to identify the DataSupplier;

sending at least one data tuple from the DataSupplier to a DataUser, said at least one data tuple including the record ID and the record;

sending, from the DataSupplier to an entity correlator, at least one pair of the record ID and an identifying ID, both being associated with the third-party entity, the identifying ID identifying the third-party entity associated with the RecNum contained in the record ID,

wherein the record ID is later utilized to correlate all records associated with the third-party entity.

7. The method of claim 6, wherein said record includes a medical record.

8. The method of claim 6, wherein said record includes a personal record.

9. The method of claim 6, wherein said third-party entity includes a company.

10. The method of claim 6, wherein said third-party entity includes an organization.

11. A method, comprising:

receiving, at a DataUser, at least one data tuple from a Data Supplier, each data tuple including a unique record ID and a record, said record containing information about a third-party entity, said record ID including a Supplier ID to identify the DataSupplier, and a Recnum, said RecNum being an identification number assigned by the DataSupplier to the third-party entity to identify the third-party entity, wherein parties other than the DataSupplier cannot identify the third-party entity based solely on the RecNum;

forwarding a record ID list from said DataUser to an entity correlator, said record ID list including at least one record ID, said DataUser gathering information about the third-party entity from a plurality of DataSuppliers; and

receiving an entity list from said entity correlator, said entity list correlating said third-party entity in the entity list with one of said record IDs included in said record ID list.

12. The method of claim 11, wherein said record includes a medical record.

13. The method of claim 11, wherein said record includes a personal record.

14. The method of claim 11, wherein said third-party entity includes a company.

15. The method of claim 11, wherein said third-party entity includes an organization.

16. A system, comprising:

a DataSupplier to generate at least one data tuple, to send said at least one data tuple, to generate at least one pair, and to send the at least one pair, the at least one data tuple including a record ID and a record, each pair including the record ID and an identifying ID, wherein the DataSupplier generates data about a third-party entity which is included in the record, the record ID including a Supplier ID to identify the DataSupplier and a RecNum, the RecNum being an identification number assigned by the DataSupplier to identify the third-party entity, wherein parties other than the DataSupplier cannot identify the third-party entity based solely on the RecNum, the identifying ID identifying the third-party entity, and the record lacking information to identify the third-party entity;

a DataUser to receive said at least one data tuple from said DataSupplier, to gather information about the third-party entity from a plurality of DataSuppliers, to generate a record ID list including said record ID from at least one data tuple, and to send said record ID list; and

an entity correlator to receive said at least one pair from said DataSupplier, to receive said record ID list, to produce an entity list based on said record ID List, said entity list including said RecNum assigned to the third-party entity, said RecNum being matched to one of said at least one record ID from said record ID list, and to send said entity list to said Data User.

17. The system of claim 16, wherein said DataSupplier includes,

a collector to collect data, said data including the record and the identifying ID,

a generator to generate the record ID,

a former to form said at least one data tuple, the at least one data tuple including the record ID and the corresponding record, and

an extractor to extract the record ID and the identifying ID, which form said at least one pair.

18. The system of claim 16, wherein said DataUser includes,

a first receiver to receive at least one data tuple from said DataSupplier;

a former to form said record ID list based on said at least one data tuple received by said first receiver; and

a second receiver to receive said entity list from said entity correlator.

19. The system of claim 16, wherein the third-party entity is not the DataSupplier, the DataUser, or the entity correlator.

20. The system of claim 16, wherein the RecNum is unique to the third-party entity.

21. The system of claim 16, wherein the identifying ID is a social security number.

22. The system of claim 16, wherein the identifying ID is a name.

23. An entity correlator, comprising:

a receiver to receive at least one pair, the at least one pair including a record ID and an identifying ID, the at least one pair being transmitted in conjunction with said record ID and a record;

a storage mechanism to store said at least one pair;

a second receiver to receive a record ID list including the at least one record ID from a data user;

a correlator to correlate the at least one record ID included in said record list according to said record ID stored in the storage mechanism;

a generator to generate at least one entity number, each entity number corresponding to said identifying ID;

a former to form an entity list with at least one entity, the entity list listing the at least one entity and the at least one record ID; and

a transmitter to send the entity list to said data user.

24. The entity correlator of claim 23, wherein the third-party entity is not the DataSupplier, the DataUser, nor the entity correlator.

25. The entity correlator of claim 23, wherein the RecNum is unique to the third-party entity.

26. The entity correlator of claim 23, wherein the identifying ID is a social security number.

27. The entity correlator of claim 23, wherein the identifying ID is a name.