# US 10,504,619 B2 · Systems and methods for translating messages between a healthcare entity and a vendor entity

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

- Number: US 10,504,619 B2
- Document ID: US10504619B2
- Status: Granted
- Kind: B2
- Application number: 16/360,493
- Filed: 2019-03-21
- Published: 2019-07-18
- Granted: 2019-12-10
- Earliest claimed: 2016-10-07
- Assignees: Redox, Inc.
- Applicants: Redox, Inc.
- Inventors: James Lloyd; Christopher Tobin-Campbell; Andrew Kitson; Nicholas Hatt; Nijay Patel
- Web page: https://patentgrep.com/patent/US10504619B2

## CPC

- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- G06F 16/258: {Data format conversion from or to a database}
- G06F 16/33: Querying
- G16H 40/20: for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
- H04L 51/08: Annexed information, e.g. attachments
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

An inbound message including medical record content may be received. The inbound message may indicate a healthcare entity and a vendor entity. It may be determined, from the healthcare entity and stored correspondences between medical record formats and healthcare entities, that the medical record content of the inbound message is in a first medical record format. Which configuration record of stored configuration records specifying combinations of sets of rules may be determined to apply as a translation to the inbound message based upon the medical record content of the inbound message and the first medical record format. The sets of rules as indicated by the configuration record may be accessed and applied to the inbound message to translate the medical record content in the inbound message from the first medical record format to the standardized format. The standardized format may be transmitted to the vendor entity.

## Claims

### Claim 1

A system configured to convert messages communicated between a healthcare entity and a vendor entity, the messages including medical record content, the system comprising:
physical non-transitory electronic storage storing:
correspondence information, wherein the correspondence information specifies correspondences between medical record formats of electronic medical records and healthcare entities, the medical record formats being customized by individual healthcare entities, the customizations including locations of medical record content within the electronic medical records, such that an individual medical record format corresponds to an individual healthcare entity; and
configuration record information, wherein the configuration record information includes configuration records specifying individual combinations of rules to convert messages between the medical record formats and a standardized medical record format, an individual configuration record specifying an individual combination of rules to convert messages between the individual medical record format and the standardized medical record format; and
one or more physical computer processors configured by computer readable instructions to:
receive an inbound message including particular medical record content, the inbound message indicating the individual healthcare entity and a vendor entity;
determine, from the correspondence information and the configuration record information, which configuration record to use to convert the inbound message to the standardized medical record format, wherein determination of the individual configuration record is based upon the particular medical record content of the inbound message and the indication of the first healthcare entity;
responsive to determination of the individual configuration record, apply the individual combination of rules to the inbound message to convert the particular medical record content in the inbound message from the individual medical record format to the standardized medical record format; and
effectuate transmission of the particular medical record content in the inbound message in the standardized medical record format to the vendor entity.

### Claim 2 (depends on 1)

The system of claim 1, wherein the individual medical record format is similar to at least one other medical record format.

### Claim 3 (depends on 1)

The system of claim 1, wherein the individual medical record format and the other individual medical record formats differ based upon customizations by the individual healthcare entities.

### Claim 4 (depends on 3)

The system of claim 3, wherein the individual combination of rules in the sets of rules specify the differences between the individual medical record format and the other individual medical record formats based upon the customizations.

### Claim 5 (depends on 1)

The system of claim 1, wherein a first rule in the individual combination of rules includes parsing the particular medical record content in the inbound message into structured objects including data fields.

### Claim 6 (depends on 5)

The system of claim 5, wherein a second rule in the individual combination of rules includes converting the data fields from the structured objects into standardized format fields of the standardized format.

### Claim 7 (depends on 1)

The system of claim 1, wherein one or more configuration records specify sets of rules that reference nested configuration records.

### Claim 8 (depends on 7)

The system of claim 7, wherein the nested configuration records specify combinations of sets of rules that are common between the one or more configuration records that reference the nested configuration records.

### Claim 9 (depends on 1)

The system of claim 1, wherein the particular medical record content includes an electronic health record.

### Claim 10 (depends on 1)

The system of claim 1, wherein the individual medical record formats follow one or more standards of communication.

### Claim 11

A method to convert messages communicated between a healthcare entity and a vendor entity, the messages including medical record content, the method being implemented in a computer system comprising one or more physical computer processors and non-transitory electronic storage, the method comprising:
obtaining, by the one or more physical computer processors, correspondence information, the correspondence information specifying correspondences between medical record formats of electronic medical records and healthcare entities, the medical record formats being customized by individual healthcare entities, the customizations including locations of medical record content within the electronic medical records, such that an individual medical record format corresponds to an individual healthcare entity;
obtaining, by the one or more physical computer processors, configuration record information, the configuration record information including configuration records specifying individual combinations of rules to convert messages between the medical record formats and a standardized medical record format, an individual configuration record specifying an individual combination of rules to convert messages between the individual medical record format and the standardized medical record format;
receiving, by the one or more physical computer processors, an inbound message including particular medical record content, the inbound message indicating the individual healthcare entity and a vendor entity;
determining, by the one or more physical computer processors from the correspondence information and the configuration record information, which configuration record to use to convert the inbound message to the standardized medical record format, wherein determination of the individual configuration record is based upon the particular medical record content of the inbound message and the indication of the first healthcare entity;
responsive to determination of the individual configuration record, applying the individual combination of rules to the inbound message to convert the particular medical record content in the inbound message from the individual medical record format to the standardized medical record format; and
effectuating, by the one or more physical computer processors, transmission of the particular medical record content in the inbound message in the standardized medical record format to the vendor entity.

### Claim 12 (depends on 11)

The method of claim 11, wherein the individual medical record format is similar to at least one other medical record format.

### Claim 13 (depends on 11)

The method of claim 11, wherein the individual medical record format and the other individual medical record formats differ based upon customizations by the individual healthcare entities.

### Claim 14 (depends on 13)

The method of claim 13, wherein the individual combination of rules in the sets of rules specify the differences between the individual medical record format and the other individual medical record formats based upon the customizations.

### Claim 15 (depends on 11)

The method of claim 11, wherein a first rule in the individual combination of rules includes parsing the medical record content in the inbound message into structured objects including data fields.

### Claim 16 (depends on 15)

The method of claim 15, wherein a second rule in the individual combination of rules includes converting the data fields from the structured objects into standardized format fields of the standardized format.

### Claim 17 (depends on 11)

The method of claim 11, wherein one or more configuration records specify sets of rules that reference nested configuration records.

### Claim 18 (depends on 17)

The method of claim 17, wherein the nested configuration records specify combinations of sets of rules that are common between the one or more configuration records that reference the nested configuration records.

### Claim 19 (depends on 11)

The method of claim 11, wherein the particular medical record content includes an electronic health record.

### Claim 20 (depends on 11)

The method of claim 11, wherein the individual medical record formats follow one or more standards of communication.