Glossary
Definitions for the terms you’ll see across the platform.
Agreement
Section titled “Agreement”The active relationship between two organizations, created when a peering request is accepted. Agreements make it possible to share channels and provision connections.
Channel
Section titled “Channel”A message route on a server. A published channel is one exposed through the Contact System so partners can send to it or receive from it. Channels have a direction.
Connection
Section titled “Connection”A secure tunnel between two servers. A P2P connection carries channel data; an Admin connection carries remote management access (read-write or read-only).
Direction
Section titled “Direction”Whether a channel listens (receives from peers) or sends (delivers to a peer). A listener can accept from many peers (N:1 fan-in); a sender targets one peer per connector.
Discoverable
Section titled “Discoverable”A profile setting that controls whether your organization appears in the Directory for others to find.
Gateway
Section titled “Gateway”The technology that powers connections — encrypted peer-to-peer tunnels that traverse firewalls without inbound network changes. See Gateway overview.
Permission given to a specific peer to access a specific channel. Grants are scoped and revocable.
Listener / Sender
Section titled “Listener / Sender”The two Gateway Connector types on a Mirth channel: a Listener (source) receives data from authorized peers; a Sender (destination) delivers data to a remote peer.
Organization
Section titled “Organization”Your healthcare entity on the platform. Most resources belong to an organization.
Peering request
Section titled “Peering request”An invitation sent to another organization to establish an agreement.
Self-peering
Section titled “Self-peering”Peering one of your own servers with another (or itself) — useful for testing the full flow without a partner.
Server
Section titled “Server”An integration server (Open Integration Engine / Mirth) that you operate. Servers run channels and are the endpoints of data flows.
Shared secret
Section titled “Shared secret”A per-connection secret used to authenticate a tunnel. Secrets are never shown in lists and are revealed only once, to the owning side.
Your subscription level (Free, Standard, Enterprise), which determines limits and available features.