EN
Contact

How it works

4 Steps. Done.

From an empty server to an ISiK-compliant healthcare backend — no FHIR team required, no regulatory deep-dive needed.

  1. Install

    One command. The gateway starts with PostgreSQL, Keycloak and the FHIR server. Docker Compose for quick start, Helm chart for Kubernetes, or Ansible for automated on-prem deployment.

    # Option A: Docker Compose (on-prem / dev)
    git clone <repository-url>
    cd gateway
    docker compose up -d
    # Option B: Kubernetes (cloud / production)
    helm install fhir-gateway deploy/cloud/helm/fhir-gateway -f values.yaml
    # Option C: Ansible (remote server)
    ./deploy/on-prem/install.sh 192.168.1.100 deploy_user

    Kubernetes / Helm

    Production Helm chart with HPA (2–10 pods), Pod Disruption Budget, Prometheus integration and rolling updates. AWS EKS, Azure AKS, GKE.

    Docker Compose

    Fastest start for on-prem: one Compose file with all services, resource limits and health checks. Monitoring stack included.

    Ansible Installer

    Automated deployment on Ubuntu or RHEL. Docker installation, build, configuration and health checks — one command.

    Multi-tenant from day one

    Each tenant gets isolated data via HAPI Partitioning. One gateway, unlimited facilities.

  2. Connect your systems

    Your HIS, PMS, LIS or ERP doesn't speak FHIR? No problem. The gateway ships adapters for all common formats. You configure the connection — we handle the mapping.

    HL7v2 / MLLP

    ADT, ORU, ORM, SIU — the MLLP listener receives HL7v2 messages and automatically translates them to FHIR R4.

    REST API

    Your system has a REST interface? The REST adapter connects, fetches data and maps it to the 353 German FHIR profiles.

    CSV / XML / Database

    Even legacy systems without APIs can be connected — via file import, database views or the AI mapping assistant.

    AI Mapping Assistant

    For proprietary formats: describe your data format, the AI assistant suggests the FHIR mapping. You review and approve.

    177 ready-made mappings cover all German profile types — Gematik, KBV, ISiK, MII, HL7 DE. No mapping team needed.

  3. Configure Telematikinfrastruktur

    You have an HSK connector, a KIM transport provider, TIM transport access? Enter the credentials — the gateway handles the protocol complexity. No gemSpec study required.

    HSK Connector

    Upload certificate, configure endpoint. The gateway speaks SOAP with the connector and exposes FHIR APIs.

    Gematik IDP

    OAuth2-based authentication against the Gematik Identity Provider — for ePA, E-Rezept and VZD access.

    KIM Transport & TIM Transport

    KIM transport (secure system-to-system messaging) and TIM transport (FHIR data exchange via TI-Messenger) — you choose your provider, we integrate the protocol.

    ePA & E-Rezept

    Electronic health record and e-prescription service — complete integration via FHIR APIs, VAU-encrypted.

    Bring Your Own Provider: You choose your KIM transport provider, your TIM transport provider, your HSK. The customer uses their provider's end-user apps — the gateway provides the system-to-system integration layer.

  4. Done. Your healthcare backend is live.

    From this moment, your systems speak FHIR. ISiK-compliant. TI-connected. All on your server, under your control.

    ISiK-compliant

    Level 4/5 — all mandatory profiles implemented. No manual profile work, no yearly rework.

    FHIR R4 Server

    Full HAPI FHIR R4 JPA Server — Search, CRUD, Bundles, Subscriptions, everything out of the box.

    Dashboard & Monitoring

    Admin portal with tenant management, API key management, onboarding wizard and real-time monitoring.

    Updates included

    New ISiK level? New Gematik specification? We deliver the update. You deploy it. Done.

Without vs. with the Gateway

TaskBuild yourselfWith FHIR Link
Implement FHIR profiles6–12 months, FHIR team353 profiles ready
ISiK complianceAnnual reworkUpdates included
TI integrationSOAP, certificates, gemSpecEnter credentials
HL7v2 migrationBuild translation layer177 mappings ready
ePA & E-RezeptIntegrate each serviceBuilt in
Regulatory effortOngoing, every levelWe stay compliant, you deploy
Time to market12–24 monthsDays

What you get from day one

Not a prototype. Not an MVP. A production-ready healthcare backend.

FHIR R4 Server

Full HAPI FHIR JPA Server with Search, CRUD, Bundles, Transactions and Subscriptions.

353 German profiles

ISiK, Gematik, KBV, MII, HL7 DE — every published German FHIR profile is registered and validated.

Complete TI

HSK, IDP, KIM transport, TIM transport, ePA, E-Rezept, VZD — the entire Telematikinfrastruktur through one gateway.

Multi-tenant

One gateway for unlimited facilities. Data strictly isolated via HAPI Partitioning.

Admin portal

Tenant management, onboarding wizard, API key management, dashboard and monitoring.

Adapter SDK

REST, HL7v2/MLLP, CSV, database — plus AI mapping assistant for proprietary formats.

1,600+ tests

Automated test suite including Gematik Reference Validator. Every update is validated.

Self-hosted

Your server. Your data. Your control. On-premises, your own cloud or data center.

Ready?

Get in touch or request a demo.

Or write to us: kontakt@brainwave-software.de