What MediSync Connect is
MediSync Connect links MediSync to the clinical systems your organization already uses — hospital information systems (KIS) and practice management / EHR systems (PVS). It reads the right patient context out of your system and writes finished clinical documentation — notes, letters, and clinician-confirmed diagnoses — straight back into it, so there is no duplicate data entry and no copy-paste between applications. Connect is built on open healthcare standards and meets each system where it is: some expose a modern cloud API, some connect through a partner platform, and many run only inside the practice network. Connect supports all three through three connectivity models.Direct
Cloud-to-cloud over FHIR R4 or REST, for systems reachable over the internet
(including hospital FHIR endpoints that provide the ISiK profiles).
HealthHub
FHIR through the medatixx HealthHub partner platform, for the medatixx
product family.
On-site Agent
The MediSync Agent bridges systems that live only inside the practice network,
using their existing GDT, HL7 v2, or XML interfaces.
Why it matters
No rip-and-replace
MediSync layers on top of your existing KIS/PVS using the interfaces it already
exposes — no new core system, no proprietary protocol.
Bidirectional
Pull patient context in; file structured notes, letters, and the diagnoses the
clinician has confirmed back into the record.
Structured & coded
Clinician-confirmed diagnoses travel as coded data (ICD-10-GM) so they land as
structured, queryable entries rather than free text. Connect transfers codes; it
does not create diagnoses.
Security
Encrypted transport everywhere, scoped access, credentials stored encrypted, and —
for on-site connections — an outbound-only connector that needs no inbound firewall
changes.
Supported systems
MediSync Connect supports German KIS and PVS systems across all three models. The supported systems page lists each one with its status: available, early access, or coming soon. We work directly with practice- and hospital-software vendors to add new connectors.Don’t see your system? It may already be in progress. We regularly onboard new
connectors and coordinate directly with the vendor and your practice to add one.
Get in touch and we’ll tell you where
your system stands.
Continue
Standards & protocols
FHIR R4, ISiK, SMART on FHIR, HL7 v2, GDT, XML, CDA, REST.
Connectivity models
Direct, HealthHub, and the on-site Agent — and when each applies.
The MediSync Agent
The on-site connector for systems inside the practice network.
Supported systems
The full catalog of hospital and practice systems.
Data exchange
What data flows, and in which direction.
Getting connected
The onboarding path, and how to request a new integration.