Systems and methods for clinical data exchange from electronic health record systems to participants

A computer-program product tangibly embodied in a non-transitory machine-readable storage medium, including instructions configured to cause one or more data processors to perform a set of actions including:

• creating, via a console, a query endpoint that is associated with an interoperability interface, configured to transmit one or more requests from an external entity to access clinical information associated with a particular subject encounter from a healthcare provider domain;
• creating a delivery endpoint, via the console, to receive the clinical information back to the external entity;
• establishing a communication channel between the healthcare provider domain and the external entity by linking the query endpoint and the delivery endpoint, wherein the communication channel is configured for a subject associated with the particular subject encounter;
• processing, via an engine configured in a cloud service, the one or more requests received through the communication channel, wherein the engine:
• identifies the subject and a healthcare provider associated with the subject encounter holding the clinical information based on a master subject index (MSI) that uniquely identifies a subject across a healthcare provider domain;
• and
• applies subject-specific data-sharing permissions to determine whether the clinical information is authorized to share with the external entity;
• retrieving the clinical information from the identified healthcare provider based on the authorization;
• generating a response including the clinical information in a standardized format via the engine;
• and
• transmitting the response to the external entity via the communication channel.

A computer-program product tangibly embodied in a non-transitory machine-readable

• storage medium, including instructions configured to cause one or more data processors to perform a set of actions including:
• detecting an event trigger related to an initiation of a subject encounter in a healthcare provider domain;
• generating, in real-time, one or more ADT (admission, discharge, transfer) messages associated with the event trigger via an interface of a healthcare provider of the healthcare provider domain, wherein the interface is configured to transmit the one or more ADT messages to a backend cell;
• receiving, in real-time, the one or more ADT messages from the interface by the backend cell that is configured within a cloud service;
• processing, via a frontend cell configured within the cloud service, the one or more ADT messages by assigning a master subject index to uniquely identify each subject across the healthcare provider domain;
• identifying one or more external entities from the one or more ADT messages based on identifiers assigned by the frontend cell;
• storing the one or more ADT messages in association with the master subject index and the identifiers to record an encounter lifecycle including the subject encounter and one or more related subject encounters;
• dynamically selecting from the one or more ADT messages, via the frontend cell, based on subject-based data-sharing permissions that are configured by the healthcare provider for each of the one or more external entities;
• and
• transmitting, in real-time, the selected one or more ADT messages to each of the one or more external entities via an interoperability interface configured within the frontend cell.

A computer-implemented method comprising:

• creating, via a console, a query endpoint that is associated with an interoperability interface, configured to transmit one or more requests from an external entity to access clinical information associated with a particular subject encounter from a healthcare provider domain;
• creating a delivery endpoint, via the console, to receive the clinical information back to the external entity;
• establishing a communication channel between the healthcare provider domain and the external entity by linking the query endpoint and the delivery endpoint, wherein the communication channel is configured for a subject associated with the particular subject encounter;
• processing, via an engine configured in a cloud service, the one or more requests received through the communication channel, wherein the engine:
• identifies the subject and a healthcare provider associated with the subject encounter holding the clinical information based on a master subject index (MSI) that uniquely identifies a subject across a healthcare provider domain;
• and
• applies subject-specific data-sharing permissions to determine whether the clinical information is authorized to share with the external entity;
• retrieving the clinical information from the identified healthcare provider based on the authorization;
• generating a response including the clinical information in a standardized format via the engine;
• and
• transmitting the response to the external entity via the communication channel.