# US 2025/0166769 A1 · Messaging Protocol

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

- Number: US 2025/0166769 A1
- Document ID: US20250166769A1
- Status: Published application
- Kind: A1
- Application number: 19/030,816
- Filed: 2025-01-17
- Published: 2025-05-22
- Earliest claimed: 2016-12-28
- Assignees: Cerner Innovation, Inc.
- Applicants: Cerner Innovation, Inc.
- Inventors: Christopher Dillard Cline; Aravind R. Mereddi; Joel Robert Norton; Scott Gordon Siebers
- Web page: https://patentgrep.com/patent/US20250166769A1

## CPC

- G16H 15/00: ICT specially adapted for medical reports, e.g. generation or transmission thereof
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- G06F 21/606: {by securing the transmission between two devices or processes}
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- H04L 51/226: Delivery according to priorities
- H04L 51/48: Message addressing, e.g. address format or anonymous messages, aliases
- H04L 63/04: {for providing a confidential data exchange among entities communicating through data packet networks}
- 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
- H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)}
- H04L 67/54: Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods provide for implementation of a messaging protocol that provides security necessary for clinical messaging while also providing scalability needed to properly function within a clinical setting. The messaging protocol provides for federation of messages across messaging domains with a direct target address or via a role or group endpoint address that resolves to one or more target addresses. The messaging protocol also provides the ability to include content other than text in messages.

## Claims

### Claim 1

A computer-implemented method, comprising:
accessing, via at least one hardware processor associated with a source device that is configured to communicate at a medical environment that includes a control server, one or more electronic medical records that are stored at or associated with a database in the medical environment;
generating, via the at least one hardware processor, a payload for use with a message to be communicated via the control server;
sending, via the at least one hardware processor, a request to transmit the message to a destination associated with a target device, the message including the payload and comprising particular clinical information identified from one or more electronic medical records,
wherein:
the control server and the destination are in separate domains associated with the medical environment; and
the control server is configured to determine whether a first path for transmitting the message to a target endpoint address associated with the target device is unavailable; and
receiving, via one or both of the at least one hardware processor and the source device and in response to the sending of the request to transmit, a notification corresponding to content selected from a group comprising at least the message, the target endpoint address, and a second path for transmitting the message to the target endpoint address associated with the target device.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein sending the request to transmit includes addressing the request to transmit to the control server.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein the notification comprises a push receipt.

### Claim 4 (depends on 3)

The computer-implemented method of claim 3, wherein the push receipt is received at the source device from the control server.

### Claim 5 (depends on 4)

The computer-implemented method of claim 4, wherein the push receipt is configured to indicate to the source device information corresponding to the first path being unavailable.

### Claim 6 (depends on 3)

The computer-implemented method of claim 3, wherein the notification further comprises an indication that the second path to the target endpoint address has been identified as available for transmitting the message to the target endpoint address.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, wherein receiving the notification corresponds to determining delivery information with respect to the target endpoint address or with respect to use of the second path by the control server in connection with responding to the request to transmit.

### Claim 8

One or more non-transitory media having computer-readable instructions that, when executed by one or more hardware processors, cause the one or more hardware processors to facilitate a plurality of operations, the operations comprising:
accessing, via at least one hardware processor of the one or more hardware processors associated with a source device that is configured to communicate at a medical environment that includes a control server, one or more electronic medical records that are stored at or associated with a database in the medical environment;
generating, via the at least one hardware processor, a payload for use with a message to be communicated via the control server;
sending, via the at least one hardware processor, a request to transmit the message to a destination associated with a target device, the message including the payload and comprising particular clinical information identified from one or more electronic medical records,
wherein:
the control server and the destination are in separate domains associated with the medical environment; and
the control server is configured to determine whether a first path for transmitting the message to a target endpoint address associated with the target device is unavailable; and
receiving, via one or both of the at least one hardware processor and the source device and in response to the sending of the request to transmit, a notification corresponding to content selected from a group comprising at least the message, the target endpoint address, and a second path for transmitting the message to the target endpoint address associated with the target device.

### Claim 9 (depends on 8)

The one or more non-transitory media of claim 8, wherein sending the request to transmit includes addressing the request to transmit to the control server.

### Claim 10 (depends on 8)

The one or more non-transitory media of claim 8, wherein the notification comprises a push receipt.

### Claim 11 (depends on 10)

The one or more non-transitory media of claim 10, wherein the push receipt is received at the source device from the control server.

### Claim 12 (depends on 11)

The one or more non-transitory media of claim 11, wherein the push receipt is configured to indicate to the source device information corresponding to the first path being unavailable.

### Claim 13 (depends on 10)

The one or more non-transitory media of claim 10, wherein the notification further comprises an indication that the second path to the target endpoint address has been identified as available for transmitting the message to the target endpoint address.

### Claim 14 (depends on 8)

The one or more non-transitory media of claim 8, wherein receiving the notification corresponds to determining delivery information with respect to the target endpoint address or with respect to use of the second path by the control server in connection with responding to the request to transmit.

### Claim 15

A system having one or more hardware processors configured to facilitate a plurality of operations, the operations comprising:
accessing, via at least one hardware processor of the one or more hardware processors associated with a source device that is configured to communicate at a medical environment that includes a control server, one or more electronic medical records that are stored at or associated with a database in the medical environment;
generating, via the at least one hardware processor, a payload for use with a message to be communicated via the control server;
sending, via the at least one hardware processor, a request to transmit the message to a destination associated with a target device, the message including the payload and comprising particular clinical information identified from one or more electronic medical records,
wherein:
the control server and the destination are in separate domains associated with the medical environment; and
the control server is configured to determine whether a first path for transmitting the message to a target endpoint address associated with the target device is unavailable; and
receiving, via one or both of the at least one hardware processor and the source device and in response to the sending of the request to transmit, a notification corresponding to content selected from a group comprising at least the message, the target endpoint address, and a second path for transmitting the message to the target endpoint address associated with the target device.

### Claim 16 (depends on 15)

The system of claim 15, wherein sending the request to transmit includes addressing the request to transmit to the control server.

### Claim 17 (depends on 15)

The system of claim 15, wherein the notification comprises a push receipt, and, wherein the push receipt is received at the source device from the control server.

### Claim 18 (depends on 17)

The system claim 17, wherein the push receipt is configured to indicate to the source device information corresponding to the first path being unavailable.

### Claim 19 (depends on 17)

The system of claim 17, wherein the notification further comprises an indication that the second path to the target endpoint address has been identified as available for transmitting the message to the target endpoint address.

### Claim 20 (depends on 15)

The system of claim 15, wherein receiving the notification corresponds to determining delivery information with respect to the target endpoint address or with respect to use of the second path by the control server in connection with responding to the request to transmit.
