Skip to content
MDDS-LLM MDDS-LLM Docs

Connection types

Every connection on the platform has a type that determines what it carries and who can see what.

Connection types at a glance

Section titled “Connection types at a glance”
TypeLabel in UIPurpose
P2PP2PCarries channel data between two servers.
Admin read-writeAdmin RWRemote Mirth management access, full control.
Admin read-onlyAdmin RORemote Mirth management access, view only.

P2P connections

Section titled “P2P connections”

P2P connections carry the actual integration data — HL7v2, DICOM, or other messages — between a source server and a target server through a secure gateway tunnel. They are provisioned from an approved grant between two agreement parties.

When to use: Any time you want to exchange clinical or operational data with a peer organization.

Route display: The connection list shows {sourceServer} → {targetServer} to indicate data direction.

Admin connections

Section titled “Admin connections”

Admin connections give one party remote management access to the other party’s Mirth server. They are offered by the server owner and must be explicitly accepted by the recipient.

  • Admin RW — full read-write access. Requires Standard or Enterprise tier.
  • Admin RO — read-only access. Available on any tier.

When to use: When a partner needs to configure or monitor your server, or when you need to manage a peer’s server remotely.

Privacy model

Section titled “Privacy model”

Server names and descriptions are visible to both parties once a connection exists. You do not need to own a server to see its name if you are a party to a connection involving it.

Secrets and connector configuration are not shared symmetrically:

DataWho can see it
Server name and descriptionBoth connection parties.
Shared secretOnly revealed via the dedicated View Secret action to the owning side. Never in list views.
Connector configurationOnly the target server’s owner. Contains registration tokens.
Section titled “Related”