> ## 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.

# Getting connected

> How a practice or hospital connects its system to MediSync — the onboarding flow, what each model needs, and how to request a new integration.

Connecting a system is driven from the MediSync dashboard, not through a public API.
The exact steps depend on your system's [connectivity model](/connect/connectivity-models),
and the dashboard guides you through the ones that apply. This page explains what to
expect and what to prepare.

## The onboarding flow

<Steps>
  <Step title="Choose your system">
    In MediSync, open **Settings → MediSync Connect** and pick your KIS or PVS. If you
    entered your system when you signed up, MediSync already recommends the right one.
  </Step>

  <Step title="Complete the prep steps">
    Some systems need a one-time action on the vendor or hospital side before MediSync can
    connect — the dialog lists exactly what's needed for your system (see
    [What each model needs](#what-each-model-needs)).
  </Step>

  <Step title="Install the Agent (on-site systems only)">
    If your system runs inside the practice network, install and pair the
    [MediSync Agent](/connect/medisync-agent) with a one-time 6-digit code. Skip this
    step for Direct and HealthHub systems.
  </Step>

  <Step title="Authorize or enter credentials">
    Depending on the system, you authorize via OAuth, enter API credentials, or enter the
    local interface configuration (for GDT/HL7, the import/export folder your PVS admin
    set up for MediSync).
  </Step>

  <Step title="Test & save">
    MediSync verifies the connection (for the Agent, that the folders or endpoint are
    reachable), then activates it. Patient context and documentation start flowing.
  </Step>
</Steps>

## What each model needs

<AccordionGroup>
  <Accordion icon="hospital" title="Direct — hospital KIS (ISiK FHIR)">
    From hospital IT:

    * The system's **FHIR R4 / ISiK** endpoint URL.
    * A **bearer token** for access (or an OAuth client registration for SMART-capable
      endpoints).

    No software is installed at the site. If the FHIR endpoint is only reachable inside
    the hospital network, it can be routed through the [Agent](/connect/medisync-agent)
    instead.
  </Accordion>

  <Accordion icon="cloud" title="Direct — cloud-capable PVS (REST / FHIR)">
    From the vendor:

    * **API access** enabled for your practice (some vendors require you to request it).
    * **Credentials** — typically a username/password that MediSync exchanges for a
      short-lived token, or an API key.
  </Accordion>

  <Accordion icon="link" title="HealthHub — medatixx family">
    * Book the relevant **interface / add-on** for your product in the vendor portal.
    * Authorize MediSync's access to your practice through **HealthHub**.
  </Accordion>

  <Accordion icon="server" title="On-site Agent — GDT / HL7 / XML">
    * Your **PVS administrator** configures an interface for "MediSync" (e.g. a GDT device)
      pointing at a shared import/export folder.
    * Some systems need a one-time vendor **licence** for the interface (for example a GDT
      add-on). The dialog tells you when this applies.
    * Install and pair the **MediSync Agent**, then enter the **same folder path** the PVS
      admin configured.
  </Accordion>
</AccordionGroup>

## Requesting a new integration

We support many systems already, and the list keeps growing. If your system isn't
listed yet, it may already be in progress — and if it isn't, we'll look at adding it. We
regularly onboard new connectors and coordinate **directly with the system vendor and
your practice** to work out the integration together.

To get started, reach out with:

* The **KIS or PVS** you run (and version, if you know it).
* Which **interfaces** it supports (FHIR, GDT, HL7, XML, REST, …).
* The **data flows** you need (patient import, note/letter export, diagnosis write-back,
  scheduling, …).

<CardGroup cols={2}>
  <Card title="Contact MediSync" icon="envelope" href="https://www.medisynchealth.ai/de/kontakt">
    Ask about your system or scope a new integration with our team.
  </Card>

  <Card title="Email support" icon="life-ring" href="mailto:support@medisync.me">
    Reach us directly at [support@medisync.me](mailto:support@medisync.me).
  </Card>
</CardGroup>

<Note>
  Standards recap: **FHIR R4** / **ISiK**, **SMART on FHIR (OAuth2)**, **HL7 v2**,
  **GDT**, structured **XML**, **HL7 CDA**, and **REST/JSON**. See
  [Standards & protocols](/connect/standards) for what each one enables.
</Note>