> ## Documentation Index
> Fetch the complete documentation index at: https://docs.medisync.me/llms.txt
> Use this file to discover all available pages before exploring further.

# MediSync Connect

> The interoperability layer that connects MediSync to the hospital and practice systems you already run — over open healthcare standards.

## 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, diagnoses, and letters — 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**.

<CardGroup cols={3}>
  <Card title="Direct" icon="cloud">
    Cloud-to-cloud over **FHIR R4** or **REST**, for systems reachable over the internet
    (including **ISiK**-conformant hospital FHIR endpoints).
  </Card>

  <Card title="HealthHub" icon="link">
    **FHIR** through the medatixx **HealthHub** partner platform, for the medatixx
    product family.
  </Card>

  <Card title="On-site Agent" icon="server">
    The **MediSync Agent** bridges systems that live only inside the practice network,
    using their existing **GDT**, **HL7 v2**, or **XML** interfaces.
  </Card>
</CardGroup>

## Why it matters

<CardGroup cols={2}>
  <Card title="No rip-and-replace" icon="layer-group">
    MediSync layers on top of your existing KIS/PVS using the interfaces it already
    exposes — no new core system, no proprietary protocol.
  </Card>

  <Card title="Bidirectional" icon="arrows-rotate">
    Pull patient context in; file structured notes, diagnoses, and letters back into
    the record.
  </Card>

  <Card title="Structured & coded" icon="table-cells">
    Diagnoses travel as coded data (ICD-10-GM) so they land as structured, queryable
    entries — not free text.
  </Card>

  <Card title="Secure by design" icon="shield-check">
    Encrypted transport everywhere, scoped access, credentials stored encrypted, and —
    for on-site connections — an outbound-only connector that needs no inbound firewall
    changes.
  </Card>
</CardGroup>

## A broad and growing catalog

MediSync Connect already supports a wide range of German KIS and PVS systems across
all three models — and the list keeps growing. We work directly with practice- and
hospital-software vendors to add new connectors.

<Note>
  **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](https://www.medisynchealth.ai/de/kontakt) and we'll tell you where
  your system stands.
</Note>

## Continue

<CardGroup cols={2}>
  <Card title="Standards & protocols" icon="book" href="/connect/standards">
    FHIR R4, ISiK, SMART on FHIR, HL7 v2, GDT, XML, CDA, REST.
  </Card>

  <Card title="Connectivity models" icon="diagram-project" href="/connect/connectivity-models">
    Direct, HealthHub, and the on-site Agent — and when each applies.
  </Card>

  <Card title="The MediSync Agent" icon="server" href="/connect/medisync-agent">
    The on-site connector for systems inside the practice network.
  </Card>

  <Card title="Supported systems" icon="network-wired" href="/connect/supported-systems">
    The full catalog of hospital and practice systems.
  </Card>

  <Card title="Data exchange" icon="arrow-right-arrow-left" href="/connect/data-exchange">
    What data flows, and in which direction.
  </Card>

  <Card title="Getting connected" icon="route" href="/connect/getting-connected">
    The onboarding path, and how to request a new integration.
  </Card>
</CardGroup>