Skip to main content
Many German practice systems (PVS) run only on a server inside the practice and exchange data through local, file-based interfaces — they have no internet API for MediSync to call. The MediSync Agent bridges that gap.

​
What it is

The Agent is a small desktop application that runs on a workstation in the practice (Windows, with macOS and Linux builds available). It sits in the system tray, keeps a secure connection to MediSync, and translates between MediSync and the practice software’s existing interfaces.

Outbound-only

The Agent makes a secure outbound connection to MediSync. No inbound ports and no firewall changes are required at the practice.

Uses existing interfaces

It speaks the interfaces your PVS already supports — GDT, HL7 v2, structured XML, or a local FHIR endpoint — so no changes to your core system are needed.

Runs quietly

One-click install, tray icon, and automatic start at boot. Practice staff don’t have to launch anything.

Privacy-preserving

Transport is encrypted end to end. The Agent never logs patient data, and nothing is stored on it beyond the local configuration.

​
What it bridges

GDT / HL7 v2 (file-based)

Exchanges records through the import/export folders your PVS is configured to use — reading patient context the system drops there and writing examination/result records back.

Structured XML

For systems that accept a native XML document format, writes documentation in that format (one section per clinical block).

Local FHIR (deep link)

For systems that expose FHIR only on the local machine, the PVS launches MediSync in the current patient’s context and the Agent relays FHIR calls to that local endpoint.

On-site FHIR / REST

For a practice or hospital API that is reachable only inside the network, the Agent can relay calls to it so MediSync doesn’t need a public endpoint.

​
Install & pairing

Setup is driven entirely from the dashboard and takes a few minutes.
1

Start from the dashboard

In MediSync, open Settings → MediSync Connect and choose Install Agent. The dashboard offers the installer for your platform and shows a verification hash for the download.
2

Run the installer

Installers are code-signed. On Windows it’s a one-click install that needs no administrator rights. The Agent launches automatically when the install finishes.
3

Pair with a one-time code

The dashboard shows a 6-digit pairing code. Enter it in the Agent’s window to link it to your practice account. The code is single-use and expires after 15 minutes.
4

Connect your system

Add a connection for your PVS in the dashboard and provide the local interface configuration (for GDT/HL7, the same import/export folder your PVS admin set up for MediSync). The Agent verifies access, and the tray icon shows Connected.
For file-based systems, the practice’s PVS administrator first configures an interface (e.g. a GDT device named “MediSync”) pointing at a shared folder. You then enter that same folder path in the dashboard — there is no auto-detection, because the path is an install-time decision made in the PVS.

​
Security & compliance

Encrypted, authenticated transport

All communication runs over TLS with certificate validation enforced. The Agent authenticates to MediSync with its own credentials, established during pairing.

Verified, signed installers

Installers are code-signed, and the dashboard publishes a SHA-256 hash so practice IT can verify the binary before running it.

No PII in logs

The Agent is built to never write patient-identifying data to its logs.

Full-disk encryption

Because it runs on a clinical workstation, the Agent’s install guidance requires full-disk encryption (BitLocker / FileVault / LUKS), in line with German medical confidentiality obligations (§203 StGB).
The Agent is for practices whose systems run on-site. If your system already exposes a reachable FHIR/REST endpoint, no agent is needed — see Direct integration.

​
Next

Supported systems

Which systems use the Agent today.

Getting connected

The full onboarding flow, step by step.