Identity Matching And Information Linking

• US 20110246230A1
• Filed: 03/31/2010
• Published: 10/06/2011
• Est. Priority Date: 03/31/2010
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Nolan, Sean, Bordenet, Matthew, Punniamoorthy, Pranavakumar, SampathKumar, VenkataChari, Ahmed, Muzammil, Sie, Yu Lin
• Application Number:
  US12/751,805
• Publication Number:
  US 20110246230A1
• Time in Patent Office: Days
• US Class Current: 705/3
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records

Abstract

A connection component establishes an identity of a person for permitting access to information in a database. Responsive to establishing the identity of the person, the connection component may link an external account to the information in the database for providing a flow of information between the database and the external account.

Claims

1. A computer-implemented method comprising:

implementing, by a processor, a connection component providing electronic access to hospital visit records maintained in a hospital database;

creating, by the connection component, an account for a patient, the account created by the connection component corresponding to a health repository account of the patient maintained by a health information repository;

establishing, by the connection component, an identity of the patient for permitting access to hospital visit records of the patient; and

linking the hospital visit records of the patient to the health repository account of the patient to provide the hospital visit records to the health repository account.

2. The method according to claim 1, the establishing the identity of the patient comprising:

obtaining patient identification information from the patient for comparison with identity information for the patient maintained in the hospital database; and

executing automated matching that establishes the identity of the patient when there is a match between the identification information obtained and the identity information for the patient maintained in the hospital database.

3. The method according to claim 1, the establishing the identity of the patient further comprising:

obtaining identification information for the patient for comparison with identity information for the patient maintained in the hospital database;

when there is not a match between the identification information obtained for the patient and the identity information for the patient maintained in the hospital database, performing manual matching comprising;

providing a filter having selectable identity matching criteria corresponding to the identification information received for the patient; and

deselecting one or more identity matching criteria by using the filter to obtain a broader search for effecting a match between the identification information received for the patient and the identity information maintained in the database.

4. The method according to claim 1, wherein the patient is a first patient and the health repository account has a first record for the first patient, the health repository account having a second record for a second patient, the account created by the connection component having a corresponding first record and second record, further comprising:

providing, by the connection component, an interface for the first patient to manage the first record and the second record in the connection component account.

5. The method according to claim 1, further comprising using a connection-component-specific data type recognized by the health repository to manage a relationship between the account created by the connection component, the health repository account and the hospital visit records of the patient.

6. The method according to claim 5, wherein the health repository account is a first health repository account having a health record for the patient, the account created by the connection component having a corresponding record, further comprising:

establishing a sharing relationship for sharing the health record between the first health repository account and a second health repository account, the sharing relationship being supported by the connection component when a user of the second health component account attempts to access the hospital visit records of the patient.

7. The method according to claim 6, further comprising:

using a connection-component-specific data type to support the sharing relationship, the connection-component-specific data type enabling binding of a single patient identifier to multiple health repository account identifiers and health record identifiers.

8. A computing device comprising:

a processor in communication with computer-readable storage media;

a connection component, maintained in the computer-readable storage media and executed on the processor, to generate an interface for display to a connection component operator, the interface enabling specification of one or more of a plurality of supported fields for multiple identification criteria, wherein the connection component operator specifies at least one of the plurality of supported fields for changing identification information to be requested from a user.

9. The computing device according to claim 8, the interface providing for addition of a custom field for identification criteria, the custom field specifying an identification criterion not included in the supported fields, the connection component operator adding the custom field for changing identification information requested in an identification information interface displayed to a user of the connection component, the identification information interface requesting identification information from the user for establishing an identity.

10. The computing device according to claim 8, the interface further being configured to display fields selectable by the connection component operator for specifying whether the identification information requested from the user is matched to user identity information using automated matching or a manual matching.

11. The computing device according to claim 10, the automated matching comprising comparing identification information received from the user with identity information maintained in a database, and automatically establishing the identity of the user when there is a match between the identification information received from the user and the identity information maintained in the database.

12. The computing device according to claim 10, the manual matching comprising a match request interface displayed to the connection component operator, the match request interface displaying identification information received from the user for comparison with displayed identity information maintained in the database.

13. The computing device according to claim 12, the manual matching further comprising a filter displayed in the match request interface having selectable identity matching criteria corresponding to the identification information received from the user, one or more identity matching criteria being de-selectable using the filter to locate additional possible matches.

14. The computing device according to claim 13, wherein the selectable identity matching criteria in the filter is automatically changed as a result of the connection component operator selecting at least one of the plurality of supported fields for changing the identification information to be requested from a user.

15. The computing device according to claim 8, wherein the connection component is in communication with a database containing user information, the connection component being configured to:

request selected identification information in an interface presented to the user for obtaining the selected identification information from the user;

establish an identity of the user by matching the selected identification information obtained from the user with identity information for the user maintained in the database; and

responsive to establishing the identity of the user, link an external account of the user to the user information in the database for providing access to the user information in the database through the external account.

16. A method comprising:

implementing, by a processor, a connection component providing electronic access to patient information maintained in a database;

creating, by the connection component, a first account corresponding to a first health repository account in a health information repository for enabling access to the patient information through the first account;

creating by the connection component a second account, the second account corresponding to a second health repository account in the health information repository, wherein there is a sharing relationship established at the health information repository between the first health repository account and the second health repository account; and

supporting, by the connection component, the sharing relationship for permitting the second account to access the patient information accessible in the database through the first account.

17. The method according to claim 16,

wherein the sharing relationship in the health information repository gives the second health repository account read-only access to information in the first health repository account,

wherein the second account created by the connection component is provided read-only access to the patient information accessible in the database through the first account.

18. The method according to claim 16, wherein there is a first connection component record in the first account created by the connection component and a corresponding first health record in the first health repository account, further comprising:

using a connection-component-specific data type to create globally unique identifiers for the first connection component record and the first health record for managing a relationship between the first connection component record and the first health record.

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

establishing, by the connection component, an identity of a patient corresponding to the patient information in the database for permitting the access the patient information; and

responsive to establishing the identity of the patient, linking the patient information in the database to the first health repository account for providing a flow of the patient information to the first health repository account.

20. The method according to claim 19, wherein an attempt by the second account to establish an identity of the patient corresponding to the patient information in the database for permitting the access the patient information is denied by the connection component based on linking of the patient information already being established with the first health repository account.