# US 2025/0166751 A1 · Systems and methods for patient record matching

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0166751 A1
- Document ID: US20250166751A1
- Status: Published application
- Kind: A1
- Application number: 18/513,208
- Filed: 2023-11-17
- Published: 2025-05-22
- Earliest claimed: 2023-11-17
- Assignees: Express Scripts Strategic Development, Inc.
- Applicants: Express Scripts Strategic Development, Inc.
- Inventors: Narasimha Prasad Bingi; Sharmistha Vyas; Roshan Kumar; Madhumitha Raghunathan
- Web page: https://patentgrep.com/patent/US20250166751A1

## CPC

- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- G16H 50/70: for mining of medical data, e.g. analysing previous cases of other patients
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA

## Abstract

A system and method may monitor a stream of messages from plural different sources of medical records to identify a new or updated record of the medical records, identifying one or more suspect records from a system of record (SOR) database. The one or more suspect records are identified as being potential matches to the new or updated record that is identified. The system and method can determine that the one or more suspect records match the new or updated record, and can obtain a person entity profile related to the new or updated record from a person entity database. The system and method can merge the new or updated record with the one or more suspect records or splitting the new or updated record from the one or more suspect records based on the person entity profile that is obtained.

## Claims

### Claim 1

A method comprising:
monitoring a stream of messages from plural different sources of medical records to identify a new or updated record of the medical records;
identifying one or more suspect records from a system of record (SOR) database, the one or more suspect records identified as being potential matches to the new or updated record that is identified;
determining that the one or more suspect records match the new or updated record;
obtaining a person entity profile related to the new or updated record from a person entity database; and
merging the new or updated record with the one or more suspect records or splitting the new or updated record from the one or more suspect records based on the person entity profile that is obtained.

### Claim 2 (depends on 1)

The method of claim 1, wherein the new or updated record is identified in real time.

### Claim 3 (depends on 1)

The method of claim 1, wherein the one or more suspect records are determined to match the new or updated record by comparing information contained within the one or more suspect records and the new or updated record using matching rules.

### Claim 4 (depends on 3)

The method of claim 3, further comprising:
authoring one or more new rules or one or more changes to the matching rules off-line while the matching rules without the one or more new rules or the one or more changes continue to be used to determine whether the one or more suspect records match the new or updated record.

### Claim 5 (depends on 4)

The method of claim 4, further comprising:
testing the one or more new rules or the one or more changes to the matching rules off-line using the medical records without merging the new or updated record with the one or more suspect records and without splitting the new or updated record from the one or more suspect records.

### Claim 6 (depends on 1)

The method of claim 1, wherein the one or more suspect records include plural suspect records, and further comprising:
determining that two or more of the suspect records match each other; and
merging the two or more of the suspect records with each other.

### Claim 7 (depends on 1)

The method of claim 1, wherein the medical records include source identifiers uniquely identifying which of the sources generated the medical records and the person entity database stores the source identifiers associated with each of several different persons,
wherein merging the new or updated record with the one or more suspect records occurs responsive to the source identifiers in the new or updated record and the one or more suspect records being associated with two or more of the different persons in the person entity database.

### Claim 8 (depends on 1)

The method of claim 1, wherein the medical records include source identifiers uniquely identifying which of the sources generated the medical records and the person entity database stores the source identifiers associated with each of several different persons,
wherein splitting the new or updated record from the one or more suspect records occurs responsive to the source identifiers in the new or updated record and the one or more suspect records being associated with a single person of the different persons in the person entity database along with one or more other source identifiers.

### Claim 9

A record matching system comprising:
one or more data sync processors configured to monitor a stream of messages from plural different sources of medical records to identify a new or updated record of the medical records; and
a person matching engine configured to identify one or more suspect records from a system of record (SOR) database, the one or more suspect records identified as being potential matches to the new or updated record that is identified, the person matching engine also configured to determine that the one or more suspect records match the new or updated record, obtain a person entity profile related to the new or updated record from a person entity database, and merge the new or updated record with the one or more suspect records or splitting the new or updated record from the one or more suspect records based on the person entity profile that is obtained.

### Claim 10 (depends on 9)

The record matching system of claim 9, wherein the one or more data sync processors are configured to identify the new or updated record in real time.

### Claim 11 (depends on 9)

The record matching system of claim 9, wherein the person matching engine is configured to determine that the one or more suspect records match the new or updated record by comparing information contained within the one or more suspect records and the new or updated record using matching rules.

### Claim 12 (depends on 11)

The record matching system of claim 11, wherein the person matching engine is configured to be used to author one or more new rules or one or more changes to the matching rules off-line while the matching rules without the one or more new rules or the one or more changes continue to be used to determine whether the one or more suspect records match the new or updated record.

### Claim 13 (depends on 12)

The record matching system of claim 12, wherein the person matching engine is configured to test the one or more new rules or the one or more changes to the matching rules off-line using the medical records without merging the new or updated record with the one or more suspect records and without splitting the new or updated record from the one or more suspect records.

### Claim 14 (depends on 9)

The record matching system of claim 9, wherein the one or more suspect records include plural suspect records, and the person matching engine is configured to determine that two or more of the suspect records match each other; and further comprising:
one or more update processors configured to merge the two or more of the suspect records with each other.

### Claim 15 (depends on 9)

The record matching system of claim 9, wherein the medical records include source identifiers uniquely identifying which of the sources generated the medical records and the person entity database stores the source identifiers associated with each of several different persons,
wherein the person matching engine is configured to merge the new or updated record with the one or more suspect records responsive to the source identifiers in the new or updated record and the one or more suspect records being associated with two or more of the different persons in the person entity database.

### Claim 16 (depends on 9)

The record matching system of claim 9, wherein the medical records include source identifiers uniquely identifying which of the sources generated the medical records and the person entity database stores the source identifiers associated with each of several different persons,
wherein the person matching engine is configured to split the new or updated record from the one or more suspect records responsive to the source identifiers in the new or updated record and the one or more suspect records being associated with a single person of the different persons in the person entity database along with one or more other source identifiers.

### Claim 17

A method comprising:
monitoring a stream of messages from plural different sources of medical records to identify a new or updated record of the medical records;
identifying one or more suspect records from a system of record (SOR) database, the one or more suspect records identified as being potential matches to the new or updated record that is identified;
determining that the one or more suspect records match the new or updated record;
obtaining a person entity profile related to the new or updated record from a person entity database, the person entity profile including source identifiers uniquely identifying which of the sources generated the medical records associated with each of several different persons; and
one or more of (a) merging the new or updated record with the one or more suspect records or (b) splitting the new or updated record from the one or more suspect records,
wherein merging the new or updated record with the one or more suspect records occurs responsive to the source identifiers in the new or updated record and the one or more suspect records being associated with two or more of the different persons in the person entity database, and
wherein splitting the new or updated record from the one or more suspect records occurs responsive to the source identifiers in the new or updated record and the one or more suspect records being associated with a single person of the different persons in the person entity database along with one or more other source identifiers.

### Claim 18 (depends on 17)

The method of claim 17, wherein the new or updated record is identified in real time.

### Claim 19 (depends on 17)

The method of claim 17, wherein the one or more suspect records are determined to match the new or updated record by comparing information contained within the one or more suspect records and the new or updated record using matching rules, and further comprising:
authoring one or more new rules or one or more changes to the matching rules off-line while the matching rules without the one or more new rules or the one or more changes continue to be used to determine whether the one or more suspect records match the new or updated record.

### Claim 20 (depends on 19)

The method of claim 19, further comprising:
testing the one or more new rules or the one or more changes to the matching rules off-line using the medical records without merging the new or updated record with the one or more suspect records and without splitting the new or updated record from the one or more suspect records.
